Re: Why are new package versions depending on libc6 in unstable?
Michael Stone <mstone@debian.org> wrote:
> On Tue, Nov 19, 2002 at 05:26:04PM -0500, Daniel Jacobowitz wrote:
>>This has been hashed out before. I recommend list archives to you,
>>friend, for the last time I had to explain this.
> I've seen the topic come up before, but I've never seen a convincing
> rationale for the current behavior.
[...]
Hello,
I know two rationales, and imho both of themn are convincing.
The main point is that it is needed for propagation of library
upgrades to testing. New version of libfoo (source-package producing
libfoo1 and libfoo-dev) can only propagate to testing and replace the
old version if there is nothing in testing that requires the old
version. If you don't build with sid this will never happen. You could
work around this and e.g. change testing fundamentally to keep old
library-packages around without source package, but the
workarounds don't help with reason2:
We want the _libraries_ to be tested, *before* they move to testing.
cu andreas
Reply to: