Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Sat, 08 Oct 2022 01:13:21 +0200
Message-Id: <CNG2LTDA05SC.3EVTYAI1YLLIF@sumire>
From: "alice" <alice@ayaya.dev>
To: "Wolf" <wolf@wolfsden.cz>, <~alpine/devel@lists.alpinelinux.org>
Subject: Re: Why did pipeline build two packages?
References: <Y0Cq5VKmcRgkezYu@ws>
In-Reply-To: <Y0Cq5VKmcRgkezYu@ws>

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 for m=
y
> 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 the
rebuilds for CI gets confused by it. the new one should be named bazel5
in any case :)
>
> Thank,
> W.
>
> 0: https://gitlab.alpinelinux.org/gray-wolf/aports/-/jobs/865337
> 1: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/39933
>
> --=20
> There are only two hard things in Computer Science:
> cache invalidation, naming things and off-by-one errors.