-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAkv/9wEACgkQYoWFBIJE9eWpfQCcDtuCr+JyPeUEwlilRpQSkHND
0FcAnioTBc0UYNHtm/YRUZVq0O4HZakl
=ZL58
-----END PGP SIGNATURE-----