- This topic has 11 replies, 5 voices, and was last updated Nov 9-8:23 pm by AR.
-
Posts
-
AR
As was recommended by @anticapitalista, I did not pure reinstall for 19.3, but instead upgraded my 19.2 (“full” distributive) up to 19.3 just by step-by-step – “sudo apt update” and then “sudo apt full-upgrade”. When I have tried to install new kernel after some time, “Package Installer” (my last version is 0.2.4) just refused to install as the new kernel, as any other packages, and also to deinstall anything – all buttons there except “Close” was greyed and non-fuctional. I tried “sudo packageinstaller” in terminal, tried to change repos, but the problem still persist. Of course I can install new kernel via Synaptic, or by another way, but what’s the hell with my “Package Installer”?
BTW, also I think that older kernels should be persist in “Package Installer” to easy deinstall/reinstall if someone need so.
- This topic was modified 2 years, 5 months ago by christophe.
Anonymous
As was recommended by @anticapitalista
hmmm…
apt-get full-upgrade full-upgrade performs the function of upgrade but will remove currently installed packages if this is needed to upgrade the system as a whole. apt-get dist-upgrade dist-upgrade in addition to performing the function of upgrade, also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. The dist-upgrade command may therefore remove some packages.
christophe
Perhaps try reinstalling the package.
sudo apt --reinstall install packageinstallerconfirmed antiX frugaler, since 2019
christophe
Regarding the older kernels, use cli-aptiX & search for antiX kernels. (It’s very easy, if you haven’t used it yet.)
confirmed antiX frugaler, since 2019
I think that kernels should be persist in “Package Installer”
Reading this sent me to check and, nope, neither packageinstaller nor cli-aptiX warns when a liveboot user attempts to install an alternate kernel.
https://gitlab.com/antiX-Linux/packageinstaller/-/blob/master/mainwindow.cpp
https://gitlab.com/antiX-Linux/cli-aptiX/-/blob/master/cli-aptiX#L254
caprea
Just to rule that out entirely, the buttons “install”, “deinstall” in packageinstaller are greyed out by default until you mark something from the package-list.
There was no hint when opening packageinstaller from terminal ?
Xecure
I tried “sudo packageinstaller” in terminal, tried to change repos, but the problem still persist.
After changing the repos, do you run
sudo apt update
before running package installer?Also, give us
inxi -rantiX Live system enthusiast.
General Live Boot Parameters for antiX.1. @skidoo: Now “apt-get” is only the part of “apt” package, so “full-upgrade” and “dist-upgrade” commands there are synonyms. In some older “man apt”‘s was written that “dist-upgrade” is obsolete. But both commands still acceptable till now and are equal in both “apt” and “apt-get”.
2. @christophe: Of course I did “sudo apt –reinstall install packageinstaller”, but with the same result. About another ways for installing what I need, e.g. via “cli-aptix”, I already wrote in my first post that I can do it. But I want to understand what’s happened with my “Package Installer”.
3. @caprea: I know how to use “Package Installer”, and successfully used it before. While running from terminal, there was no any messages at all.
4. @xecure: I do “sudo apt update” every time before any upgrades or installing of new software. But I noticed that “Package Installer” do it itself before showing the list of packages. Am I right? Anyway, I still do it before.
Finally, my “inxi -r”:$ inxi -r Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb https://mirrors.evowise.com/mxlinux-packages/antix/buster/ buster main nonfree nosystemd Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 1: deb http://deb.debian.org/debian/ buster-backports main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http://ftp.ru.debian.org/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.ru.debian.org/debian/ buster main contrib non-free 2: deb http://security.debian.org/ buster/updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main No active apt repos in: /etc/apt/sources.list.d/onion.list Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 1: deb [arch=amd64] https://repo.skype.com/deb stable main No active apt repos in: /etc/apt/sources.list.d/teams.list Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 1: deb https://linux.teamviewer.com/deb stable main No active apt repos in: /etc/apt/sources.list.d/various.listSo the problem still persist. Thank you all for attention, and hope for your help.
P.S.: I’ve not quoted your messages to not overload my reply.
I think that kernels should be persist in “Package Installer”
Reading this sent me to check and, nope, neither packageinstaller nor cli-aptiX warns when a liveboot user attempts to install an alternate kernel.
https://gitlab.com/antiX-Linux/packageinstaller/-/blob/master/mainwindow.cpp
https://gitlab.com/antiX-Linux/cli-aptiX/-/blob/master/cli-aptiX#L254Here I understood a bit less than nothing. 😉 I meant that some older kernels should be available in “Package Installer” in “Kernels” partition to easy deinstall/reinstall of them when someone needs it. But what meant you?
caprea
To me your repos looks OK.
Might also reinstall the packageinstaller-pkglist
You can look in the /var/log/apt/history.log if something got removed during the full-upgrade.
Xecure
I tried installing from the normal repo using package manager (installed abiword). This was done in an installed antiX 19.2 base x64 upgraded to 19.3 with sudo apt upgrade.
Steps:
0. Launched package installer from Control Centre. It looked normal. Opening the Audio category displayed black text for “new” software (not installed in my system) and grey text for MOC and XMMS (installed by default).
1. Searched abiword using the top right search box. Gave me correct result
2. Ticked Abiword option and clicked Install
3. Typed “Y” in the terminal prompt to download and install abiword.
4. Installation ended successfully. I checked and abiwork launches from the menu.
5. I didn’t close package installer and proceeded to Uninstall Abiword.
6. Uninstall worked.“Package Installer” (my last version is 0.2.4) just refused to install as the new kernel, as any other packages, and also to deinstall anything – all buttons there except “Close” was greyed and non-fuctional.
I tried on a VM to reproduce this starting from 19.2 x64 full, changing repos to the ones you list (except for skype, teamviewer, and google chrome) and doing full-upgrade, as you did, but I couldn’t fetch for packages from the evowise antiX mirror, so I changed to the it.mxrepo.com mirror (I hope this doesn’t change much the results compared to yours).
I answered “Y” to all questions about replacing files during the upgrade.
0. Launched package installer from the Control Centre. The same as before, in the Audio category, available programs were in black, installed programs in gray. Ticking any of them gave me different options beside the Close button, in black (Install if available, uninstall and Reinstall if already installed).
1. Searched for kernel using the top right search box.
2. Ticked the first option (4.19 antiX kernel) and then clicked the Install button.
3. Typed “Y” to install the 7 packages suggested (including the linux-image and linux-header for 4.19.152 antiX kernel)
4. Installation was successful. Now kernel 4.19 option is grayed out (meaning, installed).As I couldn’t reproduce, I tried to purge packageinstaller-pkglist to see if that is the list of packages that you are missing, but that also purged packageinstaller, so it probably isn’t the reason of your problem.
Try again to purge the package installer and install it again ad give us a step by step set of instructions to reproduce.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Try again to purge the package installer and install it again ad give us a step by step set of instructions to reproduce.
After purging of packageinstaller and packageinstaller-pkglist, and then installing packageinstaller again all works fine! So I think that the problem was in packageinstaller-pkglist.
Thank you all for help, especially @caprea and @xecure!
I cannot mark topic as [SOLVED], so I ask moderators to do this.
- You must be logged in to reply to this topic.
