[SOLVED] slackpkg+ and AlienBob's latest instructions for KDE-5_20.06

aikempshall · 06-20-2020, 05:25 AM

I've got current, multilib and ktown installed in a VirtualBox guest.

I'm a bit confused as to how to proceed with the upgrade to KDE-5_20.06. I'm using slackpkg+.

After reading the README https://slackware.nl/alien-kde/current/latest/README I was going to tackle the early part of the upgrade as follows

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade slackware64 multilib
slackpkg remove consolekit2
slackpkg upgrade ktown

Unfortunately when I was about to embark on the 2nd step I noticed that KDE4 was going to be reinstalled. What have I done wrong.

For previous upgrades I've done

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all

Which has always worked flawlessly.

If I'd done

Code:

slackpkg upgrade-all

instead of

Code:

slackpkg upgrade slackware64 multilib

it looked like that my KDE5 install would have been left intact. Though I wouldn't have been following the letter of AlienBob's README.

So I'm thinking my problem must be in how I'm using slackpkg.

Any suggestions?

Alex

gattocarlo · 06-20-2020, 05:48 AM

Quote:

Originally Posted by aikempshall

For previous upgrades I've done

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all

Which has always worked flawlessly.

If I'd done

Code:

slackpkg upgrade-all

instead of

Code:

slackpkg upgrade slackware64 multilib

it looked like that my KDE5 install would have been left intact. Though I wouldn't have been following the letter of AlienBob's README.

So I'm thinking my problem must be in how I'm using slackpkg.

Any suggestions?

Alex

what I'm presently doing is this:
- comment out ktown from slackpkgplus.conf

- then:

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all

- uncomment ktown in slackpkgplus.conf

- remove ConsoleKit and repeat the passage above.

I didn't finish yet but it seems to be working fine, here.

Hope this helps.
andrea

gegechris99 · 06-20-2020, 05:54 AM

After upgrading to KDE 5_20.06, don't forget the last part in the README:

Quote:

- Move the new X session files into place which SDDM uses to start your
login-session, but first check that you won't accidentally overwrite
any of your customizations:
# mv /usr/share/sddm/scripts/Xsession.new /usr/share/sddm/scripts/Xsession
# mv /usr/share/sddm/scripts/Xsetup.new /usr/share/sddm/scripts/Xsetup

0XBF · 06-20-2020, 08:12 AM

Slackpkg and Slackpkgplus can get a little tricky with the blacklist as well. If you are using slackpkgplus for ktown then you shouldn't have 'kde' listed in the blacklist because it will skip the kde folder of ktown. However, if you comment out ktown from the slackpkgplus.conf file then slackpkg will try to install the kde4 packages, because it no longer sees ktown taking priority there.

In short, you could comment out ktown, blacklist kde, upgrade slackware64, unblacklist kde, uncomment ktown, then upgrade ktown. At least that's how I tackled it. Note that you should run 'slackpkg update' after editing slackpkgplus.conf, or it will complain at you.

Also don't forget to run 'slackpkg install ktown' in the process to pick up the new packages that Eric added. Otherwise you will miss out on elogind and a few other packages.

gattocarlo · 06-20-2020, 09:28 AM

Quote:

Originally Posted by 0XBF

However, if you comment out ktown from the slackpkgplus.conf file then slackpkg will try to install the kde4 packages, because it no longer sees ktown taking priority there.

this is not true with

Code:

slackpkg upgrade-all

unless you already have kde4. But in the original post aikempshall said it was updating ktown (which means no kde4 installed)

upgrade-all only upgrades already installed packages. this is the reason why you also have to run:

Code:

slackpkg install-new
slackpkg install ktown

0XBF · 06-20-2020, 09:42 AM

Actually what I wrote out wasn't 100% accurate. I looked back at how I upgraded yesterday and my approach was to disable slackpkgplus by setting SLACKPKGPLUS=off, then I upgraded slackware with normal slackpkg, with kde blacklisted, then re-enabled slackpkgplus and went on with the ktown upgrade. In that process slackpkg upgrade-all offered to put kde4 back so I had to temporarily blacklist it while slackpkgplus was off. Guess I should have looked at my configs before posting the other response.

gegechris99 · 06-20-2020, 09:57 AM

If you already have KDE-5_20.05, the steps for upgrading to KDE-5_20.06 with slackpkg+ are pretty simple if you read carefully the README.

I upgraded as follows:

Code:

init 3
# log in as root
slackpkg update
slackpkg remove ConsoleKit2
# Install new ktown packages
slackpkg install elogind autoconf-archive kwayland-server plasma-wayland-protocols
# Upgrade all packages for both Slackware and ktown repositories
# Check manually that dbus and polkit packages will be upgraded with the ktown packages
slackpkg upgrade-all
# Move the new X session files into place which SDDM uses to start your
# login-session, but first check that you won't accidentally overwrite
# any of your customizations:
mv /usr/share/sddm/scripts/Xsession.new /usr/share/sddm/scripts/Xsession
mv /usr/share/sddm/scripts/Xsetup.new /usr/share/sddm/scripts/Xsetup

Should the upgrade also included a new kernel, don't forget to do the usual post-upgrade kernel configuration (create initrd.gz, edit /etc/lilo.conf, run lilo)

chrisretusn · 06-20-2020, 11:44 AM

Quote:

Originally Posted by aikempshall

I've got current, multilib and ktown installed in a VirtualBox guest.

I'm a bit confused as to how to proceed with the upgrade to KDE-5_20.06. I'm using slackpkg+.

After reading the README https://slackware.nl/alien-kde/current/latest/README I was going to tackle the early part of the upgrade as follows

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade slackware64 multilib
slackpkg remove consolekit2
slackpkg upgrade ktown

Unfortunately when I was about to embark on the 2nd step I noticed that KDE4 was going to be reinstalled. What have I done wrong.

The highlighted above, specifically slackware64 is why it tried to do KDE4. You should not use multilib this why either.

The README says to remove consolekit2 first.

Based on your post and not knowing the update state of your system. If I was to to this upgrade using slackpkg I would do it this way.

First make sure I am at runlevel 3. If that is what I boot to, then just log out of Plasma switch to root and proceed. If runlevel 4 what the system boots to. Then Ctrl-Alt-F1, login as root, type "init 3" and proceed.

slackpkg update
slackpkg remove consolekit2
slackpkg install multilib #<< Doesn't hurt, if no new packages, nothing will happen.
slackpkg install ktown #<< There are new packages in this ktown.
slackpkg upgrade-all #<< this upgrades everything.
slackpkg clean-system #<< never hurts.
Then complete the other steps outlined in the README

How I will do it.

I mirror the ktown repository locally. This gives me total control over whether or not it gets updated. For example right now I have not refreshed my local mirror, so the updated ktown is not available to slackpkg so running slackpkg will not do anything to upgrade ktown. Note: The README has instruction for creating a local copy.

I have already upgraded to the latest slackware64-current (Fri Jun 19 19:59:04 UTC 2020)

I am refreshing my ktown mirror now as I type this to tackle this upgrade tomorrow morning.

Tomorrow I will:

slackpkg update #<< include the updated ktown mirror
slackpkg remove ConsoleKit2

Next I will upgrade to KDE 5_20.06 using the steps outlined in README

I use this in a script (edited for brevity).

Code:

cd /home/non-slack/ktown/current/latest/
upgradepkg --reinstall --install-new x86_64/deps/*.t?z
upgradepkg --reinstall --install-new x86_64/kde/*/*.t?z

Then complete these steps as outlined in the README

Code:

- Move the new X session files into place which SDDM uses to start your
  login-session, but first check that you won't accidentally overwrite
  any of your customizations:
  # mv /usr/share/sddm/scripts/Xsession.new /usr/share/sddm/scripts/Xsession
  # mv /usr/share/sddm/scripts/Xsetup.new /usr/share/sddm/scripts/Xsetup

Note: The only entries I have in /etc/slackpkg/blacklist are kernel entries.

In my case I will also do the following based on the README:

Add to my lilo.conf:

Code:

# This is needed to run wayland with NVIDEA
append = "nvidia-drm.modeset=1"

Run lilo

Create /etc/profile.d/kwin.sh (and kwin.csh just for gp)

Code:

#!/bin/sh
# KWin needs to use EGLStreams for accelerated graphics support:
export KWIN_DRM_USE_EGL_STREAMS=1

Then reboot.

Log in from runlevel 3 and run "startkwayland"

And see what happens.

pchristy · 06-20-2020, 12:48 PM

I added kde5 to the greylist and then ran slackpkg+. This updated slackware, but left the KDE install alone.

I upgraded kde5 using the upgradepkg --install-new (/path/to/kde5/) route as I've previously found that for some reason, slackpkg+ doesn't always pick up new kde5 files, and there were some very critical ones in this update.

Once I had everything working, I un-greylisted kde5, so everything should upgrade as before now.

A couple of minor things: I've never used wayland before, but since it now appears a s a option, I thought I'd give it a try. everything works except the analogue audio out to my speakers for some reason. It can't even find the analogue out device! It finds the HDMI out, though. Reverting to X restores normal operation.

Also, Dolphin now lists numerically named folders (for example) in the order 1, 10, 11, 2, 3, 4, etc. Never did this before...!

Probably configuration funnies on my part, but I haven't changed anything.

--
Pete

titopoquito · 06-20-2020, 01:27 PM

Quote:

Originally Posted by pchristy

I upgraded kde5 using the upgradepkg --install-new (/path/to/kde5/) route as I've previously found that for some reason, slackpkg+ doesn't always pick up new kde5 files, and there were some very critical ones in this update.

I noticed this as well, but "slackpkg install ktown" presented me the new packages. As far as I can tell it looked complete.

akimmet · 06-20-2020, 02:26 PM

Quote:

Originally Posted by titopoquito

I noticed this as well, but "slackpkg install ktown" presented me the new packages. As far as I can tell it looked complete.

This is the method I have always used to make sure new packages in ktown are installed. So far I've had no problems doing it this way.

chrisretusn · 06-21-2020, 12:59 AM

Quote:

Originally Posted by akimmet

This is the method I have always used to make sure new packages in ktown are installed. So far I've had no problems doing it this way.

That is the correct way. 'slackpkg install-new' ONLY works on slackware packages.

pchristy · 06-21-2020, 03:01 AM

Quote:

Originally Posted by chrisretusn

That is the correct way. 'slackpkg install-new' ONLY works on slackware packages.

Slackpkg yes, but not Slackpkg+. I have an old laptop that I use for testing purposes, and as this has an up-to-date install of slackware and plasma5, I used it as a test bed. Slackpkg+ failed to pick up elogind!

I then went back and used the upgradepkg method, and as well as picking up elogind, it picked up a few other things too (didn't note what they were). So when I came to upgrade my main machine, I used the upgradepkg method for kde5, as detailed above, and everything went smoothly.

The only problem I've encountered so far is that "Notifications" try and use the Xfce daemon instead of Plasma. Not experienced that before, but there is another thread hereabouts about that!

--
Pete

aikempshall · 06-21-2020, 03:06 AM

Quite a lot to take onboard. It's starting to explain why from time to time I was missing packages that install-new didn't prompt.

Anyway I went down this process

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg remove ConsoleKit2
slackpkg install elogind
slackpkg install autoconf-archive kwayland-server plasma-wayland-protocols
slackpkg install ktown
mv /usr/share/sddm/scripts/Xsession.new /usr/share/sddm/scripts/Xsession
mv /usr/share/sddm/scripts/Xsetup.new /usr/share/sddm/scripts/Xsetup

I've now got a working system. The only strange bit is that before the login screen I get a keyboard pop up. Have to close it down before I see the userid icons.

I'll reread this thread a number of times to ensure that I understand everything. I will then revert to the system immediately before I embarked on the latest set of changes. I'm upgrading a VirtualBox guest and had taken a clone of the guest before embarking on the upgrade to KDE-5_20.06. Reading the README gave me the impression this upgrade wasn't going to be straigt forward especially as I had a nagging doubt as to whether I understood all intricacies of slackpkg+. Once everything is in place in 15.0 life should be simpler!

The

Code:

slackpkg install ktown

was a bit of an eye opener for me.

Thanks for all your help. I'll mark this as solved once I've reread, understood and successfully put into practice!

Alex

chrisretusn · 06-21-2020, 03:57 AM

Quote:

Originally Posted by pchristy

Slackpkg yes, but not Slackpkg+. I have an old laptop that I use for testing purposes, and as this has an up-to-date install of slackware and plasma5, I used it as a test bed. Slackpkg+ failed to pick up elogind!

Like I said " 'slackpkg install-new' ONLY works on slackware packages." elogind is part of ktown.

When it comes to a major update to ktown, I never use slackpkg (w/slackpkg+) to upgrade. I use the method outlined in the ktown README file that uses "upgradepkg --install-new --reinstall". I only use slackpkg (w/slackpkg+) on minor updates.