this post was submitted on 27 Mar 2024

143 points (100.0% liked)

linuxmemes

23939 readers

484 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 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, <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 2 years ago

MODERATORS

[email protected]

143

Genuinely the only time Arch has broken something I can't fix myself (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

Context: A few days ago Arch pushed out a legitimately broken update. This was because they shipped out a testing version of util-linux. They very quickly fixed this... except I use SE Linux (say what you will I wanted to dive into it) and now I'm stuck waiting for the maintainer to update the AUR package so I can fix my system. This is not a general arch problem but a me problem because of my less standard, more niche build. Although the wait is genuinely making me reconsider using SE Linux as it's been a hassle to maintain (just to keep things up to date, I gave up on keeping it in enforcing mode).

top 12 comments

sorted by: hot top controversial new old

[–] [email protected] 26 points 1 year ago (1 children)

If working with the AUR,
you can alter the PKGBUILD and other build files on your own behalf.

To either fix what's wrong,
or to roll back to a previous version of the package.

I've did both a few times already,
however I'm on Manjaro.
Pamac, their graphical installer,
prompts me if I'd like to edit the build files before starting the build/install process, unsure how to do it in Arch, but the ArchWiki should be able to tell you.

Also, if you'd fix what's wrong,
please post your diff on the AUR package thread, that can save the maintainer some work / help with rolling an updated package out to the other users faster.

[–] [email protected] 8 points 1 year ago (1 children)

I attempted to do so, but the package applies some patches to the source code and it's version dependent. I don't have the experience with this specific project to easily fix it, and I suspect by the time I figure it out the update will have already been pushed.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago (1 children)

Have you tried rolling back the affected packages from the main repo?

[–] [email protected] 1 points 1 year ago

It was my weekly update, ngl I'm not entirely sure all of which packages broke. That one's on me

[–] [email protected] 15 points 1 year ago* (last edited 1 year ago) (1 children)

I just want to say that "Arch" didn't push or update anything. Everything in the AUR is maintained by the community and if something from there breaks then it's not on the Arch team

[–] [email protected] 2 points 1 year ago

This package is not the fault of the Arch team. However they did push a legitimately broken update that required some people to manually reinstall core components of their system to make it functional again. They sre not responsible for my issues but they did actually fuck up recently.

[–] [email protected] 14 points 1 year ago* (last edited 1 year ago) (1 children)

If you’re not running SELinux in enforcing mode and you’re not developing policy then you’re really not doing anything with it, for what it’s worth.

SELinux without a policy similar to a targeted policy seems not advisable on a rolling release system, unless you are actively maintaining a policy for the use case or your upstream package maintainers are releasing robust policy for everything

[–] [email protected] 8 points 1 year ago

It was a way to learn how to actually use SE Linux and its different components. I still have more that I wanna do with it, but it's one of those projects that's been on the back burner for a while

[–] [email protected] 2 points 1 year ago

I wasn't ever going to touch SE linux, zero patience for this nonsense. Even just maintaining a firewall is tedious as hell IMHO

[–] [email protected] 2 points 1 year ago

Just fix it yourself dude