4 ms·

All of my Arch Linux nodes ate-shit when I did this upgrade years ago. Things didn't like when their shared libraries got moved. I had to manually recover ever

All of my Arch Linux nodes ate-shit when I did this upgrade years ago. Things didn't like when their shared libraries got moved. I had to manually recover every single one. It was actually the straw that broke the camel's back for me as an Arch user. This was around the time Arch Linux was going through lots of breaking changes.

gnarbarian 10y ago
It's what happens with any rolling release distro given enough time. We thought it would solve the problem of having to upgrade the OS and migrate every few years but it didn't really. Now we have docker. Probably not solved until we write all our applications as some sort of crazy monad to minimize maintenance pain. I think docker is a meaningful step toward that.
- toyg 10y ago
  > until we write all our applications as some sort of crazy monad Desktop Linux seems to be finally moving towards self-contained formats like AppImage and Flatpak. They are clearly not oriented towards server apps, but who knows.
  - deleted 10y ago
    [deleted]
  - lisivka 10y ago
    OMG. Self contained apps were there starting from Linux 0.1. They are reinvented every second year.
    - toyg 10y ago
      Yeah but they never got traction for this or that reason. This time it looks like several big players actually agree on a common way forward. I guess time will tell.
- c3833174 10y ago
  >It's what happens with any rolling release distro given enough time. Not really, the KISS nature of arch means that stuff that could be automated isn't because reasons, while systemd gets a special pass.
  - digi_owl 10y ago
    because systemd is a personal passion of one of the lead arch devs...
- skykooler 10y ago
  Of course, now you need to deal with docker itself updating constantly, and the client not being able to talk to the server if they're updated more than 3 months apart.
  - SEJeff 10y ago
    Or just use rkt and don't worry about it. The CoreOS team takes api stability pretty seriously.
laumars 10y ago
It wasn't that bad. It did require manual intervention to get the install to work (which isn't a great surprise given the nature of the update) but it installed pretty painlessly on all bar one machine. The one exception being a laptop which I put off the update for several weeks and then left myself with a much larger job than it should have been - so really that one was partly my own fault. The glibc update from around the same time was a much worse update update. I think that one did break every Arch install I had at that time.
majewsky 10y ago
Interesting. I had zero trouble with this change on any of my boxes. Did not even have to --force the upgrade.
SSLy 10y ago
Well, the instructions on the frontpage were very clear and simple how to process the update.
dizzystar 10y ago
Not on Arch anymore, but I do remember that upgrade. I had no issues at all with it.

gnarbarian 10y ago

It's what happens with any rolling release distro given enough time. We thought it would solve the problem of having to upgrade the OS and migrate every few years but it didn't really. Now we have docker. Probably not solved until we write all our applications as some sort of crazy monad to minimize maintenance pain. I think docker is a meaningful step toward that.

toyg 10y ago
> until we write all our applications as some sort of crazy monad Desktop Linux seems to be finally moving towards self-contained formats like AppImage and Flatpak. They are clearly not oriented towards server apps, but who knows.
- deleted 10y ago
  [deleted]
- lisivka 10y ago
  OMG. Self contained apps were there starting from Linux 0.1. They are reinvented every second year.
  - toyg 10y ago
    Yeah but they never got traction for this or that reason. This time it looks like several big players actually agree on a common way forward. I guess time will tell.
c3833174 10y ago
>It's what happens with any rolling release distro given enough time. Not really, the KISS nature of arch means that stuff that could be automated isn't because reasons, while systemd gets a special pass.
- digi_owl 10y ago
  because systemd is a personal passion of one of the lead arch devs...
skykooler 10y ago
Of course, now you need to deal with docker itself updating constantly, and the client not being able to talk to the server if they're updated more than 3 months apart.
- SEJeff 10y ago
  Or just use rkt and don't worry about it. The CoreOS team takes api stability pretty seriously.

laumars 10y ago

It wasn't that bad. It did require manual intervention to get the install to work (which isn't a great surprise given the nature of the update) but it installed pretty painlessly on all bar one machine. The one exception being a laptop which I put off the update for several weeks and then left myself with a much larger job than it should have been - so really that one was partly my own fault. The glibc update from around the same time was a much worse update update. I think that one did break every Arch install I had at that time.

majewsky 10y ago

Interesting. I had zero trouble with this change on any of my boxes. Did not even have to --force the upgrade.

SSLy 10y ago

Well, the instructions on the frontpage were very clear and simple how to process the update.

dizzystar 10y ago

Not on Arch anymore, but I do remember that upgrade. I had no issues at all with it.