Bug#672820: transition: libcdio

On Wed, Jun 13, 2012 at 09:08:48PM +0200, Julien Cristau wrote: > Thanks for your patience. It should be fine to go ahead now. #676100 > will need to be fixed, but that may just mean dropping the > libxmmsclient-ruby* packages. Ok, thanks. I just uploaded libcdio 0.83-4 to unstable. Cheers, -

Bug#672820: transition: libcdio

Hi KiBi, On Mon, May 14, 2012 at 12:19:57AM +0200, Cyril Brulebois wrote: > Hi Nicolas, > > does it mean the API didn't change much, That's true. > and that you test-rebuilt those packages? Unfortunately not. I test-rebuilt vcdimager (which lead me to patching libcdio to revert a change in i

Bug#672820: transition: libcdio

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear release team, I'd like to upload a recent libcdio to unstable. Unfortunately, as usual with libcdio, upgrading from 0.81 to 0.83 means breaking the ABI and changing the sonames of t

libcdio transition

Dear release team, I'd like to upload a recent libcdio to unstable. Unfortunately, as usual with libcdio, upgrading from 0.81 to 0.83 means breaking the ABI and changing the sonames of the libcdio-cdda, libcdio-paranoia, libcdio and libiso9660 libraries... FWIW, here is the list of (source pack

libcdio transition

Hi, The new libcdio in still waiting in unstable, after 32 days, although all depending packages have been successfully rebuilt against it (according to https://buildd.debian.org/transitions/summary.html). As far as I understand it, this is because some maintainers of depending packages (such a

Re: libcdio transition

Hi, On Thu, Jul 23, 2009 at 11:22:40AM +0200, Luk Claes wrote: > Nicolas Boullis wrote: >> >> On Wed, Jul 22, 2009 at 10:38:03AM +0200, Luk Claes wrote: >>> For vlc on sparc it might not be a bad idea to have a look why it >>> failed there. >> >> I

Re: libcdio transition

Hi, On Wed, Jul 22, 2009 at 10:38:03AM +0200, Luk Claes wrote: > > For vlc on sparc it might not be a bad idea to have a look why it failed > there. I just tried to build both vlc 0.9.9a-3+b1 and 1.0.0-1 on my sparc box. Both times, I had build failures because of /usr/include/scsi/scsi.h mis

Re: libcdio transition

Hi, On Sat, Jul 11, 2009 at 12:23:42PM +0200, Luk Claes wrote: > Nicolas Boullis wrote: > > > > Hence, I just uploaded libcdio 0.81-4 to unstable (I uploaded packages > > for i386, powerpc and sparc). Now, I think you can schedule binNMUs. > > Scheduled. What'

Re: libcdio transition

Hi, On Fri, Jul 03, 2009 at 01:08:22AM +0200, Luk Claes wrote: > Nicolas Boullis wrote: > > Cheers, > > > > On Wed, Jul 01, 2009 at 08:03:20AM +0200, Luk Claes wrote: > >> If you are sure that there are no API changes, then please upload to > >> unst

Re: libcdio transition

Hi, On Fri, Jul 03, 2009 at 01:08:22AM +0200, Luk Claes wrote: > > Just manually checking the builds of all reverse build dependencies with > the new version on one arch would also be fine. OK, I'll give it a try as soon as I can (hopefully within a few days). Cheers, Nicolas signature.asc

Re: libcdio transition

Cheers, On Wed, Jul 01, 2009 at 08:03:20AM +0200, Luk Claes wrote: > > If you are sure that there are no API changes, then please upload to > unstable and tell us when you did so we can schedule binNMUs (as it does > not seem to interfere with existing transitions). I just played with diff over

libcdio transition

Dear release team, I'd like to upload a recent libcdio to unstable. Unfortunately, as usual with libcdio, upgrading from 0.78.2 to 0.81 means breaking the ABI and changing the sonames of the libcdio and libiso9660 libraries... FWIW, here is the list of (source packages of) packages that depend

daemons that keep open file descriptors for the terminal

Hi, I have found a few daemons that, when started, keep open file descriptors on the terminal. I think this is very annoying because when one starts or restarts such a daemon through a ssh connexion, then it would not close cleanly. As far as I understand what a daemon is, they are supposed to c

Re: libcdio stable update for CVE-2007-6613

Hi Nico and others, On Sun, Jan 20, 2008 at 02:31:39PM +0100, Nico Golde wrote: > Hi, > the following CVE (Common Vulnerabilities & Exposures) id was > published for libcdio some time ago. > > CVE-2007-6613[0]: > | Stack-based buffer overflow in the print_iso9660_recurse function in > | iso-info

Re: em8300 REMOVED from testing

Hi, On Mon, Jan 14, 2008 at 04:39:13PM -0700, Debian testing watch wrote: > FYI: The status of the em8300 source package > in Debian's testing distribution has changed. > > Previous version: 0.16.3-1 > Current version: (not in testing) > Hint:

Please unblock isync/1.0.3-3

Hi, isync 1.0.3-3 only adds a po-debconf translation. No other change. Please unblock it. Cheers, Nicolas signature.asc Description: Digital signature

Please unblock em8300/0.16.0-2

Hi, em8300 0.16.0-2 adds and updates a few translations and fix a significant typo in a debconf template. No code chage. Please unblock it. Cheers, Nicolas signature.asc Description: Digital signature

Re: will you allow a new em8300 in?

Hi, On Tue, Dec 19, 2006 at 08:59:43AM +0100, Luk Claes wrote: > Nicolas Boullis wrote: > >Hi, > > > >One month ago, em8300 was removed from testing, because of #342377, with > >the following comment from Steve Langasek: > > > ># long-standing brokenness,

Please unblock isync/1.0.3-2.1

Hi, isync 1.0.3-2.1 is a translation-only update over 1.0.3-2 (NMU by Christian Perrier with my permission). Please unblock it. Nicolas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

will you allow a new em8300 in?

Hi, One month ago, em8300 was removed from testing, because of #342377, with the following comment from Steve Langasek: # long-standing brokenness, can get back in if maintainer gets the new upstream version packaged Now, a package for the new upstream version is mostly packages (I'd still l

Re: Etch frozen!

Hi, On Tue, Dec 12, 2006 at 01:47:09AM +0100, Luk Claes wrote: > > > Now, a question about a package of mine: will you allow isync 1.0.3-2 > > in? > > Yes, unblock hint added. Thanks! :-) > Updates that only include RC bug fixes, translation or documentation updates > are fine. But I will h

Re: Etch frozen!

Hi, First of all, congratulations for freezing etch, that's very good news! :-) Now, a question about a package of mine: will you allow isync 1.0.3-2 in? Before I uploaded to unstable, I asked you (the list) and Steve replied it was alright. As a summary, it is a new upstream release that so

Re: new updtream release for isync

Hi Steve and others; On Mon, Nov 20, 2006 at 05:52:25PM -0800, Steve Langasek wrote: > > Yes, with the understanding that late-introduced RC bugs in the new version > may cause the package to be removed from the etch release completely. In case this upload introduces RC bugs, re-uploading a pack

Please allow libcdio/vcdimager to enter testing

Hi, Can you please hint britney that libcdio/0.76-1 and vcdimager/0.7.21-2 should be considered together for the unstable->testing propagation? Thanks, Nicolas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]