Your message dated Fri, 03 Nov 2017 23:00:47 +
with message-id
and subject line Bug#784029: fixed in libcdio-paranoia 10.2+0.94+2-0.1
has caused the Debian Bug report #784029,
regarding RFP: libcdio-paranoia
to be marked as done.
This means that you claim that the problem has been dealt with
This is the ben config I used in Ubuntu (which successfully completed the
libcdio transition today) since the auto-libcdio ben file wasn't adequate.
title = "libcdio";
is_affected = .depends ~
/\b(libcdio16|libiso9660\-10|libcdio\-cdda\-dev|libcdio\-cdda1|libcdio\-paranoia\-dev|libcdio\-paranoia1|
Hi, I'll upload libcdio-paranoia 0.94 to experimental, because it's needed for
the libcdio 0.94 update. I don't intend to maintain this package, so feel free
to suggest yourself as an uploader or maintainer, however I'd like to see the
GCC 7 build failures fixed.
Matthias
Packaging uploaded to
http://mentors.debian.net/package/libcdio-paranoia
Builds clean in pbuilder environment.
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/canv2p
Package: wnpp
Severity: normal
Hello, the version of libcdio 0.83 in Debian is stale. The upstream libcdio-
paranoia component has been updated to use a newer cdparanoia code base and
also is now split into its own work. The maintainer of libcdio appears busy.
Please help with packaging.
--
To
5 matches
Mail list logo
