[01:18] <Kmos> http://revu.tauware.de/details.py?upid=377
[01:18] <Kmos> can someone nuke this one?
[01:53] <bddebian> Heya gang
[01:55] <minghua> Hi there bddebian.
[01:55] <bddebian> Hi minghua
[01:55] <minghua> The mail from GetDeb.net admin looks interesting.
[01:56] <minghua> Hmm, so we are 5 minutes from archive freeze...
[01:58] <bddebian> eeks :-)
[01:58] <ajmitch> nice, positive email on -sounder
[01:59] <bddebian> So how long before the first getdeb bugs start getting filed on LP? :-)
[01:59] <ajmitch> what makes you think that they haven't already been there?
[02:01] <ajmitch> eg https://bugs.edge.launchpad.net/ubuntu/+source/pidgin/+bug/134707
[02:01] <ubotu> Launchpad bug 134707 in pidgin "Group with broken characters keeps coming back with ICQ/AIM buddies" [Undecided,New] 
[02:02] <bddebian> Of course...
[02:03] <minghua> That pidgin is not quite bad, actually...
[02:16] <bddebian> Heya persia
[02:16] <persia> hey bddebian
[02:19] <persia> So, it's Monday UTC now.  Does motu-uvf need to ACK all the pending sync requests?
[02:26] <RAOF> Wow, eclipse is *still* building.  ScottK - you wanted the eclipse build, right?
[02:27] <persia> RAOF: Still?  That seemed like a sensible patch, but that's a long time for he buildds to be busy.
[02:28] <RAOF> persia: It'll probably be faster when it doesn't have to thrash swap to build :/
[02:28] <persia> heh
[02:28] <RAOF> How much ram in the buildds, again?
[02:28] <RAOF> :)
[02:32] <minghua> Alas.  Have tracker enabled and not exclude ~/Temp from its tracking, meanwhile use ~/Temp as a place to extract big HTML documents to read is probably not a good idea...
[02:39] <RAOF> Build needed 19:02:38, 1654800k disk space
[02:39] <persia> It's done!  Hurrah.  Does it work?
[02:39] <RAOF> Build killed with signal TERM after 151 minutes of inactivity!
[02:39] <RAOF> Gah!  It had built, damnit!
[02:39] <persia> Umm....
[02:40] <RAOF> It was assembling the debs, and something killed it!
[02:40] <persia> Usually 151 minutes of inactivity indicates it couldn't get something done.  Doesn't usually bode well for later buildd building...
[02:41] <RAOF> persia: Want a pastebin of the last builder output?
[02:42] <persia> RAOF: Sure.  No guarantees I can explain it, but it might help (and someone else might look as well)
[02:43] <RAOF> I'd mail you the build log, but apparently postfix doesn't like sending messages that large(!)
[02:43] <persia> Err.  That's huge!   Does pastebin accept it?
[02:44] <RAOF> I don't have all the buildlog in backscroll, I haven't set screen's buffer to 64MB yet
[02:45] <RAOF> Pastebin will accept what I have :)
[02:48] <RAOF> Ah, what I meant was: I don't *have* a full build log, because I rely on sbuild to mail me one.  And postfix won't :)
[02:48] <persia> RAOF: Look in ~/logs/
[02:48] <TheMuso> RAOF: heh
[02:49] <RAOF> persia: Nope, empty.
[02:49] <persia> RAOF: Ah.  My sbuild is configured to store the logs there (and I don't remember fiddling with it).
[02:49] <RAOF> Anyway, here's the end of the log: http://paste.ubuntu-nl.org/40667/
[02:49] <RAOF> Maybe I should look into that :)
[02:50] <ajmitch> that's a seriously broken package
[02:50] <RAOF> Oh, whoops.  ~/Ubuntu/logs ;)
[02:50] <TheMuso> heh] 
[02:50] <TheMuso> again
[02:50] <TheMuso> The bigger the project...
[02:51] <RAOF> Ah, there it is.  Surprisingly enough, postfix doesn't like sending a 26Mb build log.
[02:52] <RAOF> Anyone who wants to run a post mortem on that can grab all glorious 26Mb of that log from http://cooperteam.net/eclipse_3.2.2-3ubuntu4_20071014-1525
[02:55] <RAOF> They perhaps could generate fewer than 6000 warnings/code file, yes.
[03:04] <persia> RAOF: Why does it have "L Launchpad-Bugs-Fixed" everywhere?  Isn't that usually just "Launchpad-Bugs-Fixed"?
[03:05] <RAOF> Uuum, let me grep some other build logs...
[03:06] <RAOF> Nope, all my builds have "L Launchpad-Bugs-Fixed".  I don't know why.
[03:06] <persia> RAOF: Also, did it produce any binaries?
[03:06] <RAOF> No.
[03:07] <persia> Interesting.  I wonder if that is because all those dpkg-deb lines failed, or because sbuild removed them after the final failure notice.
[03:08] <persia> RAOF: Is your sbuild purge-mode "successful"  or "never" by any chance?
[03:08] <RAOF> persia: Let me check
[03:08] <pwnguin> grr. it should be a crime to use flash video playback when i have plugins that run flv perfectly fine
[03:10] <pwnguin> im tired of 100 percent cpu playback for crappy youtube / google video
[03:10] <pwnguin> when totem et all handle it flawlessly
[03:10] <RAOF> persia: It's default, which seems to be "successful"
[03:10] <persia> RAOF: Does the build-tree have any useful clues?
[03:12] <RAOF> No, it's gone, apparently.  The snapshot is no more. (Maybe the default *is* always)
[03:13] <persia> RAOF: I like to use "successful" just for this type of eventuality.
[03:14] <RAOF> Not very useful for now, of course.
[03:14] <persia> Next time :)
[03:14] <RAOF> I think, however, that this may be an artifact of how long it takes to build, although it's stupid that it'd be triggered at the end.
[03:15] <RAOF> Some of the build commands would've taken > 150 minutes without any output, and I think sbuild tries to kill such builds.
[03:15] <persia> RAOF: I'm inclined to agree, although the number of warnings is larger than I'm willing to look at individually.  Unfortunately, it may be difficult to get enough build time to try again for gutsy.
[03:17] <RAOF> Yeah.  I could turn off the timeout & try again, but that will *still* mean that the package finishes building *tomorrow*.
[03:18] <RAOF> Yeah, probably.
[03:19] <TheMuso> RAOF, persia, what option is that?
[03:19] <TheMuso> c
[03:19] <TheMuso> ugh
[03:20] <persia> TheMuso: "purge-mode".  If set to "successful", it doesn't delete the build-tree when the build is complete if there is an error.  ("never" always leaves the build-tree, and "always" always deletes it (the default))
[03:21] <RAOF> persia: And that's going to work with lvm snapshots, too?
[03:22] <ScottK> RAOF: At this point I'd say it's not worth uploading Eclipse.  I don't know that the buildd's are going to finish with what they already have.
[03:22] <persia> RAOF: I've not looked at it in a bit, and my sbuild / schroot configuration is broken in a couple ways that I've manually worked around, but my memory is that it skips the "delete the build directory" step, but still clears the chroot (leaving the build directory in .)
[03:23] <RAOF> ScottK: In that case an extra ~90min worth of build time is not going to go down well :)
[03:23] <TheMuso> persia: I'm guessing thats a .sbuildrc option?
[03:23] <persia> ScottK: You'll have an opinion: Do the sync requests filed yesterday need motu-uvf ACK if the syncs haven't been completed?
[03:23] <ScottK> RAOF: Right.
[03:23] <persia> TheMuso: I believe so.  man sbuild
[03:23] <ScottK> persia: I'd say not, but I'm easy.
[03:23] <ScottK> persia: Did you see you got a 2nd ack for polyxmass-doc
[03:24] <persia> ScottK: Yep.  It's now amoung the 8 syncs I'd like to see get in :)
[03:24] <lamont> $purge_build_directory="successful";
[03:24] <lamont> $purge_build_directory="never";
[03:24] <lamont> persia: one of those...
[03:24] <lamont> or "always"
[03:25] <ScottK> persia: I'd say it's time to push the process along.
[03:26] <theneb> Hi all, common question I'm sure but how do I get our project (maintained in svn and on the debian repos) onto Ubunut?
[03:26] <theneb> *Ubuntu
[03:27] <persia> ScottK: I'm agreed to that, I just wanted to verify that I didn't need to get motu-uvf ack for all of them before making noise.
[03:27] <RAOF> theneb: If it's in Debian, it should get sync'd into Ubuntu at the start of each dev cycle.
[03:28] <RAOF> theneb: Or is that an answer to a different question to the one you asked? :)
[03:28] <persia> theneb: The software will need to be packaged.  The first step is to file a bug in Launchpad, asking that the package be included.  The next step is preparing a candidate package for review.  After that, it's just shared feedback, and once two developers have approved, it will be uploads.
[03:28] <theneb> We started being in aptitude on the 27th of April
[03:29] <RAOF> theneb: What package is this?
[03:30] <theneb> liquidsoap
[03:30] <theneb> http://savonet.sourceforge.net
[03:30] <persia> ScottK: I also haven't seen the snort-common-libraries package hit NEW yet.  Have you been chasing that?
[03:31] <RAOF> theneb: So, if it's packaged in Debian, it'll automatically get synced over into Hardy when the archives open (in a couple of weeks, I think).
[03:31] <imbrandon> moins all
[03:32] <theneb> RAOF: thanks for your help so far, I've just noticed it's not in stable Debian, do I need to get a release in stable before it'll be included?
[03:33] <ajmitch> liquidsoap |    0.3.2-4 | http://nz2.archive.ubuntu.com gutsy/universe Sources
[03:33] <bddebian> Heya imbrandon
[03:34] <RAOF> Ah, ubotu was only looking at binary packages :)
[03:34] <ajmitch> which means that it probably never built
[03:34] <RAOF> And no-one noticed :)
[03:35] <ajmitch> right, build error with the docs
[03:35] <ajmitch> maybe you'll get lucky & it'll be fixable with a stable release update
[03:35] <theneb> I know they were broken at some point, though I'll do a compile and check on it
[03:36] <TheMuso> I wonder whether we should see about getting general FTBFS notices for autosyncs for universe sent somewhere.
[03:36] <TheMuso> So we can pick up no them and get them fixed.
[03:36] <TheMuso> s/no/on/
[03:37] <bddebian> I thought we had a list of all source packages with no binaries somewhere?
[03:38] <ajmitch> or even a list of packages where source version != binary version
[03:38] <bddebian> Aye
[03:38] <TheMuso> ajmitch: IMO the FTBFS notice approach would cover all architectures better, unless we could run version checks on several arches in the DC somehow.
[03:39] <theneb> Oh and one little thing, stop making Ubuntu awesome, My gentoo desktop now fails in comparision
[03:39] <theneb> :D
[03:39] <ajmitch> TheMuso: you mean by grabbing the Packages.bz2 files? :)
[03:39] <bddebian> lucas had an FTBFS list of the whole archive
[03:39] <persia> TheMuso: You don't need to be in the DC to get that.
[03:39] <TheMuso> ajmitch: ...or that.
[03:40] <persia> Also, more generally, I've found a lot of FTBFS issues from bitrot, which a package version comparison won't help with.  Maybe we could schedule an archive-autobuild starting with UVF (or autosync-off), and track those?
[03:40] <ajmitch> persia: one was meant to be scheduled
[03:41] <ajmitch> you just have to poke people harder, I suspect
[03:41] <persia> ajmitch: What happened?
[03:41] <ajmitch> as with everything, nobody found the time to do it
[03:43] <persia> ajmitch: Could you wait until the per-bug commenting system is available?  A fair number of those will be relevant during the hardy cycle, and active tracking of RCs isn't usually agreesively relevant until autosync freeze
[03:43] <persia> s/ees/sse/
[03:43] <persia> um.
[03:44] <ScottK> persia: snort hasn't built yet.  It was accepted, but the line is long at the buildd's.
[03:45] <persia> ScottK: It's built on a few architectures.  Are all the binaries bundled, and presented in NEW together?
[03:45] <ScottK> persia: Dunno.  I'll have a look.
[03:45] <StevenK> If they're waiting in NEW, it usually won't be accepted until it has built everywhere
[03:45] <persia> StevenK: That makes sense.
[03:47] <ajmitch> persia: the whole point of removing per-package comments is because they couldn't simply be copied to per-bug
[03:47] <persia> ajmitch: I completely agree.  I just don't know your release schedule.  If you're releasing, by all means wipe it.
[03:48] <ajmitch> 'release schedule' is when I have the urge to work on it
[03:48] <ajmitch> though I've been doing some hacking in that area today with django, but on another app
[04:02] <tonyyarusso> RAOF: Did you get a chance to test that amd64 kompozer crash?
[04:04] <RAOF> tonyyarusso: Ah, no sorry.
[04:04] <tonyyarusso> k
[04:04] <RAOF> I actually forgot about it! :(
[04:08] <minghua> Does anybody else's nautilus in browser mode need double-click in the sidepane to switch directories (gutsy)?
[04:34] <bigon> may I upload a fix for the liquidsoap FTBFS?
[04:34] <persia> bigon: I'd recommend opening a bug with the debdiff to make it easy for motu-uvf to approve.
[04:37] <persia> bigon: Also, if you want to chase FTBFS issues, there's still heaps of FTBFS bugs listed on http://django.ajmitch.net.nz/rcbugs/ (all of which are guaranteed to have a solution)
[04:38] <bigon> thx
[04:39] <persia> bigon: Only thing to remember is that hard freeze is in seven hours, and you'll want to have had anything already accepted and built by then (and neither the accept nor build queues are empty)
[04:40] <jdong> is bryce's xserver-xorg-video-intel fix going to make it?
[04:41] <bigon> and it's nearly 5 am here :o
[04:42] <bigon> https://launchpad.net/bugs/152821
[04:42] <ubotu> Launchpad bug 152821 in liquidsoap "Fix FTBFS" [Undecided,New] 
[04:43] <bigon> good night
[04:52] <ScottK> Since it looks like bigon went to bed, anyone want to upload his fix in 152821 ^^^.  Feel free to go for it.
[04:52] <TheMuso> I'll look into it.
[04:52] <TheMuso> bug 153821
[04:53] <TheMuso> ugh
[04:53] <TheMuso> bug 152821
[04:53] <ubotu> Launchpad bug 152821 in liquidsoap "Fix FTBFS" [Undecided,New]  https://launchpad.net/bugs/152821
[04:53] <ScottK> TheMuso: Thanks.
[05:06] <TheMuso> Ugh. Didn't put the bug number in the aptch. I'll do it for the sake of expediency.
[05:07] <TheMuso> s/aptch/patch/
[05:08] <TheMuso> I thought Laurent was a MOTU. Obviously not activated yet...
[05:09] <ScottK> persia: His is, but we are in the mother-may-I motu-uvf stage of the process.
[05:09] <ScottK> His/He
[05:09] <ScottK> I guess he gave up getting an answer.
[05:09] <persia> TheMuso: ScottK is really speaking to you :)
[05:09] <ScottK> persia: Sorry.
[05:09] <ScottK> Right.
[05:09] <TheMuso> heh
[05:10] <persia> ScottK: Not so much gave up, as was advised he needed motu-uvf-may-I just when he finally finished and was going to sleed (5am local time)
[05:10] <TheMuso> ScottK: Yeah I know, and the fact he has gone to bed.
[05:10] <persia> s/sleed/sleep/
[05:11] <StevenK> TheMuso: And this is why having a local mirror is *wonderful*
[05:11] <TheMuso> StevenK: When my server is built, I'll likely have such a local mirror.
[05:12] <TheMuso> Till then, it gives my CPU enough time to finish another build session I have running.
[05:15] <StevenK> TheMuso: Yeah, but then you get to deal with the joys of syncing a mirror. And how completly brain-dead debmirror really is.
[05:16] <ajmitch> at least it's better than apt-proxy
[05:17] <StevenK> Sometimes I question that. :-)
[05:17] <ajmitch> apt-proxy is a nice idea
[05:18] <StevenK> Yeah, it just completly and utterly blows. :-)
[05:20] <TheMuso> StevenK: Well I'll worry about it when I get roudn to having to set it up.
[07:55] <dholbach> good morning
[07:55] <Fujitsu> Hi dholbach.
[07:55] <dholbach> hey Fujitsu
[07:58] <ajmitch> hello
[07:59] <dholbach> hey ajmitch
[07:59] <TheMuso> Hey dholbach.
[07:59] <dholbach> hiya TheMuso
[07:59] <dholbach> how are you guys doing?
[07:59] <TheMuso> Couldn't be better atm!
[07:59] <ajmitch> ok
[07:59] <dholbach> hehe, cool :-)
[08:01] <TheMuso> Looks like a fair few MOTUs will be in Boston.
[08:02] <ajmitch> that's a good change
[08:03] <TheMuso> ajmitch: I thought a lot of MOTUs were in attendance for all of the UDSs.
[08:04] <ajmitch> often there's not many
[08:04] <TheMuso> Right.
[08:04] <dholbach> we always had a few MOTUs there, no?
[08:05] <TheMuso> dholbach: Yeah, I'm just not sure how many, and looking at the boston attendees on LP, I see a few MOTUs, and theres likely to be more.
[08:05] <ajmitch> a few but not a lot
[08:05] <TheMuso> superm1: Sweet, so will I.
[08:06] <superm1> TheMuso, cool :)
[08:06] <superm1> TheMuso, all week?
[08:06] <dholbach> :-)
[08:08] <luk_> hi dholbach
[08:09] <luk_> a pitty I have to go now, will contact you later today...
[08:09] <dholbach> hey luk_ - yeah, feel free to send me a mail or ping me on IRC
[08:27] <white> there is not by any chance a nice conference in the US in middle of june, which would sponsor DDs to come there and stuff?
[08:31] <white> ScottK: 0.9.8.5-1 will probably do
[08:32] <white> ScottK: the maintainer is also upstream and the new version was uploaded straight after my NMU
[08:33] <white> knowledgeroot
[08:34] <persia> 0.9.8.5-1 is just finishing building now :)
[08:35] <white> well it is time to go for a run now :)
[08:54] <persia> I just noticed bug #87844.  Is anyone planning on fixing that in the next three hours?  Should it perhaps not be milestoned?  If nothing else, I'm tempted to unassign "MOTU".
[08:54] <ubotu> Launchpad bug 87844 in spe "[apport]  spe crashed with AttributeError in skip()" [Medium,Confirmed]  https://launchpad.net/bugs/87844
[09:03] <TheMuso> persia: What needs doing to it to get it fixed? Is there a patch attached?
[09:03] <persia> TheMuso: There's a patch, but the comments indicate it doesn't work.  Last comment is pkern suggesting an SVN pull (as far as I understand the buglog)
[09:04] <TheMuso> persia: Ok, I'll have a look in a bit.
[09:07] <persia> TheMuso: Thanks.  If a solution doesn't occur to you, would you mind getting it unmilestoned?  I'm not sure it's really as release-critical as some of the other outstanding bugs.
[09:10] <TheMuso> persia: I'm going to see bout pulling it from svn if I can.
[09:11] <ajmitch> how old is the bug?
[09:11] <TheMuso> from February.
[09:12] <ajmitch> so hardly a regression if it's released as-is
[09:12] <persia> The only confusing bit is that the bug was milestoned, and assigned to MOTU.
[09:13] <ajmitch> that sort of thing happens
[09:13] <Fujitsu> Assigning to MOTU is fairly normal.
[09:13] <ajmitch> dholbach assigned it to motu back in march, so it's been there for awhile
[09:13] <ajmitch> the activity log doesn't track nominations though
[09:14] <Fujitsu> You'd have to check bugmail
[09:16] <Fujitsu> Patrice Vetsel milestoned it to beta more than a month ago, so it has been a while...
[09:28] <TheMuso> Meh. Can't find its svn repo.
[09:28] <TheMuso> I must say I haven't looked very hard for it either.
[09:28] <TheMuso> Considering the discussion thats been had about the bug.
[09:29] <persia> TheMuso: No rush.  There's more than 100 outstanding of each FTBFS and unmetdeps bugs, either of which is probably more interesting.
[09:31] <StevenK> If they both start with virtualbox, they're mine.
[09:31] <TheMuso> ajmitch: I'm kinda in agreement. We've done all we can, anything important to be fixed can wait for SRUs.
[09:34] <Fujitsu> TheMuso: Why are they unripped?
[09:35] <persia> StevenK: No.  There are four now: liquidsoap, sqlfairy, virtualbox-ose-modules, and virtualbox-ose
[09:35] <TheMuso> Fujitsu: The HD I had them on several months ago crashed, and I haven't been bothered till now to re-rip them, and it gives me a chance to re-organise them, and change the way I'm storing them.
[09:35] <Fujitsu> Ah.
[09:36] <jml> RAOF: hi
[09:37] <ajmitch> ah, jml is back
[09:38] <jml> yes, I'm back and I've discovered the xrandr command line tool
[09:38] <ajmitch> heh
[09:39] <ajmitch> good evening Hobbsee
[09:39] <RAOF> jml: Ho!
[09:40] <RAOF> Afternoon Hobbsee, ajmitch.
[09:40] <ajmitch> hi RAOF, how's it going?
[09:40] <RAOF> ajmitch: It's hot, and I've got a friend from Hobart staying with me.
[09:40] <RAOF> This is in order of obviousness.
[09:41] <Hobbsee> heya ajmitch, RAOF!
[09:41] <jml> RAOF: you had, but for some reason when I upgraded to gutsy, I tried the GUI tool instead
[09:41] <TheMuso> Good $Time_Of_Day newcomers.
[09:42] <jml> RAOF: anyway, it looks like I can get 1680x1050 on my new monitor from my laptop (although not while displaying stuff on the laptop screen)
[09:42] <RAOF> jml: Yay!  Kinda.
[09:44] <persia> StevenK: Does virtualbox not work with -rt?
[09:44] <StevenK> persia: I've not tried.
[09:44] <StevenK> And to be honest, I didn't think of trying to build against -rt
[09:44] <TheMuso> Does virtualbox need a CPU with virtualization support?
[09:45] <StevenK> TheMuso: Not that I've seen.
[09:45] <persia> Also, doesn't i386 provide a special -i686 kernel which isn't -generic?  Anyway, I'll stop whining :)
[09:45] <StevenK> persia: -386. And, hmph.
[09:46] <Hobbsee> how's the sponsorship queue?
[09:46] <Hobbsee> we have 9 hours, iirc
[09:47] <Fujitsu> Hobbsee: Isn't it a bit over 2 hours?
[09:47] <persia> Hobbsee: I think we only have 2 hours, and sponsorship queue looked triaged about 8 hours ago (although I haven't looked since)
[09:47] <Hobbsee> Fujitsu: oh, so i cant do maths? great.
[09:47] <Hobbsee> oh, i see, by 10 UTC
[09:47] <Fujitsu> Yeah, 20071014 1000 UTC
[09:47] <Hobbsee> fuzzy deadline
[09:48] <Fujitsu> Erm, the date in the mail looks wrong. I presume it means the 15th, not the 14th?
[09:48] <Fujitsu> That would be a while ago.
[09:48] <Fujitsu> And not a Monday.
[09:48] <Hobbsee> yeah
[09:55] <persia> The buildds are hungry...
[09:55] <Hobbsee> yeah, i know.  i've poked.
[09:56] <Hobbsee> but...i'm dependant on them doing the work
[09:56] <persia> Hobbsee: I completely understand.  Thanks for poking :)
[09:57] <TheMuso> What needed poking?
[09:58] <Hobbsee> TheMuso: the archive admins who are permitted to accept packages from unapproved
[09:58] <TheMuso> ah
[09:58] <persia> TheMuso: Someone could accept some sources before the next publication so the buildds have something to do.
[09:59] <persia> (well, non-hppa buildds)
[09:59] <TheMuso> yep
[09:59] <TheMuso> I'm aware of that, but wasn't aware the builds had nothing to do.
[10:00] <persia> TheMuso: As far as I can tell, the last 4 compiles are now underway, and there's one source expected in the next publish.
[10:00] <TheMuso> right
[10:01] <Hobbsee> oh, there's not even that much there
[10:01] <persia> For universe, we've only 3: liquidsoap + virtualbox (x2)
[10:01] <Fujitsu> I'm still wondering how they managed to have +queue using such different code that it doesn't announce.
[10:02] <persia> Fujitsu: Doesn't announce?
[10:02] <Fujitsu> persia: Yeah, Hobbsee has permissions to accept things through the web UI, but the code there doesn't announce to <release>-changes, so is dangerous.
[10:02] <TheMuso> persia: Web UI for accepting packages not announcing to changes.
[10:02] <persia> Fujitsu: Ah.  Right.
[10:04] <Hobbsee> persia: goodness only knows.  but i havent found any launcphad-types yet.
[10:04] <persia> Am I correct that the next publish run is the last allowed?
[10:05] <Fujitsu> persia: The 0903Z run?
[10:05] <StevenK> The publisher probably started about a minute ago, unless they've already pushed it to manual
[10:05] <Fujitsu> I suspect it will be.
[10:05] <persia> Fujitsu: Yep.
[10:05] <persia> StevenK: It did.  I'm hoping for at least one more run to grab the last few packages.
[10:07] <Hobbsee> persia: there's still stuff in unapproved, so until someone actually ack's that, then...
[10:08] <Fujitsu> Actually, there's no need to switch publisher to manual at the moment that I can see, so anything accepted will probably be published as normal, so the 1003 will be the last.
[10:08] <persia> Hobbsee: Yes.  It's the 3 in unapproved I'm watching.  At least sqlfairy made the run.  I'm guessing someone will pay attention soon, given the growing critical population.
[10:08] <Hobbsee> persia: yeah, well.  i've poked.
[10:10] <persia> Fujitsu: That still means we need the rest of the sources in for 0903, as otherwise the binaries will never go.
[10:10] <Fujitsu> persia: Hm, not sure about how freezes apply to binaries.
[10:10] <persia> Is it not the same queue?  It looks that way from the web UI.
[10:12] <Fujitsu> Hobbsee: Do you know if binaries ever go into unapproved?
[10:12] <Fujitsu> (only sources seem to be published in p.u.c/~ubuntu-archive/queue
[10:12] <Hobbsee> Fujitsu: they dont.
[10:13] <Hobbsee> well, not that i can see, anyway :)
[10:13] <Fujitsu> That's what I thought.
[10:13] <Hobbsee> hiya jono
[10:13] <Hobbsee> persia: exactly
[10:13] <persia> Oddly though, I had a package with NEW binaries go in today, without ever showing in the NEW queue (that I saw).
[10:13] <Fujitsu> persia: Somebody might just have been very quick.
[10:14] <Hobbsee> persia: which was that?
[10:14] <persia> Fujitsu: Maybe.
[10:14] <Fujitsu> snort?
[10:14] <persia> Hobbsee: snort-common-libraries
[10:14] <Hobbsee> oh, i didnt ack that
[10:14] <persia> Hobbsee: New snort finished publishing for !hppa a couple hours ago.  Refresh your apt-cache :)
[10:15] <jono> heya Hobbsee
[10:15] <Fujitsu> Why aren't we permitted to see UNAPPROVED through the LP UI?
[10:15] <Hobbsee> persia: wasnt looking in my aptcache.
[10:15] <persia> Fujitsu: Silliness
[10:15] <Hobbsee> Fujitsu: goodness only knows.  becaus eit's soyuz, and we know about how soyuz is made..
[10:16] <Hobbsee> and they refuse to break the freeze, and add a chunk of existing launchpad code now.  GRRR!
[10:16] <Fujitsu> NEW I could understand (even though we can see it), due to copyright issues, but UNAPPROVED is explicitly denied for no particularly good reason that I can see.
[10:16] <Hobbsee> they say it's not critical.
[10:16] <Fujitsu> Hobbsee: Bah, who needs release managers.
[10:16] <Hobbsee> yeah, well
[10:19] <Fujitsu> Aw, they're not releasing 1.1.10 in the next couple of days. It doesn't seem right to not have new Soyuz-breaking features a day before release.
[10:19] <StevenK> Nope, being released on the 24th
[10:20] <StevenK> TheMuso: Like you need a video driver.
[10:20] <TheMuso> At least for gutsy that is.
[10:20] <persia> Anyone happen to know the planned estimated toolchain schedule?
[10:21] <TheMuso> StevenK: I do actually, and I'd like my monitor to run at full res.
[10:22] <TheMuso> StevenK: Actually, the eZoom plugin is very andy, particularly on my notebook.
[10:22] <TheMuso> s/andy/handy/
[10:22] <StevenK> TheMuso: Which is what I thought about, hence the lack of jokes.
[10:22] <TheMuso> StevenK: Gotcha.
[10:24] <TheMuso> But at any rate, I feel there will be a few unhappy ati driver users out there...
[10:24] <TheMuso> Come release.
[10:26] <Fujitsu> What's broken about it?
[10:26] <TheMuso> Fujitsu: Well for me at least, its not driving my monitor at full resolution possible, even though xorg.conf is correct for the monitor.
[10:27] <Fujitsu> TheMuso: What if you play around with displayconfig-gtk or xrandr?
[10:29] <TheMuso> Fujitsu: I could play with those a bit. It could also be something to do with my DDC-signaling incapable KVM.
[10:29] <Fujitsu> Ah, that could do it.
[10:29] <Fujitsu> randr probably wants EDID.
[10:29] <TheMuso> SO I need to try direct via VGA and DVI.
[10:34] <bryce> moving to -ati 6.7.x was a chancy risk we took, and we knew it would incur regressions for certain users.  However this was balanced by fixes to a number of long-standing problems.  I felt it was worth the risk, and I think due to how responsive Alex Deucher has been to generate fixes to the issues we've reported, it was a good decision.
[10:36] <bryce> the good news is that while we may still have some issues for situations like kvms or triple-head, or etc. Alex is still being very active with fixes, so as long as they get reported upstream effectively, we should be able to continue rolling out updates for -ati and resolve many of the remaining issues.
[10:36] <persia> bryce: Are you expecting high -updates traffic for the driver?
[10:37] <bryce> persia: I am hopeful we can roll out 6.8.0 and be done, but can't say for sure
[10:38] <bryce> persia, I think what we have now is stable enough that we could hold off until 6.8.0
[10:58] <huats> good morning everybody
[11:02] <pkern> persia: you highlighted me
[11:02] <persia> pkern: It was about bug #87844
[11:02] <ubotu> Launchpad bug 87844 in spe "[apport]  spe crashed with AttributeError in skip()" [Medium,Confirmed]  https://launchpad.net/bugs/87844
[11:03] <persia> pkern: More specifically, that bug was milestoned when I mentioned it (I don't know about the current state), and I thought the last comment was you indicating it should be pulled from SVN.  I doubt there's time for it to matter now.
[11:04] <persia> (hard freeze in < 1 hour and RM reviewing the last uploads beforehand already)
[11:06] <pkern> persia: It is too late. It would somehow require a UVFe anyway because the changes are way too intrusive.
[11:06] <pkern> Their way of programming is broken.
[11:10] <persia> pkern: It's still milestoned.  You don't happen to know how to unmilestone do you?
[11:11] <pkern> I don't see a milestone there.
[11:13] <pkern> persia: Sorry yeah. Un-milestoned.
[11:13] <pkern> Point is that this program might be unusable in its current state.
[11:14] <pkern> We can't fix that for RC/release, but we should consider a SRU iff we release with that program in Ubuntu.
[11:14] <persia> pkern: I totally agree it's broken.  I just don't think it's any more RC than the > 100 unmetdeps or > 100 FTBFS bugs that aren't milestoned, and I don't want to promise to fix it for gutsy unless someone actually volunteers to do so.
[11:15] <persia> Also.  Thanks for unmilestoning.
[11:15] <pkern> Now packages with unmetdeps should be removed IMHO, but well.
[11:16] <pkern> persia: Unmilestoning is clicking on the bug state and removing the milestone besides the bug's priority.
[11:16] <persia> pkern: Thanks for the hint.
[11:16] <nxvl> persia: hi
[11:16] <persia> removing packages is hard, so we don't.
[11:17] <persia> hi nxvl
[11:17] <nxvl> how are you?
[11:17] <nxvl> im reading the docs to help wwith hardy
[11:17] <nxvl> :D
[11:17] <nxvl> im creating mi pbuild chroot also
[11:17] <persia> pkern: The main obstacle is that we don't have "testing", so it's hard to keep a good model of the target set.
[11:17] <pkern> persia: Now actually removing packages should not be hard.
[11:17] <pkern> persia: If a package is not in a releasable state it should not be released.
[11:17] <persia> nxvl: Great!  We're having a bunch of sessions for Ubuntu Open Week soon, which might be interesting to you.
[11:17] <pkern> It could be pulled back in afterwards.
[11:18] <pkern> But universe isn't supported anyway, so... whatever.
[11:18] <pkern> Or rather *officially supported
[11:18] <persia> pkern: Perhaps.  If you have an idea for implementation, write a spec for hardy.
[11:18] <nxvl> persia: i have add Ubuntu Open week to mi Gcal so i don't forget it :D
[11:19] <nxvl> persia: and the motu meeting too
[11:19] <nxvl> but it's a little bit harder to be in MOTU meeting, here it will be at 7 am
[11:19] <pkern> persia: Implementation to get rid of unmetdeps/FTBFS packages shortly before release or somehow draw more attention to them throughout the cycle?
[11:20] <persia> pkern: Either would be good.  We have some infrastructure to detect unmetdeps, and tend to do better with them, but having something run dist-problems on universe would help.  We don't have any infrastructure to detect FTBFS due to bitrot, and only very weak infrasrtucture to support FTBFS from sync.
[11:21] <pkern> You have archive rebuilds to detect FTBFS?
[11:21] <persia> pkern: No.  We also only rebuild when we get a new upload, so if the build-deps shift, nobody notices.
[11:22] <persia> (sometimes this happens when there's no new upstream in >6 months)
[11:23] <persia> pkern: Actually, let me clarify that.  We have archive analysis runs & archive rebuilds, but only for main.
[11:25] <nxvl> persia: when it will be up the hardy mirrors? on Oct 18?
[11:26] <persia> nxvl: Perhaps.  It might be a little later.  Development won't really start until the developer summit is underway.
[11:30] <pkern> persia: Now main is actually a tiny subset.  I'm all for fix or lose it.  But well, probably too many packages for too few people.
[11:32] <persia> pkern: I don't think that's true.  We get a lot of people who want to help generally, but haven't found their niche yet.  Given public resources with dynamic TODO lists, I think they would be happy to use them to try different things, including unmetdeps and FTBFS work.
[11:32] <pkern> How could we track possible SRUs which are not prepared yet?
[11:33] <pkern> persia: The first dholbach pointed me at in the `mentor process' were unmetdeps.
[11:33] <persia> On the other hand, just implementing "lose it" might be a step in the right direction.  We'd need a pocket in which to temporarily stuff things, and get them back.
[11:34] <pkern> Well, we could just prepare a merged package and upload it.  But maybe it shouldn't need NEW approval (don't know how this is handled here).
[11:34] <pkern> The old version we synced was broken anyway.
[11:34] <persia> pkern: Possible SRUs?  I was just thinking of something that detected FTBFS from the buildd logs, and prepared a web interface listing them, with version and last uploader.  The system would auto-remove on the next successful build.  That'd be a good start.
[11:34] <pkern> And it lives on in librarian.
[11:35] <pkern> persia: I'm talking about spe.
[11:35] <pkern> Actually I did talk about both and intermixed, oh well.
[11:36] <persia> For spe, we've lost the window.  If it's broken enough (I don't know spe), we can prepare something for -updates, which is fairly easy, but needs to be a minimal changeset.
[11:36] <pkern> persia: Yep, but how to track that?
[11:36] <persia> For hardy, we just upload a fixed version, and everyone is happy.
[11:37] <pkern> It's confirmed -- medium, you can't escalate it more. ;)
[11:37] <pkern> I could open a gutsy task for it.
[11:37] <persia> pkern: Nominate the bug for "gutsy", and track as an SRU.
[11:37] <pkern> Aye.
[11:37] <pkern> And I also may approve the nomination, right? ;)
[11:37] <pkern> (It may be auto-approved anyway.)
[11:37] <persia> pkern: So the primary task becomes "hardy", and the new task is "gutsy".  And yes, approve the nomination if you like :)
[11:38] <pkern> It was auto-approved. ;)
[11:38] <persia> pkern: That's nice to hear.  For ages it was much more annoying than that.
[11:39] <pkern> Well I'm on edge, don't know the `real' LP. ;)
[11:40] <pkern> \sh_away: Thanks again for yesterday. ;)
[11:47] <nxvl> what that SRU means?
[11:47] <Hobbsee> !sru
[11:47] <ubotu> Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates for main and restricted, while https://wiki.ubuntu.com/MOTU/SRU is for universe and multiverse.
[11:47] <nxvl> Hobbsee: thanx
[11:48] <nxvl> !lp
[11:48] <ubotu> Sorry, I don't know anything about lp - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[11:48] <nxvl> :(
[11:48] <pkern> ubotu: LP is Launchpad (http://launchpad.net)
[11:49] <nxvl> !lp
[11:49] <nxvl> !LP
[11:49] <nxvl> ubotu: ping
[11:49] <pkern> Do I need elevated access to add factoids? Or are !ones specialcased anyway?
[11:49] <ubotu> Sorry, I don't know anything about lp - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[11:49] <ubotu> pong
[11:49] <pkern> Ah, he informed me, sorry.
[11:49] <persia> pkern: You'll want to submit to the list.  See the web page.
[11:50] <Amaranth> !launchpad
[11:50] <ubotu> launchpad is a collection of development services for Open Source projects. It's Ubuntu's Bounty and Bug tracker, and much more; see https://launchpad.net/
[11:50] <Amaranth> !lp is <alias> launchpad
[11:50] <ubotu> I'll remember that, Amaranth
[11:50] <proppy> ohayo
[11:50] <pkern> persia: #ubuntu-ops will review it according to the message I just got. ;)
[11:50] <pkern> Amaranth: Thanks.
[11:50] <nxvl> pbuild takes a lot to "create"
[11:50] <Fujitsu> !launchpad is a collection of development services for Open Source projects. It's Ubuntu's bug tracker, and much more; see https://launchpad.net/
[11:51] <persia> Fujitsu: You don't like Bounties?
[11:51] <Fujitsu> persia: That part was turned off more than a year ago.
[11:51] <Fujitsu> Well, unlinked, anyway.
[11:51] <persia> Fujitsu: Ah.
[11:51] <Fujitsu> It is meant to have died.
[11:51] <persia> Was it not a succesful program?
[11:51] <Amaranth> Fujitsu: Done
[11:52] <Fujitsu> persia: Not sure.
[11:54] <nxvl> pbuild create downloads a new OS, didn't it?
[11:54] <Hobbsee> effectively
[11:55] <nxvl> and why it doesn't use the packages in my system instead of downloading them?
[11:57] <TheMuso> nxvl: The idea is to use a clean environment to ensure the package builds properly.
[11:59] <nxvl> mmm
[12:00] <nxvl> TheMuso: ant why it doesn't use the .debs on /var/cache/apt/archives/
[12:00] <Fujitsu> nxvl: It's very unlikely that the entire base system would be there.
[12:01] <nxvl> mmm
[12:01] <nxvl> but it can use some packages
[12:01] <nxvl> so i don't need to download again
[12:02] <TheMuso> nxvl: Copy the packages you have to /var/cache/pbuilder/aptcache I think its called. Can't remember as I no longer use pbuilder.
[12:03] <nxvl> for example, if it's an upgrade for my system, why did i need to download once for my system and a second time for pbuild
[12:03] <nxvl> mm
[12:03] <nxvl> interesting
[12:03] <nxvl> whnx
[12:03] <Hobbsee> because you may have installed packages from unofficial repos, etc, and i dont think pbuilder is smart enough to detect that.
[12:03] <nxvl> Hobbsee: i haven't think on that
[12:04] <nxvl> :D
[12:43] <TheMuso> Adri2000: Your audacious-plugins upload has a broken upgrade path, as you forgot to put necessary conflicts etc in place for the binary packages, since you were moving a file from one package to the other.
[01:03] <pkern> gnome-dbg unmet recommends epiphany-browser-dbg, libtotem-plparser1-dbg. Annoying.
[01:04] <pkern> Newest gutsy.
[01:05] <blueyed> It's not uploaded yet.
[01:06] <pkern> Haha.
[01:06] <persia> blueyed: The archive is closed (I think), so it's too late now.  I'm just surprised it wasn't uploaded at the end of the session.
[01:06] <pkern> aptitude refuses to install gnome-desktop-environment. Fun.
[01:06] <pkern> From a minimal cli install.
[01:07] <blueyed> pkern: dholbach said to handle it, when he gets the mail.
[01:07] <Hobbsee> it's almost closed
[01:07] <blueyed> bug #145543
[01:07] <ubotu> Launchpad bug 145543 in meta-gnome2 "[UNMETDEPS]  meta-gnome2 has unmet dependencies" [Undecided,Triaged]  https://launchpad.net/bugs/145543
[01:07] <dholbach> blueyed: anybody else can upload it too - is the sponsoring team subscribed?
[01:08] <dholbach> I'm doing something else atm, if nobody looks at it in the next 30 minutes, I can do it - no problem
[01:08] <persia> dholbach: Are uploads not frozen?  I can upload now, but stopped ~24 hours ago because of the release freeze.
[01:08] <blueyed> someone assigned it to the ubuntu desktop bugs
[01:08] <dholbach> persia: some uploads were processed this morning
[01:08] <TheMuso> Hobbsee: As in almost closed, how long?
[01:08] <persia> dholbach: I've been watching :)
[01:08] <Hobbsee> unsure
[01:08] <Hobbsee> sometime after i shove my upload in :P
[01:09] <persia> Anyone from motu-uvf want to give me a blessing on meta-gnome2?
[01:09] <ajmitch> Hobbsee: ok, approve some NEW packages for me then, I just want to throw some last minute crack in ;)
[01:09] <TheMuso> ajmitch: lol
[01:10] <TheMuso> Hobbsee: I think the archive is closed.
[01:10] <TheMuso> judging by the time.
[01:10] <StevenK> Bah, it isn't even 1200UTC yet
[01:10] <Hobbsee> ajmitch: i cant :P
[01:11] <Hobbsee> TheMuso: yeah, but judging by the state of gutsy-changes still getting packages in, i dont thin it's quite closed yet :P
[01:11] <StevenK> persia: Can I bug you for a debdiff?
[01:11] <persia> StevenK: Sure.  Which?
[01:11] <StevenK> persia: meta-gnome2
[01:11] <persia> StevenK: http://launchpadlibrarian.net/9953256/meta-gnome2_2.18.3ubuntu2.dsc.diff
[01:12] <ajmitch> Hobbsee: not fair
[01:12] <Hobbsee> ajmitch: okay, more to teh point, i wont.
[01:12] <ajmitch> :P
[01:12] <persia> (assuming it applies & builds cleanly)
[01:12] <ajmitch> you're mean & cruel to me
[01:12] <ajmitch> who wouldn't want new, unreviewed crack in the archive?
[01:14] <StevenK> persia: Looks fine.
[01:14] <persia> StevenK: Thanks.
[01:18] <persia> blueyed: Uploaded.
[01:19] <persia> TheMuso: There was just an upload of that today, wasn't there?  Is it still broken?
[01:20] <TheMuso> persia: A file was moved between audacious-plugins, and plugins-extra, and no conflicts were put in place for the older package version, so upon upgrade, the upgrade process breaks.
[01:20] <ajmitch> ouch
[01:21] <StevenK> TheMuso: Do It.
[01:21] <persia> Nasty.
[01:21] <TheMuso> Thats what my message to Adri2000 was about before.
[01:21] <ajmitch> bad upgrades really suck
[01:21] <TheMuso> StevenK: Doing so.
[01:21] <persia> TheMuso: Just fix it.  It's too late to be poking people
[01:21] <TheMuso> persia: Yeah I was just telling him.
[01:21] <StevenK> TheMuso: So, if your testing is okay, you have my blessing to upload, and you can tell $release_person that
[01:21] <TheMuso> StevenK: Ok.
[01:27] <ajmitch> persia: why apologise? noone else has seen it & fixed it
[01:27] <persia> ajmitch: Because I uploaded it in May?
[01:27] <ajmitch> so we're all equally at fault
[01:27] <ajmitch> doesn't matter
[01:27] <dholbach> persia: thanks for meta-gnome2 love
[01:27] <persia> ajmitch: Except someone probably sent me the buildlog and I missed it in my mail.
[01:28] <persia> dholbach: No problem.
[01:29] <persia> ajmitch: It also is apparently responsible for us shipping libssl0.9.7, which we'd be better off without.
[01:31] <ajmitch> is that the only thing holding libssl0.9.7 in?
[01:31] <persia> ajmitch: Yep.  aolserver4-nsimap on amd64.  I'm looking now.
[01:31] <ajmitch> amazing
[01:32] <ajmitch> so close to having it removed :)
[01:36] <pkern> Now why oh why did you, Gutsy, start X albeit I did not request it... sucker.
[01:36] <ajmitch> heh
[01:38] <persia> Grr..  Who wrote "Ubuntu package not affected" on the RC bugs list for Debian bug# 438425
[01:38] <pkern> Now why does the postinst of xserver-xorg start X. That's just... braindead, kthx.
[01:39] <ajmitch> funny, I can't connect to the rc bugs page from my laptop
[01:41] <ajmitch> night
[01:42] <Fujitsu> ajmitch: Isn't it on your machine?
[01:44] <persia> Fujitsu: laptop / workstation
[01:44] <ajmitch> Fujitsu: yes, and it's solely due to the funny networking setup at home
[01:45] <Fujitsu> Night ajmitch.
[01:54] <TheMuso> Youch. audacious-plugins-extra pre-depends on audacious-plugins.
[01:54] <TheMuso> So I can't test my fix locally I don't think...
[01:55] <TheMuso> Am I right in thinking that a conflicts field is used if files have been moved between binary packages
[01:56] <persia> TheMuso: I'd recommend versioned comflicts & versioned replaces
[01:56] <persia> s/m/n
[01:56] <persia> um.  s/m/n/3
[01:56] <TheMuso> ah yes of course, replaces.
[01:57] <ScottK> Hobbsee: Do I need to bug someone about NEWing the liquidsoap?  TheMuso's upload seems to have got it to build for the first time.
[01:58] <persia> ScottK: You may at least want to wait for the amd64 build to finish...
[01:59] <ScottK> persia: Yes.
[02:01] <fernando> moin all
[02:02] <Hobbsee> you know, sometimes i'm not surprised why people say our QA is crap.
[02:02] <Hobbsee> TheMuso: which did you have a go at Adri2000 over?
[02:03] <Hobbsee> oh, it was audacious-plugins.
[02:03] <blueyed> StevenK: thanks for uploading/using the virtualbox-ose* patches! I've found another small problem though: bug 152925
[02:03] <ubotu> Launchpad bug 152925 in virtualbox-ose-modules ""vboxdrv stop" fails, if virtualbox is not running" [Undecided,New]  https://launchpad.net/bugs/152925
[02:03] <blueyed> (this can be really bad, if you want to remove the package)
[02:03] <TheMuso> Hobbsee: Telling him that he did not put appropriate conflicts/replaces into the audacious-plugins package due to a file move.
[02:03] <Hobbsee> when people dont test whether their stuff installs, particularly around the close of the archives, and it's simple to test....they clearly dont care much about QA>
[02:03] <StevenK> blueyed: I hate you.
[02:03] <StevenK> blueyed: :-P
[02:03] <Hobbsee> TheMuso: was wondering if it was the same or different to the one i'd found.
[02:04] <blueyed> StevenK: it worked with the Depends on virtualbox-ose :P
[02:05] <StevenK> Actually, that was me, I added set -e to the init script, yours didn't have it.
[02:05] <pkern> Hobbsee: Thanks (re QA)
[02:05] <pkern> I'm mindly disappointed of the result I get with cli+gnome-desktop-environment. Metacity does not start automatically albeit being installed.
[02:05] <pkern> But it's too laaaaate.
[02:07] <blueyed> Any chance the fix for bug 127325 can be uploaded still? libphp-phplot seems to be unusable in Gutsy otherwise.
[02:07] <ubotu> Launchpad bug 127325 in libphp-phplot "No graphs after upgrade to Feisty" [Undecided,Confirmed]  https://launchpad.net/bugs/127325
[02:08] <StevenK> blueyed: I wonder if '|| :' works too
[02:09] <blueyed> StevenK: '|| :' ? instead of '|| true'? I don't know the former.
[02:09] <StevenK> || true requires forking /bin/true, || : doesn't. :-)
[02:12] <pkern> persia: At least when you don't assume that Debian will do the work. :-P
[02:12] <ScottK> blueyed: At this point, does it meet the criteria for an SRU?
[02:14] <blueyed> ScottK: I think so. At least the package can be left in a broken state and joe user would have no clue what's wrong, when he wants to remove the package.
[02:14] <StevenK> ScottK: It could convincably make an update harder.
[02:14] <StevenK> ScottK: So I'd rather get it fixed now.
[02:15] <ScottK> StevenK: OK.
[02:15] <StevenK> Er, conceivably
[02:15] <ScottK> blueyed: What StevenK said.
[02:15] <StevenK> Whatever. You know what I mean.
[02:17] <blueyed> Speaking about upgrades, see bug 152825: "virtualbox" gets replaced by "virtualbox-ose", but the modules are missing then..
[02:17] <ubotu> Launchpad bug 152825 in virtualbox-ose "virtual box not working after 7.10 upgrade (dup-of: 152405)" [Undecided,New]  https://launchpad.net/bugs/152825
[02:17] <ubotu> Launchpad bug 152405 in virtualbox-ose "Virtualbox should depend on virtualbox-ose-modules" [Undecided,Confirmed]  https://launchpad.net/bugs/152405
[02:17] <StevenK> It Recommends them. Enough already
[02:17] <StevenK> If they use a package manager with sense, the modules get dragged in to
[02:18] <StevenK> s/to/too/
[02:18] <Hobbsee> StevenK: apt wont.
[02:18] <blueyed> StevenK: synaptic neither
[02:18] <StevenK> "with sense"
[02:18] <Hobbsee> yeah, well.
[02:18] <StevenK> Users suck
[02:18] <ScottK> Hobbsee: Can we go ahead with an upload for bug 127325?
[02:18] <ubotu> Launchpad bug 127325 in libphp-phplot "No graphs after upgrade to Feisty" [Undecided,Confirmed]  https://launchpad.net/bugs/127325
[02:18] <ScottK> Package is currently pretty broken.
[02:18] <Hobbsee> ScottK: who are you asking me this as?
[02:19] <Hobbsee> ScottK: oh, motu-uvf?
[02:19] <ScottK> RM hat.
[02:19] <ScottK> Should I ask in another channel?
[02:19] <Hobbsee> ScottK: should be fine
[02:19] <Hobbsee> archive isnt frozen yet
[02:19] <ScottK> blueyed: It's going to work, right?
[02:20] <blueyed> ScottK: yes, I've made the patch, and let it confirm by another user. I've not tested it myself, but it's quite safe and cannot be more broken anyway.
[02:21] <persia> Did anyone ever get eclipse built?
[02:21] <ScottK> persia: No.
[02:21] <ScottK> I wouldn't wish it on the buildd's at this point.
[02:22] <persia> I'm not advocating it, just curious.  When IDEing (rarely) I'm a netbeans person anyway
[02:23] <persia> StevenK: Why?
[02:23] <StevenK> Because 'ew' :-)
[02:24] <TheMuso> Argh! I'm dumn. "Who cares about QA? Not me. :p" I just found out that I moved a file between two bloody binary packages for ubuntustudio without doing the same thing as I am working on for audacious plugins. Would one of you UVF gods mind giving an exception for an ubuntustudio-look upload to fix this stupid oversight I made a couple of days ago? :S *Me blushes*
[02:24] <persia> StevenK: The very concept of an IDE, or NetBeans vs. Eclipse
[02:24] <StevenK> persia: Latter.
[02:24] <StevenK> TheMuso: You also can't spell. :-P
[02:24] <persia> StevenK: Ah.  Personal ties :)
[02:24] <StevenK> TheMuso: Hit me with your debdiff
[02:25] <TheMuso> StevenK: Will do so shortly, and will have one for audacious once their both tested.
[02:25] <pkern> The person who chose to ship that...
[02:27] <StevenK> blueyed: New virtualbox-ose and virtualbox-ose-modules uploaded.
[02:28] <ScottK> blueyed: How about a feisty SRU once this is uploaded?
[02:28] <blueyed> StevenK: -ose? for the Depends?
[02:28] <StevenK> blueyed: Yes
[02:28] <blueyed> Great :)
[02:28] <blueyed> ScottK: about what exactly?
[02:29] <StevenK> I am going to hunt down these virtualbox bug submitters ... :-P
[02:29] <ScottK> blueyed: Is the libphp-phplot but an issue in Feisty too?
[02:29] <ScottK> but/bug.
[02:29] <persia> So, aolserver4 starts a daemon in the postinst, and always fails because it can't read a library it itself is supplying.  `dpkg --configure -a` always fixes it.  Any suggestions?
[02:30] <pkern> persia: nsopenssl was just given back on amd64.
[02:30] <blueyed> ScottK: Ah, yes. Why not? I've nominated it for feisty.
[02:30] <pkern> persia: Same failure AFAIK.
[02:30] <persia> pkern: It won't help.  See Debian bug #438425
[02:30] <ubotu> Debian bug 438425 in aolserver4 "aolserver4: Fails to install: error while loading shared libraries: libnsd.so" [Serious,Fixed]  http://bugs.debian.org/438425
[02:31] <pkern> persia: Bah ):
[02:32] <persia> pkern: My candidate aolserver4 fixes that issue, but I've encountered the new one above during package review.  Any ideas?
[02:32] <pkern> I already suspected a trigger problem (libc6 ldconfig), but that somehow confirms it.
[02:32] <pkern> persia: "the new one"? But no, probably no idea. DkrtKranz (+ spelling) fixed nsopenssl through giveback.
[02:33] <persia> pkern: Ah.  Because ldconfig hasn't yet run, the postinst fails?  Do you know of another package that encountered the ldconfig issue, and was fixed?
[02:33] <persia> pkern: Basically, I have a fix for the issues with building plugins, but not for actually installing the server cleanly (it's still as broken after my work as before)
[02:34] <ScottK> Hobbsee and blueyed: libphp-phplot uploaded.
[02:34] <blueyed> ScottK: thanks!
[02:35] <pkern> persia: And the postinst still fails? The last I saw was a "hey, I can't bind on port 80" message in the buildlogs, which was non-critical as it didn't cause the postinst to fail actually.
[02:35] <TheMuso> How does dpkg work when it encounters conflicts/replaces? Does it have to remove a package before it upgrades the other?
[02:35] <ScottK> blueyed: I also approved the Feisty task and assigned it to you.
[02:37] <persia> pkern: http://paste.ubuntu-nl.org/40698/
[02:37] <persia> TheMuso: It prefers to remove and install.  Ideally you'd test against a local repo.
[02:38] <TheMuso> persia: THought as much.
[02:38] <pkern> persia: Does a ldconfig -n <path> in postinst help?
[02:38] <geser> persia: perhaps the triggers for ldconfig break it
[02:38] <pkern> persia: Would be a crude hack but well better than a broken package.
[02:38] <persia> geser: That's what pkern had suggested.
[02:38] <pkern> geser: Yes.
[02:40] <persia> Um.  Where do I put it?  Right before the call to launch the daemon?
[02:42] <persia> Err..  There's actually a call to "ldconfig" already there.  Will ldconfig -n <path> act differently than just ldconfig?
[02:42] <TheMuso> StevenK: http://www.themuso.id.au/ubuntu has the diffs
[02:43] <geser> persia: isn't ldconfig a wrapper now?
[02:43] <persia> geser: Good point.  I'll just swap that with ldconfig.real, shall I.  Thanks.
[02:43] <Fujitsu> geser: It is.
[02:47] <proppy> hi
[02:50] <blueyed> ScottK: I've provided a debdiff for the SRU (libphp-phplot)
[02:50] <ScottK> blueyed: Let's wait until the Gutsy one is built.  Then subscribe UUS.
[02:51] <blueyed> UUS? ubuntu-sru? I've subscribed the latter already, sorry. Can you undo it?
[02:51] <StevenK> TheMuso: Providing the version numbers are correct, I'm fine.
[02:51] <TheMuso> StevenK: Ok.
[02:53] <persia> Cool.  `ldconfig.real` worked.  Thanks pkern, geser, and Fujitsu.
[02:54] <Adri2000> TheMuso: argh, I'm really sorry :( thank you for taking care of fixing my mistake
[02:54] <TheMuso> Adri2000: np.
[02:54] <TheMuso> Adri2000: I made the mistake on another package, so we're both guilty. :)
[02:57] <pkern> persia: I don't know what the wrapper does.  I sounds a bit wrong to call .real but well. -n just looks in the path you specify, not all.
[02:58] <geser> pkern: ldconfig checks if it is called by the triggers and runs ldconfig.real else registers only that it needs running and the end
[02:59] <pkern> Which explains why it isn't on Debian.  What a hack.
[03:00] <persia> pkern: There are about 6 shared libraries.  I don't think it's going to hurt it too much to run ldconfig twice during install, rather than once (it's still better than for every package)
[03:00] <pkern> Thanks geser
[03:00] <geser> pkern: afaik Debian's dpkg doesn't support triggers yet
[03:02] <pkern> geser: Exactly.
[03:08] <ubotu> Launchpad bug 151563 in openssl097 "Please remove openssl097 source and binaries from Gutsy" [Medium,In progress]  https://launchpad.net/bugs/151563
[03:09] <blueyed> ScottK: virtualbox-ose-modules 5 appears to have been rejected.
[03:09] <blueyed> StevenK: ^^, sry
[03:09] <StevenK> And then reuploaded
[03:22] <Kopfgeldjaeger> hi
[03:29] <bddebian> Heya gang
[03:29] <persia> hi bddebian
[03:30] <bddebian> Heya persia
[03:44] <persia> If any further uploads are permitted to the archive, I'd like to submit http://launchpadlibrarian.net/10008813/aolserver4_4.5.0-10ubuntu2.debdiff.  It fixes the FTBFS for aolserver4-nsimap, which allows the removal of libssl0.9.7.  If not, I'd like to be told "No", so I can sleep without worry.  Could someone please guide me?
[03:45] <zul> !uvf
[03:45] <ubotu> uvf is Upstream Version Freeze.  For an exception, see https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6
[03:45] <zul> but i think it might be too late
[03:45] <persia> zul!  Does xenman work in gutsy?
[03:45] <zul> i havent tried it
[03:46] <zul> but sure
[03:47] <persia> zul: Ah.  I wasn't sure from comparing versions if Debian bug #444784 applied, and you seemed to be the person with whom I should have spoken.
[03:47] <ubotu> Debian bug 444784 in xenman "xenman doesn't run at all" [Grave,Fixed]  http://bugs.debian.org/444784
[03:48] <zul> persia: it says fixed
[03:48] <zul> persia: i just ran it
[03:48] <persia> zul: It's fixed in Debian, but in a version later than the last merge.  That's why I wasn't sure.
[03:48] <zul> persia: we have that patch already in gutsy
[03:49] <persia> zul: Excellent.  Thanks for the confirmation.  It was the last of the closed Debian Grave bugs that I was trying to make sure were fixed for gutsy.
[04:02] <blueyed> StevenK: virtualbox-ose-modules's postinst script is missing the DEBHELPER marker..
[04:02] <blueyed> Therefor the driver does not get started after installing the package.
[04:02] <blueyed> This was in my debdiff..
[04:05] <blueyed> Also I had to execute "sudo depmod" now manually, because the "depmod -A" from the init script seems to have been "not enough".
[04:07] <norsetto> hi bddebian, thx again for your help
[04:07] <Hobbsee> norsetto: seen lp.net/ubuntu yet?
[04:08] <norsetto> Hobbsee: no, whats up!?
[04:08] <Hobbsee> norsetto: most active contributors
[04:09] <norsetto> Hobbsee: he, there must be a bug somewhere ...
[04:11] <norsetto> Hobbsee: most probably they meant kmos ;-)
[04:11] <Hobbsee> HAHAHAHAHAHA
[04:11] <Hobbsee> he *would* be one ofthe most active, if his fixes were actually right.
[04:12] <bddebian> Heya norsetto, NP
[04:12] <bddebian> He pissed of some of the Debian games folks already too :-)
[04:13] <Hobbsee> now why does this not surprise me.....
[04:17] <blueyed> StevenK: I've re-opened bug 152376. The fix is really trivial. See the previous debdiff from me. Should I create a debdiff for this particular fix?
[04:17] <ubotu> Launchpad bug 152376 in virtualbox-ose-modules "Load kernel driver (vboxdrv) during boot" [Undecided,Confirmed]  https://launchpad.net/bugs/152376
[04:18] <StevenK> blueyed: I uploaded -modules 6 about five minutes ago
[04:47] <effie_jayx> is there a wiki page on how to use pbuilder? I need to learn how add extra packages as dependencies
[04:49] <Hobbsee> !pbuilder
[04:49] <ubotu> pbuilder is a system to easily build packages in a clean chroot environment. To get started with PBuilder, see http://wiki.ubuntu.com/PbuilderHowto
[04:49] <superm1> Hi effie_jayx, actually the way that extra dependencies are added is via debian/control of your source package though
[04:49] <superm1> in the build depends line
[04:49] <effie_jayx> ohh cool
[04:50] <superm1> once you've added them there, you pass the source package onward to pbuilder as Hobbsee described
[04:50] <effie_jayx> great
[04:50] <effie_jayx> Hobbsee and superm1 ,  thanks ;)
[05:19] <bddebian> Grr@games team :-(
[05:20] <geser> Hi bddebian
[05:20] <bddebian> Heya geser
[09:29] <ScottK> ajmitch: Are you looking for Python/django $PAID development work?
[09:38] <xtknight> tonyyarusso, ah, thanks for dealing w/ that bug.
[09:40] <ondrej> ScottK: what kind of job? :) just curious
[09:40] <ScottK> Ubuntu Masters of the Universe: https://wiki.ubuntu.com/MOTU | Archive is frozen for Gutsy.  Time to get ready for Hardy. | Want to get involved with the MOTUs? https://wiki.ubuntu.com/MOTU/Contributing | http://ubuntu.joejaxx.org/ - TOP 10 Uploaders/Packages"
[09:40] <ScottK> ondrej: IETF just put out an RFP for converting some of there stuff.
[09:41] <ScottK> It's not on their archive page yet, but it should be here shortly: http://www1.ietf.org/mail-archive/web/ietf-announce/current/maillist.html
[09:43] <ajmitch> ScottK: it would be nice, assuming I have spare time :)
[09:44] <ScottK> ajmitch: As i just said above ^^^ IETF is converting some of there tools to python/django and looking for proposals.
[09:44] <ajmitch> interesting
[09:44] <ondrej> ScottK: thanks for info
[09:45] <ScottK> ajmitch and ondrej: This is what they want to redo - https://datatracker.ietf.org/idtracker/ it's currently 6K lines of Perl.
[09:46] <ondrej> ScottK: I see. I don't have time for any job, I was just interested
[09:47] <RainCT> hi
[09:49] <RainCT> have you ever tried doing "sudo chmod 644 /"? (don't do it)
[09:49] <ajmitch> sounds like a silly thing to do
[09:49] <ajmitch> how far does it boot?
[09:52] <RainC1> I've been like 10 minutes hitting the PC (well, actually unmounting it because the damn CD reader is broken and didn't want to open) until I remembered I've a Gutsy install that should be working :P
[09:54] <RainC1> anyways.. what's about patching chmod (for Hardy) in order that it asks for confirmation before doing that stupid things lol. I think most of the users wouldn't have much of a clue what to do if they have the great idea to try this.. :P
[09:54] <ScottK> RainC1: What's the complete list of stupid user tricks you think should be banned?
[09:55] <ScottK> Hint: This is a slippery slope.
[09:56] <RainCT> uh.. well, there would be time enough until Hardy to talk about it
[09:56] <RainCT> s/talk/thing
[09:57] <ajmitch> there are *far* too many ways to break a system
[10:02] <RainCT> yes, so having less wouldn't be bad, or?
[10:02] <RainCT> it's just an idea.. isn't that important to me, I just thought I would ask you what you think about it since if it happens to someone (imagine a bad copy-past from a tutorial) if suddently programs start crashing and the terminal won't accept any command it might be quite disappointing..
[10:04] <RainCT> ok, I see it doesn't seems to be that a good idea.. :-p
[10:37] <DktrKranz> keescook, mind looking at bug 152624?
[10:37] <ubotu> Launchpad bug 152624 in nagios-plugins "Buffer overflow in check_http.c (CVE-2007-5198)" [Undecided,Confirmed]  https://launchpad.net/bugs/152624
[10:41] <keescook> DktrKranz: sure, it's on my list for today (got email about it).   thanks!
[10:41] <DktrKranz> I added a task for dapper too...original patch was not compatible, but it was just indentation issues
[11:31] <ScottK> pkern_: pitti just killed openssl097, thanks for your help in that.
[11:34] <gnomefreak> is there known issues with bzr package?
[11:34] <gnomefreak> people are telling me it doesnt install :(
[11:36] <nenolod> Adri2000, https://bugs.launchpad.net/ubuntu/+source/audacious-plugins/+bug/152918
[11:36] <ubotu> Launchpad bug 152918 in audacious-plugins "Try to replace libcurl.so from audacious-plugins-extra" [Undecided,Confirmed] 
[11:36] <nenolod> Adri2000, your non-maintainer upload broke the upgrade path :P
[11:37] <Adri2000> nenolod: I know
[11:38] <Adri2000> nenolod: TheMuso uploaded ubuntu4 to fix my mistake, it should be available soon
[11:42] <ScottK> Unforunately the upload didn't make the archive freeze cutoff.  Since that file doesn't exist in Feisty, it won't affect upgraders, only people already on Gutsy.  We'll need to deal with it in gutsy-updates.
[11:46] <nenolod> ScottK, no, because the file is provided by _two_ _packages_
[11:47] <nenolod> ScottK, which makes the other package (audacious-plugins-extra) uninstallable unless you do a kludgy workaround
[11:47] <ScottK> nenolod: At this point we need to get it into gutsy-updates as soon as we can.
[11:48] <ScottK> At this point we'd be pretty close to delaying the entire Gutsy release to get it in and the release manager said no.
[11:48] <nenolod> ok, fair enough
[11:54] <Adri2000> ScottK: I can upload to -proposed directly right? (no ack needed or something?)
[11:55] <ScottK> Adri2000: Yes.
[11:55] <ScottK> Once it's there, we can bug an archive admin to copy it to updates tomorrow.
[11:55] <persia> Adri2000: You'll want to follow the SRU process to get the package accepted after the upload
[11:55] <persia> !sru
[11:55] <ubotu> Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates for main and restricted, while https://wiki.ubuntu.com/MOTU/SRU is for universe and multiverse.
[11:59] <ScottK> Ubuntu Masters of the Universe: https://wiki.ubuntu.com/MOTU | Universe Freeze in effect, don't even ask start working on Gutsy SRUs. | Want to get involved with the MOTUs? https://wiki.ubuntu.com/MOTU/Contributing | http://ubuntu.joejaxx.org/ - TOP 10 Uploaders/Packages
[11:59] <ScottK> oops
[12:00] <TheMuso> ScottK: lol
[12:00] <Fujitsu> Shouldn't that go at the end where it usually is?
[12:00] <Fujitsu> I almost missed it.
[12:00] <ScottK> Well it seemed like the lead story.
[12:01] <persia> ScottK: Nah.  Archive freeze is old news.  So yesterday
[12:01] <ScottK> Konversation doesn't wrap /topic, so I never see the stuff at the end unless I scroll over it.
[12:01] <Fujitsu> Ah.
[12:04] <desertc> Re: Free Software games .... Considered ManiaDrive ?
[12:04] <desertc> http://maniadrive.raydium.org/
[12:04] <desertc> version 1.2 and 10,000s of tracks are available
[12:04] <Adri2000> TheMuso: your audacious-plugins upload got rejected (too late) :/ so I'm preparing an upload to -proposed: http://adrishost.homeip.net/~adri2000/ubuntu/audacious-plugins_1.3.5-3ubuntu3.1.debdiff < is it the same as what you did and tested?
[12:05] <persia> desertc: bug #131108
[12:05] <ubotu> Launchpad bug 131108 in ubuntu "[needs-packaging]  Maniadrive" [Wishlist,New]  https://launchpad.net/bugs/131108
[12:05] <ScottK> persia: Yesterday the archive was frozen.  Now it's FROZEN.
[12:06] <persia> ScottK: methnks it's just cured.  There's still 1 source in "Accepted"
[12:06] <TheMuso> Adri2000: You would have to do it with both packages would you not?
[12:06] <slangasek> Adri2000: change of plans, I've just accepted it after all
[12:06] <slangasek> sorry for the flip-flop
[12:06] <ScottK> I'm sure he doesn't mind.
[12:06] <persia> Adri2000: You can grab the rejected source from https://launchpad.net/ubuntu/gutsy/+queue?queue_state=4&queue_text=
[12:07] <ScottK> persia: Yes, it's not FROZEN, FROZEN, really I mean it yet.
[12:07] <Fujitsu> Still slushy, I'd say.
[12:07] <slangasek> our timeline on the dak stuff got pushed back somewhat involuntarily, which gave me an opportunity to take a second look
[12:07] <Adri2000> slangasek: ah! great, thanks, that will make things easier :)
[12:08] <persia> Fujitsu: More than that.  Think concrete, after a day or so of curing.  It's still not ready to dismantle the forms, but it's really hard to change now.
[12:08] <slangasek> also, I just hit the overwrite issue when upgrading my own system, so naturally that makes it a higher prio ;)
[12:08] <Fujitsu> slangasek: Hahah.
[12:08] <ScottK> slangasek: Thank you for all the attention you are paying to getting Universe right in the endgame.
[12:11] <Fujitsu> Aw, are we using `Alpha' as the milestone for Hardy?
[12:11] <slangasek> two minute build?  Yeah, let's go for it. :)
[12:13] <slangasek> ScottK: heh, color me puzzled that this requires any thanks.. :)
[12:13] <ScottK> slangasek: How about it hasn't always gone this way.
[12:13] <persia> slangasek: It's effort on your part.  That's always appreciated.
[12:14] <ScottK> persia: He's just accepted it.
[12:14] <slangasek> publisher's on manual right now
[12:15] <slangasek> since the only things being published are individually hand-held by the release team
[12:15] <persia> Ah.  That's it.  We were wondering if it would go that way ~15 hours ago.
[12:15] <Fujitsu> slangasek: What happens with binaries? Or do we not care if there are a tonne of hppa uploads post-freeze?
[12:17] <slangasek> Fujitsu: that's an interesting question and I do not know the answer
[12:17] <slangasek> but I assume that any binaries which land in gutsy after the hard freeze are SOL
[12:17] <Fujitsu> slangasek: I'd presume so, but I don't think this has happened before.
[12:17] <slangasek> which?
[12:18] <Fujitsu> Having thousands of binaries unbuilt at release.
[12:18] <Fujitsu> persia: That's true.
[12:18] <persia> Fujitsu: hppa is the only culprit
[12:24] <imbrandon> TheMuso: there is always plenty o beer after hours :)
[12:25] <ScottK> Particularly the ones that did after the 'freeze' uploads...
[12:27] <TheMuso> ScottK: aye.
[12:29] <Fujitsu> A new upstream release of KDE4 stuff at the 11th hour... how strange.
[12:33] <imbrandon> Fujitsu: howso ? they dont follow our release schedule