The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn't it be sha1?
I can tell Katello that it is sha256, which gets me past the 'the download
doesn't match' message, but then I'm left with a sha256 local repo which
CentOS 5 clients can't use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can't think how I got
round it! At least not without manually running a createrepo]
I imagine the Candlepin team maintains that repository and as such you'd
have to contact them. However, for Katello itself, we recommend using our
client repositories. You'll note if you look at the EL5 client repository
[1], we provide a version of subscription-manager so that you can use the
client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the download
doesn’t match’ message, but then I’m left with a sha256 local repo which
CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think how I got
round it! At least not without manually running a createrepo]
I imagine the Candlepin team maintains that repository and as such you’d
have to contact them. However, for Katello itself, we recommend using our
client repositories. You’ll note if you look at the EL5 client repository
[1], we provide a version of subscription-manager so that you can use the
client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think how I
got round it! At least not without manually running a createrepo]
···
On Monday, 18 May 2015 17:01:33 UTC+1, Eric Helms wrote:
>
> I imagine the Candlepin team maintains that repository and as such you'd
> have to contact them. However, for Katello itself, we recommend using our
> client repositories. You'll note if you look at the EL5 client repository
> [1], we provide a version of subscription-manager so that you can use the
> client repository directly (and so we provide a copy of
> subscription-manager that works with our setup since EL5 is special).
>
>
> Eric
>
>
> [1]
> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/5Server/x86_64/
>
> On Mon, May 18, 2015 at 11:18 AM, JC <mr.jamie...@gmail.com > > wrote:
>
>> The repodata for the above is using sha256, but as it is presumably
>> intended for CentOS/RHEL 5 clients, shouldn't it be sha1?
>>
>> I can tell Katello that it is sha256, which gets me past the 'the
>> download doesn't match' message, but then I'm left with a sha256 local repo
>> which CentOS 5 clients can't use.
>>
>> Thanks,
>> Jamie.
>>
>> [I think I had this problem earlier, but if I did, I can't think how I
>> got round it! At least not without manually running a createrepo]
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
···
On Monday, 18 May 2015 17:36:44 UTC+1, JC wrote:
>
> Ahh, super. Cheers Eric, I'll give that a whirl.
>
> On 18 May 2015 at 17:01, Eric D Helms wrote:
>
>> I imagine the Candlepin team maintains that repository and as such you'd
>> have to contact them. However, for Katello itself, we recommend using our
>> client repositories. You'll note if you look at the EL5 client repository
>> [1], we provide a version of subscription-manager so that you can use the
>> client repository directly (and so we provide a copy of
>> subscription-manager that works with our setup since EL5 is special).
>>
>>
>> Eric
>>
>>
>> [1]
>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/5Server/x86_64/
>>
>> On Mon, May 18, 2015 at 11:18 AM, JC wrote:
>>
>>> The repodata for the above is using sha256, but as it is presumably
>>> intended for CentOS/RHEL 5 clients, shouldn't it be sha1?
>>>
>>> I can tell Katello that it is sha256, which gets me past the 'the
>>> download doesn't match' message, but then I'm left with a sha256 local repo
>>> which CentOS 5 clients can't use.
>>>
>>> Thanks,
>>> Jamie.
>>>
>>> [I think I had this problem earlier, but if I did, I can't think how I
>>> got round it! At least not without manually running a createrepo]
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Foreman users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to foreman-users+unsubscribe@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> foreman-users+unsubscribe@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Jamie.
>
You should definitely only need the client repositories and by the looks of
it we have python-rhsm specified in our comps for that repository but not
tagged into the repository. Good find! I will work on getting this fixed
and reply to this thread when it's available.
I imagine the Candlepin team maintains that repository and as such you’d
have to contact them. However, for Katello itself, we recommend using our
client repositories. You’ll note if you look at the EL5 client repository
[1], we provide a version of subscription-manager so that you can use the
client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think how I
got round it! At least not without manually running a createrepo]
You should definitely only need the client repositories and by the looks
of it we have python-rhsm specified in our comps for that repository but
not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as such
you’d have to contact them. However, for Katello itself, we recommend using
our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think how I
got round it! At least not without manually running a createrepo]
You should definitely only need the client repositories and by the looks
of it we have python-rhsm specified in our comps for that repository but
not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as such
you’d have to contact them. However, for Katello itself, we recommend using
our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think how
I got round it! At least not without manually running a createrepo]
Cheers Eric. I think we need a slightly newer release than python-rhsm- 1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has depsolving
problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
···
On 19 May 2015 at 14:08, Eric D Helms wrote:
Ok, the 2.2 RHEL5 client repository should be fixed now. Thanks again for
reporting the discrepancy!
You should definitely only need the client repositories and by the looks
of it we have python-rhsm specified in our comps for that repository but
not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as such
you’d have to contact them. However, for Katello itself, we recommend using
our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think how
I got round it! At least not without manually running a createrepo]
You are correct. I will track down a version of python-rhsm that meets that
requirement and let you know when I get it pushed out.
Eric
···
On Tue, May 19, 2015 at 9:18 AM, Jamie Caldwell wrote:
Cheers Eric. I think we need a slightly newer release than python-rhsm- 1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by the
looks of it we have python-rhsm specified in our comps for that repository
but not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as such
you’d have to contact them. However, for Katello itself, we recommend using
our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is presumably
intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think
how I got round it! At least not without manually running a createrepo]
Cheers Eric. I think we need a slightly newer release than python-rhsm- 1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by the
looks of it we have python-rhsm specified in our comps for that repository
but not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as such
you’d have to contact them. However, for Katello itself, we recommend using
our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think
how I got round it! At least not without manually running a createrepo]
Cheers Eric. I think we need a slightly newer release than python-rhsm- 1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by the
looks of it we have python-rhsm specified in our comps for that repository
but not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as such
you’d have to contact them. However, for Katello itself, we recommend using
our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think
how I got round it! At least not without manually running a createrepo]
Cheers Eric. I think we need a slightly newer release than python-rhsm- 1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by the
looks of it we have python-rhsm specified in our comps for that repository
but not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as such
you’d have to contact them. However, for Katello itself, we recommend using
our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the ‘the
download doesn’t match’ message, but then I’m left with a sha256 local repo
which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think
how I got round it! At least not without manually running a createrepo]
I'll have to look into this further within our Koji and how those
repositories get generated. However, if you are syncing them down into
Katello, you should be able to set the checksum on the repository to sha1
such that they end up in Pulp that way I believe.
Eric
···
On Wed, May 20, 2015 at 5:07 AM, Jamie Caldwell wrote:
Eric - so that’s great, thanks; I see the right package is there. But the
repodata is generated using sha256, rather than sha1…
Cheers Eric. I think we need a slightly newer release than python-rhsm- 1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by the
looks of it we have python-rhsm specified in our comps for that repository
but not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as
such you’d have to contact them. However, for Katello itself, we recommend
using our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the
’the download doesn’t match’ message, but then I’m left with a sha256 local
repo which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t think
how I got round it! At least not without manually running a createrepo]
Cheers Eric. Unfortunately, if you do that, when the client tries to use
it, yum errors with '[Errno -1] Package does not match intended download'.
···
On 20 May 2015 at 13:26, Eric D Helms wrote:
I’ll have to look into this further within our Koji and how those
repositories get generated. However, if you are syncing them down into
Katello, you should be able to set the checksum on the repository to sha1
such that they end up in Pulp that way I believe.
Cheers Eric. I think we need a slightly newer release
than python-rhsm-1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by package
subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by the
looks of it we have python-rhsm specified in our comps for that repository
but not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as
such you’d have to contact them. However, for Katello itself, we recommend
using our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the
’the download doesn’t match’ message, but then I’m left with a sha256 local
repo which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t
think how I got round it! At least not without manually running a
createrepo]
I’ll have to look into this further within our Koji and how those
repositories get generated. However, if you are syncing them down into
Katello, you should be able to set the checksum on the repository to sha1
such that they end up in Pulp that way I believe.
Cheers Eric. I think we need a slightly newer release
than python-rhsm-1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by the
looks of it we have python-rhsm specified in our comps for that repository
but not tagged into the repository. Good find! I will work on getting this
fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as
such you’d have to contact them. However, for Katello itself, we recommend
using our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the
’the download doesn’t match’ message, but then I’m left with a sha256 local
repo which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t
think how I got round it! At least not without manually running a
createrepo]
I’ll have to look into this further within our Koji and how those
repositories get generated. However, if you are syncing them down into
Katello, you should be able to set the checksum on the repository to sha1
such that they end up in Pulp that way I believe.
Cheers Eric. I think we need a slightly newer release
than python-rhsm-1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by
the looks of it we have python-rhsm specified in our comps for that
repository but not tagged into the repository. Good find! I will work on
getting this fixed and reply to this thread when it’s available.
I imagine the Candlepin team maintains that repository and as
such you’d have to contact them. However, for Katello itself, we recommend
using our client repositories. You’ll note if you look at the EL5 client
repository [1], we provide a version of subscription-manager so that you
can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past the
’the download doesn’t match’ message, but then I’m left with a sha256 local
repo which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t
think how I got round it! At least not without manually running a
createrepo]
Sorry Eric, more dependencies…now for python-gofer:
python-gofer-2.5.3-1.el5.noarch from katello-agent has depsolving problems
–> Missing Dependency: python-hashlib is needed by package
python-gofer-2.5.3-1.el5.noarch (katello-agent)
python-gofer-2.5.3-1.el5.noarch from katello-agent has depsolving problems
–> Missing Dependency: python-uuid is needed by package
python-gofer-2.5.3-1.el5.noarch (katello-agent)
···
On Wednesday, 20 May 2015 17:09:40 UTC+1, JC wrote:
>
> Okidoki, will do in the morning.
> On 20 May 2015 16:43, "Eric D Helms" wrote:
>
>> Ok, I think I got it figured out. Please try the 2.2 RHEL5 client
>> repositories again and let me know if they work.
>>
>>
>> Thanks,
>> Eric
>>
>> On Wed, May 20, 2015 at 8:44 AM, Jamie Caldwell < >> mr.jamie.caldwell@gmail.com> wrote:
>>
>>> Cheers Eric. Unfortunately, if you do that, when the client tries to
>>> use it, yum errors with '[Errno -1] Package does not match intended
>>> download'.
>>>
>>> On 20 May 2015 at 13:26, Eric D Helms wrote:
>>>
>>>> I'll have to look into this further within our Koji and how those
>>>> repositories get generated. However, if you are syncing them down into
>>>> Katello, you should be able to set the checksum on the repository to sha1
>>>> such that they end up in Pulp that way I believe.
>>>>
>>>> Eric
>>>>
>>>> On Wed, May 20, 2015 at 5:07 AM, Jamie Caldwell < >>>> mr.jamie.caldwell@gmail.com> wrote:
>>>>
>>>>> Eric - so that's great, thanks; I see the right package is there. But
>>>>> the repodata is generated using sha256, rather than sha1....
>>>>>
>>>>> On 19 May 2015 at 17:45, Eric D Helms wrote:
>>>>>
>>>>>> Ok.. this should be fixed for real now. I added python-rhsm-1.11.3-5
>>>>>> to the 2.2 and nightly client repos for EL5.
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> On Tue, May 19, 2015 at 9:35 AM, Eric D Helms >>>>>> wrote:
>>>>>>
>>>>>>> You are correct. I will track down a version of python-rhsm that
>>>>>>> meets that requirement and let you know when I get it pushed out.
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>> On Tue, May 19, 2015 at 9:18 AM, Jamie Caldwell < >>>>>>> mr.jamie.caldwell@gmail.com> wrote:
>>>>>>>
>>>>>>>> Cheers Eric. I think we need a slightly newer release
>>>>>>>> than python-rhsm-*1.11.3-3*.el5.x86_64.rpm...
>>>>>>>>
>>>>>>>> subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
>>>>>>>> depsolving problems
>>>>>>>> --> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
>>>>>>>> package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
>>>>>>>> Error: Missing Dependency: python-rhsm >= *1.11.3-5* is needed by
>>>>>>>> package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
>>>>>>>>
>>>>>>>> On 19 May 2015 at 14:08, Eric D Helms wrote:
>>>>>>>>
>>>>>>>>> Ok, the 2.2 RHEL5 client repository should be fixed now. Thanks
>>>>>>>>> again for reporting the discrepancy!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> On Tue, May 19, 2015 at 9:07 AM, Jamie Caldwell < >>>>>>>>> mr.jamie.caldwell@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks Eric. I'll wait to hear...
>>>>>>>>>>
>>>>>>>>>> On 19 May 2015 at 13:53, Eric D Helms >>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> You should definitely only need the client repositories and by
>>>>>>>>>>> the looks of it we have python-rhsm specified in our comps for that
>>>>>>>>>>> repository but not tagged into the repository. Good find! I will work on
>>>>>>>>>>> getting this fixed and reply to this thread when it's available.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Eric
>>>>>>>>>>>
>>>>>>>>>>> On Tue, May 19, 2015 at 3:58 AM, JC >>>>>>>>>> > wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Ok, now that I'm back in front of Foreman I realise a) that I
>>>>>>>>>>>> use that repo already and b) why I use both repos (
>>>>>>>>>>>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/5Server/x86_64/ and
>>>>>>>>>>>>
>>>>>>>>>>>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-5/x86_64/)...because
>>>>>>>>>>>> the later provides the missing dependency - python-rhsm (Jorick helped me
>>>>>>>>>>>> with this before).
>>>>>>>>>>>>
>>>>>>>>>>>> So which repo should be updated?
>>>>>>>>>>>>
>>>>>>>>>>>> On Monday, 18 May 2015 17:36:44 UTC+1, JC wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ahh, super. Cheers Eric, I'll give that a whirl.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 18 May 2015 at 17:01, Eric D Helms >>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I imagine the Candlepin team maintains that repository and as
>>>>>>>>>>>>>> such you'd have to contact them. However, for Katello itself, we recommend
>>>>>>>>>>>>>> using our client repositories. You'll note if you look at the EL5 client
>>>>>>>>>>>>>> repository [1], we provide a version of subscription-manager so that you
>>>>>>>>>>>>>> can use the client repository directly (and so we provide a copy of
>>>>>>>>>>>>>> subscription-manager that works with our setup since EL5 is special).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [1]
>>>>>>>>>>>>>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/5Server/x86_64/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, May 18, 2015 at 11:18 AM, JC < >>>>>>>>>>>>>> mr.jamie.caldwell@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The repodata for the above is using sha256, but as it is
>>>>>>>>>>>>>>> presumably intended for CentOS/RHEL 5 clients, shouldn't it be sha1?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I can tell Katello that it is sha256, which gets me past the
>>>>>>>>>>>>>>> 'the download doesn't match' message, but then I'm left with a sha256 local
>>>>>>>>>>>>>>> repo which CentOS 5 clients can't use.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Jamie.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [I think I had this problem earlier, but if I did, I can't
>>>>>>>>>>>>>>> think how I got round it! At least not without manually running a
>>>>>>>>>>>>>>> createrepo]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>>>>>>> Google Groups "Foreman users" group.
>>>>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails
>>>>>>>>>>>>>>> from it, send an email to
>>>>>>>>>>>>>>> foreman-users+unsubscribe@googlegroups.com.
>>>>>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>>>>>> foreman-users@googlegroups.com.
>>>>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> You received this message because you are subscribed to a
>>>>>>>>>>>>>> topic in the Google Groups "Foreman users" group.
>>>>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>>>>>>>>>> .
>>>>>>>>>>>>>> To unsubscribe from this group and all its topics, send an
>>>>>>>>>>>>>> email to foreman-users+unsubscribe@googlegroups.com.
>>>>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>>>>> foreman-users@googlegroups.com.
>>>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Jamie.
>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>>>> Google Groups "Foreman users" group.
>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>>>>>>> it, send an email to foreman-users+unsubscribe@googlegroups.com
>>>>>>>>>>>> .
>>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>>> foreman-users@googlegroups.com.
>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> You received this message because you are subscribed to a topic
>>>>>>>>>>> in the Google Groups "Foreman users" group.
>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>>>>>>> .
>>>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>>>> to foreman-users+unsubscribe@googlegroups.com.
>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>> foreman-users@googlegroups.com.
>>>>>>>>>>> Visit this group at http://groups.google.com/group/foreman-users
>>>>>>>>>>> .
>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Jamie.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>> Google Groups "Foreman users" group.
>>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>>> send an email to foreman-users+unsubscribe@googlegroups.com.
>>>>>>>>>> To post to this group, send email to
>>>>>>>>>> foreman-users@googlegroups.com.
>>>>>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>>>> the Google Groups "Foreman users" group.
>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>>>>> .
>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>> to foreman-users+unsubscribe@googlegroups.com.
>>>>>>>>> To post to this group, send email to
>>>>>>>>> foreman-users@googlegroups.com.
>>>>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jamie.
>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "Foreman users" group.
>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>> send an email to foreman-users+unsubscribe@googlegroups.com.
>>>>>>>> To post to this group, send email to foreman-users@googlegroups.com
>>>>>>>> .
>>>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to a topic in
>>>>>> the Google Groups "Foreman users" group.
>>>>>> To unsubscribe from this topic, visit
>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> foreman-users+unsubscribe@googlegroups.com.
>>>>>> To post to this group, send email to foreman-users@googlegroups.com.
>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jamie.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Foreman users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to foreman-users+unsubscribe@googlegroups.com.
>>>>> To post to this group, send email to foreman-users@googlegroups.com.
>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Foreman users" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> foreman-users+unsubscribe@googlegroups.com.
>>>> To post to this group, send email to foreman-users@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Jamie.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Foreman users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to foreman-users+unsubscribe@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> foreman-users+unsubscribe@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
Looks like those packages are available in epel which our docs currently
omit as something to add for EL5.
···
On Thu, May 21, 2015 at 5:46 AM, JC wrote:
Sorry Eric, more dependencies…now for python-gofer:
python-gofer-2.5.3-1.el5.noarch from katello-agent has depsolving problems
–> Missing Dependency: python-hashlib is needed by package
python-gofer-2.5.3-1.el5.noarch (katello-agent)
python-gofer-2.5.3-1.el5.noarch from katello-agent has depsolving problems
–> Missing Dependency: python-uuid is needed by package
python-gofer-2.5.3-1.el5.noarch (katello-agent)
On Wednesday, 20 May 2015 17:09:40 UTC+1, JC wrote:
Okidoki, will do in the morning.
On 20 May 2015 16:43, “Eric D Helms” ericdhelms@gmail.com wrote:
Ok, I think I got it figured out. Please try the 2.2 RHEL5 client
repositories again and let me know if they work.
I’ll have to look into this further within our Koji and how those
repositories get generated. However, if you are syncing them down into
Katello, you should be able to set the checksum on the repository to sha1
such that they end up in Pulp that way I believe.
Cheers Eric. I think we need a slightly newer release
than python-rhsm-1.11.3-3.el5.x86_64.rpm…
subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
depsolving problems
–> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
Error: Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
You should definitely only need the client repositories and by
the looks of it we have python-rhsm specified in our comps for that
repository but not tagged into the repository. Good find! I will work on
getting this fixed and reply to this thread when it’s available.
On 18 May 2015 at 17:01, Eric D Helms ericdhelms@gmail.com >>>>>>>>>>>>>> wrote:
I imagine the Candlepin team maintains that repository and
as such you’d have to contact them. However, for Katello itself, we
recommend using our client repositories. You’ll note if you look at the EL5
client repository [1], we provide a version of subscription-manager so that
you can use the client repository directly (and so we provide a copy of
subscription-manager that works with our setup since EL5 is special).
The repodata for the above is using sha256, but as it is
presumably intended for CentOS/RHEL 5 clients, shouldn’t it be sha1?
I can tell Katello that it is sha256, which gets me past
the ‘the download doesn’t match’ message, but then I’m left with a sha256
local repo which CentOS 5 clients can’t use.
Thanks,
Jamie.
[I think I had this problem earlier, but if I did, I can’t
think how I got round it! At least not without manually running a
createrepo]
Darn! I thought EPEL was enabled. You are quite right; all looks good.
Cheers again for our help.
···
On Thursday, 21 May 2015 13:43:56 UTC+1, Eric Helms wrote:
>
> Looks like those packages are available in epel which our docs currently
> omit as something to add for EL5.
>
> On Thu, May 21, 2015 at 5:46 AM, JC <mr.jamie...@gmail.com > > wrote:
>
>> Sorry Eric, more dependencies...now for python-gofer:
>>
>> python-gofer-2.5.3-1.el5.noarch from katello-agent has depsolving problems
>> --> Missing Dependency: *python-hashlib* is needed by package
>> python-gofer-2.5.3-1.el5.noarch (katello-agent)
>> python-gofer-2.5.3-1.el5.noarch from katello-agent has depsolving problems
>> --> Missing Dependency: *python-uuid* is needed by package
>> python-gofer-2.5.3-1.el5.noarch (katello-agent)
>>
>>
>>
>> On Wednesday, 20 May 2015 17:09:40 UTC+1, JC wrote:
>>>
>>> Okidoki, will do in the morning.
>>> On 20 May 2015 16:43, "Eric D Helms" <ericd...@gmail.com > >>> wrote:
>>>
>>>> Ok, I think I got it figured out. Please try the 2.2 RHEL5 client
>>>> repositories again and let me know if they work.
>>>>
>>>>
>>>> Thanks,
>>>> Eric
>>>>
>>>> On Wed, May 20, 2015 at 8:44 AM, Jamie Caldwell >>> > wrote:
>>>>
>>>>> Cheers Eric. Unfortunately, if you do that, when the client tries to
>>>>> use it, yum errors with '[Errno -1] Package does not match intended
>>>>> download'.
>>>>>
>>>>> On 20 May 2015 at 13:26, Eric D Helms >>>> > wrote:
>>>>>
>>>>>> I'll have to look into this further within our Koji and how those
>>>>>> repositories get generated. However, if you are syncing them down into
>>>>>> Katello, you should be able to set the checksum on the repository to sha1
>>>>>> such that they end up in Pulp that way I believe.
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>> On Wed, May 20, 2015 at 5:07 AM, Jamie Caldwell < >>>>>> mr.jamie...@gmail.com > wrote:
>>>>>>
>>>>>>> Eric - so that's great, thanks; I see the right package is there.
>>>>>>> But the repodata is generated using sha256, rather than sha1....
>>>>>>>
>>>>>>> On 19 May 2015 at 17:45, Eric D Helms >>>>>> > wrote:
>>>>>>>
>>>>>>>> Ok.. this should be fixed for real now. I added
>>>>>>>> python-rhsm-1.11.3-5 to the 2.2 and nightly client repos for EL5.
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> On Tue, May 19, 2015 at 9:35 AM, Eric D Helms >>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> You are correct. I will track down a version of python-rhsm that
>>>>>>>>> meets that requirement and let you know when I get it pushed out.
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> On Tue, May 19, 2015 at 9:18 AM, Jamie Caldwell < >>>>>>>>> mr.jamie...@gmail.com > wrote:
>>>>>>>>>
>>>>>>>>>> Cheers Eric. I think we need a slightly newer release
>>>>>>>>>> than python-rhsm-*1.11.3-3*.el5.x86_64.rpm...
>>>>>>>>>>
>>>>>>>>>> subscription-manager-1.11.3-11.el5.x86_64 from katello-agent has
>>>>>>>>>> depsolving problems
>>>>>>>>>> --> Missing Dependency: python-rhsm >= 1.11.3-5 is needed by
>>>>>>>>>> package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
>>>>>>>>>> Error: Missing Dependency: python-rhsm >= *1.11.3-5* is needed
>>>>>>>>>> by package subscription-manager-1.11.3-11.el5.x86_64 (katello-agent)
>>>>>>>>>>
>>>>>>>>>> On 19 May 2015 at 14:08, Eric D Helms >>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Ok, the 2.2 RHEL5 client repository should be fixed now. Thanks
>>>>>>>>>>> again for reporting the discrepancy!
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Eric
>>>>>>>>>>>
>>>>>>>>>>> On Tue, May 19, 2015 at 9:07 AM, Jamie Caldwell < >>>>>>>>>>> mr.jamie...@gmail.com > wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks Eric. I'll wait to hear...
>>>>>>>>>>>>
>>>>>>>>>>>> On 19 May 2015 at 13:53, Eric D Helms >>>>>>>>>>> > wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> You should definitely only need the client repositories and by
>>>>>>>>>>>>> the looks of it we have python-rhsm specified in our comps for that
>>>>>>>>>>>>> repository but not tagged into the repository. Good find! I will work on
>>>>>>>>>>>>> getting this fixed and reply to this thread when it's available.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, May 19, 2015 at 3:58 AM, JC >>>>>>>>>>>> > wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ok, now that I'm back in front of Foreman I realise a) that I
>>>>>>>>>>>>>> use that repo already and b) why I use both repos (
>>>>>>>>>>>>>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/5Server/x86_64/ and
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-5/x86_64/)...because
>>>>>>>>>>>>>> the later provides the missing dependency - python-rhsm (Jorick helped me
>>>>>>>>>>>>>> with this before).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So which repo should be updated?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Monday, 18 May 2015 17:36:44 UTC+1, JC wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Ahh, super. Cheers Eric, I'll give that a whirl.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 18 May 2015 at 17:01, Eric D Helms >>>>>>>>>>>>>> > wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I imagine the Candlepin team maintains that repository and
>>>>>>>>>>>>>>>> as such you'd have to contact them. However, for Katello itself, we
>>>>>>>>>>>>>>>> recommend using our client repositories. You'll note if you look at the EL5
>>>>>>>>>>>>>>>> client repository [1], we provide a version of subscription-manager so that
>>>>>>>>>>>>>>>> you can use the client repository directly (and so we provide a copy of
>>>>>>>>>>>>>>>> subscription-manager that works with our setup since EL5 is special).
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Eric
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [1]
>>>>>>>>>>>>>>>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/5Server/x86_64/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, May 18, 2015 at 11:18 AM, JC >>>>>>>>>>>>>>> > wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The repodata for the above is using sha256, but as it is
>>>>>>>>>>>>>>>>> presumably intended for CentOS/RHEL 5 clients, shouldn't it be sha1?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I can tell Katello that it is sha256, which gets me past
>>>>>>>>>>>>>>>>> the 'the download doesn't match' message, but then I'm left with a sha256
>>>>>>>>>>>>>>>>> local repo which CentOS 5 clients can't use.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> Jamie.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [I think I had this problem earlier, but if I did, I can't
>>>>>>>>>>>>>>>>> think how I got round it! At least not without manually running a
>>>>>>>>>>>>>>>>> createrepo]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> You received this message because you are subscribed to
>>>>>>>>>>>>>>>>> the Google Groups "Foreman users" group.
>>>>>>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails
>>>>>>>>>>>>>>>>> from it, send an email to foreman-user...@googlegroups.com
>>>>>>>>>>>>>>>>> .
>>>>>>>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>>>>>>>> forema...@googlegroups.com .
>>>>>>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>>>>>>>>>>>>> .
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> You received this message because you are subscribed to a
>>>>>>>>>>>>>>>> topic in the Google Groups "Foreman users" group.
>>>>>>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>>>>>>>>>>>> .
>>>>>>>>>>>>>>>> To unsubscribe from this group and all its topics, send an
>>>>>>>>>>>>>>>> email to foreman-user...@googlegroups.com .
>>>>>>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>>>>>>> forema...@googlegroups.com .
>>>>>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Jamie.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>>>>>> Google Groups "Foreman users" group.
>>>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>>>>>>>>> it, send an email to foreman-user...@googlegroups.com
>>>>>>>>>>>>>> .
>>>>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>>>>> forema...@googlegroups.com .
>>>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> You received this message because you are subscribed to a
>>>>>>>>>>>>> topic in the Google Groups "Foreman users" group.
>>>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>>>>>>>>> .
>>>>>>>>>>>>> To unsubscribe from this group and all its topics, send an
>>>>>>>>>>>>> email to foreman-user...@googlegroups.com .
>>>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>>>> forema...@googlegroups.com .
>>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Jamie.
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>>>> Google Groups "Foreman users" group.
>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>>>>>>> it, send an email to foreman-user...@googlegroups.com
>>>>>>>>>>>> .
>>>>>>>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>>>>>>>> .
>>>>>>>>>>>> Visit this group at
>>>>>>>>>>>> http://groups.google.com/group/foreman-users.
>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> You received this message because you are subscribed to a topic
>>>>>>>>>>> in the Google Groups "Foreman users" group.
>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>>>>>>> .
>>>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>>>> to foreman-user...@googlegroups.com .
>>>>>>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>>>>>>> .
>>>>>>>>>>> Visit this group at http://groups.google.com/group/foreman-users
>>>>>>>>>>> .
>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Jamie.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>> Google Groups "Foreman users" group.
>>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>>> send an email to foreman-user...@googlegroups.com .
>>>>>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>>>>>> .
>>>>>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>>> the Google Groups "Foreman users" group.
>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>>>> .
>>>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>>>> foreman-user...@googlegroups.com .
>>>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>>>> .
>>>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jamie.
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Foreman users" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to foreman-user...@googlegroups.com .
>>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>>> .
>>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to a topic in
>>>>>> the Google Groups "Foreman users" group.
>>>>>> To unsubscribe from this topic, visit
>>>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> foreman-user...@googlegroups.com .
>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>> .
>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jamie.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Foreman users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to foreman-user...@googlegroups.com .
>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>> .
>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Foreman users" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/foreman-users/AntO8Qc27OI/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> foreman-user...@googlegroups.com .
>>>> To post to this group, send email to forema...@googlegroups.com
>>>> .
>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>