pkg 2.0.0 problems

T-Aoki said:
Not precise.
kmod ports like graphics/drm-*-kmod installs kernel modules in /boot/modules/.
And firmware ports like sysutils/cpu-microcode-intel installs firmwares in /boot/firmware/.
These are because of possible problem on dedicated /usr/local partition.

And Linuxulator ports and anything running under Linuxulater are usually installed in /compat/linux/.

And more, if pkgbase become default, FreeBSD base components are installed using pkg, too (except src upgrades).

Things are going to be more complexed.
Click to expand...
There's lots of other details that automated upgrading fails to account for. Especially when they are added much later after the fresh install. This is why automated utilities are not to be really trusted. This is why I recommend going for a fresh reinstall every time. This is true in Linux camp as well. Just something that all Open Source OS users learn to live with and tolerate the consequences.
 
astyle said:
There's lots of other details that automated upgrading fails to account for. Especially when they are added much later after the fresh install. This is why automated utilities are not to be really trusted. This is why I recommend going for a fresh reinstall every time. This is true in Linux camp as well. Just something that all Open Source OS users learn to live with and tolerate the consequences.
Click to expand...
If I recall correctly, at start, ports framework considered (almost) fresh installation only.
The introduction of portupgrade drastically changed the situation (it was like a dream at the moment), but as things went more and more complexed, it got behind, unfortunately.
Other tools like portmaster popped in, but it was "race conditions" within ports framework and upgrading tools.
I think this is not yet drastically improved (improving slower than ports framework).
 
im not sure its related, but:
Code: 
~ sudo pkg install vscode
Updating FreeBSD repository catalogue...
Fetching data.pkg: 100% 10 MiB 5.3MB/s 00:02
Processing entries: 100%
FreeBSD repository update completed. 35847 packages processed.
All repositories are up to date.
The following 31 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
krb5: 1.21.3
libb2: 0.98.1_1
vscode: 1.96.4_3
Installed packages to be UPGRADED:
FreeCAD: 1.0.0_1 -> 1.0.0_2
boost-libs: 1.86.0_1 -> 1.87.0_1
harfbuzz-icu: 10.2.0 -> 10.2.0_1
icu: 74.2_1,1 -> 76.1,1
libcdr01: 0.1.8 -> 0.1.8_1
libcmis: 0.6.2_3 -> 0.6.2_4
libe-book: 0.1.3_28 -> 0.1.3_29
libixion: 0.19.0_3 -> 0.19.0_4
libmspub01: 0.1.4_24 -> 0.1.4_25
liborcus: 0.19.2_3 -> 0.19.2_4
libqxp: 0.0.0_24 -> 0.0.0_25
libreoffice: 25.2.0.3 -> 25.2.0.3_2
librewolf: 134.0.2_1 -> 135.0_1
libvisio01: 0.1.8 -> 0.1.8_1
libzmf: 0.0.2_29 -> 0.0.2_30
poppler: 24.02.0_2 -> 24.12.0
poppler-glib: 24.02.0_2 -> 24.12.0
poppler-utils: 24.02.0_2 -> 24.12.0
postgresql16-server: 16.6 -> 16.7_1
qt5-core: 5.15.16p130 -> 5.15.16p130_1
qt6-base: 6.8.2 -> 6.8.2_2
raptor2: 2.0.16_3 -> 2.0.16_4
vte3: 0.78.2 -> 0.78.2_1
webkit2-gtk_40: 2.46.5_2 -> 2.46.5_3
Installed packages to be REINSTALLED:
cups-filters-1.28.17_6 (required shared library changed)
Installed packages to be REMOVED:
deluge: 2.1.1_2,2
deluge-cli: 2.1.1_3
py311-libtorrent-rasterbar: 1.2.20,2
Number of packages to be removed: 3
Number of packages to be installed: 3
Number of packages to be upgraded: 24
Number of packages to be reinstalled: 1
The process will require 344 MiB more space.
475 MiB to be downloaded.
Have no idea why ... have no idea why deluge is being removed ... allowed to carry on - yep, deluge is gone !

Code: 
➜  ~ sudo pkg install deluge
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'deluge' have been found in the repositories
➜  ~ sudo pkg install net-p2p/deluge
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'net-p2p/deluge' have been found in the repositories
I thought its automatically updated/upgraded but no ..
Code: 
➜  ~ sudo pkg update
Updating FreeBSD repository catalogue...
pkg: Repository FreeBSD has a wrong packagesite, need to re-create database
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01
Fetching data.pkg: 100%   10 MiB   5.3MB/s    00:02
Processing entries: 100%
FreeBSD repository update completed. 35847 packages processed.
All repositories are up to date.
➜  ~ sudo pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (515 candidates): 100%
Processing candidates (515 candidates): 100%
The following 21 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        aom: 3.11.0 -> 3.12.0
        binutils: 2.43.1,1 -> 2.44,1
        chromium: 132.0.6834.159 -> 132.0.6834.159_1
        cpu-microcode-intel: 20241112 -> 20250211
        drm-61-kmod: 6.1.92.1402501_3 -> 6.1.128.1401000
        exiv2: 0.28.3,1 -> 0.28.4,1
        gpgme: 1.24.1 -> 1.24.2
        gpgme-cpp: 1.24.1 -> 1.24.2
        libpsl: 0.21.5_1 -> 0.21.5_2
        lp_solve: 5.5.2.5 -> 5.5.2.5_1
        mesa-devel: 25.0.b.479 -> 25.0.b.664
        nss: 3.107 -> 3.108
        openldap26-client: 2.6.9 -> 2.6.9_1
        openssl: 3.0.15_1,1 -> 3.0.16,1
        postgresql16-client: 16.6_1 -> 16.7_1
        py311-boost-libs: 1.86.0 -> 1.87.0
        qpdf: 11.9.1 -> 11.10.0
        qt6-multimedia: 6.8.2 -> 6.8.2_1
        sqlite3: 3.46.1,1 -> 3.46.1_1,1
        vm-bhyve-devel: 1.6.2.4 -> 1.6.2.15
        wayland-protocols: 1.39 -> 1.40

Number of packages to be upgraded: 21

The process will require 6 MiB more space.
199 MiB to be downloaded.

P.s pkg is from latest ... if i do quarterly - some apps going to be deleted
 
You must log in or register to reply here.
Back
Top