[SOLVED] Requests for -current (20151216)

mats_b_tegner · 06-17-2017, 07:20 AM

https://imagemagick.org/script/changelog.php

Quote:

2017-06-10 6.9.8-10 Cristy <quetzlzacatenango@image...>
* Release ImageMagick version 6.9.8-10, GIT revision 11637:eb6f363:20170610.

2017-06-10 6.9.8-10 Cristy <quetzlzacatenango@image...>
* Introduce SetMagickSecurityPolicy() (MagickCore) and
MagickSetSecurityPolicy() (MagickWand) to set the ImageMagick security
policy (reference https://github.com/ImageMagick/ImageMagick/issues/407).

https://www.imagemagick.org/download....9.8-10.tar.xz
https://www.imagemagick.org/download...-10.tar.xz.asc

gmgf · 06-17-2017, 07:39 AM

Quote:

Originally Posted by gmgf

ModemManager-1.6.6:

https://www.freedesktop.org/software...r-1.6.6.tar.xz

1.6.8 is available now:

https://www.freedesktop.org/software...r-1.6.8.tar.xz

(1.6.6 and 1.6.8 are two bugs fix version)

USUARIONUEVO · 06-17-2017, 06:03 PM

libbluray-1.0.1
ftp://ftp.videolan.org/pub/videolan/...-1.0.1.tar.bz2

libwacom-0.25
https://sourceforge.net/projects/lin...m-0.25.tar.bz2

rworkman · 06-17-2017, 09:53 PM

Quote:

Originally Posted by gmgf

For Robby, i have tested the new udisks-2.7.0, on current,

https://github.com/storaged-project/udisks/releases

This new release is based on libblockdev, it need, dmraid (maybe optionnal), libbytesize, volum_key, and libblockdev.

(i have make all needed packages)

These changes leave me a little perplexed, but, it seem this new release work correctly

Yeah, I'm trying out both of them locally and both *seem* fine. I'll admit that I'm not convinced to jump on the libblockdev stuff yet, but we'll see.

gmgf · 06-17-2017, 10:23 PM

Quote:

Originally Posted by rworkman

Yeah, I'm trying out both of them locally and both *seem* fine. I'll admit that I'm not convinced to jump on the libblockdev stuff yet, but we'll see.

yes, i agree.

atelszewski · 06-18-2017, 05:13 PM

Hi,

I tried to compile libclc-20160921_520743b with LLVM 4.0 and it was failing with:

Code:

./utils/prepare-builtins.cpp:1:10: fatal error: 'llvm/Bitcode/ReaderWriter.h' file not found

I updated libclc to the latest (as of now) git_20170602_1cb3fbf and it compiled fine.
Looks like LLVM 4.0 introduced API changes, and you compiled libclc-20160921_520743b just before upgrading to LLVM 4.0, so you didn't encounter the error.
Mesa-17.1.2 seems to compile fine against libclc-git_20170602_1cb3fbf too.

Just a heads up.

P.S. I've been doing all of this on 14.2, but that should be irrelevant.

--
Best regards,
Andrzej Telszewski

Didier Spaier · 06-18-2017, 06:48 PM

Some parts of the Releases Notes may provide food for thoughts for upcoming Slackware version and derivatives.
Some examples:

2.2.6 Move to "Modern" GnuPG
2.2.8 A new method for naming network interfaces
5.1.1 Late mounting of /usr is no longer supported (make /usr a separate partition should be explicitly discouraged anyway)
5.3.1 Older ciphers and SSH1 protocol disabled in OpenSSH by default
5.3.3 Desktops will migrate to libinput Xorg driver
5.3.4 Upstart removed [Just kidding. But be happy, OpenRC is still supported ]
5.3.9 net-tools will be deprecated in favor of iproute2 (both are shipped in Slackware)
A.4 Upgrade legacy locales to UTF-8 (include something about that in "Changes and Hints"?)

rworkman · 06-18-2017, 08:11 PM

Quote:

Originally Posted by Didier Spaier

Some parts of the Releases Notes may provide food for thoughts for upcoming Slackware version and derivatives.
Some examples:

2.2.6 Move to "Modern" GnuPG

Done. Should be doc'd already in C&H unless I forgot to push those changes.

Quote:

2.2.8 A new method for naming network interfaces

Nope. I guess it's technically there if someone needs it, but the number of reports I've gotten about it is zero. I suspect that anyone who actually needs that manages to figure it out.

Quote:

5.1.1 Late mounting of /usr is no longer supported (make /usr a separate partition should be explicitly discouraged anyway)

This hasn't been expected to work for a while, but meh, if someone tries and it works, good for them.

Quote:

5.3.1 Older ciphers and SSH1 protocol disabled in OpenSSH by default

Yep, probably worth a mention.

Quote:

5.3.3 Desktops will migrate to libinput Xorg driver

In theory, nobody should even notice this.

Quote:

5.3.9 net-tools will be deprecated in favor of iproute2 (both are shipped in Slackware)

This one is doubtful, but I do have a work in progress on it. However, I've received zero feedback on it from anyone, even though I *know* it has bugs.
https://harrier.slackbuilds.org/cgit...slacknetsetup/
I'd love to get feedback (and especially patches for bugs - I lost interest since nobody seems to have tried it).

Quote:

A.4 Upgrade legacy locales to UTF-8 (include something about that in "Changes and Hints"?)

Suggested "something" to include? :-)

cwizardone · 06-19-2017, 09:48 AM

Mesa 17.1.3.

The release notes, https://www.mesa3d.org/relnotes/17.1.3.html

CTM · 06-19-2017, 01:42 PM

Quote:

Originally Posted by rworkman

This one is doubtful, but I do have a work in progress on it. However, I've received zero feedback on it from anyone, even though I *know* it has bugs.
https://harrier.slackbuilds.org/cgit...slacknetsetup/
I'd love to get feedback (and especially patches for bugs - I lost interest since nobody seems to have tried it).

One major reason to go for iproute2 is that it has full support for network namespaces. Yesterday I set up a Slackware container whose host-side veth adapter was in a non-main network namespace and found that I wasn't able to get any network connectivity without also installing iproute2 inside the container - if nothing else, could that at least be added to the default package list in source/ap/lxc/lxc-slackware.in?

Didier Spaier · 06-19-2017, 02:35 PM

Quote:

Originally Posted by CTM

if nothing else, could that at least be added to the default package list in source/ap/lxc/lxc-slackware.in?

Done here, at least.

CTM · 06-19-2017, 02:36 PM

Separately from the iproute2 issue above, the default "minimal" package list for Slackware containers is missing a few packages that mean some tools won't work inside containers:

Code:

/usr/bin/setpriv
        libcap-ng.so.0 => not found
/usr/bin/wget
        libunistring.so.0 => not found
/usr/sbin/ninfod
        libgnutls-openssl.so.27 => not found
/bin/ping6
        libgnutls-openssl.so.27 => not found
/sbin/udevadm
        libkmod.so.2 => not found
/sbin/udevd
        libkmod.so.2 => not found
/sbin/tipc
        libmnl.so.0 => not found
/sbin/arpd
        libdb-4.8.so => not found
/usr/libexec/gnupg/gpgkeys_ldap
        libsasl2.so.3 => not found
/usr/libexec/gnupg/gpgkeys_curl
        libsasl2.so.3 => not found
/usr/libexec/gnupg/gpgkeys_hkp
        libsasl2.so.3 => not found

The wget breakage in particular is a bit of a problem.

The following packages need to be added to the package list in source/ap/lxc/lxc-slackware.in to make these programs usable:

a/kmod
l/db48
l/libcap-ng
l/libffi
l/libtasn1
l/libunistring
n/cyrus-sasl
n/gnutls
n/libmnl
n/nettle
n/p11-kit

Didier Spaier · 06-19-2017, 02:50 PM

Done in the same place. I don't know if the changes I have already proposed will be accepted, however testing would help (I blindly copied your list).

CTM · 06-19-2017, 03:35 PM

Quote:

Originally Posted by Didier Spaier

Done in the same place. I don't know if the changes I have already proposed will be accepted, however testing would help (I blindly copied your list).

Thanks on both counts, Didier - fingers crossed

franzen · 06-20-2017, 03:51 AM

Quote:

Originally Posted by CTM

Separately from the iproute2 issue above, the default "minimal" package list for Slackware containers is missing a few packages that mean some tools won't work inside containers:

Code:

...
/sbin/udevadm
        libkmod.so.2 => not found
/sbin/udevd
        libkmod.so.2 => not found

...

The following packages need to be added to the package list in source/ap/lxc/lxc-slackware.in to make these programs usable:

a/kmod

"kmod - Program to manage Linux Kernel modules"
I don't think this will be useful in a container.

Some packages have many tools inside, with diffrent dependencies, without corresponding to each other.
So a package may have still half of its functionality, even if not all dependencies are covered.
The minimal-installation may end up very big, if all dependencies from all further dependencies have to be covered.

e.g. the eudev package will do almost nothing in a container, therefor kmod is not needed as a dependency for it.
But some other's package core functionality may need libudev.so from the eudev package.

Johannes