[08:38] -queuebot:#ubuntu-release- New: accepted oem-somerville-maester-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[09:26] -queuebot:#ubuntu-release- Packageset: Added gcc-12 to i386-whitelist in jammy
[09:26] -queuebot:#ubuntu-release- Packageset: Added pytest-runner to i386-whitelist in jammy
[09:27] -queuebot:#ubuntu-release- Packageset: Added python-pkgconfig to i386-whitelist in jammy
[11:22] -queuebot:#ubuntu-release- New binary: yubikey-manager-qt [amd64] (jammy-proposed/universe) [1.2.4-1] (no packageset)
[11:38] -queuebot:#ubuntu-release- New binary: yubikey-manager-qt [ppc64el] (jammy-proposed/universe) [1.2.4-1] (no packageset)
[11:49] -queuebot:#ubuntu-release- New binary: yubikey-manager-qt [arm64] (jammy-proposed/universe) [1.2.4-1] (no packageset)
[11:49] -queuebot:#ubuntu-release- New binary: yubikey-manager-qt [armhf] (jammy-proposed/universe) [1.2.4-1] (no packageset)
[12:34] -queuebot:#ubuntu-release- New binary: yubikey-manager-qt [s390x] (jammy-proposed/universe) [1.2.4-1] (no packageset)
[13:32] <xnox> sil2100:  are you around for simple SRU actions? (1 reject, and 2 to consider for sru-release)
[13:33] <xnox> https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=curl the second one (older one), which was uploaded at 17:.. GMT needs to be rejected, it FTBFS and got fixed up by the new one in the queue.
[13:34] <xnox> and then from https://people.canonical.com/~ubuntu-archive/pending-sru.html dwarves-dfsg and openssl from me are ready to release.
[14:03] <tjaalton> xnox: looking
[14:03] -queuebot:#ubuntu-release- Unapproved: rejected curl [source] (focal-proposed) [7.68.0-1ubuntu2.8]
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted wget [source] (focal-proposed) [1.20.3-1ubuntu2]
[14:24] -queuebot:#ubuntu-release- Unapproved: accepted curl [source] (focal-proposed) [7.68.0-1ubuntu2.8]
[14:32] <sil2100> xnox: o/
[14:32] <sil2100> xnox: I'll do SRU releases in a bit, didn't go through it yet - curl and wget I just reviewed for focal
[14:43] <tjaalton> I released openssl and dwarves-dfsg
[14:44] <xnox> tjaalton:  thank you!
[14:44] <xnox> sil2100:  thank you!
[14:52] <sil2100> yaay
[14:52] <sil2100> yw!
[14:59] -queuebot:#ubuntu-release- New: accepted oem-stella.cmit-rattata-meta [sync] (focal-proposed) [20.04~ubuntu1]
[15:04] -queuebot:#ubuntu-release- New binary: oem-stella.cmit-rattata-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)
[15:10] -queuebot:#ubuntu-release- New: accepted oem-stella.cmit-rattata-meta [amd64] (focal-proposed) [20.04~ubuntu1]
[16:53] <juliank> We are now back at the normal 40 ppc64el autopkgtest workers from the temporary raise to 60
[16:55] <vorlon> tumbleweed: tracker> reminder that we generally don't need to add force-badtest hints manually now, as opposed to doing baseline retests with trigger=migration-reference/0 and letting britney figure it out
[16:58] <tumbleweed> ah, is that how we got the list cut down so much
[17:01] <vorlon> yes :)
[17:01] <vorlon> which improves britney runtime as well \o/
[17:01] <tumbleweed> triggered migration reference tests for it
[17:01] <vorlon> I did also ;)
[17:05] <laney> Wonder how we can build a view of the baseline status. I'd love to know if it's getting better or worse over time.
[17:05] <laney> Guess that relies on continuous retesting to have the data
[17:10] <juliank> laney: well, we can tag baseline tests
[17:11] <juliank> laney: then we can do rolling 30 day average over baseline tests
[17:12] <vorlon> I don't think we want to measure percent of baseline tests failed in the past 30 days
[17:12] <vorlon> I think we want to measure percent of all baseline tests that are pass/fail
[17:12] <juliank> hmm
[17:12] <vorlon> because the rate at which we test can vary
[17:12] <juliank> true
[17:13] <juliank> but I guess that's a lot harder
[17:13] <juliank> Need to add an sqlite query and then send data to influxdb
[17:14] <juliank> might want to tag baseline tests in the dtabase then, to avoid having to use LIKE '%migration-reference/0%' to find them slowly :D
[17:15] <juliank> vorlon: Regarding baseline expiry, I understand not wanting to fight for resources, but on the other hand I think it makes the results more consistent if we ensure that we only consider baselines that are of certain recentness
[17:15] <juliank> Also, we can abort the normal baseline retest once we issue an expiry based once
[17:15] <juliank> such that effectively, things only move up in the queue
[17:17] <juliank> It means packages that get triggered more often might get tested more often, as they'd jump ahead of the retest queue if needed
[17:19] <juliank> The odd thing about baseline retesting is the cron job needs to run from the web worker right now
[17:19] <juliank> as we need the database to figure out which packages we have tests for :)
[17:19] <juliank> vorlon: Oh, and I guess setting an expiry can be useful for stable releases, but also weird
[17:20] <vorlon> juliank: should be able to do = 'migration-reference/0' instead of a LIKE that misses the index :)
[17:21] <vorlon> so yeah, we could certainly have a britney-triggered baseline retest cancel the cronned one
[17:21] <juliank> vorlon: So we have triggers as their own field, but not an index
[17:21] <vorlon> I just don't think it's worth the added complexity
[17:21] <vorlon> juliank: "not an index" is solved easily enough :)
[17:22] <juliank> vorlon: it's a bit problematic, as that index would be large, and we offer the file for download
[17:22] <juliank> indexing a bool field would be smaller I suppose
[17:23] <juliank> We could delete indexes and vaccuum the published databases too
[17:23] <juliank> it would save space
[17:23] <juliank> I vaccuumed the main db on one worker so it's now 1.8GB while the other worker has 2.2GB
[17:23] <juliank> :D
[17:24] <juliank> (unfortunately it wrote all that to the wal journal, so just consumed 2GB more; that's why I did not do the other)
[17:24] <juliank> (after removing groovy that was)
[17:25] <juliank> the baseline cronjob is a bit hard to write if we want to do it nicely
[17:26] <juliank> the easy way is to just queue all tests once the queues are empty, try that hourly or so
[17:26] <juliank> but rabbitmq then starts getting funky and lies to clients about queue contents while that's running
[17:26] <juliank> so optimally, you'd like rate limit the queueing
[17:26] <juliank> hmm I can just sleep in the cron job
[17:27] <tumbleweed> can you limit the quantity of items queued to avoid flooding the queues?
[17:28] <juliank> I can keep a log of what tests are pending and then check them off once they are done
[17:28] <juliank> and then I can issue in small batches every couple minutes
[17:28] <juliank> but it's harder vs just filling the queue when it's empty
[17:28] <tumbleweed> yeah
[17:29] <juliank> what does not work is filling up the queue with remaining items so it always has a fixed size, as rabbitmq sometimes lies, as mentioned
[17:29] <laney> did you discard the idea of using priorities?
[17:30] <juliank> laney: no, this is just a question of how to queue the tests without borking rabbitmq
[17:30] <tumbleweed> does it actually bork, or just give an incomplete picture?
[17:30] <juliank> laney: because if you submit too many items too fast it will start acting up when other clients query the queues
[17:31] <juliank> laney: it gives an incomplete picture, yes
[17:31] <laney> if you use another queue?
[17:31] <laney> normal / upstream / huge / baseline
[17:31] <juliank> I have not checked actually
[17:31] <juliank> But what this means is I can't check the queeu contents and then fill it up to a 100 tests or so
[17:32] <juliank> Maybe if I add caching
[17:32] <juliank> because if we have like a constant low number of tests in that queeu, we don't need to change anything else like amqp-cache and web frontend display
[17:33] <juliank> we'd have to exclude those queues from the web frontend if we had 20k tests in them every week
[17:33] <laney> yeah I'd not really expected to see those, at least not the queued ones (running ones, arguably yes you should)
[17:34] <tumbleweed> it would be useful to see the queues for manual tasks
[17:34] <tumbleweed> often several people re-test the same package
[17:34] <juliank> manual baseline retests land on the normal queue though, not the automatic baseline retest queue
[17:35] <juliank> most likely :D
[17:35] <tumbleweed> yeah, that works
[17:40] <juliank> I guess we can just dump pending tests in a/the database
[17:40] <juliank> then we can look at which tests we know of as pending, and check for new results like britney does
[17:41] <juliank> and do a continous-length baseline retest queue that way
[17:42] <juliank> with the simple approach of "dump all when queue is empty" we end up with weird behavior if the process fails during queueing
[17:43]  * juliank wants to build robust software
[17:43] <laney> start by HAing the rabbitmq then :-)
[17:45] <juliank> laney: ah people say smaller queue lengths are more reliable anyway
[17:46] <tumbleweed> my experience of HA rabbit hasn't been amazing
[17:46] <juliank> laney: but yeah, rabbitmq should maybe be a cluster of two
[17:46] <juliank> tumbleweed: my experience of normal rabbit has not been amazing eihter
[17:46] <juliank> tumbleweed: thing just grows CPU usage over time until it eventually locks up somewhat and needs to be restarted
[17:46] <tumbleweed> at least I haven't run into that
[17:47] <laney> it OOMs from time to time as well, kind of annoying
[17:47] <laney> we had to enable all the disk persistence otherwise queues were getting dumped
[17:47] <juliank> it's fun
[17:48] <juliank> so my understanding of people who know more about rabbitmq is that it's best if we keep the queues small rather than have potentially all tests queued at the same time
[17:49] <juliank> > In RabbitMQ 3.6 and larger, a feature called lazy queues was added. Lazy queues are queues where the messages are automatically stored to disk. Messages are only loaded into memory when they are needed.
[17:49] <juliank> wonder if we use those
[17:49] <juliank> would avoid the OOMs, one would assume
[17:50] <juliank> huge queue might benefit from that at the very least
[17:51] -queuebot:#ubuntu-release- New binary: yubikey-manager-qt [riscv64] (jammy-proposed/universe) [1.2.4-1] (no packageset)
[17:51] <juliank> rabbitmqctl set_policy Lazy "huge" '{"queue-mode":"lazy"}' --apply-to queues
[17:52] <juliank> ugh but also it does not make too much sense because we read the entire queues all the time from the web frontends
[17:57] <cjwatson> juliank: at some point a while back I worked out that this was a kernel bug
[17:57] <cjwatson> rabbitmq itself had reasonable memory use but the kernel was fragmenting itself to death, IIRC
[18:03] -queuebot:#ubuntu-release- New: accepted ksyntax-highlighting [amd64] (jammy-proposed) [5.87.0-0ubuntu1]
[18:03] -queuebot:#ubuntu-release- New: accepted ksyntax-highlighting [armhf] (jammy-proposed) [5.87.0-0ubuntu1]
[18:03] -queuebot:#ubuntu-release- New: accepted ksyntax-highlighting [riscv64] (jammy-proposed) [5.87.0-0ubuntu1]
[18:03] -queuebot:#ubuntu-release- New: accepted ksyntax-highlighting [arm64] (jammy-proposed) [5.87.0-0ubuntu1]
[18:03] -queuebot:#ubuntu-release- New: accepted ksyntax-highlighting [s390x] (jammy-proposed) [5.87.0-0ubuntu1]
[18:03] -queuebot:#ubuntu-release- New: accepted ksyntax-highlighting [ppc64el] (jammy-proposed) [5.87.0-0ubuntu1]
[18:11] <juliank> cjwatson: whoa
[18:21] <cjwatson> Not sure I ever tracked it down all the way though, because at the time we were running rabbitmq on an old Ubuntu release and it made more sense to upgrade first
[18:21] <cjwatson> Seemed like unreclaimable slabs IIRC
[18:22] <cjwatson> juliank: Ah right, if memory serves we redeployed rabbitmq-server on focal (previously trusty) and it stopped being a problem
[18:23] <cjwatson> juliank: https://portal.admin.canonical.com/C128584/
[18:23] <cjwatson> What series are you running it on at the moment?
[19:30] <vorlon> doko: gcc-arm-none-eabi-source is in the NBS report, but libstdc++-arm-none-eabi build-depends on it, and this doesn't seem to be a false-positive?
[19:38] -queuebot:#ubuntu-release- New: accepted glance-tempest-plugin [amd64] (jammy-proposed) [0.2.0-2]
[19:38] -queuebot:#ubuntu-release- New: accepted trove-tempest-plugin [amd64] (jammy-proposed) [1.3.0-2]
[19:38] -queuebot:#ubuntu-release- New: accepted yubikey-manager-qt [arm64] (jammy-proposed) [1.2.4-1]
[19:38] -queuebot:#ubuntu-release- New: accepted yubikey-manager-qt [ppc64el] (jammy-proposed) [1.2.4-1]
[19:38] -queuebot:#ubuntu-release- New: accepted yubikey-manager-qt [s390x] (jammy-proposed) [1.2.4-1]
[19:38] <vorlon> cjwatson: autopkgtest rabbit is currently on focal also
[19:38] -queuebot:#ubuntu-release- New: accepted python-elgato-streamdeck [amd64] (jammy-proposed) [0.8.5+ds-2]
[19:38] -queuebot:#ubuntu-release- New: accepted yubikey-manager-qt [armhf] (jammy-proposed) [1.2.4-1]
[19:38] -queuebot:#ubuntu-release- New: accepted yubikey-manager-qt [amd64] (jammy-proposed) [1.2.4-1]
[19:38] -queuebot:#ubuntu-release- New: accepted yubikey-manager-qt [riscv64] (jammy-proposed) [1.2.4-1]
[19:38] -queuebot:#ubuntu-release- New: accepted python-promise [amd64] (jammy-proposed) [2.3.0-1]
[21:43] <juliank> vorlon: i wish the workers had access to the results database, then we could have flags on tests and the workers could just ack and ignore baseline retests if we already had one in the past 7 days :D
[21:44] <juliank> no need to play with queues and all
[21:44] <juliank> just add {"only_if_not_run_since": "2021-11-08 21:44"}
[21:47] <juliank> I sometimes wonder if britney should submit the baseline retesting tests. If it hasn't seen a baseline reference test in 7 days -> submit a new one; for each package in the archivee
[21:47] <juliank> britney has all the logic in there to deal with de-duplicating requests and stuff already
[21:48] <juliank> (and it only has one instance, when running on autopkgtest, you always need to coordinate because everything exists twice :D)
[21:49] <juliank> but oh well, the web nodes have elected a leader, so everything ,ight be alright
[21:56] <vorlon> juliank: we shouldn't add more work to the inner loop of proposed-migration
[21:56] <juliank> vorlon: yeah I understand that
[21:57] <juliank> so what I can do if I want to be leaderless
[21:58] <juliank> is submit all test requests to a new queue dedup-<queue name>
[21:58] <juliank> which then is processed by only one web node, exclusively
[21:58] <juliank> and then that really schedules tests and writes pending tests to a json like britney and ignores new ones
[21:59] <juliank> but this still fails if that web unit goes down
[21:59] <juliank> wish we had a distributed sql
[22:00] <juliank> there is another weird hack for a distributed small database
[22:00] <juliank> dump it to json
[22:00] <juliank> define an exclusive consumer queue in rabbitmq
[22:00] <juliank> read item in your exclusive consumer, add new request, write item back, close consumer
[22:01] <juliank> basically it's a single distributed locked json file :D
[22:28] <bdmurray> vorlon: Why is app-install-data-partner still in main?
[22:30] <vorlon> bdmurray: well I haven't actually announced partner deprecation publicly yet, have I :)
[22:30] <vorlon> bdmurray: seems it should be dropped entirely
[22:32] <vorlon> (and unseeded)
[22:35] <juliank> oh silly me should just write the baseline retester to always request tests for packages who have not run migration-reference tests in 7 days
[22:35] <juliank> (it then deduplicates if the test is recorded as pending)
[22:36] <juliank> And just manually hack in which web worker issues those tests by virtue of having that pending tests json file exist
[22:53] <juliank> vorlon: laney I believe consumer priorities are the answer to make sure the standard queues get processed first: https://www.rabbitmq.com/consumer-priority.html
[22:56] <juliank> I'll ask in the ML to be sure
[22:58] <juliank> (https://groups.google.com/u/1/g/rabbitmq-users/c/ZRI11erf4zk)
[23:20] -queuebot:#ubuntu-release- New binary: libnetconf2 [amd64] (jammy-proposed/universe) [2.0.24-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: proglog [amd64] (jammy-proposed/none) [0.1.9-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: critnib [amd64] (jammy-proposed/universe) [1.0-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: tml [amd64] (jammy-proposed/universe) [0.4.0-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: ntfs2btrfs [amd64] (jammy-proposed/universe) [20210523-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: zydis [amd64] (jammy-proposed/universe) [3.2.1-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: snowflake [amd64] (jammy-proposed/universe) [1.1.0-1] (no packageset)
[23:22] <tumbleweed> hrm, are DNS queries blocked from autopkgtests? Re aiodns failing
[23:22] -queuebot:#ubuntu-release- New binary: bcm2835 [arm64] (jammy-proposed/universe) [1.68+ds-1] (no packageset)
[23:23] <juliank> tumbleweed: it worked fine at 18:54:19 UTC
[23:24] -queuebot:#ubuntu-release- New binary: bcm2835 [amd64] (jammy-proposed/universe) [1.68+ds-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: critnib [arm64] (jammy-proposed/universe) [1.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: zydis [arm64] (jammy-proposed/universe) [3.2.1-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: bcm2835 [armhf] (jammy-proposed/universe) [1.68+ds-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: libnetconf2 [ppc64el] (jammy-proposed/universe) [2.0.24-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: libnetconf2 [armhf] (jammy-proposed/universe) [2.0.24-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: sysrepo [arm64] (jammy-proposed/universe) [2.0.53-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: zydis [armhf] (jammy-proposed/universe) [3.2.1-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: ntfs2btrfs [ppc64el] (jammy-proposed/universe) [20210523-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: sysrepo [ppc64el] (jammy-proposed/universe) [2.0.53-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: libnetconf2 [arm64] (jammy-proposed/universe) [2.0.24-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: rhonabwy [armhf] (jammy-proposed/universe) [1.1.1-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: bcm2835 [ppc64el] (jammy-proposed/universe) [1.68+ds-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: sysrepo [armhf] (jammy-proposed/universe) [2.0.53-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: ksh93u+m [s390x] (jammy-proposed/universe) [1.0.0~beta.1-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: aws-nuke [amd64] (jammy-proposed/universe) [2.16.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: aws-nuke [ppc64el] (jammy-proposed/universe) [2.16.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: zycore-c [arm64] (jammy-proposed/universe) [1.1.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: ksh93u+m [ppc64el] (jammy-proposed/universe) [1.0.0~beta.1-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: ntfs2btrfs [arm64] (jammy-proposed/universe) [20210523-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: tml [arm64] (jammy-proposed/universe) [0.4.0-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: ntfs2btrfs [armhf] (jammy-proposed/universe) [20210523-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: tml [armhf] (jammy-proposed/universe) [0.4.0-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: sysrepo [s390x] (jammy-proposed/universe) [2.0.53-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: bcm2835 [s390x] (jammy-proposed/universe) [1.68+ds-1] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: snowflake [ppc64el] (jammy-proposed/universe) [1.1.0-1] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: snowflake [armhf] (jammy-proposed/universe) [1.1.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: critnib [s390x] (jammy-proposed/universe) [1.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: snowflake [s390x] (jammy-proposed/universe) [1.1.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: ntfs2btrfs [s390x] (jammy-proposed/universe) [20210523-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: tml [s390x] (jammy-proposed/universe) [0.4.0-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: aws-nuke [s390x] (jammy-proposed/universe) [2.16.0-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: libnetconf2 [riscv64] (jammy-proposed/universe) [2.0.24-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: aws-nuke [arm64] (jammy-proposed/universe) [2.16.0-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: ksh93u+m [amd64] (jammy-proposed/universe) [1.0.0~beta.1-1] (no packageset)
[23:40] -queuebot:#ubuntu-release- New binary: aws-nuke [armhf] (jammy-proposed/universe) [2.16.0-1] (no packageset)
[23:40] -queuebot:#ubuntu-release- New binary: ksh93u+m [armhf] (jammy-proposed/universe) [1.0.0~beta.1-1] (no packageset)
[23:40] -queuebot:#ubuntu-release- New: accepted aws-nuke [arm64] (jammy-proposed) [2.16.0-1]
[23:40] -queuebot:#ubuntu-release- New: accepted ksh93u+m [armhf] (jammy-proposed) [1.0.0~beta.1-1]
[23:40] -queuebot:#ubuntu-release- New: accepted aws-nuke [armhf] (jammy-proposed) [2.16.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted aws-nuke [s390x] (jammy-proposed) [2.16.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted critnib [s390x] (jammy-proposed) [1.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted libnetconf2 [riscv64] (jammy-proposed) [2.0.24-1]
[23:41] -queuebot:#ubuntu-release- New: accepted snowflake [armhf] (jammy-proposed) [1.1.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted snowflake [s390x] (jammy-proposed) [1.1.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted bcm2835 [s390x] (jammy-proposed) [1.68+ds-1]
[23:41] -queuebot:#ubuntu-release- New: accepted ntfs2btrfs [s390x] (jammy-proposed) [20210523-1]
[23:41] -queuebot:#ubuntu-release- New: accepted tml [s390x] (jammy-proposed) [0.4.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted ksh93u+m [amd64] (jammy-proposed) [1.0.0~beta.1-1]
[23:41] -queuebot:#ubuntu-release- New: accepted snowflake [ppc64el] (jammy-proposed) [1.1.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted aws-nuke [amd64] (jammy-proposed) [2.16.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted ksh93u+m [ppc64el] (jammy-proposed) [1.0.0~beta.1-1]
[23:41] -queuebot:#ubuntu-release- New: accepted ntfs2btrfs [armhf] (jammy-proposed) [20210523-1]
[23:41] -queuebot:#ubuntu-release- New: accepted tml [arm64] (jammy-proposed) [0.4.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted zycore-c [arm64] (jammy-proposed) [1.1.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted aws-nuke [ppc64el] (jammy-proposed) [2.16.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted sysrepo [s390x] (jammy-proposed) [2.0.53-1]
[23:41] -queuebot:#ubuntu-release- New: accepted ntfs2btrfs [arm64] (jammy-proposed) [20210523-1]
[23:41] -queuebot:#ubuntu-release- New: accepted tml [armhf] (jammy-proposed) [0.4.0-1]
[23:41] -queuebot:#ubuntu-release- New: accepted bcm2835 [ppc64el] (jammy-proposed) [1.68+ds-1]
[23:42] -queuebot:#ubuntu-release- New: accepted libnetconf2 [arm64] (jammy-proposed) [2.0.24-1]
[23:42] -queuebot:#ubuntu-release- New: accepted rhonabwy [armhf] (jammy-proposed) [1.1.1-1]
[23:42] -queuebot:#ubuntu-release- New: accepted sysrepo [armhf] (jammy-proposed) [2.0.53-1]
[23:42] -queuebot:#ubuntu-release- New: accepted ksh93u+m [s390x] (jammy-proposed) [1.0.0~beta.1-1]
[23:42] -queuebot:#ubuntu-release- New: accepted sysrepo [arm64] (jammy-proposed) [2.0.53-1]
[23:42] -queuebot:#ubuntu-release- New: accepted ntfs2btrfs [ppc64el] (jammy-proposed) [20210523-1]
[23:42] -queuebot:#ubuntu-release- New: accepted sysrepo [ppc64el] (jammy-proposed) [2.0.53-1]
[23:42] -queuebot:#ubuntu-release- New: accepted bcm2835 [amd64] (jammy-proposed) [1.68+ds-1]
[23:42] -queuebot:#ubuntu-release- New: accepted bcm2835 [armhf] (jammy-proposed) [1.68+ds-1]
[23:42] -queuebot:#ubuntu-release- New: accepted libnetconf2 [armhf] (jammy-proposed) [2.0.24-1]
[23:42] -queuebot:#ubuntu-release- New: accepted snowflake [amd64] (jammy-proposed) [1.1.0-1]
[23:42] -queuebot:#ubuntu-release- New: accepted zydis [armhf] (jammy-proposed) [3.2.1-1]
[23:42] -queuebot:#ubuntu-release- New: accepted bcm2835 [arm64] (jammy-proposed) [1.68+ds-1]
[23:42] -queuebot:#ubuntu-release- New: accepted libnetconf2 [ppc64el] (jammy-proposed) [2.0.24-1]
[23:42] -queuebot:#ubuntu-release- New: accepted critnib [arm64] (jammy-proposed) [1.0-1]
[23:42] -queuebot:#ubuntu-release- New: accepted zydis [arm64] (jammy-proposed) [3.2.1-1]
[23:42] -queuebot:#ubuntu-release- New: accepted critnib [amd64] (jammy-proposed) [1.0-1]
[23:42] -queuebot:#ubuntu-release- New: accepted ntfs2btrfs [amd64] (jammy-proposed) [20210523-1]
[23:42] -queuebot:#ubuntu-release- New: accepted tml [amd64] (jammy-proposed) [0.4.0-1]
[23:43] -queuebot:#ubuntu-release- New: accepted libnetconf2 [amd64] (jammy-proposed) [2.0.24-1]
[23:43] -queuebot:#ubuntu-release- New: accepted zydis [amd64] (jammy-proposed) [3.2.1-1]
[23:43] -queuebot:#ubuntu-release- New: accepted proglog [amd64] (jammy-proposed) [0.1.9-1]
[23:46] <tumbleweed> juliank: one of the changes in 3.0.0-1 was to explicitly query 8.8.8.8
[23:46] <tumbleweed> https://salsa.debian.org/python-team/packages/aiodns/-/commit/47a029f34e3a80d4f2610549c983d0810ab1e19e#5f0316cda8d9317a3982eee7fe909a0b0de59630_17_17
[23:54] -queuebot:#ubuntu-release- New binary: rhonabwy [riscv64] (jammy-proposed/universe) [1.1.1-1] (no packageset)