Re: Update net/tintin++ to 2.00.9

2014-01-01 Thread Brian Callahan
On 1/1/2014 11:35 PM, Ted Roby wrote: This diff was run against -current. It updates net/tintin++ to 2.00.9. Any reason not to have updated to 2.01.0? MASTER_SITES now grabs from MASTER_SITE_SOURCEFORGE. Licensing has been changed to GPLv2. Pedantic nit: the license is actually GPLv2+ WA

Update net/tintin++ to 2.00.9

2014-01-01 Thread Ted Roby
This diff was run against -current. It updates net/tintin++ to 2.00.9. MASTER_SITES now grabs from MASTER_SITE_SOURCEFORGE. Licensing has been changed to GPLv2. WANTLIB has been updated to reflect pcre dependency. Source files are modified as follows: Makefile.in: include ${LOCALBASE}/include pa

Re: Drop USE_GROFF from Makefile.template

2014-01-01 Thread Ingo Schwarze
Hi, Jérémie Courrèges-Anglas wrote on Thu, Jan 02, 2014 at 12:42:51AM +0100: > Rafael Sadowski writes: >> "Drop USE_GROFF since groff and mandoc produce identical output." > I don't think this is a good idea. + 1 > Lots of ports still need USE_GROFF, and having this in the template > reminds

Re: Drop USE_GROFF from Makefile.template

2014-01-01 Thread Brad Smith
On 01/01/14 6:19 PM, Rafael Sadowski wrote: "Drop USE_GROFF since groff and mandoc produce identical output." The quoted comment is without context and isn't always true yet. cheers Rafael Index: Makefile.template === RCS file:

Re: Drop USE_GROFF from Makefile.template

2014-01-01 Thread Jérémie Courrèges-Anglas
Rafael Sadowski writes: > "Drop USE_GROFF since groff and mandoc produce identical output." > > cheers Rafael I don't think this is a good idea. Lots of ports still need USE_GROFF, and having this in the template reminds people to look at the groff and mandoc produced output. shannon ~$ sqlite

Drop USE_GROFF from Makefile.template

2014-01-01 Thread Rafael Sadowski
"Drop USE_GROFF since groff and mandoc produce identical output." cheers Rafael Index: Makefile.template === RCS file: /cvs/ports/infrastructure/templates/Makefile.template,v retrieving revision 1.68 diff -u -p -r1.68 Makefile.templa

Re: i386 bulk build failures

2014-01-01 Thread Marc Espie
On Wed, Jan 01, 2014 at 09:38:48PM +, Stuart Henderson wrote: > Quick summary of the failures in the last i386 bulk build. > Java ports are now broken on i386 as a result of JDK problems. > > www/chromium,proprietary: 'chrome/common/extensions/api/runtime.h' file not > found > - this is possi

Re: JDK 1.6 Broken

2014-01-01 Thread Scott Vanderbilt
On 1/1/2014 1:21 PM, Stuart Henderson wrote: If anyone is able to help track down the timeframe this got broken (or even pin it to a particular commit in base), that would be extremely helpful... I was previously running a snapshot from Dec. 7 that did not exhibit the error. Sorry I can't be

i386 bulk build failures

2014-01-01 Thread Stuart Henderson
Quick summary of the failures in the last i386 bulk build. Java ports are now broken on i386 as a result of JDK problems. www/chromium,proprietary: 'chrome/common/extensions/api/runtime.h' file not found - this is possibly the missing interdependency that espie just fixed. Following are PIE-rela

Re: JDK 1.6 Broken

2014-01-01 Thread Stuart Henderson
On 2014/01/01 10:11, Scott Vanderbilt wrote: > On 1/1/2014 10:00 AM, Ian Darwin wrote: > > >Given that Java 6 has been EOL'd by Oracle for almost a year (Feb 2013, > >as announced in Feb 2011), and it's on an operating system they > >don't even know about, your bug report will most likely be ignor

Re: Help needed - a WIP port for ocrfeeder

2014-01-01 Thread Jiri B
On Wed, Jan 01, 2014 at 03:48:10PM -0500, Jiri B wrote: > Hi all, > > I've thought it would be not so difficult to make ocrfeeder > (port[1]) running on OpenBSD but... Well, it core dumps. WIP ocrfeeder port and its (new) deps in attachment. jirib ocrfeeder.tar.gz Description: application/tar-

Help needed - a WIP port for ocrfeeder

2014-01-01 Thread Jiri B
Hi all, I've thought it would be not so difficult to make ocrfeeder (port[1]) running on OpenBSD but... Well, it core dumps. I would appreciate any help, as it seems to be one of few OSS OCR application available. I submitted a BZ[2] for upstream but I'm not even sure if it is an OpenBSD issue o

Re: UPDATE: fonts/dina-fonts

2014-01-01 Thread Rafael Sadowski
On Tue Dec 31, 2013 at 07:26:28PM +0100, Tobias Ulmer wrote: > On Sun, Dec 29, 2013 at 10:24:39PM +0100, Rafael Sadowski wrote: > > On Sun Dec 29, 2013 at 09:16:10PM +, Mikolaj Kucharski wrote: > > > On Sun, Dec 29, 2013 at 06:33:27PM +0100, Rafael Sadowski wrote: > > > > +SHA256 (Dina.zip) = H

Re: JDK 1.6 Broken

2014-01-01 Thread Scott Vanderbilt
On 1/1/2014 10:00 AM, Ian Darwin wrote: Given that Java 6 has been EOL'd by Oracle for almost a year (Feb 2013, as announced in Feb 2011), and it's on an operating system they don't even know about, your bug report will most likely be ignored. Sorry you wasted time there. Given the situation wi

Re: JDK 1.6 Broken

2014-01-01 Thread Ian Darwin
> While I have no doubt the port may have been broken for some time, it > was working reliably in my particular use case as of the Dec. 7 > snapshot. (I'm running Apache Solr 4.6.) It was only after I updated to > the Dec. 28 snapshot that the breakage manifested itself. > > Following up on you

Re: JDK 1.6 Broken

2014-01-01 Thread Scott Vanderbilt
On 1/1/2014 6:41 AM, Marc Espie wrote: On Tue, Dec 31, 2013 at 12:14:26PM -0800, Scott Vanderbilt wrote: So I see that the jdk-1.6 port has been marked as broken, unfortunately, only after upgrading to the latest snapshot (i386). Might anyone have any idea when this will be working again? No

[RFC] graphics/pysane

2014-01-01 Thread Jiri B
Hi, could you please: * have a look at port as itself * (if you have a scanner) to test it? pysane is needed as deps for ocrfeeder, which I'm working on. We don't have any OCR gui in our ports :( jirib pysane.tar.gz Description: application/tar-gz

Re: JDK 1.6 Broken

2014-01-01 Thread Marc Espie
On Tue, Dec 31, 2013 at 12:14:26PM -0800, Scott Vanderbilt wrote: > So I see that the jdk-1.6 port has been marked as broken, > unfortunately, only after upgrading to the latest snapshot (i386). > > Might anyone have any idea when this will be working again? No. It's actually been broken for a wh