pkg 2.0.0 problems

I can't understand why I'm on an old version (1.21.3)? I'm updating, but the package is "frozen"...
# cat /etc/pkg/FreeBSD.conf
Bash: 
url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly"
# pkg lock -l
Bash: 
Currently locked packages:
drm-61-kmod-6.1.92
telegram-desktop-5.10.0_2
 
USerID said:
I can't understand why I'm on an old version (1.21.3)? I'm updating, but the package is "frozen"...
# cat /etc/pkg/FreeBSD.conf
Bash: 
url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly"
# pkg lock -l
Bash: 
Currently locked packages:
drm-61-kmod-6.1.92
telegram-desktop-5.10.0_2
Click to expand...
It's because you're using quarterly. Currently pkg 2.* landed only on latest (main) branch. Your /etc/pkg/FreeBSD.conf indicates it's configured for "quarterly".
 
My problem is solved too but I do not know why I have :
Code: 
 pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (5 candidates): 100%
Processing candidates (5 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

Code: 
 pkg version -vRL=
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
drm-61-kmod-6.1.92.1402000_3       >   succeeds remote (remote has 6.1.92.1401000_3)
hplip-plugin-3.24.4                ?   orphaned: print/hplip-plugin
libdvdcss-1.4.3                    ?   orphaned: multimedia/libdvdcss

Code: 
pkg lock -l
Currently locked packages:
drm-61-kmod-6.1.92.1402000_3
ksh-1.0.10

Before I had just two - lock files.
I solved the "problem" with pkg -dd upgrade
 
BaronBS said:
2.0.3 is out o latest+stable, but not in current yet.
Click to expand...
Just to clarify 2.0.3 (on 2025-01-24T13:09:30.000Z) has landed in the ports tree: ports-mgmt/pkg - commits.

On amd64 I don't see any version beyond 1.21.3 actually installable as a package (see also freshports: ports-mgmt/pkg); "stable" or stable/14 isn't relevant in this context.

You'll have to build from source to get 2.0.3; however, in Re:_Regression_in_pkg:_it_complains_about_m issing_pkg_files_instead_of_downloading_them - Sun, 26 Jan 2025 07:13:20 UTC, Baptiste Daroussin indicated:
[...]
a fix for this will be in 2.0.4, it is still being tested right now. 2.0.4 will probably happen today

bapt
Click to expand...
 
Erichans said:
Just to clarify in 2.0.3 has landed in the ports tree: ports-mgmt/pkg - commits.

On amd64 I don't see any version beyond 1.21.3 actually installable as a package (see also freshports: ports-mgmt/pkg); "stable" or stable/14 isn't relevant in this context.

You'll have to build from source to get 2.0.3; however, in Re:_Regression_in_pkg:_it_complains_about_m issing_pkg_files_instead_of_downloading_them - Sun, 26 Jan 2025 07:13:20 UTC, Baptiste Daroussin indicated:
Click to expand...
IDK what you are saying, but I commented here because I got 2.0.3 from the repos in my Stable machine:
Code: 
beastie@BattleStar-Lat5420 --> ~
Ψ pkg -v                                                                                                                                                                     < 13:30 >  < 11,725-01-26 >  < 130 >
2.0.3
beastie@BattleStar-Lat5420 --> ~
Ψ doas grep pkg /var/log/messages | grep ' 26 '                                                                                                                                < 13:30 >  < 11,725-01-26 >  < 0 >
Jan 26 01:15:48 BattleStar-Lat5420 pkg[86309]: nano-8.2 deinstalled
Jan 26 12:04:53 BattleStar-Lat5420 pkg[77748]: pkg upgraded: 2.0.0 -> 2.0.3
Jan 26 12:32:56 BattleStar-Lat5420 pkg[8781]: libarchive upgraded: 3.7.7_1,1 -> 3.7.7_2,1
Jan 26 12:32:56 BattleStar-Lat5420 pkg[8781]: libimagequant upgraded: 4.3.3_5 -> 4.3.4
Jan 26 12:32:56 BattleStar-Lat5420 pkg[8781]: pkg reinstalled: 2.0.3 -> 2.0.3
Jan 26 12:32:57 BattleStar-Lat5420 pkg[8781]: qt6-webengine upgraded: 6.8.1 -> 6.8.1_1
.....
That fixed the problem I had, as someone said early in this thread.

Also, I didn't got it in my Current machine yet:
Code: 
beastie@BattleStar-Hydra:~ $ pkg -v
2.0.0
beastie@BattleStar-Hydra:~ $ doas pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

So, there is that.
 
BaronBS said:
IDK what you are saying, but I commented here because I got 2.0.3 from the repos in my Stable machine:
Click to expand...
Thanks, you're correct, I'm (14.2-R) also seeing it now:
Code: 
 # pkg upgrade                                                   pts/1
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.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pkg: 1.21.3 -> 2.0.3 [FreeBSD]

Number of packages to be upgraded: 1

12 MiB to be downloaded.

Proceed with this action? [y/N]:
My wrong impression was probably caused by locking pkg-1.21.3 yesterday/early this morning.
 
Erichans said:
If you've build pkg-2.0.4 on your host, I suggest you consider submitting a PR or an issue in order to help Baptiste Daroussin solving this.

As 2.0.4 is literally just a few hours old, at a cursory scan I didn't see any specifics regarding 2.0.4. at bugzilla or freebsd/pkg/issues.
Click to expand...
It builds just fine. The problem is that it wants to uninstall parts of Xfce and xorg to upgrade libraries. I know howto submit bugs. But I wait a bit, because I think the developers are aware of it, and are trying to sort things out in a kind of understandable hurry. And to see if of it is just me having a problem on 14-STABLE. It might be different to others. And it means better and more information for the developers.
 
larshenrikoern said:
It builds just fine. The problem is that it wants to uninstall parts of Xfce and xorg to upgrade libraries. I know howto submit bugs. But I wait a bit, because I think the developers are aware of it, and are trying to sort things out in a kind of understandable hurry. And to see if of it is just me having a problem on 14-STABLE. It might be different to others. And it means better and more information for the developers.
Click to expand...
You're not alone. Me, too, still bitten by 2.0.4.
I have local repo built by poudriere and usually keep default official repo enabled with lower priority.
In this case, crashes like below.

Code: 
Checking integrity... done (6 conflicting)
  - llvm17-lite-17.0.6_8 [FreeBSD] conflicts with llvm17-17.0.6_8 [installed] on /usr/local/llvm17/lib/clang/17/include/arm_sme_draft_spec_subject_to_change.h
  - llvm17-lite-17.0.6_8 [FreeBSD] conflicts with llvm17-17.0.6_8 [custom] on /usr/local/llvm17/lib/clang/17/include/arm_sme_draft_spec_subject_to_change.h
  - libebur128-1.2.6 [FreeBSD] conflicts with ebur128-0.1.10_2 [installed] on /usr/local/include/ebur128.h
  - libebur128-1.2.6 [FreeBSD] conflicts with ebur128-0.1.10_2 [custom] on /usr/local/include/ebur128.h
  - llvm15-lite-15.0.7_10 [FreeBSD] conflicts with llvm15-15.0.7_10 [installed] on /usr/local/llvm15/lib/clang/15.0.7/include/arm_bf16.h
  - llvm15-lite-15.0.7_10 [FreeBSD] conflicts with llvm15-15.0.7_10 [custom] on /usr/local/llvm15/lib/clang/15.0.7/include/arm_bf16.h
Assertion failed: (j->system_shlibs == NULL), function pkg_jobs_solve, file pkg_jobs.c, line 1919.
Child process pid=70263 terminated abnormally: Abort trap

And disabling official repo (use local repo alone, which all pkgs of installed ports are built) pkg 2.0.4 wants 422 ports to be deinstalled including fundamental ones and leaf ports.

But me, too, holding to file a PR because Bapt@ seems to be digging into some other issues now (not sure technically related or not, though). So I don't want him too much confused with new info without proper analysis.
 
😩
Code: 
# pkg fetch my-package.pkg
# pkg add /var/cache/my-package.pkg

This sequence usually works for me if I want to install a pre-compiled package. If dependencies are not safisfied/filled beforehand, pkg add will of course complain, but at least it will not threaten to remove Firefox and other useful components. add subcommand (as opposed to install) seems to be a bit better behaved. At the same time, it's on me (instead of automated dependency resolution mechanism) to make sure deps are satisfied beforehand, and that can be an effort.
 
I am using synth

My terminal gives the following:

# pkg upgrade
Updating Synth repository catalogue...
Fetching meta.conf: 100% 179 B 0.2kB/s 00:01
Fetching data.pkg: 100% 572 KiB 585.6kB/s 00:01
Processing entries: 100%
Synth repository update completed. 1808 packages processed.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pkg: 2.0.3 -> 2.0.4 [Synth]

Number of packages to be upgraded: 1

Proceed with this action? [y/N]: y
[1/1] Upgrading pkg from 2.0.3 to 2.0.4...
[1/1] Extracting pkg-2.0.4: 100%
Updating Synth repository catalogue...
Synth repository is up to date.
All repositories are up to date.
Checking for upgrades (338 candidates): 100%
Processing candidates (338 candidates): 100%
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
The following 77 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
brlaser: 6.2.6 -> 6.2.7 [Synth]
dcmtk: 3.6.8_1 -> 3.6.9 [Synth]
desktop-file-utils: 0.27 -> 0.28 [Synth]
gegl: 0.4.48_3 -> 0.4.48_4 [Synth]
hedgewars: 1.0.2_4 -> 1.0.2_5 [Synth]
libarchive: 3.7.7_1,1 -> 3.7.7_2,1 [Synth]
libical: 3.0.16_1 -> 3.0.19 [Synth]
libimagequant: 4.3.3_5 -> 4.3.4 [Synth]
libproxy: 0.5.9 -> 0.5.9_1 [Synth]
luv: 1.48.0.2 -> 1.50.0.0 [Synth]
neovim: 0.10.3 -> 0.10.3_1 [Synth]
openimageio: 2.5.13.1_4 -> 2.5.13.1_5 [Synth]
py311-numpy: 1.26.4_3,1 -> 1.26.4_4,1 [Synth]
spirv-tools: 2024.4.r2 -> 2024.4.r2_1 [Synth]
suitesparse-config: 7.8.2_1 -> 7.8.3 [Synth]
suitesparse-umfpack: 6.3.4 -> 6.3.5 [Synth]
vulkan-headers: 1.4.305 -> 1.4.306 [Synth]
vulkan-loader: 1.4.305 -> 1.4.306 [Synth]
vulkan-tools: 1.4.305 -> 1.4.306 [Synth]
wine-mono: 8.1.0 -> 9.4.0 [Synth]
xdg-utils: 1.1.3_4 -> 1.2.1 [Synth]
yt-dlp: 2025.01.15 -> 2025.01.26 [Synth]

Installed packages to be REINSTALLED:
ffmpeg4-4.4.4_17 [Synth] (options changed)
firefox-134.0.2,2 [Synth] (required shared library changed)
gcc12-12.4.0 [Synth] (provided shared library changed)
gcc13-13.3.0 [Synth] (provided shared library changed)
libraw-0.21.3 [Synth] (options changed)
libreoffice-24.8.4.2 [Synth] (required shared library changed)
llvm15-15.0.7_10 [Synth] (provided shared library changed)
postgresql16-client-16.6_1 [Synth] (options changed)
py311-boost-libs-1.86.0 [Synth] (options changed)
waterfox-6.5.3_1,1 [Synth] (required shared library changed)
xvid-1.3.7,1 [Synth] (options changed)
zstd-1.5.6 [Synth] (options changed)

Installed packages to be REMOVED:
0ad: 0.0.26_36
audacity: 3.7.1
brasero: 3.12.3_6
glade: 3.40.0_5
gnome-online-accounts: 3.44.0_4
gnuplot: 5.4.10_2
grilo-plugins: 0.3.15_1
hugin: 2024.0.1_1
libgdata: 0.18.1_1
libgepub: 0.6.0_6
libhandy: 1.6.2_2
lightzone: 4.1.8.3_13
mesa-dri: 24.1.7_1
nautilus: 42.2_3
nvidia-driver: 550.127.05
qalculate-gtk: 5.5.0_1
rhythmbox: 3.4.6_5
ristretto: 0.13.3
spirv-llvm-translator-llvm15: 15.0.7
thunar: 4.20.1
thunar-archive-plugin: 0.5.3
thunar-media-tags-plugin: 0.5.0
thunar-vcs-plugin: 0.3.0
totem: 3.38.2_7
webkit2-gtk_40: 2.46.5_1
wx30-gtk3: 3.0.5.1_6
wx32-gtk3: 3.2.6_1
xed: 3.4.5
xf86-input-keyboard: 1.9.0_6
xf86-input-libinput: 1.3.0_1
xf86-input-mouse: 1.9.3_5
xf86-video-scfb: 0.0.7_2
xf86-video-vesa: 2.5.0_3
xfce: 4.20
xfce4-desktop: 4.20.0
xfce4-goodies: 4.20
xfce4-tumbler: 4.20.0
xorg: 7.7_3
xorg-drivers: 7.7_7
xorg-server: 21.1.14,1
xreader: 3.2.2_22
yelp: 42.1_4

Number of packages to be removed: 42
Number of packages to be upgraded: 22
Number of packages to be reinstalled: 12

The operation will free 4 GiB.

Proceed with this action? [y/N]: n
 
T-Aoki said:
If pkg is not yet upgraded to 2.* (staying at 1.21.3),
pkg lock ports-mgmt/pkg
would stop upgrading of pkg itself.
Once 2.* turns out to become safe, you can
pkg unlock ports-mgmt/pkg
to allow it to be upgraded again.
Click to expand...
Thank you, however I had already upgraded to pkg 2.0.0 before I found this thread (it was why I had found the thread) and now my issue is how to roll back package.

Would something like
Code: 
pkg add -f /var/cache/pkg/pkg-1.21.3.pkg
work to roll it back? I still have that in my pkg cache and that looks to be my most recent one in the cache.
 
Baenwort said:
Would something like pkg add -f /var/cache/pkg/pkg-1.21.3.pkg work to roll it back? I still have that in my pkg cache and that looks to be my most recent one in the cache.
Click to expand...
If you still have the actual package (not a symlink) /var/cache/pkg/pkg-1.21.3.pkg, then copy it somewhere else just to be on the safe side, then do pkg add...

If you don't pay attention, that package will be gone with no good way to recover it other than a complete and fresh reinstall of FreeBSD...
 
- librsvg2-2.40.21_4 [FreeBSD] conflicts with librsvg2-rust-2.58.5_3 [installed] on /usr/local/bin/rsvg-convert
Click to expand...

I had this same problem, I removed rsvg-convert and anything that depended on it.
Everything works well, except lots of stuff depends on it and if I try to install any of those packages it throws the same error during the install.

Is there any solution?
 
astyle said:
If you still have the actual package (not a symlink) /var/cache/pkg/pkg-1.21.3.pkg,
Click to expand...
Precisely, /var/cache/pkg/pkg-1.21.3.pkg should be a symlink to another file containing ~<shortened hash> in its filename at the same directory. So the symlink'ed file is needed to be preserved into somewhere else.
 
Champion said:
I had this same problem, I removed rsvg-convert and anything that depended on it.
Everything works well, except lots of stuff depends on it and if I try to install any of those packages it throws the same error during the install.

Is there any solution?
Click to expand...
There would be 2 solutions.
  • Wait until everything depending upon graphics/librsvg2-rust (say, missingly linked against graphics/librsvg2) and you actually need are rebuilt and ready on the official repo.
  • If you already have up-to-date ports tree in hand (or do not hesitated to clone and maintain local clone of official repo yourself) and enough computer resources (CPU, memory, disk and of course including your time), build them locally yourself.
 
You must log in or register to reply here.
Back
Top