From nobody Wed Apr 12 10:26:21 2023 X-Original-To: dev-commits-ports-main@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 4PxJlk1FnYz44TyB; Wed, 12 Apr 2023 10:26:26 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PxJlj0fC3z3M67; Wed, 12 Apr 2023 10:26:25 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681295185; 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=OiYDF0C2/2JO9Oz9DbjmzxUHKVXIE33hhqxeupm+VD8=; b=Tyak3CRcu1sVcqyXAQNR//Zxh2QLWvnZlan5LmM+LGg5/MLY7aVX8Nv2nfQeAt2LGsBisq 11q7ByIDZyPBsRrJwRLQNnNYlpYtEi+kYxLttvU/3iVmpexq3dfiqPsERQKqpPaYrx4xp5 8BFWTE+wkQxOVV51fQgfGFV+Z0uKMjPUmS1xIdK+hKMYoWEMqUp2s71UOE7HDYHlTsHlUO PmRWz5AXlyT1aniE5oIyB6hbLCPDMvjBbjwa9+q/CUQZCEUFDhf3pazFFNrguZpjSyKx66 ZXyA7NHL7UVesQzoHWt0W9cUGK39DJv1FJAUG+BlgkFtvMKPlC8nmLPrqii5EQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681295185; 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=OiYDF0C2/2JO9Oz9DbjmzxUHKVXIE33hhqxeupm+VD8=; b=ORbh6Nksupyp7ZL12pP3/cDeYv9celJNAxQ17j0R2TKGs8yfMELxGTa0jPDkCAfGeEreju pTCseIen7wfKbW46EKcK6fcN7rIp27YxuFxf6cg4cfHdU4MHf028/YpfAu4Mo3b7vgpcww Uoq15SZy4MCcMv7Vz7IZNErmI9dQmlrxX1h726CrsO7+A/JDGZmv4xy/iT/Oq0GO8/POjR ldgbC/sWGM/x99pyU3pN7xrlWbWcJFwHXF4uL6+xgYxKA42gsVF+p54nfOtUlP7KPhGec+ N0ZuXZtN8tKJCzslbB3mOtqgTZaHZtjy6AJNU+avg6YI3N+Q4piqDead+jmHcg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1681295185; a=rsa-sha256; cv=none; b=oCrTF5Um1AAOLcBbxJn2GLTS3RBFc6E9VNLGgvhMltG+tWdWUYLqqn0/bmP/x9DNEJ9K4F 1Ynr8iSVRfPHJQMGF4ExkwDgB9OjzwoK+/IoGV2Pqn3blalboN/2QOqElS4RFhghSgmVVt 4CG6brQFfbVFp1BK7DIM/a8jzi3+x7Xfx1q84q/Xc/IjJnnm9jFkzJdk6mIRpRSM1D7ajK 5NxAPAFHdkLDWZ/if5kP7XbtcQ6yRdWEkTmtZ3r0NY/U1zPU2HswWSB9HSz7diXqilkY0n 4Z6Jcy3XuhlnQCF6ZpIlr+yCcpgnxymn1FftYoSTBE/km16j7Ai/S0FnNHgPEw== Received: by freefall.freebsd.org (Postfix, from userid 1354) id F30BDD8CF; Wed, 12 Apr 2023 10:26:24 +0000 (UTC) From: Jan Beich To: Daniel Engberg Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: a650970e9116 - main - multimedia/libva-utils: unbreak fetch due to tag update In-Reply-To: <2f6735ac033562bd3c75ec5603b0a26e@FreeBSD.org> (Daniel Engberg's message of "Wed, 12 Apr 2023 11:49:24 +0200") References: <202304120934.33C9YaOL008619@gitrepo.freebsd.org> <2f6735ac033562bd3c75ec5603b0a26e@FreeBSD.org> Date: Wed, 12 Apr 2023 12:26:21 +0200 Message-ID: <8rex-qtv6-wny@FreeBSD.org> List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-ThisMailContainsUnwantedMimeParts: N Daniel Engberg writes: > On 2023-04-12 11:34, Jan Beich wrote: > >> The branch main has been updated by jbeich: >> URL: >> https://cgit.FreeBSD.org/ports/commit/?id=a650970e91168940eb1728a5923d87ae7dea4b05 >> commit a650970e91168940eb1728a5923d87ae7dea4b05 >> Author: Jan Beich >> AuthorDate: 2023-04-12 09:33:15 +0000 >> Commit: Jan Beich >> CommitDate: 2023-04-12 09:34:24 +0000 >> multimedia/libva-utils: unbreak fetch due to tag update >> => Fetched file size mismatch (expected 1279583, actual 1279551) >> Changes: >> https://github.com/intel/libva-utils/compare/38e2a65...2.18.1 >> --- >> multimedia/libva-utils/distinfo | 6 +++--- >> 1 file changed, 3 insertions(+), 3 deletions(-) >> diff --git a/multimedia/libva-utils/distinfo >> b/multimedia/libva-utils/distinfo >> index 67d5bc3cfa93..1debfc7db0ca 100644 >> --- a/multimedia/libva-utils/distinfo >> +++ b/multimedia/libva-utils/distinfo >> @@ -1,3 +1,3 @@ >> -TIMESTAMP = 1680135218 >> -SHA256 (intel-libva-utils-2.18.1_GH0.tar.gz) = >> 79da4a683dc4b10639edd7ad4c9434789ef208f5361f87aca9bc986a4ebcb155 >> -SIZE (intel-libva-utils-2.18.1_GH0.tar.gz) = 1279583 >> +TIMESTAMP = 1681291944 >> +SHA256 (intel-libva-utils-2.18.1_GH0.tar.gz) = >> 724a54524d9156967d3508f294ce5c45d94cb8f7326537c24ee7fcf59e70de91 >> +SIZE (intel-libva-utils-2.18.1_GH0.tar.gz) = 1279551 > > Hi, > > Seeing that we've only stuck with releases for years just use > upstreams release tarball to avoid these unnecessary breakages? > See https://github.com/intel/libva-utils/releases/tag/2.18.1 etc This assumes upstream won't refresh tarballs on tag updates. Notice the timestamp on the release artifact for 2.18.1. I don't remember if 2.18.1 was a release or just a tag before today. Besides, I'm not going to wait weeks for upstream to promote a tag to a release just to get release artifacts.