Bug#995405: marked as done (python3-pygccxml: python3.9 error: module 'time' has no attribute 'clock')

2021-12-23 Thread Debian Bug Tracking System
Your message dated Fri, 24 Dec 2021 05:03:40 + with message-id and subject line Bug#995405: fixed in pygccxml 2.2.1-1 has caused the Debian Bug report #995405, regarding python3-pygccxml: python3.9 error: module 'time' has no attribute 'clock' to be marked as done. This means that you claim

Bug#1002527: postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist

2021-12-23 Thread Marvin Renich
Package: milter-greylist Version: 4.6.4-1 Severity: critical With an existing installation of milter-greylist set up to work with chrooted postfix (i.e. USER="postfix" in /etc/default/milter-greylist), every upgrade sets the owner of the directory /var/lib/milter-greylist to "greylist" regardless

brandy_1.20.1-3_source.changes ACCEPTED into unstable

2021-12-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Dec 2021 17:40:02 +0100 Source: brandy Architecture: source Version: 1.20.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Stephen Kitt Changes: brandy (1.20.1-3) unstable;

Processing of brandy_1.20.1-3_source.changes

2021-12-23 Thread Debian FTP Masters
brandy_1.20.1-3_source.changes uploaded successfully to localhost along with the files: brandy_1.20.1-3.dsc brandy_1.20.1-3.debian.tar.xz brandy_1.20.1-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1002085: marked as done (clipit: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.2.4) were not met)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002085, regarding clipit: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.2.4) were not met to be marked as done. T

Processed: your mail

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 988985 confirmed fixed-upstream pending Bug #988985 [cflow] CVE-2020-23856 Added tag(s) pending, fixed-upstream, and confirmed. > End of message, stopping processing here. Please contact me if you need assistance. -- 988985: https://bugs.de

Processed: your mail

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 939916 confirmed fixed-upstream pending Bug #939916 [src:cflow] cflow: CVE-2019-16166 Added tag(s) confirmed, pending, and fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 939916: http

Processed: your mail

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 939915 confirmed fixed-upstream pending Bug #939915 [src:cflow] cflow: CVE-2019-16165 Added tag(s) pending, confirmed, and fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 939915: http

Bug#931113: cflow: wierd Info node with emacs

2021-12-23 Thread Marcos Talau
Control: tags 931113 confirmed fixed-upstream patch pending upstream Hi Dmitry! First, thanks for your report! I talked with the upstream and he gently fixed this in the commit: https://git.savannah.gnu.org/cgit/cflow.git/commit/?id=7aa2a89af63849736df6a230927d54cf25e3bf51 The fix will be par

Processed: Re: cflow: wierd Info node with emacs

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > tags 931113 confirmed fixed-upstream patch pending upstream Bug #931113 [cflow] cflow: wierd Info node with emacs Added tag(s) upstream, patch, pending, confirmed, and fixed-upstream. -- 931113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931113 Debian Bug Tr