Oh, but that was not the only error. So, maintainers are not reading this thread? Are you the lawyer for this thread?

no, sorry, we cannot assume SBo's maintainers are reading this thread, please have a look at the first post and please read this post on the mailing list

https://lists.slackbuilds.org/piperm...il/018920.html

audriusk was simply repeating what I had written multiple times in the posts above yours.

I have actually emailed the maintainer ponce, no response for several days. I figured I post here in case someone else are working (except the maintainer) with this and may give me a hint.

I will try to solve this issue myself before submitting an issue to the mailing-list.

Spotify is known to remove the old source once they got a new release
sbosrcarch still has the source: http://slackware.uk/sbosrcarch/by-na...media/spotify/

You should definitely mention this when you are reporting issues. The admins don't like to implement fixes without the maintainer's involvement (since it is the maintainer's SlackBuild and not SBo's), but if you aren't getting a response from the maintainer, they're more likely to step in and help with troubleshooting the problem.

I'm having issues building pygobject3-python3 from SBo on -current.

Here is my log: https://www.dropbox.com/s/p0tr7qa2qq...thon3.log?dl=0

I did get it to compile by adding the CFLAG:
But I don't think that that is the smartest thing to do.

Edit: I am using a fresh/clean install of -current update: Wed Apr 26 23:09:45 UTC 2017

Edit2: I just updated my current ISO, did a fresh install and still getting the same error.

Fixed on my branch

thanks

Hi , one more time :=)

Package --> aacgain

One of the depends is mp4v2-trunk-r355 , the link is broken.


Ponce save me, one more time ... http://ponce.cc/slackware/sources/re...k-r355.tar.bz2

stop reporting broken links here, pls.

then ..

broken links --> NOOOOOOO
error building --> email the mantainer

why exists this thread...? close ?

As stated in the first post of this thread:

As Didier quoted, this thread is designed to fix issues that are specific to -current. Not all maintainers are willing to try and support -current. I know I don't have -current installed on any of my machines, so I am unable to test any of my SlackBuilds on -current (although, I'm willing to try and get any of my SlackBuilds working on -current if someone runs into issues). However, any broken links will affect the stable release as well, so those should always be reported to the maintainer. And if you get errors running the SlackBuild, it is likely those same errors occur on stable, so it is best to report it to the maintainer.

The thing to remember is SBo is just hosting the SlackBuilds. The maintainers are the ones who are supposed to handle all the issues that arise with those SlackBuilds (with a stable release).

i not understand nothing.
if report to mantainer..or mailing slackbuilds mailing list..
mua haha , but ok ..i think no report nothing anymore..and all happy.

No problem.

It's pretty simple. When you encounter any issue with a build, ask yourself this question:

"Does this ONLY happen when I'm running on -current?"

If that answer is not "yes" then don't post in this thread.

post #529 (and a few others after)
https://lists.slackbuilds.org/piperm...il/018920.html

what rworkman has just written in the post above (also stated in the first post, that the title of this topic invites you to read).

don't get it wrong, but see it instead as an opportunity to start frequenting that nice place that's SBo's mailing list. :)