LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-21-2019, 05:22 PM   #31
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,018

Rep: Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686

Quote:
Originally Posted by BW-userx View Post
yeah what bassmadrigal said, for somethings i do sometimes find myself having to bounce back and fourth between ponce repo for slackbuilds and slackbiulds.org to get deps to install to make the final package but that is for a very few things, and mostly because they are not found in ponce repo, so I just jump over to slackbuilds and get them, then go back to ponce repos to get the rest of it.
You misunderstand... the repo I mention of ponces started from a clone of the SBo repo and is synced with SBo weekly. He then applies the changes needed over that sync to make everything works on -current.

There is no reason to bounce back and forth between the two repos as ponce's should have everything SBo does with the addition of fixes (or version bumps) to ensure they build on -current.

In other words, I am NOT referencing his personal package repo, but his fork of the SBo repo, which is only SlackBuilds scripts and no packages.
 
Old 01-21-2019, 06:42 PM   #32
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware 14.2 current / ArcoLinux / Void Linux
Posts: 8,643

Rep: Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794
Quote:
Originally Posted by bassmadrigal View Post
You misunderstand... the repo I mention of ponces started from a clone of the SBo repo and is synced with SBo weekly. He then applies the changes needed over that sync to make everything works on -current.

There is no reason to bounce back and forth between the two repos as ponce's should have everything SBo does with the addition of fixes (or version bumps) to ensure they build on -current.

In other words, I am NOT referencing his personal package repo, but his fork of the SBo repo, which is only SlackBuilds scripts and no packages.
yes there is.... when I get back in slack I'll prove it..
mod nevermind here it is


mpv install deps

Code:
SlackBuilds Repository
14.2 > Development > docutils (0.14)
it is not in ponce git.

https://github.com/Ponce/slackbuilds...nt/development

Last edited by BW-userx; 01-21-2019 at 07:53 PM.
 
Old 01-21-2019, 08:29 PM   #33
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,491

Rep: Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111
Quote:
Originally Posted by BW-userx View Post
yes there is.... when I get back in slack I'll prove it..
mod nevermind here it is


mpv install deps

Code:
SlackBuilds Repository
14.2 > Development > docutils (0.14)
it is not in ponce git.

https://github.com/Ponce/slackbuilds...nt/development
That's because it is already in -current (called python-docutils). I recommend you uninstall docutils from SBo and reinstall python-docutils so as not to confuse package management.

Last edited by montagdude; 01-21-2019 at 08:32 PM.
 
1 members found this post helpful.
Old 01-21-2019, 11:45 PM   #34
solarfields
Member
 
Registered: Feb 2006
Location: Outer Shpongolia
Distribution: Slackware
Posts: 975

Rep: Reputation: 544Reputation: 544Reputation: 544Reputation: 544Reputation: 544Reputation: 544
Yep, the -current ChangeLog says it was added on Sep 23 01:02:32 UTC 2017.
 
1 members found this post helpful.
Old 01-21-2019, 11:54 PM   #35
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,018

Rep: Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686
Quote:
Originally Posted by BW-userx View Post
Code:
SlackBuilds Repository
14.2 > Development > docutils (0.14)
it is not in ponce git.

https://github.com/Ponce/slackbuilds...nt/development
As the others have shown, the only packages not in ponce's that exist in the official repo are ones that were added to -current and thus were removed from ponce's. If you installed SBo versions over the -current versions, you might've broken things (if the versions are different enough or built differently). I'd follow montagdude's suggestion of removing docutils and reinstalling the official package, just to make sure things aren't broken.

ponce's repo is complete and should have everything you need to build. If you happen to come across something like this example, you should be bringing those up in the stickied thread. You would've been able to find why docutils isn't available, whether due to a glitch or because it was purposefully removed. In this case, it would've notified ponce to remove the docutils dependency from mpv rather than having you (and others) possibly breaking your system by replacing stock packages with SBo versions that are tested against 14.2.
 
1 members found this post helpful.
Old 01-22-2019, 12:28 AM   #36
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,789

Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
In this case, it would've notified ponce to remove the docutils dependency from mpv
I just remove things added to current, but I don't remove them from the REQUIRES lines of the *.info files of other packages or it will be a huge pain to rebase all the things every week (there are more than 450 branches already), they will be removed just before the SlackBuilds.org repository will go live for the next Slackware version.
it's up to the user to ignore stuff added to current (they can also check here, this is already linked in the dedicated thread), or if they use a third party tool (over which I have no control) it should also just ignore them.

Last edited by ponce; 01-22-2019 at 02:00 AM.
 
2 members found this post helpful.
Old 01-22-2019, 03:30 AM   #37
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,018

Rep: Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686Reputation: 3686
Quote:
Originally Posted by ponce View Post
I just remove things added to current, but I don't remove them from the REQUIRES lines of the *.info files of other packages or it will be a huge pain to rebase all the things every week (there are more than 450 branches already), they will be removed just before the SlackBuilds.org repository will go live for the next Slackware version.
it's up to the user to ignore stuff added to current (they can also check here, this is already linked in the dedicated thread), or if they use a third party tool (over which I have no control) it should also just ignore them.
Thanks for the clarification!
 
Old 01-22-2019, 05:44 AM   #38
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware 14.2 current / ArcoLinux / Void Linux
Posts: 8,643

Rep: Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794
Nope , hold on, now I am going to put something to the test. I just need to set it up first.
 
Old 01-22-2019, 05:50 AM   #39
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware 14.2 current / ArcoLinux / Void Linux
Posts: 8,643

Rep: Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794
Quote:
Originally Posted by ponce View Post
I just remove things added to current, but I don't remove them from the REQUIRES lines of the *.info files of other packages or it will be a huge pain to rebase all the things every week (there are more than 450 branches already), they will be removed just before the SlackBuilds.org repository will go live for the next Slackware version.
it's up to the user to ignore stuff added to current (they can also check here, this is already linked in the dedicated thread), or if they use a third party tool (over which I have no control) it should also just ignore them.
ok I just read Ponce post here, see for 1, that is what I was thinking, 2, the configure, and or the make file too is looking for them (the dep) I user sbotools, so I always get a docutils not found, so I just go back to slackbuilds, but now I am going to put something to the test.

the other things is when this current goes on line, is released then it will all come out in the ironing, so being that it is current I expect somethings to go bonkers, though I have had no issues with packages in relationship to mpv and its deps. so i do not worry. this is just a laptop I use, yes I like it working, but just the same it not a production server where I need to keep it up and running at all times, and again, this is current, "unstable" or "testing" if you will, even though it (slackware ) still works (in that current state).

3 I don't see why you, Ponce, should have to update every stinking slackbuild, is that not use the maintainers job to fix our submissions to slackbuilds, for the most part?

even though some stuff up on the sight that people submitted. That person may have long gone away.

that was to everyone that told me to straighten up my ship. not particularity you Ponce.

Last edited by BW-userx; 01-22-2019 at 06:06 AM.
 
Old 01-22-2019, 07:25 AM   #40
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,491

Rep: Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111
Quote:
Originally Posted by BW-userx View Post
3 I don't see why you, Ponce, should have to update every stinking slackbuild, is that not use the maintainers job to fix our submissions to slackbuilds, for the most part?
The maintainers are officially expected only to maintain their scripts for the latest stable release of Slackware. Not everyone runs -current, and of course -current is a moving target and not officially supported. But eventually, -current will become the next stable release, and Ponce has taken it upon himself to maintain his fork of SBo to make that transition smoother. He doesn't have to do it, he chooses to do it. (Though it could be argued that someone has to do it. Thanks, Ponce!)

Last edited by montagdude; 01-22-2019 at 07:28 AM.
 
Old 01-22-2019, 07:35 AM   #41
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware 14.2 current / ArcoLinux / Void Linux
Posts: 8,643

Rep: Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794
Quote:
Originally Posted by montagdude View Post
The maintainers are officially expected only to maintain their scripts for the latest stable release of Slackware. Not everyone runs -current, and of course -current is a moving target and not officially supported. But eventually, -current will become the next stable release, and Ponce has taken it upon himself to maintain his fork of SBo to make that transition smoother. He doesn't have to do it, he chooses to do it. (Though it could be argued that someone has to do it. Thanks, Ponce!)
well I suppose as long as he hopefully has a script to automate it, that would be ok with me.

Check every single one by hand, screw that.

Last edited by BW-userx; 01-22-2019 at 07:37 AM.
 
Old 01-22-2019, 08:16 AM   #42
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,491

Rep: Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111
Quote:
Originally Posted by BW-userx View Post
well I suppose as long as he hopefully has a script to automate it, that would be ok with me.

Check every single one by hand, screw that.
I don't think he checks every single one by hand. He has a thread where people report errors, and he corrects those as they come in. He may also run automated tests to ensure that things at least build correctly, but I'm not sure.
 
Old 01-22-2019, 08:50 AM   #43
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware 14.2 current / ArcoLinux / Void Linux
Posts: 8,643

Rep: Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794Reputation: 1794
Quote:
Originally Posted by montagdude View Post
I don't think he checks every single one by hand. He has a thread where people report errors, and he corrects those as they come in. He may also run automated tests to ensure that things at least build correctly, but I'm not sure.
I'm speaking of when the big move comes, to update all of them, per what he was speaking of about deps changing due to slackware now including them into the install so they are no longer valid. so the info files need to be updated to remove these deps requirements.
 
Old 01-22-2019, 08:58 AM   #44
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,491

Rep: Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111Reputation: 1111
Quote:
Originally Posted by BW-userx View Post
I'm speaking of when the big move comes, to update all of them, per what he was speaking of about deps changing due to slackware now including them into the install so they are no longer valid. so the info files need to be updated to remove these deps requirements.
Oh, ok. I'm not sure what process they use for that, but it is definitely scriptable. SBo actually stops accepting submissions for a couple months prior to a new Slackware release, and all the admins work on the big move, so it's not all Ponce's res-ponce-ibility.

(I couldn't resist the punce. Oh look, another one. )

Last edited by montagdude; 01-22-2019 at 09:00 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Script that changes the install location of SlackBuilds affinity Slackware 2 12-24-2009 11:23 AM
[SOLVED] ffmpeg install error from SlackBuilds eraosso Slackware 7 11-05-2009 07:23 PM
[SOLVED] Slackware 13 64bit: First time using SlackBuilds and unable to install programs. Switch7 Slackware 19 10-08-2009 09:26 AM
Gnucash, can't install from the slackbuilds basheer Slackware 6 04-04-2009 10:03 PM
Use SlackBuilds.org or my own hosting to offer up SlackBuilds? hollywoodb Slackware 6 11-30-2006 08:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:15 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration