[00:00] <smoser> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483440
[01:02] <smoser> infinity, is your /proc/net/route exactly 512 bytes like mine is
[01:02] <smoser> did i just really luck into the fencepost ?
[01:05] <infinity> smoser: No, mine is 768.  Though, still a curiously round number in binary land, so I assume the lines are a padded length.
[01:05] <infinity> And, indeed, they are.
[01:06] <sarnold> heh, mine's 77 * 128 bytes long
[01:07] <smoser> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483440
[01:08] <sarnold> this reminds me so much of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381005 -- but that looks to be tty specific
[01:08] <smoser> walking through powers of two for byte size, i get error right at 512, which is exactly mine.
[03:01] <pitti> Good morning
[03:02] <pitti> slangasek: I heard you want to force gcc-5 into wily-release, so that at least some of the transitions can land?
[03:02] <sarnold> hey pitti, this seems especially early..
[03:02] <pitti> that would at least help a bit to untangle the mess
[03:02] <pitti> sarnold: yeah, can't sleep any more :/
[03:02] <sarnold> oh :( sorry
[03:12] <tjaalton> seems to be the trend..
[03:24] <pitti> tjaalton: morning :)
[03:25] <pitti> The early bird can bite me
[03:26] <tjaalton> hehe
[03:26] <tjaalton> yeah or the cat, woke me up 1+ hrs ago
[04:24] <mwhudson> blargh
[04:25] <mwhudson> i can't install packages in the wily chroot on the ppc64el porter box
[04:25] <mwhudson> SystemError: E:Unable to correct problems, you have held broken packages.
[04:25] <mwhudson> how can this be unpicked?
[04:25] <mwhudson> i don't know how to use rapt very well
[04:26] <pitti> mwhudson: if apt-get -f install doesn't help, then you need an RT I'm afraid
[04:26] <pitti> unfortunately the schroots on our porter boxes are quite useless
[04:26] <mwhudson> ERROR: only install/update/upgrade/dist-upgrade supported as argument
[04:26] <mwhudson> rt time!
[04:26] <mwhudson> also eod time so that's ok i guess
[04:26] <pitti> mwhudson: perhaps while you are at it you can ask for re-setting them up properly
[04:27] <pitti> i. e. with session overlays instead of "everyone uses and breaks one single schroot"
[04:27] <mwhudson> pitti: heh uh, i don't think putting that literal text into the rt would be productive
[04:27] <pitti> I thought I did that years ago already
[04:27] <pitti> but it seems nobody got around to it yet
[04:27] <pitti> mwhudson: asking for session overlays? but that's the right thing to do, and constructive?
[04:28] <pitti> nobody except IS should ever be able to access the "real" (source) schroot
[04:28] <pitti> one should be able to start a session, hack in that, end it, and it's all gone
[04:28] <mwhudson> i can see how that would be useful
[04:28] <mwhudson> but i'm not sure i'm going to fight that fight today
[04:29] <pitti> what makes me wonder is how IS set this up in the first place, given that sessions are schroot's default mode of operation
[04:29] <pitti> you actually have to go through great lenghts of effort to set them up the way they are right now :)
[05:50] <slangasek> pitti: if by "force" you mean "review the remaining autopkgtest blockers and make judicious decisions about whether to override them", yes
[05:52] <pitti> slangasek: oh, please don't force-badtest those; all the KDE failures also appear in more proper excuses where they *should* hold back stuff until the transitions get completed
[05:52] <pitti> slangasek: I thought you were going to force-skiptest gcc-5 itself only?
[05:52] <slangasek> pitti: I was not suggesting a force-badtest at all
[05:52] <pitti> (after reviewing the remaining failures, yes)
[05:53] <slangasek> pitti: there should be some information on the pad; I know robru confirmed that some of the regressions started only after gcc-defaults landed so are not related, but I think there are some remaining failures that need looked at
[05:54] <robru> pitti: yeah i put those at the very bottom of the pad
[05:54] <pitti> but that's misleading
[05:55] <pitti> well, it can be argued that gcc-5 broke all those, but shouldn't they rather be tacked to the kde lib renames instead of gcc-5 itself?
[05:56] <robru> pitti: how can that be argued? There's a handful of cases where tests passed after gcc5 was uploaded.
[05:56] <pitti> either way, for gcc itself it doesn't matter much whether it promotes; we effectively can't "hold back" gcc, as we build everything from -proposed
[05:56] <pitti> I thought we wanted to do this to unblock some unrelated transitions
[05:57] <slangasek> I wouldn't say unrelated
[05:57] <pitti> e. g. scim, snappy, schroot, etc.
[06:00] <slangasek> so, unrelated to kde but not unrelated to gcc, sure
[06:27] <slangasek> pitti: fyi gr-* failed because gnuradio has a wrong dependency on libuhd
[06:27] <pitti> slangasek: yeah, just looked at it
[06:27] <pitti> slangasek: want me to fix, or are you on it?
[06:28] <pitti> (yay for not using proper shlibs..)
[06:28] <slangasek> pitti: I'm just letting you know since you triggered the builds; I'm off to bed now
[06:28] <pitti> slangasek: right, the previous FTBFS was due to non-current gnuradio, so it looked worth a retry
[06:28] <pitti> slangasek: ack, will fix
[06:31] <pitti> slangasek: are you the blue editor on the pad?
[06:31] <pitti> (I don't see any names except robru's and mine)
[06:32] <slangasek> pitti: yep
[06:32] <pitti> ah, thanks
[06:32] <slangasek> and going to bed for real now ;)
[06:33] <pitti> slangasek: sleep well!
[06:36] <pitti> Logan: hmm, aqsis still fails, did that work locally for you for some weird reason?
[06:40] <darkxst> jdstrand, can you look again at bug 1466290?, remaining core GNOME is blocked on that
[07:10] <dholbach> good morning
[07:15] <shine_> I have a situation that I feel is a but in the ubuntu o/s (unity?) and I'm having a hell of a time finding a way to just submit a bug in my own words. Been to https://bugs.launchpad.net/ubuntu ... click "report a bug" and get a howto document (not a place to submit a bug). In my particular case, there is no system information that would be useful. it will effect every 14.04 system (no matter the hardware) because it's a design
[07:15] <shine_> choice I'm pointing out.
[07:15] <ikonia> this isn't really a "bug" channel
[07:15] <shine_> Been on #ubuntu and not getting anywhere in an economic amount of time. What can I do?
[07:15] <ikonia> (check the topic)
[07:16] <shine_> well perhaps the requirement is too much to ask (time wise) for something as simple as this. Shame if suffering result because the failure to report somethgin important
[07:17] <shine_> Suppse, at this point, ubuntu doesn't want you to report bugs
[07:18] <ikonia> you know it does want you to report bugs, this was explained in #ubuntu
[07:18] <ikonia> so hitting other channels and repeating won't help
[07:18] <ikonia> getting the bug logged, will, which if you rejoin #ubuntu people will work through with you
[07:20] <shine_> I just don't feel it's fair to require someone to do research before they can report what seems like a problem to them. Person should be able to spend 5 or 10 minutes total, make a couple clicks, write in some text, click "submit" and be done with it.
[07:20] <ikonia> this isn't the channel for this discussion
[07:21] <shine_> Suppse, at this point, ubuntu doesn't want you to report bugs
[07:21] <shine_> but hey - who cares - right?
[07:21] <ikonia> this self pity stuff doesn't help
[07:44] <pitti> doko: bug 1483400> why is dropping -Werror not an option? IMHO -Werror is just plain wrong in "production" builds (specific errors are okay and good of course)
[07:45] <pitti> -Werror is only ever a thing for local developer builds
[07:46] <infinity> pitti: I used to think that way too, but I've come to love gcc warnings more and more over the years.
[07:46] <pitti> sure, they are good
[07:46] <infinity> pitti: And a lot of them really, really do point to real bugs that will affect runtime.
[07:46] <pitti> infinity: not in my experience then
[07:46] <pitti> I used to see tons of FTBFS due to deprecation warnings wiht e. g. new glib which turned into FTBFS
[07:46] <infinity> Oh, well, that's glib. :P
[07:47] <infinity> I'm talking gcc warnings, not people abusing #warning.
[07:47] <pitti> and building a package with a new compiler which has new warnings doesn't suddenly break your software
[07:47] <infinity> No, it means it was already broken, often.
[07:47] <pitti> the developer of that software should build with it, but never packages
[07:47] <infinity> I still kinda want to know.
[07:47] <pitti> yes, but no-change rebuilds are the wrong place for that
[07:48] <infinity> See, I still disagree.
[07:48] <infinity> "It was always broken" is no excuse for not fixing it.
[07:48] <infinity> And when we discover it is a good time to fix it.
[07:48] <pitti> well, I was mostly interested in why doko said "not an option" -- just out of general principle, or whether he reviewed the warnings and they are actual errors
[07:48] <infinity> I have a slight bias here after putting in years to get glibc to build warning-free. :P
[07:48] <infinity> But the number of real bugs we found in the process was pretty shocking.
[07:49] <pitti> infinity: yes, and that's the very "developer build" use case
[07:49] <infinity> pitti: We build it with -Werror in Debian and Ubuntu too!
[07:49] <infinity> (And Fedora and Gentoo, and...)
[07:49] <pitti> I'm not going to fix all the warnings in juju-mongodb
[07:50] <pitti> and while I do agree that warnings are important, they are not *more* important to me as a random "do this transition" packager than to upstream
[07:50] <pitti> (or the package maintainer)
[07:50] <infinity> pitti: So, the answer for things you don't care about fixing is to see what *new* warning are affecting it, decide they don't matter, and build with -Wno-error=$warning
[07:50] <pitti> and I yet have to see a C++ package rebuild that doesn't have warnings :)
[07:50] <infinity> Cause a new warning might be a nasty bug.  But maybe the warning of the day isn't.
[07:50] <pitti> infinity: right, that was kind of the point of my question to doko
[07:51] <infinity> Effectively, when you drop -Werror entirely, you're making a future decision that you can't support because you have limited info (you don't know if future warnings will catch awesome bugs or code style issues or cows in your comment blocks)
[07:53] <RAOF> In my experience with Mir, we've had a bunch of new warnings appear as compilers advance. These have *all* been stylistic.
[07:54] <doko> pitti, at least -Werror is not good enough to fix the ftbfs
[07:54] <pitti> well, it's a question of who can and will do something about it
[07:54] <RAOF> But we're doing more fun things than the average package, and are aggressive with enabling warnings, and CI requires the build to succeed with -Wall -Werror before it lands, so...
[07:54] <pitti> upstream and a package's maintainer should
[07:58] <infinity> pitti: Anyhow, mongo may well be a lost cause, and maybe the answer is to turn off -Werror, and purists like doko and I should shut up.
[07:58] <infinity> pitti: I definitely get where you're coming from too.
[07:58] <infinity> pitti: But if it's just a few warnings on repeat, -Wno makes more sense.
[07:58] <infinity> IMO.
[07:58] <pitti> infinity: yes, agreed
[07:59] <doko> pitti, if you work on this, please update to the current upstream of the 2.6 series ...
[08:00] <pitti> currently working on luabind and libcrypto++ FTBFSes (I spotted the above when reviewing the list)
[08:00] <pitti> doko: noted
[08:09] <pitti> infinity: "[-Werror=unused-variable]" -> that definitively sounds like a case of -Wno-error :)
[08:09] <infinity> pitti: Yeah, unused-variable probably should be in extra, not all.
[08:09] <infinity> (or is mongo building with -Wextra?)
[08:10] <pitti> I'll look at mongodb/juju-mongodb, and update the former to 2.6.10
[08:10] <infinity> unused-variable is in -Wall.  That seems perhaps wrong.
[08:24] <Mirv> hmh, why does apt continuously give me hash mismatch on http://archive.ubuntu.com/ubuntu/dists/wily-proposed/main/i18n/Translation-en
[08:25] <Mirv> good to complain, the continuity stopped
[08:33] <darkxst> Mirv, I get that often, but usually on mirrors
[08:33] <darkxst> usually clears up after 5mins or so
[08:41] <Mirv> darkxst: this was on main. I do tend to see that every now and then, but usually it's immediately that the next apt update works. this was maybe that 5min or such
[08:43] <zyga> doko: looking at https://bugs.launchpad.net/ubuntu/+source/checkbox-support/+bug/1483410 -- when I test-build the package from debain in a wily sbuild I get python 3.4 and it builds okay, what am I missing?
[08:43] <zyga> doko: is that built using something (proposed?) that has 3.5 as default?
[08:44] <doko> zyga,  come out of your comfort zone and enable -proposed as the buildds?
[08:44] <zyga> doko: ack, thanks
[08:44] <zyga> :-)
[08:56] <zyga> I'm getting hash sum mismatch on wily-proposed, is that something common/expected?
[08:57] <zyga> odd, now it works
[08:58] <pitti> that's the case fairly often indeed
[09:04] <pitti> sil2100: did you have a chance to review http://pad.ubuntu.com/drop-obsolete-phone-packages already?
[09:07] <sil2100> pitti: no, on it right now, I had a few firefights yesterday :)
[09:07] <pitti> sil2100: cool, thanks; not that urgent, I was just wondering
[09:33] <sil2100> pitti: ok, had a look at those
[09:33] <sil2100> pitti: so libdbusmenu-qt is required and can't be removed, but I'm not sure about libcolumbus
[09:34] <sil2100> pitti: the rest looks fine to get rid of
[09:34] <sil2100> I remember hud was using libcolumbus on the desktop as well some time ago, so I suppose it's still using it
[09:34] <sil2100> And since we have hud still in unity7 desktops, I wouldn't remove it
[09:51] <zyga> doko: fixed, should I just request a new version in Debian (which might take a while, I cannot upload yet) or do you want to get the patch in ubuntu faster?
[09:54] <doko> zyga, ubuntu then. and pretty please watch these packages, if you sync them, and they ftbfs
[09:55] <zyga> doko: I just realized this is not in my inbox, how can I ensure we are subscribed?
[09:55] <zyga> doko: I didn't explicitly sync them they just got auto synced
[09:56] <zyga> doko: I'm watching debian bugs carefuly now but bugs on source packages in ubuntu still seme not to be subscribed
[09:58] <rbasak> doko: in bug 1483400, you say "just building without -Werror is not an option". Why?
[09:59] <tseliot> pitti: hi. Did you get any more reports of that symbols problem with fglrx? I'm asking as my 15.04 installation works well here
[09:59] <doko> rbasak, because it fails later on boost1.58 (please talk with pitti)
[10:10] <pitti> tseliot: yes, the u-d-c test still fails
[10:10] <pitti> rbasak: I'm currently test-building a potential fix for both
[10:11] <pitti> argh, one failed with more followup errors, the other with "out of space"
[10:11] <tseliot> pitti: can you point me to the link again, please?
[10:11] <rbasak> pitti: thanks! Please let me know if you need anything.
[10:11] <pitti> tseliot: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-wily/wily/amd64/u/ubuntu-drivers-common/20150804_151050@/log.gz
[10:11] <pitti> tseliot: from http://autopkgtest.ubuntu.com/packages/u/ubuntu-drivers-common/wily/amd64/
[10:16] <pitti> sil2100: cheers! I'll go through them with reverse-depends again and clean up
[10:16] <sil2100> pitti: thanks a lot :)
[10:20] <tseliot> pitti: I'm not sure if you saw my last few messages. I was saying that it seems to me that you're testing fglrx instead of fglrx-core (which is what builds the module)
[10:21] <pitti> tseliot: yes, it installs fglrx indeed
[10:21] <pitti> tseliot: ah, did the module recently move from fglrx to fglrx-core?
[10:21] <pitti> tseliot: then I suppose we just need to adjust the test?
[10:21] <tseliot> pitti: yes, that's what I was trying to say
[10:22] <pitti> tseliot: how is it called for fglrx-updates? there's no f-core-updates
[10:22] <pitti> ah, fglrx-updates-core
[10:22] <tseliot> yep
[10:22] <pitti> tseliot: I'll try that once my computer becomes usable again (building two mongodbs ATM)
[10:23] <pitti> tseliot: thanks!
[10:23] <tseliot> pitti: thanks to you
[10:27] <zyga> doko: how do you want me to send the patch (I never uploaded directly to ubuntu before), a debdiff attached to the bug?
[10:28] <doko> zyga, do you have upload rights?
[10:28] <zyga> doko: no
[10:28] <doko> pff
[10:28] <zyga> doko: (though I'd like to work on gettin that)
[10:28] <zyga> after all those years ...
[10:28] <doko> apply for it
[10:28] <zyga> per package upload or UD?
[10:28] <doko> dholbach, ^^^ here's your next victim
[10:28] <zyga> :D
[10:28] <zyga> dholbach: with pleasure :)
[10:29] <doko> zyga, send me the patch, or file a bug report
[10:29] <zyga> allright
[10:29] <zyga> dholbach: and please tell me what to do to apply for upload rights
[10:44] <zyga> doko: sent
[10:54] <zyga> __hmm__
[10:54] <zyga> doko: looking, I just built it like 12s of times
[10:55] <zyga> oh, I see... somehow the python3-gi dependency is not in the debdiff, sorry, my bad
[10:55] <doko> that's all?
[10:55] <zyga> doko: yes
[10:56] <zyga> doko: it's in debian, I must have d'd it by accident before running debdiff
[10:56] <zyga> doko: it's a build-dependency
[10:56] <zyga> doko: sorry :/
[10:56] <zyga> doko: I just checked that it's not in the debdiff
[10:56] <zyga> doko: do you want -1ubuntu2 or will you do that yourself?
[10:59] <doko> https://launchpad.net/ubuntu/+source/checkbox-support/0.20-1ubuntu2
[11:00] <pitti> rbasak: juju-mongodb now fails in that "smoke" test during build: http://paste.ubuntu.com/12054846/
[11:01] <pitti> rbasak: any idea what's wrong with the pymongo module?
[11:01] <zyga> doko: thank you
[11:01] <pitti> rbasak: AFAICS there is no "Connection" in dir(pymongo)
[11:02] <rbasak> pitti: I know no more than you on this, sorry. If the server team needs to take this on I can add it to our list.
[11:03]  * pitti retries mongodb, take IV
[11:04] <zyga> doko: built fine! I'll subscribe to all the source package bugs not to miss that next time
[11:06] <pitti> rbasak: I'm adding my preliminary patch with the above output to bug 1483400
[11:06] <rbasak> Thanks!
[11:10] <rbasak> pitti: are you still working on the bug or are you handing it over to us?
[11:10] <pitti> rbasak: I'm trying something
[11:10] <rbasak> OK, np
[11:11] <pitti> I found http://api.mongodb.org/python/current/tutorial.html, I hope it's just a simple renaming
[11:11] <pitti> I see the test suite now, looking good
[11:19] <pitti> dpkg-deb: building package 'juju-mongodb' in '../juju-mongodb_2.4.10-0ubuntu4_amd64.deb'.
[11:19] <pitti> \o/
[11:19] <pitti> rbasak: ^
[11:24] <rbasak> \o/
[11:24] <rbasak> Thank you!
[11:24] <dholbach> zyga, sure... which packages do you want to upload? which did you upload in the past?
[11:25] <zyga> dholbach: I never uploaded packages directly to ubuntu before, it would be fantastic if we could (the checkbox development team in general but probably me in particular for now), upload plainbox, checkbox-ng, checkbox-support, plainbox-provider-checkbox, plainbox-provider-resource-generic and perhaps one or two misc packages that I also maintain in debian, python-guacamole, python-morris, python-padme
[11:27] <zyga> dholbach: we also want to land a whole new checkbox to wily and that will include two new packages (not in debian), checkbox-converged and qchartjs (a qml module)
[11:27] <dholbach> nice, that should be possible
[11:27] <zyga> dholbach: excellent, what do I need to do?
[11:30] <dholbach> zyga, https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess explains the application process
[11:30] <zyga> dholbach: allright
[11:30] <dholbach> zyga, it's a lot like the membership process - so set up a wiki page, explain what you're after, get a few endorsements and attend a meeting
[11:31] <zyga> dholbach: one question, should I apply for per-package uploader or for something more generic?
[11:32] <dholbach> zyga, as you like it... for something more generic, you might have to demonstrate a more diverse interest or prior work on other packages
[11:33] <zyga> dholbach: ok, let me read the precise difference between them and see what to do next
[11:33] <dholbach> zyga, the process is very much the same
[11:34] <dholbach> zyga, you might have to explain what your interests are and what you worked on in the past
[11:37] <pitti> Mirv, sil2100, seb128: I processed most of http://pad.ubuntu.com/drop-obsolete-phone-packages but qml-friends and friends (and thus libfriends) are still seeded on ubuntu-touch adn ubuntu-desktop-next; should these be dropped?
[11:37] <pitti> see "reverse-depends src:libfriends"
[11:37] <pitti> and "reverse-depends src:friends"
[11:37] <pitti> * ubuntu-desktop-next [amd64 armhf i386]  (for friends-twitter)
[11:37] <pitti> * ubuntu-desktop-next [amd64 armhf i386]  (for friends-facebook)
[11:37] <pitti> * ubuntu-touch [amd64 armhf i386]  (for friends-facebook)
[11:37] <pitti> * ubuntu-touch [amd64 armhf i386]  (for friends-twitter)
[11:37] <pitti> * unity-lens-friends            (for friends)
[11:38] <zyga> dholbach: for what we are after (creation of ubuntu-specific new packages) core dev might be better as it includes "specify, develop and deploy new features for the default installation of Ubuntu" but I lack the required "hitory of substantial direct contributions to the distribution"
[11:39] <zyga> history*
[11:39] <dholbach> zyga, maybe start with a checkbox package set first?
[11:39] <dholbach> get it created for you, and team mates can apply for that later on as well
[11:39] <zyga> dholbach: yes, I think that is appropriate
[11:39] <dholbach> cool
[11:39] <dholbach> let me know if I can help with anything
[11:39] <zyga> dholbach: so package sets are only briefly mentioned there
[11:39] <zyga> dholbach: how does one create a new set?
[11:40] <zyga> dholbach: is that the delegated team concept?
[11:40] <dholbach> no
[11:40] <dholbach> just mention which packages you need upload rights for
[11:40] <zyga> ok
[11:40] <dholbach> and mention that A, B and C should be made a package set
[11:40] <zyga> ok
[11:40] <dholbach> later on you can still go and get packages added and removed
[11:40] <zyga> makes sense, thanks!
[11:41] <dholbach> cool :)
[11:43] <Mirv> pitti: wow, that's true
[11:46] <sil2100> pitti: I'm pretty sure we don't use that anymore
[11:46] <sil2100> But hm
[11:46] <sil2100> Let's double-confirm with robru
[11:47] <Mirv> sil2100: yeah, and in general even though we don't use the Friends anymore on the images, robru can weigh in if it'd be nice to keep it in archives still
[11:48] <Mirv> sil2100: anyway, created https://code.launchpad.net/~timo-jyrinki/ubuntu-seeds/ubuntu-touch.wily_remove_friends/+merge/267648
[11:48] <Mirv> it is/was a nice program from user point of view
[11:49] <Mirv> but maybe it could rather live on as a click package rather than in archives, if somewhere
[11:50] <seb128> pitti, unsure about friends, to be checked with kenvandine
[11:51] <sil2100> Mirv: thanks!
[12:44] <pitti> tseliot: that's not it -- fglrx Depends: fglrx-core
[12:44] <pitti> tseliot: it actually fails to build in -proposed; I'll file a bug with the details
[12:45] <pitti> make[1]: gcc-4.9: Command not found
[12:45] <pitti> heh, that would do it :)
[12:48] <pitti> tseliot: filed as bug 1483695
[12:52] <pitti> tseliot: what I'm not sure about is where the gcc-4.9 comes from -- I can't find anything in fglrx about it
[12:52] <pitti> then again, nvidia* build fine, and I don't see it in dkms itself either
[13:07] <mterry> bdmurray, FYI team mapping update: ~checkbox-dev has agreed to look after xlsxwriter in main
[13:23] <tseliot> pitti: maybe something's pulled in as a result of the depending on these: lib32gcc1 [amd64], libc6-i386 [amd64], dkms, make, linux-libc-dev
[13:23] <pitti> tseliot: I didn't find anything that would set CC -- do you know where that gcc-4.9 might come from?
[13:24] <TJ-> pitti: I believe the gcc-4.9 comes from the kernel due to parsing /proc/version in lib/modules/fglrx/build_mod/make.sh
[13:24] <pitti> ah, so it tries to invoke the same compiler that the kernel was built with?
[13:25] <pitti> that would explain it indeed (and why it doesn't affect nvidia or other DKMS mods)
[13:25] <tseliot> oh
[13:28] <tseliot> pitti, TJ-: yes, the set_GCC_version function in make.sh http://paste.ubuntu.com/12055486/
[13:29] <pitti> tseliot: ah, that's it; so we either need to patch that out (preferred), or add a gcc-4.9 dep?
[13:31] <tseliot> pitti: yes, a patch would be easier
[13:31] <pitti> I mean "better" -> so that users don't end up with a second compiler just for this
[13:32] <pitti> hm, LP keeps timing out on me, I wanted to add that info to the bug
[13:33] <tseliot> pitti: I agree, I don't want to hardcode the gcc-$ver dependency
[13:35] <mterry> sarnold, on bug 1455644, is it ACK to be approved *now* or did you want a release with the fixes you've discussed in wily first?
[13:36] <mterry> bdmurray, FYI team mapping update: ~ubuntu-printing has agreed to look after ippusbxd in main
[13:36] <ricotz> doko, hi, maybe you are able to confirm this? this is running aptitude from wily-proposed -- http://people.ubuntu.com/~ricotz/ubuntu/aptitude-gcc5.png
[13:40] <pitti> Riddell: as per http://pad.ubuntu.com/gcc-5-transition there are several KDE libs that need to be renamed to v5 and rdepends rebuilt: okular, libkdegames, marble, okteta
[13:41] <pitti> Riddell: for coordination: do you plan to upload them anytime soon? is there a new upstream version for those for 5.13 which changes SONAME anyway?
[13:41] <pitti> Riddell: if not, want me to upload renames?
[13:41] <pitti> (and rebuilds)
[13:41] <pitti> doko: ^ (FYI)
[13:42] <Riddell> pitti: we're onto it
[13:43] <pitti> Riddell: cool, thanks (FYI, just uploaded cantor, but that was just a no-change rebuild)
[13:43] <Riddell> pitti: it's KDE Applications 15.07.90 (the third large release from KDE along with Frameworks and Plasma)
[13:43] <Riddell> pitti: it'll take us a couple more days because it's got stuff ported to frameworks5/qt5 as well as the gcc transitions but I can start uploading stuff sooner
[13:44] <pitti> Riddell: that's ok, I just don't want to step on your feet, thus asking who's on what
[13:44] <Riddell> pitti: along with doko we're still poking the frameworks and plasma packages to compiling happyness
[13:44] <pitti> these four don't block gcc-5 any more, just the konsole FTBFS
[13:44] <pitti> "undefined reference to `Konsole::HistoryScroll::hasScroll()'"
[13:46] <pitti> doko: oh, you didn't rename the openvdb libs? because no rdepends?
[13:47] <Riddell> pitti: ok I'll look at the new version of konsole
[13:47] <doko> pitti, no cxx11 symbols
[13:48] <doko> ricotz, I don't use aptitude
[13:51] <ricotz> doko, hmm, ok
[14:18] <tdaitx> pitti, doko, infinity, slangasek: notmuch is now FTBFS on ppc64le, how can I get a ppa that has ppc64le? I need to add one debug flag to the build to see what is going on. I created LP: #1483760
[14:19] <pitti> tdaitx: we have porter boxes (with incredibly brittle schroots)
[14:19] <pitti> tdaitx: porter-ppc64el.canonical.com
[14:19] <pitti> tdaitx: however, note that this isn't a blocker -- notmuch never built on ppc64el, so britney won't block it on that
[14:20] <tdaitx> right, anyway, those are the only failures, that test runs gdb, I bet it is related to it
[14:23] <tdaitx> pitti, err... what am I supposed to do with porter-ppc64el.canonical.com? is it offline? I can ping it, but there is no response for either http or ssh
[14:23] <pitti> tdaitx: hm, I can ssh to it; maybe you aren't on the company VPN?
[14:24] <tdaitx> indeed, vpn is down
[15:03] <hallyn> pitti: hey, i have some systemd ignorance i'm hopng you can help with
[15:03] <hallyn> when you have a minute
[15:07] <pitti> hey hallyn -- better just ask, mostly left for the day already
[15:11] <hallyn> pitti: trying to write systemd jobs for libvirt.  i've got the libvirt-bin one working, trying to write the one which would shut down vms cleanly before machined kills them at shutdown
[15:11] <hallyn> but i've not been able to get it to run in time.
[15:12] <hallyn> i'm trying to figure out what it is that does tha tkilling.  is it machined.service?  having my job run before or after that doesn't seem to work
[15:13] <hallyn> debian uses a job from upstream that is supposed to suspend vms at shutdown adn restart them at startup, but that doesn't seem to be working either
[15:14] <hallyn> well i guess let me take another stab at that one
[15:14] <slangasek> pitti: it seems http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html hasn't updated for 10 hours
[15:14] <pitti> slangasek: right, just noticed 10 mins ago (sorry), I'm at it
[15:20] <pitti> slangasek: I went over the gcc-5 test regressions today and cleared out some things, pad updated
[15:20] <pitti> some test fixes, some FTBFS fixes etc.
[15:20] <pitti> britney should be back in the next run
[15:27] <pitti> hallyn: machined doesn't really cause any peer service to get shut down; I assume you are talking about libvirt on the host, not in the guest?
[15:28] <pitti> hallyn: shutting down will cause all services to get stopped; if they specify an ExecStop= then by running that, otherwise by TERM and eventually KILL
[15:28] <pitti> hallyn: and with Before=/After= you can influence the shutdown order (note that it has an inverse meaning on shutdown)
[15:28] <pitti> hallyn: e. g. After=network.target will ensure that a service gets stopped before anything which brings the network down, like stopping ifupdown, NM, or networkd
[15:31] <hallyn> pitti: in one attempt, my service was WantedBy shutdown.target and Before=shutdown.target.  but it didn't run until later
[15:32] <hallyn> in another, it is simply wantedby=multi-level.target and after=libvirt-bin.service, with execstart=/bin/true and remainafterexit=true,
[15:32] <hallyn> but then the execstop seems to run as soon as /bin/true exits
[15:33] <hallyn> ideally th eformer would work,
[15:33] <hallyn> i.e. like a 'stop scrip' in upstart
[15:34] <pitti> hallyn: with ExecStart=/bin/true it needs to be Type=oneshot, is it?
[15:34] <hallyn> yes it is
[15:36] <hallyn> pitti: here's the one i was really hping toulw work: http://paste.ubuntu.com/12056134/
[15:39] <pitti> hallyn: looks good at first sight; so this is running too early or too late, or what goes wrong?
[15:42] <hallyn> pitti: too late.  lemme get that one installed again and show the log output,
[15:50] <hallyn> pitti: http://paste.ubuntu.com/12056205/ and /var/log/libvirt/shutdownlog.log .
[15:51] <hallyn> maybe if i add After=libvirt-bin...
[15:52] <pitti> hallyn: http://paste.ubuntu.com/12056205/ is very short, and doesn't contain "libvirt" at all -- wrong log?
[15:54] <hallyn> pitti: http://paste.ubuntu.com/12056205/ is syslog output, from where i 'virsh start cdboot' until after some things have shutdown due to shutdown
[15:54] <hallyn> the other is the /var/log/libvirt/shutdownlog which is written to by the script called at ExecStop
[15:55] <hallyn> is there a way to get 'journalctl' to show me the last boot's journal?
[15:55]  * hallyn sees --list-boots
[15:55] <pitti> hallyn: yes -- enable persistant journal (/usr/share/doc/systemd/README.Debian
[15:56] <pitti> hallyn: then sudo journalctl -b -1
[15:56] <hallyn> sigh
[15:56] <hallyn> how come that's not auto-enabled? :)
[15:58] <hallyn> thanks, that's very helpful
[15:58] <pitti> hallyn: because we install rsyslog by default, and I don't want every log be written to disk twice
[15:59] <pitti> /var/log/syslog should also contain most things
[15:59] <hallyn> pitti: http://paste.ubuntu.com/12056255/  full boot log showing the ordering
[15:59] <hallyn> pitti: sadly no syslog misses a lot of systemd ordering info
[16:02]  * pitti really needs to run now, o/
[16:04] <hallyn> pitti: thanks \o
[16:09] <doko> jibel, please could you have a look at the autopilot autopkg test failure? somehow urgent
[16:09] <jibel> doko, sure
[16:14] <flexiondotorg> I'm migrating some Ubuntu MATE application to python3 because I see that is an objective for 16.04.
[16:14] <flexiondotorg> Should I reference python3 in the shebang or just rely on the packaging to install the correct versions?
[16:15] <flexiondotorg> Just interested to know what others are doing in this regard.
[16:15] <flexiondotorg> The code will run on Python 2.6+ and Python3.3+ now.
[16:17] <doko> barry, ^^^
[16:24] <jibel> doko, it's an unreliable test apparently and nothing to do with gcc. Can you force it? I'll ask veebers to fix it.
[16:26] <doko> slangasek, ^^^ can't do this myself
[16:26] <slangasek> doko: context? what test?
[16:27] <slangasek> doko: if you can document it on the pad, that's the best way to track at the moment
[16:27] <slangasek> (I guess autopilot-gtk)
[16:31] <doko> slangasek, done
[16:34] <doko> barry, https://launchpad.net/ubuntu/+source/pytables/3.1.1-3build2
[16:35] <jibel> doko, slangasek filed a bug and added details to the pad.
[17:04] <juliank> doko: We're trying to get current APT git building on travis-ci.org again, for continuous integration. But it  keeps failing with internal compiler errors in most cases, with both gcc 4.9 and 5.1 from https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test - idea?
[17:04] <juliank> dobey: travis-ci runs precise, BTW.
[17:04] <doko> juliank, check wily-proposed, not interested in anything else
[17:04] <dobey> uhm, ok
[17:30] <doko> seb128, Laney: norwegian is dep-wait, please file a MIR or drop the additional requirements
[17:40] <jdstrand> darkxst: I responded in the bug (sorry, I was on vacation last week)
[17:40] <doko> seb128, Laney: gnome-online-accounts is dep-wait, please file a MIR or drop the additional requirements (just one more webkit copy)
[17:41] <seb128> doko, there is a mir for webkit2gtk
[17:41] <doko> seb128, without dropping anything? I can assure you that jdstrand will reject that
[17:41] <seb128> doko, see https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1466290
[17:41] <seb128> which jdstrand was just mentioning
[17:42] <jdstrand> that was actually what I just responded to, above
[17:48] <doko> smoser, https://bugs.launchpad.net/ubuntu/+source/acpica-unix/+bug/1483836
[17:54] <hallyn> pitti: ok, i think i've figured out my problem.  slice dependencies were messing with me
[18:05] <hallyn> eureka
[18:16] <dragos> guys i have an cool idea
[18:16] <dragos> for ubuntu
[18:55] <doko> seb128, Laney: ibus-chewing is dep-wait, please file a MIR or drop the additional requirements (cmake-fedora)
[19:16] <boldfilter1> Ping IdleOne
[20:19] <doko> mterry, welcome to the gcc 5 madness
[20:19] <mterry> doko, :)
[20:19] <mterry> doko, figured I'd help out
[20:19] <doko> is clementine your next one?
[20:19] <doko> looks similar
[20:19] <mterry> doko, oh is it?  where are you seeing that?  I can take it
[20:20] <doko> ahh, no, already fixed
[20:21] <mterry> \o/
[20:31] <ari-tczew> does anybody know a workaround for long taking time pbuilder while "I: Obtaining the cached apt archive contents" ?
[20:32] <ari-tczew> I think more than 15 minutes is not a normal
[20:38] <doko> zyga, https://launchpad.net/ubuntu/+source/plainbox/0.22.2-1/+build/7738741
[20:59] <slangasek> mterry: are you working on the freecad build failure?  this should be the same fix as for other qt4+boost1.58 bugs
[20:59] <slangasek> mterry: oh, Debian bug says you have :)
[20:59] <mterry> slangasek, yeah I was, and uploaded a patch
[20:59] <mterry> slangasek, but now I'm hitting something unexpected and am looking into it
[20:59] <slangasek> ok
[21:30] <ochosi> hey everyone, anybody else apart from Sweet5hark taking care of libreoffice packaging?
[21:52] <hallyn> sigh.  is it too late to delete https://launchpad.net/ubuntu/+source/libvirt/1.2.16-2ubuntu6 ?
[21:52] <hallyn> it's still Pending, so i'm kinda hoping not
[21:55] <hallyn> maybe my testing is bogus anyway.
[22:01] <infinity> hallyn: I can delete it.
[22:01] <infinity> hallyn: But ask quickly.
[22:02] <infinity> hallyn: You could also add the "block-proposed" tag to your bug there, so it never migrates.
[22:02]  * infinity does that for you.
[22:04] <hallyn> infinity: i dunno, i had one vm where upgrading upset systemd.  but a new one is fine.  my worry is - I'm switching from the syvsinit job to a systemd job.  but the first vm mustve had something else funky i think
[22:04] <hallyn> there's not supposed to be anything for me to do manually in preinst-postinst right?  dh_installinit + dh_systemd should do it for me...
[22:05] <hallyn> yeah upgrade went fine here.  what the hell happened in the other place
[22:05] <infinity> hallyn: That's the general theory.  That said, a new systemd service that didn't exist before and autostarts in postinst might exhibit curious behaviour if the daemon is already running.
[22:07] <hallyn> however that job is --restart-after-upgrade, so it must get stopped from sysvinit and then started from systemd right?
[22:07] <infinity> hallyn: Anyhow, you missed your chance to delete before it's published, it's on disk now.  But that bug has block-proposed on it still, so when you're happy with things, remove that.
[22:07] <hallyn> otherwise it would get very screwed :)
[22:07] <hallyn> infinity: thanks
[22:08] <infinity> hallyn: restart-after does the restart all in postinst, so there'd be no way of knowing to stop the sysv job, unless the systemd unit is smart enough to find the orphaned not-a-systemd-service version of the daemon and eat it first.
[22:09] <infinity> hallyn: There's also a stop on prerm, start on postinst semantic, but you can't go back in time and make the old package do that. :)
[22:13] <infinity> hallyn: Why did you write libvirt-stop-guests twice? :P
[22:13] <infinity> hallyn: Surely, the init script can call it instead of embedding a copy.
[22:13] <hallyn> so the q is whether i need to add a stop to pre-inst
[22:13] <hallyn> infinity: ?
[22:14] <hallyn> init script can call what?
[22:14] <infinity> /usr/lib/libvirt/libvirt-stop-guests
[22:14] <hallyn> oh.  yeah.
[22:14] <infinity> Ditto if there's a copy of the same logic already in the upstart job.
[22:14] <hallyn> i'd done the inline version first before i realized there was no way to do it from sysvinit
[22:15] <infinity> "No way to do it from sysv" seems fatalistic.
[22:15] <infinity> And probably not true...
[22:15] <hallyn> yeah will clean that up if i have to push a new version
[22:16] <hallyn> no - libvirt defines VMs with systemd-machined, which then hard-kills them at shutdown.  you can't get a sysvinit job to block that hard-kill
[22:16] <infinity> Ugh, another systemd-rules-the-world thing?
[22:16] <infinity> When did that happen?
[22:17] <hallyn> took me two days to find where tha twas done - the systemd service name you have to define is hardcoced in libvirt
[22:17] <infinity> Still, there must be a way to order that differently.
[22:17] <hallyn> years ago actually, but when we used upstart we could ignore it
[22:17] <hallyn> "it's opt-in"
[22:17] <hallyn> well we could compile libirt to nto use systemd-machined
[22:17] <hallyn> s/compile/patch/
[22:18] <infinity> I mean ordering of the shutdown.
[22:18] <hallyn> the other code is still there as a backup if systemd isn't running
[22:18] <infinity> Or is it because services are all acted on before sysv, because sysv is a second class citizen?
[22:18] <infinity> Except, no.  It should be the inverse on shutdown.
[22:18] <infinity> sysv first, then systemd services.
[22:18] <infinity> So, one should be able to stop things gracefully from sysv before systemd goes nutty on it.
[22:19] <infinity> If it's not inverted on shutdown, that's a bug in our systemd sysv emulation, IMO.
[22:20] <hallyn> i don't think so.  libvirt tells systemd "create this slice for the vm, and it is Before=libvirt-guests which will shut it down orsuspend it"
[22:20] <hallyn> not sure about before, but at least in parallel
[22:22] <infinity> hallyn: Also, minor nitpick, that "Suggests: systemd" is pointless.  It's pretty much a no-op.
[22:22] <hallyn> i don't know the systemd code enough to know how systemd-machined-defined slices relate
[22:23] <hallyn> ok i'm removing the duplicate libvirt-sotp-guests from libvirt-bin.init, but removing it from the upstart job worries me bc users may be depending on changes they made to variables in /etc/defualt/libvirt-bin
[22:28] <hallyn> infinity: ok, yeah, systemd doesn't know what to do with libvirt afte rthe upgrade.  so i guess in pre-inst from older versions i'll stop libvirtd by hand
[22:28] <infinity> hallyn: If the upstart version uses bits sourced from /etc/defualt/libvirt-bin, then the new script should source it too, no?
[22:29] <bluesabre> hi doko, ochosi tells me that you might be able to help with a libreoffice packaging request
[22:29] <bluesabre> bug 1483914
[22:29] <hallyn> infinity: i dunno.  sounds reasonable....  i was just going by the "systemd jobs don't like /etc/default" mantra
[22:29] <infinity> hallyn: Pfft.
[22:30] <bluesabre> The Xubuntu team is shipping libreoffice, libreoffice-gtk, and libreoffice-style-elementary this cycle
[22:30] <infinity> hallyn: If it was tunable before, upgrading shouldn't break that.
[22:30] <hallyn> so yeah i'll do that and yank it from hte upstart job
[22:30] <infinity> hallyn: So, /usr/lib/thing should be a cargo-cult of the upstart logic, including sourcing the defaults file, then tear it out of upstart/systemd/sysv and replace with refernce to script.
[22:31] <infinity> hallyn: The upshot of that sort of thing is that it makes maintaining all three inits super simple too, which is nice.
[22:31] <infinity> hallyn: You get to be a fence-sitting commitment-free developer with near zero effort.
[22:31] <hallyn> infinity: one bugaboo being that upstart wanted libvirtd -d, systemd does not.  so /etc/default/libvirt could cause problems.  but it shouldn't in the libvirt-stop-guests script
[22:32] <infinity> hallyn: What's "-d"?  Daemonize?
[22:32] <infinity> hallyn: If so, you were using upstart wrong.
[22:32] <infinity> hallyn: Using "-d" and then "expect daemon" is just obtuse.  upstart's default mode, without the "expect" is to want foreground processes, same as systemd.
[22:33] <infinity> hallyn: (sysv, OTOH, probably wants "-d" to be sane)
[22:33] <hallyn> yes
[22:34] <hallyn> luckily i can point to the author field and say i didn't do it :)
[22:34] <infinity> Heh.
[22:34] <ochosi> doko: just fyi, i'm the maintainer of that icon theme. as mentioned in the bugreport, we're trying to get this upstream too, but that might take a bit and we'd like to ship it by default in xubuntu 15.10
[22:34] <infinity> hallyn: Well, no point changing that bit now, if it works, it works.
[22:35] <infinity> hallyn: But if we had a time machine, I'd tell past Dustin he was wrong. :P
[22:35] <sarnold> ochosi: btw, it's nice to prefix every line with the other person's nickname, so they can read it all with /lastlog -hilight -- otherwise picking out the bits of conversation ten hours later is difficult
[22:36] <hallyn> ok those changes are made, but i still need to test the pre-inst bit.
[22:36] <ochosi> sarnold: i thought that was what i did?
[22:36] <hallyn> infinity: any harm in my waiting for morning to upload the new version?
[22:36] <ochosi> sarnold: oh, i guess you're referring to bluesabre not doing that before
[22:36] <sarnold> ochosi: ah, I'm sorry, I didn't notice the different nick between bluesabre and ochosi. /me hangs his head in shame.
[22:36] <ochosi> heh, no worries ;)
[22:37] <bluesabre> woops
[22:37] <infinity> hallyn: Not unless your users run wily-proposed.
[22:37] <infinity> hallyn: Which no one should.
[22:38] <bluesabre> doko: bug 1483914
[22:38] <bluesabre> doko: The Xubuntu team is shipping libreoffice, libreoffice-gtk, and libreoffice-style-elementary this cycle