Anaconda-devel April 2006

anaconda-devel@lists.fedoraproject.org

27 participants
30 discussions

corrupt package message during FC5 install from NFS.
by Aggarwal, VikasX 21 Apr '06

21 Apr '06

Hi, I am trying to do install from NFS of a custom distribution which is based on FC5test3. After formatting the local drive the anaconda-installer shows message - "The package traceroute-1.0.4-1.2.i386 cannot be opened. This is due to missing file or perhaps the corrupt package. If you are installing from CD media this usually means the CD is corrupt, or the CD drive is unable to read media". I tried to check the internal checksum of each package with the -K option to rpm, based on an article from http://www.linuxjournal.com/article/6473 cd /Fedora5test3/ONE_CD/RedHat/RPMS rpm --import /usr/share/rhn/RPM-GPG-KEY rpm -K *.rpm | grep "NOT *OK" For all the packages I get " (GPG) NOT OK MISSING KEYS ". My build system is FC5. What could be wrong with my install tree? Please provide ideas about troubleshooting the above anaconda error message or otherwise why "rpm -K" will say MISSING KEYS. Thanks for help -vikas

2 1

Fedora 5 om POER5
by Josef Mádl 21 Apr '06

21 Apr '06

Hello to all, I am trying to install fedora 5 on IBM i5 system. Instalation start, all seems to good to partitioning disk. Fedora see two disks /dev/sda (real disk - virtual disk prepared with CRTNWSSTG) and /dev/sdb (booting disk of instalation - Prep). I choise /dev/sda for creating linux partitions, fedora show me how it will be parted but try to write to /dev/sdb - it ends with error. Do anybody know how solved this problem ? I can send detail error from anaconda. Josef

2 1

Re: Frustrated with a Custom FC5 Dist CD's
by Dan Carpenter 20 Apr '06

20 Apr '06

My scripts are attached. Lightly tested... 1) Download all the ISOs to /home/yourname/whatever/ 2) cd /home/yourname/whatever/ 3) ./unpack.sh 4) (Optional) Modify /usr/lib/anaconda-runtime/splittree.py for whatever size ISOs you want. 5) Edit this section in repack.sh ######################## ARCH=x86_64 PRODUCT="Fedora 5 Respin 1" VERSION=5 RELEASE=1 SHORT_NAME="FC" COMPONENT=FedoraRespin #No idea what this is for really... ######################## 6) ./repack.sh 7) Have a small "I Respun Fedora" party. regards, dan carpenter

1 0

Frustrated with a Custom FC5 Dist CD's
by Matt Paine 19 Apr '06

19 Apr '06

Firstly my apologies for questions that may seem simple for some people on the list. After years of working with Redhat (6.3 and onwards) I thought It would be fun for a challenge and try building a custom distro, you know the ones, updated rpm's etc. Anyway, after getting completely frustrated trying with FC4, I gave up until FC5 came out. So I've been trying and trying ever since day one of FC5, but still no luck. I'm not receiving any errors during the build process, and the build cd's boot okay, but as soon as it gets to the install part it spits the cd out and asks for the correct cd (No Fedora Core CD was found which matches your boot media. Please insert......). I checked out the .discinfo file and it looks exactly like (except for the datestamp) the one on the original cd. Could someone please let me know what could be going on. I have one script that runs the build process....... ===============8<====================== #!/bin/bash ARCH=i386 SOURCE=/home/fedora/public_html/fc5 BUILD=/home/fedora/public_html/mswfc5 PKGORDER=$BUILD-pkgorder.txt # clean rm -fr ${BUILD}* cp -la ${SOURCE} ${BUILD} /usr/lib/anaconda-runtime/pkgorder ${BUILD} ${ARCH} Fedora > ${PKGORDER} /usr/lib/anaconda-runtime/buildinstall --comp mswfc5 --pkgorder ${PKGORDER} --version 5 --product "Fedora Core" --release "Fedora Core" --prodpath Fedora --discs "1,2,3,4,5" ${BUILD} /usr/lib/anaconda-runtime/splittree.py --arch=${ARCH} --total-discs=5 --bin-discs=5 --src-discs=0 --release-string="Fedora Core" --pkgorderfile=${PKGORDER} --distdir=${BUILD} --srcdir=${BUILD}-SRPMS --productpath=Fedora mkisofs -R -J -T -no-emul-boot -boot-load-size 4 -boot-info-table -V "Fedora Core" -A "Fedora Core" -P "Fedora Core" -p "Fedora Core" -b isolinux/isolinux.bin -c isolinux/boot.cat -o ${BUILD}-disc1.iso ${BUILD}-disc1/ for i in 2 3 4 5 ; do mkisofs -R -J -T -V "Fedora Core" -A "Fedora Core" -P "Fedora Core" -p "Fedora Core" -o ${BUILD}-disc${i}.iso ${BUILD}-disc${i}/ done; =========================>8============= I would have loved to work this out myself but I've been trying lots of things and nothing has been working, and there seems limited information through the archive. Thankyou for any help. Matt

4 12

need help wiht boot cd
by Mark Hammerton 19 Apr '06

19 Apr '06

I am using red hat etherprise linux v4 i finally created a boot cd that will boot up and it uses the ks.cfg file on the cd so it does a complete install with out me beiing there. however after i install it instructs me to reboot and when i go to reboot it doesnt come grub starts to load and but nothing is install except a few folders under the root directory but no files or any of the packages are install before i reboot i checked the red hat installation screen and go this off of it *not all packages in hdlist had order tag File descriptor 3 left open the file descriptor on list from 1 until 31 No volume groups found these ar eth errors that i see on the screen from. can anyone help me out as to what they think my problem may be. everything would be greatly appreciated

1 0

Mexico City Goverment Distro
by Ricardo Gastelum 15 Apr '06

15 Apr '06

Distro based on FC4 Mexico City Goverment www.softwarelibre.tlalpan.gob.mx Yeah!!!

1 0

RE: Problem building anaconda on RHEL 4
by Shawn Starr 14 Apr '06

14 Apr '06

Try disabling diet libc in the Makefile.inc. Shawn. -----Original Message----- From: anaconda-devel-list-bounces(a)redhat.com on behalf of James Olin Oden Sent: Fri 4/14/2006 3:55 PM To: anaconda-devel-list(a)redhat.com Cc: Subject: Problem building anaconda on RHEL 4 Hi All, I'm trying to build anaconda (the SRPM, and its binary RPMS) on RHEL 4 and I'm gettting a peculiar error, when it tries to link loader: anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x2b9): In function `entryDraw': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x2cc): In function `entryDraw': anaconda: : undefined reference to `mbtowc' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x329): In function `entryDraw': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x342): In function `entryDraw': anaconda: : undefined reference to `mbtowc' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x559): In function `previous_char': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x568): In function `previous_char': anaconda: : undefined reference to `mblen' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x599): In function `next_char': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x5a8): In function `next_char': anaconda: : undefined reference to `mblen' anaconda: collect2: ld returned 1 exit status It looks like the libnewt.a that came with RHEL 4 is using some symbols (locale related I think) that are not part of dietlibc. How do I fix this? Don't mind rebuilding other packages, but I don't really know how to start. Thanks...james P.S. The reason I rebuild anaconda is because the pkgorder script has to be patched to work with the latest rpm (4.4.6), also, RHEL4 does not have the fix for fairly long filenames on packages applied to hdlist. Anyway thanks for any help. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list

1 0

Problem building anaconda on RHEL 4
by James Olin Oden 14 Apr '06

14 Apr '06

Hi All, I'm trying to build anaconda (the SRPM, and its binary RPMS) on RHEL 4 and I'm gettting a peculiar error, when it tries to link loader: anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x2b9): In function `entryDraw': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x2cc): In function `entryDraw': anaconda: : undefined reference to `mbtowc' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x329): In function `entryDraw': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x342): In function `entryDraw': anaconda: : undefined reference to `mbtowc' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x559): In function `previous_char': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x568): In function `previous_char': anaconda: : undefined reference to `mblen' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x599): In function `next_char': anaconda: : undefined reference to `__ctype_get_mb_cur_max' anaconda: /usr/lib/gcc/i386-redhat-linux/3.4.5/../../../libnewt.a(entry.o)(.text+0x5a8): In function `next_char': anaconda: : undefined reference to `mblen' anaconda: collect2: ld returned 1 exit status It looks like the libnewt.a that came with RHEL 4 is using some symbols (locale related I think) that are not part of dietlibc. How do I fix this? Don't mind rebuilding other packages, but I don't really know how to start. Thanks...james P.S. The reason I rebuild anaconda is because the pkgorder script has to be patched to work with the latest rpm (4.4.6), also, RHEL4 does not have the fix for fairly long filenames on packages applied to hdlist. Anyway thanks for any help.

1 0

FC5 Anaconda only installs i586 kernels
by Jason L Tibbitts III 12 Apr '06

12 Apr '06

I'm trying to track down a weird problem: I've kickstarted three FC5 machines on various different CPUs (SMP Via Nehemiah, hyperthreaded P4, dual core Athlon, all withthe i386 distro) and on each one Anaconda has installed just the uniprocessor i586 kernel. I can sort of understand the Nehemiah machine (as older processors in the series weren't fully i686 compatible) but the others are strange, and FC4 on the same hardware will install the proper kernels. Is there any way I can extract information from the installer about what it's finding, or can I run the detection routines standalone? - J<

1 0

anaconda installer interface component error
by Christian Theil Have 11 Apr '06

11 Apr '06

Hi list I'm trying to build a one-cd distro with Anaconda. The installer seems to work untill I get to the point where I need to select packages. Then I get the error shown on the image below: http://www.itu.dk/~cth/misc/anaconda-error.png Can anybody tell me why this happens? I only use a subset of the packages from FC so I thought that maybe I am missing an important package? Regards, Christian.

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel April 2006