Every time I try to upgrade a package, this misleading warning comes and says it's already installed. -Well, not the latest version-
Is there a way to get rid of this warning?
What happens when you first uninstall the previous .deb file 1.106.2 of the program?
It is not misleading since the package is indeed, installed.
You are trying to install a later version, not install the base package.
The warning is a necessary feature of dpkg and cannot be removed. But you can bypass it by installing your upgrade .deb package differently.
Replace package with the actual package name:
sudo apt install ./package.deb
run from within the directory.
2 Likes
Do that work with GDebi, too or would it behave like above?
Gdebi will alert if if installed, but as simple text on the left hand side - it does not have the confirmation button or warning aspect to it, more an informative aspect.
So, yes, good thinking. Using Gdebi for .deb package management might also be a solution.
2 Likes
Generally I find, the software store always has version of software too old, like a year or more old. If one wants the latest version, the best way to do that, is to bypass the software store entirely. Don't use DEB files, they will just install the version already in the software store, like OPENRGB for example.
Its best to install a PPA, known to have the latest version of something, then run the APT install command. I used to think DEB files were the be all end all too. That was until I realized, everytime I tried to install a later version of OPENRGB, using their DEB installer, it would just always point, to the outdated version, in the software store.
1 Like
A PPA installs DEB packages.
So, really... this depends on whether the .deb package is the package or if it is a Redirect.
Some maintainers will proved a .deb package that only contains a redirect.
But in general, getting the latest .deb package will install that later version. In the majority of cases.
I use Gdebi, and it will often even tell me "An older version is available in the software channel" when I run the installer, offering that I can opt to use the older for stability.
As a side note... let's be real. A year old for software is Not Old. By any means. Software is not measured in dog years.
Depends on the software, for a word processor no, for a photo editor no, for a video editor no.
I specifically mentioned OPENRGB, because it hasn't been updated in software repo's in literall years. For OPENRGB to work, new hardware has to be added to its support list. I still to this day, can't get OPENRGB to fully work on this 2021 computer. Supposedly the devs have a new version, but its not in the repo's, at least not for Zorin OS 16.
I eventually gave up on it, and recently removed the quick launch icon from my taskbar. I've already complained about this on their Discord, before I left that ridiculous APP business too. Whats wrong with web forums? Got to push everyone to use APPs now, so they can mine your data.
So, I guess it depends on the APP, I just checked the date, the latest version I got of OPENRGB, is literally from 2024, and if I remember correctly, I had to install that special, directly from a developer link provided to me. My 2021 machine is still not in it, despite being released years ago.
I don't like being left in the dark by developers, who just choose to go in their own way, refuse to accept feedback from others, and get nasty in communication on Discord. I suppose thats another issue entirely to the original topic at hand.
Having said that, my position still stands, when it comes to old versions of software, that don't support my machine, making a DEB installer useless, cause all its going to install, is that year old version, that has no support for your machine.
2 Likes
I do not understand this assertion... If it is installing the specified version, but you feel that OpenRGB lacks your hardware, then it is not installing an older version.
Also as an Aside, I think there is a misunderstanding here. OpeenRGB operates by code, not year of hardware production - There is an option within the application itself to specify hardware (and this not only can trip you up but is likely to because it is confusing as hell), but as a fellow OpenRGB user, I run it without specifying any of the hardware (My machine is newer than 2021) and everything works that way.
Maybe an OpenRGB troubleshooting thread can help alleviate that headache for you.
My hardware is not in the support list, therefor I can't use it, its simple as that. I've seen screenshots on discord, where they installed a newer version, that is not in the software store repo. This is what I ma trying to say, there is a newer version other's have installed. But there is no longer support for the OS 16 software REPO, thus it only has the older version of OPENRGB. I can't get the new version.
I forget what its called but you know what I mean, for every new generation of ubuntu's and gnomes, their is a new software codename like Jammy or whatever. Anyways, I have nothing more to say, my situation is screwed and won't be improved for the time being.
1 Like
Did You tried it with the AppImage when the .deb Version don't work?
And only to mentioned that: They have multiple Version. Older stable Version (until 0.9), then Release Candidates (1.0rc1 and rc2) and an Experimental Version (OpenRGB Pipline).
Since now vscode 1.107.0 is available I can test again.
Gdebi gives this warning:
It doesn't show update is available.
When I open Sofware as it suggests, only flathub (old version 1.106.3) is available
On software there is another snap app but it shows commit id instead of version so I don't even know if it's newer or not.
@Aravisian if a terminal command can show if something is upgrading, why ui cannot show that? We are not in 2005 anymore, asking what terminal shows on ui as well is not too much. (I believe in general Zorin is much better about that compared to other distros.)
The APT version matches, but yes... The Gnome Software Store defaults to Flatpak.
And here we witness a fallacy first hand: The assumption that Flatpak packages will always be a later version.
Different UI will show if updgrading or installing. But it does depend on the UI.
Gdebi is a large Package and seeks to simplify.
Gnome also seeks to reduce and simplify.
Personally, I think your question in this post is a valid one.
In the O.P. it is reversed. There, your popup shows a statement that the package is installed (which it was) and the version you were installing was a different version.
It can be confusing - leading the end user to wonder if the package is actually installed or not.
And... it gets more confusing - where we have Flatpak (Isolated), Snap (Isolated) and APT (Standard) all being used, but cannot interact - in order to tell you if something is installed but as a different format.
apt list --installed will not show the flatpaks... flatpak list will not show the .deb's....
It's not just GnuLinux.
Windows OS does the same and is unable to show if Appimages are present or if some software was installed using ninja for example. But it is more widespread on GnuLinux
All you can do for now is accept awareness of the system you own.
When installing a package, check the format. Avoid formats you find troublesome or confusing and try to stay consistent.
Save copies of installed standalone packages (.deb or appimage) in a dedicated folder you can easily and quickly reference.
If upgrading a piece of software that you installed and use... You probably already know that is what you are doing and do not need reminders.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
Today, something weird happened to an app that wasn't even installed. There were two option "Run" and "Install" but install is just opening gnome softeare with this error popup. Only "Run anyway" shows the details of the local .deb package.
Were you able to install it? I read that on github they recommend to use the flatpak instead because there are dependency problems on ubuntu 24.04. I haven't tested it yet.
1 Like
Yes but I used a different method to install libmpv1 dependency. Anyway the issue is "Install" option is misleading.
1 Like
Do you have added this repository to install stremio or how did you manage it?
Did you change the dependencies of the .deb package and the re-build the package and set a link to the old libmpv1
as shown in that post from github?
"I have found a way around it that hopefully others can use also.
- Download the .deb package for Ubuntu/Debian from the site
- Change the dependencies of the .deb from libmpv1 (>=0.30.0) to libmpv2 (>=0.35.0) (instructions for changing dependencies can be found here)
- Create a soft link to libmpv.so.2 to libmpv.so.1 by running the following command
ln -s /usr/lib/x86_64-linux-gnu/libmpv.so.2 /usr/lib/x86_64-linux-gnu/libmpv.so.1
"
Edit: I tested the installation of stremio with the vejeta repository, and the installation of stremio-server worked, but for stremio there was shown that it couldn't be installed. When running sudo apt update there were shown notes about i386 referring to the vejeta repository.
If you want an easy solution, just run:
wget -O - https://raw.githubusercontent.com/Kabir5296/Stremio-Ubuntu24.04-Fix/refs/heads/main/install_stremio.sh | bash
And then for torrent support, click install here:
https://torrentio.strem.fun/configure
1 Like