Bug#840555: guile-2.0: New upstream release 2.0.13 available

[Rob Browning]

Antonio Ospite  writes:

> Package: guile-2.0
> Version: 2.0.11+1-12+b1
> Followup-For: Bug #840555
>
> Dear Maintainer,
>
> the CVE fixes are also in the new upstream release 2.0.13
>
> Packaging that _might_ also help with getting the lilypond package in
> shape for Stretch[1], since guile 2.0.12 contains some fixes to bugs
> exposed by lilypond (e.g. [2]).

Thanks.  I've already backported both of the CVE fixes for a possible
jessie update, and after I file the relevant proposal with the release
managers, I'm planning to prepare a 2.0.13 upload for unstable.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#840555: guile-2.0: New upstream release 2.0.13 available

[Antonio Ospite]

Package: guile-2.0
Version: 2.0.11+1-12+b1
Followup-For: Bug #840555

Dear Maintainer,

the CVE fixes are also in the new upstream release 2.0.13

Packaging that _might_ also help with getting the lilypond package in
shape for Stretch[1], since guile 2.0.12 contains some fixes to bugs
exposed by lilypond (e.g. [2]).

Thanks,
   Antonio

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005
[2] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19883

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages guile-2.0 depends on:
ii  guile-2.0-libs  2.0.11+1-12+b1

guile-2.0 recommends no packages.

Versions of packages guile-2.0 suggests:
pn  guile-2.0-doc  

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?