From: Luis Francisco Araujo <araujo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree
Date: Tue, 12 Jun 2007 12:05:16 -0400 [thread overview]
Message-ID: <466EC43C.7090107@gentoo.org> (raw)
In-Reply-To: <AAC967D1-766E-46E1-9A0A-A1F2B3425F12@cilly.mine.nu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
cilly wrote:
> On Jun 12, 2007, at 12:46 PM, Fernando J. Pereda wrote:
>
>> Known to be buggy versions.
>
> Of course, there are bugs in every version. Sometimes a user must be
> able to choose which bug is more problematic, i.e. the bug in the newer
> ebuild which makes the package unusable for them or the older bug which
> has a security issue the users are aware of but not present, i.e.
> prevented by firewall. A timeline of two weeks would allow the user to
> easily downgrade and if necessary put the ebuild in overlay.
Hello,
We (developers) won't immediately remove old packages versions if there
is no a good reason for it, at least in my case.
One of the main motivation for fast removal are security concerns, they
sometimes happen and they don't even get into our bugzilla database ,
but the maintainer of the package is aware of it from upstream reports,
so these might be "unknown" problems for our users.
Best recommendation is that you trust the package maintainer and report
bugs in the new packages if you find them.
Regards,
- --
Luis F. Araujo "araujo at gentoo.org"
Gentoo Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)
iD8DBQFGbsQ8aTNpke9pJcURAugPAJ9MuOmIFMzNNAx7DqKCm/ZuxLj5mACfcOf/
W3oxNo4aXWZLGlT9D5HblQ4=
=GLS5
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-12 16:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 9:40 [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree cilly
2007-06-12 9:49 ` [gentoo-dev] " Christian Faulhammer
2007-06-12 9:53 ` cilly
2007-06-12 9:59 ` [gentoo-dev] " Luca Barbato
2007-06-12 10:04 ` Fernando J. Pereda
2007-06-12 10:01 ` Fernando J. Pereda
2007-06-12 10:14 ` cilly
2007-06-12 10:21 ` Fernando J. Pereda
2007-06-12 10:30 ` cilly
2007-06-12 10:40 ` Marijn Schouten (hkBst)
2007-06-12 10:48 ` cilly
2007-06-12 11:09 ` Marijn Schouten (hkBst)
2007-06-12 10:36 ` Richard Freeman
2007-06-12 10:46 ` Fernando J. Pereda
2007-06-12 10:53 ` cilly
2007-06-12 10:59 ` cilly
2007-06-12 11:27 ` Luca Barbato
2007-06-12 11:37 ` cilly
2007-06-12 11:29 ` Christoph Mende
2007-06-12 11:38 ` cilly
2007-06-13 14:35 ` Robert Buchholz
2007-06-13 14:58 ` Brian Harring
2007-06-12 16:55 ` [gentoo-dev] " Duncan
2007-06-13 14:44 ` banym tuxaner
2007-06-12 11:03 ` [gentoo-dev] " Fernando J. Pereda
2007-06-12 11:08 ` cilly
2007-06-12 16:05 ` Luis Francisco Araujo [this message]
2007-06-12 10:48 ` Luca Barbato
2007-06-12 10:50 ` cilly
2007-06-12 11:21 ` Petteri Räty
2007-06-12 11:50 ` cilly
2007-06-12 11:00 ` Marijn Schouten (hkBst)
2007-06-12 11:25 ` [gentoo-dev] " Christian Faulhammer
2007-06-12 11:52 ` cilly
2007-06-12 12:55 ` [gentoo-dev] " Marius Mauch
2007-06-12 12:59 ` cilly
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=466EC43C.7090107@gentoo.org \
--to=araujo@gentoo.org \
--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