brl fetch solus - fix issue
I noticed that brl fetch solus fails due to unresolved dependency.
After this update util-linux needs python3 which is not a part of system.base component and it breaks eopkg install -c system.base. I fixed this issue modifying /bedrock/share/brl-fetch/distros/solus file. from Code:
chroot "${bootstrap_dir:-}" eopkg -y -D/target-root install -c system.base Code:
chroot "${bootstrap_dir:-}" eopkg -y -D/target-root install -c system.base --ignore-dep |
Thanks! I'll see about including this in an upcoming point update.
|
I noticed another issue for brl fetch solus. It occurred for hijacked void and artix linux.
Quote:
Code:
# groupadd -g 18 messagebus Quote:
|
I've applied your initial fix in 0.7.7beta1, which you can try with https://bedrocklinux.org/0.7/beta-channel.html
If you find the time, please do test it and confirm it resolves the original issue. Thanks again for the fix! I'll look into this new item and either add it to 0.7.7 before it leaves beta or queue it up for 0.7.8. |
I can confirm that original issue gone, checked today with 0.7.7beta1.
I have to say I like bedrock linux and I follow commits on github recently. |
Happy to hear it :)
|
I tested latest improvements for src/slash-bedrock today.
brl fetch solus works fine. dbus-daemon problem gone. |
The latest release - 0.7.7 - includes your python fix but, as far as I recall, not your dbus fix.
By latest improvements do you mean the master branch? I did include the dbus fix there, but didn't want to get your attention to fix it until I pushed a beta release with it. If that's what you mean, awesome :) |
Yes, I used the master branch.
I tried interrupt fetching bootstrap packages due to I wanted to check caching support. Seems it works as well. I had only run brl remove solus before second brl fetch solus. Do you think about checking if brl fetch is executed for resume? (to avoid run brl remove when something went wrong at the first attempt) |
Quote:
Quote:
Resuming an interrupted fetch is difficult, because:
Given the new caching feature, the need to resume should be greatly diminished, as it should be able to re-run the initial steps with cached content relatively quickly. The main non-cached steps are verifying the cached files are current - something we'd have to do if resuming as well - and applying the cached data. |
All times are GMT -5. The time now is 11:52 AM. |