Bug#987149: xscreensaver: allows starting external programs with cap_net_raw
Hi Tormod, On Mon, Jun 14, 2021 at 11:43:44PM +0200, Tormod Volden wrote: > This issue is marked as affecting 5.42+dfsg1-1 in buster (and even > stretch) in our CVE tracker, however the set_cap action was first > added in 5.44+dfsg1-1. > > https://security-tracker.debian.org/tracker/CVE-2021-31523 Thanks! Regards, Salvatore
Bug#989508: xscreensaver: Disconnecting a video output can cause XScreenSaver to crash and unlock
Hi Tormod, On Mon, Jun 14, 2021 at 11:38:34PM +0200, Tormod Volden wrote: > This issue is marked as affecting 5.42+dfsg1-1 in buster (and even > stretch) in our CVE tracker, however the openwall report says: > > "The issue affects only XScreenSaver version 5.45. Versions 5.44 and > older, as well as 6.00, are not affected." Correct, see as well my initial bugreport. Though on checking the code it was not immediately clear (to me) what makes earlier version not affected. Thus the general rule for us is, to err on the wrong side and have something marked as affected which is not, rather the other way around. SuSE seem to have similar issue, cf. https://bugzilla.suse.com/show_bug.cgi?id=1186918#c1 Do you have any more insights here? Regards, Salvatore
Processed: Re: Bug#989872: thunderbird-dbgsym: uninstallable cruft package in buster
Processing control commands: > reassign -1 src:thunderbird Bug #989872 [thunderbird-dbgsym] thunderbird-dbgsym: uninstallable cruft package in buster Warning: Unknown package 'thunderbird-dbgsym' Bug reassigned from package 'thunderbird-dbgsym' to 'src:thunderbird'. No longer marked as found in versions thunderbird/1:60.9.0-1~deb10u1. Ignoring request to alter fixed versions of bug #989872 to the same values previously set -- 989872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989872: thunderbird-dbgsym: uninstallable cruft package in buster
Control: reassign -1 src:thunderbird On Ma, 15 iun 21, 01:41:12, Andreas Beckmann wrote: > Package: thunderbird-dbgsym > Version: 1:60.9.0-1~deb10u1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > thunderbird-dbgsym is a cruft package still sitting in buster-debug > while thunderbird is already at version 1:78.6.0-1~deb10u1 (without a > corresponding -dbgsym package). Apparently the BTS doesn't know about -debug, which means this bug is currently assigned against an "inexistent" package. Reassigning to src:thunderbird instead. Kind regards, Andrei -- Looking after bugs assigned to unknown or inexistent packages signature.asc Description: PGP signature
Bug#968897: src:pylint should provide a pylint3 transitional package
On Mon, Jun 14, 2021 at 10:39 AM Hideki Yamane wrote: > > control: tags -1 +patch > > > On Tue, 1 Jun 2021 22:49:18 +0300 Adrian Bunk wrote: > > Provides is good for fulfilling dependencies, but won't for an upgrade > > to the renamed package. > > Okay, then add transitional dummy package for it as below. thanks, i've applied and uploaded your change as-is; next time, please open an MR on salsa Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Processed: user debian...@lists.debian.org, usertagging 936954, found 986097 in 8.0.7-1, found 924226 in 2.15.2 ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 936954 piuparts Usertags were: piuparts. Usertags are now: piuparts. > found 986097 8.0.7-1 Bug #986097 [libphp8.0-embed] libphp8.0-embed: unusual unversioned soname: libphp.so Marked as found in versions php8.0/8.0.7-1. > found 924226 2.15.2 Bug #924226 [debci-worker] debci-worker: cronjob exits with error after package removal Marked as found in versions debci/2.15.2. > usertags 945254 piuparts There were no usertags set. Usertags are now: piuparts. > affects 945254 + python3-libzfs Bug #945254 [src:py-libzfs] py-libzfs: FTBFS against python3.8 Added indication that 945254 affects python3-libzfs > thanks Stopping processing here. Please contact me if you need assistance. -- 924226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924226 945254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945254 986097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989880: cpl-plugin-muse-calib: muse-kit-2.6*.tar.gz no longer downloadable
Package: cpl-plugin-muse-calib Version: 2.6+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-muse-calib (2.6+dfsg-1) ... --2021-06-14 22:38:06-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.6.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/muse ... done. ==> SIZE muse-kit-2.6.tar.gz ... done. ==> PASV ... done.==> RETR muse-kit-2.6.tar.gz ... No such file 'muse-kit-2.6.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2021-06-14 22:38:06-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.6-1.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/muse ... done. ==> SIZE muse-kit-2.6-1.tar.gz ... done. ==> PASV ... done.==> RETR muse-kit-2.6-1.tar.gz ... No such file 'muse-kit-2.6-1.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now [...] cheers, Andreas cpl-plugin-muse-calib_2.6+dfsg-1.log.gz Description: application/gzip
Bug#989879: sane-utils: fails to purge: post-removal script subprocess returned error exit status 1
Package: sane-utils Version: 1.0.32-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge. According to policy 7.2 you cannot rely on the depends being available during purge, only the essential packages are available for sure. >From the attached log (scroll to the bottom...): Purging configuration files for sane-utils (1.0.32-1) ... dpkg: error processing package sane-utils (--purge): installed sane-utils package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: sane-utils After injecting 'set -x' into the postrm script: Purging configuration files for sane-utils (1.0.32-1) ... + set -e + [ purge = purge ] + pathfind update-inetd + OLDIFS= + IFS=: + [ -x /usr/local/sbin/update-inetd ] + [ -x /usr/local/bin/update-inetd ] + [ -x /usr/sbin/update-inetd ] + [ -x /usr/bin/update-inetd ] + [ -x /sbin/update-inetd ] + [ -x /bin/update-inetd ] + IFS= + return 1 dpkg: error processing package sane-utils (--purge): installed sane-utils package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: sane-utils cheers, Andreas sane-utils_1.0.32-1.log.gz Description: application/gzip
Bug#989878: openstack-dashboard: fails to remove: rm: cannot remove '/usr/lib/python3/dist-packages/openstack_dashboard/local/enabled': Is a directory
Package: openstack-dashboard Version: 3:19.2.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing openstack-dashboard (3:19.2.0-3) ... rm: cannot remove '/usr/lib/python3/dist-packages/openstack_dashboard/local/enabled': Is a directory dpkg: error processing package openstack-dashboard (--remove): installed openstack-dashboard package pre-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: openstack-dashboard Processing was halted because there were too many errors. This was observed after an upgrade from sid to experimental. cheers, Andreas openstack-dashboard_3:19.2.0-3.log.gz Description: application/gzip
Bug#989876: syncplay-common,syncplay-server: missing Breaks+Replaces: syncplay (<< 1.6.7+repack1-7)
Package: syncplay-common,syncplay-server Version: 1.6.8+repack1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + syncplay Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package syncplay-common. (Reading database ... (Reading database ... 13126 files and directories currently installed.) Preparing to unpack .../syncplay-common_1.6.8+repack1-1_all.deb ... Unpacking syncplay-common (1.6.8+repack1-1) ... dpkg: error processing archive /var/cache/apt/archives/syncplay-common_1.6.8+repack1-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/syncplay/__init__.py', which is also in package syncplay 1.6.7+repack1-5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../syncplay_1.6.8+repack1-1_all.deb ... Unpacking syncplay (1.6.8+repack1-1) over (1.6.7+repack1-5) ... Errors were encountered while processing: /var/cache/apt/archives/syncplay-common_1.6.8+repack1-1_all.deb The existing Breaks+Replaces: syncplay (<= 1.6.7) are incorrectly versioned since the package split happened in 1.6.7+repack1-7 cheers, Andreas syncplay_1.6.8+repack1-1.log.gz Description: application/gzip
Processed: syncplay-common,syncplay-server: missing Breaks+Replaces: syncplay (<< 1.6.7+repack1-7)
Processing control commands: > affects -1 + syncplay Bug #989876 [syncplay-common,syncplay-server] syncplay-common,syncplay-server: missing Breaks+Replaces: syncplay (<< 1.6.7+repack1-7) Added indication that 989876 affects syncplay -- 989876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pulseaudio-utils: missing Breaks+Replaces: pulseaudio (<< 14.99)
Processing control commands: > affects -1 + pulseaudio Bug #989875 [pulseaudio-utils] pulseaudio-utils: missing Breaks+Replaces: pulseaudio (<< 14.99) Added indication that 989875 affects pulseaudio -- 989875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989875: pulseaudio-utils: missing Breaks+Replaces: pulseaudio (<< 14.99)
Package: pulseaudio-utils Version: 14.99.1+dfsg1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + pulseaudio Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libpulsedsp_14.99.1+dfsg1-2_amd64.deb ... Unpacking libpulsedsp:amd64 (14.99.1+dfsg1-2) over (14.2-2) ... Preparing to unpack .../pulseaudio-utils_14.99.1+dfsg1-2_amd64.deb ... Unpacking pulseaudio-utils (14.99.1+dfsg1-2) over (14.2-2) ... dpkg: error processing archive /var/cache/apt/archives/pulseaudio-utils_14.99.1+dfsg1-2_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which is also in package pulseaudio 14.2-2 Preparing to unpack .../pulseaudio_14.99.1+dfsg1-2_amd64.deb ... Unpacking pulseaudio (14.99.1+dfsg1-2) over (14.2-2) ... Preparing to unpack .../libpulse0_14.99.1+dfsg1-2_amd64.deb ... Unpacking libpulse0:amd64 (14.99.1+dfsg1-2) over (14.2-2) ... Errors were encountered while processing: /var/cache/apt/archives/pulseaudio-utils_14.99.1+dfsg1-2_amd64.deb cheers, Andreas pulseaudio_14.99.1+dfsg1-2.log.gz Description: application/gzip
Bug#989873: pcp: FTBFS: pcp-export-pcp2xlsx is missing files
Source: pcp Version: 5.3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian...@lists.debian.org Usertags: piuparts Hi, pcp FTBFS everywhere: https://buildd.debian.org/status/package.php?p=pcp=unstable dh_install -a --sourcedir=debian/pcp dh_install: warning: Cannot find (any matches for) "usr/bin/pcp2xlsx" (tried in debian/pcp, debian/tmp) dh_install: warning: pcp-export-pcp2xlsx missing files: usr/bin/pcp2xlsx dh_install: warning: Cannot find (any matches for) "usr/share/bash-completion/completions/pcp2xlsx" (tried in debian/pcp, debian/tmp) dh_install: warning: pcp-export-pcp2xlsx missing files: usr/share/bash-completion/completions/pcp2xlsx dh_install: warning: Cannot find (any matches for) "usr/share/man/man1/pcp2xlsx.1.gz" (tried in debian/pcp, debian/tmp) dh_install: warning: pcp-export-pcp2xlsx missing files: usr/share/man/man1/pcp2xlsx.1.gz dh_install: error: missing files, aborting Andreas
Bug#989872: thunderbird-dbgsym: uninstallable cruft package in buster
Package: thunderbird-dbgsym Version: 1:60.9.0-1~deb10u1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts thunderbird-dbgsym is a cruft package still sitting in buster-debug while thunderbird is already at version 1:78.6.0-1~deb10u1 (without a corresponding -dbgsym package). Andreas
Bug#989870: libwine-development,libwine-development-dev: both ship usr/lib/x86_64-linux-gnu/wine-development/libwine.so
Package: libwine-development,libwine-development-dev Version: 5.22+repack-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package libwine-development:amd64. Preparing to unpack .../98-libwine-development_5.22+repack-1_amd64.deb ... Unpacking libwine-development:amd64 (5.22+repack-1) ... Selecting previously unselected package libwine-development-dev. Preparing to unpack .../99-libwine-development-dev_5.22+repack-1_amd64.deb ... Unpacking libwine-development-dev (5.22+repack-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-5EjfOJ/99-libwine-development-dev_5.22+repack-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/wine-development/libwine.so', which is also in package libwine-development:amd64 5.22+repack-1 Errors were encountered while processing: /tmp/apt-dpkg-install-5EjfOJ/99-libwine-development-dev_5.22+repack-1_amd64.deb cheers, Andreas libwine-development-dev_5.22+repack-1.log.gz Description: application/gzip
Bug#989852: xorg-server-source: Cannot build X from provided source tarball
Package: src:xorg-server Version: 2:1.20.4-1+deb10u3 Severity: serious Control: tags -1 patch Hi, the source tarball of xorg-server shipped via bin:pkg xorg-server-source in Debian buster is in some broken state. The reason for this is that quilt patches don't get applied before the tarball gets created during package build. Additionally, the xorg-server src:pkg is in some weird patch management state (which probably is not fixable for buster): it applies some changes to the upstream code via a .diff.gz file (source format 1.0) and other patches via quilt. Even more broken the source tarball becomes because of some changes being applied to xkb/xkb.c via the diff.gz file, some others via debian/patches/09_Correct-bounds-checking-in-XkbSetNames.patch. So, at the moment my 3rd party project depending on the availability of the xorg-server-source package is not buildable. As a work around, I provided a fixed 2:1.20.4-1+deb10u3.1 version in a 3rd party repo outside of Debian. See the attached .debdiff that fixes the FTBFS issue, but that also excludes the tarball from itself (#930405) and also applies some reproducibility fixes. Please get this change into buster. If help is required, I am happy to do the upload. Thanks. The attached fix probably also needs forward porting for the quilt push/pop -a part. In my changelog (in the .debdiff), I don't close #930405, so that should be added when uploading. Thanks! Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de diff -u xorg-server-1.20.4/debian/changelog xorg-server-1.20.4/debian/changelog --- xorg-server-1.20.4/debian/changelog +++ xorg-server-1.20.4/debian/changelog @@ -1,3 +1,17 @@ +xorg-server (2:1.20.4-1+deb10u3.1) UNRELEASED; urgency=medium + + [ Mike Gabriel ] + * Non-maintainer upload. + * Apply quilt patches before generating xorg-server-source tarball. +Unapply patches again after source tarball has been created (to +not confuse the rest of the build). + + [ Sven Joachim ] + * Exlude the build-source directory from xorg-server.tar.xz. + * Fix reproducibility problems in the xorg-server-source package. + + -- Mike Gabriel Mon, 14 Jun 2021 11:56:53 +0200 + xorg-server (2:1.20.4-1+deb10u3) buster-security; urgency=high * Fix XChangeFeedbackControl() request underflow (CVE-2021-3472) diff -u xorg-server-1.20.4/debian/rules xorg-server-1.20.4/debian/rules --- xorg-server-1.20.4/debian/rules +++ xorg-server-1.20.4/debian/rules @@ -8,14 +8,21 @@ dh $@ --with quilt,autoreconf --parallel build-source-stamp: + QUILT_PATCHES=debian/patches quilt push -a mkdir -p build-source tar \ --owner=0 --group=0 \ ---transform 's,^,xorg-server/,' \ + --transform 's,^,xorg-server/,' \ --exclude=debian \ --exclude=autom4te.cache \ --cf - * | xz > build-source/xorg-server.tar.xz + --exclude=build-source \ + --sort=name \ + --mtime=@$(SOURCE_DATE_EPOCH) \ + --clamp-mtime \ + --mode=u+rw,go+r,go-w,a-s \ + -cf - * | xz > build-source/xorg-server.tar.xz >$@ + QUILT_PATCHES=debian/patches quilt pop -a override_dh_auto_configure: dh_auto_configure --builddirectory=debian/build/main -- \ pgpBPSeK1QB1e.pgp Description: Digitale PGP-Signatur
Bug#989111: libopenmpi-dev: broken symlinks: /usr/lib/i386-linux-gnu/openmpi/lib/libmca_common_{ofi,ompio}.so
On 26/05/2021 15.49, Alastair McKinstry wrote: This appears to be limited to i386/ 32-bit systems. They're shipped elsewhere. No, same on 64-bit: 0m50.1s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmca_common_ofi.so -> libmca_common_ofi.so.10.0.1 (libopenmpi-dev:amd64) /usr/lib/x86_64-linux-gnu/openmpi/lib/libmca_common_ompio.so -> libmca_common_ompio.so.41.29.1 (libopenmpi-dev:amd64) Andreas
Bug#944751: marked as done (trousers: Migrate to tpm-udev)
Your message dated Mon, 14 Jun 2021 22:49:26 + with message-id and subject line Bug#944751: fixed in trousers 0.3.14+fixed1-1.2 has caused the Debian Bug report #944751, regarding trousers: Migrate to tpm-udev 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.) -- 944751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trousers Severity: normal Dear Maintainer, As part of bug 918973 there was a request to create a common udev rules package for TPM 1.2 and TPM2.0 tpm* devices. This was created as the package 'tpm-udev' which is now in the Debian archive. 'tpm2-tss' now uses this to provide udev rules. Can you please transition trousers to also use this new package to provide udev rules so that users don't have duplicated rule sets? -- System Information: Debian Release: buster/sid APT prefers eoan-updates APT policy: (500, 'eoan-updates'), (500, 'eoan-security'), (500, 'eoan'), (100, 'eoan-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0+ (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: trousers Source-Version: 0.3.14+fixed1-1.2 Done: Laurent Bigonville We believe that the bug you reported is fixed in the latest version of trousers, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated trousers 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: SHA256 Format: 1.8 Date: Tue, 15 Jun 2021 00:29:18 +0200 Source: trousers Architecture: source Version: 0.3.14+fixed1-1.2 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier Changed-By: Laurent Bigonville Closes: 787244 889491 944751 Changes: trousers (0.3.14+fixed1-1.2) unstable; urgency=medium . * Non-maintainer upload. * Migrate to tpm-udev package, do not ship the udev rule file, create the user or /var/lib/tpm directory anymore (Closes: #787244, #889491, #944751) * debian/trousers.prerm: Remove migration code path that predates Jessie Checksums-Sha1: 8543f7164082744b8b0276ab7eade50d19268294 1693 trousers_0.3.14+fixed1-1.2.dsc 31423c9ad08b6dab23f2fbfdbffeb29b8b1b611a 16028 trousers_0.3.14+fixed1-1.2.debian.tar.xz 2267527e32905b0e83cfdd188c3f30820af82b5a 5797 trousers_0.3.14+fixed1-1.2_source.buildinfo Checksums-Sha256: e41cfb2a612d47927df643450c1224a9166c4b562f55cd2013595c49a7882abd 1693 trousers_0.3.14+fixed1-1.2.dsc 2a69955aea65dd1e793b354e0e75b80510e5e010ba0914bf6d69db7cb76d56c0 16028 trousers_0.3.14+fixed1-1.2.debian.tar.xz 1274d72206b387cd0eab323ba2db5add85561b6716108037fb15c8932f11e392 5797 trousers_0.3.14+fixed1-1.2_source.buildinfo Files: 24d9c742f8e97414505fa7c74b8b635b 1693 admin optional trousers_0.3.14+fixed1-1.2.dsc 24412d9814356e541a8d8789948d08aa 16028 admin optional trousers_0.3.14+fixed1-1.2.debian.tar.xz 4df8587bd6fe15df43c623926f6d29f3 5797 admin optional trousers_0.3.14+fixed1-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAmDH2FYRHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9XXSgf+JFdQeXjbsTCFSQK87G80LdlVY1nKDI+J 9xh89h4T7CEeCE1Hxd2G2nYNZCsFjmd9NuHtfYtVZDIvdakPYDbavf34vb0MjcTH BQA4X03sNJFlaWdHgSrPNmnJXqOt8s/xF+PZaPngBSTutmZbHJ34w7Ja3PvTpe0w 48zumoIEqOMRbtdBTPPqCVNeC5t/4bBKsX8VKQ68fDbXcXVC6FUVWM5NQOyT5/n3 fkDYS+wh3B8SgJkATKCgDTxrzuksI005cXCTlDI/0hemYYRWk2aIPN9dSPn0zbuA c3vU/ut8IracFQY/RrcJNQ95lILBTEir3O0csaFWLUtHr+H17w7+Zw== =wwAB -END PGP SIGNATURE End Message ---
Bug#980466: cervisia: missing dependency on kinit package
Dear Hideki, > I'd prepare tiny patch for this issue as below. Thanks a lot for the NMU, much appreciated! 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
Bug#989843: thunderbird: Problem loading page: NS_ERROR_NET_INADEQUATE_SECURITY
Package: thunderbird Version: 1:78.11.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, Since the update to 78.11.0 Thunderbird cannot load various webpages. To reproduce the error, try to do a search in the Add-ons Manager (type something in the search box and press Enter). The error message is "The website tried to negotiate an inadequate level of security. ... Error code: NS_ERROR_NET_INADEQUATE_SECURITY" There is perhaps a more useful error message in the error console: addons.thunderbird.net : server does not support RFC 5746, see CVE-2009-3555 The problem also appears when trying to load other pages or using certain add-ons (for example, calendar-google-provider). The problem goes away if one sets network.http.spdy.enforce-tls-profile to false in the preferences. This makes me think that there is an issue with the TLS library. Cheers, Todor -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thunderbird depends on: ii debianutils 4.11.2 ii fontconfig 2.13.1-4.2 ii libatk1.0-0 2.36.0-2 ii libbotan-2-172.17.3+dfsg-2 ii libbz2-1.0 1.0.8-4 ii libc62.31-12 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-2 0.110-6 ii libevent-2.1-7 2.1.12-stable-1 ii libffi7 3.3-6 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4 ii libicu67 67.1-6 ii libjson-c5 0.15-2 ii libnspr4 2:4.29-1 ii libnss3 2:3.61-1 ii libpango-1.0-0 1.46.2-3 ii libstdc++6 10.2.1-6 ii libvpx6 1.9.0-1 ii libx11-6 2:1.7.1-1 ii libx11-xcb1 2:1.7.1-1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxext6 2:1.3.3-1.1 ii libxrender1 1:0.9.10-1 ii psmisc 23.4-2 ii x11-utils7.7+5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages thunderbird recommends: ii hunspell-bg [hunspell-dictionary]1:7.1.0~rc3-3 ii hunspell-en-gb [hunspell-dictionary] 1:7.1.0~rc3-3 ii hunspell-en-us [hunspell-dictionary] 1:2019.10.06-1 ii hunspell-fr-classical [hunspell-dictionary] 1:7.0-1 Versions of packages thunderbird suggests: ii apparmor 2.13.6-10 ii fonts-lyx 2.3.6-1 ii libgssapi-krb5-2 1.18.3-5 ii libgtk2.0-0 2.24.33-2
Bug#980466: marked as done (cervisia: missing dependency on kinit package)
Your message dated Mon, 14 Jun 2021 21:48:33 +
with message-id
and subject line Bug#980466: fixed in cervisia 4:20.12.0-2
has caused the Debian Bug report #980466,
regarding cervisia: missing dependency on kinit package
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.)
--
980466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cervisia
Version: 4:20.12.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: jjusti...@yahoo.fr
Dear Maintainer,
I've installed cervisia without any prior KDE related packages (on a VM running
Debian testing), launch it and I've got :
cervisia &
$ QCommandLineParser: already having an option named "v"
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
kf.dbusaddons: Can not find 'kdeinit5' executable at
"/home/test/perl5/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
"/usr/bin, /usr/lib/qt5/bin"
kf.xmlgui: 0x5592b820f0c8 deleted without having been removed from the factory
first. This will leak standalone popupmenus and could lead to crashes.
as-is, cervisia is unusable as there is nothing user can do, go a quite blank
window, no way to configure, add a repository, whatever.
kdeinit5 binary is included in package kinit, after installing it, I've got
QCommandLineParser: already having an option named "v"
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 18935, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0.0
kdeinit5: Got EXT_EXEC '/usr/bin/cvsservice5' from launcher.
kdeinit5: preparing to launch '/usr/bin/cvsservice5'
log_cervisia: dbusObjectPath: "/NonConcurrentJob"
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 180, resource
id: 16777506, major code: 20 (GetProperty),
minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 181, resource
id: 16777506, major code: 20 (GetProperty), minor code: 0
...
Then, cervisia runs ok as expected.So adding package 'kinit' in dependency list
will fix the issue.
Here are all packages installed (and not installed) with cervisia:
$ aptitude install cervisia
Les NOUVEAUX paquets suivants vont être installés :
cervisia cvsservice{a} kded5{a} kio{a} liba52-0.7.4{a} libaa1{a} libaom0{a}
libaribb24-0{a} libass9{a}
libavc1394-0{a} libavcodec58{a} libavformat58{a} libavutil56{a}
libbasicusageenvironment1{a} libbluray2{a}
libcaca0{a} libcddb2{a} libchromaprint1{a} libcodec2-0.9{a} libdav1d4{a}
libdbusmenu-qt5-2{a} libdc1394-25{a}
libdca0{a} libdouble-conversion3{a} libdvbpsi10{a} libdvdnav4{a}
libdvdread8{a} libebml5{a} libfaad2{a}
libfam0{a} libgles2{a} libgme0{a} libgpgme11{a} libgpgmepp6{a}
libgroupsock8{a} libgsm1{a} libidn11{a}
libixml10{a} libkate1{a} libkf5archive5{a} libkf5attica5{a}
libkf5auth-data{a} libkf5authcore5{a}
libkf5codecs-data{a} libkf5codecs5{a} libkf5completion-data{a}
libkf5completion5{a} libkf5config-data{a}
libkf5configcore5{a} libkf5configgui5{a} libkf5configwidgets-data{a}
libkf5configwidgets5{a}
libkf5coreaddons-data{a} libkf5coreaddons5{a} libkf5crash5{a}
libkf5dbusaddons-data{a} libkf5dbusaddons5{a}
libkf5doctools5{a} libkf5globalaccel-bin{a} libkf5globalaccel-data{a}
libkf5globalaccel5{a}
libkf5globalaccelprivate5{a} libkf5guiaddons5{a} libkf5i18n-data{a}
libkf5i18n5{a} libkf5iconthemes-data{a}
libkf5iconthemes5{a} libkf5itemviews-data{a} libkf5itemviews5{a}
libkf5jobwidgets-data{a} libkf5jobwidgets5{a}
libkf5kiocore5{a} libkf5kiogui5{a} libkf5kiontlm5{a} libkf5kiowidgets5{a}
libkf5notifications-data{a}
libkf5notifications5{a} libkf5parts-data{a} libkf5parts5{a} libkf5pty-data{a}
libkf5pty5{a} libkf5service-bin{a}
libkf5service-data{a} libkf5service5{a} libkf5solid5{a} libkf5solid5-data{a}
libkf5sonnet5-data{a}
libkf5sonnetcore5{a} libkf5sonnetui5{a} libkf5su-data{a} libkf5su5{a}
libkf5textwidgets-data{a}
libkf5textwidgets5{a} libkf5wallet-bin{a} libkf5wallet-data{a}
libkf5wallet5{a} libkf5widgetsaddons-data{a}
libkf5widgetsaddons5{a} libkf5windowsystem-data{a} libkf5windowsystem5{a}
libkf5xmlgui-data{a} libkf5xmlgui5{a}
libkwalletbackend5-5{a} liblirc-client0{a}
Bug#987149: xscreensaver: allows starting external programs with cap_net_raw
This issue is marked as affecting 5.42+dfsg1-1 in buster (and even stretch) in our CVE tracker, however the set_cap action was first added in 5.44+dfsg1-1. https://security-tracker.debian.org/tracker/CVE-2021-31523 Tormod
Bug#989508: xscreensaver: Disconnecting a video output can cause XScreenSaver to crash and unlock
This issue is marked as affecting 5.42+dfsg1-1 in buster (and even stretch) in our CVE tracker, however the openwall report says: "The issue affects only XScreenSaver version 5.45. Versions 5.44 and older, as well as 6.00, are not affected." Tormod
Bug#989843: thunderbird: Problem loading page: NS_ERROR_NET_INADEQUATE_SECURITY
Dear Maintainer, I can confirm this behavior too, with an gmail account since today. In the morning before the update, gmail was working. Now it isn't. This error message in german language is shown: Die Website versuchte, eine unpassende Sicherheitsstufe auszuhandeln. live.thunderbird.net verwendet Sicherheitstechnologie, welche veraltet und verwundbar ist. Ein Angreifer könnte leicht Informationen entschlüsseln, welche Sie für sicher hielten. Der Website-Administrator muss dieses Problem auf dem Server beheben, bevor Sie die Seite aufrufen können. Fehlercode: NS_ERROR_NET_INADEQUATE_SECURITY regards Reiner On Mon, 14 Jun 2021 19:31:37 +0200 Todor Tsankov wrote: > Package: thunderbird > Version: 1:78.11.0-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Since the update to 78.11.0 Thunderbird cannot load various webpages. To > reproduce the error, try to do a search in the Add-ons Manager (type > something in the search box and press Enter). > > The error message is > > "The website tried to negotiate an inadequate level of security. > ... > Error code: NS_ERROR_NET_INADEQUATE_SECURITY" > > There is perhaps a more useful error message in the error console: > > addons.thunderbird.net : server does not support RFC 5746, see CVE-2009-3555 > > The problem also appears when trying to load other pages or using > certain add-ons (for example, calendar-google-provider). > > The problem goes away if one sets network.http.spdy.enforce-tls-profile > to false in the preferences. This makes me think that there is an issue > with the TLS library. > > Cheers, > Todor > > > > -- System Information: > Debian Release: 11.0 > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE > not set > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages thunderbird depends on: > ii debianutils 4.11.2 > ii fontconfig 2.13.1-4.2 > ii libatk1.0-0 2.36.0-2 > ii libbotan-2-17 2.17.3+dfsg-2 > ii libbz2-1.0 1.0.8-4 > ii libc6 2.31-12 > ii libcairo-gobject2 1.16.0-5 > ii libcairo2 1.16.0-5 > ii libdbus-1-3 1.12.20-2 > ii libdbus-glib-1-2 0.110-6 > ii libevent-2.1-7 2.1.12-stable-1 > ii libffi7 3.3-6
Processed: severity of 944751 is serious
Processing commands for cont...@bugs.debian.org: > severity 944751 serious Bug #944751 [src:trousers] trousers: Migrate to tpm-udev Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 944751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 987441 with 989863
Processing commands for cont...@bugs.debian.org: > block 987441 with 989863 Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for Bullseye 987441 was blocked by: 988786 987568 961056 987368 987377 988826 987788 987449 988951 926539 988787 987441 was not blocking any bugs. Added blocking bug(s) of 987441: 989863 > thanks Stopping processing here. Please contact me if you need assistance. -- 987441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986117: marked as done (yarnpkg is not compatible with node-proper-lockfile 3.0.0+)
Your message dated Mon, 14 Jun 2021 19:33:56 + with message-id and subject line Bug#986117: fixed in node-yarnpkg 1.22.10+~cs22.25.14-3 has caused the Debian Bug report #986117, regarding yarnpkg is not compatible with node-proper-lockfile 3.0.0+ 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.) -- 986117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yarnpkg Version: 1.22.10+~cs22.25.14-2 Yarn uses proper-lockfile to implement its `--mutex=file:whatever` option. Its package.json depends on proper-lockfile ^2.0.0, which had the calling convention lockfile.lock( file, options, callback ) In proper-lockfile 3.0.0 they removed that calling convention in favor of use of promises (much like what happened with mkdirp in bug #972952). This causes yarn's callback to never be called, so yarn does nothing other than print the command name. See, for example, $ yarn init --mutex=file:whatever yarn init v1.22.10 $ --- End Message --- --- Begin Message --- Source: node-yarnpkg Source-Version: 1.22.10+~cs22.25.14-3 Done: Paolo Greppi We believe that the bug you reported is fixed in the latest version of node-yarnpkg, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paolo Greppi (supplier of updated node-yarnpkg 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: Mon, 14 Jun 2021 20:25:04 +0200 Source: node-yarnpkg Architecture: source Version: 1.22.10+~cs22.25.14-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Paolo Greppi Closes: 986117 Changes: node-yarnpkg (1.22.10+~cs22.25.14-3) unstable; urgency=medium . * Team upload . [ Paolo Greppi ] * Use promise calling convention for proper-lockfile 3+ (Closes: #986117) . [ Xavier Guimard ] * Fix GitHub tags regex in watch file Checksums-Sha1: 88f84f1cb114898ccfcb41a40fc43dc159cb391b 8177 node-yarnpkg_1.22.10+~cs22.25.14-3.dsc 34014ad62e8b231f4ffe95546be79bcdcd79a975 14364 node-yarnpkg_1.22.10+~cs22.25.14-3.debian.tar.xz da9c9b9835cba01b3e9a72b3580ec93dc6d4e20e 22664 node-yarnpkg_1.22.10+~cs22.25.14-3_source.buildinfo Checksums-Sha256: fe79791c63dd391a4f5efe71d5699e62dade087bab8ef5c2e8afc14f69e7384d 8177 node-yarnpkg_1.22.10+~cs22.25.14-3.dsc c9dd8973ef55c6aab71b90b56f6a1dfa9b419f158f4a5e11106ff40625b14f3b 14364 node-yarnpkg_1.22.10+~cs22.25.14-3.debian.tar.xz 79c8d873069f92fa659b73b2d9a75afb626f76cf6839972209714716ccd636a4 22664 node-yarnpkg_1.22.10+~cs22.25.14-3_source.buildinfo Files: ca2071a4104883dd6d283b597c53 8177 javascript optional node-yarnpkg_1.22.10+~cs22.25.14-3.dsc 0c09c86ff80427156b8177f799a6555e 14364 javascript optional node-yarnpkg_1.22.10+~cs22.25.14-3.debian.tar.xz a89bd115791f1483ed3d18d7e5ca5f2c 22664 javascript optional node-yarnpkg_1.22.10+~cs22.25.14-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEEyTpTRBhTUv5T0mHqIjkMJVxGBPQFAmDHrLAXHHBhb2xvLmdy ZXBwaUBsaWJwZi5jb20ACgkQIjkMJVxGBPSF7BAA2gPJzXF1xFe1qEMPKn4DUAlt f1FB7QjQuzvyHKKRQ7DYKBoxq+eGaoFu8gWsxlBcjjd6hfdwIxavbWaEGk/G24gg ppBiBT5491yEC2OhT1GuXA8L7vx28lbcYgDj0xgZFNeMa9xERoBM1l28I9Ffs42/ P7hAlB/8ABA1tGwiOnm6+Z/HoRsDeXdIiS3LiH8OvsUi7CCeil6hMS5VV0kXUdg8 uPqSccTnEKC7fY4/aaH61sUslANQQLUxsvlUvIP7PT5kashRuIcwR/WXEuKHeq6L 06RkoYTnbkYNONtClGFXgIKsNOG9ua3j07jtjIjCD1GJATcIHpm3la40vgK+5ZQP tGcx8yeOpkarDI/XvFEwrqroER2/8fTtMtk63UrzCK8a9/aFoYABYZEHASJmQ+lM LYLnmnjeQniYqzU7kbESEIthTyDyFt2rQLpUKi+37g0LRFiZO2dop1JpPQNULnv7 wwRnv9dQoy86t1YMYCniZmn3GjNZ06C4HD4grT+GOe1r6+XdOW9l9CO4IGc39Q94 z2kSny3WNQEppKBzaU7ZUYVUaGmCqZ1Wl0VBVO0f5oz3wvwcLNbLuHGKKgjAyzor 4L8xrUfAshHOr1dXVm+wxgnZrGZ2keUPCSzqipHvzcxnc+Voy2dXxIR93MzhrvyB b58Bc3mVeFeBXJn6/Hw= =/f8J -END PGP SIGNATURE End Message ---
Processed: severity of 986975 is important
Processing commands for cont...@bugs.debian.org: > severity 986975 important Bug #986975 [src:gdal] gdal: rename gdal-data to gdal3-data and move files to /usr/share/gdal3 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 986975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: xorg-server-source: Cannot build X from provided source tarball
Processing control commands: > tags -1 patch Bug #989852 [src:xorg-server] xorg-server-source: Cannot build X from provided source tarball Added tag(s) patch. -- 989852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988722: postgresql-common: Upgrading cluster with postgis does not migrate tables using postgis
Hi Andreas, Andreas Beckmann a écrit le 14/06/2021 à 10:18 : On 08/06/2021 13.05, Sebastian Ramacher wrote: Here it is. Now testing upgrades ... There were some new symbols ... but they appeared independently of my changes (I built in bullseye, not sid, in case it does matter). Tests have not shown any problems. And in combination with patched gdal and friends we have achieved co-installability ;-) This is good news. Thanks for this work. Thanks Andreas! Once that tests are done and the packages was uploaded, please let me know so that I can add the appropriate hints on the release team side. FWIW, the symbol is a template instantiation of a function from the standard library and should be marked as optional. Attached is a new version of the patch. Some wording was tweaked and 'optional' added. The new packages are still available as cruft in sid, so we should be able to avoid NEW. Gilles, do you want to do the upload or shall I NMU it? I'll try to upload this evening. I'll now reupload libaec with the recently added Breaks dropped, since they are no longer needed ;-) Thanks again! _g.
Bug#989344: marked as done (libogre-1.12: package name does not match soname)
Your message dated Mon, 14 Jun 2021 18:00:13 + with message-id and subject line Bug#989344: fixed in ogre-1.12 1.12.10+dfsg2-1.1 has caused the Debian Bug report #989344, regarding libogre-1.12: package name does not match soname 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.) -- 989344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rviz Version: 1.14.4+dfsg-3 Severity: grave Justification: renders package unusable Hi, when trying to run rviz I get: rviz: error while loading shared libraries: libOgreOverlay.so.1.12.5: cannot open shared object file: No such file or directory But all my system has is /usr/lib/x86_64-linux-gnu/libOgreOverlay.so.1.12.10 Maybe a binNMU is needed? A rebuild of rviz in current Debian unstable fixed the problem for me. Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: ogre-1.12 Source-Version: 1.12.10+dfsg2-1.1 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ogre-1.12, 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 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ogre-1.12 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: Sat, 12 Jun 2021 16:37:07 +0200 Source: ogre-1.12 Binary: libogre-1.12-dev libogre1.12.10 libogre1.12.10-dbgsym ogre-1.12-doc ogre-1.12-tools ogre-1.12-tools-dbgsym python3-ogre-1.12 python3-ogre-1.12-dbgsym Architecture: source amd64 all Version: 1.12.10+dfsg2-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Jochen Sprickerhof Description: libogre-1.12-dev - 3D Object-Oriented Graphics Rendering Engine (development files) libogre1.12.10 - 3D Object-Oriented Graphics Rendering Engine (libraries) ogre-1.12-doc - 3D Object-Oriented Graphics Rendering Engine (documentation) ogre-1.12-tools - 3D Object-Oriented Graphics Rendering Engine (tools) python3-ogre-1.12 - 3D Object-Oriented Graphics Rendering Engine (Python3) Closes: 989344 Changes: ogre-1.12 (1.12.10+dfsg2-1.1) unstable; urgency=medium . * Non-maintainer upload. * Rename library package to match Soname (Closes: #989344) Checksums-Sha1: f4e78e0fed35870f547349a380dcff133c5ca922 2748 ogre-1.12_1.12.10+dfsg2-1.1.dsc 62ddd4cacd01031c47f074b6d4f32541f04e28b9 34516 ogre-1.12_1.12.10+dfsg2-1.1.debian.tar.xz dc46ef1bf7d46b75a283bd8e9e4fae29921746a9 923488 libogre-1.12-dev_1.12.10+dfsg2-1.1_amd64.deb 682c5c60956949a7eece14983253638b0af5738a 74024932 libogre1.12.10-dbgsym_1.12.10+dfsg2-1.1_amd64.deb 4dd6c0958bf71c07da88aad07d353e94a0670e25 3286020 libogre1.12.10_1.12.10+dfsg2-1.1_amd64.deb e48eb61c47cb0b9c1f4ef6dc34b722d46bea8374 7341996 ogre-1.12-doc_1.12.10+dfsg2-1.1_all.deb 2964c6730987fe2547fb10ccf784443171d7ec32 2288392 ogre-1.12-tools-dbgsym_1.12.10+dfsg2-1.1_amd64.deb c783e206e52de6cdcc787dc9717e8c2b0e3f29dc 254116 ogre-1.12-tools_1.12.10+dfsg2-1.1_amd64.deb ee6e822cbf7e681b343f01cd96d01e4e48094b49 16022 ogre-1.12_1.12.10+dfsg2-1.1_amd64.buildinfo 87407690cc07c2446113478157fdbc360e467c5b 21732588 python3-ogre-1.12-dbgsym_1.12.10+dfsg2-1.1_amd64.deb 56359ae028e2c93e74118b104c11ee2b5003df02 2460396 python3-ogre-1.12_1.12.10+dfsg2-1.1_amd64.deb Checksums-Sha256: f0f4c01d9fbfcc73b1805b276fa69e5deb4558025636bfa90835982a9a89f072 2748 ogre-1.12_1.12.10+dfsg2-1.1.dsc ab58381238d04f280c4d6ef28a8b031411ac41036f0a2cffc7d3c49098c68213 34516 ogre-1.12_1.12.10+dfsg2-1.1.debian.tar.xz 4ffaaf79fdeb2b40a604ea32ab7d3123c2f6bf39e913d949fb08aaf1d5ab8f10 923488 libogre-1.12-dev_1.12.10+dfsg2-1.1_amd64.deb e568c6d1310f48bae9f851d3d9627aaaec9a63ba131de5ac7cc8a6b2a16dd61d 74024932 libogre1.12.10-dbgsym_1.12.10+dfsg2-1.1_amd64.deb d357a9a53a8c478dc5bceb3af5294c58e228f81683369fe0cebb3df936465906 3286020 libogre1.12.10_1.12.10+dfsg2-1.1_amd64.deb a0945aa25939c6eb51fb4af7d69b56021f6c95ef38ec2cd426574ae72be48b6f 7341996 ogre-1.12-doc_1.12.10+dfsg2-1.1_all.deb c1412c9d9276ce37751d5ac3795b43d8f25b538c473d8cd516b3c631627c016f 2288392
Bug#986134: marked as done (acorn: please reintroduce node-acorn as transitional package)
Your message dated Mon, 14 Jun 2021 18:00:10 + with message-id and subject line Bug#986134: fixed in acorn 8.0.5+ds+~cs19.19.27-2 has caused the Debian Bug report #986134, regarding acorn: please reintroduce node-acorn as transitional package 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.) -- 986134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: acorn Version: 8.0.5+ds+~cs19.19.27-2 Severity: serious Tags: patch User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + node-buble Hi, during a test with piuparts I noticed node-buble fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. The upgrade involves switching from the real package node-acorn to the (versioned) virtual package node-acorn, something that is usually difficult for apt and in this case apt fails to find a working upgrade path. Introducing a (real) transitional package node-acorn makes the whole process smooth. >From the attached log (scroll to the bottom...): Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libnode72:amd64 < none -> 12.21.0~dfsg-1 @un uN Ib > Broken libnode72:amd64 Breaks on libnode64:amd64 < 10.24.0~dfsg-1~deb10u1 @ii mK > Considering libnode64:amd64 -3 as a solution to libnode72:amd64 27 Added libnode64:amd64 to the remove list Fixing libnode72:amd64 via remove of libnode64:amd64 Investigating (0) node-debbundle-acorn:amd64 < none -> 8.0.5+ds+~cs19.19.27-1 @un uN Ib > Broken node-debbundle-acorn:amd64 Breaks on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (< 6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-2~) Considering node-acorn:amd64 0 as a solution to node-debbundle-acorn:amd64 -1 Holding Back node-debbundle-acorn:amd64 rather than change node-acorn:amd64 Investigating (1) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (2) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (2) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (3) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (3) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (4) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (4) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (5) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in
Bug#986117: take ownership and mark as pending
On Tue, 1 Jun 2021 16:41:51 +0200 Paolo Greppi wrote: > owner 986117 Paolo Greppi > tag 986117 pending Hi Paolo, Can you upload it? Thanks Praveen
Processed: [bts-link] source package src:gemrb
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gemrb > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #936595 (http://bugs.debian.org/936595) > # Bug title: gemrb: Python2 removal in sid/bullseye > # * https://github.com/gemrb/gemrb/issues/101 > # * remote status changed: open -> closed > # * closed upstream > tags 936595 + fixed-upstream Bug #936595 [src:gemrb] gemrb: Python2 removal in sid/bullseye Bug #966737 [src:gemrb] gemrb: Unversioned Python removal in sid/bullseye Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 936595 - status-open Usertags were: status-open. There are now no usertags set. > usertags 936595 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #966737 (http://bugs.debian.org/966737) > # Bug title: gemrb: Unversioned Python removal in sid/bullseye > # * https://github.com/gemrb/gemrb/issues/101 > # * remote status changed: open -> closed > # * closed upstream > tags 966737 + fixed-upstream Bug #966737 [src:gemrb] gemrb: Unversioned Python removal in sid/bullseye Bug #936595 [src:gemrb] gemrb: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #966737 to the same tags previously set Ignoring request to alter tags of bug #936595 to the same tags previously set > usertags 966737 - status-open Usertags were: status-open. There are now no usertags set. > usertags 966737 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 936595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936595 966737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969907: inkscape, etc. crashing with mismatched libpoppler102 and libpoppler-glib8
On Sun, Jun 13, 2021 at 05:14:31PM +0200, Francesco Poli wrote: > Hello, > is there any progress on this [bug]? I kinda lost track of it after I handled it in inkscape (since it's not effectively out of my concerns). Are there any other affected packages? If so, they probably ought to tighten their dependencies. (though I still think poppler should do something to fix this issue, but as Ivo said, it's too late for bullseye). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#988512: CAcert class 3 validates
Hi, just adding my two cents here: the new class3.crt does verify against the already packaged Class 1 Root. To wit: $ openssl verify -show_chain -CAfile /usr/share/ca-certificates/CAcert/root_X0F.crt class3.crt class3.crt: OK Chain: depth=0: O = CAcert Inc., OU = http://www.CAcert.org, CN = CAcert Class 3 Root (untrusted) depth=1: O = Root CA, OU = http://www.cacert.org, CN = CA Cert Signing Authority, emailAddress = supp...@cacert.org Is there any other reason why the intermediate certificate should not be replaced immediately? Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Processed: Re: cervisia: missing dependency on kinit package
Processing control commands: > tags -1 +confirmed +patch Bug #980466 [cervisia] cervisia: missing dependency on kinit package Added tag(s) confirmed. Bug #980466 [cervisia] cervisia: missing dependency on kinit package Added tag(s) patch. -- 980466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980466: cervisia: missing dependency on kinit package
control: tags -1 +confirmed +patch
Hi,
I'd prepare tiny patch for this issue as below.
diff --git a/debian/changelog b/debian/changelog
index cbd284c..7fde2e5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+cervisia (4:20.12.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix dependency to exec without whole KDE environment (Closes: #980466)
+
+ -- Hideki Yamane Tue, 15 Jun 2021 01:08:14 +0900
+
cervisia (4:20.12.0-1) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index 44c6731..9da63c4 100644
--- a/debian/control
+++ b/debian/control
@@ -29,7 +29,8 @@ Rules-Requires-Root: no
Package: cervisia
Architecture: any
Section: devel
-Depends: cvsservice (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: cvsservice (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends},
+ kinit,
Suggests: khelpcenter
Description: graphical CVS client
Cervisia is a front-end for the CVS version control system client.
Bug#989799: psmisc: Undeclared file conflict with manpages-de from buster-backports
Hello Axel, hello Craig, On Mon, Jun 14, 2021 at 12:19:17PM +0200, Axel Beckert wrote: > Craig Small wrote: > > reassign -1 manpages-de > > Might be the right place indeed, but maybe not in the way you'd > expect. See below. Ack. And thank you very much for your analysis and suggestions. > > > JFTR: What came to me after sending that mail and what I didn't check > > > so far, is if 4.9.3-4 is fine, but 4.9.3-4~bpo10+1 has those files. > > > > > > Actually in that case, I have no idea how the Breaks/Replaces headers > > > and the maintainer scripts need to look like. > > > > $ debdiff manpages-de_4.9.3-4_all.deb manpages-de_4.9.3-4_bpo10+1_all.deb | > > head > > [The following lists of changes regard files as different if they have > > different names, permissions or owners.] > > > > Files in second .deb but not in first > > - > > -rw-r--r-- root/root /usr/share/man/de/man1/fuser.1.gz > > -rw-r--r-- root/root /usr/share/man/de/man1/killall.1.gz > > -rw-r--r-- root/root /usr/share/man/de/man1/lzmainfo.1.gz > > -rw-r--r-- root/root /usr/share/man/de/man1/peekfd.1.gz > > -rw-r--r-- root/root /usr/share/man/de/man1/prtstat.1.gz > > > > There's about 20 "new" files and 20 removed files. > > > > For some reason, the backport version included files that clash with the > > procps and psmisc packages. The sid version on 4.9.3-4 doesn't have those > > conflicting files. > > This actually makes sense, because the backports version is targetted > for buster with psmisc/procps package versions which don't/still have > them. So the exclude/include list the buster-backports package is more > similar to the buster package than the bullseye package — just the > contents of the manpages is as up to date as the bullseye package. > > From that point of view, this is _not_ a bug in the manpages-de > package in buster-backports. (But it still might be the best option to > fix it in there.) > > Then again, dist-upgrades from buster with to bullseye should work > smoothly like without backports and it seems to be that the main > burden to make this sure lays in the backports-packages. > > I though still think that this is a serious (sic!) issue and it should > be fixed. > > Here's my analysis of the potential solutions I see: > > 1) If that Breaks/Replaces headers in psmisc (and probably procps) >would be bumped to "<< 4.9.3-4" it would also match the manpages-de >backports package, but then again, this would also match other >non-backports manpages-de package versions inbetween which don't >have these files. And I fear this would have any unwanted (and >potentially also RC-level) side effects. :-/ I see. But if we decide on the final version for unstable and backports, this should work, shouldn't it? > 2) So I wonder if the buster-backports package of manpages-de could >conflict with the psmisc and procps package in bullseye(*)? This >should probably take care that it is upgraded before procps and >psmisc are upgraded and hopefully solves the issue without too many >side-effects. > >(I'm not sure if Breaks/Replaces with ">>" or ">=" really work as >expected. I've never seen that in use anywhere before. Taking >Guillem into Cc so maybe he can tell something about if Conflicts >or Breaks/Replaces are the better choice here.) > >I only see these hopefully only minor disadvantages of that latter >solution: > >* Users need to have uptodate buster-backports package, i.e. > 4.9.3-4~bpo10+2. If they don't upgrade to 4.9.3-4~bpo10+2 before > dist-upgrading and then upgrade with 4.9.3-4~bpo10+1 still being > installed, they will run into this issue again. Might be > something for the Release Notes. I always remember that your system has to be up-to-date before the dist-upgrade and extra care was necessary for users of backports. Hence I would think this is reasonable. >* I'm not sure if apt gets confused while trying to find a good > order for dist-upgrading if the Conflicts/Breaks/Replaces is in > the old package and not the to-be-upgraded-to one. I hopefully > think that this is no issue, but I'm Cc'ing the APT team for > input on that to be on the safe side. If (and relly if) this works, then from a maintainers POV this would be the nicest solution. > 3) Only ship manpages in manpages-de in buster-backports which are in >psmisc/procps neither in buster nor in bullseye. I assume this is >the solution, Craig had in mind when reassigning the bug report. > >IMHO this is also a viable solution if variant 2) has too many side >effects as it IMHO only has a minor impact on the usability of the >manpages-de package in buster-backports. But this would partially defeat the purpose of the backport, to provide localized man pages where upstream did not. So from a maintainer POV I would prefer either solution 1) or 2). And as this situation will
Bug#989799: psmisc: Undeclared file conflict with manpages-de from buster-backports
Hello Craig, On Mon, Jun 14, 2021 at 06:35:19PM +1000, Craig Small wrote: > On Mon, 14 Jun 2021 at 18:04, Axel Beckert wrote: > > > JFTR: What came to me after sending that mail and what I didn't check > > so far, is if 4.9.3-4 is fine, but 4.9.3-4~bpo10+1 has those files. > > > > Actually in that case, I have no idea how the Breaks/Replaces headers > > and the maintainer scripts need to look like. > > > > $ debdiff manpages-de_4.9.3-4_all.deb manpages-de_4.9.3-4_bpo10+1_all.deb | > head > [The following lists of changes regard files as different if they have > different names, permissions or owners.] > > Files in second .deb but not in first > - > -rw-r--r-- root/root /usr/share/man/de/man1/fuser.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/killall.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/lzmainfo.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/peekfd.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/prtstat.1.gz > > There's about 20 "new" files and 20 removed files. > > For some reason, the backport version included files that clash with the > procps and psmisc packages. The sid version on 4.9.3-4 doesn't have those > conflicting files. That is on purpose. manpages-l10n has various flavours, one is tracking unstable, another one is tracking Buster (currently). Additionally, when translations are moving upstream, they get (manually, if needed be) removed from the version for unstable. So two cases may occur: 1. The translation status is different for unstable and buster. Then the localized man page may appear only in either unstable or buster. 2. Due to the moving of translations to upstream package, the translation may be contained in buster (where upstream did not contain the translation) and not in unstable (where upstream contains the translation and so its no longer present in manpages-l10n). Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#989799: psmisc: Undeclared file conflict with manpages-de from buster-backports
Hello Craig, On Mon, Jun 14, 2021 at 11:41:56AM +1000, Craig Small wrote: > On Mon, 14 Jun 2021 at 00:03, Axel Beckert wrote: > > > So the Breaks and Replaces headers (c.f. #982059) should likely be > > against "<< 4.9.3-4", not just against "<< 4.9.1-1". > > > > It looks like both the psmisc and procps manpages came back from the dead. > They were removed in manpages-de 4.9.1-1 and all was good but then they > came back in 4.9.3 > Helge, the package maintainer for manpages-l10n, then removed them at > 4.9.3-4. Yes, I did a packaging error back then, which was fixed in -4. > > Is that how you see it Helge? I can re-release procps and psmisc with the > updated breaks/replaces but just making sure I hit the right version. > I agree with Axel, it looks like 4.9.3-4 is the right one to aim for now. > I assume that the just imported 4.10.0 won't have these files (again). Correct. The only change is the updated set of translations (at least in de). The "removal" is unchanged. Best greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#932501: problem still present in 0.8.15
On Tue, 13 Apr 2021 20:13:59 +0200 =?UTF-8?B?SsOpcsOpbXkgVmnDqHM=?= wrote: > Just to confirm the issue is still present in bullseye current release. > I had to add the following lines to apparmor configuration to make it work. > > /etc/squid-deb-proxy/** r, > /var/log/squid-deb-proxy/* rw, > /run/squid-deb-proxy.pid rwk, > /var/cache/squid-deb-proxy/** rw, Thank you, put it to debdiff now. diff -Nru squid-deb-proxy-0.8.15/debian/apparmor-profiles/squid-deb-proxy squid-deb-proxy-0.8.15+nmu1/debian/apparmor-profiles/squid-deb-proxy --- squid-deb-proxy-0.8.15/debian/apparmor-profiles/squid-deb-proxy 1970-01-01 09:00:00.0 +0900 +++ squid-deb-proxy-0.8.15+nmu1/debian/apparmor-profiles/squid-deb-proxy 2021-06-14 23:38:09.0 +0900 @@ -0,0 +1,6 @@ +# vim:syntax=apparmor + +/etc/squid-deb-proxy/** r, +/var/log/squid-deb-proxy/* rw, +/run/squid-deb-proxy.pid rwk, +/var/cache/squid-deb-proxy/** rw, diff -Nru squid-deb-proxy-0.8.15/debian/changelog squid-deb-proxy-0.8.15+nmu1/debian/changelog --- squid-deb-proxy-0.8.15/debian/changelog 2020-01-19 03:00:55.0 +0900 +++ squid-deb-proxy-0.8.15+nmu1/debian/changelog2021-06-14 23:41:11.0 +0900 @@ -1,3 +1,10 @@ +squid-deb-proxy (0.8.15+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Add apparmor profiles to work (Closes: #932501) + + -- Hideki Yamane Mon, 14 Jun 2021 23:41:11 +0900 + squid-deb-proxy (0.8.15) unstable; urgency=medium [ Graham Cantin ] diff -Nru squid-deb-proxy-0.8.15/debian/squid-deb-proxy.dirs squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.dirs --- squid-deb-proxy-0.8.15/debian/squid-deb-proxy.dirs 2020-01-10 19:02:40.0 +0900 +++ squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.dirs 2021-06-14 23:40:40.0 +0900 @@ -1,2 +1,3 @@ etc/resolvconf/update-libc.d +etc/apparmor.d/abstractions/squid-deb-proxy var/log/squid-deb-proxy diff -Nru squid-deb-proxy-0.8.15/debian/squid-deb-proxy.install squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.install --- squid-deb-proxy-0.8.15/debian/squid-deb-proxy.install 2020-01-10 19:02:40.0 +0900 +++ squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.install 2021-06-14 23:40:21.0 +0900 @@ -1,3 +1,4 @@ ../update-libc.d etc/resolvconf/ etc/squid-deb-proxy init-common.sh usr/share/squid-deb-proxy/ +../apparmor-profiles/* etc/apparmor.d/abstractions/squid-deb-proxy/
Processed: Re: Bug#989554: Add argyll dependency
Processing control commands: > severity -1 normal Bug #989554 [gnome-control-center] Add argyll dependency Severity set to 'normal' from 'serious' -- 989554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989554: Add argyll dependency
Control: severity -1 normal On Mon, 14 Jun 2021 at 21:46:30 +0900, Hideki Yamane wrote: > On Mon, 07 Jun 2021 13:36:17 + Age Bosma wrote: > > The colour calibration functionality gnome-control-center will > > happily start the lengthy process of colour testing, only the fail at > > the end with the error: > > > > "Tools required for calibration are not installed" > > > > This without specifying which tools exactly. I can see that this is annoying, but I don't think it's release-critical. Many users of gnome-control-center use it sucessfully without ever having carried out colour calibration. normal severity, or maybe important, seems more proportionate. There is already an upstream issue report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1194 saying that the check for argyll should happen before the slow process of colour testing. If you want to contribute an implementation of that, I'm sure the upstream developers would appreciate the help. > > Installing the argyll package solves the issue. > > It seems that we can pull it via Recommends is enough as below. Recommends is for "packages that would be found together with this one in all but unusual installations". Does that really apply here, or would a Suggests be more appropriate? argyll has an installed size of around 100M, which is a significant fraction of the size of the GNOME desktop environment, so I don't think we necessarily want to be pulling it in by default. > But its git repo is a bit confusing, should I patch it to 3.38.4-1 > in unstable or more updated version 3.38.6-1 in repo? If you are making changes targeted at GNOME 40 (currently in experimental due to the freeze, but will go to unstable after Debian 11 is released) then the debian/master branch is correct. If this is release-critical for Debian 11 (which I don't think it is, but perhaps other GNOME team members disagree), then the debian/unstable branch (which I've just updated) is the correct starting point for preparing an update for testing/unstable. Thanks, smcv
Processed: Re: Bug#968897: src:pylint should provide a pylint3 transitional package
Processing control commands: > tags -1 +patch Bug #968897 [src:pylint] src:pylint should provide a pylint3 transitional package Added tag(s) patch. -- 968897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968897: src:pylint should provide a pylint3 transitional package
control: tags -1 +patch On Tue, 1 Jun 2021 22:49:18 +0300 Adrian Bunk wrote: > Provides is good for fulfilling dependencies, but won't for an upgrade > to the renamed package. Okay, then add transitional dummy package for it as below. If anything goes wrong, I'll upload it to delay-5 queue later. >From 2e52e9170265d4eb8160f813b07e34aa41b97521 Mon Sep 17 00:00:00 2001 From: Hideki Yamane Date: Mon, 14 Jun 2021 21:51:09 +0900 Subject: [PATCH 1/2] Add Transitional dummy package pylint3 (Closes: #968897) --- debian/control | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/debian/control b/debian/control index a60b507..cca8351 100644 --- a/debian/control +++ b/debian/control @@ -58,7 +58,7 @@ Depends: python3-astroid (>= 2.4.0), Recommends: python3-tk, Suggests: pylint-doc, python3-mccabe, -Breaks: pylint3, +Breaks: pylint3 (<< 2.7.2-2), python3-pylint-django (<< 2.0), python3-pylint-plugin-utils (<< 0.4), python3-pytest-pylint (<< 0.10), @@ -83,3 +83,9 @@ Description: Python 3 code static checker and UML diagram generator * pyreverse3: an UML diagram generator * symilar3: an independent similarities checker * epylint3: Emacs and Flymake compatible Pylint + +Package: pylint3 +Architecture: all +Depends: pylint +Description: Transitional dummy package + This is transitional dummy package for pylint, you can safely remove it. -- 2.32.0 >From 4d18a26c96b9a0b449a01efe198f8aa46ddc046d Mon Sep 17 00:00:00 2001 From: Hideki Yamane Date: Mon, 14 Jun 2021 22:04:59 +0900 Subject: [PATCH 2/2] note to changelog --- debian/changelog | 8 1 file changed, 8 insertions(+) diff --git a/debian/changelog b/debian/changelog index bae2d32..37bdddb 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +pylint (2.7.2-2) unstable; urgency=medium + + * Team upload + * debian/control +- Introduce pylint3 trantional package for smooth upgrade (Closes: #968897) + + -- Hideki Yamane Mon, 14 Jun 2021 23:03:38 +0900 + pylint (2.7.2-1) unstable; urgency=medium * New upstream release -- 2.32.0
Processed: tagging 932008
Processing commands for cont...@bugs.debian.org: > tags 932008 + pending Bug #932008 [procmeter3] stat-disk.so: undefined symbol: minor Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 932008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 951647
Processing commands for cont...@bugs.debian.org: > tags 951647 + pending Bug #951647 [libmstch-dev] libmstch-dev: Library configuration is misplaced Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 951647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 964357
Processing commands for cont...@bugs.debian.org: > tags 964357 + pending Bug #964357 [alttab] alttab: fails to start: ***buffer overflow detected ***: alttab terminated - Aborted Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 964357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989554: Add argyll dependency
Hi, On Mon, 07 Jun 2021 13:36:17 + Age Bosma wrote: > The colour calibration functionality gnome-control-center will happily start > the lengthy process of colour testing, only the fail at the end with the > error: > > "Tools required for calibration are not installed" > > This without specifying which tools exactly. > > Installing the argyll package solves the issue. It seems that we can pull it via Recommends is enough as below. But its git repo is a bit confusing, should I patch it to 3.38.4-1 in unstable or more updated version 3.38.6-1 in repo? >From 9eaa7e05e3279637667b5aad6cc2555906c6ae6a Mon Sep 17 00:00:00 2001 From: Hideki Yamane Date: Mon, 14 Jun 2021 21:38:24 +0900 Subject: [PATCH] Add Recommends: argyll to provide color management feature (Closes: #989554) --- debian/control.in | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/control.in b/debian/control.in index 7c106ecb3..4e02f278a 100644 --- a/debian/control.in +++ b/debian/control.in @@ -92,6 +92,7 @@ Recommends: cups-pk-helper, libnss-myhostname, cracklib-runtime, pulseaudio-module-bluetooth, +argyll, realmd Suggests: gnome-software | gnome-packagekit, gstreamer1.0-pulseaudio, -- 2.32.0
Bug#966301: guile oom test fails (but currently not on buildds)
Hi, It looks like we have to ignore test failures on all arches. Should we do a NMU for bullseye? See attached debdiff. Best, Dylan guile-2.2_2.2.7+1-5.5_NMU.debdiff Description: Binary data
Processed: severity of 988584 is important
Processing commands for cont...@bugs.debian.org: > severity 988584 important Bug #988584 [manpages-hu] manpages-hu: Contains undistributable content - All rights reserved Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 988584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989799: psmisc: Undeclared file conflict with manpages-de from buster-backports
Hi Craig and Helge, Craig Small wrote: > reassign -1 manpages-de Might be the right place indeed, but maybe not in the way you'd expect. See below. > > JFTR: What came to me after sending that mail and what I didn't check > > so far, is if 4.9.3-4 is fine, but 4.9.3-4~bpo10+1 has those files. > > > > Actually in that case, I have no idea how the Breaks/Replaces headers > > and the maintainer scripts need to look like. > > $ debdiff manpages-de_4.9.3-4_all.deb manpages-de_4.9.3-4_bpo10+1_all.deb | > head > [The following lists of changes regard files as different if they have > different names, permissions or owners.] > > Files in second .deb but not in first > - > -rw-r--r-- root/root /usr/share/man/de/man1/fuser.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/killall.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/lzmainfo.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/peekfd.1.gz > -rw-r--r-- root/root /usr/share/man/de/man1/prtstat.1.gz > > There's about 20 "new" files and 20 removed files. > > For some reason, the backport version included files that clash with the > procps and psmisc packages. The sid version on 4.9.3-4 doesn't have those > conflicting files. This actually makes sense, because the backports version is targetted for buster with psmisc/procps package versions which don't/still have them. So the exclude/include list the buster-backports package is more similar to the buster package than the bullseye package — just the contents of the manpages is as up to date as the bullseye package. >From that point of view, this is _not_ a bug in the manpages-de package in buster-backports. (But it still might be the best option to fix it in there.) Then again, dist-upgrades from buster with to bullseye should work smoothly like without backports and it seems to be that the main burden to make this sure lays in the backports-packages. I though still think that this is a serious (sic!) issue and it should be fixed. Here's my analysis of the potential solutions I see: 1) If that Breaks/Replaces headers in psmisc (and probably procps) would be bumped to "<< 4.9.3-4" it would also match the manpages-de backports package, but then again, this would also match other non-backports manpages-de package versions inbetween which don't have these files. And I fear this would have any unwanted (and potentially also RC-level) side effects. :-/ 2) So I wonder if the buster-backports package of manpages-de could conflict with the psmisc and procps package in bullseye(*)? This should probably take care that it is upgraded before procps and psmisc are upgraded and hopefully solves the issue without too many side-effects. (I'm not sure if Breaks/Replaces with ">>" or ">=" really work as expected. I've never seen that in use anywhere before. Taking Guillem into Cc so maybe he can tell something about if Conflicts or Breaks/Replaces are the better choice here.) I only see these hopefully only minor disadvantages of that latter solution: * Users need to have uptodate buster-backports package, i.e. 4.9.3-4~bpo10+2. If they don't upgrade to 4.9.3-4~bpo10+2 before dist-upgrading and then upgrade with 4.9.3-4~bpo10+1 still being installed, they will run into this issue again. Might be something for the Release Notes. * I'm not sure if apt gets confused while trying to find a good order for dist-upgrading if the Conflicts/Breaks/Replaces is in the old package and not the to-be-upgraded-to one. I hopefully think that this is no issue, but I'm Cc'ing the APT team for input on that to be on the safe side. 3) Only ship manpages in manpages-de in buster-backports which are in psmisc/procps neither in buster nor in bullseye. I assume this is the solution, Craig had in mind when reassigning the bug report. IMHO this is also a viable solution if variant 2) has too many side effects as it IMHO only has a minor impact on the usability of the manpages-de package in buster-backports. Footnotes: (*) buster-backports neither seems to have psmisc nor procps which surely makes this issue less complicated than it could be. :-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#989344: ogre-1.12: diff for NMU version 1.12.10+dfsg2-1.1
On Sun, 13 Jun 2021 at 21:39:48 -0400, Olek Wojnar wrote:
> After bullseye is released, next time upstream bumps the SONAME
> (presumably 1.12.12?), I think it would be good to seriously consider
> packaging the libraries as libogremain1.12.12, libogreoverlay1.12.12
> and so on.
>
> My perspective on that is if the libraries are all meant to be used together
> then it makes little sense to split them into separate packages. That being
> said, I'm not 100% that this is the case with OGRE. If not, your suggestion
> would certainly make the packaging cleaner, if more lengthy. My other concern
> is that I don't want to force dependent packages to declare 20 dependencies.
If you leave the -dev package as a single monolithic binary package, then
maintainers of dependent packages shouldn't need to change anything: they
still declare Build-Depends: libogre-1.12-dev, and then their
${shlibs:Depends} expands to something like
"libogremain1.12.12 (>= x), libogreoverlay1.12.12 (>= y)" depending which
ones they are linked to.
For example, Pango now works like this: we still only have one -dev
package to Build-Depend on, libpango1.0-dev. Depending on which parts
you actually use, you might get runtime dependencies on libpango-1.0-0,
libpangocairo-1.0-0, libpangoft2-1.0-0 and/or libpangoxft-1.0-0.
Qt is another good example of this approach: qtbase5-dev is the -dev
package for libqt5core5a, libqt5gui5 and various others.
Having one -dev package per shared library is not required, although
some maintainers prefer to do it anyway for consistency (for example
libpolkit-agent-1-dev and libpolkit-gobject-1-dev are separate,
but arguably they could equally well have been combined). The time it
becomes important to split -dev packages is when they have relatively
"heavy" dependencies, for example in the poppler source package, which
has separate -dev packages for the core library, the generic C++ binding,
the GLib binding and the Qt binding.
If I'm packaging a multi-library package from scratch, and the upstream
project is already neatly split up by shared library with separate
header directories and pkg-config .pc modules (like Pango is, and like
Ogre seems to be), then I would personally split the -dev package - but
that's personal opinion and not a Policy requirement. If I'm updating an
existing package, I won't usually split a monolithic -dev package unless
there's a specific reason to need to do it, which is why I didn't split
libpango1.0-dev.
> Organizing the package contents to not waste
> archive space is definitely a good thing to add to the list of things to
> address next.
This isn't actually about (not) wasting archive space, it's about whether
two different SONAMEs of the same library can be installed in parallel
(like the way you could install both libssl1.0.2 and libssl1.1 on Debian
9 systems, and in practice often had to do so during upgrades). Not
wasting archive space by introducing an Architecture: all package for
data is just a nice side-effect.
smcv
Processed: Re: libgdal28: please add Breaks: libgdal20
Processing control commands: > reassign -1 src:gdal 3.2.1+dfsg-1 Bug #986975 [libgdal28] libgdal28: please add Breaks: libgdal20 Bug reassigned from package 'libgdal28' to 'src:gdal'. No longer marked as found in versions gdal/3.2.1+dfsg-1. Ignoring request to alter fixed versions of bug #986975 to the same values previously set Bug #986975 [src:gdal] libgdal28: please add Breaks: libgdal20 Marked as found in versions gdal/3.2.1+dfsg-1. > retitle -1 gdal: rename gdal-data to gdal3-data and move files to > /usr/share/gdal3 Bug #986975 [src:gdal] libgdal28: please add Breaks: libgdal20 Changed Bug title to 'gdal: rename gdal-data to gdal3-data and move files to /usr/share/gdal3' from 'libgdal28: please add Breaks: libgdal20'. > severity -1 serious Bug #986975 [src:gdal] gdal: rename gdal-data to gdal3-data and move files to /usr/share/gdal3 Severity set to 'serious' from 'important' > tag -1 - moreinfo Bug #986975 [src:gdal] gdal: rename gdal-data to gdal3-data and move files to /usr/share/gdal3 Removed tag(s) moreinfo. -- 986975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989799: psmisc: Undeclared file conflict with manpages-de from buster-backports
reassign -1 manpages-de On Mon, 14 Jun 2021 at 18:04, Axel Beckert wrote: > JFTR: What came to me after sending that mail and what I didn't check > so far, is if 4.9.3-4 is fine, but 4.9.3-4~bpo10+1 has those files. > > Actually in that case, I have no idea how the Breaks/Replaces headers > and the maintainer scripts need to look like. > $ debdiff manpages-de_4.9.3-4_all.deb manpages-de_4.9.3-4_bpo10+1_all.deb | head [The following lists of changes regard files as different if they have different names, permissions or owners.] Files in second .deb but not in first - -rw-r--r-- root/root /usr/share/man/de/man1/fuser.1.gz -rw-r--r-- root/root /usr/share/man/de/man1/killall.1.gz -rw-r--r-- root/root /usr/share/man/de/man1/lzmainfo.1.gz -rw-r--r-- root/root /usr/share/man/de/man1/peekfd.1.gz -rw-r--r-- root/root /usr/share/man/de/man1/prtstat.1.gz There's about 20 "new" files and 20 removed files. For some reason, the backport version included files that clash with the procps and psmisc packages. The sid version on 4.9.3-4 doesn't have those conflicting files. - Craig
Bug#988722: postgresql-common: Upgrading cluster with postgis does not migrate tables using postgis
On 08/06/2021 13.05, Sebastian Ramacher wrote:
Here it is. Now testing upgrades ...
There were some new symbols ... but they appeared independently of my
changes (I built in bullseye, not sid, in case it does matter).
Tests have not shown any problems. And in combination with patched gdal
and friends we have achieved co-installability ;-)
Thanks Andreas! Once that tests are done and the packages was uploaded,
please let me know so that I can add the appropriate hints on the
release team side.
FWIW, the symbol is a template instantiation of a function from the
standard library and should be marked as optional.
Attached is a new version of the patch. Some wording was tweaked and
'optional' added.
The new packages are still available as cruft in sid, so we should be
able to avoid NEW.
Gilles, do you want to do the upload or shall I NMU it?
I'll now reupload libaec with the recently added Breaks dropped, since
they are no longer needed ;-)
Andreas
diff -Nru hdf5-1.10.6+repack/debian/changelog hdf5-1.10.6+repack/debian/changelog
--- hdf5-1.10.6+repack/debian/changelog 2020-04-24 20:00:42.0 +0200
+++ hdf5-1.10.6+repack/debian/changelog 2021-06-08 08:57:04.0 +0200
@@ -1,3 +1,17 @@
+hdf5 (1.10.6+repack-3) UNRELEASED; urgency=medium
+
+ * Reintroduce libhdf5-103, libhdf5-cpp-103, libhdf5-openmpi-103,
+libhdf5-mpich-103 as transitional packages depending on the individual
+library packages that were bundled under these names in buster. This is a
+workaround for upgrade issues caused by libhdf5-103 (in buster) and
+libhdf5-103-1 (in bullseye) not being co-installable. The transitional
+packages cannot depend on libhdf5{,-openmpi,-mpich}-fortran100 because
+these had the SOVERSION bumped from 100 to 102, but luckily there are no
+known users of these libraries in buster. (See #988722)
+ * Add a new optional symbol to libhdf5*-cpp-103-1.symbols.
+
+ -- Andreas Beckmann Tue, 08 Jun 2021 08:57:04 +0200
+
hdf5 (1.10.6+repack-2) unstable; urgency=medium
* Default plugindir per flavor
diff -Nru hdf5-1.10.6+repack/debian/control hdf5-1.10.6+repack/debian/control
--- hdf5-1.10.6+repack/debian/control 2020-04-24 20:00:42.0 +0200
+++ hdf5-1.10.6+repack/debian/control 2021-06-08 08:57:04.0 +0200
@@ -28,8 +28,8 @@
Depends: ${shlibs:Depends},
${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
-Breaks: libhdf5-103
-Replaces: libhdf5-103
+Breaks: libhdf5-103 (<< 1.10.5)
+Replaces: libhdf5-103 (<< 1.10.5)
Description: HDF5 C runtime files - serial version
Hierarchical Data Format 5 (HDF5) is a file format and library for
storing scientific data. HDF5 was designed and implemented to address
@@ -88,14 +88,35 @@
This package contains the high level Fortran API runtime files for serial
platforms.
+Package: libhdf5-103
+Architecture: any
+Multi-Arch: same
+Section: libs
+Depends: libhdf5-103-1 (= ${binary:Version}),
+#libhdf5-fortran-102 (= ${binary:Version}),
+ libhdf5-hl-100 (= ${binary:Version}),
+ libhdf5-hl-fortran-100 (= ${binary:Version}),
+ ${misc:Depends}
+Description: HDF5 C runtime files - serial version (transitional package)
+ Hierarchical Data Format 5 (HDF5) is a file format and library for
+ storing scientific data. HDF5 was designed and implemented to address
+ the deficiencies of HDF4.x. It has a more powerful and flexible data
+ model, supports files larger than 2 GB, and supports parallel I/O.
+ .
+ This package contains the C runtime files for serial platforms.
+ .
+ This transitional package helps upgrading from the single package bundling
+ multiple libraries in buster to the individiual library packages in
+ bullseye. It can be safely removed.
+
Package: libhdf5-cpp-103-1
Architecture: any
Multi-Arch: same
Section: libs
Depends: ${shlibs:Depends},
${misc:Depends}
-Breaks: libhdf5-cpp-103
-Replaces: libhdf5-cpp-103
+Breaks: libhdf5-cpp-103 (<< 1.10.5)
+Replaces: libhdf5-cpp-103 (<< 1.10.5)
Description: HDF5 - C++ runtime files - serial version
Hierarchical Data Format 5 (HDF5) is a file format and library for
storing scientific data. HDF5 was designed and implemented to address
@@ -122,6 +143,25 @@
This package contains the high level C++ API runtime files for serial
platforms.
+Package: libhdf5-cpp-103
+Architecture: any
+Multi-Arch: same
+Section: libs
+Depends: libhdf5-cpp-103-1 (= ${binary:Version}),
+ libhdf5-hl-cpp-100 (= ${binary:Version}),
+ ${misc:Depends}
+Description: HDF5 - C++ runtime files - serial version (transitional package)
+ Hierarchical Data Format 5 (HDF5) is a file format and library for
+ storing scientific data. HDF5 was designed and implemented to address
+ the deficiencies of HDF4.x. It has a more powerful and flexible data
+ model, supports files larger than 2 GB, and supports parallel I/O.
+ .
+ This package contains the C++ runtime files for serial platforms.
+ .
+ This transitional package helps
Bug#989799: psmisc: Undeclared file conflict with manpages-de from buster-backports
Hi, Craig Small wrote: > On Mon, 14 Jun 2021 at 00:03, Axel Beckert wrote: > > So the Breaks and Replaces headers (c.f. #982059) should likely be > > against "<< 4.9.3-4", not just against "<< 4.9.1-1". > > It looks like both the psmisc and procps manpages came back from the dead. > They were removed in manpages-de 4.9.1-1 and all was good but then they > came back in 4.9.3 JFTR: What came to me after sending that mail and what I didn't check so far, is if 4.9.3-4 is fine, but 4.9.3-4~bpo10+1 has those files. Actually in that case, I have no idea how the Breaks/Replaces headers and the maintainer scripts need to look like. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
