The what should be updated in -current thread

Two worthwhile point upgrades would be:

1. slrn upgraded to 1.0.2
2. irssi upgraded to 0.8.17

Originally Posted by the3dfxdude Please qualify your statement better.

There's no real benefit from going to SDL2 other than simply to have it around, plus most SDL using software still only uses SDL-1.2.x. MPlayer is an example. Plus, SDL2 has updates for Wayland usage, which also is SBo only at this time also.

dmeventd wants to create its fifos in /var/run. But when /var is a separate partition, dmeventd will not start.

May I humbly request that lvm2 be rebuild with the following parameter:

--with-default-dm-run-dir=/run/lvm \

And can the following line be added to "/etc/rc.d/rc.S":

--- rc.S.old    2014-11-29 10:42:00.912305356 +0700
+++ rc.S.new    2014-11-29 10:43:22.456498581 +0700
@@ -65,6 +65,7 @@
 # create some VGs and LVs).
 if [ -r /etc/lvmtab -o -d /etc/lvm/backup ]; then
   echo "Initializing LVM (Logical Volume Manager):"
+  mkdir -p /run/lvm /run/lock/lvm
   # Check for device-mapper support.
   if ! grep -wq device-mapper /proc/devices ; then
     # Try to load a device-mapper kernel module:

I also had to add "/sbin/modprobe -q dm-raid" to be able to setup a raid1 mirror with lvm2.

Thank you.

Here's one good one:

procps-3.2.8 > procps-ng-3.3.10

Procps hasn't been developed on in a few years. Procps-ng is now the focus.

The newer version will have to probably be packaged separate from psmisc, but here's the build instructions for a SlackBuild targeting procps-ng only...

./configure --prefix=/usr                           \
            --exec-prefix=                          \
            --libdir=/usr/lib                       \
            --docdir=/usr/doc/procps-ng-3.3.10      \
            --disable-static                        \
            --disable-kill &&
make &&
make install &&
mv -v /usr/bin/pidof /bin
mv -v /usr/lib64/libprocps.so.* /lib64
ln -sfv ../../lib64/$(readlink /usr/lib64/libprocps.so) /usr/lib64/libprocps.so

Flag --disable-kill is used to avoid installing the kill utility which is included with util-linux.

No patches were required.

whats up with kmod ?
i can't find a changelog anywhere, so idk

gettext and gettext-tools packages can be upgraded to version 0.19.3. No change needed in the SlackBuilds beyond the VERSION. No issue to compile nor run that on a Slackware 14.1, I assume that stands for -current as well. The fixes and enhancements since 0.18.2.1 are worth the upgrade IMO (see relevant part of the NEWS file attached).

Originally Posted by genss whats up with kmod ? i can't find a changelog anywhere, so idk

kmod is maintained by kernel.org, so probably that's why.

I do know the current version I've seen in rotation is kmod-19.

https://www.kernel.org/pub/linux/utils/kernel/kmod/

I pulled this from the archive NEWS file:

kmod 19
=======

- Bug fixes:
- Fix missing CLOEXEC in library
- Fix error message while opening kmod's index

- New features:
- Add kmod(8) man page
- Allow to build with libc's without be32toh()
- Move code around separating common code and data structures into a
shared directory. This allows to share more code between library and
tools, making the binary size of tools shorter.
- Clarify tools vs library licenses
- static-nodes: when writting in tmpfiles format, indicate that
creation of static nodes should only happen at boot. This is used and
required by systemd-217+.

- Improvements to testsuite:
- Add tests for newly created shared/ code
- Improve how tests are declared so there's less boilerplate code for
each test.

Originally Posted by ReaperX7 kmod is maintained by kernel.org, so probably that's why. I do know the current version I've seen in rotation is kmod-19. https://www.kernel.org/pub/linux/utils/kernel/kmod/ I pulled this from the archive NEWS file:

well, the slackware version is 15

http://git.kernel.org/cgit/utils/ker....git/tree/NEWS
i don't see anything game breaking, could be blind though

    - static-nodes: when writing in tmpfiles format, indicate that
      creation of static nodes should only happen at boot. This is used and
      required by systemd-217+.

<off-topic>required or requested?</off-topic>

Originally Posted by Didier Spaier required by systemd-217+.

be honest, you ctrl+f-d it !
well, at least it's not the other way around on that one
(bdw, you can guess who committed that)

dk, i upgraded, simple test seems fine, didn't reboot yet though

It's just for systemd apparently.

Originally Posted by ReaperX7 @Robby We probably should also update UPower: upower-0.9.17 > upower-0.9.23 Not sure if this will help xfce4-power-manager, but might be worth investigating

Got it already, and no, it doesn't have an impact on xfpm :-)

However, another key package might be needed as well: udev-182 > eudev-2.1(udev-217)

I've got udev from system-215 queued up, but it's unclear as to whether there's any real benefit to using 215 versus 208 or even some other version. It might be worth getting 218 when it releases, as that will be the first version to support the mouse database for libinput. Time will tell.

Didier had a Slackbuild for this with the updated handlers for /dev/shm linking to /run/shm properly. I wouldn't prioritize this update if udev-182 can build upower effectively.

What's wrong with /dev/shm/ as is? Is it merely that some other stuff is now expecting it in /run/shm/ (in which case that's easy to fix)?

Originally Posted by rworkman Didier had a Slackbuild for this with the updated handlers for /dev/shm linking to /run/shm properly. I wouldn't prioritize this update if udev-182 can build upower effectively. What's wrong with /dev/shm/ as is? Is it merely that some other stuff is now expecting it in /run/shm/ (in which case that's easy to fix)?

Robby, ReaperX7's quoted statement is wrong, actually I just borrowed your solution to deal with /dev/shm as stated in this post.

Originally Posted by turtleli tmux -> 1.9a Builds/runs on Slackware 64-14.1, no changes to SlackBuild necessary.

Got it; thanks!

---------- Post added Dec 6th, 2014 at 17:22 ----------

Originally Posted by franzen proftpd -> 1.3.4e Here's a patch that enables the filebased Quota-support in proftpd, there were no compile issues. I built/testet it on slackware64 14.0, no messages about "Quotas off". Franzen --- proftpd.SlackBuild.orig 2014-11-27 09:29:49.370789253 +0100 +++ proftpd.SlackBuild 2014-11-27 09:32:15.662474554 +0100 @@ -21,8 +21,8 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. -VERSION=1.3.4c -DIRVER=1.3.4c +VERSION=1.3.4e +DIRVER=1.3.4e BUILD=${BUILD:-1} NUMJOBS=${NUMJOBS:-" -j7 "} @@ -81,11 +81,8 @@ --enable-ctrls \ --enable-ipv6 \ --localstatedir=/var/run \ - --with-modules=mod_radius:mod_ban:mod_readme:mod_ratio:mod_tls:mod_wrap:mod_ctrls_admin \ + --with-modules=mod_radius:mod_ban:mod_readme:mod_ratio:mod_tls:mod_wrap:mod_ctrls_admin:mod_quotatab:mod_qu otatab_file \ --build=$ARCH-slackware-linux -# This caused funny messages about "Quotas off" with every FTP command, -# and mod_wrap gets a compile error: -# --with-modules= ... mod_quota ... make $NUMJOBS || make || exit 1 make install DESTDIR=$PKG || exit 1

Got it; thanks!

Originally Posted by OldHolborn smartmontools-6.3

Got it; thanks!