[12:07] <jamespage> hello - do I need a FFE to get a package removed from the archive?  I need todo some re-jigs first but euca moving out of main means I can do a bit of housekeeping...
[12:18] <doko> jamespage, which one?
[12:19] <jamespage> doko: libcommons-fileupload-java-universe - libcommons-fileupload-java is now in universe so we can drop the -universe version and restore its full feature set with a sync from debian
[12:20] <jamespage> doko: Documenting here - https://bugs.launchpad.net/ubuntu/+source/libcommons-fileupload-java/+bug/845541
[12:20] <ubot4> Launchpad bug 845541 in solr (Ubuntu) (and 5 other projects) "Remove libcommons-fileupload-java-universe from the Oneiric archive (affects: 1) (heat: 8)" [Undecided,New]
[12:20] <doko> jamespage, once it's not built anymore it will show up in NBS
[12:20] <cjwatson> removals don't typically require FFEs anyway, no
[12:21] <doko> pitti: FFE above ^^^
[12:23] <doko> so, is ubuntuone-couch now wanted in main?
[12:23] <pitti> jamespage: this sounds fine, removing duplicate sources is really cleanup and not a feature
[12:23] <jamespage> pitti: OK - but I do need a couple of FFE's to support this removal - re-syncs from Debian
[12:23] <jamespage> testing and documenting ATM
[12:24] <pitti> doko: it's an rrecommends of deja-dup, so I guess yes
[12:25] <doko> pitti, but we did move the rest out of main ...
[12:25] <pitti> doko: did we?
[12:25] <pitti> I thought it's back
[12:25] <pitti> U1 really ought to be in main
[12:25] <pitti> desktopcouch, ubuntuone-client etc. are all in main
[12:27] <doko> insighttoolkit built on powerpc, five more days now on armel ...
[12:29] <pitti> that's bigger than kernel and LibO together, isn't it?
[12:29] <pitti> must be a helluva tib
[12:29] <pitti> s/tib/lib/
[12:29] <doko> ahh, bug 844995
[12:29] <ubot4> Launchpad bug 844995 in python-couchdb (Ubuntu) (and 4 other projects) "Archive demotion to universe (affects: 1) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/844995
[12:31] <doko> pitti: couchdb, not ubuntuone
[12:42] <doko> pitti: thanks for taking the ladvd ftbfs ;-P
[12:43] <pitti> doko: two tests fail, they look a bit weird (it's trying a chroot() call); if they fail on the buildds as well, I'll have a closer look
[12:43] <pitti> gearmand built fine here, so I synced Debian's version as there is no delta any more
[12:43] <pitti> and I removed python-event; FUBAR, and no rdepends
[12:43] <doko> pitti, they did
[12:43] <pitti> that should take care of the libevent-1.4-2 ones
[12:44] <pitti> doko: ah, interestingly the chroot() one passed on the buildds
[12:44] <pitti> so I'll examine the http one
[12:46] <pitti> doko: BTW, I followed up to the ptlib/opal bug, asking for other release team member opinions; either we update the whole stack or remove them all
[12:47] <cjwatson> I'd rather not have to remove ekiga frankly
[12:47] <pitti> me neither
[12:47] <cjwatson> it may be a bit weird and shonky sometimes but it's definitely used
[12:47] <pitti> I had used it for years without much problem
[12:47] <pitti> these days I prefer empathy, but according to the changelog it's still quite alive
[12:48] <pitti> I just don't feel unbiased enough any more to say "let's update it all"
[12:48] <tumbleweed> sorry I totally dropped the ball on that, thanks for looking at it. It looked like updating the whole stack would do the trick
[12:48] <pitti> tumbleweed: yes, I followed up there some hours ago; it took the better part of my morning, but I have all packages ready for upload now
[12:48] <ScottK> It would be good to have Daviey check out the asterix aspect of it.
[12:49] <pitti> the main risk here AFAICS is breakig asterisk due to the new spandsp
[12:49] <ScottK> Fortunately we know someone who's very familiar with the package.
[12:49] <pitti> that version is in unstable, of course, so I'd think that asterisk breakage would have been detected there
[12:49] <pitti> but better checking twice at this point
[12:51] <doko> jamespage,  libcommons-fileupload-java synced
[12:54] <jamespage> doko: thanks
[12:55] <jamespage> hrm - although I think that needed a FFE ack from ubuntu-release as its a minor version upgrade
[12:56] <jamespage> plus it generates a new -java-doc package for the API documentation which is now in NEW
[12:58] <cjwatson> jamespage: you only need an FFE if there are new features in that minor version upgrade, not just because of the version change
[12:58] <doko> jamespage, hmm sorry, had the impression pitti had given one
[12:59] <jamespage> cjwatson: ah-ha - I missed that point of detail - thanks for clarifying
[13:01] <cjwatson> pitti: non-binding opinion :-) added to the bug
[13:01] <jamespage> doko: so that sync was OK - my mistake
[13:01] <cjwatson> (as in, probably worth giving other people a chance to respond)
[13:02] <jamespage> doko: with that new nugget of information I don't believe the minor version upgrade to libspring-java needs an FFE either - great
[13:03] <jamespage> well at least I tested it well and learn't something new today :-)
[13:14] <pitti> cjwatson: *nod*
[13:18] <doko> pitti: is calling dpkg-gensymbols -c4 really a good idea for an 48h building package like webkit?
[13:21] <pitti> well, wasn't my idea :) but in general I do -c4 in my packages as well
[15:51] <cyphermox_> fyi, I'd like to upload the release tarballs of 0.9.0 for the different vpn plugins (vpnc, openconnect). They are all just bugfix. mostly making sure all strings are translatable (the translations should already be available, just not getting used in code)
[15:52] <cyphermox_> openvpn needs an update too bug that one will get a UIFE, since there is one extra combo
[16:41] <ScottK> lamont: Are you around?  I've got a problem that might need some of your help to diagnose.
[16:44] <lamont> bah
[16:44] <lamont> I mean, wassup?
[16:44] <ScottK> Hi.
[16:44] <ScottK> kde-runtime FTBFS because patches wouldn't unapply.
[16:44] <ScottK> It works fine for everyone locally.
[16:44] <lamont> neat
[16:45] <ScottK> Tried the same package in a PPA an it magically built on i386, but failed on amd64.
[16:45] <lamont> bzr branch lp:~lamont/launchpad-buildd/chroot-scripts; chroot-scripts/make-chroot.sh -d oneiric --lp
[16:45] <lamont> that is most strange
[16:46] <ScottK> So I was wondering if you had some way to capture the debris of the build and examine it's entrails?
[16:46] <lamont> not trivially
[16:47] <lamont> and certainly not expostfacto
[16:47] <ScottK> Right, but if you were prepared, we could retry it.
[16:47] <ScottK> I'll suggest someone try to replicate it with your sbuild branch first.
[16:48] <lamont> that branch just gives you a launchpad build-chroot as it should exist after dist-upgrade
[16:48] <ScottK> OK.
[16:49] <ScottK> If you get bored, the PPA version of the 'bad' thing in question is https://launchpad.net/~kubuntu-active/+archive/ppa/+sourcepub/1932597/+listing-archive-extra
[16:50] <lamont> ok.  I see boredom coming sometime in 2040 at this rate
[16:50] <ScottK> OK.  Just checking.
[17:06] <lamont> ScottK: if it's still not solved on monday, poke me and we'll figure out a time (prolly wednesdayish) to work on it
[17:06] <ScottK> lamont: Thanks.
[17:16] <skaet> lamont,  is there an ETA on https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/796769
[17:16] <ubot4> Launchpad bug 796769 in gradle (Ubuntu Oneiric) (and 1 other project) "gradle needs a manual build using the unstable binaries (affects: 2) (heat: 12)" [High,Confirmed]
[17:17] <skaet> ?
[17:22] <micahg> skaet: re firefox for beta 2, chrisccoulson and I were discussing yesterday with upstream, it seems that we'll be shipping the final beta for Firefox/Thunderbird 7 for beta 2 and uploading the release builds once the freeze is lifted (Firefox/Thunderbird 7 final is what oneiric will hopefully ship with)
[17:23] <micahg> should be minimal if any changes from final beta to release
[17:43] <micahg> skaet: did you miss my notes before?
[17:43] <skaet> micahg, yes, appear to have.   Changing rooms at the conference.
[17:43] <lamont> skaet: deej bootstrapped it yesterday
[17:44] <micahg> ah, well, this can wait till, monday, but wanted to give you a heads up
[17:44] <micahg> [12:22] <micahg> skaet: re firefox for beta 2, chrisccoulson and I were discussing yesterday with upstream, it seems that we'll be shipping the final beta for Firefox/Thunderbird 7 for beta 2 and uploading the release builds once the freeze is lifted (Firefox/Thunderbird 7 final is what oneiric will hopefully ship with)
[17:44] <micahg> [12:23] <micahg> should be minimal if any changes from final beta to release
[17:44] <lamont> skaet: all of which is to say "I have no clue why the bug should have been assigned to me"
[17:45] <skaet> lamont,  it was one of a set from a while back.   entropy I imagine.   If deej has done it,  would be good if the status can be updated.  :)
[17:45] <lamont> yeah, I'll go kill the bug
[17:46] <skaet> lamont,  Thanks!
[17:46] <lamont> no worries.
[17:47] <skaet> micahg,  thanks for the head's up.  When will the version for beta 2 be landing?
[17:47] <lamont> skaet: as a heads up, syowa is going to retire early next week.  it has served us well as syncproxy.ubuntu.com these past 7+ years or so.
[17:47] <micahg> skaet: chrisccoulson might have a better idea, my guess is either day before or day of beta 2 freeze
[17:48] <skaet> lamont,  earlier is better than later in the week.
[17:48] <lamont> skaet: that is a major point in why I'm not rushing to finish it today. :p
[17:48]  * skaet trying to minimize opportunities for murphy around beta freeze.
[17:49] <skaet> lamont,  :)  indeed.
[17:49] <lamont> OTOH, the announcement to the mirror community will go out todayish, and I expect that "early" == tuesday
[17:50] <skaet> lamont,  that should work out ok.  We have wednesday to recover then before beta freeze.  :)
[17:51] <lamont> oh, it only affects things mirroring.  nothing big or anything. :(
[17:51] <lamont> actually only about a dozen or two boxes where we don't have total control.
[17:51] <lamont> OTOH, not replacing syowa is even worse in its expected consequences
[17:51] <skaet> micahg:  thanks I'll follow up with you and chriscoulson on monday then.
[17:52] <skaet> lamont,  starting to show its age, huh?
[17:53] <lamont> that's a polite way to say it
[17:53] <skaet> gotcha
[23:47] <ScottK> lamont: I got the problem sorted.  It'd be nice if when dh_quilt can't unapply the patch it'd actually say that instead of just error in the build log.  Thanks for the offer.