svn commit: r311135 - head/ports-mgmt/pkg

[Matthew Seaman]

On 29/01/2013 21:07, Adam McDougall wrote:
> I couldn't figure out what component is injecting this problem (pkg
> 1.0.5?) nor did I see anyone else report problems yet, but I've seen
> problems on a couple computers now while other computers upgraded fine.
>  I've been installing packages on a mix of post-9.1 and pre-9.1
> systems.  I can't figure out why pkg 1.0.7 would make packages that pkg
> 1.0.7 complains about when installing.  Can I provide more information
> or help in some way?  Thanks.

It was a bug in pre-1.0.5 that any mtree files were actually not being
processed at all by pkg.  Most of the time, that isn't detrimental: only
a few pkgs actually need mtree functionality.

Unfortunately, hooking mtree processing back up has exposed a number of
bugs in dealing with mtree files.  Mostly they should be harmless --
just annoying warnings, like you're seeing -- and you can ignore them.

There should be any difference in the package formats generated by 1.0.7
or earlier versions.  The mtree files themselves are copied out of the
ports, so shouldn't differ between versions.  It's just the code that
interprets mtree files that has changed and is complaining a bit loudly
at the moment.

The long term plan is to get rid of mtree functionality entirely.  pkg's
+MANIFEST can encode the same information, and it makes no sense to have
the redundancy.  However, that can't be done until pkg_tools go out of
support with the EoL of 8.3-RELEASE in April 2014 at the earliest, as we
have to maintain compatibility in the ports tree until then.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey


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