Unexplained pkg behavior and schema errors

[Matthew Seaman]

On 07/01/2016 18:55, Rick Miller wrote:
> The first, and obvious, question is what is causing the schema errors?  pkg
> update and pkg clean were executed after configuring the new repos in
> response to a post located on -questions@[1], but as can be observed in the
> aforementioned transcript, executing this prior to pkg install fails to
> resolve the errors.

That's actually not a problem -- there were some extra fields added to
the package metadata with pkg-1.6 release.  This is just the older
version of pkg warning that it's seen those extra fields.  Harmless, and
it will go away once you've upgraded to 1.6.x.

> Observe also that pkg is upgraded, then downgraded, then upgraded again.
> Is this the expected behavior or is it more likely that something else has
> gone awry?  What possible circumstances would result in this behavior?

OK.  What's happenned there is that you have snmpd in your repo with a
dependency on an older version of pkg.  snmpd is one of very few
packages that depends on pkg itself.  Try rebuilding the snmpd package
and then have another go at upgrading.   Actually, if you have time, it
might be one of those occasions where completely rebuilding all of the
packages in your repo would pay off.  pkg works a lot better when all of
the package versions tally with all of the dependencies across the
available repos.

	Cheers,

	Matthew


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 957 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-pkg/attachments/20160107/8ca4484b/attachment.sig>