[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#889803: add package with cd-paranoia binary



On Fri, 25 Jan 2019 00:23:22 +0100 Klaumi Klingsporn <klaumikli@gmx.de>
wrote:
> Package: cd-paranoia
> Followup-For: Bug #889803
> 
> On Tue, 14 Aug 2018 19:24:07 +0000 Niels Thykier
> <niels@thykier.net> wrote:
> > Source: libcdio-paranoia
> > Source-Version: 10.2+0.94+2-4
> > 
> > We believe that the bug you reported is fixed in the
> > latest version of libcdio-paranoia
> > ...
> >    * Remove cd-paranoia package again; the binary is also
> > provided by libcdio-utils.  (Reopens: #889803, Closes:
> > #906112)   
> 
> Dear Niels,
> 
> cd-paranoia is no longer provided in the package
> libcdio-utils >= 0.92. Version 2.0.0 is in testing
> and unstable. 
> 
> So there is no need to remove cd-paranoia from debian. There
> only needs to be set a
> "Breaks: libcdio-utils (<< 2.0.0)" 
> in the Debian/control file for the cd-paranoia package and
> upgrades from stable should work fine, without trying
> to overwrite anything.
> 
> Packages that I built with this change can be found at:
> apt.klaumikli.de/testing.
> 
> You can't ban cd-paranoia from Debian because of a missing
> Breaks-line! The binary is needed e.g. by whipper, the only
> linux-equivalent to the ExactAudioCopy-cd-ripper in the
> windows-world.
> 
> Nevertheless: Thanks for caring about this orphaned package!
> 
> Klaumi
> 
> [...]
Hi Klaumi,

I undid a faulty change I uploaded/introduced; nothing more, nothing
less.  From here the floor is open; I am not holding you (or Benjamin
back, who also showed interest in this).

However, I have spent the energy / time I was willing to use on
libcdio-paranoia for the next many years.  "Someone else(tm)" will have
to (properly) introduce the binary if they want it.  It would be even
better if they had a stake/interest in libcdio-paranoia (which I do not)
and could become the maintainer of the package.

Thanks,
~Niels


Reply to: