On Monday 23 June 2008 18:03:34 Odhiambo Washington wrote:
On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell [EMAIL PROTECTED] wrote:
Below is the hunk of ports that continually fail to upgrade due to
problems with patching. i use the command portupgrade -aDkp -m BATCH=yes
Any assistance
On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell [EMAIL PROTECTED] wrote:
Below is the hunk of ports that continually fail to upgrade due to problems
with patching. i use the command portupgrade -aDkp -m BATCH=yes
Any assistance with this greatly appreciated.
Do you have the latest ports tree
On Monday 23 June 2008 18:03:34 Odhiambo Washington wrote:
On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell [EMAIL PROTECTED] wrote:
Below is the hunk of ports that continually fail to upgrade due to
problems with patching. i use the command portupgrade -aDkp -m BATCH=yes
Any assistance
On Monday 23 June 2008 05:03:34 Odhiambo Washington wrote:
On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell [EMAIL PROTECTED] wrote:
Below is the hunk of ports that continually fail to upgrade due to
problems with patching. i use the command portupgrade -aDkp -m BATCH=yes
Any assistance
Warren Liddell writes:
Do you have the latest ports tree (via cvsup or csup)?
I csup'd my ports today and am re-doing it at present.
Can't speak to the other ports, but the current version of ruby
is ruby-1.8.6.111_3,1 which built yesterday for me with zero
problems.
Below is the hunk of ports that continually fail to upgrade due to problems
with patching. i use the command portupgrade -aDkp -m BATCH=yes
Any assistance with this greatly appreciated.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! lang/ruby18 (ruby-1.8.6.111_1,1) (patch
