Your message dated Thu, 4 Dec 2025 22:42:09 +0100
with message-id <[email protected]>
and subject line Re: Bug#722262: Packages removed from testing when taken over 
by another source in sid
has caused the Debian Bug report #722262,
regarding Packages removed from testing when taken over by another source in sid
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.)


-- 
722262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722262
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: britney

It seems Britney will happily remove from testing any binary package taken over
in sid by another source package when its initial source package is removed or
updated, instead of waiting for the new version of the package to be ready. I'm
wondering whether this is an expected behavior of Britney.

For instance, package proftpd-mod-geoip was removed from testing together with
its source package on July 1, while the new version of the package build from
the source package proftpd-dfsg is still stuck in sid.

Likewise, libcolord-gtk-dev and libcolord-gtk1 were removing from testing when
the source package colord was updated on July 6; a new version of these
packages were put back in testing the next day together with their new source
package colord-gtk.

Finally, ulogd and other packages from the source package ulogd were removed
from testing on July 7, while transitional dummy packages of the same names
remained in sid until July 15 together with the new source package ulogd2.

-- Jérôme Vouillon



-- System Information:
Debian Release: jessie/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
tags 722262 wontfix
thanks

On Tue, 10 Sep 2013 05:50:26 +0100 "Adam D. Barratt" <[email protected]> wrote:
Is this actually causing any practical problems, rather than "seeming
the wrong thing to do"?

I've now stumbled upon this bug report multiple times and each time I think it's not worth fixing even if we could agree on the right behavior. If there are no reverse dependencies, I think it's not that bad if a package would temporarily disappear from testing in cases like this one.

Don't hesitate to reopen this bug if there are arguments not mentioned in the bug report worth considering.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to