Fri Jul 27 21:01:22 UTC 201820180727210122

Hey folks, my first order of business here needs to be a huge thank you to
everyone who has donated at https://paypal.me/volkerdi to help keep this
project going. As most of you are already aware by now, the financal situation
here at Slackware HQ has not been great for many years, including not getting
any pay for the last two years and forcing me (and my family) to live very
frugally while I continued to work on the project hoping I'd figure out a way
to actually monitize it by the time that Slackware 15.0 is ready for release.
I'm not trying to cast any blame regarding the situation. Really, I can only
blame myself for not trying to build my own ship years ago when things began
to not really work out. I'm still looking into sustainable funding options
such as Patreon or Liberapay (or perhaps both), and I'm open to other ideas.
I'm no longer in immediate danger of going broke, and I'm no longer
entertaining the notion of joining my friends at the local potato chip factory
in order to pay my bills. :) My family is grateful and humbled by the support
we've received. Hope we'll be able to keep this project going for a long time.
Also, I realize that the website lacks updates and needs attention and I will
need to find some time to devote to that. I've never been much of a website
designer, and the slackware.com site is basically left over from work done by
former Walnut Creek / BSDi employees. I've never seen able to make much sense
of the SQL backend. The interface to edit and post articles is clunky (and
I'm not sure the PHP for that even works any more). When I've posted articles
in recent years, I've done so by editing the main page already processed from
PHP into HTML, which is pretty darn messy as I'm sure you can imagine. I tend
to prioritize the distribution itself over other demands on my time - that's
clearly a lot to do with how things ended up the way they did.
So, I guess that's the report for now. Lots more work to do and not enough
time to do it in... that part I don't see changing moving forward. :)
Thanks very much again. I'll do my best to keep you all posted.
  - Pat
a/file-5.34-x86_64-1.txz:  Upgraded.
a/kernel-firmware-20180727_b01151b-noarch-1.txz:  Upgraded.
a/kernel-generic-4.14.58-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.14.58-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.14.58-x86_64-1.txz:  Upgraded.
d/gcc-8.2.0-x86_64-1.txz:  Upgraded.
d/gcc-brig-8.2.0-x86_64-1.txz:  Upgraded.
d/gcc-g++-8.2.0-x86_64-1.txz:  Upgraded.
d/gcc-gfortran-8.2.0-x86_64-1.txz:  Upgraded.
d/gcc-gnat-8.2.0-x86_64-1.txz:  Upgraded.
d/gcc-go-8.2.0-x86_64-1.txz:  Upgraded.
d/gcc-objc-8.2.0-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.14.58-x86-1.txz:  Upgraded.
d/libtool-2.4.6-x86_64-9.txz:  Rebuilt.
  Recompiled to update embedded GCC version number.
k/kernel-source-4.14.58-noarch-1.txz:  Upgraded.
   CRASH_DUMP n -> y
   KEXEC n -> y
  +KEXEC_JUMP y
  +PROC_VMCORE y
l/babl-0.1.54-x86_64-1.txz:  Upgraded.
l/gegl-0.4.6-x86_64-1.txz:  Upgraded.
l/libart_lgpl-2.3.21-x86_64-2.txz:  Removed.
  This actually hasn't been needed by any Slackware package since koffice in
  KDE3, and this particular version won't work with the Trinity Desktop
  Environment, which is essentially a fork of KDE 3.5 updated to compile and
  run with modern libraries and development tools. I can't see much point in
  keeping it around. Thanks to _gin.
n/NetworkManager-1.12.2-x86_64-1.txz:  Upgraded.
n/dhcpcd-7.0.7-x86_64-1.txz:  Upgraded.
x/libinput-1.11.3-x86_64-1.txz:  Upgraded.
extra/tigervnc/tigervnc-1.9.0-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.

2 files changed, 1 insertions, 55 deletions

diff --git a/source/n/NetworkManager/NetworkManager.SlackBuild b/source/n/NetworkManager/NetworkManager.SlackBuild
index b50b603ac..9f370bc8d 100755
--- a/source/n/NetworkManager/NetworkManager.SlackBuild
+++ b/source/n/NetworkManager/NetworkManager.SlackBuild
@@ -27,7 +27,7 @@ cd $(dirname $0) ; CWD=$(pwd)
 
 PKGNAM=NetworkManager
 VERSION=${VERSION:-$(echo $PKGNAM-*.tar.?z* | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
-BUILD=${BUILD:-3}
+BUILD=${BUILD:-1}
 
 # Automatically determine the architecture we're building on:
 MARCH=$( uname -m )
diff --git a/source/n/NetworkManager/patches/NM-1.12.0-e205664ba8c25939f1678d1b078a67989c180046.patch b/source/n/NetworkManager/patches/NM-1.12.0-e205664ba8c25939f1678d1b078a67989c180046.patch
deleted file mode 100644
index 3c17434b7..000000000
--- a/source/n/NetworkManager/patches/NM-1.12.0-e205664ba8c25939f1678d1b078a67989c180046.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-From e205664ba8c25939f1678d1b078a67989c180046 Mon Sep 17 00:00:00 2001
-From: Beniamino Galvani <bgalvani@redhat.com>
-Date: Fri, 6 Jul 2018 15:54:16 +0200
-Subject: [PATCH] manager: accept non-null device for VPN activations
-
-Commit 10753c36168a ("manager: merge VPN handling into
-_new_active_connection()") added a check to fail the activation of
-VPNs when a device is passed to ActivateConnection(), since the device
-argument is ignored for VPNs.
-
-This broke activating VPNs from nm-applet as nm-applet sets both the
-specific_object (parent-connection) and device arguments in the
-activation request.
-
-Note that we already check in _new_active_connection() that when a
-device is supplied, it matches the device of the parent
-connection. Therefore, the check can be dropped.
-
-Reported-by: Michael Biebl <biebl@debian.org>
-Fixes: 10753c36168a82cd658df8a7da800960fddd78ed
-
-https://github.com/NetworkManager/NetworkManager/pull/159
----
- src/nm-manager.c | 16 +---------------
- 1 file changed, 1 insertion(+), 15 deletions(-)
-
-diff --git a/src/nm-manager.c b/src/nm-manager.c
-index 67c71fea91..4c4b6bb5a9 100644
---- a/src/nm-manager.c
-+++ b/src/nm-manager.c
-@@ -4611,21 +4611,7 @@ validate_activation_request (NMManager *self,
- 		}
- 	}
- 
--	if (is_vpn && device) {
--		/* VPN's are treated specially. Maybe the should accept a device as well,
--		 * however, later on during activation, we don't handle the device.
--		 *
--		 * Maybe we should, and maybe it makes sense to specify a device
--		 * when activating a VPN. But for now, just error out.  */
--		g_set_error_literal (error,
--		                     NM_MANAGER_ERROR,
--		                     NM_MANAGER_ERROR_UNKNOWN_DEVICE,
--		                     "Cannot specify device when activating VPN");
--		return NULL;
--	}
--
--	nm_assert (   ( is_vpn && !device)
--	           || (!is_vpn && NM_IS_DEVICE (device)));
-+	nm_assert (is_vpn || NM_IS_DEVICE (device));
- 
- 	*out_device = device;
- 	*out_is_vpn = is_vpn;
-