New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail at check_loop_device: device node doesn't exist and LOOP=
in cycle 1
#6568
Comments
Jira ticket: AR-2132 |
It looks like the script needs to call |
mknod does get called in check_loop_device, but only with a "found" device, not for creating a missing device. I am putting together a fix for this and will make a PR. |
$LOOP=
LOOP=
in cycle 1
It looks like the commit to fix this issue got reverted: FYI this issue also affects Fedora the same way, only /dev/loop-control present and an losetup -f run needed. |
Yes, the commit got reverted until a better solution is made. And thanks for reporting that this is also the case on Fedora, it's probably much easier to test with for others than gentoo |
What happened?
I did confirm this problem on the main branch
Trying to build armbian on gentoo with docker. Targeting bigtreetech CB2 from https://github.com/bigtreetech/build/tree/CB2The fork isn't far behind the main branch, at least in terms of the compile script.The problem seems to be that the script is looking for a loop device, but there aren't any that match a pattern, yet the loop exits on the first iteration with a false positive and empty
LOOP
variable.How to reproduce?
(May get updated)
./compile.sh
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Other (Gentoo with docker)
Are you building on Windows WSL2?
Relevant log URL
{message:Error adding document.}
paste.armbian.com/log returns a 500 status code, putting the log here:
log-build-3ebc61fd-016c-4aa1-9a41-00194251ff89.log.ans.txt
Also, the log with docker prefix, because the script decided to use docker automatically:
log-docker-3ebc61fd-016c-4aa1-9a41-00194251ff89.log.ans.txt
Code of Conduct
The text was updated successfully, but these errors were encountered: