Post Ac1XO7ycY2Q8dDDRbM by stefano@mastodon.bsd.cafe
(DIR) More posts by stefano@mastodon.bsd.cafe
(DIR) Post #Ac0m0uzRyDI7qe2Dbc by stefano@mastodon.bsd.cafe
2023-11-20T22:20:31Z
0 likes, 0 repeats
FeeeBSD 14.0 has been officially announced. Tomorrow I'll begin with the upgrade process of some of my servers. Fingers crossed, but I'm confident that everything will be ok, as usual.#FreeBSD
(DIR) Post #Ac0p30oLbBlaLKX1OK by jamesoff@mastodon.jamesoff.net
2023-11-20T22:54:34Z
0 likes, 0 repeats
@stefano Gone are the days of waiting for .1? :) I think I’m still jaded from 5, was it?
(DIR) Post #Ac16r2eUj5g3kkMgHA by ianthetechie@fosstodon.org
2023-11-21T02:14:06Z
0 likes, 0 repeats
@stefano all good from me except that Firefox broke -_- Well not technically broke but the packages for 14 are still stuck at version 119, but 13 already cut a binary with 120. I don’t think I’m missing anything by going back to 119 but it’s problematic because I can’t open my old profile with an older version of Firefox. So yeah going into port building mode. It’s a slog lol
(DIR) Post #Ac1XO7ycY2Q8dDDRbM by stefano@mastodon.bsd.cafe
2023-11-21T07:11:26Z
0 likes, 0 repeats
@jamesoff I'll start with non-critical servers - and boot environments will help 🙂 When I'll have tested all the configurations/all use cases, I'll start with the critical servers. I'm proceeding this way with all the OSes, and usually I keep problems out (or deal with them on non critical machines) 🙂
(DIR) Post #Ac1XTyyquPIIT37FrM by philbaker1@fosstodon.org
2023-11-21T06:38:35Z
0 likes, 1 repeats
@ianthetechie @stefano I'm wondering if pkg-static upgrade -f... would help.My upgrade was on a VM with no GUI. No issues that I came across. I notice portsnap was gone, which I would have noticed earlier had I read the release notes. :)
(DIR) Post #Ac1XU0113qcRg38Us4 by ianthetechie@fosstodon.org
2023-11-21T06:45:31Z
0 likes, 0 repeats
@philbaker1 @stefano I actually did that and only 3 out of ~300 packages were downgraded and I can't even remember what the others were ;) The problem isn't that Firefox is broken per se; it launches, but it tells me clearly that I can't use a newer version's profile with an older version of Firefox (they aren't compatible from newer -> older).I ended up solving it by rebuilding the port, but that took a fair bit of mucking about since a lot of other deps also changed, creating some conflicts.
(DIR) Post #Ac1XU0uJkEr4RZ0f4K by ianthetechie@fosstodon.org
2023-11-21T06:48:04Z
0 likes, 0 repeats
@philbaker1 @stefano fortunately the conflicts were resolvable though; mostly a case of one package being obsoleted by another / a major version upgrade.Having mostly binary packages normally makes things easier, but actually complicated it in this case. I'm actually quite tempted at this point to just use ports henceforth. I already use the git + portmaster setup (git makes it *way* easier to contribute to ports than the old way IMO).
(DIR) Post #Ac1XU1ogMfwRGNNfvM by ianthetechie@fosstodon.org
2023-11-21T06:50:43Z
0 likes, 1 repeats
@philbaker1 @stefano I think it's actually going to be slightly easier if, given a working userland built from ports, you issue a global rebuild with portsnap, since ports would guarantee a stable (source) snapshot in time. You don't get that stability guarantee when upgrading binary packages *across major versions* the same way you do within the *same major version* quarterly snapshots.Anyways, hope this helps someone :)