Re: pkg install -f ... doesn't?

From: Erwan David <erwan_at_rail.eu.org>
Date: Thu, 23 Jan 2025 18:15:20 UTC
Le 23/01/2025 à 18:47, Gary Aitken a écrit :
> Not sure exactly what the problem was,
> but updating the package database
> and using security/py-certbot-apache
> instead of py-certbot-apache
> solved the problem:
>
> # pkg update -f
> Updating FreeBSD repository catalogue...
> Fetching meta.conf: 100%    178 B   0.2kB/s    00:01
> Fetching data.pkg: 100%    7 MiB 503.1kB/s    00:15
> Processing entries: 100%
> FreeBSD repository update completed. 35910 packages processed.
>
> # pkg install py-certbot-apache
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up to date.
> All repositories are up to date.
> pkg: No packages available to install matching 'py-certbot-apache' 
> have been found in the repositories
>
> # pkg install security/py-certbot-apache
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up to date.
> All repositories are up to date.
> The following 21 package(s) will be affected (of 0 checked):
>
> New packages to be INSTALLED:
> ...
> Installed packages to be REMOVED:
>         py39-charset-normalizer: 3.3.2
>         py39-distro: 1.9.0
>         py39-requests: 2.31.0
> New packages to be INSTALLED:
>         py311-acme: 3.0.1,1
> ...
>
> I tried security/py-certbot-apache after checking freshports,
> which says:
> To add the package, run one of these commands:
>         pkg install security/py-certbot-apache
>         pkg install py311-certbot-apache
>
> Why is the "security/" required? 


with the security you specify the port. You can see it installs py311-* 
packages that means packages compiled fotr Python3.11 which is the 
crurrent version. By specifying py39-* you forced packages made for 
python 3.9 which do not exist anymore in the repositories.