Bug 250056 - Ports prematurely demanding the latest ports-mgmt/pkg
Summary: Ports prematurely demanding the latest ports-mgmt/pkg
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Port Management Team
Depends on:
Reported: 2020-10-02 20:15 UTC by Jason W. Bacon
Modified: 2020-10-02 20:26 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Jason W. Bacon freebsd_committer 2020-10-02 20:15:31 UTC
I just upgraded my packages with pkg upgrade and ports with portsnap and currently cannot build any ports from source unless I first install the latest ports-mgmt/pkg from source.

I assume this will resolve itself as soon as pkg builds catch up on ports-mgmt/pkg, but I wonder if there's a way we can avoid this situation in the future.

Glitches like this can be a turn-off to new users exploring FreeBSD.

root@mako:/usr/ports/biology/muscle # make
===>  muscle-3.8.1551 pkg(8) must be version 1.15.8 or greater, but you have
1.15.6. You must upgrade the ports-mgmt/pkg port first.
*** Error code 1

make: stopped in /usr/ports/biology/muscle

root@mako:/usr/ports/biology/muscle # pkg update -f
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
Fetching packagesite.txz: 100%    6 MiB 733.2kB/s    00:09    
Processing entries: 100%
FreeBSD repository update completed. 31885 packages processed.
All repositories are up to date.

root@mako:/usr/ports/biology/muscle # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Updating database digests format: 100%
Checking for upgrades (3 candidates): 100%
Processing candidates (3 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
Comment 1 Baptiste Daroussin freebsd_committer 2020-10-02 20:26:26 UTC
Yes it is unfortunate that it had to be bumped that quickly but the bug it fixes mandated it. Of course it is not in the intention of anyone to have those bump happening so often/quickly.

This is also why it happens on the latest branch and not on the quarterly and why it happens soon after branching the latest quarterly.
Most end users should use quarterly.