Your message dated Sun, 06 Aug 2017 04:45:35 +0000
with message-id <>
and subject line Bug#869366: Removed package(s) from unstable
has caused the Debian Bug report #869366,
regarding RM: creepy -- ROM; Unmaintained upstream
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Severity: normal

Creepy has failed to make it into any of the previous 2 Debian releases despite
the efforts of Petter Reinholdtsen (mainly) and myself.

Although upstream merged some of our Debianisation (and other) patches
initially, they have stopped responding to our prompts. The repo has not been
touched for 2 years now.

Until the major work is done to convert Creepy from QT4 to QT5, it will not be
possible to install Creepy in Debian. This issue has been closed as "won't fix"

There are also many other issues with the instagram/twitter etc. plugins that
are not being responded to. Creepy is pretty useless without these plugins.


Ross (on behalf of Petter Reinholdtsen & the GIS Team)

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

    creepy |    1.4.1-5 | source, all

------------------- Reason -------------------
ROM; Unmaintained upstream

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

The full log for this bug can be viewed at

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

Debian distribution maintenance software
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to