Hello, n.
You wrote 17 октября 2011 г., 12:51:28:
> might the reason be the following?
> Every night I do (from cron), a # portsnap fetch
> but not portsnap update, this I do just before my weekly #
> portupgrade -yaRrpb
>
> I just did
> # portsnap update
> This updated files in /usr/ports/de
Hi,
might the reason be the following?
Every night I do (from cron), a # portsnap fetch
but not portsnap update, this I do just before my weekly # portupgrade
-yaRrpb
I just did
# portsnap update
This updated files in /usr/ports/devel/subversion16/files (and also in
/usr/ports/devel/subversion/f
Hello, n.
You wrote 17 октября 2011 г., 11:55:08:
> There was a message in /usr/ports/UPDATING about subversion 1.6.x
> and 1.7.0
> my daily
> # pkg_version -vIL=
> reports
> subversion-1.6.17_2 < needs updating (index has
> 1.7.0_1)
> I didn't use subversion-freebsd in the
There was a message in /usr/ports/UPDATING about subversion 1.6.x and 1.7.0
my daily
# pkg_version -vIL=
reports
subversion-1.6.17_2 < needs updating (index has 1.7.0_1)
I didn't use subversion-freebsd in the past and I want to stick to version
1.6
So from /usr/ports/UPDATING, I b