Hi
We use mrepo to keep a local repository. I downloaded the CentOS6.1 iso and used that as the base. We also have the CR repo added.
I was expecting this change to cause no issues but the following packages have version issues between the base 6.1 and the CR repo:-
base version CR version dbus-libs-1.2.24-4.el6_0.x86_64 dbus-libs-1.2.24-5.el6_1.x86_64 libpng-1.2.44-1.el6.x86_64 libpng-1.2.46-1.el6_1.x86_64 cups-libs-1.4.2-39.el6.x86_64 cups-libs-1.4.2-39.el6_1.1.x86_64 zlib-1.2.3-25.el6.x86_64 zlib-1.2.3-26.el6.x86_64 krb5-libs-1.9-9.el6.x86_64 krb5-libs-1.9-9.el6_1.2.x86_64 perl-5.10.1-119.el6.x86_64 perl-5.10.1-119.el6_1.1.x86_64 perl-libs-5.10.1-119.el6.x86_64 perl-libs-5.10.1-119.el6_1.1.x86_64
There maybe a few other packages but this causes an issue with yum as it doesn't handle the el6_ suffix differences.
Is this the intended behaviour ?
Thanks
On 12/13/2011 06:05 PM, Philip Manuel wrote:
Hi
We use mrepo to keep a local repository. I downloaded the CentOS6.1 iso and used that as the base. We also have the CR repo added.
I was expecting this change to cause no issues but the following packages have version issues between the base 6.1 and the CR repo:-
base version CR version dbus-libs-1.2.24-4.el6_0.x86_64 dbus-libs-1.2.24-5.el6_1.x86_64 libpng-1.2.44-1.el6.x86_64 libpng-1.2.46-1.el6_1.x86_64 cups-libs-1.4.2-39.el6.x86_64 cups-libs-1.4.2-39.el6_1.1.x86_64 zlib-1.2.3-25.el6.x86_64 zlib-1.2.3-26.el6.x86_64 krb5-libs-1.9-9.el6.x86_64 krb5-libs-1.9-9.el6_1.2.x86_64 perl-5.10.1-119.el6.x86_64 perl-5.10.1-119.el6_1.1.x86_64 perl-libs-5.10.1-119.el6.x86_64 perl-libs-5.10.1-119.el6_1.1.x86_64
There maybe a few other packages but this causes an issue with yum as it doesn't handle the el6_ suffix differences.
Is this the intended behaviour ?
please run:
yum clean all
then try the update again.
Yum handles the updates with no problems, but cached metadata can cause issues.
On 12/14/2011 11:17 AM, Johnny Hughes wrote:
On 12/13/2011 06:05 PM, Philip Manuel wrote:
Hi
We use mrepo to keep a local repository. I downloaded the CentOS6.1 iso and used that as the base. We also have the CR repo added.
I was expecting this change to cause no issues but the following packages have version issues between the base 6.1 and the CR repo:-
There maybe a few other packages but this causes an issue with yum as it doesn't handle the el6_ suffix differences.
Is this the intended behaviour ?
please run:
yum clean all
then try the update again.
Yum handles the updates with no problems, but cached metadata can cause issues.
yum clean all --> Finished Dependency Resolution Error: Protected multilib versions: 1:dbus-libs-1.2.24-4.el6_0.i686 != 1:dbus-libs-1.2.24-5.el6_1.x86_64 Error: Protected multilib versions: 2:libpng-1.2.44-1.el6.i686 != 2:libpng-1.2.46-1.el6_1.x86_64 Error: Protected multilib versions: 1:cups-libs-1.4.2-39.el6.i686 != 1:cups-libs-1.4.2-39.el6_1.1.x86_64 Error: Protected multilib versions: zlib-1.2.3-25.el6.i686 != zlib-1.2.3-26.el6.x86_64 Error: Protected multilib versions: krb5-libs-1.9-9.el6.i686 != krb5-libs-1.9-9.el6_1.2.x86_64 You could try using --skip-broken to work around the problem
I've fixed the perl ones by removing them and reinstalling but I don't want to keep doing this for every package
Thanks
On 12/13/2011 06:26 PM, Philip Manuel wrote:
On 12/14/2011 11:17 AM, Johnny Hughes wrote:
On 12/13/2011 06:05 PM, Philip Manuel wrote:
Hi
We use mrepo to keep a local repository. I downloaded the CentOS6.1 iso and used that as the base. We also have the CR repo added.
I was expecting this change to cause no issues but the following packages have version issues between the base 6.1 and the CR repo:-
There maybe a few other packages but this causes an issue with yum as it doesn't handle the el6_ suffix differences.
Is this the intended behaviour ?
please run:
yum clean all
then try the update again.
Yum handles the updates with no problems, but cached metadata can cause issues.
yum clean all --> Finished Dependency Resolution Error: Protected multilib versions: 1:dbus-libs-1.2.24-4.el6_0.i686 != 1:dbus-libs-1.2.24-5.el6_1.x86_64 Error: Protected multilib versions: 2:libpng-1.2.44-1.el6.i686 != 2:libpng-1.2.46-1.el6_1.x86_64 Error: Protected multilib versions: 1:cups-libs-1.4.2-39.el6.i686 != 1:cups-libs-1.4.2-39.el6_1.1.x86_64 Error: Protected multilib versions: zlib-1.2.3-25.el6.i686 != zlib-1.2.3-26.el6.x86_64 Error: Protected multilib versions: krb5-libs-1.9-9.el6.i686 != krb5-libs-1.9-9.el6_1.2.x86_64 You could try using --skip-broken to work around the problem
I've fixed the perl ones by removing them and reinstalling but I don't want to keep doing this for every package
There is nothing in 6.1 CR, your machine does not seem to see the updates for the i686 arch, although the x86_64 directory does contain them.
Do you have an exclude=*.i686 someplace in your yum setup.
The same directory that contains dbus-libs-1.2.24-5.el6_1.x86_64 also contains dbus-libs-1.2.24-5.el6_1.i686.rpm ... you are seeing one (x86_64) and not the other (i686).
On 12/14/2011 11:49 AM, Johnny Hughes wrote:
On 12/13/2011 06:26 PM, Philip Manuel wrote:
On 12/14/2011 11:17 AM, Johnny Hughes wrote:
On 12/13/2011 06:05 PM, Philip Manuel wrote:
Hi
We use mrepo to keep a local repository. I downloaded the CentOS6.1 iso and used that as the base. We also have the CR repo added.
I was expecting this change to cause no issues but the following packages have version issues between the base 6.1 and the CR repo:-
There maybe a few other packages but this causes an issue with yum as it doesn't handle the el6_ suffix differences.
Is this the intended behaviour ?
please run:
yum clean all
then try the update again.
Yum handles the updates with no problems, but cached metadata can cause issues.
I've fixed the perl ones by removing them and reinstalling but I don't want to keep doing this for every package
There is nothing in 6.1 CR, your machine does not seem to see the updates for the i686 arch, although the x86_64 directory does contain them.
Do you have an exclude=*.i686 someplace in your yum setup.
The same directory that contains dbus-libs-1.2.24-5.el6_1.x86_64 also contains dbus-libs-1.2.24-5.el6_1.i686.rpm ... you are seeing one (x86_64) and not the other (i686).
OK but why when there are no i686 packages installed on the machine is it trying to look for them? If I remove the offending x86_64 packages and put the base equivalent on then the issue goes away, but I shouldn't have to do this step.
On 12/13/2011 06:54 PM, Philip Manuel wrote:
On 12/14/2011 11:49 AM, Johnny Hughes wrote:
On 12/13/2011 06:26 PM, Philip Manuel wrote:
On 12/14/2011 11:17 AM, Johnny Hughes wrote:
On 12/13/2011 06:05 PM, Philip Manuel wrote:
Hi
We use mrepo to keep a local repository. I downloaded the CentOS6.1 iso and used that as the base. We also have the CR repo added.
I was expecting this change to cause no issues but the following packages have version issues between the base 6.1 and the CR repo:-
There maybe a few other packages but this causes an issue with yum as it doesn't handle the el6_ suffix differences.
Is this the intended behaviour ?
please run:
yum clean all
then try the update again.
Yum handles the updates with no problems, but cached metadata can cause issues.
I've fixed the perl ones by removing them and reinstalling but I don't want to keep doing this for every package
There is nothing in 6.1 CR, your machine does not seem to see the updates for the i686 arch, although the x86_64 directory does contain them.
Do you have an exclude=*.i686 someplace in your yum setup.
The same directory that contains dbus-libs-1.2.24-5.el6_1.x86_64 also contains dbus-libs-1.2.24-5.el6_1.i686.rpm ... you are seeing one (x86_64) and not the other (i686).
OK but why when there are no i686 packages installed on the machine is it trying to look for them? If I remove the offending x86_64 packages and put the base equivalent on then the issue goes away, but I shouldn't have to do this step.
You do have i686 packages on that machine ... that is what the error you posted is.
create (or edit( a file called:
/root/.rpmmacros
put this in the that file as the top line:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Then do the command:
rpm -qa | grep i[3,6]86
That should show you the i686 packages that are installed on the machine.
On 12/14/2011 12:07 PM, Johnny Hughes wrote:
On 12/13/2011 06:54 PM, Philip Manuel wrote:
On 12/14/2011 11:49 AM, Johnny Hughes wrote:
You do have i686 packages on that machine ... that is what the error you posted is.
create (or edit( a file called:
/root/.rpmmacros
put this in the that file as the top line:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Then do the command:
rpm -qa | grep i[3,6]86
That should show you the i686 packages that are installed on the machine.
cat /etc/rpm/macros.zomojo # Zomojo global rpm macros %org_tag .zmj %dist .el6 %rhel 6 %zmj_bjam_flags '-j 4' %packager Zomojo build@zomojo.com %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} rpm -qa | grep i[3,6]86 :~#
Nothing other than x86_64 packages
Le mer 14 déc 2011 12:17:36 CET, Philip Manuel a écrit:
On 12/14/2011 12:07 PM, Johnny Hughes wrote:
On 12/13/2011 06:54 PM, Philip Manuel wrote:
On 12/14/2011 11:49 AM, Johnny Hughes wrote:
You do have i686 packages on that machine ... that is what the error you posted is.
create (or edit( a file called:
/root/.rpmmacros
put this in the that file as the top line:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Then do the command:
rpm -qa | grep i[3,6]86
That should show you the i686 packages that are installed on the machine.
cat /etc/rpm/macros.zomojo # Zomojo global rpm macros %org_tag .zmj %dist .el6 %rhel 6 %zmj_bjam_flags '-j 4' %packager Zomojo build@zomojo.com %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} rpm -qa | grep i[3,6]86 :~#
Nothing other than x86_64 packages
Maybe also, in the case there is something broken in the yum database : yum list installed '*i[3456]86'
On 12/14/2011 07:26 PM, Philippe Naudin wrote:
Le mer 14 déc 2011 12:17:36 CET, Philip Manuel a écrit:
You do have i686 packages on that machine ... that is what the error you posted is.
create (or edit( a file called:
/root/.rpmmacros
put this in the that file as the top line:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Then do the command:
rpm -qa | grep i[3,6]86
That should show you the i686 packages that are installed on the machine.
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} rpm -qa | grep i[3,6]86 :~#
Nothing other than x86_64 packages
Maybe also, in the case there is something broken in the yum database : yum list installed '*i[3456]86'
yum list installed '*i[3456]86' base | 1.2 kB 00:00 cr | 1.9 kB 00:00 dag | 1.9 kB 00:00 local | 2.6 kB 00:00 of | 951 B 00:00 updates | 1.1 kB 00:00 Error: No matching Packages to list
Vreme: 12/14/2011 01:54 AM, Philip Manuel piše:
OK but why when there are no i686 packages installed on the machine is it trying to look for them? If I remove the offending x86_64 packages and put the base equivalent on then the issue goes away, but I shouldn't have to do this step.
Your mrepo CR repository, have you by any chance froze it and kept the packages?
P.S. I have 6.1 and mrepo local repository and I do not have any problems, even without "yum clean all".
-
Johnny Hughes -
Ljubomir Ljubojevic -
Philip Manuel -
Philippe Naudin