Your message dated Wed, 28 Oct 2026 18:37:43 +0000
with message-id <[email protected]>
and subject line Bug#1151749: Removed package(s) from unstable
has caused the Debian Bug report #1151749,
regarding RM: gmpc -- ROM; dead upstream, depends on GTK 2, alternatives 
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 [email protected]
immediately.)


-- 
1151749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151749
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:gmpc
Control: block -1 by 1151748
User: [email protected]
Usertags: remove

gmpc has not been in testing since the beginning of 2026 due to 
its dependency on the unmaintained GTK 2. It's dead upstream, and so is 
the most promising GTK 3 fork.

I think it's time to remove this from Debian. Alternatives include 
cantata, plattenalbum and sonata, possibly combined with mpdris2 and 
desktop environment MPRIS integration (I mostly use mpdris2 and cantata 
myself).

gmpc-plugins will need to be removed first (#1151748).

    smcv

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

      gmpc | 11.8.16-23 | source
      gmpc | 11.8.16-23+b2 | amd64, arm64, armhf, i386, loong64, ppc64el, 
riscv64, s390x
 gmpc-data | 11.8.16-23 | all
  gmpc-dev | 11.8.16-23+b2 | amd64, arm64, armhf, i386, loong64, ppc64el, 
riscv64, s390x

------------------- Reason -------------------
ROM; dead upstream, depends on GTK 2, alternatives available
----------------------------------------------

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 [email protected].

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

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to