Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16013 - [udev] invalid backup array

Attached to Project: Arch Linux
Opened by Xavier (shining) - Saturday, 05 September 2009, 09:22 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 07 September 2009, 06:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

backup=(etc/udev/udev.conf
etc/scsi_id.config
etc/udev/cdsymlinks.conf
etc/modprobe.d/framebuffer_blacklist.conf)

but etc/scsi_id.config and etc/udev/cdsymlinks.conf are not in udev package
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 07 September 2009, 06:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  udev-146-2
Comment by Roman Kyrylych (Romashka) - Saturday, 05 September 2009, 09:26 GMT
I think they were left to support upgrade from old udev versions.
But how old? Tobias, can we safely remove them now?
Comment by Xavier (shining) - Saturday, 05 September 2009, 09:55 GMT
keeping files in backup does not do anything, except creating stalled entries in pacman local database
in any cases the old files should be saved to pacsave
Comment by Tobias Powalowski (tpowa) - Sunday, 06 September 2009, 16:29 GMT
Ok cdsymlinks seems not to be used by anything anymore.
The scsi_id.config is still read by scsi_id program according to the manual page.
So removing just cdsymlinks from backup array should be fine.
Comment by Xavier (shining) - Sunday, 06 September 2009, 17:22 GMT
The fact that the file might be on the filesystem or not is irrelevant.
If it is not in the package, pacman simply won't touch it ever.

The rule is pretty simple and brain-dead : file in backup array <-> file in package
The future version of makepkg will simply break on pkgbuilds which does not respect this rule (see  FS#13551 )
Comment by Dan McGee (toofishes) - Sunday, 06 September 2009, 17:22 GMT
It makes no sense to keep files in the backup array that don't exist in a package. When pacman upgrades a package, it uses the old filelist and old backup array to decide whether to keep a pacsave file, and not the new backup array.
Comment by Tobias Powalowski (tpowa) - Monday, 07 September 2009, 05:59 GMT
ahh, thanks for clarification, removing the file.

Loading...