File: NEWS

package info (click to toggle)
s3ql 3.0+dfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 3,020 kB
  • sloc: python: 15,998; makefile: 125; sh: 37; ansic: 22
file content (87 lines) | stat: -rw-r--r-- 3,194 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
s3ql (2.27.1+dfsg-1) unstable; urgency=medium

  The internal file system revision has changed. File systems created
  with S3QL 2.27 or newer are not compatible with prior S3QL
  versions. To update an existing file system to the newest revision,
  use the `s3qladm upgrade` command.

 -- Nikolaus Rath <Nikolaus@rath.org>  Sat, 09 Jun 2018 11:53:26 +0100

s3ql (2.17+dfsg-1) unstable; urgency=medium

  The internal file system revision has changed. File systems created
  with S3QL 2.17 or newer are not compatible with prior S3QL
  versions. To update an existing file system to the newest revision,
  use the `s3qladm upgrade` command.

 -- Nikolaus Rath <Nikolaus@rath.org>  Thu, 10 Mar 2016 08:13:37 -0800

s3ql (2.14+dfsg-1) unstable; urgency=medium

  The internal file system revision has changed. File systems created
  with S3QL 2.14 or newer are not compatible with prior S3QL
  versions. To update an existing file system to the newest revision,
  use the 's3qladm upgrade' command.

 -- Nikolaus Rath <Nikolaus@rath.org>  Wed, 12 Aug 2015 14:57:22 -0700

s3ql (2.10.1+dfsg-1) unstable; urgency=medium

  The internal file system revision has changed. File systems created
  with S3QL 2.10 or newer are not compatible with prior S3QL
  versions. To update an existing file system to the newest revision,
  use the 's3qladm upgrade' command.

  It is strongly recommended to run the (new) s3ql_verify command with
  the --data option at shortly after the upgrade. This is necessary to
  ensure that the upgrade to the next (2.11) S3QL release will run
  smoothly.

 -- Nikolaus Rath <Nikolaus@rath.org>  Sun, 03 Aug 2014 20:49:06 -0700

s3ql (2.5-1) unstable; urgency=low

  * The file system structure has changed, existing file systems
    need to be upgraded using "s3qladm upgrade" before they can
    be used.

 -- Nikolaus Rath <Nikolaus@rath.org>  Sat, 19 Oct 2013 16:34:46 -0700

s3ql (1.11-1) unstable; urgency=low

  * The file system structure has changed, existing file systems
    need to be upgraded using "s3qladm upgrade" before they can
    be used.

 -- Nikolaus Rath <Nikolaus@rath.org>  Sun, 29 Apr 2012 15:23:20 -0400

s3ql (1.9-1) unstable; urgency=low

  * The file system structure has changed, existing file systems
    need to be upgraded using "s3qladm upgrade" before they can
    be used.

 -- Nikolaus Rath <Nikolaus@rath.org>  Sat, 21 Jan 2012 13:49:59 -0500

s3ql (1.7-1) unstable; urgency=low

  * The file system structure has changed, existing file systems
    need to be upgraded using "s3qladm upgrade" before they can 
    be used.

 -- Nikolaus Rath <Nikolaus@rath.org>  Sun, 27 Nov 2011 16:43:06 -0500

s3ql (1.4-1) unstable; urgency=low

  Notes for upgrading from version 1.0 or earlier:
  ------------------------------------------------

  * The file system structure has changed, existing file systems
    need to be upgraded using "s3qladm upgrade" before they can 
    be used.

  * The format and default name of the authentication file has
    changed. The default location is now ~/.s3ql/authinfo2. 
    Please refer to the documentation for the file format.

 -- Nikolaus Rath <Nikolaus@rath.org>  Thu, 06 Oct 2011 11:25:44 -0400