Community Packages

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#11122 - [preload 0.6.3-1] updating the package overwrite your /var/lib/preload/preload.state

Attached to Project: Community Packages
Opened by solsTiCe (zebul666) - Tuesday, 05 August 2008, 13:17 GMT
Last edited by Jaroslaw Swierczynski (swiergot) - Saturday, 09 August 2008, 12:16 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Jaroslaw Swierczynski (swiergot)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
when upgrading preload to 0.6.3-1, it simply overwrites without any guilt your /var/lib/preload/preload.state.
it does not even create a .pacnew for this file ...

is this because there is a new format for this file ?? i doubt it

what is expected:
(1) either create a .pacnew file for this file but that 's not really usefull
(2) better only create that file if it does not exists from the install script. is it even necessary because preload create that file automatically ?

i guess i am the only one affected by this bug, because the only one to have preload.state in /var/lib. thnx for me :-(

think of future release of your package !

This task depends upon

Closed by  Jaroslaw Swierczynski (swiergot)
Saturday, 09 August 2008, 12:16 GMT
Reason for closing:  Fixed
Comment by Jaroslaw Swierczynski (swiergot) - Tuesday, 05 August 2008, 14:38 GMT
Why do you think you're the only one with preload.state in /var/lib/preload? Anyway, sorry for that, my fault.

I will take your second solution. Although preload indeed creates the file itself, it does it with the default mask so the file ends up with 644. I guess it may be bad for privacy of users. So to sum it up, the following changes are going to be made:

1. Don't include the state file and the log file in the package.
2. Upon package installation create the state file and chmod it 640.
3. When upgrading from version earlier than 0.6.3-2 back up the state file in pre-upgrade and restore it in post-upgrade (because pacman will remove it seeing that it's not in the new package).
4. Upon package removal display a message saying that the state file and the log file are still there.

Is that ok with you?
Comment by solsTiCe (zebul666) - Tuesday, 05 August 2008, 15:46 GMT
if i run preload with no preload.state it creates one when you stop it. here it gives it 660 permission. and if i chmod the file to something else, it revert it to 660
so isn't it better to not create the file at all in the install script ?

you need to take of preload.state if the package is removed too. by removing that file ?? tricky question ? and how ?

may be the simple thing is to add that file to backup array ?

well, do as you like. and what you think it is the best
may be stating that the file is still there is too much ?

isn't it an arch policy for that somewhere ? how do other package deal with that ?

Loading...