[08:35] <dholbach> good morning
[09:33] <bilalakhtar> tumbleweed: around?
[09:34] <tumbleweed> bilalakhtar: yes
[09:34] <bilalakhtar> tumbleweed: did you get my mail?
[09:35] <bilalakhtar> Thanks in advance!
[09:35] <tumbleweed> bilalakhtar: you don't want to see my inbox :P (yes I did)
[09:35] <bilalakhtar> hehe, thanks tumbleweed !
[09:35] <bilalakhtar> TyT, I just thought if I sent to the right address, since you have so many
[09:41] <AnAnt> Hello
[10:14] <tumbleweed> https://code.edge.launchpad.net/~cosme/ubuntu/maverick/freeimage/freeimage/+merge/33347 <- is it possible to switch from orig.tar.gz -> bz2 without an upstream version bump?
[10:17] <directhex> tumbleweed, i don't think so
[10:18] <tumbleweed> that's what I thought :)
[10:58] <bilalakhtar> +$(RM) libdumb.so
[10:58] <bilalakhtar> ^^ is the only diff remaining from Debian after a merge
[10:58] <bilalakhtar> what should I do
[10:58] <bilalakhtar> ?
[10:58] <bilalakhtar> I prefer sync and forward to Debian
[10:59] <bilalakhtar> This diff removes the shared library after a clean
[11:06] <tumbleweed> bilalakhtar: does that make any difference to the build? or is it only needed when working on the package?
[11:06] <bilalakhtar> tumbleweed: I have alreadyu requested sync
[11:06] <tumbleweed> ok
[11:06] <bilalakhtar> tumbleweed: no it doesn't make any difference to the build
[11:06] <tumbleweed> that's what I'd do then
[11:09] <bilalakhtar> tumbleweed: bhavani already requested sync, what happened there?
[11:09] <tumbleweed> requestsync checks for existing syncs, but there is probably some lag in processing e-mail sync requests
[11:11] <bilalakhtar> tumbleweed: I requested a new sync, ah it came bug #622630
[11:11] <bilalakhtar> tumbleweed: should I mark mine dup?
[11:12] <tumbleweed> bilalakhtar: oh, well there you go. bhavani didn't use request sync :) shout at him :P
[11:13] <bilalakhtar> tumbleweed: so would you prefer his or mine?
[11:13] <tumbleweed> did you read his one?
[11:13] <tumbleweed> it's incomplete because it didn't build
[11:14] <bilalakhtar> tumbleweed: it builds here
[11:14] <bilalakhtar> pbuilder
[11:15] <bilalakhtar> tumbleweed: wait I am trying another ubild, this time with latest updates
[11:15] <bilalakhtar> tumbleweed: BRB in 10 mins
[11:15] <tumbleweed> ok, cool. mark his as a duplicate of yours (or vice versa)
[11:15] <bilalakhtar> tumbleweed: I will see after this build succeeds
[11:15] <bilalakhtar> it should
[11:19] <bilalakhtar> tumbleweed: NO
[11:19] <bilalakhtar> tumbleweed: BUILD HAS FAILED!
[11:19] <bilalakhtar> tumbleweed: CANCEL ACK_SYNC!
[11:19] <bilalakhtar> wierd
[11:19] <tumbleweed> indeed it has
[11:19] <bilalakhtar> it built on my PPA
[11:20] <bilalakhtar> tumbleweed: it has? what do you mean by that?
[11:20] <tumbleweed> it has failed
[11:20] <bilalakhtar> goog
[11:20] <bilalakhtar> *good
[11:30] <tumbleweed> micahg: you subscribed ubuntu-sponsors to bug #614912, but in it you say you want two acks first. I only see one.
[11:30] <and471> tumbleweed, thanks again for the sponsor
[11:35] <ari-tczew> hello tumbleweed, nice to see you :P I've got case for you :)
[11:35] <tumbleweed> err, yeah?
[11:35] <ari-tczew> tumbleweed: oh, I wanted ping you on bug agg, just you touch it
[11:36] <ari-tczew> btw. tumbleweed, are you familiar with NMU
[11:36] <ari-tczew> ?
[11:36] <tumbleweed> in debian?
[11:36] <AnAnt> I don't think that this diff: $(RM) <some binary file> is needed
[11:36] <ari-tczew> tumbleweed: yea in Debian
[11:37] <AnAnt> because the binary file , if it doesn't get cleaned, it won't be represented in debdiff anyways
[11:37] <AnAnt> bilalakhtar: ^
[11:37] <tumbleweed> AnAnt: yes, that's waht we were saying. But the package can't be synced because it doesn't build
[11:37] <AnAnt> ah
[11:38] <tumbleweed> ari-tczew: yes, but I'm not a DD so I need sponsorship for NMUs
[11:38] <ari-tczew> tumbleweed: I wanted to ask whether NMU phrase in debian/changelog in version is necessary?
[11:38] <tumbleweed> I think policy requires it
[11:39] <bilalakhtar> AnAnt: Back
[11:39] <ari-tczew> tumbleweed: answering to your comment, I forgot to did bzr add :(
[11:39] <bilalakhtar> AnAnt: yes it doesn't build, so I am lookin at what can be done
[11:39] <tumbleweed> ari-tczew: it's a "must" in Debian Developer's Reference, section 5.11.2
[11:40] <ari-tczew> tumbleweed: you wrote: Unnecessary diversion from debian
[11:41] <ari-tczew> I did this, because I remember that some sponsors poke me for fixing lintian's warnings
[11:41] <tumbleweed> ari-tczew: yes, we want to be able to sync again in the future
[11:41] <ari-tczew> I know that we shouldn't change Debian package most
[11:41] <tumbleweed> I used to prod sponsorees about lintian warnings when I was new to it, but I've become more conservative
[11:42] <tumbleweed> if the lintian warning is about something serious, then deal with it (i.e. read the warnings)
[11:42] <tumbleweed> but if not, ignore it. (Most packages generate a few warnings)
[11:43] <ari-tczew> tumbleweed: so do you suggest to drop these 2 changes?
[11:43] <ari-tczew> in debian/control and debian/README.source
[11:43] <tumbleweed> yes
[11:44] <ari-tczew> tumbleweed: ok, I'll drop it, but please don't remember this as my technical-issues. I just do it, because in the past I've been warned to fixing lintian's warning, ok?
[11:44] <tumbleweed> ari-tczew: I won't hold it against you :)
[11:46] <ari-tczew> tumbleweed: ok. I asked you about NMU because I'd like to try get first NMU through forwarding this change to Debian. what do you think about it?
[11:46] <bilalakhtar> tumbleweed: As for that FTBFS, I got it
[11:46] <tumbleweed> ari-tczew: sounds good
[11:46] <tumbleweed> bilalakhtar: great
[11:47] <bilalakhtar> tumbleweed: now confirming it by a build
[11:47] <ari-tczew> tumbleweed: I'd like to prepare SRUs for other releases. are you interested in sponsoring?
[11:47] <bilalakhtar> actually, recently the ubuntu devs splitted the audacious-dev package
[11:48] <tumbleweed> ari-tczew: sure
[11:48] <ari-tczew> tumbleweed: what do you think about adding both tags LP: # and Closes: # ?
[11:48] <ari-tczew> I think that it's good.
[11:49] <ari-tczew> into debian/changelog of course
[11:49] <tumbleweed> if it's an ubuntu upload and the debian bug is linked to the lp one, it probably isn't necessary. For debian uploads one does see people doing this
[11:50] <ari-tczew> tumbleweed: so do you want to see only LP: # ?
[11:50] <tumbleweed> ari-tczew: I don't mind, up to you
[11:52] <ari-tczew> tumbleweed: are sure about dropping Depends: ${misc:Depends} ?
[11:52] <ari-tczew> is it nothing important?
[11:53] <tumbleweed> ari-tczew: you can see if it's important, by seeing what gets substituted
[11:53] <ari-tczew> tumbleweed: I've tested package and it can be installed without this change.
[11:53] <tumbleweed> I'd assume that, yes
[12:00] <ari-tczew> tumbleweed:  review:  Resubmit
[12:00] <ari-tczew> :)
[12:00] <bilalakhtar> tumbleweed: no it isn't working, I think I should let Bhavani work on this one; he came here first
[12:00] <tumbleweed> bilalakhtar: ok, mark as dup
[12:00] <bilalakhtar> done
[12:02] <tumbleweed> ari-tczew: I understand "review: resubmit" to mean that the merge should be resubmitted. To actually resubmit, you set the status to resubmit (but I'm reviewing anyway, so rather don't)
[12:03] <AnAnt> how can I unpack an .egg file ?
[12:03] <tumbleweed> AnAnt: it's a zip file
[12:03] <ari-tczew> tumbleweed: so in future should I use 'comment only'?
[12:04] <tumbleweed> no, if you set the status to resubmit, it creates a new merge proposal
[12:04] <tumbleweed> i.e. it resubmits it
[12:04] <ari-tczew> tumbleweed: is it wrong?
[12:04] <tumbleweed> is what wrong?
[12:06] <ari-tczew> tumbleweed: setting resubmit
[12:08] <tumbleweed> ari-tczew: no, but now it's unecessary, because I knew what you meant
[12:08] <ari-tczew> aha
[12:09] <AnAnt> tumbleweed: tried unzip, but didn't work
[12:10] <tumbleweed> AnAnt: no clue then. Python eggs are definitly zip files
[12:23] <ari-tczew> tumbleweed: ok thanks for sponsoring, I'll prepare patches for lucid, karmic and jaunty
[12:24] <Bachstelze> tumbleweed: should I make a debdiff against maverick for #622319 ? I see you unsubscribed sponsors
[12:25] <ari-tczew> Bachstelze: please use on IRC phrase: bug 622319
[12:26] <tumbleweed> Bachstelze: ubuntu has already diverged from debian (in maverick) so yes that sounds sensible
[12:26] <tumbleweed> Bachstelze: obviously make sure debian has the patch, (and any other patches we have applied to their source)
[12:29] <ari-tczew> tumbleweed: Artur: Please pass debian the correct patch, rather than just a LP Link - what do you mean?
[12:32] <tumbleweed> the current debian patch contains a bug report, and a link to the lp bug
[12:32] <tumbleweed> "the current debian bug report"
[12:32] <ari-tczew> tumbleweed: but it's not me do this...
[12:33] <tumbleweed> what do you mean?
[12:33] <ari-tczew> tumbleweed: please look at field "From:" on Debian's bug
[12:33] <ari-tczew> it's not me
[12:34] <tumbleweed> yes? that doesn't mean you can't contribute a fix
[12:34] <ari-tczew> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575620
[12:34] <ari-tczew> tumbleweed: I always sending a patch to Debian, but after sponsorship in Ubuntu.
[12:35] <ari-tczew> You said that this "only give link to LP" is my change, but it is not.
[12:35] <tumbleweed> ok, that's great. I didn't say that change was yours
[12:36] <tumbleweed> or at least I didn't mean to imply that
[12:36] <ari-tczew> tumbleweed: ok, no problem. Scarely after sponsorship in Ubuntu, because then I'm sure that my patch is correct.
[12:36] <tumbleweed> that works for me
[12:36] <ari-tczew> :)
[12:37]  * ari-tczew is hungry, going away. Later back to work.
[12:56] <Bachstelze> tumbleweed: debdiff for Maverick posted, should I resubscribe -sponsors?
[12:57] <tumbleweed> Bachstelze: normally yes, but I'll look now, so don't worry
[12:57] <Bachstelze> okay, thanks
[12:58] <tumbleweed> Bachstelze: any reason why you are removing dead code?
[12:59] <tumbleweed> it seems somewhat unecessary
[12:59] <Bachstelze> because the upstream commit did it, but I guess we could keep it
[12:59] <tumbleweed> ok, that's fine
[13:00] <tumbleweed> It would be good if you linked to the upstream commit in the patch header. http://dep.debian.net/deps/dep3/ is a good standard for describing patches
[13:03] <ari-tczew> who is there a Debian Developer?
[13:09] <Bachstelze> tumbleweed: then there are two upstream commits modifying the same file, should I make a separate debian/patch with header for each one?  I think I read in the packaging guide that you should avoid having several patches modifying the same file
[13:12] <tumbleweed> No, you can just link to both of them
[13:27] <Bachstelze> tumbleweed: done
[13:30] <Bachstelze> argh, no, for some reason the second patch was left out
[13:34] <Bachstelze> there
[13:51] <lucas> LP#518122 needs someone with some time (i.e not me) to do a no-changes upload to -updates
[14:16] <ari-tczew> is it require FFe? bug 622626
[14:19] <AnAnt> Laney: ^
[14:19] <tumbleweed> ari-tczew: -1 -> -2 is *probably* ok
[14:20] <ari-tczew> tumbleweed: I'm confused. I remember discussion about FeatureFreeze that it's time for only bug-fixes upload.
[14:21] <tumbleweed> ari-tczew: I haven't looked at the changelog. Is it a bugfix? (looks)
[14:21] <AnAnt> it fixes a couple of Debian bugs
[14:21] <ari-tczew> Laney: can I get to know your opinion?
[14:22] <tumbleweed> none of those seem serious enough, but yes, ask Laney
[14:25] <devfil> ari-tczew, it doesn't
[14:26] <ari-tczew> so I guess that it can't be passed without FFe
[14:27] <devfil> ari-tczew, it doesn't require a FFe
[14:27] <tumbleweed> ari-tczew: no it doesn't need one, the question is, is the upload necessary / helpful?
[14:27] <ari-tczew> devfil: and can be synced?
[14:27] <devfil> tumbleweed, it is
[14:28] <devfil> tumbleweed, next time (maverick+1) the package will be autosynced so it's ok
[14:28] <devfil> ari-tczew, yes
[14:29] <tumbleweed> devfil: agreed re autosync, but I haven't looked at a debdiff, and some people have been grumbling about almost-no-change syncs
[14:30] <ari-tczew> devfil, tumbleweed, AnAnt: I remember that some sponsors said me that syncs are not good during FF because it's getting some resources etc...
[14:30] <devfil> tumbleweed, looks like there are fixes
[14:31] <ari-tczew> personally I don't want fight with syncs during FeatureFreeze, it's OK for me, but now I'm confused and I'd like get to know opinion so loving Feature Freeze Laney
[14:33] <tumbleweed> ari-tczew: if uploaded with syncpackage (which still seems to be a grey area), I don't see the difference between fixing a bug with a sync or an ubuntu1 upload. Except that the sync saves us work in the future
[14:33] <Bachstelze> tumbleweed: what's in the Ubuntu-Bug DEP3 field? (or where can I get it, it's not on archive.ubuntu.com yet)
[14:34] <tumbleweed> Bachstelze: I added this below your Origin header: "Bug-Ubuntu: http://launchpad.net/bugs/622319" - you can see the upload here: http://launchpad.net/ubuntu/+source/opensc
[14:34] <ari-tczew> tumbleweed: I agree with you, but as I said, I'm confused.
[14:35] <tumbleweed> ari-tczew: people may be concerned about new changes from debian causing regressions
[14:37] <tumbleweed> devfil: seeing as you are here, did you see bug 620280? (I subscribed you)
[14:38] <devfil> tumbleweed, it's pretty useless to subscribe me to a bug, just send me an email next time
[14:38] <tumbleweed> devfil: aah, I thought LP sends an e-mail when you subscribe someone
[14:39] <devfil> tumbleweed, yes, but I receive a lot of emails from launchpad so I can miss someone
[14:39] <tumbleweed> right, that's why I'm pinging you :)
[14:39] <devfil> tumbleweed, will fix this ASAP (tomorrow) ;) thank you
[15:17] <smallfoot-> package Firefox 4 beta and put it in repo
[15:22] <micahg> tumbleweed: sorry, I should've commented, you can be the second ack, I gave up on the review/papercuts team
[15:23] <micahg> smallfoot-: it's on our list, chrisccoulson is actually fixing up Firefox 4 packaging so we can do that
[15:23] <micahg> *our = Ubuntu Mozilla Team
[15:26] <smallfoot-> awesome!
[15:26] <smallfoot-> will it be in maverick?
[15:26] <chrisccoulson> smallfoot-, no
[15:26] <smallfoot-> then where the hell will it be?
[15:27] <chrisccoulson> smallfoot-, it will be in a PPA
[15:27] <smallfoot-> oh
[15:27] <smallfoot-> long time ago ubuntu had firefox 2 installed by default, but in repo was available firefox 3
[15:27] <smallfoot-> i think 4 should be in repo
[15:28] <Bachstelze> smallfoot-: we're past Feature Freeze for Maverick IIRC
[15:28] <Bachstelze> so no new packages
[15:28] <chrisccoulson> smallfoot- we aren't shipping a beta browser in the archive. we'll only be shipping a single version of firefox at any one time
[15:28] <chrisccoulson> but it will be available in a PPA (and the daily builds are already available)
[15:29] <smallfoot-> oh cool
[15:30] <smallfoot-> fair enough
[15:30] <smallfoot-> even though they ought to backport firefox 4
[15:31] <micahg> smallfoot-: who is they?
[15:31] <chrisccoulson> "they"?
[15:31] <smallfoot-> canonical or whoever is responsible of putting stuff in the repository
[15:32] <micahg> smallfoot-: we'll probably be backporting 4.1 or whatever is after 4.0, but that only happens when the default browser is EOL
[15:33] <smallfoot-> oh
[15:33] <smallfoot-> cuz it will be shit boring for ppl to run Firefox 3 on Ubuntu when all their friends on Windows have cool new Firefox 4
[15:33] <micahg> !language | smallfoot-
[15:34] <micahg> smallfoot-: that's what the PPA is for
[15:34] <smallfoot-> normal ppl dont use ppa, its only advanced users
[15:35] <micahg> smallfoot-: no, normal people do use PPAs, if they have something that's wanted
[15:35] <ari-tczew> smallfoot-: PPA is not hard to use
[15:35] <smallfoot-> i dont even know what PPAs exist
[15:35] <ari-tczew> you can also create your own repository!
[15:36] <vish> micahg: hmm?  "I gave up on the review/papercuts team" what do you mean?
[15:36] <smallfoot-> no cuz packaging stuff in ubuntu is impossible, you have to read 100 pages of stuff, download 100 stuffs, etc
[15:36] <micahg> vish: waiting for 2 ACKs like we discussed
[15:36] <micahg> smallfoot-: we do the packaging, you just install
[15:37] <ari-tczew> nothing never was easy like snap at start
[15:37] <vish> micahg: i dont understand , i already told you if its just to make it more specific , go ahead.. you hadnt replied on the bug and i had to poke you yesterday , not sure what else i'm supposed to do..
[15:37] <ari-tczew> smallfoot-: do you want use PPA? you have to only add lines to /etc/apt/sources.list
[15:38] <ari-tczew> you don;t need package if you don't want ...
[15:39] <smallfoot-> i would not manually edit configuraiton files with a text editor
[15:39] <smallfoot-> neither would anyone else that is not a nerd
[15:40] <ari-tczew> smallfoot-: do you use gnome?
[15:41] <smallfoot-> yes
[15:41] <ari-tczew> smallfoot-: then you can use graphic editor for /etc/apt/sources.list
[15:41] <tumbleweed> also, you can add PPAs via software sources
[15:42] <ari-tczew> System -> Administration -> sources software
[15:42] <smallfoot-> yes
[15:42] <tumbleweed> but smallfoot- is right, PPAs aren't for run-of-the-mill users, and that's correct. They can use the version of firefox that our mozilla team recommends and provides.
[15:43] <smallfoot-> then they will be stuck with firefox 3, while their friends with windows all can enjoy firefox 4
[15:43] <tumbleweed> smallfoot-: we can't provide the latest version of everything *and* stability, the two don't go hand in hand
[15:45] <micahg> smallfoot-: that's the nature of the distro, stable releases don't change unless there are extenuating circumstances
[15:45] <smallfoot-> but im sure firefox 4  is perfectly stable on windows 7
[15:45] <smallfoot-> how come you can run firefox 4 perfectly stable on windows 7, but not on ubuntu?
[15:46] <micahg> smallfoot-: that's not the question, there are other apps that depend on a certain series of Firefox
[15:46] <chrisccoulson> smallfoot-, stability is not the only criteria. because it's still in beta, it doesn't have any security updates
[15:48] <smallfoot-> micahg, like which apps?
[15:48] <chrisccoulson> smallfoot-, "apt-cache rdepends xulrunner-1.9.2" ?
[15:48] <smallfoot-> chrisccoulson, thats why firefox3 should be installed by default, and firefox4 optional in repo
[15:48] <smallfoot-> xulrunner isnt firefox
[15:48] <chrisccoulson> smallfoot-, yes it is
[15:48] <chrisccoulson> it's exactly the same codebase
[15:50] <ari-tczew> tumbleweed: bug 393923 needs some love :)
[15:50] <micahg> smallfoot-: we have 2 people working on Mozilla stuff at the moment, that's all, there are not enough resources to support 2 versions of Firefox in the repos, in addition that causes other problems with defaults/updates/conflicts
[15:51] <smallfoot-> ok
[15:51] <tumbleweed> ari-tczew: tasks approved
[15:52] <lfaraone> micahg: although pyxpcom is being packaged separately in Debian, you want it to have a maintainer who will keep it up-to-date with Firefox updates before you include it in Maverick, right?
[15:52]  * lfaraone is writing an email summarizing the Sugar browser situation, and wants to make sure he understands it correctly.
[15:55] <micahg> lfaraone: most likely yes since it seems to have been abandoned upstream, glandium said he'd talk to the Sugar team
[15:55] <chrisccoulson> micahg - did you have a look at the packaging?
[15:56] <micahg> chrisccoulson: I only had time to do a test build, not look in depth, and it builds itself at least with our xulrunner with the one caveat I told you about
[15:56] <micahg> the next test would be to compile something against it
[15:56] <chrisccoulson> is it installing components in to /usr/lib/xulrunner-1.9.2.8/components?
[15:56]  * micahg checks
[15:57] <micahg> chrisccoulson: yep, so you're right, we'll need to figure out a way around that
[15:57] <chrisccoulson> yeah, we'll need to build those components in to an extension and install it that way i think
[15:58] <chrisccoulson> that should work
[15:59] <micahg> chrisccoulson: well, the problem is extensions don't have the same API access as pyxpcom
[15:59] <chrisccoulson> it should be ok. it's shipping binary XPCOM components, and you can ship those in extensions and have the same level of access as you normally would
[16:00] <Bachstelze> lfaraone: since you're a DD, can I have a PM please? I'm lookin for a sponsor for my package in Debian
[16:01] <lfaraone> micahg: I tested pyxpcom and it worked with sugar-browse-activity-*, at least.
[16:01] <lfaraone> Bachstelze: sure, although rarely are such things worthy of a PM rather than just public discussion :)
[16:02] <Bachstelze> well, we're on an Ubuntu channel :p
[16:03] <micahg> lfaraone: that's good at least
[16:08] <ari-tczew> lfaraone: are you DD?
[16:13] <lfaraone> ari-tczew: that's what people keep telling me.
[16:33] <lfaraone> micahg: oh, Mike Hommey == glandium. Right, he already sent us a mail (to debian-olpc-devel) asking us to test his package, which we did.
[16:36] <lfaraone> micahg: speaking of which, do you have a link to the dsc of his package? I can't seem to find it on mozilla.debian.net anymore.
[16:36]  * micahg wonders if it's past new
[16:37] <micahg> lfaraone: http://people.debian.org/~glandium/pyxpcom_0.0~hg20100212-1.dsc
[16:43] <lfaraone> aha.
[17:08] <lfaraone> If I have a local copy of the Ubuntu archive, can I mount that in pbuilder as the cached apt contents
[17:08] <lfaraone> *?
[17:09] <james_w> lfaraone: not if it is laid out like a normal mirror of the Ubuntu archive, as the cached apt contents are a flat directory structure I believe
[17:09] <tumbleweed> lfaraone: but you can configure your pbuilder not to use a cache
[17:10] <lfaraone> james_w: I used apt-mirror.
[17:10] <tumbleweed> james_w: correct re structures
[17:10] <lfaraone> hmmm. could I have it mount the directory containing the mirror as an extra dir and just point to that folder in /etc/apt/sources.list?
[17:11] <tumbleweed> that'd probably work
[17:11] <tumbleweed> personally, I just point my pbuilders at my local apt-cacher-ng (and have them not cache debs themselves)
[17:12]  * lfaraone likes to be able to build packages without internet access, say, on the train, so it's useful to have a full copy of the archive.
[17:12] <james_w> lfaraone: yes, that would work. It would copy the packages around unless you disable the cache dir. I don't know if apt is sensible enough to just use the files on disk if it is a local mirror and there is no cache
[17:12] <lfaraone> *cobwuilder
[17:12] <lfaraone> *cowbuilder
[17:12] <tumbleweed> james_w: it is if you use file:// urls
[17:14] <lfaraone> hm. another thing I was looking at, I see that people use sbuild with aufs to mimick what is used on the buildds. Would it be possible to go further and use sbuild + tempfs with aufs? (so that the unpacking etc doesn't need to be done on the disk, it can just be done in RAM and discarded afterwards)
[17:14] <lfaraone> *tmpfs
[17:17] <tumbleweed> lfaraone: I build in tmpfs, yes. But you need >4G of ram for most packages (haven't tried openoffice :) )
[17:17] <lfaraone> tumbleweed: hehe. I've 4G myself.
[17:17] <tumbleweed> tmpfs on /var/cache/pbuilder/build type tmpfs (rw,size=5G)
[17:18] <tumbleweed> haven't run into issues with that
[19:01] <lfaraone> micahg: hmm. is it a known issue that xulrunner-1.9.2 stalls on "Setting up" when installing?
[19:02] <micahg> lfaraone: no...it shouldn't
[19:02] <micahg> which release?
[19:02] <lfaraone> micahg: on Maverick I attempted to build pyxpcom in pbuilder and xulrunner-bin was using 100% CPU. (and I left it there for an hour and a half)
[19:03] <micahg> weird, I built it locally without issue, can you login and see where it's stuck?
[19:06] <lfaraone> micahg: how can I determine that? (I'm running cowbuilder --login right now and it froze again while Setting up xulrunner-1.9.2)
[19:06] <micahg> can you do ps in cowbuilder env?
[19:06] <lfaraone> micahg: "top" (run from outside the enviornment) shows xulrunner-bin using 100%cpu.
[19:07] <lfaraone> micahg: the command in question is "/usr/lib/xulrunner-1.9.2.8/xulrunner-bin --gre-version"
[19:08] <micahg> lfaraone: what's the parent process?
[19:10] <lfaraone> micahg: it seems to be calling itself?  http://sprunge.us/SaJc
[19:11] <micahg> lfaraone: what's above that
[19:13] <lfaraone> micahg: "/bin/sh /usr/bin/xulrunner-1.9.2 --gre-version"
[19:13] <micahg> lfaraone: hmm
[19:13] <lfaraone> micahg: which is called by "/bin/sh /var/lib/dpkg/info/xulrunner-1.9.2.postinst configure"
[19:14] <micahg> lfaraone: maybe it was a bad install
[19:14] <lfaraone> micahg: bad install? I just did "cowbuilder --login" and installed the packages, it has happened all 3 times I've tried it.
[19:14] <lfaraone> micahg: I can rebuild my cowbuilder chroot if you want.
[19:15] <micahg> lfaraone: oh, we should look into that then...
[19:15] <lfaraone> micahg: I'll file a bug. I'm debootstrapping a new chroot just to verify it's not something specific to cowbuilder.
[19:16] <micahg> lfaraone: like I said, I had no problem in pbuilder
[19:16] <micahg> but I"m also on lucid with a maverick pbuilder
[19:16] <ari-tczew> error: expected ')' before ';' token
[19:16] <ari-tczew> what happens?
[19:16] <lfaraone> ari-tczew: uh, there's a syntax error.
[19:16] <ari-tczew> lfaraone: and how can I fix it?
[19:17] <lfaraone> ari-tczew: by using proper syntax.
[19:17] <lfaraone> ari-tczew: you should probably show us your source if you want us to help you determine the cause of the erorr.
[19:18] <ari-tczew> lfaraone: http://paste.ubuntu.com/482514/
[19:19] <lfaraone> ari-tczew: did it say what line the problem was on?
[19:19] <ari-tczew> lfaraone: ../include/agg_rasterizer_cells_aa.h:342: error: expected ')' before ';' token
[19:20] <ari-tczew> lfaraone: buildlog: http://paste.ubuntu.com/482515/
[19:21] <lfaraone> ari-tczew: no idea, that's odd.
[19:22] <ari-tczew> lfaraone: I'm thinking about includes
[19:25] <lfaraone> micahg: huh... it works in a chroot. Time to recreate my cowbuilder enviorn then :)
[19:25] <micahg> lfaraone: :)
[19:38] <neeraj> lfaraone: hi
[19:51] <ari-tczew> tumbleweed: I need your help :(
[19:55] <tumbleweed> ari-tczew: yes?
[19:56] <ari-tczew> tumbleweed: patching agg in karmic won't work. the possibly way is backport from lucid.
[19:56] <ari-tczew> tumbleweed: but lucid is waiting for sponsor
[19:56] <tumbleweed> one can always just not bother with karmic :)
[19:57] <ari-tczew> tumbleweed: do you mean end work after fix lucid?
[19:58] <tumbleweed> yeah, if it isn't trivially fixable
[20:00] <ari-tczew> tumbleweed: I've spent half day on fixing karmic and no result :(
[20:02] <lfaraone> micahg: it freezes when I use cowbuilder even after rebuilding. It looks like a cowbuilder-specific bug, is it worth reporting? (ie,is it a problem that should be fixed in cowbuilder or in xulrunner?)
[20:04] <ari-tczew> tumbleweed: is this version ok? *ubuntu1~9.10 ?
[20:05] <tumbleweed> ari-tczew: follow the security team's number policy
[20:07] <ari-tczew> okay
[20:08] <ari-tczew> tumbleweed: oh, done! \o/
[20:11] <micahg> lfaraone: idk about cowbuilder
[21:06] <ari-tczew> tumbleweed: do you have permission for reopen bug?
[21:06] <ari-tczew> from Won't fix
[21:08] <tumbleweed> ari-tczew: yes
[21:08] <ari-tczew> tumbleweed: I wrote 21:08 (UTC+2h) that it's done :P
[21:08] <ari-tczew> I'm testing again to be sure
[21:08] <shadeslayer> tumbleweed: which package has grab-udd-merge ?
[21:09] <ari-tczew> shadeslayer: trunk from stefanor bzr?
[21:09] <shadeslayer> does it do syncs as well?
[21:10] <tumbleweed> shadeslayer: not packaged: lp:~stefanor/ubuntu-dev-tools/grab-udd-merge (direct: http://bazaar.launchpad.net/~stefanor/ubuntu-dev-tools/grab-udd-merge/download/stefanor%40ubuntu.com-20100807125513-uo4gyakmpvc5k3r6/grabuddmerge-20100715005242-yrbierkfi6zix8mj-1/grab-udd-merge )
[21:10] <ari-tczew> shadeslayer: merge tool for syncs? :P
[21:10] <tumbleweed> shadeslayer: no, ack-sync
[21:10] <shadeslayer> need a sync from debian experimental without going through madison
[21:10] <shadeslayer> madison -> highly outdated db
[21:10] <ari-tczew> shadeslayer: syncpackage ?
[21:10] <shadeslayer> i dont have upload rights :)
[21:11] <shadeslayer> requestsync goes through madison :P
[21:11] <micahg> ari-tczew: doesn't syncpackage use madison?
[21:11] <tumbleweed> write a manual sync request?
[21:11] <micahg> that's what I did
[21:11] <tumbleweed> shadeslayer: will madison ever be up to date for this package?
[21:12] <shadeslayer> tumbleweed: idk... its in debian experimental
[21:12] <shadeslayer> i think ill have to write a manual sync request
[21:12] <micahg> yes, madison can show experimental
[21:12] <shadeslayer> http://qa.debian.org/madison.php?package=kmymoney <<
[21:12] <shadeslayer> currently out of date for 5 days
[21:13] <micahg> shadeslayer: right, Debian's having some HW issues with their QA boxes
[21:13] <shadeslayer> micahg: any ideas if they will fix soonish ? :)
[21:13] <micahg> shadeslayer: nope, but they are working on it
[21:13] <shadeslayer> might as well write a request manually
[21:13] <tumbleweed> shadeslayer: the udd rmadison endpoint seems to be up to date
[21:14] <tumbleweed> shadeslayer: edit your requestsync :)
[21:14] <micahg> tumbleweed: what do you mean udd rmadison?
[21:14] <shadeslayer> tumbleweed: erm.. dont understand :)
[21:14] <tumbleweed> rmadison -u udd kmymoney
[21:14] <shadeslayer> ah yes
[21:15] <micahg> tumbleweed: I get cannot resolve host
[21:15] <shadeslayer> tumbleweed: what do i edit in /usr/bin/requestsync ?
[21:15] <shadeslayer> or do i edit something else? :P
[21:17] <tumbleweed> shadeslayer: hmm, looking
[21:17] <shadeslayer> there is this one line
[21:17] <shadeslayer>  # try rmadison
[21:22] <tumbleweed> shadeslayer: add RMADISON_URL_MAP_DEBIAN=http://qa.debian.org/cgi-bin/madison.cgi to .devscripts
[21:22] <ajmitch> sometimes it's just as fast to write up manual sync requests
[21:22] <shadeslayer> ajmitch: but this is more fun ;)
[21:23] <shadeslayer> tumbleweed: which file? :P
[21:24] <tumbleweed> shadeslayer: ~/.devscripts
[21:24] <shadeslayer> oic
[21:24] <shadeslayer> \o/
[21:24]  * shadeslayer hugs tumbleweed
[21:24] <tumbleweed> heh
[21:25] <micahg> \o/
[21:26] <micahg> thanks tumbleweed
[21:26]  * ajmitch waits very very patiently for this laptop
[21:43] <ari-tczew> tumbleweed: next changes needs some love (tasks also)
[21:46]  * shadeslayer hops up and down
[21:46] <shadeslayer> look : v
[21:46] <shadeslayer> http://www.jonobacon.org/2010/08/23/11-04-ubuntu-developer-summit-announced/
[22:27] <debuilder> hey guys i want to build a python package
[22:27] <debuilder> but i dunno whether to use distutils or setuptools
[22:27] <debuilder> which one should i use
[22:29] <ebroder> debuilder: If you don't know you need setuptools, probably go with distutils. It's simpler
[22:30] <debuilder> and I just include stuff in the cdbs class?
[22:43] <simar> shadeslayer: heya!! there?
[22:43] <shadeslayer> simar: yes... rolling on a caffeine high
[22:44] <simar> shadeslayer: same here ...
[22:44] <simar> shadeslayer: i was reading you article http://irclogs.ubuntu.com/2010/02/27/%23ubuntu-classroom.html#t17:01
[22:44] <shadeslayer> alrighty
[22:45] <simar> shadeslayer: I got this output while authorizing the ubuntu-dev-tools .. i think it got some errors .. http://paste.ubuntu.com/482614/
[22:46] <simar> shadeslayer: is that ok
[22:46] <shadeslayer> doesnt look so
[22:46] <shadeslayer> simar: happens every time?
[22:46] <shadeslayer> oh
[22:47] <shadeslayer> ubuntu pastebin got a overhaul :P
[22:47] <simar> shadeslayer: kk
[22:47] <shadeslayer> whut?
[22:47] <shadeslayer> can you run it again?
[22:48] <simar> shadeslayer: wait
[22:50] <simar> shadeslayer: http://paste.ubuntu.com/482614/  ....same output
[22:52] <ajmitch> simar: is your system clock correct?
[22:52]  * shadeslayer was about to say that
[22:53] <ajmitch> I've had problems recently where it skewed by more than 15 minutes & caused issues with OAuth
[22:53] <shadeslayer> simar: last line of traceback
[22:53] <shadeslayer> Invalid nonce/timestamp: Timestamp appears to come from bad system clock
[22:53] <simar> ajmitch: In launchpad my time zone is UTC while here I have Indian time ..
[22:54] <ajmitch> that shouldn't be a problem
[22:55] <ajmitch> what does 'date -u' say?
[22:55] <simar> ajmitch: oh my god, I had lived a day back ... ;-))
[22:56] <simar> ajmitch: I hope it will work now.. let me chck
[22:56] <shadeslayer> hehe :P
[22:56] <simar> ajmitch: shadeslayer Mon Aug 23 21:55:13 UTC 2010 is that right ...
[22:56] <ajmitch> yes
[22:56] <ajmitch> or around about there
[22:58] <shadeslayer> Mon Aug 23 21:57:58 UTC 2010
[22:58] <shadeslayer> so yes
[22:59] <simar> Credentials successfully written to /home/simar/.cache/lp_credentials/simar-write_public.txt. yoyo!!!
[22:59] <ajmitch> great
[22:59] <shadeslayer> :)
[23:01] <simar> shadeslayer: ajmitch : guess what has happened, if you dinnt come to my rescue .... this would had been my last day with PPAs .. ;-))
[23:01] <shadeslayer> hehe
[23:02] <simar> continuing ...
[23:06] <shadeslayer> simar: btw id suggest one thing if your reading that log
[23:06] <shadeslayer> have a look at the bottom 2-3 lines
[23:06] <simar> shadeslayer: ya..
[23:06] <shadeslayer> i made a mistake during the session
[23:06] <simar> shadeslayer: oh.
[23:07] <shadeslayer> otherwise its a pretty good session, i made every possible detail available
[23:08] <simar> shadeslayer: Hey, I'm enjoying reading it...but wait!! pkg-kde-tools. I'm using gnome. Does it make a difference
[23:08] <shadeslayer> no it doesnt... thats the beauty of it
[23:09] <shadeslayer> its just a collection of scritps
[23:09] <shadeslayer> *scripts
[23:09] <simar> k
[23:09] <simar> shadeslayer: when do you sleep ..
[23:10] <shadeslayer> probably not tonight
[23:10] <shadeslayer> might do some 8085 programming :P
[23:10] <simar> shadeslayer: oh,, great soul..
[23:10] <simar> shadeslayer: wait,, you work on embedded
[23:11] <shadeslayer> uh no... basically ECE student ;)
[23:11] <simar> shadeslayer: I'm working on atmega8, 16 and motorola mc9s12x256 and 512..
[23:11] <simar> shadeslayer: if you need any help .. i'm here ..
[23:11] <simar> shadeslayer: :))
[23:11] <shadeslayer> your on embedded :P
[23:12] <shadeslayer> hehe
[23:12] <shadeslayer> not really... the mnemonics are quite easy as of now :P
[23:12] <shadeslayer> were just doing the basics... but im yet to grasp the concept of LXI and LDLH properly :P
[23:13] <simar> shadeslayer: my bed at this time is tucked with electronics..
[23:13] <shadeslayer> hehe :)
[23:13] <simar> shadeslayer: LXI and LDLH, I hope these are registers ..
[23:13] <shadeslayer> yeah
[23:13] <shadeslayer> lets not make this OT now :P
[23:13] <simar> shadeslayer: oh, yeah,...
[23:13] <shadeslayer> im off for a while...
[23:14] <simar> shadeslayer: wait by the way i'm making a project for kvpy..
[23:14] <shadeslayer> simar: are you following my session line to line?
[23:14] <shadeslayer> kvpy?
[23:14] <simar> shadeslayer: ya ..
[23:14] <simar> shadeslayer: kvpy search on net .. by the way which yr??
[23:14] <shadeslayer> alright, since the package is choqok, you may go to #kubuntu-devel if you have questions
[23:15] <shadeslayer> simar: 5 th sem ( 3rd year )
[23:15] <simar> shadeslayer: k,, thanks
[23:15] <shadeslayer> + and nobody here answers
[23:15] <simar> shadeslayer: then you need not search..
[23:15] <simar> shadeslayer: its upto 2nd yr
[23:15] <shadeslayer> hehe :P
[23:16] <simar> shadeslayer: excepts you.. you really help to help ... great soul ..
[23:16] <shadeslayer> ^_^
[23:16] <simar> wow now this is last .. i will also try this
[23:16] <shadeslayer> im thinking of applying for kubuntu-dev once i can get project neon up
[23:16] <simar> ^_^
[23:17] <simar> shadeslayer: if i can help(for you app) someway, please tell, i really want to..
[23:18] <shadeslayer> you could comment on it... but idk if they will take that into account or not :P
[23:19] <shadeslayer> havent made a application yet :D
[23:20] <simar> shadeslayer: k, but i will comment ... something is better that nothing (my case))
[23:20] <shadeslayer> :P
[23:20] <shadeslayer> sure
[23:20] <simar> shadeslayer: you were applying for moto .. don't you
[23:21] <shadeslayer> yeah, but i havent contributed to universe enough
[23:21]  * micahg is thinking about applying for MOTU after UDS
[23:21] <simar> shadeslayer: oh, i c..
[23:22] <shadeslayer> otoh... ive contributed alot to main :P
[23:22] <simar> micahg: but i though you are **motu
[23:22] <shadeslayer> mostly kubuntu specific stuff
[23:22] <shadeslayer> simar: https://edge.launchpad.net/~rohangarg/+related-software << my list of uploaded packages
[23:22] <simar> shadeslayer: i'm not very familiar with these terms literarly main, universe .. so much
[23:23] <shadeslayer> micahg: care to explain ^... im off for noq
[23:23] <simar> shadeslayer: i'm seeing that
[23:23] <shadeslayer> *now
[23:23] <simar> shadeslayer: thanks
[23:23] <simar> micahg: you turn now .. if you are free ..
[23:23] <shadeslayer> most significant difference is that, main is supported by canonical, universe is not :P
[23:24] <micahg> simar: well, 1. I'm not MOTU, I have upload rights for the mozilla package set
[23:24] <micahg> simar: main and restricted have security support from canonical for the life of release
[23:24] <simar> micahg: good..
[23:24] <micahg> simar: universe and multiverse are supported by the community
[23:25] <simar> micahg: k
[23:26] <simar> micahg: what are these all ... what i think is that, these are places where packages are stored . ..or these are just virtual terms ??
[23:26] <micahg> simar: they are in essence super package sets
[23:27] <micahg> main and universe are freely redistributable and able to build from source, restricted and multiverse are freely distributable with binary components
[23:28] <simar> micahg: ok, i think i got the relevant part .. how can i contribute to these .. or should i ask it after reading the ppa session from shadeslayer
[23:29] <ari-tczew> micahg: where is UDS?
[23:29] <shadeslayer> ari-tczew: orlando florida
[23:29] <micahg> simar: well, there are sponsors for those that can't upload packages
[23:29] <ari-tczew> arhg, I wanted ask when :P
[23:29] <micahg> Oct 25-29
[23:30] <shadeslayer> hehe :P
[23:30] <simar> micahg: k, and what should i ask these sponsers to upload .. is it bug fixes .. patches
[23:30] <simar> micahg: or something more than that
[23:31] <micahg> simar: https://wiki.ubuntu.com/SponsorshipProcess
[23:31] <ari-tczew> simar: are you interested in security issues?
[23:32] <simar> ari-tczew: ya i want something to work.. but what next ..
[23:32] <ari-tczew> simar: what expierence with packaging have you got?
[23:33] <simar> ari-tczew: ya, i have fixed some ftbfs and made patches ..
[23:33] <simar> ari-tczew: i hope i can learn more .. if i get chance
[23:36] <ari-tczew> simar: hehe, "get chance" ... every motivated person will got chance :)
[23:36] <ajmitch> the opportunities are there
[23:36] <ajmitch> there's more than enough stuff that needs fixing
[23:36] <simar> ari-tczew: i hope so..
[23:37] <simar> ajmitch: i wish if you can be a bit more specific .. actually i'm very familiar with *stuff*
[23:37] <ari-tczew> simar: at start in contributing to security sector, I'd invite you to testing patches :)
[23:37] <simar> ari-tczew: good start :))
[23:37] <ajmitch> simar: it's hard to be more specific in such a broad field :)
[23:38] <ari-tczew> you can review what are looks procedures, then you will could prepare yourself patches
[23:38] <ajmitch> security fixes are a good place to start, certainly
[23:38] <simar> ajmitch: i hope if you can direct me somewhere to a link..
[23:38] <micahg> simar: find packages you care about/use and then check for CVEs
[23:38] <micahg> that's a good place to start
[23:39] <ari-tczew> I offer instruction for fixing security issues, simar
[23:39] <simar> micahg: what is CVEs
[23:39] <ari-tczew> !CVE
[23:40] <simar> ari-tczew: k
[23:40] <simar> !CVE
[23:40] <ajmitch> the bot is being a bit slow today?
[23:40] <micahg> !cve
[23:40] <simar> !cve
[23:40] <ari-tczew> not found :(
[23:40] <micahg> simar: common vulnerabilities and exposure
[23:40] <ari-tczew> simar: http://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures
[23:40] <simar> micahg: k, i got it
[23:41] <ajmitch> argh, nearly 300MB of updates to grab for maverick
[23:41] <ajmitch> this'll take awhile
[23:42] <simar> ari-tczew: i think i know what are taking exactly ... but where should i start looking and how to do security testing .. i mean there are tools, as of i know..
[23:44] <ari-tczew> simar: please read https://wiki.ubuntu.com/SecurityTeam
[23:44] <ari-tczew> simar: tomorrow I'll prepare some patches and we can talk about testing, ok?
[23:44] <ari-tczew> ATM I don't have any patches ready for testing.
[23:46] <simar> ari-tczew: i had a hacking workshop here, there the tutor demonstrated exactly this .. he gained access to windows shell using some tool that displays all vulnerabilities and how to target them .. i had a taste of it ..
[23:49] <ari-tczew> simar: please come on channel #ubuntu-hardened