Bug#945797: Sketch for a patch

2019-12-04 Thread David Bürgin
Below is a first sketch for a patch (= works for me). I’ve tried to solve it with an additional patch in debian/patches. The library path, and the library name, description, and version are still hard-coded in milter.pc, they would need to be substituted in from somewhere. Perhaps it would be bett

Processed: notfound 944776 in prepair/0.7.1-3+b2, found 944776 in 0.7.1-3, tagging 944775, tagging 946114 ...

2019-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 944776 prepair/0.7.1-3+b2 Bug #944776 [src:prepair] FTBFS with CGAL 5.0 The source prepair and version 0.7.1-3+b2 do not appear to match any binary packages No longer marked as found in versions prepair/0.7.1-3+b2. > found 944776 0.7.1-3

Bezoek ons vandaag op Kortrijk XPO

2019-12-04 Thread Ergovan
Version en ligne ([[webcopy]]) La moitié de nos clients sontfrançais, alors pourquoi pas vous? Pas de frais de déplacement - montage chez vous en1 jour 1. MEILLEUR RAPPORT QUALITE / PRIX 2. MONTAGE CHEZ VOUS SANS SUPPLEMENT 3. UN VRAI SERVICE ! Ergovan, votre partenaire en aménagement de véhi

Processing of sweep_0.9.3-9_source.changes

2019-12-04 Thread Debian FTP Masters
sweep_0.9.3-9_source.changes uploaded successfully to localhost along with the files: sweep_0.9.3-9.dsc sweep_0.9.3-9.debian.tar.xz sweep_0.9.3-9_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

sweep_0.9.3-9_source.changes ACCEPTED into unstable

2019-12-04 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Dec 2019 16:57:15 -0500 Source: sweep Architecture: source Version: 0.9.3-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Changes: sweep (0.9.3-9) unstable; urgen

ladr is marked for autoremoval from testing

2019-12-04 Thread Debian testing autoremoval watch
ladr 0.0.200911a-2.1 is marked for autoremoval from testing on 2019-12-27 It is affected by these RC bugs: 945658: ladr: Python2 removal in sid/bullseye

fofix-dfsg is marked for autoremoval from testing

2019-12-04 Thread Debian testing autoremoval watch
fofix-dfsg 3.121-7 is marked for autoremoval from testing on 2019-12-27 It is affected by these RC bugs: 945671: fofix-dfsg: Python2 removal in sid/bullseye

flowscan-cuflow is marked for autoremoval from testing

2019-12-04 Thread Debian testing autoremoval watch
flowscan-cuflow 1.7-9 is marked for autoremoval from testing on 2020-01-11 It (build-)depends on packages with these RC bugs: 945642: flow-tools: Python2 removal in sid/bullseye

Bug#715716: marked as done ([Mayhem] Bug report on ccontrol: ccontrol crashes with exit status 139)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:16 + with message-id and subject line Bug#574013: Removed package(s) from unstable has caused the Debian Bug report #715716, regarding [Mayhem] Bug report on ccontrol: ccontrol crashes with exit status 139 to be marked as done. This means that you cla

Bug#716317: marked as done ([Mayhem] Bug report on prover9: isofilter crashes with exit status 139)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:46 + with message-id and subject line Bug#681042: Removed package(s) from unstable has caused the Debian Bug report #716317, regarding [Mayhem] Bug report on prover9: isofilter crashes with exit status 139 to be marked as done. This means that you cla

Bug#885519: marked as done (ccontrol: Recommends unmaintained pygtk)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:16 + with message-id and subject line Bug#574013: Removed package(s) from unstable has caused the Debian Bug report #885519, regarding ccontrol: Recommends unmaintained pygtk to be marked as done. This means that you claim that the problem has been de

Bug#716205: marked as done ([Mayhem] Bug report on ladr4-apps: mirror-flip crashes with exit status 139)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:46 + with message-id and subject line Bug#681042: Removed package(s) from unstable has caused the Debian Bug report #716205, regarding [Mayhem] Bug report on ladr4-apps: mirror-flip crashes with exit status 139 to be marked as done. This means that y

Bug#716206: marked as done ([Mayhem] Bug report on ladr4-apps: perm3 crashes with exit status 139)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:46 + with message-id and subject line Bug#681042: Removed package(s) from unstable has caused the Debian Bug report #716206, regarding [Mayhem] Bug report on ladr4-apps: perm3 crashes with exit status 139 to be marked as done. This means that you clai

Bug#716316: marked as done ([Mayhem] Bug report on prover9: isofilter0 crashes with exit status 139)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:46 + with message-id and subject line Bug#681042: Removed package(s) from unstable has caused the Debian Bug report #716316, regarding [Mayhem] Bug report on prover9: isofilter0 crashes with exit status 139 to be marked as done. This means that you c

Bug#716061: marked as done ([Mayhem] Bug report on prover9: isofilter2 crashes with exit status 139)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:46 + with message-id and subject line Bug#681042: Removed package(s) from unstable has caused the Debian Bug report #716061, regarding [Mayhem] Bug report on prover9: isofilter2 crashes with exit status 139 to be marked as done. This means that you c

Bug#930007: marked as done (dtrx does not support password encrypted zip files)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:22:42 + with message-id and subject line Bug#830618: Removed package(s) from unstable has caused the Debian Bug report #930007, regarding dtrx does not support password encrypted zip files to be marked as done. This means that you claim that the problem

Bug#721836: marked as done (mididings-doc: Wrong path for examples)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:22:14 + with message-id and subject line Bug#814894: Removed package(s) from unstable has caused the Debian Bug report #721836, regarding mididings-doc: Wrong path for examples to be marked as done. This means that you claim that the problem has been dea

Bug#945658: marked as done (ladr: Python2 removal in sid/bullseye)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:46 + with message-id and subject line Bug#681042: Removed package(s) from unstable has caused the Debian Bug report #945658, regarding ladr: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#937044: marked as done (mididings: Python2 removal in sid/bullseye)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:22:14 + with message-id and subject line Bug#814894: Removed package(s) from unstable has caused the Debian Bug report #937044, regarding mididings: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#661331: marked as done (fofix: does not work with spaces in songpaths)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:24:20 + with message-id and subject line Bug#836421: Removed package(s) from unstable has caused the Debian Bug report #661331, regarding fofix: does not work with spaces in songpaths to be marked as done. This means that you claim that the problem has b

Bug#945650: marked as done (ccontrol: Python2 removal in sid/bullseye)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:21:16 + with message-id and subject line Bug#574013: Removed package(s) from unstable has caused the Debian Bug report #945650, regarding ccontrol: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#915631: marked as done (mididings: Problem calling Output with pan value)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:22:14 + with message-id and subject line Bug#814894: Removed package(s) from unstable has caused the Debian Bug report #915631, regarding mididings: Problem calling Output with pan value to be marked as done. This means that you claim that the problem ha

Bug#740833: marked as done (get-orig-source fails for non hg snapshot versions)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:23:48 + with message-id and subject line Bug#834337: Removed package(s) from unstable has caused the Debian Bug report #740833, regarding get-orig-source fails for non hg snapshot versions to be marked as done. This means that you claim that the problem

Bug#730034: marked as done (xnbd-server: exporting cd with odd number of sectors gives an ERR message)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:23:48 + with message-id and subject line Bug#834337: Removed package(s) from unstable has caused the Debian Bug report #730034, regarding xnbd-server: exporting cd with odd number of sectors gives an ERR message to be marked as done. This means that you

Bug#938853: marked as done (xnbd: Python2 removal in sid/bullseye)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:23:48 + with message-id and subject line Bug#834337: Removed package(s) from unstable has caused the Debian Bug report #938853, regarding xnbd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#936449: marked as done (dtrx: Python2 removal in sid/bullseye)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:22:42 + with message-id and subject line Bug#830618: Removed package(s) from unstable has caused the Debian Bug report #936449, regarding dtrx: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#661330: marked as done (fofix: Please integrate better with frestonfire-songs-*)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:24:20 + with message-id and subject line Bug#836421: Removed package(s) from unstable has caused the Debian Bug report #661330, regarding fofix: Please integrate better with frestonfire-songs-* to be marked as done. This means that you claim that the pro

Bug#945671: marked as done (fofix-dfsg: Python2 removal in sid/bullseye)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:24:20 + with message-id and subject line Bug#836421: Removed package(s) from unstable has caused the Debian Bug report #945671, regarding fofix-dfsg: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has bee

Bug#602986: marked as done (fofix crashes at startup with Illegal instruction output)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:24:20 + with message-id and subject line Bug#836421: Removed package(s) from unstable has caused the Debian Bug report #602986, regarding fofix crashes at startup with Illegal instruction output to be marked as done. This means that you claim that the pr

Bug#737877: marked as done (fofix: menu icon entry missing)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:24:20 + with message-id and subject line Bug#836421: Removed package(s) from unstable has caused the Debian Bug report #737877, regarding fofix: menu icon entry missing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#279101: marked as done (Kill -USR2 when going offline?)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #279101, regarding Kill -USR2 when going offline? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#912484: marked as done (fofix: Please migrate to python3-pygame)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:24:20 + with message-id and subject line Bug#836421: Removed package(s) from unstable has caused the Debian Bug report #912484, regarding fofix: Please migrate to python3-pygame to be marked as done. This means that you claim that the problem has been de

Bug#301228: marked as done (Polipo doesn't notice change of /etc/resolv.conf)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #301228, regarding Polipo doesn't notice change of /etc/resolv.conf to be marked as done. This means that you claim that the problem ha

Bug#511277: marked as done (Polipo does not obey domain search path)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #511277, regarding Polipo does not obey domain search path to be marked as done. This means that you claim that the problem has been de

Bug#524341: marked as done (Accept-Compression: deflate problems)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #524341, regarding Accept-Compression: deflate problems to be marked as done. This means that you claim that the problem has been dealt

Bug#292993: marked as done (polipo: default for dnsUseGethostbyname)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #292993, regarding polipo: default for dnsUseGethostbyname to be marked as done. This means that you claim that the problem has been de

Bug#250754: marked as done (Internal DNS server only queries first server)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #250754, regarding Internal DNS server only queries first server to be marked as done. This means that you claim that the problem has b

Bug#513062: marked as done (Spurious 417 Expectation failed (with midori & roundup))

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #513062, regarding Spurious 417 Expectation failed (with midori & roundup) to be marked as done. This means that you claim that the pro

Bug#654660: marked as done (polipo: needs to ignore comments and extended resolvconf entries)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #654660, regarding polipo: needs to ignore comments and extended resolvconf entries to be marked as done. This means that you claim tha

Bug#678470: marked as done (ext. redirector function is not squid-compatible)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #678470, regarding ext. redirector function is not squid-compatible to be marked as done. This means that you claim that the problem ha

Bug#890380: marked as done (polipo: ForbiddenFile not used for https requests)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #890380, regarding polipo: ForbiddenFile not used for https requests to be marked as done. This means that you claim that the problem h

Bug#639501: marked as done (/etc/polipo/options exists, is documented, but is unused)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #639501, regarding /etc/polipo/options exists, is documented, but is unused to be marked as done. This means that you claim that the pr

Bug#756572: marked as done (polipo: Polipo dies after a few days with `Too many open files')

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #756572, regarding polipo: Polipo dies after a few days with `Too many open files' to be marked as done. This means that you claim that

Bug#911287: marked as done (polipo: Dependency on dnsmasq)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #911287, regarding polipo: Dependency on dnsmasq to be marked as done. This means that you claim that the problem has been dealt with.

Bug#655852: marked as done (polipo: Polipo should log queries/fetches.)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #655852, regarding polipo: Polipo should log queries/fetches. to be marked as done. This means that you claim that the problem has been

Bug#775856: marked as done (polipo hangs on HTTP basic authentication)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #775856, regarding polipo hangs on HTTP basic authentication to be marked as done. This means that you claim that the problem has been

Bug#732942: marked as done (please include example proxy.pac to handle *.onion domains)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #732942, regarding please include example proxy.pac to handle *.onion domains to be marked as done. This means that you claim that the

Bug#945689: marked as done (polipo: Python2 removal in sid/bullseye)

2019-12-04 Thread Debian Bug Tracking System
Your message dated Thu, 05 Dec 2019 06:25:54 + with message-id and subject line Bug#900127: Removed package(s) from unstable has caused the Debian Bug report #945689, regarding polipo: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#814894: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: mididings | 0~20120419~ds0-6 | source, all mididings-doc | 0~20120419~ds0-6 | all python-mididings | 0~20120419~ds0-6+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s39

Bug#574013: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
Version: 1.0-2+rm Dear submitter, as the package ccontrol has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/574013 The ve

Bug#574013: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: ccontrol | 1.0-2 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; orphaned 9+ years ago; python2-on

Bug#681042: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: ladr | 0.0.200911a-2.1 | source ladr4-apps | 0.0.200911a-2.1+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libladr-dev | 0.0.200911a-2.1+b2 | amd64, arm64,

Bug#681042: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
Version: 0.0.200911a-2.1+rm Dear submitter, as the package ladr has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/681042

Bug#814894: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
Version: 0~20120419~ds0-6+rm Dear submitter, as the package mididings has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/81

Bug#830618: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: dtrx | 7.1-2 | source, all --- Reason --- RoQA; orphaned 3+ years ago; python2-only; dead upstream; low popcon --

Bug#830618: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
Version: 7.1-2+rm Dear submitter, as the package dtrx has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/830618 The versio

Bug#834337: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: xnbd |0.3.0-3 | source xnbd-client |0.3.0-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x xnbd-common |0.3.0-3 | amd64, arm64, armel, armhf, i386,

Bug#834337: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
Version: 0.3.0-3+rm Dear submitter, as the package xnbd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/834337 The vers

Bug#836421: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: fofix |3.121-7 | all fofix-dfsg |3.121-7 | source --- Reason --- RoQA; orphaned 3+ years ago; python2-only (even upstream); low popcon

Bug#836421: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
Version: 3.121-7+rm Dear submitter, as the package fofix-dfsg has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/836421 Th

Bug#900127: Removed package(s) from unstable

2019-12-04 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: polipo | 1.1.1-10 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; orphaned 1.5+ years ago; python2-