[00:00] <mwhudson> doko (or anyone else): any chance of uploading the co-installable go stuff today?
[00:01] <mwhudson> ibm are suggesting i update the s390x patch
[00:01] <doko> mwhudson, it's there for a few hours ...
[00:01] <mwhudson> oh!
[00:02] <mwhudson> i wonder why i didn't get bugmail
[00:02] <mwhudson> doko: thanks
[00:02] <doko> not yet migrated
[00:02] <mwhudson> oh because the bug wasn't reported against the right source packages, because they didn't exist yet
[00:03] <mwhudson> doko: migrated 18 mins ago apparently...
[00:03] <nacc> slangasek: ah, debian has already dropped it as a dep for php-letodms-lucene
[00:03] <mwhudson> ah -defaults hasn't migrated yet
[00:04] <mwhudson> should in the next run though
[00:05] <nacc> slangasek: LP: #1560737
[00:08] <slangasek> jdstrand: so, bug #1020598 is interesting; we've been carrying a delta to iptables to drop ipq support since quantal because "the kernel no longer supports ip_queue", yet the Debian package builds libipq just fine against xenial (and unblocks the perlipq package hanging around in -proposed). Do you remember this?
[00:09] <slangasek> nacc: php-letodms-lucene has an Ubuntu delta which seems to still be relevant.  Maybe needs to be a merge instead?
[00:09] <nacc> slangasek: ack, sorry! was looking at the wrong output
[00:11] <mwhudson> how often does britney run for xenial-proposed -> xenial-release?
[00:14] <nacc> slangasek: ah nm, no longer depends on zend-framework
[00:15] <slangasek> nacc: ok
[00:15] <doko> pitti, more locale issues: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/p/python3.5/20160322_210741@/log.gz
[00:16] <slangasek> doko: probably fixed by infinity's upcoming glibc upload
[00:17] <slangasek> doko: or at least, worked around - but the actual test failure in there doesn't look locale related?
[00:17] <slangasek> Now running lintian...
[00:17] <slangasek> Complex regular subexpression recursion limit (32766) exceeded at /usr/share/lintian/checks/cruft.pm line 939.
[00:17] <slangasek> nacc: ^^ ugh, what is this package
[00:17] <slangasek> (icinga-web)
[00:19] <doko> slangasek, yes, test_cmath failing, but only in debug mode... will have to wait until tomorrow
[00:19] <nacc> slangasek: a fairly old framework for monitoring systems and networks
[00:19] <nacc> slangasek: that's the web interface part
[00:20] <nacc> i think there is a 2.x at this point, but not packaged anywhere
[00:20] <nacc> afaict
[00:21] <nacc> slangasek: err, the web interface isn't
[00:21] <nacc> there is a icinga2 package
[00:21] <slangasek> yeah; and the icinga2 package has a wrong dep and is blocked in -proposed
[00:22] <nacc> slangasek: oh i see it now
[00:22] <slangasek> mwhudson: britney runs every minute, sees that a lock is taken, and goes back into its hole for 4 more weeks of winter
[00:22] <mwhudson> slangasek: i see, this is a "how long is a piece of string" question then
[00:24] <nacc> slangasek: so on consideration, if we can fix up icingaweb2, we can just remove icinga-web, i think?
[00:24] <nacc> no rev-deps?
[00:24] <slangasek> nacc: probably, if icinga2 is something you care about
[00:32] <nacc> slangasek: ok, patch for icingaweb2 posted in LP: #1544352
[00:33] <mwhudson> stgraber: the lxd test on i386 on http://autopkgtest.ubuntu.com/running.shtml looks unhappy?
[00:33] <slangasek> nacc: ok. is there a bug requesting removal of dh-make-php?
[00:33] <mwhudson> oh no, nm, it's going again
[00:33] <mwhudson> (thought it was stuck)
[00:33] <nacc> slangasek: i'll add it to LP : #1547183 if that's ok?
[00:33] <slangasek> nacc: sure
[00:37] <slangasek> nacc: re: icingaweb2, I will note that it seems suboptimal that Debian and Ubuntu have different spellings of 'zendframework'.  it looks like there are half a dozen packages in Debian that depend on it.  rather than needing to carry a delta for each of these, should we (eventually) sync up the zendframework package names?
[00:38] <nacc> slangasek: yeah it's quite annoying
[00:39] <nacc> we definitely should, i wonder why it happened
[00:39] <nacc> slangasek: i think they might be idfferent packages :/
[00:40] <slangasek> hmm, well, then this package that just got uploaded maybe won't dtrt ;)
[00:40] <nacc> well, i mean, different sources
[00:40] <nacc> they are the "same" but ubuntu has its own
[00:40] <nacc> i don't know why
[00:40] <slangasek> sure, I think because someone in Ubuntu was interested in packaging it before it was available in Debian
[00:40] <nacc> yeah, could be, and now we're out of date :)
[00:41] <slangasek> we don't have to get the packages in sync, but synchronizing on the package name would save us from having to carry delta on /other/ packages
[00:41] <nacc> we're older than oldstable at this point :)
[00:41] <nacc> agreed on the naming issue, though, i'll try to figure that out
[00:46] <mwhudson> golang-defaults has migrated too w00t
[00:53] <infinity> mwhudson: So, guessing we can remove golang, then?
[00:53] <mwhudson> infinity: yes
[00:53] <mwhudson> infinity: and golang-race-detector-runtime
[00:54] <mwhudson> infinity: want a bug or will you JFDI?
[00:55] <infinity> mwhudson: What produces golang-race-detector-runtime now?
[00:55] <mwhudson> infinity: golang-defaults
[00:55] <mwhudson> and it depends on the new golang-1.6-race-detector-runtime
[00:55] <infinity> Ta.  Both removed.
[00:55] <mwhudson> cool
[00:56] <mwhudson> infinity: golang-go.tools while you're there? :)
[00:56] <mwhudson> that was replaced by golang-golang-x-tools aaages ago
[00:57] <mwhudson> (the latter packages makes transitional dep packages)
[00:58] <infinity> golang-golang-x-tools ... What a lovely redundant name.
[00:58] <infinity> (And removed)
[00:59] <infinity> mwhudson: Thanks for doing this.  I really hope it makes future golang maintenance slightly less painful.
[00:59] <infinity> mwhudson: And we need to revisit trusty really soon, I guess. :/
[00:59] <mwhudson> infinity: so do i!
[00:59] <mwhudson> infinity: slangasek put himself on the hook for that, the fool :-p
[00:59] <infinity> Hah.
[00:59] <infinity> Excellent.
[00:59] <infinity> One more thing off my plate.
[01:00] <infinity> To be fair, now that you have the versioned golang-1.6 in xenial, it should be pretty much a straight backport.  Almost.
[01:00] <infinity> I'm guessing.
[01:00] <infinity> And then making $stuff in trusty build with the versioned paths.
[01:01] <mwhudson> oh yes that's a good point, we should backport the xenial golang-1.6, not the hacked up one i made
[01:01] <mwhudson> um
[01:02] <mwhudson> infinity: how do we do this and end up with a golang-1.6 package in trusty that has a lower version than the one in xenial? :)
[01:02] <slangasek> I should clearly buy galangal.com, so I can have a package called golang-galangal-root-dev
[01:02] <slangasek> mwhudson: add new changelog entry, copy previous version number, append ~14.04
[01:02] <mwhudson> slangasek: but this process starts by copying-with-binaries from xenial to trusty
[01:03] <slangasek> mwhudson: Russian nesting ppas
[01:03] <slangasek> you can build-depend on packages in a ppa not your own
[01:03] <mwhudson> ah right
[01:04] <mwhudson> and then you can upload a version that has a lower version than the ppa you b-d on
[01:04] <slangasek> yep
[01:04] <infinity> Yeah, should be nice and simple now.
[01:04] <infinity> Extra bonus to the defaults thing I forced on you. :P
[01:05] <slangasek> jdstrand: ignore my previous inquiry; I've confirmed that the ipq support Debian added back to iptables by copying a kernel header is useless on modern kernels
[01:06] <mwhudson> infinity: heh the only forced thing was getting it done in time for x, i think it's a good idea :-)
[01:06] <infinity> mwhudson: s/forced/encouraged/ :)
[01:13] <nacc> slangasek: ok, i think i'm stopping with updates for the day ... only 19 done out of 400 or so, but ... something!
[01:14] <nacc> slangasek: Pharaoh_Atem: we need to figure out a plan for drupal
[01:14] <nacc> drupal7 is in the archive & in debian, but doesn't support php7
[01:14] <nacc> drupal8 does, but isn't pacakged
[01:14]  * sarnold *shudders*
[01:14] <infinity> drupal should never have been packaged in the first place.
[01:14]  * nacc tends to agree
[01:15] <sarnold> http://people.canonical.com/~ubuntu-security/cve/pkg/drupal7.html
[01:15]  * mwhudson checks that golang-1.6 doesn't need to breaks the golang in trusty
[01:15] <nacc> and was going to ask if we could just drop it
[01:15]  * Pharaoh_Atem agrees violently
[01:15] <infinity> mwhudson: I'd assume all the new versioned paths won't have any conflicts.  But nice to be sure.
[01:15] <Pharaoh_Atem> can we drop *all* the web apps?
[01:15] <mwhudson> infinity: yeah, i'd certainly hope not
[01:15] <mwhudson> but assume make a etc etc
[01:16] <infinity> mwhudson: I, too, spell assume "etcetc".
[01:17] <nacc> infinity: sarnold: ok, drupal7 is close to a leaf package, so in terms of that, should be easy to drop (along with drupal7-mod-libraries). Just one update to civicrm to not build a drupal7 module.
[01:19] <Pharaoh_Atem> nacc: what about phpbb3 and wordpress?
[01:19] <Pharaoh_Atem> the former doesn't even HAVE a version that supports php7, and wp is just a nightmare
[01:20] <infinity> My personal opinion is that no webapps should ever be packaged, but I'm not sure I should be making that call alone. :P
[01:20] <infinity> I've certainly been losing that war for years.
[01:21] <nacc> Pharaoh_Atem: on my list to look at
[01:21] <Pharaoh_Atem> at least owncloud isn't in the archive anymore
[01:23] <slangasek> nacc: heh, the auto-sed of cacti results in debian/README.Debian making some interesting claims about suhosin support
[01:24] <slangasek> well. not actually auto in this case
[01:25] <nacc> slangasek: argh, sorry! i had dropped that bit in my local tree
[01:25] <nacc> i think that whole paragraph is wrong
[01:25] <slangasek> yep ;)
[01:26] <nacc> http://askubuntu.com/questions/298689/i-cant-get-apt-get-install-php5-suhosin-to-work
[01:26] <nacc> :)
[01:26] <nacc> slangasek: i am trying to review the pacakges at that level, which is making the process pretty slow
[01:26] <nacc> slangasek: i can send an updated debdiff for cacti tmrw with that removed
[01:27] <slangasek> nacc: I'm not sure that level of review is required, tbh. I just noticed it in passing
[01:31] <mwhudson> ah now the game of "waiting for publisher runs" begins
[02:03] <nacc> slangasek: yeah, it may not be, but i wanted to minimize my own mistakes
[02:22] <Pharaoh_Atem> suhosin is unnecessary these days
[02:22] <Pharaoh_Atem> just use fpm and protect it with SELinux or AppArmor
[02:25] <tsimonq2> what's the deal with all my PPAs using SHA-1, which is showing a warning as being weak when I update my computer..
[02:25] <tsimonq2> *computer...
[02:25] <Pharaoh_Atem> tsimonq2: the switch was flipped to enforce SHA-2 hashes for signatures
[02:25] <sarnold> tsimonq2: the fix is apparently in progress
[02:26] <tsimonq2> well I've seen the blog post from the apt team, but the fix is in progress for PPAs?
[02:26] <sarnold> yeah
[02:26] <sarnold> if you add e.g. a new xenial release to your ppa the signatures ought to be fixed quickly
[02:26] <sarnold> but they'll bulk-resign all ppas soon
[02:27] <tsimonq2> soon being hours, days, weeks, months, years, what?
[02:28] <sarnold> probably "days"
[02:28] <sarnold> https://lists.ubuntu.com/archives/ubuntu-devel/2016-March/039287.html
[02:29] <tsimonq2> okay, thank you sarnold :)
[02:30] <Unit193> sarnold: It already hit, if you'd upload a new source package (Eg, make it re-publish the PPA.)
[02:30] <Unit193> Source: The bug report I don't remember the number. :3
[02:30] <sarnold> hehe
[02:32] <Unit193> Just looking now to re-publish all of 'em.
[02:43] <tsimonq2> you guys got an API function to republish a PPA or do you have to do it all by hand?
[02:43] <tsimonq2> the latter would be painful
[02:43] <tsimonq2> *very* painful
[02:52] <rbasak> Do we have a Haskell guy? libghc-gnutls-dev 0.2-2 in Xenial ships /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.10.3/gnutls-0.2-BYccZTzDgCw38R5GwM0fsE/libHSgnutls-0.2-BYccZTzDgCw38R5GwM0fsE-ghc7.10.3.so which needs libgnutls-deb0.so.28 which doesn't exist in the archive.
[02:53] <rbasak> Rebuilding src:haskell-gnutls gives me a libghc-gnutls-dev that uses libgnutls.so.30 instead.
[02:53] <rbasak> I could just upload a no-change rebuild, but I wonder if this indicates that some wider check is needed.
[02:54] <sarnold> rbasak: i've got a vague feeling infinity handled the last pile of haskell changes
[02:55] <rbasak> Thanks. I've just found another with the same issue: libghc-network-protocol-xmpp-dev
[02:55] <rbasak> So I think we need a bunch of rebuilds.
[02:59] <rbasak> Where a bunch appears to equal two.
[06:40] <cpaelzer> good morning
[07:15] <pitti> Good morning
[07:15] <mwhudson> good evening
[07:21] <pitti> infinity, doko: after the two latest responses in bug 1534263 I'm inclined to approve this; WDYT?
[07:52] <infinity> pitti:
[07:52] <infinity> Setting up udev (229-3ubuntu1) ...
[07:52] <infinity> addgroup: The group `input' already exists as a system group. Exiting.
[07:52] <infinity> /var/lib/dpkg/info/udev.postinst: 109: [: Illegal number: *
[07:55] <pitti> infinity: yep, fixed in git already, bug 1560112
[07:56] <infinity> pitti: Does that break anything?
[07:56] <pitti> but it's just cosmetical, thus no reason to panic-upload
[07:56] <infinity> pitti: Kay.
[08:11] <dholbach> good morning
[08:25] <asac> beta coming today?
[08:25] <asac> :)
[08:26]  * asac considers to do the LTS->LTS upgrade test and wonders when is best time to be most useful :)
[08:26] <asac> ah its tomorrow... nevermind
[09:54] <cjwatson> tsimonq2: We will not have to do it by hand.  The thing I'm working on is some adjustments to the publishing scripts so that we can do a bulk run over everything without it taking all week.
[09:54] <Unit193> Still, thanks for the fix so far.
[10:05] <doko> infinity, seen on amd64: https://launchpadlibrarian.net/249606658/buildlog_ubuntu-xenial-amd64.python3.5_3.5.1-8_BUILDING.txt.gz
[10:06] <doko> (search for: final link failed)
[10:19] <doko> ok, this complaint seems to be valid, _math.o is built without -fPIC
[11:08] <darkxst> slangasek, upstream plymouth has proper hidpi support in git now (but no release as yet) do we want to cherry-pick the patches for 16.04? ricotz has test packages at https://launchpad.net/~ricotz/+archive/ubuntu/staging/+packages?field.name_filter=&field.status_filter=published&field.series_filter=xenial
[11:09] <LocutusOfBorg> hi folks, can anybody please explain this? https://launchpad.net/ubuntu/+source/fpc/3.0.0+dfsg-4/+build/9390047
[11:10] <LocutusOfBorg> Setting up fp-compiler-3.0.0 (3.0.0+dfsg-2) ...
[11:10] <LocutusOfBorg> An unhandled exception occurred at $0FE502D0:
[11:10] <LocutusOfBorg> EAccessViolation:
[11:10] <LocutusOfBorg>   $0FE502D0
[11:10] <LocutusOfBorg>   $0FE5E684
[11:10] <LocutusOfBorg>   $0FE152A8
[11:10] <LocutusOfBorg>   $0FE1537C
[11:11] <LocutusOfBorg> the build doesn't even start
[11:12] <darkxst> LocutusOfBorg, its failing before that though,
[11:12] <darkxst> dpkg: dependency problems prevent configuration of sbuild-build-depends-fpc-dummy:
[11:12] <darkxst>  sbuild-build-depends-fpc-dummy depends on fp-compiler; however:
[11:12] <darkxst>   Package fp-compiler is not configured yet.
[11:12] <darkxst>   Package fp-compiler-3.0.0 which provides fp-compiler is not configured yet.
[11:13] <mdeslaur> pitti: hi! can you take a look at the comment I've added in https://bugs.freedesktop.org/show_bug.cgi?id=85477 please?
[11:14] <LocutusOfBorg> darkxst, that part "Setting up fp-compiler-3.0.0" is before what your wrote :)
[11:15] <LocutusOfBorg> something really bad is happening on boost / ppc64el
[11:15] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/clblas/2.10-2/+build/9384486
[11:18] <darkxst> LocutusOfBorg, oh yes seems I skipped to the second error
[11:18] <LocutusOfBorg> :)
[11:18] <LocutusOfBorg> seems some sort of apt/dpkg/chroot/sbuild issue?
[11:20] <cjwatson> how would that be an sbuild issue?  /usr/include/boost/math/policies/policy.hpp:818:18: error: ‘__float128’ was not declared in this scope
[11:20] <darkxst> LocutusOfBorg, seems like an arch issue to me
[11:25] <mpt> Huh. I wasn’t expecting “sudo usermod -l 😌 testaccount” to work, but it does
[11:27] <LocutusOfBorg> cjwatson, sbuild issue is fpc
[11:28] <LocutusOfBorg> boost issue clblas
[11:28] <LocutusOfBorg> :)
[11:28] <cjwatson> sure, but you weren't desperately specific in the one I was replying to
[11:28] <LocutusOfBorg> yes, sorry
[11:28] <cjwatson> anyway, the fpc thing is also not an apt/dpkg/chroot/sbuild issue; the build-depended-on fpc itself is apparently blowing up
[11:33] <LocutusOfBorg> I don't understand sorry :)
[11:38] <cjwatson> LocutusOfBorg: dpkg tries to install fp-compiler-3.0.0; its postinst fails with the output you quoted.  this is not the fault of dpkg or any layer above it, but the fault of whatever the postinst is calling that's exploding, which is probably some bit of fp-compiler-3.0.0 itself.
[11:40] <LocutusOfBorg> and only on ppc64el :(
[11:40] <LocutusOfBorg> I have no porterstuff on ubuntu, and Debian is fine
[11:40] <ginggs> LocutusOfBorg: is that update-alternatives?
[11:40] <LocutusOfBorg> nice and trivial to debug :(
[11:42] <ginggs> LocutusOfBorg: i have a VM at OpenPower, lemme try...
[11:42] <LocutusOfBorg> that would be *awesome*
[11:43] <LocutusOfBorg> https://sources.debian.net/src/fpc/3.0.0%2Bdfsg-4/debian/fp-compiler.postinst.in/
[11:43] <LocutusOfBorg> this seems to the failing script?
[11:46] <cjwatson> the failing build you quoted is powerpc, not ppc64el
[11:47] <cjwatson> my guess would be that the failing thing is something itself implemented in Pascal, so probably fpcmkcfg
[11:47] <cjwatson> but that's a guess
[11:47] <LocutusOfBorg> the boost stuff is failing on ppc64el
[11:47] <LocutusOfBorg> the fpc on powerpc :)
[11:47] <cjwatson> see "not desperately specific" above
[11:47] <ginggs> aargh, i'm installing fpc on ppc64el :(
[11:48] <LocutusOfBorg> probably my bad connection is messing up the messages
[11:48] <ginggs> LocutusOfBorg: try to break one thing at a time
[11:55] <LocutusOfBorg> ginggs, I'm leaving because of bad connection, please upload/fix/send me a mail or whatever if you have updates <3
[12:13] <ginggs> hmm rebuilding clblas 2.10-1 also fails with ‘__float128’ was not declared in this scope on ppc64el
[12:23] <doko> ginggs, can you check if this is triggered by glibc 2.23?
[12:32] <ginggs> doko: sure, i'll have a look
[12:35] <ginggs> doko: i don't think so, clblas FTBFS on 2016-03-11 already http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160226-xenial.html
[12:54] <rbasak> update_excuses.html says "libmysqlclient-dev/amd64 unsatisfiable Depends: libmysqlclient20 (= 5.7.11-0ubuntu2)"
[12:54] <rbasak> But libmysqlclient20 5.7.11-0ubuntu2 is in xenial-proposed for amd64.
[12:54] <rbasak> Some help please?
[12:54] <slangasek> rbasak: check components
[12:55] <rbasak> Ah
[12:55] <rbasak> That'll be it, thanks.
[12:55] <rbasak> slangasek: mind moving libmysqlclient20 and mysql-{client,server}-5.7 to main, please?
[12:56] <rbasak> They will replace libmysqlclient18 and 5.6 when we're done.
[13:00] <slangasek> rbasak: done
[13:00] <rbasak> Thank you!
[13:23] <ginggs> LocutusOfBorg, cjwatson: same access violation when installing fp-compiler on real powerpc hardware
[13:27] <ginggs> and just running 'fpcmkcfg-3.0.0' also
[13:38] <doko> mvo, https://launchpad.net/ubuntu/+source/golang-github-mvo5-goconfigparser/0.2-0ubuntu5/+build/9322535
[13:40] <mvo> doko: thanks, I have a look
[13:46] <slangasek> mvo: morning! so I see that ubuntu-snappy FTBFS on powerpc with a test timeout; do you know if it's likely to build on a retry?
[13:50] <mvo> slangasek: good morning! I doubt it, it seems to be a bug in the gccgo, I will probably hvae to disable the test
[13:51] <slangasek> mvo: is it the test that's broken or the code under test?  should I just delete the old powerpc binaries instead?
[13:51] <mvo> slangasek: its hard to say, but if we could remove powerpc for now, that would be fine with me as well, its the only problematic arch
[13:56] <rbasak> slangasek: sorry, I missed mysql-client-core-5.7. Did you notice mysql-server-core-5.7 since that seems to be OK?
[13:57] <slangasek> rbasak: I noticed mysql-server-core, yeah, and missed the other. fixing now
[13:57] <rbasak> Thanks
[13:57] <rbasak> Skuggen: FYI ^^
[14:25] <slangasek> mvo: oops, ubuntu-snappy did build successfully on powerpc after a give-back; sorry ;)
[14:28] <superm1> rbasak: is 5.7 intended to replace 5.6 for beta?
[14:33] <TJ-> pitti: 2 users reporting udev 229-3ubuntu1 failing postinst with  "/var/lib/dpkg/info/udev.postinst: 109: [: Illegal number: * "  "
[14:35] <Son_Goku> slangasek: does Ubuntu not support UsrMerge?
[14:36] <Son_Goku> I distinctly remember that it was something Ubuntu looked into in the quantal days, but I don’t see any indications of it being supported
[14:36] <pitti> TJ-: already fixed in git, it's just cosmetical
[14:36] <pitti> TJ-: the postinst doesn't fail, it just spits out this warning
[14:37] <TJ-> pitti: ahhh, OK :) couldn't find a bug report for it
[14:37] <pitti> TJ-: bug 1560112
[14:37] <TJ-> pitti: strange; the launchpad search on the udev package didn't show that
[14:38] <pitti> TJ-: the source package is systemd
[14:38] <pitti> udev has been built from that since, hmm, looong ago
[14:39] <TJ-> pitti: oh, of course! I was caught out because there are some very recent 16.04 reports on the udev package
[14:44] <mvo> slangasek: heh, nice
[14:49] <rbasak> superm1: replace yes, not sure about beta.
[14:49] <rbasak> Which is a point. I wasn't expecting it to hit the archive this late. Am I OK to proceed with the transition during the beta freeze?
[14:49] <superm1> rbasak: ok i'm hoping not by beta because mythbuntu has some hardcoded stuff in the ubiquity plugin to configure 5.6 mysql
[14:50] <superm1> it's not a problem to change it to 5.7 other than it's a timing thing to make sure they both land in the right ISO image
[14:51] <rbasak> superm1: noted. I tagged block-proposed in bug 1528583 to ensure we hold off until I understand what we should do.
[14:52] <superm1> rbasak: ok thanks.  after beta no problem for me to adjust our code
[14:54] <rbasak> Skuggen: FYI ^^
[14:54] <rbasak> infinity: ^^ thoughts? Should we hold off?
[14:55] <slangasek> I guess at this point the only way to hold it off is by blocking it in britney
[14:56] <slangasek> if not already too late
[14:56] <slangasek> rbasak: can you open a proposed-migration blocking bug?
[14:56] <rbasak> slangasek: already done
[14:56] <slangasek> ok
[14:56] <rbasak> I think it's in time because the dep8 tests take quite a while.
[14:56] <slangasek> oh, also freeze, which means it needs hinting anyway, so good
[14:57] <slangasek> errr except it wasn't previously seeded so it's not in the freeze hint, oops ;)
[14:57] <slangasek> so blocking bug is it
[14:57] <rbasak> I used the "update to 5.7" bug but moved it to the new src:mysql-5.7 first. So I presume it'll work.
[14:58] <slangasek> should do, yes
[15:01] <Skuggen> rbasak: Ok
[15:13] <Son_Goku> nacc: so… I sorta/kinda cajoled Remi into porting libvirt-php to work on php7: https://gitlab.com/Conan_Kudo/libvirt-php7/commits/php7
[15:13] <Son_Goku> I’m going to try to see if I can get it upstreamed
[15:13] <Son_Goku> I really, really, really want to get it upstreamed
[15:14] <Son_Goku> I’m not a huge fan of maintaining a fork like this
[15:28] <nacc> Son_Goku: cool, also on my list to look at
[16:01] <ginggs> cjwatson: so fpc 3.0.0+dfsg-2 has become uninstallable on powerpc. I installed 2.6.4+dfsg-8 from wily and tried building 3.0.0+dfsg-4. It got to 99% and then hit an access violation
[16:02] <ginggs> [ 99%] Compiled package zorba
[16:02] <ginggs> An unhandled exception occurred at $0FE502D0:
[16:02] <ginggs> EAccessViolation:
[16:02] <ginggs>   $0FE502D0
[16:02] <ginggs>   $0FE5E684
[16:02] <ginggs>   $0FE152A8
[16:02] <ginggs>   $0FE1537C
[16:03] <slangasek> Son_Goku: no. UsrMerge is upside-down from the way a merged /usr should be done
[16:03] <Son_Goku> slangasek: how so?
[16:03] <slangasek> things should be merged into /, not into /usr
[16:03] <Son_Goku> why
[16:03] <pitti> err, no
[16:05] <Son_Goku> slangasek: merging things into / sounds like it’d make things harder, not easier
[16:07] <cjwatson> ginggs: I'm not going to be able to help further with this, I was just pointing in the right general direction to start with
[16:08] <ginggs> cjwatson: ok, i pinged you because i recall you have bootstrapped fpc in the past
[16:09] <cjwatson> ginggs: I can help with rebootstrapping given specific directions if that's what it needs, but not with the investigation along the way
[16:09] <cjwatson> I probably just did something mechanical based on Debian's binaries, if it was me
[16:32] <coreycb> bdmurray, can you reject the wily nova upload that is in the queue?  I am going to combine it with another sru.
[16:33] <bdmurray> coreycb: done
[16:33] <coreycb> bdmurray, thanks
[16:41] <pitti> slangasek: do you happen to know about watershed?
[16:42] <coreycb> bdmurray, can you also reject the python-oslo.messaging upload to wily dated 2016-03-18?
[16:43] <slangasek> pitti: sure
[16:44] <pitti> slangasek: if I run "/lib/udev/watershed sleep 5" n times, are the other n-1 instances actually supposed to hang until the first one finishes?
[16:44] <slangasek> pitti: yes
[16:44] <pitti> I wonder if that's a regression, or I just misunderstand how watershed works
[16:44] <slangasek> watershed serializes, but doesn't skip the calls
[16:44] <pitti> ah, then it's rather pointless to use watershed in an udev rule
[16:44] <slangasek> well
[16:45] <slangasek> the purpose is to avoid multiple calls to a thing running in parallel that shouldn't
[16:45] <pitti> slangasek: thanks, so I guess we'll either need to change watershed (it's only being used by that lvm rule and apport-noui) or find something else that's non-blocking
[16:45] <slangasek> but we can't just /drop/ the extra calls, because of races
[16:45] <slangasek> why non-blocking? because of udev rule timeouts?
[16:46] <pitti> that too, but blocking an udev rule blocks the worker, and there's only finitely many of them
[16:46] <pitti> so in that bug 1560710 with 50 LVs this leads to a deadock
[16:46] <slangasek> right
[16:46] <pitti> ok, I'll think about that, thanks for confirming that it's not a regression in watershed itself
[16:47] <slangasek> but are there expectations elsewhere in the system that the rule be synchronous?
[16:47] <infinity> How did I know that was going to be an IBM bug as soon as you said "50 LVs"
[16:47] <slangasek> yeah, it's not a regression, it's just IBM testing at scale
[16:47] <slangasek> ;)
[16:47] <pitti> slangasek: not really -- the only point is to run vgchange after the last pending LVM event got processed
[16:47] <slangasek> ok
[16:47] <tsimonq2> cjwatson: good :)
[16:48] <pitti> that can happen asynchronously (and it might cause more uevents due to the new block devices)
[16:48] <pitti> slangasek: at scale> yeah, not even smb managed to hit that limit :)
[16:48] <slangasek> pitti: so if the actual calls to vgscan/vgchange need to be serialized, maybe watershed itself should just be backgrounded in the rule?
[16:49] <infinity> pitti: In IBM's world, this isn't "at scale", this is "normal".
[16:49] <pitti> no, you can't background stuff from an udev rule
[16:49] <pitti> :)
[16:49] <smb> pitti, I would not be sure :-P
[16:49] <pitti> it'll get killed right after the main process exits (to avoid zombies)
[16:49] <infinity> Even our teeny tiny POWER8 machines from them are insanely overspecced.
[16:49] <slangasek> pitti: wellll that what would it matter if watershed "hung"?  or did you just not understand the purpose of watershed?
[16:49] <slangasek> s/that/then/
[16:50] <pitti> slangasek: obviously; I thought it woudl detect if the same command was already running, just re-inc the "refcount" of the first instance, and quit itself immediately
[16:50] <pitti> but apparently it's not doing that
[16:50] <slangasek> pitti: ah.  can't do that, because not guaranteed that the running command picked up the latest events
[16:50] <slangasek> that's the race I meant
[16:51] <pitti> slangasek: right, every further call would need to update some stamp file/thingy somewhere which resets the first instance's idea of "after"
[16:51] <slangasek> pitti: now, maybe what watershed should actually do is detect when there are *two* other watersheds running, and quietly exit any others
[16:52] <pitti> slangasek: hm, but how is that guaranteeing that the first or second one defers the re-run enough for the n-th invocation?
[16:52] <slangasek> because if you have 1 running, and 5 queued, when the first one exits you only need 1 of the other 5 to run to catch up
[16:52] <slangasek> not all 5 of them back-to-back
[16:52] <pitti> right, but the second one is just going to wait for #1, not for #17, no?
[16:52] <slangasek> and actually this would also address the boot-time load bugs we saw with apport-noui
[16:53] <pitti> well, I don't know how watershed detects duplicates of itself, maybe that already works
[16:53] <slangasek> it doesn't work
[16:53] <slangasek> I know for sure ;)
[16:53] <pitti> so, somewhere in teh system we need some kind of lock/stamp file with the command
[16:53] <pitti> and duplicate invocations need to touch that
[16:54] <slangasek> but if we made it do so, it would improve the scaling of watershed with AFAIK no downsides
[16:54] <infinity> No need for lock files.
[16:54] <pitti> and some running instance needs to defer the second run until after the current timestamp
[16:54] <sarnold> having N-2 of them exit may only work when the command that's called is idempotent
[16:54] <pitti> sarnold: it is
[16:54] <pitti> it's always exactly the same "/sbin/lvm vgscan; /sbin/lvm vgchange -a y"
[16:55] <pitti> the point is just to run it *after* the last pending LVM uevent
[16:55] <pitti> and avoid running multiple copies while a whole bunch of them is coming in in parallle
[16:55] <pitti> well, this is an ugly hack which we've been carrying for a decade, maybe this is all moot with modern versions, not sure
[16:58] <pitti> infinity: well, not necessarily lock files, but the watersheds must communicate with each other somehow if we don't want all of them to stick around indefinitely?
[16:58] <infinity> pitti: Instead of lockfiles, I'd think all it needs is a SIGUSR* handler.  New invocation of watershed sends signal to all running watersheds.  If running watershed is in "wait" state and /proc/<pid-of-process-that-signalled-us>/cmdline matches our own, exit immediately.
[17:00] <infinity> Once we transition from wait to running, just ignore SIGUSR and carry on to a normal exit.
[17:00] <coreycb> bdmurray, thanks.  if you or someone else on the sru team has some time we could use reviews of nova, python-oslo.messaging, and keystone in the wily queue.
[17:01] <chiluk> slangasek who should I talk to about auto package test SRU failures http://people.canonical.com/~ubuntu-archive/pending-sru.html ??  The failures for coreutils and initramfs-tools all look to be infrastructure issues.
[17:03] <pitti> infinity: nice idea; it currently communicates via /run/watershed/ files, but comparing /proc/pid/cmdline sounds easier indeed
[17:04] <sarnold> does ibm have any systems where 64k pids aren't enough? :) it might not be fun to find all watershed processes if there's a few hundred thousand or million processes running
[17:05] <pitti> well, hopefully with a change like this they would die much quicker
[17:05] <pitti> and thus there should only be at most one long-running one around
[17:05] <sarnold> sorry, I meant if the system has a few hundred thousand -other- processes running
[17:05] <pitti> oh, that's right
[17:05] <sarnold> say if someone goes nuts and runs a few hundred thousand ubuntu lxds
[17:05] <pitti> you mean that pidof takes too long
[17:06] <sarnold> yeah, that's a lot of getdents / open / read / close .. calls
[17:06] <pitti> so maybe we'll keep the /run/watershed/ files for now
[17:06] <slangasek> chiluk: pitti is a good resource for that :)
[17:06] <sarnold> a shared memory segment may be quicker
[17:06] <infinity> pitti: Yeah, I didn't realise it already uses the filesystem.  It just seems Wrong(tm) for a utility like this to touch files at all, given that one might not know exactly what system context it's being run in (pre-boot, mid-pivot, post-boot...)
[17:06] <sarnold> files for watershed specifically probably also fine
[17:06] <slangasek> infinity: we mount --move /run, though
[17:07] <infinity> slangasek: Fair.
[17:07] <chiluk> thanks slangasek.  Hey pitti.  it looks like the failures for initramfs-tools and coreutils on   http://people.canonical.com/~ubuntu-archive/pending-sru.html appear very bogus..
[17:07] <pitti> ok, but I guess we mostly agree to changing watershed instead of trying to invent a new tool which does that?
[17:08] <infinity> pitti: Fixing watershed to not have 200 copies of itself blocking on the same cmdline seems like the right thing to do regardless.
[17:08] <infinity> pitti: Time, of course (or lack thereof) may lead to other hacks that aren't the Right Thing. :P
[17:09] <pitti> chiluk: ah indeed; the kernel has lots of special cases, we can't currently test those for other triggers; can you please file a bug for it against auto-package-testing? For the time being, please ignore those
[17:09] <chiluk> sure thing will do.
[17:09] <pitti> well, we could increase the number of workers so that it hits the wall on 80 instead of 40 LVMs, at the expense of slowing down everything else
[17:10] <pitti> but that doesn't feel like a real solution
[17:11] <slangasek> infinity, pitti: I guess this seems straightforward to me; maybe I'll have a look at the watershed code
[17:11] <infinity> pitti: No, not a real solution at all and, while big iron can handle it, slangasek's note about this being a real problem on small devices for apport-noui as well leads to a "maybe it's time to just fix it right".
[17:11] <pitti> I'll update the bug then, thanks for the discussion
[17:13] <slangasek> sarnold: btw, regarding idempotency, cf. the watershed.c header - "for optimizing away unnecessary runs of idempotent commands".
[17:14] <sarnold> slangasek: yay :) my trusty system didn't have a manpage so it wasn't clear that it's only for idempotent calls..
[17:16] <infinity> sarnold: xenial also lacks a manpage for it. :)
[17:16] <infinity> Evidently, one is meant to read the source to determine if they want to use it.
[17:17] <sarnold> ah :) hehe
[17:17] <slangasek> infinity: or the package description; or just read Scott's mind
[17:17] <infinity> slangasek: I don't recommend the latter.
[17:18] <slangasek> and the package description says it is supposed to only result in one further attempt, instead of one for each call to watershed
[17:18] <slangasek> but I think we found that didn't work for apport-noui
[17:18] <slangasek> and regardless, the udev workers need to not block, rather than just not running extra copies of vgscan
[17:22] <pitti> FTR, it's still bearable to block one of them, so that the other's don't get deadlocked
[17:22] <slangasek> pitti: ok, just checked, and yes watershed *does* only run 2 copies of the command (the first one, and one at the end).  So the only issue is whether watershed itself blocks until the command has run
[17:23] <slangasek> if backgrounding the command doesn't work, then a --nowait option to watershed may be the thing
[17:23] <slangasek> (new option, to avoid breaking the existing contract, just in case)
[17:23] <pitti> AFAIUI, right now it's the last called instance of watershed which executes the second command, right?
[17:24] <pitti> and that'd need to become the first one, with some time stamp bumping/signal receiving/whatever
[17:24]  * pitti still reading watershed.c
[17:34] <pitti> hm, from the "Theory:" it's not clear how the second (last) time the command is actually ran
[17:34] <pitti> if all other invocations happen while the first one is stil running, none but the first can grab the lock, and it only runs the command if it can grab the lock
[17:50] <slangasek> pitti: so, all the processes in the "cohort", which are waiting for the currently-running process to finish, try to acquire the lock in parallel; whichever one succeeds first is the "lockholder" and runs the process; the others sit waiting for the lock held by the current process, and once it clears they read back the data from the cohort_fd (the file is unlinked, but the processes all have an open
[17:50] <slangasek>  fd to it, which defines the cohort)
[17:53] <slangasek> this makes it somewhat difficult to define a --no-wait option, since the process doesn't know if it's supposed to be the runner or not until it's succeeded in acquiring the lock
[18:28] <TJ-> who would be responsible for mariadb on the ubuntu side? some recent Debian changes incorporating passwordless auth via unix_socket has broken log-in over TCP for the same user
[18:28] <sarnold> TJ-: otto kek.... otto something :)
[18:29] <TJ-> sarnold: do you know if Otto Kekäläinen sits on the Ubuntu side as well Debian?
[18:29] <Skuggen> I think he does
[18:29] <TJ-> sarnold: I've just spent an interesting few hours debugging this with another user who reported it
[18:29] <Skuggen> rbasak: Right?
[18:30] <TJ-> Skuggen: thanks. I'll email him first and ask about this
[18:30] <sarnold> TJ-: I opened the bug so otto couldsee it 1561062
[18:30] <Skuggen> mysql-5.7 does something similar with a passwordless root user, but it only touches root@localhost, so not entirely sure how MariaDB does it
[18:34] <TJ-> Skuggen: that's the issue; root@localhost cannot log-in over TCP protocol when the GRANT .. identified via unix_socket is in place
[18:35] <Skuggen> Ah, right. Then we'll probably have the same issue in mysql-5.7
[18:37] <TJ-> Yes
[18:37] <TJ-> is unix_socket built-in on mysql too?
[18:37] <Skuggen> It's a plugin
[18:38] <Skuggen> The maintainer script checks if the root user has passwordless login. If it does, it enables the unix socket auth
[18:38] <TJ-> right, so it isn't affected out-of-the-box
[18:38] <Skuggen> You can change it back easily enough (though you'd need to be able to log in)
[18:39] <TJ-> the mariadb has built the module in and sets unix_socket for root by default
[18:45] <Skuggen> TJ-: You could try manually changing the plugin field in the user table and running flush privileges after
[19:00] <TJ-> Skuggen: tried that and many other things. The main problem is the other 2 user entries for root@[127.0.0.1|::1] are never reached because they're reversed to be 'localhost' despite any changes to /etc/hosts
[19:14] <Skuggen> TJ-: Even if you override --host when starting the client?
[19:16] <TJ-> Skuggen: that has no effect on what the server does. I just found a sneaky way to avoid the unix_socket rule - configuring te server with skip-name-resolve but that's hardly a solution, but it proves the other 2 rules added by these passwordless auth patches are useless when name-resolving is enabled
[19:28] <rbasak> TJ-, Skuggen: yeah, otto should be able to help. Whichever way we probably want to support the same use cases in the same way between MySQL and MariaDB - there's no reason to differ and we should come up with the same conclusion for both variants. And that's for Debian and Ubuntu as well. So would you mind raising your use case on the Debian MySQL mailing list please?
[19:29] <rbasak> In general Ubuntu is in sync with Debian with both MySQL and MariaDB now, apart from release-time differences, so we'll want to fix this in Debian.
[19:58] <doko> pitti, a quick reminder how I run autopkg tests against a version in -proposed? (mpdecimal)
[20:07] <doko> rbasak, squid3 is still blocked by some manual testing. did that happen?
[20:10] <mwhudson> is/was lxc broken on xenial? http://paste.ubuntu.com/15480646/
[20:23] <doko> barry, you accepted the last mksh, please could you have a look at the pdksh removal: http://people.canonical.com/~ubuntu-archive/nbs.html
[20:23] <barry> doko: ack
[20:23] <doko> ta
[20:34] <barry> doko: pdksh revdeps are all safe since they conditionally dep on pdksh, e.g.: Depends: ${misc:Depends}, ${shlibs:Depends}, ksh | mksh | pdksh | zsh,
[20:34] <barry>  
[20:34] <barry> i can file bugs in debian (haven't checked yet) to get rid of them, but i don't think we need to update them in ubuntu to remove pdksh
[20:36] <LocutusOfBorg> ginggs, thanks
[20:37] <doko> barry, no, that's good enough. thanks for checking. removing the binary
[21:21] <balloons> barry, I added a new one for your python3 quest :-) , just fyi: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1561210
[21:21] <barry> balloons: \o/  - let me know if i can help
[21:22] <balloons> barry, sounds like it's trivial, but just wanted to make sure you knew about it, since it's definitely going to be on the image
[21:22] <barry> balloons: which image?
[21:25] <balloons> well presumably your crusade thus far is only against the desktop images right?
[21:25] <balloons> in which case you are safe
[21:26] <barry> balloons: server too
[21:26] <barry> which i think has been py2 free for a while
[21:28] <balloons> yea, here I thought juju was on the server image
[21:28] <balloons> I guess if you care about all packages in main it applies :-)
[22:15] <nacc> Pharaoh_Atem: fyi: rebuilt wordpress seems to work fine with php7
[22:16] <nacc> jgrimm: --^
[22:17] <jgrimm> nice!
[23:30] <mwhudson> sigh, i thought i'd started on ubuntu dev when it was safe to pretend cdbs didn't exist
[23:32] <nacc> mwhudson: :) i've hit it a few times too