On Fri, 2003-03-21 at 19:45, Axel Thimm wrote:
> I managed to get yum 1.8-20030307 running on RH8.0/rpm 4.2/python 2.2.1 (the
> bug with httplib was easy to fix by reducing the arguments, the other with
> coflicting epochs/versions I simply deleted the older package).
>
huh? The older pkg is just ignored in that case - the error you
encountered was the following:
a request for the strings which represent the version information
resulted in one of the strings returning an int not an string or None -
that isn't an "old pkg" paackage problem.
> Now I am playing with building yum repositories, e.g. such from vanilla Red
> Hat 8.0. Since I want to understand everything I turn on all options:
>
> > # yum-arch -l -d -c -z os
> > Checking deps 13 % completewarning: package glibc = 2.2.93-5 was already added, replacing with glibc <= 2.2.93-5
> > Checking deps 14 % completewarning: package glibc-debug = 2.2.93-5 was already added, replacing with glibc-debug <= 2.2.93-5
> > Checking deps 25 % completewarning: package kernel = 2.4.18-14 was already added, replacing with kernel <= 2.4.18-14
> > Checking deps 25 % completewarning: package kernel = 2.4.18-14 was already added, replacing with kernel <= 2.4.18-14
> > Checking deps 25 % completewarning: package kernel-smp = 2.4.18-14 was already added, replacing with kernel-smp <= 2.4.18-14
> > Checking deps 42 % completewarning: package openssl = 0.9.6b-29 was already added, replacing with openssl <= 0.9.6b-29
> > Checking deps 100 % complete[(('docbook-dtds', '1.0', '14'), ('openjade', '1.3.1'), 4, None, 1), (('glibc-common', '2.2.93', '5'), ('glibc', '2.2.93'), 4, None, 1)]
> > errors found
> >
> > Errors within the dir(s):
> > os
> > depcheck: package docbook-dtds conflicts with openjade
> > depcheck: package glibc-common conflicts with glibc
>
> The warnings seem to be due to packages built for different architectures
> (i386 vs i686 etc.). The message implies that only one will make it to the
> repository, but I checked and both have hdr files and are listed in
> header.info. So this seems to be OK, or not?
this is just in the creation of the dependency check.
what this does is it adds all the pkgs together as if they were all to
be installed in an empty rpmdb and see if there are any unresolved
dependencies and/or conflicts, etc.
The idea is to make sure you don't leave a complete install tree hung
up.
The warnings outputted there are just rpm complaining that you're
marking for install a lot of crack.
> The conflicting errors puzzle me. How can glibc conflict with glibc-common?
> And docbook-dtds conflicts with openjade only if openjade!=1.3.1.
Which distro ver is this? I just ran a yum-arch -l -c -vv on phoebe+some
rawhide and I don't get this problem.
>
> Can anyone explain/reproduce this?
-sv
