FS#1148 - pacman segfaults with existing file
Attached to Project:
Pacman
Opened by Juan Pablo (jp_leon) - Sunday, 18 July 2004, 17:03 GMT
Last edited by Judd Vinet (judd) - Wednesday, 21 July 2004, 18:16 GMT
Opened by Juan Pablo (jp_leon) - Sunday, 18 July 2004, 17:03 GMT
Last edited by Judd Vinet (judd) - Wednesday, 21 July 2004, 18:16 GMT
|
Details
pacman seg faults when upgrading module-init-tools with
other upgrades (pacman -Syu) and /etc/modprobe.devfs exists
in filesystem (i had touch'ed it to make modprobe stop
showing the error)
when i tried to upgrade the module-init-tools package alone (pacman -S module-init-tools) it failed but it didn't seg fault.. [root@wire conf]# pacman -S module-init-tools when i upgraded module-init-tools only : <code> Targets: module-init-tools-3.0-2 Proceed with upgrade? [Y/n] checking package integrity... done. loading package data... done. checking for file conflicts... error: the following file conflicts were found: /etc/modprobe.devfs: exists in filesystem errors occurred, no packages were upgraded. </code> when i upgraded all the packages : <code> [root@wire conf]# pacman -Su Targets: gimp-print-4.2.7-1 glib2-2.4.4-1 gphoto2-2.1.4-2 grub-0.95-2 gtk2-2.4.4-1 imagemagick-6.0.3-1 libgphoto2-2.1.4-2 libpcap-0.8.3-1 libusb-0.1.8-4 libxml2-2.6.11-1 libgpg-error-0.7-1 libgcrypt-1.1.94-1 libxslt-1.1.8-1 module-init-tools-3.0-2 neverball-1.3.4-1 openoffice-1.1.2-2 php-5.0.0-1 tcpdump-3.8.3-2 xmame-sdl-0.83.1-2 Proceed with upgrade? [Y/n] checking package integrity... done. loading package data... done. checking for file conflicts... Violación de segmento </code> (violación de segmento is spanish for segmentation fault) |
This task depends upon
I've started to bulk install packages by hand (there were too many) forcing the upgrade for some of them (don't remember really which ones). Afterwards, pacman didn't segfault, but stopped upgrading due to conflict errors. I'll create a new flyspray task for this - http://bugs.archlinux.org/index.php?do=details&id=1162