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#10698 - update 2008.06-2 for filesystem overwrite configuration files

Attached to Project: Arch Linux
Opened by Stephane Souque (finss) - Thursday, 19 June 2008, 12:22 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 20 June 2008, 16:58 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture x86_64
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: the update of filesystem overwrite files passwd, fstab, group, shadow and profile from /etc with 'base' configs and not my own config. Fortunately i've made a backup from my entire /etc folders and can replace right files in place with rescueCd system.


Additional info:
* package version(s) : update from filesystem-2008.03-2-x86_64.pkg.tar.gz to filesystem-2008.06-2-x86_64.pkg.tar.gz ( i'm with archlinux testing repositery for an x86_64 computer )
* config and/or log files etc.


Steps to reproduce : ...
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 20 June 2008, 16:58 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Problem with reporter's pacman database. See comments for details.
Comment by Glenn Matthys (RedShift) - Thursday, 19 June 2008, 13:05 GMT
Can you supply the relevant parts out of pacman.log?
Comment by Stephane Souque (finss) - Thursday, 19 June 2008, 13:10 GMT
here a sample of pacman.log
   pacman.log (2.8 KiB)
Comment by Aaron Griffin (phrakture) - Thursday, 19 June 2008, 18:33 GMT
Hmm, this should never happen. Unless your md5sums were borked.

In case you didn't notice, however, pacman didn't overwrite them, it moved them out of the way (to .pacorig files)
Comment by Dan McGee (toofishes) - Thursday, 19 June 2008, 18:38 GMT
  • Field changed: Category (Packages: Testing → Packages: Core)
  • Field changed: Severity (Critical → Low)
[2008-06-19 11:08] starting full system upgrade
[2008-06-19 11:09] warning: /etc/fstab saved as /etc/fstab.pacorig
[2008-06-19 11:09] warning: /etc/group saved as /etc/group.pacorig
[2008-06-19 11:09] warning: /etc/passwd saved as /etc/passwd.pacorig
[2008-06-19 11:09] warning: /etc/shadow saved as /etc/shadow.pacorig
[2008-06-19 11:09] warning: /etc/resolv.conf saved as /etc/resolv.conf.pacorig
[2008-06-19 11:09] warning: /etc/profile saved as /etc/profile.pacorig
[2008-06-19 11:09] installed filesystem (2008.06-2)

Note that you didn't actually *upgrade* filesystem, you *installed* it. This means one of two things- you either uninstalled the filesystem package at some point, or the filesytem local DB entry somehow disappeared. Compare the above 'installed' entry to one that says 'upgraded'.

I would try grepping your pacman.log for any more entries related to the 'filesystem' package and see what you can come up with to determine how this happened.
Comment by Glenn Matthys (RedShift) - Friday, 20 June 2008, 11:18 GMT
I upgraded the filesystem package today (it's in core already) and cannot reproduce this.
Comment by Aaron Griffin (phrakture) - Friday, 20 June 2008, 16:20 GMT
I think this is a one-off error. As Dan pointed out, the local DB was corrupt somehow (hence the 'installing' instead of 'upgrading').

I don't think there's anyway we can actually address this, as pacman behaved exactly as it should and DID move the files to pacorig files as a safety net

Loading...