linux things not to do 

I'm a deeply lazy person. To test foreign bindings to libraries like Cairo and OpenSSL, I built a slightly different version and overwrote the system-provided one with it. While this did indeed help testing the binding, it also breaks my system in funny ways:

- Cairo is used to draw all kinds of things, including GTK widgets. Cairo without xlib support results in gpg-agent no longer working with the default graphical frontend, thereby preventing me from using `pass` and by extension, `sudo`. Don't ask. I ended up changing the gpg-agent configuration to use the ncurses frontend, reloaded it, got `sudo` working again and installed the normal package.
- OpenSSL is used for all kinds of cryptography. After downgrading to an older version because I couldn't be arsed to package it in a different install location, `ssh` broke. Therefore I'll quickly finish debugging my issue, reinstall the normal package and have `ssh` working again.

linux things not to do 

gdb also broke because it depends on Python3 which depends on libcurl and libssh2, both of which depend on openssl. So I guess I can't debug after all and need to set up an environment or custom package for that.

linux things not to do 

In fact, a lot more things broke. `sudo` itself indirectly relies on openssl, so does `pacman`. So I guess it's time to fix the system from inside a chroot...

Follow

linux things not to do 

@wasamasa For these kind of things I see value in Nix/Guix as they do not replace your global OS state, just fork it. For general use they can be overkill, but for these kind of experiments those would be part of my lazy approach.

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko