Bug#883194: please convert mountstats and nfsiostat scripts to Python3
On 2021-06-28 00:35, Diederik de Haas wrote: On zondag 27 juni 2021 22:37:10 CEST Salvatore Bonaccorso wrote: Let's ask the release team instead. Here my arguments why: nfs-utils needs a major rehaul, this was not possible to finish in time for bullseye, so this means nfs-utils is generally in not a very good shape for bullseye,details in https://salsa.debian.org/kernel-team/nfs-utils/-/merge_requests/3 . That overhaul/MR is indeed out of scope for Bullseye. Agreed, we don't want to make a major rehaul here. But unless I misunderstood, here we only need to update shebangs, as Diederik and Laurent mentioned. Jann Haber prepared a small PR, https://salsa.debian.org/kernel-team/nfs-utils/-/merge_requests/4 Is anything more than that needed for updating the python2 Recommends to python3? Drew
Bug#883194: please convert mountstats and nfsiostat scripts to Python3
On zondag 27 juni 2021 22:37:10 CEST Salvatore Bonaccorso wrote: > Let's ask the release team instead. Here my arguments why: nfs-utils > needs a major rehaul, this was not possible to finish in time for > bullseye, so this means nfs-utils is generally in not a very good > shape for bullseye,details in > https://salsa.debian.org/kernel-team/nfs-utils/-/merge_requests/3 . That overhaul/MR is indeed out of scope for Bullseye. But as Laurent Bigonville already said: > So it's just a matter of changing the shebang and the dependency. (It's actually a Recommends) Without that fix, many Bullseye systems will get python2 because of NFS, and several people have already verified that it works just fine with python3. My €0.02 signature.asc Description: This is a digitally signed message part.
Bug#990382: rust-file-diff FTBFS
Source: rust-file-diff Version: 1.0.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-file-diff.html ... dh_shlibdeps -O--buildsystem=cargo dpkg-shlibdeps: error: cannot find library libglib-2.0.so.0 needed by debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/c_hello_copy (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '') dpkg-shlibdeps: error: cannot find library libglib-2.0.so.0 needed by debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/c_hello (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '') dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/rust_hello was not linked against libdl.so.2 (it uses none of the library's symbols) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/rust_hello was not linked against librt.so.1 (it uses none of the library's symbols) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/rust_hello was not linked against libm.so.6 (it uses none of the library's symbols) dpkg-shlibdeps: error: cannot continue due to the errors listed above Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file. To help dpkg-shlibdeps find private libraries, you might need to use -l. dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/librust-file-diff-dev.substvars debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/c_hello debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/c_hello_copy debian/librust-file-diff-dev/usr/share/cargo/registry/file_diff-1.0.0/testdata/rust_hello returned exit code 2 dh_shlibdeps: error: Aborting due to earlier error make: *** [debian/rules:6: binary] Error 25
Bug#975270: rdiff-backup: Can't talk to the version from buster
Samuel Thibault, le dim. 27 juin 2021 23:06:03 +0200, a ecrit: > Samuel Thibault, le ven. 18 juin 2021 19:27:40 +0200, a ecrit: > > Samuel Thibault, le dim. 16 mai 2021 19:03:11 +0200, a ecrit: > > > Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > > > > * Samuel Thibault [13. Mai. 2021]: > > > > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > > > > >> I recently found out that my backup has broken for months. > > > > > > > > > > Not for month, but this does break my backups now that I try to > > > > > upgrade > > > > > some machines, and I don't have another solution than to either > > > > > downgrade the package, or upgrade all my machines at the same time > > > > > (!?) > > > > > to get my backups working again. > > > > > > > > the rdiff-backup project provides a helpful document > > > > regarding this: > > > > > > > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > > > > > > > providing this document in the NEWS.Debian file might be > > > > enough in order to close this bug? > > > > > > Perhaps we could have a buster-backports package, so that before > > > upgrading machines to bullseye, we first just upgrade rdiff-backup on > > > all buster machines? > > > > I have uploaded it to buster-backports, it's now in so people can > > pre-upgrade. I'd however probably still be important to ship a > > NEWS.Debian entry to let people about about the incompatibility issue. > > I have uploaded so, and requested an unblock. (filed as Bug#990379)
Bug#975270: rdiff-backup: Can't talk to the version from buster
Samuel Thibault, le ven. 18 juin 2021 19:27:40 +0200, a ecrit: > Samuel Thibault, le dim. 16 mai 2021 19:03:11 +0200, a ecrit: > > Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > > > * Samuel Thibault [13. Mai. 2021]: > > > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > > > >> I recently found out that my backup has broken for months. > > > > > > > > Not for month, but this does break my backups now that I try to upgrade > > > > some machines, and I don't have another solution than to either > > > > downgrade the package, or upgrade all my machines at the same time (!?) > > > > to get my backups working again. > > > > > > the rdiff-backup project provides a helpful document > > > regarding this: > > > > > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > > > > > providing this document in the NEWS.Debian file might be > > > enough in order to close this bug? > > > > Perhaps we could have a buster-backports package, so that before > > upgrading machines to bullseye, we first just upgrade rdiff-backup on > > all buster machines? > > I have uploaded it to buster-backports, it's now in so people can > pre-upgrade. I'd however probably still be important to ship a > NEWS.Debian entry to let people about about the incompatibility issue. I have uploaded so, and requested an unblock. Samuel
Bug#975270: marked as done (rdiff-backup: Can't talk to the version from buster)
Your message dated Sun, 27 Jun 2021 21:03:23 + with message-id and subject line Bug#975270: fixed in rdiff-backup 2.0.5-2 has caused the Debian Bug report #975270, regarding rdiff-backup: Can't talk to the version from buster 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.) -- 975270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rdiff-backup Version: 2.0.5-1 Severity: important Hi, I recently found out that my backup has broken for months. It seems that the version from testing doesn't want to talk to the version from stable/buster. It gives the following error: Exception 'object.__new__(X): X is not a type object (classobj)' raised of class '': File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 304, in error_check_Main try: Main(arglist) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 278, in take_action connection.PipeConnection(sys.stdin, sys.stdout).Server() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 355, in Server self.get_response(-1) File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 315, in get_response try: req_num, object = self._get() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 241, in _get if format_string == "o": result = cPickle.loads(data) File "/usr/lib/python2.7/copy_reg.py", line 48, in _reconstructor obj = object.__new__(cls) Traceback (most recent call last): File "/usr/bin/rdiff-backup", line 30, in rdiff_backup.Main.error_check_Main(sys.argv[1:]) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 304, in error_check_Main try: Main(arglist) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 278, in take_action connection.PipeConnection(sys.stdin, sys.stdout).Server() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 355, in Server self.get_response(-1) File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 315, in get_response try: req_num, object = self._get() File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 241, in _get if format_string == "o": result = cPickle.loads(data) File "/usr/lib/python2.7/copy_reg.py", line 48, in _reconstructor obj = object.__new__(cls) TypeError: object.__new__(X): X is not a type object (classobj) Fatal Error: Truncated header string (problem probably originated remotely) Couldn't start up the remote connection by executing ssh -C X rdiff-backup --server Remember that, under the default settings, rdiff-backup must be installed in the PATH on the remote system. See the man page for more information on this. This message may also be displayed if the remote version of rdiff-backup is quite different from the local version (2.0.5). If I downgrade to the local version 1.2.8-7, which is also the remote version, things work. Kurt --- End Message --- --- Begin Message --- Source: rdiff-backup Source-Version: 2.0.5-2 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of rdiff-backup, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated rdiff-backup 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: Sun, 27 Jun 2021 22:47:12 +0200 Source: rdiff-backup Architecture: source Version: 2.0.5-2 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Samuel Thibault Closes: 975270 Changes: rdiff-backup (2.0.5-2) unstable; urgency=medium . * NEWS: Notify users that the network protocol of versions 1 and 2 of rdiff-backup are incompatible (Closes: #975270). Checksums-Sha1: 4cad4c3de0309d97
Bug#883194: please convert mountstats and nfsiostat scripts to Python3
Hi Drew, On Sun, Jun 27, 2021 at 10:37:14PM +0200, Salvatore Bonaccorso wrote: > Hi, > > On Sun, Jun 27, 2021 at 04:46:36PM +0200, Drew Parsons wrote: > > Package: nfs-common > > Followup-For: Bug #883194 > > X-Debbugs-Cc: debian-rele...@lists.debian.org > > Control: severity 883194 serious > > Control: usertag 883194 py2removal > > > > Since removing Python2 is a release goal for bullseye (other packages > > have been removed because of their python2 dependencies), and since > > the fix for this bug in nfs-common is trivial, I'm flagging this bug > > as RC. > > Let's ask the release team instead. Here my arguments why: nfs-utils > needs a major rehaul, this was not possible to finish in time for > bullseye, so this means nfs-utils is generally in not a very good > shape for bullseye,details in > https://salsa.debian.org/kernel-team/nfs-utils/-/merge_requests/3 . > > I would rather not touch at this stage of the release for bullseye > nfs-utils anymore, instead we should try to rewamp asap after the > bullseye release so we can make sure nfs-utils is proper again for > bookworm. > > Release team, do you want a fix this late still for #883194 ? forgot to metion: if the Release team agrees on the late fix for it sitll, I'm happy to do it and ask for an unblock. Regards, Salvatore
Bug#883194: please convert mountstats and nfsiostat scripts to Python3
Hi, On Sun, Jun 27, 2021 at 04:46:36PM +0200, Drew Parsons wrote: > Package: nfs-common > Followup-For: Bug #883194 > X-Debbugs-Cc: debian-rele...@lists.debian.org > Control: severity 883194 serious > Control: usertag 883194 py2removal > > Since removing Python2 is a release goal for bullseye (other packages > have been removed because of their python2 dependencies), and since > the fix for this bug in nfs-common is trivial, I'm flagging this bug > as RC. Let's ask the release team instead. Here my arguments why: nfs-utils needs a major rehaul, this was not possible to finish in time for bullseye, so this means nfs-utils is generally in not a very good shape for bullseye,details in https://salsa.debian.org/kernel-team/nfs-utils/-/merge_requests/3 . I would rather not touch at this stage of the release for bullseye nfs-utils anymore, instead we should try to rewamp asap after the bullseye release so we can make sure nfs-utils is proper again for bookworm. Release team, do you want a fix this late still for #883194 ? Regards, Salvatore
Bug#934747:
1565781747 E Could not create download: Info hash already used by another torrent. 1565781771 C Caught signal: 'Erreur de segmentation. ---DUMP---
Bug#934747:
Date: Wed, 14 Aug 2019 11:42:04 UTC Severity: *grave* Tags: fixed-upstream, upstream Found in version curl/7.65.1-1 Fixed in version curl/7.65.3-1
Processed: Re: Processed: Re: Bug#990158: fixed in shim 15.4-6
Processing commands for cont...@bugs.debian.org:
> # oops
> fixed 990158 15.4-6
Bug #990158 {Done: Steve McIntyre <93...@debian.org>} [src:shim]
shim-signed-common: No UEFI boot with error "Could not create MokListXRT"
Marked as fixed in versions shim/15.4-6.
> fixed 990158 15.4-6~deb10u1
Bug #990158 {Done: Steve McIntyre <93...@debian.org>} [src:shim]
shim-signed-common: No UEFI boot with error "Could not create MokListXRT"
Marked as fixed in versions shim/15.4-6~deb10u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
990158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#990158: fixed in shim 15.4-6
Processing control commands:
> reassign -1 src:shim
Bug #990158 {Done: Steve McIntyre <93...@debian.org>} [shim-signed-common]
shim-signed-common: No UEFI boot with error "Could not create MokListXRT"
Bug reassigned from package 'shim-signed-common' to 'src:shim'.
No longer marked as found in versions shim-signed/1.33.
No longer marked as fixed in versions shim/15.4-6 and shim/15.4-6~deb10u1.
--
990158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#990158: fixed in shim 15.4-6
Control: reassign -1 src:shim Hi, On Wed, 23 Jun 2021 18:18:51 + Debian FTP Masters wrote: >* In insecure mode, don't abort if we can't create the MokListXRT > variable. Upstream issue #372. Closes: #989962, #990158 Bug 990158 was assigned to shim-signed. As this is closed by src:shim, I reassign it, such that the BTS knows it's properly fixed. Please let me know if I got it wrong. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> found 989320 5.22+repack-1
Bug #989320 {Done: Michael Gilbert }
[src:wine-development] libwine-development-dev: libwine-development and
libwine-development-dev both supply libwine.so
Bug #989870 {Done: Michael Gilbert }
[src:wine-development] libwine-development,libwine-development-dev: both ship
usr/lib/x86_64-linux-gnu/wine-development/libwine.so
Marked as found in versions wine-development/5.22+repack-1.
Marked as found in versions wine-development/5.22+repack-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
989320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989320
989870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#990344: exim 4.94.2 update default configuration option breaks MTA
On 2021-06-26 sawb...@xsmail.com wrote: > On 26 Jun 2021 at 15:12, Andreas Metzler wrote: > > I think that assumption is not correct. dpkg will (should) only ask > > about the confffile if it *was* locally changed, otherwise the files are > > overwritten without asking. > I see ... > The thing is that I don't remember *ever* changing any exim > configuration. > Unfortunately I cannot be categorical about it. > ie: I am not absolutely certain. > Right. > Please bear with me, I'll try to be as brief as possible. > Let us assume for the sake of the argument that I (on purpose or > inadvertently) changed something in the configuration. > What could I have possibly changed? > Is there any user/userland configurable setting which would be then > reflected or change *anything* in the exim4.conf.template file > itself? Hello, the exim packages do not change/edit the file, if it was changed then manually. > Specifically, any of the settings mentioned in the readme.updating > file: > https://git.exim.org/exim.git/blob/HEAD:/src/README.UPDATING > --- snip ---> > Exim version 4.94 > --- > Some Transports now refuse to use tainted data in constructing their > delivery location; this WILL BREAK configurations which are not > updated accordingly. In particular: any Transport use of $local_part > which has been relying upon check_local_user far away in the Router > to make it safe, should be updated to replace $local_part with > $local_part_data. > <--- snip --- > eg: $local_part > I have checked and my pre-4.94.2 version reads *$local_part* and the > 4.94.2 version reads *$local_part_data*. > So, if the original configuration file *was* changed by me (on > purpose or inadvertently), whatever change I could have made does not > seem to be related to (at least one) of the settings that need to be > changed for the exim4 configuration to be compatible with exim > 4.94.2. Sounds reasonable, yes. If you are not sure what you did change, you can download older versions of exim4-config from https://snapshot.debian.org/binary/exim4-config/ extract the file with e.g. ametzler@argenau:~$ dpkg --fsys-tarfile /path/to/exim4-config_4.91-9_all.deb | tar -f - --one-top-level=/tmp -v -x ./etc/exim4/exim4.conf.template and use e.g. diff or tkdiff to find local changes. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#990355: marked as done ([src:donkey] FTBFS with the tmux test runner)
Your message dated Sun, 27 Jun 2021 14:48:46 + with message-id and subject line Bug#990355: fixed in donkey 1.2.0-6 has caused the Debian Bug report #990355, regarding [src:donkey] FTBFS with the tmux test runner 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.) -- 990355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: donkey Version: 1.2.0-1 Severity: serious Tags: patch The donkey upstraem source has two modes of running its tests: using a pseudo-tty driver, and using tmux in control mode. However, tmux 3.x has a regression (that is probably worth reporting a separate bug for) that, among other things such as my need for an actual tmux control mode library, led to me writing up the (still raw and quite unfinished) https://gitlab.com/ppentchev/tmux-ctlmode project. That part is not really pertinent to the Debian package of donkey though, since I have not yet finished or packaged tmux-ctlmode for Debian so donkey can use it to build. A quick workaround for e.g. https://ci.debian.net/data/autopkgtest/testing/i386/d/donkey/13206643/log.gz ...would be to use the donkey source build system's "pty" test runner: diff --git a/debian/rules b/debian/rules index 8fe8f13..d16747a 100755 --- a/debian/rules +++ b/debian/rules @@ -20,7 +20,7 @@ override_dh_auto_build: dh_auto_build -D src override_dh_auto_test: - dh_auto_test -D src + dh_auto_test -D src -- TEST_PROCESS_DRIVER=pty override_dh_auto_clean: dh_auto_clean -D src diff --git a/debian/tests/control b/debian/tests/control index d544f0c..3650d6e 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -1,4 +1,4 @@ -Test-Command: env TEST_PROG=/usr/bin/donkey python3 src/test-donkey.py +Test-Command: env TEST_PROCESS_DRIVER=pty TEST_PROG=/usr/bin/donkey python3 src/test-donkey.py Depends: @, python3, python3-ddt, python3-six, tmux Restrictions: allow-stderr Features: test-name=upstream This should be enough to get the donkey package up and building again. G'luck, Peter -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: donkey Source-Version: 1.2.0-6 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of donkey, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated donkey 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: Sun, 27 Jun 2021 01:00:00 +0300 Source: donkey Architecture: source Version: 1.2.0-6 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Closes: 990355 Changes: donkey (1.2.0-6) unstable; urgency=medium . * Use the "pty" test driver to avoid problems with tmux not always sending us the full output of the command that was run. Closes: #990355 Checksums-Sha1: ba931b2f7005e5ba93c888df795dc1d55f8df0a2 2370 donkey_1.2.0-6.dsc 1b924f6535c8ac920396f50a1f27e895cdf2468a 10696 donkey_1.2.0-6.debian.tar.xz Checksums-Sha256: 80834ec28b1308204c14da3ac08ce3b8bc8133a7a90ed3a65e84107c3618904e 2370 donkey_1.2.0-6.dsc dd9276d5bc825454bf85e185487b41959a7cc48276a0a2264ca166998b418fc4 10696 donkey_1.2.0-6.debian.tar.xz Files: 62943da503f11d5e993fc82e327b69c7 2370 net optional donkey_1.2.0-6.dsc 873b5f881af83e8ca99f0a7d2bcff964 10696 net optional donkey_1.2.0-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmDYiqYQHHJvYW1AZGVi aWFuLm9yZwAKCRBlHu+wJSffE7ZnD/9ZtFmANQPTDtTcXIg0PVzxGEdbu7BsO+ZD 9DkUfbhyaKSvSDZPvnZZsqv5L1SIF4zT0VAOxXNlnkD3t7PlkskPwZRVYmguXX1R MOFO9wQFS
Processed (with 1 error): Re: please convert mountstats and nfsiostat scripts to Python3
Processing control commands: > severity 883194 serious Bug #883194 [nfs-utils] please convert mountstats and nfsiostat scripts to Python3 Severity set to 'serious' from 'normal' > usertag 883194 py2removal Unknown command or malformed arguments to command. -- 883194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: oof, the feature-check bug is present in stable, too
Processing commands for cont...@bugs.debian.org:
> package feature-check
Limiting to bugs with field 'package' containing at least one of 'feature-check'
Limit currently set to 'package':'feature-check'
> found 990276 0.1.0-1
Bug #990276 {Done: Peter Pentchev } [feature-check]
[feature-check] Version comparisons may return the wrong result
Marked as found in versions feature-check/0.1.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
990276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964357: marked as done (alttab: fails to start: ***buffer overflow detected ***: alttab terminated - Aborted)
Your message dated Sun, 27 Jun 2021 14:19:00 + with message-id and subject line Bug#964357: fixed in alttab 1.5.0-2 has caused the Debian Bug report #964357, regarding alttab: fails to start: ***buffer overflow detected ***: alttab terminated - Aborted 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.) -- 964357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: alttab Version: 1.3.0-1 Severity: important Dear Maintainer, * What led up to the situation? Don't know, maybe an update? * What exactly did you do (or not do) that was effective (or ineffective)? $ alttab *** buffer overflow detected ***: alttab terminated Abortado Then, opened issue at: https://github.com/sagb/alttab/issues/96 * What was the outcome of this action? Can't cope at the time with the complexities of developer's proposed steps. * What outcome did you expect instead? Simple solution. ;) -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages alttab depends on: ii libc62.30-8 ii libpng16-16 1.6.37-2 ii libx11-6 2:1.6.9-2+b1 ii libxft2 2.3.2-2 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii zlib1g 1:1.2.11.dfsg-2 alttab recommends no packages. Versions of packages alttab suggests: ii fonts-dejavu-core 2.37-2 -- no debconf information --- End Message --- --- Begin Message --- Source: alttab Source-Version: 1.5.0-2 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of alttab, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated alttab 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: Sun, 27 Jun 2021 16:57:21 +0300 Source: alttab Architecture: source Version: 1.5.0-2 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Closes: 964357 989842 Changes: alttab (1.5.0-2) unstable; urgency=medium . * New maintainer. Closes: #989842 * Point Vcs-Git and Vcs-Browser to the new salsa/debian repository. * Add the strncpy patch to fix some buffer overflows. Closes: #964357 Checksums-Sha1: 50c5bc5e3b722431b12161845cf49c063e9131ac 2156 alttab_1.5.0-2.dsc 1a342101950d6aa5e3127fa1abda7ffc8f896934 318518 alttab_1.5.0.orig.tar.gz 1147937a614cb79dafd9702929d22bdc55574f17 833 alttab_1.5.0.orig.tar.gz.asc 50ce8c81bcf42de895d75b27e26b9c4b1f86595a 6576 alttab_1.5.0-2.debian.tar.xz beedc2d12d51d3d686c0894fb40da6460a59f940 7465 alttab_1.5.0-2_amd64.buildinfo Checksums-Sha256: a836986053d98c7c9241adf296c19390cae4b1f6f1b52beb05db092ac3bb01bc 2156 alttab_1.5.0-2.dsc d170425a34d1a92cf0eb5ba7306bf77729a6c04f211593cc5fdd8a0ab583a280 318518 alttab_1.5.0.orig.tar.gz 26b23acb8fd0ea05957ae4ed74d16c1f210419c7bea7413ce23f423584b416a5 833 alttab_1.5.0.orig.tar.gz.asc 9db9e21bb6fc6d9963447bbcd602830ec68a52da391438bbd97530e50f2b8a35 6576 alttab_1.5.0-2.debian.tar.xz 4cf03229f48570fbfac3aa4723bbf05254a6c5012d71d4ec10d6be954bb5e9e4 7465 alttab_1.5.0-2_amd64.buildinfo Files: 5ce5cd8426e11d2740347257773232c6 2156 x11 optional alttab_1.5.0-2.dsc ec4159bfa8be63e9891db9cc14fb599e 318518 x11 optional alttab_1.5.0.orig.tar.gz 4ff37098a20580e670dc453bfd18f720 833 x11 optional alttab_1.5.0.orig.tar.gz.asc 835491bad304c96711089bb013819d05 6576 x11 optional alttab_1.5.0-2.debian.tar.xz 9c5cd3ddcb09e39a51465fc182c689c5 7465 x11 optional alttab_1.5.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmDYhRsACgkQZR7vsCUn 3xN4CRAAuqQ94IeArROpjfGkcaSi9Uc1stG0Vw64P3iOxACv39Pb2F8HzBTrY4Ea RlvPX3wN7iocig90rVbDWPPKslkZysi159JpVYlYkfAsVaKN9ttYe/HaVpEqxmV0 Xpaevvrkj0B/pdR77AQ
Bug#990345: zookeeper: various security issues
Hey. On Sun, 2021-06-27 at 14:46 +0200, Salvatore Bonaccorso wrote: > To me this looks like CVEs in other products, but which zookeeper > uses > as dependency? Is this correct? Indeed, but I couldn't find that the zookeeper package depends on these while it does contain: zookeeper-3.4.13/src$ find . -iname "*nett*" ./java/main/org/apache/zookeeper/server/NettyServerCnxnFactory.java ./java/main/org/apache/zookeeper/server/NettyServerCnxn.java ./java/test/org/apache/zookeeper/server/NettyServerCnxnTest.java ./java/test/org/apache/zookeeper/test/NioNettySuiteTest.java ./java/test/org/apache/zookeeper/test/NioNettySuiteHammerTest.java ./java/test/org/apache/zookeeper/test/NioNettySuiteBase.java ... so I figured these might still be affected? And apart from that... if they apparently don't support older versions anymore, we'd like not even notice should these contain any security issues. Cheers, Chris.
Processed: grab the alttab segfault RC bug
Processing commands for cont...@bugs.debian.org: > owner 964357 ! Bug #964357 [alttab] alttab: fails to start: ***buffer overflow detected ***: alttab terminated - Aborted Owner recorded as Peter Pentchev . > End of message, 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#990345: zookeeper: various security issues
[Disclaimer, not the package maintainer, but quickly checked your report for tracking within the security team] On Sat, Jun 26, 2021 at 01:50:44PM +0200, Christoph Anton Mitterer wrote: > Source: zookeeper > Version: 3.4.13-6 > Severity: grave > Tags: security > Justification: user security hole > X-Debbugs-Cc: Debian Security Team > > > Hi. > > The release notes for > https://zookeeper.apache.org/doc/r3.6.3/releasenotes.html > list various security issues: > CVE-2020-25649 > CVE-2021-21295 > CVE-2021-28165 > CVE-2021-21409 > > It's a bit unclear to me whether 3.4 is affected to, but since 3.5.x > versions seem > to be, I'd guess the issues go back longer and may affect 3.4 as well. > > I would guess that 3.4.x has no upstream support anymore. To me this looks like CVEs in other products, but which zookeeper uses as dependency? Is this correct? CVE-2021-21409 is for instance for netty and fixed in 1:41.48-4 and in DSA 4885-1. CVE-20202-25649 was in jackson-databind. Similar for the other CVEs mentioned in the release notes, and they usually refer to "upgrate X.Y to version [...], dependency check, etc. I have not (yet) checked the respective imapct and if something needs to be changed about those specifically in zookeeper. Regards, Salvatore
