blob: 95a80834023e03aa337953bd71c73bf27d28af92 (
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
|
# ChangeLog for app-arch/unarj
# Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/app-arch/unarj/ChangeLog,v 1.18 2005/02/06 18:21:29 corsair Exp $
06 Feb 2005; Markus Rothe <corsair@gentoo.org> unarj-2.63a-r2.ebuild:
Stable on ppc64
29 Dec 2004; Markus Rothe <corsair@gentoo.org> unarj-2.63a-r2.ebuild:
Added ~ppc64 to KEYWORDS
18 Nov 2004; Olivier Crete <tester@gentoo.org> unarj-2.63a-r2.ebuild:
Stable on x86 wrt 70966
16 Nov 2004; Simon Stelling <blubb@gentoo.org> unarj-2.63a-r2.ebuild:
stable on amd64 ; bug #70966
16 Nov 2004; Bryan Østergaard <kloeri@gentoo.org> unarj-2.63a-r2.ebuild:
Stable on alpha, bug 70966.
15 Nov 2004; Gustavo Zacarias <gustavoz@gentoo.org> unarj-2.63a-r2.ebuild:
Stable on sparc wrt #70966
15 Nov 2004; <SeJo@gentoo.org> unarj-2.63a-r2.ebuild:
stable on ppc gsla: 70966
*unarj-2.63a-r2 (14 Nov 2004)
14 Nov 2004; <solar@gentoo.org> +files/unarj-2.65-CAN-2004-0947.patch,
+files/unarj-2.65-sanitation.patch, +unarj-2.63a-r2.ebuild:
security bump - CAN-2004-0947 - bug 70966
24 Nov 2003; Aron Griffis <agriffis@gentoo.org> unarj-2.63a-r1.ebuild:
Mark stable on alpha
*unarj-2.63a-r1 (13 Feb 2003)
29 Jun 2003; Daniel Ahlberg <aliz@gentoo.org> :
Added missing changelog entry.
06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
*unarj-2.63a (04 Nov 2002)
04 Nov 2002; Nick Hadaway <raker@gentoo.org> unarj-2.63a-r1.ebuild,
files/digest-unarj-2.63a-r1 :
Added IUSE="" and changed ebuild so unarj is installed in /usr/bin.
*unarj-2.63a (19 Jul 2002)
14 Aug 2002; Pieter Van den Abeele <pvdabeel@gentoo.org> :
Added ppc keyword
19 Jul 2002; Ryan Phillips <rphillips@gentoo.org> ChangeLog :
Added initial ChangeLog which should be updated whenever the package is
updated in any way. This changelog is targetted to users. This means that the
comments should well explained and written in clean English. The details about
writing correct changelogs are explained in the skel.ChangeLog file which you
can find in the root directory of the portage repository.
|