[02:46] <sergiusens> slangasek: mind sponsoring/accepting the click's in https://launchpad.net/~sergiusens/+archive/ubuntu/ppa/+packages?field.name_filter=click&field.status_filter=published&field.series_filter= ? or do I need to ask separate people?
[03:10] <Ukikie> Has skype allowed/pushed/whatever an update for -partner?  According to them, the version that's in partner will be incompatible with the network July 1st.
[03:41] <slangasek> sergiusens: I will try to take a look at it.  But why does the 'finalize' log at https://bileto.ubuntu.com/log/2790/finalize/1/ show that the branches were merged before I clicked finalize?
[03:42] <sergiusens> slangasek: I tried to click and got "unautharized" error, maybe it did really trigger them?
[03:45] <slangasek> sergiusens: hmm, well I hope not
[03:51] <sergiusens> slangasek: cannot say much after that, first time I use bileto; I don't have permissions for lp:click nor this part of the command. The merges do say bileto bot
[04:53] <slangasek> sergiusens: indeed.  Could be a bug in bileto, I simply hope that it wasn't
[08:26] -queuebot:#ubuntu-release- Unapproved: mesa (zesty-proposed/main) [17.0.6-0ubuntu0.17.04.1 => 17.0.7-0ubuntu0.17.04.1] (core, xorg)
[09:01] -queuebot:#ubuntu-release- New source: python-os-traits (artful-proposed/primary) [0.3.1-0ubuntu1]
[09:31] <bluesabre> Hello release team,  is it possible to release thunar (xenial, yakkety, zesty) and xfce4-weather-plugin (xenial) into -proposed? We started the SRU process  a couple weeks ago, but I think these two got missed and never made it to the second step. https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1679488 and https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1688056
[09:31] <ubot5> Ubuntu bug 1679488 in thunar (Ubuntu Zesty) "Thunar freezes when left inactive for a while" [Undecided,In progress]
[09:31] <ubot5> Ubuntu bug 1688056 in xfce4-weather-plugin (Ubuntu Xenial) "Package outdated" [Undecided,In progress]
[09:56] <apw> bluesabre, hmmmm, can look in a little i suspect
[10:03] -queuebot:#ubuntu-release- Unapproved: accepted thunar [source] (zesty-proposed) [1.6.11-1ubuntu0.17.04.1]
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted thunar [source] (yakkety-proposed) [1.6.11-0ubuntu0.16.10.2]
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted thunar [source] (xenial-proposed) [1.6.11-0ubuntu0.16.04.2]
[10:10] -queuebot:#ubuntu-release- Unapproved: accepted xfce4-weather-plugin [source] (xenial-proposed) [0.8.9-0ubuntu0.16.04.1]
[10:33] -queuebot:#ubuntu-release- Unapproved: rejected mesa [source] (zesty-proposed) [17.0.7-0ubuntu0.17.04.1]
=== med_ is now known as Guest72612
[10:38] -queuebot:#ubuntu-release- Unapproved: mesa (zesty-proposed/main) [17.0.6-0ubuntu0.17.04.1 => 17.0.7-0ubuntu0.17.04.1] (core, xorg)
[10:47] -queuebot:#ubuntu-release- Unapproved: xfce4-weather-plugin (yakkety-proposed/universe) [0.8.7-3 => 0.8.9-0ubuntu0.16.10.1] (ubuntustudio, xubuntu)
[10:51] -queuebot:#ubuntu-release- Unapproved: accepted xfce4-weather-plugin [source] (yakkety-proposed) [0.8.9-0ubuntu0.16.10.1]
[11:45] <tjaalton> could someone override glbinding autopkgtest on armhf, it "fails" because current gcc adds some deprecation notifications to the test output. tests itself pass fine
[11:46] <apw> tjaalton, is someone going to sort out the tests for next time ?
[11:47] <tjaalton> as in modifying glbinding pkg?
[11:47] <tjaalton> maybe I should try that first
[11:52] <tjaalton> though I don't know how to best do that
[11:52] <tjaalton> right now it does
[11:52] <tjaalton> cmake .. && make && make test
[11:53] <tjaalton> and it's the output from 'make' that fails the autopkgtest
=== sforshee` is now known as sforshee
[11:58] <apw> tjaalton, you do not want to have to read the output for the tests every time for ever going forward to check it is overridable, so we want to do something with it
[11:59] <tjaalton> yes, but what
[12:00] <apw> i guess we have some options, 1) fix the code so it is no longer using the deprecated interfaces, 2) elide the deprecation errors from make component
[12:00] <apw> the first is ideal of course
[12:02] <tjaalton> I just wanted to update mesa, and now have to update glbinding :P
[12:02] <tjaalton> esp. since the debian maintainer isn't too active
[12:02] <tjaalton> this is the initial upload from last year
[12:02] <apw> heh life does suck sometimes
[12:02] <apw> it may of course not build .... la la la
[12:03] <apw> tjaalton, i guess if those are the only errors and you ahve checked them for your mesa we could just ignore them for your upload
[12:04] <apw> so they don't get a free pass forever in this version
[12:05] <tjaalton> there are no errors
[12:05] <tjaalton> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/g/glbinding/20170608_080105_30a3a@/log.gz
[12:05] <apw> tjaalton, there are failures when re-testing with your mesa update because of the warnings coming out, right ?
[12:05] <tjaalton> it's just the make output that makes it fial
[12:05] <tjaalton> fail
[12:05] <tjaalton> notifications, yes
[12:05] <tjaalton> and it's not because of mesa but something else
[12:06] <tjaalton> that changed in artful
[12:06] <tjaalton> mesa just triggered the autopkgtes
[12:06] <tjaalton> t
[12:06] <apw> tjaalton, so i am saying it would likely be reasonable to say we can ignore the failures for mesa if that is the only regression you have
[12:06] <tjaalton> it is
[12:09] <apw> tjaalton, ok done
[12:09] <tjaalton> thx'
[12:09] -queuebot:#ubuntu-release- Unapproved: libclc (xenial-proposed/universe) [0.2.0+git20150813-2 => 0.2.0+git20170213-1~16.04.1] (no packageset)
=== juergh_ is now known as juergh
[14:27] <jamespage> any archive-admins have a few cycles to review some new packages for OpenStack in the artful NEW queue?
[14:27] <jamespage> specifically: python-deprecation, pypowervm, python-ovsdbapp, python-zunclient and python-os-traits
=== ratliff_ is now known as ratliff
[15:28] <slashd> morning bdmurray (today's vanguard), I know you are sprinting and I don't want to take a lot of your time, but could you please have a look at theses uploads whenever you have time [1] - https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=lxd [2]- https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=vlan and if you have extra time to "Fix Released" percona-xtradb-cluster-5.5 that would be
[15:28] <slashd> awesome for us.
[15:29] <slashd> ddstreet ^
[15:31] <stgraber> looks like the snapcraft test is busted right now, most likely because of external code it's getting/running which appears to have changed
[15:31] <stgraber> that's blocking the push of a critical bugfix for LXD in artful so I'm going to be pushing a force-badtest for snapcraft
[15:36] <apw> stgraber, if you badtest it it will migrate, so it needs blocking
[15:36] <apw> stgraber, or you could skiptest lxd if that is its only blocker
[15:36] <stgraber> apw: I'm badtesting the old snapcraft from artful itself, not the one in artful-proposed (which seems to also be broken)
[15:37] <apw> stgraber, ahh ok
[15:37] <stgraber> apw: but indeed as it's the only failure for LXD, I could have gone with skiptest for LXD instead
[15:37] <stgraber> apw: I pinged kyrofa about it so upstream snapcraft can figure out what's going on here. AFAICT they're downloading bits from pip and running them, so it's likely external code which changed...
[15:37] <apw> stgraber, the second fatal change in pip in 2 weeks by the sounds of it
[15:38] <stgraber> yeah, I saw you and infinity pushed similar overrides to snapcraft...
[15:38] <stgraber> that's a big hint not to depend on external code in your package tests but given what snapcraft does, it might be kinda hard for them to do
[15:39] <apw> yeah
[16:16] -queuebot:#ubuntu-release- Unapproved: accepted vlan [source] (trusty-proposed) [1.9-3ubuntu10.4]
[16:31] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-proposed) [2.0.10-0ubuntu1~16.04.1]
[16:57] <slashd> sil2100, hi about LP: #1657256. My colleague Mmike told me that this particular fix is percona-xtradb-cluster-5.5 (only available in trusty) and the current fix doesn't apply to Xenial and late because it run 5.6 (totally different source code) and no upstream fix is made yet for 5.6 but there was one already for 5.5, does that make any difference ? if not it's totally fine, just wanted to bring this to the table since the
[16:57] <slashd> sru has been blocked. If you keep the decision to block the SRU, I'll talk to Mmike in order for him to create a upstream fix to 5.6 before SRU'ing 5.5
[16:57] <ubot5> Launchpad bug 1657256 in percona-xtradb-cluster-5.5 (Ubuntu) "Percona crashes when doing a a 'larger' update" [Medium,In progress] https://launchpad.net/bugs/1657256
[17:01] <sil2100> slashd: so the case here is that for us to release a fix somewhere in an older series it needs to be also present in the devel series - the package names are different but basically 5.6 replaces 5.5 in future releases
[17:05] <slashd> sil2100, yeah I though it wouldn't apply because it's totally 2 different versions, so I'll told MMike to start working on a 5.6 fix upstream, SRU'ing it, and then restart the SRU of 5.5 from skratch
[17:05] <sil2100> slashd: if we accept the 5.5 fix in trusty and people will upgrade to a future release, the fix will be gone
[17:06] <sil2100> slashd: this is the biggest worry and the main reason why we require the devel series to be released first
[17:07] <slashd> sil2100, true, and I'm totally in favour to have the fix release in devel release first. I just thought that since it was 2 different version it wouldn't apply in this particular, case but it's noted for future, thanks
[17:07] <sil2100> slashd: it doesn't have to be the *very same* fix, but the bug needs to be fixed
[17:07] <slashd> sil2100, sure, I'll pass the message to MMike and it's noted in my case for similar SRU situation.
[17:08] <slashd> thanks bdmurray and sil2100, much appreciated
[17:09] <slangasek> override_dh_fixperms:
[17:09] <slangasek> 	$(overridden_command) -Xetc/xdg/autostart/kalarm.autostart.desktop
[17:09] <slangasek> $ cat debian/lintian-overrides
[17:09] <slangasek> executable-not-elf-or-script etc/xdg/autostart/kalarm.autostart.desktop
[17:09] <slangasek> $
[17:09] <slangasek> mmmhmm
[17:09] <sil2100> slashd: thanks!
[17:11] -queuebot:#ubuntu-release- New binary: gir-to-d [amd64] (artful-proposed/universe) [0.9.0-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: gir-to-d [armhf] (artful-proposed/universe) [0.9.0-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: gir-to-d [i386] (artful-proposed/universe) [0.9.0-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: python-pyepsg [amd64] (artful-proposed/universe) [0.3.1-1] (no packageset)
[17:14] <slangasek> acheronuk: kalarm debian/copyright claims that the code is all GPL2+; the copyright in ./src/kalarmmigrateapplication.{cpp,h} does not agree
[17:15] -queuebot:#ubuntu-release- New: accepted kalarm [source] (artful-proposed) [4:16.12.3-0ubuntu1]
[17:16] -queuebot:#ubuntu-release- New: accepted python-pyepsg [amd64] (artful-proposed) [0.3.1-1]
[17:17] -queuebot:#ubuntu-release- New: accepted gir-to-d [amd64] (artful-proposed) [0.9.0-1]
[17:17] -queuebot:#ubuntu-release- New: accepted gir-to-d [i386] (artful-proposed) [0.9.0-1]
[17:17] <acheronuk> slangasek: oh. I didn't do the copyright updated for those, but will make sure any that are wrong are correct with the next upload
[17:17] -queuebot:#ubuntu-release- New: accepted libp11-openssl1.1 [amd64] (artful-proposed) [0.4.4-4]
[17:17] -queuebot:#ubuntu-release- New: accepted libp11-openssl1.1 [armhf] (artful-proposed) [0.4.4-4]
[17:17] -queuebot:#ubuntu-release- New: accepted libp11-openssl1.1 [ppc64el] (artful-proposed) [0.4.4-4]
[17:17] -queuebot:#ubuntu-release- New: accepted lua-argparse [amd64] (artful-proposed) [0.5.0-1]
[17:17] -queuebot:#ubuntu-release- New: accepted python-iso3166 [amd64] (artful-proposed) [0.8.git20170319-1]
[17:17] -queuebot:#ubuntu-release- New: accepted gir-to-d [armhf] (artful-proposed) [0.9.0-1]
[17:17] -queuebot:#ubuntu-release- New: accepted libp11-openssl1.1 [arm64] (artful-proposed) [0.4.4-4]
[17:17] -queuebot:#ubuntu-release- New: accepted libp11-openssl1.1 [s390x] (artful-proposed) [0.4.4-4]
[17:17] -queuebot:#ubuntu-release- New: accepted jquery-at.js [amd64] (artful-proposed) [1.5.3+dfsg.1-1]
[17:17] -queuebot:#ubuntu-release- New: accepted node-stream-assert [amd64] (artful-proposed) [2.0.3-1]
[17:17] -queuebot:#ubuntu-release- New: accepted libp11-openssl1.1 [i386] (artful-proposed) [0.4.4-4]
[17:18] <slangasek> acheronuk: this was not a regression vs. kdepim, and I have accepted the package.  should be fixed, though
[17:19] <acheronuk> slangasek: it will be. thanks for doing that :)
[17:19] <slangasek> acheronuk: also, see my skepticism above regarding the combination of a dh_fixperms override in debian/rules with a lintian override
[17:19] <acheronuk> noted, and now looking where that came from
[17:32] <acheronuk> slangasek: I'm doubtful we need any of that. I'll do a test build to see if we can throw that away and still have that autostart
[18:07] <Ampelbein> Hi. Is there anything missing for #1513567 to be reviewed? Do you need any more information?
[18:08] <Ampelbein> bug #1513567
[18:08] <ubot5> bug 1513567 in gwakeonlan (Ubuntu Xenial) "[SRU] There is no executable in this package" [High,In progress] https://launchpad.net/bugs/1513567
[18:10] -queuebot:#ubuntu-release- New binary: dpdk [ppc64el] (artful-proposed/main) [16.11.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[18:14] -queuebot:#ubuntu-release- New binary: dpdk [amd64] (artful-proposed/main) [16.11.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[18:15] -queuebot:#ubuntu-release- New binary: dpdk [i386] (artful-proposed/main) [16.11.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[18:18] -queuebot:#ubuntu-release- New binary: dpdk [arm64] (artful-proposed/main) [16.11.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[18:23] -queuebot:#ubuntu-release- New: accepted dpdk [amd64] (artful-proposed) [16.11.1-2]
[18:23] -queuebot:#ubuntu-release- New: accepted dpdk [i386] (artful-proposed) [16.11.1-2]
[18:23] -queuebot:#ubuntu-release- New: accepted dpdk [arm64] (artful-proposed) [16.11.1-2]
[18:23] -queuebot:#ubuntu-release- New: accepted dpdk [ppc64el] (artful-proposed) [16.11.1-2]
[19:09] -queuebot:#ubuntu-release- New binary: node-gulp-concat [amd64] (artful-proposed/universe) [2.6.1-1] (no packageset)
=== santa is now known as Guest22192
[20:39] -queuebot:#ubuntu-release- New binary: octave [ppc64el] (artful-proposed/universe) [4.2.1-1ubuntu1] (no packageset)
[20:55] -queuebot:#ubuntu-release- New binary: octave [i386] (artful-proposed/universe) [4.2.1-1ubuntu1] (no packageset)
[21:01] -queuebot:#ubuntu-release- New binary: octave [amd64] (artful-proposed/universe) [4.2.1-1ubuntu1] (no packageset)
[21:02] -queuebot:#ubuntu-release- New binary: octave [s390x] (artful-proposed/universe) [4.2.1-1ubuntu1] (no packageset)
[21:21] -queuebot:#ubuntu-release- New binary: octave [armhf] (artful-proposed/universe) [4.2.1-1ubuntu1] (no packageset)
[21:39] -queuebot:#ubuntu-release- New binary: octave [arm64] (artful-proposed/universe) [4.2.1-1ubuntu1] (no packageset)
=== cpaelzer_ is now known as cpaelzer
[23:10] -queuebot:#ubuntu-release- New binary: flask-htmlmin [amd64] (artful-proposed/universe) [1.2-1] (no packageset)
[23:14] <infinity> lan3y: I had to restart all but 3 ppc64el worker services for autopkgtest.  Not sure how or where to debug why they were dead, so if you feel like doing a post-mortem, please do.
=== lan3y is now known as Laney
[23:28] <Laney> infinity: Why did you have to?
[23:31] <infinity> Laney: Because they were all dead, only 3 things were running, yet hundreds in the queue.
[23:31] <infinity> Laney: Which implied to me that all the dead ones were maybe an issue.
[23:31] <infinity> Laney: But I dunno.
[23:31] <Laney> They're supposed to self-restart
[23:31] <Laney> Would be interesting if they didn't
[23:32] <infinity> Laney: "systemctl --all list-units autopkgtest\*|sort | grep dead" seems to disagree on that score.
[23:32] -queuebot:#ubuntu-release- Unapproved: cloud-init (trusty-proposed/main) [0.7.5-0ubuntu1.21 => 0.7.5-0ubuntu1.22] (ubuntu-cloud, ubuntu-server)
[23:33] <smoser> hi. there are now 2 cloud-init uploads in trusty  queue
[23:33] <smoser> could someone NACK my first? the first does not have a fix for bug 1379080
[23:33] <ubot5> bug 1379080 in cloud-init (Ubuntu Zesty) "update-grub-legacy-ec2 fails to detect xen kernel" [Medium,Fix released] https://launchpad.net/bugs/1379080
[23:33] <Laney> infinity: I'll look later on if you don't figure it out
[23:33] <Laney> Got to go watch election results / sleep
[23:33] <Laney> night
[23:34] <infinity> Laney: I'm about to go eat all the meat, hence the hand-off (which I assumed would catch you in the morninig, not now. :P)
[23:34] <infinity> morning.  Typing hard.
[23:35] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (trusty-proposed) [0.7.5-0ubuntu1.22]
[23:37] -queuebot:#ubuntu-release- Unapproved: rejected desktop-file-utils [source] (precise-proposed) [0.20-0ubuntu3.1]
[23:56] -queuebot:#ubuntu-release- Unapproved: maas (xenial-proposed/main) [2.1.5+bzr5596-0ubuntu1~16.04.1 => 2.2.0+bzr6054-0ubuntu2~16.04.1] (ubuntu-server)
[23:56] -queuebot:#ubuntu-release- Unapproved: maas (yakkety-proposed/main) [2.1.5+bzr5596-0ubuntu1~16.10.1 => 2.2.0+bzr6054-0ubuntu2~16.10.1] (ubuntu-server)
[23:57] -queuebot:#ubuntu-release- Unapproved: maas (zesty-proposed/main) [2.2.0~rc1+bzr5922-0ubuntu2 => 2.2.0+bzr6054-0ubuntu2~17.04.1] (ubuntu-server)