From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12 Description of problem: Very frustating: When the installer is about to finish, this happens: python: ./rpmio_internal.h:522: c2f: Assertion 'fd && fd->magic == 0x04463138' failed. The installer brings the computer to a halt: "It is now safe to reboot your computer" - or something to that effect Version-Release number of selected component (if applicable): anaconda-10.2.0.19-1.ppc How reproducible: Always Steps to Reproduce: 1. Install on a ppc from download.fedora.redhat.com/pub/fedora/linux/core/development/ppc Actual Results: Installer dies right at the end, which is really frustrating. Expected Results: Installer does not die right at the end, which is a big relief. Additional info:
This is _probably_ caused by a bad tree.
When did you mirror the tree - so I can try and replicate here. Can you give me the buildstamp/discinfo so I can ensure I'm testing against the correct tree. I've done a ppc install based off a tree built between 19 and 20 February, which installs fine. From a full tree: cat .discinfo From boot.iso: mount -o loop boot.iso /mnt zcat /mnt/ppc/mac/ramdisk.image.gz > /tmp/ramdisk.image umount /mnt cd /tmp; cpio -ivd .buildstamp < ramdisk.image cat .buildstamp
Unfortunately, I didn't take a snapshot of the tree. I installed directly from download.fedora.redhat.com/pub/fedora/linux/core/development/ppc over http. Thus, if the tree has changed since then, I can not replicate the problem. The .discinfo at this writing (2005-02-21 15:14 MST) reads: 1108985286.752955 Fedora Core 4 ppc 1,2,3,4 Fedora/base Fedora/RPMS Fedora/pixmaps FWIW
This same error has just happened during package download when I ran yum -y update. yum is yum-2.1.13-1.ppc
Is this reproducible with yum? Can you narrow down the package it is failing at (try yum -d 5 -y update. Can you check using rpm -K the contents of /var/cache/yum/development/packages rpm -K /var/cache/yum/development/packages/*rpm | grep NOT
Closing due to inactivity. If this issue still occurs with current releases, please reopen and set the release in which you've encountered the problem.