naccrbasak: i think i got ubuntu/devel working :)00:22
naccrbasak: will talk w/ you in the am on it, i think i got barry's bug fixed too, as well as the isc-dhcp import00:48
pittiGood morning05:00
infinitypitti: Morning.05:13
infinitypitti: Kernel attempt number 2 in progress.  Turns out that changing CC in the top level Makefile blows up dksm. :/05:13
infinitydkms, too.05:13
infinityQt will migrate today if I have to jam it in with a fork.05:18
* pitti hands infinity some lube too05:19
sarnolddon't force it, get a bigger hammer05:22
infinitypitti: Witness the horror: http://paste.ubuntu.com/23066399/05:22
infinityexport SHELL=env PATH=$(PWD)/debian/compiler:$(PATH) /bin/bash -e05:23
* infinity shudders.05:23
pittithat's a curious ABI bump05:23
pitti9034 → 9134?05:23
infinitypitti: 34.53 matches the xenial source.05:23
pittiusing gcc 6 instead of 5 changes ABI?05:23
infinitypitti: 90/91 was me making the ABI not clash with xenial.05:23
pittiln -s /usr/bin/gcc-5 debian/compiler/gcc05:24
pittielegant! *cough*05:24
infinitypitti: No, not actually an ABI change, but ABI == package name, they have to be unique these days for other reasons (signed modules, for one)05:24
infinityThe days of ABI tracking are dead.  Unless we move to using a central signing key for modules.05:25
infinityBut for now, because of the baked in ephemeral key, every kernel needs to be a unique "abi".05:25
infinitypitti: And yes, "elegant". :P05:25
infinitypitti: Though, I might clean it up and propose something similar but more robust for compiler switching.  Specifying CC breaks some of upstream's Makefiles (a joyous bug I won't bother hunting down), and changing CC in the top level Makefile breaks installed kbuild (ie: dkms), so...05:26
pittisergiusens: FYI, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#snapcraft test fails06:46
Unit193pitti: BTW, with upstart user sessions, dbus-launh would launch an application in a new session or something such that the new application was unaware of other applications.  With the new systemd/dbus-user-session, that and unsetting DBUS_SESSION_BUS_ADDRESS no longer work.  Do you know how I can do this?06:48
pittiUnit193: that's not the same -- dbus-launch starts a new (local) bus and sets D_S_B_A to *that* address; that should continue to work as before06:50
pittiUnit193: *unsetting* D_S_B_A will just make applications use the builtin $XDG_RUNTIME_DIR/bus default06:50
Unit193Hrm, neither are working now as a workaround.06:51
pittineither of this is a function of how you start the session -- most probably this changed with installing dbus-user-session06:51
Unit193I figured it was from dbus-user-session, aye.  But clearly I don't know dbus magic. :)06:51
pittiwhat are you tryign to do?06:51
Unit193There's a workaround to get dropbox to show up correctly, but it's to force it out of indicator-application and use its trayicon, otherwise you get an IMAGENOTFOUND icon and a non-functioning menu.06:53
pittiUnit193: and "DBUS_SESSION_BUS_ADDRESS=invalid dropbox" doesn't work? I tried "dbus-launch --exit-with-session d-feet" and that runs in its own private session bus world as expected06:55
Unit193pitti: Correct.06:56
pittiI figure actually launching a new bus is moot as dropbox then can't communicate with anything else anyway -- so just using an invalid address is simpler06:58
Unit193pitti: Eh, I'll just nuke XDG_RUNTIME_DIR for now instead I guess.07:02
pittiUnit193: that's much worse, but if you know what you are doing, sure :)07:02
Unit193pitti: Dropbox is entirely weird, it has /usr/bin/dropbox, which launches ~/.dropbox-dist/dropboxd, which launches another script, which finally launches the actual process.  If I set the env in the uppermost script, I should still get a functional dropbox without breaking too much, I'd think.07:04
pitticjwatson: FYI, I just committed http://bazaar.launchpad.net/~ubuntu-archive/ddeb-retriever/trunk/revision/171 to ignore wily as a supported release; this should hopefully stop the cron spam07:04
pitti(not sure why it can't be marked as obsolete yet, but I suppose there are reasons)07:05
infinitypitti: There's a reason, it's just my TODO list being too long, and some things I need to clean up before I disable it.07:11
infinitypitti: Sorry it was causing backscatter.07:11
pittiinfinity: no problem, it's an easy enough workaround07:13
pitticjwatson, infinity: is there some way to find out what pulls p3-lp into standard now? http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt07:37
pittithis will affect containers as well, and might not be intended07:37
pittioh, I think update-manager-core (in standard seed) → python3-update-manager → python3-launchpadlib07:41
pittibut python-launchpadlib has been optional forever, even in xenial07:41
pittiok, that came from http://launchpadlibrarian.net/275354292/update-manager_1%3A16.10.2_1%3A16.10.3.diff.gz07:42
pitti"Attempt to retrieve Changelogs from PPA sources"07:43
tsdgeosis libreoffice-writer crashing in yakkety for anyone else?08:01
jibeldoko, hey, could you help with bug 1613602 to understand where the problem is, if it's libc or something else?08:15
ubottubug 1613602 in Canonical System Image "repowerd crashes on xenial/arm64" [Critical,New] https://launchpad.net/bugs/161360208:15
jibeldoko, alf and vicamo can provide more info if needed08:15
mwhudsonhow do i see the default gcc flags? (i.e. the place where pie got turned on for s390x in 16.04)08:22
juliankI feel like the arm64 build is going weird, it's printing "INFO: pkgstripfiles: waiting for lock (apt-transport-https) ..."  since a minute or so https://launchpad.net/ubuntu/+source/apt/1.3~rc2ubuntu1/+build/1063145908:24
brendandhas anyone been using the nose-subunit plugin successfully recently? my attempts to install it have been underwhelming08:24
juliankI guess I'll restart the build and hope for more luck this time08:25
juliankHmm, now it's cancelling stuff since a minute or so08:30
juliankwell, seems to have been cancelled. retrying now. let's hope it works better this time ...08:32
dokojibel: glibc should be infinity's expertise. but I can have a look tomorrow08:57
dokomwhudson, compile and link a helloworld.c with -v and look for the flags08:58
xnoxmwhudson, PIE is on by default in the toolchain for s390x in 16.04, in 16.10 it's also on for amd64 and ppc64el.09:03
dokoahh, yes, we even have a wiki page documenting these ...09:03
mwhudsonxnox, doko: context is https://github.com/golang/go/issues/1678009:09
mwhudsonwhich i think roughly speaking means "-fdebug-prefix-map doesn't work"09:10
mwhudsonbut only on s390x!09:10
mwhudsonwhich makes no sense09:10
jibelinfinity, any insight on bug 1613602?10:07
ubottubug 1613602 in Canonical System Image "repowerd crashes on xenial/arm64" [Critical,New] https://launchpad.net/bugs/161360210:07
infinityjibel: Nothing immediately leaps to mind.10:08
infinityjibel: I can look more $later, but not sure precisely when $later will be.10:08
infinityLaney: The default gedit colour scheme has a transparent background.  That can't be right. :P10:10
jibelinfinity, that's fine as long as later != infinity10:10
infinityjibel: infinity would be an awful result indeed.  The last thing I want to do is examine the same bug at every point in time.10:10
infinityMaybe that's what hell is.10:11
Laneyinfinity: Not seen that, will check on an iso or something later10:15
infinityLaney: I thought it might be a bad local mapping of old setting or something, but if you go to preferences, colours, and click the schemes/themes (which I would expect would reset any bad settings I have?), they all seem to work fine, but the top one has a transparent window.10:16
infinityAnd the top is, I assume, also the default.  It is here anyway.10:16
infinityLaney: Also an entertaining menu re-rendering bug (which I'm guessing is the theme's fault?) where hilighting a menu item makes the menu grow in size slightly...10:18
LaneyIt looks right on a live session :(10:18
LaneyYes, that one is known10:18
infinityLaney: Hrm.  The gedit thing is fine in live?  Great.  I'll try a fresh profile at some point, but if it's an upgrade bug, that's icky.10:19
LaneyThose are my known issues10:19
infinityLaney: Handy.  I'll keep that card open and only bug you when something is either not there or listed fixed and clearly not. :)10:20
LaneyTry gedit in a guest session10:20
LaneyMaybe something's held back pre-3.20 or whatever10:20
infinityLaney: Guest session is fine.10:29
infinityLaney: Which implies an upgrade bug.  But I haven't exactly customized gedit or anything.  I only use it for quick throwaway notes.10:29
Laneyinfinity: Meh, keep the bug around and let me see it when we're next in the same place10:35
xnoxMirv, i'm getting QT_QT_INCLUDE_DIR set to NOTFOUND building against Qt4 in calligra10:36
xnoxnever mind, i have qt5 installed as well.10:37
Mirvcalligra is removed from Debian it seems10:38
xnoxit's not.10:39
xnoxit's in unstable.10:39
xnoxbut yeah, it is not in a nice state at the moment.10:40
Mirvcorrect, just looking regarding release. it seems there's some 2.9 packaging in there but not finished or touched since 2015.10:40
Mirv(I was mostly curious there is still some software using Qt 4 which should be on its way out)10:40
xnoxubuntu is on 2.9 series10:40
xnoxi wonder what happened. I guess libreoffice got better kde/qt integration and people gave up on calligra?10:41
xnoxit is ex-KOffice, right?10:41
MirvI think Calligra was funded by Nokia until... not anymore, maybe it's been searching for itself a bit and with less resources10:42
xnoxah, did not know about nokia funding10:42
Mirvso calligra was also more mobile oriented and was running on Nokia N9 as the document viewer10:42
Mirvbut indeed LO is starting to cover all those corners now10:42
xnoxanyway, i have an umbigious reference between "half" and "Eigen::half_impl::half" to fix. Silly OpenEXR not using a namespace.10:43
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
mdeslaurslangasek: I'm going to need some help from someone to figure out why libgcrypt20 isn't building on armhf anymore in xenial: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/1062882311:53
mdeslaurslangasek: unfortunately, it's an urgent update11:53
mdeslaurslangasek: could you please tell me who I can ask?11:54
ogra_does anyone else see apparmor hangs in 16.04 upgrades today ?11:59
ogra_i see a kernel oops during the apparmor package postinst on two 16.04 machines i upgraded today11:59
ogra_involving an uncloseable update-manager too11:59
ogra_bug 161445912:00
ubottubug 1614459 in apparmor (Ubuntu) "daily upgrade on 16.04 hangs" [Undecided,New] https://launchpad.net/bugs/161445912:00
infinitycjwatson: What conclusion did we draw the last time we talked about alignment on armhf on arm64 kernels?12:02
infinitycjwatson: Looks like mdeslaur is seeing SIGBUSes in libgcrypt that (presumably) were being fixed up or ignored before. :/12:03
mdeslaurinfinity: fixed up by what?12:04
infinitymdeslaur: Anyhow, short story, gcrypt has alignment bugs.  Long story, it seems our armv7 kernels were fixing those up instead of throwing bus errors, and our arm64 kernels aren't (or can't).12:04
mdeslauroh, huh12:04
ogra_SRU team ... see above bug please (havent heard of anyone else who can reproduce it yet, but i have seen it on two machines now)12:04
jibeltyhicks, hey, can you have a look at the bug ogra pasted earlier? 1614459 it's a regression in xenial12:05
infinitymdeslaur: I'll note that yakkety doesn't seem to have said problem, so finding the commit(s) that fixed the alignment bug(s) might not be too hard.12:05
mdeslauryeah, possibly http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=a6158a01a4d81a5d862e1e0a60bfd6063443311d and http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=1111d311fd6452abd4080d1072c75ddb1b5a3dd112:06
mdeslaurI'll try backporting those12:06
MirvLaney: both http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-ui-toolkit and the -gles would be there now for the --all-proposed run of unity812:06
Laneyhuh, I thought I did it12:07
Laneylemme see12:07
infinitymdeslaur: It was probably a mistake for us to ever have kernels that fixed up alignment errors on ARM in the first place, but now here we are.12:07
infinityThose traps are super expensive, we were just hurting ourselves by not catching the bugs.12:08
LaneyMirv: there we go12:09
mdeslaurinfinity: thanks for the hint12:10
Laneyit's disappeared12:13
cjwatsoninfinity: https://bugs.launchpad.net/launchpad-buildd/+bug/151633112:16
ubottuLaunchpad bug 1516331 in launchpad-buildd "please set /proc/cpu/alignment=4 on Launchpad ARM buildd kernels" [Undecided,New]12:16
MirvLaney: indeed I still don't see them at http://autopkgtest.ubuntu.com/running.shtml#pkg-unity812:16
cjwatsoninfinity: Steve explicitly wanted us there to do more raising of SIGBUS, which at the time seemed to be not a thing on arm64 kernels, but maybe that is in fact a thing now, in which case "yay" as far as that bug is concerned12:16
LaneyMirv: Some kernel uninstallability, looks like things are publishing out12:17
infinitycjwatson: Well, mdeslaur was sigbusing all over the place, so it definitely seems to be a thing.12:31
infinitycjwatson: I think what's not a thing is the config that does alignment fixups.  I think.12:31
infinitycjwatson: Although, that indeed contradicts the bug comments.  Hrm.12:33
infinitycjwatson: Oh!  But your test was an armv8 binary.  mdeslaur's sigbussery was armv7 on arm64.12:34
infinitycjwatson: From this, I would conclude that armv8 allows and fixes unaligned access, but v7-on-64 raises a sigbus.  Maybe.12:35
cjwatsonAh, could be.  Either way it's apparently what we wanted for more reliable behaviour with phones.12:35
infinitycjwatson: If you can prove the truth of my conclusion, I think you can close Steve's bug as Fix Released By Accident.12:37
xnoxMirv, is qml working correctly on powerpc - a harmless test fails to work https://launchpad.net/ubuntu/+source/biometryd/0.0.1+16.10.20160628-0ubuntu313:04
=== _salem is now known as salem_
caribouinfinity: mdeslaur: I'm working on building statically linked pam-winbind & libnss-winbind as suggested for LP: #158448513:37
ubottuLaunchpad bug 1584485 in samba (Ubuntu) "Upgrading samba to latest security fixes together with winbind in nsswitch.conf can harm entire OS" [High,In progress] https://launchpad.net/bugs/158448513:37
caribouinfinity: building them statically brings a bunch of crtbeginT.o: relocation R_X86_64_32 against `__TMC_END__' that seems to be fixed by using -static-libgcc13:38
caribouinfinity: should I just iteratively identify each one that fails & add the flag or there is a more direct approach ?13:38
Mirvxnox: no, 32-bit powerpc has problems that are tagged with powerpc https://is.gd/9FnqIR13:39
infinitycaribou: I'm not sure I have much advice, I don't tend to do much static linking.13:41
caribouinfinity: well, I'll keep on the iterative approach if the number of modification is small (not many so far)13:42
infinitycaribou: If you've got the time, I'd recommend trying to do it in a suitably upstreamable way, so the build can just be done with --static-winbind or some such.  We may be the first to notice the problem, but it really should bite anyone.13:43
infinity(In fact, I'd suggest that --static-winbind be the default, for that reason)13:43
caribouinfinity: ok, will keep that in mind once I get something building13:44
infinitycaribou: Not critical for the SRU or anything, but would be nice to push something upstream so we don't have to maintain a delta, that's all.13:44
caribouinfinity: should be feasible with some waf hacking13:45
infinitycaribou: It might be enough to extend the NONSHARED bit in buildtools/wafsamba/samba_deps.py to allow type BINARY and type LIBRARY, and then tweak it a bit, then one can do --nonshared-binary=nss_winbind or some such.13:52
infinitycaribou: But that's my naive poke ater 5 minutes of grepping. :)13:53
caribouinfinity: ok will look at that too13:53
infinitycaribou: How did this end up in your lap? :P13:56
caribouinfinity: took it over from a colleague13:56
mdeslaurcaribou: did he quit? I'd consider quitting too if that was on my lap :)13:57
cariboumdeslaur: :D13:57
cariboumdeslaur: that's how one builds experience in build weirdiness I suppose13:58
xnoxMirv, ack. Do you want a bug open about it + upload that skips that one test on powerpc?13:59
xnox(fro biometryd)13:59
infinityxnox: Looks like they're tacking "skip tests on ppc" bugs on to that master bug as tasks.14:00
* xnox looks again14:00
infinityA one-stop shop to reopen them all after the Qt bug is fixed, I guess.14:00
tyhicksogra_, jibel: the apparmor oops was a known bug that only affected a handlful of people14:13
tyhicksogra_, jibel: unfortunately, the apparmor package SRU is causing it to happen to a lot more people now because the update process triggers a profile reload :/14:13
tyhicksogra_, jibel: I've duped your bug to bug #1579135 - jjohansen has a proposed fix and any testing of the kernel mentioned in comment #27 would be appreciated14:14
jibeltyhicks, so what is the plan of action?14:14
ubottubug 1579135 in apparmor (Ubuntu) "AppArmor profile reloading causes an intermittent kernel BUG" [Critical,Incomplete] https://launchpad.net/bugs/157913514:14
jibeltyhicks, okay, thanks14:15
coreycbarges, mind rejecting cinder and aodh from the xenial queue? I forgot the bug #.15:11
argescoreycb: rejected! *slams basketball*15:12
coreycbarges, lol, thanks15:12
pittiarges: he'll get the rebound, I'm sure :)15:20
seb128happyaron, cyphermox, looks like the network-manager-applet (1.2.0-0ubuntu2) and ubuntu3 uploads didn't get commited to git which made the 1.2.2-0ubuntu1 update revert them/drop them, we really need to sort out the nm vcses and standardize on using them...16:01
cyphermoxjust use git; that's what we agreed on16:02
cyphermoxfor the record, I haven't done an upload of NM in weeks16:02
seb128cyphermox, yeah, those you did in may16:02
seb128still there are missing from the vcs16:02
seb128which makes happyaron's update he handed me for sponsoring today buggy16:03
seb128happyaron, can you please fix the vcs tomorrow then I can have another look at uploading it for you16:03
cyphermoxseb128: the git tree was up to date, I'm not sure what happened for stuff to be missing16:05
seb128let's see with Aron tomorrow16:05
seb128cyphermox, thanks16:05
seb128I'm sure what happened is "git"16:05
seb128the best tool to get things screwed up it seems :-/16:05
cyphermoxtbh it has happened a couple of times that people forget to commit or whatever16:06
seb128yeah, but you said that it was uptodate16:06
seb128so it means somebody rewrote the commit history or something16:06
cyphermoxI think it's counter-productive to try to figure out who did what and where16:07
cyphermoxaron will fix the git tree, things will be good16:07
seb128yeah, that was mostly joking16:08
seb128I just wanted to make sure everybody was syncing up on using the same vcs16:08
seb128seems you guys are16:08
seb128so it's good16:08
seb128cyphermox, thanks16:08
MirvLaney: rerunning autopkgtests with --all-proposed still broken?16:32
LaneyMirv: nope16:34
Laneyi386 done, amd64 nearly16:34
* Mirv finds the correct entry on the running page16:34
Mirvi386 was a pass, and seems amd64 too (qmluitests pass just visible on the running page)16:36
LaneyMirv: can you find out why the disabling didn't work and fix it please?16:38
MirvLaney: yes, robru should be online now16:40
=== JanC is now known as Guest7844
=== JanC_ is now known as JanC
juliankHow can I check what translation stuff was exported during the apt build? A tarball is generated, but it's not accessible; and the translation import queue does not have it either.18:12
* juliank is wondering if launchpad exporting/importing of apt translation domains now works18:12
=== beisner is now known as beisner-biab
=== beisner-biab is now known as beisner
=== salem_ is now known as _salem
=== Insight is now known as Guest18492
naccpowersj: nice find on LP: #1613982, I just reviewed and rejected it :)22:20
ubottuLaunchpad bug 1613982 in php-defaults (Ubuntu) "Date parsing has been fixed in 14.04, but broken in 16.04 again" [Undecided,Invalid] https://launchpad.net/bugs/161398222:20
powersjnacc, thanks :)22:21
Unit193nacc: BTW, I think it's very cool that you're an active developer that keeps an eye out in #ubuntu too.  Thanks.22:26
naccUnit193: thanks! i try to be -- always hard with time constraints, though :)22:28
naccluckily i'm mostly working on release stuff, so people's complaints tend to be relevant :)22:28

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