• 0 Posts
  • 99 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2024

help-circle



  • pacman -S vulcan-mesa-implicit-layers

    Which will then probably tell you that it conflicts with vulkan-mesa-device-select and asks if you want to replace it. Which might either work or just get you another conflict because vulkan-mesa-device-select is required by some other package.

    Btw… pacman -Qi <package name> usually tells you anything you need to know about a package. In this context mainly why it was installed (as a requirement for which package) and which other packages are required as a dependency.

    So maybe you should take one step back first. Check why 'vulkan-mesa-device-select` was installed in the first place. If it’s not dependency of something else you can either remove it (or replace it) alongside its lib32 version.


  • That’s a totally separate error… It can happen that the keyring itself is so out of date that it blocks the update, and with it the upgrade to a newer keyring. For this reason it’s often safer after a long time to do pacman -Syu cachyos-keyring (pretending I guesse right and that’s the name of the package) first to avoid the whole update getting blocked by signature with an out-of-date-key. Yet that should not apply here.

    But Ignoring the warnings you get for now… This looks like vulkan-mesa-implicit-layers did not replace vulkan-mesa-device-select but now the 32bit library version lib32-vulkan-mesa-device is supposed to be replaced by cachyos/lib32-vulkan-mesa-implicit-layers, which would in turn need vulkan-mesa-implicit-layers as a dependency.

    What happens when you answer ‘no’ to that first question? Alternatively, is there anything keeping you from installing vulkan-mesa-implicit-layers (thus replacing vulkan-mesa-device-select)?


  • Not using CachyOS but Arch… but after a long break from updates you should probably start by checking if your mirror is still up-to-date (doesn’t look like it when you local stuff is newer…).

    Again… not my OS but this seems to be the file you could use to manually replace the mirrorlist in your /etc/pacman.d/ directory.

    Edit: Also just to be sure… -Syyu will force a refresh of all databases (doubling the u would force “upgrading” even it’s an actual downgrade from your local version). You normally don’t do it because it puts extra load on the mirror, but in case of problems it won’t hurt.

    PS: For the future (and although partial upgrades are normally to be avoided)… after a long break in updating the key breaking points are mirrors, then keyfile (they can be so out of date that you can’t start the update - so do them separately first), then pacman itself…

    The latter is very rare but there have been a handful of major changes in pacman’s lifetime that broke down compatibility after a long time. Arch keeps a static pacman version available for these cases, so you can still do a proper update to fix it, but don’t know where CachyOS keeps it’s equivalent.

    2nd Edit for sake of completion: A quick searched seems to indicate that CachyOS does not have a separate static pacman. So if everything else fails and it’s an actual problem of pacman itself (and only then, so please don’t try that just now) https://pkgbuild.com/~morganamilo/pacman-static/x86_64/bin/pacman-static has the static standalone version of pacman. So you can download this file, make it executable and run it.


  • It’s wrose than useless.

    There is barely a lack of third party video evidence. And in cases where we don’t have those, a body cam is useless… unless there is a guarantee a) they are running and b) the footage is accessible.

    So handing out body cams will not help in any way. I won’t be a deterrence for officers if they have control when to activate it. It will rarely produce footage incriminating officers and if it does that footage will be held back anyway.

    There is however a reasonable chance to capture enough footage that can be framed (or straight out manipulated) to show those violent protesters they crave for their narrative.



  • You listed just about anyone you can think of to be involved in your conspiracy.

    No, I listed a few of those Axel Springer SE is well documented to have already pushed propaganda for. In fact as I live in Germany I can read their lies in big red letters every morning on that rag displayed everywhere. So I sadly know how bad it really is…

    PS:

    “[…] claimed that Axel Springer SE, along with its subsidiaries, exhibits a pro-American stance, often omitting criticism of US foreign policy. This observation is then backed by allegations made by two former CIA officers in an interview with The Nation, claiming that Axel Springer received $7 million from the CIA”

    " As of 2001, the Axel Springer SE names “solidarity with the libertarian values of the United States of America” as one of its core principles on its website. This explicit stance has led to critiques from scholars and independent observers"

    “Foreign Policy has critiqued Axel Springer SE for a history of compromising journalistic ethics to support right-wing causes.”

    All quotes from the Wiki link you refused to click to imply conspiracy theories on my side instead.



  • Those “some” you mention are a miniscule minority.

    That official US government account posting from Israel while a big political delegation is there right now? Sure.

    Bigger numbers of very active MAGA influencers consistently posting from Russia or Nigeria? All those proud Irish “Celtic Warriors” posting from the US? Eastern European far-right politicians pushing Russian narratives and using Twitter through Russian apps? No, that’s a very obvious pattern.

    So while your first about a global society is technically correct, it is definitely not the defining portion in this. And stressing “that can happen and is totally normal” when it’s an exception has the sour aftertaste of a diversion.