Date: Sat, 24 Jul 2004 14:36:45 GMT From: Jochen Gensch <incmc@gmx.de> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/69537: Portupgrade cannot be run by cron properly Message-ID: <200407241436.i6OEajfn071193@www.freebsd.org> Resent-Message-ID: <200407241440.i6OEeQpm005472@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 69537 >Category: ports >Synopsis: Portupgrade cannot be run by cron properly >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jul 24 14:40:25 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Jochen Gensch >Release: 4.10 >Organization: >Environment: FreeBSD serverspeedy.da-butze.uga 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Fri Jun 11 16:02:32 CEST 2004 status@serverspeedy.da-butze.uga:/usr/obj/usr/src/sys/APM i386 >Description: When you run a portupgrade by cron, it ends up with messages like "fetch error" or "unknown build error" etc. I have posted a bug report on the portupgrade cron problem some time ago, but the fixes so far just prevent it from deleting the ports being upgraded. >How-To-Repeat: Use a "portupgrade -arR" initialized by cron. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407241436.i6OEajfn071193>