[13:30] <onkarshinde> Is it possible to remove certain binary from archive?
[13:30] <tumbleweed> can we remove the sources that build it too?
[13:33] <onkarshinde> My query is in regard to bug #903382 It will be reat if someone with more knowledge about archive look at it and let me know which is feasible approach.
[13:37] <ampelbein_> onkarshinde: micah's suggestion looks sensible, did you try it?
[13:38] <geser> onkarshinde: 1) isn't possible (archive constraint that published packages mustn't change)
[13:38] <Laney> yes, just rebuild it
[13:38] <geser> so your only option is to do a new SRU
[13:38] <onkarshinde> Bumping the version means that I will have to work on SRU. Also the 'no change rebuild' SRUs are supposed to be clubbed with other SRUs. So I just wanted to check if '1' was possible. And 'geser' just said no. :-)
[13:39] <onkarshinde> By the way, isn't this a bug if 'precise' binary got copied to 'oneiric-proposed' in case of FTBFS.
[13:40] <geser> yes, checking if LP shows what happened
[13:41] <tumbleweed> removing it would mean replacing the binary currently published in precise, where it *is* installable
[13:42] <tumbleweed> so yes, rebuild
[13:43] <geser> wouldn't precise need an upload too? to guarantee that (version in oneiric(-updates) <= version in precise)?
[13:44] <tumbleweed> yes
[14:16] <Laney> woe is buildd backlog
[15:49] <studentz> New in MOTU & running Oneric. My q? Which dist should replace <release> (Oneric or Precise) in this command pbuilder-dist <release> create. Thanks for your patient.
[15:50] <psusi> whichever one you want
[15:51] <studentz> psusi Thanks.
[15:51] <psusi> presumably you want oneiric if you are planning on backporting, precise otherwise
[15:51] <psusi> or if you are just building to install yourself on oneiric
[16:17] <studentz> Hi there: I got an error with pbuilder  http://paste.ubuntu.com/769099/       Sorry bother you. What I'm doing wrong?
[16:40] <psusi> are you running ubuntu or setting up an ubuntu pbuilder on debian?
[16:41] <psusi> it looks like you're missing the ubuntu archive keys... install ubuntu-keyring
[16:41] <studentz> psusi running Ubuntu Oneiric .
[16:45] <studentz> psusi  ubuntu-keyring already installed. Also I have a gpg  exported and ssh key.
[16:47] <psusi> I usually just use pbuilder, not pbuilder-dist
[16:51] <studentz> psusi something like pbuilder create or pbuilder oneiric create ?
[16:56] <psusi> studentz: you have to set up a .pbuilderrc and configure it for what release and so on... I didn't know about pbuilder-dist, which looks like it handles most of that for you automatically which seems nice...
[18:07] <hyperair> jtaylor: ping
[18:07] <jtaylor> hyperair: pong
[18:07] <hyperair> jtaylor: regarding the gtk+ backport, do you know which bugs are fixed by 2.24.7?
[18:08] <jtaylor> one in easymp3gain and one in geany
[18:08] <jtaylor> one moment
[18:09] <jtaylor> Bug 875878 and Bug 851383
[18:10] <jtaylor> its possible there there are more in other gtk2 packages
[18:16] <jtaylor> its time for my first motu action :)
[18:16] <jtaylor> is this correct: syncpackage -d unstable pyzmq
[18:17] <jtaylor> (from unstable as precise already has zmq 2.10 so we need to upgrade, its not in testing due to a failure on arm)
[18:17] <jtaylor> and I'm curious if it builds on armhf
[18:23] <micahg> jtaylor: click ports on the PTS page
[18:23] <jtaylor> ah it built there
[18:23] <jtaylor> weird
[18:26] <jtaylor> I'd still like to sync it, as right now ir ftbs on all arches in precise due to b-d zeromq < 2.10
[18:26] <jtaylor> it works fine on i386 + amd64 and I plan to investigate the arm issue when I find the time
[18:30] <micahg> jtaylor: sounds good
[18:33] <hyperair> jtaylor: both bugs look like they come from gtkfilechooser being broken.
[18:34] <jtaylor> yes that is the source of the bugs
[18:34] <hyperair> jtaylor: the diff between 2.46.6 and 2.46.7 is pretty damn big. is it really not feasible to backport patches?
[18:34] <jtaylor> both fixed in .7
[18:34] <jtaylor> not really
[18:35] <jtaylor> the patch is not small and something of the 1000 line diff can easily be forgotten
[18:35] <jtaylor> pretty much the complete source file was refactored between .5 and .6 leading to the breakage
[18:35] <hyperair> urgh
[18:35] <jtaylor> + another huge diff to fix that again
[18:35] <hyperair> i see.
[18:36] <jtaylor> I'm running on .8 from precise currently
[18:36] <hyperair> hm
[18:37] <jtaylor> in one of the bugs is a backport attempt for the geany issue, but it does not fix the mp3gain issue
[18:37] <jtaylor> fixing that will probably pull the rest of the .7 changes
[18:37] <hyperair> i see.
[18:38] <hyperair> with geany, there's actually a workaround upstream that fixes the issue, but the diff for that is nontrivial and involves some refactoring again.
[19:22] <hyperair> jtaylor: huh, i see a patch in gtk+ that already fixes the filechooser issue with geany, and i can't seem to reproduce it here.
[19:22] <hyperair> werid.
[19:22] <jtaylor> yes its incomplete
[19:22] <jtaylor> I could still reproduce it with the patch
[19:22] <jtaylor> as a few others but not all
[19:23] <hyperair> i see.
[19:26] <jtaylor> great pyzmq fails on the archive builders but works fine in my chroot ...
[19:27] <ScottK> jtaylor: build log?
[19:27] <broder> https://launchpadlibrarian.net/87386428/buildlog_ubuntu-precise-i386.pyzmq_2.1.10-2_FAILEDTOBUILD.txt.gz
[19:27] <broder> there are...a lot of test failures there
[19:29] <broder> unfortunately the output from the test suite isn't very useful
[19:29]  * Zhenech_ smells some network-needing tests and your buildd-chroots forbidding it and then disappears
[19:29] <jtaylor> it should not need network
[19:29] <jtaylor> its the same testsuite as all versions before which worked fine on the builders
[19:30] <broder> it is using network - at least one of the failures is from binding to 127.0.0.1
[19:30] <broder> but that should work
[19:31] <broder> i wonder if the buildd's network access is firewalled off in some dumb way that causes problems
[19:32] <tumbleweed> I've never seen binding to 127.0.0.1 be a problem before
[19:38] <tumbleweed> hrm, SpamapS is talking about similar problems in #ubuntu-devel
[19:38] <ajmitch> I've seen binding to localhost fail, and binding to 127.0.0.1 succeed
[19:38] <ajmitch> iirc that was because of buggy ipv6 code