Date: Sat, 13 Jul 2013 14:02:37 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Leslie Jensen <leslie@eskk.nu> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: pkg: Unable to open ports directory /usr/ports: No such file or directory Message-ID: <51E14FED.9030708@infracaninophile.co.uk> In-Reply-To: <51E1292F.7070005@eskk.nu> References: <51DFE7A6.70505@eskk.nu> <51E1292F.7070005@eskk.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2CWVBTHRKHRKUUEWKTGIE
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 13/07/2013 11:17, Leslie Jensen wrote:
> 2013-07-12 13:25, Leslie Jensen skrev:
>>
>> When I run
>>
>> portsnap fetch update
>>
>> pkg version -vIL=3D
>>
>>
>> It returns
>>
>> pkg: Unable to open ports directory /usr/ports: No such file or direct=
ory
>>
>>
>> The directory is there and I can list the contents.
>>
>> What's going on?
>=20
> I get this as well
>=20
> gunzip: can't stat:
> files/30173a70f7852dc247fda74d2d4babaae21067417fc17e67dc388c9ec85a8e8a.=
gz:
> No such file or directory
> gunzip: can't stat:
> /var/db/portsnap/files/845df3602aa1742b771872ffbe945ee60e0c834ae1540ba0=
dab02f224cce56f5.gz:
> No such file or directory
> pkg: Unable to open ports directory /usr/ports: No such file or directo=
ry
>=20
> I'm a bit lost. Do I have to remove something for this command to succe=
ed?
Let's look at the command line you're using:
pkg version -vIL=3D
That -I means it's going to try and read the ports INDEX specifically --
ie. /usr/ports/INDEX
Does that file exist? Does it have sensible contents?
Now, given your further comments, it seems something relatively
significant is wrong. There's on obvious (but fairly easy to fix) thing
it might be. Have you run out of space on any of your partitions?
What goes 'df -h' report? Any real partition reporting 100% full is a
problem. (Don't worry about synthetic filesystems like devfs reporting
100% usage: that's normal.) If some filesystem is full, then you need
to either delete stuff, or move it onto a filesystem with more space.
You also seem to be having problems with portsnap(8) -- be aware there
was a problem reported recently. See the thread on freebsd-ports@...
subject 'Latest snapshot' starting with this message:
http://lists.freebsd.org/pipermail/freebsd-ports/2013-July/084833.html
but to summarize several people saw the problem, and the cure was to
delete the files portsnap was using by 'rm -Rf /var/db/portsnap/files'
and then re-run 'portsnap fetch' and 'portsnap extract' -- warning: this
will wipe out everything you have in /usr/ports and download a complete
set of replacements.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matthew@infracaninophile.co.uk
------enig2CWVBTHRKHRKUUEWKTGIE
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/
iEYEARECAAYFAlHhT/QACgkQ8Mjk52CukIxPXQCfXWA8uhFb+t990q/gxINgeoeo
nI8Ani0wtsu/XCUDa0Ou3bg2NocI7w0l
=HLfl
-----END PGP SIGNATURE-----
------enig2CWVBTHRKHRKUUEWKTGIE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51E14FED.9030708>