[00:18] -queuebot:#ubuntu-release- Unapproved: sbuild-launchpad-chroot (bionic-proposed/universe) [0.14ubuntu0.18.04.3 => 0.17ubuntu0.20.10.1~18.04.1] (no packageset)
[00:18] -queuebot:#ubuntu-release- Unapproved: sbuild-launchpad-chroot (focal-proposed/universe) [0.16ubuntu0.20.04.2 => 0.17ubuntu0.20.10.1~20.04.1] (no packageset)
[04:23] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (groovy-proposed) [5.8.0-31.33]
[04:23] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (groovy-proposed) [5.8.0-31.33]
[04:23] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (groovy-proposed) [5.8.0-31.33]
[04:23] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (groovy-proposed) [5.8.0-31.33]
[04:30] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (focal-proposed) [5.4.0-56.62]
[04:30] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (focal-proposed) [5.4.0-56.62]
[04:30] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (focal-proposed) [5.4.0-56.62]
[04:30] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (focal-proposed) [5.4.0-56.62]
[05:45] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (hirsute-proposed) [5.8.0-1011.11+21.04.1]
[06:48] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [amd64] (bionic-proposed/main) [5.4.0-56.62~18.04.1] (no packageset)
[06:49] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [arm64] (bionic-proposed/main) [5.4.0-56.62~18.04.1] (no packageset)
[06:49] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [ppc64el] (bionic-proposed/main) [5.4.0-56.62~18.04.1] (no packageset)
[08:08] -queuebot:#ubuntu-release- New sync: mariadb-10.5 (hirsute-proposed/primary) [1:10.5.8-3]
[08:10] <LocutusOfBorg> mariadb-10.5 fails to autosync ^^ because of a binary takeover from mariadb-10.3 libmariadbclient-dev (transitional package)
[08:14] -queuebot:#ubuntu-release- New sync: python-pyxs (hirsute-proposed/primary) [0.4.2~git20190115.97f14313-3]
[08:16] <LocutusOfBorg> python-pyxs is a takeover of pyxs from rbalint ^^
[08:27] -queuebot:#ubuntu-release- New: accepted pynpoint [amd64] (hirsute-proposed) [0.8.3-1]
[08:27] -queuebot:#ubuntu-release- New: accepted gloo [sync] (hirsute-proposed) [0.0~git20200918.3dc0328-1]
[08:30] -queuebot:#ubuntu-release- New binary: gloo [ppc64el] (hirsute-proposed/universe) [0.0~git20200918.3dc0328-1] (no packageset)
[08:30] -queuebot:#ubuntu-release- New binary: gloo [s390x] (hirsute-proposed/universe) [0.0~git20200918.3dc0328-1] (no packageset)
[08:31] -queuebot:#ubuntu-release- New binary: gloo [amd64] (hirsute-proposed/universe) [0.0~git20200918.3dc0328-1] (no packageset)
[08:35] -queuebot:#ubuntu-release- New binary: gloo [arm64] (hirsute-proposed/universe) [0.0~git20200918.3dc0328-1] (no packageset)
[08:48] -queuebot:#ubuntu-release- New binary: gloo [riscv64] (hirsute-proposed/universe) [0.0~git20200918.3dc0328-1] (no packageset)
[09:26] <doko> vorlon: no idea, also fails with binutils trunk: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/binutils/+sourcepub/11788127/+listing-archive-extra
[09:26] <wgrant> Is autopkgtest back up and running on all archs? We can probably clean up the topics here and #ubuntu-devel.
[09:28] <tjaalton> sil2100: just in case you missed it, focal sru queue has that libglvnd backport now
[09:38] <doko> wgrant: afaik, only half of the ppc64el machines are available
[09:52] <sil2100> tjaalton: ok, will pick it up soon!
[09:52] <sil2100> Thanks
[11:05] <LocutusOfBorg> any admin, can you please help nodejs migrate? only two regressions in release are left
[11:06] <LocutusOfBorg> vorlon, ^^ hint node-address/arm64 and node-clean-css/arm64 please?
[11:21] -queuebot:#ubuntu-release- New: accepted oem-stella.cmit-rhyhorn-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[11:29] <LocutusOfBorg> seb128, I have an answer for gloo
[11:29] <LocutusOfBorg> after lots of debugging of auto-sync, the solution was "easy"
[11:29] <LocutusOfBorg> Date	Status	Target	Pocket	Component	Section	Version
[11:29] <LocutusOfBorg>  	2020-11-26 09:28:19 CET	Published	Hirsute	proposed	universe	misc	0.0~git20200918.3dc0328-1
[11:29] <LocutusOfBorg>  	2008-01-09 19:47:02 CET	Obsolete	Warty	release	universe	utils	20020927-2
[11:29] <LocutusOfBorg> it finds a previous publication, with an higher version, so it doesn't even try to sync
[11:29] <LocutusOfBorg> vorlon, ^^
[11:30] <seb128> LocutusOfBorg, right, that's what I asked/guessed the other day, thanks for confirming
[11:30] <LocutusOfBorg> it finds it here:
[11:30] <LocutusOfBorg>             spphs = self.options.source.archive.getPublishedSources(
[11:30] <LocutusOfBorg> anyway, I don't think anybody is still running warty, and updates to hirsute lol
[11:30] <LocutusOfBorg> :)
[11:31] <seb128> right :-)
[12:10] <chrisccoulson> hi, we'd like the next thunderbird security update for focal to go through proposed first - who is able to publish an update to focal-proposed from https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa ?
[12:15] <apw> chrisccoulson, you want "thunderbird - 1:78.5.0+build3-0ubuntu0.20.04.1" in focal-proposed (with binaries); what about the groovy version
[12:18] <apw> (ahh already there)
[12:21] <chrisccoulson> apw, yeah, just focal. I did groovy as a normal security update because it was released with this version of thunderbird already
[12:21] <apw> chrisccoulson, on its way
[12:22] <chrisccoulson> oSoMoN, is there a bug to track this btw?
[12:22] <chrisccoulson> apw, thanks! :)
[12:28] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [s390x] (bionic-proposed/main) [5.4.0-56.62~18.04.1] (no packageset)
[12:31] <juliank> ugh I want to make autopkgtest surface temporary failures rather than just silently retrying
[12:40] <oSoMoN> chrisccoulson, yes, bug #1895643
[12:40] <oSoMoN> apw, thanks!
[13:46] <cpaelzer> Laney: I have a trigger in the autopkgtest queue "omnidb {"requester": "paelzer", "submit-time": "2020-11-23 14:48:54", "triggers": ["postgresql-13/13.1-1build1", "postgresql-common/223", "omnidb/2.17.0+ds-5build1"]}" - I know it will fail, is there any way I can cancel that "myself"?
[13:47] <cpaelzer> IIRC you can do so, but I wondered if there is a way withotu bothering others - permission-wise at least to be able to cancel my own maybe?
[13:52] <seb128> cpaelzer, he's off this week, maybe try juliank?
[13:53] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (groovy-proposed/multiverse) [6.1.14-2 => 6.1.16-1~ubuntu1.20.10.1] (no packageset)
[13:53] <cpaelzer> thanks seb128
[13:53] <seb128> np!
[13:54] -queuebot:#ubuntu-release- Unapproved: virtualbox (groovy-proposed/multiverse) [6.1.14-dfsg-4 => 6.1.16-dfsg-4~ubuntu1.20.10.1] (ubuntu-cloud)
[13:54] <cpaelzer> plusone: is anyone looking at the autopkgtests of "ubuntu-image" ?
[13:56] <cpaelzer> sil2100: FYI ^^ as you did the last upload and set the unblock in hints
[13:57] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (focal-proposed/multiverse) [6.1.10-1~ubuntu1.20.04.1 => 6.1.16-1~ubuntu1.20.04.1] (no packageset)
[13:57] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (focal-proposed/multiverse) [6.1.10-dfsg-1~ubuntu1.20.04.1 => 6.1.16-dfsg-4ubuntu1.20.04.1] (no packageset)
[13:57] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (focal-proposed/multiverse) [6.1.10-1~ubuntu1.20.04.1 => 6.1.16-1ubuntu1.20.04.1] (no packageset)
[13:57] -queuebot:#ubuntu-release- Unapproved: virtualbox (focal-proposed/multiverse) [6.1.10-dfsg-1~ubuntu1.20.04.1 => 6.1.16-dfsg-4~ubuntu1.20.04.1] (ubuntu-cloud)
[13:58] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (focal-proposed/multiverse) [6.1.10-1~ubuntu1.20.04.1 => 6.1.16-1~ubuntu1.20.04.1] (no packageset)
[13:58] <LocutusOfBorg> please reject virtualbox-guest-additions-iso 6.1.16-1ubuntu1.20.04.1, missing the "~" in versioning (the latest version is good)
[14:10] -queuebot:#ubuntu-release- Unapproved: boinc (groovy-proposed/universe) [7.16.15+dfsg.is.7.16.11+dfsg-1 => 7.16.15+dfsg.is.7.16.11+dfsg-3~ubuntu1.20.10.1] (no packageset)
[14:13] <LocutusOfBorg> please reject the older boinc, sigh (autogenerated control file sucks)
[14:14] -queuebot:#ubuntu-release- Unapproved: boinc (groovy-proposed/universe) [7.16.15+dfsg.is.7.16.11+dfsg-1 => 7.16.15+dfsg.is.7.16.11+dfsg-3~ubuntu1.20.10.1] (no packageset)
[14:17] -queuebot:#ubuntu-release- New: accepted gloo [amd64] (hirsute-proposed) [0.0~git20200918.3dc0328-1]
[14:17] -queuebot:#ubuntu-release- New: accepted gloo [ppc64el] (hirsute-proposed) [0.0~git20200918.3dc0328-1]
[14:17] -queuebot:#ubuntu-release- New: accepted gloo [s390x] (hirsute-proposed) [0.0~git20200918.3dc0328-1]
[14:17] -queuebot:#ubuntu-release- New: accepted python-pyxs [sync] (hirsute-proposed) [0.4.2~git20190115.97f14313-3]
[14:17] -queuebot:#ubuntu-release- New: accepted gloo [arm64] (hirsute-proposed) [0.0~git20200918.3dc0328-1]
[14:17] -queuebot:#ubuntu-release- New: accepted mariadb-10.5 [sync] (hirsute-proposed) [1:10.5.8-3]
[14:17] -queuebot:#ubuntu-release- New: accepted gloo [riscv64] (hirsute-proposed) [0.0~git20200918.3dc0328-1]
[14:27] -queuebot:#ubuntu-release- New binary: python-pyxs [amd64] (hirsute-proposed/universe) [0.4.2~git20190115.97f14313-3] (no packageset)
[14:32] <oSoMoN> apw, chrisccoulson: I almost forgot: the thunderbird focal update that was published to -proposed needs to go together with the enigmail update in ppa:ubuntu-mozilla-security/ppa
[14:33] <oSoMoN> (version 2:2.2.4-0ubuntu0.20.04.1)
[14:33] <oSoMoN> apw, would you mind publishing that one to focal-proposed too?
[14:42] -queuebot:#ubuntu-release- New binary: mariadb-10.5 [s390x] (hirsute-proposed/universe) [1:10.5.8-3] (no packageset)
[14:50] <cpaelzer> seb128: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1905735
[14:51] <seb128> cpaelzer, oh, ups, sorry I just uploaded that, see #ubuntu-devel
[14:52] <cpaelzer> np
[14:52] <seb128> cpaelzer, I also reported  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975910 to ask to the python-debian maintainer if they meant to break the compat or not
[14:54] <cpaelzer> seb128: I gave a non-formal +1 to your MP and linked my PPA which has effectively the smae change
[14:54] <cpaelzer> same
[14:54] <seb128> cpaelzer, sorry for not noticing that you did ping Lukazs there earlier or I would have asked you before chassing that down, I just came from another angle (#ubuntu-devel has details), I was chassing how to fix our canary image build
[14:55] <seb128> cpaelzer, thanks!
[14:55] <cpaelzer> my angle was from things blocking postgres
[14:55] <cpaelzer> sil2100: seb128: once the new ubuntu-image is in hirsute wll one of you retrigger all the currently blocked packages against it?
[14:56] <cpaelzer> a.k.a can I forget about it and it will magically resolve :-)
[14:56] <seb128> cpaelzer, yes
[14:56] <cpaelzer> thanks
[14:56] <seb128> np!
[14:58] <cpaelzer> sil2100: since seb128 raced me for ubuntu-image as an alternative I instead now ping you for https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/394530 (in cae you are in MP review mood)
[14:59] <sil2100> cpaelzer: o/
[15:01] -queuebot:#ubuntu-release- New binary: mariadb-10.5 [ppc64el] (hirsute-proposed/universe) [1:10.5.8-3] (no packageset)
[15:05] <juliank> cpaelzer: I can have a look
[15:05] <cpaelzer> juliank: for the cancelling of omnidb? thanks , but be careful - there is an old one (to be cancelled) and a new one (should stay)
[15:06] <cpaelzer> this is why I copied the full line above
[15:06] <juliank> cpaelzer: yup, i saw
[15:06] <juliank> cpaelzer: done
[15:06] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (focal-proposed/main) [1:3.36.4-0ubuntu2 => 1:3.36.5-0ubuntu1] (ubuntu-desktop)
[15:07] <cpaelzer> thanks juliank
[15:07] <juliank> I feel like I should give them nice uuids so they're a bit nicer to cancel by uuid
[15:08]  * cpaelzer votes for everyone being allowed to kill "his own" jobs if that is doable somehow
[15:09] -queuebot:#ubuntu-release- New binary: mariadb-10.5 [amd64] (hirsute-proposed/universe) [1:10.5.8-3] (no packageset)
[15:12] <juliank> cpaelzer: hmm should be
[15:13] <juliank> cpaelzer: Just need to add a delete=1 parameter to request.cgi and make it delete entries instead of adding them
[15:14] -queuebot:#ubuntu-release- New: accepted mariadb-10.5 [amd64] (hirsute-proposed) [1:10.5.8-3]
[15:14] -queuebot:#ubuntu-release- New: accepted mariadb-10.5 [s390x] (hirsute-proposed) [1:10.5.8-3]
[15:14] -queuebot:#ubuntu-release- New: accepted mariadb-10.5 [ppc64el] (hirsute-proposed) [1:10.5.8-3]
[15:14] -queuebot:#ubuntu-release- New: accepted python-pyxs [amd64] (hirsute-proposed) [0.4.2~git20190115.97f14313-3]
[15:18] <cpaelzer> juliank: I saw you issuing retries for mpi4py/openmpi - are you looking deeper into that?
[15:18] <juliank> cpaelzer: just retrying what doko told me to do, all python stuff with all-proposed
[15:18] <juliank> :D
[15:19] <juliank> cpaelzer: I'm now writing your self-delete request
[15:19] <cpaelzer> ok, then I'll look at MPI (but probably tomorrow morning)
[15:20] <doko> britney not running currently?
[15:23] -queuebot:#ubuntu-release- Unapproved: linux-firmware (focal-proposed/main) [1.187.4 => 1.187.5] (core, kernel)
[15:38] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (focal-proposed) [1.187.5]
[15:46] <juliank> cpaelzer: I now added a &delete=1 parameter support which you can use to delete your own requests, give it some testing
[15:46] <juliank> :)
[15:47] <juliank> cpaelzer: I accidentally pushed it to the main branch instead of my personal one
[15:48] <juliank> Laney: FYI: I now added a &delete=1 parameter to request.cgi for deleting a request you made (just append to a previous request), I accidentally pushed this to main branch, so it's in production directly and no merge :/
[15:48] <cpaelzer> juliank: does this mean it is active right away - yeah will give it some testing
[15:48] <juliank> cpaelzer: Yeah, you take any request.cgi url you requested with, append &delete=1 and it will find and delete it
[15:51] <juliank> I'm also wondering if I should delete duplicate requests every 15 minutes or so
[15:51] <juliank> via cron job
[15:52] <juliank> Filtering at request submission time is too expensive
[15:52] <juliank> well not really super expensive but still
[15:53] <juliank> You have to iterate over the entire queue to find duplicates, like the delete code does
[16:00] <juliank> bad bot:  "GET /request.cgi?arch=arm64&package=backport-iwlwifi-dkms&release=bionic&trigger=linux-meta-aws-5.4%2F5.4.0.1028.13 HTTP/1.1" 403 3789 "-" "Mozilla/5.0 (compatible; SemrushBot/7~bl; +http://www.semrush.com/bot.html)"
[16:01] <juliank> why did we give it 403 for robots.txt?
[16:13] <juliank> This test keeps coming back in duplicates baconqrcode {'triggers': ['baconqrcode/2.0.3-1']}
[16:13] <juliank> I've deleted so many of them today
[16:14] <LocutusOfBorg> juliank, isn't pushing directly to production something that should be done on friday PM? :) good job anyway, I'll test it soon
[16:15] <juliank> LocutusOfBorg: I think it should have gotten some review, it's also fairly taxing on the system compared to submitting a test
[16:15] <juliank> because it iterates over the entire queue to find items to delete
[16:18] <LocutusOfBorg> I was joking, please don't take me seriously :)
[16:18] <LocutusOfBorg> can I delete only my jobs, or all?
[16:19] <juliank> LocutusOfBorg: only your own
[16:19] <LocutusOfBorg> nice thanks
[16:20] <LocutusOfBorg> mmmm juliank
[16:20] <LocutusOfBorg> I had to xmlschema requests
[16:20] <LocutusOfBorg> python-xmlschema {"all-proposed": "1", "requester": "costamagnagianfranco", "submit-time": "2020-11-26 14:38:59", "triggers": ["python3-defaults/3.9.0-3"]}
[16:20] <LocutusOfBorg> python-xmlschema {"all-proposed": "1", "requester": "costamagnagianfranco", "submit-time": "2020-11-26 14:39:14", "triggers": ["elementpath/2.0.4-1"]}
[16:20] <LocutusOfBorg> I did this: https://autopkgtest.ubuntu.com/request.cgi?release=hirsute&arch=ppc64el&package=python-xmlschema&trigger=python3-defaults/3.9.0-3&delete=1
[16:20] <LocutusOfBorg> and it said "deleted 4 requests"
[16:20] <LocutusOfBorg> mmm
[16:21] <juliank> hmm
[16:21] <juliank> LocutusOfBorg: are you sure you had no earlier requests?
[16:21] <LocutusOfBorg> and looks like another python-xmlschema test that was running got deleted too
[16:21] <LocutusOfBorg> yes juliank I did use "find" on the "running" webpage
[16:22] <juliank> hmm
[16:22] <juliank> but that one might be inaccurate
[16:23] <LocutusOfBorg> in any case, the test that was scheduled by britney seems to have been lost
[16:23] <LocutusOfBorg> and meh, it deleted two different tests? I asked to remove the one against python3-defaults, not the one against elementpath
[16:24]  * LocutusOfBorg reschedules it
[16:24] <juliank> LocutusOfBorg: there are 4 tests queued
[16:24] <juliank> 2020-11-26 16:24:37,864 - queue item: b'python-xmlschema {"requester": "costamagnagianfranco", "submit-time": "2020-11-26 16:22:10", "triggers": ["python3-defaults/3.9.0-3"]}' (would delete)
[16:24] <juliank> 2020-11-26 16:24:37,865 - queue item: b'python-xmlschema {"requester": "costamagnagianfranco", "submit-time": "2020-11-26 16:22:18", "triggers": ["elementpath/2.0.4-1"]}' (would delete)
[16:24] <juliank> 2020-11-26 16:24:37,866 - queue item: b'python-xmlschema {"requester": "costamagnagianfranco", "submit-time": "2020-11-26 16:22:22", "triggers": ["python3-defaults/3.9.0-3"]}' (would delete)
[16:24] <juliank> 2020-11-26 16:24:37,867 - queue item: b'python-xmlschema {"requester": "costamagnagianfranco", "submit-time": "2020-11-26 16:24:07", "triggers": ["python-xmlschema/1.3.1-1"]}' (would delete)
[16:25] <LocutusOfBorg> hey, such are the newly scheduled tests
[16:25] <LocutusOfBorg> let me try to delete only the python3-defaults ones, that should be two of them
[16:25] <juliank> LocutusOfBorg: hmm, now I deleted them, so you're right
[16:25] <juliank> this is weird
[16:26] <LocutusOfBorg> ok this is why it didn't delete them :D
[16:26] <juliank> LocutusOfBorg: I typoed
[16:26] <LocutusOfBorg> can I see the code?
[16:26] <juliank> LocutusOfBorg: if ... and _params == params:
[16:26] <juliank> Lum
[16:26] <LocutusOfBorg> found it
[16:26] <juliank> LocutusOfBorg: if ... and params == params:
[16:26] <juliank> LocutusOfBorg: should be if ... and this_params == params:
[16:28] <LocutusOfBorg> LOL
[16:28] <LocutusOfBorg> true!
[16:28] <juliank> let me readd your entries
[16:28] <LocutusOfBorg> params looks really equal to params :D
[16:30] <LocutusOfBorg> so the query should be really the same, we can't swap parameters and delete them anyway
[16:30] <juliank> Now it works
[16:31] <juliank> sorry
[16:31] <LocutusOfBorg> no problem I'm happy to beta-test it :D
[16:31] <juliank> I can also sneakily inject test requests with requesters :D
[16:32] <LocutusOfBorg> LOL
[16:34] <LocutusOfBorg> ok I like it now, nice feature!
[16:35] <LocutusOfBorg> juliank, feature request: is it possible to add something like &trigger=itself, to trigger against itself and see if it has regressed in release?
[16:35] <LocutusOfBorg> I think it would be a nice feature to have
[16:35] <juliank> I just retrigger against hello :D
[16:35] <juliank> but this is not what we want people to do anyway
[16:36] <juliank> the goal being to have automatic continuous baseline retesting eliminate manual rerunning against release pocket
[16:36] <LocutusOfBorg> I think, britney itself when founds a regression should trigger against release, and see automatically ignore if the regression is in release pocket
[16:36] <LocutusOfBorg> like debian does, nice
[16:37] <LocutusOfBorg> and report them somewhere so they can be easily hinted
[16:39] -queuebot:#ubuntu-release- Unapproved: linux-firmware (groovy-proposed/main) [1.190.1 => 1.190.2] (core, kernel)
[16:41] -queuebot:#ubuntu-release- Unapproved: gnome-desktop3 (focal-proposed/main) [3.36.3.1-0ubuntu1 => 3.36.8-0ubuntu1] (ubuntu-desktop)
[16:46] <juliank> LocutusOfBorg: if they were retried with migration-reference/0 britney will see that next time, and no hint is needed
[16:46] <juliank> Like that's how baseline retesting works
[16:46] <LocutusOfBorg> even better
[16:47] -queuebot:#ubuntu-release- Unapproved: linux-firmware (focal-proposed/main) [1.187.5 => 1.187.6] (core, kernel)
[16:48] <rbalint> juliank, how about doing that with hello? :-)
[16:48] <juliank> rbalint: then everyone could do it themselves
[16:49] <rbalint> juliank, only core devs afaik
[16:49] <juliank> we do not want to give people the ability to hint themselves
[16:49] <juliank> I don't know why, given that we want to do that automatically, but that's what we want
[16:49] <rbalint> juliank, it is not a hint, it works only if release version does fail with hello
[16:50] <juliank> this is a force-reset-test hint
[16:50] <juliank> well, equivalent to it
[16:50] <rbalint> juliank, can you hint something that passes with hello this way
[16:50] <rbalint> ?
[16:50] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (focal-proposed) [1.187.6]
[16:50] <juliank> i don't understand the question
[16:51] <juliank> If it fails in the release pocket, that means you want it to migrate
[16:51] <juliank> If it passes in the release pocket, you don't need a hint
[16:51] <rbalint> juliank, yes you need if the package fails in proposed for an unimportant reason
[16:52] <juliank> Yes, but that'S not relevant to the topic
[16:52] <rbalint> juliank, sorry, i missed the topic then
[16:52] <juliank> for the failure in release pocket you want to do a force-reset-test of that version
[16:53] <juliank> such that the new version can migrate
[16:53] <juliank> If you trigger the package with migration-reference/0 trigger, that's the same result
[16:53] <rbalint> juliank, i just wanted to show that treating hello as baseline is less effective than letting people to add hints
[16:54] <juliank> Unless it does fail, then it's the same
[16:54] <rbalint> juliank, otoh i'm not fully recommending treating hello as such
[16:54] <juliank> We never would
[16:54] <juliank> I wanted to allow you to submit  migration-reference/0 tests, but this was NAKed
[16:54] <rbalint> juliank, afaik in Debian rc bugs are filed for flaky tests because they mess up the baseline testing
[17:06] <rbalint> juliank, imo the current practice of ubuntu-release approving the hints is ok, but the approval needs to be timely to not hold back progress on plusone
[17:08] <juliank> rbalint: well yes, that'S a bit of a pain
[17:09] <rbalint> juliank, what part?
[17:09] <juliank> I want to test out if migration-reference/0 works with current britney
[17:09] <juliank> rbalint: the timely part
[17:09] <rbalint> juliank, is is just a matter of practice
[17:10] <rbalint> and having an established call sign, for example ubuntu-release like ubuntu-archiv_e
[17:13] <LocutusOfBorg> juliank, it would be also nice to detect all the "will make the package foo uninstallable" and suggest you the "rebuild command" :)
[17:15] -queuebot:#ubuntu-release- Unapproved: accepted libglvnd [source] (focal-proposed) [1.3.2-1~ubuntu0.20.04.1]
[17:26] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [amd64] (bionic-proposed) [5.4.0-56.62~18.04.1]
[17:26] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [ppc64el] (bionic-proposed) [5.4.0-56.62~18.04.1]
[17:26] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [arm64] (bionic-proposed) [5.4.0-56.62~18.04.1]
[17:26] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [s390x] (bionic-proposed) [5.4.0-56.62~18.04.1]
[17:26] -queuebot:#ubuntu-release- New binary: rust-deflate [ppc64el] (hirsute-proposed/universe) [0.7.20-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: rust-deflate [s390x] (hirsute-proposed/universe) [0.7.20-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: kineticstools [ppc64el] (hirsute-proposed/universe) [0.6.1+git20200729.e3723e0+dfsg-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: rust-deflate [amd64] (hirsute-proposed/universe) [0.7.20-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: kineticstools [amd64] (hirsute-proposed/universe) [0.6.1+git20200729.e3723e0+dfsg-1] (no packageset)
[17:30] <tjaalton> sil2100: \o/
[17:43] -queuebot:#ubuntu-release- New binary: rust-deflate [riscv64] (hirsute-proposed/universe) [0.7.20-1] (no packageset)
[17:47] -queuebot:#ubuntu-release- New binary: kineticstools [arm64] (hirsute-proposed/universe) [0.6.1+git20200729.e3723e0+dfsg-1] (no packageset)
[17:47] -queuebot:#ubuntu-release- New binary: kineticstools [armhf] (hirsute-proposed/universe) [0.6.1+git20200729.e3723e0+dfsg-1] (no packageset)
[17:47] -queuebot:#ubuntu-release- New binary: rust-deflate [armhf] (hirsute-proposed/universe) [0.7.20-1] (no packageset)
[17:49] -queuebot:#ubuntu-release- New binary: rust-deflate [arm64] (hirsute-proposed/universe) [0.7.20-1] (no packageset)
[18:00] <blackboxsw> bdmurray: yes, definitely will verify that first. wow stale. completely slipped the radar on old update-notifier SRU.
[18:05] -queuebot:#ubuntu-release- New: accepted kineticstools [amd64] (hirsute-proposed) [0.6.1+git20200729.e3723e0+dfsg-1]
[18:05] -queuebot:#ubuntu-release- New: accepted kineticstools [armhf] (hirsute-proposed) [0.6.1+git20200729.e3723e0+dfsg-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-deflate [amd64] (hirsute-proposed) [0.7.20-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-deflate [armhf] (hirsute-proposed) [0.7.20-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-deflate [riscv64] (hirsute-proposed) [0.7.20-1]
[18:05] -queuebot:#ubuntu-release- New: accepted kineticstools [arm64] (hirsute-proposed) [0.6.1+git20200729.e3723e0+dfsg-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-deflate [arm64] (hirsute-proposed) [0.7.20-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-deflate [s390x] (hirsute-proposed) [0.7.20-1]
[18:05] -queuebot:#ubuntu-release- New: accepted kineticstools [ppc64el] (hirsute-proposed) [0.6.1+git20200729.e3723e0+dfsg-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-deflate [ppc64el] (hirsute-proposed) [0.7.20-1]
[18:16] -queuebot:#ubuntu-release- New binary: pytorch [ppc64el] (hirsute-proposed/universe) [1.7.0-2] (no packageset)
[18:23] <kanashiro> ubuntu-archive: ruby-defaults/1:2.7+2 was deleted from hirsute-proposed some time ago but now I need it back. It can't be synced from Debian using syncpackage (I got it rejected), could someone please help me to get it re-published?
[18:32] <doko> kanashiro: that would connect the ruby transition with the perl and python ones ...
[18:33] <kanashiro> doko: there is no new ruby version, just rubygems was extracted to another source package. The default would still be 2.7
[18:33] <LocutusOfBorg> doko, I copied it back, I think
[18:34] <LocutusOfBorg> why do you think it entangles?
[18:34] <doko> ahh, ok
[18:34] <LocutusOfBorg> anyway, its now back in proposed pocket
[18:34] <LocutusOfBorg> (pending publisher run)
[18:35] <kanashiro> LocutusOfBorg: thanks!
[18:35] <LocutusOfBorg> you are welcome
[18:35] <LocutusOfBorg> I need that sync too, to fix ruby-webpacker/4.2.2-5 autopkgtests
[18:35] <LocutusOfBorg> and lots of uninstallabilities in proposed
[18:36] <kanashiro> it will solve many FTBFS and test failures
[18:36] <LocutusOfBorg> sure, we need to trigger something
[18:36] <kanashiro> I am tracking the needed triggers
[18:36] <kanashiro> today and tomorrow I am working on my +1 maint shift :)
[18:38] <LocutusOfBorg> do we have a list of stuff that needs a retry? mitya57 ? or should we just try it all?
[18:38] <LocutusOfBorg> I mean, stuff that has been syncd/uploaded after 2020-10-30 13:10:09 CET
[18:39] <mitya57> LocutusOfBorg: I don't have such a list, that's a question to kanashiro
[18:40] <LocutusOfBorg> I was just highlithing to avoid double efforts
[18:41] <kanashiro> I am building a list here based on the excuses page, packages needing to be rebuilt and tests needing triggers
[18:41] <LocutusOfBorg> please ping once you have it
[18:42] <LocutusOfBorg> unless you are MOTU or core-dev already... I forget about such things too easily
[18:43] <LocutusOfBorg> oh yes you are, so nevermind
[18:44] <kanashiro> np, I am already a core-dev I can handle it
[18:45] <LocutusOfBorg> I remember advocating you, but I missed your status change, congrats :)
[18:45] -queuebot:#ubuntu-release- New binary: gcc-mingw-w64 [s390x] (hirsute-proposed/universe) [24] (i386-whitelist, kubuntu)
[18:47] <kanashiro> thanks :) (for advocating me and the congratulations)
[18:47] <LocutusOfBorg> doko, are you available to remove pyxs and move python-pyxs to main? the python3-pyxs is already in main, but the source package isn't...
[18:47] <LocutusOfBorg> the source is the same ^^
[19:05] -queuebot:#ubuntu-release- New: accepted gcc-mingw-w64 [s390x] (hirsute-proposed) [24]
[19:05] -queuebot:#ubuntu-release- New: accepted pytorch [ppc64el] (hirsute-proposed) [1.7.0-2]
[20:52] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [amd64] (focal-proposed/main) [5.8.0-31.33~20.04.1] (no packageset)
[20:52] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [s390x] (focal-proposed/main) [5.8.0-31.33~20.04.1] (no packageset)
[20:52] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [ppc64el] (focal-proposed/main) [5.8.0-31.33~20.04.1] (no packageset)
[20:52] -queuebot:#ubuntu-release- New binary: ruby-elasticsearch-rails [amd64] (hirsute-proposed/universe) [7.1.1-1] (no packageset)
[20:53] -queuebot:#ubuntu-release- New binary: pytorch-audio [ppc64el] (hirsute-proposed/universe) [0.7.0-1] (no packageset)
[20:53] -queuebot:#ubuntu-release- New binary: pytorch-vision [ppc64el] (hirsute-proposed/universe) [0.8.1-1] (no packageset)
[20:53] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [arm64] (focal-proposed/main) [5.8.0-31.33~20.04.1] (no packageset)