On 14/05/2013 02:53, Ronald F. Guilmette wrote:
> Running my revised version of the script yields this output:
>
> pkg_sanity: gettext-0.18.1.1: Newer than +CONTENTS file:
> /usr/local/lib/charset.alias
> pkg_sanity: linux_base-f10-10_5: Newer than +CONTENTS file:
> /compat/linux/etc/ld.so.cache
Well, I have looked a bit more at some of the files that posted about
just a short while ago. It turns out that pretty much all of the
remaining anomolies (i.e. MD5 mismatches) in package-related or port-
related files on my system can be attributed to either (a) some person
or else (b) some thin
So, as I have now learned (and just as the post by CyberLeo Kitsana had
suggested) if one wishes to write a script to do the rough equivalent
of what "pkg_info -g" does, then one has to be mindful of the fact that
for those specific MD5 checksums contained in the various +CONTENTS
files within the
In message <518e1a51.3020...@cyberleo.net>, you wrote:
>On 05/10/2013 03:04 PM, Ronald F. Guilmette wrote:
>
>> pkg_sanity: ImageMagick-6.8.0.7_1: +CONTENTS file does not exist -- skipped
>> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-2.so: File failed MD5
>> checksum
>> pkg_sanity: ORBi
On 05/10/2013 03:04 PM, Ronald F. Guilmette wrote:
> pkg_sanity: ImageMagick-6.8.0.7_1: +CONTENTS file does not exist -- skipped
> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-2.so: File failed MD5
> checksum
> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-imodule-2.so: File failed
On Fri, May 10, 2013 at 02:17:32PM -0700, Ronald F. Guilmette wrote:
> b.f. bf1783 at googlemail.com wrote:
>
> >Yes, of course, this is a basic package management feature:
> >pkg_info(1) with the "-g" flag.
> >(The analogous part of the newer pkgng is described in pkg-check(8)
> >from ports-mgmt/
b.f. bf1783 at googlemail.com wrote:
>Yes, of course, this is a basic package management feature:
>pkg_info(1) with the "-g" flag.
>(The analogous part of the newer pkgng is described in pkg-check(8)
>from ports-mgmt/pkg.)
Thank you. I did not know about the -g option.
I have just now run tha
"Ronald F. Guilmette" wrote:
>
> The subject line pretty much says it all.
Additional to other ideas so far,
You could also make a chroot, install normal bins from src,
install all your ports, ^D to exit chroot, then do a compare & strip with eg:
cd chroot ;
find . -type f -exec cmpd -d {} / \;
abble.com/WANTED-Tool-to-verify-installed-package-port-consistancy-tp5810087p5810174.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsub
Ronald wrote:
...
> It occurs to me that *something*, i.e. some tool(s) within the FreeBSD
> panoply, *must* already be reading and/or otherwise making use of those
> MD5 checksums within the +CONTENTS files. Otherwise, why would they even
> be there? So my question really comes down to this: W
The subject line pretty much says it all.
As I explained here the other day, numerous of my installed ports
have semi-mysteriously had their corresponding +CONTENTS files
just disappear. I do have a backup of my /var partition, from which
I could, in theory, fetch replacements for the specific +
11 matches
Mail list logo
