rebuilding a failed portion of a SlackBuilds build, instead of rebuilding everything
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
rebuilding a failed portion of a SlackBuilds build, instead of rebuilding everything
So, I used sbopkg to build SAGE with its SlackBuild. It took about 3 hours to compile, using >5 GB of temp space, but then just one particular of it failed. How do I fix that particular package so I don't have to rebuild everything again?
An accurate answer would need that you show the error messages but generally speaking that's not possible, unless what failed was the compilation of a dependency in case you used a queue file.
In the latter case, just re-do the build using the "-k" option of sbopkg (using its command line interface).
An accurate answer would need that you show the error messages but generally speaking that's not possible, unless what failed was the compilation of a dependency in case you used a queue file.
In the latter case, just re-do the build using the "-k" option of sbopkg (using its command line interface).
Yes, it was a dependency that it built.
When I run "sbopkg -k", nothing happens; sbopkg doesn't load… (Maybe this is because my /tmp/ folder was recently cleared out, and sbopkg had to create a new one…)
Or f you want sbopkg to install the packages as they are built:
Code:
sbopkg -k -i sage
Thanks
I tried that, but it's not exactly what I'm looking for. I want to install what has already been built (unless "sbopkg -k -i sage" deleted everything and started over again?)
@Geremia: You can try to build sage 6.2 using non-root account. I tried this in the past and it worked, but i didn't submit it to SBo.
Make sure you remove /tmp/SBo directory first or use another directory, such as /tmp/SBo2
@Geremia: You can try to build sage 6.2 using non-root account. I tried this in the past and it worked, but i didn't submit it to SBo.
Make sure you remove /tmp/SBo directory first or use another directory, such as /tmp/SBo2
I'll try that.
What about using the root account makes the build fail?
I don't know but most people in the sage list said it's not working using root user
I tried to build 6.3 now using normal user and see if i can make exception for this package
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
