Processed: Re: Bug#998200: transition: bibutils
Processing control commands: > tags -1 confirmed Bug #998200 [release.debian.org] transition: bibutils Added tag(s) confirmed. > forwarded -1 https://release.debian.org/transitions/html/auto-bibutils.html Bug #998200 [release.debian.org] transition: bibutils Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-bibutils.html'. -- 998200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998200: transition: bibutils
Control: tags -1 confirmed Control: forwarded -1 https://release.debian.org/transitions/html/auto-bibutils.html On 2021-10-31 22:32:05, Pierre Gruet wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear Release Team, > > I am preparing the transition from libbibutils7 to libbibutils8, which is in > experimental and builds well. > This change is needed as the ABI has encountered many changes by upstream. Please go ahead Cheers > > Ben file: > > title = "bibutils"; > is_affected = .depends ~ "libbibutils7" | .depends ~ "libbibutils8"; > is_good = .depends ~ "libbibutils8"; > is_bad = .depends ~ "libbibutils7"; > > The auto-transitioner page [1] is fine. > > Here are the results of the test builds of the 5 reverse dependencies: > > * bibutils build OK in experimental (same source package > as libbibutils8) > * haskell-hs-bibutils build OK, binNMU needed for the dependencies > list of libghc-hs-bibutils-dev > * haskell-pandoc-citeproc build OK > * haskell-blogliteratelybuild OK > * haskell-hakyllbuild OK > > Best regards, > Pierre > > [1] https://release.debian.org/transitions/html/auto-bibutils.html > -- Sebastian Ramacher
Bug#997929: transition: yaml-cpp
On 2021-11-03 00:26:07, Sebastian Ramacher wrote: > Control: tags -1 confirmed > > On 2021-10-29 00:24:37, Adrian Bunk wrote: > > On Thu, Oct 28, 2021 at 09:50:10PM +0200, Sebastian Ramacher wrote: > > > Control: forwarded -1 > > > https://release.debian.org/transitions/html/auto-yaml-cpp.html > > > > > > On 2021-10-27 05:05:57 -0500, Simon Quigley wrote: > > > > Package: release.debian.org > > > > Severity: normal > > > > User: release.debian@packages.debian.org > > > > Usertags: transition > > > > > > > > Dear Release Team, > > > > > > > > I would like to upload yaml-cpp 0.7.0 to unstable which includes an ABI > > > > bump > > > > and a package name change (libyaml-cpp0.6 -> libyaml-cpp0.7). It has > > > > already > > > > been uploaded to Experimental and cleared NEW. Since the package now > > > > depends > > > > on googletest instead of including its own embedded copy, the package > > > > now > > > > builds on less architectures. > > > > > > Are builds on releases acrchitectures affected by this change? > > > > sh4 (in ports) is the only affected Linux architecture: > > https://buildd.debian.org/status/package.php?p=yaml-cpp=experimental > > Please go ahead … but please without the Breaks+Replaces on the old binary packages. They are unnecessary Cheers -- Sebastian Ramacher
Processed (with 1 error): Re: Bug#998169: transition: unixodbc
Processing control commands: > tags -1 moreinfo Bug #998169 [release.debian.org] transition: unixodbc Added tag(s) moreinfo. > https://release.debian.org/transitions/html/auto-unixodbc.html Unknown command or malformed arguments to command. -- 998169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998169: transition: unixodbc
Control: tags -1 moreinfo Control: https://release.debian.org/transitions/html/auto-unixodbc.html On 2021-10-31 22:30:26, Hugh McMaster wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Due to various changes, unixodbc's libraries, libodbc, libodbccr and libodbccr > have a new soversion. Why do the binary packages have Breaks + Replaces on binary packages with the old SONAME? Cheers > > Test results after rebuilding all reverse dependencies and reverse-build > dependencies: > > The following packages FTBFS for reasons unrelated to unixodbc: > * asterisk; see #997136 > * libghc-hdbc-odbc-dev (src:hdbc-odbc); not in testing > * libmyodbc (src:myodbc); not in testing > * pike8.0-odbc (src:pike8.0); not in testing > * w1retap-odbc (src:w1retap); not in testing > > tdbcodbc will require a source or NMU upload; see #997057, where the > maintainer > says he will take care of this. > > grass, vtk7, mysql-workbench and saga all require rebuilds once gdal is > rebuilt. > > > Ben file: > > title = "unixodbc"; > is_affected = .depends ~ "libodbc1" | .depends ~ "odbcinst1debian2" | .depends > ~ "libodbc2" | .depends ~ "libodbccr2" | .depends ~ "libodbcinst2"; > is_good = .depends ~ "libodbc2" | .depends ~ "libodbccr2" | .depends ~ > "libodbcinst2"; > is_bad = .depends ~ "libodbc1" | .depends ~ "odbcinst1debian2"; > -- Sebastian Ramacher
Bug#997929: transition: yaml-cpp
Control: tags -1 confirmed On 2021-10-29 00:24:37, Adrian Bunk wrote: > On Thu, Oct 28, 2021 at 09:50:10PM +0200, Sebastian Ramacher wrote: > > Control: forwarded -1 > > https://release.debian.org/transitions/html/auto-yaml-cpp.html > > > > On 2021-10-27 05:05:57 -0500, Simon Quigley wrote: > > > Package: release.debian.org > > > Severity: normal > > > User: release.debian@packages.debian.org > > > Usertags: transition > > > > > > Dear Release Team, > > > > > > I would like to upload yaml-cpp 0.7.0 to unstable which includes an ABI > > > bump > > > and a package name change (libyaml-cpp0.6 -> libyaml-cpp0.7). It has > > > already > > > been uploaded to Experimental and cleared NEW. Since the package now > > > depends > > > on googletest instead of including its own embedded copy, the package now > > > builds on less architectures. > > > > Are builds on releases acrchitectures affected by this change? > > sh4 (in ports) is the only affected Linux architecture: > https://buildd.debian.org/status/package.php?p=yaml-cpp=experimental Please go ahead Cheers -- Sebastian Ramacher
Processed: Re: Bug#997929: transition: yaml-cpp
Processing control commands: > tags -1 confirmed Bug #997929 [release.debian.org] transition: yaml-cpp Added tag(s) confirmed. -- 997929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997695: marked as done (transition: draco)
Your message dated Wed, 3 Nov 2021 00:17:57 +0100 with message-id and subject line Re: Bug#997695: transition: draco has caused the Debian Bug report #997695, regarding transition: draco 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.) -- 997695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997695 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: roehl...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear release team, the draco library needs a transition after an ABI break due to a refactored class in a public header. I notified upstream that they forgot to bump the SOVERSION, but they did not react yet. Fortunately, none of the reverse dependencies (PDAL and the filament library waiting in NEW) uses that refactored class, so the transition should run smoothly, and my local rebuild on amd64 was successful at least. The auto-generated ben file is good. Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmF1LFoACgkQ+C8H+466 LVmFkgwAqAfVlDMCoa6XBfCBPnzUqv1oHnrPHMTKx09keKTWsxAAYaQULy1ieLhm e3lSm+yJHx8UJW0O1poWQiYGslWceQ8iF83SCF8PWpudvoX1T3j8giuRIO1aY+a9 XhP92QSW7iNt/QqHrg2tImsECTsqfnYSJ/BJNUI2wm+oUm5zdy4wByqk5AWRBFot tgONw2hyVKjGSPmd+KnmQsm8zixKdYa6uY+1tKLSvMUnQeP7sD4ViqAVcLlPMAae QYcD2dk+O6ZlwgsAhW1INrlmcjcOjXmMGFEJNnTKRG7fV6xF9qwwnGOf+/aoU8DK 9fp8y7iFtnnnlC0ZWXoE2wEhuhLl3VVFRvJjgENE3aNEdjJwMk3+nMgA0R1HpToa RiJOLWjxUvoZmrdJnbOlYkp6pn9WscLenLiETPjpdXzkd+flBRfrh34SL93KCS7y kLdABmI6jwjwYbcnMCbH8fQZNP0Hes/mUXD/gUo6gQyzQIpM8AaN7Ar18vSQEBhm JGnN4K7X =//07 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 2021-10-28 21:48:08, Sebastian Ramacher wrote: > Control: tags -1 confirmed > > On 2021-10-24 11:50:22 +0200, Timo Röhling wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > X-Debbugs-Cc: roehl...@debian.org > > > > Dear release team, > > > > the draco library needs a transition after an ABI break due to a > > refactored class in a public header. I notified upstream that they > > forgot to bump the SOVERSION, but they did not react yet. > > > > Fortunately, none of the reverse dependencies (PDAL and the filament > > library waiting in NEW) uses that refactored class, so the transition > > should run smoothly, and my local rebuild on amd64 was successful at > > least. > > > > The auto-generated ben file is good. > > Please go ahead It's done Cheers > > Cheers > > > > > Cheers > > Timo > > > > > > > > -- > Sebastian Ramacher -- Sebastian Ramacher--- End Message ---
Bug#998148: transition: libavif
On 2021-11-02 21:22:35, Norbert Preining wrote: > Hi Boyuan > > > > I plan to start another libavif transition as shown in the following > > Great, actually it would be great going straight to 0.9.3-2 with libaom v3 > support, so that writing of avif files also works. For the future: we prefer to not entangle transitions in general and especially when they have already been started. Please let us know before uploading if you want to entangle them. And the general recommendation for all packages involved in a transition still applies: please only upload if the upload is required to finish a transition - otherwise wait until its done. Best Sebastian -- Sebastian Ramacher
Uploading linux (5.14.16-1)
Hi I would like to upload linux version 5.14.16-1 to unstable tomorrow. It imports stable versions from 5.14.13 to 5.14.16. An ABI bump is included. The packaging changes done cover: * Revert "[amd64] Unset AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT" * media: ir-kbd-i2c: improve responsiveness of hauppauge zilog receivers (Closes: #994050) * [x86] media: ite-cir: IR receiver stop working after receive overflow (Closes: #996672) Regards, Salvatore signature.asc Description: PGP signature
Bug#998344: buster-pu: package llvm-toolchain-11/1:11.0.1-2~deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello release managers, In order to support the update of rustc in buster, which in turn is needed to support the updates of firefox-esr and thunderbird, I am proposing an update of llvm-toolchain-11 in buster. The attached diff represents the change from the current package in the buster-backports repository. As a result of mips build failures with the backport package, I am running a test build on a mips porter box to verify that the mips changes result in a successfully built package. Please advise on when I can proceed with upload. Regards, - -Roberto -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEz9ERzDttUsU/BH8iLNd4Xt2nsg8FAmGBdTEACgkQLNd4Xt2n sg86zA/9HB/c+D/pi9eUvh8hcw/TsQXSElpbncK0rCmIx1V7TFFPSuysVONXDjgk RMuz8ZVuNd5NRlhlgF45wNivL9TgOXCdARH60J+hdEXFgAgPbsRDkRNlMy6muMSY RJEmInlK+h3s6BDs8TpMw6DVjfKw1Tj7DAcGv/lZezyCoBZsnVGq6u/SSF+qHrRf 7oV0u5rc5Q8sS0hwe12LMzR8SSWiY+B4LFc7MALuFAuhcoroEjiLHqNceq4IP1mc zQcBPANUa7PE8KHVgyDWY6RgTJXWlQWP6macFyCUYvYjfc9gzIpXHgI/REocH1QY 9MyZ/lzqhQZbukcZS5kXJw6IelQmQ7kFQk4eLbAy03ipf5bMiI2zWPSvsCqTChra U87crvx1HnBg5yZsknWMBPocUsh9VYLH1WU+IZx6ZlH9N24Z+QU0mzmyLl834Vju XjnPY+VYJpU3jDzrlMrzRbmeFvqtDElycPJrFe9ZChajjM3ojJvkutWiaZu0Xc8s clyqcX9TDfeTM0P1g29uIJgYXfWJdsA21yFS4C1qlpQS7rEEux7f4cKRP/SWGJ/9 nPrtZFjD6W2QRUVaA50VEDLCYqnL82bb3wpPoz87xspJRBGh01P0WnlhmCUAC2iq ezG1ByC3q26cgjjs8Mi1WfUdrVjwQyLbOUeJECXAdp1wl4PnCyU= =XlZX -END PGP SIGNATURE- commit b3d946dff1649aeba70269aaf68c0323439559c8 (HEAD -> master) Author: Roberto C. Sánchez Date: Sat Oct 30 13:22:03 2021 -0400 Backport to buster. * Backport to buster. - Disable tests on (big endian) mips due to timeout (i.e., test runtime exceeds 10h). diff --git a/debian/changelog b/debian/changelog index c74466b96..1ffd5c65d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +llvm-toolchain-11 (1:11.0.1-2~deb10u1) buster; urgency=medium + + * Backport to buster. +- Disable tests on (big endian) mips due to timeout (i.e., test runtime + exceeds 10h). + + -- Roberto C. Sánchez Sat, 30 Oct 2021 13:14:49 -0400 + llvm-toolchain-11 (1:11.0.1-2~bpo10+1) buster-backports; urgency=medium * Rebuild for buster-backports. diff --git a/debian/clang-tools-11.install b/debian/clang-tools-11.install index 194e30f5d..a89d42227 100755 --- a/debian/clang-tools-11.install +++ b/debian/clang-tools-11.install @@ -32,7 +32,7 @@ usr/lib/llvm-11/bin/pp-trace usr/lib/llvm-11/bin/clang-move usr/lib/llvm-11/bin/clang-offload-wrapper -[!armel !armhf !ppc64el !hurd-any !s390x !powerpc !ppc64 !mipsel !mips64el !sparc64 !riscv64] usr/lib/llvm-11/lib/clang/11.0.1/bin/hwasan_symbolize +[!armel !armhf !ppc64el !hurd-any !s390x !powerpc !ppc64 !mips !mipsel !mips64el !sparc64 !riscv64] usr/lib/llvm-11/lib/clang/11.0.1/bin/hwasan_symbolize clang/tools/scan-build-11 usr/share/clang/ clang/tools/scan-build-py-11 usr/share/clang/ diff --git a/debian/rules b/debian/rules index 5aedc9b06..2532a80e2 100755 --- a/debian/rules +++ b/debian/rules @@ -196,7 +196,7 @@ endif endif # llvm tests timeout, disable it on mipsel -ifeq (mipsel,$(DEB_HOST_ARCH)) +ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel)) RUN_TEST=no endif
Bug#998338: transition: urdfdom
Control: tags -1 moreinfo On 2021-11-02 16:25:17, Jose Luis Rivero wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear release team: > > urdfdom library bumped the SOVERSION from 1.x to 3.x. I've run ratt in > the Open Robotics buildfarm: > https://build.osrfoundation.org/job/debian-ratt-builder/123/ > > 2021/10/29 11:58:02 Build results: > 2021/10/29 11:58:02 PASSED: ros-kdl-parser > 2021/10/29 11:58:02 PASSED: ros-urdf > 2021/10/29 11:58:02 PASSED: gazebo > 2021/10/29 11:58:02 PASSED: sdformat > 2021/10/29 11:58:02 PASSED: ros-rviz > 2021/10/29 11:58:02 PASSED: ros-robot-state-publisher > 2021/10/29 11:58:02 PASSED: ros-collada-urdf > 2021/10/29 11:58:02 PASSED: dart > > results seems fine. > > Ben file: > > title = "urdfdom"; > is_affected = .depends ~ > /\b(liburdfdom\-model\-state3\.0|liburdfdom\-model3\.0|liburdfdom\-sensor3\.0|liburdfdom\-tools3\.0|liburdfdom\-world3\.0|liburdfdom\-model|liburdfdom\-model\-state|liburdfdom\-sensor|liburdfdom\-tools|liburdfdom\-world)\b/ > is_good = .depends ~ > /\b(liburdfdom\-model\-state3\.0|liburdfdom\-model3\.0|liburdfdom\-sensor3\.0|liburdfdom\-tools3\.0|liburdfdom\-world3\.0)\b/ > is_bad = .depends ~ > /\b(liburdfdom\-model|liburdfdom\-model\-state|liburdfdom\-sensor|liburdfdom\-tools|liburdfdom\-world)\b.depends > ~ > /\b(liburdfdom\-model|liburdfdom\-model\-state|liburdfdom\-sensor|liburdfdom\-tools|liburdfdom\-world)\b// Why is liburdfom-tools being renamed? This packages does not contain a shared library. Cheers > > Could you please proceed with the transition? > Thanks! > -- Sebastian Ramacher
Processed: Re: Bug#998338: transition: urdfdom
Processing control commands: > tags -1 moreinfo Bug #998338 [release.debian.org] transition: urdfdom Added tag(s) moreinfo. -- 998338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998339: nmu: xmlsec1_1.2.32-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu [ nss maintainer X-Debbugs-Cc'ed ] Hi, nss 2:3.72-1 uploaded this morning did: nss (2:3.72-1) unstable; urgency=medium [...] * debian/libnss3-dev.links.in: Remove xulrunner-nss.pc. [...] Without any coordination whatsoever. This now results in stuff using libxmlsec1-dev (the nss variant) to FTBFS: $ pkg-config --libs xmlsec1-nss Package xulrunner-nss was not found in the pkg-config search path. Perhaps you should add the directory containing `xulrunner-nss.pc' to the PKG_CONFIG_PATH environment variable Package 'xulrunner-nss', required by 'xmlsec1-nss', not found cf. also the libreoffice autopkgtest which runs ./configure and needs the build-deps for this: https://ci.debian.net/data/autopkgtest/testing/amd64/libr/libreoffice/16373758/log.gz https://ci.debian.net/data/autopkgtest/testing/armhf/libr/libreoffice/16373879/log.gz https://ci.debian.net/data/autopkgtest/testing/i386/libr/libreoffice/16373931/log.gz https://ci.debian.net/data/autopkgtest/unstable/amd64/libr/libreoffice/16377878/log.gz https://ci.debian.net/data/autopkgtest/unstable/amd64/libr/libreoffice/16349711/log.gz Thankfully libxmlsec seems to write into that file what it detects at configure stage (in current sid nss.pc) and thus a bin-NMU should suffice. So please nmu xmlsec1_1.2.32-2 . ANY . unstable . -m "rebuild against nss 3.72-1 to fix xmlsec1-nss.pc" Regards, Rene
Bug#998338: transition: urdfdom
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear release team: urdfdom library bumped the SOVERSION from 1.x to 3.x. I've run ratt in the Open Robotics buildfarm: https://build.osrfoundation.org/job/debian-ratt-builder/123/ 2021/10/29 11:58:02 Build results: 2021/10/29 11:58:02 PASSED: ros-kdl-parser 2021/10/29 11:58:02 PASSED: ros-urdf 2021/10/29 11:58:02 PASSED: gazebo 2021/10/29 11:58:02 PASSED: sdformat 2021/10/29 11:58:02 PASSED: ros-rviz 2021/10/29 11:58:02 PASSED: ros-robot-state-publisher 2021/10/29 11:58:02 PASSED: ros-collada-urdf 2021/10/29 11:58:02 PASSED: dart results seems fine. Ben file: title = "urdfdom"; is_affected = .depends ~ /\b(liburdfdom\-model\-state3\.0|liburdfdom\-model3\.0|liburdfdom\-sensor3\.0|liburdfdom\-tools3\.0|liburdfdom\-world3\.0|liburdfdom\-model|liburdfdom\-model\-state|liburdfdom\-sensor|liburdfdom\-tools|liburdfdom\-world)\b/ is_good = .depends ~ /\b(liburdfdom\-model\-state3\.0|liburdfdom\-model3\.0|liburdfdom\-sensor3\.0|liburdfdom\-tools3\.0|liburdfdom\-world3\.0)\b/ is_bad = .depends ~ /\b(liburdfdom\-model|liburdfdom\-model\-state|liburdfdom\-sensor|liburdfdom\-tools|liburdfdom\-world)\b.depends ~ /\b(liburdfdom\-model|liburdfdom\-model\-state|liburdfdom\-sensor|liburdfdom\-tools|liburdfdom\-world)\b// Could you please proceed with the transition? Thanks!
Bug#998148: transition: libavif
Hi Boyuan > I plan to start another libavif transition as shown in the following Great, actually it would be great going straight to 0.9.3-2 with libaom v3 support, so that writing of avif files also works. Thanks a lot for your work on this. All the best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
