Re: pkg upgrade odity

Le 29 avril 2024 22:33:09 GMT+02:00, Miroslav Lachman <000.fbsd@quip.cz> a écrit :
>On 29/04/2024 19:36, Baptiste Daroussin wrote:
>> Le 29 avril 2024 19:33:35 GMT+02:00, Miroslav Lachman <000.fbsd@quip.cz> a écrit :
>>> On 29/04/2024 17:21, Baptiste Daroussin wrote:
>
>>>>> I see similar behavior from time to time. Last time (a few days ago) pkg
>>>>> wanted to uninstall about 30 packages when I tried to install Signal Desktop
>>>>> (I tried to install another package without any dependencies, but pkg
>>>>> behaves the same). I didn't have time to solve it, I just left it alone. The
>>>>> second day (after reboot) everything worked normally and pkg installed only
>>>>> Signal Desktop, no other dependencies/libraries were affected.
>>>>> 
>>>>> And similarly, pkg during 'pkg upgrade' installed several packages, which
>>>>> after completing 'pkg upgrade' again uninstalled by command 'pkg autoremove'
>>>>> (I remember mate-desktop, which I don't use at all, I use KDE Plasma) It was
>>>>> right before I tried to install Signal Desktop.
>>>>> 
>>>>> 
>>>> 
>>>> This is usually due to shlibs_provided and shlibs_required,, pkg check -d should
>>>> be able to highlight some of the issues
>>> 
>>> Speaking of pkg check, should it work with a changed root directory (pkg -r /some/path check) or chroot (pkg -c /some/path check)? I'm doing a pkg upgrade of a desktop in a cloned BE and if I run pkg check after pkg upgrade (with -c), pkg check prints an error for hundreds or thousands of files. So it seems I cannot check before the reboot to newly updated BE (I know I can run it as jail but it more work than pkg -c)
>>> 
>>> Kind regards
>>> Miroslav Lachman
>>> 
>> 
>> Yes it is supposed to work with -r, all it needs is the db access.
>
>My notes from 2024-04-23:
>
># pkg -r /tmp/be_mount.bN62 check -Ba
>Checking all packages:
>(0ad-0.0.26_23) /usr/local/bin/ActorEditor - required shared library ../../../binaries/system/libAtlasUI.so not found
>Checking all packages...
>pkg: fstat() failed for(/usr/local/lib/libappstream.so.1.0.1): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStream-1.0.1/GPLv2+): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStream-1.0.1/LGPL21+): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStream-1.0.1/LICENSE): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStream-1.0.1/catalog.mk): No such file or directory
>pkg: fstat() failed for(/usr/local/share/man/man1/appstreamcli.1.gz): No such file or directory
>Checking all packages...
>pkg: fstat() failed for(/usr/local/lib/libAppStreamQt5.so.1.0.1): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStreamQt5-1.0.1/GPLv2+): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStreamQt5-1.0.1/LGPL21+): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStreamQt5-1.0.1/LICENSE): No such file or directory
>pkg: fstat() failed for(/usr/local/share/licenses/AppStreamQt5-1.0.1/catalog.mk): No such file or directory
>Checking all packages...
>pkg: fstat() failed for(/usr/local/lib/ImageMagick-7.1.1/config-Q16HDRI/configure.xml): No such file or directory
>pkg: fstat() failed for(/usr/local/lib/ImageMagick-7.1.1/modules-Q16HDRI/coders/aai.la): No such file or directory
>..
>..
>
>this list was really long and all files were there (in a BE) but it seems like if pkg check does not see them.
>
>I didn't try it at 2024-04-23, but from my memory I thinkg pkg -c works, but pkg -r doesn't.
>
>Kind regards
>Miroslav Lachman
>

pkg check -d is rootdir safe pkg check -B is another beast I haven yet looked at it.

Bapt