Your message dated Thu, 29 Mar 2018 10:53:36 +0200
with message-id <[email protected]>
and subject line Re: Bug#892878: RM: consolekit/0.4.6-6
has caused the Debian Bug report #892878,
regarding RM: consolekit/0.4.6-6
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.)
--
892878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892878
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: rm
Please remove consolekit 0.4.6-6 from testing.
It is no longer useful on Linux, so I made an upload to unstable turning
it into a !Linux package.
But as the package builds no binaries anymore on Linux, the package will
not migrate automatically to testing.
I think the solution for this is to remove all binaries from testing.
Thanks,
Michael
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 14/03/18 03:10, Michael Biebl wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: rm
>
> Please remove consolekit 0.4.6-6 from testing.
> It is no longer useful on Linux, so I made an upload to unstable turning
> it into a !Linux package.
> But as the package builds no binaries anymore on Linux, the package will
> not migrate automatically to testing.
>
> I think the solution for this is to remove all binaries from testing.
Removed.
Emilio
--- End Message ---
