I’ve been seeing this message more and more recently during package updates. What could be causing this? Where can these packages be updated from if there are outdated versions in the AUR?
Perhaps posting the entire update output in the terminal could provide some more info.
2 Likes
It is likely that they are packages that were dropped from the repos but are not yet updated in AUR.
However, we need to know which specific packages they are to provide any meaningful guidance.
In addition, there are actually two defining pieces of information for these packages. Package marked as outdated or missing package.
I believe that that message will also come up for AUR “-git” packages which install the latest from HEAD while the AUR lists the version as the last time the maintainer updated the package.
This may also happen if you install binary packages from the chaotic-aur repo for basically the same reason.
Now, for example, microsoft-edge-dev-bin was such a package that I remember.
That package was downgraded by the AUR maintainer.
https://aur.archlinux.org/cgit/aur.git/log/?h=microsoft-edge-dev-bin
Thanks. I see that version 107.0.1379.1-1 has been downgraded back. According to them, there can be three reasons for the case I raised in this topic: missing package, outdated package, downgraded package.
1 Like
Thanks for your answer, maybe this is the closest to reality. Could you clarify what you mean by HEAD?
“HEAD” is a term used in the git version control system to refer to the latest commit to a particular repository.
In the AUR, you have packages which are based on a specific version of a piece of code and others which package the most recent code in a particular git repository. In many cases, you will see both versions of a package for a particular application in the AUR.
Packages based on the latest commit for an application have the suffix “-git” in their name and the version number is generated at build time based on labels in the particular git repository.
1 Like
Providing us the command and pacman results are far more helpful than you explaining then to us. We can actually help you at that point instead of just wasting time speculating things.
In this case, I wrote about automated package updates with the Welcome application, in the case of AUR packages.
Thank you for your professional answer. It looks complicated, but it’s actually simple.
Until this post, you mentioned nothing about the welcome app, so there’s no way any of us could possibly know you’re updating via the welcome app and getting these results. Your issue isn’t with the packages then, but updating with the welcome app, correct? I’ll change the title accordingly to help you, it’ll yeild far better results.
When I do the package update in the command line with the Yay command, I still get the same message as when I do it through the Welcome application.
Cool,. Post it all, I want to see what you’re seeing so we can help. If you can’t provide info, then this is just a waste of time.
1 Like
I’m seeing that honestly. If they refuse to post the actual commands and outputs, they are basically one of those people which I’m not allowed to say. They’ll be blacklisted by me as someone who will never get my help again.
microsoft-edge-dev-bin has been downgraded by the maintainer to version 107.0.1375.0-1, as noted in @dalto’s post above. The other affected package is ceph-libs, and the output of yay used for the update is this:
→ ceph-libs: local (15.2.14-7) is newer than AUR (15.2.14-6)
That was caused by what I referenced above. It was recently dropped to AUR from the repos and the AUR package is at a different pkgrel level.
However, you should check if you actually need ceph-libs still. For most people, it has been safe to remove it.
Yes, we discussed this in another thread. On the other hand, the fact that the local version of a particular package is newer than the one in the AUR comes up from time to time. @jruschme gave a possible realistic answer to the reason for this above.