[03:01] <hallyn_> hm, dash isn't coming up
[03:01] <hallyn_> (the dash, not the shell)
[07:08] <dholbach> good morning
[07:16] <tsdgeos> dholbach: do you know how do i get the patch at https://bugs.launchpad.net/ubuntu/+source/fbi/+bug/1450949/comments/8 to the package so that the fbi package is not totally useless by aborting on run?
[07:18] <tsdgeos> which is quite funny is marked as medium since basically makes the software unusable
[07:21] <dholbach> tsdgeos, maybe somebody marked the importance as medium who didn't really know what they were doing
[07:22] <tsdgeos> i guess, now it feels a bit weird if i overwrite the importance given i'm a user of the package that just happens to have the power to change it
[07:22] <dholbach> http://packaging.ubuntu.com/html/patches-to-packages.html is basically the answer
[07:23] <dholbach> but I can take a quick look too
[07:25] <dholbach> there's already debian/patches/use-jpeg-turbo.diff which patches the value to 62 right now
[07:25] <tsdgeos> guess coming from debian that may be using jpeg-turbo and not libjpeg.so.8 like us
[07:26] <tsdgeos> the package is a bit weird since it packages the jpeg headers itself
[07:26] <dholbach> yeah
[07:31] <dholbach> tsdgeos, I uploaded the following patch: http://pastebin.ubuntu.com/11760921/
[07:31] <dholbach> (and confirmed that it works)
[07:32] <tsdgeos> dholbach: awesomeness, will it hit vivid or just wily?
[07:33] <dholbach> oh, that's just wily
[07:35] <dholbach> tsdgeos, is it the same issue in vivid?
[07:35] <tsdgeos> dholbach: yep, it's how i found it
[07:36] <dholbach> ok
[07:36] <dholbach> tsdgeos, do you know why there's a geeqie task for the bug?
[07:36] <tsdgeos> i don't know what geeqie is sorry :/
[07:37] <tsdgeos> ah you mean the other package
[07:37] <tsdgeos> no idea really
[07:37] <dholbach> mh, ok
[07:39] <dholbach> I'll remove it from the bug - looks like geeqie only depends on it
[07:39] <tsdgeos> yeah my guess it was either a dependency or "not sure what i'm doing"
[07:40] <tsdgeos> after having a grep-look a geeqie's code
[08:00] <dholbach> tsdgeos, uploaded the vivid fix as well - it's now sitting in the review queue
[08:04] <tsdgeos> dholbach: great :) thanks a lot :)
[08:05] <dholbach> anytime
[08:23] <jamespage> pitti, any idea why component-mismatches-proposed is still showing junit4 + dependency explosion? the junit4 I uploaded yesterday should have resolved that
[08:34] <LocutusOfBorg1> Logan, sorry, I fixed one udiskie build failure introducing another... :s
[08:34] <LocutusOfBorg1> the new one comes from upstream, I'm opening a bug report there
[09:03] <pitti> jamespage: hm, https://launchpadlibrarian.net/209692232/junit4_4.12-2_4.12-2ubuntu1.diff.gz LGTM too
[09:04] <pitti> jamespage: perhaps c-m looks at the packages in -release as well, not sure
[09:04] <jamespage> pitti, junit4 is blocked on migration due to a regression in libreoffice, but that was already failing afaict
[09:05] <jamespage> (prior to my upload)
[09:05] <pitti> jamespage: I was just looking -- libo fails on
[09:05] <Laney> fixing that
[09:05] <pitti> configure: error: Package requirements (libwps-0.3) were not met:
[09:05] <pitti> No package 'libwps-0.3' found
[09:05] <jamespage> awesome
[09:05] <Laney> (wps transition)
[09:05] <pitti> Laney: oh, you are? thanks
[09:05] <Laney> currently deciding the best way to test build this :-)
[09:05] <Laney> "not"
[09:06] <pitti> jamespage: so, let's postpone this until it migrates?
[09:06] <jamespage> pitti, just trying to unexplode component mismatches so that I can reasonable hassle about binary migrations to main :-)
[09:14] <LocutusOfBorg1> Logan, a fix in on the Debian git, the upload will come shortly :D
[10:20] <Unit193> pitti: Also, I took a quick look, know what bug (if any) is filed for restarting dbus crashing network-manager and lightdm (and not starting network-manager back up, at that)?
[10:56] <mdeslaur> @pilot in
[10:59]  * dholbach hugs mdeslaur
[10:59]  * mdeslaur hugs dholbach
[11:46] <mdeslaur> cjwatson: in wheezy's putty package, you replaced the security fix's use of smemclr() with memset()...I have a feeling that's going to get optimized away by the compiler...
[11:50] <cjwatson> mdeslaur: Do you mean in vuln-bignum-division-by-zero.patch ?
[11:51] <mdeslaur> cjwatson: private-key-not-wiped-2.patch
[11:52] <cjwatson> Oh, I'm on the wrong branch, one moment
[11:52] <cjwatson> mdeslaur: To be fair, wheezy's putty didn't have smemclr at all, so if that's a problem, it's a problem for all the rest of putty as well
[11:55] <mdeslaur> ah, yes, looks like there are other similar uses
[11:55] <cjwatson> mdeslaur: But please do file a Debian bug - I probably ought to backport aa5bae89 et seq
[11:56] <cjwatson> Thanks for the spot
[11:56] <mdeslaur> cjwatson: ack, will do, thanks
[12:01] <Laney> stgraber: trying to use lxd for the first time on wily and I think I'm being stung by https://github.com/lxc/lxd/issues/764 - any plans to update ubuntu's package?
[12:28] <pitti> Unit193: sorry, I don't think I've seen a bug report like that before
[12:29] <pitti> Unit193: we don't restart dbus on upgrades for this very reason -- many dbus services don't get along with that very well
[12:29] <pitti> Unit193: it even used to crash your entire session (although I think that got fixed at some point)
[13:09] <cyphermox> good morning!
[13:09] <jtaylor> pitti: hi, the lvm2 package has the lvmcache manpage but the executable seems to be missing, is that a mistake?
[13:09] <jtaylor> in vivid
[13:10] <pitti> hey cyphermox, how are you?
[13:10] <pitti> jtaylor: hm, no idea -- does Debian have it?
[13:10] <seb128> hey cyphermox
[13:10] <jtaylor> need to check
[13:10] <seb128> cyphermox, btw did you see my ping from some days ago with that nm-applet upstream patch to backport?
[13:23] <jtaylor> pitti: nevermind there is no such binary ...
[13:23] <jtaylor> though fixing bug 1423796 would be nice
[13:52] <cyphermox> pitti: hey!
[13:52] <cyphermox> seb128: hi! I'm not sure, do you mean the one for the add_menu_item crash?
[13:53] <seb128> cyphermox, yes
[15:14] <mdeslaur> @pilot out
[15:16] <flexiondotorg> Laney, I wonder if you can help.
[15:16] <flexiondotorg> Laney, I think this package update was not complete correctly - https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1466521
[15:17] <flexiondotorg> Laney, The update moved some images and added news. The new and moved images are no in the updated package.
[15:17] <Laney> flexiondotorg: Wasn't me that uploaded it: https://launchpad.net/ubuntu/+source/ubuntu-mate-artwork/0.4.9
[15:17] <Laney> You could provide a new package for sponsoring to fix it
[15:18] <flexiondotorg> Laney, Thanks I see the sponsor now.
[15:58] <pitti> kees, slangasek, infinity, mdeslaur, stgraber: TB meeting reminder
[15:58] <mdeslaur> pitti: thanks!
[16:56] <cjwatson> barry: Would it be worth doing a mass retry pass or two on the py35asdefault PPA, to weed out the easy uninstallable-dep cases without too much manual inspection?
[16:58] <barry> cjwatson: i think it would.  can that be easily done through the api?
[16:59] <cjwatson> barry: Yep, I can put that together for you
[16:59] <barry> cjwatson: that would be awesome, thanks!
[17:03] <infinity> Laney: syncing from Debian to a silo might not be the brightest idea while autosyncs are still on. :P
[17:03] <cjwatson> barry: http://paste.ubuntu.com/11763253/
[17:04] <infinity> Laney: (evolution-rss was synced to proposed while your silo was in prep, so you now have a version clash)
[17:06] <barry> cjwatson: nice, thanks
[17:07] <cjwatson> barry: scalingstack can probably blast through those in under half an hour, so feel free to do the same a couple more times later if you like
[17:07] <cjwatson> (though wait for whatever pops out of this round to finish publishing first)
[20:47] <smoser> pitti, dont know how closely you follow systemd bugs, but since you're the one who fixes all my issues with it, just thought i'd mention them here. bug 1468103 and bug 1468102
[20:51] <smoser> (feel free to tell me not to ping you like this)
[21:17] <doko> infinity, pitti: I'm not amused about gcc-5 stuck in proposed with nobody looking at the triggered autopkg tests. and I'm tired to do that myself, only finding issues with the test environment or other packages
[21:18] <infinity> "0 days old" is "stuck"?
[21:19] <doko> the last upload was stuck as well
[22:41] <Laney> infinity: I'll no-change rebuild or delete if necessary before publishing