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#1058 - Srcpac 0.2-1 to 0.2.1-1 and srcpac.conf

Attached to Project: Arch Linux
Opened by Miroslaw Czachor (forest76) - Saturday, 03 July 2004, 13:40 GMT
Last edited by Judd Vinet (judd) - Saturday, 03 July 2004, 16:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jason Chu (jason)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

While upgrade srcpac.conf is overwriting without notice.
This task depends upon

Closed by  Jason Chu (jason)
Thursday, 09 December 2004, 03:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in version 0.3. I actually ended up using a pre_upgrade script.
Comment by Jason Chu (jason) - Saturday, 03 July 2004, 18:02 GMT
You'd think I would have set a config file to be backed up.

I can change it, but it will overwrite it for one more update. Should I make the update now and overwrite everything again? or make it later, next time, when people may have forgotten?
Comment by Miroslaw Czachor (forest76) - Sunday, 04 July 2004, 12:22 GMT
> You'd think I would have set a config file to be backed up.
> I can change it, but it will overwrite it for one more update.
I think you can resolve this problem with many ways, for example:
1) Ignored it now, and fix it when other important updates have been made, and add info messages before install process.
2) PACMAN HAVE PRE_INSTALL() SCRIPLET (from 2.8 version, thank's Judd), you can use this function for makes backup srcpac.conf automaticly.

Greetings,
Miroslaw.
Comment by Jason Chu (jason) - Sunday, 04 July 2004, 21:42 GMT
I will probably go with option 1.

Option 2 is really only a temporary solution across one update. What if the users don't upgrade to that version and upgrade to the next? Then the pre_install script won't be run and they'll lose their config.

I dislike pre_install scripts in general.

Loading...