Conflict hell after freebsd-update

Based upon bsdinstall/scripts/auto#L208-L218:
Bash:
if [ ! -f $BSDINSTALL_DISTDIR/MANIFEST ]; then
    PKGBASE=yes
else
    bsddialog --backtitle "$OSNAME Installer" --title "Select Installation Type" \
        --yes-label "Distribution Sets" --no-label "Packages (Tech Preview)" --yesno \
        $PKGBASE_DEFAULT_BUTTON \
        "Would you like to install the base system using traditional distribution sets or packages (technology preview)?" 0 0
    if [ $? -eq 1 ]; then
        PKGBASE=yes
    fi
fi
the term actually used is Packages (Tech Preview). On 14.2|3-RELEASE and 14-STABLE pkgbase was "experimental".

I believe whether or not Packages (Tech Preview) is presented as the default option, depends on what image you are installing FreeBSD15.0-RELEASE from; AFAIK, if I'm reading this correctly, when both options are available and a MANIFEST is present then the default option is "distribution sets". IIRC a minimal (smallest?) memstick or ISO image does only offer the option of installing a packaged base; there simply isn't room for both options when space is at a minimum.


This has been discussed rather fiercly on the MLs. The fact remains that, although this is in accordance to the documented behaviour of pkg-delete(8), in the era of pre-base packages this was often used to "get rid" of any non-base stuff, that is: packages from the ports tree, and have a clearly defined state with only the base install. Some work/ideas seem to be in the making where it is easy to not affect base packges when issueing such a rigorous pkg-delete or pkg-remove command; I'm not aware of the current status of these developments.
Thanks for the clarification. Yes "Packages (Tech Preview)" is the correct term - my previous wording was based on my memory of the installer.

I really appreciated that packages were separated from the base system in the past. Hopefully, this can be achieved again with a flag or similar option in pkg, allowing users to either include or exclude base packages as needed.
 
Regardless if pkgbase or not, or 3rd party packages, it's not a good idea to pkg-delete(8) -y, --yes Assume yes when asked for confirmation before package deletion. without checking what packages are removed.
Sometimes this is what you want, at least in the past, to get a clean base system. The fact that is now removes the kernel is absolute madness.
 
My installation was actually FreeBSD 12 initially and I've been upgrading it. I decided to run pkgbasify yes so that is my fault.

However, I did a fresh installation right now and pkgbase (Experimental Tech) was the default selected option in the installer. Weird to have a experimental feature selected by default. I chose freebsd-update of course.
Well, it's a matter of choice. That said, it's not surprising because it is said that freebsd-update will be deprecated and, in the future, you will have nothing else than pkgbase. The future in question might be 16.0-RELEASE.

My main point was: this thead isn't about pkgbase. Don't mix things.
 
Well, it's a matter of choice. That said, it's not surprising because it is said that freebsd-update will be deprecated and, in the future, you will have nothing else than pkgbase. The future in question might be 16.0-RELEASE.

My main point was: this thead isn't about pkgbase. Don't mix things.
I suspected pkgbasify.lua since it overwrites the user repro conf file. But others in this thread reported the same issue with freebsd-update so it can't be that.
 
Ah, that did the trick, tho I don't completely understand why. Is it because it was trying to pull latest and quaterly ports? I don't even remember installing ports when I first installed this system, as I am very tight in space (I needed them later, and if I remember correctly, it was simply a git clone).

Another worrying (for me) thing I found out reading previous posts is people using that pkgbasify thing. I looked it up and it seems updating freebsd can be done with that thing. Is freebsd-update being phased out? if so why?

Anyway, thanks a lot for everyone's help. I think I can mark this as solved now
 
Another worrying (for me) thing I found out reading previous posts is people using that pkgbasify thing. I looked it up and it seems updating freebsd can be done with that thing. Is freebsd-update being phased out? if so why?
For what it's woth, on snapshots of 16 CURRENT, at least the ones I've used, as recently as a few days ago, pkgbase was still being shown as Tech Preview. As to why, while I don't know the ins and outs, I think, (but my memory is going) that the maintainer of it said it was getting difficult to maintain, but I could be wrong. I'm sure that if you did some web searching you might find the reasons behind it. (That sounds nasty when I re-read it, but it's not meant to be--it's just that I'm too lazy to search, and the reasons don't matter that much to me).
Using pkgbase, even to update to 15 isn't that hard when you know what to do. The trouble is that the handbook's page on it leaves out some needed information. I have a page on it, at least for updating on ZFS, https://srobb.net/fbsd14_15.html, but you'll note that there's a lot fewer posts on having problems with it than there were a few weeks ago.
 
I have to say, I tough everything worked, until I tried to install a package and it froze looking for it. I tried updating and upgrading, and it just loops without doing anything....
pkg-static upgrade -f
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
FreeBSD-kmods repository is up to date.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
Checking integrity... done (0 conflicting)

It doesn't matter if I use pkg upgrade, or what. This is what I get
 
When using the traditional upgrade process from a non-packaged base FreeBSD 14.x-RELEASE to a non-packaged base 15.0-RELEASE using freebsd-update(8), you'll only need to use pkg-static(8) (instead of just pkg(8)) in case things have gone a bit wrong.
I have to say, I tough everything worked, until I tried to install a package and it froze looking for it. I tried updating and upgrading, and it just loops without doing anything....
pkg-static upgrade -f
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
FreeBSD-kmods repository is up to date.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
Checking integrity... done (0 conflicting)

It doesn't matter if I use pkg upgrade, or what. This is what I get
Based on your output you do not have all pkg configuration settings correct.
Please post the output of:
pkg -vv | sed -nE -e '/(OSVERSION|ABI|BACKUP)/ p' -e '/^Repositories:/,$ p'
grep -EH '^[^#].*' /usr/local/etc/pkg/repos/*.conf
freebsd-version -kru
 
Back
Top