Re: Is staging a port really this simple?

2014-05-25 Thread John Marino
On 5/25/2014 07:04, Perry Hutchison wrote: Some months ago, Baptiste Daroussin b...@freebsd.org wrote: ... if you need any help staging your ports I can provide reviews. I have a couple of ports that need staging support added, and I've finally managed to find time to look into it. Having

Re: Is staging a port really this simple?

2014-05-25 Thread Zsolt Udvari
2014-05-25 7:04 GMT+02:00 Perry Hutchison per...@pluto.rain.com: post-install: - @[ -f ${PREFIX}/etc/diskcheckd.conf ] \ - || ${CP} -p ${PREFIX}/etc/diskcheckd.conf.sample \ - ${PREFIX}/etc/diskcheckd.conf + @[ -f

Re: Is staging a port really this simple?

2014-05-25 Thread John Marino
On 5/25/2014 09:09, Zsolt Udvari wrote: 2014-05-25 7:04 GMT+02:00 Perry Hutchison per...@pluto.rain.com: post-install: - @[ -f ${PREFIX}/etc/diskcheckd.conf ] \ - || ${CP} -p ${PREFIX}/etc/diskcheckd.conf.sample \ - ${PREFIX}/etc/diskcheckd.conf +

Re: Is staging a port really this simple?

2014-05-25 Thread Zsolt Udvari
2014-05-25 9:12 GMT+02:00 John Marino freebsd.cont...@marino.st: no, the @sample keyword in pkg-plist does that (replacing other lines there). pkg doesn't do this by itself, it needs to be told. Yes, this is more accurate. ___

Re: Is staging a port really this simple?

2014-05-25 Thread Fbsd8
Perry Hutchison wrote: Some months ago, Baptiste Daroussin b...@freebsd.org wrote: ... if you need any help staging your ports I can provide reviews. I have a couple of ports that need staging support added, and I've finally managed to find time to look into it. Having read such

Re: Is staging a port really this simple?

2014-05-25 Thread Michael Gmelin
On Sun, 25 May 2014 04:14:42 -0400 Fbsd8 fb...@a1poweruser.com wrote: Perry Hutchison wrote: Some months ago, Baptiste Daroussin b...@freebsd.org wrote: ... if you need any help staging your ports I can provide reviews. I have a couple of ports that need staging support added, and

[QAT] 355146: 4x leftovers

2014-05-25 Thread Ports-QAT
- Add a patch to fix the result of xmlRoot because of changing the layout in May 2014 - Specify LICENSE BSD - BSD3CLAUSE - Build ID: 20140525085600-64898 Job owner: t...@freebsd.org Buildtime: 41

FreeBSD ports you maintain which are out of date

2014-05-25 Thread portscout
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,

Re: Net-SNMP conflict

2014-05-25 Thread Michael Gmelin
On Tue, 20 May 2014 19:12:36 +0100 Matthew Seaman matt...@freebsd.org wrote: On 20/05/2014 18:34, Richard Kuhns wrote: So doesn't that mean that the net-snmp port is doing things wrong? If pkg *isn't* installed it's pretty safe to say that net-snmpd is not going to be able to use pkg(8) to

stagify mail/up-imapproxy

2014-05-25 Thread freebsd
Submitter-Id: free...@nagilum.org Originator:free...@nagilum.org Organization: Confidential: no Synopsis: stagify mail/up-imapproxy Severity: non-critical Priority: low Category: ports Class: sw-bug Release: FreeBSD 9.2-STABLE i386 Environment: System:

Re: postfix-policyd-weight broken with p5-Net-DNS 0.75

2014-05-25 Thread Herbert J. Skuhra
On Sat, 24 May 2014 10:03:23 +0200 olli hauer wrote: On 2014-05-23 23:57, Herbert J. Skuhra wrote: Hi, after updating p5-Net-DNS from version 0.74 to 0.75 postfix-policyd-weight (0.1.15.2) stopped working. I get the below error on two systems: May 23 13:31:35 mx

autoplist

2014-05-25 Thread Helmut Schneider
Hi, I'm trying to replace my pkg-plist (www/typo3*, 12k lines) with autoplist. do-install: ${MKDIR} ${STAGEDIR}${PREFIX}/${TYPO3WWW}/${PORTNAME}-${TYPO3RELEASE} ${CP} -R ${WRKDIR}/${TYPO3SRC} ${STAGEDIR}${PREFIX}/${TYPO3WWW}/ ${LN} -fs ../${TYPO3SRC}

Re: autoplist

2014-05-25 Thread Helmut Schneider
Helmut Schneider wrote: @${FIND} ${STAGEDIR}${PREFIX}/${TYPO3WWW} \( -type f -or -type l \) | \ ${SED} -ne 's#^${WRKSRC}#${TYPO3WWW}#p' | ${SORT} ${TMPPLIST} @${FIND} ${STAGEDIR}${PREFIX}/${TYPO3WWW} -type d | \ ${SED} -ne

mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Milan Obuch
Hi, pkg-fallout-buil...@freebsd.org sends me every other day mails about failing mail/courier build for both 10.0 and 11.0 FreeBSD versions. There is some incompatibility with GCC 4.7, which is used to build mail/courier on systems with system compiler switched to clang. It works, however, with

docbook error persisting

2014-05-25 Thread Jeffrey Bouquet via freebsd-ports
I found a PR which was closed with the same error (Its originator had fixed it by reinstalling all ports.) .. This persists in dbus, po4a, etc and I reinstalled exactly as UPDATING all docbook, as well as a fix someone recently found for it, to the extent it was

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Kurt Jaeger
Hi! In the mean time, could someone review PR ports/190209 which addresses this issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=190209)? It is really simple and should solve package builder failures for [REL - 10i386-default], [REL - 10amd64-default], [REL - 10i386-quarterly], [REL -

Review Request, update clementine-player 1.2.3

2014-05-25 Thread Sean Bruno
Upstream has moved distfiles to github. New depend on libechonest 2 patches accepted upstream so they're dropped 1 new patch generated and added http://people.freebsd.org/~sbruno/clementine_1.2.3.txt sean ___ freebsd-ports@freebsd.org mailing list

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Milan Obuch
On Sun, 25 May 2014 22:10:08 +0200 Kurt Jaeger p...@opsec.eu wrote: Hi! In the mean time, could someone review PR ports/190209 which addresses this issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=190209)? It is really simple and should solve package builder failures for [REL -

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Kurt Jaeger
Hi! In the mean time, could someone review PR ports/190209 which addresses this issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=190209)? It is really simple and should solve package builder failures for [REL - 10i386-default], [REL - 10amd64-default], [REL - 10i386-quarterly],

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Milan Obuch
On Sun, 25 May 2014 22:43:14 +0200 Kurt Jaeger li...@opsec.eu wrote: Hi! In the mean time, could someone review PR ports/190209 which addresses this issue (http://www.freebsd.org/cgi/query-pr.cgi?pr=190209)? It is really simple and should solve package builder failures for

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Kurt Jaeger
Hi! Do you also plan to upgrade to 0.73. ? With 0.65 we're badly behind the times, aren't we ? Yes, this upgrade is long due, but it has some issues too. What issues does 0.73.1 have ? Is there a list somewhere ? Frankly, courier looses more and more marketshare, as can be seen on

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Milan Obuch
On Sun, 25 May 2014 23:19:55 +0200 Kurt Jaeger li...@opsec.eu wrote: Hi! Do you also plan to upgrade to 0.73. ? With 0.65 we're badly behind the times, aren't we ? Yes, this upgrade is long due, but it has some issues too. What issues does 0.73.1 have ? Is there a list somewhere ?

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Matthias Andree
Am 25.05.2014 23:19, schrieb Kurt Jaeger: Hi! Do you also plan to upgrade to 0.73. ? With 0.65 we're badly behind the times, aren't we ? Yes, this upgrade is long due, but it has some issues too. What issues does 0.73.1 have ? Is there a list somewhere ? Frankly, courier looses more

Re: mail/courier build failures on newer FreeBSD versions

2014-05-25 Thread Milan Obuch
On Mon, 26 May 2014 03:29:55 +0200 Matthias Andree matthias.and...@gmx.de wrote: [ snip ] I'd suggest to let Milan work on the port and tell him the constraints - for instance, that now staging needs to be addressed first and then the build-on-10 issue. OK, I already began work on staging,