[01:14] How do I verify which DIST pdebuild is using? === lifeless_ is now known as lifeless [01:39] god damn you pbuilder [07:34] good morning [07:39] <_nullthree> morning === almaisan-away is now known as al-maisan [10:50] jtaylor: from #debian-ubuntu: [10:50] 12:46 < sgnb> unison has been synchronized in precise, but not unison2.32.52 [10:50] 12:47 < sgnb> unison2.32.52 should be imported to precise as well, to keep compatibility with previous ubuntu releases === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === yofel_ is now known as yofel [17:26] wtf is that for a source package name oO === almaisan-away is now known as al-maisan [17:36] compatibility package :) [17:37] do you know what exactly its needed for? [17:37] because I'm guessing it will fail to build + needs patching for the log [17:38] the reason in the debian upload was "to maintain compatibility with squeeze" [17:38] I'm assuming the network protocol has changed [17:38] but I left finding that out to you :P [17:39] I already inquired in #debubu [17:39] * tumbleweed saw === al-maisan is now known as almaisan-away [18:26] jtaylor: why to you expect it to FTBFS? [18:27] rsvg has disappeared in ubuntu [18:27] ah === tobin is now known as joshuaBRB [18:32] jtaylor: see also bug #941836 and bug #937596 requesting that version too [18:32] Launchpad bug 941836 in unison (Ubuntu) "Please add unison2.32.52 packages to precise" [Undecided,New] https://launchpad.net/bugs/941836 [18:32] Launchpad bug 937596 in unison (Ubuntu) "Ubuntu should deliver compat package: unison 2.32" [Undecided,New] https://launchpad.net/bugs/937596 [18:33] meh forgot to subscribe to the package [18:33] is there a tool for that btw? [18:33] only know of pts-subscribe [18:34] I don't know of any for LP [18:34] CLI tool? you could add one to lp-dev-tools [18:34] but the only events LP knows about for a per-package-subscription today are bug mail [18:34] you might also want to ask sgnb if we really need 3 version of unison in the archive (there is also unison2.27.57) [18:35] hm and it does not look patched for the log dir change [18:36] why was that done without debian in a package that forks so often :( === joshuaBRB is now known as tobin [18:52] tumbleweed: I'll merge the unison package, do I need an ffe for that? [18:53] 2.32 [18:54] as it's a new source package you'll need a FFe [18:55] its not really new ;) === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [19:56] It takes an archive admin to review it, so you need an FFe. [19:57] k I'll reuse the existing unison ffe [20:00] Please don't [20:04] k new one then [20:25] bug 937596 [20:25] Launchpad bug 937596 in unison (Ubuntu) "feature freeze exception: Ubuntu should deliver compat package: unison 2.32" [Undecided,In progress] https://launchpad.net/bugs/937596 [21:25] whats the SRU version number when the same XYbuildZ version is in a later release and is not affected? [21:30] How about XY0.1 [21:30] buildX.11.04.1? [21:30] Oh, wait. [21:31] Same version in a later release is not affected? [21:31] jtaylor: you're in trouble, you have to rebuild the later release in any event, for versioning: https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging [21:31] How does that work out? [21:31] and the same question as ScottK ^^ :) [21:31] the cause is actually a library, but the broken packages declares its dependencies in a broken way, fixing that fixes the issue [21:31] the broken package is a leaf package, the library not [21:32] so its safer to just fix the leaf package [21:32] the library is not actually broken, it just behaves in a way not expected by the broken leaf package [21:32] it does in a later release so no fix necessary [21:32] but I could fix the leaf package in the later release too, it does not even declare a dependency on libc [21:33] That would solve the versioning problem. [21:53] can armel and armhf do unaligned memory access? if no how is that handled in qemu armel? [21:58] hm no to the first according to http://wiki.debian.org/ArmEabiFixes but my qemu question still stands