Date: Tue, 22 May 2018 23:58:34 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: freebsd-ports@freebsd.org Subject: unreliable pkg upgrades Message-ID: <cfdee765-942e-0a8d-f0b5-8d7294b7e2aa@quip.cz>
next in thread | raw e-mail | index | archive | help
Am I the only one seeing occasional unreliable pkg upgrades?
I think changes in package name or ports origin should be better handled
by pkg tools.
For example, we have php-composer installed on many of our machines. The
ports was flavorized, ports origin is the same, but pkg reports
php-composer as orphaned.
pkg upgrade just ignores php-composer:
root@jahoda ~/# pkg upgrade
Updating codelab repository catalogue...
codelab 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.
But if I tell the pkg that I want to upgrade devel/php-composer it will
do the right thing
root@jahoda ~/# pkg upgrade devel/php-composer
Updating codelab repository catalogue...
codelab repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
php71-composer: 1.6.3
Number of packages to be installed: 1
The process will require 2 MiB more space.
380 KiB to be downloaded.
Proceed with this action? [y/N]: y
[1/1] Fetching php71-composer-1.6.3.txz: 100% 380 KiB 389.3kB/s 00:01
Checking integrity... done (1 conflicting)
- php71-composer-1.6.3 conflicts with php-composer-1.6.2 on
/usr/local/bin/composer
Checking integrity... done (0 conflicting)
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 2 package(s) will be affected (of 0 checked):
Installed packages to be REMOVED:
php-composer-1.6.2
New packages to be INSTALLED:
php71-composer: 1.6.3
Number of packages to be removed: 1
Number of packages to be installed: 1
Proceed with this action? [y/N]: y
[1/2] Deinstalling php-composer-1.6.2...
[1/2] Deleting files for php-composer-1.6.2: 100%
[2/2] Installing php71-composer-1.6.3...
[2/2] Extracting php71-composer-1.6.3: 100%
Why it is not handled automatically like in other OSes?
That's the reason we are still not using Ansible for mass pkg upgrades,
because we must carefully watch each and every pkg upgrade run. What it
will do and what it refuse to do without manual intervention.
Miroslav Lachman
PS: we are using own repository built with poudriere
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cfdee765-942e-0a8d-f0b5-8d7294b7e2aa>