SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
### 5.0.1 - 29/03/2024
- Updated:
* Updated to check upgrade packages against all repositories (slpkg upgrade --repository='*' --check)
- Bugfixes:
* Upgrade packages for -current version (Thanks to Marav)
Two things behave differently than I would expect:
1. When I run `slpkg -U`, all dependencies for all packages which can be upgraded are ticked on by default even when they are up to date. Hence also all dependencies are rebuild/updated even if they are already up to date.
2. When dependencies are installed with `slpkg -U`, it will always use `upgradepkg`, if however a new dependency was added since the last update, this does not work since there is no package that could be upgraded. In this case the new dependency should be installed and not "upgraded"
At least the second point is clear bug in my opinion.
Two things behave differently than I would expect:
1. When I run `slpkg -U`, all dependencies for all packages which can be upgraded are ticked on by default even when they are up to date. Hence also all dependencies are rebuild/updated even if they are already up to date.
2. When dependencies are installed with `slpkg -U`, it will always use `upgradepkg`, if however a new dependency was added since the last update, this does not work since there is no package that could be upgraded. In this case the new dependency should be installed and not "upgraded"
At least the second point is clear bug in my opinion.
### 5.0.2 - 30/03/2024
- Updated:
* Updated for coding style
* Updated tomli import for -current version
* Updated for "ticked on/off" packages if they are already up-to-date #181
- Bugfixes:
* Check for custom upgrade packages (Thanks to Marav)
* Fixed to install packages when run upgrade command #180
Hello, is there a possibility to push updates to ponce repo?
Hi rizitis,
the scope of the unofficial repository for current is to host fixes to let SBo's scripts build on current, is not for parallel-maintaining script to have the latest software, so if the update fixes a building issue on current with the script is welcome but if it's just an update you better check with the maintainer and propose the update to her/him.
Hey ponce thanks for answer, this new release of slpkg is a fix , because after python upgrade to current, slpkg is not working.... Thats why I asked... Thanks again.
Hey ponce thanks for answer, this new release of slpkg is a fix , because after python upgrade to current, slpkg is not working.... Thats why I asked... Thanks again.
I thought slpkg was fixed for that with version 5.0.1, that is actually available in the unofficial repository for current...
also, if updates to slpkg are pushed to the official SBo repository they will also be available in the unofficial repository for current.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
Code:
~/scripts# slpkg -u
Traceback (most recent call last):
File "/usr/sbin/slpkg", line 5, in <module>
from slpkg.main import main
File "/usr/lib/python3.11/site-packages/slpkg/main.py", line 19, in <module>
from slpkg.choose_packages import Choose
File "/usr/lib/python3.11/site-packages/slpkg/choose_packages.py", line 8, in <module>
from slpkg.dialog_box import DialogBox
File "/usr/lib/python3.11/site-packages/slpkg/dialog_box.py", line 5, in <module>
from dialog import Dialog
ModuleNotFoundError: No module named 'dialog'
~/scripts# slpkg -u
Traceback (most recent call last):
File "/usr/sbin/slpkg", line 5, in <module>
from slpkg.main import main
File "/usr/lib/python3.11/site-packages/slpkg/main.py", line 19, in <module>
from slpkg.choose_packages import Choose
File "/usr/lib/python3.11/site-packages/slpkg/choose_packages.py", line 8, in <module>
from slpkg.dialog_box import DialogBox
File "/usr/lib/python3.11/site-packages/slpkg/dialog_box.py", line 5, in <module>
from dialog import Dialog
ModuleNotFoundError: No module named 'dialog'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.