00:07 <havenwood> kjetilho: mutex_m used to be a default gem where it couldn't be uninstalled but now it's a bundled gem and you can: gem uninstall mutex_m

00:07 <havenwood> You can also: gem update mutex_m

00:07 <havenwood> See https://stdgems.org/mutex_m/

00:08 <kjetilho> yeah, problem is this is on Ruby 2.7. so I think I am stuck with it?

00:09 <havenwood> kjetilho: Yeah, back then it was a default gem so it could be updated but not uninstalled.

00:09 <kjetilho> gem uninstall refuses to touch a default gem, and I can't un-default it

00:10 <havenwood> kjetilho: Updated but not uninstalled.

00:10 <kjetilho> funnily enough it allows both 0.1.0 and 0.3.0 to be default

00:10 <havenwood> You can update default gems.

00:11 <havenwood> On Ruby 2.7, `gem update mutex_m` will install 0.3.0, the latest version.

00:11 <kjetilho> hmm! so I just have to do that before bundle install

00:11 <kjetilho> (I'm building a container here)

00:12 <havenwood> kjetilho: If you're using mutex_m, and want to use 0.3.0, add it to you Gemfile and bundle.

00:12 <havenwood> gem 'mutex_m', '~> 0.3.0'

00:12 <kjetilho> I don't really care - it is pulled in by some dependency solver

00:12 <kjetilho> but the system ruby version in 0.1.0 causes these noisy complaints

00:12 <havenwood> kjetilho: Default gems can be added to your bundle if you need a specific version for any reason.

00:12 <havenwood> bundle add mutex_m

00:13 <kjetilho> I did try to add it explicitly to Gemfile like you said, with `gem 'mutex_m', '~> 0.3.0'` - but it didn't affect the message

00:13 <havenwood> kjetilho: After adding it to your Gemfile, run `bundle` or its alias `bundle install`.

00:14 <kjetilho> I did that. trying an explicit '= 0.1.0' now first. let's see what complains

00:15 <kjetilho> -fist

00:15 <kjetilho> -first

00:16 <kjetilho> no complaints. but building the whole container takes a bit more time. *drums fingers*

00:20 <kjetilho> yay - that workaround did the trick. trying the `gem update mutex_m` prior to running bundle now.

00:23 <kjetilho> nope, the 0.1.0 sticks around

00:23 <kjetilho> anyway, thanks a lot for your input!

10:26 <nakilon> speakng about thelounge, somehow docker on ubuntu has glitched like this https://askubuntu.com/q/1315822/160618 and so I can't issue thelounge commands, and to restart it I need to sudo and I don't remember the password ) and I absolutely don't remember how you are supposed to have root priviledges and not use password -- it's so weird, like I was

10:26 <nakilon> used to cloud OS maybe and on usual VPS I had to do some extra steps... somehow this linux stuff got out of my memory

10:31 <testone> nakilon: you can have 'root' without password rebooting in single user mode

10:32 <testone> then change root password with passwd

10:32 <testone> otherwise, both the same pc from a live usb image

10:55 <nakilon> not sure how to boot like that on VPS