migrated more from mcro #133
Merged
duke
merged 4 commits from jahway603/hush3:dev
into dev
2 years ago
Loading…
Reference in new issue
There is no content yet.
Delete Branch 'jahway603/hush3:dev'
Deleting a branch is permanent. It CANNOT be undone. Continue?
@jahway603 looks mostly groovy. What is the reason for the checksum change on utfcpp?
The reason for the different checksums is because gitea created it's own new *.tar.gz for a "Release", which had to be created manually.
@jahway603 I forked the repo to hush/utfcpp and made a new release with the exact file we used to have on Github, so the the SHA256 checksum is now the same. Please update this PR to use https://git.hush.is/hush/utfcpp/releases/tag/3.1 and don't change the checksum, and it should work. Thanks!
Fresh git clone and changed it to use the hush/utfcpp release, but it bombs because of a hashing error. I don't know how to force this utfcpp.mk file to download that exact file you want...
What I do see is the following... which has a changed checksum in the release you just created...
I was only able to succesfully build hush by changing the utfcpp sha256sum hash to
eb4d5b9843a8411a20da8d011983e5351bf6c5893814f6756de8a31392185a98
which is the same hash as the file https://git.hush.is/hush/utfcpp/archive/v3.1.tar.gz@jahway603 sorry, the filename to download is now: https://git.hush.is/attachments/11822fe4-3846-4ce4-9c84-ba0877a7b186
which is the file uploaded to the release, not the auto-generated file from Gitea, which has a different checksum.
I'm well aware of what you're saying.
What I am asking is - how do I force the Hush build system (in depends/packages/utfcpp.mk) to use that "special" or unique gitea filename?
@jahway603 change
$(package)_download_path
tohttps://git.hush.is/attachments/
and$(package)_file_name
to11822fe4-3846-4ce4-9c84-ba0877a7b186
should hopefully workIt definitely does not like that, lol
@jahway603 that output looks like it's trying to download
https://git.hush.is/attachments/v3.1.tar.gz
which isn't write, push a commit and I can take a look@duke had to also change
$(package)_download_file
to11822fe4-3846-4ce4-9c84-ba0877a7b186
and now it builds fine with it@jahway603 good enough for me 👍
7d2427074d
into dev 2 years ago7d2427074d
.