Your message dated Thu, 7 Sep 2017 16:12:50 +0200
with message-id <[email protected]>
and subject line fso-common is gone from unstable
has caused the Debian Bug report #870930,
regarding fso-common: should fso-common be removed from unstable?
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.)
--
870930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870930
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: fso-common
User: [email protected]
Usertags: qa-removals-post-stretch
Hi,
Following a discussion[1] on the debian-qa@ mailing list on packages that
missed both jessie and stretch, I am proposing the removal of this package from
unstable, because:
it was in unstable at the time of the stretch freeze
but wasn't part of stretch
AND
it was in unstable at the time of the jessie freeze
but it wasn't part of jessie
AND
it is still not in testing
AND
it was not uploaded since the beginning of 2017.
If you disagree and think that this package should remain in unstable, feel
free to just close this bug.
If this bug is still open one month from now (on 2017-09-06), it will be turned
into a removal request, using:
reassign -1 ftp.debian.org
retitle -1 RM: fso-common -- RoQA; missed both jessie and stretch
thanks
- Lucas, for the QA team.
[1] https://lists.debian.org/debian-qa/2017/07/msg00021.html
--- End Message ---
--- Begin Message ---
closing the remaining bugs
Andreas
--- End Message ---
