[02:02] <akgraner> The new edition of the Ubuntu Weekly Newsletter is now available here:
[02:02] <akgraner> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue193


[08:51] <bencer> hi guys. how you can report spam comments on launchpad? i just saw https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/577477/comments/26
[08:58] <cjwatson> bencer: https://answers.launchpad.net/launchpad
[09:12] <shadeslayer> hi, I'm getting a OOPS when copying packages
[09:13] <shadeslayer> OOPS-ac31afe79c02a3124719003e2e838590
[09:13] <shadeslayer> copying the "homerun-kickstarter" source from https://launchpad.net/~blue-shell/+archive/homerun to https://launchpad.net/~netrunner-os/+archive/enigma-1306-updates/+packages
[09:17] <shadeslayer> wgrant: ^^
[09:29] <cjwatson> There was a previous PackageDiff for that pair of SPRs, with requester==None.  I wonder how that happened ...
[09:32] <wgrant> cjwatson: PackageDiff.requester used to always be SPR.creator, but that became dangerous when it started being used as Job.requester, which can get emailed on failure
[09:33] <wgrant> So now it can be None when there is no obvious person to blame for the diff
[09:33] <wgrant> I thought StevenK checked that nothing actually used requester, but apparently somewhere was missed..
[09:34] <wgrant> It's odd that that case had no requester, though.
[11:00] <stub> I'm going to need to make the test runner unset the OS_* openstack environment variables so tests don't attempt to connect to random Swift servers if they happen to be set.
[11:00] <stub> I'll probably need the same change to 'make run'
[11:01] <stub> Any other problems I'm going to hit? Or should I not use the standard OS_* environment for Swift configuration and move it somewhere else?
[11:01] <stub> Dealing with secrets, so best not launchpad.conf I think
[11:02] <stub> I can put in a flag in the launchpad.conf (or a featureflag if you prefer) to not use Swift at all.
[11:05] <lifeless> stub: so the OS_* variables are really suited for command line tool usage; most libraries don't use them (because in part of the above, also because setting environment variables on daemon start up is a little icky)
[11:05] <lifeless> stub: also, ECHANNEL, perhaps #launchpad-dev ? :)
[11:14] <stub> ECHANNEL
[12:09] <shadeslayer> wgrant: should I file a bug on launchpad regarding that issue?
[12:13] <wgrant> shadeslayer: It's fixed in trunk. Let me just QA and deploy it.
[12:13] <shadeslayer> ack, would be super nice to have it deployed :)
[12:37] <toabctl> how long does it take before a package appears in launchpad when I uploaded a package to my ppa? minutes?hours?
[12:40] <Ampelbein> toabctl: minutes. You'll get an email when it's processed.
[12:40] <toabctl> Ampelbein: I'm not sure if I can receive the mail. is there any other method to get the possible reason why an upload fails?
[12:41] <Ampelbein> toabctl: That I do not know. Is your pgp key imported to launchpad? correct distribution set in debian/changelog? Correct signatures on the source package?
[12:42] <toabctl> Ampelbein: yes
[12:46] <wgrant> toabctl: Why can't you receive an email?
[12:47] <wgrant> toabctl: But you should receive an email within 5 minutes if you signed the package properly.
[12:49] <wgrant> I'm not seeing any successul or failed uploads to your PPA today.
[12:49] <shadeslayer> wgrant: fix deployed?
[12:50] <wgrant> shadeslayer: Waiting for the deployment to be kicked off.
[12:50] <shadeslayer> ah okay
[12:53] <toabctl> wgrant: my ppa?
[12:53] <wgrant> toabctl: Yes
[12:55] <toabctl> wgrant: I uploaded to the ~telekomcloud ppa
[12:55] <toabctl> wgrant: the ppa is called testing
[12:55] <wgrant> toabctl: 'Signing key C870D1F099D654756D227716767142C5A7C75548 not registered in launchpad.'
[12:58] <toabctl> wgrant: ~telekomcloud is a team. can a team register a key?
[12:59] <toabctl> wgrant: forget it. I have to validate the key. missed to validation mail.
[12:59] <wgrant> toabctl: Only people have keys, not teams. So you'd associate it with your personal account.
[13:00] <toabctl> wgrant: and the mails for the failure go to my primary email address?
[13:00] <toabctl> wgrant: or to the address mentioned in debian/changelog?
[13:01]  * czajkowski peers at wgrant
[13:01] <wgrant> toabctl: They'll go to the primary email address of the Launchpad account to which the signing key is registered.
[13:02] <wgrant> But only if the signing key is known to Launchpad.
[13:03] <toabctl> wgrant: ah.ok. so without a known signing key, the user doesn't get an email.
[13:03] <wgrant> Right.
[13:03] <wgrant> We can't trust Maintainer or Changed-By
[13:03] <wgrant> So we can't safely email anyone if the signature can't be verified.
[13:06] <toabctl> wgrant: do you see an upload now?
[13:08] <wgrant> toabctl: You have mail.
[13:08] <wgrant> You need to build with debuild -S -sa, not just debuild -S
[13:11] <toabctl> wgrant: what is -sa for?
[13:13] <wgrant> toabctl: It includes the orig.tar.gz
[13:13] <wgrant> In the changes file
[13:14] <toabctl> wgrant: ok. thanks!
[14:19] <jf_> Hi, I don't have any access to my proprietary project: https://launchpad.net/iller : the commercial subscription has expired. I bought a new subscription, but can't link it to the project. Could you help me ? Thanks.
[14:26] <czajkowski> jf_: if you look under https://launchpad.net/~/+vouchers
[14:26] <czajkowski> you'll see your voucher so you can apply it
[14:26] <czajkowski> if your project has expired
[14:26] <czajkowski> you';ll need an admin to make it unexpired in order to apply the voucher
[14:26] <jf_> czajkowski, and where can I find an admin ?
[14:28] <czajkowski> jf_: maybe not around at this hour of the day, you'll need to file a answer on lp - https://answers.launchpad.net/launchpad/+addquestion
[14:28] <jf_> czajkowski, ok I'll try, thanks.
[14:30] <wgrant> jf_: I've revived the project.
[14:30] <wgrant> You should be able to apply the voucher now.
[14:31] <wgrant> shadeslayer: That copy should work now.
[14:31] <shadeslayer> Launchpad encountered an internal error during the following operation: copying a package.  It was logged with id OOPS-89b73987b42084f729cac479dfd3eb62.  Sorry for the inconvenience.
[14:31] <shadeslayer> though I used a script to do it
[14:32] <jf_> wgrant, it works, many thanks.
[14:32] <czajkowski> wgrant: thanks :)
[14:34] <shadeslayer> wgrant: same thing from the webui
[14:34] <shadeslayer> OOPS-df5803a99f82e519a2d75b6cbc5f28a8 from webui
[14:34] <wgrant> shadeslayer: Missed something. Can you try again now?
[14:35] <wgrant> Running...
[14:35] <wgrant> Or another job is :)
[14:35] <wgrant> It worked.
[14:35] <shadeslayer> yay
[14:35] <shadeslayer> yep :)
[14:35] <shadeslayer> thanks wgrant
[14:35] <wgrant> np, sorry about the glitch
[14:38] <shadeslayer> wgrant: did that affect all repos?
[14:39] <wgrant> shadeslayer: It only affected certain packages for which we couldn't determine the uploader when generating the diff. It's a rare situation, and I don't yet know why it affected that particular package.
[14:39] <wgrant> I worked it out half way through that last sentence, though.
[14:39] <shadeslayer> recipe builds?
[14:40] <wgrant> Yup
[14:40] <shadeslayer> yeah thought so :)
[14:40] <shadeslayer> I am pretty certain I have copied recipe builds before
[14:40] <wgrant> It only broke last week
[14:41] <wgrant> And recipe builds are copied infrequently enough that it's only shown up a few times since then.
[14:41] <shadeslayer> ah that probably explains why :)
[15:01] <dobey> how can i get an mbox or maildir or something of a mailing list archive on lp?
[15:02] <shadeslayer> IIRC you create a team
[15:02] <shadeslayer> and then you get a mailing list for free?
[15:03] <shadeslayer> oh
[15:03] <shadeslayer> you want an archive of old posts
[15:03] <shadeslayer> https://lists.launchpad.net/team_name/ ?
[15:03] <dobey> yeah, i don't want more mailing lists
[15:04] <dobey> yes i can see the archive. i don't want to read it on the web. i want to import it into evolution so i can reply to stuff properly
[15:05] <dobey> typical mailman setups have a "download a tarball of this month" or "download an mbox of this message" thing. lp seems to not expose that
[15:05] <shadeslayer> ahhh nope, not that I know of
[15:10] <czajkowski> dobey: nope cant be done, there can be a once off dump if needed
[15:11] <dobey> can i do it, or does someone with more duck powers than i, have to do it?
[15:13] <czajkowski> dobey: you'd need to file a lp Q and webops do it for you
[16:54] <elfy> is there anyone about that could guide me in part of creating a team page - in particular how I can make a NEW team page be owned by  this teamhttps://launchpad.net/~forum-council
[16:55] <elfy> I need to create a team page similar to https://launchpad.net/~ubuntuforums-staff but for a slightly different group of people
[16:55] <elfy> or do I need to get the communiyt council to do it and make the FC admins
[16:55] <elfy> thanks
[16:56] <cjwatson> Creating a team is done here: https://launchpad.net/people/+newteam
[16:56] <saiarcot895> elfy: I can't guide you here, but I think you have to create a team page from the Launchpad home page with either Moderated or Restricted permissions, and request to be considered as a subteam of the forum-council team
[16:57] <elfy> cjwatson: yea I know that - there doesn't appear to be anywhere to specify an owner though
[16:57] <cjwatson> If you own the team you can go to "Change details" on the team page, then "Change owner"
[16:57] <elfy> cjwatson: aaah - ok :)
[16:57] <cjwatson> (or https://launchpad.net/~TEAM/+reassign)
[16:58] <cjwatson> Permissions don't matter
[16:58] <elfy> so just forge ahead and build it with restricted and then reassign - thanks :)
[16:58] <cjwatson> Well, not for ownership at any rate
[16:58] <elfy> this is one of the last bits of the forum saga ...
[16:58] <elfy> which I will be pleased to see the back off
[17:37] <elfy> cjwatson: thank you - all done :)
[17:42] <Uni> so,/2
[17:42]  * Uni sighs
[17:42] <Uni> irc is hard


[01:08] <RAOF> Lots of SRUs to release. Yay!
[04:05] -queuebot:#ubuntu-release- New binary: linux-signed-lts-trusty [amd64] (precise-proposed/main) [3.13.0-107.154~precise1] (kernel)
[04:28] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-trusty [amd64] (precise-proposed) [3.13.0-107.154~precise1]
[06:05] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-58.79~14.04.1] (kernel)
[06:05] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-107.154] (core, kernel)
[10:09] <josvaz> rbasak: could you review and hopely approve the walinuxagent uploads to -propose from this bug https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522
[10:09] <ubot5`> Ubuntu bug 1650522 in walinuxagent (Ubuntu Yakkety) "walinuxagent 2.1.5 needs to have AutoUpdate On" [Undecided,In progress]
[10:10] <josvaz> rbasak: they are for yakkety, xenial & trusty we have done the manual testing as per https://wiki.ubuntu.com/walinuxagentUpdates
[10:10] <josvaz> and we need the images to be in proposed to do the "automated" SRU testing part
[12:06] <bluesabre> any AA's interested in accepting sgt-launcher from NEW into zesty? https://bugs.launchpad.net/ubuntu/+bug/1641300
[12:06] <ubot5`> Ubuntu bug 1641300 in Ubuntu "[needs-packaging] sgt-launcher" [Wishlist,Fix committed]
[12:31] <sil2100> Not too many AA's around this week sadly
[12:31] <flocculant> sil2100: we began to guess that :)
[12:55] -queuebot:#ubuntu-release- New sync: messaging-framework (zesty-proposed/primary) [0.2+17.04.20161208-0ubuntu1]
[13:32] <LocutusOfBorg> doko, hi, how do you feel about an ocaml sync?
[13:32] <LocutusOfBorg> I don't understand your delta, but seems a no-change build from Debian works, and builds fine
[13:32] <LocutusOfBorg> at least the amd64 fPIC patch seems to be useless now
[13:32] <LocutusOfBorg> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa/+sourcepub/7340254/+listing-archive-extra
[13:33] <LocutusOfBorg> here the no-change from debian build
[13:38] <xnox> LocutusOfBorg, we want PIC for the native options compiler.
[13:39] <xnox> unless that was only for the PIE by default bootstrap on amd64.
[13:39] <xnox> LocutusOfBorg, note the difference in the "Configuration for the native-code compiler:" section, as that is what is changed by that patch.
[13:39] <xnox> i'd rather keep our delta, and merge experimental.
[13:44] <LocutusOfBorg> xnox, according to ubuntu 4.02.3-6ubuntu1 was FTBFS on amd64 while 4.02.3-6ubuntu2. Now the new version seems to build without that patch
[13:44] <LocutusOfBorg> this is why I'm inclined in dropping it
[13:44] <LocutusOfBorg> "    - Pass --hash-style=both --as-needed --build-id to the linker."
[13:45] <LocutusOfBorg> this is something I don't understand really, it has no bugs, and no patch description
[13:45] <LocutusOfBorg> also, the failed amd64 build https://launchpadlibrarian.net/256002221/buildlog_ubuntu-yakkety-amd64.ocaml_4.02.3-6ubuntu1_BUILDING.txt.gz
[13:46] <LocutusOfBorg> was probably due to some other dependencies needing a rebuild (e.g. binutils?)
[13:46] <xnox> LocutusOfBorg, please don't do that.
[13:46] <xnox> LocutusOfBorg, the patch is to enable PIC in native compiler by default, rather than to fix FTBFS. It would say fix FTBFS, if it was just that.
[13:46] <LocutusOfBorg> ok, so keep them both
[13:47] <LocutusOfBorg> and revert this Debian change    "* Default to PIC on arm, to fix failing armhf tests (Closes: #837359)."
[13:47] <xnox> why?
[13:47] <LocutusOfBorg> because arm in ubuntu has no default pic?
[13:47] <xnox> LocutusOfBorg, do you even follow PIE by default changes to toolchains in Debian and Ubuntu and understand how that corelates with native code compilation with PIC?
[13:48] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-58.79~14.04.1]
[13:48] <LocutusOfBorg> PIE in enabled everywhere in Debian, but not in Ubuntu
[13:48] <LocutusOfBorg> and no, I don't understand it completely, this is why I'm here :)
[13:49] <xnox> LocutusOfBorg, then please do not drop or change, pic or pie, on any arches.
[13:49] <xnox> LocutusOfBorg, you are not TIL on the package, so please don't mess it up.
[13:50] <xnox> updating ocaml triggers the binary transition touching a tonne of packages.
[13:52] <LocutusOfBorg> this is the reason, I'm doign the ocaml transition, and I don't want doko to merge it in some days and having to redo it
[13:53] <LocutusOfBorg> xnox, I don't mess it up, I don't upload when I don't understand things
[13:53] <LocutusOfBorg> actually I even already did the merge https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/7340201/+listing-archive-extra
[13:54] <LocutusOfBorg> before trying a plain sync, that ringed a bell to me leading to me asking here :)
[13:54] <LocutusOfBorg> so, I would upload that -8 and do the ocaml game, to see it migrate
[13:54] <LocutusOfBorg> I leave merging from experimental to somebody else
[13:55] <xnox> LocutusOfBorg, please don't
[13:55] <xnox> we don't want -8 from unstable
[13:55] <xnox> we want new upstream point release from experimental
[13:56] <xnox> to enable native ocaml support on ppc64el and s390x
[13:56] <xnox> LocutusOfBorg, merging from unstable, when you are not touch it last, or syncing, will double the work for ocaml.
[13:56] <LocutusOfBorg> ok, so can I merge from experimental then?
[13:56] <LocutusOfBorg> there is some ocaml stuff that needs migration
[13:57] <LocutusOfBorg> this is why I would like to do this little transition
[13:57] <LocutusOfBorg> what about this: let the current ocaml migrate
[13:57] <LocutusOfBorg> and then prepare the experimental merge in a ppa
[13:57] <xnox> LocutusOfBorg, please don't touch ocaml.
[13:57] <xnox> LocutusOfBorg, and please don't revert it.
[13:57] <xnox> LocutusOfBorg, which package are you concerned about not migrating? which is not src:ocaml?
[13:58] <LocutusOfBorg> camlzip
[13:58] <xnox> And do note we have PIC enabled in src:ocaml on armhf, so your assertion about reverting PIC is wrong.
[14:00] <xnox> LocutusOfBorg, merging src:ocaml will do nothing to migrate camlzip
[14:00] <LocutusOfBorg> ok let me rephrase
[14:01] <LocutusOfBorg> I want to fix the two/three ocaml packages not migrating
[14:01] <LocutusOfBorg> since I will have to do some rebuilds, I though about ppicking the -8 from Debian, to save some work
[14:01] <xnox> LocutusOfBorg, check the transition tracker and rebuild $ reverse-depends -b src:camlzip which need rebuild to become installable with the new camlzip.
[14:01] <LocutusOfBorg> xnox, yes I know that
[14:01] <LocutusOfBorg> I'll do that
[14:01] <LocutusOfBorg> just is a wasted time if tomorrow somebody merges it again from Debian
[14:02] <xnox> LocutusOfBorg, merge of ocaml triggers rebuild of 269 packages; there are only 31 currently outstanding packages stuck in proposed that are not installable; fixing the package you care about migrating is only 3 rebuilds.
[14:02] <xnox> not 269.
[14:02] <xnox> by miss-merging ocaml you are offering to double 269 rebuilds.
[14:03] <xnox> LocutusOfBorg, just rebuild the leaf packages you are about migrating, and don't touch src:ocaml
[14:03] <LocutusOfBorg> ok, got it
[14:03] <LocutusOfBorg> fdkaac and camlzip needs care, not sure about how many others
[14:03] <LocutusOfBorg> but yeah, lets keep the transition simple
[14:03] <xnox> and if somebody merges src:ocaml, it will delay migration of leaf packages by a much longer while, and it is not a duplication of work of sorting out reverse deps on camlzip against the current ocaml abi
[14:04] <LocutusOfBorg> yep indeed, but I think my question was legit anyway :)
[14:04] <LocutusOfBorg> usually before starting my haskell rebuilds I make sure ghc is syncd/merged
[14:36] <slashd> For sru or Wednesday vanguard arges/rbasak, could you please take action on "os-prober" version "1.70ubuntu3.2" waiting on the X upload queue ? It is fixing a CRITICAL bug which potentially risk FS corruption, 3.2 is the continuity of the patch found in version 3.1 that was missing a dependency (verification-failed). Let me know if you need more details
[15:06] -queuebot:#ubuntu-release- New binary: pybigwig [ppc64el] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[15:08] -queuebot:#ubuntu-release- New binary: pybigwig [i386] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[15:08] -queuebot:#ubuntu-release- New binary: pybigwig [amd64] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[15:08] -queuebot:#ubuntu-release- New binary: pybigwig [arm64] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[15:09] -queuebot:#ubuntu-release- Unapproved: linux (precise-proposed/main) [3.2.0-119.162 => 3.2.0-120.163] (core, kernel) (sync)
[15:10] -queuebot:#ubuntu-release- New binary: pybigwig [armhf] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[15:11] -queuebot:#ubuntu-release- New binary: pybigwig [s390x] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[15:13] -queuebot:#ubuntu-release- New binary: pybigwig [powerpc] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[16:05] -queuebot:#ubuntu-release- New binary: maxima-sage [s390x] (zesty-proposed/universe) [5.35.1-2ubuntu1] (no packageset)
[16:07] <josvaz> pinged slangasek as rbasak might be out today
[16:08] -queuebot:#ubuntu-release- New binary: maxima-sage [ppc64el] (zesty-proposed/universe) [5.35.1-2ubuntu1] (no packageset)
[16:09] <slashd> seems like most of sru members are in holiday... I'm taking a chance to tag the other active members just in case someone have the time to look at my above request in the channel : infinity, bdmurray, sbeattie, rmcbride, jibel, pedro_, arges , thanks in advance
[16:17] -queuebot:#ubuntu-release- New binary: maxima-sage [amd64] (zesty-proposed/universe) [5.35.1-2ubuntu1] (no packageset)
[16:17] -queuebot:#ubuntu-release- New binary: maxima-sage [i386] (zesty-proposed/universe) [5.35.1-2ubuntu1] (no packageset)
[16:19] -queuebot:#ubuntu-release- New binary: maxima-sage [powerpc] (zesty-proposed/universe) [5.35.1-2ubuntu1] (no packageset)
[16:24] -queuebot:#ubuntu-release- Unapproved: rejected walinuxagent [source] (yakkety-proposed) [2.1.5-0ubuntu4.1]
[16:24] -queuebot:#ubuntu-release- Unapproved: rejected walinuxagent [source] (xenial-proposed) [2.1.5-0ubuntu4.1~16.04.0]
[16:25] -queuebot:#ubuntu-release- Unapproved: rejected walinuxagent [source] (trusty-proposed) [2.1.5-0ubuntu4.1~14.04.0]
[16:28] -queuebot:#ubuntu-release- Unapproved: linux-backports-modules-3.2.0 (precise-proposed/main) [3.2.0-119.111 => 3.2.0-120.112] (core, kernel) (sync)
[16:28] -queuebot:#ubuntu-release- Unapproved: linux-meta (precise-proposed/main) [<IP_ADDRESS>.134 => <IP_ADDRESS>.135] (core, kernel) (sync)
[16:39] -queuebot:#ubuntu-release- New binary: maxima-sage [arm64] (zesty-proposed/universe) [5.35.1-2ubuntu1] (no packageset)
[16:43] -queuebot:#ubuntu-release- Unapproved: linux-armadaxp (precise-proposed/main) [3.2.0-1680.107 => 3.2.0-1681.108] (kernel) (sync)
[16:44] -queuebot:#ubuntu-release- Unapproved: linux-meta-armadaxp (precise-proposed/main) [<IP_ADDRESS>0.96 => <IP_ADDRESS>1.97] (kernel) (sync)
[16:48] -queuebot:#ubuntu-release- New binary: maxima-sage [armhf] (zesty-proposed/universe) [5.35.1-2ubuntu1] (no packageset)
[17:20] -queuebot:#ubuntu-release- Unapproved: linux (vivid-proposed/main) [3.19.0-78.86 => 3.19.0-79.87] (core, kernel) (sync)
[17:22] -queuebot:#ubuntu-release- Unapproved: linux-meta (vivid-proposed/main) [<IP_ADDRESS>.76 => <IP_ADDRESS>.77] (core, kernel) (sync)
[17:22] -queuebot:#ubuntu-release- Unapproved: linux-signed (vivid-proposed/main) [3.19.0-78.86 => 3.19.0-79.87] (core, kernel) (sync)
[17:27] -queuebot:#ubuntu-release- New binary: link-grammar [ppc64el] (zesty-proposed/universe) [5.3.13-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: libsearpc [ppc64el] (zesty-proposed/universe) [3.0.7+git20161217.04f6ba7-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: spigot [ppc64el] (zesty-proposed/universe) [0.2016-12-18.g8372d450-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: asterisk-opus [ppc64el] (zesty-proposed/universe) [13.7+20161113-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: link-grammar [s390x] (zesty-proposed/universe) [5.3.13-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: link-grammar [amd64] (zesty-proposed/universe) [5.3.13-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: pbcopper [ppc64el] (zesty-proposed/universe) [0.0.1+20161202-1] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: asterisk-opus [s390x] (zesty-proposed/universe) [13.7+20161113-1] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: spigot [s390x] (zesty-proposed/universe) [0.2016-12-18.g8372d450-1] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: libsearpc [s390x] (zesty-proposed/universe) [3.0.7+git20161217.04f6ba7-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: pbcopper [s390x] (zesty-proposed/universe) [0.0.1+20161202-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- Unapproved: linux (xenial-proposed/main) [4.4.0-57.78 => 4.4.0-58.79] (core, kernel) (sync)
[17:32] -queuebot:#ubuntu-release- New binary: docker-pycreds [amd64] (zesty-proposed/universe) [0.2.1-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: link-grammar [i386] (zesty-proposed/universe) [5.3.13-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: golang-gopkg-retry.v1 [amd64] (zesty-proposed/universe) [0.0~git20161025.0.c09f6b8-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: fonts-oradano-mincho-gsrr [amd64] (zesty-proposed/universe) [0.2016.0612-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: libsearpc [i386] (zesty-proposed/universe) [3.0.7+git20161217.04f6ba7-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: python-btrees [ppc64el] (zesty-proposed/universe) [4.3.1-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: libsearpc [amd64] (zesty-proposed/universe) [3.0.7+git20161217.04f6ba7-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: nrpe-ng [amd64] (zesty-proposed/universe) [0.1.2-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- Unapproved: linux-meta (xenial-proposed/main) [<IP_ADDRESS>.60 => <IP_ADDRESS>.61] (core, kernel) (sync)
[17:34] -queuebot:#ubuntu-release- Unapproved: linux-signed (xenial-proposed/main) [4.4.0-57.78 => 4.4.0-58.79] (core, kernel) (sync)
[17:34] -queuebot:#ubuntu-release- New binary: asterisk-opus [i386] (zesty-proposed/universe) [13.7+20161113-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: node-ansi-escapes [amd64] (zesty-proposed/universe) [1.4.0-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: node-external-editor [amd64] (zesty-proposed/universe) [2.0.1+dfsg-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: node-gulp-util [amd64] (zesty-proposed/universe) [3.0.7-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: python-btrees [s390x] (zesty-proposed/universe) [4.3.1-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: spigot [i386] (zesty-proposed/universe) [0.2016-12-18.g8372d450-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: asterisk-opus [amd64] (zesty-proposed/universe) [13.7+20161113-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: node-exit-hook [amd64] (zesty-proposed/universe) [1.1.1-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: node-lodash-reescape [amd64] (zesty-proposed/universe) [3.0.0-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: libpgobject-util-dbadmin-perl [amd64] (zesty-proposed/universe) [0.100.0-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: spigot [amd64] (zesty-proposed/universe) [0.2016-12-18.g8372d450-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: node-globals [amd64] (zesty-proposed/universe) [9.14.0-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: link-grammar [arm64] (zesty-proposed/universe) [5.3.13-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: node-gulp-plumber [amd64] (zesty-proposed/universe) [1.1.0-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: node-kew [amd64] (zesty-proposed/universe) [0.7.0-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: link-grammar [armhf] (zesty-proposed/universe) [5.3.13-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: pydbus [amd64] (zesty-proposed/universe) [0.5.1-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: node-is-promise [amd64] (zesty-proposed/universe) [2.1.0-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: node-lodash-reevaluate [amd64] (zesty-proposed/universe) [3.0.0-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: pbcopper [i386] (zesty-proposed/universe) [0.0.1+20161202-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: node-tildify [amd64] (zesty-proposed/universe) [1.2.0-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: dolfin [ppc64el] (zesty-proposed/universe) [2016.2.0-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: pbcopper [amd64] (zesty-proposed/universe) [0.0.1+20161202-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: libsearpc [armhf] (zesty-proposed/universe) [3.0.7+git20161217.04f6ba7-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: libsearpc [arm64] (zesty-proposed/universe) [3.0.7+git20161217.04f6ba7-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: spigot [armhf] (zesty-proposed/universe) [0.2016-12-18.g8372d450-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: spigot [arm64] (zesty-proposed/universe) [0.2016-12-18.g8372d450-1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: asterisk-opus [arm64] (zesty-proposed/universe) [13.7+20161113-1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: asterisk-opus [armhf] (zesty-proposed/universe) [13.7+20161113-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: python-btrees [amd64] (zesty-proposed/universe) [4.3.1-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: python-btrees [i386] (zesty-proposed/universe) [4.3.1-1] (no packageset)
[17:46] -queuebot:#ubuntu-release- New binary: dolfin [s390x] (zesty-proposed/universe) [2016.2.0-1] (no packageset)
[17:49] -queuebot:#ubuntu-release- New binary: dolfin [amd64] (zesty-proposed/universe) [2016.2.0-1] (no packageset)
[17:49] -queuebot:#ubuntu-release- New binary: dolfin [i386] (zesty-proposed/universe) [2016.2.0-1] (no packageset)
[17:49] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (precise-proposed) [3.2.0-120.163]
[17:49] -queuebot:#ubuntu-release- Unapproved: accepted linux-backports-modules-3.2.0 [sync] (precise-proposed) [3.2.0-120.112]
[17:50] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (precise-proposed) [<IP_ADDRESS>.135]
[17:50] -queuebot:#ubuntu-release- New binary: link-grammar [powerpc] (zesty-proposed/universe) [5.3.13-1] (no packageset)
[17:50] -queuebot:#ubuntu-release- Unapproved: bubblewrap (yakkety-proposed/universe) [0.1.2-1 => 0.1.5-1~ubuntu16.10.0] (no packageset)
[17:52] -queuebot:#ubuntu-release- New binary: dolfin [armhf] (zesty-proposed/universe) [2016.2.0-1] (no packageset)
[17:52] -queuebot:#ubuntu-release- New binary: python-btrees [arm64] (zesty-proposed/universe) [4.3.1-1] (no packageset)
[17:54] -queuebot:#ubuntu-release- Unapproved: accepted linux-armadaxp [sync] (precise-proposed) [3.2.0-1681.108]
[17:54] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-armadaxp [sync] (precise-proposed) [<IP_ADDRESS>1.97]
[17:56] -queuebot:#ubuntu-release- New binary: libsearpc [powerpc] (zesty-proposed/universe) [3.0.7+git20161217.04f6ba7-1] (no packageset)
[17:56] -queuebot:#ubuntu-release- New binary: python-btrees [armhf] (zesty-proposed/universe) [4.3.1-1] (no packageset)
[17:57] -queuebot:#ubuntu-release- New binary: dolfin [arm64] (zesty-proposed/universe) [2016.2.0-1] (no packageset)
[17:58] -queuebot:#ubuntu-release- New binary: dolfin [powerpc] (zesty-proposed/universe) [2016.2.0-1] (no packageset)
[17:58] -queuebot:#ubuntu-release- New binary: spigot [powerpc] (zesty-proposed/universe) [0.2016-12-18.g8372d450-1] (no packageset)
[17:58] -queuebot:#ubuntu-release- New binary: pbcopper [powerpc] (zesty-proposed/universe) [0.0.1+20161202-1] (no packageset)
[17:59] -queuebot:#ubuntu-release- New binary: asterisk-opus [powerpc] (zesty-proposed/universe) [13.7+20161113-1] (no packageset)
[18:01] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (vivid-proposed) [<IP_ADDRESS>.77]
[18:01] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (vivid-proposed) [3.19.0-79.87]
[18:06] -queuebot:#ubuntu-release- New binary: python-btrees [powerpc] (zesty-proposed/universe) [4.3.1-1] (no packageset)
[18:07] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (vivid-proposed) [3.19.0-79.87]
[18:09] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (xenial-proposed) [<IP_ADDRESS>.61]
[18:09] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (xenial-proposed) [4.4.0-58.79]
[18:10] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (xenial-proposed) [2.02~beta2-36ubuntu3.6]
[18:11] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (xenial-proposed) [4.4.0-58.79]
[18:12] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (xenial-proposed) [1.66.6]
[19:26] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-107.154]
[19:26] -queuebot:#ubuntu-release- New sync: freeipa (zesty-proposed/primary) [4.3.2-1]
[19:26] -queuebot:#ubuntu-release- New: accepted snapd [i386] (trusty-proposed) [2.20.1~14.04]
[19:27] -queuebot:#ubuntu-release- New: accepted snapd [armhf] (trusty-proposed) [2.20.1~14.04]
[19:32] -queuebot:#ubuntu-release- New: accepted asterisk-opus [powerpc] (zesty-proposed) [13.7+20161113-1]
[19:32] -queuebot:#ubuntu-release- New: accepted python-btrees [powerpc] (zesty-proposed) [4.3.1-1]
[19:33] -queuebot:#ubuntu-release- New: accepted dolfin [arm64] (zesty-proposed) [2016.2.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted libsearpc [powerpc] (zesty-proposed) [3.0.7+git20161217.04f6ba7-1]
[19:33] -queuebot:#ubuntu-release- New: accepted python-btrees [arm64] (zesty-proposed) [4.3.1-1]
[19:33] -queuebot:#ubuntu-release- New: accepted spigot [powerpc] (zesty-proposed) [0.2016-12-18.g8372d450-1]
[19:33] -queuebot:#ubuntu-release- New: accepted dolfin [powerpc] (zesty-proposed) [2016.2.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted python-btrees [armhf] (zesty-proposed) [4.3.1-1]
[19:33] -queuebot:#ubuntu-release- New: accepted pbcopper [powerpc] (zesty-proposed) [0.0.1+20161202-1]
[19:33] -queuebot:#ubuntu-release- New binary: pybigwig [i386] (zesty-proposed/universe) [0.3.2-1ubuntu1] (no packageset)
[19:37] -queuebot:#ubuntu-release- New: accepted asterisk-opus [arm64] (zesty-proposed) [13.7+20161113-1]
[19:37] -queuebot:#ubuntu-release- New: accepted dolfin [amd64] (zesty-proposed) [2016.2.0-1]
[19:37] -queuebot:#ubuntu-release- New: accepted dolfin [i386] (zesty-proposed) [2016.2.0-1]
[19:37] -queuebot:#ubuntu-release- New: accepted dolfin [s390x] (zesty-proposed) [2016.2.0-1]
[19:37] -queuebot:#ubuntu-release- New: accepted libsearpc [armhf] (zesty-proposed) [3.0.7+git20161217.04f6ba7-1]
[19:37] -queuebot:#ubuntu-release- New: accepted pbcopper [amd64] (zesty-proposed) [0.0.1+20161202-1]
[19:37] -queuebot:#ubuntu-release- New: accepted python-btrees [amd64] (zesty-proposed) [4.3.1-1]
[19:37] -queuebot:#ubuntu-release- New: accepted spigot [arm64] (zesty-proposed) [0.2016-12-18.g8372d450-1]
[19:37] -queuebot:#ubuntu-release- New: accepted asterisk-opus [armhf] (zesty-proposed) [13.7+20161113-1]
[19:37] -queuebot:#ubuntu-release- New: accepted dolfin [ppc64el] (zesty-proposed) [2016.2.0-1]
[19:37] -queuebot:#ubuntu-release- New: accepted link-grammar [powerpc] (zesty-proposed) [5.3.13-1]
[19:37] -queuebot:#ubuntu-release- New: accepted python-btrees [i386] (zesty-proposed) [4.3.1-1]
[19:37] -queuebot:#ubuntu-release- New: accepted dolfin [armhf] (zesty-proposed) [2016.2.0-1]
[19:37] -queuebot:#ubuntu-release- New: accepted pbcopper [i386] (zesty-proposed) [0.0.1+20161202-1]
[19:37] -queuebot:#ubuntu-release- New: accepted libsearpc [arm64] (zesty-proposed) [3.0.7+git20161217.04f6ba7-1]
[19:37] -queuebot:#ubuntu-release- New: accepted spigot [armhf] (zesty-proposed) [0.2016-12-18.g8372d450-1]
[19:38] -queuebot:#ubuntu-release- New: accepted asterisk-opus [amd64] (zesty-proposed) [13.7+20161113-1]
[19:38] -queuebot:#ubuntu-release- New: accepted asterisk-opus [ppc64el] (zesty-proposed) [13.7+20161113-1]
[19:38] -queuebot:#ubuntu-release- New: accepted docker-pycreds [amd64] (zesty-proposed) [0.2.1-1]
[19:38] -queuebot:#ubuntu-release- New: accepted golang-gopkg-retry.v1 [amd64] (zesty-proposed) [0.0~git20161025.0.c09f6b8-1]
[19:38] -queuebot:#ubuntu-release- New: accepted libpgobject-util-dbadmin-perl [amd64] (zesty-proposed) [0.100.0-1]
[19:38] -queuebot:#ubuntu-release- New: accepted libsearpc [i386] (zesty-proposed) [3.0.7+git20161217.04f6ba7-1]
[19:38] -queuebot:#ubuntu-release- New: accepted libsearpc [s390x] (zesty-proposed) [3.0.7+git20161217.04f6ba7-1]
[19:38] -queuebot:#ubuntu-release- New: accepted link-grammar [arm64] (zesty-proposed) [5.3.13-1]
[19:38] -queuebot:#ubuntu-release- New: accepted link-grammar [i386] (zesty-proposed) [5.3.13-1]
[19:38] -queuebot:#ubuntu-release- New: accepted link-grammar [s390x] (zesty-proposed) [5.3.13-1]
[19:38] -queuebot:#ubuntu-release- New: accepted asterisk-opus [i386] (zesty-proposed) [13.7+20161113-1]
[19:38] -queuebot:#ubuntu-release- New: accepted fonts-oradano-mincho-gsrr [amd64] (zesty-proposed) [0.2016.0612-1]
[19:38] -queuebot:#ubuntu-release- New: accepted libsearpc [amd64] (zesty-proposed) [3.0.7+git20161217.04f6ba7-1]
[19:39] -queuebot:#ubuntu-release- New: accepted link-grammar [amd64] (zesty-proposed) [5.3.13-1]
[19:39] -queuebot:#ubuntu-release- New: accepted link-grammar [ppc64el] (zesty-proposed) [5.3.13-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-exit-hook [amd64] (zesty-proposed) [1.1.1-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-globals [amd64] (zesty-proposed) [9.14.0-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-gulp-util [amd64] (zesty-proposed) [3.0.7-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-kew [amd64] (zesty-proposed) [0.7.0-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-lodash-reevaluate [amd64] (zesty-proposed) [3.0.0-1]
[19:39] -queuebot:#ubuntu-release- New: accepted asterisk-opus [s390x] (zesty-proposed) [13.7+20161113-1]
[19:39] -queuebot:#ubuntu-release- New: accepted libsearpc [ppc64el] (zesty-proposed) [3.0.7+git20161217.04f6ba7-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-ansi-escapes [amd64] (zesty-proposed) [1.4.0-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-gulp-plumber [amd64] (zesty-proposed) [1.1.0-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-lodash-reescape [amd64] (zesty-proposed) [3.0.0-1]
[19:39] -queuebot:#ubuntu-release- New: accepted nrpe-ng [amd64] (zesty-proposed) [0.1.2-1]
[19:39] -queuebot:#ubuntu-release- New: accepted pbcopper [s390x] (zesty-proposed) [0.0.1+20161202-1]
[19:39] -queuebot:#ubuntu-release- New: accepted python-btrees [ppc64el] (zesty-proposed) [4.3.1-1]
[19:39] -queuebot:#ubuntu-release- New: accepted r-cran-prettyunits [amd64] (zesty-proposed) [1.0.2-1]
[19:39] -queuebot:#ubuntu-release- New: accepted spigot [i386] (zesty-proposed) [0.2016-12-18.g8372d450-1]
[19:39] -queuebot:#ubuntu-release- New: accepted libbio-coordinate-perl [amd64] (zesty-proposed) [1.7.1-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-external-editor [amd64] (zesty-proposed) [2.0.1+dfsg-1]
[19:39] -queuebot:#ubuntu-release- New: accepted node-tildify [amd64] (zesty-proposed) [1.2.0-1]
[19:39] -queuebot:#ubuntu-release- New: accepted pydbus [amd64] (zesty-proposed) [0.5.1-1]
[19:39] -queuebot:#ubuntu-release- New: accepted spigot [amd64] (zesty-proposed) [0.2016-12-18.g8372d450-1]
[19:39] -queuebot:#ubuntu-release- New: accepted spigot [s390x] (zesty-proposed) [0.2016-12-18.g8372d450-1]
[19:39] -queuebot:#ubuntu-release- New binary: ip4r [arm64] (zesty-proposed/universe) [2.1.1-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: ip4r [i386] (zesty-proposed/universe) [2.1.1-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: ip4r [ppc64el] (zesty-proposed/universe) [2.1.1-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: mimeo [amd64] (zesty-proposed/universe) [1.4.4-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New: accepted link-grammar [armhf] (zesty-proposed) [5.3.13-1]
[19:39] -queuebot:#ubuntu-release- New: accepted pbcopper [ppc64el] (zesty-proposed) [0.0.1+20161202-1]
[19:39] -queuebot:#ubuntu-release- New: accepted spigot [ppc64el] (zesty-proposed) [0.2016-12-18.g8372d450-1]
[19:39] -queuebot:#ubuntu-release- New binary: ip4r [armhf] (zesty-proposed/universe) [2.1.1-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: ip4r [s390x] (zesty-proposed/universe) [2.1.1-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgmemcache [arm64] (zesty-proposed/universe) [2.3.0-3ubuntu3] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgmemcache [powerpc] (zesty-proposed/universe) [2.3.0-3ubuntu3] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgmemcache [s390x] (zesty-proposed/universe) [2.3.0-3ubuntu3] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgrouting [i386] (zesty-proposed/universe) [2.3.1-1build2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgrouting [ppc64el] (zesty-proposed/universe) [2.3.1-1build2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New: accepted node-is-promise [amd64] (zesty-proposed) [2.1.0-1]
[19:39] -queuebot:#ubuntu-release- New binary: ip4r [amd64] (zesty-proposed/universe) [2.1.1-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgmemcache [amd64] (zesty-proposed/universe) [2.3.0-3ubuntu3] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgmemcache [ppc64el] (zesty-proposed/universe) [2.3.0-3ubuntu3] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgrouting [powerpc] (zesty-proposed/universe) [2.3.1-1build2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: postgis [amd64] (zesty-proposed/universe) [2.3.1+dfsg-1build1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: postgis [armhf] (zesty-proposed/universe) [2.3.1+dfsg-1build1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: postgis [powerpc] (zesty-proposed/universe) [2.3.1+dfsg-1build1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: postgis [s390x] (zesty-proposed/universe) [2.3.1+dfsg-1build1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New: accepted python-btrees [s390x] (zesty-proposed) [4.3.1-1]
[19:39] -queuebot:#ubuntu-release- New binary: pgmemcache [i386] (zesty-proposed/universe) [2.3.0-3ubuntu3] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgrouting [s390x] (zesty-proposed/universe) [2.3.1-1build2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: postgis [i386] (zesty-proposed/universe) [2.3.1+dfsg-1build1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: ip4r [powerpc] (zesty-proposed/universe) [2.1.1-1ubuntu2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: postgis [arm64] (zesty-proposed/universe) [2.3.1+dfsg-1build1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: pgrouting [amd64] (zesty-proposed/universe) [2.3.1-1build2] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: postgis [ppc64el] (zesty-proposed/universe) [2.3.1+dfsg-1build1] (no packageset)
[20:11] -queuebot:#ubuntu-release- New sync: yabasic (zesty-proposed/primary) [1:2.77.2-1]
[20:30] -queuebot:#ubuntu-release- New binary: r-cran-progress [amd64] (zesty-proposed/universe) [1.1.2-1] (no packageset)
[20:32] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (vivid-proposed/main) [3.19.0-79.87] (core, kernel)
[20:32] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-58.79] (core, kernel)
[20:40] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (vivid-proposed) [3.19.0-79.87]
[23:13] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-58.79]


[00:10] <xnox> vorlon:  openssh:i386 has a depwait on libfido2-dev => would you like to disable that feature on i386? or build libfido2-dev for i386?
[00:10] <xnox> https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4/+build/18767920
[00:10] <vorlon> xnox: that's so 2 hours ago
[00:10] <vorlon> xnox: now I need to fix the dep-wait of libfido2/i386 instead
[00:11] <xnox> ok
[00:11] <xnox> vorlon:  you don't need to do no-change rebuild, you can have done a binary copy from focal to focal-proposed => this would have created a build record on i386.
[00:12]  * xnox ponders to do that with libcbor then
[00:12] <vorlon> (it's being mired so there's no reason to deviate)
[00:12] <vorlon> xnox: no, the binary copy does not create the build records
[00:12] <vorlon> I tried that early in the process :)
[00:13] <vorlon> xnox: hmm although I don't think I ever did a focal->focal-proposed, did you actually do this and see that it worked?
[00:14] <xnox> vorlon:  it did for me before, i've done that earler in the cycle when something for doko got re-whitelisted
[00:14] <xnox> i have done this now for libcbor, let's see what happens.
[00:14] <vorlon> k
[00:14]  * xnox has no ACLs to copy to focal-release, so I only can copy to focal-proposed
[00:15] <xnox> vorlon:  https://launchpad.net/ubuntu/focal/i386/libcbor-dev looks like it is getting published from the past
[00:15] <vorlon> and we don't want it built in focal anyway, we want it built in focal-proposed and go through the appropriate p-m sanity checks
[00:15] <xnox> vorlon:  why build at all? it's simply republishing removed i386 binary that was there.
[00:16] <vorlon> xnox: ah right, in that case it'll bring back the i386 binaries with no new build
[00:16] <xnox> i386 build of libcbor-dev already exists
[00:16] <vorlon> yes
[00:16] <xnox> vorlon:  i have done this already
[00:16] <vorlon> but I've not seen the binary copy create a new build record
[00:16] <xnox> ignore me =)
[00:16] <xnox> vorlon:  so for mattias, i did binary copy for something that didn't have i386 build, that was built in focal-proposed and already migrated to release pocket.
[00:17] <xnox> and i386 build record got created in focal-proposed
[00:17] <vorlon> and the binary copy resuscitates the i386 binaries whether you want them or not
[00:17] <xnox> that's similar to how new arches get bootstraped too
[00:17] <xnox> i think it still goes thorugh the whitelist/blacklist. I did not see non-whitelisted binaries getting published.
[00:17] <xnox> but also wouldn't want to experiment with that
[00:18] <vorlon> no, the whitelist definitely does not filter out the binaries on binary copy
[00:18] <vorlon> so packages that were built in -proposed before the whitelist was in place and haven't yet migrated to the release pocket, I've been having to go back and clean up :P
[00:20] <xnox> ouch
[00:20] <xnox> ok
[00:21] -queuebot:#ubuntu-release- New binary: linux-signed-gke-4.15 [amd64] (bionic-proposed/main) [4.15.0-1054.57] (no packageset)
[00:22] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-90.91] (core, kernel)
[00:23] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-90.91] (core, kernel)
[00:30] -queuebot:#ubuntu-release- Packageset: Added libcbor to i386-whitelist in focal
[00:30] <xnox> hm
[00:34] -queuebot:#ubuntu-release- New: accepted azure-cosmos-table-python [amd64] (focal-proposed) [1.0.5+git20191025-1]
[00:34] -queuebot:#ubuntu-release- New: accepted kodiplatform [amd64] (focal-proposed) [20180302-0ubuntu1]
[00:34] -queuebot:#ubuntu-release- New: accepted kodiplatform [armhf] (focal-proposed) [20180302-0ubuntu1]
[00:34] -queuebot:#ubuntu-release- New: accepted kodiplatform [s390x] (focal-proposed) [20180302-0ubuntu1]
[00:34] -queuebot:#ubuntu-release- New: accepted libserial [arm64] (focal-proposed) [1.0.0-2~build1]
[00:34] -queuebot:#ubuntu-release- New: accepted libserial [ppc64el] (focal-proposed) [1.0.0-2~build1]
[00:34] -queuebot:#ubuntu-release- New: accepted eshell-z [amd64] (focal-proposed) [0.4-3]
[00:34] -queuebot:#ubuntu-release- New: accepted kodiplatform [ppc64el] (focal-proposed) [20180302-0ubuntu1]
[00:34] -queuebot:#ubuntu-release- New: accepted libserial [armhf] (focal-proposed) [1.0.0-2~build1]
[00:34] -queuebot:#ubuntu-release- New: accepted kodiplatform [arm64] (focal-proposed) [20180302-0ubuntu1]
[00:34] -queuebot:#ubuntu-release- New: accepted libserial [s390x] (focal-proposed) [1.0.0-2~build1]
[00:34] -queuebot:#ubuntu-release- New: accepted libserial [amd64] (focal-proposed) [1.0.0-2~build1]
[01:44] <wxl> did we add some thing to check the iso on boot? if so, where?
[01:44] <wxl> also does anyone know if this new iso manifest-diff check applies to flavors? or can we make it be? is there code for this somewhere?
[01:44] <wxl> (forgive me folks on devel for the doublespeak but it should probably be here)
[04:02] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (focal-proposed) [2.12.0-0ubuntu2]
[04:15] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (focal-proposed/main) [5.4.0-1004.4] (core, kernel)
[04:15] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (focal-proposed/main) [5.4.0-16.19] (core, kernel)
[04:15] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (focal-proposed/main) [5.4.0-16.19] (core, kernel)
[04:16] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (focal-proposed/main) [5.4.0-16.19] (core, kernel)
[04:16] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (focal-proposed/main) [5.4.0-16.19] (core, kernel)
[05:12] -queuebot:#ubuntu-release- New: accepted linux-signed-gke-4.15 [amd64] (bionic-proposed) [4.15.0-1054.57]
[05:12] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-90.91]
[05:12] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1074.84]
[05:13] -queuebot:#ubuntu-release- New binary: microsoft-authentication-library-for-python [amd64] (focal-proposed/none) [1.1.0-1] (no packageset)
[05:14] -queuebot:#ubuntu-release- New binary: azure-multiapi-storage-python [amd64] (focal-proposed/universe) [0.2.4-1] (no packageset)
[05:14] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (focal-proposed) [5.4.0-1004.4]
[05:14] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (focal-proposed) [5.4.0-16.19]
[05:14] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (focal-proposed) [5.4.0-16.19]
[05:14] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (focal-proposed) [5.4.0-16.19]
[05:14] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (focal-proposed) [5.4.0-16.19]
[05:33] <vorlon> doko: was a new upload of python3-defaults still incoming this week?
[06:10] <vorlon> cpaelzer: https://launchpad.net/ubuntu/+source/procps/2:3.3.16-1ubuntu2 lol (Debian bug #951494)
[06:26] <vorlon> mysqltest: At line 69: Query 'ALTER EVENT event_starts_test ON SCHEDULE AT '2020-02-02 20:00:02'' failed.
[06:26] <vorlon> ERROR 1589 (HY000): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.
[06:26] <vorlon> mmmhmm
[07:03] <cpaelzer> vorlon: nice on procps, one would think that this would have wreaked more havoc than the bit we have seen
[08:01] <vorlon> Laney, sil2100: so icu didn't quite make it because of one last package that was in the easy hint but shouldn't have been because it's not a candidate. :/  the next britney run SHOULD take care of this, but I don't have 2 hours to wait around for it.  can one of you help shepherd?  I've added some aggressive hints on this such that it really really should go through, but there might be some manual
[08:02] <vorlon> cleanup required afterwards
[08:07] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-90.91]
[08:14] <sil2100> vorlon: hey! Okay, thanks for that! I can keep an eye out on it
[08:15] <sil2100> vorlon: I see the force hint, any particular issues I should be looking out for? Or just seeing if icu migrates?
[08:16] -queuebot:#ubuntu-release- New binary: libept [s390x] (focal-proposed/universe) [1.1+nmu3ubuntu3] (no packageset)
[08:17] -queuebot:#ubuntu-release- New binary: libept [ppc64el] (focal-proposed/universe) [1.1+nmu3ubuntu3] (no packageset)
[08:17] -queuebot:#ubuntu-release- New binary: libept [amd64] (focal-proposed/universe) [1.1+nmu3ubuntu3] (no packageset)
[08:19] <juliank> Finishing up the APT transition uploads now
[08:19] -queuebot:#ubuntu-release- New binary: libept [arm64] (focal-proposed/universe) [1.1+nmu3ubuntu3] (no packageset)
[08:21] -queuebot:#ubuntu-release- New binary: libept [armhf] (focal-proposed/universe) [1.1+nmu3ubuntu3] (no packageset)
[08:37] -queuebot:#ubuntu-release- Unapproved: aptitude (eoan-proposed/universe) [0.8.11-3ubuntu3 => 0.8.12-1ubuntu4] (no packageset)
[08:37] -queuebot:#ubuntu-release- New binary: therion [amd64] (focal-proposed/universe) [5.4.4ds1-5ubuntu1] (no packageset)
[08:39] -queuebot:#ubuntu-release- Unapproved: apt-move (eoan-proposed/universe) [4.2.27-5ubuntu1 => 4.2.27-5ubuntu2] (no packageset)
[08:43] -queuebot:#ubuntu-release- Unapproved: libapt-pkg-perl (eoan-proposed/main) [0.1.36 => 0.1.36build2] (core)
[08:45] -queuebot:#ubuntu-release- Unapproved: libqapt (eoan-proposed/universe) [3.0.4-1ubuntu4 => 3.0.4-1ubuntu5] (kubuntu)
[08:46] <juliank> huh
[08:47] <juliank> Sorry seems the script had eoan in changelog
[08:48] <juliank> I'll reupload shortly, sorry
[08:49] <apw> juliank, should i assume that those 4 uploads all want to be rejected ?
[08:50] <juliank> yes, apw
[08:50] <juliank> thanks
[08:50] <apw> np
[08:51] -queuebot:#ubuntu-release- Unapproved: rejected apt-move [source] (eoan-proposed) [4.2.27-5ubuntu2]
[08:51] -queuebot:#ubuntu-release- Unapproved: rejected libapt-pkg-perl [source] (eoan-proposed) [0.1.36build2]
[08:51] -queuebot:#ubuntu-release- Unapproved: rejected aptitude [source] (eoan-proposed) [0.8.12-1ubuntu4]
[08:51] -queuebot:#ubuntu-release- Unapproved: rejected libqapt [source] (eoan-proposed) [3.0.4-1ubuntu5]
[09:05] <seb128> hey there, so since the icu transition still didn't go through, if it doesn't clear today, can we get a standing ff report for packages blocked from being uploaded by it?
[09:12] <juliank> seb128: did you wait for the latest run?
[09:13] <juliank> seb128: vorlon added hints an hour ago that should make it go through
[09:15] <seb128> juliank, I had other packages migrating 50 minutes ago
[09:15] <seb128> but maybe it needs yet another round?
[09:15] <juliank> seb128: sil2100 should know
[09:19] <seb128> juliank, do you know where one can check what's the publisher status? like when was the last update started/finished?
[09:20] <sil2100> https://people.canonical.com/~ubuntu-archive/proposed-migration/log/focal/2020-02-27/
[09:20] <sil2100> So it's still running right now, the previous run seems to have been the one for vorlon's previous easy hint
[09:21] <sil2100> I assume only now the force one will be taken into consideration
[09:25] <seb128> hey sil2100, thanks
[09:26] <seb128> sil2100, do you know if update_excuses_by_team.html was listed reason why 'candidate' were not moving, like 'depends on icu' earlier in the week of I had dreamed that one?
[09:49] <juliank> who/what's retrying python-apt builds all the time`
[09:49] <juliank> ?
[09:49] <juliank> this is annoying
[09:49] <juliank> it's failing, it will continue to fail, there's no point in retrying it every hour or so
[10:04] <LocutusOfBorg> juliank, sorry, I mass retried what failed tonight, because of the x11 sadness
[10:04] <LocutusOfBorg> I had around 40 packages that went from sad to good
[10:04] <LocutusOfBorg> and I retried them once more after they published
[10:04] <rbalint> LocutusOfBorg, thanks for the retries for the sadness
[10:05] <LocutusOfBorg> lots of ruby stuff is now good
[10:06] <doko> vorlon: I wanted the current one to migrate first, maybe overriding the uninstallability issue firsdt
[10:26] <LocutusOfBorg> vorlon, can you please NBS-proposed cleanup https://launchpad.net/ubuntu/+source/reposurgeon/4.3+git20200214.8d048e1-1 ?
[10:26] <LocutusOfBorg> armhf is NBS now and gone in Debian
[10:57] <Laney> icu stuff is going in now
[10:58] <LocutusOfBorg> <3
[10:59] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (eoan-proposed/main) [1.8+19.10ubuntu1 => 1.9+19.10ubuntu1] (desktop-core)
[11:00] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (bionic-proposed/main) [1.8+18.04ubuntu2 => 1.9+18.04ubuntu1] (desktop-core)
[11:00] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (xenial-proposed/main) [1.8+16.04ubuntu1 => 1.9+16.04ubuntu1] (no packageset)
[11:06] <LocutusOfBorg> since ocaml/gprbuild were mostly ready before ruby started the transition, can we copy-back two packages and then restore after migration?
[11:07] <LocutusOfBorg> hivex 1.3.18-2build1 and libguestsfs 1:1.40.2-7ubuntu3 are probably enough
[11:08] <LocutusOfBorg> doko,  what is your opinion? I can't parse anymore britney, it was stuck by python3.8 autopkgtests
[11:17] -queuebot:#ubuntu-release- New: accepted azure-multiapi-storage-python [amd64] (focal-proposed) [0.2.4-1]
[11:17] -queuebot:#ubuntu-release- New: accepted microsoft-authentication-library-for-python [amd64] (focal-proposed) [1.1.0-1]
[11:18] <cjwatson> vorlon: Could you file a bug about copies reviving binaries in spite of the DAS filter?  I don't think that's totally intended.
[11:18] <cjwatson> Or at least it seems questionable.
[11:19] <cjwatson> Copies should certainly create build records.
[11:19] <cjwatson> (Assuming the filter permits them)
[12:16] -queuebot:#ubuntu-release- New source: kpeoplevcard (focal-proposed/primary) [0.1-0ubuntu1]
[12:17] -queuebot:#ubuntu-release- New binary: microsoft-authentication-extensions-for-python [amd64] (focal-proposed/universe) [0.1.3-1] (no packageset)
[13:01] <sforshee> can someone help get linux-firmware 1.173.15 promoted in bionic? It looks like it should be ready
[13:06] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-90.91~16.04.1] (kernel)
[13:09] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-90.91~16.04.1] (kernel)
[13:23] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-90.91~16.04.1]
[13:23] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-90.91~16.04.1]
[14:14] <sil2100> rbalint: hey! Did you see my comment/question https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1861909/comments/8 ?
[14:21] -queuebot:#ubuntu-release- New binary: elasticsearch-curator [amd64] (focal-proposed/universe) [5.8.1-1] (no packageset)
[14:26] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1073.78] (kernel)
[14:49] -queuebot:#ubuntu-release- New source: sane-airscan (focal-proposed/primary) [0.9.16-0ubuntu1]
[14:50] <cpaelzer> hi AAs I'd ask for help on https://launchpad.net/ubuntu/+source/microsoft-authentication-extensions-for-python
[14:50] <cpaelzer> 0.1.3-1 just passed debian-New ~10h ago
[14:51] <cpaelzer> as usual with Debian new that was a binary upload
[14:51] <cpaelzer> 0.1.3-2 is the source upload and in Debian since ~3h and soon hitting ubutu as well I guess
[14:51] <cpaelzer> the package is in the Ubuntu new queue at https://launchpad.net/ubuntu/focal/+queue?queue_state=0&queue_text=
[14:52] <cpaelzer> I was wondering if an AA would need to accept the one in the new queue right now
[14:52] <cpaelzer> or if this has to wait until the source upload of 0.1.3-2 appears?
[14:52] <cpaelzer> apw: seb128: doko: ^^
[14:54] <cpaelzer> bluca: I just asked the archive admins - lets wait for an answer
[14:54] <bluca> hello - thanks
[15:11] <bluca> hi seb128 - I see you took care of network-manager-openconnect in the past, any chance you could have time to please look at https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1857624 please? We got patches in Debian to add GP support, and we use GP in Microsoft so it would be great if it worked out of the box in 20.04 for the internal users. Thanks!
[15:12] <seb128> bluca, do you know what that version is in debian/experimental only?
[15:12] <seb128> cpaelzer, I'm in a call but I try to have a look when possible
[15:16] <bluca> not 100% sure - I think the maintainer was holding back to go to the next release directly, since the patches in -3 were reworked upstream - but that requires also a new version of openconnect, so it's all kinda stalled
[15:33] <rbalint> sil2100, no, i've missed that but i'm on it, thanks!
[15:38] <vorlon> sil2100: it was just watching to make sure that if the uninstallables increased, we followed through on those.  The force hint was "just in case" something changed and broke the main hint
[15:43] <vorlon> now, does anyone know why there hasn't been a britney run /since/ this?
[15:43] <vorlon> doko: the current python3-defaults /did/ migrate last week
[15:43] <vorlon> doko: because I override the tests as we discussed
[15:43] <vorlon> overrode
[15:46] <Laney> this> icu? Sure there has
[15:51] <vorlon> ah, I was just using a wrong glob
[15:51] <vorlon> hours beginning with 1 do not have logs matching 0*
[15:51] <vorlon> :)
[15:53] <Laney> check out snakefruit:~laney/tail-latest-britney-log
[15:53] <Laney> :>
[15:58] <vorlon> Laney: do you know why arm64 autopkgtest queues aren't progressing?
[15:59] <Laney> vorlon: they are
[15:59] <Laney> ubuntu@juju-prod-ues-proposed-migration-machine-11:~$ journalctl --since=15:00 ADT_ARCH=arm64 | grep -c 'Acknowledging request'
[15:59] <Laney> 48
[15:59] <vorlon> Laney: but much more slowly than they should https://cdo.kpi.canonical.com/d/000000030/ubuntu-foundations?panelId=19&fullscreen&orgId=1
[16:01] <Laney> can't say what the value of should is
[16:01] <Laney> I noticed some unhelpful things earlier in the day like lots of duplicated gscan2pdf requests that people had done
[16:02] <Laney> and for example right now there are some libreoffice runs that are duplicating one another
[16:02] <vorlon> ah, well we should axe those for sure
[16:02] <vorlon> Laney: generally arm64 seems to be about half as fast as the others
[16:03] <vorlon> but obviously duplicate libreoffice tests are outside the norm :P
[16:05] <Laney> I sort of trained myself to expect arm64 to be the worst
[16:05] <Laney> perhaps that's not always been the case ...
[16:07] <Laney> if we had engineering but not hardware to look into this I would suggest looking at lxding by default and VMing only when needed
[16:08] <doko> vorlon: no asked for python3.8, not python3-defaults
 vorlon: would you be willing to ignore every autopkg test for python3-defaults, dropping python3.7? the reason I'm asking is that everything else is still tested with 3.7, which we don't care about anymore
[16:11] <vorlon> doko: there are logs :P
[16:11] <vorlon> you asked me to skip for python3-defaults and said there would be a new upload this week
[16:11] <Laney> vorlon: would be handy if you could take on killing off those libreoffice requests if you've time; I'm trying to help people get stuff uploaded for FF at the minute
[16:11] <vorlon> ack
[16:12] <Laney> you might like the not committed filter-amqp-dupes script
[16:12] <Laney> hmm, actually that's not that helpful for already-in-progress runs
[16:13] <Laney> what you need to do is HUP the workers, kill the runner/autopkgtest processes and then filter the requests before anything restarts and picks it back up
[16:48] <cpaelzer> seb128: apw: doko: (and now I also see vorlon around) - I wanted to ping again for microsoft-authentication-extensions-for-python in the focal new queue and how it needs to be handled (details about 2h up in the log)
[16:49] <seb128> cpaelzer, accepted
[16:50] -queuebot:#ubuntu-release- New: accepted microsoft-authentication-extensions-for-python [amd64] (focal-proposed) [0.1.3-1]
[16:50] <cpaelzer> thanks seb128
[16:50] <cpaelzer> did the discussion on that vpn thing conlude as well?
[16:50] <cpaelzer> +c
[16:51] -queuebot:#ubuntu-release- New: accepted elasticsearch-curator [amd64] (focal-proposed) [5.8.1-1]
[16:51] -queuebot:#ubuntu-release- New: accepted libept [arm64] (focal-proposed) [1.1+nmu3ubuntu3]
[16:51] -queuebot:#ubuntu-release- New: accepted libept [ppc64el] (focal-proposed) [1.1+nmu3ubuntu3]
[16:51] -queuebot:#ubuntu-release- New: accepted therion [amd64] (focal-proposed) [5.4.4ds1-5ubuntu1]
[16:51] -queuebot:#ubuntu-release- New: accepted libept [amd64] (focal-proposed) [1.1+nmu3ubuntu3]
[16:51] -queuebot:#ubuntu-release- New: accepted libept [s390x] (focal-proposed) [1.1+nmu3ubuntu3]
[16:51] -queuebot:#ubuntu-release- New: accepted libept [armhf] (focal-proposed) [1.1+nmu3ubuntu3]
[16:51] <seb128> cpaelzer, if it's not good enough to get to Debian unstable I'm a bit nervous to get it in focal
[16:52] <seb128> cpaelzer, but if someone wants to do the Debian merge and upload I will not stop them
[16:52] <seb128> I just don't have enough acccess to VPNs to test that and the fact that the Debian maintainer keeps it in experimental doesn't give me confidence
[16:53] <cpaelzer> ok good to know, bluca ^^ here you know what to work on now
[16:53] <cpaelzer> get it in unstable might be the easiest path to work on for you I guess?
[16:54] <vorlon> rafaeldtinoco: libguestfs entangled ocaml and ruby, I'm rolling this back to let us try to get both halves through sooner
[16:54] <rafaeldtinoco> no problem. tks!
[16:55] <cjwatson> Can I assume that somebody is going to take care of putting auto-sync into --dry-run mode at EOD today?
[16:56] <vorlon> cjwatson: yes
[16:56] <cpaelzer> vorlon: will you (later) bring libguestfs back again => https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1864164 ?
[16:56] <cjwatson> good good
[16:56] <vorlon> cpaelzer: yes
[16:56] <cpaelzer> ok
[16:56] <cpaelzer> just asked as I've known bugs depend on it
[16:57] <bluca> thanks, I'll ping the Debian maintainer
[16:58] <bluca> and thanks for processing new
[16:58] <juliank> ooh, libept is accepted, time to do rebuilds for its rdeps
[16:59] <juliank> oh not publshed yet
[16:59] <juliank> oh, my affected hint is wrong for apt transition, so you only see bad ones
[17:00] <bluca> are syncs from unstable still happening automatically? I've fixed a silly mistake in the b-deps list in https://launchpad.net/ubuntu/+source/azure-functions-devops-build/ early this morning
[17:00] <vorlon> bluca: yes, until EOD Pacific coast time
[17:04] <vorlon> LocutusOfBorg, kenvandine, marcustomlinson: I am killing all libreoffice/arm64 autopkgtests from the queue, please don't queue any more; these timeouts are choking the infra.  We will treat this as a badtest for now
[17:08] <sforshee> can linux-firmware 1.173.15 in bionic be promoted? It looks ready to me
[17:08] <vorlon> by promoted, you mean the sru released to -updates?
[17:08] <sforshee> vorlon: yes
[17:09] <vorlon> yes, doing
[17:09] <sforshee> ta
[17:11] <vorlon> xnox: I've done what I can to clear out the autopkgtest regressions for your glibc upload (by badtesting those reproducible in updates), but there are some that seem to really be proposed-only; nauty/i386 is really weird
[17:13] <vorlon> doko: what did you say was the blocker for removing python3.7 right now?
[17:17] -queuebot:#ubuntu-release- New binary: python-pweave [amd64] (focal-proposed/universe) [0.25-2] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: smrtanalysis [amd64] (focal-proposed/universe) [0~20200227] (no packageset)
[17:19] -queuebot:#ubuntu-release- New: accepted python-pweave [amd64] (focal-proposed) [0.25-2]
[17:19] -queuebot:#ubuntu-release- New: accepted smrtanalysis [amd64] (focal-proposed) [0~20200227]
[17:20] -queuebot:#ubuntu-release- New binary: gnumed-server [amd64] (focal-proposed/universe) [22.9-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New: accepted gnumed-server [amd64] (focal-proposed) [22.9-1]
[17:28] <vorlon> rafaeldtinoco: hivex also rolled back, same rationale (ocaml+ruby)
[17:29] <rafaeldtinoco> cool
[17:36] <xnox> vorlon:  i've seen weird things on i386, as if the machines started to use 64bit kernel; because some packages started to try to search for 64bit implementation of things, instead of 32bit ones. Do we know if images have changed in eoan to use 64bit kernel and for example some packages didn't run tests in eoan, since that change?
[17:37] <vorlon> xnox: but a baseline retest of that one succeeded, it only failed with the new glibc
[17:39] <xnox> vorlon:  excellent. it does suggest a missbuilt glibc.
[17:39] <xnox> and nauty itself hasn't been rebuilt in ages.
[17:40] <vorlon> except via the rebuild autopkgtest
[17:43] <xnox> checked rebuild test results for disco & eoan they don't list it
[17:50] <LocutusOfBorg> vorlon, are you available for some quick migration? 1) reposurgeon -> NBS on armhf in proposed, removed in debian 2) gazebo: amd64 only package, needs a permanent hint everywhere else
[17:51] <LocutusOfBorg> and this https://code.launchpad.net/~till-kamppeter/britney/hints-ubuntu/+merge/379911
[17:51] <LocutusOfBorg> its a matter of kick the can along
[17:55] -queuebot:#ubuntu-release- Unapproved: zfs-linux (bionic-proposed/main) [0.7.5-1ubuntu16.8 => 0.7.5-1ubuntu16.9] (core)
[17:58] <xnox> vorlon:  there are two tests, make-check and build-examples. The build-examples autopkgtest depends on build-essential and after failing initially, it does use all-proposed and installs both libc6-dev and libc6. During the make-check test, it does not depend on build-essential and there is this gem in the log:
[17:58] <xnox> Holding Back libc6-dev:i386 rather than change libc6:i386
[17:59] <xnox> meaning that neither new libc6 got installed, nor libc6-dev got installed thus leading to
[17:59] <xnox> naucompare.c:5: error: include file 'stdio.h' not found
[17:59] <doko> vorlon: uwsgi-plugin-python3
[18:00] <xnox> vorlon:  in an eoan i386 schroot, with manually installed libc6-dev & libc6 from proposed, ./debian/tests/make-check passes
[18:07] <xnox> vorlon:  https://paste.ubuntu.com/p/X8mqs53rcs/
[18:13] -queuebot:#ubuntu-release- New binary: kodi [s390x] (focal-proposed/universe) [2:18.5+dfsg1-0ubuntu2] (no packageset)
[18:15] <rbalint> sil2100, ec2-instance-connect is now really verified
[18:18] <bluca> can a build be done with a profile (say "nocheck") to break a build-time tie?
[18:22] <vorlon> xnox: ah, right, this is the arch skew bug with the foreign-arch hinting, I think?  hmm I thought I had patched that?  anyway, if you retry it with all-proposed=1 I think it should pass
[18:22] <vorlon> LocutusOfBorg: reposurgeon/armhf removed
[18:23] <sil2100> rbalint: on it!
[18:23] <vorlon> LocutusOfBorg: libqtpropertybrowser-dev is amd64-only?  that seems... weird
[18:24] <vorlon> LocutusOfBorg: anyway, gazebo hinted
[18:46] <rafaeldtinoco> there is a dead-lock in build-dependency among jruby and ruby-psych packages.. debian has done a binary upload to unlock this ..
[18:46] <rafaeldtinoco> can I upload a binary for ruby-psych, build jruby, and upload ruby-psych in source again ?
[18:46] <rafaeldtinoco> would that be possible ?
[18:46] <rafaeldtinoco> to unlock this situation ?
[18:47] <bluca> (same for azure-cli and azure-functions-devops-build which is the reason I asked about the nocheck profile build)
[18:53] <rafaeldtinoco> for my case I would need "sid" binaries of libpsych-java_3.1.0+really3.1.0-1_all.deb AND ruby-psych_3.1.0+really3.1.0-1+b1_amd64.deb for amd64, arm64, armhf, ppc64el, s390x into -proposed
[18:53] <rafaeldtinoco> that would allow be to build jruby
[18:53] <rafaeldtinoco> and rebuild ruby-psych and libpsych-java would work
[18:55] <rafaeldtinoco> just tested and it worked
[18:55] <rafaeldtinoco> vorlon: ^ any comment on that ?
[18:55] <rafaeldtinoco> would that be possible ?
[18:55] <rafaeldtinoco> this would unlock the ruby transition
[18:56] <rafaeldtinoco> https://people.canonical.com/~ubuntu-archive/transitions/html/html/ruby2.7-add.html
[18:56] <rafaeldtinoco> kanashiro: fyi ^
[18:56] <LocutusOfBorg> rafaeldtinoco, no
[18:56] <LocutusOfBorg> you can't upload binaries
[18:56] <rafaeldtinoco> yep, would it be possible for an AA to do it
[18:57] <LocutusOfBorg> you can add a binary such as jruby into ruby-psych/debian directory and call it directly
[18:57] <rafaeldtinoco> bringing from sid
[18:57] <LocutusOfBorg> and then no change rebuild
[18:57] <LocutusOfBorg> this is how I do it usually
[18:57] <rafaeldtinoco> yep but there are multiple arches
[18:57] <LocutusOfBorg> you add multiple binaries :p
[18:57] <rafaeldtinoco> =o)
[18:57] <LocutusOfBorg> and then call the one directly
[18:58] <rafaeldtinoco> well, i can uncompress the debian binary
[18:58] <rafaeldtinoco> from debian/ and do lots of things
[18:58] <rafaeldtinoco> but syncing 2 binaries from sid
[18:58] <rafaeldtinoco> seem easier, no ?
[18:59] <rafaeldtinoco> they will go away right after
[18:59] <rafaeldtinoco> as soon as the first (jruby) is compiled
[19:14] -queuebot:#ubuntu-release- New binary: kodi [amd64] (focal-proposed/universe) [2:18.5+dfsg1-0ubuntu2] (no packageset)
[19:31] <LocutusOfBorg> rafaeldtinoco, if possible, yes
[19:31] <LocutusOfBorg> :)
[19:32] <rafaeldtinoco> let's see
[19:42] -queuebot:#ubuntu-release- New binary: kodi [ppc64el] (focal-proposed/universe) [2:18.5+dfsg1-0ubuntu2] (no packageset)
[19:59] <vorlon> doko: I think I heard you mention gnat earlier, what's the analysis here on plplot vs gnat-8 vs gnat-9? why is it depending on gnat+gnat-9?
[19:59] <vorlon> doko: ah because there's a new gnat metapackage in -proposed, ignore me
[20:10] <bluca> LocutusOfBorg: no profiles either? I'll do an upload to sid without the dependency then, and change it manually later - it's just for tests
[20:10] <bluca> too bad we can't set nocheck or stage1 or whatev
[20:11] -queuebot:#ubuntu-release- Unapproved: linux-firmware (bionic-proposed/main) [1.173.15 => 1.173.16] (core, kernel)
[20:23] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (eoan-proposed) [2.620.1]
[20:23] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (eoan-proposed/main) [2.620 => 2.620.1] (desktop-core)
[20:30] -queuebot:#ubuntu-release- Packageset: Removed boost1.67 from i386-whitelist in focal
[20:30] -queuebot:#ubuntu-release- Packageset: Removed python3.7 from i386-whitelist in focal
[20:30] -queuebot:#ubuntu-release- Packageset: Added amtk to i386-whitelist in focal
[20:30] -queuebot:#ubuntu-release- Packageset: Added mapbox-geometry to i386-whitelist in focal
[20:30] -queuebot:#ubuntu-release- Packageset: Added mapbox-variant to i386-whitelist in focal
[20:30] -queuebot:#ubuntu-release- Packageset: Added mapbox-wagyu to i386-whitelist in focal
[20:50] <kanashiro> vorlon, could you please provide some feedback about rafaeldtinoco's proposal above regarding ruby-psych and jruby situation?
[20:53] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1073.78]
[21:34] <vorlon> rafaeldtinoco, kanashiro: "upload a binary" - no, that's not an option
[21:34] <rafaeldtinoco> no no I know
[21:34] <rafaeldtinoco> what about U copying from debian temporarily ?
[21:34] <rafaeldtinoco> is that an option ?
[21:35] <vorlon> rafaeldtinoco: we can't copy binaries from Debian, no
[21:35] <rafaeldtinoco> ok
[21:35] <rafaeldtinoco> trying to find alternatives =)
[21:36] <vorlon> I mean, I could use a Debian binary in the bootstrap archive
[21:36] <vorlon> if that's really the only way
[21:36] <vorlon> but that requires an AA to do it
[21:36] <rafaeldtinoco> let me explain to see if you can come up with any idea
[21:37] <rafaeldtinoco> if I have libpsych-java and ruby-psych installed (from sid) I can compile jruby and then I can compile ruby-psych and libpsych-java
[21:37] <rafaeldtinoco> somehow debian got itself in a build-dependency loop by copying binaries over the releases
[21:37] <rafaeldtinoco> ruby-psych was turned into a dependency for jruby to yaml wrapping
[21:38] <rafaeldtinoco> i can generate jruby without ruby-psych, but then it complains about not supporting it when trying to compile ruby-psych itself
[21:44] <vorlon> rafaeldtinoco: is there an earlier, interim version of either package that was in Debian that didn't have the circular dep?
[21:44] <rafaeldtinoco> yes but using ruby2.5
[21:44] <vorlon> ah
[21:44] <rafaeldtinoco> not ruby2.7
[21:44] <vorlon> but would it build in Ubuntu against ruby2.7 if we synced it?
[21:44] <rafaeldtinoco> kanashiro: ^ u know ?
[21:45] <rafaeldtinoco> kanashiro: was the one working with debian ruby team
[21:45]  * rafaeldtinoco checking git in salsa
[21:45] <kanashiro> I have no idea
[21:45] <kanashiro> need to try it
[21:45] <rafaeldtinoco> debian has binary copied it also
[21:45] <rafaeldtinoco> for sid, is that correct ?
[21:46] <rafaeldtinoco> (over the releases I mean)
[21:46] <rafaeldtinoco> and it contained 2.5 and 2.7
[21:46] <kanashiro> debian sid now has ruby 2.5 and 2.7 enabled
[21:47] <rafaeldtinoco> commit f7bfddd57
[21:47] <rafaeldtinoco> Author: Miguel Landaeta<EMAIL_ADDRESS>[21:47] <rafaeldtinoco> Date:   Sat Sep 16 20:41:24 2017
[21:47] <rafaeldtinoco>     Fix dependencies on ruby-psych and add dependencies on libpsych-java
[21:47] <rafaeldtinoco> debian/<IP_ADDRESS>-3
[21:47] <rafaeldtinoco> this is the tag where it got included
[21:48] <rafaeldtinoco> let me see if I can build that version
[21:50] <kanashiro> that is before the current debian stable release, the chances are low of this jruby version builds fine against ruby 2.7
[21:52] <rafaeldtinoco> -               ruby-json,
[21:52] <rafaeldtinoco> it used ruby-json before
[21:54] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [amd64] (focal-proposed/main) [20.2.1~0ubuntu1] (core)
[21:54] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [s390x] (focal-proposed/main) [20.2.1~0ubuntu1] (core)
[21:54] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [ppc64el] (focal-proposed/main) [20.2.1~0ubuntu1] (core)
[21:56] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [arm64] (focal-proposed/main) [20.2.1~0ubuntu1] (core)
[21:56] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [armhf] (focal-proposed/main) [20.2.1~0ubuntu1] (core)
[22:05] <rafaeldtinoco> the version not depending on psych is so old
[22:05] <rafaeldtinoco> i can't get it to build
[22:09] <vorlon> ok
[22:10] <vorlon> then we might have to resort to the bootstrap archive
[22:20] <rafaeldtinoco> yes, sorry about that
[22:21] <rafaeldtinoco> i really spent a bunch of time on this trying to avoid
[22:21] <rafaeldtinoco> but ruby with java is really not my style to come up with some magick
[22:22] <rafaeldtinoco> ill have a rebuild for both pkgs ready
[22:43] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.40 => 2.525.41] (desktop-core)
[22:47] <vorlon> xnox: o hey, all autopkgtests for glibc/eoan cleared
[23:54] -queuebot:#ubuntu-release- New binary: libxml2 [s390x] (focal-proposed/main) [2.9.10+dfsg-4] (core, i386-whitelist)
[23:54] -queuebot:#ubuntu-release- New binary: libxml2 [i386] (focal-proposed/main) [2.9.10+dfsg-4] (core, i386-whitelist)
[23:54] -queuebot:#ubuntu-release- New binary: libxml2 [ppc64el] (focal-proposed/main) [2.9.10+dfsg-4] (core, i386-whitelist)
[23:57] -queuebot:#ubuntu-release- New binary: libxml2 [amd64] (focal-proposed/main) [2.9.10+dfsg-4] (core, i386-whitelist)
[23:58] -queuebot:#ubuntu-release- New binary: libxml2 [arm64] (focal-proposed/main) [2.9.10+dfsg-4] (core, i386-whitelist)
[23:59] -queuebot:#ubuntu-release- New binary: libxml2 [armhf] (focal-proposed/main) [2.9.10+dfsg-4] (core, i386-whitelist)


[11:16] <keesj> Hi
[11:23] <keesj> I am hitting a old bug that the env are not taken into account on restart
[11:23] <keesj> I am searching for a bug report for that but can't seem to find it (/me need ammo to upgrade to 0.5)
[11:37] <keesj> where is Keybuk?
[13:41] <Md> BTW, a debian user too reported that $REMOVE_CMD is broken
[18:55] <Millox> is it possible to act on custom events sent by initctl emit in upstart 0.3.9 (the one included in hoary)
[18:58] <sadmac> Millox: yes
[18:58] <sadmac> Millox: no settup. Just initctl emit anystringyoucanthinkof
[18:59] <sadmac> and start on thatstring
[19:02] <Millox> well, i'm trying just that but somehow it doesnt work
[19:03] <Millox> in the configfile I have "start on blah" but "initctl emit blah" doesn't start the service
[19:03] <Millox> actually it sometimes say Unknown stanza
[19:04] <sadmac> Millox: pastebin your entire job definition
[19:05] <Millox> hmm, should I use several stop on .. or should I use stop on blah or bleh?
[19:05] <sadmac> depends
[19:06] <sadmac> in 0.3.9 several stop on will work
[19:06] <sadmac> in 0.5 it won't
[19:06] <Millox> okay
[19:07] <Millox> this is the start on and stop on definitions:
[19:07] <Millox> start on (quagga and firewall) or router-up
[19:07] <Millox> stop on router-down
[19:07] <Millox> stop on runlevel 0
[19:07] <Millox> stop on runlevel 1
[19:08] <Millox> stop on runlevel 6
[19:08] <Millox> there is also a post-start script which enables routing and a post-stop which disables routing
[19:09] <Millox> start router and stop router works fine
[19:09] <Millox> sorry about the spamming
[19:09] <Millox> log says:
[19:09] <Millox> init: /etc/event.d/router: unable to read: Invalid argument
[19:10] <sadmac> dunno that 0.3.9 has an and operator
[19:10] <sadmac> or parens
[19:11] <sadmac> not too sure though :O
[19:11] <Millox> maybe it doesn't
[19:11] <Millox> I just removed them and now the invalid argument isn't seen anymore
[19:12] <Millox> however, it still doesn't work
[19:12] <sadmac> hm
[19:23] <Millox> okay, now i managed to get the bounce example working but I still havn't the foggiest why the other doesn't work
[19:23] <Millox> hmm
[19:30] <Millox> just tried adding a script stanza  containg just /bin/true (and exec as well) but it still doen't work
[19:34] <sadmac> try doing it without any and or or operators or parens at all
[19:37] <Millox> tried with only one start on and one stop on but nothing
[19:39] <Millox> hmm
[19:39] <Millox> hsuccess!
[19:39] <Millox> unfortunately i managed to shut down my router in the process ;-)
[19:45] <Millox> apparently you can't have dash in signal names
[19:47] <Millox> changing only the signal names is the difference between invalid argument and succes
[19:47] <Millox> s
[19:48] <Millox> unfortunately the start process doesn't return
[19:48] <Millox> now
[19:51] <sadmac> hm
[19:51] <Millox> ah, service solved that
[19:52] <Millox> okay, now I'm confused
[19:53] <Millox> I've changed everything so much now that I dont know what I changed anymore
[19:53] <Millox> but now it works as it should
[19:55] <sadmac> heh
[20:03] <Millox> okay, another question: the way to emit a signal from a job description is executing /sbin/initctl emit, right or wrong?
[20:04] <sadmac> right
[20:08] <Millox> isn't the job supposed to not run if any of the pre,post-start,stop scripts return nonzero?
[20:11] <sadmac> pre-start maybe
[20:12] <sadmac> the rest of those I think it keeps going
[20:20] <Millox> seems like it yes
[20:20] <sadmac> post-start things are already running, so its too late
[20:20] <sadmac> post stop things are already stopped, so...now what?
[20:21] <sadmac> pre-stop, well you don't want to make it impossible to stop something ever really
[20:26] <Millox> no, that seems reasonable
[20:26] <Millox> I just hadn't thought about it really
[20:27] <Millox> and I suppose, it would be better to spell correctly so that the script doesn't return nonzero :-/
[20:36] <Millox> hmm, I don't feel that the service jobs works correctly...
[20:36] <Millox> i had a problem just now with jobs not starting
[20:37] <Millox> i have a "bogus" job called network which is basically a placeholder for all network starting, and i had only an emitted signal in this job
[20:38] <Millox> firewall and quagga had start on starting network in their job description
[20:40] <Millox> when I had script or exec /sbin/initctl the network first started and then stopped immideately whereas if I used pre-start and no exec or script stanza the network started
[20:40] <Millox> may
[20:40] <Millox> maybe I've completely misunderstood the stanzas
[21:41] <Millox> how is the environment set up for scripts, for instance is pid available through a variable in post-start/pre-stop?