The what should be updated in -current thread

Here is my yearly list again to help PV have a nice overview of what the community wants for updates.

Please reply with the upgrades you want.

dbus --> 1.8.x (1.8.10 is latest)
util-linux --> 2.25.x (2.25.2 is latest)
LVM2 --> 2.02.106
bluez --> 5.20
libevdev --> 1.3
libinput --> please add, 0.6.0
mesa --> 10.3.4 or even wait for 10.4.0
xorg-server 1.16.2
libepoxy --> please add, 1.2
libdrm --> 2.4.58
shared-mime-info --> 1.3
itstool --> 2.0.2
glib2 --> 2.42.1
gobject-introspection --> 1.42.0
atk --> 2.14.0
harfbuzz --> 0.9.35
pango --> 1.36.8
cairo --> 1.14.0
gdk-pixbuf2 --> 2.31.1
at-spi2-core --> 2.14.1
at-spi2-atk --> 2.14.1
gtk+3 --> 3.14.5
dconf --> 0.22
gsettings-desktop-schemas --> 3.14.1
p11-kit --> 0.22.1
glib-networking --> 2.42.0
libsoup --> 2.48.0
gcr --> 3.14.0
iso-codes --> 3.56
libsecret --> 0.18
libnotify --> 0.7.6
lcms2 --> 2.6
gvfs --> 1.22.2
gtk+2 --> 2.24.25
upower --> 0.99.1
librsvg --> 2.40.5
libgsf --> 1.14.30
poppler-data --> 0.4.7
poppler --> 0.26.5
gnome-keyring --> 3.14.0
gnome-themes-standard --> 3.14.2
gucharmap --> 3.14.2

This last item seems to be having 2 additional deps.
appstream-glib
appdata-tools

This is basically my list that I would like to see upgraded.

(the following is a general hint, IMHO, and not related to these particular upgrades)
IMHO, if the proposed upgrades are in form of patches for the existing SlackBuilds (where needed beside a simple version bump) and if it's stated they are tested by the proposer with what's already there, they *might* have more chances to be accepted...

99% of these are version jumps, and 99% is tested.
xorg-server has patches for vmware, and can be posted where needed.

I did not test the new mesa yet.
only 10.2.9 has been tested.

I can create a patch for those version updates, but the version is extracted from the tarball, so a patch can not be made.
for the items where a patch/diff can be made, I will create 1.
hope to have this before end of the week, need to check when I can spend some time for it.

regards,

Bart

that's nice, but just notice what I wrote:
- first I wrote "IMHO": I don't know at all what Pat thinks/has plan to do, I'll just personally think this way is easier for him to verify stuff;
- "the following is [...] not related to these particular upgrades", because, from what I have understood, usually rworkman upgrades/tests most of the stuff you listed and I have no idea of his plans too (which version of X, of the gnome platform, etc.).

Originally Posted by bartgymnast Here is my yearly list again to help PV have a nice overview of what the community wants for updates. Please reply with the upgrades you want. dbus --> 1.8.x (1.8.10 is latest) util-linux --> 2.25.x (2.25.2 is latest) LVM2 --> 2.02.106 bluez --> 5.20 libevdev --> 1.3 libinput --> please add, 0.6.0 mesa --> 10.3.4 or even wait for 10.4.0 xorg-server 1.16.2 libepoxy --> please add, 1.2 libdrm --> 2.4.58 shared-mime-info --> 1.3 itstool --> 2.0.2 glib2 --> 2.42.1 gobject-introspection --> 1.42.0 atk --> 2.14.0 harfbuzz --> 0.9.35 pango --> 1.36.8 cairo --> 1.14.0 gdk-pixbuf2 --> 2.31.1 at-spi2-core --> 2.14.1 at-spi2-atk --> 2.14.1 gtk+3 --> 3.14.5 dconf --> 0.22 gsettings-desktop-schemas --> 3.14.1 p11-kit --> 0.22.1 glib-networking --> 2.42.0 libsoup --> 2.48.0 gcr --> 3.14.0 iso-codes --> 3.56 libsecret --> 0.18 libnotify --> 0.7.6 lcms2 --> 2.6 gvfs --> 1.22.2 gtk+2 --> 2.24.25 upower --> 0.99.1 librsvg --> 2.40.5 libgsf --> 1.14.30 poppler-data --> 0.4.7 poppler --> 0.26.5 gnome-keyring --> 3.14.0 gnome-themes-standard --> 3.14.2 gucharmap --> 3.14.2 This last item seems to be having 2 additional deps. appstream-glib appdata-tools This is basically my list that I would like to see upgraded.

bluez-5.x won't happen if it's up to me; we don't have a bluetooth manager capable of working with it. blueman is being worked on, and I'm trying to help out upstream as best I can with some other parts, but until/unless that happens soon, I don't see bluez5 making it.

libinput - why do we need it? What will use it? Same re libepoxy.

gdk_pixbuf2 - I'd rather stay with 2.30.x until they push out a stable 2.32.x release

I'm not convinced that gnome-themes-standard and gucharmap are worth the upgrade if they add two new deps. Convince me. :-)

xorg-server - I've not messed with 1.16.x, but it's on the TODO at some point.

The rest of these (and more) are in my queue.

Originally Posted by rworkman libinput - why do we need it? What will use it? Same re libepoxy.

Libinput does not seem of any use, as long as we do not add Wayland or KDE 5 to Slackware.
Libepoxy looks like it might ultimately replace GLEW. It is considered for kde-workspace but likewise that will not happen in KDE 4.

Eric

libepoxy will be used by xorg-1.16.x, while my Cinnamon project can make use of libinput since it's needed by clutter, but i haven't really tested and tell whether it's hard dep or soft dep.

I would motion that we might want to look into ConsoleKit2-0.9.2 for testing purposes as an update to ConsoleKit-0.4.5. Bug fixed from Slackware 0.4.5 version include #275761 and #650330 which make patches consolekit-0.2.10-cleanup_console_tags.patch and ck-history-don-t-truncate-frequent-output-to-8-chars.patch unnecessary. These patches do not apply in ConsoleKit2-0.9.2.

Patch consolekit-0.4.2-revert.patch might still be needed. This patch can still be applied.

Also build flag --enable-pam-module=no|yes is now listed as --enable-pam-module without the yes or no identifier. New option --enable-udev-acl has been added.

Libepoxy is a dependency for glamor acceleration in package xorg-server as required for AMD Radeon, Nvidia GeForce (Maxwell only curently), and Intel graphics chips.

Yes, unless we're going for Wayland, libinput is totally useless, that is unless something else uses it, but maybe best for SBo?

Not a big issue, but perhaps looking into Grub-2.02~beta2 as an update to Grub-2.00 might be warranted if any problems are outstanding with Grub currently, plus the package has been stable for a while now.

Grub-2.02~beta2 has been patched for these patches:

• txtHRnXiHYUrM.txt
• grub.dejavusansmono.gfxterm.font.diff
• grub.e75fdee420a7ad95e9a465c9699adc2e2e970440.terminate.efi.several.times.diff

Those patches do not apply.

The patch initrd_naming.patch does still apply safely and could still be useful.

In summary:

/a/grub-2.00 > grub-2.02~beta2
/l/ConsoleKit-0.4.5 > ConsoleKit2-0.9.2

exiv2 to 0.24

Originally Posted by ReaperX7 I would motion that we might want to look into ConsoleKit2-0.9.2 for testing purposes as an update to ConsoleKit-0.4.5. Bug fixed from Slackware 0.4.5 version include #275761 and #650330 which make patches consolekit-0.2.10-cleanup_console_tags.patch and ck-history-don-t-truncate-frequent-output-to-8-chars.patch unnecessary. These patches do not apply in ConsoleKit2-0.9.2. Patch consolekit-0.4.2-revert.patch might still be needed. This patch can still be applied. Also build flag --enable-pam-module=no|yes is now listed as --enable-pam-module without the yes or no identifier. New option --enable-udev-acl has been added. Libepoxy is a dependency for glamor acceleration in package xorg-server as required for AMD Radeon, Nvidia GeForce (Maxwell only curently), and Intel graphics chips. Yes, unless we're going for Wayland, libinput is totally useless, that is unless something else uses it, but maybe best for SBo? Not a big issue, but perhaps looking into Grub-2.02~beta2 as an update to Grub-2.00 might be warranted if any problems are outstanding with Grub currently, plus the package has been stable for a while now. Grub-2.02~beta2 has been patched for these patches: txtHRnXiHYUrM.txt grub.dejavusansmono.gfxterm.font.diff grub.e75fdee420a7ad95e9a465c9699adc2e2e970440.terminate.efi.several.times.diff Those patches do not apply. The patch initrd_naming.patch does still apply safely and could still be useful. In summary: /a/grub-2.00 > grub-2.02~beta2 /l/ConsoleKit-0.4.5 > ConsoleKit2-0.9.2

I've looked at new CK, and it's also in the TODO queue - the problem is that xfce4-power-manager 1.2.x doesn't support it, and I'm not entirely happy with xfpm-1.3.x yet.

Originally Posted by cwizardone exiv2 to 0.24

Added to queue; thanks!

Originally Posted by rworkman Added to queue; thanks!

That's very nice, but KDE must also be recompiled (or even better upgraded to 4.14.x) to be linked against new exiv2

I'll have a crack at xfce-power-manager-1.3.x if I have time to check the build. I plugged CK2 into my existing -current box and it works as is. There is a new flag --enable-udev-acl but I didn't enable it. Robby was it a functionality bug or a build time dependency error?

Of course there's xfce-power-manager-1.4.1 which may have fixed anything between 1.2.x and 1.3.x.

Upgrade xf86-video-mach64 driver to git version? Or at least use this patch - Someone had trouble on 14.1 in this thread and this patch solved the issue. Should probably also be fixed for 14.1 now that I think about it.

Originally Posted by ReaperX7 I'll have a crack at xfce-power-manager-1.3.x if I have time to check the build. I plugged CK2 into my existing -current box and it works as is. There is a new flag --enable-udev-acl but I didn't enable it. Robby was it a functionality bug or a build time dependency error?

If you're using xfce, xfpm won't do any of the suspend/hibernate/shutdown/reboot stuff with CK2. CK2 uses (iirc) new functions for those things to match the systemd function names. I don't think 1.4.x addresses this either, but it has other issues (I meant 1.4.x instead of 1.3.x) - the system tray plugin is gone, and I miss that feature. It's replaced by a panel plugin that monitors battery status, but it doesn't implement the right-click suspend/hibernate feature. It's not a showstopper, but I miss that, so I'm still using 1.2.x.

Re udev-acl, that part requires PAM, and it builds (and presumably works) fine if PAM is present.