Processing of raptor2_2.0.16-2_source.changes

[Debian FTP Masters]

raptor2_2.0.16-2_source.changes uploaded successfully to localhost
along with the files:
  raptor2_2.0.16-2.dsc
  raptor2_2.0.16-2.debian.tar.xz
  raptor2_2.0.16-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

raptor2_2.0.16-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Jul 2023 08:56:32 +0200
Source: raptor2
Architecture: source
Version: 2.0.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard F. Aasen 
Changes:
 raptor2 (2.0.16-2) unstable; urgency=medium
 .
   * QA upload.
   * Move from experimental to unstable.
   * Add libcurl-ssl-dev as alternative to libcurl4-gnutls-dev. LP: #1899809
   * Add libicu-dev as BD.
   * Enable all tests but do not run them in parallel.
Checksums-Sha1:
 47795bbf367ab1671b537020fc7aab06c73a37e5 2157 raptor2_2.0.16-2.dsc
 f84fcbcea66ce7a10ded99e128e14349a673d0b5 11088 raptor2_2.0.16-2.debian.tar.xz
 2dceab5980c9f3ecb57afe3e35a1e8bb14ef5351 7813 raptor2_2.0.16-2_source.buildinfo
Checksums-Sha256:
 5f931688aa81bbe5d6e36a3309a2c3891a87847d5bffc3ae9179ff1749b4b4c6 2157 
raptor2_2.0.16-2.dsc
 e981265affaf1371584b45c32679593314da9edea00375438e4f02b2d0f0 11088 
raptor2_2.0.16-2.debian.tar.xz
 6c3cb6935ed8c6680d265a7f0add42b8d713292f1651bd8b356dc760670ae09b 7813 
raptor2_2.0.16-2_source.buildinfo
Files:
 f4caa213c94277694f3820474da7b4ef 2157 devel optional raptor2_2.0.16-2.dsc
 4ca555f9d484de5d736d085da0c5729b 11088 devel optional 
raptor2_2.0.16-2.debian.tar.xz
 825736a438eaed758304e0d224b456bc 7813 devel optional 
raptor2_2.0.16-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmSifQAACgkQweDZLphv
fH484RAAm2t+1BcC6SQ+C3aWI8THnyjzuN01ceTPzf/QME+b52//jgk55g45c40V
F3ZX+43Vj1mgWKtpqWyAM7bzXn8JN6Y3tdyesmXrjputfAW9WDB+TsvL+i0SKXFV
cFJts1BArtd4O47ZzKUigtu5W5Li8mc83/XkLRB1UH9FShjMbpxounaUFTlIbjZj
igDiJDEI+Eh+Xgw79wgbt/Dj5LlRfbI3mezR1Gbpc0cncmTtkpIVJepWRP7l1gFv
PvcrDe7SxmBafwxoaPdMYL3xivaiKopcj/RvpEnx2wvE0WRYABtUDW8q1pRFLcxU
qJEFrdn7zHr4hbU3t1Ya0V7MzJguJDGqdCcWvWK0udgNuEj0ox4HSTEYvslDbeAK
ZizmV1INRIlk9Sz8u0nrS09YjV8J2k1BWNjm4bveKzp6yYoR+87ZzOvObjbiAtnN
Pj5dSak5e6sJxDC0yFBKn/Xbg1OMqPHeLsUUle/a2Cu+UkNwEZQYnhEpYGXBgNDr
oqybagQRsELoPoUjabtT00b0xGHF1UO5yIz0oDOPbZFDr7sy9H2IPgHLqz5yA6Va
gucvgEXgOSs564gzu+V8o3SOdPvCohseL0hb8DE5ycfTdVoGBcvSAJpaz7whdquv
exouwsu69XC/aFtGZ2cwFl4YOVLOr6FejrAsVCCMOiVZaM8WtqI=
=Ai2E
-END PGP SIGNATURE-

Processing of sispmctl_4.10-1~exp1_source.changes

[Debian FTP Masters]

sispmctl_4.10-1~exp1_source.changes uploaded successfully to localhost
along with the files:
  sispmctl_4.10-1~exp1.dsc
  sispmctl_4.10.orig.tar.gz
  sispmctl_4.10-1~exp1.debian.tar.xz
  sispmctl_4.10-1~exp1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

sispmctl_4.10-1~exp1_source.changes ACCEPTED into experimental

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Jul 2023 12:38:02 +0200
Source: sispmctl
Architecture: source
Version: 4.10-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Hilko Bengen 
Changes:
 sispmctl (4.10-1~exp1) experimental; urgency=medium
 .
   * QA upload.
   * New upstream version 4.10
   * Update watch file
   * Drop patches
   * Modernize packaging: Debhelper, compat level, Standards-Version
   * Update debian/copyright
   * Add udev rule and matching system user
   * Add git-buildpackage configu
   * Add Vcs-* headers
Checksums-Sha1:
 37e835a996b82c50c87c7a57ad96fd89b1a3700f 1887 sispmctl_4.10-1~exp1.dsc
 71e785d261101401aa5a875ae5d13fb1084216e7 406259 sispmctl_4.10.orig.tar.gz
 f35a73e3dff1cbd777f5aef275d6b3e65a660977 2740 
sispmctl_4.10-1~exp1.debian.tar.xz
 c13c867b3cf897bfb309f8e1441f0118ee9a53f0 6466 
sispmctl_4.10-1~exp1_source.buildinfo
Checksums-Sha256:
 83e6325ccf00975eeb20c5b408232981d206252d74d51afcb48c03a223162fc5 1887 
sispmctl_4.10-1~exp1.dsc
 e648b6e87584330a0a693e7b521ebbc863608d6c97ef929063542b459d16bc6f 406259 
sispmctl_4.10.orig.tar.gz
 c227daaae051df6dd020b9b603647e4eea0df3fa3364680453b1790cf538c94d 2740 
sispmctl_4.10-1~exp1.debian.tar.xz
 70ca7b326ebbbe84c19950b391cdc04d21bd7718781798da808d7ba373263c1e 6466 
sispmctl_4.10-1~exp1_source.buildinfo
Files:
 520f8fc6ea07be90e5cca3080fe8332a 1887 admin optional sispmctl_4.10-1~exp1.dsc
 4ff3180d1ff861c404deeef9086d9b37 406259 admin optional 
sispmctl_4.10.orig.tar.gz
 bc9767586782e18e9d846a1c2bd3ac98 2740 admin optional 
sispmctl_4.10-1~exp1.debian.tar.xz
 e966969db86ac362636a533b7c24855a 6466 admin optional 
sispmctl_4.10-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmSirPQACgkQdbcQY1wh
On6t3A/9FbB3UsLhAjBJ8Muat3GgOFeXskNAox0arc1/Z8I3UHdiiNxtbAZcBzBb
1Dx7o00oa7vgc+eP8v9pljDqsWVD2VoKguQltIeoStLA/mzrUMMpix4OCdFhaFKL
kCbATl3ZUghRFI3xO82JHzXX/rNDAdqJMpSgDf86YJXt2RCd2CxS9+p1iTpRRYO6
uF415DiH1SAx/vsRks8s9OeCQiFwrAn5NGm1etjaZUZNmWJDUWOl7jGgq7nrfTAS
xNCWnlO7oat3C4w6xdLV0kC10EkfxssF+5WWTWQ0Z0uW6yAOhD5BWcwTXSU1yaH8
m6cmejv9q9bAahxNHBhYoHoEaV/f7WnaF+qgmnWwXepTw2URJAE9xVHjHu2arSTF
nz0cO1t0ZI3JvjU7YO2ZaBbVM2UgXlYlHtkJpIR1EuO1jW2kHyIyVPv8PMRwS2x1
gfMClV04yqknhMCGOkMLd4DuQ6AicI9h5WnghLWCdknTypDJ3WNlImwBhMZqAl7a
8hwGDlZyi3ftV/mHfREcDVdUh8UhbTfyWtdcuArjyM+b2NOyiaWv+4RSOIzAxhXx
bUFjbsD36q2XFho4X2UESE5ze393IP2QM3jkgPfE+4eFcq7A9oIttxKdQeegZpij
HFHdT9am5wI2zCNbO2EhYr5CpAHyrf2fC2EJXmV0gV+zz/D121c=
=1K0y
-END PGP SIGNATURE-

Bug#1039330: marked as done (proxsmtp: ships sysv-init script without systemd unit)

[Debian Bug Tracking System]

Your message dated Mon, 3 Jul 2023 19:56:41 +0200
with message-id <20230703175641.gg7...@inutil.org>
and subject line Already fixed
has caused the Debian Bug report #1039330,
regarding proxsmtp: ships sysv-init script without systemd unit
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.)


-- 
1039330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proxsmtp
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service

Dear Maintainer(s),

proxsmtp has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a transitional
sysv-init-to-unit generator was shipped by systemd. This is in the
process of being deprecated and will be removed by the time Trixie
ships, so the remaining packages that ship init scripts without
systemd units will stop working.

There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html

You can find the Lintian warning here:

https://lintian.debian.org/sources/proxsmtp

In case this is a false positive, please add a Lintian override to
silence it and then close this bug.

Thanks! 
--- End Message ---
--- Begin Message ---
Version: 1.10-4--- End Message ---

Bug#1039326: marked as done (powerman: ships sysv-init script without systemd unit)

[Debian Bug Tracking System]

Your message dated Mon, 3 Jul 2023 20:03:48 +0200
with message-id <20230703180348.gj7...@inutil.org>
and subject line Already fixed
has caused the Debian Bug report #1039326,
regarding powerman: ships sysv-init script without systemd unit
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.)


-- 
1039326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: powerman
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service

Dear Maintainer(s),

powerman has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a transitional
sysv-init-to-unit generator was shipped by systemd. This is in the
process of being deprecated and will be removed by the time Trixie
ships, so the remaining packages that ship init scripts without
systemd units will stop working.

There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html

You can find the Lintian warning here:

https://lintian.debian.org/sources/powerman

In case this is a false positive, please add a Lintian override to
silence it and then close this bug.

Thanks! 
--- End Message ---
--- Begin Message ---
Version: 2.3.27-3--- End Message ---

Bug#1040237: RM: masqmail -- RoQA; dead upstream, RC-buggy

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: masqm...@packages.debian.org
Control: affects -1 + src:masqmail

Please remove masqmail. It's dead upstream, orphaned without an adopter
since 2015 and RC-buggy (dropped from testing since 2017).

Cheers,
Moritz

Bug#1040236: RM: mason -- RoQA; dead upstream, alternatives exist

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: ma...@packages.debian.org
Control: affects -1 + src:mason

Please remove mason, it's orphaned without an adopter since 2018, upstream
is dead upstream (vanished off the internet) and it only supports legacy
tooling (iptables, ipchains, ipwfadm)

Bug#1040239: RM: apf-firewall -- RoQA; obsolete, unmaintained

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: apf-firew...@packages.debian.org
Control: affects -1 + src:apf-firewall

Please remove apf-firewall. Removal was already hinted at in the original
orphan bug from 2016 and at this point the version in a the archive is
a release from 2009.

Cheers,
Moritz

Bug#1040238: RM: gsm0710muxd -- RoQA; obsolete, dead upstream, uses legacy libs

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: gsm0710m...@packages.debian.org
Control: affects -1 + src:gsm0710muxd

Please remove gsm0710muxd. It's been orphaned since nine years and removal was
already suggested in the original O:bug (#761519), it's dead upstream and 
depends
on th deprecated dbus-glib (#955900)

Cheers,
Moritz

Processing of srecord_1.64-4_source.changes

[Debian FTP Masters]

srecord_1.64-4_source.changes uploaded successfully to localhost
along with the files:
  srecord_1.64-4.dsc
  srecord_1.64-4.debian.tar.xz
  srecord_1.64-4_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#825330: New version uploaded to experimental

[Hilko Bengen]

control: fixed -1 4.1.0-1~exp1

srecord_1.64-4_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Jun 2023 18:48:23 -0300
Source: srecord
Architecture: source
Version: 1.64-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Aquila Macedo Costa 
Changes:
 srecord (1.64-4) unstable; urgency=medium
 .
   * QA upload.
   * debian/control: 'debhelper-compat' in Build-Depends is bumped to level 13.
   * debian/control: Bumped Standards-Version to 4.6.2.
   * debian/rules: Added compilation option to enable "bindnow" in linker.
   * debian/patches: Created 01-fix-typos-in-manpages.patch
 to fix typos in the manpages.
Checksums-Sha1:
 57c3544a616c9a0be13b9706776643afd2632b52 1988 srecord_1.64-4.dsc
 7b54934e91a70e147e626cb8b6b1f529e51670fd 7676 srecord_1.64-4.debian.tar.xz
 939b9f90bbff47e33c21b8f6ed2d09155052bb04 8182 srecord_1.64-4_source.buildinfo
Checksums-Sha256:
 8b28bbf3e18130eb3a4f426171d341d9600d3a43a0ce0d2aa7481596c7ac9a99 1988 
srecord_1.64-4.dsc
 913c026135f48ee589f8fc6de5f2bae9ba3802676b643acc4252cc6c57f7c627 7676 
srecord_1.64-4.debian.tar.xz
 88ef2b0e49ddd5dd905b7e3010d23781306dbb98190882d02cf21d3f755349a4 8182 
srecord_1.64-4_source.buildinfo
Files:
 3e21c3f5fe48095616460b7128152305 1988 utils optional srecord_1.64-4.dsc
 9e06391bbe43365be6f41356cea37757 7676 utils optional 
srecord_1.64-4.debian.tar.xz
 7b83f12c5b5004628cf3d1699f6aa7e6 8182 utils optional 
srecord_1.64-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmSgIbgACgkQ+COicpiD
yXyJTBAAm5S2r12aHvXpXZU4P623aLeiBfXCL5VyLKnNSEImN8RoCiZsajOAZVGP
zynf5jzlxOa0Krz7RPJXC9/7vY2uSr5D9x5Vy4Q1DB8dcxc5z+sb8FZuAblEhSY5
1R4UT4t1riWHDh2Y95d6ZPnjmGkYNIq85Y7pD56Nf2AX8WYuBi9vjBxZMDTHhy4y
Rf6Y8fuaBSizLCT1kv7YgUu6/Qea5RO5PB7QWbJn8/PP1Fmc1nwSwSUo8lEeR6Jv
pVL/ETvYTsJE1Rlhmxm1Vas0PNODobT7HWoY4fFQSyvmhrcrTB0pGxpIYPxuRSZz
HpHrenDjUxXEGt6wd5XPcUt6XvdVOlyZUEZ3EEMnOTrY3QmyBBgVW2MdwM4bjOdl
nvxaKNJ42DUmgVdCtyA6vYDZVYhKv7IIbJOSm/I5kOZHKj03xBqKSMC/fw49mivs
kYsELG62qMdc+m1z/bjTLbFi/vJcuPZtisH/uEuKbGX5Tzu+oXqp8/HOBABgGJVd
9SgWr64jrHn1mdhXmT/rgca19LLg+FYwZ0sE6qpc+0k0XPrY08baNWQmGLGxejAZ
7H5TTKKE0DNcT5nb6ZnswV4b0q7ECGy8yQ/hDmIF3ow/1BHJzwCUCK129hmjP3ND
o/wiY7lNyG+N4iELbw8u0qWJw3+iP4WvRZCvo32jjX9IuOChSoA=
=fNje
-END PGP SIGNATURE-

Bug#825330: New version uploaded to experimental

[Hilko Bengen]

control: fixed -1 4.10-1~exp1

Processed: New version uploaded to experimental

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.1.0-1~exp1
Bug #825330 [sispmctl] sispmctl: New upstream version is available
There is no source info for the package 'sispmctl' at version '4.1.0-1~exp1' 
with architecture ''
Unable to make a source version for version '4.1.0-1~exp1'
Marked as fixed in versions 4.1.0-1~exp1.

-- 
825330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: New version uploaded to experimental

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.10-1~exp1
Bug #825330 [sispmctl] sispmctl: New upstream version is available
Marked as fixed in versions sispmctl/4.10-1~exp1.

-- 
825330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#804265: new version contains udev rules

[Hilko Bengen]

control: fixed -1 4.10-1~exp1

Processed: new version contains udev rules

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.10-1~exp1
Bug #804265 [sispmctl] sispmctl: Allow sispmctl to be run as non-priviledged 
user
Marked as fixed in versions sispmctl/4.10-1~exp1.

-- 
804265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

ghostscript_10.0.0~dfsg-11+deb12u1_source.changes ACCEPTED into proposed-updates->stable-new

[Debian FTP Masters]

Thank you for your contribution to Debian.

Mapping stable-security to proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Jul 2023 10:50:27 +0200
Source: ghostscript
Architecture: source
Version: 10.0.0~dfsg-11+deb12u1
Distribution: bookworm-security
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Salvatore Bonaccorso 
Changes:
 ghostscript (10.0.0~dfsg-11+deb12u1) bookworm-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Don't "reduce" %pipe% file names for permission validation
 (CVE-2023-36664)
   * Revisit fix for upstream bug 706761 (CVE-2023-36664)
Checksums-Sha1:
 e5049b6c95850be01c086ae0a434a5fb7e625a32 3019 
ghostscript_10.0.0~dfsg-11+deb12u1.dsc
 7aa37250cc830f3c9914b083ef468cfe30e6a00f 26688456 
ghostscript_10.0.0~dfsg.orig.tar.xz
 9ec57c8615d07870946686c25fe3acf79fc54747 86840 
ghostscript_10.0.0~dfsg-11+deb12u1.debian.tar.xz
 5494833599b1698e614b07cd7ff2a78342c9e97c 7241 
ghostscript_10.0.0~dfsg-11+deb12u1_source.buildinfo
Checksums-Sha256:
 fb2553f22cb746028b7b695fca5fd165df945cbc71fccbd9550975fbf83b9d5f 3019 
ghostscript_10.0.0~dfsg-11+deb12u1.dsc
 67a288151fd88f0d44e165429c48cc85d69b3e4d3765c95e60839a094bfb8df3 26688456 
ghostscript_10.0.0~dfsg.orig.tar.xz
 250b67a674434027fe32c08895e24b6fe0a281d3794e579a862efb6645b3824a 86840 
ghostscript_10.0.0~dfsg-11+deb12u1.debian.tar.xz
 8e21435af519f3a62ac6aaa1452c9e83187fec6ce5f523a6769ce8c5832986d5 7241 
ghostscript_10.0.0~dfsg-11+deb12u1_source.buildinfo
Files:
 cb59b0e8adc7ca0ee266caf8eb19bb48 3019 text optional 
ghostscript_10.0.0~dfsg-11+deb12u1.dsc
 ef38488b0a39c7064a027f4a4c9b9151 26688456 text optional 
ghostscript_10.0.0~dfsg.orig.tar.xz
 a4bf275a6bf53dc58af257ad30e9710a 86840 text optional 
ghostscript_10.0.0~dfsg-11+deb12u1.debian.tar.xz
 9bd155911b3b94f5b8930441ca4cb22e 7241 text optional 
ghostscript_10.0.0~dfsg-11+deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmShPApfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E+XoP/juusb2iMweZRx8qf3iM0N7//kuJwPMv
qKF41GexGkwK/bOBSLC6QxKLO5jwrFoa6J104jfyOyFBIH+zAjrl9kZYIhze1Tjh
Uus+q+SgjNAPW012hnau1A2S73iSxGF6XviwerpR7u3tHe0pcalr4x0ZUEp1FSIB
JowJm4Qjb8DGgUot0f/dx0RoDB/hNIXLQw6QdyjaFa6zduZ3R7tnpISKA+7/cklo
+ShV1Tqb1kFoxerBqFLQwlZrizrbtvQa0sdSmWmh5LQYyaRuPI/5ZK5T76mQvQhF
kNipAvZrYMDlK4oOo7rKW0cevd/DKl9FbEGcQ/hKzMUAKPQRk17VVjvNjq+vtRex
1PZ56lrP/mojUkKFRclih2cFjm1mVZzuh1aPt5bKT+OB0tLTqQYg6X/sgt+5JiAK
KILT7dXj6qD6HMXA1y4tEs80wrxeBNWhZkaDaGWkurwGbzDBb7IE20RQzkefGQBI
gIhYQsj4sFc/BaAYsF5pLPgZ+CxvWe4HHxFQoJWTXo/fwxeptMkZzgm7+C3oW/h6
xyMvig06OWkgFyL6FU2I3Rl1yv7XwURg8AypZU1PYG0ylB7mXer9hlBgAJ5eaIC2
mqFLpwGcM/KOFBZUxMY+5PzvGnxwENYWljAnvbmQeoFrKZLgHeAey2jnWbxBFz8a
U8ALB4XnL2Z9
=vKWr
-END PGP SIGNATURE-

Bug#1040258: gthumb FTBFS with libraw 0.21.1

[Adrian Bunk]

Source: gthumb
Version: 3:3.12.2-3
Severity: serious
Tags: ftbfs trixie sid

https://buildd.debian.org/status/logs.php?pkg=gthumb&ver=3%3A3.12.2-3%2Bb2

...
FAILED: extensions/raw_files/libraw_files.so.p/main.c.o 
cc -Iextensions/raw_files/libraw_files.so.p -Iextensions/raw_files 
-I../extensions/raw_files -I. -I.. -Igthumb -I../gthumb -I/usr/include/glib-2.0 
-I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gtk-3.0 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/aarch64-linux-gnu -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/aarch64-linux-gnu/dbus-1.0/include 
-I/usr/include/gsettings-desktop-schemas -I/usr/include/libraw 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_54 -Wall 
-Wno-deprecated-declarations -MD -MQ 
extensions/raw_files/libraw_files.so.p/main.c.o -MF 
extensions/raw_files/libraw_files.so.p/main.c.o.d -o 
extensions/raw_files/libraw_files.so.p/main.c.o -c 
../extensions/raw_files/main.c
../extensions/raw_files/main.c: In function 
‘_cairo_image_surface_create_from_raw’:
../extensions/raw_files/main.c:216:33: error: 
‘LIBRAW_OPIONS_NO_MEMERR_CALLBACK’ undeclared (first use in this function); did 
you mean ‘LIBRAW_OPIONS_NO_DATAERR_CALLBACK’?
  216 | raw_data = libraw_init (LIBRAW_OPIONS_NO_MEMERR_CALLBACK | 
LIBRAW_OPIONS_NO_DATAERR_CALLBACK);
  | ^~~~
  | LIBRAW_OPIONS_NO_DATAERR_CALLBACK
../extensions/raw_files/main.c:216:33: note: each undeclared identifier is 
reported only once for each function it appears in
[557/720] cc -Iextensions/raw_files/libraw_files.so.p -Iextensions/raw_files 
-I../extensions/raw_files -I. -I.. -Igthumb -I../gthumb -I/usr/include/glib-2.0 
-I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gtk-3.0 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/aarch64-linux-gnu -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/aarch64-linux-gnu/dbus-1.0/include 
-I/usr/include/gsettings-desktop-schemas -I/usr/include/libraw 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_54 -Wall 
-Wno-deprecated-declarations -MD -MQ 
extensions/raw_files/libraw_files.so.p/gth-metadata-provider-raw.c.o -MF 
extensions/raw_files/libraw_files.so.p/gth-metadata-provider-raw.c.o.d -o 
extensions/raw_files/libraw_files.so.p/gth-metadata-provider-raw.c.o -c 
../extensions/raw_files/gth-metadata-provider-raw.c
FAILED: extensions/raw_files/libraw_files.so.p/gth-metadata-provider-raw.c.o 
cc -Iextensions/raw_files/libraw_files.so.p -Iextensions/raw_files 
-I../extensions/raw_files -I. -I.. -Igthumb -I../gthumb -I/usr/include/glib-2.0 
-I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gtk-3.0 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/aarch64-linux-gnu -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/aarch64-linux-gnu/dbus-1.0/include 
-I/usr/include/gsettings-desktop-schemas -I/usr/include/libraw 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_54 -Wall 
-Wno-deprecated-declarations -MD -MQ 
extensions/raw_files/libraw_files.so.p/gth-metadata-provider-raw.c.o -MF 
extensions/raw_files/libraw_files.so.p/gth-metadata-provider-raw.c.o.d -o 
extensions/raw_files/libraw_files.so.p/gth-metadata-provider-raw.c.o -c 
../extensions/raw_files/gth-metadata-provider-raw.c
../extensions/raw_files/gth-metadata-provider-raw.c: In function 
‘gth_metadata_provider_raw_read’:
../extensions/raw_files/gth-metadata-provider-raw.c:65:33: error: 
‘LIBRAW_OPIONS_NO_MEM

Processed: extras/ is gone as of 4.10

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wontfix
Bug #829104 [sispmctl] sispmctl: Please package gemplug
Added tag(s) wontfix.

-- 
829104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#829104: extras/ is gone as of 4.10

[Hilko Bengen]

control: tag -1 wontfix

As of version 4.10 (which I uploadeed to experimental today) the whole
extras/ subdirectory which contains gemplug is gone.

Cheers,
-Hilko

Bug#1037225: marked as done (mason: [INTL:tr] turkish translation of debconf messages)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id 
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #1037225,
regarding mason: [INTL:tr] turkish translation of debconf messages
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.)


-- 
1037225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: mason
Version: N/A
Severity: wishlist
Tags: l10n patch

Hello,

Find attached the updated Turkish translation of the mason debconf messages.
It has been submitted for review to the debian-l10n-turkish mailing list.

Regards,
Atila KOÇ
--- YASAL UYARI ---

# Turkish debconf translation of mason
# This file is distributed under the same license as the mason package.
# Mert Dirik , 2008.
# Atila KOÇ , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: mason\n"
"Report-Msgid-Bugs-To: packa...@qa.debian.org\n"
"POT-Creation-Date: 2010-06-29 22:07+0200\n"
"PO-Revision-Date: 2023-04-17 21:30+0300\n"
"Last-Translator: Atila KOÇ \n"
"Language-Team: Debian L10n Turkish \n"
"Language: tr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Poedit 2.4.2\n"

#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../templates:1001 ../templates:2001
msgid "accept"
msgstr "kabul et"

#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../templates:1001 ../templates:2001
msgid "reject"
msgstr "geri çevir"

#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../templates:1001 ../templates:2001
msgid "deny"
msgstr "görmezden gel"

#. Type: select
#. Description
#: ../templates:1002
msgid "Default action for new firewall rules:"
msgstr "Yeni güvenlik duvarı kuralları için öntanımlı eylem:"

#. Type: select
#. Description
#: ../templates:1002
msgid ""
"The new rule default action specifies how Mason will handle unknown packets, "
"when the firewall is in learning mode."
msgstr ""
"Yeni kural öntanımlı eylemi, güvenlik duvarı öğrenme kipindeyken, Mason'un "
"bilinmeyen paketleri nasıl ele alacağını belirler."

#. Type: select
#. Description
#: ../templates:1002
msgid ""
"The \"accept\" action will allow the packet through.  \"Reject\" will stop "
"the packet with a rejection reply, while \"deny\" will drop the packet "
"silently."
msgstr ""
"\"kabul et\" paketin geçişine izin verir. \"geri çevir\" bir ret yanıtı ile "
"paketi durdurur, \"görmezden gel\" ise paketi sessizce düşürür."

#. Type: select
#. Description
#: ../templates:2002
msgid "Default action for rulesets:"
msgstr "Kural setleri için öntanımlı eylem:"

#. Type: select
#. Description
#: ../templates:2002
msgid ""
"The default action specifies how Mason will handle unknown packets, when the "
"firewall is not in learning mode."
msgstr ""
"Öntanımlı eylem, güvenlik duvarı öğrenme kipinde değilken, Mason'un "
"bilinmeyen paketleri nasıl ele alacağını belirler."

#. Type: select
#. Description
#: ../templates:2002
msgid ""
"Again, \"accept\" allows the packet through, \"reject\" drops the packet "
"with a reply, and \"deny\" silently drops the packet."
msgstr ""
"Yeniden, \"kabul et\" paketin geçişine izin verir. \"geri çevir\" bir yanıt "
"ile paketi düşürür ve \"görmezden gel\" paketi sessizce düşürür."

#~ msgid "accept, reject, deny"
#~ msgstr "kabul et, reddet, inkâr et"

#~ msgid ""
#~ "When Mason detects a new kind of traffic and creates a rule for it, what "
#~ "action should the rule take?"
#~ msgstr ""
#~ "Mason öncekilerden farklı türde bir trafik tespit edip bu yeni trafik "
#~ "için bir kural oluşturduğunda, yeni oluşturulacak bu kuralın tanımlaması "
#~ "gereken eylem ne olmalıdır?"

#~ msgid ""
#~ "What should the default action be when a packet does not match any of the "
#~ "rules set up by Mason?"
#~ msgstr ""
#~ "Bir paket Mason tarafından oluşturulmuş hiç bir kuralla eşleşmiyorsa bu "
#~ "pakete uygulanacak öntanımlı eylem ne olmalı?"
--- End Message ---
--- Begin Message ---
Version: 1.0.0-13+rm

Dear submitter,

as the package mason 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/1040236

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next 

Bug#169220: marked as done (mason: Broken signal handling)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id 
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #169220,
regarding mason: Broken signal handling
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.)


-- 
169220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=169220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mason
Severity: normal
Version: 1.0.0-0.1

If you press ^Q while editing a rulesfile from within mason-gui-test,
only the editor (e.g. emacs) gets supspended and you won't arrive at
shell level. The only help in this situation is to open another shell
and to send a SIGCONT to the suspended editor.

Also pressing ^C should either be ignored or the firewall rules should
be reset to the last sane settings and all processes should be killed.

Christoph


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
--- End Message ---
--- Begin Message ---
Version: 1.0.0-13+rm

Dear submitter,

as the package mason 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/1040236

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#216226: marked as done (masqmail: big mails over slow links get sent multiple times)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #216226,
regarding masqmail: big mails over slow links get sent multiple times
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.)


-- 
216226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.2.19-1.aylee
Severity: normal

Yesterday i tried to send a 32MB Mail over my 128kBit/s-connection. I got
lots of 'timeout' and 'too many connections from this IP address' error
messages from the receiving SMTP host.

Further investigation revealed, that the masqmail-process had forked off
14 sending processes for the one mail.

The daemon was running with the (default?) setting -q10m.
Sending 32MB over a 16kB/s connection needs at least 30 minutes, in my
case there were other streams, leaving ca. 5kB/s, that would be 90
minutes.

So i suspect, every 10 minutes the daemon saw: there are still unsent
mails (which in reality were still in flight) and started a new sending
process, which caused even more congestation on my uplink. It just
should have waited for termination or timeout of the running sending
process(es).

Setting the queuing parameter to -q10h for this one mail helped.

PS: This could be part of the same problem: /etc/init.d/masqmail stop did not
stop the sending processes.

-- System Information
Debian Release: 3.0-bunk-1
Architecture: i386
Kernel: Linux strcmp.libc 2.4.22.strcmp.4 #2 Tue Oct 7 21:43:42 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages masqmail depends on:
ii  debconf   1.2.34 Debian configuration management sy
ii  libc6 2.3.2-7GNU C Library: Shared libraries an
ii  libglib1.21.2.10-6   The GLib library of C routines
ii  libident  0.22-2 simple RFC1413 client library - ru
ii  liblockfile1  1.03   NFS-safe locking library, includes
ii  netbase   4.07   Basic TCP/IP networking system


--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#178791: marked as done (mason: Masquerading with iptables fails)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id 
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #178791,
regarding mason: Masquerading with iptables fails
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.)


-- 
178791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=178791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mason
Version: 1.0.0-0.1
Severity: normal

When changing a forwarding rule from ACCEPT to MASQ with mason-decide,
the following rule will be generated:

/sbin/iptables -A POSTROUTING -t nat  -i isdn6 -o eth0 -p tcp
-s 10.254.1.0/24 --sport 1024:65535 -d 10.7.96.24/32 --dport ldap -j
MASQUERADE

correct would be to not change the forwarding rule and add a nat rule
without the -i flag:

/sbin/iptables -A FORWARD  -i isdn6 -o eth0 -p tcp   -s
10.254.1.0/24 --sport 1024:65535 -d 10.7.96.60/32 --dport ldap -j ACCEPT

/sbin/iptables -A POSTROUTING -t nat -o eth0 -p tcp   -s
10.254.1.0/24 --sport 1024:65535 -d 10.7.96.60/32 --dport ldap -j MASQUERADE

Christoph


pgp5oWrFagAZd.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.0.0-13+rm

Dear submitter,

as the package mason 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/1040236

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#517837: marked as done (Stopping mason does not flush nat table)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id 
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #517837,
regarding Stopping mason does not flush nat table
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.)


-- 
517837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mason
Version: 1.0.0-11~bpo40+1
Severity: important


calling /etc/init.d/mason stop does only flush the rules in the
default table but not in the nat table.


-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (900, 'oldstable'), (90, 'stable'), (70, 'testing'), (50, 
'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24-etchnhalf.1-686-bigmem
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mason depends on:
ii  bash 3.1dfsg-8   The GNU Bourne Again SHell
ii  debconf [debconf-2.0]1.5.11etch2 Debian configuration management sy

mason recommends no packages.

-- debconf information:
* mason/newrulepolicy: accept
* mason/defaultpolicy: deny


--- End Message ---
--- Begin Message ---
Version: 1.0.0-13+rm

Dear submitter,

as the package mason 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/1040236

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#241796: marked as done (mail with large amount of receipient addresses causes excessive memory consumption)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #241796,
regarding mail with large amount of receipient addresses causes excessive  
memory consumption
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.)


-- 
241796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.2.20-1
Severity: normal

When recieving email (through pop3) with a large amount of addresses* in
the To field, masqmail consumes a very large amount of memory, eventually
resulting in the fetch process being killed, and this repeats until I tell
masqmail to stop fetching mail.

I can probably resolve this in my installation through ulimit (and use of
other mail clients to delete troublesome mail), but this might affect
other users too.

* Some of the students at my school seem to think it's a good idea to send
email to everybody in the mail server's address book, all at once, without
using BCC.  The address book contains approximately 5000 names.  The
administrators are not willing to implement restrictions on the number of
reciepients in an email. I can forward an example email, if it'll help.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.4
Locale: LANG=C, LC_CTYPE=C

Versions of packages masqmail depends on:
ii  debconf 1.4.19   Debian configuration
management sy
ii  libc6   2.3.2.ds1-11 GNU C Library: Shared
libraries an
ii  libglib1.2  1.2.10-9 The GLib library of C routines
ii  libident0.22-2.2 simple RFC1413 client library
- ru
ii  liblockfile11.05 NFS-safe locking library,
includes
ii  netbase 4.16 Basic TCP/IP networking system

-- debconf information:
* masqmail/ipup_fetch: false
  masqmail/mda: /usr/bin/procmail -Y -d ${rcpt_local}
  masqmail/online_file: /tmp/connect_route
* masqmail/mbox_default: maildir
  masqmail/init_smtp_daemon: true
* masqmail/ipup_runqueue: false
* masqmail/online_detect: file
* masqmail/local_hosts: localhost;galoshes
* masqmail/you_are_not_finished:
  masqmail/note_pcmcia_scripts:
* masqmail/note_moved_tpl:
  masqmail/queue_daemon_ival: -q10m
* masqmail/host_name: galoshes
  masqmail/alias_local_caseless: false
* masqmail/manage_config_with_debconf: true
  masqmail/use_syslog: false
* masqmail/listen_addresses:
* masqmail/init_fetch_daemon: true
  masqmail/move_existing_nondebconf_config: true
* masqmail/ifup_ifaces: all
  masqmail/online_pipe:
  masqmail/init_queue_daemon: true
  masqmail/fetch_daemon_ival: -go5m
* masqmail/local_nets: *



--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#245882: marked as done (masqmail: spool files not completely removed upon delivery)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #245882,
regarding masqmail: spool files not completely removed upon delivery
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.)


-- 
245882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.2.20-1
Severity: normal

My boss uses masqmail on a machine that often has bad connectivity - the
connections used to send mail often break.  The result is that the mail
is sent, the -D files are removed, but the -H files remain.  This means
that when he runs "mailq" he's informed that there are a bunch of
messages still waiting to be delivered.  Running "sendmail -qo" yields
errors because the -H files are not there though.

Please handle this better.  I suggest removing -H files for which no -D
file is available.

Thank you.

--kyler

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5-mh3
Locale: LANG=C, LC_CTYPE=C

Versions of packages masqmail depends on:
ii  debconf 1.4.22   Debian configuration management sy
ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libglib1.2  1.2.10-9 The GLib library of C routines
ii  libident0.22-2.2 simple RFC1413 client library - ru
ii  liblockfile11.05 NFS-safe locking library, includes
ii  netbase 4.16 Basic TCP/IP networking system

-- debconf information excluded


--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#678361: marked as done (stopped expanding aliases)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #678361,
regarding stopped expanding aliases
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.)


-- 
678361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.3.4-1
Severity: important

Hi,

After upgrading to the new version masqmail stopped expanding aliases.
Mail which usually landed in my mailbox ended up in root's.

Upgrade should not break the current setup without any warning.

Regards,

Raf

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (999, 'unstable'), (500, 'testing-proposed-updates'), (500, 
'stable-updates'), (500, 'testing'), (1, 'experimental'), (1, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 3.2.0-2-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages masqmail depends on:
ii  dpkg  1.16.4.3
ii  libc6 2.13-33
ii  libglib2.0-0  2.32.3-1
ii  liblockfile1  1.09-4
ii  netbase   5.0

masqmail recommends no packages.

Versions of packages masqmail suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.2006cvs-1
ii  emacs23 [mail-reader]23.4+1-3
ii  evolution [mail-reader]  3.4.3-1
ii  icedove [mail-reader]10.0.4-1
ii  logrotate3.8.1-4
ii  mailutils [mail-reader]  1:2.2+dfsg1-6+b1
ii  mutt [mail-reader]   1.5.21-5+b1
ii  procmail 3.22-20

-- debconf information:
* masqmail/ipup_fetch: false
* masqmail/mda: /usr/bin/procmail -Y -d ${rcpt_local}
* masqmail/init_smtp_daemon: false
* masqmail/local_hosts: localhost;thor;thor.local
* masqmail/host_name: thor.local
* masqmail/manage_config_with_debconf: true
* masqmail/use_syslog: false
* masqmail/listen_addresses:
* masqmail/init_fetch_daemon: false
* masqmail/init_queue_daemon: false
* masqmail/online_file: /var/run/masqmail-route
* masqmail/mbox_default: mbox
* masqmail/ipup_runqueue: false
* masqmail/online_detect: file
  masqmail/queue_daemon_ival: -q10m
* masqmail/alias_local_caseless: false
  masqmail/move_existing_nondebconf_config: true
* masqmail/ifup_ifaces: none
  masqmail/online_pipe:
  masqmail/fetch_daemon_ival: -go5m
* masqmail/local_nets:


--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#427900: marked as done (masqmail: SMTP server hangs when used to send when offline)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #427900,
regarding masqmail: SMTP server hangs when used to send when offline
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.)


-- 
427900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Severity: normal

When I'm not online, every connection to the localhost SMTP server
results in another "masqmail -bd -q10m" process which doesn't go away
and the mail never completes sending (from the MUA's point of view).
stracing shows the process waiting on a futex; gdbing doesn't give any
symbols in the backtrace.

Allowing the MUA (alpine, in my case) to break the connection (it
prompts me for this after waiting for a while) results in the mail
being apparently sent, although the masqmail process still remains.

If I instead use /usr/lib/sendmail, I don't get this problem.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages masqmail depends on:
ii  debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii  libc6 2.5-9+b1   GNU C Library: Shared libraries
ii  libglib2.0-0  2.12.12-1  The GLib library of C routines
ii  libident  0.22-3 simple RFC1413 client library - ru
ii  liblockfile1  1.06.1 NFS-safe locking library, includes
ii  netbase   4.29   Basic TCP/IP networking system

masqmail recommends no packages.

--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#654643: marked as done (masqmail: Silently discards mails when mbox exceeds 2 GiB)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #654643,
regarding masqmail: Silently discards mails when mbox exceeds 2 GiB
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.)


-- 
654643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.2.30-1
Severity: critical
Tags: lfs
Justification: causes serious data loss

Dear Maintainer,

I'm using masqmail -g to fetch email with pop3, and store them in a
traditional mbox file. New mails silently ceased to arrive. (Luckly I
discoverd this after irretrievably loosing "only" a bit more than 100
mails...) It turns out my mbox reached a size of 2 GiB.

Not only does masqmail fail to store the mails: it doesn't even realize
anything is wrong -- so there is no warning whatsoever, and the
undelivered mails are purged from the queue.

-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.0.0antrik1 (PREEMPT)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages masqmail depends on:
ii  debconf [debconf-2.0]  1.5.40  
ii  libc6  2.13-21 
ii  libglib2.0-0   2.28.8-1
ii  libident   0.22-3  
ii  liblockfile1   1.09-3  
ii  netbase4.47
ii  update-inetd   4.40

masqmail recommends no packages.

Versions of packages masqmail suggests:
pn  bsd-mailx [mail-reader]  8.1.2-0.20100314cvs-1
pn  cone [mail-reader]   0.89-1   
pn  logrotate3.7.8-6  
pn  mutt [mail-reader]   1.5.21-5 
pn  procmail

-- Configuration Files:
/etc/ppp/ip-down.d/99masqmail [Errno 13] Permission denied: 
u'/etc/ppp/ip-down.d/99masqmail'
/etc/ppp/ip-up.d/1masqmail [Errno 13] Permission denied: 
u'/etc/ppp/ip-up.d/1masqmail'

-- debconf information:
  masqmail/ipup_fetch: false
  masqmail/mda: /usr/bin/procmail -Y -d ${rcpt_local}
  masqmail/init_smtp_daemon: true
  masqmail/local_hosts:
  masqmail/you_are_not_finished:
* masqmail/note_pcmcia_scripts:
  masqmail/host_name:
* masqmail/manage_config_with_debconf: false
  masqmail/use_syslog: false
  masqmail/listen_addresses: localhost:25
  masqmail/init_fetch_daemon: false
  masqmail/init_queue_daemon: true
  masqmail/online_file: /var/run/masqmail-route
  masqmail/mbox_default: mbox
  masqmail/ipup_runqueue: true
  masqmail/online_detect: file
* masqmail/note_moved_tpl:
  masqmail/queue_daemon_ival: -q10m
  masqmail/alias_local_caseless: false
  masqmail/move_existing_nondebconf_config: false
  masqmail/ifup_ifaces: all
  masqmail/online_pipe:
  masqmail/fetch_daemon_ival: -go5m
  masqmail/local_nets:

-- debsums errors found:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 1252 package 
'libstdc++2.9-glibc2.1':
 missing architecture
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 10226 
package 'netscape4':
 missing architecture
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 22193 
package 'funny-manpages':
 missing architecture


--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#673551: marked as done (ifupdown: error during boot: grep: unrecognized option '--all')

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #673551,
regarding ifupdown: error during boot: grep: unrecognized option '--all'
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.)


-- 
673551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifupdown
Version: 0.7~rc3
Severity: normal

Dear Maintainer,

today i updated to ifupdown 0.7~rc3 and now i get during boot the
following error:


 snip ---

[ ok ] Setting up resolvconf...done.
[] Configuring network interfaces...grep: unrecognized option '--all'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
ifup: interface eth0 already configured
done.
[] Starting rpcbind daemon...rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
. ok

 snip ---


-- 
Regards,
Thilo

4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6  7C18 89A4 A2A0 C70B 1A8F



--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#691947: marked as done ([masqmail] Error using rmail: Exit status 127)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #691947,
regarding [masqmail] Error using rmail: Exit status 127
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.)


-- 
691947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.2.30-1
Severity: normal

--- Please enter the report below this line. ---
The following error is coming up when attempting use the 'rmail'
script installed by masqmail for receiving email via uucp:

ERROR: Execution: Exit status 127

I thought it might be an issue with permissions, but that did not
make any difference.  Checked the installed '/usr/sbin/rmail' itself and
and found that the SENDMAIL variable is defined there like this:

SENDMAIL="/build/buildd-masqmail_0.2.30-1-i386-W8eUJA/masqmail-0.2.30/debian/masqmail/usr/sbin/masqmail"


Changed that to be just "/usr/sbin/masqmail" and it now appears to
run properly.


--- System information. ---
Architecture: i386
Kernel: Linux 3.2.0-3-686-pae

Debian Release: wheezy/sid
500 testing ftp.us.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-
libc6 (>= 2.3) | 2.13-35
libglib2.0-0 (>= 2.12.0) | 2.33.12+really2.32.4-2
libident (>= 0.22-3) | 0.22-3
liblockfile1 (>= 1.0) | 1.09-4
debconf (>> 0.5) | 1.5.46
OR debconf-2.0 |
netbase | 5.0
update-inetd | 4.43


Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
mail-reader |
procmail | 3.22-20
logrotate | 3.8.1-4
--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#678493: marked as done (masqmail: prompting due to modified conffiles which were not modified by the user)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #678493,
regarding masqmail: prompting due to modified conffiles which were not modified 
by the user
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.)


-- 
678493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.3.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

http://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In http://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

>From the attached log (scroll to the bottom...):

  Setting up masqmail (0.3.4-1) ...
  
  Configuration file `/etc/default/masqmail'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** masqmail (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing masqmail 
(--configure):
   EOF on stdin at conffile prompt


cheers,

Andreas


masqmail_0.3.4-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#986648: marked as done (masqmail: new upstream version 0.3.5 available)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #986648,
regarding masqmail: new upstream version 0.3.5 available
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.)


-- 
986648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.3.4-1
Severity: wishlist

version 0.3.5 has been available at 
http://marmaro.de/prog/masqmail/files/ since 2015; i'd say it's about 
time to package it.
--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#882316: marked as done (masqmail fails to install on amd64 architecture)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #882316,
regarding masqmail fails to install on amd64 architecture
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.)


-- 
882316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Version: 0.2.30-1
Severity: important

Dear Maintainer,

I tried to install masqmail on my system via aptitude but it fails every time. 
The error message I get from aptitude is:
E: Internal Error, No file name for masqmail:amd64▒
I can't use the package at all.

-- System Information:
Debian Release: 8.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-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
Init: systemd (via /run/systemd/system)

Versions of packages masqmail depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-18+deb8u9
ii  libglib2.0-0   2.42.1-1+b1
ii  libident   0.22-3
ii  liblockfile1   1.09-6
ii  netbase5.3
ii  update-inetd   4.43

masqmail recommends no packages.

Versions of packages masqmail suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20141216cvs-2
ii  logrotate3.8.7-1+b1
ii  mutt [mail-reader]   1.5.23-3
ii  procmail 3.22-24

-- debconf information:
  masqmail/local_nets:
  masqmail/mbox_default: mbox
  masqmail/online_pipe:
  masqmail/queue_daemon_ival: -q10m
  masqmail/local_hosts: localhost;serwer;santelab.pl
  masqmail/manage_config_with_debconf: true
  masqmail/listen_addresses: localhost:25
  masqmail/host_name: santelab.pl
  masqmail/ipup_runqueue: true
  masqmail/fetch_daemon_ival: -go5m
  masqmail/online_detect: file
  masqmail/move_existing_nondebconf_config: true
  masqmail/init_fetch_daemon: false
  masqmail/online_file: /var/run/masqmail-route
  masqmail/init_smtp_daemon: true
  masqmail/ipup_fetch: false
  masqmail/mda: /usr/bin/procmail -Y -d ${rcpt_local}
  masqmail/ifup_ifaces: all
  masqmail/init_queue_daemon: true
  masqmail/use_syslog: false
  masqmail/alias_local_caseless: false



smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#558113: marked as done (unix domain socket support)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:22 +
with message-id 
and subject line Bug#1040238: Removed package(s) from unstable
has caused the Debian Bug report #558113,
regarding unix domain socket support
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.)


-- 
558113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gsm0710muxd
Version: 1.13-1+b1
Severity: wishlist
Tags: patch

hi!

i'm working for some time now on a phone app using dynamic gsm tty channels. 
using dbus to request new channels from the muxd showed to be extremely slow 
(at least on the target platform, which is - surprise - a gsm phone ;), and far 
too slow to be actually useable. i tried to improve things with channel 
pooling, but this still doesn't perform in a way that's somewhat useable.
thinking about it a bit, it came to my mind that a unix domain socket to the 
muxd is what seemed to be the most straightforward solution, and i guessed this 
way things would actually be a lot easier to handle - just connect to the 
socket, the muxd creates a new channel for you, no need to take care of 
anything else, the new channel will ofc also be removed as soon as the socket 
is disconnected. sounds like a perfect solution to me.
a quick search showed that somebody obviously not just had the same idea, but 
also already implemented it. i tried the patch out, and: works like a charm!
also, the patch just adds the socket method, but doesn't remove or change 
anything of the existing functionality.

i'd really like to suggest you to add the patch to the gsm0710muxd. it's a 
great feature and at least from my perspective (i.e. for apps using dynamic gsm 
tty channels) it makes the muxd actually useable/working in the first place.

the patch can be found at:

http://neil.brown.name/blog/20090131205109

kind regards,

Chris


--- End Message ---
--- Begin Message ---
Version: 1.13-3+rm

Dear submitter,

as the package gsm0710muxd 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/1040238

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#519961: marked as done (apf-firewall: package name is ... strange)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #519961,
regarding apf-firewall: package name is ... strange
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.)


-- 
519961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Version: 9.6+rev5-3
Severity: wishlist

Hi!

 If APF means "Advanced Policy Firewall", what does apf-firewall mean
then? What's the need for the duplicated firewall here? :)

 Thanks,
Rhonda


--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#955900: marked as done (gsm0710muxd: Depends on deprecated dbus-glib)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:22 +
with message-id 
and subject line Bug#1040238: Removed package(s) from unstable
has caused the Debian Bug report #955900,
regarding gsm0710muxd: Depends on deprecated dbus-glib
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.)


-- 
955900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsm0710muxd
Severity: normal
Tags: sid bullseye
Control: block 895291 by -1
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: dbus-glib-deprecation

dbus-glib is a deprecated D-Bus library with some significant design
flaws, and is essentially unmaintained. I would like to minimize its
use, and eventually remove it from Debian. There will not be a
version that fixes its design flaws, because that would be a major
compatibility break, and any user of dbus-glib who is willing to port
their application to a newer, incompatible version should instead be
porting their application to a better D-Bus implementation such as
GDBus.

For most purposes, the recommended replacement for dbus-glib is the
GDBus family of APIs in GLib, found in . This does not add
an additional dependency, because dbus-glib already depends on a
sufficiently new version of GLib. A porting guide is available in the
GLib documentation:
. Practical
examples of porting from dbus-glib to GDBus can be found in the git
history of most older GNOME applications.

Alternatives to GDBus, with different design emphasis and trade-offs,
include sd-bus (systemd's D-Bus implementation), QtDBus (Qt's D-Bus
API), and libdbus (the low-level reference D-Bus implementation).
Please contact the D-Bus mailing list 
if you are unsure which D-Bus implementation is most suitable for a
particular package.

Some libraries expose dbus-glib as part of their API/ABI, in which
case removing the deprecated dependency requires breaking API/ABI
(telepathy-glib is a good example). For these libraries, maintainers
should talk to the dependent library's upstream developers about
whether the dependent library should break API/ABI and switch to
GDBus, or whether the dependent library should itself be deprecated.

In a few cases, the package uses the reference D-Bus library libdbus
for all D-Bus-related APIs, and only uses dbus-glib as a way to
connect libdbus to the GLib main loop: if the only functions
referenced from dbus-glib are dbus_connection_setup_with_g_main() and
dbus_server_setup_with_g_main(), then you are in this situation. The
recommended replacement in this case is to bundle the dbus-gmain
branch from the dbus-glib git repository, for example as a `git
subtree` or `git submodule`. For example, dbus-python's GLib
integration now works like this. See
 for more details. 
--- End Message ---
--- Begin Message ---
Version: 1.13-3+rm

Dear submitter,

as the package gsm0710muxd 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/1040238

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#703220: marked as done (apf-firewall: RAB broken due to ipt_recent changing name to xt_recent)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #703220,
regarding apf-firewall: RAB broken due to ipt_recent changing name to xt_recent
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.)


-- 
703220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Version: 9.7+rev1-2
Severity: important

See check_rab() in functions.apf. It expects to see ipt_recent, but that
won't work because that module is now xt_recent.

-- System Information:
Debian Release: 6.0.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
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 apf-firewall depends on:
ii  iptables1.4.8-3  administration tools for packet fi
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  wget1.12-2.1 retrieves files from the web

apf-firewall recommends no packages.

apf-firewall suggests no packages.

-- Configuration Files:
/etc/apf-firewall/conf.apf changed [not included]
/etc/apf-firewall/ds_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/ds_hosts.rules'
/etc/apf-firewall/glob_allow.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/glob_allow.rules'
/etc/apf-firewall/glob_deny.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/glob_deny.rules'
/etc/apf-firewall/internals/reserved.networks [Errno 13] Permission denied: 
u'/etc/apf-firewall/internals/reserved.networks'
/etc/apf-firewall/sdrop_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/sdrop_hosts.rules'
/etc/default/apf-firewall changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#633648: marked as done (apf-firewall: The SET_REFRESH option is useless because of cron ignores refresh.apf link)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #633648,
regarding apf-firewall: The SET_REFRESH option is useless because of cron 
ignores refresh.apf link
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.)


-- 
633648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Version: 9.7+rev1-2
Severity: important

The SET_REFRESH option in conf.apt does not work because the cron daemon will 
ignore scripts in /etc/cron.d/ with dots (.) in their name, therefore the 
refresh.apf link is ignored.
Instead cron will always download the rules once a day.
Interestingly, if you rename the refresh.apf and take out the dot, cron will 
complain saying that there is an error in the minutes format (Debian specific 
issue?)

-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#703221: marked as done (apf-firewall: RAB doesn't work because ipt_recent is now xt_recent.)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #703220,
regarding apf-firewall: RAB doesn't work because ipt_recent is now xt_recent.
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.)


-- 
703220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Version: 9.7+rev1-2
Severity: important

In /etc/apf-firewall/internals/functions.apf, there is this line:

if [ "$RAB" == "1" ] && [ ! -f "/lib/modules/$(uname 
-r)/kernel/net/ipv4/netfilter/ipt_recent.$MEXT" ]; then

Well, this doesn't work because ipt_recent is now xt_recent. This means that
reactive address blocking (RAB) is broken, which means that APF's ability to
detect and respond to portscans (one of its most important features) is
inoperative.

Changes further up in the file indicate that someone knows about the
xt_recent change, but for whatever reason they forgot to fix it there.


-- System Information:
Debian Release: 6.0.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
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 apf-firewall depends on:
ii  iptables1.4.8-3  administration tools for packet fi
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  wget1.12-2.1 retrieves files from the web

apf-firewall recommends no packages.

apf-firewall suggests no packages.

-- Configuration Files:
/etc/apf-firewall/conf.apf changed [not included]
/etc/apf-firewall/ds_hosts.rules changed [not included]
/etc/apf-firewall/glob_allow.rules changed [not included]
/etc/apf-firewall/glob_deny.rules changed [not included]
/etc/apf-firewall/internals/reserved.networks changed [not included]
/etc/default/apf-firewall changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#841895: marked as done (apf-firewall: Apf blocks mysql connection on 127.0.0.1)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #841895,
regarding apf-firewall: Apf blocks mysql connection on 127.0.0.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.)


-- 
841895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Version: 9.7+rev1-3
Severity: important

There is a daily cronjob running which is restarting apf-firewall. However, 
sometimes 
it breaks my system - to be specific - it somehow blocks connectivity for mysql 
on 127.0.0.1 
and I'm not able to connect neither command line, websites are not working, MTA 
postfix (with ispconfig) 
fails to check for table lookup (because it's connecting to with user/pass on 
127.0.0.1. Localhost 
connections are working normally. After stopped firewall with e.g. "apf -f" - 
on first F5 refresh all 
websites are working, I'm able to connect in mysql through "mysql -p -h 
127.0.0.1". This doesn't happen 
every day, it happens on random basics and always in same time around 06:26AM - 
cronjob dailys are schedules 
to run on 06:25AM. I can't reproduce the problem, but so far I know that 
stopping apf-firewal 
fixes the problem. I don't even have to restart mysql/MTA - stopping apf is 
enough. Any idea what 
could cause this?

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages apf-firewall depends on:
ii  iproute   1:3.16.0-2
ii  iptables  1.4.21-2+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  wget  1.16-1

apf-firewall recommends no packages.

apf-firewall suggests no packages.

-- Configuration Files:
/etc/apf-firewall/conf.apf changed [not included]
/etc/apf-firewall/deny_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/deny_hosts.rules'
/etc/apf-firewall/ds_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/ds_hosts.rules'
/etc/apf-firewall/glob_allow.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/glob_allow.rules'
/etc/apf-firewall/glob_deny.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/glob_deny.rules'
/etc/apf-firewall/preroute.rules changed [not included]
/etc/apf-firewall/sdrop_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/sdrop_hosts.rules'
/etc/cron.daily/apf-firewall changed [not included]
/etc/default/apf-firewall changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#908655: marked as done (apf-firewall: The rules activated by PKT_SANITY_STUFFED are overzealous and block DSL customers)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #908655,
regarding apf-firewall: The rules activated by PKT_SANITY_STUFFED are 
overzealous and block DSL customers
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.)


-- 
908655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Version: 9.7+rev1-5
Severity: normal

Dear Maintainer,

thanks for the time you make available for maintaining packages in
Debian.

I just had an issue in apf-firewall I hopefully expressed understandably
below.

   * What led up to the situation?

   I got a report that someone could only access my website via his
   mobile phone, not via his landline internet access. After switching
   off apf-firewall access was possible, further investigation revealed
   a conceptional mistake.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   
   Added the IP address directly to the allow hosts.

   * What was the outcome of this action?
   
   Access to website was restored, then went on to hunt rules which
   triggered with the orignal rulesets. Found the source rule in
   bt.rules and went and deactivated PKT_SANITY_STUFFED.  Not every
   0.0.0.255 is a broadcast, and even .191, .127 or .63 may be, why not
   also block those? 

   * What outcome did you expect instead?

   Not to block 0.0.0.255 as you can't tell how the provider uses a big
   allocation like92.252.0.0/17AS15747 for his customers.
   netnum:92.252.8.0 - 92.252.111.255


With kind regards

Peter

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apf-firewall depends on:
ii  iproute   1:4.9.0-1+deb9u1
ii  iptables  1.6.0+snapshot20161117-6
ii  lsb-base  9.20161125
ii  wget  1.18-5+deb9u2

apf-firewall recommends no packages.

apf-firewall suggests no packages.

-- Configuration Files:
/etc/apf-firewall/allow_hosts.rules changed:
92.252.xx.255

/etc/apf-firewall/conf.apf changed:
DEVEL_MODE="0"
INSTALL_PATH="/etc/apf-firewall"
IFACE_IN="eth0" 
IFACE_OUT="eth0"
IFACE_TRUSTED=""
SET_VERBOSE="1"
SET_FASTLOAD="0"
SET_VNET="0"
SET_ADDIFACE="0"
SET_MONOKERN="0"
SET_REFRESH="30"
SET_TRIM="150"
VF_ROUTE="1"
VF_CROND="1"
VF_LGATE=""
RAB="1"
RAB_SANITY="1"
RAB_PSCAN_LEVEL="2"
RAB_HITCOUNT="1"
RAB_TIMER="300"
RAB_TRIP="1"
RAB_LOG_HIT="1"
RAB_LOG_TRIP="0"
TCP_STOP="RESET"
UDP_STOP="RESET"
ALL_STOP="DROP"
PKT_SANITY="1"
PKT_SANITY_INV="1"
PKT_SANITY_FUDP="1"
PKT_SANITY_PZERO="1"
PKT_SANITY_STUFFED="0"
TOS_DEF="0"
TOS_DEF_RANGE="512:65535"
TOS_0=""
TOS_2=""
TOS_4=""
TOS_8="80,443"
TOS_16="25,110,143,22"
TCR_PASS="1"TCR_PORTS="33434:33534"
ICMP_LIM="30/s"
RESV_DNS="1"
RESV_DNS_DROP="1"
BLK_P2P_PORTS=""
BLK_PORTS="111,135_139,445,513,520,1234,1433,1434,1524,3127"
BLK_MCATNET="1"
BLK_PRVNET="1"
BLK_RESNET="1"
BLK_IDENT="1"
SYSCTL_CONNTRACK="34576"
SYSCTL_TCP="1"
SYSCTL_SYN="1"
SYSCTL_ROUTE="1"
SYSCTL_LOGMARTIANS="1"
SYSCTL_ECN="1"
SYSCTL_SYNCOOKIES="1"
SYSCTL_OVERFLOW="0"
HELPER_SSH="1"
HELPER_SSH_PORT="22"
HELPER_FTP="0"
HELPER_FTP_PORT="21"
HELPER_FTP_DATA="20"
IG_TCP_CPORTS="22,25,465,587,80,443,993,995,1011,30033"
IG_UDP_CPORTS="9987"
IG_ICMP_TYPES="3,5,11,0,30,8"
EGF="0"
EG_TCP_CPORTS="21,25,80,443,43"
EG_UDP_CPORTS="20,21,53"
EG_ICMP_TYPES="all"
EG_TCP_UID=""
EG_UDP_UID=""
EG_DROP_CMD="eggdrop psybnc bitchx BitchX init udp.pl"
DLIST_PHP="1"
DLIST_PHP_URL="rfxn.com/downloads/php_list"  
DLIST_PHP_URL_PROT="http"
DLIST_SPAMHAUS="1"
DLIST_SPAMHAUS_URL="www.spamhaus.org/drop/drop.lasso" 
DLIST_SPAMHAUS_URL_PROT="http"
DLIST_DSHIELD="1"
DLIST_DSHIELD_URL="feeds.dshield.org/top10-2.txt"   
DLIST_DSHIELD_URL_PROT="http"   
DLIST_RESERVED="1"
DLIST_RESERVED_URL="rfxn.com/downloads/reserved.networks"
DLIST_RESERVED_URL_PROT="http"  
DLIST_ECNSHAME="0"
DLIST_ECNSHAME_URL="rfxn.com/downloads/ecnshame.lst" 
DLIST_ECNSHAME_URL_PROT="http"   
USE_RGT="0"
GA_URL="yourhost.com/glob_allow.rules"   
GA_URL_PROT="http"   
GD_URL="yourhost.com/glob_deny.ru

Bug#841897: marked as done (apf-firewall: Apf blocks mysql connection on 127.0.0.1)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #841895,
regarding apf-firewall: Apf blocks mysql connection on 127.0.0.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.)


-- 
841895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: apf-firewall
Version: 9.7+rev1-3
Severity: important

There is a daily cronjob running which is restarting apf-firewall. However, 
sometimes
it breaks my system - to be specific - it somehow blocks connectivity for mysql 
on 127.0.0.1
and I'm not able to connect neither command line, websites are not working, MTA 
postfix (with ispconfig)
fails to check for table lookup (because it's connecting to with user/pass on 
127.0.0.1. Localhost
connections are working normally. After stopped firewall with e.g. "apf -f" - 
on first F5 refresh all
websites are working, I'm able to connect in mysql through "mysql -p -h 
127.0.0.1". This doesn't happen
every day, it happens on random basics and always in same time around 06:26AM - 
cronjob dailys are schedules
to run on 06:25AM. I can't reproduce the problem, but so far I know that 
stopping apf-firewal
fixes the problem. I don't even have to restart mysql/MTA - stopping apf is 
enough. Any idea what
could cause this?

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages apf-firewall depends on:
ii  iproute   1:3.16.0-2
ii  iptables  1.4.21-2+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  wget  1.16-1

apf-firewall recommends no packages.

apf-firewall suggests no packages.

-- Configuration Files:
/etc/apf-firewall/conf.apf changed [not included]
/etc/apf-firewall/deny_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/deny_hosts.rules'
/etc/apf-firewall/ds_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/ds_hosts.rules'
/etc/apf-firewall/glob_allow.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/glob_allow.rules'
/etc/apf-firewall/glob_deny.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/glob_deny.rules'
/etc/apf-firewall/preroute.rules changed [not included]
/etc/apf-firewall/sdrop_hosts.rules [Errno 13] Permission denied: 
u'/etc/apf-firewall/sdrop_hosts.rules'
/etc/cron.daily/apf-firewall changed [not included]
/etc/default/apf-firewall changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#851349: marked as done (leftover crontab entry)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #851349,
regarding leftover crontab entry
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.)


-- 
851349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Version: 9.7+rev1-5

When you install and then decide to remove it again before any manual
configuration the following is left behind in "/etc/crontab":
*/5 * * * * root /etc/init.d/apf-firewall stop >> /dev/null 2>&1

Please make the package cleanup this addition on uninstall, for
example using "sed -ire '/apf-firewall/ d' /etc/crontab" or
similar
otherwise the machine will try to run this non-existent command for
eternity (and thus log it)

Note: mail to this address will automatically be deleted !
--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1040236: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 mason |   1.0.0-13 | source, all

--- Reason ---
RoQA; dead upstream, alternatives exist
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1040...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1040236

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1040236: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.0.0-13+rm

Dear submitter,

as the package mason 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/1040236

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1040237: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  masqmail |0.3.4-2 | source, amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; dead upstream, RC-buggy
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1040...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1040237

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1040237: Removed package(s) from unstable

[Debian FTP Masters]

Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1039262: marked as done (mason: ships sysv-init script without systemd unit)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id 
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #1039262,
regarding mason: ships sysv-init script without systemd unit
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.)


-- 
1039262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mason
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service

Dear Maintainer(s),

mason has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a transitional
sysv-init-to-unit generator was shipped by systemd. This is in the
process of being deprecated and will be removed by the time Trixie
ships, so the remaining packages that ship init scripts without
systemd units will stop working.

There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html

You can find the Lintian warning here:

https://lintian.debian.org/sources/mason

In case this is a false positive, please add a Lintian override to
silence it and then close this bug.

Thanks! 
--- End Message ---
--- Begin Message ---
Version: 1.0.0-13+rm

Dear submitter,

as the package mason 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/1040236

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1040238: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

gsm0710muxd | 1.13-3 | source
gsm0710muxd |  1.13-3+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x

--- Reason ---
RoQA; obsolete, dead upstream, uses legacy libs
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1040...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1040238

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1040238: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.13-3+rm

Dear submitter,

as the package gsm0710muxd 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/1040238

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1039263: marked as done (masqmail: ships sysv-init script without systemd unit)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id 
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #1039263,
regarding masqmail: ships sysv-init script without systemd unit
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.)


-- 
1039263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: masqmail
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service

Dear Maintainer(s),

masqmail has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a transitional
sysv-init-to-unit generator was shipped by systemd. This is in the
process of being deprecated and will be removed by the time Trixie
ships, so the remaining packages that ship init scripts without
systemd units will stop working.

There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html

You can find the Lintian warning here:

https://lintian.debian.org/sources/masqmail

In case this is a false positive, please add a Lintian override to
silence it and then close this bug.

Thanks! 
--- End Message ---
--- Begin Message ---
Version: 0.3.4-2+rm

Dear submitter,

as the package masqmail 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/1040237

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1040239: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

apf-firewall | 9.7+rev1-7 | source, all

--- Reason ---
RoQA; obsolete, unmaintained
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1040...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1040239

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1039216: marked as done (gsm0710muxd: ships sysv-init script without systemd unit)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:22 +
with message-id 
and subject line Bug#1040238: Removed package(s) from unstable
has caused the Debian Bug report #1039216,
regarding gsm0710muxd: ships sysv-init script without systemd unit
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.)


-- 
1039216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsm0710muxd
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service

Dear Maintainer(s),

gsm0710muxd has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this worked because a
transitional sysv-init-to-unit generator was shipped by systemd. This
is in the process of being deprecated and will be removed by the time
Trixie ships, so the remaining packages that ship init scripts
without systemd units will stop working.

There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html

You can find the Lintian warning here:

https://lintian.debian.org/sources/gsm0710muxd

In case this is a false positive, please add a Lintian override to
silence it and then close this bug.

Thanks! 
--- End Message ---
--- Begin Message ---
Version: 1.13-3+rm

Dear submitter,

as the package gsm0710muxd 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/1040238

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1040239: Removed package(s) from unstable

[Debian FTP Masters]

Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#985635: ghostscript 9.53 produces incorrect output with xelatex and PStricks

[Jim McCloskey]

This problem is resolved in Debian 12 Bookworm, with the arrival of ghostscript 
10.0.
The bug should probably be closed.  Thank you all for all of your work,

Jim McCloskey

* Jim McCloskey (mccl...@ucsc.edu) wrote:

  |>  Package: ghostscript
  |>  Version: 9.53~dfsg-2+deb10u4
  |>  X-Debbugs-Cc: mccl...@ucsc.edu, debian-tex-ma...@lists.debian.org
  |>  Severity: normal
  |>  Tags: upstream
  |>  
  |>  Dear Maintainer,
  |>  
  |>  A LaTeX document which includes a call to PStricks and the pst-jtree 
package produces correct
  |>  PDF output when compiled with xelatex in Debian buster.  Following an 
upgrade to bullseye, the
  |>  same document compiled in exactly the same way produces incorrect output.

--
Jim McCloskey mccl...@ucsc.edu
Department of Linguistics
UC Santa Cruz  http://people.ucsc.edu/~mcclosk
--

Bug#1039127: marked as done (apf-firewall: ships sysv-init script without systemd unit)

[Debian Bug Tracking System]

Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id 
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #1039127,
regarding apf-firewall: ships sysv-init script without systemd unit
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.)


-- 
1039127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apf-firewall
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service

Dear Maintainer(s),

apf-firewall has been flagged by Lintian as shipping a sysv-init
script without a corresponding systemd unit file. The default init
system in Debian is systemd, and so far this worked because a
transitional sysv-init-to-unit generator was shipped by systemd. This
is in the process of being deprecated and will be removed by the time
Trixie ships, so the remaining packages that ship init scripts
without systemd units will stop working.

There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html

You can find the Lintian warning here:

https://lintian.debian.org/sources/apf-firewall

In case this is a false positive, please add a Lintian override to
silence it and then close this bug.

Thanks! 
--- End Message ---
--- Begin Message ---
Version: 9.7+rev1-7+rm

Dear submitter,

as the package apf-firewall 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/1040239

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

purple-discord is marked for autoremoval from testing

[Debian testing autoremoval watch]

purple-discord 0.9.2023.02.15.git.4a09188-2 is marked for autoremoval from 
testing on 2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-nateon is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-nateon 0.0.0.svn147-2 is marked for autoremoval from testing on 
2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-privacy-please is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-privacy-please 0.7.1-4 is marked for autoremoval from testing on 
2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-librvp is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-librvp 0.9.7cvs-4 is marked for autoremoval from testing on 2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-audacious is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-audacious 2.0.0-8 is marked for autoremoval from testing on 2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-extprefs is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-extprefs 0.7-3 is marked for autoremoval from testing on 2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

bitlbee-facebook is marked for autoremoval from testing

[Debian testing autoremoval watch]

bitlbee-facebook 1.2.2-2 is marked for autoremoval from testing on 2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-skype is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-skype 20140930+svn665+dfsg-2 is marked for autoremoval from testing on 
2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-blinklight is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-blinklight 0.11.1-5 is marked for autoremoval from testing on 2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

pidgin-hotkeys is marked for autoremoval from testing

[Debian testing autoremoval watch]

pidgin-hotkeys 0.2.4-3 is marked for autoremoval from testing on 2023-07-28

It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
 https://bugs.debian.org/1036113



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

Bug#1040275: python3-socketio-client: SyntaxWarning during package installation

[Andreas Beckmann]

Package: python3-socketio-client
Version: 0.6.5-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package emits a SyntaxWarning
during installation:

  Setting up python3-socketio-client (0.6.5-1) ...
  /usr/lib/python3/dist-packages/socketIO_client/__init__.py:278: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
if engineIO_packet_type is 4:


Andreas