Debian Bug report logs - #870990
RM: jitsi -- RoQA; missed both jessie and stretch

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@debian.org>

To: submit@bugs.debian.org

Subject: jitsi: should jitsi be removed from unstable?

Date: Sun, 06 Aug 2017 09:50:12 -0400

Source: jitsi
User: debian-qa@lists.debian.org
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: jitsi -- RoQA; missed both jessie and stretch
  thanks

- Lucas, for the QA team.


[1] https://lists.debian.org/debian-qa/2017/07/msg00021.html

Message #16 received at 870990-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 870990-close@bugs.debian.org

Cc: jitsi@packages.debian.org, jitsi@packages.qa.debian.org

Subject: Bug#870990: Removed package(s) from unstable

Date: Mon, 07 Aug 2017 17:24:17 +0000

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

     jitsi | 2.4.4997-1.2 | source, all
     jitsi | 2.5.5313-1 | source, all
jitsi-common | 2.5.5313-1 | all
 jitsi-jni | 2.5.5313-1 | amd64
libjitsi-jni | 2.4.4997-1.2 | i386

------------------- Reason -------------------
RoQA; missed both jessie and stretch
----------------------------------------------

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 870990@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/870990

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

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

Send a report that this bug log contains spam.