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#15328 - Bad entry in minitcpio.conf cause kernel 2.6.30 installation failure

Attached to Project: Arch Linux
Opened by Damien Solimando (dsolimando) - Wednesday, 01 July 2009, 06:15 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 01 July 2009, 10:53 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: the raid-partitions hook entry in /etc/mkinitcpio.conf made the kernel 2.6.30 package failed ton install.
Without be carefull, a reboot after the distri update make the system unbootable.

Changing raid-partition with mdadm solve the problem. The question is why mkinitcpio.conf has not been modified.


This task depends upon

Closed by  Roman Kyrylych (Romashka)
Wednesday, 01 July 2009, 10:53 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Wednesday, 01 July 2009, 06:41 GMT
pacman does not touch configuration files.
Comment by edac val (edacval) - Wednesday, 01 July 2009, 06:54 GMT
Confirm it
Comment by Roman Kyrylych (Romashka) - Wednesday, 01 July 2009, 10:53 GMT
@Damien: such changes are announced (unless forgotten) on archlinux.org main page and arch-announce mailing list,
or in post_upgrade message during package installation.
Pacman will not fix your hook list automagically.

A quick google search revealed this as the first result:
http://bbs.archlinux.org/viewtopic.php?id=70808
with a link to http://www.archlinux.org/pipermail/arch-dev-public/2009-March/010567.html
and http://repos.archlinux.org/viewvc.cgi/mdadm/trunk /PKGBUILD?r1=22215&r2=29447
and from here we can go to http://repos.archlinux.org/viewvc.cgi/mdadm/trunk/mdadm.install?view=markup
which shows clearly that a warning is displayed during mdadm upgrade, which you've missed at that time.

Loading...