[Slackbuilds-users] Attn Maintainers: Is one of your SBs on this list?

[Duncan Roe]

Hi All,

I've attach a distilled sbolint report covering those SBs not amenable to
correction in a bulk edit.

The report is 217 lines long; before bulk-editing it was 4763 lines.

I did the bulk edits using Q editor macros. I was delaying submission of a Q SB
until upstream put outthe next release. That still seems to be some ways off so
I'll try to get a snapshot SB out in time for this Saturday's update.

Cheers ... Duncan.

solint.log notes:

| redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
| (+ 37 repeats)
Why is this an ERR? The URLs download fine (at least the 2 I randomly tried did)

| frogatto: NOTE: ./fbsd-fixes.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
The source has DOS-style CRLF line endings so the patch has to have them.
This might get mangled by some mailers, but not by git itself surely?

| nexus: NOTE: nexus.SlackBuild:61: LIBDIRSUFFIX gets set, but never used.
This is a false positive. LIBDIRSUFFIX is used in a sed command

sbolint.log

-------------------------------------------------------------

sage: ERR: sage.SlackBuild:58: TMP=${TMP:-/tmp/SBo} is required
pyalsaaudio: NOTE: pyalsaaudio.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
gtk-xfce-engine: NOTE: README ends with 1 blank line
cudnn: NOTE: README ends with 1 blank line
gcc5: NOTE: ./patches/glibc2.30-ipc_perm.diff has DOS-style CRLF line endings, git may mess it up unless you gzip it
guzzle_sphinx_theme: NOTE: guzzle_sphinx_theme.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
jdk: WARN: README has lines >72 characters
nexus: NOTE: nexus.SlackBuild:61: LIBDIRSUFFIX gets set, but never used.
protobuf3: ERR: protobuf3.info:5: malformed line (no = sign, missing \ on prev line?)
protobuf3: NOTE: 1 possibly-fixable errors found. suggest running sbofixinfo.
protobuf3: ERR: protobuf3.info: we have 1 DOWNLOAD URLs but 2 MD5SUM values
python3-matplotlib: ERR: python3-matplotlib.info:6: malformed line (no = sign, missing \ on prev line?)
python3-matplotlib: NOTE: 1 possibly-fixable errors found. suggest running sbofixinfo.
python3-matplotlib: ERR: python3-matplotlib.info: we have 1 DOWNLOAD URLs but 3 MD5SUM values
valkyrie: NOTE: ./vk_configh.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
Scorched3D: NOTE: ./patches/scorched3d-freetype-buildfix.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
Scorched3D: NOTE: ./patches/scorched3d-returntype.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
Scorched3D: NOTE: ./patches/scorched3d-fix-hang-on-fast-machines.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
Scorched3D: NOTE: ./patches/scorched3d-help.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
Scorched3D: NOTE: ./patches/scorched3d-wx3.0.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
brutalchess: NOTE: ./brutalchess-0.5.2-gcc4.3.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
frogatto: NOTE: ./fbsd-fixes.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
mars: NOTE: ./pull17.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
qmc2: NOTE: ./qmc2-types.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
yabause: NOTE: ./qt-5.11.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
opencpn-plugin-oesenc: NOTE: ./slackware-detection-logic.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
python-mapnik: NOTE: python-mapnik.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
ldglite: NOTE: ./cflags.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
opencollada: NOTE: ./pcre.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
pygraphviz: NOTE: pygraphviz.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
FreeImage: NOTE: ./cross_platform_byteswap_fix.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
FreeImage: NOTE: ./gcc-version-fix-includes.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
Impacket: NOTE: Impacket.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
PyOpenGL: NOTE: PyOpenGL.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
SDL_Pango: NOTE: ./SDL_Pango-0.1.2-matrix_declarations.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
SDL_Pango: NOTE: ./SDL_Pango-0.1.2-API-adds.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
SDL_Pango: NOTE: ./SDL_Pango-0.1.2-suppress-warning.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
SlowAES: NOTE: SlowAES.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
aubio: NOTE: aubio.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
html5lib: NOTE: html5lib.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
kaadbg: NOTE: kaadbg.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
libearth: NOTE: libearth.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
libglpng: NOTE: ./libglpng-1.45-libpng15.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
libofa: NOTE: ./patches/libofa-0.9.3-gcc-4.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
musicbrainzngs: NOTE: musicbrainzngs.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
opencl-amd: ERR: opencl-amd.SlackBuild: this script has no error checking (need bash -e option, 'set -e', or '|| exit 1').
portsmf: NOTE: ./portsmf_sharedlib.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
pyPEG2: NOTE: pyPEG2.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pyftpdlib: NOTE: pyftpdlib.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pysendfile: NOTE: pysendfile.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-xlrd: NOTE: python-xlrd.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
tlsh: NOTE: tlsh.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
uptime: NOTE: uptime.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
ws4py: NOTE: ws4py.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
olive: NOTE: ./olive-0.1.2-proxygenerator.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
olive: NOTE: ./olive-0.1.2-FlowLayout.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
olive: NOTE: ./olive-0.1.2-QFontMetrics.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
olive: NOTE: ./olive-0.1.2-QPainterPath.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
olive: NOTE: ./olive-0.1.2-QWheelEvent.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
olive: NOTE: ./olive-0.1.2-cacher.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
olive: NOTE: ./olive-0.1.2-clickablelabel.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
ripperX: NOTE: ./gtk_cpp_workaround.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
sinthgunt: NOTE: ./sinthgunt.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
winff: NOTE: ./patches/unit3-lfm.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
xvst: NOTE: ./patches/chilloutzone.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
xvst: NOTE: ./patches/myvideo.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
Pafy: NOTE: Pafy.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
PySocks: NOTE: PySocks.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
hamachi: NOTE: README ends with 1 blank line
openconnect-sso: NOTE: openconnect-sso.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
policyd2: NOTE: ./patches/httpd_policyd2_conf.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
speedtest-cli: NOTE: speedtest-cli.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
uwsgi: NOTE: uwsgi.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
youtube-dl-server: NOTE: youtube-dl-server.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
youtube-dl: NOTE: youtube-dl.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
ocrmypdf: ERR: ocrmypdf.info:7: malformed line (no = sign, missing \ on prev line?)
ocrmypdf: NOTE: 1 possibly-fixable errors found. suggest running sbofixinfo.
ocrmypdf: ERR: ocrmypdf.info: we have 1 DOWNLOAD URLs but 4 MD5SUM values
xmind: WARN: README has lines >72 characters
CommonMark: NOTE: CommonMark.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
Markups: NOTE: Markups.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
PyAudio: NOTE: PyAudio.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
PyPDF2: NOTE: PyPDF2.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
Pyro4: NOTE: Pyro4.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
apsw: NOTE: apsw.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
blessings: NOTE: blessings.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
bsddb3: NOTE: bsddb3.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
captcha: NOTE: captcha.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
click-default-group: NOTE: click-default-group.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
click-legacy7: NOTE: click-legacy7.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
css-parser: NOTE: css-parser.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
cssselect2: NOTE: cssselect2.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
cssutils: NOTE: cssutils.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
ecdsa: NOTE: ecdsa.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
filechunkio: NOTE: filechunkio.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
google-images-download: NOTE: google-images-download.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
hachoir: NOTE: hachoir.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
hpack: NOTE: hpack.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
huepy: NOTE: huepy.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
ipaddr-py: NOTE: ipaddr-py.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
mock: NOTE: mock.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
msgpack-python: NOTE: msgpack-python.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
ndg_httpsclient: ERR: ndg_httpsclient.info: we have 9 DOWNLOAD URLs but 1 MD5SUM values
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "httpsclient:" doesn't look like a valid URL (http, https, or ftp)
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "NOTE:" doesn't look like a valid URL (http, https, or ftp)
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "ndg_httpsclient.info:" doesn't look like a valid URL (http, https, or ftp)
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "canonical" doesn't look like a valid URL (http, https, or ftp)
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "pypi" doesn't look like a valid URL (http, https, or ftp)
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "URL" doesn't look like a valid URL (http, https, or ftp)
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "should" doesn't look like a valid URL (http, https, or ftp)
ndg_httpsclient: ERR: ndg_httpsclient.info: DOWNLOAD URL "be" doesn't look like a valid URL (http, https, or ftp)
npm: NOTE: npm.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
optional-django: NOTE: optional-django.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
phply: NOTE: phply.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
polib: NOTE: polib.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pyaes: NOTE: pyaes.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pyblake2: NOTE: pyblake2.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pychm: NOTE: pychm.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pyliblo: NOTE: pyliblo.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pymysql: NOTE: pymysql.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pyserial: NOTE: pyserial.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
pysha3: NOTE: pysha3.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-axolotl: NOTE: python-axolotl.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-daemonize: NOTE: python-daemonize.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-djvulibre: NOTE: python-djvulibre.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-fusepy: NOTE: python-fusepy.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-gflags: NOTE: python-gflags.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-gntp: NOTE: python-gntp.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-ipcalc: NOTE: python-ipcalc.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-jsonrpclib: NOTE: python-jsonrpclib.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-kerberos: NOTE: python-kerberos.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-libnacl: NOTE: python-libnacl.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-magic: NOTE: python-magic.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-oauthlib: NOTE: python-oauthlib.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-parsedatetime: NOTE: python-parsedatetime.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-pbkdf2: NOTE: python-pbkdf2.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-pcapy: NOTE: python-pcapy.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-rubymarshal: NOTE: python-rubymarshal.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-serpent: NOTE: python-serpent.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-setuptools-git: NOTE: python-setuptools-git.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-sh: NOTE: python-sh.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-slip: NOTE: python-slip.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-smartypants: NOTE: python-smartypants.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-tlslite: NOTE: python-tlslite.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-uritemplate: NOTE: python-uritemplate.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-vdf: NOTE: python-vdf.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-wand: NOTE: python-wand.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-webpack: NOTE: python-webpack.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python-xlib: NOTE: python-xlib.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
python3-holidays: NOTE: README ends with 1 blank line
python3-opencv: ERR: python3-opencv.info:5: malformed line (no = sign, missing \ on prev line?)
python3-opencv: NOTE: 1 possibly-fixable errors found. suggest running sbofixinfo.
python3-opencv: ERR: python3-opencv.info: we have 1 DOWNLOAD URLs but 2 MD5SUM values
pyusb: NOTE: pyusb.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
recommonmark: NOTE: recommonmark.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
rencode: NOTE: rencode.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
requests-oauthlib: NOTE: requests-oauthlib.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
requests-toolbelt: NOTE: requests-toolbelt.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
rfc6555: NOTE: rfc6555.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
rst-linker: NOTE: rst-linker.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
rst: NOTE: rst.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
scikit-umfpack: NOTE: scikit-umfpack.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
simplejson: NOTE: simplejson.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
snuggs: NOTE: snuggs.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
stopit: NOTE: stopit.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
timehash: NOTE: timehash.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
tzlocal: NOTE: tzlocal.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
vcversioner: NOTE: vcversioner.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
virtualenv-clone: NOTE: virtualenv-clone.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
vobject: NOTE: vobject.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
wcwidth: NOTE: wcwidth.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
werkzeug-legacy1: NOTE: werkzeug-legacy1.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
workbook: NOTE: workbook.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
xlutils: NOTE: xlutils.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
foremost: NOTE: ./gcc10.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
graylog-sidecar: NOTE: README ends with 1 blank line
nvidia-legacy390-driver: ERR: nvidia-legacy390-driver.SlackBuild: douninst.sh exists, but the script doesn't install it
routersploit: NOTE: routersploit.SlackBuild: it looks like this build includes both python2 and python3 code. consider splitting it into separate python2- and python3- builds.
xen: NOTE: ./patches/edk2-ovmf-werror.diff has DOS-style CRLF line endings, git may mess it up unless you gzip it