/srv/irclogs.ubuntu.com/2012/06/14/#ubuntu-devel.txt

keesinfinity: eglibc ping :)00:02
infinitykees: "I'm not ignoring you, I've just been busy" pong.00:06
infinitykees: (I also have a few other things lined up for eglibc, so I'm going to make a day of it at some point)00:06
keesinfinity: cool; thanks :)00:16
=== shirgall is now known as Guest81642
infinityScottK: What's with the ksplosion of kthins moving to universe on component-mismatches?01:02
ScottKinfinity: I'd guess Kubuntu not driving stuff to Main landed.01:04
ScottKThat's in the plan.01:04
ScottKBut that's a guess.01:04
cjwatsonScottK: I haven't landed that yet.01:29
cjwatsonHm, it's a fair bit, but I'm not sure it's enough for that.01:30
micahgcjwatson: any chance components-mismatches suddenly got smart about versions?01:36
cjwatsonYou'd see it in lp:ubuntu-archive-tools if it had.01:37
infinitymicahg: "smart about versions"?01:42
micahginfinity: straw grasping due to low glucose :) (the basic premise is to drop it out of main if the version doesn't satisfy something, but it doesn't make much sense)01:43
infinityOh, hallelujah, the armel GCC build finally finished...01:48
infinityI wonder how that took 13 hours longer than armhf...01:48
ScottKinfinity: Then I'll go with KDE is half 4.8.3 and half 4.8.80 or 90 and stuff is confused.01:57
infinityScottK: Yeah, that's possible.  I'm certainly not knee-jerk demoting anything tonight.01:58
infinityI know some AAs are a bit more militant about just demoting everything on the list, but hopefully everyone will take pause at the size of the list and not do so. :P01:58
infinityCause it's annoying to have to promote half of it the next day...01:59
=== scott_ is now known as Guest46365
micahgBenC: did you test scilab on i386?02:19
BenCI did, but I don't think it rebuilt configure like it was supposed to02:19
micahgah, ok, I was waiting for the diff, but saw the failure first02:20
BenCscilab was FTBFS on everything !amd64 already, so it's def not a regression :)02:20
micahgright :), but that's the same thing that happened when the last person sync'd :)02:21
BenCI'll refix it02:21
micahgBenC: thanks02:21
* infinity fixes calligra...02:22
infinityMostly because it's annoying me that it's blowing up quantal_probs...02:22
=== dendro-afk is now known as dendrobates
=== ssweeny is now known as sweeny
=== sweeny is now known as ssweeny
BenCI wonder if anything else can brag about 3Gigs of installed size for it's build-deps03:00
* BenC tips his hat to sdcc03:00
StevenKBenC: Libreoffice? :-)03:05
mwhudsonthat did seem the obvious suggestion03:06
StevenKBuild-Depends: all of main. At once.03:06
BenCbyte of source to byte of build-dep, I suspect sdcc wins this one though :)03:07
=== dendrobates is now known as dendro-afk
=== jalcine is now known as Jacky
infinityBenC: Making build-indep only get run as a dependency of binary-indep means it all happens under (fake)root.03:45
infinityBenC: Not a huge issue, I suppose, since we use fakeroot and not real root, but not ideal.03:45
BenCinfinity: Hence the reason I said, "not ideal"03:45
BenCBut it was a toss up of "force the buildd's to install 3Gig of build-deps" or "generate docs as (fake)root on i386 only"03:46
BenCI may be biased in that I didn't want the ppc buildd's to install all those damn build-deps :)03:47
infinityThere's a theory some day that dpkg-buildpackage -B will eventually change to call "clean ; build-foo ; binary-foo", but that's going to require a critical mass of packages in the archive actually supporting separate build-{arch,indep} targets. :/03:47
infinitySince suddenly making half the world RC buggy is unpleasant.03:48
BenCI was under the impression that this was already the case…it's really odd to me that I don't remember this class of FTBFS being a major issue until now03:48
infinity-B has always done "build ; binary-arch"03:49
BenCAt least, all the packages I create have "build: build-arch build-indep" :)03:49
infinityAnd -b does "build ; binary"03:49
BenCAll these years, Build-Depends-Indep was just tease03:49
infinityThis class of FTBFS almost never shows up in Debian because arch:all packages are built on maintainer machines, so no one ever bothers to test if they fail when built in a pristine environment.03:50
BenCThat's the thing, this is causing failures when not building with arch: all as a target03:50
infinityOh, hah.03:50
BenCI would have thought it would show up in Debian too03:50
infinityYeah, that also is a uniquely Debian build failure. ;)03:50
infinityBecause, again, it will work for the maintainer.03:51
infinityAnd he'll ignore the buildds failing, cause hey, his works.03:51
BenCRight, so the maintainer will keep saying "but it's under build-indep"03:51
BenCDamn social problems03:51
infinityActually, hrm.  Debian may have switched.03:52
* infinity wonders if his pending dpkg merge will change this...03:52
* infinity sees a "debian/rules build-arch" in a Debian build log.03:52
BenCDoes Debian install Build-Depends-Indep on all builds?03:53
infinityBenC: If you're running into more of these, you might want to hold off for a bit.03:53
infinityBenC: No, BDI is never installed on Debian buildds (since none of them build arch:all)03:53
infinityBenC: But if you check the logs for sdcc on sid, they show a call to build-arch.03:53
BenCinfinity: Unfortunately, most of the ones I've seen are causing a slew of dep-wait and other FTBFS, so the cascade of fixing it does makes me impatient :)03:53
infinityBenC: So maybe this changed VERY recently in dpkd.03:53
infinitydpkg*03:54
infinityBenC: Well, I'm merging dpkg tomorrow.  Let me look right now to see if this behaviour will be changed by that.03:54
BenCOk03:54
micahg\o/ new dpkg will solve a few more depwaits :)03:54
BenCI don't know of any others right now, but if I see any, I'll note them for rebuild later03:55
infinity  * Update dpkg-buildpackage to use the "build-arch" (for -B) and03:55
infinity    "build-indep" (for -A) targets unless "make -qn" says that they do not03:55
infinity    exist. Closes: #22935703:55
infinityBenC: Yeah, looks like my merge will let you stop doing these fixes.03:55
BenCAh, that's great fix03:55
infinityI like the age of the bug that closed.03:56
infinityNot 5-digit, but still back a bit.03:56
BenC8 year old bugs...03:56
infinityHey, this is why I'm against auto-expiry of bugs.  "We'll get to it eventually..."03:57
BenCI may have still been in the Uploaders list back then03:58
* micahg still loves how powerpc is doing better than i386 ATM03:58
infinityGive me to the end of the week to resolve that oversight. :P03:59
micahga new dpkg and debhelper would probably tip the scales04:00
infinityIs our dh lagging too?04:00
infinityThat's a much easier merge.04:01
micahgyes, --extreme or something like that04:01
infinitydpkg is pain.04:01
BenCI dunno…if you can dislodge all the ppc dep-waits, I think I can keep up :)04:01
infinitymicahg: No, that's dpkg.04:01
infinitymicahg: That's just passed unfiltered to dpkg-deb.04:01
infinityBenC: If ross wasn't unhelpfully sitting at a yaboot prompt without a keyboard or serial console attached, PPC might be a bit happier. :/04:02
BenCNo wonder I keep getting "Build will start in 39182913 hours, you tool"04:03
micahginfinity: hrm, http://packages.debian.org/changelogs/pool/main/d/debhelper/current/changelog#version9.20120513, http://packages.debian.org/changelogs/pool/main/f/fonts-aoyagi-soseki/current/changelog, people seem to be doing this slightly backwards04:03
BenCinfinity: pay someone to walk over to it with a usb keyboard04:04
StevenKHah, USB keyboard on a Xserve04:04
BenCPlease tell me it doesn't use an ADB port04:05
micahghehe, ADB port, now I'm getting nostalgic04:05
infinitymicahg: Well, merging debhelper too won't hurt.04:05
infinitymicahg: And gets the default udeb compression for free.04:05
BenCshaweet, scilab built on something != amd6404:05
infinityBenC: Pretty sure there's no ADB bus on any G5 system. :P04:06
micahgBenC: awesome, now let's see if sylvestre takes the patch :)04:06
BenCccvjbsmt.s:285077: Error: operand out of range (0x0000000000008000 is not between 0xffffffffffff8000 and 0x0000000000007fff)04:34
BenCMy math may be a little rusty, but I suspect that error is incorrect04:34
infinityBenC: Heh.04:38
BenCAt the same time, I suspect half a million lines of assembly would confuse the best assembler04:38
BenCBug #101297605:22
ubottuLaunchpad bug 1012976 in spatialite (Ubuntu) "FTBFS: PowerPC build fails choking on half a million lines of assembly" [Undecided,New] https://launchpad.net/bugs/101297605:22
pittiGood morning05:24
pittislangasek: changelogs.u.c.> functionally that's mvo's, but out of disk is RT matter05:26
pittiyay for python3-ified aptdaemon!05:30
glatzormorning pitti and slangasek05:43
pittihey glatzor05:43
glatzorpitti, may I ask you about the status of the aptdaemon/packagekit plugins? They are already available for Python 3?05:44
pittiglatzor: I'm porting ubuntu-drivers-common as we speak05:44
pittiglatzor: and language-selector is also on my list today05:44
pittiglatzor: I don't know about the software-center plugin05:44
glatzorgreat news.05:44
pittido we have others?05:44
pittiglatzor: aptdaemon now landed, this blocked pretty much else on my list before :)05:45
glatzorI am not aware of any further plugins.05:45
glatzorpitti, I just wrote an email to slangasek that I am ok with an upload :)05:45
* glatzor seems to be late05:45
glatzorThanks for the upload slangasek05:48
pittiglatzor: argh, seems we missed some bits06:01
pitti/usr/share/aptdaemon/tests/fake-polkitd.py06:01
pitti#!/usr/bin/env python06:01
pittithat's causing test failures06:01
pittioh, I see that all scripts except gtk3-demo.py stil run with "env python" in trunk06:03
pittiglatzor: so I guess the package converts those?06:03
glatzorpitti, hm. but the fake-polkitd should still work if python 2 is installed. have you already remove python2 completely from your disk?06:03
pittiglatzor: it works fine in my normal system, but u-d-common shows ImportErrors when building in a pbuilder06:04
pittiglatzor: the pbuilder doesn't have python-dbus, only the python3-dbus build dep06:04
pitticuriously even the fake polkitd keeps all tests succeeding06:04
pittiit seems aptdaemon doesn't actually query polkit, or ignores if it's not there06:05
=== Zic is now known as Zic_
pittiso I think we can ignore that for now06:05
=== Zic_ is now known as Zic__
=== Zic__ is now known as Zic
glatzorpitti, I used the demo scripts to test the python 2 interaction since at the python 3 port release time update-manager, s-c and friends would still be python 2 based06:06
glatzorpitti, Hm. I will have a look at the policykit thing06:06
pittiglatzor: if it becomes a problem, I'll just add (temporarily) a python-dbus build dep06:07
glatzorpitti, without a working or always denying fake-polkitd the test suites hangs here06:10
pittilet's see how it behaves on the buildds, but it worked fine in my pbuilder06:11
pittiglatzor: so perhaps a workaround would be to start the fake polkit like Popen([sys.executable, 'fake-polkit.py', ...], ...) ?06:11
pittiin aptdaemon.test06:12
pittiso that it always runs with the same python version as your test06:12
slangasekpitti: yes, I was asking about the implementation because I think we should be garbage-collecting some of these changelogs... instead of letting them accumulate without limit06:13
glatzorpitti, I just replaced the shebang in trunk06:14
slangasekwhy would we need to keep changelogs around indefinitely?06:14
* slangasek waves to glatzor - you're welcome :)06:14
pittiglatzor: wouldn't that cause the opposite problem then?06:14
slangasekglatzor: and thank you for doing all the hard work on the port06:14
* pitti moves python3-xkit to main, to relieve u-d-common from its depwait06:15
pittislangasek: changelogs> indeed; they are still on LP for the historians06:15
pitticjwatson: I pushed your language-selector py3 branch to lp:~ubuntu-core-dev/ubuntu/quantal/language-selector/python06:19
pitticjwatson: so that we can work on it together06:19
micahgfun, colliding meta uploads :)06:25
pittimicahg: urgh, did you update it as well? sorry about that06:27
pittifun, I've never seen that happen before in 8 years06:27
micahgpitti: no, but slangasek did after you, I'm surprised how that worked06:28
pittiI uploaded 1.272, slangasek 1.27306:28
micahgright, but they're the exact same changelog06:28
pittiwith exactly the same changelog06:28
pittislangasek: so it seems we both had exactly the same idea at the same time? so it must be good!06:29
pitticjwatson: err, I mean lp:~ubuntu-core-dev/ubuntu/quantal/language-selector/python306:31
pitticjwatson: (i. e. the changed branch name in the blueprint work items is correct)06:31
pitticjwatson: now the test suite works with python3 (except test_package_lists_good, which has failed for years; but as this part, just like most of language-selector, is being deprecated, I don't bother much)06:44
dholbachgood morning06:53
pittiglatzor: when I run language-selector with Python 3, I get07:00
pittiTypeError: update() takes exactly 2 arguments (1 given)07:00
pittiError in function update07:00
pittiglatzor: is that something that rings a bell to you? it's not something I do in language-selector itself07:01
pitti/usr/lib/pyshared/python2.7/apt_pkg.so contains "Error in function", anyway07:01
pittiglatzor: nevermind; apparently apt.progress.base.OpProgress.update() now gets called with one argument sometimes (not in python2); I added support for this and pulse() the progress bar in that case07:16
glatzorpitti, sorry I was away07:16
glatzorpitti, right there is now an optional argument07:17
=== smb` is now known as smb
pitticjwatson: I tested PYTHONPATH=. python3 ./gnome-language-selector fairly well now, seems to work fine07:18
pitticjwatson: so I'll switch the whole thing to #! python3 and merge07:19
verwilsthm, precise has a 2-year old lvm2 package, i wonder why it hasn't been upgraded for the LTS07:36
pitticjwatson: uploaded l-s now; thanks for your porting work!07:52
pittignagh, dear debhelper, stop calling setup.py through "python" explicitly08:03
cjwatsonpitti: wow, that was quick, thanks08:05
cjwatsonpitti: debhelper needs to do that, surely08:05
pitticjwatson: yeah, it's nice to have a package that doesn't need millions of bytes-> str conversions for a change :)08:06
cjwatsonI mean, aside from its general lack of python3 support08:06
pitticjwatson: yeah, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597105 all over again08:06
ubottuDebian bug 597105 in debhelper "add support to build python3-* packages" [Wishlist,Open]08:06
pittiI did that for a number of other packages, I'm mostly just grumbling because I keep falling into that trap08:06
cjwatsonbut it needs to be called for each supported interpreter, and IIRC it needs to be called with python rather than python2.7 or #! lines come out wrong ...08:06
pitticjwatson: btw, you ignore jockey on the py3 sprint, right?08:12
cjwatsonpitti: Yeah08:14
cjwatsonMore didn't even consider it because there was so much else ;-)08:14
cjwatsonmvo: Thanks for the command-not-found merge.  Shall I roll a new Ubuntu package?  How do you pick version numbers, as setup.py seems to be out of date?08:18
cjwatsonmvo: And do you by any chance have an opinion on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656288?08:21
ubottuDebian bug 656288 in python3-apt "python3-apt: difficulties with non-UTF-8-encoded TagFiles" [Normal,Open]08:21
xnoxverwilst: we didn't get around to updating lvm2 in time. It is updated in quantal.08:21
pitticjwatson: so it seems this is really going well, great! the two biggest things that worry me are ubuntuone and system-config-printer08:21
cjwatson(Scroll to the end, I think)08:21
pittixnox: good morning08:21
xnoxpitti: that's for pushing u-d-c =)08:21
pittixnox: thanks for your work there; I mopped up the remaining bits, and uploaded now; I had a quick discussion with glatzor about the "import dbus" failure from the fake polkit, but it doesn't hurt for now08:22
xnoxpitti: yeap, I reread on irclogs.ubuntu.com ;-)08:23
seb128pitti, is it worth spending time porting system-config-printer if we plan to deprecate it?08:29
seb128pitti, well, we will still need the service, but the ui part might be not worth spending time on it08:29
pittiseb128: right, that's what I meant08:30
pittiwe at least need to port the bckend08:30
pittiseb128: it seems Fedora is going py3 as well, so maybe it even already happened; I don't know08:30
pittiI wouldn't worry about the frontend, and rather spend the time helping Lars with fixing the GNOME frontend enough08:31
seb128right08:31
seb128though I doubt Lars will have any time for that this cycle08:31
seb128but we will change before the next LTS for sure08:31
pittiwell, if we don't switch this cycle, we'd have to port the GUI to py3 as well, which seems like a waste? I thought the GUI was already very close08:33
pittiseb128: I thought GNOME upstream's printer panel would already talk to s-c-p, doesn't it?08:34
seb128pitti, it does08:34
pittinice08:34
mvocjwatson: I can do a new version but either way is fine, I had hoped that rookery is fixed so that we get updated command-not-found data for quantal with the new release too08:41
dokodidrocks, online?08:46
didrocksdoko: yes08:46
seb128doko, infinity: do you have an idea if bug #1007588 could be a toolchain issue? not sure what those @plt are, but the code didn't change since precise (out of being rebuilt with the new toolchain) and the segfaults don't happen when building with gcc-4.608:48
ubottuLaunchpad bug 1007588 in gnome-settings-daemon (Ubuntu) "[mouse]: gnome-settings-daemon SIGSEGV in gdk_device_manager_list_devices@plt()" [High,Confirmed] https://launchpad.net/bugs/100758808:48
=== tkamppeter_ is now known as tkamppeter
hrwhi09:01
hrwcan someone tell me how to specify two arches in apt sources.list for one repo? for one arch it is simple: "deb [arch=armel] http://repo" but tried "[arch=amd64,i386]" and it still tries to find armel there09:02
hrwok, [arch=amd64 arch=i386] looks like working09:06
hrwchrisccoulson: do you have plans to provide quantal packages for thunderbird-next ppa?09:10
cjwatsonmvo: I hadn't seen much sign of rapid movement on getting rookery fixed ...09:13
hrwnope, only solution is duplication of lines ;(09:31
hrwogra_: do you know why ddebs.ubuntu.com does not have armel/armhf ddebs for quantal?09:36
dokomvo, online?09:39
mvodoko: yes09:40
seb128doko, hey, did you see my ping before?10:03
seb128doko, should we just build gnome-settings-daemon with gcc-4.6?10:03
dokoseb128, no, didn't look yet10:04
seb128doko, let me know if,when you have some time to look at it, that's hitting quite some quantal users10:04
chrisccoulsonseb128, ooh, that bug looks interesting ;)10:04
seb128chrisccoulson, lol, you like toolchain issues right? ;-)10:04
chrisccoulsonlol10:04
chrisccoulson"like" is a bit of a strong word ;)10:05
seb128chrisccoulson, do you want to have a look to it?10:06
chrisccoulsonseb128, sure, i don't mind10:06
seb128chrisccoulson, thanks!10:06
=== MacSlow is now known as MacSlow|lunch
verwilstxnox, , i guess an upgrade of lvm2 will never be allowed in precise? :)10:59
xnoxverwilst: i have enquired about that and the conclusion is that no precise will stay at it's current revision as it's too high of a jump and we do not have sufficient regression testing in place to catch unforeseen problems. A backport on the other hand....11:04
Bluefoxicybuh.  Ejecting the kindle from Ubuntu doesn't make it drop out of USB drive mode and charge while in use11:04
xnoxverwilst: individual bugs, can and should be fixed/lumped together in an SRU11:04
BluefoxicyI think because it ejects /dev/sdc1 but not /dev/sdc?11:04
verwilstxnox, a backport of that one patch the redhat guy mentioned?11:05
Bluefoxicythat should be looked into11:05
Bluefoxicyif you hit 'eject' and nothing on that device is mounted after unmounting, eject the base device itself11:05
Bluefoxicy(I just manually ejected /dev/sdc, kindle data is /dev/sdc1; it worked)11:06
Bluefoxicybleh I'll file a bug after work.11:06
xnoxverwilst: the whole thing. Plus quntal is at .88, so it needs to be fixed in quantal. Debian is at .95 so it should/does affect debian as well.11:06
xnoxverwilst: .96 just got released.11:06
verwilsti guess quantal can just get an upgrade to .9611:07
xnoxBluefoxicy: unless you want to repartition the drive. or connected to the yellow always on port....11:07
Bluefoxicyyellow always on port?11:08
Bluefoxicyxnox:  this could be serious you know :P11:08
Bluefoxicywhat if you're using a (moron-developed) USB hard drive that expects a proper eject command to know to flush cache?11:09
* Bluefoxicy jumping jacks on tatami, then goes to work.11:10
Bluefoxicy(I'd imagine a well-designed external drive will flush cache as soon as nothing else is going on, and immediately park the heads awaiting power drop, rather than needing commands for all this)11:11
=== dendro-afk is now known as dendrobates
pittijibel: I so love the adt tests11:19
pittijibel: that upower regression detected an actual bug11:20
=== Guest34040 is now known as Zic
scarneiroexit11:29
scarneiroexit11:29
jibelpitti, Great. If only cloning VMs concurrently could be reliable. I'll spend some time on it tomorrow.11:36
Davieyjibel: How are you currently cloning ?11:42
Davieyjibel: if you have a consistent base image, and want lots of duplicates.. using qemu to create an image with a 'backing' image might be wise...11:43
jibelDaviey, with vm-clone from vm-tools which uses kpartx but sometimes it doesn't find the loopback devices11:44
Davieyjibel: qemu-img create -f qcow2 -b base.img test-runner.img .. might be what you want?11:45
jibelDaviey, yes but then I must change the config inside the VM hence the use of kpartx11:46
Davieyjibel: If you can add cloud-init to the image, you can use that 'stanalone' without a metadata service.. it's quite a gentlemanly way of injecting arbitrary code.11:47
Daviey(create an iso image, which is attached to the machine, and cloud-init reads from there)11:47
Davieyhttp://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/nocloud/README11:48
jibelDaviey, nice. That looks like a solution. I'll try it. Thanks!11:50
Davieysuper11:50
=== _salem is now known as salem_
ogra_@pilot in12:44
=== udevbot changed the topic of #ubuntu-devel to: 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: ogra_
=== MacSlow|lunch is now known as MacSlow
* dholbach hugs ogra_12:59
dholbachogra_, lots to choose from :)12:59
ogra_:)12:59
pittiseb128: I updated the test case on bug 984944, FYI; it's working for me here13:12
ubottuLaunchpad bug 984944 in apport (Ubuntu Precise) "Reject crashes that happen right after upgrade" [Medium,Fix committed] https://launchpad.net/bugs/98494413:12
seb128pitti, thanks, I will give it a try it a bit13:13
pittibut right now I only tested on quantal13:13
mterry@pilot in13:17
=== udevbot changed the topic of #ubuntu-devel to: 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: ogra_, mterry
* dholbach hugs mterry13:18
mterryogra_, ah hello!  You're piloting too?  In the interest of avoiding the ones you're looking at, should I look at the bottom or top of the sponsor report?13:18
mterrydholbach, morning (for me)!13:18
ogra_mterry, i started in the middle :)13:18
ogra_(bottom of yellow)13:18
ogra_planned to work upwards through it13:19
mterryogra_, heh, OK.  I'll do some of the newer ones at the bottom then13:19
cjwatsonjuliank: Do you have any thoughts on my latest patch sent to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656288 ?  I'd really like to unblock this.13:19
ubottuDebian bug 656288 in python3-apt "python3-apt: difficulties with non-UTF-8-encoded TagFiles" [Normal,Open]13:19
=== mterry is now known as rickspencer
=== rickspencer is now known as mterry
juliankcjwatson: I'll comment on that later. I have to go now.13:22
=== zyga is now known as zyga-afk
ScottKbryceh: It looks like xdiagnose is getting called to run in python3 now and 'bad' things happen.  See Bug #1013171 .13:52
ubottuLaunchpad bug 1013171 in xdiagnose (Ubuntu Quantal) "xdiagnose run in python3, but not ported" [Critical,Confirmed] https://launchpad.net/bugs/101317113:52
xnoxScottK: it has been ported.... during python jam monday->wednesday13:55
xnoxogra_: ^^^ bug 101317113:55
ubottuLaunchpad bug 1013171 in xdiagnose (Ubuntu Quantal) "xdiagnose run in python3, but not ported" [Critical,Confirmed] https://launchpad.net/bugs/101317113:55
ScottKxnox: Something's gone awry then because those are python print statements in that bug, not python3.13:55
ogra_xnox, oooh, thanks !13:55
ScottKxnox: Actually it looks like the update isn't uploaded as the current package is weeks old13:56
ogra_thats not the ported version13:56
* ScottK isn't sure why it's getting run in python3, but it is.13:56
ogra_(note that part of the porting is to wrap brackets around all print stanzas)13:57
ScottKMultiple dupes too.13:57
ScottKYep.13:57
ogra_i'm pretty sure the ported code wasnt merged yet13:58
xnoxScottK: is update-manager calling that or aptdaemon or something like that?13:58
ScottKNo idea.13:58
* ScottK hasn't been following it until his ubuntu bug mailbox started filling up this morning.13:59
* ogra_ added the branch to the bug and the bug to the changelog ... should be fixed once the merge is uploaded14:04
ogra_ScottK, ^^^14:04
ScottKogra_: Thanks.  It'd be good to get it done since it's hitting multiple people.14:05
ogra_yeap, bryceh knows about the branch, i guess he will merge and upload asap14:05
=== manjo` is now known as manjo
ogra_ogasawara, hmm, just looking at bug 183076 ... seems your fix is upstream since ages and also in all supported releases, how about closing the bug so it drops of the patches list :)14:25
ubottuLaunchpad bug 183076 in tsclient (Ubuntu) ""enable bitmap caching" option in tsclient doesn't work properly" [Undecided,Confirmed] https://launchpad.net/bugs/18307614:25
ogasawarawhoa, 200814:26
ogra_:)14:26
ogasawaraogasawara: I'll close it14:26
ogasawarabah14:26
ogasawaraogra_: ^^14:27
ogra_great14:27
* ogra_ giggles14:27
ogasawaraogra_: now I fully understand how I steal your pings14:27
ogra_hehe14:27
cjwatsonScottK,ogra_,pitti: Doesn't the presence of /usr/share/python3/runtime.d/apport.rtupdate suddenly mean that all apport hooks are required to be Python 3-compatible?14:35
cjwatsonxdiagnose is very far from unique.14:36
ScottKThat sounds reasonble.14:36
pitticjwatson: by and large, yes14:36
ogra_oh, indeed14:36
pittias the GUI is now running as py314:36
pittis/as/with/14:36
cjwatsonSo isn't this going to require about a bazillion Breaks?14:36
hyperairRAOF: ping14:37
cjwatsonI mean, I understand it, but it'll all need to be exhaustively handled14:37
xnoxemergency porting all apport hooks to python3?14:37
seb128cjwatson, pitti: change the hooks dir to avoid the breaks?14:37
seb128it will just reduce the debug infos for a bit14:37
seb128but at least it will not trigger reports14:37
seb128like version it "3" or something?14:38
pittiI don't like changing the hooks dir; it should not be rocket science to fix the few hooks that we have that aren't already workign with py3 anyway to work with both 2 and 314:38
cjwatsonFew?14:39
cjwatsonhttp://paste.ubuntu.com/1040874/14:39
cjwatsonA lot of those are symlinks to source_xorg, I guess14:39
seb128yes, I was going to say14:40
cjwatsonBut I do think we'll need the Breaks, otherwise we'll get mid-upgrade reports14:40
cjwatsonAnd possibly crashes14:40
pittiright, most of them are symlinks to source_xorg.py; that's the primary one that we need to fix14:40
pitticrashes/14:40
ogra_that is fixed14:40
pitti?14:40
ogra_i ported xdiagnose the last days14:41
cjwatsonThere're others there though, network-manager, udisks, ...14:41
cjwatsonogra_: xdiagnose != xorg14:41
* cjwatson fixes ogra_'s lexer to go past the first character :-)14:41
pittixdiagnose: /usr/share/apport/package-hooks/source_xorg.py14:41
pittiI guess ogra meant that?14:41
ogra_right :)14:41
pittipython3 /usr/share/apport/package-hooks/source_xorg.py fails, though (print statement)14:42
ogra_i fought with that file enough the last days ;)14:42
ogra_pitti, because my port isnt merged yet14:42
pittiah14:42
ogra_i linked it to the bug14:42
ogra_xdialog just needs the merge and an upload and will be fixed, though i think cjwatson is right being worried about other hooks, we should make a lot of noise to get people moving imho14:43
cjwatsonHuh14:43
cjwatsonogra_: Fair enough, sorry, failed to run dpkg -S14:44
dholbachcjwatson, if you could publish the fix that might help in a lot of other cases :-P14:44
* cjwatson fixes his own parser to not suck14:44
cjwatsonThere are also some that won't show up in a current grep but that were fixed after precise14:45
cjwatsonFor example source_grub2.py is only py3-compatible in quantal, not precise14:45
ogra_well, but in precise apport doesnt default to py3, does it ?14:46
pittiITHM on upgrades14:46
ogra_ah, k14:46
pittii. e. if you upgrade to quantal, and apport gets upgraded before, say, grub214:46
pittithen package install failures of grub2 woudln't have the infos from teh package hook14:46
seb128should we SRU python3 compat fixes for hooks for packages we upload to precise for other reasons?14:47
pittifortunately the hook info does not seem all that relevant for package installation failures in most cases14:47
seb128i.e I wouldn't do a SRU only to fix a hook to be python3 compatible14:47
pittimost of them are for manual bug reports, and some for crashes14:47
seb128but we can probably include those in uploads14:47
pittigrub2 might be the very exception to this, of course14:48
=== zyga-afk is now known as zyga
=== dendrobates is now known as dendro-afk
pittiudisks hook fix uploaded, udisks2 hook fix committed to git15:11
pitticjwatson, seb128 ^ FYI15:11
seb128pitti, thanks15:12
pittichrisccoulson: can you please fix python3 /usr/share/apport/package-hooks/source_firefox.py ?15:13
cjwatsonpitti: Maybe apport should just catch SyntaxError in hooks and downgrade that to some kind of warning.15:14
pitticjwatson: apport itself never crashes on bad hooks15:15
cjwatsonOh, but this bug is about running py3compile over the source directory, so that's not applicable.15:15
pittiit just shows the exception on stderr for debugging and goes on15:15
cjwatsonOK.15:15
pittiit's external code, I assume the worst :)15:15
xnoxogra_: thanks for sponsorship! =)15:17
* ogra_ tips his pilot cap 15:17
xnoxogra_: you didn't mark the whole proposal as merged, but I did now =)15:18
ogra_oh, sorry15:18
pittichrisccoulson: http://paste.ubuntu.com/1040950/ shoudl be the bulk of the fixes, but I'm not quite sure how your ExtensionINIParserIter parser works (it fails there)15:18
chrisccoulsonpitti, i'll have a look in a bit. and this has changed quite a lot recently as well (but it's not in the archive yet)15:19
chrisccoulsonpitti, i also need to maintain compatibility with the current python :)15:19
pittichrisccoulson: yes, my pastebin patch works with both15:20
chrisccoulsonah, ok. thanks!15:20
chrisccoulsoni'll apply it in a bit :)15:20
pittichrisccoulson: thanks; NB that it's not sufficient15:20
pittichrisccoulson: please use http://paste.ubuntu.com/1040952/ rather, debug output looks nicer with that15:21
chrisccoulsonpitti, sure, thanks15:21
zulbdmurray: ping15:27
bdmurrayzul: hi, done sprinting and looking at the queue now15:29
zulbdmurray: thanks15:29
stokachustgraber: hi, could you take a look at http://pad.lv/951343 for possible sponsorship15:40
ubottuLaunchpad bug 951343 in nss-pam-ldapd (Ubuntu Precise) "authentication fails silently with long pam_authz_search filter" [Medium,In progress]15:40
hallynlool: slangasek: hey, I want to test whether qemu-common from a newly merged (not yet pushed) qemu-kvm-1.1 would break qemu-linaro.  is there a testsuite i can use?15:50
slangasekhallyn: not to my knowledge15:51
xnoxslangasek: I remember you mention that lvm .88  was the 'recommended' version of lvm to use15:52
xnoxdebian is now on .95, and upstream released .9615:52
slangasekxnox: at the time, .88 was /a/ version that upstream had blessed for use; but things have moved on since then15:53
hallynslangasek: is there some small .img i can wget and use under qemu-arm as a test?15:53
xnoxare there stability criteria for lvm.15:53
xnoxslangasek: hmm. ok15:53
dobeystgraber, pitti: want to moderate my reply mail to technical-board through? :)15:53
slangasekhallyn: I don't know one offhand, sorry15:53
hallynslangasek: ok, thanks.15:53
slangasekhallyn: I mean, between Linaro and Ubuntu there should be several... but if you're meaning to test qemu-system, you need an image for a supported subarch, which is probably only beagle at this point15:54
hallynperhaps the thing to do is drop by #linaro and ask if anyone cares to test with a version in my ppa :)15:55
hallynthanks15:55
stgraberdobey: don't have moderation rights, sorry.16:09
stgrabercjwatson: ^16:09
cjwatsonuh, why not16:10
dobeyoh. thanks16:10
cjwatsonstgraber: you have /msg16:10
loolhallyn: I dont know a testsuite either; you can create QEMU images from Linaro images with linaro-image-tools16:13
stgraberdobey: done16:13
hallynstgraber: all of the removal of apparmor policies for lxc was meant to NOT be done in lxc.postrm anymore right?16:14
hallynlool: ok will try, thanks (saw a few urls describing that)16:15
alexbligh1What would be the easiest way of automatically building Lucid & Precise installation media with the security updates already applied?16:32
alexbligh1(specifically amd64 server)16:33
hallynlool: seemed to boot up fine.  Terminal worked.  Terminal on vnc connection didn't seem to accept input, but mirrored the other output.  (don't know if that's normal)16:35
ogra_@pilot out16:37
=== udevbot changed the topic of #ubuntu-devel to: 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: mterry
SpamapSHrm.. shouldn't we have an 'update-vcs' the same way we have 'update-maintainer' ?16:48
ScottKFirst we should have a policy decision on if we want to replace Debian VCS info or just add Ubuntu info too.16:51
SpamapSScottK: right, like the XFOO-Original-Maintainer16:52
ScottKYes.16:52
SpamapShaving screwed up the apport upload the other day16:52
SpamapSI want to make sure UDD and Vcs-* play nice :-P16:52
cjwatsonScottK: I thought we had a policy decision on that years ago.16:52
* cjwatson hunts.16:52
ScottKDunno?16:53
cjwatsonThread starting https://lists.ubuntu.com/archives/ubuntu-devel/2007-March/023332.html16:53
cjwatsonWhich agreed on XS-Debian-Vcs-*16:54
ScottKOK.16:54
ScottKThat's about two months after I started doing Ubuntu development, so no wonder I don't remember.16:54
SpamapSslangasek: Hey I'm going to fix bug 794082 and do the cron merge (you are TIL) ok?16:55
ubottuLaunchpad bug 794082 in cron (Ubuntu) "cron ignores /etc/default/cron" [Undecided,Confirmed] https://launchpad.net/bugs/79408216:55
xnoxcjwatson: does the archive consistently override that? or is it manual job?16:57
xnoxcjwatson: update-maintainer should probably do that, unless it points to launchpad with *ubuntu* somewhere in the url16:57
cjwatsonxnox: Binary packages are consistently overridden.  Sources are only overridden if we've changed them.16:59
cjwatson(XSBC-Original-Maintainer, that is.16:59
cjwatson)16:59
cjwatsonWe don't override Vcs-* at all at the moment.  I'm not clear whether we should or could.17:00
xnoxhmmm =/17:00
cjwatsonNot actually massively wild about more hacks to override bits of Sources, TBH17:00
cjwatsonIf we don't have to17:00
xnox=)17:00
xnoxyeah, you'd think that you could do a blancket lp:ubuntu/package..... if all of them were realibly up to date, and used by all teams17:01
* xnox grumbles something unintelligent17:01
SpamapScjwatson: the only reason I think we might want to is that its now impossible to actually know where the Vcs is in Ubuntu... one must check Vcs-*, and lp:ubuntu/foo17:02
ScottKSpamapS: If there's an Ubuntu Vcs-* then you know.17:12
SpamapSIt is inferrable..17:13
SpamapSbut its damn unclear17:13
SpamapSI'm > 2 years into UDD and I only just now learned that some teams still use distinct Vcs branches. Up until now, I had not encountered that.17:13
ScottKI'm > 2 years into ignoring UDD and I can't imagine how you didn't know that.17:18
SpamapSBasically I don't think any server packages use it17:20
SpamapSand it seems very few foundational packages do either17:20
SpamapSmeanwhile, I started with Ubuntu dev with UDD17:20
SpamapSso, I always start with 'bzr branch ubuntu:..'17:20
SpamapSnever debcheckout17:20
SpamapSnever apt-get source17:20
SpamapSunless the branch is brorked17:20
dobeythanks stan17:22
dobeyerr17:22
dobeystgraber: ^^ thanks17:22
seb128SpamapS, I would say that most packages which are actively maintained are not using UDD in Ubuntu...17:23
smoserseb128, thats an interesting thought. i have had difference experience.17:24
smoserthe only times i don't use it are when the branches are borked (which, unfortunately, seems too often).17:24
seb128smoser, well none of the desktop packages are maintained in UDD17:24
seb128smoser, I'm guessing from ScottK's comment that kubuntu is not using UDD either17:25
ScottKNo.17:25
ScottKWe have our own /debian only branches.17:25
xnoxseb128: not UDD but lp:~ubuntu-desktop-team/package/ubuntu ?17:26
xnoxseb128: not UDD but lp:~ubuntu-desktop-team/package/quantal?17:26
SpamapSRight, so the desktop side of the house, which I think has a lot more Ubuntu delta than server side, is rejecting UDD17:26
seb128xnox, yes, debian only vcses17:26
seb128xnox, lp:~ubuntu-desktop/source/ubuntu17:26
xnoxyeah, so with bzr and correct Vcs-* headers17:26
seb128yes17:26
xnoxnot with apt-get source17:26
SpamapSIts something that needs to be really clear in the UDD manuals17:26
seb128but with debian only vcs-es17:26
SpamapS"This is not a given"17:26
seb128yeah, that's creating lot of confusions for contributors :-(17:27
* xnox somehow has a notion that UDD is bzr regardless of which branch it actually is. As ~ubuntu-desktop predates UDD package importer.17:27
ScottKPersonally, I think that UDD is great just by virtue of the ubuntu: branch getting created/updated for each upload much of the inherent value is provided without me actually using it.17:27
seb128xnox, well, our vcs-es are not full source17:27
SpamapSxnox: no, UDD is lp:ubuntu/17:27
seb128xnox, so they don't really qualify for an UDD like workflow17:28
ScottKThat means when I need to go understand when something was done, I've got the history to figure it out.17:28
xnoxat one point it was ment to point UDD to ~team branches, for packages that do that. Not sure why that didn't happen for long established branches, like on the desktop17:28
ScottKUDD branches are full source.17:28
ScottKubuntu-desktop and kubuntu branches are /debian only.17:28
* xnox would rather have inconsistent checkouts (/debian only and/or full), but always have consistent locations e.g. lp:ubuntu/package17:29
SpamapSxnox: +1 from me17:29
ScottKCan't.17:29
xnoxeven if lp:ubuntu/package resolves is a symlink to ~ubuntu-desktop17:29
SpamapSthe full source bit seems to be the part that frustrates most people17:29
ScottKThe UDD branches have to be able to represent changes anywhere in the package.17:29
seb128what drives me crazy with UDD is that every time I try to get a source it's outdated17:30
xnoxScottK: I'm sure it was possible to 'bless' and designate branches as "official" at one point.17:30
Davieyso i understand that if a team maintains a full source bzr branch, the UDD branch can be re-pointed.17:30
seb128the importer keeps failing for desktop packages17:30
SpamapSseb128: thats been addressed quite a bit17:30
DavieySpamapS: *every* time?17:30
Davieyerr seb12817:30
seb128SpamapS, we got 3 people asking why lp:ubuntu/source is outdated this month17:30
ScottKAlso, now that Kubuntu is going to Universe, it would drive me nuts to have some random upload overwrite anything staged in the branch.17:30
seb128SpamapS, i.e the gtk import is outdated still17:30
xnoxseb128: for gnome stuff it is due to .xz tarballs which are failing to import, due to out of date OS of the package-import machine. This is being worked on.17:30
DavieyScottK: well, at least you get a auto generated MP to cover the staged stuff17:31
xnoxseb128: more info on ubuntu-distributed-devel mailing list17:31
ScottKDaviey: That's a regression from not having the changes stepped on at all.17:31
ScottKxnox: That'll affect KDE too.17:31
ScottK(note that no one noticed)17:31
SpamapSseb128: right, caused by pristine-tar issues17:31
* xnox had no clue that KDE is doing .xz tarballs......17:31
seb128xnox, thanks for the info, but well that's the sort of problem which keeps us away from using UDD17:31
DavieyScottK: well it's because we are in the middle ground of not having build-from-bzr and dput.. I can't see how you can keep everyone happy17:32
seb128xnox, I'm not interested in trade a well working efficient workflow for a "known broken but being worked" one, we will reconsider the days things are solid17:32
xnoxseb128: please comment on the udd mailing list. it's being worked on. as it blocks a lot of stuff in e.g. foundations team.17:32
ScottKseb128: +117:32
SpamapSseb128: I agree with you actually. I'd like for UDD to adapt to that reality, rather than keep fighting against it17:32
* xnox runs his own instance of package import to get mdadm branches for example17:33
ScottKxnox: I filed bugs on UDD tools two years ago that haven't been addressed.  Why should I invest more time in it now?17:33
slangasekSpamapS: no objections to the merge, but why fix bug #794082?17:33
ubottuLaunchpad bug 794082 in cron (Ubuntu) "cron ignores /etc/default/cron" [Undecided,Confirmed] https://launchpad.net/bugs/79408217:33
Davieyseb128: right, by that logic.. you don't want any people testing Quantal pre-release?17:33
SpamapSslangasek: because its broken?17:33
seb128Daviey, quantal is supposed to be usable every day17:33
ScottKDaviey: No, by that logic I don't want me testing quantal now and I'm not.17:33
SpamapSslangasek: and, as yet, we have not come up with a decent way to transition from /etc/default/* to env statements in upstar tjobs17:33
seb128Daviey, UDD is far from usable every day17:33
Davieyseb128: except the days it is not, right?17:34
slangasekSpamapS: but /etc/default is lousy and shouldn't be encouraged - given that this hasn't been usable for two LTS cycles now, why re-insert it now?17:34
seb128Daviey, well it's not we fix it in the hour or revert17:34
seb128Daviey, the day UDD will be issues we report in the hour I might consider using it17:34
seb128doh, can't type17:34
SpamapSslangasek: because hardy is going away soon? ;)17:34
seb128the day UDD will fix*17:34
DavieyI actually cannot criticise the response time on issues i have escalated to the people working on it.17:35
SpamapSslangasek: we agree, but we don't have a migration path.17:35
seb128Daviey, you maybe know who to poke to get your issues sorted ;-)17:35
xnoxseb128: tranlation fail of "seb128> Daviey, the day UDD will be issues we report in the hour I might consider using it" can you rephrase?17:35
slangasekSpamapS: right; but just re-adding /etc/default handling everywhere will regress boot speed17:35
seb128xnox, <seb128> the day UDD will fix*17:35
xnoxseb128: gotcha17:35
SpamapSslangasek: I don't worry too much about things that start on runlevel 2 affecting boot speed17:36
Davieyseb128: right, and i know who to poke to get desktop issues fixed.. because i interface with them :)17:36
seb128xnox, like if had a place to say "can we get gtk import fix" and have it fixed in a timeline which doesn't block me for a week I would sign on maybe17:36
SpamapSslangasek: perhaps that is misguided?17:36
slangasekSpamapS: well we certainly do17:36
ScottKFundamentally, I don't know what problem I'm having that switching to UDD would solve.17:36
infinityScottK: Honestly, all it seems to do for me is create problems.17:36
seb128xnox, but maybe I would not, because once the reliability issues are fixed we still run into the source v3, full source, quilt mess issues17:37
Davieyseb128: who did you speak to about the xz issue of imports?17:37
infinity(I appreciate the ultimate goal of perhaps building from bzr, it's the interim steps that hurt)17:37
Davieyseb128: have you been following the work on v3/quilt issues?17:37
xnoxDaviey: xz issues are being discussed on the ubuntu-distritubuted-devel mailing list17:38
seb128Daviey, nobody and no, I've an efficient, established, working workflow and work to get done which I prefer to spend on the content rather than on the tools17:38
xnoxDaviey: seb128 *just* found out about the cause.17:38
MFeni'm using debhelper (dh) in my local custom package. i want to customize the source package, so i've got debian/source/format 3.0 (custom) and debian/source/options --target-format="3.0 (native)"17:38
MFenit errors out, it says..17:38
MFendpkg-source: error: can't build with source format '3.0 (custom)': no files indicated on command line17:38
cjwatsonMFen: You've misunderstood "3.0 (custom)".  It's not what you want.17:38
MFenwhere does that file list.. go?17:38
Davieyseb128: right, my Dapper desktop works great... I'll stick with that.17:38
seb128Daviey, I've been going to the UDD sessions at each UDS and explaining there why we don't use UDD though ;-)17:38
xnoxMFen: use 3.0 (quilt).17:39
cjwatsonMFen: Just put "3.0 (native)" in debian/source/format and drop that --target-format thing.17:39
seb128Daviey, oh, come on, that's nothing to compare17:39
cjwatsonOr "3.0 (quilt)" if you have a separate upstream tarball.17:39
ScottKDaviey: Also, I do a lot of work on Debian and so using a common toolset is a major feature for me.17:39
MFeni don't. i *am* upstream, i just want to pass in a list of files from hg manifest17:39
SpamapSslangasek: I feel that it is pretty lousy of us to just break peoples systems (even if we have 2 LTS's that are broken, its still lousy) and not give them a way to fix it17:39
seb128Daviey, it's like saying I should use dpatch instead of quilt in my packages, why would that be a strategic thing17:39
cjwatsonMFen: OK, so if you don't have a separate tarball, just use 3.0 (native) in debian/source/format.17:40
seb128Daviey, it's just tooling, we use whatever let us do the job best17:40
Davieyseb128: I'm simply suggesting that putting yourself in a little bit of pain, helps the process develop.. Otherwise, progression is really slow.  I know mbp was able to solve many issues, based on user feedback.17:40
MFencjwatson: i don't want all the files in this directory though.17:40
MFenare you saying i need to manually generate a tarball first, and then there's a source format that just lets me use that tarball?17:40
cjwatsonMFen: Then build yourself a tarball and use 3.0 (quilt).17:40
cjwatsonThat's what most normal upstreams do.17:40
seb128Daviey, the issues we have are known for a long time and don't need use to go through extra pain17:40
SpamapSslangasek: and the google guys were pretty mad about us suggesting that we can just have them keep all those settings in /etc/init/*.conf because that is impossible for them to resolve on package upgrade..17:40
seb128Daviey, like we have been converting a few packages to UDD for testing and gave the feedback, the situation didn't change in 3 cycles17:41
ScottKDaviey: I gave it a good try, gave feedback and filed bugs.  That was two years ago and not much has changed.  Doing the same thing again is not a priority.17:41
SpamapSslangasek: either way, I don't have time to implement a /etc/default/* converter ..17:41
* xnox uses UDD to do debdiffs/NMU's into debian17:41
cjwatsonSpamapS: /etc/init/*.override exists17:41
seb128Daviey, I go at the UDD session at each UDS and they admit UDD is just not having lot of resources allocated17:41
slangasekSpamapS: a) they can put it in /etc/init/*.override instead; b) /etc/default/cron is also a conffile so I don't see any reason to believe that's easier to resolve on upgrade than /etc/init/cron.conf, which should change rarely if ever17:41
seb128Daviey, they don't lack feedback17:41
SpamapSslangasek: /etc/init/cron.conf is code, and so they're not as comfortable using --force-confold17:42
cjwatsonMFen: the stuff about "arbitrary files" in dpkg-source(1) for 3.0 (custom) is talking about something a bit different; it's basically for people who are doing enormously arcane source package format development.  Basically, nobody who isn't developing dpkg itself needs it.17:43
slangasek"code" wut17:43
SpamapScjwatson: aye, but we are not converting things into .override17:43
slangasekSpamapS: the only code there is 'exec cron'17:43
slangasekindeed, /etc/init/cron.conf is a stellar example of a declarative job17:43
SpamapSexcept it would break if you apt-get remove cron17:43
MFencjwatson: gotcha. ok, so the quilt documentation is far from clear.. where do i put that tarball?17:44
xnoxMFen: ../myapp_1.3.orig.tar.bz217:45
MFenhmm. maybe it's just the missing version that's the problem17:45
slangasekSpamapS: FSVO "break"17:45
SpamapSslangasek: emit an error?17:46
SpamapSslangasek: Maybe we don't care?17:46
xnoxMFen: what version control system do you use?17:46
MFenxnox: mercurial17:46
cjwatsonMFen: you must have a version, yes.17:46
slangasekSpamapS: I don't care enough about the emitted error to go making /etc/init/cron.conf ugly17:47
MFeni'm still having issues with this. now i have the right filename, but it's spewing errors about other files that are in the directory. e.g.17:47
MFendpkg-source: error: cannot represent change to m11/util.pyc: binary file contents changed17:47
cjwatsonand it must match the bit before "-" in the head version in debian/changelog17:47
MFen(this is a file in the source directory but not in the source tarball)17:47
slangasekSpamapS: nor do I care enough about upgrade support for /etc/default/cron to make the boot slower for all users17:47
MFenhow do i make it stfu about that17:47
cjwatsonyou should remove .pyc files on clean; dh will do that for you17:47
MFenthe whole point is not to do that. there are mountains of files in here that i do not want considered in the source tarball17:47
MFenremoving pyc files is one thing, removing tons of demo directories and data directories and config files is another17:48
cjwatsonI think you're missing the point somewhere here ...17:48
cjwatsonget your source tarball right first, then unpack it somewhere else and do the packaging there17:48
cjwatsonthe packaging must clean up after itself.  that's unrelated to what's in your source directory, because the packaging should never see that17:48
MFenthat seems like a waste of time. i don't even *want* a source tarball, i will never use it because we don't build our package that way. i'm only doing this so it's not so enormous, because debuild insists on building it anyway17:49
cjwatsonif dpkg-source is seeing that you're doing something wrong17:49
cjwatsonyou can use -I to exclude things from the source tarball with 3.0 (native)17:49
cjwatsonif you want to do it that way17:49
Davieynative, generally, makes babies cry.17:50
cjwatsonnot always, and let's not be dogmatic about this17:50
SpamapSslangasek: ok, so we should mark that bug Won't Fix ;)17:50
slangasekSpamapS: that's my preference, yes17:50
SpamapSslangasek: but I do feel that this is pretty crappy still. Users with customized /etc/default/* are getting screwed.17:50
cjwatsonyou could even put tar-ignore = <stuff> in debian/source/options (the equivalent of -I)17:50
cjwatsonhowever you should still make sure to build the package separately otherwise you might well find that you're accidentally shipping incomplete source17:51
slangasekSpamapS: users with customized /etc/default get a one-time upgrade issue to deal with... when upgrading to lucid17:51
MFencjwatson: i've been trying to avoid that because there will be many patterns i have to add to that. i was hoping for a whitelist, not a blacklist17:51
cjwatsonYou can't have one, sorry17:51
SpamapSslangasek: *if* its obvious that it is broken17:51
MFenalthough maybe what i really want is to blacklist everything. just give me an empty source package17:51
cjwatsonWhy build a source package at all if you're going to do that?  Just use debuild -b17:51
SpamapSslangasek: if they've just raised log priority .. they may not realize for weeks or months that they've lost logs.17:52
MFenwon't that confuse apt, and reprepro if i don't have one?17:52
cjwatsonIt won't confuse apt.  I can't speak for your archive.17:52
slangasekSpamapS: sure, entirely possible - but I don't see why we should be making the boot slower two LTS cycles *later* to try to patch over this when we shipped with that issue for this long17:52
SpamapSslangasek: I'm not saying this is super urgent crazy important. But I really don't like that we're sweeping this under the rug. :-/17:52
cjwatsonOr the policies imposed by your archive administrators, if you don't run it.17:53
slangasekSpamapS: maybe a release note is better?17:53
MFenwell, we don't ship source at all. (properly speaking, we don't ship any of this, it's for internal servers)17:53
cjwatsonGiven that this is the primary Ubuntu development channel, I can't recommend shipping packages without source, but perhaps this is something local.17:53
SpamapSslangasek: Or some priority for something to convert them all to env statements in override files.17:53
cjwatsonDon't see why you need a source package then.  Configure your archive to accept binary-only uploads17:53
cjwatsonAnd use debuild -b17:53
MFencjwatson: i like that idea. thanks, i'll work on that17:54
SpamapSslangasek: but meh, my time for this issue is officially used up.17:54
slangasekSpamapS: right, I wouldn't object to a standard-ish tool to convert /etc/default/foo to foo.override... I think we've discussed this explicitly in the past... but it's not anywhere near the top of the priority list17:55
SpamapSslangasek: one thing.. we should remove the file from the package17:57
SpamapSslangasek: it would be much more clear that way17:57
juliankcjwatson: Your patch looks OK I'd say. I'd like to take a final look at it tomorrow, and then merge it. Currently, I need to do university stuff.18:00
SpamapSslangasek: actually even better, I'll install a "# This file is deprecated please edit /etc/init/cron.conf or /etc/init/cron.override directly'"18:00
cjwatsonjuliank: Great, thanks18:01
juliankcjwatson: Upload of the new release to unstable is planned for next Thursday.18:02
juliank(As we have next Thursday planned due to translation updates)18:03
=== yofel_ is now known as yofel
SpamapSslangasek: this might even be a change worth SRU'ing back to lucid, so late hardy upgraders will get the notification that the conffile has changed18:05
cjwatsonSounds good, I think.  I just don't want the python3-debian work to get caught up in a freeze.18:05
mterry@pilot out18:19
=== udevbot changed the topic of #ubuntu-devel to: 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:
slangasekSpamapS: dropping /etc/default/cron> oh indeed, very good point19:03
SpamapSslangasek: uploaded a "This is deprecated" version19:05
slangasekSpamapS: cheers19:06
brycehogra_, if you're still around, see the merge proposal; branch is failing to build19:30
=== BenC__ is now known as BenC
mterrympt, the SoftwareUpdates spec defines "uninstallable updates" as updates that would remove ubuntu-desktop.  What about updates that would remove some other package?  There is no UI for presenting such updates (and I think the current U-M handles that by pointing users at a release upgrade dialog)20:57
BenCinfinity: any way I can get scilab to stop being bumped on the ppc buildd?22:09
StevenKBenC: bumped?22:10
BenCIt keeps getting pushed back while other package builds get higher priority it seems22:10
StevenKBenC: Ah, I can rescore it for you, if you wish.22:10
BenCYes, please22:10
StevenKBenC: Link me the build?22:10
BenCStevenK: https://launchpad.net/ubuntu/+source/scilab/5.3.3-10ubuntu2/+build/357441222:11
BenCThanks22:11
BenCI have a few other FTBFS to kick off once that's done, and it's been in queue since last night :)22:11
StevenKBenC: sulfur just picked it up22:12
=== salem_ is now known as _salem
RAOFhyperair: pong.22:40
infinityBenC: Queue jumper. :P22:41
BenCinfinity: queues go in order…that sucker was on a negative timeline22:43
infinityBenC: It's in universe and people kept uploading stuff in main.22:43
BenCDamn core-devs and their main packages22:44
BenCDear thunderbird…welcome back to powerpc22:53
BenCAnd with that, I've gotten rid of all the FTBFS in main/powerpc22:53
BenCDamn you firefox22:54
micahgBenC: please tell me you didn't upload thunderbird22:54
BenCNope, but I need someone to do it22:54
BenC…if not me22:54
micahgBenC: yeah, ask chrisccoulson how he wants it, it can go in with the next beta22:54
micahgunfortunately, it's a monstrosity22:55
BenCFirefox will need the same fix22:55
micahgyeah22:55
BenCDoes he handle that too?22:55
micahgyep22:55
* micahg would think merge proposal against lp:firefox/beta22:55
micahgreally should have one for lp:firefox as well ideally22:55
* micahg wonders if it was fixed for 1522:56
* micahg will be happy if we get powerpc back in the stable releases for 1422:57
* infinity is trying to decide how deeply he cares about mozilla.org stuff compiling for incorrect CPU targets on armel.22:57
infinityWell, or failing to.22:58
infinityI'm sure I'll care at some point.22:58
BenCGive it a beer or two22:58
infinityCould take a few litres of gin.22:59
infinityGHC seems okay locally, at least.  Just needed a hard rebootstrap, since it sort of explodes upon trying to compile itself.23:00
infinityNot the brightest compiler on the tree.23:00
BenCGHC on ppc?23:00
infinityarmel.23:00
infinityNot EVERYTHING is about you. :P23:01
BenCI was trying earlier (with no success) to re-enable ghci on powerpc23:01
BenChehe23:01
infinityGHC on PPC is fine.  Well, except for ghci.23:01
infinityNo ghci on ARM either.23:01
infinityUpstream doesn't much care.23:01
BenCIt's causing a lot of FTBFS and dep-waits23:01
micahginfinity: hrm?  is something else broke?23:01
infinityAnd it's not trivial.23:01
infinityBenC: Yeah, ghci just plain isn't support on non-primary arches upstream.23:01
BenCIt's at least not segfaulting on innovation like it was in Jan23:01
BenC*invocation23:02
infinityBenC: That may be some failures you'll just have to live with, unless you have a lot of free time.23:02
* infinity would like to get some people on ghci-on-ARM too, but I'm not made of Engineers.23:02
BenCIf only I were a haskell type person, but alas, I'm only concerned enough because of the numbers, not because I really like haskell23:02
infinityWell, I suppose I *am* made of engineer.  Just one, though.23:03
micahginfinity: oh, right, yeah, well, packages build on Debian somehow, so there's got to either be a patch or flag to make it work23:03
BenCAn Engineer of One (™)23:03
infinityBenC: I don't care about Haskell, but everyone I know who does use it, uses ghci, so it's effectively useless to them on non-primary arches.23:03
infinitymicahg: Eh?23:03
infinitymicahg: A patch or flag for what?23:03
micahginfinity: firefox/thunderbird23:03
infinitymicahg: Oh.  Right.23:04
micahgbuilds on armel in Debian last I checked23:04
* ajmitch thought that ghci on arm was merged upstream now23:04
infinityajmitch: Is it?23:05
infinityajmitch: If so, yay, but that certainly hasn't filtered down to the masses.23:05
ajmitchwas reading http://www.haskell.org/pipermail/haskell-cafe/2012-June/101704.html from a few days ago, in 7.4.223:05
* RAOF might get mono to actually work on armhf over the weekend.23:05
ajmitchRAOF: that'd be nice :)23:06
infinityajmitch: Oh, VERY recently.  Nice.23:06
infinityRAOF: Define "work".23:06
infinityRAOF: It already works, it's just not hard float...23:06
RAOFinfinity: Fail to segfault as soon as someone p/invokes.23:06
infinityRAOF: Unless you meant s/armhf/armel/23:07
infinityRAOF: Or did I miss a recent development with it no loger working?23:07
RAOFIt's apparently never worked on armhf.23:08
RAOFWell, except for purely managed code.23:08
RAOFThe JIT works, but as soon as you try to call out to a native library it uses the wrong ABI and things go horribly pear-shaped.23:08
Bluefoxicyhmm, seems ejecting even the partition does it.23:08
BluefoxicyIs 'eject' just umounting?23:09
RAOFYou can see this in the build logs; the test-suite works, except for everything that has “pinvoke” in the name, which segfaults :)23:09
infinityRAOF: Oh, lovely.  Well, if you like mono, go to town.23:09
infinityRAOF: Bonus points if you make it actually be hard-float while you're at it. :P23:09
RAOFIt's *got* a hard-float codepath; is that not on?23:10
infinityRAOF: (Also, I think this hilights that the testsuite is awful, since it passes on armhf...)23:10
RAOFNo, I don't think it does. But failing the testsuite doesn't fail the build.23:11
infinityRAOF: I could be mistaking it for some other nasty hack, but I was fairly sure that mono on armel and armhf were both more-or-less no-float.23:11
infinityOh, indeed.  "390 test(s) passed. 9 test(s) did not pass."23:12
RAOFIt's entirely possible; I've recently prodded around a tiny bit in the ARM (and s390, and sparc, and PPC) JITter, and it seemed to have a float codepath.23:13
infinityRAOF: Honestly, I only tend to care about mono is as much as it's critical path for building a ton of other crap.23:13
infinityRAOF: But if you can make it actually work correctly, go nuts.23:13
RAOFI may ask questions about ARM ABIs :)23:13
infinityAnd I may answer them.23:14
infinityBenC: So, upstream has a table that *claims* ghci is supported on PPC.  So, it may just be suffering a tiny bit of bitrot, might not be as much effort as I initially claimed.23:15
infinityAnd with ghci supported on ARM in 7.4.2, that tosses out a ton of build failures and brings all our arches to parity.  Ish.23:15
infinityYay for toy languages.23:15
infinity(Actually, as much as I don't care about ghc/ghci, I guess having a toy language on toy dev boards is kinda the ideal for poor university students and such)23:16
BenCinfinity: Are you uploading 7.4.2? If so, I'll try re-enabling ghci on PPC23:16
infinityBenC: No.  But I'll probably prod the Debian maintainers about it once I'm done rebootstrapping 7.4.1 on armel. :P23:16
BenCinfinity: irk…Yeah, there's a patch that disables in on ppc…apparently the 6.8 core (of whatever it is that handles ghci) works on ppc, but the 6.10 in current ghc doesn't work so good23:17
BenCinfinity: BTW, I only found one more build-arch fixable package, so I have a note to kick it once dpkg is merged23:39
RAOF@pilot in23:59
=== udevbot changed the topic of #ubuntu-devel to: 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: RAOF

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!