New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chksum files for images do not reflect actual filenames #413
Comments
packages: 578a7c506 tinc: update to 1.0.35 fe3eb92a4 Merge pull request #7165 from pacien/181009-1701-pkg-tinc c3109a256 tiff: security bump to 4.0.10 94685f7a7 Merge pull request #7555 from micmac1/tiff-4010-17.01 6fdeb2df9 sqlite3: security bump d309d0090 sqlite3: use dynamic linking for sqlite cli tool b04fe7f74 Merge pull request #7723 from micmac1/lede-17.01-sqlite3 Luci: c04c81f0d timezone data: update to 2018e 2cb704f63 timezone data: update to 2018f 883f66f70 timezone data: update to 2018g 27ff6e930 freifunk profiles: add nameserver 80.67.169.40 from www.fdn.fr/actions/dns 3f16979c2 community-profiles: create profile for Fürstenwalde f4f063252 community-profiles: change subnet of mesh_network option for Berlin 8a3100c14 Merge pull request #2354 from pmelange/freifunk_backport_17.01 routing: 2ac8e7b batman-adv: Merge bugfixes from 2018.3 ad22c77 Merge pull request #413 from ecsv/batadv-17.01 2c8de62 batman-adv: Merge bugfixes from 2018.4 216512c Merge pull request #424 from ecsv/batadv-17.01
@Akira25 reported (freifunk-berlin/buildbot#61) that with Lede-17.01 based firmwares the chksum file is broken even more (it just contains a single file). I just had a look in the firmware-directory of a recent build (master branch based on OpenWrt-19.07) where this problem seems to have been fixed. |
probably that's a reason, why gluon is using it's own script for calculation the chksums (https://github.com/freifunk-gluon/gluon/blob/master/scripts/sha256sum.sh) |
since #178 the imagenames of the firmware-files get changed. But the contens of
md5sums
andsha256sums
still have the old / original filenames inside.The text was updated successfully, but these errors were encountered: