=== _salem is now known as salem_
=== salem_ is now known as _salem
=== Malsasa is now known as Guest82745
=== Malsasa_ is now known as Malsasa
=== work_alkisg is now known as alkisg
[03:57] <alkisg> upstart needs /sbin in its path to work (/etc/X11/Xsession.d/99upstart). ssh, sudo, lightdm etc all put /sbin in the user's path. `su -` doesn't put it, it uses the values from /etc/login.defs instead of /etc/environment, so one cannot launch upstart if he logged in with `su -`.
[03:58] <alkisg> That affects us in LTSP were we're using our own DM. We can work around it, but it does sound like inconsistent behaviour, should I file a bug against upstart or su?
[04:04] <micahg> based on the man page, sounds like a bug against su
[04:04] <micahg> well, there's at least the bug against su, can't speak for upstart's proper behaviour
[04:13] <alkisg> Thank you micahg, I'll file a bug against it
[04:24] <alkisg> xnox, good morning, I've filed LP #1457730 about what we were talking about 2 days ago, feel free to close it as "won't fix" if you prefer, but I wanted to document it so that I mention why the workaround is needed in the LTSP changelog. I hope you know I appreciate you and thanks for the time you've dedicated in chatting about it with me.
[04:24] <ubottu> Launchpad bug 1457730 in upstart (Ubuntu) "Upstart packaging conflicts with man Xsession" [Undecided,New] https://launchpad.net/bugs/1457730
[04:29] <pitti> Good morning
[06:21] <Mirv> I wonder if anyone has wily in an lxc working? just checking. I just get "E: Method http has died unexpectedly" when attached and trying apt update :(
[06:30] <Mirv> oh, interestingly it's just my lack of lxc skills, but seems like downgrading apt to the previous version works
[06:30] <Mirv> s/just/not just/
[06:32] <Mirv> I filed bug #1457754 , triaging help welcome since I have no idea what's happening in there
[06:32] <ubottu> bug 1457754 in apt (Ubuntu) ""E: Method http has died unexpectedly" when run under lxc on wily apt 1.0.9.9ubuntu1" [Undecided,New] https://launchpad.net/bugs/1457754
=== work_alkisg is now known as alkisg
[07:35] <zequence> Can I request backports from Vivid to Trusty at this time?
[07:36] <zequence> Seems like every time there is a new non-LTS release, you don't really want to backport to the latest non-LTS release
[07:36] <zequence> Only to the LTS
=== oSoMoN_ is now known as oSoMoN
[07:37] <zequence> I know in the past you had to backport in the correct order, like Vivid -> Utopic -> Trusyt
[07:41] <zequence> We might want to do a bunch (The Ubuntu Studio dev team), and we're not really that interested in backporting to Utopic
[07:46] <pitti> zequence: AFAICS the problem there is primarily to ensure that utopic has a newer version than trusty
[07:46] <pitti> zequence: otherwise, if you backport to trusty from vivid, install that, and upgrade to utopic there is no version for that package, and it might not even be installable any more
[07:46] <pitti> (i. e. conflict because of changed libraries, etc.)
[07:47] <zequence> pitti: Ah, right.
=== iulian is now known as Guest6655
[08:59] <Mirv> stgraber: you may not have gotten enough thanks yet for your lxc blog series, so here's +1!
[10:00] <cjwatson> tedg: dbus-test-runner/amd64 did build cleanly in the end.  Must have been a race of some kind ...
=== oSoMoN__ is now known as oSoMoN
=== alkisg is now known as work_alkisg
[11:01] <Mirv> ok, that mix of -fPIC/-fPIE patches was not perfect after all
[11:03] <Mirv> mitya57: since we need to keep -reduce-relocations not set (so not enforcing) and have -fPIE on arm, do you see any other option out than to actually do what I was already doing, ie keep all of the patches disabled?
[11:23] <mitya57> Mirv: I think it's OK to disable them until we find a better way to fix that
[11:23] <mitya57> But those patches are applied upstream in 5.4.2 anyway
[11:27] <Mirv> so they are
=== soee_ is now known as soee
=== _salem is now known as salem_
=== gammax90 is now known as gammax
=== oSoMoN_ is now known as oSoMoN
=== work_alkisg is now known as alkisg
=== oSoMoN_ is now known as oSoMoN
=== oSoMoN__ is now known as oSoMoN
[16:44] <LocutusOfBorg1> Oh bad I can't install xserver-xorg-dev on a clean 14.04.2 machine
[16:44] <LocutusOfBorg1> the usual xorg backport, I'm wondering *why* people backport it :)
[16:44] <LocutusOfBorg1> giving me bugs like 1424769
[16:46] <LocutusOfBorg1> so I have bug 1457776, but I can't fix it because of impossibility to satisfy build-depends
[16:47] <ubottu> bug 1358157 in virtualbox (Ubuntu) "duplicate for #1457776 virtualbox-dkms 4.3.10-dfsg-1: virtualbox kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]" [High,Invalid] https://launchpad.net/bugs/1358157
[16:48] <LocutusOfBorg1> anyway time lo leave
[16:48] <LocutusOfBorg1> bye folks
=== alkisg is now known as work_alkisg
=== oSoMoN_ is now known as oSoMoN
[17:22] <rcj> wgrant, How can I delete an LP git repo created in error https://code.launchpad.net/~rcj/open-vm-tools/+git/open-vm-tools
[17:31] <cjwatson> rcj: You can't yet, but I have approved branches ready to land to fix that.
[17:31] <cjwatson> rcj: Should roll out next week.
[17:31] <cjwatson> rcj: Once it rolls out, there'll be a nice obvious "Delete repository" link at the top right there.
[18:46] <rcj> cjwatson, thanks
=== oSoMoN_ is now known as oSoMoN
=== salem_ is now known as _salem
[21:31] <taggart> kees, cjwatson: does ubuntu use sshd_config DebianBanner?