On Wed, Apr 27, 2022 at 08:47:26PM -0700, Chris wrote: > On 2022-04-27 20:40, Michael Schuster wrote: > > Chris, > > > > thx for your response. However .... > > > > On Thu, Apr 28, 2022 at 4:19 AM Chris <bsd-li...@bsdforge.com> wrote: > > > > > > On 2022-04-27 12:59, Michael Schuster wrote: > > > > Hi, > > > > > > > > $subject happened to me just now on current. I researched it on the > > > > internet, the answer to this issue seems to be a universal "uninstall > > > > and install the package" which seems to have worked in all cases I saw > > > > it suggested. > > > > > > > > I'm trying to embed this command into a script and would like to avoid > > > > manual intervention (I have to admit, this is the first time I've > > > > encountered this error in the two years I've been doodling with > > > > FreeBSD again) ... > > > > Is anything more known about this error behaviour, and what I can do > > > > to avoid it? > > > > > > > > TIA > > > > Michael > > > > > > > > PS: in case it matters: the full path shown in the error message is > > > > /usr/local/include/KF5/GrantleeTheme/GrantleeTheme/.pkgtemp.GenericFormatter.qSk5LxEaheWG, > > > > the package being extracted is grantleetheme-22.04.0 > > > This looks more a case for the Maintainer of the GrantleeTheme than for > > > current@ > > > > ... maybe. OTOH, the instances I found mentioned on the 'net are all > > about different packages: > > > > eg: > > https://forums.freebsd.org/threads/pkg-upgrade-fail-to-create-temporary-file.67923/ > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237767 > > > > I feel there's something different at work here than just one > > maintainer's oversight. > You may well be correct. On the surface, to me it looked like a port problem > so I thought > you might get quicker results via it's maintainer. :-) > > Good luck! :-) > > > > Thx > > Michael
It is 2 things, it is a port problem of maintainers who do not check for upgradability of their packages, and it can also been seen as something pkg can deal with, but a complicated case, so I don't know yet how. The main issue is a file in vX which becomes a directory in vX+1 which goes in the way pkg does extract files to be as atomic as possible. Best regards, Bapt
