Open blaze-developer opened 2 months ago
Can you run the build script with DEBUG=1
enabled and post the log?
is the log saved in a file anywhere? If not I guess ill have to run it again but piping into a file
can you run ls /usr/sbin/useradd
for me?
This means /usr/sbin is not in your path. Try running export PATH=$PATH:/usr/sbin
, then try rebuilding the shimboot image.
Wait but useradd is a perfectly working command on my system-
it is, but the directory that contains useradd isn't added to the list of directories your shell looks for executables in
But it seems that is is because I can simply run useradd
and its a working command
without root?
with and without
weird
~
❯ which useradd
/usr/bin/useradd
~
❯ sudo which useradd
/usr/bin/useradd
Just FYI, I am experiencing this as well (building debain unstable with gnome)
What distro are you using to build? Because my personal guess is that the building script is designed for debian-based systems and somehow doesn't work for arch based systems. But if you are using a debian based distro or not arch, I would be proven incorrect.
What distro are you using to build? Because my personal guess is that the building script is designed for debian-based systems and somehow doesn't work for arch based systems. But if you are using a debian based distro or not arch, I would be proven incorrect.
Same command you are using, but with gnome instead of kde
I wasn't able to reproduce this with an ARM build. I'll try it again at home once I have access to another x86 system to test on.
I cannot reproduce this bug on any of the devices I tested for the build. I used the exact same build command too.
It might be a problem with the version of debootstrap that Arch provides. The error that occurs is happening inside the Debian chroot, not on the host Arch system, which suggests that debootstrap didn't set the chroot up correctly.
It might be a problem with the version of debootstrap that Arch provides. The error that occurs is happening inside the Debian chroot, not on the host Arch system, which suggests that debootstrap didn't set the chroot up correctly.
I would agree, however debootstrap on the arch repository is the same debootstrap from debian.org I believe.
https://archlinux.org/packages/extra/any/debootstrap/
If there are any differences, and this does not work on any arch-based system, I would add to your readme that this build script does not work on arch machines, or something of the like.
can reproduce after attempting to run shimboot on arch
When building an image with
sudo ./build_complete.sh dedede release=unstable desktop=kde
It goes through a long process, but ultimately ends in
Build Device