Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aurutils terminal coloring with systemd 256 #1161

Closed
christian-heusel opened this issue May 23, 2024 · 6 comments
Closed

aurutils terminal coloring with systemd 256 #1161

christian-heusel opened this issue May 23, 2024 · 6 comments
Labels

Comments

@christian-heusel
Copy link

With systemd 256 (the upcoming systemd release) it includes possibilities to color terminals, i.e. on systemd-nspawn and run0. When nspawn is now used in a program this very much looks like a visual bug IMO:

image

I have therefore disabled the behaviour in devtools (https://gitlab.archlinux.org/archlinux/devtools/-/commit/0e2b16b0ac63e33e32a6cb889bc4b047e0d451e9), but since I couldn't get the above trivial fix to work with aurutils I thought I'd open this issue as a heads-up.

Feel free to close as wont-fix if you want to keep the default behaviour.

@Earnestly
Copy link
Contributor

Seems like an nspawn issue; the bleeding background colour appears to come from pacman.

@christian-heusel
Copy link
Author

@Earnestly I'm not sure I follow, what do you mean?

@AladW
Copy link
Member

AladW commented May 24, 2024

I'm confused by the commit message:

Disable this bevaviour for pkgctl, so it stays active for arch-nspawn (for now).

but arch-nspawn, makechrootpkg, and mkarchroot use src/lib/common.sh. In turn, aur-chroot uses those three tools for chroot functionality.

@AladW AladW added the devtools label May 24, 2024
@christian-heusel
Copy link
Author

I forgot that they include common.sh so its a side-effect but fine by me 😆 Disregard this issue then 👍🏻

@VorpalBlade
Copy link
Contributor

Just noticed this. It looks like eye bleed unfortunately. Any way to get this fixed in aurutils?

@christian-heusel
Copy link
Author

This is fixed in the devtools 1.2.1 release thats currently still in testing 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants