Summary: | app-backup/rsnapshot-1.3.1 fails to upgrade from 1.3.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Doug Goldstein (RETIRED) <cardoe> |
Component: | New packages | Assignee: | Erik Hahn <erik_hahn> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | yngwin |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
config.log
rsnapshot-1.3.1.ebuild |
Description
Doug Goldstein (RETIRED)
2008-09-12 22:45:55 UTC
Created attachment 165308 [details]
config.log
config.log from compile
The only reason for that erro I can imagine is "test" failing. Can you check if if "test -e foo" in bash actually returns the correct exit code (0 if file exists, 1 if it doesn't)? As a workaround, you could extract rsnapshot.conf.example from the tarball and copy it to /etc/rsnapshot.conf, it should work then. cardoe@stewie ~ % test -e foo cardoe@stewie ~ % echo $? 1 cardoe@stewie ~ % touch foo cardoe@stewie ~ % test -e foo cardoe@stewie ~ % echo $? 0 Can you kick this one to upstream? nvm.... it turns out I'm using userpriv and the Portage user does not have permissions to read that file... Created attachment 165659 [details]
rsnapshot-1.3.1.ebuild
I've added a check if rsnapshot.conf is readable so the ebuild gives a meaningful error message. Yngwin, please commit or comment.
|