FS#22402 - New syslinux packages in testing overwrites /boot/syslinux/syslinux.cfg

Attached to Project: Arch Linux
Opened by Pascal Ernster (hardfalcon) - Tuesday, 11 January 2011, 16:04 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 11 January 2011, 16:56 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The new syslinux package in testing overwrites /boot/syslinux/syslinux.cfg with it's own version of the file. This is completely unacceptable, existing config files should *never* be replaced when installing or upgrading a package. This is Archlinux, not Debian, we let the user take care of his config files instead of fucking them up automagically upon the installation of a package.

Additional info:
* Affected packages: syslinux 4.03-2 (from the testing repository)

Steps to reproduce:
Install/upgrade the syslinux package, you will find that your /boot/syslinux/syslinux.cfg (if you had one before the package was installed/upgraded) was overwritten with the syslinux.cfg from the package.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 11 January 2011, 16:56 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see last comment
Comment by Ionut Biru (wonder) - Tuesday, 11 January 2011, 16:09 GMT
it doesn't rewrite any config. the previous version didn't had any file, which means that a pacman -Syu would get a conflict.

i guess you used -f and this is completely unacceptable
Comment by Janno (JannoT) - Tuesday, 11 January 2011, 16:17 GMT
error: failed to commit transaction (conflicting files)
syslinux: /boot/syslinux/syslinux.cfg exists in filesystem
Errors occurred, no packages were upgraded.

No magical overwrite for me :(
This is completely unacceptable!!!
Comment by Pascal Ernster (hardfalcon) - Tuesday, 11 January 2011, 16:50 GMT
First of all, sorry for my harsh voice, I got carried away a little by the fact that my system didn't boot up anymore.

Hmm, I just checked it again, seems I can't reproduce my bug. I have no idea what happened here, but I know for a fact that something fiddled with my bootloader. I'll try to find out what it was, but I guess this bug can be closed for now.

Sorry for the mess again. :/

Loading...