blob: 6dc0d7688ccc5f52f0ccfc87f254834b56b69b6b (
plain)
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
|
# ChangeLog for net-misc/s3cmd
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/net-misc/s3cmd/ChangeLog,v 1.13 2011/04/05 19:08:57 arfrever Exp $
05 Apr 2011; Arfrever Frehtes Taifersar Arahesis <arfrever@gentoo.org>
s3cmd-0.9.9.91.ebuild, s3cmd-1.0.0.ebuild:
Fix dependencies, use Python 2 (bug #315841).
*s3cmd-1.0.0 (14 Jan 2011)
14 Jan 2011; Thilo Bangert <bangert@gentoo.org> -s3cmd-0.9.8.4.ebuild,
-s3cmd-0.9.9.ebuild, +s3cmd-1.0.0.ebuild:
version bump - remove old
16 Jul 2010; Christian Faulhammer <fauli@gentoo.org>
s3cmd-0.9.9.91.ebuild:
stable x86, bug 326641
06 Jul 2010; Markos Chandras <hwoarang@gentoo.org> s3cmd-0.9.9.91.ebuild:
Stable on amd64 wrt bug #326641
*s3cmd-0.9.9.91 (25 Jan 2010)
25 Jan 2010; Thilo Bangert <bangert@gentoo.org> +s3cmd-0.9.9.91.ebuild:
version bump (#302113)
23 Feb 2009; Jeremy Olexa <darkside@gentoo.org> s3cmd-0.9.9.ebuild:
add ~amd64 kw, bug 259739
*s3cmd-0.9.9 (19 Feb 2009)
19 Feb 2009; Thilo Bangert <bangert@gentoo.org> +s3cmd-0.9.9.ebuild:
version bump
02 Feb 2009; Thilo Bangert <bangert@gentoo.org> -s3cmd-0.9.4.ebuild,
-s3cmd-0.9.7.ebuild:
remove old/buggy versions
*s3cmd-0.9.8.4 (30 Jan 2009)
30 Jan 2009; Thilo Bangert <bangert@gentoo.org> metadata.xml,
+s3cmd-0.9.8.4.ebuild:
version bump - fixes bug #241304 - assume maintainership
*s3cmd-0.9.7 (22 Jun 2008)
22 Jun 2008; Jeremy Olexa <darkside@gentoo.org> +s3cmd-0.9.7.ebuild:
Version bump. bug #212010
12 Mar 2008; Christian Heim <phreak@gentoo.org> metadata.xml:
Removing Josh Glover (jmglov, #206782) from metadata.xml.
13 Feb 2008; Christian Faulhammer <opfer@gentoo.org> metadata.xml:
add no-herd
*s3cmd-0.9.4 (23 Sep 2007)
23 Sep 2007; Josh Glover <jmglov@gentoo.org> +metadata.xml,
+s3cmd-0.9.4.ebuild:
This package was submitted by Josh Glover in bug #193380
|