Arch Linux User Repository

if you are having an issue or getting an error you can

• email me: check pkgbuild for email
• dm me on discord: witheringaway

i should respond quickly

tested helpers

• helper name, last tested version - note
• works:
• pacman, officially supported
• pacman (cachyos), 1-23
• yay, 1-23
• pikaur, 1-20
• paru, 1-23
• bauh, 1-16
• octopi, 1-16
• slight jank:
• pamac, 1-16 - has horrible architecture, script must go on a scavenger hunt to find who initiated the transaction

thx, tested on both cachyos and arch with cachy repos - works like a charm

@erius updated

supposedly the aur people decided to make the aur read-only due to malware... 2 months late. so not much i can do, sorry

@erius im still unable to push the update with the same "The AUR is down due to maintenance" error which im now almost certain is a lie, ill see if i can fix this

@withering yes, cachyos repos ship a modified version of pacman, which includes this network isolation feature for hooks. looking at /etc/os-release does fix the issue for most, since all cachyos installations ship these repos by default, but some edge cases, such as a user on arch opting in to use cachyos repos for their optimized package builds, kernels and schedulers, are not covered by the current fix

unfortunately pacman --version output is identical in both vanilla and cachyos pacman versions, thats precisely why i decided to go the pacman -Qi pacman route, since it explicitly denotes whether the pacman package on the system comes from cachyos or not via the 'Packager' field

@erius im unfamiliar with how the cachy repos work, do the cachy repos ship a cachy-specific pacman version? i was also thinking looking at pacman-conf but maybe a cachy repo user may not use cachy pacman, so what about just using pacman --verison?

edit: was trying to push 1-23 with this fix but im getting The AUR is down due to maintenance. We will be back soon. ill try another time

the recent cachy related fix doesnt seem to work on non-cachy systems that use cachy pacman repos..

since this is a pacman specific feature of cachy pacman distribution, it makes more sense to look at the packager of the pacman package instead of relying on /etc/os-release:

24c24
< if grep -qi CachyOS /etc/os-release; then
---
> if pacman -Qi pacman | grep -qi CachyOS; then

the patch above fixes this issue, @withering can you apply this to PKGBUILD?

Tested on CachyOS and is working fine, thank you for the fix :)

appears to be a cachy specific thing where it isolates the network for hooks with a cachy-specific action to disable it, so in 1-21 i added a vencord-hook-cachyos.hook that should automatically install rather than the default vencord-hook.hook if youre on cachy, try that out

I made some previous comments thinking my install location issue was related to the one that @voidlesity mentions but I misunderstood the situation and deleted them after I sorted it out.

To fix the network issue network is unreachable just add NetworkAccess=allowed to the hook in the [Action] section like this:

[Trigger]
Operation=Install
Operation=Upgrade
Type=Package
Target=discord
Target=discord-ptb
Target=discord-canary

[Action]
When=PostTransaction
NetworkAccess=allowed
Exec=/etc/pacman.d/hooks.bin/vencord-hook.sh
NeedsTargets

This is related to: https://github.com/CachyOS/pacman/commit/4056cd687f6379e61e7decb9b66e9b57cb3949a9 libalpm: isolate scriptlets and hooks from the network

After manually modifying the file /etc/pacman.d/hooks/vencord-hook.hook allowing network access everything started working fine again.

Maybe @withering can upgrade the hook to allow network access :)