How can I find out what the different meta-packages are and which packages they pull in?
init (for rc.d) but not a shell. How do I know which packages I install?
pkg search FreeBSD-set- and look at descriptions. i'm working on a manpage for this, but it hasn't landed yet.FILES_IGNORE_GLOB option to get something suitable.Is this happening via a Phabricator review process?
With pkgbase landing in 15.0, I decided that it's time to announce the
timeline for deprecation of the legacy "distribution sets". Here's the
plan:
15.0-RELEASE:
* PKGBASE becomes the default in release/Makefile and a new NOPKGBASE
option is added.
* The installer supports both install options, with dist sets marked
as "legacy" in the pick-how-to-install menu.
* The disc1 images only contain a pkgbase repo; people who want to install
from disc1 without pkgbase will need an internet connection.
* The dvd images contain both dist sets and a pkgbase repo suitable for
offline installation with either mechanism.
* Traditional FreeBSD Update will work for the entire 15.x branch, including
security updates, since this is relatively easy to do as long as we have dist
sets.
* Work is underway to make freebsd-update behave as a wrapper around pkgbase
on pkgbase-enabled systems (right now it just refuses to do anything).if you're talking about packages in the (remote) repository, then no, you can query the repository regardless of whether the local system uses pkgbase. the repository config looks like this:
FreeBSD-base: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}/etc/pkg by default./etc/pkg.disabled and using pkg -R /etc/pkg.disabled search ..., which will ensure no other pkg commands pick it up.
/var/cache/pkg would be lovely, instead of downloading the same packages every time one wants to fire a jail.FREEBSD-UPDATE SHOULD NOT BE USED TO UPGRADE TO 15.0-ALPHA4 AT PRESENT.
An Errata Notice will be issued shortly to correct a bug in freebsd-update
which renders systems inoperative when upgrading to 15.0.upgrading from previous 15.0 alphas with "pkg upgrade" is supported and
should work fine; if not, that's a bug. however, do read UPDATING as
there were quite a few changes to pkgbase during the 15.0 release cycle.
the pkg.f.o packages are currently built twice a day, so if ALPHA4 isn't
available there yet, it will be shortly.Forgive me, but no packages available for “FreeBSD-set-base”
did you install from 15.0 installation media (in which case, which version)? what version are you currently using? what pkg(8) command are you using? what pkg repositories do you have configured?
yes, the package sets won't be backported to 14.x.
FreeBSD-* (like poudriere).
can you outline the use-case for this, i.e. when would you want to do that?
I'm using pkgbase for now just for testing it but I'll eventually migrate to compiling from source like always.
Nice to hear it works on 14.3. 15.0-ALPHA4 wasn't updated yet.
I believe it should be done via pkg just like this:
$ pkg update -r FreeBSD-base
$ pkg upgrade -r FreeBSD-basehm... i'm not sure if this is something we want to commit to supporting long-term, which would probably be necessary if it's documented in the Handbook since someone will find a way to rely on it. going in the other direction (dist sets -> pkgbase) will only be supported for 15.0, and maybe 16.0, as a temporary migration path.
/var/db/pkg, then re-installing your ports. obviously create a new BE to try this on, i've never tested it.if you build pkgbase from source, there's no difference. if you're using the packages from pkg.freebsd.org, those are not supported by secteam, so security updates are on a best-effort basis. in practice, those packages are rebuilt from each branch twice daily, so it shouldn't take too long for updated packages to arrive.
you still get FreeBSD-* packages if you build pkgbase from source, the problem (at least for development branches like -CURRENT and -STABLE) is the packages are stamped with the build date, so if you switch from pkg.freebsd.org to local packages, then back, pkg might be confused about what the latest version of the package is. i expect that would sort itself out after a couple of days though.
the package builds for pkg.freebsd.org are automated, releng has nothing to do with that. (i believe bapt is the one who mostly takes care of them.)
I experienced the same on my test system. Will retry when the next alpha is released.
You tried with ALPHA4?
I seem to need
/usr/share/keys/pkg in the root directory:root@jailhost:~ # freebsd-version -kru
15.0-ALPHA4
15.0-ALPHA4
15.0-ALPHA4
root@jailhost:~ # zfs create zroot/jails/templates/15
root@jailhost:~ # pkg -r /jails/templates/15 install -y FreeBSD-set-minimal-jailpkg: Error loading trusted certificates. After I copy /usr/share/keys/pkg into the root directory it works, but I wouldn't expect that to be necessary.