This one time, at band camp, Christian Schulte said: > Of course you could do something about it. You are the package > maintainers. As such, you stand between upstream and the debian > distribution. Its a debian package maintainer's job to decouple the > distribution from upstream development somehow, I think, and not to > blindly follow upstream development. Whatever upstream decides, there > is no reason to remove functionality from a stable program via > volatile. You could have left the old clamav-milter untouched instead > of replacing it. We are talking about how volatile and stable go > together and that's well stated on the volatile website. I would never > have expected volatile to break anything. It now did. For the first > time since years, I admit.
Clamav isn't the kind of project where it's easy to mix and match different parts from different releases, even if we wanted to do so. I'm sorry the milter doesn't do what you want in this release. Unfortunately, we are going to follow upstream on this issue. If you want to see functionality that you depend on stay in the software, you are able to follow upstream development and make sure it isn't removed by submitting patches and/or bug reports. Again, I'm very sorry, but you're venting in the wrong place. We are volunteers doing our best to make a great OS, but we don't have the time to actively work against our upstreams for a minority use case. If you are angry with upstream, take it there. Or, possibly, be productive about it and help them to enable the functionality you feel you need. Cheers, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [email protected] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
_______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-clamav-devel
