Unable to update repository Synth

[Jeffrey Bouquet]

--------------------------------------------
On Fri, 6/9/17, Jonathan Chen <jonc at chen.org.nz> wrote:

 Subject: Re: Unable to update repository Synth
 To: "Bob Willcox" <bob at immure.com>
 Cc: "ports list" <freebsd-ports at freebsd.org>
 Date: Friday, June 9, 2017, 3:14 PM
 
 On 10 June 2017 at 05:02, Bob
 Willcox <bob at immure.com>
 wrote:
 > I am running the drm-next-4.7
 and when I ran synth recently on my system
 > up update the ports and at the end of the
 run received these errors:
 >
 > pkg: wrong architecture: freebsd:10:x86:64
 instead of FreeBSD:12:amd64
 > pkg:
 repository Synth contains packages with wrong ABI:
 freebsd:10:x86:64
 > Processing entries:
 100%
 > Unable to update repository
 Synth
 > Error updating repositories!
 > Unfortunately, the system upgrade
 failed.
 
 synth is
 complaining that one or more of the packages in the
 configuration's package directory has
 packages built for
 FreeBSD10/amd64 instead
 of FreeBSD12/amd64. If you have upgraded from
 FreeBSD 10 to FreeBSD 12, you must remove all
 the packages that have
 been built
 previously.
 
 Cheers.
 -- 
 Jonathan Chen <jonc at chen.org.nz>
 _______________________________________________
 freebsd-ports at freebsd.org
 mailing list
 https://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
 


................................
pkg: Ignoring bad configuration entry in pkg.conf: "INDEX-12"
If I build from ports pkg thinks it is freebsd:11:x86:32 ... and will replace with freebsd:12:x86:32
 with an ABI changed.
however, it is 12.0-CURRENT.

  Any way to make it all consistent? 
..............................................
/etc/pkg has ${ABI}
/usr/local/etc/pkg.conf has freebsd:12:x86:32
/usr/local/etc/.../FreeBSD.conf has ${ABI}
..................................
  and some script to parse all the files that are relevant and/or the
  --version from all pkg binaries to tell the user where the irrelevant or
   mismatched setting may be, could be coded? 

.....................