Bug#1010171: marked as done (sbuild's "unshare" test fails with gpg-agent 2.2.34-1)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#963784: marked as done (qxw: New upstream release)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#901661: marked as done (qxw FTCBFS: upstream Makefile hard codes build architecture tools)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#758005: marked as done (qxw: please support non-ASCII letters)

2022-04-27 Thread Debian Bug Tracking System
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.

Bug#965911: marked as done (yasat: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#916870: marked as done (xrootconsole: debian/control Vcs- fields are dead)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#969751: marked as done (xrootconsole FTCBFS: fails running tests despite DEB_BUILD_OPTIONS=nocheck)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1010258: marked as done (python3-pymca5: flaky autopkgtest on i386)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#756151: marked as done (libnotify-bin: option -a is not described in notify-send man page)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#679653: marked as done (libnotify-bin: exit status is always zero (even in presence of errors))

2022-04-27 Thread Debian Bug Tracking System
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

Bug#636343: marked as done (libnotify-bin: Add support for hint of type boolean)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#609556: marked as done (Unhelpful error message when DBUS_SESSION_BUS_ADDRESS is not set)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#559544: marked as done (libnotify-bin: Please support notification IDs)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#571181: marked as done (libnotify-bin: add a flag to specify buttons)

2022-04-27 Thread Debian Bug Tracking System
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

Processed: RFS: kmscon/8+40-1 [ITP] -- Simple terminal emulator based on Kernel Mode Setting

2022-04-27 Thread Debian Bug Tracking System
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:

Bug#1008266: marked as done (unar: obsolete syntax of bash-completion file)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#974972: marked as done (unar: There is a new upstream version)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1010123: marked as done (network-manager: Wifi randomly stops after upgrade and do not auto connect)

2022-04-27 Thread Debian Bug Tracking System
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,

Bug#1008823: marked as done (transition: thrift)

2022-04-27 Thread Debian Bug Tracking System
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

Processed: closing 909401

2022-04-27 Thread Debian Bug Tracking System
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#911977: marked as done (how do we correctly guess the VM name in autopkgtest?)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#601897: marked as done (libnotify1: Raises exception if notify_uninit is called immediately after notify_init)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#499904: marked as done (libnotify-bin: notify-send incorrect display text with long words)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#630539: marked as done (libnotify1: Notifications cause menu items to go black.)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#617958: marked as done (libnotify-bin: Critical notifications should not expire)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#705608: marked as done (libnotify4: Notifications are offset when using a dual-screen)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#644923: marked as done (/usr/bin/notify-send: notify-send cannot be above FEH -F -Z)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#597272: marked as done (/usr/bin/notify-send: center of the screen argument in help file)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#597136: marked as done (/usr/bin/notify-send: would be great to have resize icons to fit (wish) although CPU power)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1004921: marked as done (libtsm: Package too old for kmscon)

2022-04-27 Thread Debian Bug Tracking System
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.

Bug#698852: marked as done ([libnotify-bin] character '&' in message text causes whole message to display empty)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#869283: marked as done (libnotify-bin: Can not find the sources of the manpage)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#869277: marked as done (/usr/bin/notify-send: Improve the manpage)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#869409: marked as done (libnotify-bin: add informations about upstream)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1007626: marked as done (libmodem-vgetty-perl: please consider upgrading to 3.0 source format)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1010277: marked as done (threeb: Correct changelog formatting)

2022-04-27 Thread Debian Bug Tracking System
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

Processed: closing 1002743

2022-04-27 Thread Debian Bug Tracking System
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:

Processed: your mail

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1009883: marked as done (dh_haskell_install_ghc_registration: does not support directories)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1010179: marked as done (haskell-devscripts: DEB_ENABLE_TESTS broken)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1010055: marked as done (ITP: base16384 -- Encode binary file to printable utf16be, and vise versa.)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1008929: marked as done (ModuleNotFoundError: No module named 'mistune.plugins'; 'mistune' is not a package)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#925180: marked as done (samba: upgrade does not pull in required libgpgme11 and fails to start smbd etc.)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#886333: marked as done (samba: cannot provision a domain: ldb_init_module() complains about gpgme_check_version(1.9.0))

2022-04-27 Thread Debian Bug Tracking System
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:

Bug#986319: marked as done (towncrier: incorrect Homepage URL)

2022-04-27 Thread Debian Bug Tracking System
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.

Bug#1009194: marked as done (open-vm-tools: Please do not run udevadm trigger without parameters)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1006845: marked as done (Open-vm-tools 12.0.0 has been released.)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1009996: marked as done (IBus broken on GNOME on x11)

2022-04-27 Thread Debian Bug Tracking System
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

Processed: close 1009701

2022-04-27 Thread Debian Bug Tracking System
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:

Bug#1009721: marked as done (gst-plugins-bad1.0 build-depends on obsolete package.)

2022-04-27 Thread Debian Bug Tracking System
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

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:)

2022-04-27 Thread Debian Bug Tracking System
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,

Bug#999672: marked as done (mutt: license conflict with libsasl2)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1009098: marked as done (gourmand: Conversion of gourmet recipes to gourmand failed: servings/yields)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#979547: marked as done (smartmontools: Homepage redirects to www.smartmontools.org)

2022-04-27 Thread Debian Bug Tracking System
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

Bug#1006630: marked as done (smartmontools: Please do not change the upstream default of the 'smartd -q' option)

2022-04-27 Thread Debian Bug Tracking System
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