[07:04] <dholbach> good morning
[07:14] <pmjdebruijn> mornin
[08:05] <bullgard4> Rhonda: I have detected a bug in packages.ubuntu.com. How to deal with it?
[08:12] <Rhonda> No clue because you didn't tell me what the bug is. :)
[08:12] <Rhonda> First thing would be to really find out whether it's a bug in packages.u.c or one in changelogs.ubuntu.com
[08:30] <bullgard4> Rhonda: If I am looking up a certain package in packages.ubuntu.com for Ubuntu 10.04, 10.10, 11.04, I can find the description of this package. But packages.ubuntu.com does not show the description of a package for Ubuntu 11.10.
[08:32] <Rhonda> As you haven't given the name of the "certain package" I still have no clue. :)
[08:32] <Rhonda> You see, it's hard to help you if you don't give me the information which are crucial to reproduce the issue on my side and check from there on.
[08:33] <geser> Rhonda: could it be because the long descriptions moved from the Packages file to Translations?
[08:34] <geser> Rhonda: compare http://packages.ubuntu.com/natty/ubuntu-dev-tools with http://packages.ubuntu.com/oneiric/ubuntu-dev-tools (no long description)
[08:35] <Rhonda> thanks, that's something with a substance
[08:36] <Rhonda> So information was removed from the Packages files in Ubuntu specificly which is there in Debian still?
[08:36] <bullgard4> Rhonda: http://packages.ubuntu.com/oneiric/gnome-commander does not contain the desscription of the gnome-commnder package.
[08:36] <Rhonda> So it's not even a "certain package" but instead, *every* package?
[08:37] <geser> yes
[08:37] <bullgard4> Rhonda: I have tried 3 examples. All three showed this effect.
[08:38] <Rhonda> bullgard4: Then please don't speak about a certain package, that is misleading and confusing on my end.
[08:38] <bullgard4> Right. Please excuse me.
[08:38] <Rhonda> Because that rather sounds you have found it in one package but seen other package that do *not* show that behavior.
[08:39] <Rhonda> And don't get me wrong or grumpy, it's not meant that way. But your description was a bit flakey :)
[08:39] <geser> "something isn't working, plz fix!" :)
[08:40] <Rhonda> geser: if it's just something, then I'm happy with that the rest is still working!  \o/
[08:41] <Rhonda> Hmm, but that sounds like a tricky issue.  Was there some announce about the removal of the package description, and where those can be found now?  How do other package frontends cope with it?
[08:43] <geser> they are now in e.g. http://archive.ubuntu.com/ubuntu/dists/oneiric/universe/i18n/Translation-en
[08:46] <geser> apt downloads them together with the Packages files. apt-cache, synaptic and software-center (didn't check other tools) can display them
[08:47] <Rhonda> hmm
[08:47] <Rhonda> I am uncertain, haven't checked the code, but if what I did just now works then I'm pleased.
[08:48] <micahg> Rhonda: was part of enabling multiarch to make the download size more tolerable
[08:48] <Rhonda> We'll know in 2 hours I guess.
[08:51] <Rhonda> I fear though it might not be that easy and "en" is special-cased …
[10:25] <cjwatson> Rhonda: "en" is kind of special-cased, yes
[10:26] <cjwatson> I can't remember if I announced that change
[10:26] <cjwatson> it hadn't occurred to me that things other than apt were going to care, I suspect
[10:27] <cjwatson> yeah, I can't see an announcement, sosrry
[10:27] <cjwatson> *sorry
[10:35] <Rhonda> I mean "en" special-cased inside the packages code. :)
[12:00] <geser> Rhonda: should your fix be visible by now?
[12:03] <Rhonda> potentially yes, the last run was an hour ago
[12:03] <Rhonda> hmmmm
[12:03] <Rhonda> 09:26:50 URL:http://archive.ubuntu.com/ubuntu/dists/oneiric/main/i18n/Translation-en.bz2 [701370/701370] -> "Translation-en.bz2" [1]
[12:03] <Rhonda> It at least fetched the file
[12:04] <Rhonda> wtf
[12:04] <Rhonda> Reading Translations for en (en)...bzcat: Can't open input file /srv/packages.ubuntu.com/archive/*/sid/*/i18n/Translation-en.bz2: No such file or directory.
[12:05] <Rhonda> sid?!
[12:05] <Rhonda> … and wheezy and squeeze and lenny
[14:25] <cdunlap> Quick question
[14:26] <cdunlap> So where do you put the dep3 information when you fix a bug?  I found docs to tell me what to include for dep3 but  I am a bit unclear on where to actually put the information.
[14:26] <tumbleweed> cdunlap: at the top of the patch. patch ignores junk data at the beginning of patches
[14:27] <tumbleweed> or just run "quilt header -e"
[14:28] <cdunlap> Thank You tumbleweed.  I really appreciate it.
[17:58]  * tumbleweed wonders if upgrading pre-LTS is a good idea
[17:59] <ajmitch> tumbleweed: what could possibly go wrong?
[17:59] <tumbleweed> err, pre UDS
[18:00] <tumbleweed> ajmitch: 18 hours of flight with a broken laptop? Mind you I can probably only squeze 4 hours out of my pair of batteries...
[18:00] <ajmitch> the fun breakage tends to happen after UDS, when people have time to hack on new stuff
[18:00] <tumbleweed> that's true
[18:01] <nigelb> ajmitch: Going to UDS?
[18:01] <ajmitch> nigelb: heh, no
[18:01] <nigelb> company \o/
[18:04] <Rhonda> <nelson point="ajmitch">HA HA!</nelson>
[18:04] <ajmitch> :(
[18:04] <Rhonda> because of your nice quote. :)
[18:05] <ajmitch> quote?
[18:05] <Rhonda> "what could possibly go wrong"
[18:06] <Rhonda> tumbleweed: but history tells to not do upgrades close to specific dates, and those include giving talks (have been hit by b0rked presentation tools myself) and wordprocessing (like, you have to deliver your work and libreoffice likes to lock you out or eat your documents)
[18:07] <Rhonda> And it happenend to others before too. But .. 18 hours of flight, your battery won't last that long, take a book with you if that's your only worry. :)
[18:08] <tumbleweed> indeed, travelling is my most productive reading time
[18:08] <tumbleweed> but long flights are also great for writing that large chunk of code you never get around to when you have internet access
[18:09] <ajmitch> tumbleweed: 18 hour flight? almost like you live in NZ :)
[18:09] <tumbleweed> 13 hours to US, and little flights on either side
[18:11] <nigelb> ajmitch: if he was in NZ, that would be 28 :P
[18:11] <ajmitch> nigelb: nah, it's ~12 hours to LAX or SFO
[18:12] <nigelb> Not to Orlando :P
[18:12] <ajmitch> no, but it wouldn't be another 16 hours to fly across the US
[18:13] <nigelb> heh
[18:24] <jtaylor> someone fancy uploading a no change rebuild sru?
[18:24] <jtaylor> bug 883204
[18:25] <jtaylor> target oneiric, maybe also maverick
[18:29] <jtaylor> I wonder why it needs rebuilding for minor releases ...
[18:29] <tumbleweed> jtaylor: sure, I'll look at it
[18:29]  * tumbleweed reminds jtaylor to get some upload rights, already
[18:29] <jtaylor> hm  guess I should finish my application this weekend
[18:30] <tumbleweed> heh, ^5
[18:38] <geser> tumbleweed: finally found time to merge your lp-ftbfs-report MP. Thanks for it.
[18:39] <tumbleweed> geser: thanks
[18:39] <tumbleweed> it's probably possible to share some caching between the sqlite database and json file that the other bits produce, I haven't looked at that
[18:46] <tumbleweed> wgrant: ^ when you deploy that, you can grab the history for precise from ~stefanor/public_html/lp-ftbfs-report/historical/source/primary-precise.db
[18:58] <tumbleweed> jtaylor: uploaded
[18:58] <jtaylor> thx, maverick too?
[18:58] <jtaylor> my chroot is still setting up
[18:58] <jtaylor> it also fails but did not test if rebuild helps
[18:58] <tumbleweed> err, no
[18:58]  * tumbleweed didn't look at maverick
[18:59]  * jtaylor building
[18:59] <jtaylor> yup also fixed by rebuild
[19:01] <tumbleweed> have you filed a bug in debian about adding a Breaks / Depends on r-base-core << foo + 1 ?
[19:01] <jtaylor> no but I will
[19:01] <tumbleweed> thanks
[19:02]  * tumbleweed merges the ubuntu bugs, and adds a maverick task
[19:16] <jtaylor> debian bug filed
[20:28] <Laney> packing, i hate you so
[20:30] <tumbleweed> hrm, should do something about that...
[20:30] <Laney> travelling tomorrow?
[20:30] <tumbleweed> yeah
[20:32] <broder> i still need to figure out what computer i'm bringing
[20:36] <Laney> the luxury of choice
[20:40] <tumbleweed> heh, yeah, also only 1 suitable for travel here (and it's well due for replacement)