Le 9 avril 2024 18:06:12 GMT+02:00, FreeBSD User <free...@walstatt-de.de> a écrit : >Am Tue, 9 Apr 2024 17:10:52 +0200 >Rainer Hurling <rhur...@gwdg.de> schrieb: > >> Am 09.04.24 um 09:20 schrieb Baptiste Daroussin: >> > On Sat 06 Apr 09:23, Rainer Hurling wrote: >> >> Am 06.04.24 um 09:05 schrieb FreeBSD User: >> >>> Hello, >> >>> >> >>> after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> >> >>> 1.21.0 on CURRENT >> >>> and 14-STABLE, I can't update several ports: >> >>> >> >>> www/apache24 >> >>> databases/redis >> >>> >> >>> pkg core dumps while performing installation. apache24 and redis are >> >>> ports I realized >> >>> this misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants >> >>> latest builds, >> >>> i.e. FreeBSD 15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 >> >>> 20:30:39 CEST 2024 >> >>> amd64). >> >>> >> >>> After some updates on a poudriere builder (CURRENT base host, >> >>> 14.0-RELENG jail with >> >>> poudriere) building packages for 14.0-RELENG, I observed the same >> >>> behaviour when >> >>> updating packages on target hosts where pkg is first updated, on those >> >>> hosts, >> >>> nextcloud-server and icinga2 host utilizing also databases/redis and >> >>> www/apache24, pkg >> >>> fails the same way. >> >>> >> >>> I do not dare to update our poudriere hosts since the problem seems to >> >>> pop up when pkg >> >>> 1.21.0 is installed, no matter whether I use poudriere built ports (from >> >>> our own builder >> >>> hosts) or recent source tree with portmaster/make build process. >> >>> >> >>> Looks like a serious bug to me and not a site/user specific problem. >> >>> Hopefully others do >> >>> realize the same ... >> >>> >> >>> Thanks in advance, >> >>> >> >>> oh >> >> >> >> >> >> Hmm, I just tried to reproduce that. Both ports mentioned, databases/redis >> >> and www/apache24, can be built and installed with Portmaster. The box is a >> >> 15.0-CURRENT with pkg-1.21.0. >> >> >> >> Maybe 'pkg check -Bn' or 'portmaster --check-depends --check-port-dbdir' >> >> show some inconsistencies? >> >> >> >> Best wishes, >> >> Rainer >> >> >> >> >> > using portmaster or not are strictly unlikely to be helpful here. >> > >> > The right way to test if to report running with pkg -dddd and also to >> > recommand >> > testing with default options in pkg.conf. >> > >> > Best regards, >> > Bapt >> >> This is correct and certainly better. I was not aware of this. >> >> Fortunately, my less optimal suggestions helped O. Hartmann in this case >> to find the missing and outdated dependencies. >> >> In any case, many thanks for this helpfull advice. >> >> Regards, >> Rainer >> >> > >Hello, > >@Babptist : it should be pkg -d, shouldn't it? Or do I miss again something >here?
Each d will provide a more verbose level of debug Bapt
