Jeroen van Wolffelaar a écrit :
On Wed, Sep 20, 2006 at 05:08:09PM -0400, Filipus Klutiero wrote:
unblock 382907 with 370436
unblock 384179 with 370436
unblock 378751 with 370436
unblock 378752 with 370436
severity 382907 serious
Removal bugs are not release-critical, and not 'serious'.
I can't argue much with that. If the presence of a RC-buggy package in
the archive that should be removed isn't a serious issue for you, we
have different standards and I'll let you do your triaging.
Please don't
severity-ping-pong -- both myself as member of the FTP-master team as
Adam Barratt who's for quite a while helpfully triaging bugs on
'ftp.debian.org' have set it to normal before.
Quick call; nobody explained what you just explained before.
thanks
As Jeroen pointed out in #370436 a while ago, mozilla won't be removed from
the archive until a suitable replacement (i.e. seamonkey) is in etch with a
transition plan in place.
This isn't exactly what Jeroen stated. Quoting him:
It shouldn't just be removed and leaving users without an
upgrade path.
I don't interpret this "shouldn't" as a "won't", but rather as a
"shouldn't at this moment". And this moment is already 5 weeks ago,
during which not much concrete evolution happened to my knowledge, so
Jeroen's comment is of limited relevance now.
My comment is still current, nothing changed: seamonkey didn't enter
Debian yet, so there's still no migration path. I fail to see how 'not
much evolution' actually changes this situation. Feel invited to work on
seamonkey's packaging though to ensure something is changing.
"not much evolution" doesn't change the situation. "5 weeks ago" does.
Since this time, it is almost certain that some grave mozilla security
vulnerabilities were disclosed. See
http://www.mozilla.org/projects/security/known-vulnerabilities.html#seamonkey1.0.5
for issues solved by Seamonkey 1.0.5. What has changed (or not...) is
that at this point Mozilla is so outdated that security advisories won't
even mention it (as can be guessed from the fact that none of the 6
issues fixed by Seamonkey 1.0.5 mention the Mozilla suite).
On that basis, this is just a quick ping to confirm that these bugs will
not
be actioned until mozilla has actually been removed.
If it's not obvious that the blocking is the other way around, see what
happened in testing.
Reverting these changes.
Adam had it the correct way. I see no reason to remove locale packages
when the package they provide locales for is still there, and on the
other hand, the existance of locale packages will not hold up the
removal, as it's obviously coupled.
I'm not saying there's a reason to remove locale packages when the
package they provide locales for is still there, but the presence of
mozilla doesn't block the locale packages from being removed. If you see
a point in representing the coupling, a merge could be appropriate.
I'm not enough aware of the
differences mozilla vs seamonkey, but perhaps those locale packages
'just' need an update to work for seamonkey instead of mozilla, instead
of being removed?
Seems uselessly risky. Mozilla is a trademark.
Anyway, not relevant yet as long as mozilla is still
here.
--Jeroen
