Date: Mon, 29 Apr 2024 19:36:45 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: ports@freebsd.org, Alexander Leidinger <Alexander@leidinger.net> Subject: Re: pkg upgrade odity Message-ID: <3AEDC553-F5D8-448F-AAD8-3DE19973022B@FreeBSD.org> In-Reply-To: <42392cc8-db69-4316-840b-dae5beeea396@quip.cz> References: <6e8aea8cce83e0a82be430be1989980a@Leidinger.net> <f64b7244-5cb1-450d-8aad-525f8673410a@quip.cz> <zypr5fta76iochorlmqbikm5ygdzpk5vqq66yta5ulprgbtjwe@fmhgiee2ugte> <42392cc8-db69-4316-840b-dae5beeea396@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 29 avril 2024 19:33:35 GMT+02:00, Miroslav Lachman <000=2Efbsd@quip=2Ecz= > a =C3=A9crit=C2=A0: >On 29/04/2024 17:21, Baptiste Daroussin wrote: >> On Mon 29 Apr 16:41, Miroslav Lachman wrote: >>> On 29/04/2024 12:49, Alexander Leidinger wrote: >>>> Hi, >>>>=20 >>>> pkg wants to remove some package on upgrade=2E I do not understand wh= y=2E=2E=2E >>>> ---snip--- >>>> # pkg upgrade >>>> Updating FreeBSD repository catalogue=2E=2E=2E >>>> Fetching meta=2Econf: 100%=C2=A0=C2=A0=C2=A0 178 B=C2=A0=C2=A0 0=2E2k= B/s=C2=A0=C2=A0=C2=A0 00:01 >>>> Fetching data=2Epkg: 100%=C2=A0 130 KiB 133=2E5kB/s=C2=A0=C2=A0=C2=A0= 00:01 >>>> Processing entries: 100% >>>> FreeBSD repository update completed=2E 467 packages processed=2E >>>> All repositories are up to date=2E >>>> Checking for upgrades (1 candidates): 100% >>>> Processing candidates (1 candidates): 100% >>>> The following 4 package(s) will be affected (of 0 checked): >>>>=20 >>>> Installed packages to be REMOVED: >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mosh: 1=2E4=2E0_2 >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 netdata: 1=2E43=2E2_1 >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 protobuf: 24=2E4,1 >>>>=20 >>>> Installed packages to be UPGRADED: >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rsync: 3=2E2=2E7_1 -> 3= =2E3=2E0 >>>>=20 >>>> Number of packages to be removed: 3 >>>> Number of packages to be upgraded: 1 >>>>=20 >>>> The operation will free 55 MiB=2E >>>> 405 KiB to be downloaded=2E >>>>=20 >>>> Proceed with this action? [y/N]: n >>>> ---snip--- >>>>=20 >>>> If I do this instead, it is doing what I expect the former command to= do: >>>> ---snip--- >>>> # pkg upgrade mosh netdata protobuf rsync >>>> Updating FreeBSD repository catalogue=2E=2E=2E >>>> FreeBSD repository is up to date=2E >>>> All repositories are up to date=2E >>>> The following 1 package(s) will be affected (of 0 checked): >>>>=20 >>>> Installed packages to be UPGRADED: >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rsync: 3=2E2=2E7_1 -> 3= =2E3=2E0 >>>>=20 >>>> Number of packages to be upgraded: 1 >>>>=20 >>>> 405 KiB to be downloaded=2E >>>>=20 >>>> Proceed with this action? [y/N]: >>>> ---snip--- >>>>=20 >>>> Any ideas why it wants to remove those packages in the first case? >>>=20 >>>=20 >>> I see similar behavior from time to time=2E Last time (a few days ago)= pkg >>> wanted to uninstall about 30 packages when I tried to install Signal D= esktop >>> (I tried to install another package without any dependencies, but pkg >>> behaves the same)=2E I didn't have time to solve it, I just left it al= one=2E The >>> second day (after reboot) everything worked normally and pkg installed= only >>> Signal Desktop, no other dependencies/libraries were affected=2E >>>=20 >>> And similarly, pkg during 'pkg upgrade' installed several packages, wh= ich >>> after completing 'pkg upgrade' again uninstalled by command 'pkg autor= emove' >>> (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=2E >>>=20 >>>=20 >>> Kind regards >>> Miroslav Lachman >>>=20 >>>=20 >>=20 >> 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 u= pgrade 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=2E= 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=2E Bapt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AEDC553-F5D8-448F-AAD8-3DE19973022B>