this post was submitted on 27 Mar 2024
137 points (96.0% liked)
linuxmemes
21180 readers
873 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
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 members of the community for any reason.
- 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.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
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
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can try rolling back to a previous version though.
By checking the log section in the AUR,
you can see all the commits (changes) done to the build files.
https://aur.archlinux.org/cgit/aur.git/log/?h=util-linux-selinux
Clicking on a commit message shows you the diff.
Start by the last commit,
undo the changes (green lines),
re-apply the removals (red lines),
then attempt to re-build.
If that did not work out,
do the same for the commit before that until you rolled back up to the latest working version.
This specific version of the package isn't the issue, it's that main repo packages are built on the updated version and this hasn't been updated yet. I'm unsure of the process that is used to choose and apply the patches for this project, and I'm unsure if the current version in the repos actually has the work done on it for this specific package.
Have you tried rolling back the affected packages from the main repo?
It was my weekly update, ngl I'm not entirely sure all of which packages broke. That one's on me