[hardy]: reinstalling kernel from -proposed/p.u.c makes silo.conf vanish

Bug #351572 reported by StefanPotyra
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,

noticed this as a side-effect of testing fixes for bug #349655:

installing
* linux-image-2.6.24-24-sparc64-smp_2.6.24-24.51_sparc.deb
* linux-image-sparc64-smp_2.6.24.24.26_sparc.deb
* linux-restricted-modules-2.6.24-24-sparc64-smp_2.6.24.16-24.57_sparc.deb
* linux-ubuntu-modules-2.6.24-24-sparc64-smp_2.6.24-24.38_sparc.deb
from hardy-proposed, then
http://people.ubuntu.com/~smb/bug349655/linux-image-2.6.24-23-sparc64-smp_2.6.24-23.52b349655v1_sparc.deb

made silo.conf disappear (i.e. it was a symlink after that to non-existing /boot/silo.conf, not too sure if it was a symlink before, but at least it was present). Other silo files that should have resided in /boot (*.b) were missing as well, just as if silo would have somehow being uninstalled -- even though it was still marked as installed).

There were a few more side-conditions (e.g. I manually purged a few older kernels, and space in boot was a little bit low), but I can say for sure that after these actions silo.conf was still existing.

After installing the package from p.u.c, I rebooted, maybe that might chime in as well (can't say if after the reboot, but before installing the -proposed packages again silo.conf was still present).

Anyway reinstalling silo and taking silo.conf from a backup easily fixed the problem for me.

Cheers,
    Stefan.

Revision history for this message
StefanPotyra (sistpoty) wrote :

hm... this is strange, I cannot reproduce this in any way again. Maybe this was just a false alarm, and I've somehow purged silo :/.
Sorry for the noise.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Stefan,

Lets go ahead and close this for now. If you are able to reproduce, please feel free to reopen. Thanks.

Changed in linux (Ubuntu):
status: New → Invalid
Revision history for this message
StefanPotyra (sistpoty) wrote :

Sure thing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.