It is not easy to workaround, as it requires manual fixing of several clean build environments like pbuilder chroots. It requires touching of the Build-Depends line, which is also just stupid to handle buggy package dependencies. To fix such an issue, nobody in the world will agree to you to "fix" this in the Build-Depends field. Please show me such an example. You fix issues in jaunty-updates, which are of much less priority or severity of this bug. Your hint to "pressed CDs" and "frozen archives" - shall I really comment these arguments?
About stability: We talk about a small library with exactly 4 or 5 rdepends, which can be easily tested (even by your own). I don't run any Ubuntu workstation and I won't want to run one, so I'm not going to test this myself. And disagreeing with you is not a violation of any code of conduct. Closing a report that is clearly about Jaunty with a hint to the unreleased Karmis is stupid and/or insulting. You can decide for your own, what you would think. Karmic is not (yet) relevant for *any* production system. And for the software (bluefish 1.3), for which I build packages for Ubuntu users, it won't even become this year, beacuse I cannot expect every user to switch in a short time period after a new release. -- libgucharmap-dev misses dependency on libgconf2-dev https://bugs.launchpad.net/bugs/436944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
