=== Logan_ is now known as k === cpg is now known as cpg|away [02:04] cjwatson: Good news: I had to use video=ofonly, but the latest quantal-live ISO boots and installs on my iMac G5 === cpg|away is now known as cpg === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates === charles_ is now known as charles [03:51] jbicha: Urm, stuff in proposed will eventually be let out... [03:57] TheMuso: yeah, I just get impatient though :( [04:04] jbicha: Well in teh case of those packages I uploaded to proposed and that you sponsored into quantal proper, it means the archive admins will now have to reject those. === spm is now known as stevemci [04:04] WHich will probably make a little more work for them, as they probably accept from proposed on mass. === stevemci is now known as spm [04:18] Good morning [04:18] hi, I'm trying to build f-spot from source on ubuntu 12.04 and when I run the autogen.sh script I get this error: autogen.sh: 10: autogen.sh: Syntax error: "(" unexpected [04:19] the function it errors out on is check_autotool_version [04:19] ev: yes, I think we can move the dependency to apport-gtk and apport-kde [04:19] am I missing some gnome devel package [04:20] or should this question be better asked in a different channel? #ubuntu? [04:21] ev: pushed to packaging branch [04:30] pitti: morning [04:31] ah, we're unfrozen, nice! /me releases his staged -proposed uploads [04:31] pitti: there seems to be a problem with glib2.0 and gobject-introspection in quantal... the latter has been copied to quantal and has a dependency on the former, which is still in -proposed? [04:31] heh :) [04:31] hm, I'm not sure why someone copied one without the others [04:32] I'll leave the linux bits, I don't know about their state [04:32] jbicha: ^^^ [04:32] pitti: well if you're about to fix it, then that's fine ;) [04:32] Goes back to what I was saying. [04:33] erk @ http://people.canonical.com/~ubuntu-archive/testing/quantal_probs.html [04:33] http://people.canonical.com/~ubuntu-archive/testing/quantal-proposed_probs.html looks slightly better, but I guess linux still needs some love [04:36] TheMuso: which packages need rejecting? === dayangkun_ is now known as dayangkun === dendrobates is now known as dendro-afk [06:56] good morning [07:00] Morning dholbach. [07:00] hey iulian [07:07] 10th Debian patch forwarded : http://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=cc11rocks%40yahoo.com (1 pending upload, 9 outstanding) === smb` is now known as smb === henrix_ is now known as henrix === tkamppeter_ is now known as tkamppeter [08:13] Someone around who can sync qpdf from Debian Experimental for me? [08:22] syncpackage doesn't work for you? [08:22] tkamppeter: does it need a FF etc. exception? or just bug fxies? [08:28] E: /var/cache/apt/archives/libgnome2-bin_2.32.1-2ubuntu2_i386.deb: trying to overwrite '/usr/bin/gnome-open', which is also in package libgnome2-0 2.32.1-2ubuntu1 [08:29] pitti: cheers! [08:29] mpt: fixed [08:29] pitti, it is part of a bug fix, for https://bugs.linuxfoundation.org/show_bug.cgi?id=1063. [08:29] bugs.linuxfoundation.org bug 1063 in cups-filters "pdftops - page management options not being removed" [Blocker,New] [08:30] pitti: why does every release hate my Sansa fuse so, It's showing up but as a usb drive rather than a music player [08:30] didrocks, thanks. Anything I need to do to repair before installing next updates? [08:30] mpt: should be nearly available: https://launchpad.net/ubuntu/+source/libgnome/2.32.1-2ubuntu3 [08:30] davmor2: not sure; when did this start breaking again? it's not like we do a whole lot of m-p-i updates.. [08:30] mpt: the easiest way is to download this .deb package: https://launchpad.net/ubuntu/quantal/+package/libgnome2-bin [08:31] pitti: tkamppeter doesn't have upload access to qpdf, according to edit-acl [08:31] pitti: it's the first time I've plugged it into Quantal so not sure [08:31] cjwatson: ah, thanks [08:32] cjwatson, pitti, as QPDF serves mainly for printing and usually needs to be updated if there is a printing problem or change it should perhaps be added to my list. [08:32] didrocks, doing that says "Failed to satisfy all dependencies (broken cache)." [08:34] mpt: ok, I thought that stokachu didn't put a strong dep in his new faulty -bin package, so the easiest way is to wait the fix to be published (should be in less than 30 minutes) or download this -bin package, libgnome2-common and libgnome2-0 + dpkg them [08:34] tkamppeter: ok, libqpdf8 does not have many rdepends, just cups-filters and "qpdf"; I guess you tested those wit 3.0.2? [08:34] from https://launchpad.net/ubuntu/+source/libgnome/2.32.1-2ubuntu3 [08:34] didrocks, I think I can avoid restarting for 30 minutes. :-) Thanks. [08:35] yw :) [08:36] pitti, qpdf was introduced only for cups-filters. The change in the new Debian package is only support for injecting comments into the PDF output. These comments are needed so that pdftopdf can communicate with pdftops, which the old pdftopdf to prevent N-up coming out as N*N-up. [08:37] tkamppeter: synced [08:38] pitti, thanks. === lifeless_ is now known as lifeless [08:51] cjwatson: hey, i wanted to see what you thought about adding X-Fields to .changes files? Thinking of adding an optional jenkins based gate to the archive to do pre-testing before pushing to the archive.. but want extra data on knowing what to do. [08:52] So for example, "X-ON-SUCCESS-UPLOAD: True" or something.. totally useless to LP/Ubuntu, but purely for Jenkins to know if it should push the signed upload to the archive [08:53] can somebody please reject https://code.launchpad.net/~vericalcroft/ubuntu/quantal/liborigin/typo-fix/+merge/122417? [08:53] Daviey: Once all the pieces are put together, you should be able to use DEP-8 tests for that, and have that control movement from -proposed - XS-Testsuite: autopkgtest [08:54] Daviey: In the meantime, sure, it's fine to use random X- fields [08:54] https://code.launchpad.net/~bmanojkumar/ubuntu/quantal/gluas/typo-fix/+merge/122388 too please [08:55] cjwatson: Yeah, we were looking to run DEP-8 tests [08:55] cjwatson: ok, thanks. [08:55] XS-Testsuite: autopkgtest is the "official" X- field for that [08:56] https://code.launchpad.net/~bmanojkumar/ubuntu/quantal/eikazo/typo-fix/+merge/122386 too please [08:56] And (AFAIK) our jenkins instance is already configured to automatically run tests for any packages that include that [08:57] cjwatson, Daviey and I are working on this idea of a build/test pipeline pre-upload [08:57] jamespage: it's on the foundations-p-upload-intermediary plan [08:57] cjwatson: so it does that as a reaction to uploads in the archive, rather than pre-testing? [08:58] Daviey: Yeah, we were intending to do it based on -proposed [08:58] * Daviey reads foundations-p-upload-intermediary [08:58] dholbach: done [08:58] thanks a lot cjwatson [08:58] the next few I'll pastebin [08:59] I'm cleaning up the should've-gone-to-Debian ones [08:59] and the bug-fixing article with a few examples is online now too [08:59] I hope that'll prevent things like this in the future [09:00] cjwatson: What would make me a happy bunny is if -proposed had /some/ promise of stability, so people wanting real craziness can run that.. with people wanting a little more stability running the release pocket. [09:00] Daviey: That isn't going to happen [09:00] I mean not with any kind of automatic promise [09:01] cjwatson: why can't we consider gating? [09:01] Pre-testing isn't going to help when you can't even install the packages [09:01] cjwatson: I mean, catching the real obvious crap that people seem to miss [09:01] Because scope [09:01] This project is already a cycle late [09:02] cjwatson: We wanted to do this from a server-dev POV anyway.. But i don't want to duplicate work either. [09:02] Also doing autopkgtest after upload allows you to parallelise the builds required [09:02] If you want to layer some independent stuff on top just for server, be my guest [09:03] Obviously people are entitled to test their uploads as much as they like before pushing them to the archive [09:04] right, that was the plan. If it worked out well, i'd like to welcome others to use the same infrastructure [09:06] In general, I don't want to cause all XS-Testsuite: autopkgtest to use pre-testing because autopkgtest at least sometimes involves building the source package, and I want to be able to do that in parallel with the official builds so that we don't slow everything down too much [09:06] If you can manage some arrangement where developers can opt in on an upload-by-upload basis (perhaps by using a different dput upload target), cool [09:06] ok [09:07] cjwatson: yeah, that was the plan [09:07] so i dput to jenkins, and if it passes, jenkins dputs to the archive for me. [09:10] So that's fine certainly, I just don't want it to turn into "developers are being irresponsible if they don't use this" in time, since there may very well be good reasons not to [09:10] And I don't think it's useful to have an expectation of "-proposed is usable" since it's solely intended as a location for staging automatic checks [09:12] sorry, you mean.. -proposed IS a location for staging automatic checks.. or shoudln't be thought as such? [09:12] It is such a location, and the checks are intended to be such that it really doesn't make sense to "want real craziness" and bypass them [09:13] It would only be interesting to run -proposed if there were a delay, in the style of Debian propagation from unstable to testing - but I think all concerned (especially those with some experience of operating the Debian testing migrator) have agreed we don't want to do that [09:16] shadeslayer, do you think you can have a look athttps://code.launchpad.net/~andreagrandi/ubuntu/quantal/kdevelop-custom-buildsystem/typo-fix/+merge/121225? [09:16] Daviey: upload to $(devel)-proposed, wait for everything to build & settle, (autopkgtests run and give OK), (britney runs & says it's installable and ok to transition), (britney moves the batch into $devel) [09:17] Daviey: apart from we don't have the bits in () yet.... [09:17] I believe we have "autopkgtests run and give OK" [09:17] ok. cool. [09:17] one down =) [09:18] cjwatson: And $devel-proposed, even if you have it enabled does not auto-install from it? (like debian-backports) [09:21] xnox: well, that is just a priority. [09:21] true. [09:28] xnox: There's a work item for that somewhere [09:28] xnox: But see https://code.launchpad.net/~laney/launchpad/proposed-notautomatic/+merge/113921 [09:29] bug 1016776 [09:29] Launchpad bug 1016776 in Launchpad itself "Users are offered updates to packages in -proposed" [Low,In progress] https://launchpad.net/bugs/1016776 [09:30] Laney: *poke* [09:32] cjwatson: argh [09:32] that [09:33] it got blocked because I didn't see what to refactor in the area for LoC [09:33] should look harder [09:35] can somebody reject http://paste.ubuntu.com/1190481/? [09:38] Laney: Next time I see something obvious I'll punt it your way, how about that [09:38] Laney: The usual no-imagination answer is to rewrite some doctests as unit tests, which tends to come out positive [10:05] what is GUdev and how is it different from udisks?! === doko_ is now known as doko [10:35] guys quick query I have a virtual box install in place I've go to additional drivers and I expect to see the vbox addition drivers in there but there is nothing [10:35] should it appear there like it did in jockey? === MacSlow is now known as MacSlow|lunch === cpg is now known as cpg|away === mcclurmc is now known as mcclurmc_away === mcclurmc_away is now known as mcclurmc === MacSlow|lunch is now known as MacSlow === dendro-afk is now known as dendrobates [12:19] xnox: GUdev is a glib wrapper around libudev; it's got nothing to do with udisks [12:20] pitti: thanks. got mislead. [12:20] xnox: i. e. it provides GLib main loop integration and an "uevent" signal which you can connect to for listening to hw changes [12:20] xnox: udisks is the dbus system service for managing disks [12:21] pitti: any idea why does thunar ignores udisks --inhibit and automounts stuff which it (presumambly) sniffed from uevents. [12:21] ? [12:21] xnox: hm, I had expected thunar to call udisks as well -- I'm not aware of another d-bus system service which provides mounting [12:22] xnox: one thing that could happen here is that we are talking about udisks vs. udisks2? [12:22] well. ubiquity is run under udisks --inhibit, yet thunar jumps in the middle and automounts partitions breaking the installer "partition is mounted....." [12:23] xnox: in ubuntu we use udisks2 now, and thunar recommends that as well [12:23] xnox: ooh -- presumably ubiquity needs to inhibit udisks2, not udisks [12:23] pitti: i have no idea =) I added a call to xfconf-query to flip automount off. And I presume udisks --inhibit is udisks2 [12:23] pitti: ah =) [12:23] Yeah, probably [12:23] no, /usr/bin/udisks is udisks1 [12:24] http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2008-04-12-desktop-automount-pain.html *whine* [12:24] DEAR EVERYONE PLEASE STOP CHANGING THIS [12:24] OK, so we should try udisks2, udisks1, devkit-disks, hal........ [12:24] let me figure out the current equivalent [12:24] pitti: any ETA on udisks3? [12:24] We can probably afford to drop devkit-disks now [12:24] yeah, and hal as well [12:24] I kept that just in case since the package was still around [12:25] Needs to work on all flavours/derivatives no matter what mad stuff they do ... [12:25] as soon as usb-creator and checkbox get ported, udisks will fall off the CD [12:25] pitti: I am hoping to do usb-creator tomorrow as part of Global Jam [12:25] together with re-packaging to use python3 by default [12:33] xnox: oh, is that the "Stop thunar from auto-mounting, above didn't work?!" part in ./bin/ubiquity-wrapper? [12:34] xnox: right, your r5638 [12:34] xnox: so yes, that should be replaced with an udisks2 inhibitor [12:34] pitti: that does work, but it's not ideal. I really don't want to care about xfce/lubuntu/gtk/kde/etc changing the names of their options. [12:35] xnox: there is no direct counterpart for this in udisks2, but how about I put a script for this (/usr/lib/udisks2/udisks2-inhibit) into our udisks package? [12:35] "udisks2" package, I mean === Phantomas1 is now known as Phantomas [12:35] pitti: can i stop that dbus service? and restarted when I am done? [12:36] xnox: my current idea was to change the polkit rules to only allow changes for root, and nobody else [12:36] i. e. what udisks --inhibit did as well [12:36] that seems to be the most robust solution to me [12:37] hmm... is that what udisks did? [12:37] not with polkit, but with --inhibit it only allowed operations from root [12:37] it seemed to me that it also made dbus calls to return "inhibited" or something like that. [12:38] pitti: that should do it. [12:38] yes, org.freedesktop.UDisks.Error.Inhibited [12:38] with the temporary polkit rule you'd get a "no permission" error [12:39] the desktop is started as $user with passwordless sudo, so users could still screw the installer over [12:39] well, with "sudo command" you can always screw the instlaler [12:39] no need to talk to udisks, you can jsut directly "sudo mount", etc. [12:39] pitti: yes, please add that wrapper =) and please don't change it's name =) [12:39] and we can improve it later. [12:40] pitti: it would be awesome to have a package $inhibit-any which will inhibit udisk, udisk2, hal and what not =) [12:40] pitti: cause I'd use it in ubquity, usb-creator not sure about others. [12:41] just curious that this hasn't been discovered in testing so far [12:41] oh it has been. [12:41] the first xubuntu bug is from ~2011 [12:42] I think I saw a bug on Ubuntu desktop amd64 from this testing cycle as well [12:42] Though that might be cognitive leakage from something else [12:42] on Ubuntu Desktop we have default settings in nautilus to prevent automounting, similar to how I now did it for thunar [12:42] Anyway this is the sort of bug that's pretty hard to track down if you don't recognise it [12:58] xnox: so http://paste.ubuntu.com/1190766/ is my first working iteration [13:00] xnox: however, not quit happy with the trap yet; I'll change it to an absolutely failsafe approach [13:00] ok. looks good. [13:04] oh what would I give for a mount -t tmpfs -o overlay [13:04] ++ [13:05] $ dpkg -S /debian [13:05] ubuntuone-client-gnome: /debian [13:05] Is that a known issue? [13:05] lol [13:05] sexy [13:05] dobey: ^ yay easter eggs! [13:06] err? [13:07] indeed [13:07] (the shiniest new quantal feature ... we're turning your rootfs into a sourcepackage you just "dpkg-buildpackage -rfakeroot -b" in / and you get a full backup alread packaged !) [13:07] y [13:07] it's a binary package, though [13:08] wtf [13:08] ogra_: Heh. [13:08] well, once cjwatson added .deb support to grob that will just work ;) [13:08] *grub indeed [13:08] * cjwatson checks 2.00 feature set [13:08] You never know [13:08] ** [13:08] err *g* [13:09] c'est vendredi, évidemment [13:10] pitti: tout à fait! :) [13:13] haha [13:15] pitti, can you upload cups-filters to Debian and to Quantal? Thanks. [13:16] yay dpkg :-/ [13:17] is the beta release done now so i can upload to quantal? [13:17] dobey: yes; and you could have uploaded before as well (it'll just get caught in unapproved) [13:18] tkamppeter: in a bit, sorry [13:19] right; just don't see a mail to devel-announce [13:19] xnox: ah, my trick with using unshare -m won't help, I'm afraid (the running polkitd won't see that); so, just tmpfs then [13:20] BenC: is there a bug for that? [13:23] dobey, the release mail was cross posted to -release and -announce [13:23] probably your filter dropped into -release (as mine did) [13:24] Exactly why I don't believe in automatic deduplication of mails :) [13:24] ogra_: i don't think i'm subscribed to -release, and i am not filtering the -announce mail so it should just go into my inbox; but i only see the "beta freeze now in effect mail" :) [13:25] Mm, there's nothing on https://lists.ubuntu.com/archives/ubuntu-devel-announce/ [13:25] weird [13:25] i definitely see it in the mail header [13:25] Oh, -announce, not -devel-announce, perhaps [13:25] oh, où est xnox? [13:25] yup [13:25] There ought to have been a separate mail to -devel-announce that the archive is open again [13:25] Oh well [13:26] right, i was expecting to see the archive mail :) [13:26] udisks2-inhibit: http://paste.ubuntu.com/1190807/ ; ugly, but working [13:26] more pairs of eyes appreciated [13:26] well, you could have guessed by the traffic on -changes that its open again :) [13:34] dobey: I just noticed it, so no bug yet [13:37] BenC: ok, should i wait for a bug or just fix it? [13:37] dobey: Would take longer to file the bug :) [13:37] dobey: just fix it please [13:39] tkamppeter: erledigt === psivaa is now known as psivaa_afk [13:40] @pilot in === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal development | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #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: jamespage [13:45] xnox: http://anonscm.debian.org/gitweb/?p=pkg-utopia/udisks2.git;a=commit;h=93ccffecb0 [13:46] pitti: (1.99.0-4) UNRELEASED [13:46] * xnox =( [13:46] xnox: yes, I just committed it; I want to fix another bug, and will then upload [13:46] pitti: ping me when it's in quantal =) [13:46] pitti: I will fix up ubiquity then. [13:46] dobey: BTW, lintian complains fairly loudly about that. Maybe pay a little more attention to it in future? :) [13:46] xnox: jsut in case you want to test it locally already [13:47] ok. [13:47] * dholbach hugs jamespage [13:47] tumbleweed: complains where? [13:47] pitti: 'testing ubiquity locally' is not a 30s setup =) [13:47] * xnox is deep in partman right now. [13:47] dobey: when you run it on the binary. do you run lintian in your test builds? [13:47] xnox: no worries; I just gave you the URL in case you were waiting for it [13:48] thank you =) [13:48] xnox: (I usually test such stuff in a live system and edit files in-place) [13:48] tumbleweed: it isn't run automatically? [13:48] lintian your _arch.changes file after test building [13:48] or configure your build environment to do it for you [13:49] lintian is run by default when you use debuild. But debuild -S only builds a source package [13:49] pbuilder/sbuild don't run it by default? [13:49] pbuilder has an example hook that runs pbuilder after the build. And in sbuild It hink it does it by default [13:50] no I think it's false by default [13:50] no, not by default, but you just set $run_lintian = 1; [13:54] set it where? i found http://askubuntu.com/questions/140697/how-do-i-run-lintian-from-pbuilder-dist which suggests i have to make a new directory in my home directory and copy things to it, then set it as the dir to use in ~/.pbuilderrc [13:54] that all sounds right [13:55] and i see dh_lintian being run in the build log for the package, but no complaints from lintian, on lp [13:55] dh_lintian copyies lintian overrides into a binary package [13:55] nothing else [13:55] pitti, thanks. [13:55] so i guess the archive builders aren't running lintian by default? [13:56] no. But we do have an external lintian lab: lintian.ubuntuwire.org [13:59] can anyone rejects https://code.launchpad.net/~logan/ubuntu/quantal/notify-osd/debian-merge/+merge/118465? thanks :) [13:59] didrocks: *zap* [14:00] * didrocks hugs pitti [14:00] (beautiful zap btw ;)) [14:00] didrocks: do you say "fini" for this, BTW? [14:01] I would say "fait" rather [14:06] @pilot in === udevbot changed the topic of #ubuntu-devel to: Quantal Quetzal development | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #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: ogasawara, jamespage [14:07] * dholbach hugs ogasawara :) [14:07] it seems to be pilot friday [14:09] hello, guys, i'm developing an app now, but there's some problem...how can i make the .gschema file installed while install the software? [14:12] does this seem wrong to anyone: http://paste.ubuntu.com/1190880/ [14:13] dholbach, I seem to be following you though bugs [14:13] err... try http://paste.ubuntu.com/1190881/ [14:13] actually, yes it does seem wrong [14:13] jamespage, I stopped :) [14:15] anyone have thoughts on how to figure out why an apt-get dist-upgrade on a cloud-image would pull in all those packages ? [14:18] mterry: ping [14:19] zul, I see it :) [14:19] zul, urllib3 right? [14:19] mterry: how did you guess? :) [14:19] zul, email wins the race against IRC [14:19] mterry: yeah sorry im not fast enough [14:20] there it is. [14:20] i think [14:21] bdmurray, your fix for bug 1043725 seems to have added a ton of dependencies to cloud-images [14:21] Launchpad bug 1043725 in update-manager (Ubuntu) "dep8 test test_stop_update.TestStopUpdate failed: missing dependency on update-notifier (schema com.ubuntu.update-notifier missing)" [High,Fix released] https://launchpad.net/bugs/1043725 [14:21] http://paste.ubuntu.com/1190881/ [14:22] zul, can you port the patch they had on their embedded urllib3 to our system one and forward on? It seemed like a generally useful thing [14:22] mterry: for requests? [14:23] zul, yeah. requests had a tiny patch for AppEngine support in their embedded urllib3 [14:23] zul, just diff it with our system one to see it [14:23] mterry: sure [14:27] are there people assigned to making Unity less battery hungry? since updating to quantal my MBA 4,1 has lost an entire hour of battery life. RIP unity2d... [14:27] SpamapS, that bug is [marked] fixed :) [14:28] https://bugs.launchpad.net/ubuntu-power-consumption/+bug/917210 [14:28] Launchpad bug 917210 in unity (Ubuntu) "compiz+unity3d generates > 50 wakeups a second on idle system" [High,Fix released] [14:28] mterry: are you talking about the ntlm stuff? [14:30] zul, http://pastebin.ubuntu.com/1190918/ [14:31] mterry: ah ok...i can add that sure [14:31] zul, just don't want to regress as we move to a system urllib3 [14:31] right [14:31] cjwatson: bug 1039022 says it's being filed from a 64 bit platform; stat(2) says that EOVERFLOW should only occurr on 32 bit platforms; did you file this from the same computer than the one showing the error? [14:31] Launchpad bug 1039022 in udisks2 (Ubuntu) "No large-file support?" [Undecided,New] https://launchpad.net/bugs/1039022 [14:35] pitti: 64-bit kernel, 32-bit userspace. Yes I did. [14:35] cjwatson: aah, missed the Architecture: field; thanks [14:36] Yep, I have a 32-bit installation I don't want to bother reinstalling, but I want to be able to use 64-bit chroots and VMs, so I run a 64-bit kernel with multiarch. === psivaa_afk is now known as psivaa [14:38] bdmurray: bug 1043725 .. seems to have added gui stuff to server/cloud images [14:38] fortunately I just created a 32 bit chroot yesterday [14:38] Launchpad bug 1043725 in update-manager (Ubuntu) "dep8 test test_stop_update.TestStopUpdate failed: missing dependency on update-notifier (schema com.ubuntu.update-notifier missing)" [High,Fix released] https://launchpad.net/bugs/1043725 [14:41] /tmp/hooks/B90lintian: 6: /tmp/hooks/B90lintian: Bad substitution [14:41] awesome! [14:41] :( [14:43] smoser: As bdmurray isn't around, Can you back out the fix for 1043725 please? [14:44] dobey: sbuild FTW [14:44] mterry: ping anything else...im just queueing up the upload for urllib3 [14:44] [14:44] Daviey, sure. [14:44] dobey: You could just run lintian foo.changes after your build anyway. [14:45] cjwatson: automation FTW [14:45] :) [14:45] zul, oh I haven't been looking through yet. If you don't mind just holding on to that until I get to it [14:45] mterry: yeah i just did a quick check and its using python2 and it runs the testsuite [14:46] dobey: Absolutely, but I assumed if you hadn't already switched to sbuild you must have had some reason [14:46] Given that pbuilder is awful [14:46] cjwatson: mostly time [14:46] zul, you server people and your python2! Living in the past, man [14:46] mterry: yeah well um...:P [14:46] mterry: Did i just hear you volunteer to help port upstream code to py3? I *think* i did. [14:47] zul: did you hear that? [14:47] Daviey: i did...mterry get on it ;) [14:47] Daviey, it's my foss-given right to bitch at other developers to do work I want to see done [14:48] mterry: Hah, yes it is. :) [14:48] smoser: I'm here now are you working on it? [14:48] xnox: there, have a new udisks2 with an inhibit script: https://launchpad.net/ubuntu/+source/udisks2/1.99.0-4 [14:48] pitti: thanks =) [14:48] i just branched the source so far. [14:48] so if you wanted to do that, i'd appreciate it. [14:48] smoser: okay, I'll fix it [14:49] * cjwatson wonders if installing https://code.launchpad.net/~cjwatson/ubuntu/quantal/grub2/2.00 on his laptop on a Friday afternoon is a Really Bad Idea [14:50] Maybe a VM test first would be the path of wisdom [14:51] cjwatson: Oh, i thought you were brave. Just. Do. It. Man or Mouse? [14:53] Unrelated, I just did a dist-upgrade on a Quantal server.. and it complained of FD leaks... now the partition seems fubar'd. I don't know if it's just hardware failure, or something more serious. [14:53] FD leaks almost certainly nothing to do with anything of importance. [14:53] Daviey: mouse, when it comes to being able to work :P [14:55] cjwatson: fdisk exited non-zero on subsequent boot, directly after. I wondered more if it was an indicator of something more serious.. or just a boring disk failure.. which FD leaks were indicating [14:55] *shrug* [14:55] That's not what an FD leak means. [14:55] dholbach: ofcourse [14:55] It means that some process isn't being tidy about its file descriptors when forking some other process. LVM likes to whine about this. [14:56] shadeslayer, shukria [14:56] yeah I am annoyed at that myself..... [14:56] :D [14:56] Once in a blue moon something actually cares (it can break debconf from time to time), but it's very rare and the symptom would be much more likely to be a hang or something, not data corruption. [14:57] well or python3 really disliking those [14:57] ev loves fixing leaked FDs =) [14:57] cjwatson: right.. I could be entirely wrong.. but I wondered if a disk failing would block an app from closing it's FD.. hence run out? [14:58] dholbach: there's a new KDevelop release as well [14:58] xnox: :) [14:58] cjwatson: ah, I also understand it as a long-running process which is missing a close() and piles up open files, so that eventually your user hits the 1024 files ulimit [14:58] anyway.. i just found it odd that a box failed to boot.. with that as it's only odd thing before it shutdown. [14:58] how practical is it to use only python3 in quantal? [14:59] shadeslayer, ok cool I'll leave it with you then [14:59] 3.3 is already multiarched, so wondering if I can just use that for python build-deps rather than finishing mulitarching 2.7... [14:59] wookey: As soon as you install someting, you'll probably end up with py2. The intention was to keep py2 off the cd.. don't know if that has been achieved [14:59] Any idea how many builds would break due to 2/3 diffreences? [14:59] but real world usage, will end up with py2. [15:00] I am doing this in a forked repo so can change build-deps [15:00] I'm just wondering if it is at all likely to actually work... [15:00] pitti: Oh, well, it depends on the exact message, but that's usually phrased as "out of FDs" rather than "FD leak" [15:00] Daviey: No, it would not cause that. [15:00] it's similar to a memleak in that regard [15:01] anyway, terms... [15:01] zul, go ahead and upload python-urllib3 with that tiny fix, looks fine to me [15:01] mterry: k...it has a dependency of python-tornado when i just have a MIR for as well [15:01] meh, defining _LARGEFILE64_SOURCE doesn't seem to do the trick :( [15:02] zul, yeah I noticed, doing that nxt [15:02] Well. You can get EIO from close(). But it would be astonishingly rare for the process in question not to fall over somewhere else afterwards; IOW you would certainly not see an FD leak as the only error in this case. [15:02] wookey: s/python2/python3/ will fail. code needs to be ported to python3. [15:02] wookey: 3.2 vs 3.3 should mostly work [15:02] pitti: You probably want -D_FILE_OFFSET_BITS=64 [15:02] cjwatson: ah, thanks [15:02] _LARGEFILE64_SOURCE isn't generally your friend [15:03] Ah, i think it was bad file descriptor.. not leak.. duh. [15:03] xnox: OK, that's what I thought, but wondering actually 'most' code might work anyway (for building purposes - I don;t care if it doesn;t install/run properly (much) [15:03] wookey: No. [15:04] Daviey: That usually indicates either a lack of correct error handling somewhere or corruption in some variable, not anything due to disk. [15:04] OK. I'll finish the 2.7 work then :-) cheers [15:04] wookey: It's possible to write code that works in both >= 2.6 and 3.x if you're careful, but most packages that have gone to that effort have already been ported to 3.x. [15:04] wookey: Anything that hasn't gone to that effort will almost certainly break immediately. [15:05] wookey: to _build_ most python packages, you need python2 anyway (as it's rare case when the package supports only 3.x) [15:05] It's not even trying to be a drop-in replacement. [15:05] mterry: done [15:07] wookey: I guess if all the build were doing was shuffling files around then you might get away with it; but many Python packages run tests too. I doubt the small saving in up-front effort is worth debugging the consequential problems. [15:09] OK. I was just looking for a possible shortcut to test some other stuff. turning off the tests is easy. (assuming nocheck is properly supported). I think it's mostly done anyway, but I just know it'll fiddly getting it all right (not helped by my exceedingly week python-foo) [15:10] zul, tornado looks to have some kind of test suite, but nosetest doesn't seem to be the right way to run it. Do you know how? [15:10] cjwatson++ [15:10] cjwatson: yer fix works [15:10]