Your message dated Sun, 08 Jun 2014 16:00:21 +0000
with message-id <[email protected]>
and subject line Bug#711947: Removed package(s) from unstable
has caused the Debian Bug report #711947,
regarding RM: rygel [kfreebsd-i386 kfreebsd-amd64] -- ROM; most likely 
fundamentally broken on kfreebsd-*
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.)


-- 
711947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711947
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

Hello!

Previous versions of rygel has been built on kfreebsd-*.
Current version has extended the testsuite which indicated problems
on kfreebsd. Further investigations by upstream indicates problems in rygel,
the gupnp stack and even the kqueue backend in gio for filesystems events
on (k)freebsd.
I've not been able to find a single user interested in doing even basic
testing rygel on kfreebsd.....
I'd thus like to request the removal of the old kfreebsd binaries
to allow current versions of rygel to propagate to testing.

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

librygel-core-2.2-2 |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
librygel-renderer-2.2-2 |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
librygel-renderer-gst-2.2-2 |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
librygel-server-2.2-2 |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
     rygel |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
rygel-2.2-dev |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
 rygel-dbg |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
rygel-gst-launch |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
rygel-mediathek |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
rygel-playbin |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
rygel-preferences |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386
rygel-tracker |   0.22.2-1 | kfreebsd-amd64, kfreebsd-i386

------------------- Reason -------------------
ROM; most likely fundamentally broken on kfreebsd-*
----------------------------------------------

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.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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/711947

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.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to