From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: last rite of dev-python/elixir
Date: Thu, 6 Jun 2013 10:32:16 +0000 (UTC) [thread overview]
Message-ID: <pan$51cad$7cd7e883$3d9ff129$f99073a6@cox.net> (raw)
In-Reply-To: 20130606175516.7ef1bd4d@archtester.homenetwork
IAN DELANEY posted on Thu, 06 Jun 2013 17:55:16 +0800 as excerpted:
> # Ian Delaney <idella4@gentoo.org> (06 Jun 2013)
> # Masked for removal in ~ 30 days. Upstream inactive dev-python/elixir
Where's the bug reference one would normally expect to see with such an
announcement?
AFAIK, simply inactive upstream hasn't traditionally been enough to
trigger removal, as long as the package still builds and has no serious
bugs, and is still either legally mirrored and redistributable, or
remains legally available from an otherwise inactive upstream.
Of course if there's serious bugs (including that it's no longer
available to build in the first place), that's an entirely different
matter, but then there should be a reference to such bugs in the
announcement/mask, and there was no such reference in this case.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next parent reply other threads:[~2013-06-06 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130606175516.7ef1bd4d@archtester.homenetwork>
2013-06-06 10:32 ` Duncan [this message]
2013-06-06 11:19 ` [gentoo-dev] Re: last rite of dev-python/elixir Markos Chandras
2013-06-06 18:38 ` Peter Alfredsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$51cad$7cd7e883$3d9ff129$f99073a6@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox