public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New backup scripts don't work
Date: Thu, 08 Nov 2018 16:48:36 +0000	[thread overview]
Message-ID: <d9c99e85bd01219da908ff1f09c1b5bfb6939499.camel@ipfire.org> (raw)
In-Reply-To: <8de5a0a4-b3c1-a1bd-fb97-db5f31115354@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2317 bytes --]

I guess this is fine on all architectures where the architecture does not have
to be rewritten. i586 was the odd one out.

Thanks for testing!

Best,
-Michael

On Thu, 2018-11-08 at 17:40 +0100, Matthias Fischer wrote:
> 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=8a0bc0345002d8a635f7c9baa08c8e4ee85696ae
> 
> 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(a)ipfire: /usr/local/bin # uname -m
> > > i686
> > > 
> > > ***SNIP***
> > > root(a)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.i686-full-core124.iso
> > > Fetching
> > > 
> > 
> > 
https://downloads.ipfire.org/releases/ipfire-2.x/2.21-core124/ipfire-2.21.i686-full-core124.iso.md5
> > > 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.i686-full-core124.iso
> > > 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
> > 
> > 
> 
> 


      reply	other threads:[~2018-11-08 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 15:36 Matthias Fischer
2018-11-08 16:09 ` Michael Tremer
2018-11-08 16:40   ` Matthias Fischer
2018-11-08 16:48     ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9c99e85bd01219da908ff1f09c1b5bfb6939499.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox