[ports-i...@freebsd.org: rubygem-dm-types-1.2.1 failed on i386 9]

2012-07-30 Thread Erwin Lansing
build of /usr/ports/databases/rubygem-dm-types ended at Sat Jul 28 23:28:40 UTC 2012 - End forwarded message - -- Erwin Lansinghttp://droso.dk er...@freebsd.orghttp:// www.FreeBSD.org __

[ports-i...@freebsd.org: rubygem-dm-serializer-1.2.1 failed on i386 9]

2012-07-30 Thread Erwin Lansing
ies: dm-serializer requires multi_json (~> 1.0.3), json (~> 1.6.1), json_pure (~> 1.6.1) *** Error code 1 Stop in /a/ports/databases/rubygem-dm-serializer. build of /usr/ports/databases/rubygem-dm-seria

[ports-i...@freebsd.org: rubygem-couchrest-1.1.2 failed on i386 9]

2012-07-30 Thread Erwin Lansing
Unable to resolve dependencies: couchrest requires multi_json (~> 1.0.0) *** Error code 1 Stop in /a/ports/databases/rubygem-couchrest. build of /usr/ports/databases/rubygem-couchrest ended at Fri

[ports-i...@freebsd.org: ruby18-password-0.5.3_4 failed on i386 8]

2012-04-04 Thread Erwin Lansing
cracklib dictionary on this system *** Error code 1 Stop in /a/ports/security/ruby-password. build of /usr/ports/security/ruby-password ended at Wed Apr 4 02:46:26 UTC 2012 - End forwarded message - -- Erwin Lansing

[ports-i...@freebsd.org: ruby18-lv-0.12 failed on i386 9]

2012-02-23 Thread Erwin Lansing
jects to Makefile.rej Hmm... Ignoring the trailing garbage. done *** Error code 1 Stop in /a/ports/converters/ruby-lv. build of /usr/ports/converters/ruby-lv ended at Wed Feb 22 15:02:49 UTC 2012 - End forwarded message - --

Ports with duplicate LATEST_LINKS

2011-12-19 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Ports with duplicate LATEST_LINKS

2011-12-18 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Ports with duplicate LATEST_LINKS

2011-12-17 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Ports with duplicate LATEST_LINKS

2011-06-27 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Ports with duplicate LATEST_LINKS

2011-06-26 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Ports with duplicate LATEST_LINKS

2011-06-25 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Ports with duplicate LATEST_LINKS

2011-06-24 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Re: [ports-i...@freebsd.org: ruby18-refe-0.8.0 failed on i386 8]

2010-12-24 Thread Erwin Lansing
On Fri, Dec 24, 2010 at 07:09:52AM +, Philip M. Gollucci wrote: > On 12/23/10 13:46, Erwin Lansing wrote: > > > > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.8.20101223122716/ruby18-refe-0.8.0.log > > > > >

[ports-i...@freebsd.org: ruby18-refe-0.8.0 failed on i386 8]

2010-12-23 Thread Erwin Lansing
/ruby and try again. *** Error code 1 Stop in /a/ports/japanese/ruby-refe. build of /usr/ports/japanese/ruby-refe ended at Thu Dec 23 13:43:46 UTC 2010 !DSPAM:4d135217315012046617956! - End forw

[ports-i...@freebsd.org: rubygem-prawn-0.6.3 failed on i386 9]

2010-12-11 Thread Erwin Lansing
t;=0.8.4. *** Error code 1 Stop in /a/ports/print/rubygem-prawn. build of /usr/ports/print/rubygem-prawn ended at Sat Dec 11 09:15:15 UTC 2010 !DSPAM:4d034129315011036810799! - End forwarded message - -- Erwin Lansing http://dr