Your message dated Mon, 07 Oct 2019 06:34:05 +0000
with message-id <[email protected]>
and subject line Bug#941832: Removed package(s) from unstable
has caused the Debian Bug report #941339,
regarding delaboratory: Should delaboratory be removed from Debian?
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.)


-- 
941339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941339
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: delaboratory
Version: 0.8-2+b2
Severity: normal

I think it's time to remove the delaboratory package:

* upstream is inactive (last upstream activity seems to be 2013)
* package has only ever been uploaded twice, most recently 5.5 years ago
* low popcon - inst:105 vote:16
* blocker for the current wxwidgets3.0-gtk3 transition
* maintainer seems unresponsive

If there are no objections within two weeks, I'll turn this into an RM
bug.

Cheers,
    Olly

--- End Message ---
--- Begin Message ---
Version: 0.8-2+rm

Dear submitter,

as the package delaboratory has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/941832

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

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