Date: Sat, 8 Oct 2022 22:44:13 +0200
From: Wolf <wolf@wolfsden.cz>
To: alice <alice@ayaya.dev>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Why did pipeline build two packages?
Message-ID: <Y0HhHVza644D2ZhP@ws>
Mail-Followup-To: alice <alice@ayaya.dev>,
	~alpine/devel@lists.alpinelinux.org
References: <Y0Cq5VKmcRgkezYu@ws>
 <CNG2LTDA05SC.3EVTYAI1YLLIF@sumire>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="rXthQX4OYqym426B"
Content-Disposition: inline
In-Reply-To: <CNG2LTDA05SC.3EVTYAI1YLLIF@sumire>


--rXthQX4OYqym426B
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 for=
 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 the
> 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?

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.

--rXthQX4OYqym426B
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEt4NJs4wUfTYpiGikL7/ufbZ/wakFAmNB4R0ACgkQL7/ufbZ/
wam8gBAAiLX/xakeyYqkWPZJN8SzUWEYvS6TLkDykWnixXe+/L5CYbWJ12MHjmUE
K7sWyXbiMiZlPzgx+sW0eU1Xqpj4kaPudovNeeSrErGRG/v3Ym7bpbOnOJ9aVRAp
r7kKA72J0cLtaVqCa4Oybk4Mu1wuRx9MfL4QaXLDo/NGqja6ry/GZzGB73ZsFnwe
ZyYLF4JT1VFDXjpTZHsfA2Iu0KvOm10kkIcZ4pMoQZkFpPXvKpzs2viweBwQlCRW
ASSaYNeQ3o8GofinEyctuE6PLF12tx1avQpYWsJbqj6S6ldR6e0fENtyO95NueuA
gSIt3osCTiln621JOeynv2+NHJus/6i4Xl4bimLwAktzA/mouuAlwY5V2kPnQ5ck
5eQWv4aJfgyoUYqlQfBq9/lThY1uFQH9C81R0zsqgXAWLeasDjsjEY5XzbxLCA1t
gaO7iS6D7PfEO5kLuZkO5UBrf8QqeGRA/YmchLA663LGubIc9bibiuIJfbSGTF/B
kc2CX4LfQJdumJ3IRfcfLH6HW5vDm28Bmkm9mI9mOxD5tD+1kVwP4GY7J/C27zg8
YQ8zoGMZcxhdv4jHB8ZXAsj8nyDC44Busn2PNsItj+HqxbIThmFF1OX7MogXjNyt
X8O1n899+wVBoP3JYrljz29oZPsZevMCrObAX+ZV8PEbre6r53o=
=KMLX
-----END PGP SIGNATURE-----

--rXthQX4OYqym426B--