python3 not available from sourcery

You have a problem with Salix? Post here and we'll do what we can to help.
Post Reply
ecfx
Posts: 3
Joined: 29. Aug 2017, 07:48

python3 not available from sourcery

Post by ecfx » 29. Aug 2017, 08:04

Hi,

I was looking to install python3 (3.6.2) from within sourcery but could not see it.

Looking in http://slackware.uk/salix/sbo/14.2/python/ (the mirror i use in /etc/slapt-get/slapt-srcrc) I see it is there.

However, looking in http://slackware.uk/salix/sbo/14.2/SLACKBUILDS.TXT, i can't see it listed.

So I think the problem is it not being listed in SLACKBUILDS.TXT. Can someone more knowledgable then myself help me get to the bottom of this.

Thanks.

User avatar
laprjns
Salix Warrior
Posts: 1032
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: python3 not available from sourcery

Post by laprjns » 29. Aug 2017, 10:21

python3 is avaiable as a pre-built binary package via gslapt or slapt-get

Code: Select all

rich[~]$ sudo slapt-get --show python3
Package Name: python3
Package Mirror: http://download.salixos.org/x86_64/14.2/
Package Priority: Preferred
Package Location: ./salix/d
Package Version: 3.5.1-x86_64-1gv
Package Size: 19823 K
Package Installed Size: 79292 K
Package Required:   bzip2,db48,expat,fontconfig,freetype,gcc,gcc-g++,gdbm,glib2,harfbuzz,icu4c,libX11,libXScrnSaver,libXau,libXdmcp,libXext,libXft,libXrender,libffi,libpng,libxcb,ncurses,openssl-solibs|openssl,readline,sqlite,xz,zlib
Package Conflicts:   
Package Suggests:   
Package MD5 Sum:  98d91ff38bd7bd335d7fda987cd804cc
Package Description:
 python3 (New high-level scripting language)
 
 Python 3 is an interpreted, interactive, object-oriented programming 
 language that combines remarkable power with very clear syntax.
 This is a new version of the language that is incompatible with the 
 2.x line of releases.
 The language is mostly the same, but many details, especially how 
 built-in objects like dictionaries and strings work, have changed 
 considerably, and a lot of deprecated features have finally been 
 removed.  Also, the standard library has been reorganized in a few 
 prominent places.
Package ChangeLog:
 Added.  Upgraded from 14.1.

DidierSpaier
Posts: 310
Joined: 20. Jun 2016, 20:15

Re: python3 not available from sourcery

Post by DidierSpaier » 29. Aug 2017, 10:41

I see python3 in http://slackbuilds.org/slackbuilds/14.2/SLACKBUILDS.TXT

For some reason it seems that http://slackware.uk/salix/sbo/14.2/ be not in sync with http://slackbuilds.org/slackbuilds/14.2/ at time of writing.

ecfx
Posts: 3
Joined: 29. Aug 2017, 07:48

Re: python3 not available from sourcery

Post by ecfx » 29. Aug 2017, 11:01

Thanks for the replies.
laprjns wrote:python3 is avaiable as a pre-built binary package via gslapt or slapt-get

Code: Select all

rich[~]$ sudo slapt-get --show python3
Package Name: python3
Package Mirror: http://download.salixos.org/x86_64/14.2/
Package Priority: Preferred
Package Location: ./salix/d
Package Version: 3.5.1-x86_64-1gv
Package Size: 19823 K
Package Installed Size: 79292 K
Package Required:   bzip2,db48,expat,fontconfig,freetype,gcc,gcc-g++,gdbm,glib2,harfbuzz,icu4c,libX11,libXScrnSaver,libXau,libXdmcp,libXext,libXft,libXrender,libffi,libpng,libxcb,ncurses,openssl-solibs|openssl,readline,sqlite,xz,zlib
Package Conflicts:   
Package Suggests:   
Package MD5 Sum:  98d91ff38bd7bd335d7fda987cd804cc
Package Description:
 python3 (New high-level scripting language)
 ...
Yes, but that is version 3.5.1, not 3.6.2

DidierSpaier wrote:I see python3 in http://slackbuilds.org/slackbuilds/14.2/SLACKBUILDS.TXT

For some reason it seems that http://slackware.uk/salix/sbo/14.2/ be not in sync with http://slackbuilds.org/slackbuilds/14.2/ at time of writing.
Yes, salix mirrors seem to miss this package in SLACKBUILDS.TXT for some reason. So is this just an oversight or something else?

DidierSpaier
Posts: 310
Joined: 20. Jun 2016, 20:15

Re: python3 not available from sourcery

Post by DidierSpaier » 29. Aug 2017, 11:59

Not sure this be related to that, but there have been since several months a general trend (there are exceptions) among http://slackbuilds.org contributors to update to the latest versions of packages, for no there other reason that "a new version has been released" .

This tendency, questionable in my humble opinion, can lead to conflicts with packages coming from repositories with a more conservative approach (and a more sound one, still IMHO), like the extra-14.2 repo (see gapan's blog post here).

Had you used spi, you would have get the Salix package instead.

So ecfx, my question is: why do want to install Python3 3.6.2 rather than 3.5.1? Do you need that as a dependency of another package that requires a more recent version, or for a specific feature not available in 3.5.1?

Personally, I am not in favor of updating a software in a stable Salix (or Slint, in my case) release, but as a security fix or a major bug fix, unless I be sure that it is a "leaf" package, in other words no other package depends on it. Which obviously is not the case of Python. And it seems me to be consistent with that policy to apply it also to sbo, as stated by gapan in his aforementioned blog post.

EDIT: after having sent this post I came across the complete explanation, that has been given by gapan in the blog post titled Our SBo mirrors. Fortunately I see no contradiction between gapan's blog post and what I wrote above ;)

User avatar
gapan
Salix Wizard
Posts: 5517
Joined: 6. Jun 2009, 17:40

Re: python3 not available from sourcery

Post by gapan » 29. Aug 2017, 12:31

Python3 is a package in the salix binary repositories. We won't upgrade it to 3.6, since that will definitely break every python library that depends on it. This is a stable distribution.

We also remove from our SBo mirror the SlackBuilds for which we provide binary packages. That's why you can't find it in Sourcery. It's not an oversight, it's how we do things.

If you really need python 3.6, nobody is preventing you from building your own package using the SlackBuild provided by SBo. We just don't provide a tool to break your system in an easy way.
Image
Image

ecfx
Posts: 3
Joined: 29. Aug 2017, 07:48

Re: python3 not available from sourcery

Post by ecfx » 29. Aug 2017, 13:18

DidierSpaier wrote:Not sure this be related to that, but there have been since several months a general trend (there are exceptions) among http://slackbuilds.org contributors to update to the latest versions of packages, for no there other reason that "a new version has been released" .

This tendency, questionable in my humble opinion, can lead to conflicts with packages coming from repositories with a more conservative approach (and a more sound one, still IMHO), like the extra-14.2 repo (see gapan's blog post here).

Had you used spi, you would have get the Salix package instead.

So ecfx, my question is: why do want to install Python3 3.6.2 rather than 3.5.1? Do you need that as a dependency of another package that requires a more recent version, or for a specific feature not available in 3.5.1?

Personally, I am not in favor of updating a software in a stable Salix (or Slint, in my case) release, but as a security fix or a major bug fix, unless I be sure that it is a "leaf" package, in other words no other package depends on it. Which obviously is not the case of Python. And it seems me to be consistent with that policy to apply it also to sbo, as stated by gapan in his aforementioned blog post.

EDIT: after having sent this post I came across the complete explanation, that has been given by gapan in the blog post titled Our SBo mirrors. Fortunately I see no contradiction between gapan's blog post and what I wrote above ;)
That all makes sense, and thanks for the link to the blog post. I guess "it's shinier" is not a good enough reason!

I see this part of the blog post answers my question.
Finally, all software that is present in both the Salix binary package repositories and SBo, is removed from our own copy of the SBo repository, so there is no way users will be confused and go back and forth between versions. Actually, the SlackBuilds themselves are not removed from the repositories, rather the reference for them in the SLACKBUILDS.TXT file is removed, so it isn't used by our SlackBuild management tools, slapt-src, Sourcery or spi.
As for
Similarly, if you find the same SlackBuild present in both the Salix binary package repositories (hence available in Gslapt) and our own copy of SBo repositories (hence available in Sourcery), please report that too.
I know of at least two, SFML and jsoncpp.
gapan wrote:Python3 is a package in the salix binary repositories. We won't upgrade it to 3.6, since that will definitely break every python library that depends on it. This is a stable distribution.

We also remove from our SBo mirror the SlackBuilds for which we provide binary packages. That's why you can't find it in Sourcery. It's not an oversight, it's how we do things.

If you really need python 3.6, nobody is preventing you from building your own package using the SlackBuild provided by SBo. We just don't provide a tool to break your system in an easy way.
Yes, makes sense and along with that blog post answers my question. As mentioned above, other packages are in both and I was just wondering why not python. Case closed.

User avatar
gapan
Salix Wizard
Posts: 5517
Joined: 6. Jun 2009, 17:40

Re: python3 not available from sourcery

Post by gapan » 29. Aug 2017, 13:39

ecfx wrote:
Similarly, if you find the same SlackBuild present in both the Salix binary package repositories (hence available in Gslapt) and our own copy of SBo repositories (hence available in Sourcery), please report that too.
I know of at least two, SFML and jsoncpp.
Thanks! Fixed for all other too. I had neglected to exclude from SLACKBUILDS.TXT all the packages in the extra repo.
Image
Image

User avatar
Luffy
Posts: 41
Joined: 3. Jul 2017, 22:03

Re: python3 not available from sourcery

Post by Luffy » 17. Oct 2017, 01:19

We also remove from our SBo mirror the SlackBuilds for which we provide binary packages. That's why you can't find it in Sourcery. It's not an oversight, it's how we do things.

Thanks! Fixed for all other too. I had neglected to exclude from SLACKBUILDS.TXT all the packages in the extra repo.
Gracias, gapan, todo claro como el agua.

Post Reply