manjaro-architect
manjaro-architect copied to clipboard
Error: ERROR [install basepkgs][255]
Medium: Following error is returned if any of the package already exist on file system. Understandable for packages on "/" but for the boot partition it fails on following for example: grub (folder) memtest (folder) kernels with the same name
This does not occur on an arch install, can it be because user is manjaro and not root? This also does not occur with calamares installer where it overwrites whatever you have. Does m-a needs to handle multiboot or is it for single boot system only?
Could you post the error output? Difference is between calamares and manjaro-architect and calamares is that calamares unpacks and copies files, while manjaro-architect installs packages with pacman. Pacman does not overwrite packages that are not managed by it.
M-a handles multiboot, but there are limitations. Your example sounds like you have multiple installations sharing one /boot partition, which inherently problematic. There can be conflicting files, and if said /boot is also the ESP, it gets filled pretty fast with kernels. Summa summarum, manjaro-architect handles multiboot but cannot make guarantees about shared /boot working.
Maybe we should modify the ESP mounting message? /boot/efi is usually preferable mount point. Systemd-boot requires /boot. Refind requires unencrypted /boot and this can be achieved mounting ESP at /boot if root is encrypted.
Haven't save the error output, but it was the standard file already exist blablabla. Also why does the installer install grub/memtest when the choice is made for systemd-bootloader?
Here is the error message: https://cloud.githubusercontent.com/assets/25054585/26274857/11fb33ea-3d54-11e7-85fc-a5272133e12e.png
Ok. Shared boot partition, files with same name. There is no clean way to implement this. The best we could do is somehow pass --force flag to basestrap, which would effectively mean forking it.
Also, it is questionable if this is desirable behavior to begin with. In principle distros should not overwrite each others files. Also, if it works,does it encourage bad practice? That is, sharing system participations between distros.
Then again, spirit of manjaro-architect is to enable user what he wants, not force them to do what is smart...
I would prefer an answer to second question :)
Also why does the installer install grub/memtest when the choice is made for systemd-bootloader?
If an user has 2 installs (gnome, kde) with different kernels, the install would still fail because of grub and memtests while he wants to use refind or systemd boot loader.
It should not install them, that is a bug that needs to be swatted.
I would argue that the problem is sharing the /boot partition. Systemd-boot requires mounting esp to /boot, but systemd-boot is not made for multibooting linux distributions. The lack of autodetection reflects this.
Manjaro-architect handles multiboot, but properly only with grub or refind + other installations bootloaders.
Anyway, plan for the next commit is now:
- ensure grub and are installed only if necessary
- renew systemd-boot section:
- generate also fallback entries (unless removable device)
- if installation exists, just add new entries for the installed kernels
I think the content of the base package is pulling to much configuration stuff already which is duplicated with the options further in the setup. You don't notice it if you install everything, but if you install/check step by step you are installing more then you selected. Don't know the impact on the complete iso builds of that if they are part of the base profiles.
Instead of base group we install filtered https://github.com/manjaro/iso-profiles/blob/master/shared/Packages-Root. We can filter it a bit further still.
I'm attempting to install Manjaro-Kde_20.2.1 in VirtualBox 6 using LVM to extend a 20GB VDI to the 50GB VDI for the base system and everything works as advertised until I attempt to install the Manjaro Base by choosing both yay and the latest Linux kernel and the KDE desktop. After all files are downloaded, and I come to the screen asking to install all 255 downloaded packages, when I press the Enter key to select OK, I get the message: "Installation Failed". This is 100% reproducible. Nothing I try allows this to go forward.
When will M-a be fixed?
Weekly. This same error can be caused by several different issues, and it resurfaces regularly and needs to be fixed repeatedly by updating the profiles.
It would be useful to have some log files and more specific errors to fix this.