From owner-freebsd-ports@FreeBSD.ORG Sun Sep 18 12:04:52 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7113106566B for ; Sun, 18 Sep 2011 12:04:52 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0898FC19 for ; Sun, 18 Sep 2011 12:04:52 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id p8IC4lEd094744 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 18 Sep 2011 13:04:48 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: Sendmail DKIM Filter v2.8.3 smtp.infracaninophile.co.uk p8IC4lEd094744 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1316347488; bh=xin5BAS54KW2xMqBReirfMKWu3dXwiDKx2W4LR4/N20=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Cc:Content-Type:Date:From:In-Reply-To: Message-ID:Mime-Version:References:To; z=Message-ID:=20<4E75DE55.7080206@infracaninophile.co.uk>|Date:=20S un,=2018=20Sep=202011=2013:04:37=20+0100|From:=20Matthew=20Seaman= 20|User-Agent:=20Mozilla/5.0=20(M acintosh=3B=20Intel=20Mac=20OS=20X=2010.6=3B=20rv:6.0.2)=20Gecko/2 0110902=20Thunderbird/6.0.2|MIME-Version:=201.0|To:=20freebsd-port s@freebsd.org|CC:=20Carmel=20|Subject:=20Re :=20Version=20of=20=20"opencv-core-2.3.1"|References:=20|In-Reply-To:=20|X-Enigmail-Version:=201.3.1|Ope nPGP:=20id=3D60AE908C|Content-Type:=20multipart/signed=3B=20micalg =3Dpgp-sha1=3B=0D=0A=20protocol=3D"application/pgp-signature"=3B=0 D=0A=20boundary=3D"------------enig5B6DCCD22037D4DA175F0319"; b=VffRkQPkEBq7RMivJCYczPAnzvsj+vPqZCaWguPJwy6rbTls+rH2Cs+qIzfzynN+F yIk93gyFKA5bc3jyDXmgVn+Qx6GAs01inBLKHZ3qvz33M4PW12VYn0eUtBvH3mjk5h zbH873Lm6zG/49XgTZgSuuvh+JJ3QLy20oIFAws0= Message-ID: <4E75DE55.7080206@infracaninophile.co.uk> Date: Sun, 18 Sep 2011 13:04:37 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: In-Reply-To: X-Enigmail-Version: 1.3.1 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5B6DCCD22037D4DA175F0319" X-Virus-Scanned: clamav-milter 0.97.2 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: Carmel Subject: Re: Version of "opencv-core-2.3.1" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2011 12:04:53 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5B6DCCD22037D4DA175F0319 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 18/09/2011 12:36, Carmel wrote: > When running: "/usr/sbin/pkg_version -vIL=3D", I received this rather > strange output:=20 >=20 > opencv-core-2.3.1 > succeeds index (index has 2.3.1= =2Ea) >=20 > I would have expected output to be more like this: >=20 > apache-2.2.20_1 < needs updating (index has 2.2.2= 1) >=20 > I have never seen this before. Is there something broken? I have a > suspicion that programs like "portupgrade" or "portmanager" will not > properly handle this. >=20 > This is on a FreeBSD-8.2 amd64 system. It's not a particularly rare thing. All it means is that the INDEX file is somewhat out of date. There's many reasons why that can happen -- eg. plenty of ways to commit things to the ports that will break generating the INDEX, the machines doing the generation getting their knickers in a twist or not being able to upload the new INDEX to the right servers. If you wait for a few hours and re-csup it should be fixed. AFAIK, I don't think this affects portsnap because it generates the INDEX in a different way. Or you can create your own INDEX if you want. However, for most uses, you don't actually need a 100% accurate INDEX. If you install from ports and set any OPTIONS to non-default values, then chances are the default INDEX won't match the actual dependencies in your ports tree anyhow. Same if you use a non-default version of perl, python, mysql, postgresql, apache or several other important ports. That doesn't impede normal ports usage. portmaster(8) only uses the INDEX file if you specifically tell it to: usually that's if run it in packages-only mode. portupgrade(8) -- it's been a while since I've used portmaster, but as far as I recall, it didn't particularly need the INDEX either. Even if a broken INDEX does screw things up, generally what will happen is that your upgrading session will fail to upgrade certain packages leaving the old versions in place and still working, and you can just wait a while and try again later. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig5B6DCCD22037D4DA175F0319 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 Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk513l8ACgkQ8Mjk52CukIz1DACfdapHMqRGDzL6rB/FdSpvC92h NaMAnRDAal50FWdmpTHAsQJ+25k/1lsv =Ryjn -----END PGP SIGNATURE----- --------------enig5B6DCCD22037D4DA175F0319--