Bug#949299: coinor-vol misses source for configure

2020-01-19 Thread Sudip Mukherjee
Control: owner -1 ! On Sun, Jan 19, 2020 at 04:26:25PM +0100, Helmut Grohne wrote: > Source: coinor-vol > Version: 1.5.4-1 > Severity: severity > Justification: missing source > > coinor-vol includes a configure script generated using autoconf. The > relevant configure.ac file is included in the

Bug#949299: coinor-vol misses source for configure

2020-01-19 Thread Sudip Mukherjee
Looks like I misread the bug report and thought it to be the same as missing source for NEW upload. I will check about the source for the configure script. -- Regards Sudip

Bug#952404: scanbd: crash on startup: kernel internal error: Oops 206 with current raspbian buster on rpi4 4g

2020-02-26 Thread Sudip Mukherjee
I tried it on a qemu image for aarch64 and could not reproduce the probem, and there was no error in dmesg. root@debian-arm64:/home/sudip# lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 10 (buster) Release:10 Codename: buster roo

Bug#952404: scanbd: crash on startup: kernel internal error: Oops 206 with current raspbian buster on rpi4 4g

2020-03-25 Thread Sudip Mukherjee
Thanks for testing and debugging it. Can you please send me your dmesg which shows the trace. -- Regards Sudip

Bug#777058: dbview: please make the build reproducible

2020-09-02 Thread Sudip Mukherjee
On Tue, Sep 01, 2020 at 10:58:04PM -, Chris Lamb wrote: > Chris Lamb wrote: > > > [..] > > Friendly ping on this? This is an orphan package and anyone can make a QA upload. And can you please check again if it still has the problem? d/rules has been completely rewritten with 1.0.4-2 version

Bug#777410: freecdb: please make the build reproducible

2020-09-02 Thread Sudip Mukherjee
On Tue, Sep 01, 2020 at 10:58:07PM -, Chris Lamb wrote: > Chris Lamb wrote: > > > [..] > > Friendly ping on this? This is an orphan package and anyone can make a QA upload. And can you please check again if it still has the problem? d/rules has been completely rewritten with 0.76 version and

Bug#969795: 2vcard: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: 2vcard Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of '2vcard' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969797: altermime: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: altermime Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'altermime' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.p

Bug#969808: cfourcc: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: cfourcc Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'cfourcc' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.packa

Bug#969812: cldump: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: cldump Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'cldump' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969811: changetrack: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: changetrack Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'changetrack' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/READ

Bug#969817: diffmon: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: diffmon Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'diffmon' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.packa

Bug#969821: dpatch: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: dpatch Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'dpatch' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969822: dyndns: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: dyndns Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'dyndns' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969826: flpsed: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: flpsed Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'flpsed' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969828: fwlogwatch: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: fwlogwatch Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'fwlogwatch' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README

Bug#969832: gox: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: gox Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'gox' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests

Bug#969842: mailcheck: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: mailcheck Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'mailcheck' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.p

Bug#969843: makebootfat: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: makebootfat Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'makebootfat' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/READ

Bug#969840: lxmms2: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: lxmms2 Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'lxmms2' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969849: ncap: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: ncap Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'ncap' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tes

Bug#969861: rdist: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: rdist Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'rdist' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-t

Bug#969870: tcpspy: autopkgtest should be marked superficial

2020-09-08 Thread Sudip Mukherjee
Source: tcpspy Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'tcpspy' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package

Bug#969822: Update to severity

2020-09-19 Thread Sudip Mukherjee
Control: severity -1 important -- Hi, As discussed on debian-devel, I am reducing the severity to important. Ref: https://lists.debian.org/debian-devel/2020/09/msg00266.html -- Regards Sudip

Bug#970946: apngasm: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: apngasm Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in apngasm is running a trivial command that does not provide significant test coverage: -Test-Command: apngasm | grep APNG Executing t

Bug#970945: acorn-fdisk: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: acorn-fdisk Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in acorn-fdisk is running a trivial command that does not provide significant test coverage: -Test-Command: acorn-fdisk --help | gre

Bug#970947: bmf: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: bmf Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in bmf is running a trivial command that does not provide significant test coverage: -Test-Command: bmf -V 2>&1 | grep version -Tes

Bug#970948: copyright-update: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: copyright-update Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in copyright-update is running a trivial command that does not provide significant test coverage: -Test-Command: copyright-upda

Bug#970955: herisvm: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: herisvm Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in herisvm is running a trivial command that does not provide significant test coverage: -Test-Command: heri-eval -h 2>&1 | grep usage

Bug#970962: procinfo: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: procinfo Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in procinfo is running a trivial command that does not provide significant test coverage: -Test-Command: procinfo -h -Test-Com

Bug#970957: mmorph: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: mmorph Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in mmorph is running a trivial command that does not provide significant test coverage: -Test-Command: mmorph -h -Test-Command:

Bug#970956: lockout: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: lockout Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in lockout is running a trivial command that does not provide significant test coverage: -Test-Command: lockout | grep -i version Exec

Bug#970975: vlock: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: vlock Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in vlock is running a trivial command that does not provide significant test coverage: -Test-Command: vlock -h -Test-Command: vlo

Bug#970974: trueprint: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: trueprint Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in trueprint is running a trivial command that does not provide significant test coverage: -Test-Command: trueprint -H -Test-

Bug#970968: rdist: autopkgtest must be marked superficial

2020-09-25 Thread Sudip Mukherjee
Source: rdist Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in rdist is running a trivial command that does not provide significant test coverage: -Test-Command: rdist -V Executing that command is

Bug#971498: python-mplexporter: autopkgtest must be marked superficial

2020-09-30 Thread Sudip Mukherjee
Source: python-mplexporter Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in python-mplexporter is running a trivial command that does not provide significant test coverage: - testcommand: import mpl

Bug#974445: antigrav: autopkgtest must be marked superficial

2020-11-11 Thread Sudip Mukherjee
Source: antigrav X-Debbugs-CC: elb...@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in antigrav is running a trivial command that does not provide significant test coverage: - xvfb-run -a /usr/games/antigrav & Executin

Bug#974436: aewm: autopkgtest must be marked superficial

2020-11-11 Thread Sudip Mukherjee
Source: aewm X-Debbugs-CC: elb...@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in aewm is running a trivial command that does not provide significant test coverage: - xvfb-run -a aewm & Executing that command is consi

Bug#974457: iroffer: autopkgtest must be marked superficial

2020-11-11 Thread Sudip Mukherjee
Source: iroffer X-Debbugs-CC: elb...@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in iroffer is running a trivial command that does not provide significant test coverage: - iroffer -v Executing that command is conside

Bug#974486: gramofile: autopkgtest must be marked superficial

2020-11-11 Thread Sudip Mukherjee
Source: gramofile X-Debbugs-CC: elb...@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in gramofile is running a trivial command that does not provide significant test coverage: - xvfb-run -a gramofile & Executing that c

Bug#974510: zope.exceptions: autopkgtest must be marked superficial

2020-11-11 Thread Sudip Mukherjee
Source: zope.exceptions X-Debbugs-CC: elb...@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in zope.exceptions is running a trivial command that does not provide significant test coverage: - import zope.exceptions; print

Bug#979965: milter-greylist exits after running for a few minutes

2021-01-12 Thread Sudip Mukherjee
Hi Michael, On Tue, Jan 12, 2021 at 5:54 PM Vagrant Cascadian wrote: > > On 2021-01-12, Michael Grant wrote: > > After update to 4.6.2-2, milter-greylist runs for a few minutes > > processing greylist requests then exits. No error in the daemon.log. > > Daemon restarts with systemd over and over

Bug#979965: milter-greylist exits after running for a few minutes

2021-01-12 Thread Sudip Mukherjee
On Tue, Jan 12, 2021 at 9:36 PM Michael Grant wrote: > > I have made this change: > > > > [Service] > > Type=forking > > ExecStart=/usr/sbin/milter-greylist > > Restart=on-failure > > PrivateTmp=true > > > > And it’s still restarting every few minutes: > > > > Jan 12 16:09:43 strange milter-greyli

Bug#979965: milter-greylist exits after running for a few minutes

2021-01-13 Thread Sudip Mukherjee
On Tue, Jan 12, 2021 at 05:43:07PM -0500, Michael Grant wrote: > On Tue, Jan 12, 2021 at 10:02:19PM +0000, Sudip Mukherjee wrote: > > On Tue, Jan 12, 2021 at 9:36 PM Michael Grant wrote: > > > > > > I have made this change: > > > > > > > > >

Bug#978863: milter-greylist: ftbfs with autoconf 2.70

2021-08-26 Thread Sudip Mukherjee
Hi, On Thu, Dec 31, 2020 at 02:28:20PM +, Matthias Klose wrote: > Package: src:milter-greylist > Version: 4.6.2-1 > Severity: normal > Tags: sid bookworm > User: d...@debian.org > Usertags: ftbfs-ac270 > > [This bug report is not targeted to the upcoming bullseye release] > > The package fai

Bug#992997: milter-greylist: segfault in libGeoIP

2021-08-30 Thread Sudip Mukherjee
Hi Bjørn, On Thu, Aug 26, 2021 at 07:09:40AM +0100, Bjørn Mork wrote: > Package: milter-greylist > Version: 4.6.2-3 > Severity: normal > > Seeing lots of these after upgrading til bullseye: > > Aug 23 22:12:23 louie kernel: milter-greylist[192919]: segfault at 28 ip > 7fbaf22fe8d9 sp