Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Mar 2020 09:48:00 +0100
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        Kubilay Kocak <koobs@FreeBSD.org>
Cc:        Neel Chauhan <neel@neelc.org>, freebsd-ports@freebsd.org, Kyle Evans <kevans@freebsd.org>, "portmgr@FreeBSD.org" <portmgr@FreeBSD.org>
Subject:   Re: Unable to run "pkg update -f" on 13-CURRENT
Message-ID:  <20200303084800.5vbrcyvl2zhr37vs@ivaldir.net>
In-Reply-To: <3b65223b-f6e2-cd80-7461-d0179348ee15@FreeBSD.org>
References:  <e5f6ad5c4f0e4b12e74176487a7f3357@neelc.org> <3b65223b-f6e2-cd80-7461-d0179348ee15@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--e3oqauqwejtys7ug
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 02, 2020 at 04:50:10PM +1100, Kubilay Kocak wrote:
> On 2/03/2020 2:47 pm, Neel Chauhan wrote:
> > Hi freebsd-ports@,
> >=20
> > I am running FreeBSD 13-CURRENT and I am getting this error on a "pkg
> > update":
> >=20
> > pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64
> > pkg: repository FreeBSD contains packages with wrong ABI:
> > FreeBSD:13.0:amd64
> >=20
> > I am running FreeBSD 13-CURRENT r358510.
> >=20
> > Why is this happening?
> >=20
> > I also filed a bug on Bugzilla:
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244549
> >=20
> > -Neel
> >=20
> > =3D=3D=3D
> >=20
> > https://www.neelc.org/
> > _______________________________________________
> > freebsd-ports@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>=20
> There's a known issue with the official FreeBSD package builders (which u=
se
> ports-mgmt/pkg-devel) causing mismatched ABI error messages for package
> users after a recent pkg-devel update.
>=20
> Pull request addressing the issue has been submitted by Kyle (CC'd):
>=20
> https://github.com/freebsd/pkg/pull/1817
>=20
> The change needs to be deployed to the build cluster to resolve the issue

No the fact that antoine marked the port as FORBIDDEN was enough. There is =
no
need to deploy anything to the build cluster

Bapt

--e3oqauqwejtys7ug
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAl5eGb4ACgkQY4mL3PG3
Plp2Ow/9HNQ94hDzi6GQmg8TeNSp89B3zmAUZ6O5FdlOlZxB/yLjjT8inzPUeuoR
B8Vt+EAlFA4VpRB4zJTZZCcowrmqBFNT/hafmowkPWRj87MYzyA+kno2LqdMy8mZ
VK39HyNdHkWips8aGfTNqUDtfo+5eejv2/it5d+NtW7AB8oNqA7M/oROw3uzEaLM
redkCTpkt20/i8q0Nv5HgikH9fpRJWF1qY3MpwvTr5Yfp9GMsTKW5BSIZykBT8Ik
8j3JIJUQV0NntU8Salp9MHUfRzwYa1G8jYEwWkvDmwjafVeqYa+diYnSjM7+9Xx3
/VJ/zgiwpEeiAtIQHseN2jzAmQQk73EO/YtHsuv8ozqVi1bEBGPwIiwptaVvksr9
ZXuc3GgzpMXd+tjPKWDImbjVB8KtObYzh5og7qf/TXbCUR0kP8QPzS7dmRNw8LZ0
HMW9HA0JuYuzoQ5J22wW+MmauXDUmJSD4MmYj7ADFeyvWp3w2S3VjDHwnTZGUIIY
81xXwBjeyIKHSIYSaEweBxHR2vzhQuj3PmHG4HqbUaCtvMthrjzd8eCTaH2ABPDu
MwRlPcNjV1mOEPOuCO7rTEDrr02t5G/mP1zych22LqYnWAtUVGFmpsIw601NHwHH
LK+cqqUtU1oF3arS4pXWbeSLO8ziiiTsf4oADJAFJc9nllJyBpI=
=CsU7
-----END PGP SIGNATURE-----

--e3oqauqwejtys7ug--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200303084800.5vbrcyvl2zhr37vs>