this post was submitted on 15 Jun 2026
612 points (97.7% liked)
linuxmemes
31752 readers
1346 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I avoid orphaned packages and I wait a few days before I type
yayYou're no fun
Is there a flag to prevent orphaned packages from installing?
Good question, I guess I might be using the wrong word when i say "orphan" because I see the arch wiki uses that term differently
You can remove these manually or if using an aur helper like yay there are flags/settings you can use to delete them after the desired package was installed.
However what I was talking about aur packages that are unmaintained or do not have a maintainer anymore.
I'm researching more at the moment.
shit, I had 150 orphaned packages
pacman -Qdtq | pacman -Rns -I made an alias for this, but IMO this cleanup should be automatic. The user didn't install it themselves after all.
This can be prevented by uninstalling with -Rs
Just removing them without user intervention could cause unexpected behavior.
I don't trust that everything that outputs from
pacman -Qdtqshould be deleted. Like I want to keepvlc.I think if you do pacman -S vlc it won't be orphan anymore though. I removed everything, if I miss something I'll install it again.
A simple install kept it orphaned. Instead I needed to run
sudo pacman -D --asexplicit vlcWaiting for updating doesnβt make any difference. The packages could be infected at any point.
I guess the same could be said for literally any open source or freely distributed project.
The difference is that this was a supply chain attack and, to my knowledge, required the package to be listed as ~~orphaned~~ unmaintained first so that the PKGBUILD could be modified to install malicious NPM packages.
The community caught it quickly because it is possible to read both the PKGBUILD and the output of the update and, I think, it is fully resolved as of now.
Basically, if one were to delete or replace orphaned packages then they wouldn't have been infected.
It is also possible to add a CVE scanner for AUR packages if reading the PKGBUILD is too much, I'm looking into how to do that now.
All this is to say that you should check if you had an infected package but I personally don't think using the aur is more risky than using a flatpak.
Are linux users allowed to juat lie like that? I thought if you do that you need to use Windows.
C'mon, man, at least pour one out for the homies who waited to update and landed in the period where it was live and undisclosed.
What?
They also wait until they get off the rollercoaster and back on solid ground before yelling
yay!