Hey,
I have been lurking following the progress on this since I discovered this bug
reported on
gvfs-backends https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886278 which I
traced back to libcdio.
And yes, as I commented there, the solution seems to get 2.0.0 out.
> As I look at Debian pack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 24 Feb 2018 19:43:50 +0200
Source: cl-mcclim
Binary: cl-mcclim cl-mcclim-examples
Architecture: source
Version: 0.9.6.dfsg.cvs20100315-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Adrian Bun
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 24 Feb 2018 19:43:50 +0200
Source: cl-mcclim
Binary: cl-mcclim cl-mcclim-examples
Architecture: source
Version: 0.9.6.dfsg.cvs20100315-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-B
cl-mcclim_0.9.6.dfsg.cvs20100315-3_source.changes uploaded successfully to
localhost
along with the files:
cl-mcclim_0.9.6.dfsg.cvs20100315-3.dsc
cl-mcclim_0.9.6.dfsg.cvs20100315-3.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Sat, 24 Feb 2018 18:04:24 +
with message-id
and subject line Bug#889184: fixed in cl-mcclim 0.9.6.dfsg.cvs20100315-3
has caused the Debian Bug report #889184,
regarding cl-mcclim-doc is empty
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Sat, 24 Feb 2018 19:04:50 +0200
with message-id <20180224170450.GD7636@localhost>
and subject line buildbot has never been backported to squeeze
has caused the Debian Bug report #705366,
regarding backport buildbot & buildbot-slave for squeeze
to be marked as done.
This means th
Your message dated Sat, 24 Feb 2018 19:00:26 +0200
with message-id <20180224170026.GC7636@localhost>
and subject line buildbot 0.8.14-1 is already in unstable
has caused the Debian Bug report #839805,
regarding new version 0.8.14 available
to be marked as done.
This means that you claim that the p
Hi -
Both of these issues were addressed in libcdio 2.0.0 and that is the way I
would recommend fixing. The reason we went from 1.1 to 2.x was because it
was pointed out that it would better follow the guidelines of semantic
version since one of the API was changed in an incompatible way. So 1.x
s
Hi!
For avoidance of doubt:
On Thu, 18 Jan 2018 16:07:37 +0100, I wrote:
> $ gdb -q --args cd-info /dev/sr1
> [...]
> CD-TEXT for Track 7:
> TITLE: The Fall
> double free or corruption (!prev)
>
> Program received signal SIGABRT, Aborted.
> $ gdb -q --ar
9 matches
Mail list logo
