On Tue, Nov 2, 2010 at 4:08 AM, Leslie Jensen les...@eskk.nu wrote:
Hello list.
I have the following in /etc/crontab
@reboot root portsnap -I cron update /root/bin/cv_portsnap_cron
pkg_version -vIL=
I don't see where you are doing a portsnap fetch first. If you haven't
done a fetch,
On Tue, Nov 2, 2010 at 5:57 AM, Leslie Jensen les...@eskk.nu wrote:
Lystic Emsen skrev 2010-11-02 11:53:
On Tue, Nov 2, 2010 at 4:08 AM, Leslie Jensenles...@eskk.nu wrote:
Hello list.
I have the following in /etc/crontab
@reboot root portsnap -I cron update /root/bin
On Tue, Nov 2, 2010 at 6:44 AM, Leslie Jensen les...@eskk.nu wrote:
On 2010-11-02 12:38, Vincent Hoffman wrote:
On 02/11/2010 11:34, Jerry wrote:
Since portsnap' has been failing on my system, I tried a different
approach and decided to rebuild the port entirely rather than just
download
From the machine you run portsnap on, try this:
nslookup portsnap2.freebsd.org
Let me know if that works. It may be a DNS error.
On Mon, Nov 1, 2010 at 3:10 PM, Jerry freebsd.u...@seibercom.net wrote:
I have been having problems with 'portsnap' for two days now. It
continually emits error
I just upgrade my php5 port to php5.3 and ran into a similar problem with
portupgrade. However, I just unregistered php5-spl, because its no longer
necessary. I believe php5-spl and php5-pcre are now integrated into PHP-5.3
by default.
I also ran into a couple of other problems. These notes
