FreeBSD 15.0-ALPHA3 Available

[FreeBSD News]

Original article here.
Consider this when replying.

The third ALPHA build for the FreeBSD 15.0 release cycle is now available. ISO images for the amd64, armv7, aarch64, powerpc64, and powerpc64le architectures are FreeBSD mirror sites.

Continue reading...

 

[Charlie_]

FreeBSD 15.0-ALPHA3 Now Available

Upgrading to 15.0-ALPHA3 is not yet possible using freebsd-update, but it is
anticipated to become possible shortly.
... this
has (at the time this announcement is being written) not yet been tested.

 

[SirDice]

Upgrading to 15.0-ALPHA3 is not yet possible using freebsd-update

Not surprising, freebsd-update(8) really only works for the releng/* branches (i.e. -RELEASE). The ALPHA builds are done from the stable/15 branch. BETA1 will probably be available with freebsd-update(8), that's going to be the first build of releng/15.0.

 

[mer]

Not surprising, freebsd-update(8) really only works for the releng/* branches (i.e. -RELEASE). The ALPHA builds are done from the stable/15 branch. BETA1 will probably be available with freebsd-update(8), that's going to be the first build of releng/15.0.

Get your ZFS boot envirionments in order. And a "prewarning" keep an eye on packages make sure the ones important to you build before you upgrade.

 

[Charlie_]

Not surprising, freebsd-update(8) really only works for the releng/* branches (i.e. -RELEASE).

FreeBSD 15.0-ALPHA2 Now Available

=== Upgrading ===

The freebsd-update(8) utility cannot be used to upgrade to 15.0-ALPHA1.

At present we anticipate that it will be possible to use freebsd-update(8)
to upgrade to 15.0-ALPHA3.

 

[scottro]

I mentioned in another thread that I ran a pkg update, pkg upgrade on a 15.0-ALPHA2 and it updated to ALPHA3. No problems, though it's small install, just runs openbox, and everything is still working after the upgrade.

 

[rbranco]

I can't uninstall FreeBSD-lp. I get:

$ doas pkg remove FreeBSD-lp
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
1 packages requested for removal: 0 locked, 1 missing

 

[anguisette]

I can't uninstall FreeBSD-lp. I get:

$ doas pkg remove FreeBSD-lp
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
1 packages requested for removal: 0 locked, 1 missing

edit: never mind, i thought you were installing it rather than removing it. correct answer:

because lp is part of the base set, you need to remove freebsd-set-base first: pkg remove -f freebsd-set-base. then you can remove freebsd-lp as normal. the diagnostic from pkg(8) is very bad here, which has been reported upstream: https://github.com/freebsd/pkg/issues/2517. i'll chase this since we definitely want this fixed before release.

 

[Charlie_]

Re: FreeBSD 15.0-ALPHA3 Now Available

DO NOT USE FREEBSD-UPDATE TO UPGRADE TO 15.0-ALPHA3.

It will break your system by installing a new libc before it installs libsys.

We'll fix freebsd-update to install libraries in the right order but until
that patch (and resulting Errata Notice) comes out this isn't going to work.

 

[scottro]

Interesting. I have a minimal 15.0 install and as its minimal there's no UPDATING. I just upgraded to ALPHA4 and now tint2, or, if in fluxbox, fluxbox's panel, as well as dmenu, will only show upper case, e.g., the date reads as SATURDAY, etc.
The only other thing I tested was alacritty terminal, which is fine, does lower case as expected. I thought it might be a font setting, but if so, I can't find it. Charlie_ , by any chance, was there anything about it in UPDATING?

 

[Charlie_]

This is UPDATING.

https://cgit.freebsd.org/src/plain/UPDATING?h=stable/15

 

[scottro]

After asking, I realized it was a stupid question, as anything about it would be in /usr/ports/UPDATING but thanks.

 

[scottro]

And, after that, I just tried a fresh install of ALPHA4 and everything is fine, that is tint2 and dmenu show their normal lower case.

 

[T-Aoki]

This is UPDATING.

https://cgit.freebsd.org/src/plain/UPDATING?h=stable/15

I think UPDATING for base (/usr/src/UPDATING if having src tree at default place) would be worth installed as /UPDATING or /usr/share/doc/UPDATING or somewhere easy to find by bsdinstall and maintained as part of base FreeBSD with freebsd-update(8).

But PkgBase could be the game-changer here.

I myself never tried PkgBase (I'm on source upgrading path), but for ports, pkg records /usr/ports/UPDATING at least for any entry related with installed pkgs and shows using pkg updating (see pkg-updating(8) for details). Why not for base pkgs?

 

[T-Aoki]

After asking, I realized it was a stupid question, as anything about it would be in /usr/ports/UPDATING but thanks.

Note that /usr/src/UPDATING is for base (src) and /usr/ports/UPDATING is for ports/pkgs. These are different files.

But something affecting both (i.e., some changes in base affects ports/pkgs and some descriptions are needed for both, with a bit of differences.

For <virtual> example, if base component AAA, which is imported "contrib" software switches its implementation BBB with, i.e., license changes to GPL and its consumers are forced to be rebuilt and modifying related configs, base side would have something like:

Any consumers of AAA needs rebuilding as of transision to BBB.
This would also require changes for configurations.
...

And if the switch rarely affect (just a few ports require AAA) ports/pkgs,
UPDATING entry for /usr/ports/UPDATING should list all affected ports/pkgs in the corresponding entry (or splitted into multiple entries).

This is because there can be locally developed programs at users side, which are NOT AT ALL in ports tree, thus, cannot limit the descriptions for specific affected ports only in /usr/src/UPDATING.