<div>Hi,</div>
<div> </div>
<div>Just as a follow-up to my last note: as of 2.1.3, setting the checksum-type to sha or sha1 was not sufficient. You will still end up with groupinfo and updateinfo metadata files created with sha256 checksums unless you change the Python for modifyrepo.</div>
<div> </div>
<div>/usr/share/createrepo/modifyrepo.py</div>
<div> </div>
<div>Christina<br></div>
<div class="gmail_quote">On Mon, Dec 16, 2013 at 1:35 PM, Barnaby Court <span dir="ltr"><<a href="mailto:bcourt@redhat.com" target="_blank">bcourt@redhat.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi, When you create a repo you can manually specify the checksum using the --checksum-type flag. For sha I would recommend using "sha1" as the value in order to be as clear as possible as to which checksum type you mean. Regards,<br>
<br>Barnabhy<br>
<div class="HOEnZb">
<div class="h5"><br>----- Original Message -----<br>From: "Tim Bielawa" <<a href="mailto:tbielawa@redhat.com">tbielawa@redhat.com</a>><br>To: "Josh Baird" <<a href="mailto:jbaird@follett.com">jbaird@follett.com</a>>, <a href="mailto:pulp-list@redhat.com">pulp-list@redhat.com</a><br>
Sent: Monday, December 16, 2013 1:26:42 PM<br>Subject: Re: [Pulp-list] Creating RHEL 5 compatible yum repositories<br><br>Thanks for the lightning-fast response!<br><br>How about the specific use case of creating a net-new repository of<br>
'SHA' type? Syncing repositories is working well for us<br><br>It's creating new ones which are giving us issues.<br><br><br>"Baird, Josh" <<a href="mailto:jbaird@follett.com">jbaird@follett.com</a>> writes:<br>
<br>> Hi,<br>><br>> This was fixed in 2.3.0 [1]. We are successfully syncing RHEL5 repositories with 2.3+.<br>><br>> [1] - <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1029057" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1029057</a><br>
><br>> Thanks,<br>><br>> Josh<br>><br>> -----Original Message-----<br>> From: <a href="mailto:pulp-list-bounces@redhat.com">pulp-list-bounces@redhat.com</a> [mailto:<a href="mailto:pulp-list-bounces@redhat.com">pulp-list-bounces@redhat.com</a>] On Behalf Of Tim Bielawa<br>
> Sent: Monday, December 16, 2013 1:18 PM<br>> To: <a href="mailto:pulp-list@redhat.com">pulp-list@redhat.com</a><br>> Subject: [Pulp-list] Creating RHEL 5 compatible yum repositories<br>><br>> Prelude: This is in response to BZ1042208 [0], "rpm metadata ignores --checksum-type from repository"<br>
><br>> Has anyone else experienced issues/victories using pulp 2.1+ to create YUM repositories which are compatible with RHEL 5?<br>><br>> Specifically, I am referring to pulp setting/not setting the checksum type of a newly created repository correctly?<br>
><br>> I have a large number of RHEL 5 boxen to maintain and when we migrated to Pulp 2.1 from 1.x we began seeing an issue where:<br>><br>>> pulp-admin ... rpm repo create --checksum-type sha ...<br>><br>
> does not honor the '--checksum-type' option [1], and instead creates all new repositories of type SHA256. This causes a backwards compatibility issue with our RHEL 5 boxes who only support the SHA checksum type.<br>
><br>> I am aware of the python-hashlib package, and have verified that installing it successfully allows RHEL 5 boxen to consume repositories of the SHA256 checksum type. However, IMHO this is a non-obvious work around, and not a change I (or other system administrators) can potentially make across my entire RHEL 5 infrastructure without a lot of coordination and approvals.<br>
><br>> Thanks for any advice!<br>><br>><br>> [0] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1042208" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1042208</a><br>> [1] <a href="https://github.com/juicer/juicer/issues/202" target="_blank">https://github.com/juicer/juicer/issues/202</a><br>
><br>> --<br>> Tim Bielawa, Senior Release Engineer/Scribe, Inception Why Should I Care What Color the Bikeshed Is?<br>> <a href="http://bikeshed.com/" target="_blank">http://bikeshed.com/</a><br>> <a href="tel:919.332.6411" value="+19193326411">919.332.6411</a> Cell | IRC: tbielawa (#inception)<br>
> 1BA0 4FAB 4C13 FBA0 A036 4958 AD05 E75E 0333 AE37<br><br>--<br>Tim Bielawa, Senior Release Engineer/Scribe, Inception<br>Why Should I Care What Color the Bikeshed Is?<br> <a href="http://bikeshed.com/" target="_blank">http://bikeshed.com/</a><br>
<a href="tel:919.332.6411" value="+19193326411">919.332.6411</a> Cell | IRC: tbielawa (#inception)<br>1BA0 4FAB 4C13 FBA0 A036 4958 AD05 E75E 0333 AE37<br><br></div></div>
<div class="HOEnZb">
<div class="h5">_______________________________________________<br>Pulp-list mailing list<br><a href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/pulp-list" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a><br>
<br>_______________________________________________<br>Pulp-list mailing list<br><a href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/pulp-list" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a><br>
</div></div></blockquote></div><br>