SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Yes Rob, pypoppler in SBo was broken by the recent upgrade of poppler to 0.40. Our usual crash test dummies (Arch and Fedora) haven't yet updated to poppler-0.40, so they have no patches for us to plagiarise. Upstream is pretty much dead. *However*, the good news is that upstream's bug tracker is still active, and this breakage is logged as bug 1528489.
But I do wonder why we couldn't just fork the 14.1 SlackBuilds and continue adding and refining the 14.1 SlackBuilds. After all, many systems will run 14.1 for a while to come yet. Then perhaps a big notice on the submit page encouraging maintainers to test against the github fork (current -> 14.2) in preparation for the release.
This has pretty much already happened, except that the big notice was on the mailing list, and the repo is on SBo's own server instead of github.
Submissions to 14.1 have been closed to keep the admin workload under control. It's quite possible that there will be selected backports and fixes in the 14.1 branch before 14.2 is released, and maybe a few more after that -- this is what happened in the 14.0 to 14.1 cycle. I remember SBo mgmt suggesting backports right up until we were put out of our misery
Originally Posted by ethoms
It begs the question; should we allow the upload form to take SB's from the current release and the last release (leap frogging). This gives users of the previous Slackware version more time whilst fully supported before they move to next release. However, it means more work for the maintainers, if they choose to maintain the previous release with up-to-date SB's.
It's not as if SBo's 14.1 will go away: users of the previous Slackware version will still have their own SBo branch for as long as they like, albeit frozen with package versions that are compatible with their Slackware installation.
Work for the maintainers is the main obstacle. There wouldn't be any choice; to do the job properly, maintainers would need to test in four clean build environments (or *eight* if the suggested "optional PAM" happened).
Originally Posted by ethoms
My only complaint would be that the time taken for the approved queue to get synced to the production repo is a bit too long (infrequent). If they are approved, what's the hold up.
Everything approved goes into the approver's publicly available git branch immediately, but issues do come to light occasionally that get fixed after approval and before the approximately weekly update. If you follow the approver's branches, you can help to discover those issues