Making port check-plist errors

I am running into errors when trying to register the installation files. The Makefile is pretty barebones, it looks like this so far: PORTNAME=epson-inkjet-printer-201401w PORTVERSION=201401w PORTREVISION=1 PORTEPOCH=0 CATEGORIES=print MASTER_SITES=

Re: Update failure E000022 after upgrade to subversion 1.9.6

Hi duglas@ I had the same problem. I completely solved it by rebuilding the dependency chain of devel/subversion: portmaster serf-1.3.9_1 expat-2.2.1 gettext-runtime-0.19.8.1_1 apr-1.5.2.1.5.4_2 sqlite3-3.19.3_1 subversion-1.9.6 Probably, only one of them is the culprit, but I haven't

Re: Writing a port make deinstall

On 7/12/17 12:38 PM, blubee blubeeme wrote: > Hello FreeBSD ports team > > I am writing a Makefile to install a port > > I've written this much so far > > PORTNAME= epson-inkjet-printer-201401w > PORTVERSION= 201401w > PORTREVISION= 1 > PORTEPOCH= 0 > CATEGORIES= print >

Re: Writing a port make deinstall

12.07.2017 9:38, blubee blubeeme wrote: > How do I properly write this Makefile so deinstall works as expected? Just add these files to pkg-plist and they are removed automatically. ___ freebsd-ports@freebsd.org mailing list

Writing a port make deinstall

Hello FreeBSD ports team I am writing a Makefile to install a port I've written this much so far PORTNAME= epson-inkjet-printer-201401w PORTVERSION= 201401w PORTREVISION= 1 PORTEPOCH= 0 CATEGORIES= print MASTER_SITES=

FreeBSD Port: freeze-2.5_2 - license dialog

Would it be possible to move the license dialog to a standard option so batch portmaster (etc) will get the license confirmation with the rest of the options updates rather than during the (often unattended) build phase? -David ___

Re: [j...@apache.org: [ANNOUNCEMENT] Apache HTTP Server 2.4.27 Released]

On Tue, Jul 11, 2017 at 06:11:45PM +0200, Herbert J. Skuhra wrote: > The Doctor skrev: > > > > Heads up Team FreeBSD . > > 1. Patch missing? > 2. Maintainer of apache2x is apache@ and it's already discussed on the > freebsd-apache ML: >

Re: Update failure E000022 after upgrade to subversion 1.9.6

On 11.07.2017 17:17, duglas wrote: Hi, After upgrading to subversion 1.9.6 My latest svn update attempts result in the following. svn update /usr/ports Updating 'ports': svn: E22: Error converting entry in directory '/usr/ports' to UTF-8 svn: E22: Can't convert string from native

Re: [j...@apache.org: [ANNOUNCEMENT] Apache HTTP Server 2.4.27 Released]

The Doctor skrev: > > Heads up Team FreeBSD . 1. Patch missing? 2. Maintainer of apache2x is apache@ and it's already discussed on the freebsd-apache ML: https://lists.freebsd.org/pipermail/freebsd-apache/2017-July/thread.html 3. Can you stop this? We already have portscout for this. -- Herbert

Re: firefox is pretty useless ...

On 5-7-2017 08:07, DTD wrote: > if you use xfce. By definition it is not a problem that: > > 1) install a new copy of FreeBSD 10.3 > 2) pkg install xorg > 3) pkg install xfce > 4) pkg install firefox > > installs a firefox package that does not run. The project seems to do > a bit > better

Re: firefox is pretty useless ...

On Tue, Jul 11, 2017 at 09:45:10AM -0500, Bob Willcox wrote: > On Wed, Jul 05, 2017 at 02:07:29AM -0400, DTD wrote: > > if you use xfce. By definition it is not a problem that: > > > >1) install a new copy of FreeBSD 10.3 > >2) pkg install xorg > >3) pkg install xfce > >4) pkg

Re: firefox is pretty useless ...

On Wed, Jul 05, 2017 at 02:07:29AM -0400, DTD wrote: > if you use xfce. By definition it is not a problem that: > >1) install a new copy of FreeBSD 10.3 >2) pkg install xorg >3) pkg install xfce >4) pkg install firefox > > installs a firefox package that does not run. The project

[j...@apache.org: [ANNOUNCEMENT] Apache HTTP Server 2.4.27 Released]

Heads up Team FreeBSD . - Forwarded message from Jim Jagielski - Date: Tue, 11 Jul 2017 09:06:14 -0400 From: Jim Jagielski To: annou...@httpd.apache.org Subject: [ANNOUNCEMENT] Apache HTTP Server 2.4.27 Released X-Mailer: Apple Mail (2.3273)

Re: make install for print/texinfo fails on -CURRENT

Hmm, I just tried running synth on my test system again (this is the system that I successfully built and install texinfo on just a bit ago) and synth still fails with the same build errors as before. I'm not all that familiar with synth, but it appears that it may be working with some old stuff.

Re: make install for print/texinfo fails on -CURRENT

On Tue, Jul 11, 2017 at 03:26:30PM +0200, Herbert J. Skuhra wrote: > > On 11 July 2017 at 15:18 Bob Willcox wrote: > > > > > > On Tue, Jul 11, 2017 at 03:12:12PM +0200, Herbert J. Skuhra wrote: > > > > On 11 July 2017 at 14:51 Bob Willcox wrote: > > > > > > >

Re: make install for print/texinfo fails on -CURRENT

> On 11 July 2017 at 15:18 Bob Willcox wrote: > > > On Tue, Jul 11, 2017 at 03:12:12PM +0200, Herbert J. Skuhra wrote: > > > On 11 July 2017 at 14:51 Bob Willcox wrote: > > > > > > > > > On Tue, Jul 11, 2017 at 01:13:33PM +0200, Herbert J. Skuhra wrote: > >

Re: make install for print/texinfo fails on -CURRENT

On Tue, Jul 11, 2017 at 03:12:12PM +0200, Herbert J. Skuhra wrote: > > On 11 July 2017 at 14:51 Bob Willcox wrote: > > > > > > On Tue, Jul 11, 2017 at 01:13:33PM +0200, Herbert J. Skuhra wrote: > > > > On 10 July 2017 at 22:59 Bob Willcox wrote: > > > > > > >

Re: make install for print/texinfo fails on -CURRENT

> On 11 July 2017 at 14:51 Bob Willcox wrote: > > > On Tue, Jul 11, 2017 at 01:13:33PM +0200, Herbert J. Skuhra wrote: > > > On 10 July 2017 at 22:59 Bob Willcox wrote: > > > > > > > > > On Mon, Jul 10, 2017 at 10:21:21PM +0200, Herbert J. Skuhra wrote: > >

Re: make install for print/texinfo fails on -CURRENT

On Tue, Jul 11, 2017 at 01:13:33PM +0200, Herbert J. Skuhra wrote: > > On 10 July 2017 at 22:59 Bob Willcox wrote: > > > > > > On Mon, Jul 10, 2017 at 10:21:21PM +0200, Herbert J. Skuhra wrote: > > > Bob Willcox skrev: > > > > > > > > On Mon, Jul 10, 2017 at 09:49:06PM +0200,

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,