Received: from out0.migadu.com (out0.migadu.com [94.23.1.103])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 49B4978079D
	for <~alpine/devel@lists.alpinelinux.org>; Sat,  8 Oct 2022 23:48:43 +0000 (UTC)
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ayaya.dev; s=key1;
	t=1665272921;
	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:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=A4Sulgnv7PocufImgtJjSd4pMa+NNJOs6jjejVyucOc=;
	b=Zd0PW4oWVwyeS6XTPEMalbW7RHHD+PiFHBcqDgX/mk76GxFS/Shmwt+P5F0bZ5jlY5qF0L
	emznbTpt0glkunEz1cPBUkH3FmYVBG/hRDBKI6+N1dJo1NLkwVjWjLazWlj8QNevCOeSqQ
	IX9qyB3HGNES6x0agfyn11FA67Th/tQ=
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Sun, 09 Oct 2022 01:48:40 +0200
Message-Id: <CNGXZEK1U52Q.39MX1JI7DVSQ@sumire>
Cc: <~alpine/devel@lists.alpinelinux.org>
Subject: Re: Why did pipeline build two packages?
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: "alice" <alice@ayaya.dev>
To: "Wolf" <wolf@wolfsden.cz>
References: <Y0Cq5VKmcRgkezYu@ws> <CNG2LTDA05SC.3EVTYAI1YLLIF@sumire>
 <Y0HhHVza644D2ZhP@ws>
In-Reply-To: <Y0HhHVza644D2ZhP@ws>
X-Migadu-Flow: FLOW_OUT

On Sat Oct 8, 2022 at 10:44 PM CEST, Wolf wrote:
> On 2022-10-08 01:13:21 +0200, alice wrote:
> > On Sat Oct 8, 2022 at 12:40 AM CEST, Wolf wrote:
> > > Hi,
> > >
> > > I'm curious about this[0] job that was executed as part of pipeline f=
or my
> > > merge request. It looks like it tried to build two packages:
> > >
> > >     >>> testing/bazel: build succesfully
> > >     >>> testing/bazel4: build succesfully
> > >
> > > Any idea why? My merge request[1] is touching just one of them, so I
> > > have no idea why both are built. It seems a bit unnecessary and the
> > > build takes quite long.
> > >
> > > Given that I do not touch bazel4, I guess following error is expected=
?
> > >
> > >     >>> bazel4: Updating the testing/x86_64 repository index...
> > >     >>> bazel4: Signing the index...
> > >     >>> ERROR: the built package (bazel4) is already in the repo
> > >
> > > Any ideas?
> > probably because bazel4 provides=3Dbazel and the thing that triggers th=
e
> > rebuilds for CI gets confused by it. the new one should be named bazel5
> > in any case :)
>
> I see, I did not notice that. I will add provides=3Dbazel into my package
> as well.
>
> Sure, I will rename it, no problem. Is there any rule on whether
> packages should include their version in the package name? For example
> neither php nor nodejs do it (and there multiple versions would be
> actually useful), but for example lua does. I assume there is no
> clear-cut rule?
php does (7, 8, 81). nodejs would too if it had more than lts/current, i
guess..
so, only really the things with multiple versions for real (and not
simply "latest"/"lts"), but there's no clear cut rule.
>
> I will rename it of course, I don't really care about the name :)
>
> W.
>
> --=20
> There are only two hard things in Computer Science:
> cache invalidation, naming things and off-by-one errors.