Pacman

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.
Tasklist

FS#3228 - Pacman backup behaviour not consistent

Attached to Project: Pacman
Opened by Tom Killian (tomk) - Sunday, 25 September 2005, 14:42 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I upgraded two packages from [community], slim and hibernate-script. The PKGBUILDs for both specified a single config file i.e.

backup=(etc/slim.conf)

and

backup=('etc/hibernate/hibernate.conf')

However, hibernate.conf was not saved. Only slim.conf was saved to slim.conf.pacsave.
This task depends upon

Closed by  arjan timmerman (blaasvis)
Sunday, 26 March 2006, 10:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  in 2.9.8 this is fixed... none of any modified version will be deleted when upgrading.
Comment by Łukasz Fibinger (lucke) - Sunday, 25 September 2005, 22:01 GMT
Was that 'new' hibernate.conf any different from the one from the version prior to upgrading (or actual hibernate.conf file)?

If you're not familiar with pacman's config files policy, read an appropriate section in man pacman.
Comment by Tom Killian (tomk) - Monday, 26 September 2005, 06:50 GMT
The current and upgraded hibernate.conf files were significantly different. Thanks for the suggestion though.
Comment by Judd Vinet (judd) - Sunday, 02 October 2005, 18:01 GMT
Hi Tom,

I know it's hard to do after the fact, but it would be really helpful if you could reproduce this scenario and show me the output from pacman when you upgrade with the --verbose switch.

Then pacman will show you the md5sums of each backup file and why it's making the choices it is.
Comment by Tom Killian (tomk) - Sunday, 02 October 2005, 18:18 GMT
Thanks Judd - leave it with me. I have the previous version of both apps in the cache still, so I'll downgrade, then upgrade again --verbosely.
Comment by Tom Killian (tomk) - Sunday, 02 October 2005, 20:30 GMT
Here's the verbose pacman output:

Targets: hibernate-script-1.10-3 slim-1.2.3-2

Total Package Size: 0.3 MB

Proceed with upgrade? [Y/n] hibernate-script-1.10-3.pkg.tar.gz is already in the cache
slim-1.2.3-2.pkg.tar.gz is already in the cache

checking package integrity... done.
loading package data... reading /var/cache/pacman/pkg/hibernate-script-1.10-3.pkg.tar.gz... done
reading /var/cache/pacman/pkg/slim-1.2.3-2.pkg.tar.gz... done
done.
checking for file conflicts... done.
upgrading hibernate-script... removing old package first...
running "/sbin/ldconfig -r /"
extracting files...
Updating database...done.
done.
upgrading slim... Executing pre_upgrade script...
echo "umask 0022; source /tmp/pacman-uOTYeO/.INSTALL pre_upgrade 1.2.3-2 1.2.3-1" | /usr/sbin/chroot / /bin/bash
removing old package first...
running "/sbin/ldconfig -r /"
extracting files...
checking md5 hashes for /etc/slim.conf
current: fbd6e59709683ab3105e5be791c3e0da
new: ebe614b359738553b297f9cbdf15fd35
original: fbd6e59709683ab3105e5be791c3e0da
action: installing new file
Updating database...done.
done.
Executing post_upgrade script...
echo "umask 0022; source /var/lib/pacman/local/slim-1.2.3-2/install post_upgrade 1.2.3-2 1.2.3-1" | /usr/sbin/chroot / /bin/bash
running "/sbin/ldconfig -r /"

If it's relevant, Jason Chu also responded on the mailing list, as follows:

<snip>
Dibble, I assume you maintain hibernate. Did you just add the backup
line? There's a "feature" in pacman that files aren't backed up unless
the version installed on the system has the backup entry. So, if you
add a backup entry, the time you upgrade to that package will overwrite
the conf file. All upgrades afterwards won't.
</snip>

Loading...