Closed Xeno-Hypster closed 4 years ago
Please mention the maintainer when submitting issues.
=> /home/dylan/projects/community/community/sbase
Cem Keylan <cem@ckyln.com>
-> kiss-maintainer ubase
=> /home/dylan/projects/community/community/ubase
Cem Keylan <cem@ckyln.com>
@cemkeylan
No worries, will do in the future.
I don't have any issues, is this because of the checksums behaviour change @dylanaraps ?
@cemkeylan It could be related to that, yes. The only issue I see is that I explicitly tried to make this backwards (or forwards(?)) compatible.
Will push a fix in a few minutes. :+1:
When I am doing with upstream kiss, it says checksum mismatch, when I am doing with my fork it doesn't. I should update the checksums anyway.
Okay, it works now, should I update the checksums regardless?
No. It's fine. Pushed a new package manager release.
If you decide to follow the same checksum changes, these checksums will over time match the new scheme whenever the checksums are updated. The KISS package manager supports both formats rather easily so there's no rush. I foresee us living in this transition period for some time. :+1:
The scheme is just:
<checksum>
<checksum>
etc
Hi, I'm getting a checksum mismatch when attempting to build both sbase/ubase.
kiss b sbase
-> Resolving dependencies
-> Building: sbase
-> sbase Checking repository files
-> Checking for pre-built dependencies
-> sbase Downloading sources
-> sbase Found local relative source 'patches/tar-dash-remove.patch
-> sbase Checksum mismatch
ERROR Checksum mismatch with: sbase