Bug#928949: unblock: s3ql/3.1+dfsg-2

On May 27, 2019 8:55:53 PM GMT+01:00, Paul Gevers wrote: >Control: tags -1 moreinfo > >Hi David, > >On Mon, 13 May 2019 15:52:56 -0400 David Gilman >wrote: >> Users who want to use s3ql with Google's cloud storage API need to >> obtain an OAuth credential with the appropriate permissions.

Bug#796947: jessie-pu: package s3ql/2.11.1+dfsg-2

On Feb 20 2016, Julien Cristau <jcris...@debian.org> wrote: > On Sat, Aug 29, 2015 at 13:46:54 -0700, Nikolaus Rath wrote: >> On Aug 29 2015, "Adam D. Barratt" <a...@adam-barratt.org.uk> wrote: >> > On Tue, 2015-08-25 at 19:29 -0700, Nikolaus Rath wrote

Bug#810136: transition: python3-defaults (python3.5 as default python3)

On Jan 06 2016, Scott Kitterman wrote: > 5. Cython3 not currently working [3]. This appears to be due to a change in > python3.5. It affects borgbackup and s3ql only. As these are rather late in > the transition, we could probably go ahead while this is getting sorted.

Bug#798589: s3ql: please allow migration to testing

Package: release.debian.org Severity: normal Hello, The s3ql package is not migrating to testing. As far as I understand, this is because it's not building on armhf. However, I think it would be a lot better to have s3ql in testing for the other archituctures than not to have it in testing at

Bug#796947: jessie-pu: package s3ql/2.11.1+dfsg-2

Hi, Please note that the majority of the patch affects only the "s3qladm upgrade" command which jessie users will either use once (and then it will have failed for them and they need this patch), or never (because they don't need it). So I think these changes have extremely little change of

Bug#798589: s3ql: please allow migration to testing

Hi Jonathan, On Sep 10 2015, Jonathan Wiltshire <j...@debian.org> wrote: > On Thu, Sep 10, 2015 at 01:00:27PM -0700, Nikolaus Rath wrote: >> The s3ql package is not migrating to testing. As far as I understand, >> this is because it's not building on armhf. > &g

Bug#796947: jessie-pu: package s3ql/2.11.1+dfsg-2

Control: tags -1 -moreinfo On Aug 29 2015, Adam D. Barratt a...@adam-barratt.org.uk wrote: Control: tags -1 + moreinfo On Tue, 2015-08-25 at 19:29 -0700, Nikolaus Rath wrote: Would it be acceptible to upload a fix for #792685 to jessie? In short, the S3QL version currently in jessie

Bug#796947: jessie-pu: package s3ql/2.11.1+dfsg-2

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Dear release managers, Would it be acceptible to upload a fix for #792685 to jessie? In short, the S3QL version currently in jessie is unable to read file system created with the

Bug#771942: now in unstable

Control: tags -1 -moreinfo The package is now in unstable. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE,

Bug#771942: unblock: python-dugong/3.3+dfsg-3

` function now knows about more kinds of temporary errors, in particular also about those that do not have a corresponding Python exception (e.g. no route to host). Closes: #771756. -- Nikolaus Rath nikol...@rath.org Wed, 03 Dec 2014 09:11:52 -0800 Debdiff against testing is attached

Bug#771879: unblock: s3ql/2.11.1+dfsg-2

or incorrectly considering storage objects as missing when the connection to remote server is interrupted. Closes: #771452. -- Nikolaus Rath nikol...@rath.org Tue, 02 Dec 2014 21:44:27 -0800 Debdiff is attached. unblock s3ql/2.11.1+dfsg-2 diff -Nru s3ql-2.11.1+dfsg/debian/changelog

Bug#745110: RM: s3ql/2.7-1

On 04/18/2014 01:35 AM, Niels Thykier wrote: Could you please remove the s3ql package from testing? It's already scheduled for autoremoval, but it'd be nice if we don't have to wait for the deadline to pass. There is a new s3ql release in unstable that fixes the RC bug of the version in

Bug#745110: RM: s3ql/2.7-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hello, Could you please remove the s3ql package from testing? It's already scheduled for autoremoval, but it'd be nice if we don't have to wait for the deadline to pass. There is a new s3ql

Bug#702728: unblock: s3ql/1.11.1-3

-0800 @@ -1,3 +1,10 @@ +s3ql (1.11.1-3) testing-proposed-updates; urgency=low + + * Call fflush() on FILE stream before repositioning underlying +file descriptor. Closes: 701350. + + -- Nikolaus Rath nikol...@rath.org Sun, 24 Feb 2013 18:51:42 -0800 + s3ql (1.11.1-2) unstable; urgency=low

Re: Uploading new s3ql to testing-proposed-updates

On 03/03/2013 10:31 PM, Adam D. Barratt wrote: On Sun, 2013-03-03 at 17:49 -0800, Nikolaus Rath wrote: Ok, I updated severity and tags of the bug and uploaded a new version to unstable that fixes the issue there. Thanks. I have put the proposed update for testing on mentors.debian.net

Re: Uploading new s3ql to testing-proposed-updates

On 02/27/2013 11:11 AM, Adam D. Barratt wrote: On Wed, 2013-02-27 at 10:18 -0800, Nikolaus Rath wrote: On 02/27/2013 05:25 AM, Adam D. Barratt wrote: On 25.02.2013 02:41, Nikolaus Rath wrote: I'd like to upload a new version of S3QL to testing-proposed-updates to fix bug #701350. Unstable

Re: Uploading new s3ql to testing-proposed-updates

Hi Adam, On 02/27/2013 05:25 AM, Adam D. Barratt wrote: On 25.02.2013 02:41, Nikolaus Rath wrote: I'd like to upload a new version of S3QL to testing-proposed-updates to fix bug #701350. Unstable already contains a newer upstream release (1.12), so I cannot upload there. The bug log

Uploading new s3ql to testing-proposed-updates

Hi, I'd like to upload a new version of S3QL to testing-proposed-updates to fix bug #701350. Unstable already contains a newer upstream release (1.12), so I cannot upload there. Essentially, a missing fflush() call when accessing a file using both a FILE* stream and a file descriptor causes data

Re: Uploading new s3ql to testing-proposed-updates

On 02/24/2013 06:41 PM, Nikolaus Rath wrote: Hi, I'd like to upload a new version of S3QL to testing-proposed-updates to fix bug #701350. Unstable already contains a newer upstream release (1.12), so I cannot upload there. Essentially, a missing fflush() call when accessing a file using