Hi. This blosxom bug was upgraded to RC severity recently. Alfie commented in the bug that it isn't easy to fix this and at the same time offer a clean upgrade path from previous versions. He also added that this isn't a woody->sarge upgrade bug since blosxom isn't present in woody.
Some thoughts on this: - Even if upgrades from woody->sarge aren't affected, this should probably remain RC since 1) it would definetly occour on security updates and 2) to have to fix the upgrade path for sarge->etch upgrades sounds even worse than the current situation. - Wouldn't it be preferable to fix the bug correctly right now even if this makes upgrades from the current version non-trivial since at least the current version is in no stable release. Why postpone the breakage? - Without knowing anything about blosxom, the obvious solution seems to be either 1) to move the files to /usr/lib or /usr/share and then advise the user how to copy them if he wants to change them or 2) move them to /etc and make them config files. Is this right? (a simple "no" would suffice for me at this point indicating that I need to learn more about the software) Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
