Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Sep 2019 14:07:10 -0000
From:      Glen Barber <gjb@freebsd.org>
To:        Colin Percival <cperciva@tarsnap.com>
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-12@freebsd.org, portmgr@freebsd.org
Subject:   Re: svn commit: r340905 - in stable/12: release/pkg_repos usr.sbin/pkg
Message-ID:  <20190419130522.GI39941@FreeBSD.org>
In-Reply-To: <0100016a32795508-fd8bbc41-2b38-40ae-903a-e3ef3739dfd8-000000@email.amazonses.com>
References:  <201811241747.wAOHlr6W029937@repo.freebsd.org> <0100016a32795508-fd8bbc41-2b38-40ae-903a-e3ef3739dfd8-000000@email.amazonses.com>

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

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

On Thu, Apr 18, 2019 at 10:02:53PM +0000, Colin Percival wrote:
> On 11/24/18 9:47 AM, Glen Barber wrote:
> > Author: gjb
> > Date: Sat Nov 24 17:47:53 2018
> > New Revision: 340905
> > URL: https://svnweb.freebsd.org/changeset/base/340905
> >=20
> > Log:
> >   Revert r340161 in stable/12, setting the default pkg(8) repository ba=
ck
> >   to 'latest' from 'quarterly' prior to branching releng/12.0.
> It looks like this is incorrect for non-x86 architectures.  Portmgr may
> correct me here, but it looks like "latest" builds are only done on non-x=
86
> architectures on HEAD.  (The same problem also applies on stable/11.)
>=20
> I'm guessing that the answer here is to have different package configurat=
ions
> installed depending on the architecture; I knew how to do this with the o=
ld
> style of src/etc but I'm not sure how to do it now that pkgbase has spread
> configuration files all over the tree.
>=20

For 13.0-CURRENT, both latest and quarterly are updated.  For non-x86 on
12.0-STABLE and 11.2-STABLE, quarterly is updated (not latest), so from
a general sense of this particular commit, it is correct.

But you are also correct in your assertion that the current default
(latest) for non-x86 does appear to be incorrect.

I'll do some poking around into this.

Thank you for bringing this up.

Glen


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

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

iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAly5x4YACgkQAxRYpUeP
4pN8IA//d/nKqUlI+8b+Mb7Dbb7Vyf3tNwEdsU6IIE1btByJpDyBJklaBXtXtpNK
em9v0t5H8T+i87ZGUzIbieg6LpZyT3PElJhnT2q0tpV6fb9JzdAvgDF7dzw8hmjS
sURwaX7eeFUqAhi5fiwBa/9JW2YUMxVOKNyIM/YFVmOwChcWENDr01TtT6J/z9gb
yxOlSUPkiB1Mi8dIMQJ0ulryjcSN4126o64cCxDSFM9WTPLTtTuzHHEkartPAolk
TFRG7rcvvv0xxoEEh+ptyo0Vi5YMD1SF3M0jQiLkXrnrwLdc2RxTiz/hySodlYLn
MMX24J6mor4qC4Ir7aXjH8G50Nmj6cVyNXVG1/IqeSPiEN12n6bQCkFgzQ4w7uc1
3UB/qKh1aoeYfBWyb4aLCCRum3dMZg0IZrWeKA4Y70qClt6xsBYB/NjpI+I/7oWQ
GW8ol38Uz3JEsXn+KlVxVD+e4k0dJ/PwHzx6zknMAiFkNpykUYAhdulDVKnr1+xI
lSJmbHWsqLHXAimuoZ2/2bFoJKzuOVeecEe8IU5rF9+YWUV7Gc6w0behpdMgXCdF
o+aaUOgQIn7mZnSymndagfp/PifQ61rTjZW5uW2yqdp+CZc/X5WJHJamE2J6bBlr
4/qOBy34BCPKGanUprVagNtkHgHkJxFRO0inK34KbRmQRNELvuY=
=7gV1
-----END PGP SIGNATURE-----

--Pgaa2uWPnPrfixyx--





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