Debian Bug report logs - #764758
RM: canto -- ROM; buggy, abandoned upstream

Toggle useless messages

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

From: Vincent Legout <vincent@legout.info>

To: submit@bugs.debian.org

Subject: RM: canto -- ROM; buggy, abandoned upstream

Date: Fri, 10 Oct 2014 17:05:21 -0400

Package: ftp.debian.org
Severity: normal

Hi,

Please remove canto from Debian unstable. The current version is buggy
and has been obsoleted upstream. This request is also seconded by
upstream.

Thanks,
Vincent

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

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

To: 764758-close@bugs.debian.org

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

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

Date: Sat, 11 Oct 2014 16:05:19 +0000

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

     canto |   0.7.10-4 | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc

------------------- Reason -------------------
ROM; buggy, abandoned 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 764758@bugs.debian.org.

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

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)

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

From: Henri Salo <henri@nerv.fi>

To: 764758@bugs.debian.org

Cc: Vincent Legout <vincent@legout.info>

Subject: Question

Date: Sat, 11 Oct 2014 20:28:22 +0300

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Where did you get this "This request is also seconded by
upstream" information? Web site http://codezen.org/canto-ng/ does not say
anything about it being abandoned status. New section in that page contains
new posts.

- ---
Henri Salo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlQ5aLYACgkQXf6hBi6kbk9PNgCdGa2p3fHaUAhUFUJUzjnOfiDQ
NccAoK4EB8MLOWzzIda7xgn1os7kG25j
=ERx8
-----END PGP SIGNATURE-----

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

From: Vincent Legout <vincent@legout.info>

To: Henri Salo <henri@nerv.fi>

Cc: 764758@bugs.debian.org

Subject: Re: Question

Date: Sat, 11 Oct 2014 13:44:26 -0400

Hi,

Henri Salo <henri@nerv.fi> writes:

> Where did you get this "This request is also seconded by
> upstream" information? Web site http://codezen.org/canto-ng/ does not say
> anything about it being abandoned status. New section in that page contains
> new posts.

Jack Miller contacted me in private and requested that canto should be
removed from Debian unstable. I thought he was right, the current
version of canto should not be part of the next Debian release because
it's too buggy. That's why I opened this bug.

But you're right, canto is still alive upstream but the version which
was in Debian was several years old and not supported upstream
anymore. The new upstream version is a complete rewrite of canto, and as
I don't use canto anymore, I had no plan to create a new package for
this new version.

Vincent

Send a report that this bug log contains spam.