Bug#1010171: marked as done (sbuild's "unshare" test fails with gpg-agent 2.2.34-1)
Your message dated Thu, 28 Apr 2022 03:03:55 + with message-id and subject line Bug#1010171: fixed in gnupg2 2.2.35-1 has caused the Debian Bug report #1010171, regarding sbuild's "unshare" test fails with gpg-agent 2.2.34-1 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.) -- 1010171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sbuild Version: 0.83.0 Control: affects -1 + gpg-agent Control: tags -1 + patch When trying to upgrade to gnupg2 from version 2.2.27-1 to version 2.2.34-1, we see a failure in the unshare-qemuwrapper test: https://ci.debian.net/data/autopkgtest/testing/amd64/s/sbuild/21152998/log.gz + ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i /tmp/autopkgtest-lxc.29hmt_yk/downtmp/autopkgtest_tmp/id_rsa -T -p 10022 root@localhost env --chdir=/build/ AUTOPKGTEST_TMP=/tmp runuser -u user -- ./debian/tests/unshare Warning: Permanently added '[localhost]:10022' (ED25519) to the list of known hosts. gpg: keybox '/tmp/gpghome/pubring.kbx' created gpg: /tmp/gpghome/trustdb.gpg: trustdb created gpg: key F08FF84541F5A0C0: public key "sbuild fake uploader " imported gpg: key F08FF84541F5A0C0/F08FF84541F5A0C0: error sending to agent: Invalid argument gpg: key F08FF84541F5A0C0/A4179B1DD69E01DD: error sending to agent: Invalid argument gpg: key F08FF84541F5A0C0: secret key imported gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: secret keys imported: 1 I traced this error down to the use of "gpg --allow-secret-key-import --import" in the unshare script. GnuPG upstream has always maintained that use of gpg in scripts requires use of the --batch directive, which avoids the error. Why this error response was introduced in the change from GnuPG 2.2.27 to 2.2.34, i don't yet fully understand, but using --batch does avoid the problem. The attached patch should hopefully make the sbuild autopkgtest succeed with either version of GnuPG2. thanks for maintaining sbuild in debian! --dkg From 4bdf145dd92df9db01fa38e1ab33cf1c36926ce9 Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Mon, 25 Apr 2022 12:30:11 -0400 Subject: [PATCH] Use --batch with gpg when importing secret key The use of gpg here is automated, and should not trigger a prompt to the user. GnuPG upstream recommends always using --batch in contexts like this. With GnuPG 2.2.34, the import actually fails, with gpg-agent logging the following failures: 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- IMPORT_KEY --timestamp=20210125T124832 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 -> [[Confidential data not shown]] 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- [[Confidential data not shown]] 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- [[Confidential data not shown]] 2022-04-25 12:28:02 gpg-agent[899673] command 'IMPORT_KEY' failed: Invalid argument 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 -> ERR 16777261 Invalid argument 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- SETKEYDESC Please+enter+the+passphrase+to+import+the+OpenPGP+secret+key:%0A%22sbuild+fake+uploader+%22%0A255-bit+EDDSA+key,+ID+A4179B1DD69E01DD,% 0Acreated+2021-01-25+(main+key+ID+F08FF84541F5A0C0).%0A 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 -> OK 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- IMPORT_KEY --timestamp=20210125T124832 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 -> [[Confidential data not shown]] 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- [[Confidential data not shown]] 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- [[Confidential data not shown]] 2022-04-25 12:28:02 gpg-agent[899673] command 'IMPORT_KEY' failed: Invalid argument 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 -> ERR 16777261 Invalid argument 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 <- SETKEYDESC Please+enter+the+passphrase+to+import+the+OpenPGP+secret+key:%0A%22sbuild+fake+uploader+%22%0A255-bit+ECDH+key,+ID+52C3581ED0C37392,%0 Acreated+2021-01-25+(main+key+ID+F08FF84541F5A0C0).%0A 2022-04-25 12:28:02 gpg-agent[899673] DBG: chan_10 -> OK Using --batch here changes the IMPORT_KEY assuan directive such that it includes an --unattended flag, which bypasses the failures we're seeing on upgrading GnuPG in debian unstable. Having to perform this workaround is unfortunate. A better approach would be to rewrite sbuild's tooling to use OpenPGP utilities designed for operation in a script, but doing so is a larger and
Bug#963784: marked as done (qxw: New upstream release)
Your message dated Thu, 28 Apr 2022 00:33:48 + with message-id and subject line Bug#963784: fixed in qxw 20200708-1 has caused the Debian Bug report #963784, regarding qxw: New upstream release 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.) -- 963784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qxw Version: 20140331-1.1 Severity: normal Tags: a11y l10n There has been a new upstream release of qxw, which adds a host of new features, including unicode support and hex grids. Please update the package to provide it! -- 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) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qxw depends on: ii libc6 2.30-8 ii libcairo2 1.16.0-4 ii libglib2.0-0 2.64.3-1 ii libgtk2.0-0 2.24.32-4 ii libpcre3 2:8.39-13 Versions of packages qxw recommends: ii wamerican [wordlist] 2019.10.06-1 qxw suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qxw Source-Version: 20200708-1 Done: Nick Morrott We believe that the bug you reported is fixed in the latest version of qxw, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nick Morrott (supplier of updated qxw 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: Thu, 28 Apr 2022 01:03:11 +0100 Source: qxw Architecture: source Version: 20200708-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Nick Morrott Closes: 758005 901661 963784 Changes: qxw (20200708-1) unstable; urgency=medium . [ Nick Morrott ] * New upstream version 20200708 (Closes: #963784, #901661, #758005) * d/changelog: - Refresh to include only Debian releases * d/control: - Set Maintainer to Debian Games Team - Refresh Vcs-* fields for Debian Games Team - Add myself as an Uploader - Bump debhelper-compat level to 13 - Declare compliance with Debian Policy 4.6.0 - Drop unnecessary greater-than versioned dependencies - Update Homepage to HTTPS URL * d/copyright: - Add Upstream-Contact details - Refresh years of upstream copyright - Refresh years of Debian copyright * d/docs: - Drop empty file * d/gbp.conf: - Add initial gbp config - Set upstream-signatures = True * d/patches: - Drop gcc9.patch (upstream changes) * d/qxw.6: - Update homepage to HTTPS URL * d/rules: - Delete boilerplate cruft - Add hardening=+all to build * d/s/lintian-overrides: - We carry the manpage in debian/ - Upstream's development repository is private * d/u/metadata: - Add initial upstream metadata * d/watch: - Migrate to version 4 watch file format . [ Mark Owen ] * d/control: - Set Rules-Requires-Root source field to "no" - Refresh short and long package descriptions * d/copyright: - Migrate copyright file to Copyright Format 1.0 * d/qxw.6: - Refresh manpage documentation * d/qxw.lintian-overrides: - Add override for false positive in source * d/watch: - Migrate to HTTPS URL for source Checksums-Sha1: 286bbae9ac6f9b6fdef4751b5057219703e69ede 2206 qxw_20200708-1.dsc efbd08082eca37b7090eb94ca0fa094551e01e8d 235087 qxw_20200708.orig.tar.gz bb52a82499f97b33e9b5f28a44eb1fce64701daa 3104 qxw_20200708.orig.tar.gz.asc eeb3e002abd3fa040f73e52e51481f1c5a7eb030 6772 qxw_20200708-1.debian.tar.xz 88a8bb2af61f5b60b04c64b855a1521241c42293 11134 qxw_20200708-1_amd64.buildinfo Checksums-Sha256: de2936e2a7258f2319aa86aef387f866af3e481088002e73b544965e981e36f4 2206 qxw_20200708-1.dsc
Bug#901661: marked as done (qxw FTCBFS: upstream Makefile hard codes build architecture tools)
Your message dated Thu, 28 Apr 2022 00:33:48 + with message-id and subject line Bug#901661: fixed in qxw 20200708-1 has caused the Debian Bug report #901661, regarding qxw FTCBFS: upstream Makefile hard codes build architecture tools 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.) -- 901661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qxw Version: 20140331-1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap qxw fails to cross build from source, because the upstream Makefile hard codes build architecture build tools such as gcc or pkg-config. After making them substitutable, qxw cross builds successfully. Please consider applying the attached patch. Helmut --- qxw-20140331.orig/Makefile +++ qxw-20140331/Makefile @@ -24,7 +24,8 @@ all:: qxw deb:: qxw -CFLAGS := -Wall -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security `pkg-config --cflags glib-2.0` `pkg-config --cflags gtk+-2.0` -I/opt/local/include +PKG_CONFIG ?= pkg-config +CFLAGS := -Wall -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security `$(PKG_CONFIG) --cflags glib-2.0` `$(PKG_CONFIG) --cflags gtk+-2.0` -I/opt/local/include LFLAGS := -Wl,-Bsymbolic-functions -Wl,-z,relro -L/opt/local/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -lm -lcairo -lgobject-2.0 -lpcre -lglib-2.0 -pthread -lgthread-2.0 # -lrt as well? ifneq ($(filter deb,$(MAKECMDGOALS)),) @@ -34,22 +35,22 @@ endif qxw: qxw.o filler.o dicts.o gui.o draw.o Makefile - gcc -rdynamic -Wall -ldl qxw.o filler.o dicts.o gui.o draw.o $(LFLAGS) -o qxw + $(CC) -rdynamic -Wall -ldl qxw.o filler.o dicts.o gui.o draw.o $(LFLAGS) -o qxw qxw.o: qxw.c qxw.h filler.h dicts.h draw.h gui.h common.h Makefile - gcc $(CFLAGS) -c qxw.c -o qxw.o + $(CC) $(CFLAGS) -c qxw.c -o qxw.o gui.o: gui.c qxw.h filler.h dicts.h draw.h gui.h common.h Makefile - gcc $(CFLAGS) -c gui.c -o gui.o + $(CC) $(CFLAGS) -c gui.c -o gui.o filler.o: filler.c qxw.h filler.h dicts.h common.h Makefile - gcc $(CFLAGS) -c filler.c -o filler.o + $(CC) $(CFLAGS) -c filler.c -o filler.o dicts.o: dicts.c dicts.h gui.h common.h Makefile - gcc $(CFLAGS) -fno-strict-aliasing -c dicts.c -o dicts.o + $(CC) $(CFLAGS) -fno-strict-aliasing -c dicts.c -o dicts.o draw.o: draw.c qxw.h draw.h gui.h common.h Makefile - gcc $(CFLAGS) -c draw.c -o draw.o + $(CC) $(CFLAGS) -c draw.c -o draw.o .PHONY: clean clean: --- End Message --- --- Begin Message --- Source: qxw Source-Version: 20200708-1 Done: Nick Morrott We believe that the bug you reported is fixed in the latest version of qxw, 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 901...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nick Morrott (supplier of updated qxw 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: Thu, 28 Apr 2022 01:03:11 +0100 Source: qxw Architecture: source Version: 20200708-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Nick Morrott Closes: 758005 901661 963784 Changes: qxw (20200708-1) unstable; urgency=medium . [ Nick Morrott ] * New upstream version 20200708 (Closes: #963784, #901661, #758005) * d/changelog: - Refresh to include only Debian releases * d/control: - Set Maintainer to Debian Games Team - Refresh Vcs-* fields for Debian Games Team - Add myself as an Uploader - Bump debhelper-compat level to 13 - Declare compliance with Debian Policy 4.6.0 - Drop unnecessary greater-than versioned dependencies - Update Homepage to HTTPS URL * d/copyright: - Add Upstream-Contact details - Refresh years of upstream copyright - Refresh years of Debian copyright * d/docs: - Drop empty file * d/gbp.conf: - Add initial gbp config - Set upstream-signatures = True * d/patches: - Drop gcc9.patch (upstream changes) * d/qxw.6: - Update homepage to HTTPS URL * d/rules: - Delete boilerplate cruft - Add hardening=+all to build *
Bug#758005: marked as done (qxw: please support non-ASCII letters)
Your message dated Thu, 28 Apr 2022 00:33:48 + with message-id and subject line Bug#758005: fixed in qxw 20200708-1 has caused the Debian Bug report #758005, regarding qxw: please support non-ASCII letters 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.) -- 758005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qxw Version: 20140331-1 Severity: wishlist I've tried to use this excellent program for Polish crossword and it looks like that non-ASCII characters are not supported at all. I'm unable to type Polish letters directly from the keyboard, and Polish letters from my custom dictionary are displayed correctly in the word list, but converted into an ASCII equivalent when inserted. Is this a feature, a bug, or am I simply missing something? My default locale is en_US.utf8, but the same problems occurs when the program is started in pl_PL.utf8. Best regards Janusz -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qxw depends on: ii libc6 2.19-7 ii libcairo2 1.12.16-2 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.24-1 ii libpcre3 1:8.35-3 Versions of packages qxw recommends: ii wamerican [wordlist] 7.1-1 ii wpolish [wordlist]20130519-1 qxw suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qxw Source-Version: 20200708-1 Done: Nick Morrott We believe that the bug you reported is fixed in the latest version of qxw, 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 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nick Morrott (supplier of updated qxw 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: Thu, 28 Apr 2022 01:03:11 +0100 Source: qxw Architecture: source Version: 20200708-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Nick Morrott Closes: 758005 901661 963784 Changes: qxw (20200708-1) unstable; urgency=medium . [ Nick Morrott ] * New upstream version 20200708 (Closes: #963784, #901661, #758005) * d/changelog: - Refresh to include only Debian releases * d/control: - Set Maintainer to Debian Games Team - Refresh Vcs-* fields for Debian Games Team - Add myself as an Uploader - Bump debhelper-compat level to 13 - Declare compliance with Debian Policy 4.6.0 - Drop unnecessary greater-than versioned dependencies - Update Homepage to HTTPS URL * d/copyright: - Add Upstream-Contact details - Refresh years of upstream copyright - Refresh years of Debian copyright * d/docs: - Drop empty file * d/gbp.conf: - Add initial gbp config - Set upstream-signatures = True * d/patches: - Drop gcc9.patch (upstream changes) * d/qxw.6: - Update homepage to HTTPS URL * d/rules: - Delete boilerplate cruft - Add hardening=+all to build * d/s/lintian-overrides: - We carry the manpage in debian/ - Upstream's development repository is private * d/u/metadata: - Add initial upstream metadata * d/watch: - Migrate to version 4 watch file format . [ Mark Owen ] * d/control: - Set Rules-Requires-Root source field to "no" - Refresh short and long package descriptions * d/copyright: - Migrate copyright file to Copyright Format 1.0 * d/qxw.6: - Refresh manpage documentation * d/qxw.lintian-overrides: - Add override for false positive in source * d/watch: - Migrate to HTTPS URL for source Checksums-Sha1: 286bbae9ac6f9b6fdef4751b5057219703e69ede 2206 qxw_20200708-1.dsc efbd08082eca37b7090eb94ca0fa094551e01e8d 235087 qxw_20200708.orig.tar.gz bb52a82499f97b33e9b5f28a44eb1fce64701daa 3104 qxw_20200708.orig.tar.gz.asc eeb3e002abd3fa040f73e52e51481f1c5a7eb030 6772 qxw_20200708-1.debian.tar.xz
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
Bug#916870: marked as done (xrootconsole: debian/control Vcs- fields are dead)
Your message dated Wed, 27 Apr 2022 22:03:51 + with message-id and subject line Bug#916870: fixed in xrootconsole 1:0.6-5 has caused the Debian Bug report #916870, regarding xrootconsole: debian/control Vcs- fields are dead 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.) -- 916870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xrootconsole Version: 1:0.6-4 Severity: minor debian/control:Vcs-Git: https://anonscm.debian.org/git/collab-maint/xrootconsole.git debian/control:Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/xrootconsole.git These URLs are sitting on discontinued alioth, therefore dead. Downloading the source advices to use them to download the source, which is kind of not working. :-) --- End Message --- --- Begin Message --- Source: xrootconsole Source-Version: 1:0.6-5 Done: Axel Beckert We believe that the bug you reported is fixed in the latest version of xrootconsole, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated xrootconsole 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 23:21:44 +0200 Source: xrootconsole Architecture: source Version: 1:0.6-5 Distribution: unstable Urgency: medium Maintainer: Axel Beckert Changed-By: Axel Beckert Closes: 916870 969751 Changes: xrootconsole (1:0.6-5) unstable; urgency=medium . [ Helmut Grohne ] * Support DEB_BUILD_OPTIONS=nocheck. (Closes: #969751) . [ Axel Beckert ] * Move packaging repo to Salsa and update Vcs-* headers accordingly. (Closes: #916870) * Bump debhelper compatibility level to 13. + Replace debian/compat with versioned dependency on debhelper-compat. * Bump debian/watch version to 4 and use HTTPS. * Stop mentioning "loco" in package description as it is no more available in Debian. Mention "grc" instead. Also replace alternative dependency on "logo" with "grc" — it was a typo of "loco" anyways. * Declare compliance with Debian Policy 4.6.0. (No changes needed.) * Update copyright years in debian/copyright. Thanks Lintian! * Add lintian overrides for very-long-line-length-in-source-file. Checksums-Sha1: f3d79205c3825f03531d79b7965d237f610bf8d7 2012 xrootconsole_0.6-5.dsc 4b5cb15803cdd6e31c0e4d903d6d1664f3d4dc5f 17320 xrootconsole_0.6-5.debian.tar.xz f264b430d59817dcda5dae38637f13b5d78e0141 8199 xrootconsole_0.6-5_source.buildinfo Checksums-Sha256: 3867af9229683a06db5bf6e47d1e1d001dfcc5689b4a72e6f532038924c65350 2012 xrootconsole_0.6-5.dsc 332e080e61f02290454147f14624a94803e4664a996271cfab124633b48f9bcf 17320 xrootconsole_0.6-5.debian.tar.xz e1b079b42eddd15f7fb44e83c01ca30f2d715458673c3e1ca47dd5a966506f6e 8199 xrootconsole_0.6-5_source.buildinfo Files: c01147b3669811b90e5c87c738b07833 2012 x11 optional xrootconsole_0.6-5.dsc 8ffc50ca728ba470c85f112e4837464a 17320 x11 optional xrootconsole_0.6-5.debian.tar.xz db1b5bd12b6b3f741b2903286e1f918b 8199 x11 optional xrootconsole_0.6-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAmJptHkACgkQa+Zjx1o1 yXVuug/+LIHVsXN/tKDcZFXrn2aIWqXVOQBoAwFWhlr70EOxSYqOwFlQrOpz+H7Q 2/iqDWWQmojR6m8eTMBgMWTJ8DhSQ9xDls27Z+zvIu4LlCVlrAuaVxIYftX7YqFA DKeyS15fJLnqIT8f6+cUQahxHlIA44HeYR2KsfDSsdeK5w80QxNmWoArObhHCYK7 z55XyE20azf/cuBkAXjS5BG2XI65iv5RPlkP0CS5sy+bJdgfDbwJED1dkNXkghA4 26i8vl4dUHH49gZAe26plh+iL7IqGASyeg8FHi/roxpDsklEeiIJOJc3jZLwfk9f bwzXgJFLTQ3Fo6soigoTeyp3VkE331iiY8VLC3K4L9yrqFb/uS0HIqrn/FmRZf2v 8ANMlb/oY3Kt6hJpVQ+tgROHnbE3hU+nmWrXcskwk888JtVzewd9+opciimaFOWG qF1+6XyBCZ02mmf6NHawwwv1op9cTMvkD9ox2ERosNoMNpZfr542Ii0jgQbEQBOG jmjMaFxRi6OZeXZn2kzPgoyh4pU/uKZKjLr0RWAYNybk9ssCXgJ11Gn2BVQ59VA/ eXqEMfaJbHj1P2XuZYwagQZ+Kf76fRG+5kb/HihF4FPi/GRBSjmrKqAYhqjgKkWo ZI79obX/5HYHk7WGPfpRbikKisauE7Wn369ErJluIiluGHOALCk= =bfwb -END PGP SIGNATURE End Message ---
Bug#969751: marked as done (xrootconsole FTCBFS: fails running tests despite DEB_BUILD_OPTIONS=nocheck)
Your message dated Wed, 27 Apr 2022 22:03:51 + with message-id and subject line Bug#969751: fixed in xrootconsole 1:0.6-5 has caused the Debian Bug report #969751, regarding xrootconsole FTCBFS: fails running tests despite DEB_BUILD_OPTIONS=nocheck 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.) -- 969751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xrootconsole Version: 1:0.6-4 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs xrootconsole fails to cross build from source, because it fails running tests despite being given DEB_BUILD_OPTIONS=nocheck. The attached patch implements support for the nocheck build option. Please consider applying it. Helmut diff --minimal -Nru xrootconsole-0.6/debian/changelog xrootconsole-0.6/debian/changelog --- xrootconsole-0.6/debian/changelog 2017-10-30 02:57:03.0 +0100 +++ xrootconsole-0.6/debian/changelog 2020-09-07 20:24:47.0 +0200 @@ -1,3 +1,10 @@ +xrootconsole (1:0.6-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Support DEB_BUILD_OPTIONS=nocheck. (Closes: #-1) + + -- Helmut Grohne Mon, 07 Sep 2020 20:24:47 +0200 + xrootconsole (1:0.6-4) unstable; urgency=medium [ Axel Beckert ] diff --minimal -Nru xrootconsole-0.6/debian/control xrootconsole-0.6/debian/control --- xrootconsole-0.6/debian/control 2017-10-30 02:51:16.0 +0100 +++ xrootconsole-0.6/debian/control 2020-09-07 20:24:47.0 +0200 @@ -7,7 +7,7 @@ Build-Depends: debhelper (>= 10~), libx11-dev, xauth, - xvfb + xvfb Homepage: https://sourceforge.net/projects/xrootconsole/ Vcs-Git: https://anonscm.debian.org/git/collab-maint/xrootconsole.git Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/xrootconsole.git diff --minimal -Nru xrootconsole-0.6/debian/rules xrootconsole-0.6/debian/rules --- xrootconsole-0.6/debian/rules 2017-10-30 01:32:02.0 +0100 +++ xrootconsole-0.6/debian/rules 2020-09-07 20:24:45.0 +0200 @@ -12,7 +12,9 @@ dh_installchangelogs NEWS override_dh_auto_test: +ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) xvfb-run ./test +endif # Empty target override_dh_auto_install: --- End Message --- --- Begin Message --- Source: xrootconsole Source-Version: 1:0.6-5 Done: Axel Beckert We believe that the bug you reported is fixed in the latest version of xrootconsole, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated xrootconsole 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 23:21:44 +0200 Source: xrootconsole Architecture: source Version: 1:0.6-5 Distribution: unstable Urgency: medium Maintainer: Axel Beckert Changed-By: Axel Beckert Closes: 916870 969751 Changes: xrootconsole (1:0.6-5) unstable; urgency=medium . [ Helmut Grohne ] * Support DEB_BUILD_OPTIONS=nocheck. (Closes: #969751) . [ Axel Beckert ] * Move packaging repo to Salsa and update Vcs-* headers accordingly. (Closes: #916870) * Bump debhelper compatibility level to 13. + Replace debian/compat with versioned dependency on debhelper-compat. * Bump debian/watch version to 4 and use HTTPS. * Stop mentioning "loco" in package description as it is no more available in Debian. Mention "grc" instead. Also replace alternative dependency on "logo" with "grc" — it was a typo of "loco" anyways. * Declare compliance with Debian Policy 4.6.0. (No changes needed.) * Update copyright years in debian/copyright. Thanks Lintian! * Add lintian overrides for very-long-line-length-in-source-file. Checksums-Sha1: f3d79205c3825f03531d79b7965d237f610bf8d7 2012 xrootconsole_0.6-5.dsc 4b5cb15803cdd6e31c0e4d903d6d1664f3d4dc5f 17320 xrootconsole_0.6-5.debian.tar.xz f264b430d59817dcda5dae38637f13b5d78e0141 8199 xrootconsole_0.6-5_source.buildinfo Checksums-Sha256:
Bug#1010258: marked as done (python3-pymca5: flaky autopkgtest on i386)
Your message dated Wed, 27 Apr 2022 21:49:06 + with message-id and subject line Bug#1010258: fixed in pymca 5.7.1+dfsg-2 has caused the Debian Bug report #1010258, regarding python3-pymca5: flaky autopkgtest on i386 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.) -- 1010258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pymca5 Version: 5.7.1+dfsg-1 Severity: normal X-Debbugs-Cc: Picca Frédéric-Emmanuel Uploading a new version of python3-qtconsole with only changes to the autopkgtest suite (no changes to the python3 module at all) caused those packages depending on it to be retested on the CI system. One of these is pymca, and it failed: https://ci.debian.net/data/autopkgtest/testing/i386/p/pymca/21180621/log.gz I tried running it locally and it passed fine, as it did with the previous version of python3-qtconsole. So it seems that this test is flaky, at least with Python 3.10: == FAIL: testFullViewNumpy (McaStackViewTest.testMcaStackView) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/PyMca5/tests/McaStackViewTest.py", line 208, in testFullViewNumpy self._assertFullView(data) File "/usr/lib/python3/dist-packages/PyMca5/tests/McaStackViewTest.py", line 274, in _assertFullView numpy.testing.assert_array_equal(data[idxFull], File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 934, in assert_array_equal assert_array_compare(operator.__eq__, x, y, err_msg=err_msg, File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 844, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not equal Mismatched elements: 1 / 1512 (0.0661%) Max absolute difference: 4.54747351e-13 Max relative difference: 2.09568557e-16 x: array(1008.747835, 1009.708006, 1010.258788, ..., 1014.26906 , 1015.457929, 1016.341512], [1017.31171 , 1018.872885, 1019.41133 , ..., 1023.968694,... y: array(1008.747835, 1009.708006, 1010.258788, ..., 1014.26906 , 1015.457929, 1016.341512], [1017.31171 , 1018.872885, 1019.41133 , ..., 1023.968694,... -- Unfortunately the output does not show which elements mismatched or what their values were. I don't know how best to proceed with a flaky test; I could re-upload python3-qtconsole, but that doesn't seem like the best approach. Or perhaps this test could be marked as flaky or skipped on i386? It would be very good to resolve this, though, as it's one of the few things blocking spyder from migrating to testing. Thanks! Julian --- End Message --- --- Begin Message --- Source: pymca Source-Version: 5.7.1+dfsg-2 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of pymca, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated pymca 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 22:04:48 +0100 Source: pymca Architecture: source Version: 5.7.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian PaN Maintainers Changed-By: Julian Gilbey Closes: 1010258 Changes: pymca (5.7.1+dfsg-2) unstable; urgency=medium . * Team upload * Relax equality tests in test suite to avoid spurious floating point comparison failures (closes: #1010258) * Specify LC_ALL and HOME in autopkgtest test Checksums-Sha1: 35193fa21aadde329509ad518facbcaa015aecd2 2689 pymca_5.7.1+dfsg-2.dsc 3070a290f0ea550920aa73625e6bcca622f5255e 10760 pymca_5.7.1+dfsg-2.debian.tar.xz 67a9ddd77a5a4deb6e1464bdc17eb669e74eff54 17720 pymca_5.7.1+dfsg-2_amd64.buildinfo Checksums-Sha256: 4857a9468fcead36a00b7f7cad31f1888a6ffd5e41795f2ddd0080c085a11b6c 2689 pymca_5.7.1+dfsg-2.dsc
Bug#756151: marked as done (libnotify-bin: option -a is not described in notify-send man page)
Your message dated Wed, 27 Apr 2022 20:34:20 + with message-id and subject line Bug#756151: fixed in libnotify 0.7.11-1 has caused the Debian Bug report #756151, regarding libnotify-bin: option -a is not described in notify-send man page 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.) -- 756151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.7.6-2 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, the man page of notify-send is not up to date. 'notify-send --help' reports the existence of the option -a whereas it is not described in the man page. Regards Raphaël - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc6 2.19-7 ii libglib2.0-0 2.40.0-3 ii libnotify40.7.6-2 libnotify-bin recommends no packages. libnotify-bin suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iF4EAREIAAYFAlPT+v0ACgkQ02ibvTExoLut0wD/QkviCsuDKj8BFoIVlhMw+Hl1 o56NpMQLVoHiDmhEJZoA/iHW5/YsE/GsB9mMjFN9jN3Ob2M2zXJo6zQIwY97Bjjo =jnDL -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libnotify Source-Version: 0.7.11-1 Done: Marco Trevisan (Treviño) We believe that the bug you reported is fixed in the latest version of libnotify, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Trevisan (Treviño) (supplier of updated libnotify 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 21:47:25 +0200 Source: libnotify Built-For-Profiles: noudeb Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Marco Trevisan (Treviño) Closes: 559544 571181 609556 636343 679653 756151 Launchpad-Bugs-Fixed: 257135 674642 1970647 Changes: libnotify (0.7.11-1) unstable; urgency=medium . * New upstream release: - notify-send: Support for replacing an existing notification (LP: #257135, Closes: #559544) - notify-send: Support commas in icon filenames (LP: #674642) - notify-send: Give failing exit code if showing notification fails (LP: #1970647, Closes: #609556, Closes: #679653) - notify-send: Add support for notification actions and responses (Closes: #571181) - notify-send: Add option to wait until notification has been closed - notify-send: Add support for boolean hints (Closes: #636343) - docs/notify-send: Add missing --app-name to manpage (Closes: #756151) * debian/rules: Use DPKG_GENSYMBOLS_CHECK_LEVEL instead of override * debian: Use debhelper 13, and remove explicit --fail-missing * debian/control: Update Standards-Version, no change needed * debian/libnotify4.symbols: Add new symbols * debian/patches: Add transient option to man Checksums-Sha1: b48bb996b770f758dc1149035c818e8aa8817094 2541 libnotify_0.7.11-1.dsc 63716a27bea21e9d0e322eca67e2c9f45ca85fba 101616 libnotify_0.7.11.orig.tar.xz 7ae61a68e57a7110a30ccf793448f59d3657d2d6 9588 libnotify_0.7.11-1.debian.tar.xz fb33360a4d1cc9708ed1a47660c161047b67226b 18470 libnotify_0.7.11-1_source.buildinfo Checksums-Sha256: 28a3845167908e1ad2289a8dbc7badda7834057a71df23ebe5f76feb6f388d1d 2541 libnotify_0.7.11-1.dsc dd5682ec68220339e11c5159b7e012204a318dd1b3683a09c482ca421ab07375 101616 libnotify_0.7.11.orig.tar.xz 257e4b2658050dd44d9df56f75b1eed9c69db0bf55f42d5518b2d731c2f2e8eb 9588 libnotify_0.7.11-1.debian.tar.xz 5e8c37fe94629988197edd3b0b9832bf6b41d16afc3dca35ed28688a75174d67 18470 libnotify_0.7.11-1_source.buildinfo Files: 40b18745a38da25e06c4af52f5337c0d 2541 libs optional libnotify_0.7.11-1.dsc 0f987fbdcbc4f0c73937c52becd7e0ec 101616 libs optional
Bug#679653: marked as done (libnotify-bin: exit status is always zero (even in presence of errors))
Your message dated Wed, 27 Apr 2022 20:34:20 + with message-id and subject line Bug#679653: fixed in libnotify 0.7.11-1 has caused the Debian Bug report #679653, regarding libnotify-bin: exit status is always zero (even in presence of errors) 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.) -- 679653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.5.0-2 Severity: minor Hi, notify-send returns zero even in presence of errors. I don't know if it is really a bug or only a missing feature, but a different exit status would be appreciated. :) For example without a running X the command $ notify-send something obviously fails, but its exit status is zero: $ echo $? 0 Thanks -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable'), (550, 'testing'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-for-dummynet (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.32.3-1 GLib library of C routines ii libnotify1 [libnotify1-gtk2.1 0.5.0-2sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libnotify Source-Version: 0.7.11-1 Done: Marco Trevisan (Treviño) We believe that the bug you reported is fixed in the latest version of libnotify, 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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Trevisan (Treviño) (supplier of updated libnotify 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 21:47:25 +0200 Source: libnotify Built-For-Profiles: noudeb Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Marco Trevisan (Treviño) Closes: 559544 571181 609556 636343 679653 756151 Launchpad-Bugs-Fixed: 257135 674642 1970647 Changes: libnotify (0.7.11-1) unstable; urgency=medium . * New upstream release: - notify-send: Support for replacing an existing notification (LP: #257135, Closes: #559544) - notify-send: Support commas in icon filenames (LP: #674642) - notify-send: Give failing exit code if showing notification fails (LP: #1970647, Closes: #609556, Closes: #679653) - notify-send: Add support for notification actions and responses (Closes: #571181) - notify-send: Add option to wait until notification has been closed - notify-send: Add support for boolean hints (Closes: #636343) - docs/notify-send: Add missing --app-name to manpage (Closes: #756151) * debian/rules: Use DPKG_GENSYMBOLS_CHECK_LEVEL instead of override * debian: Use debhelper 13, and remove explicit --fail-missing * debian/control: Update Standards-Version, no change needed * debian/libnotify4.symbols: Add new symbols * debian/patches: Add transient option to man Checksums-Sha1: b48bb996b770f758dc1149035c818e8aa8817094 2541 libnotify_0.7.11-1.dsc 63716a27bea21e9d0e322eca67e2c9f45ca85fba 101616 libnotify_0.7.11.orig.tar.xz 7ae61a68e57a7110a30ccf793448f59d3657d2d6 9588 libnotify_0.7.11-1.debian.tar.xz fb33360a4d1cc9708ed1a47660c161047b67226b 18470 libnotify_0.7.11-1_source.buildinfo Checksums-Sha256: 28a3845167908e1ad2289a8dbc7badda7834057a71df23ebe5f76feb6f388d1d 2541 libnotify_0.7.11-1.dsc dd5682ec68220339e11c5159b7e012204a318dd1b3683a09c482ca421ab07375 101616 libnotify_0.7.11.orig.tar.xz 257e4b2658050dd44d9df56f75b1eed9c69db0bf55f42d5518b2d731c2f2e8eb 9588 libnotify_0.7.11-1.debian.tar.xz 5e8c37fe94629988197edd3b0b9832bf6b41d16afc3dca35ed28688a75174d67 18470
Bug#636343: marked as done (libnotify-bin: Add support for hint of type boolean)
Your message dated Wed, 27 Apr 2022 20:34:20 + with message-id and subject line Bug#636343: fixed in libnotify 0.7.11-1 has caused the Debian Bug report #636343, regarding libnotify-bin: Add support for hint of type boolean 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.) -- 636343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.7.3-2 Severity: normal *** Please type your report below this line *** Add support for hints of type boolean. This can be used for the hint 'transient', which makes the notification to be removed from daemon's queue after the bubble is destroyed. Without this the notifications remain in daemon's queue until it is full (20 notifications by default). When the queue is full, no more bubbles are displayed. I can provide a patch for this. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to sk_SK.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc6 2.13-13Embedded GNU C Library: Shared lib ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libnotify40.7.3-2sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libnotify Source-Version: 0.7.11-1 Done: Marco Trevisan (Treviño) We believe that the bug you reported is fixed in the latest version of libnotify, 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 636...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Trevisan (Treviño) (supplier of updated libnotify 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 21:47:25 +0200 Source: libnotify Built-For-Profiles: noudeb Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Marco Trevisan (Treviño) Closes: 559544 571181 609556 636343 679653 756151 Launchpad-Bugs-Fixed: 257135 674642 1970647 Changes: libnotify (0.7.11-1) unstable; urgency=medium . * New upstream release: - notify-send: Support for replacing an existing notification (LP: #257135, Closes: #559544) - notify-send: Support commas in icon filenames (LP: #674642) - notify-send: Give failing exit code if showing notification fails (LP: #1970647, Closes: #609556, Closes: #679653) - notify-send: Add support for notification actions and responses (Closes: #571181) - notify-send: Add option to wait until notification has been closed - notify-send: Add support for boolean hints (Closes: #636343) - docs/notify-send: Add missing --app-name to manpage (Closes: #756151) * debian/rules: Use DPKG_GENSYMBOLS_CHECK_LEVEL instead of override * debian: Use debhelper 13, and remove explicit --fail-missing * debian/control: Update Standards-Version, no change needed * debian/libnotify4.symbols: Add new symbols * debian/patches: Add transient option to man Checksums-Sha1: b48bb996b770f758dc1149035c818e8aa8817094 2541 libnotify_0.7.11-1.dsc 63716a27bea21e9d0e322eca67e2c9f45ca85fba 101616 libnotify_0.7.11.orig.tar.xz 7ae61a68e57a7110a30ccf793448f59d3657d2d6 9588 libnotify_0.7.11-1.debian.tar.xz fb33360a4d1cc9708ed1a47660c161047b67226b 18470 libnotify_0.7.11-1_source.buildinfo Checksums-Sha256: 28a3845167908e1ad2289a8dbc7badda7834057a71df23ebe5f76feb6f388d1d 2541 libnotify_0.7.11-1.dsc dd5682ec68220339e11c5159b7e012204a318dd1b3683a09c482ca421ab07375 101616 libnotify_0.7.11.orig.tar.xz 257e4b2658050dd44d9df56f75b1eed9c69db0bf55f42d5518b2d731c2f2e8eb 9588 libnotify_0.7.11-1.debian.tar.xz 5e8c37fe94629988197edd3b0b9832bf6b41d16afc3dca35ed28688a75174d67 18470
Bug#609556: marked as done (Unhelpful error message when DBUS_SESSION_BUS_ADDRESS is not set)
Your message dated Wed, 27 Apr 2022 20:34:20 + with message-id and subject line Bug#609556: fixed in libnotify 0.7.11-1 has caused the Debian Bug report #609556, regarding Unhelpful error message when DBUS_SESSION_BUS_ADDRESS is not set 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.) -- 609556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.5.0-2 Severity: minor /usr/bin/notify-send dies with the following error message when DBUS_SESSION_BUS_ADDRESS is not set: $ unset DBUS_SESSION_BUS_ADDRESS $ notify-send test (notify-send:1202): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Please emit a more sensible error message. It took me a while to track down. Thanks --- End Message --- --- Begin Message --- Source: libnotify Source-Version: 0.7.11-1 Done: Marco Trevisan (Treviño) We believe that the bug you reported is fixed in the latest version of libnotify, 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 609...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Trevisan (Treviño) (supplier of updated libnotify 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 21:47:25 +0200 Source: libnotify Built-For-Profiles: noudeb Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Marco Trevisan (Treviño) Closes: 559544 571181 609556 636343 679653 756151 Launchpad-Bugs-Fixed: 257135 674642 1970647 Changes: libnotify (0.7.11-1) unstable; urgency=medium . * New upstream release: - notify-send: Support for replacing an existing notification (LP: #257135, Closes: #559544) - notify-send: Support commas in icon filenames (LP: #674642) - notify-send: Give failing exit code if showing notification fails (LP: #1970647, Closes: #609556, Closes: #679653) - notify-send: Add support for notification actions and responses (Closes: #571181) - notify-send: Add option to wait until notification has been closed - notify-send: Add support for boolean hints (Closes: #636343) - docs/notify-send: Add missing --app-name to manpage (Closes: #756151) * debian/rules: Use DPKG_GENSYMBOLS_CHECK_LEVEL instead of override * debian: Use debhelper 13, and remove explicit --fail-missing * debian/control: Update Standards-Version, no change needed * debian/libnotify4.symbols: Add new symbols * debian/patches: Add transient option to man Checksums-Sha1: b48bb996b770f758dc1149035c818e8aa8817094 2541 libnotify_0.7.11-1.dsc 63716a27bea21e9d0e322eca67e2c9f45ca85fba 101616 libnotify_0.7.11.orig.tar.xz 7ae61a68e57a7110a30ccf793448f59d3657d2d6 9588 libnotify_0.7.11-1.debian.tar.xz fb33360a4d1cc9708ed1a47660c161047b67226b 18470 libnotify_0.7.11-1_source.buildinfo Checksums-Sha256: 28a3845167908e1ad2289a8dbc7badda7834057a71df23ebe5f76feb6f388d1d 2541 libnotify_0.7.11-1.dsc dd5682ec68220339e11c5159b7e012204a318dd1b3683a09c482ca421ab07375 101616 libnotify_0.7.11.orig.tar.xz 257e4b2658050dd44d9df56f75b1eed9c69db0bf55f42d5518b2d731c2f2e8eb 9588 libnotify_0.7.11-1.debian.tar.xz 5e8c37fe94629988197edd3b0b9832bf6b41d16afc3dca35ed28688a75174d67 18470 libnotify_0.7.11-1_source.buildinfo Files: 40b18745a38da25e06c4af52f5337c0d 2541 libs optional libnotify_0.7.11-1.dsc 0f987fbdcbc4f0c73937c52becd7e0ec 101616 libs optional libnotify_0.7.11.orig.tar.xz 6cbc61cf9127a540a30623b96f7c276c 9588 libs optional libnotify_0.7.11-1.debian.tar.xz 39c17ffd7d4be9b136148d9e86a5e2cc 18470 libs optional libnotify_0.7.11-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE1MUB2kjreXoIF1CTlEnC9QmWY18FAmJpnhgACgkQlEnC9QmW Y18hJg/9Gd+9whcjh28FkRTeBOGHvcwQh+bUYO0899YDLHbJGNrfI3ZHvzeOXfeL VTq5a4kNd9+Uj5CW13+gyOUlLPnogt2qjtNvg3IGA5TdfGesOKFOjHGgDRLeW0Zh kt7zZWubvVIplrmYbG2lyT0i+vpXztawa0punSe4f8QmJLw4vMhcBOw11J0Ju9wm ZlkpOvBI4FPyKVyoRdBAeD85H/dHrqektg1Tuki+XafNWrrO9S6Ij1JfwbRWCgYZ k4jITRocGX9SRcmBkyJ+h9ATdtUcC3bOGKinX30sMZIqjNKeNjT56D/UfRfIU+a+
Bug#559544: marked as done (libnotify-bin: Please support notification IDs)
Your message dated Wed, 27 Apr 2022 20:34:20 + with message-id and subject line Bug#559544: fixed in libnotify 0.7.11-1 has caused the Debian Bug report #559544, regarding libnotify-bin: Please support notification IDs 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.) -- 559544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.4.5-1 Severity: wishlist The DBus API provides a notification ID as the response to org.freedesktop.Notifications.Notify, and via the replace_id parameter supports replacing an existing notification. Please provide a command-line option (I'd suggest -r, --replace-id) to explicitly set the replace_id parameter. notify-send also needs a command-line option to display the ID to stdout, so that a script can capture the value for later use with -r. - Josh Triplett -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libglib2.0-0 2.22.3-1 The GLib library of C routines ii libnotify1 [libnotify1-gtk2.1 0.4.5-1sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libnotify Source-Version: 0.7.11-1 Done: Marco Trevisan (Treviño) We believe that the bug you reported is fixed in the latest version of libnotify, 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 559...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Trevisan (Treviño) (supplier of updated libnotify 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 21:47:25 +0200 Source: libnotify Built-For-Profiles: noudeb Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Marco Trevisan (Treviño) Closes: 559544 571181 609556 636343 679653 756151 Launchpad-Bugs-Fixed: 257135 674642 1970647 Changes: libnotify (0.7.11-1) unstable; urgency=medium . * New upstream release: - notify-send: Support for replacing an existing notification (LP: #257135, Closes: #559544) - notify-send: Support commas in icon filenames (LP: #674642) - notify-send: Give failing exit code if showing notification fails (LP: #1970647, Closes: #609556, Closes: #679653) - notify-send: Add support for notification actions and responses (Closes: #571181) - notify-send: Add option to wait until notification has been closed - notify-send: Add support for boolean hints (Closes: #636343) - docs/notify-send: Add missing --app-name to manpage (Closes: #756151) * debian/rules: Use DPKG_GENSYMBOLS_CHECK_LEVEL instead of override * debian: Use debhelper 13, and remove explicit --fail-missing * debian/control: Update Standards-Version, no change needed * debian/libnotify4.symbols: Add new symbols * debian/patches: Add transient option to man Checksums-Sha1: b48bb996b770f758dc1149035c818e8aa8817094 2541 libnotify_0.7.11-1.dsc 63716a27bea21e9d0e322eca67e2c9f45ca85fba 101616 libnotify_0.7.11.orig.tar.xz 7ae61a68e57a7110a30ccf793448f59d3657d2d6 9588 libnotify_0.7.11-1.debian.tar.xz fb33360a4d1cc9708ed1a47660c161047b67226b 18470 libnotify_0.7.11-1_source.buildinfo Checksums-Sha256: 28a3845167908e1ad2289a8dbc7badda7834057a71df23ebe5f76feb6f388d1d 2541 libnotify_0.7.11-1.dsc dd5682ec68220339e11c5159b7e012204a318dd1b3683a09c482ca421ab07375 101616 libnotify_0.7.11.orig.tar.xz 257e4b2658050dd44d9df56f75b1eed9c69db0bf55f42d5518b2d731c2f2e8eb 9588 libnotify_0.7.11-1.debian.tar.xz 5e8c37fe94629988197edd3b0b9832bf6b41d16afc3dca35ed28688a75174d67 18470
Bug#571181: marked as done (libnotify-bin: add a flag to specify buttons)
Your message dated Wed, 27 Apr 2022 20:34:20 + with message-id and subject line Bug#571181: fixed in libnotify 0.7.11-1 has caused the Debian Bug report #571181, regarding libnotify-bin: add a flag to specify buttons 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.) -- 571181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.4.5-1 Severity: wishlist Hello I’d like to be able to pass some parameters to notify-send to add buttons (things with a label and an action) in the notifications, something like: notify-send -i /path/to/mail-unread.svg "New email" \ --button Read icedove --button "Read in console" "xterm -x mutt" If the command line parser that you use doesn’t allow an option to consume two arguments, I’d be happy with the limitation, since notify-send is a demo/quick helper and I can write more complex things in Python. I can live with only one button. The syntax could be notify-send [...] --button-label Read --button-action icedove Thanks for considering this. Regards --- End Message --- --- Begin Message --- Source: libnotify Source-Version: 0.7.11-1 Done: Marco Trevisan (Treviño) We believe that the bug you reported is fixed in the latest version of libnotify, 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 571...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Trevisan (Treviño) (supplier of updated libnotify 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 21:47:25 +0200 Source: libnotify Built-For-Profiles: noudeb Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Marco Trevisan (Treviño) Closes: 559544 571181 609556 636343 679653 756151 Launchpad-Bugs-Fixed: 257135 674642 1970647 Changes: libnotify (0.7.11-1) unstable; urgency=medium . * New upstream release: - notify-send: Support for replacing an existing notification (LP: #257135, Closes: #559544) - notify-send: Support commas in icon filenames (LP: #674642) - notify-send: Give failing exit code if showing notification fails (LP: #1970647, Closes: #609556, Closes: #679653) - notify-send: Add support for notification actions and responses (Closes: #571181) - notify-send: Add option to wait until notification has been closed - notify-send: Add support for boolean hints (Closes: #636343) - docs/notify-send: Add missing --app-name to manpage (Closes: #756151) * debian/rules: Use DPKG_GENSYMBOLS_CHECK_LEVEL instead of override * debian: Use debhelper 13, and remove explicit --fail-missing * debian/control: Update Standards-Version, no change needed * debian/libnotify4.symbols: Add new symbols * debian/patches: Add transient option to man Checksums-Sha1: b48bb996b770f758dc1149035c818e8aa8817094 2541 libnotify_0.7.11-1.dsc 63716a27bea21e9d0e322eca67e2c9f45ca85fba 101616 libnotify_0.7.11.orig.tar.xz 7ae61a68e57a7110a30ccf793448f59d3657d2d6 9588 libnotify_0.7.11-1.debian.tar.xz fb33360a4d1cc9708ed1a47660c161047b67226b 18470 libnotify_0.7.11-1_source.buildinfo Checksums-Sha256: 28a3845167908e1ad2289a8dbc7badda7834057a71df23ebe5f76feb6f388d1d 2541 libnotify_0.7.11-1.dsc dd5682ec68220339e11c5159b7e012204a318dd1b3683a09c482ca421ab07375 101616 libnotify_0.7.11.orig.tar.xz 257e4b2658050dd44d9df56f75b1eed9c69db0bf55f42d5518b2d731c2f2e8eb 9588 libnotify_0.7.11-1.debian.tar.xz 5e8c37fe94629988197edd3b0b9832bf6b41d16afc3dca35ed28688a75174d67 18470 libnotify_0.7.11-1_source.buildinfo Files: 40b18745a38da25e06c4af52f5337c0d 2541 libs optional libnotify_0.7.11-1.dsc 0f987fbdcbc4f0c73937c52becd7e0ec 101616 libs optional libnotify_0.7.11.orig.tar.xz 6cbc61cf9127a540a30623b96f7c276c 9588 libs optional libnotify_0.7.11-1.debian.tar.xz 39c17ffd7d4be9b136148d9e86a5e2cc 18470 libs optional libnotify_0.7.11-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE1MUB2kjreXoIF1CTlEnC9QmWY18FAmJpnhgACgkQlEnC9QmW
Processed: RFS: kmscon/8+40-1 [ITP] -- Simple terminal emulator based on Kernel Mode Setting
Processing commands for cont...@bugs.debian.org: > close 1004922 Bug #1004922 [sponsorship-requests] RFS: kmscon/8+40-1 [ITP] -- Simple terminal emulator based on Kernel Mode Setting Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1004922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008266: marked as done (unar: obsolete syntax of bash-completion file)
Your message dated Wed, 27 Apr 2022 19:34:23 + with message-id and subject line Bug#1008266: fixed in unar 1.10.7+ds1-1 has caused the Debian Bug report #1008266, regarding unar: obsolete syntax of bash-completion file 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.) -- 1008266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Version: 1.10.1-2+b6 Severity: normal Tags: patch X-Debbugs-Cc: sa...@lyx.org Dear Maintainer, bash-completion script syntax is outdated for this package and as a result completion does not work here. The situation can be simply fixed by replacing "have" to "_have" keyword at lines 3 & 46. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads) Locale: LANG=C, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unar depends on: ii dpkg 1.20.9 ii gnustep-base-runtime 1.27.0-3 ii libbz2-1.01.0.8-4 ii libc6 2.31-13+deb11u2 ii libgcc-s1 10.2.1-6 ii libgnustep-base1.27 1.27.0-3 ii libicu67 67.1-7 ii libobjc4 10.2.1-6 ii libstdc++610.2.1-6 ii libwavpack1 5.4.0-1 ii zlib1g1:1.2.11.dfsg-2 unar recommends no packages. unar suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: unar Source-Version: 1.10.7+ds1-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of unar, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated unar 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 15:10:23 -0400 Source: unar Architecture: source Version: 1.10.7+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Closes: 974972 1008266 Changes: unar (1.10.7+ds1-1) unstable; urgency=medium . * QA upload. * New upstream version 1.10.7. (Closes: #974972) + Import separate UniversalDetector v1.1 as component. * debian/control: Use "Rules-Requires-Root: no". * debian/unar.maintscript: Migrate away from dpkg-maintscript-helper. * debian/unar-bash-completion: Drop obsolete syntax. (Closes: #1008266) (LP: #1775046) * debian/unar.bash-completion: Install upstream-provided bash completion. * debian/unar.manpages: Install upstream-provided man pages. * debian/watch: Monitor new upstream on GitHub. * debian/copyright: + Update Files-Excluded field for source package repack. * debian/rules: + Drop obsolete get-orig-source target. + Update manual post-build test commands. * debian/patches: Analyze all old patches: - fix-crashes.patch: Dropped, applied upstream. + CSInputBuffer-bit-string-reading.patch: Refreshed as 0001-Proper-fix-for-CSInputBuffer-bit-string-reading.patch. - gnustep-support.patch: Dropped, original source file disappeared. - proper-init-autoreleasepool.patch: Dropped, original file disappeared. - document-undocumented-options.patch: Dropped, applied upstream. - use-system-wavpack.patch: Dropped, applied upstream. + pass-cppflags-for-fortify-functions.patch: Refreshed as 0003-Pass-CPPFLAGS-to-use-hardening-flags-fortify-functio.patch. - remove-build-date.patch: Dropped, no longer needed since newer GCC already made __DATE__ reproducible. * debian/patches: + Add 0002-Do-not-use-NATIVE_OBJC_EXCEPTIONS.patch. Taken from Arch Linux. Checksums-Sha1: 6a44b073a161ca5880e65435ed143cb5a0c736a4 2601 unar_1.10.7+ds1-1.dsc 9159094e887505ff4f238b27b918d8fbaff7743e 120888 unar_1.10.7+ds1.orig-UniversalDetector.tar.xz
Bug#974972: marked as done (unar: There is a new upstream version)
Your message dated Wed, 27 Apr 2022 19:34:23 + with message-id and subject line Bug#974972: fixed in unar 1.10.7+ds1-1 has caused the Debian Bug report #974972, regarding unar: There is a new upstream version 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.) -- 974972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Version: 1.10.1-2+b6 Severity: important Hi, unar code is now hosted on GitHub under the address: https://github.com/MacPaw/XADMaster The latest version is 1.10.7 and it contains many bugfixes: https://github.com/MacPaw/XADMaster/releases I hope unar can be updated in Debian. Thanks --- End Message --- --- Begin Message --- Source: unar Source-Version: 1.10.7+ds1-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of unar, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated unar 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 15:10:23 -0400 Source: unar Architecture: source Version: 1.10.7+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Closes: 974972 1008266 Changes: unar (1.10.7+ds1-1) unstable; urgency=medium . * QA upload. * New upstream version 1.10.7. (Closes: #974972) + Import separate UniversalDetector v1.1 as component. * debian/control: Use "Rules-Requires-Root: no". * debian/unar.maintscript: Migrate away from dpkg-maintscript-helper. * debian/unar-bash-completion: Drop obsolete syntax. (Closes: #1008266) (LP: #1775046) * debian/unar.bash-completion: Install upstream-provided bash completion. * debian/unar.manpages: Install upstream-provided man pages. * debian/watch: Monitor new upstream on GitHub. * debian/copyright: + Update Files-Excluded field for source package repack. * debian/rules: + Drop obsolete get-orig-source target. + Update manual post-build test commands. * debian/patches: Analyze all old patches: - fix-crashes.patch: Dropped, applied upstream. + CSInputBuffer-bit-string-reading.patch: Refreshed as 0001-Proper-fix-for-CSInputBuffer-bit-string-reading.patch. - gnustep-support.patch: Dropped, original source file disappeared. - proper-init-autoreleasepool.patch: Dropped, original file disappeared. - document-undocumented-options.patch: Dropped, applied upstream. - use-system-wavpack.patch: Dropped, applied upstream. + pass-cppflags-for-fortify-functions.patch: Refreshed as 0003-Pass-CPPFLAGS-to-use-hardening-flags-fortify-functio.patch. - remove-build-date.patch: Dropped, no longer needed since newer GCC already made __DATE__ reproducible. * debian/patches: + Add 0002-Do-not-use-NATIVE_OBJC_EXCEPTIONS.patch. Taken from Arch Linux. Checksums-Sha1: 6a44b073a161ca5880e65435ed143cb5a0c736a4 2601 unar_1.10.7+ds1-1.dsc 9159094e887505ff4f238b27b918d8fbaff7743e 120888 unar_1.10.7+ds1.orig-UniversalDetector.tar.xz 1ba979a795b8c0bb887cba9a062bccb6e0ed59c6 1007064 unar_1.10.7+ds1.orig-XADMaster.tar.xz b8a8447a89d120fde9c1a4656c4fafe7c1735403 616 unar_1.10.7+ds1.orig.tar.xz 9803034ff9e6afe96c347be107744f8bfe25fea7 14960 unar_1.10.7+ds1-1.debian.tar.xz 65fb7f309156509d40b7c6cd7db453c77e375c31 7024 unar_1.10.7+ds1-1_amd64.buildinfo Checksums-Sha256: 3ea842b47f79f57aa73e0ff64153c43a3693920b3102293c822f5a98c17f584b 2601 unar_1.10.7+ds1-1.dsc e5961e5150042995e28ac355fd890d384e8f0fa5474ba59c12d1a2435f91560e 120888 unar_1.10.7+ds1.orig-UniversalDetector.tar.xz ced8c12e90d4aee17be0ceca4b91b38fc2eb3b3280463b6104153aeb8a578356 1007064 unar_1.10.7+ds1.orig-XADMaster.tar.xz 59c0fdbc75d008c4f9e0b52284b55790beeaa143eaf861d13b3d959f9915e10c 616 unar_1.10.7+ds1.orig.tar.xz 6209b943577011a0849dd0e92d1ff85becf484d3941a41061f17e2c49508f465 14960 unar_1.10.7+ds1-1.debian.tar.xz add4e540047e87a14a4de47546939dd8d81a9cdf67e33c40529bd278071c620a 7024
Bug#1010123: marked as done (network-manager: Wifi randomly stops after upgrade and do not auto connect)
Your message dated Wed, 27 Apr 2022 21:28:17 +0200 with message-id <31207b5e-3c56-9b39-7916-6911cdb22...@debian.org> and subject line Re: [Pkg-utopia-maintainers] Bug#1010123: network-manager: Wifi randomly stops after upgrade and do not auto connect has caused the Debian Bug report #1010123, regarding network-manager: Wifi randomly stops after upgrade and do not auto connect 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.) -- 1010123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: network-manager Version: 1.36.4-2 Severity: normal Dear Maintainer, After upgrade, I got wifi randomly disconnected. I need to turn off and on it in order to get it back on or I need to restart NM by # systemctl restart NetworkManager.service logs - after wifi disconnected/stopped # journalctl -f abr 24 12:01:03 marcelo dbus-daemon[712]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' abr 24 12:01:03 marcelo systemd[1]: Started Network Manager Script Dispatcher Service. abr 24 12:01:04 marcelo NetworkManager[780]: [1650812464.3696] dhcp4 (wlp2s0): state changed new lease, address=192.168.1.175 abr 24 12:01:04 marcelo soffice.bin[9591]: g_object_weak_unref: couldn't find weak ref 0x7fa6e7a07d10(0x7fa6c8009360) abr 24 12:01:14 marcelo systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. abr 24 12:01:15 marcelo wpa_supplicant[781]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-37 noise=-93 txrate=72200 abr 24 12:03:01 marcelo wpa_supplicant[781]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-32 noise=-93 txrate=72200 abr 24 12:03:07 marcelo wpa_supplicant[781]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-21 noise=-95 txrate=72200 abr 24 12:03:09 marcelo wpa_supplicant[781]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-21 noise=-95 txrate=72200 abr 24 12:03:23 marcelo wpa_supplicant[781]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-13 noise=-95 txrate=72200 after turn off and turn on wifi (I turn off and turn on it by Networking- manager dropdown menu in right side up corner) or after run # systemctl restart NetworkManager.service # journalctl -f abr 24 12:07:48 marcelo PackageKit[1377]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh abr 24 12:07:48 marcelo PackageKit[1377]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh abr 24 12:07:49 marcelo goa-daemon[3378]: secret_password_lookup_sync() returned NULL abr 24 12:07:49 marcelo PackageKit[1377]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) abr 24 12:07:49 marcelo PackageKit[1377]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) abr 24 12:07:49 marcelo PackageKit[1377]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh abr 24 12:07:49 marcelo PackageKit[1377]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh abr 24 12:07:50 marcelo PackageKit[1377]: get-details transaction /17151_bebcddce from uid 1000 finished with success after 5070ms abr 24 12:07:50 marcelo goa-daemon[3378]: secret_password_lookup_sync() returned NULL abr 24 12:07:56 marcelo systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. abr 24 12:08:26 marcelo PackageKit[1377]: refresh-cache transaction /17148_acddadad from uid 1000 finished with success after 36393ms abr 24 12:08:26 marcelo gnome-software[3560]: failed to refresh the cache: Failed to download ‘https://odrs.gnome.org/1.0/reviews/api/ratings’: Cannot resolve hostname: Erro ao resolver “odrs.gnome.org”: Nome ou serviço desconhecido abr 24 12:08:30 marcelo PackageKit[1377]: refresh-cache transaction /17149_aeddeabb from uid 1000 finished with cancelled-priority after 3887ms abr 24 12:08:30 marcelo packagekitd[1377]: Falhou o download de alguns ficheiros de índice. Foram ignorados ou os antigos foram usados em seu lugar. abr 24 12:08:30 marcelo gnome-software[3560]: failed to refresh the cache: Failed to download ‘https://odrs.gnome.org/1.0/reviews/api/ratings’: Cannot resolve hostname: Erro ao resolver “odrs.gnome.org”: Nome ou serviço desconhecido abr 24 12:08:34 marcelo PackageKit[1377]: get-updates transaction /17167_edccedea from uid 1000 finished with success after 3655ms abr 24 12:08:36 marcelo PackageKit[1377]: refresh-cache transaction /17152_ccdebacd from uid 1000 finished with cancelled-priority after 2014ms abr 24 12:08:36 marcelo
Bug#1008823: marked as done (transition: thrift)
Your message dated Wed, 27 Apr 2022 21:03:36 +0200 with message-id and subject line Re: Bug#1008823: transition: thrift has caused the Debian Bug report #1008823, regarding transition: thrift 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.) -- 1008823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi RMs, A quick transition of thrift from 0.13.0 to 0.16.0 as the only reverse build dependency is gnuradio. It builds with the new thrift version as well. Thanks for considering, Laszlo/GCS --- End Message --- --- Begin Message --- On 2022-04-27 20:40:34, Sebastian Ramacher wrote: > On 2022-04-26 10:11:34 +0200, Sebastian Ramacher wrote: > > Hi > > > > On 2022-04-19 14:12:33, Sebastian Ramacher wrote: > > > Control: tags -1 confirmed > > > Control: forwarded -1 > > > https://release.debian.org/transitions/html/auto-thrift.html > > > > > > On 2022-04-02 11:48:40, László Böszörményi wrote: > > > > Package: release.debian.org > > > > Severity: normal > > > > User: release.debian@packages.debian.org > > > > Usertags: transition > > > > > > > > Hi RMs, > > > > > > > > A quick transition of thrift from 0.13.0 to 0.16.0 as the only reverse > > > > build dependency is gnuradio. It builds with the new thrift version as > > > > well. > > > > > > Please go ahead > > > > Please ensure in the next upload that libthrift-0.16.0 and > > libthrift-c-glib0 are in Section libs. This will ensure that for the > > next thrift transition britney can perform a smooth update. > > Thanks! > > thrift migrated and the old binary packages got removed. … and let's really close it. Cheers -- Sebastian Ramacher--- End Message ---
Processed: closing 909401
Processing commands for cont...@bugs.debian.org: > close 909401 Bug #909401 [mailutils] mailutils: don't know what 2047 is Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 909401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911977: marked as done (how do we correctly guess the VM name in autopkgtest?)
Your message dated Wed, 27 Apr 2022 14:46:38 -0400 with message-id <8735hyqs8h@curie.anarc.at> and subject line Re: Bug#911977: how do we correctly guess the VM name in autopkgtest? has caused the Debian Bug report #911977, regarding how do we correctly guess the VM name in autopkgtest? 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.) -- 911977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sbuild Version: 0.77.1-1 Severity: wishlist One of the nice things with the schroot backend is that it automatically guesses which schroot to use based on internal sbuild logic. If I build a stretch-security update, it will find my stretch chroot, for example. This doesn't seem to work with the autopkgtest backend: $ sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu [...] dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.debian.tar.bz2 dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.dsc dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: --compression=bzip2 --compression-level=9 sbuild (Debian sbuild) 0.77.1 (10 September 2018) on curie.anarc.at +==+ | gnupg2 2.1.18-8~deb9u3 (amd64) Fri, 26 Oct 2018 19:13:13 + | +==+ Package: gnupg2 Version: 2.1.18-8~deb9u3 Source Version: 2.1.18-8~deb9u3 Distribution: stretch Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full usage: autopkgtest-virt-qemu [-h] [-q QEMU_COMMAND] [-o OVERLAY_DIR] [-u USER] [-p PASSWORD] [-c CPUS] [--ram-size RAM_SIZE] [--timeout-reboot SECONDS] [--show-boot] [-d] [--qemu-options QEMU_OPTIONS] [--baseimage] [--efi] image [image ...] autopkgtest-virt-qemu: error: the following arguments are required: image Undefined chroot status E: Error creating chroot session: skipping gnupg2 Now of course I can fix this by passing the image in an argument, but then I am hardcoding that image path which is release dependent. Shouldn't it be better for sbuild to correctly figure that out? -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sbuild depends on: ii adduser 3.118 ii libsbuild-perl 0.77.1-1 ii perl5.26.2-7+b1 Versions of packages sbuild recommends: ii autopkgtest 5.6 ii debootstrap 1.0.109 ii schroot 1.6.10-5 Versions of packages sbuild suggests: ii deborphan 1.7.30 ii kmod 25-1 ii wget 1.19.5-1 -- debconf-show failed --- End Message --- --- Begin Message --- On 2022-03-09 09:36:13, Johannes Schauer Marin Rodrigues wrote: > Hi, > > Quoting Andrea Pappacoda (2022-02-19 15:39:12) >> > I have in my ~/.sbuildrc: >> > >> > $autopkgtest_opts = [ '--', 'schroot', '%r-%a-sbuild' ]; >> > >> > The %r and %a escapes expand to the current distribution and architecture. >> >> Thanks, this works really well! Would it be possible for sbuild to pass >> these options by default when the backend is schroot? This way users >> would be able to simply specify --run-autopkgtest to run tests without root >> privileges. > > I don't think that this would be easily possible. Whenever you let something > have a default you must also provide a way to change the default. This becomes > especially hairy because whichever way we implement that lets users change the > default now must also be conditionalized with schroot being the backend or > not. > > I think this is yet another sign of why sbuild running autopkgtest is a layer > violation. Instead of sbuild running autopkgtest, piuparts and lintian, there > should be a tool above sbuild which runs sbuild, autopkgtest, piuparts and > lintian. Sbuild doing the job is just a convenience option because we don't > have such a tool above sbuild yet but it would be the responsibility of that > tool to find out that it can drive both sbuild and autopkgtest with schroot. > > I'm very
Bug#601897: marked as done (libnotify1: Raises exception if notify_uninit is called immediately after notify_init)
Your message dated Wed, 27 Apr 2022 20:32:14 +0200
with message-id <1595a688-2c77-4e8f-ab65-73d0c0145...@getmailspring.com>
and subject line Bug #601897
has caused the Debian Bug report #601897,
regarding libnotify1: Raises exception if notify_uninit is called immediately
after notify_init
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.)
--
601897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnotify1
Version: 0.5.0-2
Severity: normal
libnotify raises the following exception in notify_uninit if it is
called immediately after notify_init:
GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)'
failed
If notify_notification_new is called between notify_init and
notify_uninit, the exception is not raised.
Code to reproduce:
#include
int main (void)
{
notify_init ("test");
notify_uninit ();
return 0;
}
Backtrace:
#0 IA__g_return_if_fail_warning (log_domain=0x75145712 "GLib-GObject",
pretty_function=0x75147370 "IA__g_object_unref",
expression=0x7514653a "G_IS_OBJECT (object)")
at /scratch/build-area/glib2.0-2.24.2/glib/gmessages.c:577
#1 0x77bda02a in notify_uninit () from /usr/lib/libnotify.so.1
#2 0x004007c7 in main () at notify.c:6
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libnotify1 depends on:
ii libc6 2.11.2-6+squeeze1 Embedded GNU C Library: Shared lib
ii libdbus-glib-1-2 0.88-2simple interprocess messaging syst
ii libglib2.0-0 2.24.2-1 The GLib library of C routines
ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface
Versions of packages libnotify1 recommends:
ii notification-daemon 0.5.0-2daemon to displays passive pop-up
libnotify1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Test case is working correctly now.--- End Message ---
Bug#499904: marked as done (libnotify-bin: notify-send incorrect display text with long words)
Your message dated Wed, 27 Apr 2022 20:30:34 +0200 with message-id and subject line Bug #499904 has caused the Debian Bug report #499904, regarding libnotify-bin: notify-send incorrect display text with long words 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.) -- 499904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.4.4-3 Severity: normal Hello! Sometimes notify-send does not show full text message. For example, command % notify-send 'summary' 'CashoutOutsController sometext CashoutOutsController' will show only first two words "CashoutOutsController sometext". But % notify-send 'summary' 'CashoutOutsController sometextsometext CashoutOutsController' and % notify-send 'summary' 'CashoutOutsController text CashoutOutsController' works prefectly. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libnotify-bin depends on: ii libc6 2.7-12 GNU C Library: Shared libraries ii libglib2.0-0 2.16.4-1 The GLib library of C routines ii libnotify1 [libnotify1-gtk2.1 0.4.4-3sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Not a library bug, may have been due to the desktop environment.--- End Message ---
Bug#630539: marked as done (libnotify1: Notifications cause menu items to go black.)
Your message dated Wed, 27 Apr 2022 20:29:30 +0200 with message-id <7ed0f3ce-2c32-4e5f-a4ff-b274240f7...@getmailspring.com> and subject line Bug #630539 has caused the Debian Bug report #630539, regarding libnotify1: Notifications cause menu items to go black. 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.) -- 630539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify1 Version: 0.5.0-2 Severity: normal When receiving a notification via libnotify, either through thunderbird, or pidgin(the two current methods that I've observed). It has the chance to cause the menu items to go black. Currently it is the Gnome menu bar, and two widths of the "Places" menu to teh right are also black. This usually happens ever couple dozen of notifications. The buttons and such do come back, after moving my mouse over them. The reason for it's breaking of the system is well beyond me. This issue has been in testing for about two weeks now. I don't know which update has caused it, but I've personally noticed it for about that long. I'm using gnome of course as my primary desktop. It's the latest gnome2 version. It seems to happen a second or two before the notification comes completely into view. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify1 depends on: ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libdbus-glib-1-2 0.94-2 simple interprocess messaging syst ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface Versions of packages libnotify1 recommends: ii notification-daemon 0.5.0-2daemon to displays passive pop-up libnotify1 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Not a library issue--- End Message ---
Bug#617958: marked as done (libnotify-bin: Critical notifications should not expire)
Your message dated Wed, 27 Apr 2022 20:11:17 +0200 with message-id <53c29f39-fc84-4c61-b64a-ac22f14cc...@getmailspring.com> and subject line Bug #617958 has caused the Debian Bug report #617958, regarding libnotify-bin: Critical notifications should not expire 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.) -- 617958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.5.0-2 Severity: important Consider this usage: notify-send --urgency=critical "Low battery" In my system, that notification expires after about 7 seconds. Now, the specification states: "Critical notifications should not automatically expire, as they are things that the user will most likely want to know about. They should only be closed when the user dismisses them, for example, by clicking on the notification." This issue might as well qualify for a "grave" severity, since an unattended critical notification could incur in data loss in some scenarios. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.28.1-1+b1 The GLib library of C routines ii libnotify1 [libnotify1-gtk2. 0.5.0-2 sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- This has to be handled by the desktop environment, not a notify-send issue. Also new version supports --wait --- End Message ---
Bug#705608: marked as done (libnotify4: Notifications are offset when using a dual-screen)
Your message dated Wed, 27 Apr 2022 20:12:46 +0200 with message-id <5150117d-db4d-4960-8ac9-3f545ac43...@getmailspring.com> and subject line Bug #705608 has caused the Debian Bug report #705608, regarding libnotify4: Notifications are offset when using a dual-screen 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.) -- 705608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify4 Version: 0.7.5-2 Severity: important Dear Maintainer, When a notification is fired, if the current screen is not the most-right screen and that the text is too long, the notification will be slightly offset, and a part of it will be seen on the screen to the right to the current screen. I expect it to be entirely on the current screen. -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/12 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify4 depends on: ii libc6 2.13-38 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii multiarch-support 2.13-38 Versions of packages libnotify4 recommends: ii notification-daemon 0.7.6-1 libnotify4 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Not a libnotify bug, depends on DE.--- End Message ---
Bug#644923: marked as done (/usr/bin/notify-send: notify-send cannot be above FEH -F -Z)
Your message dated Wed, 27 Apr 2022 20:09:02 +0200 with message-id <304339a4-d9e9-4414-92d4-68346f812...@getmailspring.com> and subject line Bug #644923 has caused the Debian Bug report #644923, regarding /usr/bin/notify-send: notify-send cannot be above FEH -F -Z 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.) -- 644923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.5.0-2 Severity: minor File: /usr/bin/notify-send Hi Lovin notify-send However I have noticed that if you make a loop into sh and then with it some feh -F -Z ... then the notify-send cannot be above hte fullscreen of feh. It would hlep that it works Kind regards Y. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libnotify1 [libnotify1-gtk2.1 0.5.0-2sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Not a libnotify bug. --- End Message ---
Bug#597272: marked as done (/usr/bin/notify-send: center of the screen argument in help file)
Your message dated Wed, 27 Apr 2022 20:08:07 +0200 with message-id and subject line Bug #597272 has caused the Debian Bug report #597272, regarding /usr/bin/notify-send: center of the screen argument in help file 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.) -- 597272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.5.0-2 Severity: wishlist File: /usr/bin/notify-send Dear sir, Most users use notify-send on top right or either bottom right; into --help it says: notify-send --help Usage: notify-send [OPTION...] [BODY] - create a notification Help Options: -?, --helpShow help options Application Options: -u, --urgency=LEVEL Specifies the urgency level (low, normal, critical). -t, --expire-time=TIMESpecifies the timeout in milliseconds at which to expire the notification. -i, --icon=ICON[,ICON...] Specifies an icon filename or stock icon to display. -c, --category=TYPE[,TYPE...] Specifies the notification category. -h, --hint=TYPE:NAME:VALUESpecifies basic extra data to pass. Valid types are int, double, string and byte. -v, --version Version of the package. It would be great to find soemting for the possition: -argument : -position either center of the screen, and other possibilites For script, that would help to sometimes place it in center of screen or stick to the default one selected into notification configuration gtk window Notify-send is cool All the best ! -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libnotify1 [libnotify1-gtk2.1 0.5.0-2sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Not a library issue, it depends on DE. --- End Message ---
Bug#597136: marked as done (/usr/bin/notify-send: would be great to have resize icons to fit (wish) although CPU power)
Your message dated Wed, 27 Apr 2022 20:06:50 +0200 with message-id <459c5382-13b2-44ae-b796-87df74ed9...@getmailspring.com> and subject line Bug #597136 has caused the Debian Bug report #597136, regarding /usr/bin/notify-send: would be great to have resize icons to fit (wish) although CPU power 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.) -- 597136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.5.0-2 Severity: wishlist File: /usr/bin/notify-send -i option is cool. I would be happpy to see that -i and -ir could do icons + resizing it try -i with http://media.dabi.se/2010/08/debian-logo.gif You will flood your desktop. Just a wishlist for a new feature that could evtl. help some of coders. notify-send is gorgeous !! Man, thank you ! Best regards Y. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnotify-bin depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libnotify1 [libnotify1-gtk2.1 0.5.0-2sends desktop notifications to a n libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Not a libnotify bug, has to be handled by Desktop environment.--- End Message ---
Bug#1004921: marked as done (libtsm: Package too old for kmscon)
Your message dated Wed, 27 Apr 2022 18:00:09 + with message-id and subject line Bug#1004921: fixed in libtsm 4.0.2-0.1 has caused the Debian Bug report #1004921, regarding libtsm: Package too old for kmscon 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.) -- 1004921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtsm Version: 3-1 Severity: wishlist Tags: patch Control: block 1004919 by -1 I've just opened an ITP bug for kmscon, #1004919. This package depends on libtsm version 4.0.0 or greater. Upstream development has long stopped on libtsm and kmscon depends on a fork by the same author at https://github.com/Aetf/libtsm. I have prepared packaging for version 4.0.1 from the fork at https://salsa.debian.org/viccie30/libtsm. You are welcome to use that, but I'm also willing to take over maintenance if you want. It looks like there are no reverse dependencies on the current versions of libtsm3 and libtsm-dev, so the upgrade should create no problems. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en_US:en:nl_NL:nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: libtsm Source-Version: 4.0.2-0.1 Done: Victor Westerhuis We believe that the bug you reported is fixed in the latest version of libtsm, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Victor Westerhuis (supplier of updated libtsm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Feb 2022 18:41:17 +0100 Source: libtsm Binary: libtsm-dev libtsm4 libtsm4-dbgsym Architecture: source i386 Version: 4.0.2-0.1 Distribution: unstable Urgency: medium Maintainer: Victor Westerhuis Changed-By: Victor Westerhuis Description: libtsm-dev - Terminal-emulator State Machine - development libtsm4- Terminal-emulator State Machine - runtime Closes: 1004921 Changes: libtsm (4.0.2-0.1) unstable; urgency=medium . * Non-maintainer upload * Switch upstream to maintained fork. * New upstream release. (Closes: #1004921) Checksums-Sha1: e979f5e90752b16713058cbf6f95164d1e3a4714 1770 libtsm_4.0.2-0.1.dsc f920c298439ab4ab6037f11ad324e6bc03b96255 148135 libtsm_4.0.2.orig.tar.gz 087f3cb3b41e774f40c1640bba297b8a6e9b18f7 5000 libtsm_4.0.2-0.1.debian.tar.xz 7a87380eaa241349829cd98bbc2e959d2cb008fc 41388 libtsm-dev_4.0.2-0.1_i386.deb 7dcf8ecbc6c20c79d9cf0a6a20f3350a044b103a 74272 libtsm4-dbgsym_4.0.2-0.1_i386.deb 5b489846f685e9f7b43c3b94838b9372edd295ef 30068 libtsm4_4.0.2-0.1_i386.deb cb7f35d930958104302332c0dbd7642b3e678083 7200 libtsm_4.0.2-0.1_i386.buildinfo Checksums-Sha256: 8c2b16351a70cc04db377fa5b6ab7dd92819a923f9464e6bc0e519cbeb6f40d2 1770 libtsm_4.0.2-0.1.dsc ce51be564872d3e6a35fadab1f74b8804f72d8a92c0f378ca384155134d154e5 148135 libtsm_4.0.2.orig.tar.gz 1a6054d64988cceea5313f58ca3560b32e237c42340f44c19e60317a3d191b90 5000 libtsm_4.0.2-0.1.debian.tar.xz 95b97ce8092ec1fe95310847d346269b00f8df84e5989f5382f2e0711f849d2f 41388 libtsm-dev_4.0.2-0.1_i386.deb ef75bd258d905ac60e4581753fe1f759e020ff2a2501af0ef933bf18dd65 74272 libtsm4-dbgsym_4.0.2-0.1_i386.deb 7b71e2c77cbe495360d44116c81ac5ca8aaddc06957cc5ec9fb50b6dd2ed6d42 30068 libtsm4_4.0.2-0.1_i386.deb 38e55b446eeea94b3b514e5a9b6f8698925b2876c1c325850cbedd7d3b5cfdd1 7200 libtsm_4.0.2-0.1_i386.buildinfo Files: 5344e55bf130999dcf3ac97c1b7c44cd 1770 libs optional libtsm_4.0.2-0.1.dsc bcf1bafa3798bced0e9bd16b4afdf256 148135 libs optional libtsm_4.0.2.orig.tar.gz 95d62e498d2ae1705bfb1547e0b38f1c 5000 libs optional libtsm_4.0.2-0.1.debian.tar.xz 14afd87fb6bf5caec0c4a217a83f5dce 41388 libdevel optional libtsm-dev_4.0.2-0.1_i386.deb e954c8b6c76c4dc88375ebf351f7380e 74272 debug optional
Bug#698852: marked as done ([libnotify-bin] character '&' in message text causes whole message to display empty)
Your message dated Wed, 27 Apr 2022 20:00:52 +0200 with message-id <1a284845-2c92-44ac-ab6e-84120387e...@getmailspring.com> and subject line Bug #698852 has caused the Debian Bug report #698852, regarding [libnotify-bin] character '&' in message text causes whole message to display empty 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.) -- 698852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.7.5-1 Severity: normal --- Please enter the report below this line. --- passing & in message, like that: $ notify-send 'test' 'msg' causes notify-send to display message with correct title but empty body --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: 7.0 500 testing ftp.pl.debian.org 500 stable ftp.pl.debian.org 100 squeeze-backports backports.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== libc6(>= 2.3.4) | libglib2.0-0 (>= 2.26) | libnotify4 (>= 0.7.3) | Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- This works now, at least in gnome-shell. If it doesn't, it's not library's fault but due to the server. --- End Message ---
Bug#869283: marked as done (libnotify-bin: Can not find the sources of the manpage)
Your message dated Wed, 27 Apr 2022 19:56:21 +0200 with message-id and subject line Bug #869283 has caused the Debian Bug report #869283, regarding libnotify-bin: Can not find the sources of the manpage 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.) -- 869283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.7.7-2 Severity: normal Dear Maintainer, I tried to contribute but can not find the sources of the manpage (for notify- send) somewhere. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.9-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libnotify-bin depends on: ii libc6 2.24-12 ii libglib2.0-0 2.52.3-1 ii libnotify40.7.7-2 libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- man source is now upstream: https://gitlab.gnome.org/GNOME/libnotify/-/blob/master/docs/notify-send.xml--- End Message ---
Bug#869277: marked as done (/usr/bin/notify-send: Improve the manpage)
Your message dated Wed, 27 Apr 2022 19:56:21 +0200 with message-id and subject line Bug #869283 has caused the Debian Bug report #869283, regarding /usr/bin/notify-send: Improve the manpage 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.) -- 869283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.7.7-2 Severity: normal File: /usr/bin/notify-send Dear Maintainer, please let the manpage be improved. There should be informations about the options '--category' and '--hints'. The possible values and there effect should be described in the manpage. I link to http://www.galago-project.org/specs/notification is nice but not enough and under the quality of Debian packages. kind -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.9-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libnotify-bin depends on: ii libc6 2.24-12 ii libglib2.0-0 2.52.3-1 ii libnotify40.7.7-2 libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- man source is now upstream: https://gitlab.gnome.org/GNOME/libnotify/-/blob/master/docs/notify-send.xml--- End Message ---
Bug#869409: marked as done (libnotify-bin: add informations about upstream)
Your message dated Wed, 27 Apr 2022 19:57:40 +0200 with message-id and subject line Bug #869409 has caused the Debian Bug report #869409, regarding libnotify-bin: add informations about upstream 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.) -- 869409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnotify-bin Version: 0.7.7-2 Severity: normal Dear Maintainer, plesae add informations about upstream in the expectable places. Looking at the debian tracker there is no direct information. The only hint is that the "maintainer" are the "Debian GNOME Maintainers". Concrete: - add a link to the upstream source (not only to debians one) https://git.gnome.org/browse/libnotify/ - add a link to the upstream project page (couldn't find a package specific page on gnome.org yet) - a linkt to the gnome bugtracker would be nice, too - add this infos to the debian tracker page AND somewhere in the source-docu (e.g. README.debian, CONTRIBUTE.debian, AUTHERS, manpage, ...) Of course I know and aggree that reports should be addressed first to the own distro. But some reporters are more then just "users" and know (or have their own opinion) what belongs to the distro-maintainer and what to upstream. Please make it possible to let the reporter decide that by her-/himself. kind -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.9-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libnotify-bin depends on: ii libc6 2.24-12 ii libglib2.0-0 2.52.3-1 ii libnotify40.7.7-2 libnotify-bin recommends no packages. libnotify-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- debian/upstream/metadata is in salsa--- End Message ---
Bug#1007626: marked as done (libmodem-vgetty-perl: please consider upgrading to 3.0 source format)
Your message dated Wed, 27 Apr 2022 17:33:43 + with message-id and subject line Bug#1007626: fixed in libmodem-vgetty-perl 0.03-3 has caused the Debian Bug report #1007626, regarding libmodem-vgetty-perl: please consider upgrading to 3.0 source format 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.) -- 1007626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmodem-vgetty-perl Version: 0.03-2.1 Severity: wishlist Tags: bookworm sid Usertags: format1.0 format1.0-nkp-nv Dear maintainer, This package is among the few (1.9%) that still use source format 1.0 in bookworm. Please upgrade it to source format 3.0, as (1) this format has many advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2) this contributes to standardization of packaging practices. Please note that this is also a sign that the packaging of this software could maybe benefit from a refresh. It might be a good opportunity to look at other aspects as well. It was noticed in https://lists.debian.org/debian-devel/2022/03/msg00096.html that the conversion for this package is likely trivial, and builds bit-by-bit identical binary packages. This mass bug filing was discussed on debian-devel@: https://lists.debian.org/debian-devel/2022/03/msg00074.html Thanks Lucas --- End Message --- --- Begin Message --- Source: libmodem-vgetty-perl Source-Version: 0.03-3 Done: Michael C. Schultheiss We believe that the bug you reported is fixed in the latest version of libmodem-vgetty-perl, 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 1007...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael C. Schultheiss (supplier of updated libmodem-vgetty-perl 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 16:56:12 + Source: libmodem-vgetty-perl Binary: libmodem-vgetty-perl Architecture: source all Version: 0.03-3 Distribution: unstable Urgency: medium Maintainer: Michael C. Schultheiss Changed-By: Michael C. Schultheiss Description: libmodem-vgetty-perl - Perl module for interfacing with vgetty (Modem::Vgetty) Closes: 1007626 Changes: libmodem-vgetty-perl (0.03-3) unstable; urgency=medium . * Switch to dpkg-source 3.0 (quilt) format (Closes: #1007626) * Update compat level to 13 Checksums-Sha1: 6d17050466b0163206d3a57dc60d2644c3ad8f7e 1817 libmodem-vgetty-perl_0.03-3.dsc 48c6042e1bbffac14deb6286f8843aff5a01b91c 1796 libmodem-vgetty-perl_0.03-3.debian.tar.xz 90440f6f13621a9b740602f6358f7b66fcae26ba 22816 libmodem-vgetty-perl_0.03-3_all.deb 1a5a912b911d63264c3db13d9ebeba0ab06fc405 5832 libmodem-vgetty-perl_0.03-3_amd64.buildinfo Checksums-Sha256: ab7fcf77847509d43ad310423d3c6dbe7f598346594d42bef8f566cde6e4b1aa 1817 libmodem-vgetty-perl_0.03-3.dsc fa7c6e543ff38f54599ff66fccd134aaeb881321e609c46d7aa0ddd86ab8679f 1796 libmodem-vgetty-perl_0.03-3.debian.tar.xz 1e20bcffe55e4746909f475de1ac41eab3a24dd9d3dc3c704618865f2bb9ac90 22816 libmodem-vgetty-perl_0.03-3_all.deb fc8c3743b28fba8d996266f33ce7826c563545d3573b3dc72ba2540c418ab5cd 5832 libmodem-vgetty-perl_0.03-3_amd64.buildinfo Files: ddba3b2f84cd7778ef64423260b18da0 1817 perl optional libmodem-vgetty-perl_0.03-3.dsc 4cfdb1b3f6f4ea569e6553efe5337b6d 1796 perl optional libmodem-vgetty-perl_0.03-3.debian.tar.xz 5f5fc3f11fec53b79dc2747af1723190 22816 perl optional libmodem-vgetty-perl_0.03-3_all.deb f3230feca0dc4b8e1711ce196e11c7ea 5832 perl optional libmodem-vgetty-perl_0.03-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEuuA0ASfVNq0ssS/gnsAC/hycpRcFAmJpeOIUHHNjaHVsdG1j QGRlYmlhbi5vcmcACgkQnsAC/hycpRfHmxAA21+SRvrtNw6RMZOCAgJVvuXdQ7Qs pX9VmGCIulfTRbq1uEhypTnFVNmgrMWHKpTngKkDH7aRZ/a05CTc9Ko/eQyuPFYb /g4ihpV0coQrNpE1Sf4BAO1SsalRM78IIHWRAXMSHs81V90W30gFBlsNqudwNZ4D SaNFlaihyCro6cZOcnGV4L/nhKksuZ8aV3FwMRYU0IyA35KHAebBnjAvEqdITNQK aNLwgN/WixedKBaUBw5+15WpXX7tShxNEepfhhvIEh055Cg+vwCwR2ryo9kUnbIK HHiKRzpN7p3ckSFvT8LZ8tPmt4OdGi4G2NZkt3oywWThJhkXW9p1l6XJj6kbZuG2 rD4WLEuO5DWR6RtfyljmZK+ge0GCwyiV1Oq97bo3eDzBtcl1tD7nmLPk4/YbQW+7
Bug#1010277: marked as done (threeb: Correct changelog formatting)
Your message dated Wed, 27 Apr 2022 17:33:53 + with message-id and subject line Bug#1010277: fixed in threeb 0.0~git20220106110332.a3144e0-5 has caused the Debian Bug report #1010277, regarding threeb: Correct changelog formatting 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.) -- 1010277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: threeb Version: 0.0~git20220106110332.a3144e0-4 Severity: normal Tags: patch Hi, A patch is attached that fixes the changelog formatting — a line is not indented correctly by one byte. This apparently cosmetic issue actually causes some parsers to (at least) complain, and may cause others to fail completely. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/changelog b/debian/changelog index bf347d1..0b89ac3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -6,7 +6,7 @@ threeb (0.0~git20220106110332.a3144e0-4) unstable; urgency=medium threeb (0.0~git20220106110332.a3144e0-3) unstable; urgency=medium - * Source-only upload for migration to testing. + * Source-only upload for migration to testing. -- Roland Mas Thu, 10 Feb 2022 11:28:40 +0100 --- End Message --- --- Begin Message --- Source: threeb Source-Version: 0.0~git20220106110332.a3144e0-5 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of threeb, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated threeb 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 19:15:21 +0200 Source: threeb Architecture: source Version: 0.0~git20220106110332.a3144e0-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Mattia Rizzolo Closes: 1010277 Changes: threeb (0.0~git20220106110332.a3144e0-5) unstable; urgency=medium . * Team upload. . [ Roland Mas ] * Fix syntax error in debian/changelog Closes: #1010277 . [ Mattia Rizzolo ] * Add the ITP bug to the changelog (manually closed) Checksums-Sha1: 157d59180b224ca6f8249753ff17eae9dba582f8 2359 threeb_0.0~git20220106110332.a3144e0-5.dsc 42fe6a925b2030ac376bf8413c9482c1bcd92df8 2692 threeb_0.0~git20220106110332.a3144e0-5.debian.tar.xz d71cfc66e1688de29b6296c0ed733d80abfd8204 13417 threeb_0.0~git20220106110332.a3144e0-5_amd64.buildinfo Checksums-Sha256: d3a351119737774bac7bf508bcc8965dd6a55e74789360f202f1b7cacf05bffb 2359 threeb_0.0~git20220106110332.a3144e0-5.dsc 936588f932839afab38860b22fe699a19722afb6fc7351f53367d48e89ab6b46 2692 threeb_0.0~git20220106110332.a3144e0-5.debian.tar.xz 41b99ac110f02d4b177b2ddb9256dab30be3e923ee39f89efbaefb8b5e8dca1d 13417 threeb_0.0~git20220106110332.a3144e0-5_amd64.buildinfo Files: 2e68155661df01aeb8ecb808f0660895 2359 science optional threeb_0.0~git20220106110332.a3144e0-5.dsc 842a327272ac9800fde474d2f002a046 2692 science optional threeb_0.0~git20220106110332.a3144e0-5.debian.tar.xz ea195d3f3e162b9215c47f40a93a07e4 13417 science optional threeb_0.0~git20220106110332.a3144e0-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmJpe50ACgkQCBa54Yx2 K61bJg/+J66qndttmsmjqzMtRLZfG5EdstX21n/PE5WtbTmaA7hJuLnhydJB5fLM CnL2dnobwRmyIpwRY0rXHLIuXH7PU6d0DheAMoDf9l/JQJUjG/2/aSuF9rSrXBV2 RMQHMmJPUu+SR9X2po5L5eKHXnuwmrfuioe8RiWTplSr8tTt8vymrgSVb++zbeD2 jEncar+CC/G5xq45893fW2Sh/nbSGwuHrGFLW5oIBkazHjxFH6uCeE4EtftmTVBT +aGR8EFrOVnm8Dkas95R52RfTWzctSrRzOoAaNFHklebYg+FwmTQkn/pm0Holyn/ tks1ide+qU+wh1j1JsDw4msIejLKRuB6ayThSfkmxrT6Waya1iX/AAFHVy5nah2R AzSuZpG/NndEc8+sfYrz1lXSX1zuHBLwLfv/+TuQSa2VzOHtOk8tvHZmw5CbrATg ruUqzF5SLRbEPL/hgL1Rs1JjIfoYsEF5MYlMz4D1HXDcl4wDo9VLdbn/gdsFe3az sILGO1kQFQPs1UYhs31VmmooFqiAY4LkL4uTEflbbACiIhfBeEEjpRzyJevbu+fI 1qjSxqYPD+Fdp5+Fo3I6BQmNOn7kAo3DtUNLmGZeln3yziYFsPPkd+2L0/8kPV1x j60Qb03FZnU25WybV7/i7aRrCb4sb+4UTB6jJYx2tMO4QY8+bRA= =67AS -END PGP SIGNATURE End Message ---
Processed: closing 1002743
Processing commands for cont...@bugs.debian.org: > close 1002743 Bug #1002743 [wnpp] ITP: threeb -- Bayesian analysis of blinking and bleaching (3B) microscopy analysis Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1002743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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
Bug#1009883: marked as done (dh_haskell_install_ghc_registration: does not support directories)
Your message dated Wed, 27 Apr 2022 15:33:54 + with message-id and subject line Bug#1009883: fixed in haskell-devscripts 0.16.14 has caused the Debian Bug report #1009883, regarding dh_haskell_install_ghc_registration: does not support directories 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.) -- 1009883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: haskell-devscripts Severity: normal Dear Maintainer, While attempting to update haskell-attoparsec to upstream release 0.14.4, it was observed that this version of attoparsec produces a *directory* and not a *file* for its GHC registration. This currently fails because of bug #1009873, but after that is fixed, this will still fail because dh_haskell_install_dhc_registration is searching for: "Creating package registration file" where attoparsec produces: "Creating package registration directory" And thus will result in "Cannot get package registration file." once the aforementioned bug is fixed. It's not quite clear to me how a directory is supposed to be handled (install each file in the directory?), but perhaps someone with more familiarity with GHC registrations might know. Thanks, Scott --- End Message --- --- Begin Message --- Source: haskell-devscripts Source-Version: 0.16.14 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of haskell-devscripts, 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. Scott Talbert (supplier of updated haskell-devscripts 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 11:04:45 -0400 Source: haskell-devscripts Architecture: source Version: 0.16.14 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Scott Talbert Closes: 1009883 1010179 Changes: haskell-devscripts (0.16.14) unstable; urgency=medium . * Team Upload. . [ Felix Lechner ] * Anchor dot regex; amends commit 7a92a0a0. . [ Scott Talbert ] * Add missing export for DEB_ENABLE_TESTS (Closes: #1010179) * Fix GHC package directory registration (Closes: #1009883) Checksums-Sha1: 2f0f874ad5be569d26b75a0c80bf75d8950c8c46 1953 haskell-devscripts_0.16.14.dsc 96dec73c05bae8ae2417029b0ae883fe9ebb96ea 37336 haskell-devscripts_0.16.14.tar.xz 2a59492ec7947320001b9b7af73616d0f899a676 6436 haskell-devscripts_0.16.14_amd64.buildinfo Checksums-Sha256: e60051ddb88be8ce8017845873c6fe10813b297f7efd15d8e6efcbe6d841c72e 1953 haskell-devscripts_0.16.14.dsc bbd1dbdccaeee634f77415be75fa4bd8a325024ec00f9bf3e7fe33378d3c47c0 37336 haskell-devscripts_0.16.14.tar.xz 7c6200b5d96c0fbd8f064377ad5de6eb58d6f97a5db93167a4adc69d099befda 6436 haskell-devscripts_0.16.14_amd64.buildinfo Files: 2a158e9f111404ea9ccd5cf636ec90b7 1953 haskell optional haskell-devscripts_0.16.14.dsc 6a59d102a90269fe9d74e627be612bc5 37336 haskell optional haskell-devscripts_0.16.14.tar.xz b3b00a30bb3603af805729ebb5b3699e 6436 haskell optional haskell-devscripts_0.16.14_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmJpXN8PHHN3dEB0ZWNo aWUubmV0AAoJEFPVvGS1I3ii60oQAI1FHIUVlhUNHlIrZdN93/oaoglkHgR3bHbS RjE2XjT3uBmOgnATSHVm4wb+J2UwGpiw8W2CK4obZ8IBpOq/qDt6Vx883LfNhIWh 8TDSqWqB97TRvPiyExsaNHJEulUL+uYmtGt4UDrcKhm0mr6cfgdJEB9LeuIbaLkQ RfHtNStQ+uhYQaQydhbkkfkhBOa36oCDStubRX5+ks0epZJ4IdEvbf2J+6MG+1Jp CV4EcptN/RhRsd05LCzmYKsCauI+yfcYBwgAjupUCmlowc1cWb2BmkyFEDnVlf3e 5H+uIND2mf9hOMNp29HKLenIh1l4dF9wpJWo1quVhV+hRs+W/uexvIphZ0Ahyur7 dCmAdo2GS8JR6dB66Ib8QuUDpd6NMC9JG5wmme5Us/ShQUWUD5UW0MokoAMgyE29 KJ5Ef1JXWmgqjnpQE0aFVaeHxqdlNkhtI/QGVdKM5VqMTYKi7S5hc2G0/uTejM+T M8g5Wp/YzJXVUbgyFgfV02kWbcWXF+umqXObPzlqNk0wXjhNkHkDCrwVXe1xs+CP S0noYs7A37ObHcBBbmuf9jLbB6OEOXefr/LcxRPdOFw3ghWc1CgU/+OZddMfqH+x Tqp1o/YaQAD+R15hhBSHjNeQPWD4BlGRuufQIHhsjUr4/qyjWOWFD55dMkvC+jXt Uluyk1G6 =KXjz -END PGP SIGNATURE End Message ---
Bug#1010179: marked as done (haskell-devscripts: DEB_ENABLE_TESTS broken)
Your message dated Wed, 27 Apr 2022 15:33:54 +
with message-id
and subject line Bug#1010179: fixed in haskell-devscripts 0.16.14
has caused the Debian Bug report #1010179,
regarding haskell-devscripts: DEB_ENABLE_TESTS broken
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.)
--
1010179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: haskell-devscripts
Version: 0.16.11
Severity: normal
After the recent port from shell to Perl, Setting DEB_ENABLE_TESTS=yes
in debian/rules does not cause the tests to be executed during build.
This error message is seen during builds:
Use of uninitialized value $ENV{"DEB_ENABLE_TESTS"} in string ne at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 671.
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
DEB_ENABLE_TESTS not set to yes, not running any build-time tests.
--- End Message ---
--- Begin Message ---
Source: haskell-devscripts
Source-Version: 0.16.14
Done: Scott Talbert
We believe that the bug you reported is fixed in the latest version of
haskell-devscripts, 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 1010...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Talbert (supplier of updated haskell-devscripts 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 11:04:45 -0400
Source: haskell-devscripts
Architecture: source
Version: 0.16.14
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Scott Talbert
Closes: 1009883 1010179
Changes:
haskell-devscripts (0.16.14) unstable; urgency=medium
.
* Team Upload.
.
[ Felix Lechner ]
* Anchor dot regex; amends commit 7a92a0a0.
.
[ Scott Talbert ]
* Add missing export for DEB_ENABLE_TESTS (Closes: #1010179)
* Fix GHC package directory registration (Closes: #1009883)
Checksums-Sha1:
2f0f874ad5be569d26b75a0c80bf75d8950c8c46 1953 haskell-devscripts_0.16.14.dsc
96dec73c05bae8ae2417029b0ae883fe9ebb96ea 37336
haskell-devscripts_0.16.14.tar.xz
2a59492ec7947320001b9b7af73616d0f899a676 6436
haskell-devscripts_0.16.14_amd64.buildinfo
Checksums-Sha256:
e60051ddb88be8ce8017845873c6fe10813b297f7efd15d8e6efcbe6d841c72e 1953
haskell-devscripts_0.16.14.dsc
bbd1dbdccaeee634f77415be75fa4bd8a325024ec00f9bf3e7fe33378d3c47c0 37336
haskell-devscripts_0.16.14.tar.xz
7c6200b5d96c0fbd8f064377ad5de6eb58d6f97a5db93167a4adc69d099befda 6436
haskell-devscripts_0.16.14_amd64.buildinfo
Files:
2a158e9f111404ea9ccd5cf636ec90b7 1953 haskell optional
haskell-devscripts_0.16.14.dsc
6a59d102a90269fe9d74e627be612bc5 37336 haskell optional
haskell-devscripts_0.16.14.tar.xz
b3b00a30bb3603af805729ebb5b3699e 6436 haskell optional
haskell-devscripts_0.16.14_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmJpXN8PHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3ii60oQAI1FHIUVlhUNHlIrZdN93/oaoglkHgR3bHbS
RjE2XjT3uBmOgnATSHVm4wb+J2UwGpiw8W2CK4obZ8IBpOq/qDt6Vx883LfNhIWh
8TDSqWqB97TRvPiyExsaNHJEulUL+uYmtGt4UDrcKhm0mr6cfgdJEB9LeuIbaLkQ
RfHtNStQ+uhYQaQydhbkkfkhBOa36oCDStubRX5+ks0epZJ4IdEvbf2J+6MG+1Jp
CV4EcptN/RhRsd05LCzmYKsCauI+yfcYBwgAjupUCmlowc1cWb2BmkyFEDnVlf3e
5H+uIND2mf9hOMNp29HKLenIh1l4dF9wpJWo1quVhV+hRs+W/uexvIphZ0Ahyur7
dCmAdo2GS8JR6dB66Ib8QuUDpd6NMC9JG5wmme5Us/ShQUWUD5UW0MokoAMgyE29
KJ5Ef1JXWmgqjnpQE0aFVaeHxqdlNkhtI/QGVdKM5VqMTYKi7S5hc2G0/uTejM+T
M8g5Wp/YzJXVUbgyFgfV02kWbcWXF+umqXObPzlqNk0wXjhNkHkDCrwVXe1xs+CP
S0noYs7A37ObHcBBbmuf9jLbB6OEOXefr/LcxRPdOFw3ghWc1CgU/+OZddMfqH+x
Tqp1o/YaQAD+R15hhBSHjNeQPWD4BlGRuufQIHhsjUr4/qyjWOWFD55dMkvC+jXt
Uluyk1G6
=KXjz
-END PGP SIGNATURE End Message ---
Bug#1010055: marked as done (ITP: base16384 -- Encode binary file to printable utf16be, and vise versa.)
Your message dated Wed, 27 Apr 2022 21:55:03 +0800 with message-id and subject line Re: RFS: base16384/2.2.0-3 [ITP] -- Encode binary files to printable utf16be has caused the Debian Bug report #1010055, regarding ITP: base16384 -- Encode binary file to printable utf16be, and vise versa. 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.) -- 1010055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: fumiama * Package name: base16384 Version : 2.2.0 Upstream Author : fumiama * URL : https://launchpad.net/base16384 * License : GPLv3 Programming Lang: C Description : Encode binary file to printable utf16be, and vise versa. We use 16384 Chinese characters (from \u4E00 to \u8DFF) as the "alphabet", just like what base64 did. If length of the data has a remainder after mod 7, we will use \u3Dxx to present it with xx ranging from 01 to 06. - I designed this base64-like algorithm and had published it to my lauchpad PPA https://code.launchpad.net/~fumiama/+archive/ubuntu/ppa It seems to work well so that I hope to see more people who can use this util easily by entering apt-get directly. - I have read the wiki and found that in order to pubish my package to Debian, I am requested to get a sponsor for it. So I will file a RFS bug report later. --- End Message --- --- Begin Message --- I have sought many articles about closing that ITP bug, but still not sure for whether this reply will close #1010055 , please forgive me for this trying .--- End Message ---
Bug#1008929: marked as done (ModuleNotFoundError: No module named 'mistune.plugins'; 'mistune' is not a package)
Your message dated Wed, 27 Apr 2022 15:38:05 +0200 with message-id <87h76eprx1@janja.pimeys.fr> and subject line Re: Bug#1008929: python3-django-hyperkitty: Error gone with python3-django update has caused the Debian Bug report #1008929, regarding ModuleNotFoundError: No module named 'mistune.plugins'; 'mistune' is not a 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.) -- 1008929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-django-hyperkitty Version: 1.3.5.0-2 Severity: normal Dear Maintainer, Thanks for your work on this package. After the most recent upgrade to the version above, which also brought in python3-mistune as below, I am unfortunately finding my inbox flooded by cron errors, to the extent that I disabled "by minute" cron jobs. I'm not really sure why since mistune is installed. I have tried restarting the mailman3-web service but to no avail. Traceback as below: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 121, in get_package_libraries module = import_module(entry[1]) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/hyperkitty/templatetags/decorate.py", line 4, in from hyperkitty.lib.renderer import markdown_renderer, text_renderer File "/usr/lib/python3/dist-packages/hyperkitty/lib/renderer.py", line 6, in from mistune.plugins.extra import plugin_url ModuleNotFoundError: No module named 'mistune.plugins'; 'mistune' is not a package The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/share/mailman3-web/manage.py", line 10, in execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 419, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 413, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 354, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 393, in execute self.check() File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 419, in check all_issues = checks.run_checks( File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 76, in run_checks new_errors = check(app_configs=app_configs, databases=databases) File "/usr/lib/python3/dist-packages/django/contrib/admin/checks.py", line 78, in check_dependencies for engine in engines.all(): File "/usr/lib/python3/dist-packages/django/template/utils.py", line 90, in all return [self[alias] for alias in self] File "/usr/lib/python3/dist-packages/django/template/utils.py", line 90, in return [self[alias] for alias in self] File "/usr/lib/python3/dist-packages/django/template/utils.py", line 81, in __getitem__ engine = engine_cls(params) File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 25, in __init__ options['libraries'] = self.get_templatetag_libraries(libraries) File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 43, in get_templatetag_libraries libraries = get_installed_libraries() File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 108, in get_installed_libraries for name in get_package_libraries(pkg): File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 123, in get_package_libraries raise InvalidTemplateLibrary( django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': No module named 'mistune.plugins'; 'mistune' is not a package A similar error is occuring on web access causing a 500 HTTP Error. Kind regards, CT. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8,
Bug#925180: marked as done (samba: upgrade does not pull in required libgpgme11 and fails to start smbd etc.)
Your message dated Wed, 27 Apr 2022 16:39:33 +0300 with message-id and subject line Re: Bug#886333: samba: cannot provision a domain: ldb_init_module() complains about gpgme_check_version(1.9.0) has caused the Debian Bug report #886333, regarding samba: upgrade does not pull in required libgpgme11 and fails to start smbd etc. 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.) -- 886333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: samba Version: 2:4.9.4+dfsg-4 Severity: important Dear Maintainer, * What led up to the situation? Installing samba AD DC from "testing" on a "stretch" system already AD DC * What exactly did you do (or not do) that was effective (or ineffective)? put testing in sources.list, apt-get update && apt-get install samba * What was the outcome of this action? errors in log file, libgpgme is older version than required * What outcome did you expect instead? other than that, the upgrade went smoothly -- Package-specific info: * /etc/samba/smb.conf present, but not attached * /var/lib/samba/dhcp.conf not present -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1), LANGUAGE=en_CA (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii adduser 3.115 ii dpkg 1.18.25 ii libbsd0 0.8.3-1 ii libc6 2.28-8 ii libldb1 2:1.5.1+really1.4.3-2 ii libpam-modules1.1.8-3.6 ii libpam-runtime1.1.8-3.6 ii libpopt0 1.16-10+b2 ii libpython2.7 2.7.13-2+deb9u3 ii libtalloc22.1.8-1 ii libtdb1 1.3.16-2+b1 ii libtevent00.9.37-1 ii lsb-base 9.20161125 ii procps2:3.3.12-3+deb9u1 ii python2.7.13-2 ii python-dnspython 1.15.0-1+deb9u1 ii python-samba 2:4.9.4+dfsg-4 ii python2.7 2.7.13-2+deb9u3 ii samba-common 2:4.9.4+dfsg-4 ii samba-common-bin 2:4.9.4+dfsg-4 ii samba-libs2:4.9.4+dfsg-4 ii tdb-tools 1.3.11-2 Versions of packages samba recommends: ii attr1:2.4.47-2+b2 ii logrotate 3.11.0-0.1 ii samba-dsdb-modules 2:4.9.4+dfsg-4 ii samba-vfs-modules 2:4.9.4+dfsg-4 Versions of packages samba suggests: ii bind9 1:9.10.3.dfsg.P4-12.3+deb9u4 ii bind9utils 1:9.10.3.dfsg.P4-12.3+deb9u4 pn ctdb ii ldb-tools 2:1.1.27-1+deb9u1 ii ntp1:4.2.8p10+dfsg-3+deb9u2 pn smbldap-tools pn ufw ii winbind2:4.9.4+dfsg-4 -- no debconf information --- End Message --- --- Begin Message --- Version: 2:4.11.0+dfsg-1 This bug has been fixed upstream somewhere in 4.10 series. The check is still there now (in 4.16, commit 4ae2fb2e7403191296f7c74f3098fbe121f0796a), I don't think it makes sense now but that's how things are :) Closing this bugreport now. Thanks, /mjt--- End Message ---
Bug#886333: marked as done (samba: cannot provision a domain: ldb_init_module() complains about gpgme_check_version(1.9.0))
Your message dated Wed, 27 Apr 2022 16:39:33 +0300 with message-id and subject line Re: Bug#886333: samba: cannot provision a domain: ldb_init_module() complains about gpgme_check_version(1.9.0) has caused the Debian Bug report #886333, regarding samba: cannot provision a domain: ldb_init_module() complains about gpgme_check_version(1.9.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 886333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: samba Version: 2:4.7.3+dfsg-1 Severity: normal When running "samba-tool domain provision" I get: # samba-tool domain provision Realm [HOME.WURTEL.NET]: WURTEL.NET Domain [WURTEL]: Server Role (dc, member, standalone) [dc]: DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: DNS forwarder IP address (write 'none' to disable forwarding) [172.18.0.2]: Administrator password: Retype password: Looking up IPv4 addresses More than one IPv4 address found. Using 172.18.1.11 Looking up IPv6 addresses More than one IPv6 address found. Using fd2c:2cdd:72b1:0:62e3:27ff:fe05:eec6 ldb_init_module() in ../source4/dsdb/samdb/ldb_modules/password_hash.c version[1.2.2]: gpgme_check_version(1.9.0) not available, gpgme_check_version(NULL) => '1.8.0' ldb: failed to initialise module /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba/password_hash.so : Unavailable ldb: failed to initialise module /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba : Unavailable ERROR(): uncaught exception - File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 176, in _run return self.run(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/samba/netcmd/domain.py", line 474, in run nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode) File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line 2080, in provision schemadn=names.schemadn) File "/usr/lib/python2.7/dist-packages/samba/schema.py", line 82, in __init__ self.ldb = SamDB(global_schema=False, am_rodc=False) As this is the first time I'm trying this, it may well be that I've missed something essential; OTOH I'd expect that when installing from Debian packages that any details are already taken care of. Thanks, Paul -- Package-specific info: * /etc/samba/smb.conf present, and attached * /etc/samba/dhcp.conf present, and attached -- System Information: Debian Release: buster/sid APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.3-wurtel-ws (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages samba depends on: ii adduser 3.115 ii dpkg 1.18.24 ii libattr1 1:2.4.47-2+b2 ii libbsd0 0.8.6-2 ii libc6 2.24-17 ii libldb1 2:1.2.2-2 ii libpam-modules1.1.8-3.6 ii libpam-runtime1.1.8-3.6 ii libpopt0 1.16-10+b2 ii libpython2.7 2.7.13-2 ii libtalloc22.1.8-1 ii libtdb1 1.3.11-2 ii libtevent00.9.31-1 ii lsb-base 9.20161125 ii procps2:3.3.12-3 ii python2.7.13-2 ii python-dnspython 1.15.0-1 ii python-samba 2:4.7.3+dfsg-1 ii python2.7 2.7.13-2 ii samba-common 2:4.7.3+dfsg-1 ii samba-common-bin 2:4.7.3+dfsg-1 ii samba-libs2:4.7.3+dfsg-1 ii tdb-tools 1.3.11-2 Versions of packages samba recommends: ii attr1:2.4.47-2+b2 ii logrotate 3.11.0-0.1 ii samba-dsdb-modules 2:4.7.3+dfsg-1 ii samba-vfs-modules 2:4.7.3+dfsg-1 Versions of packages samba suggests: pn bind9 pn bind9utils 1:9.11.2+dfsg-5 pn ctdb pn ldb-tools 2:1.2.2-2 ii ntp1:4.2.8p10+dfsg-3 pn smbldap-tools 0.9.9-1 pn ufw ii winbind2:4.7.3+dfsg-1 -- no debconf information # Global parameters [global] netbios name = WURTEL-WS realm = WURTEL.NET workgroup = WURTEL dns forwarder = 172.18.0.2 server role = active directory domain controller idmap_ldb:use rfc2307 = yes [netlogon] path =
Bug#986319: marked as done (towncrier: incorrect Homepage URL)
Your message dated Wed, 27 Apr 2022 13:34:10 + with message-id and subject line Bug#986319: fixed in towncrier 21.9.0-1 has caused the Debian Bug report #986319, regarding towncrier: incorrect Homepage URL 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.) -- 986319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: towncrier Severity: minor Usertags: homepage The web page at the URL in the current Homepage field says that the homepage for towncrier is elsewhere. $ apt-cache show towncrier | grep -i homepage Homepage: https://pypi.org/project/towncrier/ $ curl -s https://pypi.org/project/towncrier/ | html2markdown | grep -i homepage | sort -u * [ __Homepage](https://github.com/hawkowl/towncrier) -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental'), (500, 'testing-security') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages towncrier depends on: ii python3 3.9.2-2 ii python3-click7.1.2-1 ii python3-incremental 17.5.0-1 ii python3-jinja2 2.11.3-1 ii python3-toml 0.10.1-1 towncrier recommends no packages. towncrier suggests no packages. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: towncrier Source-Version: 21.9.0-1 Done: Ben Finney We believe that the bug you reported is fixed in the latest version of towncrier, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Finney (supplier of updated towncrier 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 22:14:36 +1000 Source: towncrier Architecture: source Version: 21.9.0-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 986319 Changes: towncrier (21.9.0-1) unstable; urgency=medium . * The “Jerri Sloan” release. * New upstream release. Highlights since previous release: * Features now delegated to ‘towncrier’ sub-commands. * New ‘create’ sub-command, to create a news fragment. * New ‘check’ sub-command, to validate the news fragments. * New ‘--config’ option to specify configuration file. * Allow configuration of project ‘version’ and ‘name’. * Document the copyright status of ‘CODE_OF_CONDUCT.md’. * Use the verbatim copyright attribution for the project files. * Declare conformance to “Standards-Version: 4.6.0”. * Remove obsolete field from DEP-12 metadata. * Document the current main packaging development VCS branch. * Update the canonical Debian packaging VCS repository. * Update the project homepage. Closes: bug#986319. Thanks to Paul Wise for the report. * Update the URL for fetching upstream source. * Add specification for AutoPkgTest of the installed package. * Override false positive Lintian check for VCS-* field names. * Add a manual page document for the ‘towncrier’ command. * Install the upstream README document. * Install the upstream change log document. Checksums-Sha1: 2a70bb70f25df21a3b16c568a3924e02bae01a76 1999 towncrier_21.9.0-1.dsc ccd415961f8805ac90c4568dcf5635d22cb85953 32161 towncrier_21.9.0.orig.tar.gz 87117d266e2029657f0eb15e096708471263eb02 11048 towncrier_21.9.0-1.debian.tar.xz 6f1d397247b163ed83464e3fabddc477ea4cf859 6962 towncrier_21.9.0-1_amd64.buildinfo Checksums-Sha256: dee633678022f1b52a9542cc42d18efc2bf59bbb09eeddc50bfe30073825c17a 1999 towncrier_21.9.0-1.dsc
Bug#1009194: marked as done (open-vm-tools: Please do not run udevadm trigger without parameters)
Your message dated Wed, 27 Apr 2022 11:19:15 + with message-id and subject line Bug#1009194: fixed in open-vm-tools 2:12.0.0-1 has caused the Debian Bug report #1009194, regarding open-vm-tools: Please do not run udevadm trigger without parameters 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.) -- 1009194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: open-vm-tools Version: 2:11.3.5-1 Severity: normal X-Debbugs-Cc: bdr...@ubuntu.com Dear Maintainer, open-vm-tools calls `udevadm trigger` in it's postinst script (line 8). Since no options or devpaths/files/units are specified, udevadm will trigger events for **all** devices. This will trigger a lot of udev rules and can cause unwanted side effects (like Ubuntu bug https://launchpad.net/bugs/1875062). You can see the list of triggered devices by running `udevadm trigger --verbose --dry-run`. Please run `udevadm trigger` only for the relevant subsystems/attributes. Example: ``` udevadm trigger --type=devices --subsystem-match=scsi ``` Bug-Ubuntu: https://launchpad.net/bugs/1968354 -- Benjamin Drung Debian & Ubuntu Developer --- End Message --- --- Begin Message --- Source: open-vm-tools Source-Version: 2:12.0.0-1 Done: Bernd Zeimetz We believe that the bug you reported is fixed in the latest version of open-vm-tools, 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. Bernd Zeimetz (supplier of updated open-vm-tools 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 11:54:11 +0200 Source: open-vm-tools Architecture: source Version: 2:12.0.0-1 Distribution: unstable Urgency: medium Maintainer: Bernd Zeimetz Changed-By: Bernd Zeimetz Closes: 1006845 1009194 Changes: open-vm-tools (2:12.0.0-1) unstable; urgency=medium . [ Debian Janitor Bot ] * [b8a7e72] Bump debhelper from old 12 to 13. + Rename debian/open-vm-tools-desktop.tmpfile to debian/open-vm-tools-desktop.tmpfiles. Changes-By: lintian-brush Fixes: lintian: package-uses-old-debhelper-compat-version See-also: https://lintian.debian.org/tags/package-uses-old-debhelper-compat-version.html * [db353fc] Update renamed lintian tag names in lintian overrides. Changes-By: lintian-brush Fixes: lintian: renamed-tag See-also: https://lintian.debian.org/tags/renamed-tag.html * [e836429] Set upstream metadata fields: Archive. Changes-By: lintian-brush . [ Bernd Zeimetz ] * [c68b4a7] New upstream version 12.0.0 (Closes: #1006845) * [5e498c2] Refresh patches * [d1a0fb3] udevadm: trigger only for scsi devices on install. Thanks to Benjamin Drung (Closes: #1009194) Checksums-Sha1: 0fe2d3cad3ae1f02ba87e27633dca65af722ff4a 2560 open-vm-tools_12.0.0-1.dsc 96fd9dfd0832784345ad7062422b8b2cf7463484 1775076 open-vm-tools_12.0.0.orig.tar.xz d23b11a133385b93716e35b25e0aa77fcbd35db5 32552 open-vm-tools_12.0.0-1.debian.tar.xz fa08cbabfea2fc2cf89e5c28c6d7b2c7ff8b49f6 7744 open-vm-tools_12.0.0-1_source.buildinfo Checksums-Sha256: a5e82d39011bcace607dbd98769b897c6b4383f7377364d26fcee74db0c5bacb 2560 open-vm-tools_12.0.0-1.dsc 794d8bb1533a61b361ec8d546e4b83d62241a9256db645b251e4d2bc33708c31 1775076 open-vm-tools_12.0.0.orig.tar.xz e5558015d92ae400e69335d112b39073f37980518208f74f2525d8bcd8484897 32552 open-vm-tools_12.0.0-1.debian.tar.xz fbcbea43275dc39ef20c6baaebd8781328ba2c8d5eafe53a968fd67229250030 7744 open-vm-tools_12.0.0-1_source.buildinfo Files: baa1dc1b311d95750186c12e46f0b875 2560 admin optional open-vm-tools_12.0.0-1.dsc ccd82bb8850a405558dbbd0bd94df994 1775076 admin optional open-vm-tools_12.0.0.orig.tar.xz 19c2bbbd349c052375a2f02610484fea 32552 admin optional open-vm-tools_12.0.0-1.debian.tar.xz 92ebe53cbe6e3522c3a4f5ed0731e31a 7744 admin optional open-vm-tools_12.0.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAmJpIrkACgkQ6zYXGm/5 Q1+PRA//foMAbttGp/rBIPNYZHymdX5nico/F5634LDcCt7suHIk3ww66pijbx9O
Bug#1006845: marked as done (Open-vm-tools 12.0.0 has been released.)
Your message dated Wed, 27 Apr 2022 11:19:15 + with message-id and subject line Bug#1006845: fixed in open-vm-tools 2:12.0.0-1 has caused the Debian Bug report #1006845, regarding Open-vm-tools 12.0.0 has been released. 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.) -- 1006845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: open-vm-tools Version: 2:12.0.0 Version 12.0.0 adds two optional features plus fixes. Open-vm-tools 12.0.0 was released on Mar. 4, 2022. The VMware Tools 12.0.0 was officially released on Mar. 1, 2022. This release contains two new, optional features - Support for managing Salt Minion. - port for gathering and publishing a list of containers running inside Linux guests. and several fixes including: - build with either libfuse2 or libfuse3. It contains a known problem - a potential Fail to Build from Source [FTBFS] and a pointer to an available fix from the "devel" branch at https://github.com/vmware/open-vm-tools/. For complete details, see: https://github.com/vmware/open-vm-tools/releases/tag/stable-12.0.0 Release Notes are available at: https://github.com/vmware/open-vm-tools/blob/stable-12.0.0/ReleaseNotes.md The granular changes that have gone into the 12.0.0 release are in the ChangeLog at https://github.com/vmware/open-vm-tools/blob/stable-12.0.0/open-vm-tools/ChangeLog. Please rebase open-vm-tools to release 12.0.0 on supported Debian Linux releases as appropriate. --- End Message --- --- Begin Message --- Source: open-vm-tools Source-Version: 2:12.0.0-1 Done: Bernd Zeimetz We believe that the bug you reported is fixed in the latest version of open-vm-tools, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernd Zeimetz (supplier of updated open-vm-tools 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 11:54:11 +0200 Source: open-vm-tools Architecture: source Version: 2:12.0.0-1 Distribution: unstable Urgency: medium Maintainer: Bernd Zeimetz Changed-By: Bernd Zeimetz Closes: 1006845 1009194 Changes: open-vm-tools (2:12.0.0-1) unstable; urgency=medium . [ Debian Janitor Bot ] * [b8a7e72] Bump debhelper from old 12 to 13. + Rename debian/open-vm-tools-desktop.tmpfile to debian/open-vm-tools-desktop.tmpfiles. Changes-By: lintian-brush Fixes: lintian: package-uses-old-debhelper-compat-version See-also: https://lintian.debian.org/tags/package-uses-old-debhelper-compat-version.html * [db353fc] Update renamed lintian tag names in lintian overrides. Changes-By: lintian-brush Fixes: lintian: renamed-tag See-also: https://lintian.debian.org/tags/renamed-tag.html * [e836429] Set upstream metadata fields: Archive. Changes-By: lintian-brush . [ Bernd Zeimetz ] * [c68b4a7] New upstream version 12.0.0 (Closes: #1006845) * [5e498c2] Refresh patches * [d1a0fb3] udevadm: trigger only for scsi devices on install. Thanks to Benjamin Drung (Closes: #1009194) Checksums-Sha1: 0fe2d3cad3ae1f02ba87e27633dca65af722ff4a 2560 open-vm-tools_12.0.0-1.dsc 96fd9dfd0832784345ad7062422b8b2cf7463484 1775076 open-vm-tools_12.0.0.orig.tar.xz d23b11a133385b93716e35b25e0aa77fcbd35db5 32552 open-vm-tools_12.0.0-1.debian.tar.xz fa08cbabfea2fc2cf89e5c28c6d7b2c7ff8b49f6 7744 open-vm-tools_12.0.0-1_source.buildinfo Checksums-Sha256: a5e82d39011bcace607dbd98769b897c6b4383f7377364d26fcee74db0c5bacb 2560 open-vm-tools_12.0.0-1.dsc 794d8bb1533a61b361ec8d546e4b83d62241a9256db645b251e4d2bc33708c31 1775076 open-vm-tools_12.0.0.orig.tar.xz e5558015d92ae400e69335d112b39073f37980518208f74f2525d8bcd8484897 32552 open-vm-tools_12.0.0-1.debian.tar.xz fbcbea43275dc39ef20c6baaebd8781328ba2c8d5eafe53a968fd67229250030 7744 open-vm-tools_12.0.0-1_source.buildinfo Files: baa1dc1b311d95750186c12e46f0b875 2560 admin optional open-vm-tools_12.0.0-1.dsc ccd82bb8850a405558dbbd0bd94df994 1775076 admin optional open-vm-tools_12.0.0.orig.tar.xz 19c2bbbd349c052375a2f02610484fea
Bug#1009996: marked as done (IBus broken on GNOME on x11)
Your message dated Wed, 27 Apr 2022 11:04:26 + with message-id and subject line Bug#1009996: fixed in im-config 0.51-1 has caused the Debian Bug report #1009996, regarding IBus broken on GNOME on x11 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.) -- 1009996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: im-config Version: 0.50-2 Hi! The IBus configuration has been messed up somehow, and inputting using IBus does no longer (Debian testing) work out of the box on GNOME on Xorg. There is a problem also on Ubuntu 22.04 on Xorg, but there the issue is limited to the candidate window being shown at the bottom of the application window instead of close to the cursor. Related Ubuntu bug: https://launchpad.net/bugs/1969637 There have been changes to gnome-settings-daemon in GNOME 42 which most likely are related. The gtk-im-module dconf key is no longer assigned the value "ibus" dynamically as was the case previously, but it's unset even if IBus IMs are included in the list of input sources. You can set gtk-im-module manually: gsettings set org.gnome.desktop.interface gtk-im-module ibus and IBus starts working. Another way to make it work is to set the environment variable GTK_IM_MODULE to "ibus". Please see the Ubuntu bug for further info. Ideally we should of course try to spot the root cause of this issue and fix it properly, and one purpose of submitting this bug is to seek help in that respect. But on the Ubuntu side this is really urgent. Ubuntu 22.04 LTS was released yesterday, and there we should make a stable release update ASAP with some kind of fix/workaround. I submitted this im-config merge request: https://salsa.debian.org/input-method-team/im-config/-/merge_requests/15 It works around the issue. Maybe we should use that on both Debian and Ubuntu for now. In any case, unless some more proper solution comes up very soon, I'm inclined to use it for a stable release update on Ubuntu. -- Looking forward to your input! Gunnar --- End Message --- --- Begin Message --- Source: im-config Source-Version: 0.51-1 Done: Gunnar Hjalmarsson We believe that the bug you reported is fixed in the latest version of im-config, 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. Gunnar Hjalmarsson (supplier of updated im-config 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 12:09:43 +0200 Source: im-config Built-For-Profiles: noudeb Architecture: source Version: 0.51-1 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: Gunnar Hjalmarsson Closes: 1009996 Launchpad-Bugs-Fixed: 1969637 Changes: im-config (0.51-1) unstable; urgency=medium . * Team upload * Set GTK_IM_MODULE in GNOME on Xorg sessions - Closes: #1009996, LP: #1969637 Checksums-Sha1: 54151411b0e0bbc9d6e6cde6194354b8c498e0d2 1632 im-config_0.51-1.dsc ce04bb56b3033ec217b4557ed169f3e4425a3ea9 56924 im-config_0.51.orig.tar.xz f859197ce88d6b74e8b11022636695866135eb01 13420 im-config_0.51-1.debian.tar.xz 8c26c425e56353ffac9f759018db661e7f62cbb5 11587 im-config_0.51-1_source.buildinfo Checksums-Sha256: 096b8263b4a0be61b53cd40b951989e2b214de5057087105603f9d8ca2c3cb24 1632 im-config_0.51-1.dsc 3c77e06c9ed8e2e98287751ffc4346d800e0a8e50d8bc4a990b5000e9aef174a 56924 im-config_0.51.orig.tar.xz af3ac235703162117a772bcc8d220f419d75b461adc083359a4d7a873dd80daf 13420 im-config_0.51-1.debian.tar.xz 07bc706a7465fdd24707284662161e7d2122f0e44a3868488555cb859b104558 11587 im-config_0.51-1_source.buildinfo Files: 2bf7d1f352fcdc590c1a182b9884c29d 1632 utils optional im-config_0.51-1.dsc ffe3703b27824be4f854b60451fcbe98 56924 utils optional im-config_0.51.orig.tar.xz 1e5250fe0fe58cb1471b43d26ef7d928 13420 utils optional im-config_0.51-1.debian.tar.xz 2fb0478c74de5a95e722ad1c1724185b 11587 utils optional im-config_0.51-1_source.buildinfo -BEGIN PGP SIGNATURE-
Processed: close 1009701
Processing commands for cont...@bugs.debian.org: > close 1009701 Bug #1009701 [opencpn] opencpn: Wrong gtk linkage causes plugin incompatibility Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 1009701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009701 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#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 ---
Bug#1009098: marked as done (gourmand: Conversion of gourmet recipes to gourmand failed: servings/yields)
Your message dated Wed, 27 Apr 2022 07:34:06 + with message-id and subject line Bug#1009098: fixed in gourmand 1.0.0-8 has caused the Debian Bug report #1009098, regarding gourmand: Conversion of gourmet recipes to gourmand failed: servings/yields 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.) -- 1009098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gourmand Version: 1.0.0-6 Severity: normal Tags: patch A number of my recipes crash when loading: DEBUG: /usr/lib/python3/dist-packages/gourmand/reccard.py: 481 showing attribute rating = 2 4:27am DEBUG: /usr/lib/python3/dist-packages/gourmand/reccard.py: 495 hiding attribute preptime Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gourmand/main.py", line 1083, in show w = reccard.RecCard(self, rec) File "/usr/lib/python3/dist-packages/gourmand/reccard.py", line 72, in __init__ self.show() File "/usr/lib/python3/dist-packages/gourmand/reccard.py", line 117, in show self.show_display() File "/usr/lib/python3/dist-packages/gourmand/reccard.py", line 97, in show_display self.__rec_display = RecCardDisplay(self, self.__rec_gui, File "/usr/lib/python3/dist-packages/gourmand/reccard.py", line 201, in __init__ self.update_from_database() File "/usr/lib/python3/dist-packages/gourmand/reccard.py", line 470, in update_from_database special_display_functions[attr]() File "/usr/lib/python3/dist-packages/gourmand/reccard.py", line 517, in update_yields_display self.yields_orig = float(self.yields_orig) TypeError: float() argument must be a string or a number, not 'NoneType' I believe it is because the yields is null. If I run sqlite3 on the gourmet database, both yields and servings were set to 0.0. In gourmand, both the yields and servings were set to null. Running: update recipe set yields=0 where yields is null; fixes the problem. -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gourmand depends on: ii gir1.2-gtk-3.0 3.24.24-4+deb11u2 ii python3 3.9.2-3 ii python3-argcomplete 1.8.1-1.5 ii python3-bs4 4.9.3-1 ii python3-gi 3.38.0-2 ii python3-gst-1.0 1.18.3-1 ii python3-lxml 4.6.3+dfsg-0.1+deb11u1 ii python3-pil 8.1.2+dfsg-0.3+deb11u1 ii python3-reportlab3.5.59-2 ii python3-requests 2.25.1+dfsg-2 ii python3-sqlalchemy 1.3.22+ds1-1 ii python3-toml 0.10.1-1 Versions of packages gourmand recommends: pn python3-gtkspellcheck pn python3-pyglet Versions of packages gourmand suggests: pn python3-ebooklib -- no debconf information --- End Message --- --- Begin Message --- Source: gourmand Source-Version: 1.0.0-8 Done: Christian Marillat We believe that the bug you reported is fixed in the latest version of gourmand, 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. Christian Marillat (supplier of updated gourmand 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:17:31 +0200 Source: gourmand Architecture: source Version: 1.0.0-8 Distribution: unstable Urgency: medium Maintainer: Christian Marillat Changed-By: Christian Marillat Closes: 1009098 Changes: gourmand (1.0.0-8) unstable; urgency=medium . * Add upstream patch to fix a crash when a yield values is None (Closes: #1009098) Checksums-Sha1: ab83c7ba4ae73de2424b35f4ec9a30b64bd11c8b 1849
Bug#979547: marked as done (smartmontools: Homepage redirects to www.smartmontools.org)
Your message dated Wed, 27 Apr 2022 06:34:48 + with message-id and subject line Bug#979547: fixed in smartmontools 7.3-1 has caused the Debian Bug report #979547, regarding smartmontools: Homepage redirects to www.smartmontools.org 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.) -- 979547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: smartmontools Version: 7.2-1 Severity: minor I noticed that the smartmontools SourceForge page redirects to a different site and so I suggest updating the Homepage field in the Debian package to the new site: https://www.smartmontools.org/ $ wget -O /dev/null $(apt-cache show smartmontools | sed -n 's/Homepage: //p' | sort -u) --2021-01-08 12:53:12-- http://smartmontools.sourceforge.net/ Resolving smartmontools.sourceforge.net (smartmontools.sourceforge.net)... 216.105.38.10 Connecting to smartmontools.sourceforge.net (smartmontools.sourceforge.net)|216.105.38.10|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.smartmontools.org/ [following] URL transformed to HTTPS due to an HSTS policy --2021-01-08 12:53:13-- https://www.smartmontools.org/ Resolving www.smartmontools.org (www.smartmontools.org)... 185.82.212.181, 2a03:6920:0:10::101 Connecting to www.smartmontools.org (www.smartmontools.org)|185.82.212.181|:443... connected. HTTP request sent, awaiting response... 200 Ok Length: 21952 (21K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[=>] 21.44K 57.9KB/sin 0.4s 2021-01-08 12:53:15 (57.9 KB/s) - ‘/dev/null’ saved [21952/21952] -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smartmontools depends on: ii debianutils 4.11.2 ii libc62.31-9 ii libcap-ng0 0.7.9-2.2+b1 ii libgcc-s110.2.1-3 ii libselinux1 3.1-2+b2 ii libstdc++6 10.2.1-3 ii libsystemd0 247.2-4 ii lsb-base 11.1.0 smartmontools recommends no packages. Versions of packages smartmontools suggests: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-2 ii curl 7.74.0-1 ii gpg2.2.20-1 pn gsmartcontrol ii lynx 2.9.0dev.6-1 ii smart-notifier 0.28-6 ii wget 1.20.3-1+b3 -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: smartmontools Source-Version: 7.3-1 Done: Dmitry Smirnov We believe that the bug you reported is fixed in the latest version of smartmontools, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated smartmontools 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 15:39:01 +1000 Source: smartmontools Architecture: source Version: 7.3-1 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Closes: 979547 1006630 Changes: smartmontools (7.3-1) unstable; urgency=medium . * New upstream release. * Standards-Version: 4.6.0. * Updated Homepage URL (Closes: #979547). Thanks, Paul Wise. * Removed "default_never-quit.patch" (Closes: #1006630). Thanks, Christian Franke. Checksums-Sha1: 73e0c1c1ef367c56113497a71c7be6dba6d21dbd 2186 smartmontools_7.3-1.dsc a4353360238533e97bc985ea5b3e052d99114970 772232
Bug#1006630: marked as done (smartmontools: Please do not change the upstream default of the 'smartd -q' option)
Your message dated Wed, 27 Apr 2022 06:34:48 + with message-id and subject line Bug#1006630: fixed in smartmontools 7.3-1 has caused the Debian Bug report #1006630, regarding smartmontools: Please do not change the upstream default of the 'smartd -q' option 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.) -- 1006630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: smartmontools Version: 7.2-1 The "default_never-quit.patch" changes the default of the 'smartd -q' option from '-q nodev' to '-q never'. It should be at least mentioned on the man page that this change is Debian (and possibly Ubuntu) specific. The change of the default is not required as the following setting in the service file has the same effect: ExecStart=/usr/sbin/smartd -n -q never $smartd_opts The '-q' option could then still be overridden via $smartd_opts. Note that the new 7.3 version of smartmontools adds `-q *nodev0*` option variants which change the 'no devices' exit code from 17 to 0. The service should be no longer reported as failed then. "No devices to monitor" is reported via sd_notify() if configured. Regards, Christian Franke smartmontools.org --- End Message --- --- Begin Message --- Source: smartmontools Source-Version: 7.3-1 Done: Dmitry Smirnov We believe that the bug you reported is fixed in the latest version of smartmontools, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated smartmontools 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 15:39:01 +1000 Source: smartmontools Architecture: source Version: 7.3-1 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Closes: 979547 1006630 Changes: smartmontools (7.3-1) unstable; urgency=medium . * New upstream release. * Standards-Version: 4.6.0. * Updated Homepage URL (Closes: #979547). Thanks, Paul Wise. * Removed "default_never-quit.patch" (Closes: #1006630). Thanks, Christian Franke. Checksums-Sha1: 73e0c1c1ef367c56113497a71c7be6dba6d21dbd 2186 smartmontools_7.3-1.dsc a4353360238533e97bc985ea5b3e052d99114970 772232 smartmontools_7.3.orig.tar.xz 40cdf9c74f7517b8d4960a609b1e4ade76834eac 36636 smartmontools_7.3-1.debian.tar.xz 88f0a860c34b3a6bce3c6e794096bda6943bd465 6411 smartmontools_7.3-1_amd64.buildinfo Checksums-Sha256: 05408b39b18aecf7f4f54e268c64c05209ba9a67b0982853eac2e8cfda8865fe 2186 smartmontools_7.3-1.dsc d507f2c55fb2fb644ec9759bf188283e06381901cb337c622e3ea0e17b4ac01f 772232 smartmontools_7.3.orig.tar.xz b85be59f445005fb7f129565d000b87a17fb4df142aea8340a5bcde5b1d71cdb 36636 smartmontools_7.3-1.debian.tar.xz b4d0b1084e31d1dbca2b85b9763f89f49ff9e68a8ab893ad4235853371efc070 6411 smartmontools_7.3-1_amd64.buildinfo Files: eee7ec965d7560933e2fc4e484a61fce 2186 utils optional smartmontools_7.3-1.dsc ff014a1512bfc6af958236103a238ddc 772232 utils optional smartmontools_7.3.orig.tar.xz eb414ebe551665f2e542f554afeaa30b 36636 utils optional smartmontools_7.3-1.debian.tar.xz fb0054b4bc1ebca1bcb4f9790c41b72c 6411 utils optional smartmontools_7.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmJo3JkACgkQUra72VOW jRvEDA//Yi1r6bU/C9k0zcdW9yQNXxvGwpPlnbRb9DTZ06WaR4rjyb3keRtlh2qk I0WswSqXRz2QYQbIT5Ve4oxipmd6bFIDYnuxPEuQuUcIiZNphuxAOKu3sPzPwecX N3XH2FlpztW77e/Ln8ITv9dzJ/pw1sRiCzMQ0jMEw9uBxfnVlDcrdC8UBpUX23Ro NzQanreFtZIHRmeubiWi75CdHK7blOXCbuIefHellEFr3dZw+hBQso8LPvDA5Kty /QKvdvQjDGK7wP/371BlghxtoJBTvMCvziBxxMa81njwQcvwLVhz4YykSsHj0SOw ZCNqzb8/cPON9ss9E9Gvd223JGH6I9GthrGQP3KamyPHtGwUGIsWU6eS3aGxZNIV SW8Y1cfaIiiir/+yKNgoKKt4YIu7mjChAAsNMcAp9frmmGgQSb1GhR5cDr+DS5j0 2ZL8qsTCIjRbRom6zirat2/ycnVlftgqLA0NuKA6m0Ms0aNwWjxbf3IDKziLwUbn ZnaOZ+j/46L4nXgvoSV3auc09J/Sf/EdIODLJrSP2pZcDfrQkZ7WIzuj6djcer6W UlfJ3tTSZr5FdsXpqGWolCW+TSx065OWbEZyYm8XYKvbD2udcH7lZn1StfpydprS dZo3leJ/b8o5zpyHgkcxbL+/MkWcs7jXrNc7ZiO+mFxK/yRjESY= =w+r7 -END PGP SIGNATURE
