Pamac Gui and pamac checkupdates -a are showing an update for beyond compare for 126.96.36.19918-1 to 188.8.131.52886-1. When I try and update via the gui or cli I get the error that beyond compare is upto date. Any ideas ?
Checking bcompare dependencies... Checking bcompare-cinnamon dependencies... Synchronizing package databases... Warning: bcompare-184.108.40.20618-1 is up to date -- skipping Warning: bcompare-cinnamon-220.127.116.1118-1 is up to date -- skipping
The issue is with pamac as I can update both packages with Yay. Wondering if the last testing branch update broke something ?
The package wasn’t upto date and wouldn’t update with pamac but it updated with yay. I’d say that is a bug rather than a message. Hopefully someone else can confirm they have the same issue rather than just the 2 of us
ok my bad, when i read code source, we have big re-write for calculate package dates in alpm_package.vala (commit v11.1)
replace uint by object datetime and now call DateTime.from_unix_local() in outofdate() method
notification test only version, but alpm test also date ?? maybe, depending on the time zone, you have to wait a few hours to install it ??
If you go to the package PKGBUILD tab in Pamac, and click the reset button, you can then click Apply and then it works, if you don’t reset the PKGBUILD and click Apply it doesn’t update, but then tells you there is an update, and you can loop like this forever.
I just had two AUR updates (GZDoom and Python Rapidfuzz) and they went well. I didn’t follow Pamac updates, but is the issue fixed or is it not consistently failing?
//EDIT: checked Pamac commits and nothing new there… now that I think about it a couple days ago I went into Pamac Preferences and cleaned all the cache so that might be why it worked this time, will see on next AUR updates for these packages.