Re: Uploading new s3ql to testing-proposed-updates

To: Nikolaus Rath <nikolaus@rath.org>
Cc: <debian-release@lists.debian.org>, Laszlo Boszormenyi <gcs@debian.hu>
Subject: Re: Uploading new s3ql to testing-proposed-updates
From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
Date: Wed, 27 Feb 2013 13:25:29 +0000
Message-id: <0b2a0bf690992f4ea6ad29d8dbe7bc7a@mail.adsl.funky-badger.org>
In-reply-to: <512ACF44.4050105@rath.org>
References: <512ACF44.4050105@rath.org>

On 25.02.2013 02:41, Nikolaus Rath wrote:

I'd like to upload a new version of S3QL to testing-proposed-updatesto
fix bug #701350. Unstable already contains a newer upstream release
(1.12), so I cannot upload there.

The bug log for #701350 implies that a) it doesn't affect the versionof s3ql in wheezy and b) it has yet to be fixed in sid. Is either orboth of those implications correct?


Regards,

Adam

Reply to:

Follow-Ups:
- Re: Uploading new s3ql to testing-proposed-updates
  - From: Nikolaus Rath <Nikolaus@rath.org>

References:
- Uploading new s3ql to testing-proposed-updates
  - From: Nikolaus Rath <Nikolaus@rath.org>

Prev by Date: Bug#701697: marked as done (unblock: cyrus-imapd-2.4/2.4.16-3)
Next by Date: Bug#701811: unblock: cups/1.5.3-2.15
Previous by thread: Re: Uploading new s3ql to testing-proposed-updates
Next by thread: Re: Uploading new s3ql to testing-proposed-updates
Index(es):
- Date
- Thread