[11:26] <jdstrand> skaet: fyi, rls-p-tracking-bugs.html seems to not have been updated since monday (see timestamp at bottom)
[11:33] <cjwatson> those pages are so aggravatingly unreliable :-(
[11:39] <slangasek> heh; at least it hasn't deleted all the bugs again
[11:39] <slangasek> :)
[11:45] <cjwatson> it can delete all my bugs any time it likes
[11:55] <jdstrand> slangasek: no kidding :)
[12:02] <skaet> jdstrand, cjwatson - I'll go track bjf down and why the cron isn't working. :P
[12:26] <CareBear\> hi everyone! I guess you are all busy like I am too
[12:27] <CareBear\> I came in here a while ago and mentioned that it would be kinda bad for LTS to ship with the current version of the libusb1 package in debian
[12:27] <CareBear\> it's an rc version, with a change that has been modified for the real release
[12:28] <CareBear\> I am working hard to get all into place and get the real release out, but it will take another couple of days
[12:28] <CareBear\> after those days, it may take another couple of days still before debian has an updated package, depending on how busy the package maintainer there is
[12:29] <CareBear\> I have established contact with him, but only via email, and it took a few days to get a response
[12:29] <CareBear\> I know that yesterday was the last day for automatic updates from the debian repo
[12:30] <CareBear\> help! :)
[12:30] <tumbleweed> we can still do syncs manually, but there's not much we can do until the new release is out (and preferably packaged in debian)
[12:30] <CareBear\> understand!
[12:31] <CareBear\> tumbleweed : all the packaging in debian will work fine also for the release, if you want to use that before debian has a package
[12:32] <CareBear\> thanks!
[12:32] <CareBear\> back to it
[12:32] <tumbleweed> is there any particular problem with the current verison? I don't see many open bugs
[12:41] <cjwatson> CareBear\: if the update is expected on the order of days, then upgrading our package independently isn't worth it; we should just do a manual sync once it's in Debian
[12:41] <cjwatson> CareBear\: and a correction, Monday was the last day
[12:41] <cjwatson> but there's no need to panic; we can do manual syncs for some time yet
[12:45] <CareBear\> right sorry Monday you mentioned that before too!
[12:46] <CareBear\> tumbleweed : yes, the particular problem is that the RC has gotten a small API change
[12:47] <CareBear\> tumbleweed : the RC was created from a testing branch which had not yet been merged into master, and that testing branch got rewritten as per policy. unfortunately the RC got packaged anyway (well after rewrite) because it had desirable bugfixes
[12:48] <tumbleweed> sounds reasonable
[12:49] <CareBear\> as long as we can get the right API out it's fine :)
[13:58] <mdeslaur> skaet: are we having a live meeting today?
[14:00] <Laney> that particular oddity in the release schedule seems to confuse a lot of people
[14:00] <skaet> mdeslaur, yes, but it will start 1/2 hour later to not conflict with Rally wrapup.
[14:00] <Laney> (DIF)
[14:00] <mdeslaur> skaet: ah, cool. do you know what room?
[14:00] <skaet> Laney, yeah working on cleaning up the second entry, but don't have permissions on that item,  should be cleaned up soon.
[14:01] <Laney> skaet: I just mean the fact that it is on Monday but the dates column refers to Thursdays
[14:01] <Laney> it seems to be hard to read
[14:01] <skaet> mdeslaur, Erkel
[14:01] <mdeslaur> skaet: thanks
[14:02] <skaet> Laney,  ah sorry misunderstood.
[14:02] <Laney> maybe if it just had the full dates there
[14:03] <skaet> Laney,  the convention agreed to at UDS was to use 3 letter day in brackets behind when not on Thursday,  lets stick with it that way for now, but revisit for Q-series.
[14:03] <cjwatson> Or we could just have it on Thursday :-)
[14:03] <Laney> there are other items not on Thursdays too
[14:04] <Laney> I don't personally mind, but I've seen several folk misunderstand
[14:05]  * skaet nods
[14:06] <skaet> Laney,  yeah, its not ideal,  and ripe for revisit, but those who have to use it understand,  and I broadcast the actual dates in the Agenda.
[14:07] <Laney> sure
[14:08]  * skaet basically not sure what else to do to make it clearer, but does agree there is room for improvement.
[14:39] <brendand> pitti - hi
[14:40] <pitti> brendand: hey
[14:40] <brendand> pitti - do you have time for a quick question?
[14:41] <pitti> brendand: just ask :) (I keep getting distracted here anyway)
[14:41] <brendand> pitti - on archive.ubuntu.com we have these Packages.gz files: http://archive.ubuntu.com/ubuntu/dists/lucid/main/binary-i386/Packages.gz
[14:42] <brendand> pitti - that one refers to the packages used in lucid back when it was first released in 2010 i believe
[14:42] <cjwatson> Correct
[14:42] <brendand> and this one has the current packages : http://archive.ubuntu.com/ubuntu/dists/lucid-updates/main/binary-i386/Packages.gz
[14:42] <pitti> right
[14:42] <brendand> but what about 10.04.3 - is there a Packages.gz for that?
[14:42] <cjwatson> Only the ones that differ
[14:43] <cjwatson> No
[14:43] <brendand> !!
[14:43] <brendand> ok
[14:43] <pitti> I think we have a snapshot somewhere, but presumably not on archive
[14:43] <cjwatson> Launchpad does not offer us a way to model point releases
[14:43] <brendand> so i have no way of finding out what packages are on the point release
[14:43] <cjwatson> We do, as pitti says, have it stored privately in case it ever does
[14:43] <brendand> ok
[14:43]  * brendand weeps a little
[14:43] <cjwatson> https://bugs.launchpad.net/launchpad/+bug/701595
[14:43] <ubot4> Launchpad bug 701595 in launchpad "representation of Ubuntu point releases (affects: 1)" [Low,Triaged]
[14:43] <roadmr> thanks for the answer! it's at least good to know for sure
[14:44] <cjwatson> Happy to answer specific questions about packages
[14:44] <cjwatson> We probably ought to put the dists/ bit somewhere a bit more public, too
[14:44] <brendand> cjwatson, pitti - thanks! not the answer we hoped for, but as roadmr says, good to know for sure so we're not wondering
[14:44] <ogra_> also if there are isos for a point release you have the manifest files next to them on the download page
[14:44] <roadmr> cjwatson: btw thanks so much on the germinate slowness fix and workaround suggestion!
[14:44] <cjwatson> Apparently nobody kept a snapshot of 10.04.2, mind you :-(
[14:44] <cjwatson> ogra_: Which covers things on the images, but nothing else
[14:44] <cjwatson> roadmr: no problem, thanks for pointing it out
[14:45] <ogra_> indeed
[14:45] <cjwatson> We have private snapshots of 6.06.[12], 8.04.[1234], and 10.04.[13]
[14:47] <cjwatson> roadmr: BTW is there a particular reason you're using a bzr checkout of germinate rather than the packaged version?
[14:47] <roadmr> cjwatson: I'd have to ask cr3, maybe there was no package when we started doing this (~august 2011)?
[14:48] <cjwatson> It's been packaged since April 2005
[14:48] <roadmr> heh so it's not that then :)
[14:52] <roadmr> cjwatson: it looks like there were problems using the package to germinate a newer release (i.e. using the lucid package to germinate oneiric) - that's why we use the bzr trunk instead
[14:53] <cjwatson> Surprising but possibe
[14:53] <cjwatson> *possible