Would a "still depends on libkpathsea3" bug be RC? (was: How to prevent a library transition)
- To: debian-devel@lists.debian.org
- Cc: debian-release@lists.debian.org
- Subject: Would a "still depends on libkpathsea3" bug be RC? (was: How to prevent a library transition)
- From: Frank Küster <frank@debian.org>
- Date: Thu, 29 Sep 2005 09:57:09 +0200
- Message-id: <[🔎] 87br2ci9wq.fsf_-_@alhambra.kuesterei.ch>
- In-reply-to: <20050928205918.GC24746@khazad-dum.debian.net> (Henrique de Moraes Holschuh's message of "Wed, 28 Sep 2005 17:59:18 -0300")
- References: <87br2dl5eg.fsf@alhambra.kuesterei.ch> <20050928130115.GC31262@mails.so.argh.org> <87slvpjmoc.fsf@alhambra.kuesterei.ch> <20050928205918.GC24746@khazad-dum.debian.net>
Henrique de Moraes Holschuh <hmh@debian.org> wrote:
> On Wed, 28 Sep 2005, Frank Küster wrote:
>> If my second interpretation is right, we depend on maintainers' action
>> for that. In order to make all dependencies on the old version
>> disappear, would a "still depends on libkpathsea3" bug be RC?
>
> Yes, fixable with a quick-and-dirty NMU that only does a rebuild against the
> new one...
That was what I was thinking about; but the question is whether the
release team would actually support such a severity; I don't want to
support libkpathsea3 for a long time (although AFAICT it didn't change
at all during the lifetime of teTeX-2.0.2).
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: