[03:40] <tzero> is there a suggested way to confine the "buildroot" of the package to a subdirectory under debian/ ? Up until now, an `rsync --delete debian/` from the host OS to a ubuntu VM to avoid subsequent `dpkg-buildpackage` runs from complaining about the extraneous files under debian/ from the prior build
[06:17] <cpaelzer> good morning
[08:01] <FourDollars> How to stop/start indicator-power in zesty like `stop indicator-power` in xenial?
[08:15] <pitti> FourDollars: systemctl --user stop indicator-power
[08:16] <FourDollars> pitti: thx
[09:38] <cjwatson> tzero: It depends on the upstream build system that's involved, but you should probably look into the "BUILD SYSTEM OPTIONS" section of debhelper(7) for building blocks you can use.  And of course you should make sure that your clean target cleans up after the build, rather than relying on rsync --delete.
[10:32] <tvoss> xnox: hey there :)
[13:47] <sil2100> Hey! Does anyone know why http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-keyboard is blocked in proposed? It the ubuntu-keyboard package the depends are unsatisfiable is provided by the source itself
[13:49] <Laney> sil2100: component-mismatch
[13:49] <sil2100> Ah!
[13:49] <sil2100> Indeed, the ubuntu-keyboard-esperanto is a new binary package from the source
[13:50] <Laney> Does it want to be in universe?
[13:50] <sil2100> I think it needs to be in main as all the other ubuntu-keyboard binaries
[14:37] <doko> barry: who should be the bug subscriber for python-webencodings?
[14:38] <barry> doko: i'm happy to be that
[14:38] <barry> doko, mterry i'll look into the tests comment
[14:38] <doko> barry: but I'm not ;p that has to be a team ...
[14:38] <barry> doko: well then, foundations of course!
[14:38] <mterry> barry should be easy
[14:38] <doko> ok
[14:42] <bluefoxxxx> sanity check:  I can't find any reference to a bug about Grub giving the error:
[14:42] <bluefoxxxx> grub-install: error: cannot open `/boot/grub/x86_64-efi/gcry_twofish.mod': No space left on device.
[14:42] <rbasak> slangasek: squid3> thank you for your reply.
[14:43] <bluefoxxxx> I've done a lot of googling and can't locate this issue.  This happens in post-install for shim-signed
[14:43] <bluefoxxxx> the way I work around it is to copy the files manually to the destination, because the device is in no way out of space
[14:43] <rbasak> slangasek: so if the update-rc.d line moved from squid3.postinst, I think it was a no-op before because it is defined not to work if /etc/init.d/squid3 exists, and that's exactly what squid3.postinst tested for first.
[14:43] <rbasak> And it's run in set -e, so I'm surprised the postinst didn't fail.
[14:44] <rbasak> Anyway, I'll sort it out. Thank you for your help :)
[14:46] <bluefoxxxx> grub-install just thinks it is.
[14:46] <bluefoxxxx> and ffs launchpad
[14:46] <bluefoxxxx> okay, you know what?
[14:47] <bluefoxxxx> I'm just pasting the output here instead of filing a bug in launchpad because whoever designed the "file a bug" ui in launchpad obviously didn't want people going to launchpad to file bugs!
[14:47] <bluefoxxxx> go to lauchpad.net
[14:47] <bluefoxxxx> click ubuntu
[14:47] <bluefoxxxx> click "Report a bug"
[14:47] <bluefoxxxx> https://help.ubuntu.com/community/ReportingBugs
[14:48] <bluefoxxxx> i.e. "Fuck off, we don't want you reporting bugs, so we'll give you this wall of text with no obvious way to get into the bug tracker and enter bug details!"
[14:49] <bluefoxxxx> oh, there it is
[14:49] <bluefoxxxx> the one-hundredth link somewhere down 2/3 of the way into the page
[14:50] <bluefoxxxx> after re-reading that page several times over about a dozen visits spanned across months, I found the link that takes me to the ACTUAL BUG REPORTING FORM
[14:50] <bluefoxxxx> hooray
[14:50] <bluefoxxxx> now let's see if I can remember what I wanted to file a bug about
[14:51] <doko> Laney: please could you override the libreoffice autopkg test for python3.5? the junit-subsequentcheck failure seems to be unrelated
[15:08] <Laney> doko: ok, would appreciate it if you could ping SweetShark / file a bug & assign it though
[15:09] <doko> Laney: he's not here, and I'm tired chasing people on various channels every time ...
[15:09] <Laney> I'm tired of skipping tests every time too
[15:09] <seb128> doko, report a bug on launchpad instead of chasing people then
[15:09] <sil2100> Can anyone please promote the binary package ubuntu-keyboard-esperanto to main?
[15:10] <sil2100> Since all the other binaries from ubuntu-keyboard are in main already
[15:11] <Laney> sil2100: That's backwards
[15:12] <sil2100> Oh, it is, but why
[15:12] <sil2100> The ubuntu-keyboard source is in main
[15:12] <sil2100> Is there any reason why ubuntu-keyboard binaries are still in universe I wonder?
[15:24] <sruli> i want to install kernel manually, is there a particular order i must install it? i have headers-, image-, image-exra, & signed-image
[15:27] <sil2100> mterry: hey! I'm wondering if you remember by any chance why ubuntu-keyboard source is in main and the binaries are still in universe
[15:27] <seb128> sil2100, binaries get only promoted if something in main depends on those
[15:28] <seb128> otherwise we keep them in universe
[15:28] <seb128> no point maintaining something in main if we don't need to
[15:28] <mterry> sil2100: yeah what seb128 said, but I don't remember why nothing depends on its binaries anymore...
[15:30] <sil2100> mterry, seb128: ok, so I would like to request someone to either promote ubuntu-keyboard binaries to main or downgrade the new ubuntu-keyboard-esperanto binary to universe - whichever is more conveninent :)
[15:30] <sil2100> Since the new binary is in main but causes a component mismatch as it depends on the ubuntu-keyboard binary which is still in universe
[15:30] <sil2100> And thanks for the explanation!
[15:31] <seb128> unsure who NEWed the new binary and why they put it in main
[15:31] <seb128> check with doko maybe?
[15:31] <sil2100> Isn't it automatic for new binaries for a main source package to also go to main, or something?
[15:31] <doko> yes, it is
[15:32] <sil2100> Anyway, I'm fine with any solution just to get this package migrating
[15:41] <gpiccoli> Hi, sorry to annoy. Anyone knows what means the message:
[15:41] <gpiccoli> WARNING **: Configuring 'bootstrap-base' failed
[15:42] <gpiccoli> on syslog during installation? Where can I get more information on why it failed?
[15:42] <gpiccoli> Seems to me it might be a failure on grub installation
[15:53] <Saviq> Laney, after a fresh boot, dbus.log just has http://pastebin.ubuntu.com/23746715/
[15:54] <Saviq> I suppose it's a chicken-egg issue?
[15:54] <Laney> Try reverting the upstart job
[15:54] <sil2100> fossfreedom_: hah! The budgie build seems to have moved forward finally!
[15:55] <sil2100> fossfreedom_: I see it's still in the middle of building but the livefs builds succeeded \o/
[15:55] <sil2100> fossfreedom_: so far so good thanks to cjwatson!
[15:56] <fossfreedom_> sil2100: brilliant news!!  1000 thank-you's to you and cjwatson
[15:57] <sil2100> For future's sake I'll document it somewhere on our wiki
[16:00] <slangasek> rbasak: that wasn't a cross-file move, AFAIR?
[16:01] <Saviq> Laney, confirmed, reverting the job makes it start, what I'm seeing happen is that DBUS_SESSION_BUS_ADDRESS is already set, but it's not running, it's likely some intricacy of how the touch session is set up
[16:02] <Saviq> maybe the pre-start job should check for validity of the var...
[16:02] <tzero> thanks cjwatson, I'll check it out
[16:03] <Laney> Saviq: Wouldn't it be better to stop setting it to a bogus value?
[16:03] <Laney> I guess this only worked before because the job just clobbered it
[16:03] <Saviq> Laney, sure, that, too
[16:03] <Laney> Wonder what's doing that
[16:04] <fossfreedom_> sil2100: I see the ISO :)  downloaded.  First image here http://imgur.com/Kq545ci
[16:04] <sil2100> \o/
[16:15] <barry> mterry: thanks!
[16:16] <mterry> :)
[16:19] <doko> seb128, Laney: filed https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1654320
[16:20] <seb128> doko, thanks
[16:20] <seb128> doko, you might want to indicate in what Ubuntu serie and maybe a log url
[16:24] <Saviq> well, kindof, commenting that line out didn't really help
[16:27] <ogra_> Saviq, theer used to be an /etc/profile.d snippet that sets it
[16:27] <ogra_> (not sure that still exists)
[16:29] <rbasak> slangasek: it seems like it was to me. I'll reply to the thread.
[16:31] <Saviq> ogra_, well, yeah, that's what I commented out, wondering now where the value comes from
[16:31] <ogra_> ah
[16:32] <ogra_> there also used to be an Xsession.d script ... neither sure if that still exists
[16:32] <ogra_> (or if that would be even processed in your case)
[16:33] <rbasak> slangasek: I'm sorry, my mistake. It was all in squid3.postinst.
[16:34] <rbasak> (I won't email the thread then)
[16:34] <slangasek> ok :)
[16:35] <rbasak> slangasek: I think my statement that it couldn't have worked before still applies, but I can raise that with Debian separately. Either way I agree we can drop it now.
[16:41] <fossfreedom_> open question to anyone - during an ISO build - is there a way to blacklist (i.e. not install) a package that is normally installed because it is a recommended package of another package?
[16:43] <jbicha> bdmurray: could you help iio-sensor-proxy through phased-updates? the error isn't new, but I guess the error signature changed and I think yakkety's release version didn't work at all, bug 1644246 & bug 1637864
[16:44] <nacc> jbicha: weird, i use iio-sensor-proxy on yakkety and rotation works fine
[16:44] <jbicha> nacc: which version?
[16:45] <nacc> jbicha: oh nm, i see, i'm running the 'fixed' version. Although i thought it has worked since i upgraded to y.
[16:47] <jbicha> I like the idea of phased-updates but for things that get stuck, it splits the userbase between those who use only update-manager to install updates and those who don't
[16:59] <slangasek> barry: NB the revert has to happen in network-manager, not in systemd
[17:00] <pitti> slangasek, barry: see https://lists.ubuntu.com/archives/ubuntu-devel/2016-December/039564.html
[17:08] <ogra_> cjwatson, hmm, did sshd startup behaviour change with the switch to systemd ? i remember in the past the sysv/upstart scripts created a host cert if there wasnt one by default on first start of a new image ... bug 1650677 looks like that isnt the case anymore
[17:21] <bdmurray> jbicha: I've restarted the phasing of iio-sensor-proxy
[17:23] <Saviq> Laney, *something* is writing to $XDG_RUNTIME_DIR/dbus-session, but dbus-daemon is never launched with that socket... (I've hacked the dbus-daemon binary to log into /tmp) http://pastebin.ubuntu.com/23747444/
[17:23] <Saviq> will now grep through / to try and find what else might be writing to dbus-session...
[17:23] <Saviq> unless you have an idea?
[17:27] <Laney> Saviq: I sort of remember ogra_ doing something to save the DBUS_SESSION_BUS_ADDRESS
[17:27] <Laney> maybe it's that?
[17:28] <ogra_> Laney, thats the one in /run ... and Saviq said he disabled the profile.d snippet that does this
[17:28] <Saviq> ogra_, one that *saves* it? no, that I didn't find, I only saw Laney, well, I think
[17:28] <Laney> oh right
[17:28] <Saviq> http://bazaar.launchpad.net/~phablet-team/ubuntu-touch-session/trunk/view/head:/etc/profile.d/dbus-source.sh
[17:29] <Saviq> which *reads* it, doesn't save?
[17:29] <ogra_> oh, right ...
[17:29] <Laney> There was a thing to save it
[17:29] <ogra_> yeah, one sec
[17:29] <Saviq> and that's the only mention in /etc/
[17:30] <ogra_> that used to be in the ubuntu-touch-session script itself, but it is gone
[17:31] <Saviq> ogra_, dbus.conf, but..
[17:31] <Saviq> that's what's *not* writing it... and anyway the format would be different
[17:32] <Saviq> because the upstart job does it with mktemp /tmp/dbus.XXXX...
[17:32] <Saviq> something's adding the guid= there
[17:32] <Saviq> http://pastebin.ubuntu.com/23747444/
[17:33] <Saviq> everything else in /usr only seems to read it, nothing writes it AFAICT
[17:34] <ogra_> lifghtdm ?
[17:35] <Saviq> doesn't look like it, nothing related in grepping the code
[17:35] <ogra_> and you are sure /etc/X11/Xsession.d/75dbus_dbus-launch is not executed ?
[17:35] <Saviq> dbus-launch? but wouldn't that call dbus-daemon anyway?
[17:36] <ogra_> (as i mentioned before)
[17:36] <Saviq> systemd --user??
[17:36] <Saviq> again, grep not helpful
[17:39] <Laney> It's written by the upstart job of dbus
[17:39] <Laney> But that should be the same one it launches dbus with
[17:40] <Saviq> Laney, well, it's *not* written in this case, since it's prepopulated and the job does "sleep infinity" in that case, so post-start never runs?
[17:40] <Laney> Oh?
[17:40]  * Saviq checks again
[17:41] <Saviq> or maybe it does, because you do exec
[17:41] <Saviq> so it then does post-start
[17:41] <Saviq> ok so dbus-session is a red herring
[17:41] <Saviq> we need to find who's setting the env
[17:43] <Saviq> correct
[17:43] <Saviq> Laney, yes it is the upstart job that's writing it
[17:43]  * Saviq was chasing the wrong thread
[17:44] <Laney> Saviq: The problem is that it's already set in the environment earlier on, right?
[17:44] <Saviq> yes
[17:44] <Laney> so the new job thinks it doesn't need to launch one
[17:45] <Saviq> got it
[17:46] <Saviq> it's systemd
[17:47] <Saviq> it even has a FIXME there...
[17:49] <Saviq> grr where do I find the code repo for the package :/
[17:50] <Laney> for systemd?
[17:50] <Saviq> Laney, ogra_ https://github.com/systemd/systemd/blob/master/src/login/pam_systemd.c#L177
[17:50] <ogra_> hah
[17:51] <Laney> that sets it to $XDG_RUNTIME_DIR/bus no?
[17:53] <Saviq> indeed
[17:54] <Saviq> lightdm's setting it, but only to a value that's already there...
[17:55] <Saviq> http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/view/head:/src/seat.c#L878
[17:57] <Saviq> ok it's dbus-server's value
[17:58] <Saviq> https://cgit.freedesktop.org/dbus/dbus/tree/dbus/dbus-server.c#n70
[17:58] <Saviq> question is now who's setting the env with it
[18:02] <Laney> look at upstart's /proc/pid/environ to see if it came earlier than upstart, maybe
[18:03] <Laney> got to run, might be back later
[18:03] <Saviq> yeah it did
[18:11] <Saviq> ok it is systemd
[18:15] <barry> pitti, slangasek yep
[18:24] <cjwatson> ogra_: none of my sysv/upstart jobs ever created host keys at boot time; I have specifically nacked that multiple times because the time you exactly shouldn't generate host keys is at boot when the system is low on entropy (there is academic research about how that particular idea leads to weak keys in the wild)
[18:25] <cjwatson> ogra_: anything which you observed doing that in the past was outside of the openssh package, and either without my knowledge or over my objections
[18:25] <cjwatson> ogra_: it should be done at imaging time or similar instead
[18:26]  * cjwatson feeds that into the bug
[18:30] <cjwatson> (https://factorable.net/weakkeys12.conference.pdf)
[18:38] <ogra_> cjwatson, oh, ok ... yeah, then it was at imaging time or so
[18:39] <ogra_> cjwatson, thanks for taking the time :)
[18:40] <cjwatson> always happy to play whack-a-mole with dangerous plans ;-)
[18:59] <Saviq> Laney, ogra_, ok found the real problem: http://pastebin.ubuntu.com/23747890/
[19:00] <Saviq> this spawns dbus with --exit-with-session, which in the case of a unity8-touch-session seems to happen right after, so DBUS_SESSION_BUS_ADDRESS is left in the environment, but the dbus it launched dies
[19:01] <Saviq> commenting out #use-session-dbus in /etc/X11/Xsession.options makes everything work again, but I'm not sure that's what we actually want
[19:01] <Saviq> jibel, sil2100 ↑
[19:01]  * Saviq filing a bug
[19:18] <Saviq> Laney, in any case, I think there's a bug in your dbus.conf - if you stop/start it, it won't launch it even if it was the one that launched it in the first place
[19:27] <Saviq> Laney, ogra_, bug #1654365
[19:28] <Saviq> mterry, do you have enough lightdm/ubuntu-touch-session knowledge to shed more light ↑?
[19:28] <Saviq> or do we need Robert?
[19:28]  * mterry reads
[19:34] <mterry> Saviq: no I don't know off hand why dbus is dying so quickly
[19:36] <mterry> I do suspect that the Xsession.d files are deprecatable
[19:36] <mterry> Upstart or systemd should be triggers for dbus these days I'd think
[19:38] <Saviq> mterry, sure, we can actually make that happen by just disabling the dbus thing in Xsessions, but that means the rest of those scripts don't get the full env (not sure if it matters much, but still)
[19:40] <Saviq> just added note of this workaround
[21:14] <fossfreedom> Please can someone add Ubuntu Budgie to the ISO tracker? TIA http://iso.qa.ubuntu.com/qatracker