Re: Working on repoclosure reports
On Fri, 20 Aug 2010 17:19:08 -0600
Stephen John Smoogen wrote:
Ok there are probably various problems I haven't figured out yet,
but
I have downloaded various releases and begun repoclosure reports..
Quickstart on a CentOS machine:
$ sudo yum -y install yum-utils
$ repoclosure -n <-- with all repos enabled by default
OR
$ repoclosure -n -r base -r updates -r epel
That's all you would need to get going. Everyone with interest in EPEL
could run that occasionally. Even better with an added -r epel-testing
and a local repo for planned/prepared update builds.
I am not sure that is exactly what mschwendt was looking for,
Not exactly. My astonishment about untested/unmaintained packages was
not limited to a missing repoclosure report. For EPEL I just expect a
more diligent/painstaking package maintenance approach (a bit like
cherry-picking established Fedora procedures and policies), which its
users and packagers can rely on.
but its
starting down that road. I hope to get something up to the old reports
so that we can clean this up rather quickly. In summary we MAY have 17
broken dependencies against CentOS-4 in EPEL-4, 85 in EPEL-5 and 115
in EPEL-6
el4-report:17
el5-report:85
el6-report:115
I say may as I found 'breaks' in CentOS accroding to repoclosure...
Wouldn't be unusual. Packagers make mistakes, dropping sub-packages
without adding "Obsoletes". Multiarch repos add extra problems.
el4-report:package: 1:openoffice.org2-pyuno-2.0.4-5.7.0.6.0.1.i386
from centos-4u
el4-report:package: 1:openoffice.org2-pyuno-2.0.4-5.7.0.6.0.i386 from
centos-4u el4-report:package:
1:openoffice.org2-pyuno-2.0.4-5.7.0.6.1.el4_8.3.i386 from centos-4u
el5-report:package: spice-xpi-2.2-1.el5_5.x86_64 from centos-5u
| package: 1:openoffice.org2-pyuno-2.0.4-5.7.0.6.0.1.i386 from centos-4u
| unresolved deps:
| libpython2.3.so.1.0
| package: 2:koffice-kivio-1.6.3-25.20090306svn.el5.i386 from epel-5
| unresolved deps:
| libpython2.4.so.1.0
Multiarch repo problems.
The occurance of "x86_64" elsewhere in your attachments indicates that
you've processed x86_64 repos. Here, for centos-4u, python.i386 is not
available for x86_64. For epel-5, python.i386 is not available for
x86_64 either.
If this is the same for RHEL x86_64, you've just found an incompatibility
between RHEL and CentOS. (What multiarch repo compose tool do they use?
I see python-devel.i386 in x86_64, so perhaps it's not resolving the
multiarch deps to pull in needed packages.)