Re: [Slackbuilds-users] Updates - 20230128.1 - logwatch

[Greg' Ar Tourter]

Whoops Thanks for the heads-up, I will push a new version of the slackbuild
shortly.

Should be up at the next release.

Cheers

Greg

On Mon, 30 Jan 2023 at 08:25, Mab974  wrote:

> Hi,
>
> Apparently, logwatch version 7.8 requires perl-html-parser which version
> 7.7 did not. Should appear in REQUIRES.
>
> thanks
>
> Selon Willy Sudiarto Raharjo  :
> > hi all,
> >
> > Sat Jan 28 01:23:47 UTC 2023
> > academic/dakota: Updated for version 6.17.0.
>
> > system/logwatch: Updated for version 7.8.
>
>
> > +--+
> >
> >
> > --
> > Willy Sudiarto Raharjo
>
>
> -*-
> Mab974 
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] new pgfplots and alegreya packages

[Greg' Ar Tourter]

Hi,

The newly submitted pgfplots and alegreya packages are already included in
the texlive-extras package also in the repo albeit a different version as
the texlive-extras package has not received an update.

It also doesn't install the files in the correct location. it places the
files in /usr/share/texmf-var/ (which is meant for cached runtime data
files) rather than /usr/share/texmf-dist (or at a pinch
/usr/share/texmf-local although that would be the equivalent to installing
packages in /usr/local/ which we do not do in SBo).

However, if the scripts are modified to install in /usr/share/texmf-dist,
they will overwrite the files provided by texlive-extras, and would get
overwritten when texlive-extras is updated.

At least this should be mentioned in the README files.

Hope this helps

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20221105.1

[Greg' Ar Tourter]

Hi

There seem to be a lot of duplicate packages in this release, mostly with
python packages .
kiwisolver = python2-kiwisolver
cycler = python2-cycler
scipy = python2-scipy
scipy3 = python3-scipy
numpy = python2-numpy
numpy3 = python3-numpy
(the ones I have noticed so far)

I guess it is quite a lot of work to change all packages that have these as
dependencies but it is quite confusing.

Cheers

Greg


On Sat, 5 Nov 2022 at 14:49, Willy Sudiarto Raharjo 
wrote:

> Sat Nov  5 14:16:40 UTC 2022
> academic/DRAMPower: Added (DRAM Power + Energy Estimation for DRAM)
> academic/DRAMsim3: Fix github tarball handling.
> academic/OpenMM: Fix github tarball handling.
> academic/SimEng: Added (cycle-accurate processor simulator)
> academic/elk: Added (Linearized augmented-plane-wave Software).
> academic/nco: Updated for version 5.1.1.
> academic/ngspice: Updated for version 38.
> academic/pgfplots: Added (Tex modules).
> academic/pyCRAC: Fix MD5SUM.
> academic/python2-kiwisolver: Added (Cassowary algorithm)
> academic/python2-scipy: Added (math, science, & engineering py2 lib)
> academic/python3-scipy: Added (py3 math, science, and engineering)
> academic/ramulator: Added (a fast and cycle-accurate DRAM simulator)
> academic/verilog: Fix download url.
> academic/yices2: Added (Satisfiability modulo theories solver).
> audio/google-musicmanager: Removed: Google Play Music is no more.
> audio/milkytracker: Update for version 1.03.00.
> audio/mpdscribble: Updated for version 0.24.
> audio/pasystray: Updated for version 0.8.0.
> audio/schismtracker: Updated for version 20221020.
> desktop/gtk-nodoka-engine: Removed: Retired.
> desktop/i3-gaps: Updated for version 4.21.1.
> development/SQLAlchemy: Updated for version 1.4.42.
> development/berkeley-abc: Added (binary sequential logic circuit)
> development/composer: Updated for version 2.4.4
> development/dwz: Removed.
> development/ghidra: Updated for version 10.2.
> development/github-cli: Updated for version 2.19.0.
> development/jupyter-ipykernel: Updated for version 6.17.0.
> development/jupyter-nbclassic: Updated for version 0.4.7.
> development/jupyter-nbconvert: Updated for version 7.2.3.
> development/jupyter-notebook: Updated for version 6.5.2.
> development/jupyter-notebook_shim: Update for 0.2.2
> development/nim: Updated for version 1.6.8, new maintainer.
> development/nodejs: Updated for version 19.0.1.
> development/php-apcu: Updated for version 5.1.22
> development/python2-cycler: Added (composable cycles in python)
> development/python2-numpy: Added (Py2 extension for sci. computing)
> development/python3-cycler: Updated for version 0.11.0.
> development/python3-matplotlib: Update REQUIRES for python3-numpy.
> development/python3-numpy: Added (scientific computing Py3 exts)
> development/qbsolv: Added (A decomposing solver for QUBO)
> development/reuse-tool: Added (License Compliance Tool)
> development/sbcl: Updated for version 2.2.10.
> development/sbt: Updated for version 1.7.3.
> development/universal-ctags: Updated for version p5.9.20221030.0
> development/vis: Updated for version 0.8
> development/vscode-bin: Updated for version 1.73.
> development/yosys: Added (A framework for Verilog RTL synthesis)
> games/RetroArch: Updated for version 1.12.0.
> games/pcsx2: Updated for version 1.7.3526.
> gis/gdal: Updated for version 3.5.3.
> gis/python3-basemap: Updated for version 1.3.5.
> gis/python3-cftime: Fix github tarball handling.
> gis/python3-netcdf4-python: Fix github tarball handling.
> gis/python3-xarray: Updated for version 2022.11.0.
> graphics/birdfont: Updated for version 2.32.3.
> graphics/mtpaint: Fix github tarball handling.
> graphics/vuescan: Updated for version 9.7.95.
> libraries/appstream-glib: Updated for version 0.8.1.
> libraries/aribb25: Fix github tarball handling.
> libraries/confuse: Updated for version 3.3.
> libraries/fast_float: Updated for version 3.6.0.
> libraries/libADLMIDI: Updated for version 1.5.1.
> libraries/libcpuid: Updated for version 0.6.1.
> libraries/libeatmydata: Updated for version 129.
> libraries/libldm: Fix github tarball handling.
> libraries/libmspack: Updated for version 0.10.1alpha.
> libraries/libpoly: Added (C library for manipulating polynomials)
> libraries/libxmp: Updated for version 4.5.0.
> libraries/parsec: Fix github tarball handling.
> libraries/pugixml: Updated for version 1.13.
> libraries/pylast: Updated for version 5.1.0.
> libraries/python2-matplotlib: Added (a Python 2D plotting library)
> libraries/python2-reportlab: Added (Python2 PDF generation toolkit).
> libraries/python3-reportlab: Added (Python3 PDF generation toolkit).
> libraries/qt6: Updated for version 6.4.0.
> libraries/reportlab: Removed (renamed python2-reportlab).
> libraries/spglib: Updated for version 2.0.1.
> libraries/trilinos: Fix github tarball handling.
> libraries/webkit2gtk4.1: Updated for version 2.38.2.
> libraries/webkit2gtk: Updated for version 2.38.2.
> libraries/xmlsec: Updated for version 1.2.36.
> libra

Re: [Slackbuilds-users] hdf5 version 1.12.2 -vs- version 1.10.6

[Greg' Ar Tourter]

As soon as the hdf5 update was released, i tested all my packages that use
it. All built and tested without any issues.

With gdal, i would suggest you rebuild all the dependencies in order. With
gdal, gdal itself compiles against hdf5, but netcdf also compiles against
netcdf. Just like cdo, hdf5 is a direct requirement, as well as an indirect
requirement via netcdf.

Hope that makes sense.

Cheers

Greg

On Sat, 29 Oct 2022, 13:07 Konrad J Hambrick,  wrote:

> Well, dang.
>
> I've got some research to do.
>
> Thanks marav !
>
> -- kjh
>
> On Sat, Oct 29, 2022 at 6:48 AM marav  wrote:
>
>> Hi Konrad,
>>
>> gdal builds fine here, with the latest hdf5 1.12.2
>>
>>
>> *# ls -lhC1 /var/lib/pkgtools/packages | grep hdf5
>> hdf5-1.12.2-x86_64-1_SBo*
>>
>> # ...
>> ...
>> *Slackware package /tmp/gdal-3.5.2-x86_64-1_SBo.tgz created.*
>>
>> Without any addition
>>
>> Cheers
>> Le 29/10/2022 à 13:09, Konrad J Hambrick a écrit :
>>
>> Matteo --
>>
>> Several of my SBo's that REQUIRE HDF5 fail to run this morning.
>>
>> I believe it's because HDF5 Version 1.12.2 introduced incompatible API
>> Changes compared to the previous version HDF5 1.10.6
>>
>> See this link( HDF5 Version 1.12.2 API Compatibility Macros ):
>>
>> Migrating from HDF5 1.10 to HDF5 1.12
>> 
>>
>> One Program is gdal which lists hdf5 as an optional REQUIRE.
>>
>> I found an optional 'compatibility' configure option here:
>>
>> https://portal.hdfgroup.org/display/HDF5/API+Compatibility+Macros
>>
>> So I added:
>>
>> --with-default-api-version=v110
>>
>> And I rebuilt HDF5.
>>
>> I tried rebuilding gdal ( where hdf5 is an optional REQUIRE ) and it
>> failed to compile.
>>
>> I reverted to hdf5 version 1.10.6 and everything works as expected.
>>
>> I am not sure how to proceed because ultimately, proper fixes for all
>> these SBo Packages will require upstream fixes for the new HDF5 API:
>>
>> # hoorex -m hdf5
>> hdf5 h5utils matio FreeFem openimageio med mpb gmsh netcdf GMT ITK OTB
>> meep cdo ncview nco paraview Blender grace
>>
>> Thanks for all your work !
>>
>> -- kjh
>>
>> ___
>> SlackBuilds-users mailing 
>> listSlackBuilds-users@slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] keepassxc 2.7.3

[Greg' Ar Tourter]

Thanks Marav for the heads up.

I have closed my PR on github and will wait for the next release before
pushing a new release.

Cheers

Gre

On Sat, 29 Oct 2022 at 02:44, marav  wrote:

> Hi,
>
> FYI
>
> KeepassXC browser integration (at least here, with Firefox) is broken with
> the last 2.7.3
> And seems to broke some other things :
>
> https://github.com/keepassxreboot/keepassxc-browser/issues/1751
> https://github.com/kkapsner/keepassxc-mail/issues/77
>
> Cheers
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Keepasxc does not work anymore

[Greg' Ar Tourter]

The latest version of keepassxc is the one that has been on the site for
some time. No new update has been released since.
.
We don't bump the build number for slackbuilds when a rebuild is required
after a dependency update so it is up to users to track that.


On Sun, 16 Oct 2022 at 23:19, Luveh Keraph <1.41...@gmail.com> wrote:

> I guess that keepassxc ought to have been part of the latest update too.
>
> On Sun, Oct 16, 2022 at 4:14 PM Fernando Lopez 
> wrote:
>
>> It works. I updated yesterday to the newest version. update botan and
>> recompile.
>>
>> On Sun, Oct 16, 2022 at 4:55 PM Luveh Keraph <1.41...@gmail.com> wrote:
>>
>>> $ keepassxc
>>> keepassxc: error while loading shared libraries: libbotan-2.so.17:
>>> cannot open shared object file: No such file or directory
>>> ___
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users@slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>>
>> --
>>
>> 
>> Regards,
>> Fernando Lopez Jr.
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20221015.1

[Greg' Ar Tourter]

Hi,

I am getting some checksum error with this update:

pyasn1:
MD5SUM check for pyasn1-0.4.4.tar.gz ... FAILED!
Expected: dffae4ff9f997a83324b3f33fe62be54
Found:0d182b71e1f72fe147d7957bc90be7f2
Source deleted.
Error occurred with build.  Please check the log.

Here the info file is pointing to the old version of the source, it should
be
https://files.pythonhosted.org/packages/source/p/pyasn1/pyasn1-0.4.8.tar.gz
updating the info file is not enough though as although the md5sum is
correct, the slackbuild then fails with:

cp: cannot stat 'CHANGELOG.rst': No such file or directory
cp: cannot stat 'TODO.md': No such file or directory

cryptography:
MD5SUM check for cryptography-38.0.1.tar.gz ... FAILED!
Expected: ba34eba3ae36cbf3d2e1ee3239f07732
Found:c47299bca4309cdda29626b0046d9229
Keeping the source and continuing.
MD5SUM check for ouroboros_macro-0.15.5.crate ... FAILED!
Expected: d74a2292a838c7a98feea8bacd494038
Found:ddadbc5d93365a6a6c95c458af039ecb
Keeping the source and continuing.

it then fails trying to use a different version of the ouroboros_macro
crate file

Error occurred with build.  Please check the log.
tar: /var/lib/sbopkg/SBo/python/cryptography/ouroboros_macro-0.15.4.crate:
Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Cleaning up...

On Sat, 15 Oct 2022 at 05:20, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> Sat Oct 15 03:48:37 UTC 2022
> Update .gitignore + waf-2.0.*.
> academic/DRAMSim2: Added (A cycle accurate DRAM simulator)
> academic/IGV: Updated for version 2.14.1.
> academic/bcftools: Upgrade to version 1.16
> academic/bowtie: Updated for version 1.3.1.
> academic/cdo: Updated for version 2.0.6
> academic/cryptominisat: Updated for version 5.11.3.
> academic/gelemental: Updated for version 2.0.1.
> academic/hyphy: Updated for version 2.5.42.
> academic/jalview: Updated for version 2.11.2.4.
> academic/mathics: sympy renamed python2-sympy in REQUIRES.
> academic/muscle5: Added (MUSCLE 5: Next-generation MUSCLE)
> academic/openboard: Fix build with newer ffmpeg.
> academic/paml: Updated for version 4.10.5.
> academic/pamlX: Rebuild for paml update.
> academic/pysam: use shipped htslib-1.15.1
> academic/rpy2: Upgrade to version 3.5.5
> academic/samtools: Ugrade to version 1.16.1
> academic/scipy3: Update README
> academic/voro++: Added (A 3D Voronoi cell software library)
> academic/zotero: updated for version 6.0.15
> audio/qtractor: Updated for version 0.9.29.
> audio/tauonmb: Rebuilt for python3-websocket-client.
> audio/yoshimi: Updated for version 2.2.2.1.
> desktop/anki: Markdown removed from REQUIRES.
> desktop/buku: Updated for version 4.7.
> development/QtPy: Update for 2.2.1
> development/cocotb: Added (verify VHDL and SystemVerilog RTL)
> development/hipSYCL: Added (SYCL implementation targeting CPU+GPUs)
> development/hugo: update 0.104.3
> development/jupyter-nbformat: Update for 5.7.0
> development/jupyter_server: Updated for version 1.21.0.
> development/nodejs: Updated for version 18.11.0.
> development/rustup: Updated README.
> development/tkdiff: Updated for version 5.5.3
> development/vc-intrinsics: Added (LLVM IR instructions rep. SIMD)
> development/xmake: Updated for version 2.7.2.
> games/0ad-data: Rebuilt to extract directly into $PKG.
> games/0ad: Updated for version 0.0.26.
> games/freeciv: updated for version 3.0.4
> gis/python3-cftime: Added (Time-handling functionality from netcdf4)
> gis/python3-netcdf4-python: Added (Python3 interface for netCDF)
> gis/python3-shapely: Updated for version 1.8.5.post1
> gis/python3-xarray: Updated for version 2022.10.0
> graphics/draw.io: Removed (renamed drawio).
> graphics/drawio: Added (powerful diagram editor)
> graphics/mtpaint: Updated for version 3.50.09.
> graphics/vuescan: Updated for version 9.7.94.
> libraries/Botan: Updated for version 2.19.2.
> libraries/dropbox-python: Modified for py2/3 pytest-runner.
> libraries/glw: Added (SGI's OpenGL Xt/Motif widgets)
> libraries/goffice: Updated for version 0.10.53.
> libraries/htslib: Upgrade to version 1.16
> libraries/libcpuid: Updated for version 0.6.0.
> libraries/libfilezilla: Updated for version 0.39.2.
> libraries/libsoup3: Updated for version 3.2.1.
> libraries/pyte: Rebuilt for python2-pytest-runner.
> libraries/zfec: Updated for version 1.5.7.2.
> misc/bitwarden-desktop: Updated for version 2022.10.0.
> multimedia/jellyfin-media-player: Use correct source for web client
> multimedia/mpv: Update waf version to 2.0.24
> multimedia/svt-hevc: Added (Xeon/HEVC-compliant encoder library)
> multimedia/svt-vp9: Added (Xeon/VP9-compliant encoder library)
> network/armcord: Added (Discord custom client)
> network/brave-browser: Updated for version 1.44.112
> network/dropbox: Updated for version 160.3.4611.
> network/element-desktop: Updated for version 1.11.10.
> network/ircd-hybrid: Updated for version 8.2.43
> network/kismet: Removed CHANGELOG from docs as it doesn't exist anymore
> network/kstart: Up

[Slackbuilds-users] syntax error in ghostwriter.info

[Greg' Ar Tourter]

Hi

There is an extra " at the beginning of the line containing MD5SUM_x86_64
in the ghostwriter info file that should not be there.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] extra .SlackBuild file in netcdf-fortran

[Greg' Ar Tourter]

No worries Nitish,

The package has already been corrected by Willy and been pushed in the
latest update. So as long as you update your local copy to what is now on
the repo you will be fine for your next update.

Cheers

Greg

On Sun, 25 Sept 2022 at 11:47, Nitish Ragoomundun 
wrote:

> Hello,
>
> Thank you for your email. Indeed, I humbly used your script as an example
> for the SlackBuilds script for netcdf-fortran. I have made a new submission
> already to correct for my mistake. I am currently in contact with Dave from
> SlackBuilds.org about the matter.
>
> I would like to second your request for a check by sbolint for such cases.
>
> Kind regards,
> Nitish
>
>
> On Sunday, September 25, 2022, Greg' Ar Tourter 
> wrote:
>
>> Hi
>>
>> It looks like a copy of the netcdf.SlackBuild found its way into the
>> netcdf-fortran package. I suspect the author used it as a starting point
>> for their script and forgot to remove it from the submission.
>>
>> Maybe a check should be added to sbolint make sure only one .SlackBuild
>> is present.
>>
>> Cheers
>>
>> Greg
>>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] extra .SlackBuild file in netcdf-fortran

[Greg' Ar Tourter]

Hi

It looks like a copy of the netcdf.SlackBuild found its way into the
netcdf-fortran package. I suspect the author used it as a starting point
for their script and forgot to remove it from the submission.

Maybe a check should be added to sbolint make sure only one .SlackBuild is
present.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] netcdf package maintenance

[Greg' Ar Tourter]

Hi

I was wondering if it would be ok if I updated netcdf again or took over
its maintenance for now. I have realised that one of my packages (cdo),
although it compiles fine with the version of netcdf in the repo, actually
outputs incorrect data in some cases. compiling against the latest version
of netcdf (4.9.0 - which also brings a few new features including zarr
support) fixes the issue.

I have already checked all the dependees and can submit some fixes to a
couple of them which require them.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [Slackware-current] sbopkg problems

[Greg' Ar Tourter]

I seem to have seen something similar a while back. It was due to a weirdly
formed package name which triped sbopkg. But I can't remember which one it
was. It only triggered when that package was up for upgrade though,
otherwise sbopkg would work fine, so it may not be the same issue.

I am currently using sbopkg with the SBo-git repo on one of my machines
without any issues though.

On Tue, 23 Aug 2022 at 06:30,  wrote:

> If you don't use Slackware-current (many do use it) simply ignore this.
>  As I and another on this mailing list stated in past, SBo-git
> sbopkg no longer works.  Even after reverting from git to stable, sbopkg
> can find updates but no longer displays any queue submenu graphically,
> and now most/all sbopkg command-line commands/arguments/flags/switches
> just open sbopkg GUI.   Someone wrote it off as 'something you did to
> your PC': clearly false as exact same happened to someone else so is
> some situation (maybe involving standard Slackware-current and/or Sbo
> upgrades) that may become common.  It all even continues to happen even
> after I removed sbopkg 20220318_8bf4e6a and installed 0.38.2
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Xerces-c source and hdf5

[Greg' Ar Tourter]

I cannot see any issue with either the xerces-c source nor the hdf5 source.
They both download and build fine using the original source and scripts.

Can you give more details about the issues you are getting?

Cheers

Greg


On Thu, 7 Apr 2022 at 01:44, Poligraf Poligrafovich Bouboulov via
SlackBuilds-users  wrote:

> Hello, just to say that the address of the xerces-c source has changed :
> the tar.gz is now at :
>
> https://dlcdn.apache.org//xerces/c/3/sources/xerces-c-3.2.3.tar.gz
>
> Also I had some problems with the hdf5 package : i had to rewrite the
> slackbuild manually but i'm not so skilled at the moment. The archive
> seems corrupted but managed to compile it wit the .tar editing the
> .Slackbuild file.
>
> Have a nice day, Bouboulov :)
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] gdal tarball possibly changed layout

[Greg' Ar Tourter]

Konrad,

note that if you are using OTB, the slackbuild is currently not maintained
as Benjamin unfortunately has stopped maintaining his builds. So if you
feel like taking it up, I suspect it is free.

Greg

On Tue, 5 Apr 2022 at 17:23, Konrad J Hambrick  wrote:

> Thanks Greg.
>
> Worked Great !
>
> OTB ( montevideo ) is running as expected without a rebuild with gdal 3.4.2
>
> -- kjh
>
>
> On Tue, Apr 5, 2022 at 10:53 AM Konrad J Hambrick 
> wrote:
>
>> Thanks Greg !
>>
>> Building gdal 3.4.2 now :)
>>
>> -- kjh
>>
>> On Mon, Apr 4, 2022 at 6:47 PM Greg' Ar Tourter 
>> wrote:
>>
>>> Hi Luis,
>>>
>>> I submitted a fix a few days ago for this. in the meantime use the
>>> source url off the slackbuild website:
>>> https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
>>> or look at the change in git:
>>>
>>> https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666
>>>
>>> Then you do not need to change anything to the slackbuild script.
>>>
>>> Hope this helps
>>>
>>> Cheers
>>>
>>> Greg
>>>
>>> On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos 
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> these days I tried to build some packages which changed the SlackBuild
>>>> script, among them, gdal.
>>>>
>>>> In the first run, it failed.
>>>>
>>>> Searching a little bit, it seemed that the tarball has a slightly
>>>> different layout. In fact, everything that was supposed to be in the
>>>> root level is actually in the "./gdal" subdirectory.
>>>>
>>>> Also, the "configure" script was not there. It was rebuilt running
>>>> "autoreconf -fi" in the right time.
>>>>
>>>> I managed to tweak the slackbuild script and could ultimately build the
>>>> package. A patch is provided below.
>>>>
>>>> Anyway, it's wise to check whether these findings happen in other
>>>> environments before taking any measure. One other possible cause would
>>>> be the tarball URL be incorrect.
>>>>
>>>> Many thanks,
>>>>
>>>> Luiz Ramos
>>>> lramos dot prof at yahoo dot com dot br
>>>> São Paulo - Brazil
>>>>
>>>>
>>>> ===
>>>> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
>>>> From: Luiz Ramos 
>>>> Date: Sun, 3 Apr 2022 19:46:55 -0300
>>>> Subject: [PATCH] gis/gdal: fixed build
>>>>
>>>> Appearently the tarball downloaded changed its layout and so the build
>>>> directory
>>>> has to be changed. Also, there is no "configure" file: it has to be
>>>> build using
>>>> "autoreconf -fi".
>>>> ---
>>>>  gis/gdal/gdal.SlackBuild | 9 -
>>>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
>>>> index 4f8345..056874624f 100644
>>>> --- a/gis/gdal/gdal.SlackBuild
>>>> +++ b/gis/gdal/gdal.SlackBuild
>>>> @@ -119,6 +119,9 @@ else
>>>> WITHLIST+=" --with-jpeg=yes"
>>>>  fi
>>>>
>>>> +cd gdal
>>>> +autoreconf -fi
>>>> +
>>>>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>>>>  CPPFLAGS="-I/usr/include/mysql/server" \
>>>>  CFLAGS="$SLKCFLAGS" \
>>>> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>>>>  make
>>>>  make install DESTDIR=$PKG
>>>>
>>>> +cd ..
>>>> +
>>>>  find $PKG | xargs file | grep -e "executable" -e "shared object" |
>>>> grep ELF \
>>>>| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>>>>
>>>>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
>>>> +cd gdal && \
>>>>  cp -a \
>>>>COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
>>>> PROVENANCE.TXT VERSION \
>>>> -  $PKG/usr/doc/$PRGNAM-$VERSION
>>>> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
>>>> +cd ..
>>>>  cat $CWD/$PRGNAM.SlackBuild >
>>>> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>>>>
>>>>  rm -f $PKG/usr/lib*/*.la
>>>> --
>>>> 2.35.1
>>>>
>>>> ___
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users@slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] gdal tarball possibly changed layout

[Greg' Ar Tourter]

Hi Luis,

I submitted a fix a few days ago for this. in the meantime use the source
url off the slackbuild website:
https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
or look at the change in git:
https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666

Then you do not need to change anything to the slackbuild script.

Hope this helps

Cheers

Greg

On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos 
wrote:

> Hello,
>
> these days I tried to build some packages which changed the SlackBuild
> script, among them, gdal.
>
> In the first run, it failed.
>
> Searching a little bit, it seemed that the tarball has a slightly
> different layout. In fact, everything that was supposed to be in the
> root level is actually in the "./gdal" subdirectory.
>
> Also, the "configure" script was not there. It was rebuilt running
> "autoreconf -fi" in the right time.
>
> I managed to tweak the slackbuild script and could ultimately build the
> package. A patch is provided below.
>
> Anyway, it's wise to check whether these findings happen in other
> environments before taking any measure. One other possible cause would
> be the tarball URL be incorrect.
>
> Many thanks,
>
> Luiz Ramos
> lramos dot prof at yahoo dot com dot br
> São Paulo - Brazil
>
>
> ===
> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
> From: Luiz Ramos 
> Date: Sun, 3 Apr 2022 19:46:55 -0300
> Subject: [PATCH] gis/gdal: fixed build
>
> Appearently the tarball downloaded changed its layout and so the build
> directory
> has to be changed. Also, there is no "configure" file: it has to be build
> using
> "autoreconf -fi".
> ---
>  gis/gdal/gdal.SlackBuild | 9 -
>  1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
> index 4f8345..056874624f 100644
> --- a/gis/gdal/gdal.SlackBuild
> +++ b/gis/gdal/gdal.SlackBuild
> @@ -119,6 +119,9 @@ else
> WITHLIST+=" --with-jpeg=yes"
>  fi
>
> +cd gdal
> +autoreconf -fi
> +
>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>  CPPFLAGS="-I/usr/include/mysql/server" \
>  CFLAGS="$SLKCFLAGS" \
> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>  make
>  make install DESTDIR=$PKG
>
> +cd ..
> +
>  find $PKG | xargs file | grep -e "executable" -e "shared object" | grep
> ELF \
>| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>
>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
> +cd gdal && \
>  cp -a \
>COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
> PROVENANCE.TXT VERSION \
> -  $PKG/usr/doc/$PRGNAM-$VERSION
> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
> +cd ..
>  cat $CWD/$PRGNAM.SlackBuild >
> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>
>  rm -f $PKG/usr/lib*/*.la
> --
> 2.35.1
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] netcdf package update

[Greg' Ar Tourter]

Hi

I was wondering if it would be ok if I updated netcdf again. I have just
realised that one of my packages (cdo), although it compiles fine with the
version of netcdf in the repo, actually outputs incorrect data in some
cases. compiling against the latest version of netcdf (4.8.1 - which also
brings a few new features including zarr support) fixes the issue.

I would of course check all it dependees (a few of which I maintain anyway)

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] SlackBuild 15.0 Office/scribus-1.5.8-x86_64-1_SBo.tgz

[Greg' Ar Tourter]

I am afraid you are still using the 14.2 tree rather than the git master
branch which is the 15.0 working tree. Scribus has been updated to the
1.5.x version which is QT5 based about a year ago and the version currently
in the master branch is 1.5.7 from November last year.

https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=scribus

Greg

On Mon, 7 Mar 2022 at 15:06, Peter Dambier  wrote:

> Hi fellow SlackBuilders,
>
> with QT5, scribus-1.4.6.tar.xz no longer builds, nor does
> scribus-1.4.7.tar.xz
>
> But scribus-1.5.8.tar.xz does. It is development but it is meant for QT5
>
> pcmanfm finds it under Graphics.
> It seems to be working.
> It takes its time loading - no wonder with so many libraries.
>
> ldd /usr/bin/scribus:
>
> linux-vdso.so.1
> libcairo.so.2
> libQt5Xml.so.5
> libQt5Network.so.5
> libQt5OpenGL.so.5
> libQt5PrintSupport.so.5
> libz.so.1
> libxml2.so.2
> libcups.so.2
> libfreetype.so.6
> libharfbuzz-icu.so.0
> libharfbuzz.so.0
> libharfbuzz-subset.so.0
> libicuuc.so.69
> libicudata.so.69
> libtiff.so.5
> libpng16.so.16
> libjpeg.so.62
> libfontconfig.so.1
> libdl.so.2
> liblcms2.so.2
> libQt5Widgets.so.5
> libQt5Gui.so.5
> libQt5Core.so.5
> libstdc++.so.6
> libm.so.6
> libgcc_s.so.1
> libc.so.6
> libpthread.so.0
> libpixman-1.so.0
> libEGL.so.1
> libxcb-shm.so.0
> libxcb.so.1
> libxcb-render.so.0
> libXrender.so.1
> libX11.so.6
> libXext.so.6
> libGL.so.1
> librt.so.1
> libgssapi_krb5.so.2
> libssl.so.1.1
> libcrypto.so.1.1
> liblzma.so.5
> libkrb5.so.3
> libk5crypto.so.3
> libcom_err.so.2
> libgnutls.so.30
> libcrypt.so.1
> libbz2.so.1
> libbrotlidec.so.1
> libgraphite2.so.3
> libglib-2.0.so.0
> /lib64/ld-linux-x86-64.so.2
> libwebp.so.7
> libzstd.so.1
> libicui18n.so.69
> libpcre2-16.so.0
> libgthread-2.0.so.0
> libGLdispatch.so.0
> libXau.so.6
> libXdmcp.so.6
> libGLX.so.0
> libkrb5support.so.0
> libkeyutils.so.1
> libresolv.so.2
> libp11-kit.so.0
> libidn2.so.0
> libunistring.so.2
> libnettle.so.8
> libhogweed.so.6
> libgmp.so.10
> libbrotlicommon.so.1
> libpcre.so.1
> libffi.so.7
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] New Templates and 15.0 Repository Progress

[Greg' Ar Tourter]

I have also checked nagios_plugins and it builds fine at my end.

If you can get more info as to why it fail, I can look further. Looking at
the build logs, it doesn't download anything during the build however the
configure script does test for ping and ping6 using 127.0.0.1 and ::1 to
test the syntax, so if there is no network at all in CI, not even localhost
that could explain the failure.

Cheers

Greg

On Sun, 6 Mar 2022 at 17:56, Willy Sudiarto Raharjo 
wrote:

> > Thanks for the explanation. I have just checked and the build script does
> > download anything. There are a few warnings at build time but otherwise
> > nothing out of the ordinary.
> >
> > I attach the log file where I built pdfpc and all its dependencies.
>
> OK, good to know
> we just have to make some adjustment on the CI tool
>
>
> --
> Willy Sudiarto Raharjo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] New Templates and 15.0 Repository Progress

[Greg' Ar Tourter]

Hi Willie,

Thanks for the explanation. I have just checked and the build script does
download anything. There are a few warnings at build time but otherwise
nothing out of the ordinary.

I attach the log file where I built pdfpc and all its dependencies.

Cheers

Greg

On Sun, 6 Mar 2022 at 01:35, Willy Sudiarto Raharjo 
wrote:

> > I noticed that pdfpc is in the failed list. I have no problem building it
> > here, can someone let me know what error they are getting?
>
> It could be false positive since that list is generated by CI system and
> it was designed with some restrictions such as no network access during
> build. If a script is downloading something in the middle of a build
> process and it has no internet access, it will fail eventually
>
>
>
> --
> Willy Sudiarto Raharjo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


pdfpc_build.log.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Pitivi not running

[Greg' Ar Tourter]

there is a separate package for the python3 version of matplotlib:
development/python3-matplotlib

On Sat, 5 Mar 2022 at 18:00, Luiz Carlos Ramos via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hello,
>
> today I tried to upgrade Pitivi version to the last one, and it turns
> out that the final binary (in fact, a Python3 script) didn't run,
> showing signs of a missing matplotlib.
>
> Digging a little bit, one found that the problem was on two
> dependencies, kiwisolver and cycler, which didn't have the Python3
> version built.
>
> I could solve it including in these packages a command to build Python3
> bits along the Python2 ones, like that:
>
>  python setup.py install --root $PKG
> [+]  python3 setup.py install --root $PKG
>
> and rebuilding kiwisource and cycler.
>
> Conversely to what the error message points, it seems there is no need
> to install the whole matplotlib. By the way, the current matplotlib SBo
> lacks Python3 support.
>
> Hope it helps,
>
> Luiz Ramos
> lramos dot prof at yahoo dot com dot br
> Sao Paulo - Brazil
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] New Templates and 15.0 Repository Progress

[Greg' Ar Tourter]

Hi Willie,

I noticed that pdfpc is in the failed list. I have no problem building it
here, can someone let me know what error they are getting?

Cheers

Greg

On Sat, 5 Mar 2022 at 16:33, Ozan Türkyılmaz 
wrote:

> He beat me to it. ALso he had the same annoyances. Never fun of cmake.
>
>
> Matteo Bernardini , 5 Mar 2022 Cmt, 19:29
> tarihinde şunu yazdı:
>
>> Hi Ozan,
>>
>> Jeremy already sent an update to 19.4 for kodi, it's on git
>>
>>
>> https://git.slackbuilds.org/slackbuilds/commit/?id=2aaa8213472023ab08488efb41181864c8d106ff
>>
>> Matteo
>>
>> Il giorno sab 5 mar 2022 alle ore 17:26 Ozan Türkyılmaz
>>  ha scritto:
>> >
>> > Hello,
>> >
>> > I started tinkering kodi now. New version looks like will work with
>> 15.0. BUild system is now cmake.
>> > I'll keep you posted.
>> > I tinkered wine-nine-standalone. I don't think it will work without
>> serious work.
>> >
>> > Regards,
>> > Ozan
>> >
>> > Willy Sudiarto Raharjo , 5 Mar 2022 Cmt,
>> 19:01 tarihinde şunu yazdı:
>> >>
>> >> Hi guys
>> >>
>> >> we are still trimming down all the remaining scripts to check against
>> >> Slackware 15.0 and hopefully we will see 15.0 repository soon.
>> >>
>> >> The list can be seen here: https://slackbuilds.org/FAILED-15.0
>> >> You can help by confirming whether a certain scripts does build
>> >> correctly against Slackware 15.0 (full installation and clean
>> >> environment please). Let us know in the mailing list when you have
>> >> confirmed.
>> >>
>> >> I have also pushed new templates for 15.0 SlackBuilds to git and also
>> to
>> >> the website at https://slackbuilds.org/templates/
>> >>
>> >> please download and use them for future new submission.
>> >>
>> >> Thanks
>> >>
>> >>
>> >> --
>> >> Willy Sudiarto Raharjo
>> >> ___
>> >> SlackBuilds-users mailing list
>> >> SlackBuilds-users@slackbuilds.org
>> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> >> FAQ - https://slackbuilds.org/faq/
>> >>
>> > ___
>> > SlackBuilds-users mailing list
>> > SlackBuilds-users@slackbuilds.org
>> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> > FAQ - https://slackbuilds.org/faq/
>> >
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] wrong md5sum for protobuf-c 1.4.0 package

[Greg' Ar Tourter]

Hi

looks like the checksum wasn't updated in the 1.4.0 upgrade:

Found protobuf-c-1.4.0.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for protobuf-c-1.4.0.tar.gz ... FAILED!
Expected: dabc05a5f11c21b96d8d6db4153f5343
Found:10e1103a012ce0877c32367949a2fa6e

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] renaming python scripts

[Greg' Ar Tourter]

Hi all,

Some of my python scripts, mostly inherited, tend to be a bit over the
place. Some are named with a python?- prefix, some aren't, some are not in
the python folder but in libraries (nltk and that one is my fault).

I know there has been a long discussion in the past on how to deal with
python naming  but I am sure where we are at.

This was vaguely prompted by me tracking my packages in repology which in
some cases doesn't add the python: prefix to some of the packages (xarray
and nltk).

Should I rename/relocate these?

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Looking for new signal-desktop maintainer

[Greg' Ar Tourter]

Hi David,

I am happy to take this one over. I will submit an updated version using
the binary build as a PR a bit later.

Cheers

Greg

On Thu, 17 Feb 2022 at 07:04, David O'Shaughnessy  wrote:

> Hello all,
>
> I'm looking to give up signal-desktop, as it's a fiddly source build, as
> well as suffering from binaries being frequently removed upstream (and I've
> started playing around with packaging it for my own repo). It's not the
> sort of package you can just leave without updates, as upstream will
> eventually disable old builds anyway.
>
> That said, it's a great program/service. Would anyone be interested in
> taking it over?
>
> --
> Dave
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] upstream name change from Shapely to shapely

[Greg' Ar Tourter]

Just a heads-up that Shapely has been renamed shapely and the git repo has
also be moved from github.com/Toblerity/Shapely to github.com/shapely/
shapely

I was updating the script for 1.8.1 when I noticed the change.

I will update the info file of all the dependent packages and send a PR but
thought I'd give a heads up first. Thankfully the list is not very long.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] qtcurve

[Greg' Ar Tourter]

Hi,

I see that qtcurve has been removed from the git master for it requiring
KD4. I have been able to compile the latest master with QT5 and KF5 support
from upstream git repo on -15.0 *but*:
- I don't actually use it anymore
- there is no GTK-3 version of the theme

The lack of GTK-3 support is very much what made me stop using it since the
whole point for me at the time was the uniform look across applications.

If someone wants to take over they are welcome, I can share my script to
make it compile on -15.0 as a starting point. Otherwise we can leave it in
the removed pile but I thought I'd let the list know.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] updating gis/proj?

[Greg' Ar Tourter]

Willy,

debian has submitted a pull request to support proj8. I have tested it and
it seems to work fine on version 0.9.5. I can submit a PR for this update
and libspatialite along with my other updates if that is ok so that nothing
breaks.

Note I am not proposing to take over maintenance of openorienteering-mapper
or libspatialite, simply submitting updates to stop these packages from
breaking after my updating of the packages I am taking over maintenance.

Cheers

Greg

On Sat, 16 Oct 2021 at 13:45, Greg' Ar Tourter  wrote:

> Hi Willy,
>
> Yes I did, it still tries to find proj by looking for the now removed
> proj_api.h rather than proj.h. I have tried to modify the FindPROJ.cmake
> file, but since I have never really played with cmake I am just guessing
> things and it didn't work.
>
> The way the version is stored in proj.h is different from what it was
> before so it is not as simple as just replacing proj_api.h with proj.h. I
> Will try and dig deeper but haven't found the time yet. If I manage to do
> it so that it still works with the older file as well I will submit a patch
> upstream.
>
> Whether there are more things in the code that need to be changed, I don't
> know yet.
>
> Cheers
>
> Greg
>
>
>
> On Sat, 16 Oct 2021 at 13:04, Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> > proj  version 8 has removed something that had been deprecated for quite
>> > some time but was still accessible to allow devs to modify their code.
>> Now
>> > it is no longer available and therefore some packages can no longer be
>> > compiled as they haven't been modified. This is the case for
>> > openorienteering-mapper.
>> >
>> > What I am asking the admins/list is whether it is ok for me to submit an
>> > update if a package that depends on it will suffer until a patch is
>> found.
>>
>> Did you try to update openorienteering-mapper to 0.9.5 and see if it
>> works?
>>
>>
>> --
>> Willy Sudiarto Raharjo
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] updating gis/proj?

[Greg' Ar Tourter]

Hi Willy,

Yes I did, it still tries to find proj by looking for the now removed
proj_api.h rather than proj.h. I have tried to modify the FindPROJ.cmake
file, but since I have never really played with cmake I am just guessing
things and it didn't work.

The way the version is stored in proj.h is different from what it was
before so it is not as simple as just replacing proj_api.h with proj.h. I
Will try and dig deeper but haven't found the time yet. If I manage to do
it so that it still works with the older file as well I will submit a patch
upstream.

Whether there are more things in the code that need to be changed, I don't
know yet.

Cheers

Greg



On Sat, 16 Oct 2021 at 13:04, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > proj  version 8 has removed something that had been deprecated for quite
> > some time but was still accessible to allow devs to modify their code.
> Now
> > it is no longer available and therefore some packages can no longer be
> > compiled as they haven't been modified. This is the case for
> > openorienteering-mapper.
> >
> > What I am asking the admins/list is whether it is ok for me to submit an
> > update if a package that depends on it will suffer until a patch is
> found.
>
> Did you try to update openorienteering-mapper to 0.9.5 and see if it works?
>
>
> --
> Willy Sudiarto Raharjo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] updating gis/proj?

[Greg' Ar Tourter]

Rich, this is not really what I am asking.

I have taken over the maintenance of several of Ben's scripts, some of
which can be updated to newer versions, especially proj.

proj  version 8 has removed something that had been deprecated for quite
some time but was still accessible to allow devs to modify their code. Now
it is no longer available and therefore some packages can no longer be
compiled as they haven't been modified. This is the case for
openorienteering-mapper.

What I am asking the admins/list is whether it is ok for me to submit an
update if a package that depends on it will suffer until a patch is found.

Greg

On Fri, 15 Oct 2021 at 13:48, Rich Shepard  wrote:

> On Fri, 15 Oct 2021, Greg' Ar Tourter wrote:
>
> > I am trying to update proj to the latest 8.x version after taking
> > maintainership.
> > I have tested the new version will all its first level dependees and most
> > of them compile without any modifications:
> > - cartopy (taking over as well and updating to 0.20.1 which requires proj
> > 8.x)
> > - cdo
> > - gdal
> > - libgeotiff
> > - pyproj
> > - proj-data
> >
> > however, a couple of the dependees fail to compile as is.
> > - libspatialite needs to be updated to version 5.x (tested with the
> latest
> > 5.0.1)
> > - openorienteering-mapper fails to compile and even updating to the
> latest
> > version doesn't help
> >
> > Should I hold off updating?
>
> Greg' Ar,
>
> I'm not an SBo package maintainer but I offer a thought I learned a long
> time ago about the build sequence for spatial analyses packages. Perhaps
> it's relavent to your question, perhaps not.
>
> The stack proj -> geos -> gdal need to be built in that order. If proj is
> updated then the other two must also be upgraded. If geos is upgraded then
> gdal has to be rebuilt. Any other software depending on those need the
> stack
> to be rebuilt before they are.
>
> I've found this is needed with GRASS, R, and SAGA.
>
> Regards,
>
> Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Slackbuilds

[Greg' Ar Tourter]

I am going to add pyproj to my list as well since it is required by the
latest version of cartopy

Cheers

Greg

On Thu, 14 Oct 2021 at 15:29, Greg' Ar Tourter  wrote:

> Also add
> - Shapely
> - pyshp
> - gdal
>
> Greg
>
> On Thu, 14 Oct 2021 at 13:22, Greg' Ar Tourter 
> wrote:
>
>> Thanks for all your work Ben. Sorry to see you go.
>>
>> Unless someone else want them, I am happy to take over
>> - keepassxc
>> - proj
>> - proj-data
>> - geos
>> - cartopy
>>
>> Cheers
>>
>> Greg
>>
>>
>> On Thu, 14 Oct 2021 at 04:07, Benjamin Trigona-Harany <
>> slackbui...@jaxartes.net> wrote:
>>
>>> I am no longer going to be maintaining my Slackbuilds. Please feel free
>>> to claim them.
>>>
>>> Best, Ben
>>> ___
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users@slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] updating gis/proj?

[Greg' Ar Tourter]

I am trying to update proj to the latest 8.x version after taking
maintainership.
I have tested the new version will all its first level dependees and most
of them compile without any modifications:
- cartopy (taking over as well and updating to 0.20.1 which requires proj
8.x)
- cdo
- gdal
- libgeotiff
- pyproj
- proj-data

however, a couple of the dependees fail to compile as is.
- libspatialite needs to be updated to version 5.x (tested with the latest
5.0.1)
- openorienteering-mapper fails to compile and even updating to the latest
version doesn't help

Should I hold off updating?

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Slackbuilds

[Greg' Ar Tourter]

Also add
- Shapely
- pyshp
- gdal

Greg

On Thu, 14 Oct 2021 at 13:22, Greg' Ar Tourter  wrote:

> Thanks for all your work Ben. Sorry to see you go.
>
> Unless someone else want them, I am happy to take over
> - keepassxc
> - proj
> - proj-data
> - geos
> - cartopy
>
> Cheers
>
> Greg
>
>
> On Thu, 14 Oct 2021 at 04:07, Benjamin Trigona-Harany <
> slackbui...@jaxartes.net> wrote:
>
>> I am no longer going to be maintaining my Slackbuilds. Please feel free
>> to claim them.
>>
>> Best, Ben
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Slackbuilds

[Greg' Ar Tourter]

Thanks for all your work Ben. Sorry to see you go.

Unless someone else want them, I am happy to take over
- keepassxc
- proj
- proj-data
- geos
- cartopy

Cheers

Greg


On Thu, 14 Oct 2021 at 04:07, Benjamin Trigona-Harany <
slackbui...@jaxartes.net> wrote:

> I am no longer going to be maintaining my Slackbuilds. Please feel free to
> claim them.
>
> Best, Ben
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20210403.1

[Greg' Ar Tourter]

Hi,

The latest Teams slackbuild fails due to the missing doinst.sh file. I am
not sure it is supposed to be there but missing, or was removed on purpose
but the slackbuild script is still expecting one.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] documentation file for pdfstudioviewer no longer available

[Greg' Ar Tourter]

Hi,

It looks like the documentation file for pdfstudioviewer is no longer
available for download. There is now only an online version. The online
version has a different link for the pdf file (
https://www.qoppa.com/files/pdfstudioviewer/guide/assets/docs/pdfstudio2019_userguide.pdf)
but you still get a 404 error when you try to download it.

Can the pdf document be removed from the slackbuild as it currently makes
it fail if you haven't got the file in the cache. (This is also valid for
the slackbuild currently in "approved")

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] help testing new package

[Greg' Ar Tourter]

Thanks for this Fellype,

from the error:
FileSupport.c:57:10: fatal error: ogr_api.h: No such file or directory
   57 | #include 
  |  ^~~
compilation terminated.

it looks like you are missing the gdal package.

it should require netcdf gdal and udunits (and their requirements). On
current I have used the version of gdal and proj from Ponce SBo-git repo

Cheers

Greg

On Thu, 18 Jun 2020 at 15:14, Fellype  wrote:

> Hello Greg,
>
>
> Em seg., 15 de jun. de 2020 às 20:32, Greg' Ar Tourter <
> artour...@gmail.com> escreveu:
>
>> Hi,
>>
>> I have written a Slackbuild for NCL (https://www.ncl.ucar.edu/).
>>
>> It is quite a tricky one to compile and it doesn't exit with an error
>> when make fails. The only way I have found to test if compilation fails is
>> to look for the ncl binary.
>>
>> Could I ask for a few kind souls to test the slackbuild and report back
>> if build fails and the error. I am interested in both -14.2 and -current,
>> 32bit and 64bit. This is not for the faint-hearted as it is quite big and
>> takes a while.
>>
>> It failed to build here (Slackware64-current). I don't know what exactly
> got wrong. So, you will have to inspect the build output, which can be
> found at:
>
> https://drive.google.com/file/d/10PVcVpnU-v3X4DXEd7zjjpHwv6nSd8sV/view?usp=sharing
> Regards,
>
> Fellype
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] help testing new package

[Greg' Ar Tourter]

Hi,

I have written a Slackbuild for NCL (https://www.ncl.ucar.edu/).

It is quite a tricky one to compile and it doesn't exit with an error when
make fails. The only way I have found to test if compilation fails is to
look for the ncl binary.

Could I ask for a few kind souls to test the slackbuild and report back if
build fails and the error. I am interested in both -14.2 and -current,
32bit and 64bit. This is not for the faint-hearted as it is quite big and
takes a while.

note that I do not compile hdf4 and grib2 compatibility in. If people want
to, I can test and add hdf4 but I cannot get the GRIB2 library to compile
and anyway, ncl requires its own patched version which feels like to
muchwork for something I cannot test myself.

Cheers

Greg


ncl.tar.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] SBOPKG: android-tools

[Greg' Ar Tourter]

You are building it on -current, aren't you?

This is exactly the same error I get when trying to build it on -current.
and slackbuilds doesn't support current.

However, try building the version from Ponce's SBo-git/current repo, and
note the additional requirement. It builds fine for me on current.


On Sat, 13 Jun 2020 at 17:35, Larry Hajali  wrote:

> It builds fine here (Slackware64 14.2 with all patches applied).
>>
>
> Same.  Builds fine here on Slackware64 14.2.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20200510.1

[Greg' Ar Tourter]

Willy, What happened to the netcdf update? was there something wrong?

On Sun, 10 May 2020 at 03:00, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> Sun May 10 01:38:26 UTC 2020
> academic/biblesync: Fix pkg-config.
> academic/chartgeany: Added (market analysis tool)
> academic/cryptominisat: Updated for version 5.7.1.
> academic/freechartgeany: Removed
> academic/gcompris-qt: Added (an educational software suite)
> academic/libqalculate: Updated for version 3.9.0a
> academic/mpb: Added (computing electromagnetic band).
> academic/qalculate-gtk: Updated for version 3.9.0a
> academic/sage: Fix post-installation path.
> academic/sword: Add patch to fix formatting.
> audio/qmmp-plugin-pack: Updated for version 0.12.2.
> audio/qmmp: Updated for version 0.12.7.
> desktop/bukubrow: Updated for version 5.1.0.
> desktop/simplenote: Updated for version 1.16.0.
> development/cmocka: Updated for version 6.5.2.
> development/jdk11: Fix shebang.
> development/jdk12: Fix shebang.
> development/jdk13: Fix shebang.
> development/jdk14: Fix shebang.
> development/libb2: Updated for version 0.98.1.
> development/nodejs: Updated for version 12.16.3.
> development/robotframework: Updated for version 3.2.1.
> development/spin: Updated for version 6.5.2.
> games/fceux: Fix build with scons.
> games/onscripter: Updated for version 20200419.
> gis/cartopy: Updated for version 0.18.0.
> gis/qgis: Updated for version 3.12.2.
> graphics/brlcad: updated for version 7.30.8
> ham/ax25-apps: Added (AX.25 Packet radio support software).
> ham/ax25-tools: Added (AX.25 Packet radio supporting tools).
> ham/libax25: Added (AX.25 Packet radio support for linux).
> libraries/SDL_kitchensink: updated for version 1.0.8
> libraries/VTK: Note VTK-8.2.0 is last suitable version for SL-14.2
> libraries/hoel: updated for version 1.4.16
> libraries/http-parser: Updated for version 2.9.4
> libraries/podofo: Updated for version 0.9.6
> libraries/zziplib: Updated for version 0.13.71
> misc/KeePass: Updated for version 2.45.
> multimedia/dvdbackup: Fix name.
> multimedia/k9copy-reloaded: Fix path.
> multimedia/lives: Fix email.
> multimedia/plexmediaserver: Updated for v 1.19.3.2764_ef515a800.
> network/asterisk: Updated for version 16.10.0.
> network/bluejeans: Fix shebang.
> network/openconnect: Updated for version 8.09 + new maintainer.
> network/pexip-infinity-connect: Fix shebang.
> network/prosody-mod-cloud-notify: Updated for version hg3996.
> network/prosody-mod-smacks: Updated for version hg4009.
> network/qutebrowser-tox: Updated for version 1.11.1.
> network/slimjet: Updated for version 26.0.5.0.
> network/telegram: Updated for version 2.1.2.
> network/telegram: Updated for version 2.1.4.
> network/tor-browser: Updated for version 9.0.10.
> network/vivaldi: Updated for version 3.0.1874.38.
> network/wireguard-linux-compat: Updated for version 1.0.20200506.
> network/zeek: Updated for version 3.0.5.
> office/gnucash-legacy-docs: Update email.
> office/gnucash-legacy: Update README.
> office/gnucash: Update README.
> office/texmaker: Updated for version 5.0.4
> office/texstudio: Updated for version 2.12.22
> office/timew: Updated for version 1.3.0.
> office/when: Added (an extremely simple personal calendar program)
> perl/MoarVM: Updated for version 2020.05.
> perl/nqp: Updated for version 2020.05.
> perl/perl-Net-ARP: Updated for version 1.0.11.
> perl/rakudo: Updated for version 2020.05.
> perl/zef: Updated for version 0.8.4.
> python/python3-astroid: Updated for version 2.4.0.
> python/python3-ipython: Updated for version 7.14.0.
> python/python3-pylint: Updated for version 2.5.0.
> system/bat: Revert to version 0.13.0.
> system/ccd2cue: Added (convert CloneCD images to bin/cue)
> system/chronograf: Updated for version 1.8.4.
> system/crc32_simple: Added (calculate crc32 checksum of files)
> system/dosbox-x: Updated for version 0.98.1.
> system/mksh: Updated for version R59.
> system/nvidia-driver: Update script.
> system/nvidia-legacy390-driver: Update script.
> system/osquery-bin: Added (OS instrumentation framework)
> system/ripgrep: Updated for version 12.1.0.
> system/skopeo: Updated to version 0.2.0.
> system/sleuthkit: Updated for version 4.9.0.
> system/telegraf: Updated for version 1.14.2.
> +--+
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] netcdf package update

[Greg' Ar Tourter]

Hi,

Grace compiles fine but GMT's slackbuilds is not correct since 'make
docs_man' and 'make docs_html' are not valid make targets. additionally,
-DLIB_SUFFIX is not a valid cmake option (although that doesn't stop it to
compile.

Once the two make commands are removed from the scripts, it compiles fine.

I also compiled gdal since I needed it as a requirement for GMT and it
automatically picked up netcdf and compiled ok.

I attach the new slackbuild if you want to test it more extensively.

Note that CDF5 is now enabled by default as the bug affecting 32 bit
install was fixed. I would probably remove the option to disable it
altogether but for now I have set it to default to yes and if for some
reason one wants to disable CDF5, one had to set CDF5=no but it is likely
to cause more issue than it is to solve.

Let me know if you are happy with it and I'll update the README file and
submit it.

Cheers

Greg

On Sat, 9 May 2020 at 18:25, Greg' Ar Tourter  wrote:

> Thanks Willy, I wish David the best.
>
> I have tested nco (which I maintain) and ncview. I will test grace and GMT
> and proceed accordingly.
>
> Cheers
>
> Greg
>
> On Sat, 9 May 2020 at 18:18, Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> > Any admin with opinions on this? I still haven't received anything back
>> > from David.
>>
>> >> I was wondering if David Spencer was was still active here. I have send
>> >> him a couple of emails earlier this months about updating his netcdf
>> >> slackbuild but I haven't received any replies from either of his email
>> >> addresses. I noticed that at least one of his script has been updated
>> by
>> >> someone else but without changing the maintainership.
>> >>
>> >> I am happy to update it myself or take over but not sure what is going
>> on.
>>
>> David is dealing with personal issue, so he may not be around for a while.
>>
>> As of netcdf, i think it's ok to bump this package with a simple
>> condition that every package that depends on netcdf must be tested to
>> avoid breakage.
>>
>> So far, i can only see GMT, grace, nco, and ncview
>> If you can test them before sending the update, it would be much
>> appreciated.
>>
>>
>> --
>> Willy Sudiarto Raharjo
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>


netcdf.tar.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] netcdf package update

[Greg' Ar Tourter]

Thanks Willy, I wish David the best.

I have tested nco (which I maintain) and ncview. I will test grace and GMT
and proceed accordingly.

Cheers

Greg

On Sat, 9 May 2020 at 18:18, Willy Sudiarto Raharjo 
wrote:

> > Any admin with opinions on this? I still haven't received anything back
> > from David.
>
> >> I was wondering if David Spencer was was still active here. I have send
> >> him a couple of emails earlier this months about updating his netcdf
> >> slackbuild but I haven't received any replies from either of his email
> >> addresses. I noticed that at least one of his script has been updated by
> >> someone else but without changing the maintainership.
> >>
> >> I am happy to update it myself or take over but not sure what is going
> on.
>
> David is dealing with personal issue, so he may not be around for a while.
>
> As of netcdf, i think it's ok to bump this package with a simple
> condition that every package that depends on netcdf must be tested to
> avoid breakage.
>
> So far, i can only see GMT, grace, nco, and ncview
> If you can test them before sending the update, it would be much
> appreciated.
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] netcdf package update

[Greg' Ar Tourter]

Hi,

Any admin with opinions on this? I still haven't received anything back
from David.

Cheers

Greg

On Sun, 26 Apr 2020 at 18:46, Greg' Ar Tourter  wrote:

> Hi,
>
> I was wondering if David Spencer was was still active here. I have send
> him a couple of emails earlier this months about updating his netcdf
> slackbuild but I haven't received any replies from either of his email
> addresses. I noticed that at least one of his script has been updated by
> someone else but without changing the maintainership.
>
> I am happy to update it myself or take over but not sure what is going on.
>
> Cheers
>
> Greg
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] netcdf package update

[Greg' Ar Tourter]

Hi,

I was wondering if David Spencer was was still active here. I have send him
a couple of emails earlier this months about updating his netcdf slackbuild
but I haven't received any replies from either of his email addresses. I
noticed that at least one of his script has been updated by someone else
but without changing the maintainership.

I am happy to update it myself or take over but not sure what is going on.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Unmaintained builds - want any of these?

[Greg' Ar Tourter]

I can take misc/linux_logo as well if that's ok.

Cheers

Greg

On Thu, 2 Jan 2020 at 13:33, Greg' Ar Tourter  wrote:

>
>
> I'll take audio/shorten and audio/shntools if no one wants them. shntools
> is a nice complement to cuetools which I already maintain.
>
> Happy New Year to All!
>
> Greg
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Michiel van Wessem's builds

[Greg' Ar Tourter]

I can take konversation if it is not wanted by anyone else.

Cheers

Greg

On Thu, 2 Jan 2020 at 11:13, Lenard Spencer 
wrote:

> I can take lame and sshfs-fuse for now,  since they are now included in
> -current.
>
> On Wed, Jan 1, 2020, 16:53 B Watson  wrote:
>
>> Michiel offered up all his builds a couple years ago... most of them
>> still list him as maintainer, meaning nobody took him up on the offer.
>>
>> I've taken the following (in my git branch):
>>
>> libraries/libopenraw
>> graphics/raw-thumbnailer
>> libraries/lame
>> office/evince
>> network/sshfs-fuse
>> libraries/exempi
>>
>> This still leaves quite a few. I have zero interest in using or
>> maintaining KDE-based builds, so it'd be nice if someone else
>> could pick these up:
>>
>> desktop/crystal
>> libraries/gtk-qt-engine
>> multimedia/kaffeine-mozilla
>> multimedia/kaffeine
>> network/konversation
>> office/kchmviewer
>>
>> Then there are a few non-KDE builds, if anyone wants them:
>>
>> libraries/gtksourceview
>> libraries/yaz
>> misc/asr-manpages
>> misc/funny-manpages
>> multimedia/gst0-plugins-bad
>> multimedia/gst0-plugins-ugly
>> system/chkrootkit
>>
>> I could take those, rather than see them disappear from the repo, but
>> I've got a ton of stuff already. Any takers?
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Unmaintained builds - want any of these?

[Greg' Ar Tourter]

I'll take audio/shorten and audio/shntools if no one wants them. shntools
is a nice complement to cuetools which I already maintain.

Happy New Year to All!

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] SOHO backup choices

[Greg' Ar Tourter]

One I have used in the past is backuppc (
https://backuppc.github.io/backuppc/). It is written in perl and includes a
web interface to manage.

I have been meaning to make a slackbuild for it but never found the time. I
may need to find some time for it though as I need to change my current
backup system.

Cheers

Greg

On Tue, 10 Sep 2019 at 15:41, Rich Shepard  wrote:

> I've used dirvish to backup my desktop server/workstation for about a
> decade. While it has worked flawlessly (and I've not needed a bare metal
> restore), I do daily incremental backups run from cron at 00:30 each day.
>
> I think it's time to replace it for use with my new desktop
> server/workstation and 2T external hard drive. I'll be adding a reserve
> desktop which will be kept current but not used for day-to-day business.
> And
> I might leave portables on overnight so they, too, can be backed up on
> occasion.
>
> The SBo list of packages displayed when I entered 'backup' in the search
> box
> is impressive, even overwhelming. I'd like advice in selecting a new backup
> tool.
>
> The two packages that look appropriate for my SOHO needs (and I didn't look
> at all of them) are flexbackup and Attic. Both do daily incremental backups
> for single hosts or small LANs. Should I install and learn both to support
> a
> choice or might there be others for me to consider?
>
> TIA,
>
> Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] skypeforlinux src not found.

[Greg' Ar Tourter]

the slackbuild needs to be updated for a newer version as the old debs are
removed regularly as new ones are released.

currently the latest stable version available is 8.51.0.92

https://repo.skype.com/deb/pool/main/s/skypeforlinux/skypeforlinux_8.51.0.92_amd64.deb

md5sum: e65f32767eb510d86db889247d6e9767

Hope this helps

Greg

On Sun, 8 Sep 2019 at 16:40, Fernando Lopez 
wrote:

>
> skypeforlinux src not found.
>
> --
>
> 
> Regards,
> Fernando Lopez Jr.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos

[Greg' Ar Tourter]

Actually, the one I use is keepassxc, so if it is ok, I'll put that one
back in the open. Sorry about this.

Cheers

Greg

On Sun, 17 Mar 2019 at 10:56, Greg' Ar Tourter  wrote:

> Hi,
>
> I can take over keepassx if no-one else wants it as I use it a lot.
>
> Cheers
>
> Greg
>
> On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> Hi
>>
>> Anyone want to take over this scripts?
>>
>>
>>  Forwarded Message 
>> Subject: New Maintainer Needed for SBos
>> Date: Sun, 17 Mar 2019 10:03:48 +
>> From: awg 
>> To: will...@slackbuilds.org
>>
>> Hi Willy,
>>
>> I no longer use the following packages:
>> * development/ChezScheme
>> * libraries/libaaio
>> * system/dieharder
>> * office/keepassx
>>
>> If someone else could take over maintainership for these packages,
>> I'd be grateful.
>>
>> Unlike the other three, ChezScheme is still actively maintained by
>> its developers.  Whoever takes this over should run the full test
>> battery on both threaded and unthreaded builds after each update to
>> check for regressions.
>>
>> Thank you!
>>
>> --
>> Willy Sudiarto Raharjo
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos

[Greg' Ar Tourter]

Hi,

I can take over keepassx if no-one else wants it as I use it a lot.

Cheers

Greg

On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> Hi
>
> Anyone want to take over this scripts?
>
>
>  Forwarded Message 
> Subject: New Maintainer Needed for SBos
> Date: Sun, 17 Mar 2019 10:03:48 +
> From: awg 
> To: will...@slackbuilds.org
>
> Hi Willy,
>
> I no longer use the following packages:
> * development/ChezScheme
> * libraries/libaaio
> * system/dieharder
> * office/keepassx
>
> If someone else could take over maintainership for these packages,
> I'd be grateful.
>
> Unlike the other three, ChezScheme is still actively maintained by
> its developers.  Whoever takes this over should run the full test
> battery on both threaded and unthreaded builds after each update to
> check for regressions.
>
> Thank you!
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] A few scripts up for grab.

[Greg' Ar Tourter]

I can take yakuake if that's ok.

we can't update yet to 3.x version as this is a qt5/plasma version but
I have a version ready for that when we do move to it.

Cheers

Greg


On Fri, 28 Sep 2018 at 17:40, Arnaud  wrote:
>
> Hello,
>
> Following the previous messages about warzone2100, I contacted both
> Matthew and David Fillpot. Matthew answered for them both, and agrees to put 
> all
> of their scripts up for grabs, I quote :
> > Yes, please notify the mailing list that the scripts for both maintainers
> > are up for grabs.
> Though he is also ok to resume his work as maintainer, in about a
> month, for anything that remains. It seems he has a bit more time at the 
> moment.
> So those scripts doesn't require a new maintainer, but if you want to
> take care of them, they are available !
>
> Most of their scripts are for abandonwares, here they are, classified by
> maintenance level :
>  * Nothing to do, mostly abandoned projects
> academic/mathomatic : up-to-date, last upstream update 2012/10/30
> desktop/kcometen4   : up-to-date, last upstream update 2010/07/30
> system/freefont : up-to-date, last upstream update 2012/05/03
> games/lightyears: up-to-date, last upstream update 2011/09/27
> games/tuxkart   : up-to-date, last upstream update unknown but >5 years 
> old
> libraries/GLee  : up-to-date, last upstream update unknown but >5 years 
> old
> libraries/quesoglc  : up-to-date, last upstream update 2013/08/23
>  * active projects but SBo package is 5 years old
> academic/gpredict : SBo version 1.3,   upstream version 2.2.1
> network/axel  : Sbo version 2.4,   upstream version 2.16.1
> graphics/qrencode : Sbo version 3.4.0, upstream version 4.0.2
> games/pysolfc : SBo version 2.0,   upstream version 2.4.0
> system/yakuake: SBo version 2.9.9, upstream version 3.0.5
>
> And I'm ok taking ownership of warzone2100, having already done the
> update work on it.
>
> --
> Arnaud 
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Skypeforlinux not compiling

[Greg' Ar Tourter]

I have been updating it on my side, regularly. A word of warning
though, the new version that was released today (8.30.0.50) fails to
run on my machines with a dbus error (runs fine as root). I have
reverted to 8.29.0.50 which works fine for me.

Hope this helps

Greg
On Wed, 12 Sep 2018 at 16:11, Daniel Prosser  wrote:
>
> Looks like they removed the 8.18.0.6 release from that site, but there are a
> bunch of newer ones available.
>
> https://repo.skype.com/deb/pool/main/s/skypeforlinux/
>
> On Wednesday, September 12, 2018 05:08:09 PM Jostein Berntsen wrote:
> > I get this error:
> >
> > Processing skypeforlinux
> >
> > skypeforlinux:
> > skypeforlinux not found in /var/cache/sbopkg.
> > --2018-09-12 17:01:00--
> > https://repo.skype.com/deb/pool/main/s/skypeforlinux/skypeforlinux_8.18.0.6_
> > amd64.deb Slår opp vertsnavn repo.skype.com … 23.52.33.92,
> > 2a02:26f0:e2:48d::1263, 2a02:26f0:e2:48a::1263
> > Kobler til repo.skype.com|23.52.33.92|:443 …tilkoblet.
> > HTTP-forespørsel sendt. Venter på svar … 404 Not Found
> > 2018-09-12 17:01:01 PROGRAMFEIL 404: Not Found.
> > RY LOG
> > Using the SBo repository for Slackware 14.2
> > Queue Process:  Download, build, and install
> >
> > skypeforlinux:
> >   Download failed.
> >
> > Error occurred with build.  Please check the log.
> >
> >
> > skypeforlinux:
> > Would you like to continue processing the rest of the
> > queue or would you like to abort?  If this failed
> > package is a dependency of another package in the queue
> > then it may not make sense to continue.
> >
> > (Y)es to continue, (N)o to abort, (R)etry the build?: y
> >
> >
> >
> > Mvh,
> > Jostein Berntsen
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] PHP 7.x

[Greg' Ar Tourter]

Well I guess that one of the reason for php7 not being in sbo is that
since it is now in -current, it would be a bit of a wasted effort to
create one now only to have it removed when slackware-15 gets
released.

I don't think it would get rejected though.

Greg
On Tue, 28 Aug 2018 at 14:55, Eugen Wissner  wrote:
>
> Hi,
>
> I don't see any reason why it wouldn't be. Name it php7 or php72 and
> don't override any files from php5. I already have one and it is
> already used on a production server. It should be only cleaned up a
> bit. I can send it you if you'd like.
>
> Regards
> Eugene
>
> Am Dienstag, den 28.08.2018, 15:37 +0200 schrieb Thomas Szteliga:
> > Hello,
> >
> > is there any reason why PHP 7.x (7.0, 7.1, 7.2, 7.3) is not available
> > on Slackbuilds.org? I know about:
> >
> > 
> > As a general rule, we do not accept SlackBuild scripts of software
> > that is
> > included as part of Slackware; however, exceptions may be made by the
> > admin
> > staff on a case-by-case basis.
> > 
> > 
> >
> >
> > There is 
> > with Python 2.7 in the official repo.
> >
> > Would a PHP 7.x slackbuild be accepted by the admin staff?
> >
> >
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Serious regression on Github archive URLs

[Greg' Ar Tourter]

Thanks for the heads up David and nice find Benjamin.

Not ideal as it requires users to actually have a github account but
still gets people back and running until github stop being idiots.

I have added the token to sbopkg.conf instead as at least it will only
be used when using sbopkg rather than every time I use
wget.

Cheers

Greg

On Sat, 18 Aug 2018 at 17:12, Benjamin Trigona-Harany
 wrote:
>
> Here is what I believe to be a reasonably safe way of getting wget to work
> again as long as you have a GitHub account:
>
> 1. In GitHub's settings, find "Developer Settings"
> 2. Click "Personal access tokens"
> 3. Click "Generate new token"
> 4. Select "public_repo" (nothing else!)
> 5. Click "Generate token"
> 6. Add the following line to .wgetrc (replacing TOKEN with the token you just
> generated
> header=Authorization: token TOKEN
>
> As far as I can tell, the drawback is that you are exposing your GitHub token
> to every server wget interacts with, but (1) there is no indication that it's
> a GitHub token and (2) the only permission the token has is to interact with
> public repositories.
>
> "public_repo: Grants read/write access to code, commit statuses,
> collaborators, and deployment statuses for public repositories and
> organizations. Also required for starring public repositories."
>
> If this works for your user account and you are comfortable with the paragraph
> above, you can then add the line to /etc/wgetrc and normal service will be
> resumed.
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] apparently abandoned packages.

[Greg' Ar Tourter]

Just to update, since B.Watson took over the maintenance of id3tool in this
morning's release, I have taken over and submitted an update for pdfpc

Cheers

Greg

On Tue, 31 Jul 2018 at 04:05, Erik Falor  wrote:

> On Sun, Jul 29, 2018 at 01:11:12PM +0100, Greg' Ar Tourter wrote:
> > Just following up on this, Erik, did you get anything back from Markus? I
> > haven't.
>
> No, I have not gotten any word from Markus about development/racket.
>
> --
> Erik Falor
> Registered Linux User #445632http://unnovative.net
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] apparently abandoned packages.

[Greg' Ar Tourter]

Just following up on this, Erik, did you get anything back from Markus? I
haven't.

Admins, can we consider these packages up for grabs?

Cheers

Greg

On Sat, 21 Jul 2018 at 19:05, Erik Falor  wrote:

> On Fri, Jul 20, 2018 at 03:22:55PM +0100, Greg' Ar Tourter wrote:
> > Hi admins,
> >
> > I have been using the pdfpc package regularly and notice it was out of
> date
> > a while back as development had moved to a new team.
> >
> > About a year and a half ago I emailed the slackbuild maintainer who
> > responded that he would update the package but never did. I emailed it
> back
> > a couple of weeks ago, but haven't got anything back from him.
>
> I had emailed him a patch for the latest Racket SlackBuild just this
> week, but haven't yet gotten a reply.
>
> If it is determined that these packages are orphaned, I am willing to
> take care of these:
>
> > development/racket
> > development/newlisp
>
>
> --
> Erik Falor
> Registered Linux User #445632http://unnovative.net
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] apparently abandoned packages.

[Greg' Ar Tourter]

Hi admins,

I have been using the pdfpc package regularly and notice it was out of date
a while back as development had moved to a new team.

About a year and a half ago I emailed the slackbuild maintainer who
responded that he would update the package but never did. I emailed it back
a couple of weeks ago, but haven't got anything back from him.

I also noticed that he has not been active on slackbuild for a while now.

Can I consider it abandoned and take it over? I have been updating the
package for my own use and kept it up-to-date locally so I can easily
submit the latest version.

For information his packages are:
network/gns3
libraries/lablgtk
libraries/ocaml-ounit
libraries/ocaml-findlib
development/ocaml
development/racket
development/ecl
development/newlisp
audio/id3tool
office/pdfpc
system/quotatool
system/dynamips
desktop/disper
desktop/stalonetray

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Greg' Ar Tourter]

And yeah I looked at the slackbuild after I sent my original email and
noticed the 2 header files. I had not realised there were there.

On 13 June 2018 at 16:26, Greg' Ar Tourter  wrote:

> That repo is also on the takedown list!
>
> On 13 June 2018 at 16:22, Matteo Bernardini 
> wrote:
>
>> 2018-06-13 17:11 GMT+02:00 Greg' Ar Tourter :
>> > I just  received a dmca takedown notice for my slackbuild repo copy on
>> > github (I looking at the document, I am not the only one from this
>> > community).
>> >
>> > It seems that steinberg is claiming jack-tools and anything related to
>> it is
>> > affected.
>> >
>> > Should we respond as a group or as individual? In this case there
>> definitely
>> > nothing in the slackbuild that belongs to steinberg but I am not a
>> lawyer...
>> >
>> > Any thoughts?
>> >
>> > Greg
>>
>> maybe the SlackBuild can just be modified to use the Steinberg headers
>> from
>>
>> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/V
>> ST/pluginterfaces/vst2.x/aeffect.h
>> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/V
>> ST/pluginterfaces/vst2.x/aeffectx.h
>>
>> as additional DOWNLOADs in the jack-tools.info file.
>>
>> Matteo
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Greg' Ar Tourter]

That repo is also on the takedown list!

On 13 June 2018 at 16:22, Matteo Bernardini 
wrote:

> 2018-06-13 17:11 GMT+02:00 Greg' Ar Tourter :
> > I just  received a dmca takedown notice for my slackbuild repo copy on
> > github (I looking at the document, I am not the only one from this
> > community).
> >
> > It seems that steinberg is claiming jack-tools and anything related to
> it is
> > affected.
> >
> > Should we respond as a group or as individual? In this case there
> definitely
> > nothing in the slackbuild that belongs to steinberg but I am not a
> lawyer...
> >
> > Any thoughts?
> >
> > Greg
>
> maybe the SlackBuild can just be modified to use the Steinberg headers from
>
> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/
> VST/pluginterfaces/vst2.x/aeffect.h
> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/
> VST/pluginterfaces/vst2.x/aeffectx.h
>
> as additional DOWNLOADs in the jack-tools.info file.
>
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] dmca takedown notice?!

[Greg' Ar Tourter]

I just  received a dmca takedown notice for my slackbuild repo copy on
github (I looking at the document, I am not the only one from this
community).

It seems that steinberg is claiming jack-tools and anything related to it
is affected.

Should we respond as a group or as individual? In this case there
definitely nothing in the slackbuild that belongs to steinberg but I am not
a lawyer...

Any thoughts?

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20180519.1 (geoclue2)

[Greg' Ar Tourter]

I can reproduce the problem on 14.2

I think the confusion is that mm-glib and glibmm are 2 different things.
mm-glib is from modem-manager, whereas glibmm is the C++ API for GLIB
(which geoclue2 is not using).

One can disable the modem-manager dependency and make it compile fine on
14.2 by add the configure flags:
--disable-modem-gps-source --disable-3g-source --disable-cdma-source

Hope this helps

Greg

On 19 May 2018 at 12:47, David Woodfall  wrote:

> On Saturday 19 May 2018 21:23,
> Christoph Willing  put forth the proposition:
> > On 19/05/18 19:31, David Woodfall wrote:
> > > On Saturday 19 May 2018 18:25,
> > > Christoph Willing  put forth the
> proposition:
> > >> On 19/05/18 10:33, David Spencer wrote:
> > >>> Hi everybody,
> > >>>
> > >>> Here's this week's public update. Thanks to all our contributors!
> > >>>
> > >>> Please note that there is a small problem with the .info file for
> > >>> prosody, we'll fix this in another update very soon.
> > >>>
> > >> [snip]
> > >>> system/geoclue2: Updated for version 2.4.10.
> > >>
> > >> I'm having a build problem with this update (previous version was
> fine)
> > >> in a clean x86_64 14.2 VM:
> > >>
> > >> checking for GTKDOC_DEPS... yes
> > >> checking for GEOCLUE... yes
> > >> checking for gobject-introspection... yes
> > >> checking for LIBGEOCLUE... yes
> > >> checking for ModemManager... no
> > >> configure: error: Package requirements (mm-glib >= 1.6) were not met:
> > >>
> > >> Requested 'mm-glib >= 1.6' but version of mm-glib is 1.4.14
> > >>
> > >> I have /var/log/packages/ModemManager-1.4.14-x86_64-1 installed
> which is
> > >> the latest for 14.2 according to the ChangeLog.txt. I see that
> -current
> > >> has ModemManager-1.6.12-x86_64-2.txz so it looks like this particular
> > >> geoclue2 update is meant for -current, not -stable.
> > >>
> > >> Any other ideas?
> > >>
> > >> chris
> > >
> > > Which version of glibmm do you have?
> > >
> > > glibmm-2.46.4 here.
> > >
> >
> > Yes, glibmm-2.46.4-x86_64-1 here too.
> >
> > However I think the mm-glib reported in the error message refers to when
> > the the geoclue2 configuration is checking the
> > /usr/lib64/pkgconfig/mm-glib.pc file (part of the ModemManager package).
> >
> > chris
>
> Yeah the configure checks that. What do
>
> pkg-config --print-errors --exists mm-glib
> pkg-config --print-errors --exists ModemManager
>
> output?
>
> --
>
> Please don't reply directly to me or CC me.
>
> > You know you are "there" when you are known by your first name, and
> > are recognized.
> > Lemmie see, there is Madonna, and Linus, and . help me out here!
> Bill ? ;-)
>   -- From some postings on comp.os.linux.misc
>
> .--.  oo
>()//
> ~'
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20180504.1

[Greg' Ar Tourter]

The info file for android-studio seems to be using some unicode characters
instead of /

https:⁄⁄dl.google.com
⁄dl⁄android⁄studio⁄ide-zips⁄3.1.2.0⁄android-studio-ide-173.4720617-linux.zip

it should be

https://dl.google.com/dl/android/studio/ide-zips/3.1.2.0/android-studio-ide-173.4720617-linux.zip

Cheers

Greg

On 5 May 2018 at 01:00, Willy Sudiarto Raharjo 
wrote:

> Hi
>
> Welcome to first update in May.
>
> Wireshark is now bumped to 2.6.0 and this branch (2.6.x) will be the
> last version that supports GTK+-based UI. Next major version will
> completely removed it and it's only Qt5-based.
>
> As for maintainers, we remind you to always take our latest version of
> SlackBuild from our website or repository before pushing an update as we
> (admins) might have made some changes to your submission. Failing to do
> so might results in a rejection of the submission and then it will have
> to be resubmitted and wait in the pending queue again.
>
> For new scripts, also please make sure to use the latest template files
> available here https://slackbuilds.org/templates/. Do not use an old
> copy from your other scripts.
>
> Enjoy your weekend :)
>
>
> Fri May  4 23:47:20 UTC 2018
> academic/QtiPlot: Updated homepage.
> academic/R: Updated for version 3.5.0.
> academic/biblesync: Updated for version 2.0.1.
> academic/sundials: Updated for version 3.1.0.
> audio/atunes: Fixed download.
> audio/audioconvert: Added (Audio Sync and Conversion Utility).
> audio/fst: Update homepage.
> audio/qmmp-plugin-pack-qt5: Added (additional plugins for Qmmp).
> audio/qmmp-qt5: Added (QT based multimedia player).
> desktop/Zafiro-icons: Added (icon pack flat with light colors).
> desktop/adapta-gtk-theme: Added (Gtk+ theme).
> desktop/bunsen-themes: Updated for version 9.4.1.
> desktop/mh5000: Fixed md5sum.
> desktop/openbox-themes-extra: Added (additional themes for Openbox).
> desktop/oranchelo-icon-theme: Updated for version 0.7.6.8.1.
> development/android-studio: Updated for version 3.1.2.0_173_4720617.
> development/d-tools: Updated for version 2.080.0
> development/dmd: Updated for version 2.080.0
> development/git-cola: Updated for version 3.1.
> development/google-go-lang: Updated for version 1.10.2.
> development/ht: Added (file viewer, analyzer for files).
> development/icecream: Fixed download.
> development/jupyter-nbdime: Update REQUIRES.
> development/kotlin: Updated for version 1.2.41.
> development/love: Updated for version 11.1.
> development/mcrl2: Updated homepage and download.
> development/meld3: Updated for version 3.18.1.
> development/mrustc: Updated for git173dfa9.
> development/qbs: Updated for version 1.11.1.
> development/qt-creator-llvm: Updated with new patches from upstream.
> development/qt-creator: Updated for version 4.6.1.
> development/rmlmmc: Update homepage.
> development/scala: Updated homepage.
> development/tanya: Updated for version 0.8.1
> development/tiled: Updated for version 1.1.5.
> development/universal-ctags: Updated for version 576c750
> games/RetroArch: Updated for version 1.7.3.
> games/flare-game: Updated for version 1.05.
> games/flare: Updated for version 1.05.
> gis/OTB: Script improvements.
> gis/osm2pgsql: Updated for version 0.96.0.
> gis/ossim: Updated for version 2.3.2.
> graphics/FreeCAD: Updated for version 0.17.
> graphics/openimageio: Updated for version 1.8.11
> graphics/qelectrotech: Updated for version 0.6.
> libraries/CGAL: Updated for version 4.12.
> libraries/exiftool: Updated for version 10.80.
> libraries/futures: Updated for version 3.2.0.
> libraries/jai-imageio: Updated homepage and dowload.
> libraries/jai: Updated homepage and download.
> libraries/leptonica: Updated for version 1.76.0.
> libraries/libetonyek: Updated for version 0.1.8.
> libraries/libhoard: Fixed download.
> libraries/libinput: Updated for version 1.10.6.
> libraries/libmwaw: Updated for version 0.3.14.
> libraries/libstaroffice: Updated for version 0.0.6.
> libraries/libwps: Updated for version 0.4.9.
> libraries/opencv: Patched to suit ffmpeg
> misc/grc: Updated for version 1.11.3.
> misc/mosquitto: Updated for version 1.5
> misc/sgrep: Added (sorted grep).
> multimedia/devedeng: Updated for version 4.10.0.
> network/basilisk-src: Updated for version 2018.04.23.
> network/opera-legacy: Updated homepage and download.
> network/sflowtool: Fixed md5sum.
> network/signal-desktop: Updated for version 1.9.0.
> network/vnstat: Updated homepage and download.
> network/wireshark: Updated for version 2.6.0.
> office/gnucash-docs: added PDF and EPUB to build options.
> office/gnucash3-docs: Updated for version 3.1.
> office/gnucash3: Updated for version 3.1.
> office/gnucash: Change option to WITHPYTHON.
> office/mobiperl: Update homepage and download.
> office/notmuch: Updated for version 0.26.2.
> perl/perl-ExtUtils-ModuleMaker: Updated for version 0.57.
> python/gunicorn: Updated for version 19.8.0.
> python/python-neovim: Updated for version 0.2.6.
> python/thonny: Updated for version

Re: [Slackbuilds-users] Rstudio

[Greg' Ar Tourter]

The new version require qt5 btw. I have manage to make it work recently if
that is of interest

Greg

On 8 March 2018 at 11:28, Ekin Akoglu  wrote:

> Sure, I will work on it, but it will take a little while though.
>
> Best,
>
> Ekin
>
>
>
> On 08/03/18 14:11, Matteo Bernardini wrote:
>
>> 2018-03-08 11:26 GMT+01:00 Ekin Akoglu :
>>
>>> I would like to take it, if no one else has already grabbed it.
>>>
>>> On 08/03/18 11:56, Matteo Bernardini wrote:
>>>
 P.S. rstudio-desktop is up for grabs for whoever wants to maintain it.

>>> it's yours: it isn't updated since four years so I think an up-to-date
>> version will be welcomed!
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] pdftk on Slackware Current

[Greg' Ar Tourter]

Hi Konrad,

Thanks for that. I have had the same setup ready for a while now, basically
since Eric released his gcc-5 package. I have been reluctant to actually
release it due to its reliance on a package that is neither available on
slackbuilds.org nor officially part of slackware.

I was in a way waiting to see if the gcc-legacy package here would start
build gcj as part of it. but since sbo doesn't officially support -current,
it was not at the top of my todo list to chase things up. Your email shows
that there is demand so maybe I should start thinking about the best way to
proceed.

SBo admins, what is the policy about requiring a package not available on
slackware or slackbuild?

Cheers

Greg

On 4 March 2018 at 15:03, Konrad J Hambrick  wrote:

>
> Dang !
>
> I said:   I documented what I had to do after to build pdftk installing
> Alien Bob's gcc5.SlackBuild on Slackware64-current in this thread on LQ:
>
> I meant:  I documented what I had to do to build pdftk after installing
> Alien Bob's gcc5.SlackBuild on Slackware64-current in this thread on LQ:
>
> Sorry ... I REALLY need a 'preview' feature :)
>
> -- kjh
>
> On Sun, Mar 4, 2018 at 9:00 AM, Konrad J Hambrick 
> wrote:
>
>> ArTourter --
>>
>> I documented what I had to do after to build pdftk installing Alien Bob's
>> gcc5.SlackBuild on Slackware64-current in this thread on LQ:
>>
>> https://www.linuxquestions.org/questions/slackware-14/buildi
>> ng-pdftk-on-slackware-15-0-current-4175624922/
>>
>> These three patch files modify the SlackBuild Files:
>>
>>-rw-r--r-- 1 root root  497 Mar  4 07:39 /home/tmp/README-Slackware-15.
>> 0.patch.txt
>>-rw-r--r-- 1 root root  694 Mar  4 07:40 /home/tmp/pdftk.SlackBuild-Sla
>> ckware-15.0.patch.txt
>>-rw-r--r-- 1 root root  300 Mar  4 07:40 /home/tmp/pdftk.info-Slackware
>> -15.0.patch.txt
>>
>> This patch file replaces the existing pdftk-1.44-add_custom_optflags.patch
>> for Slackware -current + gcc5 in the SlackBuild Directory:
>>
>>-rw-r--r-- 1 root root  665 Mar  4 07:40 /home/tmp/pdftk-2.02-on-Slackw
>> are-15.patch.txt
>>
>> I imagine there is a better way than my kludgy SLACKVER=15 Variable to
>> differentiate Slackware 15.0 from Slackware 14.2 in the pdftk.SlackBuild.
>>
>> The only real change was to force GXX=gcc-5 in the
>> pdftk/Makefile.Slackware-13.1 Makefile ...
>>
>> Thanks for the pdftk.SlackBuild ArTourter -- it is an essential tool
>> where I work !
>>
>> -- kjh
>>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20180303.1

[Greg' Ar Tourter]

Hi,

keepassxc md5sum mismatch on the lastest release:

  MD5SUM check for keepassxc-2.3.0-src.tar.xz ... FAILED!
Expected: 1dba769f0eb1303ef3fbd873acd81901
Found:127490ae7e4b3f49426619ec6f902bb6

Cheers

Greg

On 3 March 2018 at 09:39, Philip van der Hoeven  wrote:

> On 2018-03-03 03:15, Willy Sudiarto Raharjo wrote:
>
> Maintainers, please see https://pastebin.com/pbFdSAyW
>> If your name came up, please take some time to fix the URLs.
>> If you can't find alternative link, you can use sbosrcharch
>> (http://slackware.uk/sbosrcarch/).
>> Please note that some of those entries have been fixed in this batch,
>> while others might have false positive alerts
>> hkjgdf
>>
>
> Hi,
>
> The btsync can be removed as far as I am concerned.
> Since they went commercial I don't think anybody uses this anymore since
> open source alternatives exist, such as syncthing.
>
> Philip
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] possible submission

[Greg' Ar Tourter]

Actually, the removal of gcc-java will be a problem for one of the package
I maintain (pdftk). I wonder if the gcc-legacy project would consider
picking it up as well.

Cheers

Greg

On 22 June 2017 at 23:56, B Watson  wrote:

> Would anyone object to my submitting an openjdk-bin build? Basically
> just a prebuilt binary repack of the same version of openjdk that's
> currently in the openjdk build.
>
> I think this would be useful because come next Slackware release, gcc-java
> will be gone (gcc upstream dropped it). Which means we're back to the
> old "open source openjdk depends on Oracle proprietary jdk" issue that
> we resolved a few months back. I (and probably others) would rather be
> able to bootstrap openjdk without having to deal with Oracle.
>
> Thoughts, opinions, better ideas?
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] redshift and geoclue2

[Greg' Ar Tourter]

Hi,

I have an updated package ready but i have been busy. Will submit it for
next release.

Cheers

Greg

On 18 Jun 2017 12:15, "Aaditya Bagga"  wrote:

> Hi guys,
>
> Could an SBo admin update the redshift SlackBuild? I tried emailing the
> current maintainer but could not get a response.
>
> Currently it checks for geoclue and disables geoclue2 support (needed for
> automatic location detection), while the correct behaviour is to check for
> geoclue-2.0 and then disable geoclue2 support.
>
> I have attached a patch.
>
> geoclue2 (added recently) can also be listed as an optional dependency in
> the README.
>
> Thx,
> Aaditya
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20170603.1

[Greg' Ar Tourter]

> system/apcupsd: fixup a restart issue + minor tweaks

The patches are not included in the slackbuild so this fails to build.

we are missing two files:

create_lockdir_in_init_script.diff and nitpicky-fixes-to-init-script.diff

any chances of getting them added to the repo?

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] redshift package in accepted

[Greg' Ar Tourter]

Could an admin remove the redshift slackbuild from accepted, I want to
submit a corrected version.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] redshift

[Greg' Ar Tourter]

Since this looks to have been abandoned, Anyone want to take this on?
Otherwise I am happy to grab it and submit an update.

Cheers

Greg

On 19 March 2017 at 17:02, Gwenhael Le Moine 
wrote:

> I've the slackbuild to build 1.11
> I just needed some small adjustments (maybe $DOC files, it was a long time
> ago)
>
> 2017-03-19 17:51 GMT+01:00 Willy Sudiarto Raharjo  >:
> >> I see that redshift in slackbuilds is at 1.8, and there it is now up
> >> to 1.11.
> >>
> >> Is there an issue, or is it just that it hasn't been updated?
> >
> > Last update on redshift was 3 years ago
> > https://slackbuilds.org/cgit/slackbuilds/commit/?id=
> 35c78b1eedc054b9d5678de099fea9056675f0ea
> >
> >
> > --
> > Willy Sudiarto Raharjo
> >
> >
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> >
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] libspectrum

[Greg' Ar Tourter]

You seem to be building this on a multilib system. You might want to have a
look at the FAQ and see if it fixes your problem:
https://slackbuilds.org/faq/#multilib

Greg

On 1 May 2017 at 19:35, Dimitris Zlatanidis  wrote:

> I have issue to build libspectrum 1.3.3 version, any help?
>
>
> rings -MT zip.lo -MD -MP -MF .deps/zip.Tpo -c zip.c -o zip.o >/dev/null
> 2>&1
> depbase=`echo zlib.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
> /bin/sh ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include  -I/usr/include
> -DLIBSPECTRUM_EXPORTS -O2 -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD
> -MP -MF $depbase.Tpo -c -o zlib.lo zlib.c &&\
> mv -f $depbase.Tpo $depbase.Plo
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2
> -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c
> zlib.c  -fPIC -DPIC -o .libs/zlib.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2
> -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c
> zlib.c -o zlib.o >/dev/null 2>&1
> /bin/sh ./libtool  --tag=CC   --mode=link gcc -DLIBSPECTRUM_EXPORTS -O2
> -fPIC -Wall -Wwrite-strings -version-info 12:6:4 -no-undefined
> -L/usr/lib -o libspectrum.la -rpath /usr/lib64 bzip2.lo creator.lo
> crypto.lo csw.lo dck.lo ide.lo libspectrum.lo memory.lo microdrive.lo
> plusd.lo pzx_read.lo rzx.lo sna.lo snp.lo snapshot.lo snap_accessors.lo
> sp.lo symbol_table.lo szx.lo tap.lo tape.lo tape_accessors.lo
> tape_block.lo tape_set.lo timings.lo tzx_read.lo tzx_write.lo
> utilities.lo warajevo_read.lo wav.lo z80.lo z80em.lo zxs.lo zip.lo
> zlib.lo   -laudiofile -lglib-2.0 -lm -lbz2 -lz  -lgcrypt
> libtool: link: warning: `/usr/lib/libstdc++.la' seems to be moved
> libtool: link: gcc -shared  -fPIC -DPIC  .libs/bzip2.o .libs/creator.o
> .libs/crypto.o .libs/csw.o .libs/dck.o .libs/ide.o .libs/libspectrum.o
> .libs/memory.o .libs/microdrive.o .libs/plusd.o .libs/pzx_read.o
> .libs/rzx.o .libs/sna.o .libs/snp.o .libs/snapshot.o
> .libs/snap_accessors.o .libs/sp.o .libs/symbol_table.o .libs/szx.o
> .libs/tap.o .libs/tape.o .libs/tape_accessors.o .libs/tape_block.o
> .libs/tape_set.o .libs/timings.o .libs/tzx_read.o .libs/tzx_write.o
> .libs/utilities.o .libs/warajevo_read.o .libs/wav.o .libs/z80.o
> .libs/z80em.o .libs/zxs.o .libs/zip.o .libs/zlib.o   -Wl,-rpath
> -Wl,/usr/lib64/../lib -Wl,-rpath -Wl,/usr/lib64/../lib -L/usr/lib
> /usr/lib/libaudiofile.so /usr/lib/libFLAC.so /usr/lib/libogg.so
> /usr/lib64/../lib/libstdc++.so /usr/lib/libglib-2.0.so -lpthread -lm
> -lbz2 -lz /usr/lib/libgcrypt.so /usr/lib/libgpg-error.so  -O2
> -Wl,-soname -Wl,libspectrum.so.8 -o .libs/libspectrum.so.8.4.6
> /usr/lib/libaudiofile.so: error adding symbols: File in wrong format
> collect2: error: ld returned 1 exit status
> Makefile:554: recipe for target 'libspectrum.la' failed
> make[1]: *** [libspectrum.la] Error 1
> make[1]: Leaving directory '/tmp/SBo/libspectrum-1.3.3'
> Makefile:447: recipe for target 'all' failed
> make: *** [all] Error 2
>
> --
> Dimitris Zlatanidis
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Only 68 builds left!

[Greg' Ar Tourter]

I have found where the source is now being hosted (github) and I have
updated the slackbuild. I can submit it to the website, otherwise you can
grab is from github if it is faster:
https://github.com/ArTourter/Slackbuilds.org/commit/031d273be0c663a91a1d04b0ab8a3b3f9807eb0b

Cheers

Greg

On 24 March 2017 at 22:37, Greg' Ar Tourter  wrote:

> That might be a short take over as for the moment both the site and the
> download links are offline.
>
> will keep investigating...
>
> Greg
>
> On 24 March 2017 at 21:25, Ryan P.C. McQuen 
> wrote:
>
>>
>>
>>
>>  On Fri, 24 Mar 2017 13:51:45 -0700 *Greg' Ar Tourter
>> >* wrote 
>>
>>
>>
>> On 24 March 2017 at 19:09, Ryan P.C. McQuen 
>> wrote:
>>
>>
>> Hello again!
>>
>> B. Watson was nice enough to compile this list of my builds that are
>> remaining with their subsequent READMEs and dependencies (REQUIRES):
>>
>> http://urchlay.naptime.net/~urchlay/src/ryanbuilds.txt
>>
>> Thank you already for taking over more than 100 of my builds! Whatever is
>> left after the next public update, I will change to orphaned.
>>
>> Thanks for all your work Ryan.
>>
>> I'll take CellWriter if noone wants it.
>>
>>
>>
>>
>>
>> It's yours!
>>
>> -Ryan
>> [ryanpcmcquen.org]
>>
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Only 68 builds left!

[Greg' Ar Tourter]

That might be a short take over as for the moment both the site and the
download links are offline.

will keep investigating...

Greg

On 24 March 2017 at 21:25, Ryan P.C. McQuen 
wrote:

>
>
>
>  On Fri, 24 Mar 2017 13:51:45 -0700 *Greg' Ar Tourter
> >* wrote 
>
>
>
> On 24 March 2017 at 19:09, Ryan P.C. McQuen 
> wrote:
>
>
> Hello again!
>
> B. Watson was nice enough to compile this list of my builds that are
> remaining with their subsequent READMEs and dependencies (REQUIRES):
>
> http://urchlay.naptime.net/~urchlay/src/ryanbuilds.txt
>
> Thank you already for taking over more than 100 of my builds! Whatever is
> left after the next public update, I will change to orphaned.
>
> Thanks for all your work Ryan.
>
> I'll take CellWriter if noone wants it.
>
>
>
>
>
> It's yours!
>
> -Ryan
> [ryanpcmcquen.org]
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Only 68 builds left!

[Greg' Ar Tourter]

On 24 March 2017 at 19:09, Ryan P.C. McQuen 
wrote:

> Hello again!
>
> B. Watson was nice enough to compile this list of my builds that are
> remaining with their subsequent READMEs and dependencies (REQUIRES):
>
> http://urchlay.naptime.net/~urchlay/src/ryanbuilds.txt
>
> Thank you already for taking over more than 100 of my builds! Whatever is
> left after the next public update, I will change to orphaned.
>
Thanks for all your work Ryan.

I'll take CellWriter if noone wants it.

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] acroread for 64-bit machines?

[Greg' Ar Tourter]

As the maintainer of the adobe reader package, the answer to the question
of whether you need the 32bit compatibility libs to run adobe reader on
64bit slackware is yes, and I may add "unfortunately".

Now to the rest of the conversation, I always come back to adobe reader for
viewing documents but it is true that the linux version is now very old and
lacks the features its mac and windows version now have. Unfortunately, I
very much doubt we will ever see an updated version from Adobe (although
they have released a synchronised version of flash after saying they would
never do so there is still hope, albeit a very very small glimmer of it).

For presentations, I have started using pdfpc (also available on SBo, but
an old version. I have emailed the maintainer of the package a patch to a
newer one a while back and he assured me he would have a look... I probably
should probe again). pdfpc offers notes, presenter console, highlighter,
pointer

Hope this helps

Cheers

Greg

On 14 February 2017 at 16:13, Rich Shepard  wrote:

>   My use of Adobe's acrobat reader is infrequent, but good for
> presentations
> showing beamer-class slides. There was no problem that I recall using it
> with 14.1, but I'm having issues trying to get a version that works with
> 14.2.
>
>   I have a presentation tomorrow and neither xpdf nor mupdf will display
> the
> LaTeX/beamer slides full screen. The windows are full screen, but not the
> PDF file.
>
>   Do I need the 32-bit compatibility libraries to run acroread? What are
> other folks using?
>
> Rich
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] BUG: pdftk decrypt doesn't work

[Greg' Ar Tourter]

unfortunately, pdftk cannot be compiled using openjdk or oracle java
jdk as far as I know and requires gcj.

I usually have a machine on current but not at the moment so I cannot
test on current.

Greg


On 20 December 2016 at 23:50, B Watson  wrote:
>> Error: Unexpected Exception in open_reader()
>> Unhandled Java Exception in main():
>> java.lang.NullPointerException
>>at gnu.gcj.runtime.NameFinder.lookup(libgcj.so.16)
>>at java.lang.Throwable.getStackTrace(libgcj.so.16)
>>at java.lang.Throwable.stackTraceString(libgcj.so.16)
>>at java.lang.Throwable.printStackTrace(libgcj.so.16)
>>at java.lang.Throwable.printStackTrace(libgcj.so.16)
>
> I ran across a similar situation with java code that uses crypto. When
> built with gcj, crypto wasn't supported. When built with openjdk or
> oracle jdk, it worked fine.
>
> Worth trying, at least.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] BUG: pdftk decrypt doesn't work

[Greg' Ar Tourter]

Hi Eduardo,

I have tried on a pdf that I encrypted using pdftk first using the
default 128bit encryption, and decryption went without errors. do you
know what was used to encrypt your pdf in the first place and with
what settings?

Another thing that comes to mind is was pdftk compiled on current or
stable (before you upgraded to current) if the latter, you might want
to recompile it to see if the problem still occurs

Hope this helps

Greg

On 20 December 2016 at 15:00, Eduardo Sanchez  wrote:
> This was observed in Slackware64-current but it could well be the case
> with Slackware-14.2.
>
> Using the latest pdftk from SBo, an attempt to decrypt a PDF fails:
>
> Command Line:
>
> $ pdftk secured.pdf input_pw mypasswd output \
> unsecured.pdf
>
> Output:
>
> Error: Unexpected Exception in open_reader()
> Unhandled Java Exception in main():
> java.lang.NullPointerException
>at gnu.gcj.runtime.NameFinder.lookup(libgcj.so.16)
>at java.lang.Throwable.getStackTrace(libgcj.so.16)
>at java.lang.Throwable.stackTraceString(libgcj.so.16)
>at java.lang.Throwable.printStackTrace(libgcj.so.16)
>at java.lang.Throwable.printStackTrace(libgcj.so.16)
>
>
> Thankfully I was able to decrypt the PDF afterwards using Slackware's
> stock qpdf, but I nevertheless wanted to report this in case you guys
> could find a workaround.
>
> Regards,
>
>
> Eduardo
>
> --
> Eduardo Sánchez Gauto, Abog., Th.M.
> Abogado - Traductor Público Matriculado Inglés - Español
> Web: http://sombragris.org - Blog: http://shadow.sombragris.org
> TW: @thegreyshadow - FB: /thegreyshadow
> Teléfono: (0991) 755-355 - Asunción, Paraguay
> ==
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2

[Greg' Ar Tourter]

sorry I mean *without* issues...
should really check before pressing send!

Greg

On 29 August 2016 at 18:00, Serban Udrea <
serban.ud...@skmail.ikp.physik.tu-darmstadt.de> wrote:

> On 08/29/2016 06:47 PM, Greg' Ar Tourter wrote:
>
>> Well I have just build both of these an hour ago through sbopkg with
>> issues. So it
>> might be a build tools problem rather than a error in the sbo package.
>> ...
>>
>
> Hello,
>
> Could you please let me know what issues did you encounter.
>
> Best regards,
>
> Serban Udrea
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2

[Greg' Ar Tourter]

Well I have just build both of these an hour ago through sbopkg with
issues. So it might be a build tools problem rather than a error in the sbo
package.

Cheers

Greg

On 29 August 2016 at 16:29, Willy Sudiarto Raharjo 
wrote:

> > When I tried to install cycler-0.10.0 and matplotlib-1.5.2, using
> > sboinstall, I got the following errors:
> >
> > Failures:
> >   cycler: md5sum failure for
> > /usr/sbo/distfiles/cycler-0.10.0.tar.gz#md5=
> 4cb42917ac5007d1cdff6cccfe2d016b.
> >
> >   matplotlib: md5sum failure for
> > /usr/sbo/distfiles/matplotlib-1.5.2.tar.gz#md5=
> 66f35e55cc15455eb37b415ae51f1e51.
> >
> >   cycler: cycler.SlackBuild return non-zero
> >   matplotlib: matplotlib.SlackBuild return non-zero
> >
> > The md5sums of both packages looks to be OK, but they fail to build.
>
> Thanks for reporting
>
> fixed on my branch
>
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] updates to my packages

[Greg' Ar Tourter]

I have put updates to nltk (3.2.1), shorewall{,6,-core} (5.0.8.2) and
kbibtex (0.6) on my github repo (https://github.com/ArTourter/Slackbuilds).
I know I have a  key set up somewhere for the slackbuilds git repo but I am
not sure how best to migrate to it.

If grabbing off github is not practical, I can sent the tarballs or wait
for the submissions to be reopen.

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] clamav

[Greg' Ar Tourter]

not sure why these changes should be done. using the current SlackBuild
clamscan is compiled against libpcre without the need for additional
configure flag. It is on the other hand not compiled against libssh2 but
looking at the output of configure, it doesn't try to either.

There must be something weird on your system for it not to detect your
installed pcre. Can you specify why you think there is an issue with
libssh2 (although that is not something that the clamav slackbuild could do
anyway as it is not going to change system files to allow building).

Cheers

Greg

On 19 May 2016 at 19:05, Helmut Hullen  wrote:

> Hallo, slackbuilds-users,
>
> "clamav" seems to need 2 changes:
>
> --enable-pcre
>
> as additional "configure" option
>
> and "/usr/lib/libssh2.so" as symlink to "/usr/lib/libssh2.so.1".
>
> These 2 changes avoid the clamscan message "... but pcre is disabled
> ...".
>
> The "libssh2" symlink is (perhaps ...) only needed for compilation, not
> for running "clamscan".
>
> Viele Gruesse!
> Helmut
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Ugene 1.22.0

[Greg' Ar Tourter]

no it is not an issue with the program nor the package. However, Alien's
QT5 package was compiled with libxkbcommon, if you get the that package
from SBo it should work.

Hope this helps

Greg

On 11 April 2016 at 18:11, Petar Petrov  wrote:

> Hello,
>
> I am trying to update my ugene Slackbuild for version 1.22.0
>
> It builds fine, however when I try to start it, it gives the following
> error:
>
> bash-4.3$ ugene -ui
> This application failed to start because it could not find or load the
> Qt platform plugin "xcb".
>
> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
> offscreen, wayland, xcb.
>
> Reinstalling the application may fix this problem.
> /usr/lib64/ugene/ugene: line 69:  3678 Aborted
> "$dirname/$appname" "${params[@]}"
>
> I build against ALienBob's QT5 (qt5-5.5.1-x86_64-5alien.txz
> ).
> Here's the build script:
>
> https://sourceforge.net/projects/sboppetrov/files/ugene/testing/
>
> Any suggestions?
>
> Do you think it's an issue with the program itself, so I contact the
> developers? They proved to be very helpful before.
>
> regards,
>
> Petar
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] libbluray cannot be downloaded using wget

[Greg' Ar Tourter]

if one changes the the url to use the http protocol (
http://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2)
it works fine.

I suspect something was changed on the configuration of their ftp server.

Cheers

Greg

On 22 February 2016 at 06:31, Jheengut Pritvi 
wrote:

> Hi, usually slackbuilds downloads stuffs using wget.
>
> I'm building the package libbluray but I'm getting the following error ::
>
>
> libbluray:
> libbluray not found in /var/cache/sbopkg.
> --2016-02-22 10:24:52--
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>=> 'libbluray-0.9.2.tar.bz2'
> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
> 2a01:e0d:1:3:58bf:fa02:c0de:20
> Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21...
> connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libbluray/0.9.2 ... done.
> ==> SIZE libbluray-0.9.2.tar.bz2 ... 704357
> ==> PASV ... couldn't connect to 127.0.1.1 port 62782: Connection refused
>
>
> But using curl , I was able to download libbluray.
>
> curl
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
> >libbluray-0.9.2.tar.bz2
>   % Total% Received % Xferd  Average Speed   TimeTime Time
> Current
>  Dload  Upload   Total   SpentLeft
> Speed
> 100  687k  100  687k0 0  47257  0  0:00:14  0:00:14 --:--:--
> 96258
>
>
> I'm using slackware-current.
>
> wget --version
> GNU Wget 1.14 built on linux-gnu.
>
> +digest +https +ipv6 +iri +large-file +nls +ntlm +opie +ssl/openssl
>
> Wgetrc:
> /etc/wgetrc (system)
> Locale: /usr/share/locale
> Compile: gcc -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/etc/wgetrc"
> -DLOCALEDIR="/usr/share/locale" -I. -I../lib -I../lib -O2 -fPIC
> Link: gcc -O2 -fPIC -lssl -lcrypto -lz -ldl -lz -lz -lidn -luuid -lpcre
> ftp-opie.o openssl.o http-ntlm.o ../lib/libgnu.a
>
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> .
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Originally written by Hrvoje Niksic .
> Please send bug reports and questions to .
>
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] SlackBuilds up for grabs

[Greg' Ar Tourter]

I can pick up vim-qt if noone else want it.

Cheers

Greg
On 6 Feb 2016 19:52, "Benjamin Trigona-Harany" 
wrote:

> Hey everyone,
>
> I'm not planning to maintain the following SlackBuild scripts for 14.2.
> Please consider them all up for grabs.
>
> audio/podget
> desktop/kfaenza-icon-theme
> desktop/kpartsplugin
> desktop/plasma-runner-browsefirefoxbookmarks
> desktop/plasmaxplanet
> desktop/vim-qt
> desktop/wmfs
> development/apache-jmeter
> development/jython
> development/spl
> gis/geogig
> gis/geogig-py
> gis/geoserver
> gis/geoserver-control-flow
> gis/geoserver-css
> gis/geoserver-javascript
> gis/geoserver-oracle
> gis/geoserver-pyramid
> gis/geoserver-python
> gis/geoserver-wps
> gis/mobac
> gis/prepair
> gis/udig
> libraries/jai
> libraries/jai-imageio
> libraries/lua-cmsgpack
> network/glassfish
> network/hostsblock
> office/qamus
>
> python/py4j
> system/thinkfan
>
> Thanks, Ben
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Marco Boneti's Packages

[Greg' Ar Tourter]

I can pick up nltk if noone else wants it.

Cheers

Greg

On 2 November 2015 at 19:38, edinaldo  wrote:

> i'm interested in:
>
> /development/dpkg
>
> but @Glenn Becker already volunteered, so it's in good hands.
>
> I use dpkg-source for unpacking the files (* .dsc, .orig.tar.gz * and *
> .debian.tar.gz)
> for testing and for get patches for some SlackBuilds.
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] HandBrake ?

[Greg' Ar Tourter]

Handbrake has been recently updated so i suspect they have moved the old
source to a different location.

Regarding the libs, if i remember correctly, the source expects the
tarballs to be around and it deals with them directly.

Hope this helps

Greg
On 3 Oct 2015 15:59, "Nicolas Kovacs"  wrote:

> Hi,
>
> I just took a peek at HandBrake's SBo page, out of curiosity.
>
> 1. I noticed the source download link doesn't work.
>
> 2. Several multimedia libs are requested for download. I took a peek in
> HandBrake.SlackBuild. As far as I can tell, it doesn't make any use of
> these source tarballs. How is this supposed to work?
>
> Cheers,
>
> Niki
> --
> Microlinux - Solutions informatiques durables
> 7, place de l'église - 30730 Montpezat
> Web  : http://www.microlinux.fr
> Mail : i...@microlinux.fr
> Tél. : 04 66 63 10 32
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] shorewall-core update

[Greg' Ar Tourter]

Hi,

This has been on my todo list but I was away for the weekend so postponed
it to things to do this week instead.

Just to clarify, the first fix does not apply to slackware as we do not
have upstart, and shorewall-init is currently not packaged (I have not been
using it but have been thinking about bringing it in at some point as it
may be useful)

While we are talking about shorewall, the new version 5 will be out at some
point. However, it seems that a lot has changed in the way it works and is
configured. Therefore I was thinking of leaving shorewall 4 for slackware
14.1 and update to version 5 for the next stable release (and maybe bring
shorewall-init then). Does that sound acceptable? Or would people would
prefer to use it as soon as it is out?

Cheers

Greg

On 20 September 2015 at 17:41, Citizen X  wrote:

> Downloaded the slackbuild, checked build version
> against available versions.
> Newer version 4.6.13.1
> Listed corrections
> http://baltimore.shorewall.net/pub/4.6/shorewall-4.6.13/known_problems.txt
>
> 1)  On systems running Upstart, shorewall-init cannot reliably secure
> the firewall before interfaces are brought up.
>
> 2)  When one or more chain names are given in a 'reset' command, the
> command fails.
>
> Corrected in Shorewall 4.6.13.1
>
> 3)  The Tinc macro and tinc entries in the tunnels file only enable the
> UDP data connection; they do not enable the TCP meta-connection.
>
> Corrected in Shorewall 4.6.13.1
>
>
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

[Slackbuilds-users] nvidia-driver-{info,SlackBuild} fixes

[Greg' Ar Tourter]

Hi,

The latest nvidia-driver package has a few errors in it.

The info file has a trailing space after a new line \ in a couple of place
making the file unparsable by software such as sbopkg.

Additionally, if one use the compat32 option, a couple of 32bit files get
written to the 64bit path overwriting their 64bit equivalent.

Their is still something wrong with the package that makes it not work
properly on a multilib -current platform for some reason but since neither
multilib nor current are supported that will remain up to me to figure out.

Cheers

Greg
--- nvidia-driver.SlackBuild2015-08-01 01:57:43.0 +0100
+++ nvidia-driver.SlackBuild.sbopkg 2015-08-03 13:12:07.216034642 +0100
@@ -139,8 +139,8 @@
   install -m 755 32/libGL.so.$VERSION $PKG/usr/lib/libGL.so.$VERSION-nvidia
   install -m 755 32/libGL.la $PKG/usr/lib/libGL.la-nvidia
   install -m 755 32/libEGL.so.$VERSION $PKG/usr/lib/libEGL.so.$VERSION-nvidia
-  install -m 755 32/libGLESv1_CM.so.$VERSION 
$PKG/usr/lib$LIBDIRSUFFIX/libGLESv1_CM.so.$VERSION
-  install -m 755 32/libGLESv2.so.$VERSION 
$PKG/usr/lib$LIBDIRSUFFIX/libGLESv2.so.$VERSION
+  install -m 755 32/libGLESv1_CM.so.$VERSION 
$PKG/usr/lib/libGLESv1_CM.so.$VERSION
+  install -m 755 32/libGLESv2.so.$VERSION $PKG/usr/lib/libGLESv2.so.$VERSION
   install -m 755 32/libnvcuvid.so.$VERSION $PKG/usr/lib/
   install -m 755 32/libnvidia-compiler.so.$VERSION $PKG/usr/lib/
   install -m 755 32/libnvidia-eglcore.so.$VERSION $PKG/usr/lib/
--- nvidia-driver.info  2015-08-01 01:57:43.0 +0100
+++ nvidia-driver.info.sbopkg   2015-08-03 12:37:41.143263663 +0100
@@ -11,7 +11,7 @@
 c672951b0faa31089f4940d28ccd5463 \
 0e263655eaf8cf9a68697bda61e6050f \
 7975a29438550c109479b2f2bed51401 \
-e0cd59a13b5651ec2396727e7e2e54a5 \ 
+e0cd59a13b5651ec2396727e7e2e54a5 \
 1a6b4de9c3a91ef3680fa4f0bc80951b"
 
DOWNLOAD_x86_64="ftp://download.nvidia.com/XFree86/Linux-x86_64/352.30/NVIDIA-Linux-x86_64-352.30.run
 \
  
ftp://download.nvidia.com/XFree86/nvidia-installer/nvidia-installer-352.30.tar.bz2
 \
@@ -23,7 +23,7 @@
 c672951b0faa31089f4940d28ccd5463 \
 0e263655eaf8cf9a68697bda61e6050f \
 7975a29438550c109479b2f2bed51401 \
-e0cd59a13b5651ec2396727e7e2e54a5 \ 
+e0cd59a13b5651ec2396727e7e2e54a5 \
 1a6b4de9c3a91ef3680fa4f0bc80951b"
 REQUIRES="libvdpau nvidia-kernel"
 MAINTAINER="Edward W. Koenig"
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] QtCurve-{Gtk2,KDE4} md5sum check fails

[Greg' Ar Tourter]

it appears that the original maintainer has dropped the project, from the
discussion on kdelooks he says:

"I no longer actively use, nor maintain, QtCurve. However, there is a
project (on GitHub, or projects.kde.org) that is continuing QtCurve
development. I suggest you send this patch there."

I will investigate the project he is referring to and submit a new build.

In the meantime, thanks Mateo for hosting the original sources.

Cheers

On 15 November 2014 09:01, Jan Feific  wrote:

>
> The craigd.wikispaces.com website says "Subscription Expired", so the
> site is probably dead. I can confirm that the tarballs from your site build
> well, though.
> Thanks,
>
> yf
>
>
>
> On 11/15/2014 09:51 AM, Matteo Bernardini wrote:
>
>> try loading the links in a browser, like this for example
>>
>> http://craigd.wikispaces.com/file/view/QtCurve-KDE4-1.8.14.tar.bz2
>>
>> I have the original sources and self host them (I'll fix the download
>> links too)
>>
>> http://ponce.cc/slackware/sources/repo/QtCurve-Gtk2-1.8.15.tar.bz2
>> http://ponce.cc/slackware/sources/repo/QtCurve-KDE4-1.8.14.tar.bz2
>>
>> remove the downloaded files you got in /var/cache/sbopkg, download
>> these there instead and relaunch sbopkg.
>>
>> Matteo
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>  ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] clamav build issues

[Greg' Ar Tourter]

eww indeed, well they know they got it wrong but don't seem much in a hurry
to fix it. As I said there is a patch for 0.98.4rc1 that works well, and
0.98.4 is only a bugfix release.

As for the possible fixes, your "last resort" one is the only one that will
work on this one. as they have split the configure script in loads of
little bits.

Personally I have just not installed it and kept the old package. The
signatures are still being updated so I don't care too much.


On 11 June 2014 12:01, B Watson  wrote:

> On 6/11/14, Greg' Ar Tourter  wrote:
> > Well actually, not in this case. If you read the threads you will see
> that
> > they have changed the configure scripts and the build system and have
> > hardcoded the /usr/lib path in a few places. So even setting the LDFLAGS
> as
> > you mention has no effect.
>
> Eww.
>
> Try: sed -i "s,\\,lib$LIBDIRSUFFIX,g" configure
>
> (Maybe there are subdirs with their own configure scripts or such, adapt it
> as needed, I haven't actually looked at the clamav source)
>
> As a last resort, you could do something like "mv /usr/lib
> /usr/lib.backup",
> try building clamav... afterwards "mv /usr/lib.backup /usr/lib".
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] clamav build issues

[Greg' Ar Tourter]

Well actually, not in this case. If you read the threads you will see that
they have changed the configure scripts and the build system and have
hardcoded the /usr/lib path in a few places. So even setting the LDFLAGS as
you mention has no effect.


On 10 June 2014 23:25, B Watson  wrote:

> On 6/10/14, Miguel De Anda  wrote:
>
> > /usr/lib/libxml2.so: error adding symbols: File in wrong format
>
> That's a classic multilib error. You're building a 64-bit package, but the
> linker is trying to use the library in /usr/lib (which is the 32-bit one).
>
> Usually you can fix these by adding LDFLAGS="-L/usr/lib64" in front
> of the configure command (or whatever it's using), in the same way as
> CFLAGS and CXXFLAGS. See http://slackbuilds.org/faq/#multilib
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] clamav build issues

[Greg' Ar Tourter]

This is a known bug in the 0.98.3 release. there is a patch for the
0.98.4rc1 release but it hasn't been merge into the release yet.

see http://lurker.clamav.net/message/20140521.195320.a8b6c479.en.html and
http://www.linuxquestions.org/questions/slackware-14/clamav-has-upgraded-from-0-98-1-to-0-98-3-how-to-update-slackbuilds-4175505248/


On 10 June 2014 19:43, Miguel De Anda  wrote:

> has anybody tried building clamav lately? i'm on slackware-current with
> 32-bit compat libs so either of those may be the issue... here is the error
> message i get:
>
> $sbopkg -i clamav
>
> ...
> libclamav_la-fp_sqr_comba_4.o .libs/libclamav_la-fp_sqr_comba_48.o
> .libs/libclamav_la-fp_sqr_comba_6.o .libs/libclamav_la-fp_sqr_comba_64.o
> .libs/libclamav_la-fp_sqr_comba_7.o .libs/libclamav_la-fp_sqr_comba_8.o
> .libs/libclamav_la-fp_sqr_comba_9.o
> .libs/libclamav_la-fp_sqr_comba_generic.o
> .libs/libclamav_la-fp_sqr_comba_small_set.o .libs/libclamav_la-fp_sqrmod.o
> .libs/libclamavS.o -Wl,--whole-archive c++/.libs/libclamavcxx.a
> ./.libs/libclamav_internal_utils.a -Wl,--no-whole-archive  -Wl,-rpath
> -Wl,/usr/lib64/../lib64 -Wl,-rpath -Wl,/usr/lib64/../lib -Wl,-rpath
> -Wl,/usr/lib64/../lib64 -Wl,-rpath -Wl,/usr/lib64/../lib -L/usr/lib
> /usr/lib/libxml2.so -lz -L/usr/lib64 -lbz2 /usr/lib/libltdl.so
> /usr/lib64/../lib64/libstdc++.so /usr/lib64/../lib/libstdc++.so -lssl
> -lcrypto -lpthread -lm -ldl  -O2 -Wl,--version-script
> -Wl,../libclamav/libclamav.map   -pthread -Wl,-soname -Wl,libclamav.so.6 -o
> .libs/libclamav.so.6.1.22
> /usr/lib/libxml2.so: error adding symbols: File in wrong format
> collect2: error: ld returned 1 exit status
> make[4]: *** [libclamav.la] Error 1
> make[4]: Leaving directory `/home/tmp/SBo/clamav-0.98.3/libclamav'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/tmp/SBo/clamav-0.98.3/libclamav'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/tmp/SBo/clamav-0.98.3/libclamav'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/tmp/SBo/clamav-0.98.3'
> make: *** [all] Error 2
>
>
>
> $file /usr/lib/libxml2.so
> /usr/lib/libxml2.so: symbolic link to `libxml2.so.2.9.1'
>
> $file /usr/lib/libxml2.so.2.9.1
> /usr/lib/libxml2.so.2.9.1: ELF 32-bit LSB  shared object, Intel 80386,
> version 1 (SYSV), dynamically linked, stripped
>
> it looks like its trying to use the 32-bit libs. am i doing something
> wrong?
>
> -m
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20140202.1

[Greg' Ar Tourter]

Hi Robby,

The new gis folder does not contain any of the tarballs (only the expanded
folders) nor any of the .asc files for each tarball.

Cheers

Greg


On 2 February 2014 08:31, Robby Workman  wrote:

> commit 7f4c6a1a29aa1515a7ff859628f798e7eaf478c8
> Author: Robby Workman 
> Date:   Sun Feb 2 02:11:32 2014 -0600
>
> Public www update: Sun Feb  2 08:10:38 UTC 2014
>
> Sun Feb  2 08:10:38 UTC 2014
> academic/cld2: Updated for version 20140131.
> audio/minimodem: Added (software audio FSK modem).
> desktop/cheser-icon-theme: Removed (No SBo Maintainer).
> desktop/gtkman: Removed (No SBo Maintainer).
> desktop/jwm: Updated for version 2.2.0.
> development/KKEdit: Removed (No SBo Maintainer).
> development/bluefish: Updated for version 2.2.5.
> development/scite: Updated for version 3.3.9.
> games/Domination: Removed (No SBo Maintainer).
> games/qjoypad: Removed (No SBo Maintainer).
> gis/Fiona: Moved from Academic category.
> gis/OWSLib: Moved from Academic category.
> gis/SFCGAL: Moved from Libraries category.
> gis/Shapely: Moved from Academic category.
> gis/geogit: Moved from Academic category.
> gis/geopy: Moved from Python category.
> gis/geos: Moved from Libraries category.
> gis/geoserver-control-flow: Moved from Academic category.
> gis/geoserver-css: Moved from Academic category.
> gis/geoserver-pyramid: Moved from Academic category.
> gis/geoserver-wps: Moved from Academic category.
> gis/geoserver: Moved from Academic category.
> gis/horao: Moved from Academic category.
> gis/laszip: Moved from Libraries category.
> gis/mapnik: Moved from Academic category.
> gis/osm2pgrouting: Moved from Academic category.
> gis/osm2pgsql: Moved from Academic category.
> gis/pdal: Moved from Academic category.
> gis/pgrouting: Moved from Academic category.
> gis/pointcloud: Moved from Academic category.
> gis/postgis: Moved from System category.
> gis/proj: Moved from System category.
> gis/pyproj: Moved from Academic category.
> gis/qgis: Moved from Academic category.
> gis/rasterio: Moved from Academic category.
> gis/udig: Moved from Academic category.
> gis/xplanet: Moved from Desktop category.
> graphics/dcraw: Updated for version 0.9.20.
> graphics/digikam: Re-Added notes about broken lensfun deps.
> graphics/fritzing: Updated for version 0.8.7b.
> libraries/dbh: Removed (No SBo Maintainer).
> libraries/enum34: Updated for version 0.9.20.
> libraries/ffms2: Added (a cross-platform wrapper library)
> libraries/tff: Updated for version 0.2.8.
> libraries/tubo: Removed (No SBo Maintainer).
> libraries/wxGTK3: Fixed the broken wx-config symlink
> multimedia/ProjectX: Removed (No SBo Maintainer).
> multimedia/aegisub: Added (General-purpose subtitle editor)
> multimedia/mtvcgui: Removed (No SBo Maintainer).
> network/FireWorks: Updated for version 0.66.
> network/Pafy: Added (Python API for YouTube content).
> network/QuiteRSS: Updated for version 0.14.3.
> network/retroshare: Updated for version 0.5.5c.
> office/gnucash: Updated for version 2.6.1.
> office/sigil: Updated for version 0.7.4.
> perl/perl-Archive-Extract: Updated for version 0.72.
> perl/perl-Module-Pluggable: Updated for version 5.1.
> python/pycld2: Updated for version 20140131.
> system/the_silver_searcher: Updated for version 0.19.2.
> system/trachet: Updated for version 0.3.17.
> system/unetbootin: Updated for version 585.
> +--+
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Отговор: My SlackBuilds for 14.1

[Greg' Ar Tourter]

In case that helps, I have managed to compile and use perl-tk 804.031 on
current. the only changes to the slackbuild apart from the version bump was
the removal of both patches.

Cheers

Greg


On 31 October 2013 09:38, Petar Petrov  wrote:

> hi Robby,
>
> about gchemutils: the 0.12.13 version did not compile on RC1. The newest
> version (0.14.2) compiled fine. It requires an updated goffice, so I just
> did a simple version bump of 0.8.14 to 0.10.8. About gtkglext -- the
> slackbuild for 14.0 did not work for RC1, however the one from PONCE's
> unofficial SBo branch for -current compiled. And so, gchemutils 0.14.2
> compiles fine on RC1. The new version of gchemutils did not install any
> schemas in /etc (don't know why), so i modified the doinst.sh
>
> i don't have a fix for perl-Tk, i'll see what I can do on the weekend
>
> about murrine-themes: yes, put it for 14.0 as well.
>
> -petar
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] subversion linked to libpq

[Greg' Ar Tourter]

Hi,

not on my systems (all up-to-date -current with no postgres installed)

you must have recompiled subversion or you binary has been overwritten by
something.

Greg



On 19 September 2013 15:29, Adis Nezirovic  wrote:

> Hello,
>
> I know Pat reads this list, hope he sees this.
>
> It seems to me that official Slackware subversion binary is somehow linked
> to PostgreSQL
> (Slackware-Current, subversion-1.7.13, but also v1.7.10):
>
> ldd /usr/bin/svn| grep libpq
> libpq.so.5 => not found
>
> I've noticed this when I removed PostgreSQL 9.2 package, new package for
> 9.3 keeps libraries in
> /usr/lib64/postgresql/9.3/lib
>
>
> Can anoyone confirm this?
>
>
> Best regards,
> Adis
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Suggestion for nvidia-driver page

[Greg' Ar Tourter]

Indeed 3.19.49 is probably a better bet (it wasn't available when I started
using current). The 325.xx series is more a development branch (aka
"shortlived" in Nvidia's terms). I personally have had no issues with the
325.xx branch on either 14.0 and current but ultimately, it is up to the
package maintainer to choose which one he'd rather use.



On 3 September 2013 13:22, Nick Blizzard  wrote:

> as a note to the note, a newer driver was released that also supports the
> 3.10 kernel used in -current:
>
> ftp://download.nvidia.com/XFree86/Linux-x86/319.49/
>
> (Yea, I know, 319 < 325... but it really is a newer driver and is working
> well with -current)
>
>
> On Tue, Sep 3, 2013 at 6:54 AM, Greg' Ar Tourter wrote:
>
>> This has already been discussed and is fixed in the ready tree. we are
>> just waiting for the next release now.
>>
>> As a side note to this, the current version of the non legacy package
>> does not work on current as the kernel is not supported. upgrading to
>> 325.15 solves that problem.
>>
>> Cheers
>>
>> Greg
>> .
>>
>>
>> On 3 September 2013 11:26, Matteo Paoluzzi  wrote:
>>
>>> Using sbopkg for nvidia-driver installation in my new Slackware64, I
>>> found out that it failed extracting some missing archives. Those
>>> archives are listed in nvidia-driver's slackbuild page, but only under
>>> x86 architecture, thus preventing sbopkg from downloading them.
>>>
>>> This is not only a sbopkg issue, because those archives are needed by
>>> the slackbuild also on the x86_64 architecture, not only on x86, and
>>> looking at the page as is at moment, it seems that those archives are
>>> not needed under X86_64, which is wrong.
>>>
>>> My suggestion is to list the .tar.bz2 archives ALSO under "Source
>>> Download (64bit)" section.
>>> ___
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users@slackbuilds.org
>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - http://slackbuilds.org/faq/
>>>
>>>
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
>>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Suggestion for nvidia-driver page

[Greg' Ar Tourter]

This has already been discussed and is fixed in the ready tree. we are just
waiting for the next release now.

As a side note to this, the current version of the non legacy package does
not work on current as the kernel is not supported. upgrading to 325.15
solves that problem.

Cheers

Greg
.


On 3 September 2013 11:26, Matteo Paoluzzi  wrote:

> Using sbopkg for nvidia-driver installation in my new Slackware64, I
> found out that it failed extracting some missing archives. Those
> archives are listed in nvidia-driver's slackbuild page, but only under
> x86 architecture, thus preventing sbopkg from downloading them.
>
> This is not only a sbopkg issue, because those archives are needed by
> the slackbuild also on the x86_64 architecture, not only on x86, and
> looking at the page as is at moment, it seems that those archives are
> not needed under X86_64, which is wrong.
>
> My suggestion is to list the .tar.bz2 archives ALSO under "Source
> Download (64bit)" section.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] nvidia-driver.info missing 64bit file info

[Greg' Ar Tourter]

Hi Robby,

No problems, it was easy enough to do. I include the remaining 3 patches in
the same format as the previous one. If you prefer them differently let me
know.

Cheers

Greg


On 16 July 2013 06:52, Robby Workman  wrote:

> On Mon, 15 Jul 2013 20:31:58 +0100
> "Greg' Ar Tourter"  wrote:
>
> > Hi Robby,
> >
> > Well looking through the repository, the nvidia-driver  (and
> > avr8-gnu-toolchain, but that's only for the pdf manual) packages are
> > the only ones with files in common. So asking to download both
> > version seems rather a waste of bandwitdh
>
>
> Okay, fair point.
>
>
> > Moreover, for some packages (ucsc-blat, p4, p4v ), the source file
> > name is the same for 32 and 64 bit version but are downloaded from
> > different locations and have different checksum. in these case, wget
> > with append .1 to the second one and therefore making the slackbuild
> > use the 32bit version instead.
>
>
> Oh wow, I wasn't aware of that.
>
> Given all of this and erik's reply, I think it's probably a good
> change to make.
>
> Don't feel obligated to do this, as I don't mind doing it myself,
> but since I'm a bit tied up on another project right now, patches
> for all of the affected stuff would make this easier :)  Also,
> since you pointed it out, you should be credited with the fixes
> anyway.
>
> Seriously, though, if you don't want to do it or don't have time,
> that's fine.
>
> -RW
>


nvidia-legacy96-driver.patch
Description: Binary data


nvidia-legacy173-driver.patch
Description: Binary data


nvidia-legacy304-driver.patch
Description: Binary data
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] nvidia-driver.info missing 64bit file info

[Greg' Ar Tourter]

Hi Robby,

Well looking through the repository, the nvidia-driver  (and
avr8-gnu-toolchain, but that's only for the pdf manual) packages are the
only ones with files in common. So asking to download both version seems
rather a waste of bandwitdh

Moreover, for some packages (ucsc-blat, p4, p4v ), the source file name is
the same for 32 and 64 bit version but are downloaded from different
locations and have different checksum. in these case, wget with append .1
to the second one and therefore making the slackbuild use the 32bit version
instead.(unless  sbopkg instruct wget to overwrites the previous version
which again would be a waste of bandwidth)

just my 2p worth though.

Cheers

Greg


On 15 July 2013 18:56, Robby Workman  wrote:

> On Mon, 15 Jul 2013 18:52:20 +0100
> "Greg' Ar Tourter"  wrote:
>
> > All the recently released/updated nvidia*-driver.info file are
> > missing the source files and associated md5sum for the 64bit version.
> > There are indeed common to bot the 32 and 64 bit version but need to
> > be specified for both. Currently sbopkg fails because it isn't
> > downloading the tar.xz files on 64bit machines since only the .run
> > file is specified.
>
>
> Hrm, my fault, but I'm not convinced that sbopkg is DTRT.
>
> I'm going to CC  the sbopkg list to solicit feedback, but it's my point
> of view that sbopkg should *always* pull the things specified in
> $DOWNLOAD, and if on x86_64, pull the things specified in
> $DOWNLOAD_x86_64.  Unless my memory is failing me, that is how we
> envisioned things working when we added the *_x86_64 variables to
> the .info file.
>
> -RW
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

[Slackbuilds-users] nvidia-driver.info missing 64bit file info

[Greg' Ar Tourter]

Hi,

All the recently released/updated nvidia*-driver.info file are missing the
source files and associated md5sum for the 64bit version. There are indeed
common to bot the 32 and 64 bit version but need to be specified for both.
Currently sbopkg fails because it isn't downloading the tar.xz files on
64bit machines since only the .run file is specified.

I attach a patch for the non legacy version but the legacy ones need a
similar treatment.

Cheers

Greg


nvidia-driver.info_64bit.patch
Description: Binary data
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/