Debian Bug report logs - #784855
pytrainer disappeared from repositories (jessie and up)

Toggle useless messages

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

From: Mateusz Kijowski <mateusz.kijowski@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: pytrainer disappeared from repositories (jessie and up)

Date: Sat, 09 May 2015 18:16:46 +0200

Package: pytrainer
Severity: grave
Justification: renders package unusable

The pytrainer package seems to have disappeared from the Archive. The PTS
https://packages.qa.debian.org/p/pytrainer.html suggests that the reason for
removal is that the package was missing from unstable, right after the message
that 1.10.1-3 has been accepted in unstable, so perhaps this is some automation
error?

What is the reason for removal of this package?



-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

From: Christian PERRIER <bubulle@debian.org>

To: Mateusz Kijowski <mateusz.kijowski@gmail.com>, 784855@bugs.debian.org

Subject: Re: Bug#784855: pytrainer disappeared from repositories (jessie and up)

Date: Sun, 10 May 2015 08:04:20 +0200

[Message part 1 (text/plain, inline)]

Quoting Mateusz Kijowski (mateusz.kijowski@gmail.com):
> Package: pytrainer
> Severity: grave
> Justification: renders package unusable
> 
> The pytrainer package seems to have disappeared from the Archive. The PTS
> https://packages.qa.debian.org/p/pytrainer.html suggests that the reason for
> removal is that the package was missing from unstable, right after the message
> that 1.10.1-3 has been accepted in unstable, so perhaps this is some automation
> error?
> 
> What is the reason for removal of this package?


If only I knew.... I digged through the mail archives and found about
the removal back in August 2014. But I can't find the reason for it.

Two days after, I uploaded 1.10.1-4 to unstable, but the upload was
rejected because it was a source only upload (something I'm doing
since it is possible) but the package had to go through NEW.

Sadly, I then forgot to upload *again* so that it goes through
NEW. That was mostly because all this happened in the middle of August
and my own holidays....

I will upload to unstable ASAP (I'm in the process of reorganizing my
build machine so it will take a few days). But that won't make
pytrainer reappear in jessie, I'm afraid. Those people who want it on
jessie systems will have to install it manually from the unstable
version. Sorry for the trouble.

[signature.asc (application/pgp-signature, inline)]

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

From: Jens Reyer <jre.winesim@gmail.com>

To: 784855@bugs.debian.org, Christian PERRIER <bubulle@debian.org>

Subject: Re: Bug#784855: pytrainer disappeared from repositories (jessie and up)

Date: Thu, 24 Sep 2015 16:05:50 +0200

control: severity -1 normal

Hi

> pytrainer disappeared from repositories (jessie and up)
> Severity: grave
> Justification: renders package unusable

Somewhat ironic, but I guess this bug report prevents pytrainer to
reenter testing due to its RC severity. Therefore I downgrade it to normal.
I hope it is ok that I tamper with this bug's severity. After looking at
the buglog I do this in the best faith.

Looking at the release-migration site [1] a missing "python:any" is
mentioned, but I guess this is a bug in the site, not relevant to pytrainer.

Let's see what's next in the story of pytrainer-not-in-stable.

Greets
jre


[1]:
https://release.debian.org/migration/testing.pl?package=pytrainer

Why is package X not in testing yet?

Checking pytrainer

pytrainer has no old version in testing (trying to add, not update)

pytrainer (source, amd64, i386, arm64, armel, armhf, mips, mipsel,
powerpc, ppc64el, s390x) has new bugs!

Dependency analysis (including build-depends; i386 only):

pytrainer depends on python:any << 2.8 which is not available in testing
  python:any is not available in Debian

pytrainer depends on python:any >= 2.7.5-5~, which is not available in
testing
  python:any is explained above

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

From: Christian PERRIER <bubulle@debian.org>

To: Jens Reyer <jre.winesim@gmail.com>

Cc: 784855@bugs.debian.org

Subject: Re: Bug#784855: pytrainer disappeared from repositories (jessie and up)

Date: Thu, 24 Sep 2015 18:37:05 +0200

[Message part 1 (text/plain, inline)]

Quoting Jens Reyer (jre.winesim@gmail.com):
> control: severity -1 normal
> 
> Hi
> 
> > pytrainer disappeared from repositories (jessie and up)
> > Severity: grave
> > Justification: renders package unusable
> 
> Somewhat ironic, but I guess this bug report prevents pytrainer to
> reenter testing due to its RC severity. Therefore I downgrade it to normal.
> I hope it is ok that I tamper with this bug's severity. After looking at
> the buglog I do this in the best faith.


Good catch and sorry for missing this myself....:-(

[signature.asc (application/pgp-signature, inline)]

Message #27 received at 784855-done@bugs.debian.org (full text, mbox, reply):

From: Christian PERRIER <bubulle@debian.org>

To: Jens Reyer <jre.winesim@gmail.com>, 784855-done@bugs.debian.org

Subject: Re: Bug#784855: pytrainer disappeared from repositories (jessie and up)

Date: Thu, 24 Sep 2015 18:39:13 +0200

[Message part 1 (text/plain, inline)]

Quoting Jens Reyer (jre.winesim@gmail.com):
> control: severity -1 normal
> 
> Hi
> 
> > pytrainer disappeared from repositories (jessie and up)
> > Severity: grave
> > Justification: renders package unusable
> 
> Somewhat ironic, but I guess this bug report prevents pytrainer to
> reenter testing due to its RC severity. Therefore I downgrade it to normal.
> I hope it is ok that I tamper with this bug's severity. After looking at
> the buglog I do this in the best faith.


And, of course, we can now close this bug report.

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.