Bug#1041584: closed by Debian FTP Masters (Bug#1095040: Removed package(s) from unstable)

2025-02-03 Thread Andrey Semashev
On 2/4/25 06:27, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:wondershaper package: > > #1041584: Consider switching to wondershaper 1.4.1 > > It has been closed by Debian FTP Masters . > > Their explanation is

Bug#1094965: wtmpdb: provides no way to prune rotated logs

2025-02-03 Thread Andrew Bower
Thanks for the review, Chris! On Mon, Feb 03, 2025 at 11:52:08PM +0100, Chris Hofstaedtler wrote: > ISTM this is a lot of new, potentially fragile sh code, possibly > with undefined semantics. Indeed shellcheck has a lot of things to > say, including: > > | In prune-logs line 9: > | set -o pipefa

Bug#1041584: marked as done (Consider switching to wondershaper 1.4.1)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #1041584, regarding Consider switching to wondershaper 1.4.1 to be marked as done. This means that you claim that the problem has been

Bug#1067658: marked as done (Update source link to package recent software version)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #1067658, regarding Update source link to package recent software version to be marked as done. This means that you claim that the pro

Bug#1089931: marked as done (wondershaper: does not work at all with newer Linux versions (CBQ net scheduler))

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #1089931, regarding wondershaper: does not work at all with newer Linux versions (CBQ net scheduler) to be marked as done. This means

Bug#253385: marked as done (wondershaper: more advanced, but complex, option parsing)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #253385, regarding wondershaper: more advanced, but complex, option parsing to be marked as done. This means that you claim that the p

Bug#253790: marked as done (wondershaper: use the HTB version of the Wondershaper, not the CBQ version)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #253790, regarding wondershaper: use the HTB version of the Wondershaper, not the CBQ version to be marked as done. This means that y

Bug#253554: marked as done (Please use something like /etc/default/wondershaper)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #253554, regarding Please use something like /etc/default/wondershaper to be marked as done. This means that you claim that the proble

Bug#303520: marked as done (wondershaper: Please add a --dry-run option)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #303520, regarding wondershaper: Please add a --dry-run option to be marked as done. This means that you claim that the problem has be

Bug#1093528: marked as done (nixnote2: Unmaintained upstream)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:25:33 + with message-id and subject line Bug#1094954: Removed package(s) from unstable has caused the Debian Bug report #1093528, regarding nixnote2: Unmaintained upstream to be marked as done. This means that you claim that the problem has been dealt wi

Bug#348715: marked as done (wondershaper: [PATCH] Split default class into 5 based on packet size and reduce child class rates to be inclusive of total bandwidth)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #348715, regarding wondershaper: [PATCH] Split default class into 5 based on packet size and reduce child class rates to be inclusive

Bug#256754: marked as done (wondershaper: Needs a benchmark>>autoconfigure script.)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #256754, regarding wondershaper: Needs a benchmark>>autoconfigure script. to be marked as done. This means that you claim that the pro

Bug#256461: marked as done (wondershaper: Option to limit range of rules?)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #256461, regarding wondershaper: Option to limit range of rules? to be marked as done. This means that you claim that the problem has

Bug#308070: marked as done (Reenabling the NOPRIO* options of wondershaper. Some more informative output.)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #308070, regarding Reenabling the NOPRIO* options of wondershaper. Some more informative output. to be marked as done. This means tha

Bug#461560: marked as done (wondershaper: allow setting high priority ports also (ssh, ntp, etc.))

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #461560, regarding wondershaper: allow setting high priority ports also (ssh, ntp, etc.) to be marked as done. This means that you cla

Bug#440274: marked as done (wondershaper: limits incoming traffic although a higher value is set on start)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #440274, regarding wondershaper: limits incoming traffic although a higher value is set on start to be marked as done. This means tha

Bug#384536: marked as done (wondershaper: add config scripts for /etc/network)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #384536, regarding wondershaper: add config scripts for /etc/network to be marked as done. This means that you claim that the problem

Bug#616034: marked as done (wondershaper: root CBQ bandwidth needs to be bigger)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #616034, regarding wondershaper: root CBQ bandwidth needs to be bigger to be marked as done. This means that you claim that the proble

Bug#540988: marked as done (wondershaper: add ppp/ip-*.d scripts)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #540988, regarding wondershaper: add ppp/ip-*.d scripts to be marked as done. This means that you claim that the problem has been deal

Bug#461559: marked as done (doesn't let you set the NOPRIOHOSTSRC etc variables without patching the file in /sbin/wondershaper)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #253554, regarding doesn't let you set the NOPRIOHOSTSRC etc variables without patching the file in /sbin/wondershaper to be marked as

Bug#795874: marked as done (wondershaper: Hardcoded bandwidth limit)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #795874, regarding wondershaper: Hardcoded bandwidth limit to be marked as done. This means that you claim that the problem has been d

Bug#651586: marked as done (wondershaper: Prioritize DNS traffic)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #651586, regarding wondershaper: Prioritize DNS traffic to be marked as done. This means that you claim that the problem has been deal

Bug#797050: marked as done (wondershaper: Please add a NetworkManager script and instructions)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #797050, regarding wondershaper: Please add a NetworkManager script and instructions to be marked as done. This means that you claim t

Bug#924011: marked as done (wondershaper: README.Debian: Suggest using $IFACE in /etc/network/interfaces reference)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #924011, regarding wondershaper: README.Debian: Suggest using $IFACE in /etc/network/interfaces reference to be marked as done. This

Bug#1095040: Removed package(s) from unstable

2025-02-03 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: wondershaper |1.1a-12 | source, all --- Reason --- RoQA; unmaintained, and broken on kernel 6.3-rc1 and later --

Bug#1006279: marked as done (Please update to latest release 1.4.1 including configuration file and systemd support)

2025-02-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Feb 2025 03:24:31 + with message-id and subject line Bug#1095040: Removed package(s) from unstable has caused the Debian Bug report #1006279, regarding Please update to latest release 1.4.1 including configuration file and systemd support to be marked as done. This

Bug#1094954: Removed package(s) from unstable

2025-02-03 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: nixnote2 | 2.1.10+dfsg1-2 | source nixnote2 | 2.1.10+dfsg1-2+b2 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x --- Reason --- Ro

Bug#1094954: Removed package(s) from unstable

2025-02-03 Thread Debian FTP Masters
Version: 2.1.10+dfsg1-2+rm Dear submitter, as the package nixnote2 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/10949

Bug#1095040: Removed package(s) from unstable

2025-02-03 Thread Debian FTP Masters
Version: 1.1a-12+rm Dear submitter, as the package wondershaper 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/1095040

Bug#1094965: wtmpdb: provides no way to prune rotated logs

2025-02-03 Thread Andrew Bower
Control: tags -1 patch On Sat, Feb 01, 2025 at 09:24:31PM +, Andrew Bower wrote: > wtmpdb will rotate logs but nothing will prune them (like logrotate would for > other types of log - unfortunately it doesn't fit in well with the wtmpdb > way). I have come up with a solution whereby a 'prune

Processed: Re: wtmpdb: provides no way to prune rotated logs

2025-02-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1094965 [wtmpdb] wtmpdb: provides no way to prune rotated logs Added tag(s) patch. -- 1094965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1094965: wtmpdb: provides no way to prune rotated logs

2025-02-03 Thread Chris Hofstaedtler
* Andrew Bower [250203 23:39]: > Control: tags -1 patch > > On Sat, Feb 01, 2025 at 09:24:31PM +, Andrew Bower wrote: > > wtmpdb will rotate logs but nothing will prune them (like logrotate would > > for > > other types of log - unfortunately it doesn't fit in well with the wtmpdb > > way).

Processed: Re: Bug#1094921: sysvinit-core: does not write entries to wtmpdb

2025-02-03 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 wtmpdb Bug #1094921 [sysvinit-core] sysvinit-core: does not write entries to wtmpdb Bug reassigned from package 'sysvinit-core' to 'wtmpdb'. No longer marked as found in versions sysvinit/3.13-1. Ignoring request to alter fixed versions of bug #1094921 to

Processed: affects 868752

2025-02-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 868752 - src:uwsgi Bug #868752 [cdbs] cdbs: python helper finds python3.5 und python3.6 but no runtime for python3.6 Removed indication that 868752 affects src:uwsgi > thanks Stopping processing here. Please contact me if you need assist

Processed: tagging 1094943, tagging 1094942, tagging 1094940, tagging 1093526, tagging 1094655 ...

2025-02-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1094943 + sid trixie Bug #1094943 [dnsvi] dnsvi: not installable due to missing dnsutils Added tag(s) sid and trixie. > tags 1094942 + sid trixie Bug #1094942 [dns-browse] dlint: not installable due to missing dnsutils Added tag(s) sid and tr

zc.buildout_4.0-1_source.changes ACCEPTED into unstable

2025-02-03 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Feb 2025 07:30:31 +0100 Source: zc.buildout Architecture: source Version: 4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexand

zope.hookable_7.0-1_source.changes ACCEPTED into unstable

2025-02-03 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Feb 2025 07:15:53 +0100 Source: zope.hookable Architecture: source Version: 7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexa

Processing of zope.hookable_7.0-1_source.changes

2025-02-03 Thread Debian FTP Masters
zope.hookable_7.0-1_source.changes uploaded successfully to localhost along with the files: zope.hookable_7.0-1.dsc zope.hookable_7.0.orig.tar.gz zope.hookable_7.0-1.debian.tar.xz zope.hookable_7.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debia

Processing of zc.buildout_4.0-1_source.changes

2025-02-03 Thread Debian FTP Masters
zc.buildout_4.0-1_source.changes uploaded successfully to localhost along with the files: zc.buildout_4.0-1.dsc zc.buildout_4.0.orig.tar.gz zc.buildout_4.0-1.debian.tar.xz zc.buildout_4.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

zope.location_5.1-1_source.changes ACCEPTED into unstable

2025-02-03 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Feb 2025 07:04:35 +0100 Source: zope.location Architecture: source Version: 5.1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexa

Processing of zope.location_5.1-1_source.changes

2025-02-03 Thread Debian FTP Masters
zope.location_5.1-1_source.changes uploaded successfully to localhost along with the files: zope.location_5.1-1.dsc zope.location_5.1.orig.tar.gz zope.location_5.1-1.debian.tar.xz zope.location_5.1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debia

Bug#1094921: sysvinit-core: does not write entries to wtmpdb

2025-02-03 Thread Andrew Bower
Control: tags -1 + patch On Mon, Feb 03, 2025 at 09:05:59AM +, Mark Hindley wrote: > control: reassign -1 wtmpdb > > Andrew, > > This seems to be resolvable in wtmpdb, so I am reassigning. https://salsa.debian.org/abower/wtmpdb/-/commit/bfcc651ba54f2edec3cb502968db21556d0cb47e https://salsa

Processed: Re: Bug#1094921: sysvinit-core: does not write entries to wtmpdb

2025-02-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1094921 [wtmpdb] sysvinit-core: does not write entries to wtmpdb Added tag(s) patch. -- 1094921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems