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.
the to-be-removed branch has been already been merged with master: see the removed ones from http://slackbuilds.org/cgit/slackbuilds/log/?ofs=99 (for now: if new commits will be added to master it will move further).
in the eventuality that someone wants to take care of those, there will be no problems readding them with new maintainers when submission will reopen: now the priority is make a repository for 14.1 available as soon as possible.
the to-be-removed branch has been already been merged with master: see the removed ones from http://slackbuilds.org/cgit/slackbuilds/log/?ofs=99 (for now: if new commits will be added to master it will move further).
in the eventuality that someone wants to take care of those, there will be no problems readding them with new maintainers when submission will reopen: now the priority is make a repository for 14.1 available as soon as possible.
As not everyone is following SBo's mailing list I take the initiative of quoting a message posted a few hours ago on behalf of the SBo team, with just a few editing for a better display here:
Quote:
[...]
We'd like to take this time to welcome the newest member of our admin team, Willy Sudiarto Raharjo (willysr), and thank him for the huge amount of testing and fixing of various scripts that he did.
Similarly goes for Matteo Bernardini (ponce) as well as for David Somero (XGizzmo), who once again put the repository through its paces using automated build testing.
Then there's Heinz Wiesinger (pprkut) for the usual fixes and updates, as well as his work behind the scenes with our database.
Kudos also go to Erik Hanson (erik) for his never-ending job of server maintenance and upkeep, on top of fixes and updates all over the SBo tree.
Thanks go as well to Michiel van Wessem (BP{k}) and Niels Horn (niels_horn) for jumping in every once in a while for moral support and hints on various hard to crack issues.
Then there's also rob0 (/dev/rob0) hiding in the shadows working tirelessly to keep mail and dns working.
Last but not least there's Robby Workman (rworkman), our ever inspiring project lead who knows exactly how to kick us all into gear when work needs to get done!
All of our users and maintainers deserve proper thanks for our existence, but David Spencer and David Woodfall really helped out a lot this time around with testing and fixing an insane amount of SlackBuilds.
[...]
Huge thanks to all!
Last edited by Didier Spaier; 11-26-2013 at 11:55 AM.
Having served as an admin in the past, I know how much work is involved in keeping SBo working so hats off to the entire SBo team and congrats to Willy for joining the SBo team. All of the admins involved at SBo do an incredible job. Thank you all very much!!!
Thanks SBo team (admins+package maintainers) for the great work.
I've followed the communications on the mailing list. It's amazing how it happened so fast. It took you less than one month to upgrade the repository to 14.1.
One of the reason is that we have tools like sbopkg and sqf which makes it easier for us to automatic build, like what David Spencer has did on this cycle. That really helped us a lot to make sure it builds fine on 14.1
One of the reason is that we have tools like sbopkg and sqf which makes it easier for us to automatic build, like what David Spencer has did on this cycle. That really helped us a lot to make sure it builds fine on 14.1
David Woodfall was much quicker because his tools (which he shared in this thread) were more efficient, and I was writing and debugging a new script at the same time as patching the SlackBuilds it was warning about. I'll be putting it onto Github later this week, but it's still less than three weeks old, and it stops working every time I try to make it good enough for Github or have a new idea
By the way, this commit is possibly one of the most awesome commits in the history of SBo.
Last edited by 55020; 11-27-2013 at 06:59 AM.
Reason: added awesomeness
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
because his tools (which he 
