Date: Tue, 29 Jan 2013 21:43:10 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-pkg@freebsd.org Subject: Re: svn commit: r311135 - head/ports-mgmt/pkg Message-ID: <5108426E.8080109@FreeBSD.org> In-Reply-To: <51083A0E.3010308@egr.msu.edu> References: <201301282042.r0SKgM5r012171@svn.freebsd.org> <51083A0E.3010308@egr.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2NSIISPTAQKAAGFNMFLED Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey ------enig2NSIISPTAQKAAGFNMFLED Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEIQnUACgkQ8Mjk52CukIyE/gCfYZQyZxwjRBbyBSmcrUgDYDqe ArMAn30BrE/XABYip2ooqDu0W3wDiJk9 =rBXR -----END PGP SIGNATURE----- ------enig2NSIISPTAQKAAGFNMFLED--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5108426E.8080109>