=== juliank is now known as Guest22905
tzerois 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 build03:40
cpaelzergood morning06:17
FourDollarsHow to stop/start indicator-power in zesty like `stop indicator-power` in xenial?08:01
pittiFourDollars: systemctl --user stop indicator-power08:15
FourDollarspitti: thx08:16
cjwatsontzero: 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.09:38
tvossxnox: hey there :)10:32
=== mardy_ is now known as mardy
=== _salem is now known as salem_
=== Foxtrot is now known as Guest77411
=== giraffe is now known as Guest73411
=== madwizar1 is now known as madwizard
=== rumble is now known as grumble
=== hikiko_ is now known as hikiko|ln
sil2100Hey! 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 itself13:47
Laneysil2100: component-mismatch13:49
sil2100Indeed, the ubuntu-keyboard-esperanto is a new binary package from the source13:49
LaneyDoes it want to be in universe?13:50
sil2100I think it needs to be in main as all the other ubuntu-keyboard binaries13:50
=== iahmad_ is now known as iahmad
=== BrAsS_mOnKeY is now known as g2
dokobarry: who should be the bug subscriber for python-webencodings?14:37
barrydoko: i'm happy to be that14:38
barrydoko, mterry i'll look into the tests comment14:38
dokobarry: but I'm not ;p that has to be a team ...14:38
barrydoko: well then, foundations of course!14:38
mterrybarry should be easy14:38
bluefoxxxxsanity check:  I can't find any reference to a bug about Grub giving the error:14:42
bluefoxxxxgrub-install: error: cannot open `/boot/grub/x86_64-efi/gcry_twofish.mod': No space left on device.14:42
rbasakslangasek: squid3> thank you for your reply.14:42
bluefoxxxxI've done a lot of googling and can't locate this issue.  This happens in post-install for shim-signed14:43
bluefoxxxxthe way I work around it is to copy the files manually to the destination, because the device is in no way out of space14:43
rbasakslangasek: 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
rbasakAnd it's run in set -e, so I'm surprised the postinst didn't fail.14:43
rbasakAnyway, I'll sort it out. Thank you for your help :)14:44
bluefoxxxxgrub-install just thinks it is.14:46
bluefoxxxxand ffs launchpad14:46
bluefoxxxxokay, you know what?14:46
bluefoxxxxI'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
bluefoxxxxgo to lauchpad.net14:47
bluefoxxxxclick ubuntu14:47
bluefoxxxxclick "Report a bug"14:47
bluefoxxxxi.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:48
bluefoxxxxoh, there it is14:49
bluefoxxxxthe one-hundredth link somewhere down 2/3 of the way into the page14:49
bluefoxxxxafter 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 FORM14:50
bluefoxxxxnow let's see if I can remember what I wanted to file a bug about14:50
dokoLaney: please could you override the libreoffice autopkg test for python3.5? the junit-subsequentcheck failure seems to be unrelated14:51
=== hikiko|ln is now known as hikiko
Laneydoko: ok, would appreciate it if you could ping SweetShark / file a bug & assign it though15:08
dokoLaney: he's not here, and I'm tired chasing people on various channels every time ...15:09
LaneyI'm tired of skipping tests every time too15:09
seb128doko, report a bug on launchpad instead of chasing people then15:09
sil2100Can anyone please promote the binary package ubuntu-keyboard-esperanto to main?15:09
sil2100Since all the other binaries from ubuntu-keyboard are in main already15:10
Laneysil2100: That's backwards15:11
sil2100Oh, it is, but why15:12
sil2100The ubuntu-keyboard source is in main15:12
sil2100Is there any reason why ubuntu-keyboard binaries are still in universe I wonder?15:12
srulii want to install kernel manually, is there a particular order i must install it? i have headers-, image-, image-exra, & signed-image15:24
sil2100mterry: hey! I'm wondering if you remember by any chance why ubuntu-keyboard source is in main and the binaries are still in universe15:27
seb128sil2100, binaries get only promoted if something in main depends on those15:27
seb128otherwise we keep them in universe15:28
seb128no point maintaining something in main if we don't need to15:28
mterrysil2100: yeah what seb128 said, but I don't remember why nothing depends on its binaries anymore...15:28
sil2100mterry, 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
sil2100Since the new binary is in main but causes a component mismatch as it depends on the ubuntu-keyboard binary which is still in universe15:30
sil2100And thanks for the explanation!15:30
seb128unsure who NEWed the new binary and why they put it in main15:31
seb128check with doko maybe?15:31
sil2100Isn't it automatic for new binaries for a main source package to also go to main, or something?15:31
dokoyes, it is15:31
sil2100Anyway, I'm fine with any solution just to get this package migrating15:32
gpiccoliHi, sorry to annoy. Anyone knows what means the message:15:41
gpiccoliWARNING **: Configuring 'bootstrap-base' failed15:41
gpiccolion syslog during installation? Where can I get more information on why it failed?15:42
gpiccoliSeems to me it might be a failure on grub installation15:42
SaviqLaney, after a fresh boot, dbus.log just has http://pastebin.ubuntu.com/23746715/15:53
SaviqI suppose it's a chicken-egg issue?15:54
LaneyTry reverting the upstart job15:54
sil2100fossfreedom_: hah! The budgie build seems to have moved forward finally!15:54
sil2100fossfreedom_: I see it's still in the middle of building but the livefs builds succeeded \o/15:55
sil2100fossfreedom_: so far so good thanks to cjwatson!15:55
fossfreedom_sil2100: brilliant news!!  1000 thank-you's to you and cjwatson15:56
sil2100For future's sake I'll document it somewhere on our wiki15:57
slangasekrbasak: that wasn't a cross-file move, AFAIR?16:00
SaviqLaney, 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 up16:01
Saviqmaybe the pre-start job should check for validity of the var...16:02
tzerothanks cjwatson, I'll check it out16:02
LaneySaviq: Wouldn't it be better to stop setting it to a bogus value?16:03
LaneyI guess this only worked before because the job just clobbered it16:03
SaviqLaney, sure, that, too16:03
LaneyWonder what's doing that16:03
fossfreedom_sil2100: I see the ISO :)  downloaded.  First image here http://imgur.com/Kq545ci16:04
barrymterry: thanks!16:15
dokoseb128, Laney: filed https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/165432016:19
ubottuLaunchpad bug 1654320 in libreoffice (Ubuntu) "libreoffice junit-subsequentcheck autopkg test failure" [High,New]16:19
seb128doko, thanks16:20
seb128doko, you might want to indicate in what Ubuntu serie and maybe a log url16:20
Saviqwell, kindof, commenting that line out didn't really help16:24
ogra_Saviq, theer used to be an /etc/profile.d snippet that sets it16:27
ogra_(not sure that still exists)16:27
rbasakslangasek: it seems like it was to me. I'll reply to the thread.16:29
Saviqogra_, well, yeah, that's what I commented out, wondering now where the value comes from16:31
ogra_there also used to be an Xsession.d script ... neither sure if that still exists16:32
ogra_(or if that would be even processed in your case)16:32
rbasakslangasek: I'm sorry, my mistake. It was all in squid3.postinst.16:33
rbasak(I won't email the thread then)16:34
slangasekok :)16:34
rbasakslangasek: 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:35
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:41
jbichabdmurray: 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 163786416:43
ubottubug 1644246 in iio-sensor-proxy (Ubuntu) "/usr/sbin/iio-sensor-proxy:ERROR:iio-sensor-proxy.c:186:send_dbus_event: assertion failed: (data->connection)" [High,New] https://launchpad.net/bugs/164424616:43
ubottubug 1637864 in iio-sensor-proxy (Ubuntu Yakkety) "80-iio-sensor-proxy.rules in wrong location" [High,Fix released] https://launchpad.net/bugs/163786416:43
naccjbicha: weird, i use iio-sensor-proxy on yakkety and rotation works fine16:44
jbichanacc: which version?16:44
naccjbicha: oh nm, i see, i'm running the 'fixed' version. Although i thought it has worked since i upgraded to y.16:45
jbichaI 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't16:47
slangasekbarry: NB the revert has to happen in network-manager, not in systemd16:59
pittislangasek, barry: see https://lists.ubuntu.com/archives/ubuntu-devel/2016-December/039564.html17:00
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 anymore17:08
ubottubug 1650677 in Canonical System Image "Xenial image for frieza does not have SSH configured correctly" [Undecided,New] https://launchpad.net/bugs/165067717:08
bdmurrayjbicha: I've restarted the phasing of iio-sensor-proxy17:21
SaviqLaney, *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
Saviqwill now grep through / to try and find what else might be writing to dbus-session...17:23
Saviqunless you have an idea?17:23
LaneySaviq: I sort of remember ogra_ doing something to save the DBUS_SESSION_BUS_ADDRESS17:27
Laneymaybe it's that?17:27
ogra_Laney, thats the one in /run ... and Saviq said he disabled the profile.d snippet that does this17:28
Saviqogra_, one that *saves* it? no, that I didn't find, I only saw Laney, well, I think17:28
Laneyoh right17:28
Saviqwhich *reads* it, doesn't save?17:29
ogra_oh, right ...17:29
LaneyThere was a thing to save it17:29
ogra_yeah, one sec17:29
Saviqand that's the only mention in /etc/17:29
ogra_that used to be in the ubuntu-touch-session script itself, but it is gone17:30
Saviqogra_, dbus.conf, but..17:31
Saviqthat's what's *not* writing it... and anyway the format would be different17:31
Saviqbecause the upstart job does it with mktemp /tmp/dbus.XXXX...17:32
Saviqsomething's adding the guid= there17:32
Saviqeverything else in /usr only seems to read it, nothing writes it AFAICT17:33
ogra_lifghtdm ?17:34
Saviqdoesn't look like it, nothing related in grepping the code17:35
ogra_and you are sure /etc/X11/Xsession.d/75dbus_dbus-launch is not executed ?17:35
Saviqdbus-launch? but wouldn't that call dbus-daemon anyway?17:35
ogra_(as i mentioned before)17:36
Saviqsystemd --user??17:36
Saviqagain, grep not helpful17:36
LaneyIt's written by the upstart job of dbus17:39
LaneyBut that should be the same one it launches dbus with17:39
SaviqLaney, 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
* Saviq checks again17:40
Saviqor maybe it does, because you do exec17:41
Saviqso it then does post-start17:41
Saviqok so dbus-session is a red herring17:41
Saviqwe need to find who's setting the env17:41
SaviqLaney, yes it is the upstart job that's writing it17:43
* Saviq was chasing the wrong thread17:43
LaneySaviq: The problem is that it's already set in the environment earlier on, right?17:44
Laneyso the new job thinks it doesn't need to launch one17:44
Saviqgot it17:45
Saviqit's systemd17:46
Saviqit even has a FIXME there...17:47
Saviqgrr where do I find the code repo for the package :/17:49
Laneyfor systemd?17:50
SaviqLaney, ogra_ https://github.com/systemd/systemd/blob/master/src/login/pam_systemd.c#L17717:50
Laneythat sets it to $XDG_RUNTIME_DIR/bus no?17:51
Saviqlightdm's setting it, but only to a value that's already there...17:54
Saviqok it's dbus-server's value17:57
Saviqquestion is now who's setting the env with it17:58
Laneylook at upstart's /proc/pid/environ to see if it came earlier than upstart, maybe18:02
Laneygot to run, might be back later18:03
Saviqyeah it did18:03
=== Skuggen_ is now known as Skuggen
Saviqok it is systemd18:11
barrypitti, slangasek yep18:15
cjwatsonogra_: 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:24
cjwatsonogra_: anything which you observed doing that in the past was outside of the openssh package, and either without my knowledge or over my objections18:25
cjwatsonogra_: it should be done at imaging time or similar instead18:25
* cjwatson feeds that into the bug18:26
ogra_cjwatson, oh, ok ... yeah, then it was at imaging time or so18:38
ogra_cjwatson, thanks for taking the time :)18:39
cjwatsonalways happy to play whack-a-mole with dangerous plans ;-)18:40
SaviqLaney, ogra_, ok found the real problem: http://pastebin.ubuntu.com/23747890/18:59
Saviqthis 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 dies19:00
Saviqcommenting out #use-session-dbus in /etc/X11/Xsession.options makes everything work again, but I'm not sure that's what we actually want19:01
Saviqjibel, sil2100 ↑19:01
* Saviq filing a bug19:01
SaviqLaney, 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 place19:18
SaviqLaney, ogra_, bug #165436519:27
ubottubug 1654365 in ubuntu-touch-session (Ubuntu) "Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies immediately" [Undecided,New] https://launchpad.net/bugs/165436519:27
Saviqmterry, do you have enough lightdm/ubuntu-touch-session knowledge to shed more light ↑?19:28
Saviqor do we need Robert?19:28
* mterry reads19:28
mterrySaviq: no I don't know off hand why dbus is dying so quickly19:34
mterryI do suspect that the Xsession.d files are deprecatable19:36
mterryUpstart or systemd should be triggers for dbus these days I'd think19:36
Saviqmterry, 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:38
Saviqjust added note of this workaround19:40
fossfreedomPlease can someone add Ubuntu Budgie to the ISO tracker? TIA http://iso.qa.ubuntu.com/qatracker21:14
=== salem_ is now known as _salem

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!