[Slackbuilds-users] git-cola, python3 and docutils

Benjamin Trigona-Harany slackbuilds at jaxartes.net
Fri Jun 21 23:35:31 UTC 2019

On 2019-06-21 4:24 p.m., Ricardo J. Barberis wrote:
> Hello list!


> First of all, can some admin delete git-cola.tar.gz from the pending queue?
> I sent it after testing in my (heavily modified) Slackware install but
> compiling in a stock Slackware gave me a lot of trouble, so I'll have to
> re-test it. Thanks.
> I think my problems come from the fact that git-cola defaults to python3, so
> every Sphinx dependency needs to be (re-)compiled with python3 support, which
> is pretty much a must since MarkupSafe actually requires python3.

Sphinx and all its dependencies are already Python 3 builds (and Python 
3 only since the Sphinx 2.0 release).

> On the road, I found that babel and python3-babel are at different versions
> but both download an unversioned core.zip file.

You can see that the core.zip files are also different versions when you 
look at the download URL, but the sources are indeed distributed with a 
non-versioned filename.

> Both slackbuilds link core.zip to cldr/core-$CLDRVER.zip, with a different
> value for CLDRVER. Maybe they could move it instead of linking it?

We don't want to move the source files in the script, so I don't think 
this is an option.

> If you compile babel you have to remove that file from e.g. the sbopkg cache
> before compiling python3-babel.

sbopkg prompts for this when the md5sums don't match. In fact, relying 
on the md5sum to ensure that you aren't using the wrong source is how 
it's supposed to work.

> Another one that bit me: docutils keeps failing with python3, I
> added '2to3 --write --no-diffs docutils' to the slackbuild but that makes it
> pretty slow to compile.
> Anyway, I can email the corresponding maintainers about the issues I found,
> probably will do so this weekend, but wanted to let you guys know.
> Thanks for listening :)

More information about the SlackBuilds-users mailing list