On 11/2/21 9:37 AM, ste...@eissing.org wrote:
>
>
>> Am 02.11.2021 um 09:24 schrieb Ruediger Pluem <rpl...@apache.org>:
>>
>> I tried to fix the below with r1894662:
>>
>> Index: r3-push-release-tars.sh
>> ===================================================================
>> --- r3-push-release-tars.sh (revision 1894661)
>> +++ r3-push-release-tars.sh (working copy)
>> @@ -86,6 +86,11 @@
>> dest=`echo $file | sed -e "s/${FULL_VERSION}/${VERSION}/"`
>> svn mv "$file" "$dest"
>> done
>> + # fix the filenames in the hash files (PR65665)
>> + echo "fixing ${FULL_VERSION} filename to ${VERSION} in hash files"
>> + for file in
>> "${AO_DIST_RELEASE_PATH}/${PROJECT}-${FULL_VERSION}".tar.*.sha* do
>> + perl -pe "s/${FULL_VERSION}/${VERSION}/" -i $file
>> + done
>> fi
>> svn mv "${AO_DIST_DEV_PATH}/CHANGES_${VERSION}" "${AO_DIST_RELEASE_PATH}"
>
>
> I think the files have already been renamed at that point, so it should be
Good catch. I missed this.
>> + for file in "${AO_DIST_RELEASE_PATH}/${PROJECT}-${VERSION}".tar.*.sha* do
>> + perl -pe "s/${FULL_VERSION}/${VERSION}/" -i $file
>> + done
>
>
> (and we should also no more generated the .md5, I assume). Maybe no even the
> .sha1.
I missed to run against these, because they are no longer available on the
download page. Hence a good point to remove their
generation. The only use case they could have nowadays I can think of is for
users of old platforms that lack the tools for
checking newer hashes. OTOH these people would need to build httpd either
without SSL or against a very outdated version of
OpenSSL that does not provide modern hashes which seems weird too. So I think
no real use cases any longer :-).
Regards
Rüdiger
