Quote:
Originally Posted by montagdude
Kind of related question. I use slackpkg+ for ktown and multilib. During the recent big ktown update (thanks Eric), I did slackpkg install-new, but it didn't find the new Plasma 5 deps that Eric had added. I had to slackpkg install each one that was listed on the blog. Any reason why this would be expected to happen with the ktown repo, or is it more likely a configuration issue on my end?
|
All references to slackpkg also mean with slackpkg+, slackware64-current also could mean slackware-current.
'slackpkg install-new' will only find new slackware64-current packages.
You need to run 'slackpkg install ktown', this will pickup the new ktown packages
I mirror ktown locally. With a major update I do not use slackpkg. I created a short bash script the adds a log, an repeats the install (upgradepkg --install-new --reinstall) as outlined in the README. The only time I use slackpkg is with minor updates to ktown.
With this particular update to ktown running 'slackpkg clean-system' does nothing. Why? qt-gstreamer is part of slackware64-current. In fact if you are not paying attention, running 'slackpkg upgrade-all' will try to upgrade the ktown qt-gstreamer to the slackware64-current qt-gstreamer because the ktown qt-gstreamer no longer exist. You need to run 'removepkg qt-gstreamer' to remove the package. You could also run 'slackpkg remove qt-gstreamer'.
