Hello All,

Any idea when https://slackbuilds.org/ will have 15.0 in their repos?

BR

When it is ready. There are a lot of packages that need to be checked.

Meanwhile you can use https://github.com/Ponce/slackbuilds or http://cgit.ponce.cc/slackbuilds/ for reference in building packages.

3 members found this post helpful.

I am not expecting some hard date. Rather something like "Targeted to complete by year end. Consider +- 2/3 months." Some such infos/statements from the website owners.

Use the source, Luke!

master branch at:

http://git.slackbuilds.org/slackbuilds/

or even more bleeding-edge, any of the other branches that are newer than master.

4 members found this post helpful.

No word yet on when www.slackbuilds.org will go live with 15.0. But as others have stated, in the meantime you can use the master branch manually or with sbopkg. To use the master branch with sbopkg download Willy's test sbopkg here. After installing it edit /etc/sbopkg/sbopkg.conf and change the repo line from 15.0 to master. Then sync sbopkg with "sbopkg -r" and you're good to go.

8 members found this post helpful.

I would like to point out, I think that if all maintainers would have verified their scripts worked with 15.0, we would have already had the 15.0 branch by now. The number of commits SBo admins have made fixing builds is staggering.

This is only my opinion, though.

Edit: also if USERS would test what they use that would help - I currently have 231 SBo packages installed and they all seem to work fine. Of course we may not be as strict as the SBo admins are. There have been commits fixing builds that write to / during the build process which I probably wouldn't catch (I build in a chroot but don't carefully verify builds do anything naughty).

This!! The good people at SBo are working on this task on a volunteer basis on their own time. I'm grateful for their efforts; I'm happy to wait.

6 members found this post helpful.

People on 15.0 should definitely be using master. That's where all the updates from the various admins and maintainers get added to initially, then ponce will pull those updates into his "-current" repo. So it will always be lagging behind SBo's master repo.

These will only contain partial updates. It will only contain the updates that this specific admin (or maintainer with write access to the repo) has approved prior to them getting merged into master.

3 members found this post helpful.

Well, yes, that's what branches are. It was half-way a joke, though - but I know sarcasm doesn't work well on the internet. The half that wasn't a joke was my builds on my machine are from my personal branch, which is sometimes ahead of master. I could potentially see a case where a problem affecting me is fixed in a topic branch on SBO git, but not merged into master yet - that hasn't happened yet. But these days master is getting updated every couple of days, anyway.

There are over 80k commits so far since last update in 17 April 2021, so we are working hard on getting this repo ready
so many scripts to check and so many changes since Slackware 14.2 -> 15.0 while we only have limited people working on this project, so please don't rush....

we have under 300 ftbfs currently, hopefully gets reduced every single day

11 members found this post helpful.

Is there a public list available so some of us can try and see if we can find fixes?

5 members found this post helpful.

^ This, I would be happy to test and try to find fixes if there is a list.

2 members found this post helpful.

What is ftbfs ???

As I only maintain a few slackbuilds for perl modules, would be happy to test things.

Anyway, I can live with master branch. Just would like to share a few new slackbuilds

fails to build from source

4 members found this post helpful.

This would certainly help but, every change still needs to be reviewed before being committed.

1 members found this post helpful.