=== txwikinger2 is now known as txwikinger === cpg is now known as cpg|away === wgrant_ is now known as wgrant === cpg|away is now known as cpg === cpg is now known as cpg|away [02:02] Can anyone give ghc a priority bump on the ppc buildd please? [02:08] BenC: Link the build to me? [02:08] StevenK: https://launchpad.net/ubuntu/+source/ghc/7.4.1-4ubuntu1/+build/3646882 [02:08] BenC: Rescored. [02:09] StevenK: thanks! [02:09] It dropped from 60 minutes to 26. [02:15] StevenK: quicker than expected, it started already === cpg|away is now known as cpg [02:27] StevenK: if all goes well, this should clear out a huge chunk of FTBFS and dep-waits on ppc [02:27] \o/ [02:28] StevenK: any chance of an easy way to kick off rebuilds of all FTBFS on ppc matching .*haskell.* (once this is done)? [02:29] A lot of clicking on LP? :-) [02:29] * BenC prepares his rebuild-clicker thingy [02:35] api scripts should be able to, no? [02:41] Hello all! I had a quick question, I received an email back from submitting an app to the app showdown, and it said he made some changes and then " [02:41] I'll submit it for vote for inclusion in Ubuntu Extras." [02:42] I would assume this means I should take no action? However, the email also said, as part of the standard template, that I should make the changes and resubmit the application. [02:43] also, my status on myapps is Needs information. He said he posted the revised edition on a ppa which he linked, so should I resubmit and point to that ppa? Or merge, then resubmit with new ppa? [02:45] hupahuper: I'm not familiar with the myapps process, and I suspect that most of the people in this channel aren't, either. As /topic says, I think you'll be better off in #ubuntu-app-devel [02:45] ah, sorry. Thanks! [02:46] No problem! === cpg is now known as cpg|away [03:52] Good morning === cpg|away is now known as cpg [04:07] good evening [04:08] Good morning pitti === epikvision is now known as thinkndev === thinkndev is now known as epikvision === robert_ancell_ is now known as robert_ancell [04:27] StevenK: Do builds automatically get accepted or is there some handling occurring on that end? [04:33] BenC: It may be in NEW [04:34] StevenK: shouldn't be, nothing new in the package and it's accepted on i386 and amd64, but powerpc seems to be slow on the uptake [04:34] s/accepted/processed/ [04:35] It's accepted for powerpc, just not published [04:42] BenC: Ah, the publisher is blocked by generate-contents-files [04:42] Ah, thanks [05:22] Is wayland really going into 12.10? [05:24] Or was that just some wild rumor being passed around by the ignorant masses? :) [05:24] * Debolaz gets excited every time wayland is mentioned. [05:25] Debolaz: The last two releases have had wayland. [05:25] * ScottK is sure the next one won't be any different. [05:25] ScottK: Let me rephrase it: Actually used in 12.10. [05:25] By default, no. [05:27] Actually, TBD. [05:27] Still aiming for it, yes. [05:28] Debolaz: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-system-compositor [05:28] That's not user- or developer-visible wayland, of course. === tkamppeter_ is now known as tkamppeter [06:49] good morning === ubuntu is now known as Nathan_S [07:43] http://paste.ubuntu.com/1085796/ [07:43] should apt/dpkg be able to recover from this, or do I need to --reinstall? [08:13] cjwatson, around? my seed change broken the tomcat server task - not sure I understand why based on our conversation on Monday [08:35] doko, ping [08:49] hallyn: FYI, I reverted your libtiff5-dev cups change; that's not the right way; if we want to switch to libtiff5 by default, the "Provides: libtiff-dev" needs to be moved from 4 to 5 instead [09:02] jamespage: broke how? [09:02] cjwatson, so I can see that germinate picked up the seed change OK [09:03] but the ISO image build can't locate the tomcat7 packages [09:03] jamespage: oh, it's still in component-mismatches [09:03] cjwatson, so the packages have to be in main before the ISO build will pick them up? [09:03] now, I don't particularly think it needs an MIR since it's just a new version; but you filed one and it is as yet unapproved [09:03] yes [09:04] cjwatson, right - I misunderstood then [09:04] I'm a bit confused by your comment in the bug [09:04] "Jamie - When do you think you will be able to complete this review?" [09:04] but Jamie acked tomcat7 once tomcat6 is demoted [09:05] cjwatson, jdstrand did give an initial approval for tomcat7 on the MIR - but I added an extra dependency to enable the test suites which has not been acked [09:05] ah [09:05] so, I can act on the movements to main as soon as the MIR bits are ready, but I can't process the MIR for you [09:06] cjwatson, OK - I'll see what jdstrand says when he gets online but I expect the QA team will want this fixed [09:07] so I will probably back out my seed change later today [09:09] hello, [09:09] does ubuntu installer support partitions on encrypted LVM nowadays? or should I still use the text-based installer? [09:11] also, will it do the partition alignment for SSD disks? === ubuntu is now known as Nathan_S [09:15] xclaesse: encrypted LVM> not yet; it's on the roadmap for 12.10, hopefully [09:15] xclaesse: SSD alignment should work in 12.04, except for GPT (known bug, fixed in 12.10, will hopefully be fixed in 12.04.1 or failing that 12.04.2) [09:16] cjwatson, and if I use the alternate installer to have encrypted LVM, will it align as well? [09:17] I think so, though there are a lot of layers in that case :-) [09:20] yeah luks, lvm, ext4 :) [09:20] googling, and it seems it's possible to do with ubuntu [09:20] thanks :) [09:28] cjwatson, hey, is there any progress on the ubiquity,daily iso test issues? [09:34] seb128: no, I tried reproducing them again yesterday and failed to reproduce even once [09:34] :-( [09:35] cjwatson, so what would help at this point? having the test setup to run ubiquity under --debug or something? [09:35] a way to improve the probability of reproducing it locally [09:35] I need further modifications beyond --debug [09:36] I mean I can keep randomly trying but it's not a very efficient use of time :-P [09:36] right [09:37] but we need to figure out something before rick kill us all :p [09:37] I'll have another go, but I don't really know what to say [09:39] when it's this hard to reproduce manually it seems like the priority ought to be adjusted down from OMGDROPEVERYTHING a bit [09:42] cjwatson, right, I agree with that, I just think rick or jason are going to come back at some point asking where we stand and what's the plan to get the issues resolved so I'm trying to figure what the answers to those questions are... [09:42] cjwatson, do we have any idea that is a real issue for users out of the test setup? [09:42] or we just don't have enough tracking,feedback to know that? [09:42] not really aside from errors.ubuntu.com and such [09:46] hey cjwatson and seb128 , just catching up. can we at least revert the change(s) that are causing it until we have a way to reproduce it ? [09:46] jasoncwarner_: no [09:46] jasoncwarner_: there is no change I can identify as causing it [09:47] cjwatson: ok....hmmm...when you say "hard to reproduce manually", are you saying you can't reproduce, or that it is a challenge to reproduce it? [09:47] none of the recent installer changes have been AFAICS remotely related, and most of them fixed other bugs that also showed up in QA so reversion would not be an improvment [09:47] *improvement [09:47] jasoncwarner_: I have been able to reproduce maybe twice out of about a dozen attempts [09:47] jasoncwarner_: unfortunately neither of those were with sufficient debugging enabled [09:47] so, I mean, if the answer is that I just sit here mindlessly retrying I can do that [09:48] but based on experience so far I won't be able to give a timeline with any degree of confidence [09:49] cjwatson: or perhaps we can bring in some reinforcements? get more eyes on it? [09:49] well, feel free, although I'm not sure who else would be able to help [09:50] what I'm trying to do is to get logs with 'set -x' inserted just before the bit in /bin/hw-detect that asks the hw-detect/select_modules question [09:50] since that appears to be what's mysteriously bailing out [09:51] cjwatson: would it be quick to document the steps so someone else could give it a go? seb128 would you be able to take a look if that were the case? and perhaps we can grab ev and maybe pitti if they can spare a few minutes? [09:51] I just documented the steps above :-) [09:51] oh, and run with 'ubiquity -d' as well [09:51] cjwatson: always one step ahead ;) [09:52] I think it's kind of misdirected effort TBH, but well [09:52] cjwatson, it seems like the easiest way would be to get a package hacked to get whatever info we need and got it on an iso for the jenksys setup to run? [09:53] cjwatson: why so? I'm generally uneasy about something that you can only sometimes reproduce. [09:54] it's not a failure that's showing up on errors.u.c, or one I can find any other reports of from actual people [09:54] so, sure, it's a bug and we should definitely fix it to clear our automatic reports, but I feel OMG-fix-now importance for it is overinflated [09:55] and I definitely feel any more than two people on it is distracting attention from more important things that are actually affecting humans [09:55] [09:55] (grr) [09:55] cjwatson: though, it is breaking out builds right now as well, which is bad for the daily quality stuff, though, I do agree that if we put too many people on it, that takes away from other things (the careful balance ;) ) [09:55] it's not breaking our builds, it's breaking our jenkins tests, surely [09:56] not really the same [09:56] cjwatson: ack on the mispeak [09:56] cjwatson: do you suspect it might be tooling (aka the jenkins tests? ) [09:56] it can't be solely that because I did manage to reproduce it albeit rarely [09:56] (asking b/c you mention it isn't on errors etc) [09:57] cjwatson: hmmm...what is the issue exactly anyway (probably should have asked that earlier ;) ) [09:57] https://jenkins.qa.ubuntu.com/view/Quantal/view/ISO%20Testing%20Dashboard/job/quantal-desktop-amd64_default/79/ [09:58] bug 1023036 [09:58] Launchpad bug 1023036 in ubiquity (Ubuntu Quantal) "Error on /usr/share/ubiquity/plugininstall.py", line 1687, affecting desktop images (preseeded install)" [Critical,Triaged] https://launchpad.net/bugs/1023036 [09:59] ah, well, I can find one other report of it from a linux mint install in 2010 with a bunch of other errors before it [09:59] unlikely to be the same thing ... [10:04] doko, I've raised MP's for both icedtea-web and openjdk-7 to delete/recreate the alternatives with a higher priority that openjdk-6; and to switch the Dependencies for icedtea-web to openjdk-7 where appropriate. [10:04] would appreciate your review before I upload [10:05] cjwatson: I guess its puzzling (or troubling might be a better word for it) that only 2/8 manual tests have produced it, but it seems the auto tests can reproduce it quite regularly? [10:05] somewhat regularly; it's not consistent even in autotests [10:05] would only be a small change in the probability of some race or other to produce such a result, I gues [10:05] s [10:06] cjwatson: ok, so aside from adding more people looking at it, is there anything we can do for you at the moment? [10:06] would you like one minion or so to try and reproduce with you? ;) [10:07] I don't have any suggestions at the moment [10:07] I wish I did [10:08] cjwatson, what about what I said? if we get a package of an hacked ubiquity with logs details that could be useful and get it on an iso to throw to the jenkis? [10:08] seb128: that's a fair bit of work in itself, and it's not entirely clear to me that it will be useful because I don't know whether the logging I can think of so far will be sufficient [10:09] it's certainly a fallback measure, but I would prefer to continue manual reproduction attempts first [10:09] if we were going to do that I'd probably just upload extra debugging to quantal rather than bothering with building a separate iso :) [10:09] cjwatson, ok, is there anything special to do during the install, like is that specific to some options selected? [10:09] 10:50 what I'm trying to do is to get logs with 'set -x' inserted just before the bit in /bin/hw-detect that asks the hw-detect/select_modules question [10:09] 10:51 oh, and run with 'ubiquity -d' as well [10:10] the two times I reproduced it it was with all default options [10:10] cjwatson, right, I read that, I was just wondering if doing a standard full disk install with autologin is good [10:10] ok [10:10] I will try to fire a few vm installs and see if I can get it [10:10] ta, won't hurt [10:11] (that's what I've been doing since we started this conversation, too) [10:42] seb128,jasoncwarner_: well, I've uploaded a ubiquity version to quantal-proposed that adds a tiny bit more debugging, which will hopefully help [10:42] maybe [10:42] cjwatson, ok, I'm just done syncing isos, I will get that one in my vm and start test installs [10:42] cjwatson, thanks [10:43] I'll push through an updated CD build once that's all built and copied to quantal and published [10:44] IIRC jenkins automatically notices new image builds [10:44] it seems to do yes [10:44] it picked up the .1 isos yesterday === cpg is now known as cpg|away [11:07] doko, ping [11:21] seb128, ping [11:21] tvoss, hey [11:26] tvoss, it's about bug #1006860? do you know if that patch got forwarded upstream? [11:26] Launchpad bug 1006860 in gdb (Ubuntu) "gdb crashes when loading core files (in is_ctor_or_dtor)" [High,Confirmed] https://launchpad.net/bugs/1006860 [11:27] cjwatson, there is something weird with that ubiquity update, it doesn't start for me (I downloaded ubiquity ubiquity-ubuntu-artwork ubiquity-frontend-gtk and did dpkg -i those) [11:28] seb128: ENOTENOUGHDATA [11:28] seb128, no, I do not know. There was a comment on the bug saying that the ubuntu-reviewers team has been subscribed [11:28] seb128: Anyway I wasn't suggesting that you install those; it would be much quicker to edit /bin/hw-detect by hand ... [11:28] cjwatson, right, well I wanted to try those, will do that now [11:28] $ ubiquity -d [11:28] < 3 seconds wait> [11:28] $ [11:29] /var/log/syslog /var/log/installer/debug [11:29] not sure what datas would be useful [11:30] cjwatson, http://pastebin.ubuntu.com/1086028/ syslog [11:30] cjwatson, http://pastebin.ubuntu.com/1086029/ debug [11:31] No sign of an attempt to start ubiquity 2.11.11 there [11:31] hum [11:32] I think the debconf db is in some kind of broken state. Try from a fresh boot [11:32] In general running ubiquity multiple times without rebooting is not particularly well supported [11:32] Don't try it unless you're attempting to fix that :) [11:32] cjwatson, well sudo apt-get install ubiquity/quantal ... etc for the 3 binaries and it works again [11:33] but anyway I will downgrade and just hack the file by hand for the set -x [11:33] I'll worry about it if it happens to a fresh ISO built with that version [11:33] ok, fair enough, I prefered to mention it in case [11:33] Sure [11:38] tvoss, right, usually patches should be sent upstream as well if possible [11:40] seb128, okay. So I reach out to the gdb guys, referencing the bug report and proposing the patch, right? === MacSlow is now known as MacSlow|lunch [11:40] tvoss, correct [11:40] tvoss, thanks [11:40] seb128, np [11:46] seb128, hmmm, gdb points people back to the distribution [11:46] tvoss, why? our version is patched? [11:46] seb128, that's the argument, right [11:47] tvoss, ok, thanks, I was just trying to be good upstream citizen, I will check out with doko when he's online or sponsor the patch later if he doesn't reply (not sure how much he's around or if he's a debconf this week) [11:48] seb128, awesome, thanks. I will announce the patch together with a link to the bug report on gdb-patches, though [11:48] tvoss, thanks [12:01] @pilot in === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal A2 released! | Archive: open | Dev' of Ubuntu (not support or app devel) | build failures -> http://bit.ly/HaWdtw | #ubuntu for support and general discussion for hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mdeslaur, infinity [12:43] Ohm... === _salem is now known as salem_ [12:45] is in SRU queue, but doesn't show up in http://people.canonical.com/~ubuntu-archive/pending-sru.html [12:45] https://bugs.launchpad.net/ubuntu/precise/+source/aiccu/+bug/1007408 [12:45] Launchpad bug 1007408 in aiccu (Ubuntu Precise) "aiccu.conf does not need server directive, while upstart script wants it" [High,In progress] [12:45] larsduesing, https://launchpad.net/ubuntu/precise/+queue?queue_state=1 [12:45] larsduesing, the sru page only shows accepted SRUs [12:46] oh, ok.. [12:46] larsduesing, the one you mention is waiting for review to be accepted [12:49] yes... I see... [12:50] thanks... [12:55] pitti: mterry did ask cjwatson why libtiff-dev was on 4 instead of 5, I forget what the answer was [12:56] pitti: are you saying all of the changes we've been making for libtiff4-dev->libtiff5-dev are wrong, or cups is special? [12:58] If I got that question I didn't understand it [12:58] If we're switching to libtiff5-dev I tend to think we probably ought to switch the Provides [13:00] cjwatson: two days ago you added 'Provides: libtiff-dev' to tiff3 right? perhaps i misunderstood [13:00] do we not expect update-manager -d to allow upgrades yet ? [13:01] pitti: oh, i see. the ones which were 'libtiff-dev' should not be changed. [13:03] Well, they will be changed if you switch the provides. [13:05] hallyn: I didn't do anything [13:05] hallyn: All I did was sync both tiff and tiff3 directly from Debian; I made no Ubuntu-specific changes whatsoever [13:06] hallyn: tiff3 previously didn't exist; syncing it took over the libtiff4-dev binary package (and others) from what was previously built by the tiff source package [13:06] hallyn: So as far as the Provides goes, it was status quo [13:06] Changing libtiff-dev to libtiff5-dev, if anyone's been doing that, is certainly incorrect [13:06] cjwatson: i see. thanks [13:07] Changing libtiff4-dev to libtiff5-dev is merely arguable; it's probably better to make that libtiff-dev and switch the default [13:07] cjwatson: i guess the nbs reports (which have since been removed) made me think that switching to libtiff5-dev was more urgent [13:08] makes sense then, thanks [13:08] Those were only ever temporary; I'm sorry I didn't warn you, but I didn't expect the timing to be such that they'd show up on NBS at all [13:10] apw: generally yes [13:10] mvo, didn't work for me, had to do it by hand [13:15] hallyn: "no change for libtiff-dev"> right [13:18] cjwatson, ubiquity refuses to bug for me as well, 5 installs, no error :-( [13:18] jamespage: bug #1009579 ACK'd [13:18] Launchpad bug 1009579 in tomcat7 (Ubuntu) "[MIR] tomcat7 (replaces tomcat6)" [High,Fix committed] https://launchpad.net/bugs/1009579 [13:18] jamespage: do not my comments int he bug though :) [13:19] err [13:19] jamespage: do note my comments in the bug though [13:20] jdstrand, thanks for the ack; I will feed back the delta to Debian (I'm the maintainer of that package anyway) [13:20] * jdstrand nods [13:21] cjwatson, please can you dig me out of my tomcat-server seed change hole ^^ [13:21] I can do that [13:22] jdstrand, yes please [13:22] jamespage: you need an AA to promote jakarata-taglibs-standard? [13:22] And tomcat7 [13:22] jdstrand, both packages I think [13:22] apw: oohhh, the default is to do only lts -> lts at this point, need to look how to fix that via -d [13:24] cjwatson: I'm on it [13:24] mvo, ahh that'd expalin a few things ... === MacSlow|lunch is now known as MacSlow [13:30] jamespage: so, does this mean I can demote tomcat6? [13:30] jdstrand, almost - I just need to complete the transition for packages which use libservlet2.5-java to libservlet3.0-java which should free it up [13:30] @pilot in === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal A2 released! | Archive: open | Dev' of Ubuntu (not support or app devel) | build failures -> http://bit.ly/HaWdtw | #ubuntu for support and general discussion for hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: herton, mdeslaur, infinity [13:30] its packaging only so should not take to long [13:31] (i.e. I will have it done this week) [13:31] jamespage: is there a bug filed on it? [13:31] jdstrand, not yet [13:31] * jamespage add its to the list for this week [13:31] I'll file one real quick [13:31] ah - thanks [13:32] Is the apport retracer running? https://bugs.launchpad.net/ubuntu/+bugs?field.tag=need-i386-retrace&orderby=-id&start=0 has shown the same 16 bugs for at least the last 12 hours. [13:34] for multiarch packages, does the -dev need to Pre-Depends on multiarch-support as well as the lib package? [13:34] ScottK, shrug, log is "2012-07-03 08:18 i386.txt" [13:34] ScottK, so I guess it's down for a week [13:34] pitti, ^ should I just remove the lock and see how it goes? there is no obvious error in the log [13:34] jamespage: fyi, bug #1023405. I assigned it to you but didn't milestone it or anything [13:34] Launchpad bug 1023405 in tomcat6 (Ubuntu) "please demote tomcat6 source and binaries to universe" [High,Triaged] https://launchpad.net/bugs/1023405 [13:34] ScottK, thanks for pointing it [13:34] jdstrand, thanks [13:35] seb128: uh, sure; I thought I restarted it yesterday or so [13:35] seb128: if it's something permanent, it'll just fail again and then we can investigate [13:35] pitti, hum, that log is from 2012-07-03, i.e over a week untouched [13:35] pitti, if you restarted it yesterday do I overlook something? [13:36] seb128: apparently I just misremember then [13:36] pitti, ok, let me try to rm it [13:36] seb128: it looks like it just hung in the middle of retracing [13:36] Is there a part of dh_python3 or dh_python2 that mangles the shebang line at the top of scripts dropped in /usr/bin? [13:36] seb128: ah, the process is still running [13:36] seb128: I'll kill it [13:36] pitti, doh, I rm-ed the log by error [13:36] pitti, well it was only a log [13:36] pitti, thanks [13:37] seb128: ah, now I know -- I looked yesterday, saw the lock, checked ps, and saw that it was running [13:37] but I didn't look at the date [13:38] pitti, ev: does it affect errors.ubuntu.com stats in any way where a retracer is down for a week like that? [13:38] pitti, ev: if it does we should probably make sure we notice earlier when a retracer is stucked [13:38] seb128: no, errors.u.c. has its own set of retracers [13:38] ok, good [13:38] I hope they don't have similar issues ;-) [13:38] mterry: python3 setup.py install should change #!/usr/bin/python to be #!/usr/bin/python3 i think [13:39] mterry: but if you have "#!/usr/bin/env python" that breaks [13:39] dobey, I have env python3 [13:39] mterry: For dh_python3 in quantal as of yesterday. I don't think anyone's merged python-defaults, so not yet. [13:40] And setup.py seems to be called with python3 [13:40] ScottK, sorry, I don't follow [13:41] If "#!/usr/bin/env python" is pointing to a python3 version, that's not right. [13:41] The shebang rewriting is a new feature in dh_python2/3. [13:41] mterry, see changelog in http://packages.qa.debian.org/p/python-defaults/news/20120630T185419Z.html [13:41] I sync'ed python3-defaults ~yesterday, so that's in quantal. [13:41] "- rewrite shebangs by default (disable via --no-shebang-rewrite), [13:41] examples: [13:41] + "/usr/bin/env python*" → "/usr/bin/python*"" [13:41] No one merged python-defaults yet (AFAIK), so I don't think dh_python2 does that. [13:42] ScottK, makes sense, mterry's case is a python3 one [13:42] barry should do that merge though. [13:42] seb128, ScottK: I'm looking at update-manager, which during a build got translated from python3 to python, thus breaking it [13:42] ScottK, mterry: revelant upload is https://launchpad.net/ubuntu/+source/python3-defaults/3.2.3-1 for python3 then? [13:43] seb128: Yes. [13:43] ScottK: just to be clear-- /usr/bin/python shouldn't ever be python3 (unless maybe all of the world is changed). Is that accurate? [13:43] jdstrand: Something like that. [13:43] ok, that is what I thought [13:44] Or you're Arch, but they're just crazy. [13:44] mterry: Build log? [13:44] heh, it is a good thing I ported ufw then ;) [13:45] ScottK, https://launchpadlibrarian.net/109741274/buildlog_ubuntu-quantal-i386.update-manager_1%3A0.166_BUILDING.txt.gz [13:46] anyone have an answer to my multiarch question? [13:46] dobey: No, it doesn't. [13:47] mterry: And the problem is that there's a shebang re-written to /usr/bin/python? Where? [13:47] ScottK, in /usr/bin/update-manager [13:47] thanks [13:47] ScottK, in the source, it is "#!/usr/bin/python3" [13:48] but becomes "#! /usr/bin/python" [13:48] I agree that's unfortunate. [13:48] I'm testing with --no-shebang-rewrite now [13:49] It looks like it's using python3 throughout, calling setup.py with python3 and all that [13:51] Agreed. [13:53] ScottK, even with --no-shebang-rewrite, I still get the bug. Do you know which code is responsible for the build log line "copying and adjusting update-manager -> build/scripts-3.2" ? [13:53] I'm looking into it now. [13:59] gema: how long should it take jenkins to pick up the Ubuntu desktop 20120711.2 image build I did? [14:01] cjwatson: not much, let me check [14:01] cjwatson: are we talking quantal? [14:01] Yeah [14:01] * gema goes check [14:01] I figured I'd ask after an hour [14:02] cjwatson: I am going to run the jobs manually, they don't seem to have started automatically [14:03] Right, thanks [14:03] np, will keep you posted [14:03] mterry: If you can try a build locally with a modified dh_python3, what happens if you change python to python3 in the SHEBANG_RE ... line (32) of debpython/tools.py? [14:04] ScottK, ok [14:04] That RE is unchanged between dh_python2 and dh_python3, so I'm suspicious. [14:07] Also there's a log message in the relevant function (fix_shebang), so using verbose might be helpful. [14:09] ScottK, that changed the shebang line to "#!/usr/bin/python" (still python but now no space after the shebang?) [14:10] OK. I'm still looking at it. [14:10] Did you build with --verbose and did that yield anymore clues? [14:11] not yet, about to now === zyga is now known as zyga-food [14:14] ScottK, http://pastebin.ubuntu.com/1086226/ [14:15] ScottK, that is *without* the RE change [14:15] OK [14:15] I'll make one with [14:16] are we aware of a collision between ifupdown and netbase on /etc/init.d/networking ? [14:16] (this is an upgrade P -> Q) [14:18] ScottK, http://pastebin.ubuntu.com/1086239/ is *with* the RE change, if it illuminates anything [14:20] Don't see the "replacing shebang" log line in either [14:20] seb128: we don't have great failure notification on the errors.ubuntu.com retracers just yet, but webops tends to notice them going away. [14:20] at some point soon I'll get them wired up to nagios [14:21] bah, just got hit by bug #1019999 again [14:21] Launchpad bug 1019999 in moreutils (Ubuntu) "package moreutils 0.46 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/errno.1.gz', which is also in package errno 1.3-0ubuntu1" [Undecided,New] https://launchpad.net/bugs/1019999 [14:21] remove errno? it seems subsumed. [14:22] mterry: I'm not sure now what's doing it. [14:22] mterry, did you try to downgrade python3-defaults to see if that's coming from it? [14:23] ScottK, it seems python3 and dh_python3 both have shebang mangling code? [14:23] seb128, no, let me try that [14:24] dh_python3 is part of python3. [14:24] stgraber, hey .. i seem to have some fallout from the netbase/ifupdown breaks: stuff you did, seems to not be working right on upgrade ... [14:25] mterry: I have a minimal test case. fix_shebang in tools.py is definitely wrong. [14:25] ScottK, right. But there seem to be two bits. one in build_scripts.py and one in dh_python3 [14:25] ScottK, ok, well that's good then [14:26] But let's make sure we got the right thing. [14:26] apw: ah? test upgrades worked fine here, though I had one bug report of someone with a bad mirror (missing one of the two packages) [14:27] stgraber, i get this on upgrade direct from P to Q(today) [14:27] dpkg: error processing /var/cache/apt/archives/ifupdown_0.7.1ubuntu1_i386.deb (--unpack): [14:27] trying to overwrite '/etc/init.d/networking', which is also in package netbase 5.0ubuntu1 [14:28] cjwatson, did you read the discussion between ScottK and mterry? [14:28] --- 10/usr/lib/ubiquity/bin/ubiquity 2012-07-09 20:06:45.000000000 +0200 [14:28] +++ 11/usr/lib/ubiquity/bin/ubiquity 2012-07-11 12:54:45.000000000 +0200 [14:28] @@ -1,4 +1,4 @@ [14:28] -#!/usr/bin/python3 [14:28] +#! /usr/bin/python [14:28] Error: "@" is not a valid command. [14:29] cjwatson, that's ubiquity 2.11.10 -> 2.11.11 [14:29] cjwatson, I'm pretty sure that's why the update was busted for me [14:29] apw: hmm, I guess ifupdown could use a Breaks statement... I just followed what Debian did (changing the version numbers to match), but just having Replaces: netbase (<< 4.00) seems wrong indeed [14:29] ScottK, mterry: ^ btw [14:29] hm [14:29] apw: can you file a bug against ifupdown? [14:31] stgraber, ack [14:31] stgraber, so does that mean i should be upgrading netcore first, or removing it [14:32] apw: you should be upgrading netbase first indeed, that'll make /etc/init.d/networking go away, then ifupdown can unpack and take that file over [14:33] seb128, ScottK: Downgrading python-defaults to 3.2.3-0ubuntu1 didn't help [14:33] seb128: oh, hah, thanks [14:34] cjwatson, yw [14:34] gema: ^- so that jenkins test will not be very useful - sigh [14:34] stgraber, bug #1023437 [14:34] Launchpad bug 1023437 in ifupdown (Ubuntu) "ifupdown conflicts with netcore both of which own /etc/init.d/networking" [Undecided,New] https://launchpad.net/bugs/1023437 [14:35] cjwatson: sorry! [14:35] apw: netbase :) but thanks for the report, will look at it once I'm dong fighting with iscsi and meetings :) [14:35] gema: not your fault :) [14:35] mterry: OK. Then it's not the new rewriting feature. [14:35] cjwatson: let me know whenever you want another run, the one ongoing will finish anyway [14:36] I suspect it's the python3 distutils one. [14:36] stgraber, fixed :) if i try and install netbase it says it cant cause of the breaks [14:36] I assume there's no point in me debugging this from the ubiquity point of view? [14:36] mterry: clearly debhelper thinks this is a python package and I think it's running the wrong distutils. Something needs overriding. [14:36] ScottK, is there a known change in that code recently, that I can downgrade? [14:37] that was the only one I knew of. [14:37] apw: fun ;) can you try "apt-get install netbase ifupdown"? not sure if that'd be enough to give a hint to apt about the required ordering. [14:37] cjwatson, mterry ran into it with update-manager === zyga-food is now known as zyga [14:37] cjwatson, I just though of ubiquity after, so no, I doubt ubiquity debugging is needed [14:37] seb128, well, technically cjwatson ran into it with update-manager. He uploaded that one too. ;) [14:37]