Your message dated Tue, 04 Feb 2025 03:24:31 +0000
with message-id <e1tf9y7-000f2b...@fasolo.debian.org>
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 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.)


-- 
1089931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wondershaper
Version: 1.1a-12
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: ben.wiederh...@gmail.com

Dear Maintainer,

it seems that virtually any usage of wondershaper results in errors:

```
# wondershaper eno1 200 200
Unknown qdisc "cbq", hence option "avpkt" is unparsable
Error: Qdisc "cbq" is classless.
Error: Qdisc "cbq" is classless.
Error: Qdisc "cbq" is classless.
Error: Qdisc "cbq" is classless.
Error: Failed to find specified qdisc.
Error: Failed to find specified qdisc.
Error: Failed to find specified qdisc.
Error: Parent Qdisc doesn't exists.
We have an error talking to the kernel
Error: Parent Qdisc doesn't exists.
We have an error talking to the kernel
Error: Parent Qdisc doesn't exists.
We have an error talking to the kernel
Error: Parent Qdisc doesn't exists.
We have an error talking to the kernel
Error: Parent Qdisc doesn't exists.
We have an error talking to the kernel
```

It seems that this has been a known issue for at least half a year:
https://github.com/magnific0/wondershaper/issues/100

It seems that the root cause is that wondershaper needs the CBQ net scheduler,
which has been removed from the Linux kernel in 2023-02-16:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net/sched/sch_cbq.c?id=051d442098421c28c7951625652f61b1e15c4bd5

As such, this package is unusable to all users that use Linux Linux 6.3-rc1
(released around 2023-03-05) or later. (This might also affect earlier
versions, I didn't investigate too closely.)

Since wondershaper is orphaned, I suggest removing this package, but don't know
how that process works.

With regards,
Ben


-- System Information:
Debian Release: trixie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wondershaper depends on:
ii  iproute2  6.12.0-1

wondershaper recommends no packages.

wondershaper suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
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

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.
Paul Tagliamonte (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to