Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#22107 - Previously valid backup=() now invalid in makepkg
Attached to Project:
Pacman
Opened by Anonymous Submitter - Wednesday, 15 December 2010, 09:36 GMT
Last edited by Allan McRae (Allan) - Monday, 27 December 2010, 10:28 GMT
Opened by Anonymous Submitter - Wednesday, 15 December 2010, 09:36 GMT
Last edited by Allan McRae (Allan) - Monday, 27 December 2010, 10:28 GMT
|
DetailsMy packages are now complaining about the form of the backup=() entry when I use makepkg. I've always used relative file names, although I haven't in the past enclosed them in quotes. To try to fix this I have tried every possible combination e.g. for my radvd package -
backup=(etc/$pkgname/radvd.conf) backup=("etc/$pkgname/radvd.conf") backup=('etc/$pkgname/radvd.conf') backup=('etc/radvd/radvd.conf') backup=('etc/radvd.conf') # not valid for my package, but I tested it anyway All of the above alternatives give the following message - ==> WARNING: Invalid backup entry : <backup filename> According to the PKGBUILD manual page, at least one of the above should be correct. I have a number of packages that would suffer from this problem. I've looked in what I think are the obvious places as to how to fix this, or what has changed, but can't find anything. How do I fix my packages? |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 27 December 2010, 10:28 GMT
Reason for closing: Implemented
Additional comments about closing: Warning messages clarified in commit 68d8bfa0
Monday, 27 December 2010, 10:28 GMT
Reason for closing: Implemented
Additional comments about closing: Warning messages clarified in commit 68d8bfa0
A more informative error/warning message would have also been more helfpul in makepkg.
"Why would you backup a non-existent file?"
Well, after the user has installed the package, without a configuration file, they'll create a configuration file so they can use the package. Then a file now exists to be backed up if the package is removed.
To my mind, the word "backup" means keep "this" data if there is any chance it would be removed, because I might want to use it again - hence backing up/keeping a configuration file that didn't exist at package installation. If I removed the backup() entry for /etc/radvd/radvd.conf, would that file be deleted if the package was removed?
My fear was that if the package didn't know about the file in the e.g. /etc/radvd subdirectory, it would delete the subdirectory, and therefore the file, when the package was removed. My thinking was that putting the non-existent configuration file in the backup() entry would ensure that the file wouldn't be deleted.
http://projects.archlinux.org/pacman.git/commit/?id=68d8bfa0