Bug#745736: RM: isdnutils/1:3.25+dfsg1-3.3 from testing
On 25.04.2014 01:39, Julien Cristau wrote:
> Control: tag -1 moreinfo
>
> On Thu, Apr 24, 2014 at 23:51:34 +0800, Rolf Leggewie wrote:
>
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian.org@packages.debian.org
>> Usertags: rm
>>
>> Hello,
>>
>> this is a request for removal of the isdnutils package from
>> testing by the maintainer. The reason is that its presence
>> presents the new libcapi20-3 package from migrating.
>>
> # Broken Depends:
> drdsl/non-free: drdsl [i386]
> ibod: ibod [amd64 armel armhf i386 mips mipsel powerpc s390x sparc]
> isdnactivecards/contrib: isdnactivecards [amd64 armel i386 mips mipsel
powerpc sparc]
>
> # Broken Build-Depends:
> manpages-de: isdnlog
>
> What should happen to those packages?
Julien,
thank you for the swift reaction.
Hm, I'm really at a loss about this one myself. I've been the
maintainer for isdnutils for a number of years and my main focus has
always been to get rid of the many, many hacks in isdnutils that were
somehow working, but unhealthy and unmaintainable, especially all the
hand-crafted scripting. There's been an NMU that I do not approve of
and I consider hackish. It works around a kernel problem and thus is
out of place in isdnutils. I do not want to bless that NMU with an
upload of mine. At the same time, reversing that NMU would create a
backlash and wouldn't be the right thing, either, I think. Essentially,
I am unable to upload to unstable. I've seen experimental as the only
venue left for me. I was unaware it would not be sufficient.
I carved out libcapi20-3 from the isdnutils package for greater
modularity and I'd like it to migrate to testing. In 2005, a versioned
dependency on libcapi20-3 was introduced in the pppdcapiplugin and
capiutils "Depends: libcapi20-3 (= ${binary:Version})". I've contacted
doko who apparently uploaded that change to see if that is really
necessary, I believe it's not and can be relaxed to an unversioned
dependency.
The same reason that prevents the migration is now obviously preventing
the removal of the testing package. Two things need to be done, I guess
in isdnutils in testing if the binary package cannot be temporarily
removed without too much collateral damage.
1) stop building the libcapi20-3 binary
2) relax the versioned run-time dependency above to an unversioned one
For the package to successfully migrate from unstable to testing a few
RC-bugs would need to be addressed as well, though (#745624, #725000,
#710359). I'm willing to do that work, but like I stated, I feel
precluded from doing it in unstable. I'm hoping for a suggestion on how
to move this forward in the best interest of everyone involved. How do
we get out of this situation?
Regards
Rolf
Reply to: