Steve Langasek a écrit :
severity 413469 serious
reopen 413469
thanks
[...]
After discussing on IRC with Joey and other ion users, it seems that there
isn't really much demand for ion3 in a stable release after all; those I've
talked to who use ion3 all say they run testing or unstable on their
desktops, and Joey notes that the ion3 upgrade path from sarge to etch isn't
likely to be a smooth one anyway.
So under the circumstances, it does seem reasonable to defer to upstream
(and the former maintainer) on this point. I've tagged the ion3 package and
its reverse-dependencies for removal from etch.
Steve, why did you reopen this bug? As I said in a previous message,
this RFE is done and the request to remove ion3 should be made in a new
report. This is particularly important since the report is now
excessively long.
Unless you have a good reason, please close this report again and open a
new one.
Thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
