Summary: | >=app-backup/amanda-2.6.0_p2-r4 mark stable request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MATSUU Takuto (RETIRED) <matsuu> |
Component: | New packages | Assignee: | App-Backup Team <app-backup> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | lists |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
MATSUU Takuto (RETIRED)
2009-04-01 03:09:50 UTC
I agree ... they could both be marked stable. Robin? Time to jump to 2.6 I agree. 2.5.2 caused lots of autoconf hell. arches, please compile-test and mark as stable. target keywords: amd64 ppc ppc64 sparc x86 I even use 2.6.1 here since it was released by the amanda team. But 2.6.1 itself has some known issues (already solved in trunk there) so a late 2.6.0 should get stable and with 2.6.1 we should wait for a 2.6.1p1 or something from amanda.org On sparc at least, installation is not complete because of:
==================
>>> /var/spool/amanda/.amandahosts -> /etc/amanda/amandahosts
* Creating inital Amanda file (dumpdates) in /etc
* Creating inital Amanda file (amandates) in /var/spool/amanda/amanda
touch: cannot touch `///var/spool/amanda/amanda/amandates': No such file or directory
chown: cannot access `///var/spool/amanda/amanda/amandates': No such file or directory
chmod: cannot access `///var/spool/amanda/amanda/amandates': No such file or directory
* Checking setuid permissions
* You should configure Amanda in /etc/amanda now.
==========================
I don't know if it forgets to create /var/spool/amanda/amanda, or if this should be just /var/spool.amanda.
Please advise.
fmccor: only a cosmetic error, it creates the directory and file fine during the first run anyway. However, I've fixed it in -r4 anyway, it already had the file fine if you migrated from an earlier version, just not if you did a fresh install. amd64/x86 stable ppc64 done ppc done Sparc stable and closing. |