Bug#999762: bullseye-pu: package lshw/02.18.85-0.7
Control: tags -1 + moreinfo On Tue, 2021-11-16 at 10:54 +0100, Thomas Goirand wrote: > I would like to update Bullseye with the latest version of > lshw as in unstable/testing. > > [ Reason ] > The Bullseye version of lshw > has bugs with its json output, rendering the hardware report > agent of openstack-cluster-installer unuseable in some cases, > depending on the hardware. > > [ Impact ] > Broken json output, non-successful hardware report in OCI. > [...] > Note: I'm not providing a debdiff, since that's just the > version in unstable. I'd just upload it as: > > 02.19.git.2021.06.19.996aaad9c7-2~deb11u1 > > if you agree. "Just a backport" doesn't remove the request for a debdiff. Indeed, looking at a debdiff gives, amongst the expected set of changes to data and so on: Build-Depends: debhelper-compat (= 10), - libgtk2.0-dev, + libgtk-3-dev, switching GTK version isn't really the sort of change that would be expected in a stable update, and has nothing to do with broken JSON output so far as I can tell. Regards, Adam
Processed: Re: Bug#999762: bullseye-pu: package lshw/02.18.85-0.7
Processing control commands: > tags -1 + moreinfo Bug #999762 [release.debian.org] bullseye-pu: package lshw/02.18.85-0.7 Added tag(s) moreinfo. -- 999762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987013: Bug#996584: (some kind of) transition: add python3.10 as a supported python3 version
On Tue, Nov 16, 2021 at 02:23:36PM +0100, Matthias Klose wrote: > I'm planning to upload python3-defaults later tonight, adding 3.10 as a > supported Python version. Packages are able to migrate on their own, there > are > no blockages introduced on other transitions. > > We have most packages ready to build for 3.10, and around 70 leaf packages > still > needing some work. Otoh, we can much better work on these if reverse > dependencies are already built for 3.10 in the archive. The tracker used is >... I think the backwards incompatible change to the dbm extension[1] has to be reverted until after a release where someone has migrated the data of all packages using Berkeley DB. Most broken packages are likely not even among the ones that need rebuilding, they would just be just broken and Python should not make it harder to fix them. If Berkeley DB removal should be done in trixie, someone will have to analyze and implement solutions for data migrations as part of #987013 in bookworm. Ecosystem maintainers unilaterally dropping support would only make it a lot harder to implement solutions. How should a package like apt-listchanges migrate its database if the existing reader code is no longer functional due to this change in Python? That's not impossible, but might make things a lot harder. AFAIK even Python 2.7 will still be shipped in bookworm, so let's not make life harder for other people by hurrying too much with Berkeley DB. > Matthias cu Adrian [1] https://tracker.debian.org/news/1240462/accepted-python310-3100b1-2-source-into-experimental/
Bug#996584: (some kind of) transition: add python3.10 as a supported python3 version
I'm planning to upload python3-defaults later tonight, adding 3.10 as a supported Python version. Packages are able to migrate on their own, there are no blockages introduced on other transitions. We have most packages ready to build for 3.10, and around 70 leaf packages still needing some work. Otoh, we can much better work on these if reverse dependencies are already built for 3.10 in the archive. The tracker used is https://release.debian.org/transitions/html/python3.10-add.html As some kind of reference, the current state of the 3.10 addition in Ubuntu can be seen at https://people.canonical.com/~ubuntu-archive/transitions/html/python3.10-add.html Matthias
Bug#999770: transition: libjsoncpp
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear release team, I woud like to transition libjsoncpp after an ABI version bump. I rebuilt CMake successfully and I don't expect any FTBFS issues, as the diff on the public headers shows mostly added "noexpect" and "const" qualifiers, which will not break existing source code. One hacky "volatile" qualifier has been removed from the SecureAllocator::deallocate() signature in json/allocator.h, but codesearch.debian.net tells me that header is not directly used by reverse dependencies anyway. The Ben file at https://release.debian.org/transitions/html/auto-libjsoncpp.html is good. Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmGTqUYACgkQ+C8H+466 LVmBAwwAkXJS3XQgdwR4JyN6idMw/K3KrPpYLde68q5+lHOKjLUCOgcvs1gPDOfh gDI0sCOyjOocYVYy/08CHhDitOXbZxPDuYU5LLoqoORgFyaycIPMmM5zmgZnQvWA sYCe/DeLbgKSZEdvyZEurLx2T1S0QmudR96garFiIti0J9WsM6KWNDCzK6m7PVZt ZhOZ+UMBCDFzjeejTo+Nl8HQ4punVUNGmRmu4xjF5OafFmzKfPclJx2EIJOXJMyp NMV4aoqDhic+4eBSk6Epogo5bEHFQry9H2+AJtt+0MBEV7wG5tDE0eVCOSdd3TXy qdLWlfIF1vkQM8J2M6Z4eESnSeRVQK7615fFkzaZSpS6us6NaF2AJsP/acgNqJTi vIJkj8NBP/tBOR6+tkXWLy2HQCokTdbqBKtAS2YipWZNO4g9LmUFhGxeOeRCKbSS oarHOuz8YfnR8D9YGZqb7mo3UrnNRJZuivq2kYmr6hZC6aP/6v7HQlH+yvOcXrD7 fe+lvyli =oOjg -END PGP SIGNATURE-
Bug#999769: bullseye-pu: package calibre/5.12.0+dfsg-1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: yokota.h...@gmail.com [ Reason ] Fix bug #998744 (calibre: Python byte-compile error when installing calibre). [ Impact ] Installation fails as describes in bug #998744 . [ Tests ] Source code has many unit tests to check high and low level functionality. [ Risks ] Change is very trivial. See "debian/patches/0011-Avoid-to-use-embedded-assignment-syntax-Closes-99874.patch" . Not well tested on "bullseye/stable" machine because I use "sid/unstable" machine. Trivial checks on my "sid/unstable" machine was OK. [ 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 ] * Avoid to use embedded assignment syntax (Closes: #998744) [ Other info ] This fix is already applied on upstream. This error was also reported at: https://bugs.launchpad.net/calibre/+bug/1942463 Fixes are: https://github.com/kovidgoyal/calibre/commit/884839a691e800e56e185e10019a66b12feea640 and https://github.com/kovidgoyal/calibre/commit/ed32130ca4cbbf235f5560e7c53f78c01eab1106 diff -Nru calibre-5.12.0+dfsg/debian/changelog calibre-5.12.0+dfsg/debian/changelog --- calibre-5.12.0+dfsg/debian/changelog 2021-02-26 22:39:59.0 +0900 +++ calibre-5.12.0+dfsg/debian/changelog 2021-11-16 08:37:45.0 +0900 @@ -1,3 +1,9 @@ +calibre (5.12.0+dfsg-1+deb11u1) bullseye; urgency=medium + + * Avoid to use embedded assignment syntax (Closes: #998744) + + -- YOKOTA Hiroshi Tue, 16 Nov 2021 08:37:45 +0900 + calibre (5.12.0+dfsg-1) unstable; urgency=medium * New upstream version 5.12.0+dfsg diff -Nru calibre-5.12.0+dfsg/debian/patches/0011-Avoid-to-use-embedded-assignment-syntax-Closes-99874.patch calibre-5.12.0+dfsg/debian/patches/0011-Avoid-to-use-embedded-assignment-syntax-Closes-99874.patch --- calibre-5.12.0+dfsg/debian/patches/0011-Avoid-to-use-embedded-assignment-syntax-Closes-99874.patch 1970-01-01 09:00:00.0 +0900 +++ calibre-5.12.0+dfsg/debian/patches/0011-Avoid-to-use-embedded-assignment-syntax-Closes-99874.patch 2021-11-16 08:37:45.0 +0900 @@ -0,0 +1,31 @@ +From: YOKOTA Hiroshi +Date: Tue, 9 Nov 2021 23:56:51 +0900 +Subject: Avoid to use embedded assignment syntax (Closes: #998744) + +Forwarded: not-needed + +This error was also reported at: + https://bugs.launchpad.net/calibre/+bug/1942463 + +Fixes are: + https://github.com/kovidgoyal/calibre/commit/884839a691e800e56e185e10019a66b12feea640 +and + https://github.com/kovidgoyal/calibre/commit/ed32130ca4cbbf235f5560e7c53f78c01eab1106 +--- + src/calibre/utils/formatter.py | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/src/calibre/utils/formatter.py b/src/calibre/utils/formatter.py +index 83f2a00..18d1afd 100644 +--- a/src/calibre/utils/formatter.py b/src/calibre/utils/formatter.py +@@ -656,7 +656,8 @@ class _Interpreter(object): + + def do_node_first_non_empty(self, prog): + for expr in prog.expression_list: +-if v := self.expr(expr): ++v = self.expr(expr) ++if v: + return v + return '' + diff -Nru calibre-5.12.0+dfsg/debian/patches/series calibre-5.12.0+dfsg/debian/patches/series --- calibre-5.12.0+dfsg/debian/patches/series 2021-02-26 22:39:10.0 +0900 +++ calibre-5.12.0+dfsg/debian/patches/series 2021-11-16 08:37:45.0 +0900 @@ -8,3 +8,4 @@ 0008-Don-t-change-book-file-unless-user-s-consent-Closes-.patch 0009-dont-use-python-crypto.patch 0010-Restore-chardet-module-support.patch +0011-Avoid-to-use-embedded-assignment-syntax-Closes-99874.patch
Processed: Re: Bug#999565: transition: fluidsynth
Processing control commands: > tags -1 moreinfo Bug #999565 [release.debian.org] transition: fluidsynth Added tag(s) moreinfo. > forwarded -1 https://release.debian.org/transitions/html/auto-fluidsynth.html Bug #999565 [release.debian.org] transition: fluidsynth Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-fluidsynth.html'. -- 999565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999565: transition: fluidsynth
Control: tags -1 moreinfo Control: forwarded -1 https://release.debian.org/transitions/html/auto-fluidsynth.html On 2021-11-12 16:39:55, Dennis Braun wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: d_br...@kabelmail.de > > The binaryname of the fluidsynth library is changing from libfluidsynth2 to > libfluidsynth3. > > Following packages are affected: > > ardour > audacious-plugins > buzztrax > calf-plugins > denemo > doomsday-common > fluidr3mono-gm-soundfont > fluidsynth > fluidsynth-dssi > freewheeling > gstreamer1.0-plugins-bad > kodi-audiodecoder-fluidsynth > libalure1 > libcsound64-6.0 > libdrumstick-rt-backends > libfluidsynth-dev > libsdl2-mixer-2.0-0 > libsdl-mixer1.2 > libtritonus-jni > lmms > minuet > mpd > muse > musescore-general-soundfont > musescore-general-soundfont-lossless > musescore-general-soundfont-small > pianobooster > prboom-plus > qsynth > scummvm > swami > tuxguitar-fluidsynth > vlc-plugin-fluidsynth Do the reverse dependencies build fine against the new version? Cheers > > Ben file: > > title = "fluidsynth"; > is_affected = .depends ~ "libfluidsynth2" | .depends ~ "libfluidsynth3"; > is_good = .depends ~ "libfluidsynth3"; > is_bad = .depends ~ "libfluidsynth2"; > -- Sebastian Ramacher
Bug#999762: bullseye-pu: package lshw/02.18.85-0.7
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu Hi, I would like to update Bullseye with the latest version of lshw as in unstable/testing. [ Reason ] The Bullseye version of lshw has bugs with its json output, rendering the hardware report agent of openstack-cluster-installer unuseable in some cases, depending on the hardware. [ Impact ] Broken json output, non-successful hardware report in OCI. [ Tests ] We've been using the latest version of lshw for months without a glitch. [ Risks ] No risk that I can see. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable Note: I'm not providing a debdiff, since that's just the version in unstable. I'd just upload it as: 02.19.git.2021.06.19.996aaad9c7-2~deb11u1 if you agree. Cheers, Thomas Goirand (zigo)
