Bug#992216: marked as done (thunderbird: Version 91 available upstream and fixes security problems)
Your message dated Mon, 16 Aug 2021 06:47:33 +0200 with message-id <1a98d160-9d96-8e68-010b-b7fb70e65...@t-online.de> and subject line Re: Bug#992216: thunderbird: Version 91 available upstream and fixes security problems has caused the Debian Bug report #992216, regarding thunderbird: Version 91 available upstream and fixes security problems 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.) -- 992216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: thunderbird Version: 78 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: demioben...@gmail.com, Debian Security Team Dear Maintainer, Mozilla has released Thunderbird 91, which fixes several security holes. Please upgrade the Thunderbird package. -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.136-1.fc25.qubes.x86_64 (SMP w/1 CPU thread) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) 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 pn libbotan-2-17 ii libbz2-1.0 1.0.8-4 ii libc62.31-13 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 pn libdbus-glib-1-2 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-7 ii libjson-c5 0.15-2 ii libnspr4 2:4.29-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.2-1 ii libx11-xcb1 2:1.7.2-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 pn x11-utils ii zlib1g 1:1.2.11.dfsg-2 Versions of packages thunderbird recommends: pn myspell-en-us | hunspell-dictionary | myspell-dictionary Versions of packages thunderbird suggests: ii apparmor 2.13.6-10 pn fonts-lyx ii libgssapi-krb5-2 1.18.3-6 pn libgtk2.0-0 --- End Message --- --- Begin Message --- tag -1 severity wishlist Hello, Am 16.08.21 um 00:13 schrieb Demi Marie Obenour: > Package: thunderbird > Version: 78 > Severity: grave such reports have quite never a severity of grave or serious. Please have a look (again) at the various types for the severity. https://www.debian.org/Bugs/server-control > Tags: security > Justification: user security hole > X-Debbugs-Cc: demioben...@gmail.com, Debian Security Team > > > Dear Maintainer, > > Mozilla has released Thunderbird 91, which fixes several security > holes. Please upgrade the Thunderbird package. Every source package has a tracker site where it is visible what versions are a currently packaged. For Thunderbird use this URL https://tracker.debian.org/pkg/thunderbird You can see there Thunderbird 91.0 is already uploaded to the archive backend, due to new languages, means there are new binary packages, the upload is waiting in the NEW queue for approval. I'll close this report now. -- Regards Carsten--- End Message ---
Bug#982459:
Hi, On Sun, Aug 15, 2021 at 2:45 AM Håkan T Johansson wrote: > > I believe that I have been hit by this bug too. Thanks for the bug amendment! The 4.1 release happened nearly three years ago. With bullseye released, I just uploaded the latest release candidate 4.2~rc2-2 from upstream to Debian unstable. Feel free to try that too. Thank you! Kind regards Felix Lechner
Processed: tagging 947521
Processing commands for cont...@bugs.debian.org: > tags 947521 + ftbfs Bug #947521 [src:florence] florence: build-depends on deprecated gnome-doc-utils Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 947521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992216: thunderbird: Version 91 available upstream and fixes security problems
Package: thunderbird Version: 78 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: demioben...@gmail.com, Debian Security Team Dear Maintainer, Mozilla has released Thunderbird 91, which fixes several security holes. Please upgrade the Thunderbird package. -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.136-1.fc25.qubes.x86_64 (SMP w/1 CPU thread) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) 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 pn libbotan-2-17 ii libbz2-1.0 1.0.8-4 ii libc62.31-13 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 pn libdbus-glib-1-2 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-7 ii libjson-c5 0.15-2 ii libnspr4 2:4.29-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.2-1 ii libx11-xcb1 2:1.7.2-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 pn x11-utils ii zlib1g 1:1.2.11.dfsg-2 Versions of packages thunderbird recommends: pn myspell-en-us | hunspell-dictionary | myspell-dictionary Versions of packages thunderbird suggests: ii apparmor 2.13.6-10 pn fonts-lyx ii libgssapi-krb5-2 1.18.3-6 pn libgtk2.0-0
Bug#973517: marked as done (libreoffice-canzeley-client: please depend on libreoffice-sdbc-mysql instead of transitional libreoffice-mysql-connector)
Your message dated Sun, 15 Aug 2021 15:52:50 + with message-id and subject line Bug#973517: fixed in libreoffice-canzeley-client 0.5.1-5 has caused the Debian Bug report #973517, regarding libreoffice-canzeley-client: please depend on libreoffice-sdbc-mysql instead of transitional libreoffice-mysql-connector 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.) -- 973517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-canzeley-client Version: 0.5.1-4 Severity: wishlist Hi Mechtilde, libreoffice-mysql-connector is (since long) a transitional package for libreoffice-sdbc-mysql (since it's not an extension anymore but integrated into LO proper.): # apt-cache show libreoffice-mysql-connector Package: libreoffice-mysql-connector Source: libreoffice Version: 1:7.0.3-1 Installed-Size: 216 Maintainer: Debian LibreOffice Maintainers Architecture: amd64 Depends: libreoffice-sdbc-mysql Description: transitional package for MariaDB/MySQL Connector extension for LibreOffice Description-md5: f67e8b039d42be412b79ebf1381a0f85 Homepage: http://www.libreoffice.org Tag: role::shared-lib Section: misc Priority: optional Filename: pool/main/libr/libreoffice/libreoffice-mysql-connector_7.0.3-1_amd64.deb Size: 198196 MD5sum: 63c1c27fcd8ec3c336a9cdf94b8720f7 SHA256: d6e335dd242c3bace5fc45a26408721d3add9ee0bd6dcab0dcfedf7387143bd1 So please make the libreoffice-mysql-connector alternative use libreoffice-sdbc-mysql. Since I remove the transitional package for 7.1 this will get "serious" problem when 7.1 will enter Debian after the bullseye freeze. (See https://release.debian.org/transitions/html/auto-libreoffice.html[1]) Regards, Rene [1] The l10n stuff will solve itself magically, for alphas I don't build translations. --- End Message --- --- Begin Message --- Source: libreoffice-canzeley-client Source-Version: 0.5.1-5 Done: Mechtilde Stehmann We believe that the bug you reported is fixed in the latest version of libreoffice-canzeley-client, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mechtilde Stehmann (supplier of updated libreoffice-canzeley-client 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, 15 Aug 2021 10:54:08 +0200 Source: libreoffice-canzeley-client Architecture: source Version: 0.5.1-5 Distribution: unstable Urgency: medium Maintainer: Mechtilde Stehmann Changed-By: Mechtilde Stehmann Closes: 973517 Changes: libreoffice-canzeley-client (0.5.1-5) unstable; urgency=medium . [ Mechtilde ] * [d7db9a1] Added entry for source-only upload - acknowledgement to Holger * [be16735] Removed double entries in d/changelog * [043ce21] Name of MySQL/MariaDB-Connector changed (Closes:#973517) * [8bb8a11] bumped to compat level 13 - removed d/compat * [d0e6d07] bumped standard version - no changes needed * [d0cc2e6] Added Rules-Requires-Root: no * [0c83e5f] Removed d/compat * [89e5fd6] Added d/u/metadata Checksums-Sha1: c8c1b9d7428f5199d1645950f91daf7f8aeb746f 2358 libreoffice-canzeley-client_0.5.1-5.dsc 571d94748a55feb268c2ed1afaaf3126dd31f861 1082173 libreoffice-canzeley-client_0.5.1.orig.tar.gz 9e6d663527ceb182864eb38e0738e918c626e733 1089270 libreoffice-canzeley-client_0.5.1.orig.tar.gz.asc 8d0169de370554b806c8e285a80172c5461691d9 12004 libreoffice-canzeley-client_0.5.1-5.debian.tar.xz ea8ff2a8ab110cf6ec86f27286c9495781300e9d 5793 libreoffice-canzeley-client_0.5.1-5_amd64.buildinfo Checksums-Sha256: 3994acf4c7aceae2b4bc49f9b23f390e0d487a83f6903feaa599d829407d329a 2358 libreoffice-canzeley-client_0.5.1-5.dsc 8044a16051fb09379cb036854d1012746839cc7e1ced22f61b36174a9ae47ac8 1082173 libreoffice-canzeley-client_0.5.1.orig.tar.gz f7164c5bc6dc041ed332e3dfac124c08e282e478bdf4f02dab004f4e141eec5f 1089270 libreoffice-canzeley-client_0.5.1.orig.tar.gz.asc 2fe2db8a4ac60da36e9894c0beb8eed2dfcda7ed5fe36093bbe0db52a339b623 12004 libreoffice-canzeley-client_0.5.1-5.debian.tar.xz
Bug#992098: version -6 seems to have introduced another bug
On zondag 15 augustus 2021 14:33:05 CEST Salvatore Bonaccorso wrote: > On Sun, Aug 15, 2021 at 12:03:23PM +0200, Diederik de Haas wrote: > > I don't know the best way to go about that though. Technically speaking, > > the reported issue is resolved. But users got another RC bug for it back. > I have no time in the nex few days, but if there is still an new issue > uncovered present with -6 which is to be sondisered RC, then we should > fill a new spearate bug for it. Havin it RC will make sure verison in > unstable will not migrate to testing. Filed as https://bugs.debian.org/992192 Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#992192: cpio: Cannot stat: No such file or directory errors on cpio operations
Package: cpio Version: 2.13+dfsg-6 Severity: grave Tags: upstream Justification: renders package unusable Forwarded: https://lists.gnu.org/archive/html/bug-cpio/2021-08/msg5.html The fix for bug #992098 introduced a new RC error. As bug #992098 is technically fixed (and 'done'), here's a new RC bug report for the new issue. Purpose is also to prevent transitioning to testing. When building a kernel, various operations are done with cpio and I'll post an excerpt below and will attach a log file with more. make[3]: Entering directory '/home/diederik/dev/debian/salsa/kernel-team/linux' dh_installdirs /usr/share/linux-support-5.13.0-trunk/lib/python/debian_linux /usr/share/linux-support-5.13.0-trunk/modules mkdir -p debian/linux-doc-5.13/usr/share/doc/linux-doc-5.13 set -o pipefail; \ find CREDITS MAINTAINERS README Documentation \ -name '.gitignore' -prune -o -name DocBook -prune -o \ -path Documentation/media -prune -o \ -path Documentation/sphinx -prune -o \ -name 'Makefile*' -prune -o \ -print | \ cpio -pd --preserve-modification-time '/home/diederik/dev/debian/salsa/kernel-team/linux/debian/linux-doc-5.13/usr/share/doc/linux-doc-5.13' cp debian/config.defines.dump debian/linux-support-5.13.0-trunk/usr/share/linux-support-5.13.0-trunk cp -R debian/installer debian/linux-support-5.13.0-trunk/usr/share/linux-support-5.13.0-trunk/installer cpio: s.rst: Cannot stat: No such file or directory dh_installdocs --link-doc=linux-doc-5.13 dh_installdocs --link-doc=linux-source-5.13 cp debian/lib/python/debian_linux/*.py debian/linux-support-5.13.0-trunk/usr/share/linux-support-5.13.0-trunk/lib/python/debian_linux dh_python3 cpio: xt: Cannot stat: No such file or directory cpio: t: Cannot stat: No such file or directory cpio: txt: Cannot stat: No such file or directory /usr/bin/make -f debian/rules.real VERSION=5.13 UPSTREAMVERSION=5.13 SOURCE_SUFFIX= SOURCE_BASENAME=linux SOURCEVERSION=5.13.9-1~exp1 ALL_FEATURESETS=none ABINAME=5.13.0-trunk install-base BUILDDEB_ARGS='-Zgzip -z1' cpio: xt: Cannot stat: No such file or directory make[3]: Entering directory '/home/diederik/dev/debian/salsa/kernel-team/linux' cpio: l-simple.yaml: Cannot stat: No such file or directory cpio: h8300-bsc.txt: Cannot stat: No such file or directory dh_installchangelogs https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992098#34 has 2 log files attached and I'll attach the 1st one here too. I think cpio-bug992098-attempt1.log shows the whole problem. Cheers, Diederik -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cpio depends on: ii libc6 2.31-13 cpio recommends no packages. Versions of packages cpio suggests: pn libarchive1 -- no debconf information diederik@bagend:~/dev/debian/salsa/kernel-team/linux$ export DEBIAN_KERNEL_JOBS=14 diederik@bagend:~/dev/debian/salsa/kernel-team/linux$ export ARCH=arm64 diederik@bagend:~/dev/debian/salsa/kernel-team/linux$ export CC=aarch64-linux-gnu-gcc-10 diederik@bagend:~/dev/debian/salsa/kernel-team/linux$ dpkg-architecture --host-arch arm64 DEB_BUILD_ARCH=amd64 DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH_BITS=64 DEB_BUILD_ARCH_CPU=amd64 DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_ARCH_LIBC=gnu DEB_BUILD_ARCH_OS=linux DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_ARCH=arm64 DEB_HOST_ARCH_ABI=base DEB_HOST_ARCH_BITS=64 DEB_HOST_ARCH_CPU=arm64 DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH_LIBC=gnu DEB_HOST_ARCH_OS=linux DEB_HOST_GNU_CPU=aarch64 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_HOST_GNU_TYPE=aarch64-linux-gnu DEB_HOST_MULTIARCH=aarch64-linux-gnu DEB_TARGET_ARCH=arm64 DEB_TARGET_ARCH_ABI=base DEB_TARGET_ARCH_BITS=64 DEB_TARGET_ARCH_CPU=arm64 DEB_TARGET_ARCH_ENDIAN=little DEB_TARGET_ARCH_LIBC=gnu DEB_TARGET_ARCH_OS=linux DEB_TARGET_GNU_CPU=aarch64 DEB_TARGET_GNU_SYSTEM=linux-gnu DEB_TARGET_GNU_TYPE=aarch64-linux-gnu DEB_TARGET_MULTIARCH=aarch64-linux-gnu diederik@bagend:~/dev/debian/salsa/kernel-team/linux$ fakeroot debian/rules binary-indep dh_testdir /usr/bin/make -f debian/rules.gen build-indep make[1]: Entering directory '/home/diederik/dev/debian/salsa/kernel-team/linux' /usr/bin/make -f debian/rules.real build-indep ABINAME='5.13.0-trunk' ALL_FEATURESETS='none' SOURCEVERSION='5.13.9-1~exp1' SOURCE_BASENAME='linux' SOURCE_SUFFIX='' UPSTREAMVERSION='5.13' VERSION='5.13' make[2]: Entering directory '/home/diederik/dev/debian/salsa/kernel-team/linux' make[2]: Nothing to be done
Bug#992098: version -6 seems to have introduced another bug
Hi Diederik, Aníbal, On Sun, Aug 15, 2021 at 12:03:23PM +0200, Diederik de Haas wrote: > On vrijdag 13 augustus 2021 13:42:33 CEST Aníbal Monsalve Salazar wrote: > > The Debian bug report is at: > > https://bugs.debian.org/992098 > > The bug is marked as fixed in 2.13+dfsg-6 and done and thereby the block for > a > transition to testing is lifted. I think it should be kept out of testing and > people warned through apt-listbugs until this issue is fully resolved. > > I don't know the best way to go about that though. Technically speaking, the > reported issue is resolved. But users got another RC bug for it back. I have no time in the nex few days, but if there is still an new issue uncovered present with -6 which is to be sondisered RC, then we should fill a new spearate bug for it. Havin it RC will make sure verison in unstable will not migrate to testing. Regards, Salvatore
Bug#990409: ca-cacert: should this package be removed?
Hi all, Short introduction: I'm involved in CAcert as former board member and currently not holding any executive function. So not officially speaking, but I can provide some insight. On Wed, Aug 11, 2021 at 02:50:27PM +0200, Axel Beckert wrote: > Timo Röhling wrote: > > * Axel Beckert [2021-08-11 13:27]: > > > I strongly disagree. CAcert offers way more types of certificates than > > > Let's Encrypt. For example does Let's Encrypt not provide any > > > certificates suitable for use as personal S/MIME e-mail certificates. Regarding the general discussion: Server certificates for the public is no more a (near) target, as we have little resources and efforts to be accepted by vendors are huge. The main asset of the CAcert community is the web of trust with assurances, allowing personal certificates for email, although it's true that users need to install the root certificate. Not true is that we didn't bother to update the certificate on our main page. In reality, the work on critical systems here required multiple visits to the data center with cross-border travels, which is not easy these days for several reasons. By reading our blog you get an impression about what is going on: https://blog.cacert.org/ > > Have you tried creating a personal S/MIME e-mail certificate lately? > > Nope. > > > Because I tried, and neither IE nor Edge nor Firefox nor Chrome nor Opera > > support the required HTML tag any more. Although this is slightly off-topic, this symptom illustrates that we have a large backlog after many years with few persons being active in development. Overall we gain momentum here, and also in other areas such as infrastructure. So one can expect progress in the future, likely seeing some small steps in the next months. Regarding certificate creation: * Providing a CSR created by other means is and ever was possible. Please follow "The manual way" here: https://wiki.cacert.org/EmailCertificates * A proof of concept about creating a CSR in the browser using a library exists, but this needs to be refined and will take some time to be publicly available. > > > But instead it offers longer living certificates for hosts not > > > directly reachable from the internet — which is a hell to achieve with > > > Let's Encrypt. > > > > Private hosts are usually managed with a private CA, which gives you > > much more control and versatility. > > Not everyone is capable of running their own CA. Have you every tried > "easyrsa"? It's anything but easy. (And I personally rather run an > internal CA based on CAcert's scripts — which I actually do — than on > easyrsa. Tried easyrsa mostly for OpenVPN and nearly ditched OpenVPN > just because they recommend this crap.) > > > Many companies do this, > > Yeah, and often with worse outcome than with CAcert... > > > and CAcert offers no advantage, since you'd still have to distribute > > their root certificates to all your clients. > > If it's available as a Debian package, that's a clear advantage from > my point of view. :-) Correct. This helps partners in signed/encrypted email conversions, because the trust can easily be installed by almost everyone, not only people which are interested and skilled in encryption. We'd love to have the package updated with the new class3 certificate and readded to Debian. > > > Again, I strongly disagree. I rather hope that Dmitry gets it back > > > into shape and then also offers it via bullseye-backports. > > > > Well, if you, Dmitry, or anyone else feels that their time is well > > spent on this package, by all means, go ahead. I just happen to > > think that your contributions would be more valuable elsewhere. > > I already have too many packages, so yes, I agree here. This though > does not change my opinion on this package (or on a lot of other > packages in Debian which I don't maintain, but consider important for > myself as well as the community in general). Does it help if I provide a patch? Kind regards, Gero
Bug#992098: version -6 seems to have introduced another bug
On vrijdag 13 augustus 2021 13:42:33 CEST Aníbal Monsalve Salazar wrote: > The Debian bug report is at: > https://bugs.debian.org/992098 The bug is marked as fixed in 2.13+dfsg-6 and done and thereby the block for a transition to testing is lifted. I think it should be kept out of testing and people warned through apt-listbugs until this issue is fully resolved. I don't know the best way to go about that though. Technically speaking, the reported issue is resolved. But users got another RC bug for it back. signature.asc Description: This is a digitally signed message part.
Bug#982459:
Hi, I believe that I have been hit by this bug too. What has happened for me is that the machine in question 'almost' locks up, with a read-only /, and such that most commands to debug further never complete due to waiting for filesystem action. It then requires a reboot. 'dmesg' has worked, and then shows ext4-related issues. However, they were not recorded to /var/log. I generally do not find any corruption on the filesystem itself when running fsck afterwards. On the machine I have a number of chroot debian installations of different releases. By pure chance I found that 'update-initramfs' was the trigger for the system hangs. I could then repeatably trigger the issue again. (Before this, it would happen as part of system maintenance (unattended upgrades in the chroots), so just spuriously hang the machine.) In my case, the chroot installations live on a ZFS filesystem. But the host system itself is on (multiple; /, /usr/, /var/ ) MD raid1. I have had /proc mounted in the chroots. But had forgotten /dev . After mounting /dev (and /dev/pts) in the chroots, the issue has not happened again. The issue was when the host system ran Buster, I then upgraded to Bullseye ~2 weeks ago, hoping it would be resolved, but the issue was still present after the upgrade. Only after that upgrade I found the update-initramfs trigger. I am running with sysvinit, both on host and chroots. Currently, I do not have hands-on access to the system, so cannot inspect or reboot it reliably. Should be able to do some further tests in a few weeks. Best regards, Håkan
Processed: Fwd: Accepted libreoffice 1:7.1.5-1 (source) into unstable
Processing commands for cont...@bugs.debian.org: > severity 973517 serious Bug #973517 [libreoffice-canzeley-client] libreoffice-canzeley-client: please depend on libreoffice-sdbc-mysql instead of transitional libreoffice-mysql-connector Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 973517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
