Dear Unix Diary,

You made me suffer a lot yesterday... Actually Arch did!

Don't blame adam, blame Arch and its machiavellism!

I've been keeping my packages up to date but I've been doing that every 4-5 days and my box had an uptime of 24 days.

Suddenly, 2 days ago, when I went through the update process I noticed that I had to download 900MB and replace more than 500 pkgs, WHAT IS HAPPENING HERE?

Ok, No prob, let's update those.

I remembered a few days ago I was explaining the difference between the TTY and the X environment to my SO and when I switched to TTY2 and startx it wasn't starting.
At the time I didn't give it too much attention, I even forgot about it.

I let the stuffs download and update during the night and when I wake up the next morning, reboot, and X doesn't start.

Quick analysis => It seems to come from urxvt, I'm starting my X session over it.
Quick fix => Let's start the session over xterm and see what else is broken.

...

• The touchpad
  
• Urxvt
  
• Postgresql
  
• PHP
  
• Phppgadmin
  
• Ruby
  
• Some Python modules
  
• Perl
  

Calm down fellow, nothing to worry about.

Let's start with the touchpad.

"You've done that multiple times, you can do it again"
"Why the hek should I have to redo it!"

Ok, let's check the X11 files.

50-synaptics.conf is missing but it's in a .pacsave file, insane.
No need anymore to check the Arch wiki about touchpad

That's one.

Urxvt is crying about the wrong link to the perl library.
Damn perl updates breaking everything.

Let's try compiling it from the AUR:

(EE)

Dammit!

What could be wrong, let's remove some support by using the --disable flag.
No result.

Why not reinstall with pacman from the main repo.

No freaking way... It's working again, it even kept my configuration, that's great!

That's two.

I have scripts on my machine that uses my postgresql to store logs.
They didn't start correctly at boot that's when I noticed postgres couldn't start.

Ok, systemd magic tells me to check the logs in journactl -ex or journalct -u postgresql

I'm just paraphrasing here:

Yeah, that's verbose.

Where are my text logs when I need them.

Let's check /var/log/error.log, nope, /var/log/postTAB nope nope neither, /var/log/messages.log, really.


Damn, couldn't you do that during the update.

I ran the script in the wiki and my DB is up again.

That's three.

Let's see what's up with php.

They switched to php7 apparently.

And the support for phar and openssl are built in, that explains why I had a warning.

Let's just remove those extension from php.ini.

That's four.

What about phppgadmin.

It's shouting about php incompatibility or drop of support for the constructor that are named like the class.

Wow, I didn't know that was even possible, how old is that code?

Quote:xero: that was php4 style, naming the class and the constructor the same. it was ok in php5 and now deprecated in 7

Seems like it was fixed in a GH pull here but not in the main repo.

I'll fix it manually 'cause I kick asses!

I went through all the classes files and patched them.

That's five.

I use ruby for jekyll, nothing else.

Jekyll doesn't start, yep, get over it!

I tried to install the gem again, didn't find much about "re-installing" a gem.


No luck, it kept saying I was missing some module.

I kept trying to remove the gem and reinstalling them for a while, as normal user and as root, I thought it would make a difference, and then gave up.

I then completely removed my ~/.gem directory and tried again.

Ok, it's installing in ~/.gem/ruby/2.3.0 not ~/.gem/ruby/2.2.0 and my ruby path in my .zshrc points to the 2.2.0.

This is working... Eh nope.

Pygments isn't there => gem install pygments => No such module => gem install rb-pygments => not working.

Damn, can I use something else, let's update my _config.yml to use "rouge" instead, whatever that is.

Sweet, jekyll is up again!

But weirdly it's not parsing well my H tags.
Maybe it's adhering to the "newest" markdown standards, I know "standards" and markdown don't go along.

It seems to work when I add a space after the "#" but not when the word is directly next to it.

Sed comes to the rescue (even though my skill are rusty):

The rest...
I'll fix on the fly, they are just modules.

Cheers my Unix friends!