NotQball wrote on July 24, 2024 at 2:33 PM

http://skank.i2p/installers/i2pinstall_2.6.0+.exe inside i2p+ also fails on Motrix error 19: If name resolution failed. Similar with other down-loaders including browser.

I2P: 2.6.0-0+ API: 0.9.63 Wrapper: 3.5.51 Built by: dr|z3d Platform: Linux amd64 6.8.9-1kaisen-amd64 Processor: coreibwl Skylake Core i3/i5/i7 [Jcpuid version: 3] Java: N/A 21 (OpenJDK Runtime Environment 21+-adhoc.nixbld.source) Jetty: 9.3.30.v20211001 Servlet: Jasper JSP 2.3 Engine (3.1) JBigI: Native BigInteger library libjbigi-linux-coreibwl_64.so loaded from resource [version: 4] GMP: 6.1.2 JSTL: standard-taglib 1.2.0 Encoding: UTF-8 Charset: UTF-8

sha256sum i2p+ torrent downloaded: 736f38a5ac5121d33b7576cb1f61e6a9b5a28008b82795fdb31c7fb00dfd9b56

sha512sum i2p+ downloaded:

898866b715e8a32cd87d559a61d48b0d5c644d695807389f0d02bc87561cd949771e09c926df248cb422ca99b78c16dc70d375b2f64c42b4d3d70f631f29d29d

z3d OP wrote on July 25, 2024 at 2:54 AM (edited on July 25, 2024 at 4:12 PM)

Differences in the sha hashes are a result of infrequent updates to the i2pupdate.zip being served from http://skank.i2p/i2pupdate.zip ... occasionally a new update will appear, either to add new features (in the recent case, more complete translations) or fix bugs. To identify exactly which revision you're running, you can view the hashes on 127.0.0.1:7657/jars.

In addition, for some users a new release will revert them to vanilla I2P, so updating the I2P+ zip available on skank.i2p will sometimes fix this if it's date stamped after the update to vanilla.

As for "corrupt" downloads, if you're in the middle of an update when a new version is uploaded, your download will become corrupted, in which case re-downloading the update should fix. It shouldn't happen for release updates very often, slightly more chance when updating from the /dev/ path as that's sometimes updated several times a day.