Summary: | Cu 163, 164, 165 RC: "backupctrl restore" broken | ||
---|---|---|---|
Product: | IPFire | Reporter: | Manfred Knick <Manfred.Knick> |
Component: | --- | Assignee: | Michael Tremer <michael.tremer> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Major Usability | ||
Priority: | - Unknown - | CC: | adolf.belka, michael.tremer, peter.mueller |
Version: | 2 | ||
Hardware: | x86_64 | ||
OS: | Unspecified |
Description
Manfred Knick
2022-03-20 20:06:49 UTC
My profile ID: ebc1539924251781ecb8481a7c9d2691eae5258f How are you running this command? From a regular console after logging in? What is the value of your PATH variable? - New fresh install onto empty disk - Login as "root" - from console / command line - same after reboot (In reply to Michael Tremer from comment #2) > What is the value of your PATH variable? Thank you. Could you please post this, too? (In reply to Michael Tremer from comment #4) > > ... PATH variable? > > Thank you. Could you please post this, too? You're welcome. I fear, digging into this would imply even another "erase", "fresh install" and afterwards "configure" cycle - because now, at least via ssh: # echo $PATH /usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/root/bin ! . . NOTE: As descibed in my referenced forum post: ! . . ! . . . . . “which …” locates them at /user/local/bin indicating that "/user/local/bin" seems to have been member of $PATH as far as seen from the console environment. The question remains: ? Why were they not found *from* *inside* /var/ipfire/backup/bin/backup.pl ? directly after fresh install which was confirmed by Jon as well and can still be re-produced with . . . ipfire-2.27.x86_64-full-core165.iso . . . nightly.ipfire.org > master > x86_64 > 2022-03-17_03-43 Hth. Thank you. This patch fixes this problem:
> https://patchwork.ipfire.org/project/ipfire/patch/20220321190706.2969988-1-michael.tremer@ipfire.org/
AFAICS in ipfire-2.x.git, it has been committed to "next" = core166. Thank you! @Peter: Could this very helpful "one-liner" be included into "master" = core165 as well? Hi,
> Could this very helpful "one-liner" be included into "master" = core165 as well?
I have no authority to commit into the "master" branch.
Therefore, I would like to pass this decision on to Michael or Arne.
Thanks, and best regards,
Peter Müller
This change is going to be left in c166. If we would merge this into c165 last minute, it would be effectively released untested which is not what we want. Core Update 166 containing the fix for this bug has been released. https://blog.ipfire.org/post/ipfire-2-27-core-update-166-released Fix confirmed in a CU166 vm setup. |