Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes: > You should either add conflicts to the latest packages so that there > comes no file conflict, or alternatively, forget about it, as it was a > snafu in a version no longer in the archive; and tell people who still > complain that they are running unstable and that breakeage like this can > happen from time to time -- after all, it's fixed now, and for upgrades > from stable/testing to unstable, right?
I've been doing the latter anyway, and the former will suddenly become necessary to deal with a different mistake anyhow. > Assuming forgetting about it is what you want, I'm closing this bug. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
