From nobody Fri Dec 09 08:20:06 2022 X-Original-To: freebsd-ports@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 4NT3qH47pWz4jvtd for ; Fri, 9 Dec 2022 08:20:11 +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 4NT3qH3dbtz3CxC; Fri, 9 Dec 2022 08:20:11 +0000 (UTC) (envelope-from bapt@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1670574011; 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=uzVNx59xyP3/Lx3q1w54QcNjnIMiMcvX9yl83xY7Wuo=; b=tawm0zroMF6dF6UAmAJvOzXqZFGQJahYvz6nAexbnV2iYaqu6dJ7zvYtB4tQYvlxS0H5iD iThkRF7is01MVE8gX24z7xlDKh2y0zW0EuaPFpTn6pc3GVSeMDrUfzXYG8JwmLltMNB2lg qeD/YRPa7tyCFXEjTbDqkk9QvEDLxvDEb+8D16oiELJrLH6QWDQJIS6aN7EbFSKWdqmVk2 AMaLQnMvKxvYM2VeiYUHf/UMVuSQqlPUEpYbv4yFlHksisDM0I3JO/t2IjPyOczUpJk604 sCLnqN0C6I6iPYLOyNC4mtmpPY8XYtZ5h2rrTfoqb28Y/p8tJ+Kn5wCJJ80ZbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1670574011; 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=uzVNx59xyP3/Lx3q1w54QcNjnIMiMcvX9yl83xY7Wuo=; b=XZyb8bH7CzgaLURaajwYc2QE0qfqtO4OtK08PbBwb7Mkjeh0fzFnyHuU1KJ5g1yJV1iquU O0tHj2H/xg8dASebopSBsD5SpAd/arqgM0krUci/VQRDZlEhrpjWXuAkrjVPpgCtOxlqVg WTgq0ULImqd/+ClnvDl+qU/mevYTMYhgLJ+oHFuPk2m7CkULd73F4pLG+zWwR1GIydhAG/ jQvLKnsyhDzpMM60kcW+JLf9PGpsteECse4mKp5z3ImK6zKZg6Zw+XF0EtzLwRWVIIoBSC S0WmtXi+W7ZsSAeQrm9Al1drQYe66vIYEz7B2NFi+C6ezOQ3ypo7rwEVXFQr1A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1670574011; a=rsa-sha256; cv=none; b=w9qrZr2jjPFX2A40vfKMg+YFQ5Kk8i0/g55sbRTG/9Nbnpi03J0lmIsSCWTOvJWPg8REC7 8RvSJtytsvLyxXrxiVHzWPiFClawE2AYk5qm9clYepk4VaYWbtHkLZUa5S03Smk7zJWpq6 t1TTrTrj4VrMbLsUz+WR+mXZEbX5p2+ma62GEmSmo0hpgIUBswXBtJJC6zyoLLfx0+F7fc lECk9TQrFT2wQGPEhxPe9pgY5Lnb8CCIhTh4b1rn59EAg1KpaTPTIznO1rsyHpBQ3OPxME SCm4tr6CkESH9DXn6wJf4PzHUixgShVaQa7dq9p0LRzVD5Vy9/7BlvBQ4PCWvQ== Received: from aniel.nours.eu (nours.eu [176.31.115.77]) (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 did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 4NT3qH0tnlzNl4; Fri, 9 Dec 2022 08:20:11 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id 7084D18DECB; Fri, 9 Dec 2022 09:20:06 +0100 (CET) Date: Fri, 9 Dec 2022 09:20:06 +0100 From: Baptiste Daroussin To: Tatsuki Makino Cc: "freebsd-ports@FreeBSD.org" Subject: Re: ports-mgmt/pkg: 1.18.4 excess "already" message when pkg lock Message-ID: <20221209082006.cxq6u2frwp3wrkua@aniel.nours.eu> References: List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-ThisMailContainsUnwantedMimeParts: N On Fri, Dec 09, 2022 at 05:04:28PM +0900, Tatsuki Makino wrote: > Tatsuki Makino wrote on 2022/09/13 07:51: > > When pkg lock/unlock with pkg-1.18.4, some packages may say "already" message. > > # pkg lock pkg llvm13 > > llvm13-13.0.1_3: lock this package? [y/N]: y > > Locking llvm13-13.0.1_3 > > llvm13-13.0.1_3: already locked > > I have only seen the log of the 1.18.99.7 change, but I assume that is fixed because I changed it to read all packages for which the lock is to be changed before changing the lock. > Thank you very much. > > Yes this has been fixed and will be in 1.19 which is in exp-run right now. Bapt