On 08.11.2018 17:09, Michael Tremer wrote:
Hey,
thanks for reporting. This is a bug introduced in the last commits.
Variables were initialized before the architecture was corrected. Fixed here:
https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=8a0bc0345002d8a635f7...
Thanks!
Tested - seems to work here on a Duo Box (but I think it would be good if someone else could test this, too)...
Best, Matthias
Best, -Michael
On Thu, 2018-11-08 at 16:36 +0100, Matthias Fischer wrote:
Hi,
I got something weird here:
I just tried to test the new 'backupiso' and 'backup.pl'-scripts from next.
'backupiso' tells me that "arch is i586", but tries to download "...2.21.*i686*..."!?
Hardware: Duo Box
Output of 'uname -m': root@ipfire: /usr/local/bin # uname -m i686
***SNIP*** root@ipfire: /usr/local/bin # ./backupiso /tmp/test_backup Your arch is i586 Fetching
https://downloads.ipfire.org/releases/ipfire-2.x/2.21-core124/ipfire-2.21.i6...
Fetching
https://downloads.ipfire.org/releases/ipfire-2.x/2.21-core124/ipfire-2.21.i6...
Checking md5 of ipfire-2.21.i686-full-core124.iso md5sum: ipfire-2.21.i686-full-core124.iso.md5: no properly formatted MD5 checksum lines found md5 mismatch Fetching again
https://downloads.ipfire.org/releases/ipfire-2.x/2.21-core124/ipfire-2.21.i6...
Checking again md5 of ipfire-2.21.i686-full-core124.iso md5sum: ipfire-2.21.i686-full-core124.iso.md5: no properly formatted MD5 checksum lines found md5 mismatch aborting backup because md5 mismatch ***SNAP***
Can anyone confirm - or tell me whats going on here?
Best, Matthias