-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Some time ago I encountered some problems with the --rpm-list option for the cobbler repo command. As I understood, the --rpm-list option do not work with foreign architectures, e.g. if cobbler server is i386 one cannot make a repo for x86_64. https://fedorahosted.org/pipermail/cobbler/2009-June/004566.html
The related ticket was closed without a explanation why: https://fedorahosted.org/cobbler/ticket/153
I stumbled over this issue again and it seems to me its even worse. The repo for the same arch does not work too.
repo with same arch as cobbler server and rpm-list specified: reposync works but yum complains:
Error: failure: repodata/primary.xml.gz from reponame: [Errno 256] No more mirrors to try.
I also tried with --mirror-locally turned off, no difference. What are the use cases for the --rpm-list feature then ? Anyone using this ? As far as I can see it only produces a partial mirror that is not usable by yum after mirroring, and thats the best case. In the worse case it is not even capable to create the mirror.
- -- best regards, markus
We use --rpm-list to mirror portions of the EPEL repository. I believe what you are referring to would be to mirror Satellite/RHN channels from Red Hat. I believe that is much more difficult and does have some limitations. You might look at the mrepo tool from Dag Wieers to try and solve that problem, though I don't believe that is perfect, either.
Matt
-----Original Message----- From: cobbler-bounces@lists.fedorahosted.org [mailto:cobbler- bounces@lists.fedorahosted.org] On Behalf Of Markus Falb Sent: Sunday, May 23, 2010 1:20 PM To: cobbler@lists.fedorahosted.org Subject: rpm-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Some time ago I encountered some problems with the --rpm-list option for the cobbler repo command. As I understood, the --rpm-list option do not work with foreign architectures, e.g. if cobbler server is i386 one cannot make a repo for x86_64. https://fedorahosted.org/pipermail/cobbler/2009-June/004566.html
The related ticket was closed without a explanation why: https://fedorahosted.org/cobbler/ticket/153
I stumbled over this issue again and it seems to me its even worse. The repo for the same arch does not work too.
repo with same arch as cobbler server and rpm-list specified: reposync works but yum complains:
Error: failure: repodata/primary.xml.gz from reponame: [Errno 256] No more mirrors to try.
I also tried with --mirror-locally turned off, no difference. What are the use cases for the --rpm-list feature then ? Anyone using this ? As far as I can see it only produces a partial mirror that is not usable by yum after mirroring, and thats the best case. In the worse case it is not even capable to create the mirror.
best regards, markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkv5Y6sACgkQYoWFBIJE9eUlMACeK2E3cAheeJg5+VoojCQPlx2d G2kAoIHpcBUDvJqYSwyqf+1aEMCSek/w =da9L -----END PGP SIGNATURE-----
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/05/2010 13:45, Hyclak, Matthew wrote:
We use --rpm-list to mirror portions of the EPEL repository. I believe what you are referring to would be to mirror Satellite/RHN channels from Red Hat. I believe that is much more difficult and does have some limitations. You might look at the mrepo tool from Dag Wieers to try and solve that problem, though I don't believe that is perfect, either.
I want to achieve similar, partial mirrors of repositories like EPEL or rpmforge but that does not work. On a i386 cobbler server reposync produces unusable i386 repositories for me. It seems to me that the createrepo command is not executed (but should). As soon as i do a manual createrepo the missing file are created and the repository is usable.
Anyway, i will have a look at mrepo.
- -- best regards, markus
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Excerpts from Markus Falb's message of Sun May 23 13:19:39 -0400 2010:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Some time ago I encountered some problems with the --rpm-list option for the cobbler repo command. As I understood, the --rpm-list option do not work with foreign architectures, e.g. if cobbler server is i386 one cannot make a repo for x86_64. https://fedorahosted.org/pipermail/cobbler/2009-June/004566.html
Can you try again with cobbler 2.0.4? There have been some improvements in there that might help you.
The related ticket was closed without a explanation why: https://fedorahosted.org/cobbler/ticket/153
This might be because it is going to be a bug with yum that cobbler can't really fix. It shouldn't have been closed without comment, but if yum doesn't support what you are trying to do, there is nothing that cobbler can do about it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 26/05/2010 16:23, Scott Henson wrote:
Excerpts from Markus Falb's message of Sun May 23 13:19:39 -0400 2010:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Some time ago I encountered some problems with the --rpm-list option for the cobbler repo command. As I understood, the --rpm-list option do not work with foreign architectures, e.g. if cobbler server is i386 one cannot make a repo for x86_64. https://fedorahosted.org/pipermail/cobbler/2009-June/004566.html
Can you try again with cobbler 2.0.4? There have been some improvements in there that might help you.
OK. I was at 2.0.3 from EPEL and now i installed 2.0.4 from EPEL testing but it did not change anything as far as i can see.
The related ticket was closed without a explanation why: https://fedorahosted.org/cobbler/ticket/153
This might be because it is going to be a bug with yum that cobbler can't really fix. It shouldn't have been closed without comment, but if yum doesn't support what you are trying to do, there is nothing that cobbler can do about it.
I have do disagree. The --rpm-list feature is announced by cobbler. It announces a feature that in the end turns out to be unusable (for me at least). Kind of cheating. The end user is not interested in what tools are used behind the scenes. The frontend is supposed to do some kind of error detection and I would expect it to handle cases where it is known that a specific feature or setting or whatever will be disfunctional.
Or in other words, if the backend tools can not provide the needed services, cobbler should not pretend it could.
Just some thoughts, no offence please.
- -- Best Regards Markus Falb
cobbler@lists.fedorahosted.org