pkg 2.0.0 problems

I have tried waiting out the teething pains with pkg 2.0.x, and decided to give pkg upgrade a shot today. Thank God I do a bectl create Before_pkgUpgrade before actually doing the upgrade...

The upgrades worked on the servers, that are command line only, no GUI, but neither my desktop and laptop, which both run KDE/plasma5 fared nearly as well. I ended up having to roll back to my pre-upgrade BE. So there are a bunch of plasma6 packages installed, and plasma5-plasma-desktop and plasma5-plasma were deinstalled:

Code: 
Checking for upgrades (1140 candidates): 100%
Processing candidates (1140 candidates): 100%
The following 468 package(s) will be affected (of 0 checked):

 Installed packages to be REINSTALLED:
        gcc11-11.5.0 (provided shared library changed)
        gcc12-12.4.0 (provided shared library changed)
        gcc13-13.3.0 (provided shared library changed)
        libssh-0.11.1 (options changed)
        llvm15-15.0.7_10 (provided shared library changed)
        llvm17-17.0.6_8 (provided shared library changed)
        nvidia-driver-550.127.05.1401000 (provided shared library changed)

Installed packages to be REMOVED:
        akonadi-notes: 23.08.5
        digikam: 8.5.0
        kalarm: 23.08.5
        kdepim: 23.08.5_2
        kopete: 23.08.5_1
        kphotoalbum: 5.12.0_2
        phonon-vlc-qt5: 0.12.0_1
        plasma5-plasma: 5.27.11
        plasma5-plasma-desktop: 5.27.11_2
        vlc: 3.0.21_10,4

Number of packages to be removed: 10
Number of packages to be installed: 115
Number of packages to be upgraded: 336
Number of packages to be reinstalled: 7

The process will require 823 MiB more space.
2 GiB to be downloaded.

So sddm was apparently reset from the customizations I had made, and when I select "User Session" which should be KDE, the desktop never comes up...So at this point, I'm not sure if it is leftover problems from the pkg upgrade or whether KDE was not upgraded correctly. Since it occurred on both hosts with GUIs, I'm not sure which it might be.

Any suggestions? I feel like I am stuck, at this point, can't upgrade, can't install new packages, until this is resolved.

Thanks.
 
VulcanRidr said:
Any suggestions? I feel like I am stuck, at this point, can't upgrade, can't install new packages, until this is resolved.
Click to expand...
Yeah, this is exactly why I switched to ports - compiling and installing with make && make install is far less painful. Time consuming (even on fairly capable hardware), but I'd rather spend the time compiling than dealing with the pkg(8) train wreck. When I upgrade, that really means a clean start from scratch, install a fresh -RELEASE of FreeBSD base, and grab a fresh copy of ports from cgit.freebsd.org... 😩 And I only 'upgrade' when Firefox stops working.

I'd say, very smart move to use BEs before playing with upgrades, that does make it easy to roll back from a train wreck - not that many rank-and-file users are savvy enough to think of this. 👍

I really like KDE myself, and at one point I was working on a Poudriere-based project to see if I can achieve a way to compile only newer versions of KDE (a long list of KDE-specific ports) against existing stuff, and upgrade that way. Well, that fell apart because other stuff IRL demanded my attention... oh, well.
 
Given current circumstances, it is good that you made use of the BE option to provide for an easy 'way-back'.

VulcanRidr said:
So sddm was apparently reset from the customizations I had made, and when I select "User Session" which should be KDE, the desktop never comes up...So at this point, I'm not sure if it is leftover problems from the pkg upgrade or whether KDE was not upgraded correctly. Since it occurred on both hosts with GUIs, I'm not sure which it might be.

Any suggestions?
Click to expand...
It is not clear in what environment exactly you have tried upgrading your packages; please provide the following context:
pkg -v
pkg -vv | sed -n '/^Repositories:/,$ p'
freebsd-version -kru
 
VulcanRidr said:
The upgrades worked on the servers, that are command line only, no GUI, but neither my desktop and laptop, which both run KDE/plasma5 fared nearly as well.
Click to expand...
A quite dumb question. (Assuming you're on latest [aka main] branch of ports tree, as 2025Q1 does not have pkg 2.x.)

Have you read UPDATING entry dated 20250203? (Linked to github mirror, as currently cgit repo does not work correctly for me.)
KDE on latest is now KDE6.
 
VulcanRidr said:
I have tried waiting out the teething pains with pkg 2.0.x, and decided to give pkg upgrade a shot today. Thank God I do a bectl create Before_pkgUpgrade before actually doing the upgrade...

The upgrades worked on the servers, that are command line only, no GUI, but neither my desktop and laptop, which both run KDE/plasma5 fared nearly as well. I ended up having to roll back to my pre-upgrade BE. So there are a bunch of plasma6 packages installed, and plasma5-plasma-desktop and plasma5-plasma were deinstalled:

Code: 
Checking for upgrades (1140 candidates): 100%
Processing candidates (1140 candidates): 100%
The following 468 package(s) will be affected (of 0 checked):

 Installed packages to be REINSTALLED:
        gcc11-11.5.0 (provided shared library changed)
        gcc12-12.4.0 (provided shared library changed)
        gcc13-13.3.0 (provided shared library changed)
        libssh-0.11.1 (options changed)
        llvm15-15.0.7_10 (provided shared library changed)
        llvm17-17.0.6_8 (provided shared library changed)
        nvidia-driver-550.127.05.1401000 (provided shared library changed)

Installed packages to be REMOVED:
        akonadi-notes: 23.08.5
        digikam: 8.5.0
        kalarm: 23.08.5
        kdepim: 23.08.5_2
        kopete: 23.08.5_1
        kphotoalbum: 5.12.0_2
        phonon-vlc-qt5: 0.12.0_1
        plasma5-plasma: 5.27.11
        plasma5-plasma-desktop: 5.27.11_2
        vlc: 3.0.21_10,4

Number of packages to be removed: 10
Number of packages to be installed: 115
Number of packages to be upgraded: 336
Number of packages to be reinstalled: 7

The process will require 823 MiB more space.
2 GiB to be downloaded.

So sddm was apparently reset from the customizations I had made, and when I select "User Session" which should be KDE, the desktop never comes up...So at this point, I'm not sure if it is leftover problems from the pkg upgrade or whether KDE was not upgraded correctly. Since it occurred on both hosts with GUIs, I'm not sure which it might be.

Any suggestions? I feel like I am stuck, at this point, can't upgrade, can't install new packages, until this is resolved.

Thanks.
Click to expand...
I'm currently trying to fix falkon [ feb 3 .0 ] which crashes on startup and won't build [ feb 9 .2 ] , maybe the latter will appear in packages someday again for amd64-stable. Firefox works without sound and otter-browser works with sound, however.
 
jb_fvwm2 said:
I'm currently trying to fix falkon which crashes on startup and won't build either probably due to the same upgrade. Firefox works without sound and otter-browser works with sound, however.
Click to expand...
That's a surprise... I have www/firefox at v. 133.0.3 compiled from scratch (compilation goes MUCH faster compared to what it was just a few years ago!), and it works fine with sound, I use it for Youtube...

The switch to KDE 6 does look like a bit of a hurried job - those Makefiles in the Ports infrastructure are rather complicated to rewrite and debug! As an example:
1739387309618.png


Also: Makefile for math/cantor still mentions math/sage, even though that port expired on Dec. 31, 2024, and is no longer in the ports tree! I'm being stubborn about it, and trying to comile SageMath on FreeBSD anyway, but that's my personal itch.

So, I would not hurry to upgrade just yet. But if anyone was able to make KDE 6 run on Wayland using the ports tree that we have right now - please post about it! I'm particularly interested in seeing if amdgpu finally plays well with Wayland on metal.
 
May I suggest that problems with KDE (5 or 6) moves to a new thread. This one is about problems around pkg 2.0x
The problems with KDE has as far I can se nothing to do with that (although initially it looked to some like it might have been the case)
 
larshenrikoern said:
May I suggest that problems with KDE (5 or 6) moves to a new thread. This one is about problems around pkg 2.0x
The problems with KDE has as far I can se nothing to do with that (although initially it looked to some like it might have been the case)
Click to expand...
The point of my post is to show that while pkg 2.0 may have issues, sometimes the real problem is not with pkg 2.0, but the repos it is looking at. pkg 2.0 may be fine, but if you feed it crap, it will spit out crap.

Kind of like textproc/xmlto complaining about malformed XML...
 
Can someone explain in simple terms what is happening with pkg?
I had FreeBSD 14.2 installed on a system that I use from time to time.
Well, I left this system powered off for quite a while and when I powered it on again, I wanted to update everything - and you can guess what happened: pkg first upgraded itself then proceeded to upgrade the rest of the packages, except that it never did this, because it always ended up in a failure, something about some lines in a package.
I tried some solutions, after reading some advice, including forcing an upgrade of all installed packages, reinstalling them, etc but nothing worked.
Notice that I said that "I had FreeBSD installed" - that is because I was so enraged by this that I deleted FreeBSD entirely and installed Debian.

I still would like to have FreeBSD again but not with this problem - never encountered something like this, until now. I don't want to use ports, I prefer binary packages so this is a deal breaker for me.

So, what is happening and when will this be fixed?
 
Dendros said:
So, what is happening and when will this be fixed?
Click to expand...
What's happening is frankly dependency hell, same issue that Debian has anyway. If you try to upgrade Debian packages, you'll end up with a train wreck that forces you into a clean reinstall of the system. I'd know, I experienced exactly that when one of my Computer Science classes in college used Debian to study networking. Somebody wanted to update MRTG on one of the servers that was used for practice. Well, guess what, that turned out to be a train wreck, and the entire server had to be swapped out.

Dependency hell is a problem that affects any Linux distro, BSDs are not immune to it, either. Flatpaks, .deb, RPM, .pkg, you name it - dependency hell is the same no matter where you look. There's people doing research on how to ameliorate that problem. However, there's no easy, elegant solution, only time consuming kludges that get hacked up by different camps, and nobody's on the same page about what even works. Distro hopping only introduces you to new ways to accomplish pretty much the same upgrade train wreck that arises out of dependency hell.

No matter the distro, no matter the BSD flavor, if you use an Open Source OS, you'll be stuck with dependency hell that forces you to do a clean, complete reinstall every time you want an upgrade. I personally decided to stick with FreeBSD in part because of the "If it ain't broke, don't fix it" ethos (Although this thread does not inspire my confidence in how well that idea sticks). There's other reasons that I won't go into.

One thing I like about FreeBSD is how they don't try to pull smoke and mirrors about being better than other guys, and will be quite open about the bugs and shortcomings of their design.
 
Dendros said:
Can someone explain in simple terms what is happening with pkg?
I had FreeBSD 14.2 installed on a system that I use from time to time.
Well, I left this system powered off for quite a while and when I powered it on again, I wanted to update everything - and you can guess what happened: pkg first upgraded itself then proceeded to upgrade the rest of the packages, except that it never did this, because it always ended up in a failure, something about some lines in a package.
I tried some solutions, after reading some advice, including forcing an upgrade of all installed packages, reinstalling them, etc but nothing worked.
Notice that I said that "I had FreeBSD installed" - that is because I was so enraged by this that I deleted FreeBSD entirely and installed Debian.

I still would like to have FreeBSD again but not with this problem - never encountered something like this, until now. I don't want to use ports, I prefer binary packages so this is a deal breaker for me.

So, what is happening and when will this be fixed?
Click to expand...
It were problems when pkg 2.0 came out but with 2.04 and 2.05 and 2.06 looks it works normal.
 
fernandel said:
It were problems when pkg 2.0 came out but with 2.04 and 2.05 and 2.06 looks it works normal.
Click to expand...
Indeed? When I had FreeBSD installed and this problem occured, I think that pkg upgraded itself to 2.0.4 or 2.0.5 (not sure on the exact version but I'm definitely sure that it was higher that 2.0.0).
And still had the problem I talked about. But if this problem was solved in the latest version of pkg, I'm willing to give FreeBSD a try again.
 
Dendros said:
Indeed? When I had FreeBSD installed and this problem occured, I think that pkg upgraded itself to 2.0.4 or 2.0.5 (not sure on the exact version but I'm definitely sure that it was higher that 2.0.0).
And still had the problem I talked about. But if this problem was solved in the latest version of pkg, I'm willing to give FreeBSD a try again.
Click to expand...
I think in my case, it was a combination of the pkg problems going from 1.2 to 2.x, stacked atop the not-quite-correct KDE/plasma upgrade. I am going to do the plasma upgrade as stated in the notes from kde6 UPDATING, and updating pkg along the way...
 
VulcanRidr said:
I think in my case, it was a combination of the pkg problems going from 1.2 to 2.x, stacked atop the not-quite-correct KDE/plasma upgrade. I am going to do the plasma upgrade as stated in the notes from kde6 UPDATING, and updating pkg along the way...
Click to expand...
I think you'll get better results if you go for a clean reinstall (that includes backing up stuff you need and then reformatting the disk) than an upgrade. pkg upgrade still has dependency hell issues by design, even if some things got ironed out by the version bump.
 
astyle said:
I think you'll get better results if you go for a clean reinstall (that includes backing up stuff you need and then reformatting the disk) than an upgrade. pkg upgrade still has dependency hell issues by design, even if some things got ironed out by the version bump.
Click to expand...
If you choose to do that an reinstall is not needed. All ports (and everything installed with pkg) is placed in /usr/local. And nothing else.
pkg primelist > ~/installed-port-list
pkg delete -afy
rm -rf /usr/local/lib/compat/pkg
Back up any files in /usr/local you wish to save, such as configuration files in /usr/local/etc
Manually check /usr/local and /var/db/pkg to make sure that they are really empty
Install pkg and then remove it from ~/installed-port-list.
pkg install `cat ~/installed-port-list`

and you are done
 
larshenrikoern said:
All ports (and everything installed with pkg) is placed in /usr/local. And nothing else.
Click to expand...
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.
 
I upgraded FreeBSD guest with pkg 2.0.6. and noticed that the pkg 2.x messages has have changed from the pkg 1.x messages.

Rich (BB code): 
# pkg upgrade
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01
Fetching data.pkg: 100%   10 MiB   1.8MB/s    00:06
Processing entries: 100%
FreeBSD repository update completed. 35946 packages processed.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
    pkg: 1.21.3 -> 2.0.6

Number of packages to be upgraded: 1

12 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/1] Fetching pkg-2.0.6.pkg: 100%   12 MiB   2.1MB/s    00:06
Checking integrity... done (0 conflicting)
[1/1] Upgrading pkg from 1.21.3 to 2.0.6...
[1/1] Extracting pkg-2.0.6: 100%
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (337 candidates): 100%
Processing candidates (337 candidates): 100%
The following 52 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
    lzo2: 2.10_1

Installed packages to be UPGRADED:
    alsa-lib: 1.2.12 -> 1.2.13
    aom: 3.11.0 -> 3.12.0
    at-spi2-core: 2.54.0 -> 2.54.1
    cairo: 1.17.4_2,3 -> 1.18.2,3
    curl: 8.11.1_1 -> 8.12.0
    desktop-file-utils: 0.27 -> 0.28
    ffmpeg: 6.1.2_6,1 -> 6.1.2_7,1
    firefox: 134.0,2 -> 135.0_2,2
    gcc12: 12.4.0 -> 12.4.0_1
    gcc14: 14.2.0_1 -> 14.2.0_2
    gettext-runtime: 0.23 -> 0.23.1
    gnutls: 3.8.8 -> 3.8.9
    gstreamer1: 1.24.10 -> 1.24.12
    gstreamer1-plugins: 1.24.10 -> 1.24.12
    gstreamer1-plugins-bad: 1.24.10 -> 1.24.12
    harfbuzz: 10.1.0 -> 10.2.0
    hwdata: 0.390,1 -> 0.392,1
    jpeg-turbo: 3.0.4 -> 3.1.0
    json-glib: 1.10.0 -> 1.10.6
    libexif: 0.6.24 -> 0.6.25
    libimagequant: 4.3.3_4 -> 4.3.4
    librsvg2-rust: 2.58.5_2 -> 2.58.5_4
    libtasn1: 4.19.0_1 -> 4.20.0_1
    libunistring: 1.2 -> 1.3
    mesa-dri: 24.1.7_1 -> 24.1.7_4
    mpg123: 1.32.9 -> 1.32.10
    nettle: 3.10_1 -> 3.10.1
    nss: 3.107 -> 3.108
    openal-soft: 1.23.1_1 -> 1.24.2_1
    pango: 1.52.2_1 -> 1.56.1
    pciids: 20241125 -> 20250205
    pcre2: 10.43 -> 10.45
    pixman: 0.42.2 -> 0.44.2
    png: 1.6.44 -> 1.6.45
    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
    py311-PyQt5-sip: 12.15.0 -> 12.17.0
    py311-six: 1.16.0_1 -> 1.17.0
    spirv-llvm-translator-llvm15: 15.0.8 -> 15.0.9
    spirv-tools: 2024.4.r2 -> 2024.4.r2_1
    vim-gtk3: 9.1.0915 -> 9.1.1043
    virtualbox-ose-additions: 6.1.50.1401000 -> 6.1.50.1401000_1
    vulkan-headers: 1.4.304 -> 1.4.307
    vulkan-loader: 1.4.304 -> 1.4.307
    xdg-utils: 1.1.3_4 -> 1.2.1
    xterm: 396 -> 397
    xxd: 9.1.0915 -> 9.1.1043
    xxhash: 0.8.2_1 -> 0.8.3

Installed packages to be REINSTALLED:
    cups-filters-1.28.17_6 (required shared library changed)
    llvm15-15.0.7_10 (provided shared library changed)

Number of packages to be installed: 1
Number of packages to be upgraded: 49
Number of packages to be reinstalled: 2

The process will require 24 MiB more space.
480 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/52] Fetching pciids-20250205.pkg: 100%  276 KiB 282.6kB/s    00:01
snipped
[52/52] Fetching cups-filters-1.28.17_6.pkg: 100%  951 KiB 973.7kB/s    00:01
Checking integrity... done (0 conflicting)
[1/52] Upgrading alsa-lib from 1.2.12 to 1.2.13...
[1/52] Extracting alsa-lib-1.2.13: 100%
[2/52] Upgrading curl from 8.11.1_1 to 8.12.0...
[2/52] Extracting curl-8.12.0: 100%
[3/52] Upgrading gcc12 from 12.4.0 to 12.4.0_1...
[3/52] Extracting gcc12-12.4.0_1: 100%
[4/52] Upgrading gcc14 from 14.2.0_1 to 14.2.0_2...
[4/52] Extracting gcc14-14.2.0_2: 100%
[5/52] Upgrading hwdata from 0.390,1 to 0.392,1...
[5/52] Extracting hwdata-0.392,1: 100%
[6/52] Upgrading libimagequant from 4.3.3_4 to 4.3.4...
[6/52] Extracting libimagequant-4.3.4: 100%
[7/52] Installing lzo2-2.10_1...
[7/52] Extracting lzo2-2.10_1: 100%
[8/52] Upgrading mpg123 from 1.32.9 to 1.32.10...
[8/52] Extracting mpg123-1.32.10: 100%
[9/52] Upgrading openal-soft from 1.23.1_1 to 1.24.2_1...
[9/52] Extracting openal-soft-1.24.2_1: 100%
[10/52] Upgrading pciids from 20241125 to 20250205...
[10/52] Extracting pciids-20250205: 100%
[11/52] Upgrading pcre2 from 10.43 to 10.45...
[11/52] Extracting pcre2-10.45: 100%
[12/52] Upgrading py311-PyQt5-sip from 12.15.0 to 12.17.0...
[12/52] Extracting py311-PyQt5-sip-12.17.0: 100%
[13/52] Upgrading py311-six from 1.16.0_1 to 1.17.0...
[13/52] Extracting py311-six-1.17.0: 100%
[14/52] Upgrading virtualbox-ose-additions from 6.1.50.1401000 to 6.1.50.1401000_1...
[14/52] Extracting virtualbox-ose-additions-6.1.50.1401000_1: 100%
[15/52] Upgrading vulkan-headers from 1.4.304 to 1.4.307...
[15/52] Extracting vulkan-headers-1.4.307: 100%
[16/52] Upgrading xdg-utils from 1.1.3_4 to 1.2.1...
[16/52] Extracting xdg-utils-1.2.1: 100%
[17/52] Upgrading xterm from 396 to 397...
[17/52] Extracting xterm-397: 100%
[18/52] Upgrading xxhash from 0.8.2_1 to 0.8.3...
[18/52] Extracting xxhash-0.8.3: 100%
[19/52] Deinstalling cups-filters-1.28.17_6...
[19/52] Deleting files for cups-filters-1.28.17_6: 100%
[20/52] Deinstalling firefox-134.0,2...
[20/52] Deleting files for firefox-134.0,2: 100%
[21/52] Deinstalling ffmpeg-6.1.2_6,1...
[21/52] Deleting files for ffmpeg-6.1.2_6,1: 100%
[22/52] Deinstalling aom-3.11.0...
[22/52] Deleting files for aom-3.11.0: 100%
[22/52] Installing aom-3.12.0...
[22/52] Extracting aom-3.12.0: 100%
[23/52] Deinstalling gnutls-3.8.8...
[23/52] Deleting files for gnutls-3.8.8: 100%
[24/52] Upgrading libtasn1 from 4.19.0_1 to 4.20.0_1...
[24/52] Extracting libtasn1-4.20.0_1: 100%
[25/52] Upgrading libunistring from 1.2 to 1.3...
[25/52] Extracting libunistring-1.3: 100%
[26/52] Upgrading nettle from 3.10_1 to 3.10.1...
[26/52] Extracting nettle-3.10.1: 100%
[27/52] Deinstalling gstreamer1-plugins-bad-1.24.10...
[27/52] Deleting files for gstreamer1-plugins-bad-1.24.10: 100%
[28/52] Deinstalling gstreamer1-plugins-1.24.10...
[28/52] Deleting files for gstreamer1-plugins-1.24.10: 100%
[29/52] Deinstalling gstreamer1-1.24.10...
[29/52] Deleting files for gstreamer1-1.24.10: 100%
[30/52] Deinstalling json-glib-1.10.0...
[30/52] Deleting files for json-glib-1.10.0: 100%
[31/52] Deinstalling libexif-0.6.24...
[31/52] Deleting files for libexif-0.6.24: 100%
[32/52] Deinstalling librsvg2-rust-2.58.5_2...
[32/52] Deleting files for librsvg2-rust-2.58.5_2: 100%
[33/52] Deinstalling mesa-dri-24.1.7_1...
[33/52] Deleting files for mesa-dri-24.1.7_1: 100%
[34/52] Deinstalling poppler-utils-24.02.0_2...
[34/52] Deleting files for poppler-utils-24.02.0_2: 100%
[35/52] Deinstalling poppler-glib-24.02.0_2...
[35/52] Deleting files for poppler-glib-24.02.0_2: 100%
[36/52] Deinstalling poppler-24.02.0_2...
[36/52] Deleting files for poppler-24.02.0_2: 100%
[37/52] Deinstalling jpeg-turbo-3.0.4...
[37/52] Deleting files for jpeg-turbo-3.0.4: 100%
[37/52] Installing jpeg-turbo-3.1.0...
[37/52] Extracting jpeg-turbo-3.1.0: 100%
[38/52] Deinstalling nss-3.107...
[38/52] Deleting files for nss-3.107: 100%
[38/52] Installing nss-3.108...
[38/52] Extracting nss-3.108: 100%
[39/52] Deinstalling spirv-llvm-translator-llvm15-15.0.8...
[39/52] Deleting files for spirv-llvm-translator-llvm15-15.0.8: 100%
[40/52] Deinstalling llvm15-15.0.7_10...
[40/52] Deleting files for llvm15-15.0.7_10: 100%
[40/52] Installing llvm15-15.0.7_10...
[40/52] Extracting llvm15-15.0.7_10: 100%
[40/52] Installing spirv-llvm-translator-llvm15-15.0.9...
[40/52] Extracting spirv-llvm-translator-llvm15-15.0.9: 100%
[41/52] Deinstalling spirv-tools-2024.4.r2...
[41/52] Deleting files for spirv-tools-2024.4.r2: 100%
[41/52] Installing spirv-tools-2024.4.r2_1...
[41/52] Extracting spirv-tools-2024.4.r2_1: 100%
[41/52] Installing mesa-dri-24.1.7_4...
[41/52] Extracting mesa-dri-24.1.7_4: 100%
[42/52] Deinstalling vim-gtk3-9.1.0915...
[42/52] Deleting files for vim-gtk3-9.1.0915: 100%
[43/52] Deinstalling at-spi2-core-2.54.0...
[43/52] Deleting files for at-spi2-core-2.54.0: 100%
[44/52] Deinstalling desktop-file-utils-0.27...
[44/52] Deleting files for desktop-file-utils-0.27: 100%
[45/52] Deinstalling pango-1.52.2_1...
[45/52] Deleting files for pango-1.52.2_1: 100%
[46/52] Deinstalling cairo-1.17.4_2,3...
[46/52] Deleting files for cairo-1.17.4_2,3: 100%
[47/52] Upgrading pixman from 0.42.2 to 0.44.2...
[47/52] Extracting pixman-0.44.2: 100%
[48/52] Deinstalling harfbuzz-10.1.0...
[48/52] Deleting files for harfbuzz-10.1.0: 100%
[49/52] Deinstalling gettext-runtime-0.23...
[49/52] Deleting files for gettext-runtime-0.23: 100%
[49/52] Installing gettext-runtime-0.23.1...
[49/52] Extracting gettext-runtime-0.23.1: 100%
[49/52] Installing at-spi2-core-2.54.1...
[49/52] Extracting at-spi2-core-2.54.1: 100%
[49/52] Installing desktop-file-utils-0.28...
[49/52] Extracting desktop-file-utils-0.28: 100%
Building cache database of MIME types
[49/52] Installing gnutls-3.8.9...
[49/52] Extracting gnutls-3.8.9: 100%
[49/52] Installing gstreamer1-1.24.12...
[49/52] Extracting gstreamer1-1.24.12: 100%
[49/52] Installing gstreamer1-plugins-1.24.12...
[49/52] Extracting gstreamer1-plugins-1.24.12: 100%
[49/52] Installing harfbuzz-10.2.0...
[49/52] Extracting harfbuzz-10.2.0: 100%
[49/52] Installing json-glib-1.10.6...
[49/52] Extracting json-glib-1.10.6: 100%
[49/52] Installing libexif-0.6.25...
[49/52] Extracting libexif-0.6.25: 100%
[50/52] Deinstalling png-1.6.44...
[50/52] Deleting files for png-1.6.44: 100%
[50/52] Installing png-1.6.45...
[50/52] Extracting png-1.6.45: 100%
[50/52] Installing cairo-1.18.2,3...
[50/52] Extracting cairo-1.18.2,3: 100%
[50/52] Installing pango-1.56.1...
[50/52] Extracting pango-1.56.1: 100%
[50/52] Installing gstreamer1-plugins-bad-1.24.12...
[50/52] Extracting gstreamer1-plugins-bad-1.24.12: 100%
[50/52] Installing librsvg2-rust-2.58.5_4...
[50/52] Extracting librsvg2-rust-2.58.5_4: 100%
[50/52] Installing poppler-24.12.0...
[50/52] Extracting poppler-24.12.0: 100%
[50/52] Installing poppler-glib-24.12.0...
[50/52] Extracting poppler-glib-24.12.0: 100%
[50/52] Installing poppler-utils-24.12.0...
[50/52] Extracting poppler-utils-24.12.0: 100%
[50/52] Installing cups-filters-1.28.17_6...
[50/52] Extracting cups-filters-1.28.17_6: 100%
[51/52] Deinstalling vulkan-loader-1.4.304...
[51/52] Deleting files for vulkan-loader-1.4.304: 100%
[51/52] Installing vulkan-loader-1.4.307...
[51/52] Extracting vulkan-loader-1.4.307: 100%
[51/52] Installing ffmpeg-6.1.2_7,1...
[51/52] Extracting ffmpeg-6.1.2_7,1: 100%
[51/52] Installing firefox-135.0_2,2...
[51/52] Extracting firefox-135.0_2,2: 100%
[52/52] Deinstalling xxd-9.1.0915...
[52/52] Deleting files for xxd-9.1.0915: 100%
[52/52] Installing xxd-9.1.1043...
[52/52] Extracting xxd-9.1.1043: 100%
[52/52] Installing vim-gtk3-9.1.1043...
[52/52] Extracting vim-gtk3-9.1.1043: 100%
==> Cleaning up trigger: desktop-file-utils.ucl
==> Running trigger: gdk-pixbuf-query-loaders.ucl
Generating gdk-pixbuf modules cache
==> Running trigger: desktop-file-utils.ucl
Building cache database of MIME types
==> Running trigger: gtk-update-icon-cache.ucl
Generating GTK icon cache for /usr/local/share/icons/locolor
Generating GTK icon cache for /usr/local/share/icons/hicolor

Some upgraded packages are marked in a group Upgrading + Extracting, e.g. gcc12 at #3. Others are in the group Deinstalling + Deleting + Installing + Extracting, e.g. nss at #38, or the groups are split. Some operations of many packages are collected in a group with the same order number, e.g. #50.

I have never noticed anything like this in the pkg 1.x messages.

Could somebody explain these changes to me?

I did a test-only upgrade of the same state using pkg 1.21.3 and found that pkg 1.21.3 reinstalled many more packages due to changes in shared libraries than pkg 2.0.6. Is the reason that pkg 2.x is more efficient than pkg 1.x? I hope it is not a bug in the dependencies upgrade.
 
You must log in or register to reply here.
Back
Top