Bug#1054659: marked as done (transition: utf8proc)
Your message dated Tue, 31 Oct 2023 21:42:25 -0100 with message-id and subject line Re: Bug#1054659: transition: utf8proc has caused the Debian Bug report #1054659, regarding transition: utf8proc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: utf8p...@packages.debian.org Control: affects -1 + src:utf8proc Dear release team, We can start the transition for utf8proc, which recently got an SOVERSION bump from 2 to 3. I tested the reverse dependencies on ppc64el and all of them are fine. The results for amd64 should be the same. Reverse Build-depends in main: -- bibledit [ok] bibledit-cloud [ok] ccextractor [ok] deepin-terminal [ok] fcft [ok] fnott [ok] foot [ok] fuzzel [ok] mame [ok] pnetcdf [ok] qterminal [ok] qtermwidget [ok] securefs [ok] subversion [ok] yambar [ok] the automatic ben file is correct: https://release.debian.org/transitions/html/auto-utf8proc.html Ben file: title = "utf8proc"; is_affected = .depends ~ "libutf8proc2" | .depends ~ "libutf8proc3"; is_good = .depends ~ "libutf8proc3"; is_bad = .depends ~ "libutf8proc2"; Thank you for using reportbug --- End Message --- --- Begin Message --- libutf8proc2 is gone from testing, closing.--- End Message ---
Bug#1055059: marked as done (nmu: runc_1.1.5+ds1-1+b4)
Your message dated Tue, 31 Oct 2023 21:50:46 + with message-id and subject line Bug#1055059: fixed in runc 1.1.5+ds1-5 has caused the Debian Bug report #1055059, regarding nmu: runc_1.1.5+ds1-1+b4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: r...@packages.debian.org Control: affects -1 + src:runc nmu runc_1.1.5+ds1-1+b4 . ANY . unstable . -m "rebuild against golang-github-urfave-cli_1.22.14-1" please rebuild runc (again) to pickup dependency changes. I believe this rebuild to allow britney to detect the right combination of package version to allow runc to migrate. Thanks --- End Message --- --- Begin Message --- Source: runc Source-Version: 1.1.5+ds1-5 Done: Reinhard Tartler We believe that the bug you reported is fixed in the latest version of runc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler (supplier of updated runc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 31 Oct 2023 08:32:10 -0400 Source: runc Architecture: source Version: 1.1.5+ds1-5 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Reinhard Tartler Closes: 1046528 1055059 Changes: runc (1.1.5+ds1-5) unstable; urgency=medium . * Team Upload * Rebuild against golang-github-urfave-cli_1.22.14-1, Closes: #1055059 * Bug fix: "Fails to build source after successful build", thanks to Lucas Nussbaum, Closes: #1046528 Checksums-Sha1: 162a0970336515ad6fc5bdaac52269cce66363fe 3241 runc_1.1.5+ds1-5.dsc a268c277645c6078c7175c36275b8fa573838d45 11740 runc_1.1.5+ds1-5.debian.tar.xz Checksums-Sha256: 4af44d63f474d5b4556ae1fcb13fe9cb664bd27c7acff06fc1ee8e86cd2fd8e2 3241 runc_1.1.5+ds1-5.dsc df525c55f0334bef408d20ad7134d7209ad45df8bbacabba7b28db0a9d494c8f 11740 runc_1.1.5+ds1-5.debian.tar.xz Files: 360a5fea57bfdce5d4a75e5dfcb80549 3241 admin optional runc_1.1.5+ds1-5.dsc 819e0b0476f6c2ae3288f647391a58dc 11740 admin optional runc_1.1.5+ds1-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmVBZawUHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJssV9BAApOOSuYTaqrKLWsL9b40gyJUbJtqj KYuGcQeHBnHoZhYYiA7DmoBZWqh7nj6utt5unn57CmXwasaZwBdhl5SHdvAsKs6C rUzPHaFYaussZ61nido+6Uq4c8bXybNPJdExgSCAkl1llzcIXN9xGELjNPcBk47T w/Gr7gW01tCPA877yQphK77jdP2FeVRQP8rSgOeSRZXDuibNGnTsfoVHa6YPTGFx ZJk2vMzkowK8v45Z3137ufmz+kwRTYD+zuuFi6+D18XX2eDZQchl8nqQbGUAcv3f /bsut6Wx+LA7tUE8V3alaEzOsQ3MNirAlvlSIWeqtNbnC5ho68ZiObj55l+dp7xe VaArlqDcTtb6u0cmMOgZVuZPwwvk3PvdiuMGLMbeZ97j0wP0pgTS8CL3zXRPkEpR 88gHcsBInnYnO0yGGKHs570xaVe0OqnbJy0UhgDZ0TR8qtdNWbiadgah5ybZ66eQ 9kgjuqoGv/jMMHzb/vKp5dBHWobKKVcP5pTw8ntXkO66CWwKTgCZfqJ+PzOL4XY3 hiqBHzEWYO6rBSm37NGxHGRK35WbnBSthaZBlBj8kC7R0Mwe7KqMncSMu/MNWoQ3 2dsoLmfCxA/OPApHoES6XFbVHlrHjkm/kmlPlCdgNq2Iy04gh5hRsZCbhIl78cN3 KSJ6JeUa+CK+Ao0= =AT16 -END PGP SIGNATURE End Message ---
Bug#1055115: bookworm-pu: package prometheus-node-exporter-collectors/0.0~git20230203.6f710f8-1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: prometheus-node-exporter-collect...@packages.debian.org Control: affects -1 + src:prometheus-node-exporter-collectors [ Reason ] Since the bookworm upgrade, all hosts with the prometheus-node-exporter-collectors package install repeatedly hit the mirrors with spurious apt-update runs. The Debian package systemd.timer(1) schedule is once on boot and then every 15 minutes after, which imposes a tremendous load on the mirror system. It also happens to lock the apt status files which can in turn cause deadlocks with other programs. There seems to be an (unrelated?) regression in apt where some (python?) apt program can hang this way indefinitely. That's tracked separately, e.g. https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851 [ Impact ] The mirror networks are going to be badly negatively affected by this. This actually doesn't seem to have been a problem so far, possibly because deb.debian.org is absorbing everything we can throw at it and no one is looking at Fastly (or Amazon?), but I suspect this could become a problem as Prometheus adoption widens. This also can mean some security upgrades don't get deployed, as the apt update lockfile gets hung. [ Tests ] There's no autopkgtest on this package, but the patches provided here have been tested in production in about 90 servers for torproject.org over a few weeks now, fixing the diagnosed issue. https://gitlab.torproject.org/tpo/tpa/team/-/issues/41355 is our tracking ticket documenting this. [ Risks ] Code is *relatively* simple. It diverges from upstream a little now because upstream did a little reactoring post bookworm and I didn't want to make the patch bigger than it absolutely needs to be. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] There are three individual patches, cherry-picked and backported from upstream. The first one simply stops running apt-update. The second and third patch add a new metric which keeps track of the last update timestamp on the apt metadata. That is important: previously, the script was running apt-update so we could be pretty sure it was running automatically. But by making this change, we're *not* running apt-update automatically and assume users have properly setup something *else* that does. This was the behaviour in bullseye, for the record, but it's possible that some users *assume* the wrong (new) behavior was the correct one and installed the package not knowing they need to deploy their own APT::Periodic thing. diff -Nru prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/changelog prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/changelog --- prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/changelog 2023-02-02 23:57:45.0 -0500 +++ prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/changelog 2023-10-31 13:57:52.0 -0400 @@ -1,3 +1,10 @@ +prometheus-node-exporter-collectors (0.0~git20230203.6f710f8-1+deb12u1) bookworm; urgency=medium + + * Team upload + * Fix deadlock with other apt update runs (Closes: #1028212) + + -- Antoine Beaupré Tue, 31 Oct 2023 13:57:52 -0400 + prometheus-node-exporter-collectors (0.0~git20230203.6f710f8-1) unstable; urgency=medium * New upstream snapshot (Closes: #1030058) diff -Nru prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/patches/0001-do-not-run-apt-update-or-simulate-apt-dist-upgrade.patch prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/patches/0001-do-not-run-apt-update-or-simulate-apt-dist-upgrade.patch --- prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/patches/0001-do-not-run-apt-update-or-simulate-apt-dist-upgrade.patch 1969-12-31 19:00:00.0 -0500 +++ prometheus-node-exporter-collectors-0.0~git20230203.6f710f8/debian/patches/0001-do-not-run-apt-update-or-simulate-apt-dist-upgrade.patch 2023-10-31 13:57:52.0 -0400 @@ -0,0 +1,65 @@ +From 28c179ddfd3d7e0f5bc49b93f924f0dffba5b71d Mon Sep 17 00:00:00 2001 +From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= +Date: Fri, 13 Oct 2023 12:29:48 -0400 +Subject: [PATCH] do not run apt update or simulate apt dist-upgrade +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +This is causing all sorts of problems. The first of which is that +we're hitting our poor mirrors every time the script is ran, which, in +the Debian package configuration, is *every 15 minutes* (!!). + +The second is that this locks the cache and makes this script +needlessly stumble upon a possible regression in APT from Debian +bookworm and Ubuntu 22.06: +
Processed: bookworm-pu: package prometheus-node-exporter-collectors/0.0~git20230203.6f710f8-1
Processing control commands: > affects -1 + src:prometheus-node-exporter-collectors Bug #1055115 [release.debian.org] bookworm-pu: package prometheus-node-exporter-collectors/0.0~git20230203.6f710f8-1 Added indication that 1055115 affects src:prometheus-node-exporter-collectors -- 1055115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055085: (some kind of) transition: add python3.12 as a supported python3 version
Hi Matthias On Tue, 31 Oct 2023 at 07:15, Matthias Klose wrote: > Please setup a tracker to add python3.12 as a supported python3 version. This > is > non-blocking, as packages can migrate on their own once built. I'm not yet > starting this, just want to have an overview of affected packages. > > Please re-use the final version of the python3.11 tracker. > https://release.debian.org/transitions/html/python3.11-add.html I've set up a tracker [1]. It is based on the tracker used for python3.11 with the inclusion of boost-defaults (which is otherwise not pulled in) and the exclusion of dh-python (which confused ben in dependency levels 1 and 2). Excluding the 'unknown' packages on the tracker (which should not need rebuilding), it lists the same packages as the old one. Regards Graham [1] https://release.debian.org/transitions/html/python3.12-add.html
Bug#1055086: bookworm-pu: package libmateweather/1_1.26.0-1.1+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: libmateweat...@packages.debian.org Control: affects -1 + src:libmateweather Please unblock the recent bookworm-pu upload of libmateweather. [ Reason ] Main reason for providing the pu is that Aviation Weather change their data server URL for retrieving weather information from their servers. While at it, more data changes have been cherry-picked from upstream (see below). [ Impact ] If this pu does not get accepted, Debian users will have a broken weather-applet on MATE desktop. No weather information can be retrieved. Furthermore, users will experience typos and spelling issue in location names, etc. [ Tests ] Manually installed the new .deb version and test the MATE weather applet regarding the introduced changes. [ Risks ] Regressions are always possible. MATE users will be affected. Esp. when using weather reports on their desktop. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] + * debian/patches: Cherry-pick (and re-arrange) upstream fixes. + + rename: timezones.patch => 0001_Kyiv-timezone.patch (100%) + + add city: 0002_add-San-Miguel-de-Tucuman-Argentina.patch + + update Chicago area codes: 0003_Chicago-area-updates.patch + + update data server URL: 0004_data-server-url-changed.patch (Closes: + #1054248, #1054268) + + typo fixes in location names: 0005_fix-some-location-names.patch + + new Tbilisi airport code: 0006_tbilisi-IATA-airport-code-changed.patch [ Other info ] None. diff -Nru libmateweather-1.26.0/debian/changelog libmateweather-1.26.0/debian/changelog --- libmateweather-1.26.0/debian/changelog 2022-10-15 17:45:15.0 +0200 +++ libmateweather-1.26.0/debian/changelog 2023-10-31 08:25:09.0 +0100 @@ -1,3 +1,16 @@ +libmateweather (1.26.0-1.1+deb12u1) bookworm; urgency=medium + + * debian/patches: Cherry-pick (and re-arrange) upstream fixes. + + rename: timezones.patch => 0001_Kyiv-timezone.patch (100%) + + add city: 0002_add-San-Miguel-de-Tucuman-Argentina.patch + + update Chicago area codes: 0003_Chicago-area-updates.patch + + update data server URL: 0004_data-server-url-changed.patch (Closes: + #1054248, #1054268) + + typo fixes in location names: 0005_fix-some-location-names.patch + + new Tbilisi airport code: 0006_tbilisi-IATA-airport-code-changed.patch + + -- Mike Gabriel Tue, 31 Oct 2023 08:25:09 +0100 + libmateweather (1.26.0-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libmateweather-1.26.0/debian/patches/0001_Kyiv-timezone.patch libmateweather-1.26.0/debian/patches/0001_Kyiv-timezone.patch --- libmateweather-1.26.0/debian/patches/0001_Kyiv-timezone.patch 1970-01-01 01:00:00.0 +0100 +++ libmateweather-1.26.0/debian/patches/0001_Kyiv-timezone.patch 2023-10-31 08:12:39.0 +0100 @@ -0,0 +1,32 @@ +Author: Reiner Herrmann +Bug-Debian: https://bugs.debian.org/1017304 +Description: Update spelling of Kiev/Kyiv to match tzdata + tzdata 2022b-1 changed it from Kiev to Kyiv. + +--- a/data/Locations.xml.in b/data/Locations.xml.in +@@ -20618,13 +20618,13 @@ + UA + UP + +- ++ + Europe/Simferopol + Europe/Uzhgorod + Europe/Zaporozhye + + +- Europe/Kiev ++ Europe/Kyiv + + + Boryspil' +@@ -20700,7 +20700,7 @@ + "Kiev" is the traditional English name. + The local name in Ukrainian is "Kyyiv". + --> +-Kiev ++Kyiv + 50.43 30.516667 + + Kyiv diff -Nru libmateweather-1.26.0/debian/patches/0002_add-San-Miguel-de-Tucuman-Argentina.patch libmateweather-1.26.0/debian/patches/0002_add-San-Miguel-de-Tucuman-Argentina.patch --- libmateweather-1.26.0/debian/patches/0002_add-San-Miguel-de-Tucuman-Argentina.patch 1970-01-01 01:00:00.0 +0100 +++ libmateweather-1.26.0/debian/patches/0002_add-San-Miguel-de-Tucuman-Argentina.patch 2023-10-31 08:14:08.0 +0100 @@ -0,0 +1,42 @@ +From f0c9cc4764ec3d21ea0d8589c943635606aa2c09 Mon Sep 17 00:00:00 2001 +From: Rodolfo Guagnini +Date: Mon, 4 Jul 2022 10:13:46 -0300 +Subject: locations: add San Miguel de Tucuman (Argentina) + +San Miguel is the capital city of an state of Argentina, and it has international airport with corresponding 4 letter code. I used other Argentina city as template, updated the name, the airport's code, latitud and longitude taken from wikipedia: https://en.wikipedia.org/wiki/Teniente_General_Benjam%C3%ADn_Matienzo_International_Airport +--- + data/Locations.xml.in | 11 ++- + 1 file changed, 10 insertions(+), 1 deletion(-) + +diff --git
Processed: bookworm-pu: package libmateweather/1_1.26.0-1.1+deb12u1
Processing control commands: > affects -1 + src:libmateweather Bug #1055086 [release.debian.org] bookworm-pu: package libmateweather/1_1.26.0-1.1+deb12u1 Added indication that 1055086 affects src:libmateweather -- 1055086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055085: (some kind of) transition: add python3.12 as a supported python3 version
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-CC: debian-pyt...@lists.debian.org Please setup a tracker to add python3.12 as a supported python3 version. This is non-blocking, as packages can migrate on their own once built. I'm not yet starting this, just want to have an overview of affected packages. Please re-use the final version of the python3.11 tracker. https://release.debian.org/transitions/html/python3.11-add.html The upstream release in on time again, so we should be prepared to start this addition after the upstream release end of October.
