Unable to install SlackBuilds from PPM
Posted: 20 Jul 2013, 00:25
I have multiple machines with Porteus 2.0 that have all at some point become unable to build anything from slackbuilds. The repo syncs just fine, but the browse button doesn't do anything anymore. I am still able to use the search button and express button to list all the packages, but that's about as far as I get. When I try to build something using the search button, i get this error (this error was from an attempt to build pyside, but it get this error with every package):
sh: line 5: ./pyside.SlackBuild: No such file or directory
And when I try to build using the express button I get this error:
The download of the file failed!
I also have seen this error when I look in the log of a failed build:
No working repo found. Perhaps no internet connection
find_working_repo
But the repo seems just fine. It syncs, and I can see the whole repo in /var/lib/sbopkg/SBo/14.0/ and the .SlackBuild files are there as well as the README files (oh yeah, I am also unable to view the readme files from within ppm, clicking the button does nothing).
I am not sure how this happened, maybe I deleted a directory in /tmp that needed to stay there? They all used to work beautifully. I am seriously stumped!
I have reported ppmbug-585 through the package manager about this as well
sh: line 5: ./pyside.SlackBuild: No such file or directory
And when I try to build using the express button I get this error:
The download of the file failed!
I also have seen this error when I look in the log of a failed build:
No working repo found. Perhaps no internet connection
find_working_repo
But the repo seems just fine. It syncs, and I can see the whole repo in /var/lib/sbopkg/SBo/14.0/ and the .SlackBuild files are there as well as the README files (oh yeah, I am also unable to view the readme files from within ppm, clicking the button does nothing).
I am not sure how this happened, maybe I deleted a directory in /tmp that needed to stay there? They all used to work beautifully. I am seriously stumped!
I have reported ppmbug-585 through the package manager about this as well