checksum mismatch

[LhAlant]

The checksum is mismatched
Computed checksum:
--- Repository SHA-256: ---

 3825904fb49d3cd9
 cea3ca538fd6f471
 648be88911c4746a
 1cf71e02f334dc00

---

Expected checksum:

     ba2015db643a0dd6
     e78bbf92f27f76ae
     0797feb78874edb4
     19d14a8b54373269

Checksums for the GetRepositorySignature.* files match.
The PGP signed message was signed by LAX1DUDE.

Avoid using this copy of the repo, it is not authentic.

[wxnnvs]

Bro

[wxnnvs]

Its because its a reupload

[magmaus3]

shouldn't an reupload have the same checksum though?

[wxnnvs]

No

[magmaus3]

No

why not? shouldn't a correct copy not cause checksum mismatches unless it was modified?

[lDEVinux]

yall i don't know.

if you don't want to use it i don't care but I have no idea why the checksum isn't the same. I forked it before the original was put down and I never touched it.

[BytelyPlay]

Hey, the commit history is definitely not the original commit history
i assume he didn't use the fork button and instead just downloaded the .zip file and then commited and pushed it which doesn't save the old commit history
the .git folder would be different because the repository's commit history is different
and either way you put your device at risk just by running the .bat which runs the .jar
either forking or using git clone instead would have given the same commit history as the original repo