[02:15] <jbicha> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[02:17] <sarnold> "cannot open shared object file"
[02:17] <jbicha> yes, that sounds bad
[02:18] <jbicha> this is with my sbuild's now on artful host
[02:19] <jbicha> glibc?
[02:25] <Unit193> jbicha: Seen http://paste.openstack.org/show/621666/ after recent updates?
[02:42] <Unit193> Aha, I think I see it.
[03:22] <Muyfret> are multiple passes of testing and inspection of an update to a package done for popular packages
[03:22] <Muyfret> for example thunderbird or samba
[03:33] <kirkland> slangasek: alrighty -- so....other than fixing my FTBFS (which is fixed now!), are there any other changes I need to make on my end?
[03:37] <slangasek> kirkland: nope; we need to think about how to fix the lack of periodic nag mails for FTBFS packages, though
[03:47] <honestly> Hello! I know this is a big ask, but is there anyone here who can walk me through setting up an ubuntu maintenance/packaging environment so that I can prepare an SRU? It's really hard to do this on my own since the documentation is rather fragmented. The bug is here: https://bugs.launchpad.net/ubuntu/+source/ieee-data/+bug/1714602, and it should be eligible for an SRU to xenial, especially since it
[03:47] <honestly> has pretty high impact.
[05:15] <tyhicks> slangasek: thanks for the stenographer test fix!
[05:39] <cpaelzer> LocutusOfBorg: all the finger crossing helped - TL;DR fixed I made all the bug updates required
[05:39] <cpaelzer> thanks
[06:17] <slangasek> tyhicks: no prob!
[08:56] <LocutusOfBorg> ;)
[09:00] <Unit193> Is your eye twitchcing?
[10:04] <doko> bad pitti, cockpit not using python3 ;p
[10:06] <honestly> hello! I am trying to work on getting a fix for https://bugs.launchpad.net/ubuntu/+source/ieee-data/+bug/1714602 SRU'd into xenial but I'm a complete newbie. I followed http://packaging.ubuntu.com/html/getting-set-up.html to set up a packaging environment, what should I do next? Should I try to pull a new package version from upstream?
[10:07] <pitti> doko: the tests aren't indeed, but there shouldn't be a runtime dependency?
[10:08] <doko> cjwatson: nice idea with s/python/python2/ but we probably won't catch all insanities users do with symlinks. I haven't yet found the webpage recommending changing the symlink
[10:09] <doko> pitti: haven't check, just saw the autopkg test
[10:33] <cjwatson> doko: Yeah, I'm sure we won't, it just seemed like a reasonable change in this case
[12:10] <jbicha> oh, I think my ld.so error was user error since it's working fine for me now
[13:38] <seb128> smoser, re your comment from yesterday, yeah the badges on the launcher are fine if you don't autohide it ... I guess somebody could write a g-s extension that does something similar to what the messaging indicator was doing
[13:40] <smoser> g-s ?
[13:40] <smoser> gnome-..
[13:41] <seb128> gnome-shell
[13:41] <smoser> thanks.
[13:41] <seb128> yw
[13:44] <didrocks> smoser: come to our room next week, you will be used to all our acronyms you don't want to know :)
[13:44] <didrocks> (/!\ g-s can as well be gnome-session, context is important :p like for g-c-c)
[13:45] <seb128> or gnome-software
[13:45] <didrocks> oh right
[13:45] <didrocks> almost forgot that one. We need to create another project with G… S…
[13:50] <Laney> session
[13:50] <Laney> screenshot
[13:50] <Laney> shell sushi
[13:50] <Laney> :)
[13:52] <smoser> and here i thought gcc was a complier
[13:52] <smoser> lame i am
[13:57] <ogra_> it is only a compiler because it can not afford dashes ...
[13:58] <didrocks> heh
[15:37] <jtaylor> infinity: are there still glibc updates planned for 17.10?
[15:37] <jtaylor> bugfixes
[17:23] <infinity> jtaylor: There will be one or two minor bugfix uploads I'm sure, yeah.
[17:33] <jtaylor> infinity: great, can you consider the fix for bug 1718928
[17:34] <jtaylor> I can provide a patch if it helps
[17:37] <infinity> jtaylor: If the patch provided is "git show hash", I think I can figure it out. :P
[17:37] <jtaylor> though so, thanks :)
[18:07] <johnny_|_> Hi. I am trying to connect 2 4k monitors on 17.10. Sometimes I even manage to do that but right now when I connect second monitor the screen is black and I can see mouse cursor both on laptop screen and first external monitor. What to do from here?
[18:08] <wxl> johnny_|_: i'd suggest #ubuntu for support
[18:08] <wxl> johnny_|_: or perhaps #ubuntu+1 since you did say 17.10
[18:10] <johnny_|_> wxl: thanks, confused -devel with +1, sorry
[18:10] <wxl> johnny_|_: np :)