Anybody else ever have CachyOS be lazy about checking Arch repos (like core, extra & multilib), when (last) part of an “&&”ed set of update commands? Some packages get updates through paru in this case, but some apparently… don’t?
I just had, for at least the second time, a package I KNEW had been updated on Arch (cuz another machine running Arch had successfully done so) get ignored by a … && paru command, and only find it and update appropriately when I then explicitly ran paru on its own. Again, some other packages had successfully updated via paru.
I also assume (being extra) that that package would have updated fine with an explicit, isolated sudo pacman --Syuu.
Is ignoring or somehow modifying the last command a known problem with stacking them in fish? Because while CachyOS optimizes fish well enough that I so far haven’t had reason to switch it out, I’d be happy to run bash & configure it my way.
Maybe it’s a reflector problem, but pacman via paru throws no complaints about updating the repos, nor about any servers that fritzed out mid-check. It just… says it successfully updated its repos, and doesn’t pull a package you know has been updated, amongst the others it does.
Weird how a distro that on its own repos, often offers something newer than and/or forked from Arch, seems intermittently slow to update Arch’s own repos. Though (not knowing how the CachyOS team divides their labor, and keeping in mind it’s the weekend), maybe they have a reflector mechanism to hold off on checking Arch repos on a per-package basis, so they can decide whether they need to fork it?
I dunno, now I’m speculating without information.
=> More informations about this toot | View the thread | More toots from juanejot@beige.party
text/geminiThis content has been proxied by September (3851b).