Date: Mon, 13 Jul 2009 13:33:23 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Fedor Dikarev <fedor.dikarev@gmail.com> Cc: ports@freebsd.org, Cezary Morga <cm@therek.net> Subject: Re: Bad INDEX-7 file ? Message-ID: <4A5B2993.1030403@infracaninophile.co.uk> In-Reply-To: <aa8571d30907130327gea45b21k357f90607b42ad94@mail.gmail.com> References: <aa8571d30907130204r7d9bc018t87f6c341f1252805@mail.gmail.com> <4A5B09A4.5050502@therek.net> <aa8571d30907130327gea45b21k357f90607b42ad94@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2895C2F0FBFA93EDD56A1FA6
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: quoted-printable
Fedor Dikarev wrote:
> By this command I've just explained that this port has version 1.3.8
> but in INDEX-7 vesion differ -- it's 1.3.7.
> So INDEX file is built on old ports tree or there was some bug during
> building process.
It's just an old INDEX-7 file -- as I recall, they are meant to be update=
d
something like hourly, but on occasion there will be a problem and the IN=
DEX
files available for download may not be updated for an indefinite period,=
until
the INDEX can be built cleanly again.
Now, there are several things you can do about this:
* Ignore it. Having a 100% accurate INDEX file is nice, but not an
absolute necessity. Most ports management software will be forgivin=
g
of the odd irregularity. Even if it means package 'foo' doesn't get=
updated today when it could have been, it would almost certainly get=
updated tomorrow or next week. It all works itself out in time.
* Use ports management software that doesn't rely on the presence of t=
he
INDEX at all. viz: portmaster(1). As I said, most ports management
software is fairly forgiving of irregularities in the INDEX, but thi=
s=20
program goes beyond that entirely and compares the database of insta=
lled
ports under /var/db/pkg/ directly with what is in the ports tree.
* Build your own. You can just type 'make index' in /usr/ports. Then=
go
away and have a nice cup of tea. Then have another one. And some b=
iscuits.
It might have finished building by now... Building your own INDEX u=
sually
works pretty well, but it does take quite a while every time you hav=
e to
do it. It does get you an INDEX that reflects local settings you mad=
e in=20
/etc/make.conf or in OPTIONS dialogues, which is nice. If I might b=
e
permitted to tootle my own trumpet a bit, there is=20
ports-mgmt/p5-FreeBSD-Portindex that I wrote, which can cut down th=
e time
it takes to routinely build your own index by only reprocessing the =
bits
of the ports tree that have had updates since the previous time you =
built an
INDEX.
=20
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--------------enig2895C2F0FBFA93EDD56A1FA6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkpbKZkACgkQ8Mjk52CukIz1EwCdFPbtfj7dSrWPBJYkhFjLkQZc
1pkAnR2WkQHiUxTaGlkG7cQuKXo2h7rt
=AFJ8
-----END PGP SIGNATURE-----
--------------enig2895C2F0FBFA93EDD56A1FA6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A5B2993.1030403>