Re: Deprecating (and deactivation) of an archive feature?!
Joerg Jaspert <firstname.lastname@example.org> writes:
> Now, the idea would be to deprecate this feature, used by 8 packages in
> unstable, dropping complications in the database backend and the pool
> layout which we would want to avoid.
> Yes, it would require those packages to have a new (additional, maybe
> stripped to be smaller) source tarball for the one package in the other
> component. Well. 8 of them. A very tiny set compared to the whole
> archive, and the question is there if that really means we have to keep
I have no opinion one way or the other on the change, but wanted to note
that Lintian had previously warned about this and we removed the warning
at the request of one of the maintainers of those packages. (Bdale, I
think, although I'm not sure.) So this feature is being intentionally
used at present.
>  this would also work with non-free. And by policy the source has to
> be in the more-free component.
Lintian only allows the main to contrib cross; non-free will always get
warnings. The relevant tag is section-category-mismatch. (lintian.d.o
doesn't check contrib or non-free, so I don't know if that tag appears
anywhere in the archive. It doesn't appear for any packages in main,
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>