I'm running Fedora 14 32 bit. Directory does look similar: [touy@devfedora repodata]$ ls -al total 1924 drwxr-xr-x. 2 touy touy 2048 May 17 15:48 . drwxr-xr-x. 6 touy touy 6144 May 17 15:48 .. -rw-r--r--. 1 touy touy 952631 May 17 15:48 comps.xml -rw-r--r--. 1 touy touy 231145 May 17 15:48 comps.xml.gz -rw-r--r--. 1 touy touy 355332 May 17 15:48 filelists.xml.gz -rw-r--r--. 1 touy touy 208199 May 17 15:48 other.xml.gz -rw-r--r--. 1 touy touy 208391 May 17 15:48 primary.xml.gz -rw-r--r--. 1 touy touy 2107 May 17 15:48 repomd.xml -r--r--r--. 1 touy touy 1345 May 17 15:48 TRANS.TBL
On 5/18/11 8:56 AM, Douglas Hubler wrote: > On Wed, May 18, 2011 at 9:44 AM, Southanon Touy Ratsamy > <[email protected]> wrote: >> This creates an iso for me without any errors that I can see. When >> testing out the iso, it boots up and begins to run the pre-install >> scripts but errors out with the following error: >> >> "Unable to read package metadata. This may be due to a misssing repodata >> directory. Please ensure that your install tree has been correctly >> generated. failure: repodata/primary.xml.gz from >> anaconda-base-201103292314.i386: [Errno 256] No more mirrors to try." > Q: What is OS of your workstation your build on? > > Suggestions: > ----------------------------------- > mount the iso (mkdir foo; mount -o loop my.iso foo) and see if the > repository looks in order. > > ls -al foo/repodata/ > total 1921 > drwxr-xr-x 2 buildbot wheel 2048 Feb 4 13:28 . > drwxr-xr-x 7 buildbot wheel 6144 Feb 4 13:28 .. > -rw-r--r-- 1 buildbot wheel 941644 Feb 4 13:28 comps.xml > -rw-r--r-- 1 buildbot wheel 228242 Feb 4 13:28 comps.xml.gz > -rw-r--r-- 1 buildbot wheel 311103 Feb 4 13:28 filelists.xml.gz > -rw-r--r-- 1 buildbot wheel 251265 Feb 4 13:28 other.xml.gz > -rw-r--r-- 1 buildbot wheel 221458 Feb 4 13:28 primary.xml.gz > -rw-r--r-- 1 buildbot wheel 1865 Feb 4 13:28 repomd.xml > -r--r--r-- 1 buildbot wheel 1345 Feb 4 13:28 TRANS.TBL > > If it's not like the above, try to review the makefile fragment in > ./mak/35-centos-iso.mk.in > To see what could have gone wrong > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ -- Thanks, Touy _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
