Pkgbase 15 to 15.1 stories?

Zare

Zare

As this is probably the first instance of release FreeBSD being upgraded by another means, I wanted to do some chit chat before the upgrade.
The minor version bump using pkgbase looks pretty straightforward.
However the major version bump seems awfully "rude" as if there was not a procedure but a way to make it work that way using env vars and complicated workflow.

Has anyone done it yet, 15 to 15.1 using pkgbase, did it go seamless per instructions?
 
Hi Mate

I upgraded to 15.1 using pkgbase

Using a bectl boot environment and poudriere to build the nvidia-driver and nvidia-drm-66-kmod
Which took 11 and half hours to build on my Dell xps 15 2019 with 16 gb of ram

Heres the forum post

NapoleonWils0n

Thread 'Success Freebsd 15.1 upgrade with pkgbase and Poudriere'

I just upgrade to Freebsd 15.1 with pkgbase and Poudriere on my Dell XPS 15 2019

I used a bectl boot environment with Poudriere to install the new Nvidia driver and nvidia-drm-66-kmod

The trick is you have to split the Poudriere set up into 2 parts
You can do part of the poudriere set up while on 15-p10

But you have to build the jail and install the ports once you have booted into Freebsd 15.1
because you cant build a Freebsd 15.1 jail on Freebsd 15-p10

The notes exceed the character count for a forum post so here are the notes on github...
  • Like

and my notes

github.com

cerberus/freebsd/freebsd-15-1-upgrade.org at master · NapoleonWils0n/cerberus

cerberus code library. Contribute to NapoleonWils0n/cerberus development by creating an account on GitHub.
github.com github.com
 
Zare said:
As this is probably the first instance of release FreeBSD being upgraded by another means, I wanted to do some chit chat before the upgrade.
The minor version bump using pkgbase looks pretty straightforward.
However the major version bump seems awfully "rude" as if there was not a procedure but a way to make it work that way using env vars and complicated workflow.

Has anyone done it yet, 15 to 15.1 using pkgbase, did it go seamless per instructions?
Click to expand...

Yes, and ran into PR 296052 as per this thread.

/grandpa
 
Been smooth on several upgrades. I did run into issues with the machine that had an Nvidia card. I also used bectl first to create a backup boot environment. For me, I had to, after updating the machine with Nvidia, update ports to the newest, and then install nvidia-drm-kmod and nvidia-drm-66-kmod. Gory details here

S

Post in thread 'Good news today'

Ok, this might be a longish one, and I even thought of giving it its own thread, but anyway...

My main workstation is an older Dell with an Nvidia card. I went to update it via the instructions, but it said it was up to date, though it was running 15.0-p10. So, I finally realized that on both this machine and the headless one that I couldn't update until I edited what was in /usr/local/etc/pkg/repos that both this one and the headless one had a FreeBSD-base.conf as well as FreeBSD.conf, and that FreeBSD.conf has a line
Code: 
 FreeBSD-base: { enabled: yes }.
So yesterday, I fixed...
  • Thanks

But on a few AMD machines and a Thinkpad laptop, all went smoothly.
 
Yes no problem
S

Post in thread 'Good news today'

Well, I upgraded my secondary machine, which went fine. As mentioned, that headless one wasn't upgrading, so I just edited its /usr/local/etc/pkg/repos/FreeBSD.conf to match the one that upgraded successfully, then it pulled in the necessary packages and upgraded to 15.1. All machines are on packagebase. Pretty straight forward.
  • Thanks
  • Like
Upgrade
 
I'm writing a script for that, but it's not yet ready.

It managed these upgrades:

- 15.0-RELEASE -> 15.1-RC2
- 15.1-RC2 -> 15.1-RELEASE
- 15.0-RELEASE -> 15.1-RELEASE
- 15.1-RELEASE -> 15-STABLE
- 15.0-RELEASE -> 15-STABLE
- 15.1-RELEASE -> 16-CURRENT

It works for major version change.
It uses both temporary repo conf file and var ABI change.
It checks and avoids some pitfalls.
It forces kmods upgrade in all cases and all pkg in case of a major version upgrade.

I'm convinced we need a tool like this as we have freebsd-update on the other side.
So, I move things forward, at least for me, as upgrades under pkgbase aren't as easy as with freebsd-update.
 
I'm not doing pkgbase, but since pkg has worked just fine for a long time, I would think pkgbase should be no different.

What NapoleonWils0n and scottro say about manually creating a new BE is a good idea; especially since one can mount a BE and pkg supports a "-c" option which does a chroot.
When I do an upgrade across a release, I create new BE, mount it, use freebsd-update with -b and -d to do the updates into the new BE, then pkg-static -c to upgrade the new BE.
That should also work for pkgbase (of course not using freebsd-update).

An advantage of doing this is a single reboot into the new BE, you can make the new BE consistent with base and ports, you can tweak etc/rc.conf to not load problematic modules (drm).
 
I went from a 15.0-RELEASE installed with pkgbase to 15.1-RELEASE and couldn't log in after the upgrade. The pam related packages were missing for some reason. Installed those and was able login.

Also found that I had a slew of older packages that had to be manually removed. This was likely due to some mistake on my part months ago.

pkgbase is MUCH more fragile than freebsd-update imo. It tends to be easier to fix if there is an issue but there was very seldom an issue with freebsd-update. ymmv.
 
dkh said:
I went from a 15.0-RELEASE installed with pkgbase to 15.1-RELEASE and couldn't log in after the upgrade. The pam related packages were missing for some reason. Installed those and was able login.

Also found that I had a slew of older packages that had to be manually removed. This was likely due to some mistake on my part months ago.

pkgbase is MUCH more fragile than freebsd-update imo. It tends to be easier to fix if there is an issue but there was very seldom an issue with freebsd-update. ymmv.
Click to expand...
That was on the release notes: https://www.freebsd.org/releases/15.1R/relnotes/#userland-packages
 
dkh said:
pkgbase is MUCH more fragile than freebsd-update imo. It tends to be easier to fix if there is an issue but there was very seldom an issue with freebsd-update. ymmv.
Click to expand...
Is it really more fragile or is it "different from freebsd-update" which requires rethinking ones process?
I pointed out in another thread that one can create a new BE, effectively chroot into it and do all the updates. That would give a person a coherent BE on the new versions (base and applications/ports) and would require a single reboot.
freebsd-update gives you a bit of protection by automatically creating a new BE (default setting) when you do freebsd-update install.
Lots of people will create a new BE before doing pkg upgrade around quarterly; perhaps that mindset will make pkgbase feel less fragile.
 
You must log in or register to reply here.
Back
Top