> What's the purpose of this bug that isn't already achieved by #413469?
>
> Cheers,
Julien, #413469 was correctly downgraded to wishlist, since that bug is only
about "The package is outdated", i.e. the developer wished to push a fresher
snapshot into etch, which is deep frozen and cannot accept that.
The articulate discussion in #413469 ended with ion3 being removed from etch,
since the developer (Tuomo) felt only ion2 belongs to a stable distribution.
Development snapshots of ion3 are included in unstable and experimental (see
http://bugs.debian.org/cgi-bin/version.cgi?package=ion3 ), so ion3 users can
choose between use a fresh snapshot in less stable distributions or the oldish
ion2 (http://bugs.debian.org/cgi-bin/version.cgi?package=ion2 ).
If I may comment as an unconcerned debian longtime "aficionado", I feel this
solution is suboptimal to users, and also to upstream. A developer should either
not care or (more likely) be proud that a random development snapshot makes its
way into debian stable "megafreeze", even though he/she has released much
fresher versions: these are accessible to anybody who cares anyway.
Concerns for bug tracking effort devoted to an old version does not seem too
serious: if I was in Tuomo's place, I'd leave to the debian package maintainer
the task of fighting the bugs of a old piece of software until he/she gets bored
enough to prefer to upgrade to a newer better version.
I hope this upstream/distribution competitive pattern remains an isolated
example. If it spreads, it has a potentiality of damaging linux in general and
debian in particular.
All the best,
Nick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
