Genuinely the only time Arch has broken something I can't fix myself

Holzkohlen, 2 months 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

DaTingGoBrrr, 2 months ago (edited 2 months ago)

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

erev, 2 months 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.

danikpapas, 2 months ago

Just fix it yourself dude

prettybunnys, 2 months ago

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

erev, 2 months 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

Rikj000, 2 months ago

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.

erev, 2 months ago

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.

Rikj000, 2 months ago

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.
aur.archlinux.org/cgit/aur.git/log/?h=util-linux-…

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.

erev, 2 months ago

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.

midnight, 2 months ago

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

erev, 2 months ago

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