Douglas McClendon wrote:
John Summerfield wrote:
Douglas McClendon wrote:
John Summerfield wrote:
This might not strictly be an Anaconda question, but Anaconda is
involved and (it seems to me) there's some inconsistency involving
Anaconda and yum.
I've tried copying* a RHEL5-clone DVD image to disk to use for
network installs. I might not not actually have tried to install a
system from it, but I have tried to install packages from it using yum.
The problem is that yum grabs repomd.xml and primary.xml.gz and then
barfs:
10:11 [summer@numbat ~]$ sudo yum install libmtp-devel libnjb-devel
libid3tag-devel
Loading "kernel-module" plugin
Setting up Install Process
Setting up repositories
sl-security 100% |=========================| 951 B
00:00
sl-base 100% |=========================| 1.3 kB
00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 183 kB
00:02
sl-securit: ################################################## 478/478
primary.xml.gz 100% |=========================| 841 kB
00:00
sl-base : ##################################################
2454/2454
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for libid3tag-devel to pack into transaction
set.
media:/1178298547.683145//libid3tag-devel-0.15.1b-3.sl.i386.rpm:
[Errno 4] IOError: <urlopen error unknown url type: media>
Trying other mirror.
Error: failed to retrieve libid3tag-devel-0.15.1b-3.sl.i386.rpm from
sl-base
error was [Errno 4] IOError: <urlopen error unknown url type: media>
10:12 [summer@numbat ~]$
I have, of course, installed from this image, though I don't
actually recall whether I did a network or CDROM install.
I've diagnosed that media:/1178298547.683145 needs to get changed to
the base URL, but I can't see how it (apparently) works at system
install time and not later.
On checking other ISO images I have here, I this might as well arise
with FC6, F7 and (most likely) RHEL5 itself, as all have this
media:// stuff.
How's it supposed to work, and more importantly why might it not work?
* The "copy" is actually a symlink to the loop-mounted ISO image. As
yum fetches the repo files, I believe my setup is correct as far as
that goes.
I think this may be a known issue, though I forget the details. I
recall working around this (or something very similar) by using
createrepo with --outputdir. I.e. it creates a new set of metadata
which points to the same loopmounted iso rpms. I could then use the
resulting repo to install packages via yum.
I'm hoping for an official word from JK or someone: it obviously works
during install, and presumably I can mount my DVD and install stuff
from it.
Not definitive answers, but these links seem possibly related-
(though I would hope there is an official answer that suggests these
steps are no longer needed, or won't be in the near future.)
http://kbase.redhat.com/faq/FAQ_103_10415.shtm
Oh, so basically it's bollixed. It will work really well with automount.
I only have 23 ISO images I automount.
http://forums.fedoraforum.org/showthread.php?t=153437
-dmc
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
--
Cheers
John
-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
Please do not reply off-list
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
