You are not logged in.
Pages: 1
I've been trying to update my firmware with fwupd and it's been failing, and manufacturer support recommended I try a different version of fwupd. Every time I try to install a different version of fwupd, fwupdmgr always reports 1.8.1. I'm not sure if it's stuck at that version or if it's not uninstalling 1.8.1 when I try to install other versions.
Offline
I've been installing and uninstalling different versions of fwupd through pacman
Offline
how, exactly, are you installing different versions through pacman?
Online
Built packages from the AUR, downloaded a package from my computer's manufacturer, and used a PKGBUILD supplied by the manufacturer. Then installed with pacman -U. In all cases, the installed version reported from pacman was different from the version reported by fwupdmgr --version
Offline
"packages"..."a package"..."a PKGBUILD"
If you're not going to give us specifics, this thread is useless.
Online
My apologies, the one from the AUR is fwupd-git, which is version 1.7.6, I got the other pkg and PKGBUILD from StarLabs, the manufacturer of my laptop, both were also version 1.7.6. I think I also tried one other that was a different version, I forget where from. In all cases, fwupdmgr --version reported 1.8.1. Let me know what other information I can provide, I'm not sure what else to include. Thank you
Offline
Well fwupd-git isn't 1.7.6, it builds from the latest commit. The version the AUR says means nothing, you would need to look at what was actually installed. It would be 1.8.1 plus some commits, most likely.
The reset of what you provided tells us nothing. What, exactly, did they provide you?
Online
I see, so does it not update the package name when the software being built has a different version? That can lead to some misleading version discrepancies like this. I'm guessing that caused this confusion
This is the pkgbuild I got from them, most likely has the same thing going on: https://raw.githubusercontent.com/StarL … d/PKGBUILD
I got the pre-built package from them from Manjaro's repos, since they don't put the pre-built packages anywhere else: http://mirror.fcix.net/manjaro/stable/c … kg.tar.zst
I'm reading up on PKGBUILDs to see if I can force a build of an older version, would making the pkgver() function just echo the version/commit I want have that effect?
Thank you
Offline
I see, so does it not update the package name when the software being built has a different version?
No the package name will not change. But the pkgver will - in other words, the version reported by `pacman -Q` will update with the software whenever you rebuild a -git package.
That can lead to some misleading version discrepancies like this.
No, it can't - well, it could, but it doesn't happen, your premise is incorrect.
I'm guessing that caused this confusion
Your track record of guessing in this thread is not so good. This really sounds like an X-Y problem: you have some issue, and you are guessing about what's causing it and so you are asking about that suspected cause. But your reasoning is flawed.
What's the actual problem? What is the version reported by the installed binary and from pacman for the -git package from the AUR?
As for the manjaro package - who knows what they do ... well, they do, you could ask on the manjaro forums for that.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Pages: 1