=== _salem is now known as salem_
=== maclin1 is now known as maclin
=== salem_ is now known as _salem
=== marcusto_ is now known as marcustomlinson
[08:25] <rbasak> nacc_: commented and marked the Trusty task Incomplete.
[09:49] <jtaylor> is unity in some way connected to oxideqt? I'm looking at bug 1629188 and my sound not working since an update yesterday
[09:49] <ubottu> bug 1629188 in compiz (Ubuntu) "compiz crashed with SIGSEGV in unity::input::Monitor::Impl::UpdateEventMonitor()" [Medium,Confirmed] https://launchpad.net/bugs/1629188
[09:49] <jtaylor> the only related update seems to be oxideqt but it doesn't seem to be related to unity as far as I can tell
[09:52] <jtaylor> hmm just some webapp plugins I don't use
[09:57] <jtaylor> ok removing those breaks my login, so its probably oxide
[10:02] <seb128> jtaylor, compiz/unity shouldn't have have to do with it
[10:04] <jtaylor> seb128: that is my update list: http://paste.ubuntu.com/24287045/
[10:04] <jtaylor> its not linux as the sound works in lightdm
[10:04] <jtaylor> aptdaemon shouldn't be related
[10:05] <seb128> you are sure it's due to an update?
[10:06] <seb128> does sound work in a guest session?
[10:06] <jtaylor> I haven't changed anything else on the system
[10:06] <jtaylor> I can try that
[10:06] <seb128> it doesn't mean it's due to an update
[10:06] <seb128> could be a config/local/random bug that would have happened without package changes
[10:08] <jtaylor> guest session works strange
[10:09] <jtaylor> I guess I'll reset my configuration then
[10:20] <jtaylor> hm no dice ... well about time I install zesty anyway
[11:49] <jtaylor> urg zesty grub does not deal with lvmcache devices
=== _salem is now known as salem_
=== pstolowski is now known as pstolowski|schoo
=== pstolowski|schoo is now known as pstolowski-schoo
[12:38] <jtaylor> bug 1678112
[12:38] <ubottu> bug 1678112 in grub-installer (Ubuntu) "grub fails on lvmcached raid1 volume" [Undecided,New] https://launchpad.net/bugs/1678112
=== pstolowski-schoo is now known as pstolowski
[13:11] <slashd> rbasak good friday, have you been able to look at my email I sent (re: isc-dhcp) ?
[13:11] <rbasak> slashd: not yet, sorry. On my list.
[13:11] <slashd> rbasak, no problem was just curious, tks
[13:28] <mdeslaur> nacc_: thanks for imagemagick! :)
[13:31] <smoser> stgraber, I wonder if you would take a look at https://code.launchpad.net/~smoser/ubuntu/+source/resolvconf/+git/resolvconf/+merge/321203 and give it a think.
[13:33] <smoser> i'd like *someone*'s input on it.  the fix seems sane and safe to me.
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== _salem is now known as salem_
[14:41] <jgrimm> slangasek, would you be able to review smoser's resolvconf change or pointer to someone that would be good reviewer?
[14:42] <nacc_> rbasak: thanks!
[14:42] <nacc_> mdeslaur: of course, np!
=== nacc_ is now known as nacc
[15:11] <stgraber> smoser: doesn't seem unreasonable to me, slangasek and cyphermox may have opinions too and you should talk to upstream. Back when I did the resolvconf integration for Ubuntu upstream was very reactive and willing to work on such feature additions, so worth a chat with him before we start diverging from Debian
[15:12] <smoser> stgraber, thanksl
[15:15] <cyphermox> indeed, talk to upstream, they're likely to be happy with the change
[15:17] <cyphermox> I would say come up with a use-case for this that isn't cloud-init; it this is something that makes sense to write up manually for some reason, it will make it easier to understand
[15:34] <slangasek> smoser: I concur in the whole with my colleagues ;)
[15:54] <smoser> so ifupdown "upstream" is just debian, right?
[15:54] <smoser> slangasek, ? i'll file a debian bug?
[15:54] <cjwatson> yes
=== maclin1 is now known as maclin
[16:52] <mdeslaur> doko: any plans on merging bash again?
[17:10] <nacc> infinity: i feel like an idiot, but i'm not sure how to figure out why older binary packages from src:imagemagick are still in rmadison? http://paste.ubuntu.com/24289042/
=== salem_ is now known as _salem
=== _salem is now known as salem_
[19:41] <infinity> nacc: If I had to guess, I'd say that's because powerpc isn't actually removed yet, and the publisher domination code won't allow removal of arch-indep packages from a source that still has arch-dep packages published.  The part where you can't see powerpc from the outside world makes this monumentally more confusing.
[19:41] <infinity> wgrant: ^--- Yo, time's running out.  Also, the "hang on to arch:all cruft" codepath in domination means we're hanging on to cruft due to powerpc's aging binaries, which may or may not have weird outcomes.
[20:26] <nacc> infinity: oh sure, that makes sense
[20:26] <nacc> infinity: yeah, i was looking through all the revdeps and nothing was holding them by version
[22:17] <nacc> rbasak: fyi, i just pushed a fix to how we invoke gbp-import-orig; it might have fixed the import issue you were seeing
[22:23] <nacc> rbasak: sigh, not quite -- debugging some more
[22:45] <nacc> rbasak: so i think i unerstand the problem, but not sure how to fix it -- let's say you ran the importer once (or did pull-lp-source at some point) and have some symlinks for orig tarballs somewhere. gbp import-orig doesn't handle that great :)
=== salem_ is now known as _salem
[23:50] <wgrant> infinity: Ah, I'd forgotten about the arch-indep caveat. Will fix on Monday.