[Slackbuilds-users] Updates - 20180217.1

[Willy Sudiarto Raharjo]

Hi folks,

We have another busy week and we have some interesting update on this batch:
- LibreOffice is now sync with libreoffice at 6.0.1
- wine is updated  to 3.0
- postgresql is updated to 10.2
- intel-microcode is reverted to previous release after upstream recall
- vlc is updated to 3.0.0
- rust is updated to 1.24.0
- google-earth is updated to 7.3.1.4507
- skypeforlinux is updated to 8.15.0.4

Patrick has pushed a new GCC and Kernel in Slackware{64} 14.2 to support
full mitigation against Spectre v2. Please make sure to upgrade to that
version if you haven't done so.

Welcome to the Year of the Earth Dog according to the Chinese Calendar


Sat Feb 17 00:43:50 UTC 2018
academic/aliview: Added (Alignment viewer and editor).
academic/genius: Updated for version 1.0.23.
academic/qcl: Added (A Programming Language for Quantum Computers).
desktop/dunst: Updated for version 1.3.1, make cleanup
desktop/jgmenu: Updated for version 0.8.1.
desktop/kwalletcli: Updated for version 3.01.
desktop/obbrowser: Updated for version 0.09.
desktop/oranchelo-icon-theme: Updated for version 0.7.5.7.
development/Sphinx: Updated for version 1.6.7.
development/bas55: Updated for version 1.13.
development/d-tools: Updated for version 2.078.3
development/dmd: Updated for version 2.078.3
development/dwarf: Fixed md5sum.
development/eclim: Updated for version 2.7.2.
development/extra-cmake-modules: Updated for version 5.43.0.
development/jupyter-ipykernel: Updated for version 4.8.1.
development/kotlin: Updated for version 1.2.21.
development/obnc: Updated for version 0.11.1.
development/pkgconf: Updated for version 1.4.2.
development/rust: Updated for version 1.24.0.
development/tanya: Updated for version 0.7.8
development/universal-ctags: Updated for version 30ce6ee
games/Genesis-Plus-GX: Updated for version 2018.01.31_726b711.
games/crispy-doom: Updated for version 5.1.
games/cyphesis: Patched to build with postgresql-10.2.
games/instead: Updated for version 3.2.0.
games/javacpc: Updated for version 2.9.6.
games/nethack: Switch to i586, fix maintainer typo.
gis/gj2ascii: Added (render spatial vectors as ASCII).
gis/google-earth: Updated for version 7.3.1.4507.
gis/gpxsee: Added (GPX viewer and analyzer).
gis/openorienteering-mapper: Updated for version 0.8.0.
graphics/PureRef: Unsupported except on x86_64.
libraries/appstream-glib: Updated for version 0.7.6.
libraries/efivar: Updated for version 34.
libraries/leptonica: Updated for version 1.75.2.
libraries/libechonest: Fixed download url.
libraries/liblxi: Updated for version 1.11.
libraries/libwebp: Updated for version 0.6.1.
libraries/live555: Updated for version 2018.02.12
libraries/tbb: Updated for version 2018u2.
libraries/wxSQLite3: Updated for version 3.5.9.
misc/Publican: Added (Tool for publishing DocBook XML).
misc/discount: Updated for version 2.2.2 + new maintainer.
misc/wkhtmltox: Added (Render HTML into PDF).
multimedia/mpv: Updated for version 0.27.2, deps.
multimedia/opera-ffmpeg-codecs: Updated for version 64.0.3282.119.
multimedia/sfnt2woff: Fixed md5sum.
multimedia/smplayer: Updated for version 18.2.0.
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for v 64.0.3282.167.
multimedia/vlc: Updated for version 3.0.0
network/asciinema: Updated for version 2.0.0.
network/exim: Updated for version 4.90.1.
network/frostwire: Updated for version 6.6.2 + new maintainer.
network/lxi-tools: Updated for version 1.18.
network/opera-developer: Updated for version 52.0.2857.0.
network/opera: Added Terms, Privacy and EULA files.
network/qutebrowser: Updated for version 1.1.1.
network/skypeforlinux: Updated for version 8.15.0.4.
network/slimjet: Remove icons folder.
network/slimjet: Updated for version 18.0.1.0.
network/speedtest-cli: Updated for version 2.0.0.
network/vivaldi: Updated for version 1.14.1077.50.
network/xdman: Updated for version 2018.7.1.2.
network/yle-dl: Updated for version 2.31.
office/LibreOffice: Updated for version 6.0.1.1
office/krop: Updated for version 0.5.0.
office/latexdiff: Added (diff utility for LaTeX files).
office/onlyoffice-desktopeditors: Updated for version 4.8.7.392.
perl/perl-CGI-Application: Added (Framework for web-applications).
perl/perl-CSS: Added (Object oriented Cascading Style Sheets).
perl/perl-Class-ISA: Added (search path for class's ISA tree).
perl/perl-DateTime-Format-DateParse: Added (Date::Parse parser).
perl/perl-File-Inplace: Added (in-place editing of files).
perl/perl-HTML-FormatText-WithLinks-AndTables: Added (HTML to Text).
perl/perl-HTML-FormatText-WithLinks: Added (HTML to text).
perl/perl-HTML-Formatter: Added (Base class for HTML formatters).
perl/perl-HTML-WikiConverter-Markdown: Added (HTML to Markdown).
perl/perl-HTML-WikiConverter: Added (Convert HTML to wiki markup).
perl/perl-Lingua-EN-Fathom: Added (readability of English text).
perl/perl-Lingua-EN-Syllable: Added (short description of app).
perl/perl-Locale-Maketext-Gettext: Added (gettext and Maketext).
perl/perl-Locale-Msgfmt: Added (Compile .po files to 

Re: [Slackbuilds-users] lilo

[Didier Spaier]

Le 16/02/2018 à 20:12, Tim Dickson a écrit :
I still have to work on liloconfig, but if I find somewhere I can use online I 
can post the current patch for those interested.

If you send me just the patch for lilo itself I can test it.

Didier 
___
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] lilo

[Tim Dickson]

On 16/02/2018 18:18, Ythogtha wrote:

hi all, this may be off-topic,  as lilo comes with slackware, but I have
created a patch to allow lilo to work with nvme disks. I am working on
patching liloconf  to do the same.there are 2 questions I have, as lilo
is "no longer developed" - but works just fine - apart from for nvme
disks :-)
1. what is the best way of seeing if patrick is interested in the patch, and
2. is anyone interested in testing the patch?
At the moment I have patched the source for lilo, and after manually
configuring the lilo.conf it works for me, but I only have 1 nvme disk,
so am not sure how it presents for multiple nvme "disks".
a quick
dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
   comes up with a match. where previously I had to use sys/extlinux as
lilo refused to work.
specifically if someone has more than 1 nvme drive i am interested in
the output from
cat /proc/devices
   and
cat /proc/partitions

many thanks, Tim

From what I've read, it seems that Patrick is mostly the de facto
maintainer of lilo because no other distribution seems to really use it anymore.
This nvme problem is really the only one that had bothered me recently,
and I didn't dig enough to find a solution, but I am very glad that you did ! My
work laptop has an nvme main disk, and I had to put a /boot partition on the
secondary non-nvme disk for lilo to work.

So, I, for one, would be ok - and happy - to test your patch, although
not on a real 2-nvme system, but on 2 nvme systems ;)

Maybe, for easy testing purposes, you could create some sort of
lilo-nvme SlackBuild ? I don't know if it is worth it, but it might make for
easier testing.

basically it would just be the existing slackware build with the extra 
patches applied.
 I have a test qemu virtual machine with up to 3 nvme drives on it, as 
well as a single real nvme drive.
to Richard Shepard.  nvme drives use the pcie bus instead of sata (and 
so can work up to 3 times faster).
Amaude is correct. nvme disks have device macjor 259, and minor number 
starts at 0 and goes up one at a time, as you add partitions or opther 
nvme devices. My patch increases the size of the block device table, so 
that nvme devices (typically device 252) are visible in the table, and 
if an nvme device is present, it allows the  259 major device to be used 
by lilo.  I still have to work on liloconfig, but if I find somewhere I 
can use online I can post the current patch for those interested. PS. 
usuall disclaimer. it works for me YMMV. don't test on real system.

___
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] lilo

[Rich Shepard]

On Fri, 16 Feb 2018, Arnaud wrote:


It's a problem of some kind of ID number which isn't recognised by lilo
for nvme disks, it thinks the disk is something else and refuses to
install itself there.


Arnaud,

  Thanks for explaining. I've used lilo for 20+ years and have no issues
with it; I like it for its simplicity and the fact that, so far, it Just
Works.

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/

Re: [Slackbuilds-users] lilo

[Arnaud]

It's a problem of some kind of ID number which isn't recognised by lilo for 
nvme disks, it thinks the disk is something else and refuses to install itself 
there.

Le 16 février 2018 19:42:15 GMT+01:00, Rich Shepard  
a écrit :
>On Fri, 16 Feb 2018, Ythogtha wrote:
>
>> This nvme problem is really the only one that had bothered me
>recently,
>> and I didn't dig enough to find a solution, but I am very glad that
>you
>> did ! My work laptop has an nvme main disk, and I had to put a
>> /boot partition on the secondary non-nvme disk for lilo to work.
>
>Excuse my ignorance, but a web search did not tell me if a NVMe disk is
>different from a SSD; I assume so, but aren't they both non-volitile
>memory
>disks? Is the difference the bus: SATA vs PCI-express?
>
>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/

-- 
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/

Re: [Slackbuilds-users] lilo

[Rich Shepard]

On Fri, 16 Feb 2018, Ythogtha wrote:


This nvme problem is really the only one that had bothered me recently,
and I didn't dig enough to find a solution, but I am very glad that you
did ! My work laptop has an nvme main disk, and I had to put a
/boot partition on the secondary non-nvme disk for lilo to work.


  Excuse my ignorance, but a web search did not tell me if a NVMe disk is
different from a SSD; I assume so, but aren't they both non-volitile memory
disks? Is the difference the bus: SATA vs PCI-express?

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/

Re: [Slackbuilds-users] lilo

[Ythogtha]

> hi all, this may be off-topic,  as lilo comes with slackware, but I have 
> created a patch to allow lilo to work with nvme disks. I am working on 
> patching liloconf  to do the same.there are 2 questions I have, as lilo 
> is "no longer developed" - but works just fine - apart from for nvme 
> disks :-)
> 1. what is the best way of seeing if patrick is interested in the patch, and
> 2. is anyone interested in testing the patch?
> At the moment I have patched the source for lilo, and after manually 
> configuring the lilo.conf it works for me, but I only have 1 nvme disk, 
> so am not sure how it presents for multiple nvme "disks".
> a quick
> dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
>   comes up with a match. where previously I had to use sys/extlinux as 
> lilo refused to work.
> specifically if someone has more than 1 nvme drive i am interested in 
> the output from
> cat /proc/devices
>   and
> cat /proc/partitions
> 
> many thanks, Tim

From what I've read, it seems that Patrick is mostly the de facto
maintainer of lilo because no other distribution seems to really use it anymore.
This nvme problem is really the only one that had bothered me recently,
and I didn't dig enough to find a solution, but I am very glad that you did ! My
work laptop has an nvme main disk, and I had to put a /boot partition on the
secondary non-nvme disk for lilo to work.

So, I, for one, would be ok - and happy - to test your patch, although
not on a real 2-nvme system, but on 2 nvme systems ;)

Maybe, for easy testing purposes, you could create some sort of
lilo-nvme SlackBuild ? I don't know if it is worth it, but it might make for
easier testing.

-- 
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/

Re: [Slackbuilds-users] libechonest: upstream site moved - tarball file format changed

[Matteo Bernardini]

2018-02-16 19:03 GMT+01:00 Eduardo Sanchez :
> Hi there:
>
> I'm trying to rebuild clementine and one of its dependencies is
> libechonest.
>
> 1. Bear in mind that the software seems to be available here and not at
> the url provided in SBo:
>
> https://github.com/lfranchi/libechonest
>
> 2. The tarball format is now tar.gz and not tar.bz2 as previously
> expected.

Hi Eduardo,

I provided an alternative donwload url and committed it in my git
branch: it should be fixed also in the main repository soon.

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] libechonest: upstream site moved - tarball file format changed

[Eduardo Sanchez]

Hi there:

I'm trying to rebuild clementine and one of its dependencies is
libechonest.

1. Bear in mind that the software seems to be available here and not at
the url provided in SBo:

https://github.com/lfranchi/libechonest

2. The tarball format is now tar.gz and not tar.bz2 as previously
expected.

Thanks


Eduardo

-- 
Eduardo Sánchez Gauto, Abog., Th.M.
Abogado - Traductor Público Matriculado Inglés - Español
Oficina: https://goo.gl/maps/mccgBNM7Zw32
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow - 
Teléfono: (0991) 755-355 - Asunción, Paraguay 
==


pgpSXbAZxyywn.pgp
Description: OpenPGP digital signature
___
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] lilo

[Didier Spaier]

Hello Tim,

Le 16/02/2018 à 11:38, Tim Dickson a écrit :
> hi all, this may be off-topic,  as lilo comes with slackware, but I
> have created a patch to allow lilo to work with nvme disks. I am
> working on patching liloconf to do the same.there are 2 questions I
> have, as lilo is "no longer developed" - but works just fine - apart
> from for nvme disks :
> 1. what is the best way of seeing if patrick is interested in the
> patch

Just post in the Slackware forum. Ptricks reads all threads.
As an example he ecently applied in -current a patch that I have
proposed there more than one year ago and almost forgot about.

> 2. is anyone interested in testing the patch?

I am. if that works I will provide an updated package in Slint and ship
it in the next Slint ISO, among other enhancements of the installer.

> At the moment I have patched the source for lilo, and after manually
> configuring the lilo.conf it works for me, but I only have 1 nvme
> disk, so am not sure how it presents for multiple nvme "disks".
> a quick > dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
> comes up with a match. where previously I had to use sys/extlinux as
> lilo refused to work. Specifically if someone has more than 1 nvme
> drive i am interested in the output from
> cat /proc/devices
>  and
> cat /proc/partitions

You can do this: Fire up a VirtualBox virtual machine with the VB
extensions and set up two NVME devices. That's how I have tested patches
for NVME handling (now applied in -current) when using UEFI, as I have
no "physical" NVME device.

Cheers, Didier
___
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] lilo

[Tim Dickson]

hi all, this may be off-topic,  as lilo comes with slackware, but I have 
created a patch to allow lilo to work with nvme disks. I am working on 
patching liloconf  to do the same.there are 2 questions I have, as lilo 
is "no longer developed" - but works just fine - apart from for nvme 
disks :-)

1. what is the best way of seeing if patrick is interested in the patch, and
2. is anyone interested in testing the patch?
At the moment I have patched the source for lilo, and after manually 
configuring the lilo.conf it works for me, but I only have 1 nvme disk, 
so am not sure how it presents for multiple nvme "disks".

a quick
dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
 comes up with a match. where previously I had to use sys/extlinux as 
lilo refused to work.
specifically if someone has more than 1 nvme drive i am interested in 
the output from

cat /proc/devices
 and
cat /proc/partitions

many thanks, Tim
___
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] Is it worthwhile for a ports like package manager for Slackware

[Noryungi]

If you go that way, may I draw your attention to the fact that NetBSD
pkgsrc exists and works very well under Slackware?

Why reinvent the wheel?

On Feb 16, 2018 09:29, "Jheengut Pritvi"  wrote:

> With the forthcoming of Slackware 15.0, I have been nostalgic of the
> days when I tried crazy thing with my Slackbox. One of those was using
> BSD's ports and portage within Slackware. It was a succees and a
> failure too. In those times, I was not using slackbuilds.org.
> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.
>
> What is your opinion?
> ___
> 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] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

With the forthcoming of Slackware 15.0, I have been nostalgic of the
days when I tried crazy thing with my Slackbox. One of those was using
BSD's ports and portage within Slackware. It was a succees and a
failure too. In those times, I was not using slackbuilds.org.
The big question:::
Is it worthwhile for a ports/portage/pacman like package manager for
Slackware that manages both binary and source packages?


It could be tool on top of pkgtool and sbopkg.

What is your opinion?
___
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/