-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam D. Barratt wrote:
> The next point release for the "etch" oldstable distribution, 4.0r9, is
> scheduled for Saturday, 22nd May.
I guess this is rather a plain "formality" than an endorsement by the
project that this release is an up-to-date versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam D. Barratt wrote:
> The next point release for the "etch" oldstable distribution, 4.0r9, is
> scheduled for Saturday, 22nd May.
I guess this is rather a plain "formality" than an endorsement by the
project that this release is an up-to-date versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 18:36, Pierre Habouzit wrote:
> No it's not. A user that prefers to have broken software rather than
> no software (if the option "non broken" software is absent) should use
> unstable. I mean it.
>
> You can easily use testing by de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-03 19:59, Pierre Habouzit wrote:
> It depends of your definition of usable. I don't think it's usable on
> a daily basis because:
FWIW, let the users decide what they use or want to use. I took a curde
estimate by counting what the reader
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 16:11, Johannes Wiedersich wrote:
> [1] search +testing +lenny on
The searches were performed without the '+' to have 'testing or lenny' etc.
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 09:59, Pierre Habouzit wrote:
> We fully address [2]: a broken software, or an inadequate one is more
> a problem to me than not having it in Debian. Debian is about quality,
> not quantity.
I totally agree on that.
My point is that i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Within their efforts to eliminate RC bugs in testing, IMHO the release
managers should not forget that removed packages are marked as
'obsolete', eg. in aptitude.
An ordinary user who uses update-* to check for updates and who installs
other packages
7 matches
Mail list logo
