Put in ‘69420’, run makepkg -o. It will replace the value with the result of pkgver(). Generate SRCINFO etc., then push to AUR. When changing the PKGBUILD itself, either upstream will have changed, resulting in a higher pkgver and therefore triggering updates for AUR clients, or you need to increase the pkgrel.
Everything runs through fully hardened/restricted systemd units, as separate user with minimal access rights for everything
You’d need to escape the software, restrictions and get root to do anything meaningful, while avoiding detection
According to https://www.reddit.com/r/termux/comments/105fjt8/how_to_install_and_run_sdl2/,
pkg install x11-repo; pkg install sdl2
Though that would probably be different to what an actual APK would be at the end due to the X11 layer
Just take new poisons, viruses or whatever every time your condition improves. Then you’ll be in control of the edging (so to say), and therefore also the final denial/ruin.
Nah. At least for my region in Germany, DHL is very reliable and fast. Pretty much always one day early from their predictions. And idc when they get here, they’ll put it on the front door, and I’ll either pick it up a few hours later when coming home, or a neighbour will.
cuts through limb
If it bleed it’s real, if the video stops abruptly or the knife doesn’t actually cut, it’s slop
Aldi.
We will not lose anasa wörld woar!
I mean, the solution is simple: Don’t use IP!
No Internet Protocol -> No Internet -> No slop
25GB=qemu@verein.service
17GB=auto-aur-builder.service
15GB=borgmatic.service
11GB=postgresql.service
6.2GB=qemu@arturimages.service
5.5GB=gitlab-puma.service
3.0GB=immich-server.service
2.7GB=cryptpad.service
2.3GB=immich-machine-learning.service
1.4GB=clamav-daemon.service
1.3GB=gitlab-sidekiq.service
1.3GB=gitlab-gitaly.service
1.3GB=systemd-journald.service
1.2GB=lemmy.service
1.1GB=peertube.service
1.1GB=docker.service
So pretty much, a tiny 11 VM and an autobuilding service, that probably has a memory leak. Then backups, permanently running, postgres containing all my data, and a linux vm. Then, various services.
Your post ended in “Edit: To the few of you who’re taking pot shots at me like the immature cunts you are - go back to Reddit for that.”, while the rules say "Be nice and; have fun
Doxxing, trolling, sealioning, racism, toxicity and dog-whistling are not welcomed in AskLemmy."
If you want no moderation, go to another platform.
You’re like a child punching someone and then being angry they get punished, or a carbrain running a red light and complaining about the ticket.
I mean, Bun itself serves a language that should not exist
Well, I tried piper before, and some other tool. Both did not work. iirc, piper did not even detect the device
Can’t really test that.
I may need to try ratbagd then :3
It does have generic tools (eg. xdotool -> ydotool), but the most powerful way is to configure it in the DE/WM itself (eg. KDE’s shortcuts or sway’s bind command). To know if what you are doing is possible with ydotool or on sway, I’d need more specific info.
But my point was rather that it’s cool to have such functionality in the kernel, independent of desktop stack and DE/WM.
I’ve never been able to actually program my G502X Lightspeeds buttons
Sucks for wayland users tho
And I prefer C/C++ and Python due to that.
Eg. JS devs need to version pin in NPM to not expose users to compromised packages. That means that, from now on, they need to be active at least every week and update the pinning to not expose users to vulnerable packages. Meanwhile, the users need to be on-edge about the dev actually being active, and, still, for every vulnerability and compromised package, need to scan their whole system for files relating to that package. And of course, that means a very long fix path of Vuln discovered -> Vuln fixed -> Dev knows that one of the dozen packages they use needs updating -> Dev updates -> Package managers updates -> User updates.
It’s a horrible experience for sysadmins. I’m actively switching to alternatives and rewriting smaller things in C++, because everything I’ve written in the latter has never broken in years, without recompilation, because the ABI stayed the same for all libraries, while the libraries get carefully curated by a dedicated team. And as soon as a vulnerability/backdoor is found and fixed? sudo pacman -Syu. nothing more, nothing less. Fix path: Vuln discovered -> Vuln fixed -> Package managers updates -> User updates.
Looking at more than just binary files in repos: I’m also actively rewriting PKGBUILDs to use the native python packages instead of building a venv, because that just works better in my experience. I’ve never had issues with incompatibility between python-* packages, simply because they are build for each other. And I mean, it took 30 minutes to build a component that converts a requirements.txt, which requires you to trust the dev (to be active) and pypi (which you can’t trust), to a collection of pacman packages. Universally applicable to all requirements.txt and uncomplicated. So yeah, idiots can continues using pip, I laugh with a list of packages neatly curated by a dedicated team.
The pkgver is replaced by makepkg with the value of pkgver(). Similar to how updpkgsums updates the hashes.