Severity: serious Justification: makes package unusable (by its dependencies)
> bumping SONAMES is a good thing for often needed packages and if > upstream provides SONAME support, I will include it. That is good. > The current solution (with conflicts) is okay. No, it is not. You break every package that depends on guichan every time you upgrade. Fixing this is too much to ask of those maintainers. You have forced balder2d and sear out of testing. I have asked debian mentors about this last month. I sent you a link to the thread archive a while ago. Here it is again, in case you didn't get around to reading it: http://lists.debian.org/debian-mentors/2007/09/msg00223.html They recommended that bugs such as this be kept as serious or grave. I think the best way to fix this would be to only include a static library. It is sort of like washing your hands of the issue. I would also recommend not upgrading the version more than once a year, unless a new upstream version fixes a glaring bug. If compiling statically, depending packages will still break when the API changes, and it has changed before. I am not sure how acceptable this is. You could fix it by following upstream's recommendation, which would equate to not having a guichan package at all. Depending programs would instead include the guichan source. If you need advice on what to do next, I recommend writing to the debian-mentors mailing list. You can learn more here: http://lists.debian.org/debian-mentors/ -Brandon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
