[01:48] -queuebot:#ubuntu-release- New: accepted scram [amd64] (artful-proposed) [0.14.0-1]
[01:48] -queuebot:#ubuntu-release- New: accepted scram [armhf] (artful-proposed) [0.14.0-1]
[01:48] -queuebot:#ubuntu-release- New: accepted scram [ppc64el] (artful-proposed) [0.14.0-1]
[01:48] -queuebot:#ubuntu-release- New: accepted scram [arm64] (artful-proposed) [0.14.0-1]
[01:48] -queuebot:#ubuntu-release- New: accepted scram [s390x] (artful-proposed) [0.14.0-1]
[01:48] -queuebot:#ubuntu-release- New: accepted scram [i386] (artful-proposed) [0.14.0-1]
[01:49] -queuebot:#ubuntu-release- New: accepted poppler [amd64] (artful-proposed) [0.57.0-0ubuntu1]
[01:49] -queuebot:#ubuntu-release- New: accepted poppler [armhf] (artful-proposed) [0.57.0-0ubuntu1]
[01:49] -queuebot:#ubuntu-release- New: accepted poppler [ppc64el] (artful-proposed) [0.57.0-0ubuntu1]
[01:49] -queuebot:#ubuntu-release- New: accepted poppler [arm64] (artful-proposed) [0.57.0-0ubuntu1]
[01:49] -queuebot:#ubuntu-release- New: accepted poppler [s390x] (artful-proposed) [0.57.0-0ubuntu1]
[01:49] -queuebot:#ubuntu-release- New: accepted poppler [i386] (artful-proposed) [0.57.0-0ubuntu1]
[01:51] -queuebot:#ubuntu-release- New: accepted tss2 [amd64] (artful-proposed) [1045-1]
[01:51] -queuebot:#ubuntu-release- New: accepted tss2 [armhf] (artful-proposed) [1045-1]
[01:51] -queuebot:#ubuntu-release- New: accepted tss2 [ppc64el] (artful-proposed) [1045-1]
[01:51] -queuebot:#ubuntu-release- New: accepted tss2 [arm64] (artful-proposed) [1045-1]
[01:51] -queuebot:#ubuntu-release- New: accepted tss2 [s390x] (artful-proposed) [1045-1]
[01:51] -queuebot:#ubuntu-release- New: accepted tss2 [i386] (artful-proposed) [1045-1]
[01:51] -queuebot:#ubuntu-release- New: accepted erlang-asciideck [amd64] (artful-proposed) [0.0+git20170714.48cbfe8b-1]
[01:51] -queuebot:#ubuntu-release- New: accepted erlang-asciideck [armhf] (artful-proposed) [0.0+git20170714.48cbfe8b-1]
[01:51] -queuebot:#ubuntu-release- New: accepted erlang-asciideck [ppc64el] (artful-proposed) [0.0+git20170714.48cbfe8b-1]
[01:51] -queuebot:#ubuntu-release- New: accepted erlang-asciideck [arm64] (artful-proposed) [0.0+git20170714.48cbfe8b-1]
[01:51] -queuebot:#ubuntu-release- New: accepted erlang-asciideck [s390x] (artful-proposed) [0.0+git20170714.48cbfe8b-1]
[01:51] -queuebot:#ubuntu-release- New: accepted erlang-asciideck [i386] (artful-proposed) [0.0+git20170714.48cbfe8b-1]
[01:52] -queuebot:#ubuntu-release- New: accepted libgtop2 [amd64] (artful-proposed) [2.37.90-0ubuntu1]
[01:52] -queuebot:#ubuntu-release- New: accepted libgtop2 [armhf] (artful-proposed) [2.37.90-0ubuntu1]
[01:52] -queuebot:#ubuntu-release- New: accepted libgtop2 [ppc64el] (artful-proposed) [2.37.90-0ubuntu1]
[01:52] -queuebot:#ubuntu-release- New: accepted libgtop2 [arm64] (artful-proposed) [2.37.90-0ubuntu1]
[01:52] -queuebot:#ubuntu-release- New: accepted libgtop2 [s390x] (artful-proposed) [2.37.90-0ubuntu1]
[01:52] -queuebot:#ubuntu-release- New: accepted libgtop2 [i386] (artful-proposed) [2.37.90-0ubuntu1]
[01:52] -queuebot:#ubuntu-release- New: accepted clj-tuple-clojure [amd64] (artful-proposed) [0.2.2-1]
[01:52] -queuebot:#ubuntu-release- New: accepted cpath-clojure [amd64] (artful-proposed) [0.1.2-1]
[01:52] -queuebot:#ubuntu-release- New: accepted crypto-random-clojure [amd64] (artful-proposed) [1.2.0-1]
[01:52] -queuebot:#ubuntu-release- New: accepted hiccup-clojure [amd64] (artful-proposed) [1.0.5-1]
[01:52] -queuebot:#ubuntu-release- New: accepted maven-reporting-api [amd64] (artful-proposed) [3.0-1]
[01:52] -queuebot:#ubuntu-release- New: accepted raynes-fs-clojure [amd64] (artful-proposed) [1.4.6-1]
[01:52] -queuebot:#ubuntu-release- New: accepted clj-yaml-clojure [amd64] (artful-proposed) [0.4.0-1]
[01:52] -queuebot:#ubuntu-release- New: accepted fast-zip-clojure [amd64] (artful-proposed) [0.5.0-1]
[01:52] -queuebot:#ubuntu-release- New: accepted maven-reporting-exec [amd64] (artful-proposed) [1.3-1]
[01:53] -queuebot:#ubuntu-release- New: accepted crypto-equality-clojure [amd64] (artful-proposed) [1.0.0-1]
[01:53] -queuebot:#ubuntu-release- New: accepted riddley-clojure [amd64] (artful-proposed) [0.1.14-1]
[01:53] -queuebot:#ubuntu-release- New: accepted instaparse-clojure [amd64] (artful-proposed) [1.4.7-1]
[03:19] -queuebot:#ubuntu-release- New binary: fast-zip-visit-clojure [amd64] (artful-proposed/universe) [1.0.2-1] (no packageset)
[03:19] -queuebot:#ubuntu-release- New binary: specter-clojure [amd64] (artful-proposed/universe) [1.0.2-2] (no packageset)
[04:10] <slangasek> bjf, apw: the transition is ready to go now except for linux; I'm going to drop the tag long enough to let autopkgtests start and then I'll re-set it, but it would be good to have a decision ASAP on letting that package transition
[04:34] -queuebot:#ubuntu-release- New: accepted fast-zip-visit-clojure [amd64] (artful-proposed) [1.0.2-1]
[04:34] -queuebot:#ubuntu-release- New: accepted specter-clojure [amd64] (artful-proposed) [1.0.2-2]
[05:15] -queuebot:#ubuntu-release- New binary: jellyfish1 [amd64] (artful-proposed/none) [1.1.11-1] (no packageset)
[05:49] -queuebot:#ubuntu-release- New binary: dpdk [ppc64el] (artful-proposed/main) [17.05.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[05:55] -queuebot:#ubuntu-release- New binary: dpdk [i386] (artful-proposed/main) [17.05.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[05:58] <slangasek> bjf, apw: ok well that didn't go quite according to plan, I overlooked that linux is special cased and doesn't actually get autopkgtest runs triggered by proposed-migration so it immediately became a candidate and has migrated :/  Since the only autopkgtest regressions are the build failure with gcc-7, if there are no other bugs I think we should roll with this
[06:04] -queuebot:#ubuntu-release- New binary: dpdk [amd64] (artful-proposed/main) [17.05.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[06:18] -queuebot:#ubuntu-release- New binary: dpdk [arm64] (artful-proposed/main) [17.05.1-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[06:18] <cpaelzer> jamespage: the new sync of DPDKis in a-p as discussed https://launchpad.net/ubuntu/+source/dpdk/17.05.1-2
[06:19] <cpaelzer> jamespage: but as you can see currently held at the new queue which blocks you from bringin the new OVS in
[06:19] <cpaelzer> anyone around who can help with the new queue in that case
[06:19] <cpaelzer> It is the common case where this is only a sync and things are already through the new queue in Debian
[06:21] -queuebot:#ubuntu-release- New: accepted dpdk [amd64] (artful-proposed) [17.05.1-2]
[06:21] -queuebot:#ubuntu-release- New: accepted dpdk [i386] (artful-proposed) [17.05.1-2]
[06:21] -queuebot:#ubuntu-release- New: accepted dpdk [arm64] (artful-proposed) [17.05.1-2]
[06:21] -queuebot:#ubuntu-release- New: accepted dpdk [ppc64el] (artful-proposed) [17.05.1-2]
[06:21] -queuebot:#ubuntu-release- New: accepted jellyfish1 [amd64] (artful-proposed) [1.1.11-1]
[06:22] <cpaelzer> whoever that was - thanks!
[06:44] <apw> slangasek, that is fine, i think we are happy with it as we can be.  as you say the gcc thing is going to affect the next upload not this one
[07:49] <LocutusOfBorg> thanks slangasek for the fixes! somewhat I read that copy-package was requiring an AA intervention for being accepted
[07:49] <LocutusOfBorg> I even mentioned it here
[07:49] <LocutusOfBorg> I'm going to reupload now that the migration is completed :)
[09:09] <LocutusOfBorg> slangasek, I'm redoing the gmime rebuilds, for some reasons your "rebuild against gmime3" picked up the old 2.6
[09:16] <mwhudson> omg pytest migrated
[09:28] <apw> mwhudson, 830odd somethings migrated
[09:28] <LocutusOfBorg> slangasek, I asked to process gmime2.6 from debian new queue
[09:28] <LocutusOfBorg> I'm thinking about asking you to promote in main, and demote the current gmime in universe
[09:29] <LocutusOfBorg> so we can end this transition, and when Debian switches the default again, we can think about promoting it again
[09:29] <LocutusOfBorg> what do you think?
[09:30] <mwhudson> apw: yeah indeed
[09:30] <LocutusOfBorg> mmm there is a better solution
[09:31] <LocutusOfBorg> patch grilo-plugins to work with gmime3 and forget about the 2.6, all the stuff is in universe fortunately
[09:32] <apw> cpaelzer, they get a more relaxed approach as they ahve passed New in debian yes, but it still takes a human
[09:33] <LocutusOfBorg> apw, any news wrt xchat in new queue?
[09:33] <apw> LocutusOfBorg, xchat again ?
[09:33] <LocutusOfBorg> yes, I started maintaining it
[09:33] <LocutusOfBorg> I fixed all the CVEs, and the outstanding issues
[09:33] <LocutusOfBorg> and reintroduced in debain
[09:33] <LocutusOfBorg> debian
[09:34] <LocutusOfBorg> but for some reasons, the autosync didn't ppick it
[09:34] <apw> it is likely blacklisted as it has been removed
[09:39] <apw> confirmed as it has been deleted it auto blacklists a new sync
[09:45] <acheronuk> what is the issue in GCC7 that needs fixing?
[09:48] <LocutusOfBorg> apw, will you do some magic please?
[09:49] <LocutusOfBorg> acheronuk, basically AFAIK it breaks the kernel builds
[09:50] <acheronuk> oh. just trying to work out if some build failures I'm getting are a related issue
[09:51] <LocutusOfBorg> http://autopkgtest.ubuntu.com/packages/linux/artful
[09:51] <LocutusOfBorg> http://autopkgtest.ubuntu.com/packages/linux/
[09:51] -queuebot:#ubuntu-release- New: accepted xchat [sync] (artful-proposed) [2.8.8-8]
[09:56] -queuebot:#ubuntu-release- New binary: xchat [ppc64el] (artful-proposed/none) [2.8.8-8] (no packageset)
[09:58] -queuebot:#ubuntu-release- New binary: xchat [i386] (artful-proposed/none) [2.8.8-8] (no packageset)
[09:59] -queuebot:#ubuntu-release- New binary: xchat [amd64] (artful-proposed/none) [2.8.8-8] (no packageset)
[10:00] -queuebot:#ubuntu-release- New: rejected insighttoolkit4 [armhf] (artful-proposed) [4.12.0-dfsg1-1ubuntu2]
[10:00] -queuebot:#ubuntu-release- New: rejected insighttoolkit4 [s390x] (artful-proposed) [4.12.0-dfsg1-1ubuntu2]
[10:00] -queuebot:#ubuntu-release- New: rejected insighttoolkit4 [ppc64el] (artful-proposed) [4.12.0-dfsg1-1ubuntu2]
[10:00] <apw> ^ ftbfs on other arches and superceeded source ...
[10:01] -queuebot:#ubuntu-release- New binary: xchat [armhf] (artful-proposed/none) [2.8.8-8] (no packageset)
[10:04] -queuebot:#ubuntu-release- New binary: xchat [arm64] (artful-proposed/none) [2.8.8-8] (no packageset)
[10:05] <LocutusOfBorg> apw, I know it is superseeded, I didn't sync again, hopefully it will start automatically
[10:05] <LocutusOfBorg> will have a look thanks
[10:06] <LocutusOfBorg> oh you are talking about itk4
[10:06] <LocutusOfBorg> yes, I'm looking with upstream to fix it
[10:06] <LocutusOfBorg> and Debian
[10:06] <LocutusOfBorg> I did test in ppa the new castxml, but I failed in enabling proposed, so the build went good for other reasons (gcc-6)
[10:08] <apw> LocutusOfBorg, if you are answering for xchat, the comment was for insighttoolkit4
[10:08] -queuebot:#ubuntu-release- New binary: xchat [s390x] (artful-proposed/none) [2.8.8-8] (no packageset)
[10:08] <LocutusOfBorg> yes, got it
[10:08] <LocutusOfBorg> actually xchat has two new uploads in debian
[10:09] <LocutusOfBorg> will they be autosyncd?
[10:09] <LocutusOfBorg> (this is why I wrongly got the superseeded source against xchat)
[10:09] <apw> LocutusOfBorg, it appears to be blacklisted because it was most recently removed, so i think it will, i think
[10:09] <LocutusOfBorg> so you removed that block?
[10:10] <LocutusOfBorg> I'll wait 24h and see then :)
[10:10] <apw> 6 i think
[10:10] <LocutusOfBorg> I fixed a nasty bug and two CVEs, this is why I'm wondering about it
[10:10] <LocutusOfBorg> (the non-utf8 by default issue)
[10:12] <apw> well luckily it is devel so cves are not in of themselves quite so urgent
[10:12] <ginggs> LocutusOfBorg: xchat should auto sync again now after the manual sync.  it is not listed here http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt (i'm not sure where the auto blacklist for removed packages lives)
[10:13] <ginggs> but the auto blacklist for removed packages seems to be cleared after a manual sync without manual intervention
[10:13] <LocutusOfBorg> thanks, now it is even built everywhere lets wait some hours
[10:13] <apw> ginggs, in the source for auto-sync
[10:16] <ginggs> apw: ah ok, thanks. so if package-was-removed then do-not-sync, and once package is manually sync'd then package-was-removed is no longer true ?
[10:16] <apw> it looks at the last publication record, and if that is Deleted with reason it assumes you intended it gone (to my reading)
[10:17] <apw> once a sync is manually done the last record is a Published so it should not match
[10:21] -queuebot:#ubuntu-release- New: accepted xchat [amd64] (artful-proposed) [2.8.8-8]
[10:21] -queuebot:#ubuntu-release- New: accepted xchat [armhf] (artful-proposed) [2.8.8-8]
[10:21] -queuebot:#ubuntu-release- New: accepted xchat [ppc64el] (artful-proposed) [2.8.8-8]
[10:21] -queuebot:#ubuntu-release- New: accepted xchat [arm64] (artful-proposed) [2.8.8-8]
[10:21] -queuebot:#ubuntu-release- New: accepted xchat [s390x] (artful-proposed) [2.8.8-8]
[10:21] -queuebot:#ubuntu-release- New: accepted xchat [i386] (artful-proposed) [2.8.8-8]
[10:22] <apw> LocutusOfBorg, ^
[10:22] <LocutusOfBorg> <3
[10:22] <LocutusOfBorg> btw strangely enough I got already emails of people thanking me for bringing it back
[10:30] <smb> LocutusOfBorg, as long as you guys are not taking away hexchat... I just don't want to do another change... :-P
[10:34] <LocutusOfBorg> smb, I don't plan to :)
[10:34] <LocutusOfBorg> apw, autopkgtest for linux/unknown: armhf: Regression
[10:34] <LocutusOfBorg> (mumactl)
[10:43] <apw> LocutusOfBorg, that means it got lost, i would recommend a retry
[10:44] <Ukikie> LocutusOfBorg: But why?
[12:03] <LocutusOfBorg> apw, isn't kernel autopkgtest broken?
[12:03] <LocutusOfBorg> isn't ignore better?
[12:05] <LocutusOfBorg> well, somebody sorted it out in the meanwhile
[12:05] <LocutusOfBorg> ta
[12:44] -queuebot:#ubuntu-release- Unapproved: logrotate (trusty-proposed/main) [3.8.7-1ubuntu1.1 => 3.8.7-1ubuntu1.2] (core)
[12:45] -queuebot:#ubuntu-release- Unapproved: logrotate (zesty-proposed/main) [3.8.7-2ubuntu3 => 3.8.7-2ubuntu3.1] (core)
[12:55] <slashd> sil2100, Do you have a moment to approve the upload of "logrotate" for Trusty, Xenial and Zesty ?
[12:57] -queuebot:#ubuntu-release- Unapproved: logrotate (xenial-proposed/main) [3.8.7-2ubuntu2.16.04.1 => 3.8.7-2ubuntu2.16.04.2] (core)
[12:58] <sil2100> slashd: I can take a look at it in 15 mins :)
[13:00] <slashd> sil2100, thanks ;)
[13:00] -queuebot:#ubuntu-release- Unapproved: libsdl2 (trusty-proposed/universe) [2.0.2+dfsg1-3ubuntu1.1 => 2.0.2+dfsg1-3ubuntu1.2] (no packageset)
[13:20] <sil2100> slashd: hm, I'll need to wait a bit, debdiff not generated yet
[13:25] <slashd> sil2100, ok no worries
[13:48] <tjaalton> infinity: the xenial release notes say that 16.04.3 is supported for five years..
[13:48] <tjaalton> https://wiki.ubuntu.com/XenialXerus/ReleaseNotes
[13:49] <apw> that i am sure is intended to mean from the initial GA of xenial
[13:49] <apw> not that is what the words appear to actually say
[14:02] <tjaalton> it's confusing a certain vendor at least, since the lts-stack page does say the stack is only supported for 6mo
[14:02] <tjaalton> tseliot: you fixed the page?
[14:11] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.26.10~14.04 => 2.27~14.04] (no packageset)
[14:11] -queuebot:#ubuntu-release- Unapproved: snapd (zesty-proposed/main) [2.26.10+17.04 => 2.27+17.04] (desktop-core, ubuntu-server)
[14:11] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.26.10 => 2.27] (desktop-core, ubuntu-server)
[14:12] -queuebot:#ubuntu-release- New binary: qtwebengine-opensource-src [amd64] (artful-proposed/universe) [5.9.1+dfsg-2build2] (kubuntu)
[14:14] <tjaalton> ah, dropped .3
[14:21] <tseliot> tjaalton: yes
[14:21] <tseliot> tjaalton: we talked about it in #ubuntu-devel
[14:22] <tjaalton> ok
[14:42] <slashd> sil2100, how long it takes for the debdiff to be generated ? does it means I'll have to request the approval tomorrow ?
[14:42] <sil2100> slashd: no, it's done now, but it was generating really long - I'm reviewing it inbetween stuff
[14:43] <slashd> sil2100, oh ok, much appreciated
[14:48] <sil2100> Funny, since the diff is really small, duh
[14:48] <sil2100> Maybe it was busy
[15:01] -queuebot:#ubuntu-release- New binary: qtwebengine-opensource-src [i386] (artful-proposed/universe) [5.9.1+dfsg-2build2] (kubuntu)
[15:13] -queuebot:#ubuntu-release- Unapproved: accepted logrotate [source] (zesty-proposed) [3.8.7-2ubuntu3.1]
[15:15] -queuebot:#ubuntu-release- Unapproved: accepted logrotate [source] (xenial-proposed) [3.8.7-2ubuntu2.16.04.2]
[15:17] -queuebot:#ubuntu-release- Unapproved: accepted logrotate [source] (trusty-proposed) [3.8.7-1ubuntu1.2]
[15:25] <slashd> sil2100, ^^ thanks
[15:33] <sil2100> yw o/
[15:52] <blackboxsw> bdmurray: good morning.  I was wondering if you are the person to ping related to getting a recent cloud-init  package upload queued for SRU testing?
[15:55] <blackboxsw> we have a package update for xenial and zesty that has around 10 bug fixes that we would to start SRU verification testing if possible. https://trello.com/c/CAjwe8LX/273-cloud-init-sru-zesty-xenial
[15:56] <bdmurray> blackboxsw: Are you refering to this? https://launchpad.net/ubuntu/zesty/+queue?queue_state=1&queue_text=cloud-init
[16:01] <blackboxsw> bdmurray: yep that's the ticket, didn't know the process of how to bring that up and I knew smoser queued the content/request last week
[16:03] <bdmurray> blackboxsw: I talked to smoser about last week and said that I thought the upload looked more like a new upstream microrelease than a stable release update with only bug fixes.
[16:11] <blackboxsw> bdmurray: ok.  Does that mean we need to provide additional documentation to you on those existing microfeature bugs so that it's possible to queue the SRU request?  I thought cloud-init had a SRU verification exception if a micro-feature is introduced because of our existing integration testing we perform on target releases.
[16:12] <bdmurray> blackboxsw: No special case has been created for cloud-init - https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases
[16:12] <blackboxsw> ahh rharper corrected me on this that it was curtin
[16:14] <bdmurray> blackboxsw: Also see https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
[16:14] <blackboxsw> bdmurray: excellent, thx for the link. As you can tell, my first cloud-init SRU rodeo (been involved only in the SRU verification side so far)
[16:15] <bdmurray> blackboxsw: no problem
[16:19] <jbicha> AAs, please review LP: #1709764 to complete the libgtop2 transition
[16:21] <jbicha> ooh, this is causing major problems now for autopkgtests :( https://bugs.debian.org/868473
[16:21] <jbicha> https://codesearch.debian.net/search?q=path%3Adebian%2Ftests%2Fcontrol+dh-acc&perpkg=1
[16:37] <jbicha> I think we're going to need to revert that debhelper change or modify it, I commented on the Debian bug
[17:04] -queuebot:#ubuntu-release- Unapproved: zfs-linux (zesty-proposed/main) [0.6.5.9-5ubuntu4.1 => 0.6.5.9-5ubuntu4.2] (core)
[17:54] <LocutusOfBorg> apw, can we please force-bad winff/armhf? it has been failing since a lot of time
[17:54] <LocutusOfBorg> I don't think anybody will have a look
[17:55] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (zesty-proposed) [0.6.5.9-5ubuntu4.2]
[17:55] <LocutusOfBorg> (at least not me :p)
[17:57] <ginggs> LocutusOfBorg: winff hint is already in apw's hints, just needs a version bump
[17:58] <LocutusOfBorg> oh, the missing feature somebody was discussing here yesterday, thanks
[18:00] <LocutusOfBorg> jbicha, I *think* relaxing debhelper
[18:00] <LocutusOfBorg> is better
[18:00] <LocutusOfBorg> two reasons: 1) we already have a delta
[18:00] <LocutusOfBorg> 2) we do not introduce a new one :)
[18:01] <LocutusOfBorg> serious 2 point: seems more a debhelper regression to me
[18:02] <LocutusOfBorg> OTOH, fixing abi is probably preferrable, less autopkgtests, faster migration, trivial patch
[18:02] <jbicha> warnings about compat 11 seems awfully agressive to me, won't people check their code before bumping the compat level anyway?
[18:02] <jbicha> I'
[18:02] <jbicha> m thinking of dh_missing in particular
[18:03] <LocutusOfBorg> sure, and for sure it has to be emitted only when the new compat is used
[18:03] <LocutusOfBorg> but again, moving abi to the new syntax needs to be done, right now I would bump that bug to RC
[18:04] <jbicha> it's definitely RC for Ubuntu
[18:05] <LocutusOfBorg> so, lets fix abi-checker and upload?
[18:05] <LocutusOfBorg> I can do it
[18:06]  * LocutusOfBorg is doing it
[18:07] -queuebot:#ubuntu-release- Unapproved: accepted nvme-cli [source] (xenial-proposed) [0.5-1ubuntu0.2]
[18:07] <LocutusOfBorg> ${path}'_report.xml'
[18:07] <LocutusOfBorg> not sure if this is correct
[18:14] <LocutusOfBorg> meh, that documentation seems to be correct, the bug was preventing it from doing the right thing
[18:14] <LocutusOfBorg> https://anonscm.debian.org/git/debhelper/debhelper.git/commit/?id=e2c420df3aa600c6af1c734970227c2ee2a90e90
[18:14] <LocutusOfBorg> so this is not a retro-incompatible change, but rather a bug fix that breaks things
[18:15] <LocutusOfBorg> I uploaded in my ppa
[18:26] <elbrus> ginggs: regarding my question on #debian-release
[18:27] <elbrus> which was; vorlon: does Ubuntu every autopkgtest "trigger" on two packages at the same time, i.e. it needing two packages from the proposed pocket at the same time (e.g. due to dependecies I guess)
[18:27] <elbrus> I don't mean manually, does it ever need automatically two
[18:27] <elbrus> or indeed, is a combination ever needed and why/when
[18:28] <elbrus> and shouldn't that be automated then
[18:29] <ginggs> elbrus: afaik, adding additional triggers is only done manually
[18:29] <elbrus> in which cases does that help?
[18:29] <elbrus> and does that help britney to migrate the package?
[18:30] <elbrus> if not triggered by britney in the first place
[18:30] -queuebot:#ubuntu-release- Unapproved: accepted packagekit [source] (xenial-proposed) [0.8.17-4ubuntu6~gcc5.4ubuntu1.2]
[18:31] <ginggs> elbrus: when autopkgtests need other things in -proposed, i.e. they should migrate together, but they do not have explicit depends on the newer versions
[18:32] <ginggs> elbrus: yes, it definitely helps the packages migrate
[18:32] <ginggs> helps = they would not migrate without the additional triggers
[18:32] <slangasek> LocutusOfBorg: wrt gmime it would probably be best if you consult the desktop team
[18:34] <elbrus> so britney takes manual triggers into account even if it didn't create it?
[18:34] <slangasek> ye
[18:34] <elbrus> do you have an example?
[18:34] <slangasek> elbrus: yes
[18:35] <ginggs> elbrus: sometimes the packages really should be depending on the newer version in debian/tests/control
[18:35] <elbrus> one could consider that a bug?
[18:35] <slangasek> example> well, it's simply the architecture of the britney policy we have in place
[18:36] <ginggs> elbrus: some cases are bugs and should be reported, yes
[18:36] <LocutusOfBorg> slangasek, not needed, gmime now provides the 3 binding, and the two rdeps in main are compatible with it
[18:36] <LocutusOfBorg> once the old one is accepted in unstable, everything will sort out by itself
[18:36] <LocutusOfBorg> and if debian does a transition to 3, even better
[18:37] <LocutusOfBorg> but since two sources are around, I just care that the one in main has rdeps in main
[18:44] <LocutusOfBorg> jbicha, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-costamagnagianfranco-locutusofborg-ppa/?format=plain
[18:44] <LocutusOfBorg> once nemo appears here, I'll know if it is fixed or not
[18:44] <LocutusOfBorg> I appreciate if you can double-look my perl foo
[18:47] -queuebot:#ubuntu-release- Unapproved: accepted mongodb [source] (xenial-proposed) [1:2.6.10-0ubuntu1.1]
[18:51] <LocutusOfBorg> ${path}.'_report.xml' this seems better
[19:20] <slangasek> so how did pulling in an upstream patch to the ARM asm break the ppc64el build? ;P https://launchpad.net/ubuntu/+source/ffmpeg/7:3.3.3-2
[19:27] -queuebot:#ubuntu-release- New binary: node-seq [amd64] (artful-proposed/none) [0.3.5-2] (no packageset)
[19:56] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.10.0-32.36] (core, kernel)
[19:58] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.10.0-32.36]
[19:59] -queuebot:#ubuntu-release- New binary: qtwebengine-opensource-src [i386] (artful-proposed/universe) [5.9.1+dfsg-2ubuntu1] (kubuntu)
[20:00] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-91.114~14.04.1] (kernel)
[20:00] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (vivid-proposed/main) [3.19.0-91.99] (core, kernel)
[20:00] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-128.177] (core, kernel)
[20:00] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-91.114] (core, kernel)
[20:01] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.11.0-14.20~16.04.1] (kernel)
[20:01] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.10.0-32.36~16.04.1] (kernel)
[20:01] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (vivid-proposed) [3.19.0-91.99]
[20:01] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.10.0-32.36~16.04.1]
[20:01] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.11.0-14.20~16.04.1]
[20:01] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-91.114]
[20:02] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-91.114~14.04.1]
[20:02] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-128.177]
[20:07] <tsimonq2> Hm, why are half the amd64/i386 builders idle but yet there's an hour long build queue?
[20:09] <tsimonq2> Oh
[20:09] <tsimonq2> duh
[20:09] <tsimonq2> I was looking at the wrong arches, sorry
[20:24] -queuebot:#ubuntu-release- Unapproved: accepted python-acme [source] (zesty-proposed) [0.14.2-0ubuntu0.17.04.1]
[20:30] -queuebot:#ubuntu-release- Unapproved: accepted python-certbot [source] (zesty-proposed) [0.14.2-0ubuntu0.17.04.1]
[20:32] -queuebot:#ubuntu-release- New binary: qtwebengine-opensource-src [amd64] (artful-proposed/universe) [5.9.1+dfsg-2ubuntu1] (kubuntu)
[20:33] -queuebot:#ubuntu-release- Unapproved: accepted python-certbot-nginx [source] (zesty-proposed) [0.14.2-0ubuntu0.17.04.1]
[20:38] -queuebot:#ubuntu-release- Unapproved: accepted python-certbot-apache [source] (zesty-proposed) [0.14.2-0ubuntu0.17.04.1]
[20:39] <slangasek> /usr/include/ITK-4.10/vcl_compiler.h:79:4: error: #error "Dunno about this gcc"
[20:41] <slangasek> should be #error "¯\(シ)/¯"
[20:42] -queuebot:#ubuntu-release- New: accepted qtwebengine-opensource-src [amd64] (artful-proposed) [5.9.1+dfsg-2build2]
[20:42] -queuebot:#ubuntu-release- New: accepted qtwebengine-opensource-src [amd64] (artful-proposed) [5.9.1+dfsg-2ubuntu1]
[20:42] -queuebot:#ubuntu-release- New: accepted qtwebengine-opensource-src [i386] (artful-proposed) [5.9.1+dfsg-2build2]
[20:42] -queuebot:#ubuntu-release- New: accepted qtwebengine-opensource-src [i386] (artful-proposed) [5.9.1+dfsg-2ubuntu1]
[20:43] <LocutusOfBorg> slangasek, lol
[20:44] <slangasek> LocutusOfBorg: are you looking at the new insighttoolkit4 build failure already?
[20:44] <LocutusOfBorg> slangasek, yes, together with upstream and debian
[20:44] <slangasek> ok
[20:44] <LocutusOfBorg> this is a castxml failure
[20:44]  * slangasek nods
[20:44] <LocutusOfBorg> I requested upstream help
[20:45] <LocutusOfBorg> btw abi-checker-fooo should be fixed, not sure if you have a smart way of kicking failed autopkgtests
[20:45] <slangasek> I'll keep my hands off then, thanks
[20:45] <slangasek> "smart way" - you mean selectively retrying ones related to dh_acc?
[20:45] <LocutusOfBorg> how do you find the related to dh_acc?
[20:46] <slangasek> I don't have a good way, sorry
[20:46] <LocutusOfBorg> this is what I try to make smart :)
[20:46] <LocutusOfBorg> oh ok
[20:46] -queuebot:#ubuntu-release- Unapproved: accepted python-acme [source] (xenial-proposed) [0.14.2-0ubuntu0.16.04.1]
[20:46] <LocutusOfBorg> I hoped around grepping on logs directory
[20:46] <slangasek> other than looking at all regressions reported and walking the logs to find references to dh_acc
[20:46] <slangasek> logs directory> it's not a directory, it's swift
[20:46] <LocutusOfBorg> https://github.com/CastXML/CastXML/issues/87#issuecomment-321462465
[20:46] <LocutusOfBorg> for castxml
[20:46] <slangasek> so you have all the same access over http that I do ;)
[20:46] <LocutusOfBorg> if you want to help...
[20:46] <LocutusOfBorg> ack
[20:47] <LocutusOfBorg> (I don't know what swift is, and I'm happy to avoid such knowledge :p )
[20:47] <slangasek> honestly I was looking at just retrying all current failures
[20:47] <slangasek> the queue is small currently
[20:47] <LocutusOfBorg> before lets abi-foo maybe migrate
[20:47] <slangasek> ok
[20:47] <LocutusOfBorg> otherwise you will need to add a special trigger everywhere?
[20:48] <LocutusOfBorg> also, qt transition is mostly a lock-in stuff, is it ok to retry against proposed?
[20:48] <slangasek> well, retry-autopkgtest-regressions --all-proposed...
[20:48] <LocutusOfBorg> I don't know if k* and libk* foo patches will be retro-compatible for building with qt 5.7
[20:50] <Laney> I'd rather add a trigger on the new version ...
[20:50] <Laney> but YMMV I guess
[20:52] <slangasek> generally speaking yes, but that would involve analysis
[20:52] <slangasek> :)
[20:53] <slangasek> I don't like --all-proposed as a rule
[20:53] <LocutusOfBorg> we can add that trigger to every failed test
[21:08] <LocutusOfBorg> I propose to make it migrate and then retry in 12h all the failed tests
[21:08] <LocutusOfBorg> I'll do it as soon as it migrates
[21:09] <LocutusOfBorg> btw to spot regressions in release, a nice feature would be to run against release tests randomly, and report if something breaks there
[21:09] <LocutusOfBorg> sometimes you see the previous autopkgtest run of a particular package being 6 months old, and this doesn't help too much
[21:11]  * LocutusOfBorg goes to sleep
[21:11] <jbicha> I believe ci.debian.net does regular re-runs of everything
[21:13] <slangasek> yeah, but those also aren't real CI, so...
[21:47] <Laney> yes I would just add it to everything, or alternatively wait for the thing to migrate and then re-trigger
[21:51] -queuebot:#ubuntu-release- Unapproved: update-manager (zesty-proposed/main) [1:17.04.5 => 1:17.04.6] (core)
[21:53] -queuebot:#ubuntu-release- Unapproved: mesa (xenial-proposed/main) [17.0.7-0ubuntu0.16.04.1 => 17.0.7-0ubuntu0.16.04.2] (core, xorg)
[22:03] <rbasak> bdmurray: thank you for accepting the certbot packages. I had been meaning to self accept after double checking them but hadn't got round to it yet.
[22:03] <rbasak> bdmurray: the missing packages are in NEW I think?
[22:19] -queuebot:#ubuntu-release- Unapproved: libxfont (xenial-proposed/main) [1:1.5.1-1ubuntu0.16.04.1 => 1:1.5.1-1ubuntu0.16.04.2] (core, xorg)
[22:20] <tjaalton> bdmurray: hi, I've just uploaded a new mesa that adds a dummy pkg for libgles1-mesa, and a fix for libxfont1-dev that moves some docs to the correct place, fixing a file conflict with the newer libxfont-dev
[22:21] <tjaalton> would be nice to get them in before the weekend, since I'm not supposed to ack them myself tomorrow..
[22:23] <bdmurray> tjaalton: stuff can be accepted into -proposed on Friday, just not into -updates
[22:24] <tjaalton> yeah but reviewing my own uploads?
[22:25] <bdmurray> tjaalton: ah, yes that's not ideal
[22:37] -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (xenial-proposed) [17.0.7-0ubuntu0.16.04.2]
[22:39] -queuebot:#ubuntu-release- Unapproved: accepted libxfont [source] (xenial-proposed) [1:1.5.1-1ubuntu0.16.04.2]
[22:39] <tjaalton> whee, thanks
[22:59] -queuebot:#ubuntu-release- Unapproved: update-manager (xenial-proposed/main) [1:16.04.8 => 1:16.04.9] (core)
[23:18] -queuebot:#ubuntu-release- New binary: sambamba [amd64] (artful-proposed/none) [0.6.6-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: swath [amd64] (artful-proposed/universe) [0.5.5-2] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: sambamba [i386] (artful-proposed/none) [0.6.6-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: python-pymeasure [amd64] (artful-proposed/none) [0.4.5-1] (no packageset)