From nobody Thu Apr 28 07:11:40 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 40E97199367B for ; Thu, 28 Apr 2022 07:11:44 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Kpmy81PyCz4bjq; Thu, 28 Apr 2022 07:11:44 +0000 (UTC) (envelope-from bapt@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1651129904; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DoOKkaag9N79Ntx/YTLkxrTzY8vMCsZzFktj7bgFhSs=; b=Cj/6HQzWgx3mxGjrA3EO+6J4Oi93Pakwp/nPOi3WP+grXjv93fT1eAevQV0NCDeRiyH/Ku lAZRWmVK8qjS9TXGukvdLvGC1EBlYtppfDBUZHiXzdnJ+wjZNPy10bqXp9ZWMRTjV4gvmM ss0uF0/mPVm4E4efy707mynneMQTjUh8rtGubuXT+u9CZ+EUsVm7kH15LJelcmBaqozOJ4 iyy5w8a7QkOWDt45sOvc/p4ollNHQhOiSPAGby313qFw8Qju0nwH5njyvo/E8shZp52P2c cl/7O45i6YvH56k3ML8lyaNUTae4yod9G6Yvh+Wjt2rSJyYkmJQDCzgGSQPRIg== Received: from aniel.nours.eu (nours.eu [IPv6:2001:41d0:8:3a4d::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id F26F822A08; Thu, 28 Apr 2022 07:11:43 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id CF65EE889F; Thu, 28 Apr 2022 09:11:40 +0200 (CEST) Date: Thu, 28 Apr 2022 09:11:40 +0200 From: Baptiste Daroussin To: Chris Cc: Michael Schuster , FreeBSD CURRENT Subject: Re: "pkg upgrade" failing with "Fail to create temporary file: ... Not a directory" Message-ID: <20220428071140.iuydpxyuryqfs4c4@aniel.nours.eu> References: <93f322eb1d99783e568262a5cd9f5fd9@bsdforge.com> <8364fbb11098ffb0799829972cc6a35d@bsdforge.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8364fbb11098ffb0799829972cc6a35d@bsdforge.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1651129904; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DoOKkaag9N79Ntx/YTLkxrTzY8vMCsZzFktj7bgFhSs=; b=GNKv1S8Te8EI6qlGfVQROMXBfIXYRpAYztSRf9Iv5cUQ4hdasV21fBfJ/TszrkJ279Qk2X g7HCRlX/YvOW7ceT/7d9DKfyKwQHV2HLASgl4msrlBMcw0RWWZojVAWr+2sZAxW+TEZBSy sHWa4FoHhXbM0vnWoE4Y7RAoLXDYunGKvQQyibuNUWcduK97ohAZSY2QR90Yfs5F3EdRwy +YMo/EIPItcAV0rLci8J9NS8LHg64pe4q0dzXOoByB8Xx8NoDFAoSgcM3iLX4vVSQnVOCH GgatyMCYS0p3WgN/vbaIbbUkf62D/5ZvUJx+30kCnw6RbA9w9wLUr0V2Aww19w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1651129904; a=rsa-sha256; cv=none; b=KTDsMp4zHLnZk4pWiIqGY/yKswejfyMr3rYiVzxCpRBWXWwd6MDLZoaIi1dpTWYe2CQv4s KGExo96MCEQfT5mXvHplvwcOof8wb3RZ7AEUottsx9+HX5c8YIvNywWFGQm0UjYGKMt5H/ ud5mWEi9ybPBja82a+VRGUuOp03ZwKZKBOMEnw2TAm2WOjxoETHlsNnh+f9WSaWiJ7BQcM UftVvDSeXpdIHmG0nt5LscMzLMBgfF53CkWVkrxR6ozm+9RGehspC2d1hEETtYZanoTLaZ wekbjR1hV8ImWeFWCC22cUX0IQhVvtSdtb+ONMoWA9cH1rpZKtvVNsVf6oC8hQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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 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