Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
> Maybe the *.nfo files should be extended by listing optional > dependencies, so we could handle these an automated way? NO REQUIRES in .info should only be used for mandatory dependencies, not optional dependencies. > Another subject are dependencies required only during build-time > vss dependencies required at runtime. This can be written in the README -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ 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] findpkg version mismatch in .info
> Hi everybody ! > > findpkg is on version 20160817 both on the file to download in > findpkg.info and on the SlackBuild script, but the VERSION in the findpkg.info > file is still 20160710. > > It could confuse some auto-build scripts... Fixed in my branch Thanks -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ 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] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/19/2016 06:22 PM, Sebastian Arcus wrote:
> On 19/10/16 21:26, Nishant Limbachia wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 10/19/2016 08:41 AM, Franzen wrote:
>>> On 19.10.2016 12:17, Sebastian Arcus wrote:
On 19/10/16 10:59, Franzen wrote:
> On 19.10.2016 11:42, Sebastian Arcus wrote:
>> The clamav-unofficial-sigs.cron crond crontab file included with
>> clamav-unofficial-sigs seems to be incompatible with the version of
>> Cron
>> used on Slackware. It uses the extra field for the username (clamav)
>> which seems to break things on Slackware. I've just noticed this on
>> several clamav installs which were months out of date, as the
cron file
>> never worked. Also, I'm not sure the "/bin/bash" bit on the crontab
>> line
>> is needed - as it works fine for me without it.
>
> /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i
> suggest to don't use the cron-script from upstream, but put the
> following in /var/spool/cron/crontabs/clamav:
> 12 * * * * /usr/bin/clamav-unofficial-sigs.sh
I can't really make sense of what is going on here - because the
clamav-unofficial-sigs.cron file is included in the
clamav-unofficial-sigs.tar.gz - but looking at its contents, it should
be part of the sources, as it comes from upstream. Same with the
logrotate and the man files. Why are they included in the SBo scripts
archive?
>>>
>>> The cron-file and logrotate-file come from upstream, they are
generated by
>>>
>>
https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh,
>> by the --install-all option. I assume the packager exracted the files
>> because he didn't wan't to use the --install-all option for the package.
>>> As this package depends on clamav, which has also logrotate-script
>> starting with
>>> /var/log/clamav/*.log {
>>> ,logrotate will complain about double configuration, so you don't need
>> this logrotate at all.
>>> The best the you can do, is to fix the SlackBuild and propose it to
>> the maintainer.
>>>
>>> Johannes
>>> ___
>>> 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/
>>>
>>
>> I'm the maintainer for clamav-unofficial-sigs. logrotate and cron script
>> are provided within the clamav-unofficial-sigs.sh script and upstream
>> expects each user to use --install-all to generate those two. With
>> SlackBuild, we shouldn't expect the user to do one additional step after
>> install to actually use the package. So with every new version, I
>> extract logrotate and cron script first and provide them as part of
>> SlackBuild.
>>
>> As far as using upstream cron script is concerned, my intent was to
>> provide a script in DOCS so builders will take it as an example and not
>> simply copy and use the script in cron. You can roll your own or modify
>> upstream script as you see fit.
>>
>> Here's my crontab (root)
>>
>> # Run clamav-unofficial-sigs script
>> 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null
>>
>> I can provide my script as an example which would again go in DOCS and
>> not anywhere else.
>>
>
> I'm still not sure I'm following this: why is the cron file provided
with the Slackbuilds at all, if it is incompatible with Slackware? It's
worse than nothing - as the user would copy it in place and assume it
works - as it comes from Slackbuilds and it is presumed to be tested to
work with Slackware. Wouldn't it be better to provide either nothing or
provide a suitable cron file that works or at least a patch?
> ___
> 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/
>
It is provided because it is part of the script. You can generate one
anytime by running /usr/bin/clamav-unofficial-sigs.sh --install-cron.
Since it is part of script, I've packaged it in DOCS.
- --
Nishant Limbachia
nish...@mnspace.net
### Please note the new pgp keys
Old GPG Key: 0x0FF9D6D5 (expiring soon)
Old GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5
New GPG Key: 0x3D46A2D1
New GPG Fingerprint: 44D1 27CE D07F 2ED1 B4AD 2BEE A828 D6D6 3D46 A2D1
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCAAGBQJYCCVTAAoJEKgo1tY9RqLRmNsQAJC8tgYVb1piWLab+ic8Ekfz
BXtyqhoT8OFtKKdETuc9eiowclbCiA4oBbyN8s6iwnRUkGaaayW9K1zJ3GtsEQYE
MBaemwTkvryQmswM46Av4oIs31yAMTyaVQGwqH7jnW5aN6f1nFI7ZiIOvYBse2Bg
hoBN1ltA7sMWi8rWZfGNiWySkadhwrZZeP0J0iKzQHLMQPbclrg5JV90s8JL07DV
Uwx3iT4EFpt+Qb0HzZUsQFFL
Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
On 10/20/2016 01:23 AM, King Beowulf wrote: > Usbredir is not a "hard" dependency that prevents qemu from compiling. > Rather, it is an optional dependency to add functionality. This is > mentioned in the README. I'm aware, but without usbredir virt-manager becomes kind of unusable. I remember on 14.1 usbredir was optional because the official libusb was too old, but since 14.2 that's not the case anymore... And in the current state the same slackbuild script will create two different binaries depending on the installed packages. And we're not able to build QEMU without usbredir support on a system with usbredir installed (no slackbuild switches / automatically enabled if found)... Maybe the *.nfo files should be extended by listing optional dependencies, so we could handle these an automated way? Another subject are dependencies required only during build-time vss dependencies required at runtime. I'm just thinking out loud ;-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ 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] qemu/spice-gtk and usbredir
On 10/19/2016 03:26 PM, Thomas Szteliga wrote: > Hello, > > shouldn't usbredir be listed in REQUIRES of QEMU and spice-gtk? > > Because when QEMU is compiled without usbredir present > (autodetected during compilation) virt-install usage will > be problematic or even impossible. > > --- Usbredir is not a "hard" dependency that prevents qemu from compiling. Rather, it is an optional dependency to add functionality. This is mentioned in the README. -Ed signature.asc Description: OpenPGP digital signature ___ 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] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware
On 19/10/16 21:26, Nishant Limbachia wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/19/2016 08:41 AM, Franzen wrote:
On 19.10.2016 12:17, Sebastian Arcus wrote:
On 19/10/16 10:59, Franzen wrote:
On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond crontab file included with
clamav-unofficial-sigs seems to be incompatible with the version of
Cron
used on Slackware. It uses the extra field for the username (clamav)
which seems to break things on Slackware. I've just noticed this on
several clamav installs which were months out of date, as the cron file
never worked. Also, I'm not sure the "/bin/bash" bit on the crontab
line
is needed - as it works fine for me without it.
/usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i
suggest to don't use the cron-script from upstream, but put the
following in /var/spool/cron/crontabs/clamav:
12 * * * * /usr/bin/clamav-unofficial-sigs.sh
I can't really make sense of what is going on here - because the
clamav-unofficial-sigs.cron file is included in the
clamav-unofficial-sigs.tar.gz - but looking at its contents, it should
be part of the sources, as it comes from upstream. Same with the
logrotate and the man files. Why are they included in the SBo scripts
archive?
The cron-file and logrotate-file come from upstream, they are generated by
https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh,
by the --install-all option. I assume the packager exracted the files
because he didn't wan't to use the --install-all option for the package.
As this package depends on clamav, which has also logrotate-script
starting with
/var/log/clamav/*.log {
,logrotate will complain about double configuration, so you don't need
this logrotate at all.
The best the you can do, is to fix the SlackBuild and propose it to
the maintainer.
Johannes
___
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/
I'm the maintainer for clamav-unofficial-sigs. logrotate and cron script
are provided within the clamav-unofficial-sigs.sh script and upstream
expects each user to use --install-all to generate those two. With
SlackBuild, we shouldn't expect the user to do one additional step after
install to actually use the package. So with every new version, I
extract logrotate and cron script first and provide them as part of
SlackBuild.
As far as using upstream cron script is concerned, my intent was to
provide a script in DOCS so builders will take it as an example and not
simply copy and use the script in cron. You can roll your own or modify
upstream script as you see fit.
Here's my crontab (root)
# Run clamav-unofficial-sigs script
6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null
I can provide my script as an example which would again go in DOCS and
not anywhere else.
I'm still not sure I'm following this: why is the cron file provided
with the Slackbuilds at all, if it is incompatible with Slackware? It's
worse than nothing - as the user would copy it in place and assume it
works - as it comes from Slackbuilds and it is presumed to be tested to
work with Slackware. Wouldn't it be better to provide either nothing or
provide a suitable cron file that works or at least a patch?
___
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] qemu/spice-gtk and usbredir
Hello, shouldn't usbredir be listed in REQUIRES of QEMU and spice-gtk? Because when QEMU is compiled without usbredir present (autodetected during compilation) virt-install usage will be problematic or even impossible. This won't work without usbredir: # virt-install \ --connect qemu:///system \ --name guest1 \ --cdrom /srv/storage/iso/CentOS-7-x86_64-Minimal-1511.iso \ --memory 1024 \ --disk none ERROR unsupported configuration: USB redirection is not supported by this version of QEMU Domain installation does not appear to have been successful. and will work when QEMU was compiled with usbredir present: # virt-install \ --connect qemu:///system \ --name guest1 \ --cdrom /srv/storage/iso/CentOS-7-x86_64-Minimal-1511.iso \ --memory 1024 \ --disk none Starting install... Creating domain... Same goes for spice-gtk. When spice-gtk is compiled without usbredir present then View Manager in virt-manager won't be able to connect to a VM's screen. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ 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] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/19/2016 08:41 AM, Franzen wrote:
> On 19.10.2016 12:17, Sebastian Arcus wrote:
>> On 19/10/16 10:59, Franzen wrote:
>>> On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond crontab file included with
clamav-unofficial-sigs seems to be incompatible with the version of
Cron
used on Slackware. It uses the extra field for the username (clamav)
which seems to break things on Slackware. I've just noticed this on
several clamav installs which were months out of date, as the cron file
never worked. Also, I'm not sure the "/bin/bash" bit on the crontab
line
is needed - as it works fine for me without it.
>>>
>>> /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i
>>> suggest to don't use the cron-script from upstream, but put the
>>> following in /var/spool/cron/crontabs/clamav:
>>> 12 * * * * /usr/bin/clamav-unofficial-sigs.sh
>>
>> I can't really make sense of what is going on here - because the
>> clamav-unofficial-sigs.cron file is included in the
>> clamav-unofficial-sigs.tar.gz - but looking at its contents, it should
>> be part of the sources, as it comes from upstream. Same with the
>> logrotate and the man files. Why are they included in the SBo scripts
>> archive?
>
> The cron-file and logrotate-file come from upstream, they are generated by
>
https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh,
by the --install-all option. I assume the packager exracted the files
because he didn't wan't to use the --install-all option for the package.
> As this package depends on clamav, which has also logrotate-script
starting with
> /var/log/clamav/*.log {
> ,logrotate will complain about double configuration, so you don't need
this logrotate at all.
> The best the you can do, is to fix the SlackBuild and propose it to
the maintainer.
>
> Johannes
> ___
> 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/
>
I'm the maintainer for clamav-unofficial-sigs. logrotate and cron script
are provided within the clamav-unofficial-sigs.sh script and upstream
expects each user to use --install-all to generate those two. With
SlackBuild, we shouldn't expect the user to do one additional step after
install to actually use the package. So with every new version, I
extract logrotate and cron script first and provide them as part of
SlackBuild.
As far as using upstream cron script is concerned, my intent was to
provide a script in DOCS so builders will take it as an example and not
simply copy and use the script in cron. You can roll your own or modify
upstream script as you see fit.
Here's my crontab (root)
# Run clamav-unofficial-sigs script
6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null
I can provide my script as an example which would again go in DOCS and
not anywhere else.
Thanks,
- --
Nishant Limbachia
nish...@mnspace.net
### Please note the new pgp keys
Old GPG Key: 0x0FF9D6D5 (expiring soon)
Old GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5
New GPG Key: 0x3D46A2D1
New GPG Fingerprint: 44D1 27CE D07F 2ED1 B4AD 2BEE A828 D6D6 3D46 A2D1
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCAAGBQJYB9b4AAoJEKgo1tY9RqLRqRcQAITANT0yP19yMd8sWBgZemHN
sTOOcqrkx7z76bYd/zekAWX7VUNKne6ts8Va5Q8u0Xm0ZynF9yBJALI8CXw/SFBn
e5U1bhfmpM6Ja/XDVNUodvf6w+a89IisViVmtjp9Ex2PCJS0wID0REdilcF6+Jnz
FUjFKMWnbJRPod/G/e5rakUpgZhTkc2C9FYYc3/nE1iaiS5l89Z/i6x3lxsuH6Mz
WTQdIkExE1129XUCLpEvaL+hKNIGLTOz3jxIY4tChXtukDDzxiEFXumoo405EwaA
yO9KN5izddiMZMBxySNUm+dj5aahEaGnFKVHyBDWh3OHuN8WzKISLnkYDklq4UYX
CaAcZAMXNAaFiNybz+CLX29RfwBy0TB5qao5DkdyU9/15aE4nv+23uV++dN1QB1t
kQNkUMMicBO1zO8mWVQX19W+V6IFQMx25ow62enCahTKqGA9oMJKYwTUYoA13Yxy
CdukwpAUXnPi4kFJEEaNQtcMS+c+QeEB9+hSz79CVna5scrmNhQ1OWqTVS3dXy7x
5hnsnbvL9YJl67g4oiBJV6sNLrWyv85cDLGMLWUf8U+hE3lOYwBDcbiVWMBOtwkf
/kKmgaK+dC16I0DHWGS2KY6IozJTk2kfReYE8DpVuv3xr5y+kNG5sTTpTiv7fLbU
wUgJhjpu2PDCgoJ70eZN
=8DGU
-END PGP SIGNATURE-
___
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] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware
On 19.10.2016 12:17, Sebastian Arcus wrote:
On 19/10/16 10:59, Franzen wrote:
On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond crontab file included with
clamav-unofficial-sigs seems to be incompatible with the version of Cron
used on Slackware. It uses the extra field for the username (clamav)
which seems to break things on Slackware. I've just noticed this on
several clamav installs which were months out of date, as the cron file
never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line
is needed - as it works fine for me without it.
/usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i
suggest to don't use the cron-script from upstream, but put the
following in /var/spool/cron/crontabs/clamav:
12 * * * * /usr/bin/clamav-unofficial-sigs.sh
I can't really make sense of what is going on here - because the
clamav-unofficial-sigs.cron file is included in the
clamav-unofficial-sigs.tar.gz - but looking at its contents, it should
be part of the sources, as it comes from upstream. Same with the
logrotate and the man files. Why are they included in the SBo scripts
archive?
The cron-file and logrotate-file come from upstream, they are generated by
https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh,
by the --install-all option. I assume the packager exracted the files
because he didn't wan't to use the --install-all option for the package.
As this package depends on clamav, which has also logrotate-script
starting with
/var/log/clamav/*.log {
,logrotate will complain about double configuration, so you don't need
this logrotate at all.
The best the you can do, is to fix the SlackBuild and propose it to the
maintainer.
Johannes
___
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] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware
On 19/10/16 10:59, Franzen wrote: On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the extra field for the username (clamav) which seems to break things on Slackware. I've just noticed this on several clamav installs which were months out of date, as the cron file never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line is needed - as it works fine for me without it. /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i suggest to don't use the cron-script from upstream, but put the following in /var/spool/cron/crontabs/clamav: 12 * * * * /usr/bin/clamav-unofficial-sigs.sh I can't really make sense of what is going on here - because the clamav-unofficial-sigs.cron file is included in the clamav-unofficial-sigs.tar.gz - but looking at its contents, it should be part of the sources, as it comes from upstream. Same with the logrotate and the man files. Why are they included in the SBo scripts archive? ___ 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] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware
On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the extra field for the username (clamav) which seems to break things on Slackware. I've just noticed this on several clamav installs which were months out of date, as the cron file never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line is needed - as it works fine for me without it. /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i suggest to don't use the cron-script from upstream, but put the following in /var/spool/cron/crontabs/clamav: 12 * * * * /usr/bin/clamav-unofficial-sigs.sh Johannes ___ 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] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware
The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the extra field for the username (clamav) which seems to break things on Slackware. I've just noticed this on several clamav installs which were months out of date, as the cron file never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line is needed - as it works fine for me without it. Could this be fixed please - unless I'm doing something silly and it should actually work? ___ 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/
