vittorio wrote:
Well, after thourough examination and a word with the network administrator I
learnt that my FreeBSD 5.4 client cannot resolve the name (and the IP too) of
portsnap.daemonology.net because it is behind a firewall and a proxy (which
-by the way - I had already defined via both
Alle 18:27, venerdì 16 settembre 2005, Ashley Moran ha scritto:
> Vittorio wrote:
> > Thanks.
> > I've just compiled the portsnap sources and put the following
> > in /usr/local/etc/portsnap.conf:
> >
> > # Defaults:
> > WORKDIR=/usr/local/portsnap
> > PORTSDIR=/usr/ports
> > KEYPRINT=9b5feee6d69f1
On 2005-09-16 21:49, vittorio <[EMAIL PROTECTED]> wrote:
> Alle 18:21, venerd?? 16 settembre 2005, Colin Percival ha scritto:
> >
> > That key is correct. Try running "portsnap --debug fetch" to work out
> > what the problem is.
>
> Here it is :
>
> vicbsd# portsnap --debug fetch
> Fetching public
Alle 18:21, venerdì 16 settembre 2005, Colin Percival ha scritto:
> Vittorio wrote:
> > # Defaults:
> > WORKDIR=/usr/local/portsnap
> > PORTSDIR=/usr/ports
> > KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
> > URL=http://portsnap.daemonology.net
> >
> > # portsnap fetch
Vittorio wrote:
Thanks.
I've just compiled the portsnap sources and put the following
in /usr/local/etc/portsnap.conf:
# Defaults:
WORKDIR=/usr/local/portsnap
PORTSDIR=/usr/ports
KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
URL=http://portsnap.daemonology.net
BUT
Vittorio wrote:
> # Defaults:
> WORKDIR=/usr/local/portsnap
> PORTSDIR=/usr/ports
> KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
> URL=http://portsnap.daemonology.net
>
> # portsnap fetch
> Fetching
> public key... failed.
>
> What's wrong with the original key in th
fetch
Fetching
public key... failed.
What's wrong with the original key in the
portsnap.conf.sample file?
Thanks again
Vittorio
>Messaggio
originale
>Da: [EMAIL PROTECTED]
>Data: 16-set-2005 5.14 PM
>A: "Vittorio"<[EMAIL PROTECTED]>
>Cc:
Vittorio wrote:
Is there another
alternative way of defining the proxy OR any other way of getting a new
source three to be copied to the server, e.g., by means of a cd burnt
at home?
Have you considered using the sysutils/portsnap port? It's what I use
to keep my servers up-to-date. It
On Fri, Sep 16, 2005 at 03:38:42PM +0100, Vittorio wrote:
> At office I have a freebsd 5.4 server to run postgresql. I'd like to
> update the ports in it from time to time but cvsup doesn't seem to work
> behind our proxy. In fact, in make.conf I have the following two lines:
>
> FETCH_ENV = HTT
At office I have a freebsd 5.4 server to run postgresql. I'd like to
update the ports in it from time to time but cvsup doesn't seem to work
behind our proxy. In fact, in make.conf I have the following two lines:
FETCH_ENV = HTTP_PROXY=http://user:[EMAIL PROTECTED]:8080
FETCH_ENV =
FTP_PROXY=ht
10 matches
Mail list logo
