Project

General

Profile

Bug #2033

systemd/LXDE netinstall Graphical Installer fails to install the system

james - about 1 year ago - . Updated 10 months ago.

Status:
open
Priority:
broken
Category:
Installer
Assignee:
% Done:

0%


Description

The installation fails while attempting to wipe the current (NVME) ssd, giving error: target not found: unar

This prevents installation of the OS through the graphical installer. I know it's still under development, and I think I can help with this.

uname -a
Linux parabolaiso 4.16.13-gnu-1 #1 SMP PREEMPT Sat Jun 2 05:58:26 UTC 2018 x86_64 GNU/Linux


Files

install-sanitized.log (59.3 KB) install-sanitized.log Let me know if I left any sensitive information in ;) james, 2018-10-10 10:53 PM

Related issues

Related to Installation media - Bug #2132: [unar]: Broken dependency icu<62not-a-bug

Actions

History

#1

Updated by bill-auger about 1 year ago

the temporary fix for that ISO is to run this command before installing:

$ sudo sed -i 's|unar|unarchiver|' /usr/share/calamares/modules/pacstrap-base/pacstrap-base.conf
#2

Updated by james about 1 year ago

i've just been told to be hesitant to share drive details, serial numbers, etc. forgive me for my paranoia

#3

Updated by james about 1 year ago

Looks like it's just an issue with pacstrap:

2018-10-10 - 18:44:28 [1]: [PACSTRAP]: shell command exited= "pacman -S --print --config /etc/pacman.conf --root /tmp/calamares-root-ptd8h_cs grub grub2-theme-gnuaxiom mkinitcpio-openswap linux-libre bash-completion p7zip sudo unar unzip zip base gpm haveged hdparm networkmanager ntp openssh openvpn rsync wpa_supplicant"

It exits because unar is no longer in the registry. Any way I can modify this from inside the LiveBoot environment?

#4

Updated by bill-auger about 1 year ago

  • Priority changed from bug to broken
  • Assignee set to bill-auger
  • Category set to Installer

the package lists can be edited easily if you want to

$ sudo sed -i 's|unar|unarchiver|' /usr/share/calamares/modules/pacstrap-base.conf

#5

Updated by bill-auger about 1 year ago

can you tell me why you thought the log needed scrubbing?

#6

Updated by james about 1 year ago

no reason. i'm not familiar with the content of the log, so i don't know if anything needed scrubbing

#7

Updated by freemor about 1 year ago

Could this be solved for the time being by creating a unar metapackage that:
requires: unarchiver
Provides: unar

or the like. and just keep it about until new ISOs are rolled and we are fairly certain that most people are off the old ones?
Or am I just being bonkers here

#8

Updated by bill-auger about 1 year ago

  • Subject changed from LXDE systemd netinstall Graphical Installer Still using unar rather than unarchive to systemd/LXDE netinstall Graphical Installer fails to install the system
#9

Updated by bill-auger 10 months ago

  • Related to Bug #2132: [unar]: Broken dependency icu<62 added
#10

Updated by james 10 months ago

Speaking of new ISOs, when are they coming? Alternatively, can I get the source code to build my own "master" branch ISO?

#11

Updated by james 10 months ago

FIX IF YOU DON'T CARE ABOUT SECURITY

This doesn't really relate to the installer script method, but if you're manually installing using pacstrap and you run into the dependency issue (#2132) just disable keychecking in /etc/pacman.conf lol

GPG, who needs it?

#12

Updated by freemor 10 months ago

The advice above is completely wrong for the unar issue

unar is deprecated and no longer in the repos - thus the failure. If you are installing manually just use unarchiver instead of unar

The advice is also wrong for almost ALL gpg/keyring issues. Those are easy to fix with re-syncing the keyrings with the current.

In almost NO circumstances should the above "disable checking" be used

#13

Updated by james 10 months ago

Well yeah, I mean, the circumstance the above is for is if you can't re-sync the keyrings.

#14

Updated by bill-auger 10 months ago

james i dont understand your issue today - what do you mean "can't re-sync the keyrings"

all you need to do to get the installer to work on that ISO is apply the sed command above, then reset the keyring as explained on this wiki page

i hope you have not been waiting 4 months for the new ISO - i apologize for the delay but i have been very busy lately and i just did not consider this to be so fatally broken yet as to be a high-priority

you can always build your own ISO from source, though in this case, the very same change described above would need to be applied at the source level (though, i think i made that code change already - i cant remember) - somewhat simpler, you could also use the remastering method and simply apply that sed line to the image file-system then repack it - but if all you are trying to do is install once, then either of those are just more difficult ways to accomplish the thing you can do with the ISO you have

come onto the IRC if you can - i have walked several people through this - it takes only minutes

Also available in: Atom PDF