Bug#992358: marked as done (transition: pdal)
Your message dated Sun, 26 Sep 2021 06:21:50 +0200 with message-id and subject line Re: Bug#992358: transition: pdal has caused the Debian Bug report #992358, regarding transition: pdal 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.) -- 992358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992358 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: pkg-grass-de...@lists.alioth.debian.org Control: forwarded -1 https://release.debian.org/transitions/html/auto-pdal.html PDAL 2.3.0 has been in experimental for quite a while, I'd like to move it to unstable now. All reverse dependencies built successfully with the version in experimental as summarized below. Transition: pdal libpdal-base12 (2.2.0+ds-1+b1) -> libpdal-base13 (2.3.0+ds-1~exp1) libpdal-util12 (2.2.0+ds-1+b1) -> libpdal-util13 (2.3.0+ds-1~exp1) The status of the most recent rebuilds is as follows. cloudcompare (2.10.3-4) OK grass(7.8.5-1) OK paraview (5.9.0-2) OK Kind Regards, Bas --- End Message --- --- Begin Message --- On 9/8/21 10:14 AM, Sebastiaan Couwenberg wrote: > On 8/17/21 8:33 PM, Bas Couwenberg wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: transition >> X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org >> Control: forwarded -1 >> https://release.debian.org/transitions/html/auto-pdal.html >> >> PDAL 2.3.0 has been in experimental for quite a while, I'd like to move it >> to unstable now. >> >> All reverse dependencies built successfully with the version in experimental >> as summarized below. >> >> >> Transition: pdal >> >> libpdal-base12 (2.2.0+ds-1+b1) -> libpdal-base13 (2.3.0+ds-1~exp1) >> libpdal-util12 (2.2.0+ds-1+b1) -> libpdal-util13 (2.3.0+ds-1~exp1) >> >> The status of the most recent rebuilds is as follows. >> >> cloudcompare (2.10.3-4) OK >> grass(7.8.5-1) OK >> paraview (5.9.0-2) OK > > pdal (2.3.0+ds-1) is installed on all release architectures. paraview finally migrated to testing which allowed the old pdal packages to be removed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1--- End Message ---
NEW changes in stable-new
Processing changes file: hdf5_1.10.6+repack-4+deb11u1_mipsel-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: mutter_3.38.6-2~deb11u1_mipsel-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: mutter_3.38.6-2~deb11u1_mips64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_mips64el-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_mips64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: gnome-shell_3.38.6-1~deb11u1_mipsel-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_s390x-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gthumb_3.6.2-4+deb10u1_s390x-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_s390x-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_s390x-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gthumb_3.6.2-4+deb10u1_ppc64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_ppc64el-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_ppc64el-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_ppc64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_mipsel-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_i386-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gthumb_3.6.2-4+deb10u1_mips64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: linux_5.10.46-5_source.changes ACCEPT Processing changes file: linux_5.10.46-5_all-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_amd64-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_arm64-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_armel-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_armhf-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_i386-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_mips64el-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_mipsel-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_ppc64el-buildd.changes ACCEPT Processing changes file: linux_5.10.46-5_s390x-buildd.changes ACCEPT Processing changes file: flatpak_1.10.3-0+deb11u1_i386-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_i386-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_amd64-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gthumb_3.6.2-4+deb10u1_amd64-buildd.changes ACCEPT Processing changes file: gthumb_3.6.2-4+deb10u1_i386-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_amd64-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_amd64-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_armel-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_armhf-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gthumb_3.6.2-4+deb10u1_armhf-buildd.changes ACCEPT Processing changes file: gthumb_3.6.2-4+deb10u1_mips-buildd.changes ACCEPT Processing changes file: gthumb_3.6.2-4+deb10u1_mipsel-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_armel-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_armel-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_arm64-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: gthumb_3.6.2-4+deb10u1_all-buildd.changes ACCEPT Processing changes file: gthumb_3.6.2-4+deb10u1_arm64-buildd.changes ACCEPT Processing changes file: gthumb_3.6.2-4+deb10u1_armel-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_all-buildd.changes ACCEPT Processing changes file: flatpak_1.10.3-0+deb11u1_arm64-buildd.changes ACCEPT Processing changes file: flatpak_1.10.3-0+deb11u1_armhf-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_all-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_arm64-buildd.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_armhf-buildd.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_all-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: btrbk_0.27.1-1+deb10u1_all-buildd.changes ACCEPT
Processed: Re: Bug#993564: bullseye-pu: package dlt-viewer/2.21.2+dfsg-2+deb11u1
Processing control commands: > tags -1 -moreinfo Bug #993564 [release.debian.org] bullseye-pu: package dlt-viewer/2.21.2+dfsg-2+deb11u1 Removed tag(s) moreinfo. -- 993564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993564: bullseye-pu: package dlt-viewer/2.21.2+dfsg-2+deb11u1
control: tags -1 -moreinfo On Tue, 7 Sep 2021 14:40:34 +0100 Jonathan Wiltshire wrote: > Control: tag -1 confirmed moreinfo > > On Fri, Sep 03, 2021 at 08:48:41AM +0200, Gianfranco Costamagna wrote: > > Hello, for some reasons some headers in the -dev file were not > > installed, leading to an error in building external plugins. > > I opened RC: #993562 to track this issue, and I would like to fix also > > bullseye since the fix is trivial > > I'm fine with this change, but your changelog doesn't mention the bug > number that it fixes and you uploaded a binary amd64 package with it. I'm > not bothered by the binary package but I do want the changelog fixed, so we > may as well do both. > > You will receive a REJECT message from the archive. Once you have that, > please re-upload with the changelog updated and make it a source-only > upload. Then remove the wontfix tag from this request bug. > thanks! reuploaded Gianfranco
Bug#995075: bullseye-pu: package rsync/3.2.3-4+deb11u1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: pu Tags: bullseye X-Debbugs-Cc: samuel...@debian.org Severity: normal [ Reason ] I would like to update rsync based on issues we detected after releasing bullseye and on upstream commits done after 3.2.3 was released. Most of the changes are fixing regressions that showed up between the version we ship in buster and the one we ship in bullseye. The ones who don't fit into this category are either improvements to the docs or bugs that existed before the version we have in buster. [ Impact ] There are multiple changes here, but the most impactful ones are fixing regressions, thus the impact being that Debian users updating from buster to bullseye could have unexpected breakages when using rsync. [ Tests ] Some of the changes also contain their own tests, for the other ones I manually tested to confirm they're working fine (most of the bug reports from upstream had instructions on how to reproduce) [ Risks ] The risks are somewhat low as the changes were tested and they seem well contained in their domains. As in, any possible breakages would only affect those use cases and not extend to broader ones. [ 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 ] 1) Re-add upstream patch for --copy-devices, the --write-devices option is not fully equivalent (closes: #992215): https://bugs.debian.org/992215 This change will require me to update the release notes, which I'll do after the upload goes through: https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#rsync-parameter-deprecation 2) d/rsync.docs: Add NEWS.md file (previously named NEWS) (closes: #993697): Simple fix to a regression that happened when upstream renamed the file: https://bugs.debian.org/993697 3) d/p/fix_delay_updates.patch: New patch from upstream (closes: #992231): Pick upstream patch to fix a regression in the parameter --fix-delay, the patch has a low footprint and comes with a unit test: https://bugs.debian.org/992231 https://github.com/WayneD/rsync/issues/192 4) d/p/fix_mkpath.patch: New upstream patch to fix an edge case on --mkpath. Fix an issue when using rsync with mkpath when the folder exists and the file has a different name: https://github.com/WayneD/rsync/issues/96 5) d/p/fix_rsync-ssl_RSYNC_SSL_CERT_feature: New upstream patch to fix an edge case on rsync-ssl. Fix a shellscript's simple mistake: https://github.com/WayneD/rsync/commit/592c6bc3e5e93f36c2fdc0a491a9fb43a41cf688 6) d/p/fix_sparse_inplace.patch: New upstream patch to fix --sparse + --inplace options. Fix issue that happens when both --sparse and --inplace are used together: https://github.com/WayneD/rsync/issues/114 7) d/p/manpage_upstream_fixes.patch: Import multiple upstream patches to fix manpage. I merged multiple manpage fixes from upstream into a single patch, they should all be simple enough that no further details are needed. 8) d/p/update_rrsync_options.patch: New upstream patch to update rrsync options. rrsync was a bit outdated with regards to the options it supported, this simple patch updates it by adding support for the parameters mkpath, msgs2stderr and no-msgs2stderr. Note that the patch only lets rrsync receive those parameters, the support itself for those are already implemented in rsync. [ Other info ] Due to the nature of change number 1, I would appreciate it if we could ship this in time for 11.1. Thank you, -- Samuel Henrique rsync_3.2.3-4+deb11u1.debdiff Description: Binary data
NEW changes in stable-new
Processing changes file: flatpak_1.10.3-0+deb11u1_source.changes ACCEPT Processing changes file: gnome-shell_3.38.6-1~deb11u1_source.changes ACCEPT Processing changes file: mutter_3.38.6-2~deb11u1_source.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_source.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_all-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_amd64-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_arm64-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_armel-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_armhf-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_i386-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_mips64el-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_mipsel-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_ppc64el-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb11u1_s390x-buildd.changes ACCEPT Processing changes file: xen_4.14.3-1~deb11u1_amd64.changes ACCEPT Processing changes file: xen_4.14.3-1~deb11u1_arm64-buildd.changes ACCEPT Processing changes file: xen_4.14.3-1~deb11u1_armhf-buildd.changes ACCEPT Processing changes file: xen_4.14.3-1~deb11u1_i386-buildd.changes ACCEPT
Bug#995072: nmu: tripwire_2.4.3.7-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: 994...@bugs.debian.org tripwire now segfaults when it tries to read information about a file. Rebuilding the package from source makes the problem go away. The problem appeared to start after the libc6 update to 2.32. I suspect this is because tripwire is statically linked, and there are known issues with static linking with libc6 across version releases because the internal API to nsswitch modules changes. This is consistent with the pattern of segfaults, since it appears to happen around the point where tripwire would try to resolve a numeric UID or GID to a name. If this is correct, a binNMU against the latest libc6 should fix the problem. I have tested this by rebuilding the source package with no changes in a sid chroot and confirmed the resulting package works correctly. nmu tripwire_2.4.3.7-3 . ANY . unstable . -m "Rebuild with libc6 2.32"
NEW changes in oldstable-new
Processing changes file: btrbk_0.27.1-1+deb10u1_source.changes ACCEPT Processing changes file: gthumb_3.6.2-4+deb10u1_source.changes ACCEPT Processing changes file: modsecurity-crs_3.1.0-1+deb10u2_amd64.changes ACCEPT Processing changes file: nextcloud-desktop_2.5.1-3+deb10u2_source.changes ACCEPT Processing changes file: nextcloud-desktop_2.5.1-3+deb10u2_all-buildd.changes ACCEPT Processing changes file: nextcloud-desktop_2.5.1-3+deb10u2_amd64-buildd.changes ACCEPT Processing changes file: nextcloud-desktop_2.5.1-3+deb10u2_arm64-buildd.changes ACCEPT Processing changes file: nextcloud-desktop_2.5.1-3+deb10u2_armhf-buildd.changes ACCEPT Processing changes file: nextcloud-desktop_2.5.1-3+deb10u2_i386-buildd.changes ACCEPT Processing changes file: nextcloud-desktop_2.5.1-3+deb10u2_mipsel-buildd.changes ACCEPT Processing changes file: sabnzbdplus_2.3.6+dfsg-1+deb10u2_source.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_source.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_all-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_amd64-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_arm64-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_armel-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_armhf-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_i386-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_mips-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_mips64el-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_mipsel-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_ppc64el-buildd.changes ACCEPT Processing changes file: webkit2gtk_2.32.4-1~deb10u1_s390x-buildd.changes ACCEPT
Processed: mutter 3.38.6-2~deb11u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 993656 = bullseye pending Bug #993656 [release.debian.org] bullseye-pu: package mutter/3.38.6-2~deb11u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gnome-shell 3.38.6-1~deb11u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 993655 = bullseye pending Bug #993655 [release.debian.org] bullseye-pu: package gnome-shell/3.38.6-1~deb11u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993656: mutter 3.38.6-2~deb11u1 flagged for acceptance
package release.debian.org tags 993656 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: mutter Version: 3.38.6-2~deb11u1 Explanation: new upstream stable release; kms: Improve handling of common video modes that might exceed the possible bandwidth; ensure valid window texture size after viewport changes
Processed: flatpak 1.10.3-0+deb11u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 993396 = bullseye pending Bug #993396 [release.debian.org] bullseye-pu: package flatpak/1.10.3-0+deb11u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993655: gnome-shell 3.38.6-1~deb11u1 flagged for acceptance
package release.debian.org tags 993655 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: gnome-shell Version: 3.38.6-1~deb11u1 Explanation: new upstream stable release; fix freeze after cancelling (some) system-modal dialogs; fix word suggestions in on-screen keyboard; fix crashes
Bug#993396: flatpak 1.10.3-0+deb11u1 flagged for acceptance
package release.debian.org tags 993396 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: flatpak Version: 1.10.3-0+deb11u1 Explanation: new upstream stable release; don't inherit an unusual $XDG_RUNTIME_DIR setting into the sandbox
Processed: modsecurity-crs 3.1.0-1+deb10u2 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 992863 = buster pending Bug #992863 [release.debian.org] buster-pu: package modsecurity-crs/3.1.0-1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 992863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sabnzbdplus 2.3.6+dfsg-1+deb10u2 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 993034 = buster pending Bug #993034 [release.debian.org] buster-pu: package sabnzbdplus/2.3.6+dfsg-1+deb10u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: btrbk 0.27.1-1+deb10u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 993898 = buster pending Bug #993898 [release.debian.org] buster-pu: package btrbk/0.27.1-1+deb10u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993898: btrbk 0.27.1-1+deb10u1 flagged for acceptance
package release.debian.org tags 993898 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: btrbk Version: 0.27.1-1+deb10u1 Explanation: fix arbitrary code execution issue [CVE-2021-38173]
Bug#993228: gthumb 3.6.2-4+deb10u1 flagged for acceptance
package release.debian.org tags 993228 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: gthumb Version: 3.6.2-4+deb10u1 Explanation: fix heap-based buffer overflow issue [CVE-2019-20326]
Processed: gthumb 3.6.2-4+deb10u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 993228 = buster pending Bug #993228 [release.debian.org] buster-pu: package gthumb/3:3.6.2-4+deb10u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993034: sabnzbdplus 2.3.6+dfsg-1+deb10u2 flagged for acceptance
package release.debian.org tags 993034 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: sabnzbdplus Version: 2.3.6+dfsg-1+deb10u2 Explanation: prevent directory escape in renamer function [CVE-2021-29488]
Bug#992863: modsecurity-crs 3.1.0-1+deb10u2 flagged for acceptance
package release.debian.org tags 992863 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: modsecurity-crs Version: 3.1.0-1+deb10u2 Explanation: fix request body bypass issue [CVE-2021-35368]
Bug#995062: bullseye-pu: package speech-dispatcher/0.10.2-2+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
Hello,
[ Reason ]
We have recently noticed that one cannot choose between the various
mbrola speech synthesis voices in the orca screen reader.
This is not a regression from previous releases.
[ Impact ]
This prevents users from being able to switch between e.g. male/female
voices to efficiently mark different contents.
[ Tests ]
This was tested in a VM as well as on the end-user system where the bug
was noticed first.
[ Risks ]
The code is very simple: it just moves a single line of code, and adds a
few debugging prints to make sure this gets effect.
[ 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 ]
The bug comes from the fact that there are several ways to specify the
voice to be used: either through language + voice type, or precise voice
name. The second way is of course very precise, but unfortunately it was
coming first, and thus overwritten by the other ways. The change is just
to use the voice name last, so that one takes precedence over the other
(more generic) types.
diff -Nru speech-dispatcher-0.10.2/debian/changelog
speech-dispatcher-0.10.2/debian/changelog
--- speech-dispatcher-0.10.2/debian/changelog 2020-12-16 01:17:56.0
+0100
+++ speech-dispatcher-0.10.2/debian/changelog 2021-09-19 15:55:15.0
+0200
@@ -1,3 +1,10 @@
+speech-dispatcher (0.10.2-2+deb11u1) bullseye; urgency=medium
+
+ * patches/generic-set-voice-name: Fix setting voice name for the generic
+module.
+
+ -- Samuel Thibault Sun, 19 Sep 2021 15:55:15 +0200
+
speech-dispatcher (0.10.2-2) unstable; urgency=medium
* speech-dispatcher: Handle moving configuration file from main package to
diff -Nru speech-dispatcher-0.10.2/debian/patches/generic-set-voice-name
speech-dispatcher-0.10.2/debian/patches/generic-set-voice-name
--- speech-dispatcher-0.10.2/debian/patches/generic-set-voice-name
1970-01-01 01:00:00.0 +0100
+++ speech-dispatcher-0.10.2/debian/patches/generic-set-voice-name
2021-09-19 15:55:15.0 +0200
@@ -0,0 +1,41 @@
+commit 2aff49e3b8eb49dceb2c135025bc19cea6b0fd2e
+Author: Samuel Thibault
+Date: Sun Sep 19 15:52:31 2021 +0200
+
+generic: Set voice name after setting voice language and type
+
+E.g. when using various mbrola languages, we want to be able to specify
+a precise voice name. Setting the voice language/type after the voice
+name would override that choice.
+
+diff --git a/src/modules/generic.c b/src/modules/generic.c
+index 5072867d..b62cdb58 100644
+--- a/src/modules/generic.c
b/src/modules/generic.c
+@@ -205,9 +205,9 @@ int module_speak(const gchar * data, size_t bytes,
SPDMessageType msgtype)
+ DBG("Speaking when requested to write");
+ return 0;
+ }
+- UPDATE_STRING_PARAMETER(voice.name, generic_set_synthesis_voice);
+ UPDATE_STRING_PARAMETER(voice.language, generic_set_language);
+ UPDATE_PARAMETER(voice_type, generic_set_voice);
++ UPDATE_STRING_PARAMETER(voice.name, generic_set_synthesis_voice);
+ UPDATE_PARAMETER(punctuation_mode, generic_set_punct);
+ UPDATE_PARAMETER(pitch, generic_set_pitch);
+ UPDATE_PARAMETER(pitch_range, generic_set_pitch_range);
+@@ -707,6 +707,7 @@ void generic_set_language(char *lang)
+
+ void generic_set_voice(SPDVoiceType voice)
+ {
++ DBG("Setting voice type %d", voice);
+ assert(generic_msg_language);
+ generic_msg_voice_str =
+ module_getvoice(generic_msg_language->code, voice);
+@@ -717,6 +718,7 @@ void generic_set_voice(SPDVoiceType voice)
+
+ void generic_set_synthesis_voice(char *name)
+ {
++ DBG("Setting voice name %s (%s)", name, msg_settings.voice.name);
+ assert(msg_settings.voice.name);
+ if (module_existsvoice(msg_settings.voice.name))
+ generic_msg_voice_str = msg_settings.voice.name;
diff -Nru speech-dispatcher-0.10.2/debian/patches/series
speech-dispatcher-0.10.2/debian/patches/series
--- speech-dispatcher-0.10.2/debian/patches/series 2020-11-25
00:43:56.0 +0100
+++ speech-dispatcher-0.10.2/debian/patches/series 2021-09-19
15:55:15.0 +0200
@@ -1,3 +1,4 @@
doc-figures
systemd-debian
mbrola-paths
+generic-set-voice-name
Bug#994560: Bug#995032: GNOME components segfault as a result of libffi transition
On 2021-09-25 14:55:23 +0100, Simon McVittie wrote: > On Sat, 25 Sep 2021 at 15:01:46 +0200, Sebastian Ramacher wrote: > > Regardless of future transitions of libffi, if glib and the > > introspection ecosystems are closely tied to the the libffi ABI, the > > affected packages need to express that with the proper dependencies. > > It's not that they are closely tied to any specific libffi ABI - to the > best of my knowledge, they're all fine with any reasonable version of > libffi, old or new. The problem is that gobject-introspection and all > users of girffi.h[1] (gjs, pygobject, etc.) all need to be using the > *same* libffi, because girffi.h has functions that return pointers to ffi > types or take pointers to ffi types as parameters. Sorry, that's not what I meant. they are tightly coupled in the sense that the whole gobject-introspection ecosystem needs to use the same libffi version. It's the same as boost and icu where also icu's ABI leaks into boost's ABI (via some icu structs that are passed around). Hence everything that uses Boost.Regex needs also be tracked in icu transitions. To track that, libboost-regexX provides libboost-regexX-icuY and reverse dependencies have dependencies on libboost-regexX-icuY. For libgirepository1.0-1 that would mean that libgirepository1.0-1 provides libgirepository1.0-1-ffiX and symbols from girffi that depend on the specific libffi ABI then declare in the symbols files that dependencies on libgirepository1.0-1-ffiX need to be generated. Cheers > > I don't know whether it is important that glib2.0 and gobject-introspection > are *also* using the same libffi; in the past we assumed that they should, > but it is probably not critical. > > [1] https://codesearch.debian.net/search?q=girffi.h=1 > > smcv -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#994560: Bug#995032: GNOME components segfault as a result of libffi transition
On Sat, 25 Sep 2021 at 15:01:46 +0200, Sebastian Ramacher wrote: > Regardless of future transitions of libffi, if glib and the > introspection ecosystems are closely tied to the the libffi ABI, the > affected packages need to express that with the proper dependencies. It's not that they are closely tied to any specific libffi ABI - to the best of my knowledge, they're all fine with any reasonable version of libffi, old or new. The problem is that gobject-introspection and all users of girffi.h[1] (gjs, pygobject, etc.) all need to be using the *same* libffi, because girffi.h has functions that return pointers to ffi types or take pointers to ffi types as parameters. I don't know whether it is important that glib2.0 and gobject-introspection are *also* using the same libffi; in the past we assumed that they should, but it is probably not critical. [1] https://codesearch.debian.net/search?q=girffi.h=1 smcv
Bug#994560: Bug#995032: GNOME components segfault as a result of libffi transition
On 2021-09-25 11:49:39 +0100, Simon McVittie wrote: > Control: retitle 995032 GNOME components segfault as a result of libffi > transition > > On Sat, 25 Sep 2021 at 03:48:20 -0400, Jeremy Bicha wrote: > > On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > > > The problem is not gnome-shell. It is the gobject-introspection. > > > After downgrade this packages from 1.70.0-1+b1 to 1.70.0-1 it works > > > again. > > > > gobject-introspection was rebuilt as part of the libffi transition. > > (That's where the +b1 part of the version name comes from.) The > > transition is still in progress. Maybe the problem is that you didn't > > have the rebuilt gjs installed? > > > > The rebuilt gjs is version 1.68.4-1+b1 > > > > Here's the list of other packages involved in the transition: > > https://release.debian.org/transitions/html/auto-libffi.html > > Last time we had a libffi transition, in early 2020, we ended up > sprinkling versioned Breaks throughout GNOME to force the whole system > to be either "old libffi" or "new libffi". This is because some GNOME > components, notably gobject-introspection, have libffi data structures > in their public API, so in partial upgrades we get one library passing an > old-libffi data structure to another library that expects a new-libffi > data structure, and crashes. > > See the gobject-introspection 1.62.0-4 and -5 changelogs for part of what > we had to do to fix this. > > If libffi is going to continue to break ABI somewhat regularly, then I > think we are going to need a more systematic way to prevent broken partial > upgrades, and it would be very helpful for the libffi maintainer and the > release team to keep this failure mode in mind when allocating transition > slots (for example doing libffi transitions when there is not a new major > version of GLib trying to migrate, as there is at the moment). Regardless of future transitions of libffi, if glib and the introspection ecosystems are closely tied to the the libffi ABI, the affected packages need to express that with the proper dependencies. We have the same situation with boost and icu and boost and python3.X. If you implement a similar solution to that in boost, this would also allows us to track this via ben in a future libffi transition. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#995055: transition: glew
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: debian-de...@lists.debian.org This transition is triggered by an SONAME change upstream. It does not appear to have any API transition though, and seems to cause no glew-related failures. Ben file: title = "glew"; is_affected = .depends ~ "libglew2.1" | .depends ~ "libglew2.2"; is_good = .depends ~ "libglew2.2"; is_bad = .depends ~ "libglew2.1"; I've rebuilt all dependencies, with a number of unrelated FTBFS: Bugs have been submitted against all FTBFS. glew OK info-beamer : : change bd libglew1.5-dev -> libglew-dev OK phlipple: change bd libglew1.5-dev -> libglew-dev OK pymol: change bd libglew1.5-dev -> libglew-dev OK rlvm: change bd libglew1.5-dev -> libglew-dev OK asymptote: OK avogarolibs: OK ball: FTBFS (#994480) unrelated (glibc/ rpc header change) bino: OK blastem: OK blender: OK bzflag: OK casparcg-server (sid only): FTBFS (#947518) colmap: OK colobot: OK compiz-plugins-experimental: OK darkradiant: OK ddnet: OK dreamchess: OK endless-sky: OK fife: OK freeorion: OK frogatto (contrib): OK gambas3: OK gource: OK hugin: OK hyperrogue: OK k3d (sid only): FTBFS (python2 issues) kicad: OK limesuite: OK logstalgia: OK mediastreamer2: (FTFBS with gcc-11), OK megaglest : OK mesa-demos: OK mupen64plus-video-z64: OK mygui: OK open3d: OK openclonk: opencsg: OK openctm: OK openmsx:: OK otb: OK paraview: OK qutemol: OK rbdoom3bfg: OK renpy (sid only):FTBFS - needs python-sphinx rss-glx: OK scorched3d: OK slic3r-prusa OK slop: FTBFS (#994824) unrelated sludge: OK sofa-framework: FTBFS (#875184): QT4 removed spring: OK supertux: OK supertuxkart: OK trigger-rally: OK tulip: OK vice (contrib): FTBFS #994835 (jpeg support missing) vtk7: OK vtk9: OK warzone2100: OK widelands: OK cegui-mk2: OK meshlab; OK openscad: FTBFS (#994937) CGAL-related ? pcl:OK
Bug#994560: Bug#995032: GNOME components segfault as a result of libffi transition
Control: retitle 995032 GNOME components segfault as a result of libffi transition On Sat, 25 Sep 2021 at 03:48:20 -0400, Jeremy Bicha wrote: > On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > > The problem is not gnome-shell. It is the gobject-introspection. > > After downgrade this packages from 1.70.0-1+b1 to 1.70.0-1 it works > > again. > > gobject-introspection was rebuilt as part of the libffi transition. > (That's where the +b1 part of the version name comes from.) The > transition is still in progress. Maybe the problem is that you didn't > have the rebuilt gjs installed? > > The rebuilt gjs is version 1.68.4-1+b1 > > Here's the list of other packages involved in the transition: > https://release.debian.org/transitions/html/auto-libffi.html Last time we had a libffi transition, in early 2020, we ended up sprinkling versioned Breaks throughout GNOME to force the whole system to be either "old libffi" or "new libffi". This is because some GNOME components, notably gobject-introspection, have libffi data structures in their public API, so in partial upgrades we get one library passing an old-libffi data structure to another library that expects a new-libffi data structure, and crashes. See the gobject-introspection 1.62.0-4 and -5 changelogs for part of what we had to do to fix this. If libffi is going to continue to break ABI somewhat regularly, then I think we are going to need a more systematic way to prevent broken partial upgrades, and it would be very helpful for the libffi maintainer and the release team to keep this failure mode in mind when allocating transition slots (for example doing libffi transitions when there is not a new major version of GLib trying to migrate, as there is at the moment). smcv
Processed: python3.9: FTBFS on i386: test timeout
Processing control commands: > block 994560 by -1 Bug #994560 [release.debian.org] transition: libffi 994560 was blocked by: 995045 995007 991096 995036 995044 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995051 -- 994560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994560 995051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)
On Fri, Aug 27, 2021 at 10:26:39PM +0200, Paul Gevers wrote: > Hi, > > Sorry my previous message was weird. > > On 27-08-2021 22:11, Paul Gevers wrote: > > On 27-08-2021 21:58, Antonio Terceiro wrote: > >> One thing that happens when you do this type of change without > >> coordination is that all CI pipelines on unstable where rabbitmq-server > >> is installed are now broken. For example all merge requests against > >> debci at the moment have their tests in "failed" status. This creates > >> unnecessary noise for a lot of people. > > > > rabbitmq-server already got an update, so unstable should be fine (if > > not, shout (or better, file bugs)). I expect you mean testing, as I > > think that the point is that erlang already migrated before the issue > > was detected, otherwise an RC bug would have prevented the migration. > > > > That's why it was suggested earlier that rabbitmq-server should grow an > > autopkgtest as that have would prevented the migration. > > What I should have said: > we could have prevented migration of erlang until the reverse > dependencies were ready by having an RC bug on erlang. That would have > been totally appropriate if it would have lasted an reasonable time. I > *think* rabbitmq-server has problems migrating now *because* erlang > migrated, but that should clear up once the references are tested again. > However, it *also* has issues with being uninstallable. FWIW, I just did that: I made a new rabbitmq-server upload adding a superficial autopkgtest to rabbitmq-server that just checks if the service is running after installation. This should avoid testing being broken because erlang migrated before rabbitmq-server has been fixed. signature.asc Description: PGP signature
Processed: block 994560 with 995007
Processing commands for cont...@bugs.debian.org: > block 994560 with 995007 Bug #994560 [release.debian.org] transition: libffi 994560 was blocked by: 995044 995045 991096 995036 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995007 > thanks Stopping processing here. Please contact me if you need assistance. -- 994560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 991096 is serious, tagging 991096, block 994560 with 991096 995044 995036 995045
Processing commands for cont...@bugs.debian.org: > severity 991096 serious Bug #991096 [src:llvm-toolchain-9] fix ftbfs with linux 5.11 Severity set to 'serious' from 'important' > tags 991096 + ftbfs Bug #991096 [src:llvm-toolchain-9] fix ftbfs with linux 5.11 Added tag(s) ftbfs. > block 994560 with 991096 995044 995036 995045 Bug #994560 [release.debian.org] transition: libffi 994560 was not blocked by any bugs. 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995044, 995036, 991096, and 995045 > thanks Stopping processing here. Please contact me if you need assistance. -- 991096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991096 994560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
