Tools issueshttps://gitlab.manjaro.org/groups/tools/-/issues2024-03-28T04:40:10Zhttps://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/344Fix for an error and Warning in the mkinitcpio command in the prepare_initram...2024-03-28T04:40:10ZphoepsilonixFix for an error and Warning in the mkinitcpio command in the prepare_initramfs function in utils-iso-boot.sh.(WARNING: errors were encountered during the build. The image may not be complete.)```
==> Prepare [/iso/boot]
--> overlayfs mount: [/var/lib/manjaro-tools/buildiso/gnome/x86_64/bootfs]
-> Copying initcpio ...
<skip>
==> Creating xz-compressed initcpio image: '/boot/initramfs.img'
WARNING: errors were encounte...```
==> Prepare [/iso/boot]
--> overlayfs mount: [/var/lib/manjaro-tools/buildiso/gnome/x86_64/bootfs]
-> Copying initcpio ...
<skip>
==> Creating xz-compressed initcpio image: '/boot/initramfs.img'
WARNING: errors were encountered during the build. The image may not be complete.
```
One reason for this is that the symbolic links for libnss_files.so.2 and libnss_dns.so.2 do not exist in the glibc package.
We suggest commenting out the add_symlink in in miso_pxe_common.
```diff
diff --git a/initcpio/install/miso_pxe_common b/initcpio/install/miso_pxe_common
index eec9a7e..3d935f1 100644
--- a/initcpio/install/miso_pxe_common
+++ b/initcpio/install/miso_pxe_common
@@ -8,9 +8,9 @@ build() {
add_binary /usr/lib/initcpio/ipconfig /bin/ipconfig
# Add hosts support files+dns
- add_symlink /usr/lib/libnss_files.so.2 $(readlink /usr/lib/libnss_files.so.2)
+ #add_symlink /usr/lib/libnss_files.so.2 $(readlink /usr/lib/libnss_files.so.2)
add_binary $(readlink -f /usr/lib/libnss_files.so.2)
- add_symlink /usr/lib/libnss_dns.so.2 $(readlink /usr/lib/libnss_dns.so.2)
+ #add_symlink /usr/lib/libnss_dns.so.2 $(readlink /usr/lib/libnss_dns.so.2)
add_binary $(readlink -f /usr/lib/libnss_dns.so.2)
add_dir /etc
```https://gitlab.manjaro.org/tools/development-tools/manjaro-chrootbuild/-/issues/9sometimes cannot download sources2023-10-01T09:07:38ZJozef Mlichsometimes cannot download sourcesI was trying to rebuild few packages in the row and I have seen following error message:
```
==> Validating source files with sha256sums...
1.32.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
```
I...I was trying to rebuild few packages in the row and I have seen following error message:
```
==> Validating source files with sha256sums...
1.32.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
```
It looks like the sources wasn't downloaded at all.
The issue wasn't reproducible every time. I was using `-n`.
(whole script with PKGBUILDS is here)
https://github.com/nemomobile-ux/nemo-packaging/blob/0d37ebc13219cec89bca0ad91fe857d0c58c26b5/deploy4.sh#L55
so the command was:
```
chrootbuild -r /mnt/data/buildchroot -D -f -n -b arm-stable -p mce-headers
```
Unfortunately, the issue is not reproducible with clear chroot and build of single package.
In the end I have decided to provide extra packages via extra repository.https://gitlab.manjaro.org/tools/development-tools/manjaro-tools-livecd/-/issues/2pacman-key --populate fails.2023-07-21T05:37:26Zphoepsilonixpacman-key --populate fails.In the live environment,
pacman-key --populate fails if /etc/pacman.d/mirrorlist is not exist.
It would be better to run the mirror ranking script before pacman-init.service.
[0001-pacman-key-populate-fails.patch](/uploads/a78a5cea110d2...In the live environment,
pacman-key --populate fails if /etc/pacman.d/mirrorlist is not exist.
It would be better to run the mirror ranking script before pacman-init.service.
[0001-pacman-key-populate-fails.patch](/uploads/a78a5cea110d284f2f16c9d5305ba8f8/0001-pacman-key-populate-fails.patch)
Reference link:
[https://github.com/phoepsilonix/manjaro-tools-livecd/commit/e9d9c1f27a51c05e4a31cddb31d9e1d61ab5dbe8](https://github.com/phoepsilonix/manjaro-tools-livecd/commit/e9d9c1f27a51c05e4a31cddb31d9e1d61ab5dbe8)https://gitlab.manjaro.org/tools/development-tools/manjaro-chrootbuild/-/issues/7add option to install (specific) kernel to chrootfs2023-03-13T22:04:40ZBernhard Landaueradd option to install (specific) kernel to chrootfsIn some rare cases builds rely on the presence of a specific kernel.
Functionality can easily be achieved with an option `-X <kernel>`In some rare cases builds rely on the presence of a specific kernel.
Functionality can easily be achieved with an option `-X <kernel>`Bernhard LandauerBernhard Landauerhttps://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/335Locale en_IL should not exist - it's he_IL or en_US, en_GB etc.2022-03-02T00:39:55ZGalia BahatLocale en_IL should not exist - it's he_IL or en_US, en_GB etc.I've installed Manjaro with just English, and that was fine. When I added Hebrew on the Language menu (KDE settings > Regional settings > Language) some system text, like Pidgin's menus, then defaulted to Hebrew, even though English was ...I've installed Manjaro with just English, and that was fine. When I added Hebrew on the Language menu (KDE settings > Regional settings > Language) some system text, like Pidgin's menus, then defaulted to Hebrew, even though English was set as my main language and that had never changed.
I eventually found out that the environment variable LANG + /etc/locale.gen + /etc/locale.conf defined my locale/lang as en_IL, which does not exist AFAIK. Hebrew should be he_IL. Changing en_IL into en_US fixed everything.
Pidgin must've fell back to the secondary language, and when I didn't have one fell back to en_US.
So what I'm suggesting is:
1. Change en_IL into he_IL. I'm not sure where that is set in the source code, couldn't find it.
2. Show an error on the Languages menu if a locale is not found and fallbacks are used.
I'm not 100% sure this is the place to post this issue, but I found similar tickets here.https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/334Patch to handle /etc/resolv.conf is a symlink2022-01-18T13:45:36ZThenujan-0Patch to handle /etc/resolv.conf is a symlinkIn order to avoid the following error message i created a symlink of /run/NetworkManager/resolv.conf in /etc/resolv.conf
https://www.reddit.com/r/Windscribe/comments/cn2qfb/etcresolvconf_is_not_a_symlink_this_may_break_dns/
But when us...In order to avoid the following error message i created a symlink of /run/NetworkManager/resolv.conf in /etc/resolv.conf
https://www.reddit.com/r/Windscribe/comments/cn2qfb/etcresolvconf_is_not_a_symlink_this_may_break_dns/
But when using the manjaro-chroot script it fails to get my internet connection to chroot and shows mount point is a symbolic link to nowhere so i modified the script to check if /etc/resolv.conf is a symbolic link and if it is a symbolic link then use /run/NetworkManager/resolv.conf instead .
And now the script also shows the internet is not connected so internet access will not be available in chroot .
```
sudo manjaro-chroot -a ✔
[sudo] password for thenujan:
==> Mounting (Ubuntu) [/dev/sda2]
--> mount: [/mnt]
your /etc/resolv.conf is a symlink so using /run/NetworkManager/resolv.conf instead
root@manjaro-minion:/#
```
```
sudo manjaro-chroot -a 127 ✘ 51s
==> Mounting (Ubuntu) [/dev/sda2]
--> mount: [/mnt]
Internet is not connected you will not have internet connectivity inside chroot
root@manjaro-minion:/#
```
code that i added to util-mount.sh checks if connected to the internet by pinging google and if the internet is not connected then it doesn't mount /etc/resolv.conf or the /run/NetworkManager/resolv.conf .
if it is connected then it checks if the /etc/resolv.conf is a symlink,if it isnt a symlink then it mounts that file if it is a symlink,it uses /run/NetworkManager/resolv.conf instead
code that I added to manjaro-chroot does the same described above but when using manjaro-chroot manually
[da260aa088.patch](/uploads/f66a5b6eb23da733e816b0abf4006baa/da260aa088.patch)https://gitlab.manjaro.org/tools/development-tools/manjaro-docker/-/issues/5No Overview for Manjaro Docker images2021-12-18T12:44:37ZAndreyNo Overview for Manjaro Docker imageshttps://hub.docker.com/u/manjarolinux
It's not clear how these images were produced.
For example, https://hub.docker.com/r/archlinux/archlinux/ contains much more info.
(This was solved for manjaroarm images: https://gitlab.manjaro....https://hub.docker.com/u/manjarolinux
It's not clear how these images were produced.
For example, https://hub.docker.com/r/archlinux/archlinux/ contains much more info.
(This was solved for manjaroarm images: https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools/-/issues/43)https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/331buildiso fails because of missing packages due to outdated Packages-Mhwd2021-05-21T12:02:04ZAbuildiso fails because of missing packages due to outdated Packages-MhwdPossibly related issue
https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/325
This is what I get when running `buildiso -p myi3 -k linux510`:
```
error: target not found: catalyst-utils
error: target not found: l...Possibly related issue
https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/325
This is what I get when running `buildiso -p myi3 -k linux510`:
```
error: target not found: catalyst-utils
error: target not found: linux510-catalyst
error: target not found: linux510-nvidia-340xx
error: target not found: nvidia-340xx-utils
error: target not found: lib32-catalyst-utils
error: target not found: lib32-nvidia-340xx-utils
error: target not found: pangox-compat
error: target not found: catalyst-utils
error: target not found: linux510-catalyst
error: target not found: linux510-nvidia-340xx
error: target not found: nvidia-340xx-utils
error: target not found: lib32-catalyst-utils
error: target not found: lib32-nvidia-340xx-utils
error: target not found: pangox-compat
-> Copying mhwd package cache ...
building file list ... done
sent 17 bytes received 12 bytes 58.00 bytes/sec
total size is 0 speedup is 0.00
==> ERROR: File '/var/lib/manjaro-tools/buildiso/myi3/x86_64/mhwdfs/opt/mhwd/pkg/*pkg.tar*' not found.
==> No packages modified, nothing to do.
==> ERROR: A failure occurred in make_image_mhwd().
Aborting...
--> overlayfs umount: [/var/lib/manjaro-tools/buildiso/myi3/x86_64/mhwdfs]
==> ERROR: File /var/lib/manjaro-tools/buildiso/myi3/x86_64/mhwdfs/opt/mhwd/pkg/'*pkg.tar*' not found.
```
After digging a bit, I found that `buildiso -i` pulls `v18.0` profiles, where `Packages-Mhwd` contains entries that are no longer in the repos.
See:
https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/blob/master/lib/util.sh#L328
https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/blob/master/lib/util.sh#L838
Pulling v20.2 profiles manually fixes this issue.https://gitlab.manjaro.org/tools/maintenance-tools/boxit2/-/issues/2add option to blacklist packages synced from Arch2021-05-07T19:45:45ZGhost Useradd option to blacklist packages synced from ArchIn Boxit1, we have a blacklist file, where we can write which packages we don't want to sync in.
We need the same functionality with Boxit2, maybe a similar file or via the new GUI somehow.In Boxit1, we have a blacklist file, where we can write which packages we don't want to sync in.
We need the same functionality with Boxit2, maybe a similar file or via the new GUI somehow.https://gitlab.manjaro.org/tools/development-tools/manjaro-docker/-/issues/4pacman not working out of the box2021-02-25T11:49:48ZDanilo Pianinipacman not working out of the boxDockerfile:
```Docker
FROM manjarolinux/base
RUN pacman -Sy --noconfirm --debug gawk gnupg libgpg-error gnupg gpgme
```
Result on GitHub Actions:
```
docker build -t danysk/docker-manjaro-linux-with-yay:latest -t danysk/docker-manjaro-l...Dockerfile:
```Docker
FROM manjarolinux/base
RUN pacman -Sy --noconfirm --debug gawk gnupg libgpg-error gnupg gpgme
```
Result on GitHub Actions:
```
docker build -t danysk/docker-manjaro-linux-with-yay:latest -t danysk/docker-manjaro-linux-with-yay:2021-02-25T1248142021-02-25_1148 .
Sending build context to Docker daemon 99.33kB
Step 1/23 : FROM manjarolinux/base
latest: Pulling from manjarolinux/base
07d9dbb0ed02: Pulling fs layer
07d9dbb0ed02: Verifying Checksum
07d9dbb0ed02: Download complete
07d9dbb0ed02: Pull complete
Digest: sha256:c16c1acf04452be013e77bee0f5a62f9dc05949d9f99a101b512648521673417
Status: Downloaded newer image for manjarolinux/base:latest
---> 76710bd87296
Step 2/23 : RUN pacman -Sy --noconfirm --debug gawk gnupg libgpg-error gnupg gpgme
---> Running in 65ed4ffd47f9
debug: pacman v5.2.2 - libalpm v12.0.2
debug: config: attempting to read file /etc/pacman.conf
debug: config: new section 'options'
debug: config: HoldPkg: pacman
debug: config: HoldPkg: glibc
debug: config: HoldPkg: manjaro-system
debug: config: SyncFirst: manjaro-system
debug: config: SyncFirst: archlinux-keyring
debug: config: SyncFirst: manjaro-keyring
debug: config: arch: x86_64
debug: config: SigLevel: Required
debug: config: SigLevel: DatabaseOptional
debug: config: LocalFileSigLevel: Optional
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 70: including /etc/pacman.d/mirrorlist
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 73: including /etc/pacman.d/mirrorlist
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 76: including /etc/pacman.d/mirrorlist
debug: config: new section 'multilib'
debug: config file /etc/pacman.conf, line 82: including /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.conf
debug: setup_libalpm called
error: failed to initialize alpm library
(could not find or read directory: /var/lib/pacman/)
The command '/bin/sh -c pacman -Sy --noconfirm --debug gawk gnupg libgpg-error gnupg gpgme' returned a non-zero code: 255
```https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/328Stops at "( 5/35) Creating temporary files" when built on a system with kerne...2021-01-02T22:40:52ZTioStops at "( 5/35) Creating temporary files" when built on a system with kernel 5.10Using: `buildiso -p gnome` I am getting:
```
( 2/35) Registering binary formats...
Skipped: Current root is not booted.
( 3/35) Reloading system manager configuration...
Skipped: Current root is not booted.
( 4/35) Updating udev har...Using: `buildiso -p gnome` I am getting:
```
( 2/35) Registering binary formats...
Skipped: Current root is not booted.
( 3/35) Reloading system manager configuration...
Skipped: Current root is not booted.
( 4/35) Updating udev hardware database...
( 5/35) Creating temporary files..
```
And it simply stops there. So far for hours. I am not sure it does anything. All worked fine before the latest Manjaro updates.https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/327Options to set enabled calamares modules in profile.conf2020-10-28T22:17:47ZMatti HyttinenOptions to set enabled calamares modules in profile.confIt would be nice to be able to enable and disable certain calamares modules in profile.conf. This would come in handy for using gnome-initial-setup and possibly using the package selection module in the future.It would be nice to be able to enable and disable certain calamares modules in profile.conf. This would come in handy for using gnome-initial-setup and possibly using the package selection module in the future.Bernhard LandauerBernhard Landauerhttps://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/325buildiso fails with kernel 5.8.x because of missing nvidia packages2021-05-21T12:02:06ZTNT2kbuildiso fails with kernel 5.8.x because of missing nvidia packagesHi, running `buildiso -f -p xfce -b stable -t ~/iso_out`
results in
```Root : /
Conf File : /etc/pacman.conf
DB Path : /var/lib/pacman/
Cache Dirs: /var/cache/pacman/pkg/
Hook Dirs : /usr/share/libalpm/hooks/ /etc/pacman.d/hoo...Hi, running `buildiso -f -p xfce -b stable -t ~/iso_out`
results in
```Root : /
Conf File : /etc/pacman.conf
DB Path : /var/lib/pacman/
Cache Dirs: /var/cache/pacman/pkg/
Hook Dirs : /usr/share/libalpm/hooks/ /etc/pacman.d/hooks/
Lock File : /var/lib/pacman/db.lck
Log File : /var/log/pacman.log
GPG Dir : /etc/pacman.d/gnupg/
Targets : linux54-bbswitch linux54-broadcom-wl linux54-zfs zfs-utils linux54-virtualbox-guest-modules linux54-headers zfs-dkms libva-intel-driver libva-mesa-driver libva-vdpau-driver lib32-libva-vdpau-driver libxaw libxpm libxvmc mesa-vdpau lib32-mesa-vdpau lib32-libxvmc lib32-primus linux54-nvidia-455xx nvidia-455xx-utils lib32-nvidia-455xx-utils opencl-mesa open-vm-tools primus bumblebee nvidia-prime gtkmm3 spice-vdagent virtualbox-guest-utils vulkan-radeon lib32-vulkan-radeon vulkan-intel lib32-vulkan-intel xf86-input-vmmouse xf86-video-amdgpu xf86-video-ati xf86-video-dummy xf86-video-fbdev xf86-video-intel xf86-video-nouveau xf86-video-openchrome xf86-video-sisusb xf86-video-vesa xf86-video-vmware xf86-video-voodoo
:: Synchronizing package databases...
downloading core.db...
downloading extra.db...
downloading community.db...
downloading multilib.db...
error: target not found: linux54-nvidia-455xx
error: target not found: nvidia-455xx-utils
error: target not found: lib32-nvidia-455xx-utils
error: target not found: linux54-nvidia-455xx
error: target not found: nvidia-455xx-utils
error: target not found: lib32-nvidia-455xx-utils
-> Copying mhwd package cache ...
building file list ... done
sent 17 bytes received 12 bytes 58.00 bytes/sec
total size is 0 speedup is 0.00
==> ERROR: File '/var/lib/manjaro-tools/buildiso/xfce/x86_64/mhwdfs/opt/mhwd/pkg/*pkg.tar*' not found.
==> No packages modified, nothing to do.
==> ERROR: A failure occurred in make_image_mhwd().
Aborting...
--> overlayfs umount: [/var/lib/manjaro-tools/buildiso/xfce/x86_64/mhwdfs]
```
Before the kernel update, everything worked. Can you update the script for the new packages?https://gitlab.manjaro.org/tools/development-tools/manjaro-docker/-/issues/3available on docker hub?2021-12-18T12:40:10ZBernhard Landaueravailable on docker hub?*Created by: zocker-160*
Is this base image available on [docker hub](https://hub.docker.com/)?
If no; it would be very useful to have an official base image I could use for my docker images.
If yes; having a reference to and from t...*Created by: zocker-160*
Is this base image available on [docker hub](https://hub.docker.com/)?
If no; it would be very useful to have an official base image I could use for my docker images.
If yes; having a reference to and from this repo here would be good.https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/323Buildiso doesn't work in docker2021-06-07T03:53:26ZNickolay LeschevBuildiso doesn't work in dockerHello!
I am not experienced in CI/CD automatization, but I am trying to make auto build the iso in docker, which runs in CircleCI machine. I use machine executor in CircleCI to start docker in privileged mode, but buildiso still gives a...Hello!
I am not experienced in CI/CD automatization, but I am trying to make auto build the iso in docker, which runs in CircleCI machine. I use machine executor in CircleCI to start docker in privileged mode, but buildiso still gives an error: ![2020-05-03_May3829-1000x363](/uploads/d902ad75d92d79e45eeb29357cdf76bb/2020-05-03_May3829-1000x363.png)
I use the next command to start the docker container:
```
docker run \
--name manjarolinux-build \
--mount type=bind,src="$(pwd)",dst="/home/isobuilder/project" \
--workdir "/home/isobuilder/project" \
--cap-add SYS_ADMIN \
--entrypoint "./install.sh" \
demysteriismundi/manjarolinux-build:stable -b
```
I hope you will tell me the way to solve this problem. Maybe CircleCI not suitable for such purposes so what can I use for that?https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/322How can I contribute with a patch?2020-10-31T08:59:27ZChristian FinnbergHow can I contribute with a patch?I have been unable to find information about how can I contribute with a patch to Manjaro-tools. I can't fork it to make a merge request and I don't know to whom should I send it then to review. Thanks!I have been unable to find information about how can I contribute with a patch to Manjaro-tools. I can't fork it to make a merge request and I don't know to whom should I send it then to review. Thanks!https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/321[buildpkg] splitting packages not work if present multiple 'arch' array2020-05-01T15:30:18ZStefano Capitani[buildpkg] splitting packages not work if present multiple 'arch' arrayWe have an old issue present in `buildpkg` function: not working if the multiple PKGBUILD contain a mix of architecture array: in our case if we mix `arch=any` and `arch=x86_64`.
The problem is [here](https://gitlab.manjaro.org/tools/dev...We have an old issue present in `buildpkg` function: not working if the multiple PKGBUILD contain a mix of architecture array: in our case if we mix `arch=any` and `arch=x86_64`.
The problem is [here](https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/blob/master/lib/util-pkg-chroot.sh#L157-171). The `post_build` function not recognize the array if is present ( as normally ) inside the `package_XXXX()` function of the `PKGBUILD`. As i understand is because a variable into a function can't be exported in other scripts . I have tried this approach but without success. I have at the end of the idea. Following the approach of arch is hard because use more scripts and library function into makepkg process to parse e divide the PKGBUILD for any splitted package ( if understand correctly their approach )
```
post_build(){
source PKGBUILD
if [[ ${#pkgname[@]} > 1 ]]; then
archs=$(grep 'arch=' PKGBUILD | cut -d "=" -f2- | sed 's/.//;s/.$//' | tr '\n' ' ' | sed 's/^/(/;s/$/)/')
echo $archs
s=${#archs[@]}
echo $s
counter=0
echo $counter
while [[ $counter -lt $s ]]; do
local ext='pkg.tar.zst' tarch ver src
for pkg in ${pkgname[$counter]}; do
case ${archs[$counter]} in
any) tarch='any' ;;
*) tarch=${target_arch}
esac
local ver=$(get_full_version "$pkg") src
src=$pkg-$ver-$tarch.$ext
move_to_cache "$src"
done
local name=${pkgbase:-$pkgname}
archive_logs "$name"
counter=$(( $counter + 1 ))
done
else
local ext='pkg.tar.zst' tarch ver src
for pkg in ${pkgname[@]}; do
case $arch in
any) tarch='any' ;;
*) tarch=${target_arch}
esac
local ver=$(get_full_version "$pkg") src
src=$pkg-$ver-$tarch.$ext
move_to_cache "$src"
done
local name=${pkgbase:-$pkgname}
archive_logs "$name"
fi
```https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/320Symlinks for latest releases should be part of deployiso2020-05-08T11:47:52ZPhilip MüllerSymlinks for latest releases should be part of deployisoCurrently `buildiso` is creating symlinks for latest stable releases. However it would be more logical to have this function in `deployiso`. Let's see how we can achieve that.Currently `buildiso` is creating symlinks for latest stable releases. However it would be more logical to have this function in `deployiso`. Let's see how we can achieve that.https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/319Log file clash during concurrent builds2020-04-28T07:37:19ZGhost UserLog file clash during concurrent buildsI am using concurrent builds by using different terminals - usually not a problem - but just now this occurred.
Running in different terminals
buildiso -p openbox -f
and
buildiso -p lxde -f
It seems there is log file clash i...I am using concurrent builds by using different terminals - usually not a problem - but just now this occurred.
Running in different terminals
buildiso -p openbox -f
and
buildiso -p lxde -f
It seems there is log file clash in `/tmp`
```
--> Restoring [/var/lib/manjaro-tools/buildiso/lxde/x86_64/rootfs/etc/pacman.conf] ...
-> Configuring lsb-release
-> Cleaning [rootfs]
==> Done [Base installation] (rootfs)
cat: /tmp/manjaro-tools/make_image_root.ansi.log: No such file or directory
rm: cannot remove '/tmp/manjaro-tools/make_image_root.ansi.log': No such file or directory
==> ERROR: A failure occurred in make_image_root().
Aborting...
```https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/issues/318Request: not check /etc/lsb-release2020-03-05T22:08:53ZSteven LeeRequest: not check /etc/lsb-releaseCurrently, if there is no `/etc/lsb-release`, `manjaro-chroot` will report error.
Wish to not checking this, because it is not necessary for the problem this tool is going to solve.Currently, if there is no `/etc/lsb-release`, `manjaro-chroot` will report error.
Wish to not checking this, because it is not necessary for the problem this tool is going to solve.