Re: fix for security/openvpn-auth-ldap (PR: ports/175692)
> On Jan 2, 2014, at 1:15, Matthias Andree wrote: > > Am 01.01.2014 23:58, schrieb Nick Barkas: > >> security/openvpn-auth-ldap has failed to build for some time due to a >> minor change in the layout of the openvpn sources. I prepared a fix >> for this but haven’t yet found someone to commit it for me, and also >> made it so the port can build on 9.x and later, along with a couple >> of other small fixes. I’d be grateful if a committer can commit the >> attached patch. > > Nick, > > a happy new year. I have committed the patch with these changes - I > hope you do not mind them: > > - strip the .so file in post-install > - convert to staging > - also convert NOPORTEXAMPLES to optionsNG > > Please consider if you really need gcc, or if clang might work, too, and > if so, send a followup patch to support clang. Thanks! gcc is needed, mostly for its included objective C runtime. I tried for awhile to get openvpn-auth-ldap to compile with clang and link with lang/libobjc2, but was unsuccessful. > Best regards, > Matthias ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: fix for security/openvpn-auth-ldap (PR: ports/175692)
Am 02.01.2014 09:27, schrieb Nick Barkas: > >> On Jan 2, 2014, at 1:15, Matthias Andree wrote: >> >> Am 01.01.2014 23:58, schrieb Nick Barkas: >> >>> security/openvpn-auth-ldap has failed to build for some time due to a >>> minor change in the layout of the openvpn sources. I prepared a fix >>> for this but haven’t yet found someone to commit it for me, and also >>> made it so the port can build on 9.x and later, along with a couple >>> of other small fixes. I’d be grateful if a committer can commit the >>> attached patch. >> >> Nick, >> >> a happy new year. I have committed the patch with these changes - I >> hope you do not mind them: >> >> - strip the .so file in post-install >> - convert to staging >> - also convert NOPORTEXAMPLES to optionsNG >> >> Please consider if you really need gcc, or if clang might work, too, and >> if so, send a followup patch to support clang. > > Thanks! gcc is needed, mostly for its included objective C runtime. I tried > for awhile to get openvpn-auth-ldap to compile with clang and link with > lang/libobjc2, but was unsuccessful. Thanks, Nick. I have added to your comment in the port's Makefile so other people find this information easily. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: www/rubygem-passenger: link error on 10.0-PRERELEASE r259862M
Hi, I would like to confirm that issue: I've ecountered it while trying to compile rubygem-passenger-4.0.30 from ports on FreeBSD 10.0-RC3 amd64, fresh ISO installation. Is there anything happening about that? Do we know if its CLANG issue of Passenger one, and should be reported to them? Regards, S. On Thu, Dec 26, 2013 at 7:57 AM, Jiansong Liu wrote: > Hi, > > I try to re-install the www/rubygem-passenger by the portmaster tool after > I upgraded to 10.0, and got error like below: > > It produced 4 warnings at first: > > c++ -Iext -D_REENTRANT -I/usr/local/include -Wall -Wextra > -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings > -Wno-long-long -Wno-missing-field-initializers > -Wno-ambiguous-member-template -fcommon -fvisibility=hidden > -DVISIBILITY_ATTRIBUTE_SUPPORTED -g -DHAVE_ACCEPT4 -DHAS_SFENCE > -DHAS_LFENCE -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -std=gnu++11 > -DHAS_UNORDERED_MAP -o buildout/common/libboost_oxt/boost/thread.o -c > ext/boost/libs/thread/src/pthread/thread.cpp > In file included from ext/boost/libs/thread/src/pthread/thread.cpp:30: > ext/boost/libs/thread/src/pthread/./timeconv.inl:51:13: warning: unused > function 'to_time' [-Wunused-function] > inline void to_time(int milliseconds, timespec& ts) > ^ > ext/boost/libs/thread/src/pthread/./timeconv.inl:71:13: warning: unused > function 'to_timespec_duration' [-Wunused-function] > inline void to_timespec_duration(const boost::xtime& xt, timespec& ts) > ^ > ext/boost/libs/thread/src/pthread/./timeconv.inl:104:13: warning: unused > function 'to_duration' [-Wunused-function] > inline void to_duration(boost::xtime xt, int& milliseconds) > ^ > ext/boost/libs/thread/src/pthread/./timeconv.inl:126:13: warning: unused > function 'to_microduration' [-Wunused-function] > inline void to_microduration(boost::xtime xt, int& microseconds) > ^ > 4 warnings generated. > > > Then ran into a link error: > > c++ -o buildout/agents/PassengerHelperAgent.o -Iext -Iext/common > -I/usr/local/include -Wno-ambiguous-member-template -I/usr/local/include > -D_REENTRANT -I/usr/local/include -Wall -Wextra -Wno-unused-parameter > -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long > -Wno-missing-field-initializers -Wno-ambiguous-member-template -fcommon > -fvisibility=hidden -DVISIBILITY_ATTRIBUTE_SUPPORTED -g -DHAVE_ACCEPT4 > -DHAS_SFENCE -DHAS_LFENCE -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS > -std=gnu++11 -DHAS_UNORDERED_MAP -c ext/common/agents/HelperAgent/Main.cpp > c++ buildout/agents/PassengerHelperAgent.o -o > buildout/agents/PassengerHelperAgent > buildout/common/libpassenger_common/Logging.o > buildout/common/libpassenger_common/Exceptions.o > buildout/common/libpassenger_common/Utils/SystemTime.o > buildout/common/libpassenger_common/Utils/StrIntUtils.o > buildout/common/libpassenger_common/Utils/IOUtils.o > buildout/common/libpassenger_common/Utils.o > buildout/common/libpassenger_common/Utils/Base64.o > buildout/common/libpassenger_common/Utils/CachedFileStat.o > buildout/common/libpassenger_common/Utils/LargeFiles.o > buildout/common/libpassenger_common/ApplicationPool2/Implementation.o > buildout/common/libpassenger_common/ApplicationPool2/AppTypes.o > buildout/common/libpassenger_common/AgentsBase.o > buildout/common/libpassenger_common/Utils/MD5.o > buildout/common/libpassenger_common/Utils/fib.o > buildout/common/libpassenger_common/Utils/jsoncpp.o > buildout/common/libboost_oxt.a -L/usr/local/lib -lev -L/usr/local/lib > -leio -pthread -lrt > buildout/agents/PassengerHelperAgent.o: In function > `_ZNK5boost13function_base6targetIDnEEPKT_v': > > /usr/local/lib/ruby/gems/2.0/gems/passenger-4.0.29/ext/boost/function/function_base.hpp:670: > undefined reference to `_ZTIDn' > c++: error: linker command failed with exit code 1 (use -v to see > invocation) > rake aborted! > Command failed with status (1): [c++ buildout/agents/PassengerHelperAgent.o > -o buildout/agents/PassengerHelperAgent > buildout/common/libpassenger_common/Logging.o > buildout/common/libpassenger_common/Exceptions.o > buildout/common/libpassenger_common/Utils/SystemTime.o > buildout/common/libpassenger_common/Utils/StrIntUtils.o > buildout/common/libpassenger_common/Utils/IOUtils.o > buildout/common/libpassenger_common/Utils.o > buildout/common/libpassenger_common/Utils/Base64.o > buildout/common/libpassenger_common/Utils/CachedFileStat.o > buildout/common/libpassenger_common/Utils/LargeFiles.o > buildout/common/libpassenger_common/ApplicationPool2/Implementation.o > buildout/common/libpassenger_common/ApplicationPool2/AppTypes.o > buildout/common/libpassenger_common/AgentsBase.o > buildout/common/libpassenger_common/Utils/MD5.o > buildout/common/libpassenger_common/Utils/fib.o > buildout/common/libpassenger_common/Utils/jsoncpp.o > buildout/common/libboost_oxt.a -L/usr/local/lib -lev -L/usr/local/lib > -leio -pthread -lrt ] > > Tasks: TOP => nginx => nginx_without_native_support => >
Re: www/rubygem-passenger: link error on 10.0-PRERELEASE r259862M
I've just made a test and updated my port to the latest version of passenger, that is 4.0.31 and it now builds fine and starts fine compiled as Nginx module as well, so I've made a patch to the port and submitted it here: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/185416 Regards, S. On Thu, Jan 2, 2014 at 11:03 AM, Big Lebowski wrote: > Hi, > > I would like to confirm that issue: I've ecountered it while trying to > compile rubygem-passenger-4.0.30 from ports on FreeBSD 10.0-RC3 amd64, > fresh ISO installation. > > Is there anything happening about that? Do we know if its CLANG issue of > Passenger one, and should be reported to them? > > Regards, > S. > > > On Thu, Dec 26, 2013 at 7:57 AM, Jiansong Liu wrote: > >> Hi, >> >> I try to re-install the www/rubygem-passenger by the portmaster tool after >> I upgraded to 10.0, and got error like below: >> >> It produced 4 warnings at first: >> >> c++ -Iext -D_REENTRANT -I/usr/local/include -Wall -Wextra >> -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings >> -Wno-long-long -Wno-missing-field-initializers >> -Wno-ambiguous-member-template -fcommon -fvisibility=hidden >> -DVISIBILITY_ATTRIBUTE_SUPPORTED -g -DHAVE_ACCEPT4 -DHAS_SFENCE >> -DHAS_LFENCE -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -std=gnu++11 >> -DHAS_UNORDERED_MAP -o buildout/common/libboost_oxt/boost/thread.o -c >> ext/boost/libs/thread/src/pthread/thread.cpp >> In file included from ext/boost/libs/thread/src/pthread/thread.cpp:30: >> ext/boost/libs/thread/src/pthread/./timeconv.inl:51:13: warning: unused >> function 'to_time' [-Wunused-function] >> inline void to_time(int milliseconds, timespec& ts) >> ^ >> ext/boost/libs/thread/src/pthread/./timeconv.inl:71:13: warning: unused >> function 'to_timespec_duration' [-Wunused-function] >> inline void to_timespec_duration(const boost::xtime& xt, timespec& ts) >> ^ >> ext/boost/libs/thread/src/pthread/./timeconv.inl:104:13: warning: unused >> function 'to_duration' [-Wunused-function] >> inline void to_duration(boost::xtime xt, int& milliseconds) >> ^ >> ext/boost/libs/thread/src/pthread/./timeconv.inl:126:13: warning: unused >> function 'to_microduration' [-Wunused-function] >> inline void to_microduration(boost::xtime xt, int& microseconds) >> ^ >> 4 warnings generated. >> >> >> Then ran into a link error: >> >> c++ -o buildout/agents/PassengerHelperAgent.o -Iext -Iext/common >> -I/usr/local/include -Wno-ambiguous-member-template -I/usr/local/include >> -D_REENTRANT -I/usr/local/include -Wall -Wextra -Wno-unused-parameter >> -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long >> -Wno-missing-field-initializers -Wno-ambiguous-member-template -fcommon >> -fvisibility=hidden -DVISIBILITY_ATTRIBUTE_SUPPORTED -g -DHAVE_ACCEPT4 >> -DHAS_SFENCE -DHAS_LFENCE -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS >> -std=gnu++11 -DHAS_UNORDERED_MAP -c ext/common/agents/HelperAgent/Main.cpp >> c++ buildout/agents/PassengerHelperAgent.o -o >> buildout/agents/PassengerHelperAgent >> buildout/common/libpassenger_common/Logging.o >> buildout/common/libpassenger_common/Exceptions.o >> buildout/common/libpassenger_common/Utils/SystemTime.o >> buildout/common/libpassenger_common/Utils/StrIntUtils.o >> buildout/common/libpassenger_common/Utils/IOUtils.o >> buildout/common/libpassenger_common/Utils.o >> buildout/common/libpassenger_common/Utils/Base64.o >> buildout/common/libpassenger_common/Utils/CachedFileStat.o >> buildout/common/libpassenger_common/Utils/LargeFiles.o >> buildout/common/libpassenger_common/ApplicationPool2/Implementation.o >> buildout/common/libpassenger_common/ApplicationPool2/AppTypes.o >> buildout/common/libpassenger_common/AgentsBase.o >> buildout/common/libpassenger_common/Utils/MD5.o >> buildout/common/libpassenger_common/Utils/fib.o >> buildout/common/libpassenger_common/Utils/jsoncpp.o >> buildout/common/libboost_oxt.a -L/usr/local/lib -lev -L/usr/local/lib >> -leio -pthread -lrt >> buildout/agents/PassengerHelperAgent.o: In function >> `_ZNK5boost13function_base6targetIDnEEPKT_v': >> >> /usr/local/lib/ruby/gems/2.0/gems/passenger-4.0.29/ext/boost/function/function_base.hpp:670: >> undefined reference to `_ZTIDn' >> c++: error: linker command failed with exit code 1 (use -v to see >> invocation) >> rake aborted! >> Command failed with status (1): [c++ >> buildout/agents/PassengerHelperAgent.o >> -o buildout/agents/PassengerHelperAgent >> buildout/common/libpassenger_common/Logging.o >> buildout/common/libpassenger_common/Exceptions.o >> buildout/common/libpassenger_common/Utils/SystemTime.o >> buildout/common/libpassenger_common/Utils/StrIntUtils.o >> buildout/common/libpassenger_common/Utils/IOUtils.o >> buildout/common/libpassenger_common/Utils.o >> buildout/common/libpassenger_common/Utils/Base64.o >> buildout/common/libpassenger_common/Utils/CachedFileStat.o >> buildout/common/libpassenger_common/Utils/LargeFiles.o >> buildout/common/libpassenger_common/Applica
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, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ games/burrtools | 0.6.2 | 0.6.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD 10 RC2 net/jags fails to build
Hello all, All the best wishes for 2014. I hope you all had a great time at new years. Net/jags fails to build on freeBSD 10 rc2. Could someone please take a look at this for me? I've included the fail log. Regards, Seniae jags_fails_to_build Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10 RC2 net/jags fails to build
On Thu, 2 Jan 2014 12:17:46 +0100 Seniae Girl wrote: > Hello all, > > > All the best wishes for 2014. I hope you all had a great time at new > years. > > > Net/jags fails to build on freeBSD 10 rc2. Could someone please take > a look at this for me? I've included the fail log. > > > Regards, > Seniae > I created a PR with a patch (only tested build, not install). Please provide feedback to that PR to acknowledge that it works/report further problems: http://www.freebsd.org/cgi/query-pr.cgi?pr=185419 -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: dns/bind* ports overwriting conf files
28.12.2013 02:00, Mathieu Arnold wrote: +--On 25 décembre 2013 22:16:07 -0800 Doug Barton wrote: | While looking at the UPDATING entry for the bdb mess (more on that later) | I happened to see this: | | 20131209: |AFFECTS: users of dns/bind96, dns/bind98 and bind99 on FreeBSD 10.0 |AUTHOR: er...@freebsd.org | |Bind versions before 9.6.3.2.ESV.R10_2, 9.8.6_2, and 9.9.4_2 on |FreeBSD 10.0 will replace named.conf on upgrade. Make sure to |backup any local changes before upgrading to the _2 versions. | | This is not Ok. FreeBSD ports are NEVER supposed to blindly overwrite | config files. Please fix this so that it confirms to over a decade of | policy that FreeBSD ports users should be able to safely depend on. That's ok, because FreeBSD 10.0 is not released yet, and the current version of the bind ports doesn't overwrite the config files. That's what you say. > ls -la /usr/local/etc/namedb/ total 53 drwxr-xr-x 6 root wheel 16 Dec 18 18:23 . drwxr-xr-x 43 root wheel 87 Dec 31 11:47 .. -rw-r--r-- 1 root wheel101 Nov 14 15:06 acls.conf drwxr-xr-x 2 bind bind 2 Dec 6 11:51 dynamic -rw-r--r-- 1 root wheel553 Nov 15 15:18 local.conf -rw-r--r-- 1 root wheel668 Nov 14 15:06 logging.conf drwxr-xr-x 2 root wheel 9 Dec 6 11:51 master -r--r--r-- 1 root wheel 22642 Dec 9 11:33 named.conf -r--r--r-- 1 root wheel 22642 Dec 6 11:46 named.conf.good -r--r--r-- 1 root wheel 21194 Nov 14 15:41 named.conf.old -r--r--r-- 1 root wheel 21194 Dec 6 11:51 named.conf.sample -r--r--r-- 1 root wheel 3134 Dec 6 11:51 named.root -r--r--r-- 1 root wheel 1439 Dec 6 11:51 rndc.conf.sample -rw--- 1 bind wheel 97 Nov 14 15:54 rndc.key drwxr-xr-x 2 bind bind 2 Dec 6 11:51 slave drwxr-xr-x 2 bind bind 6 Jan 2 14:47 working # portmaster dns/bind99 > ls -la /usr/local/etc/namedb/ total 52 drwxr-xr-x 6 root wheel 16 Jan 2 15:14 . drwxr-xr-x 43 root wheel 87 Dec 31 11:47 .. -rw-r--r-- 1 root wheel101 Nov 14 15:06 acls.conf drwxr-xr-x 2 bind bind 2 Jan 2 15:14 dynamic -rw-r--r-- 1 root wheel553 Nov 15 15:18 local.conf -rw-r--r-- 1 root wheel668 Nov 14 15:06 logging.conf drwxr-xr-x 2 root wheel 9 Jan 2 15:14 master -r--r--r-- 1 root wheel 21194 Jan 2 15:14 named.conf -r--r--r-- 1 root wheel 22642 Dec 6 11:46 named.conf.good -r--r--r-- 1 root wheel 21194 Nov 14 15:41 named.conf.old -r--r--r-- 1 root wheel 21194 Jan 2 15:14 named.conf.sample -r--r--r-- 1 root wheel 3134 Jan 2 15:14 named.root -r--r--r-- 1 root wheel 1439 Jan 2 15:14 rndc.conf.sample -rw--- 1 bind wheel 97 Nov 14 15:54 rndc.key drwxr-xr-x 2 bind bind 2 Jan 2 15:14 slave drwxr-xr-x 2 bind bind 6 Jan 2 14:47 working And that's what I see. I doesn't even made a backup of old named.conf. All files named `named.conf.*` (except for `*.sample`) are mine and weren't touched by port. I filed a bug and it was closed: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/184562 UPDATING states that: 20131209: AFFECTS: users of dns/bind96, dns/bind98 and bind99 on FreeBSD 10.0 AUTHOR: er...@freebsd.org Bind versions before 9.6.3.2.ESV.R10_2, 9.8.6_2, and 9.9.4_2 on FreeBSD 10.0 will replace named.conf on upgrade. Make sure to backup any local changes before upgrading to the _2 versions. But this doesn't happen only on port upgrade, any time bind is installed it wipes old config. -- Sphinx of black quartz, judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
firefox and vlc without dbus
Hi, I've built both firefox and vlc without dbus (unchecked in options). FF was also built without gconf and gesettings etc. But when running them they both start a dbus-launch and dbus-daemon. FF also starts gconfd-2. So why do unchecking these options don't have any effect? Regards, Marco -- Prof:So the American government went to IBM to come up with a data encryption standard and they came up with ... Student: EBCDIC! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: dns/bind* ports overwriting conf files
+--On 2 janvier 2014 15:21:50 +0200 Volodymyr Kostyrko wrote: |> That's ok, because FreeBSD 10.0 is not released yet, and the current |> version of the bind ports doesn't overwrite the config files. | | That's what you say. Yup, that's what Erwin told me, I did believe him :-) | But this doesn't happen only on port upgrade, any time bind is installed | it wipes old config. which you're right, shouldn't happen, Erwin told me he was looking at it, though. -- Mathieu Arnold ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
RE: FreeBSD 10 RC2 net/jags fails to build
Hello Michael, Thank you for your quick reply. I've tried to apply the patch but I don't think it works. It is however very well possible that I didn't do it correctly. I've included the log file. Regards, Seniae > Date: Thu, 2 Jan 2014 13:11:52 +0100 > From: free...@grem.de > To: se...@live.nl > CC: freebsd-ports@freebsd.org; g...@freebsd.org > Subject: Re: FreeBSD 10 RC2 net/jags fails to build > > On Thu, 2 Jan 2014 12:17:46 +0100 > Seniae Girl wrote: > > > Hello all, > > > > > > All the best wishes for 2014. I hope you all had a great time at new > > years. > > > > > > Net/jags fails to build on freeBSD 10 rc2. Could someone please take > > a look at this for me? I've included the fail log. > > > > > > Regards, > > Seniae > > > > I created a PR with a patch (only tested build, not install). > > Please provide feedback to that PR to acknowledge that it works/report > further problems: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=185419 > > -- > Michael Gmelin jags_patch_apply Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/py-mercurialserver broken by last commit
Good day and happy New Year )
The last commit into devel/py-mercurialserver (rev. 337698) broke it.
Buildlog tail:
===
changing mode of build/scripts-2.7/refresh-auth from 644 to 755
===> Staging for py27-mercurialserver-1.2.0
===> py27-mercurialserver-1.2.0 depends on executable: hg - found
===> py27-mercurialserver-1.2.0 depends on file: /usr/local/bin/python2.7
- found
** Missing /usr/ports/devel/py-mercurialserver/files/pkg-message.in for
py27-mercurialserver-1.2.0.
*** [apply-slist] Error code 1
Stop in /usr/ports/devel/py-mercurialserver.
===
I suggest next patch (tested in tinderbox):
--- Makefile.orig 2013-12-27 18:34:14.0 +0800
+++ Makefile2014-01-02 23:08:47.0 +0800
@@ -24,10 +24,8 @@
USERS= ${HGUSER}
GROUPS=${HGGROUP}
-SUB_FILES= pkg-message
SUB_LIST= PORTNAME=${PORTNAME} \
HGUSER=${HGUSER}
-PKGMESSAGE=${WRKDIR}/pkg-message
USE_PYTHON=yes
USE_PYDISTUTILS=yes
@@ -41,6 +39,7 @@
${SED} -I .orig -e
"s#/etc/mercurial-server/#${PREFIX}/etc/${PORTNAME}/#"
${WRKSRC}/src/init/dot-mercurial-server
post-install:
+ ${MKDIR} ${STAGEDIR}${PREFIX}/hg
${MKDIR} ${STAGEDIR}${PREFIX}/etc/${PORTNAME}/remote-hgrc.d
${MKDIR} ${STAGEDIR}${PREFIX}/etc/${PORTNAME}/keys/users
${MKDIR} ${STAGEDIR}${PREFIX}/etc/${PORTNAME}/keys/root
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10 RC2 net/jags fails to build
On Thu, 2 Jan 2014 16:11:08 +0100 Seniae Girl wrote: > Hello Michael, > > > Thank you for your quick reply. I've tried to apply the patch but I > don't think it works. It is however very well possible that I didn't > do it correctly. I've included the log file. > > > > Regards, > Seniae > > > Date: Thu, 2 Jan 2014 13:11:52 +0100 > > From: free...@grem.de > > To: se...@live.nl > > CC: freebsd-ports@freebsd.org; g...@freebsd.org > > Subject: Re: FreeBSD 10 RC2 net/jags fails to build > > > > On Thu, 2 Jan 2014 12:17:46 +0100 > > Seniae Girl wrote: > > > > > Hello all, > > > > > > > > > All the best wishes for 2014. I hope you all had a great time at > > > new years. > > > > > > > > > Net/jags fails to build on freeBSD 10 rc2. Could someone please > > > take a look at this for me? I've included the fail log. > > > > > > > > > Regards, > > > Seniae > > > > > > > I created a PR with a patch (only tested build, not install). > > > > Please provide feedback to that PR to acknowledge that it > > works/report further problems: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=185419 > > > > -- > > Michael Gmelin > Make sure you run make clean first (or just remove the work directory, e.g. rm -rf /usr/ports/net/jags/work ). Your output doesn't show the patch and/or configure stage, so I assume those already had been done before you applied the patch. If this doesn't work, please follow these instruction: Start from a clean ports tree rm -rf /usr/ports portsnap fetch extract Then apply the patch using: cd /usr/ports/net/jags patch http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
sane-backends 1.0.24?
Has anyone tried updating sane-backends port to version 1.0.24? I tried a quick and dirty, by just updating the ports Makefile, and only using a minimal set of patches. It compiles, but during install I get this: ===> Building package for sane-backends-1.0.24 Creating package /usr/ports/graphics/sane-backends/work/sane-backends-1.0.24.tbz Registering depends: avahi-app-0.6.31 dbus-glib-0.100.2 dbus-1.6.12 gamin-0.1.10_6 gdbm-1.11 gobject-introspection-1.36.0_2 glib-2.36.3_1 python27-2.7.6_1 gettext-0.18.3.1 libX11-1.6.2,1 libxcb-1.9.3 libxml2-2.8.0_3 libiconv-1.14_1 libdaemon-0.14 libffi-3.0.13_1 libpthread-stubs-0.3_4 pcre-8.33 pkgconf-0.9.4 tiff-4.0.3 jbigkit-1.6 libv4l-0.8.8_1 jpeg-8_4 perl5.14-5.14.4_4 gnomehier-3.0 gnome_subr-1.0 expat-2.1.0 kbproto-1.0.6 libSM-1.2.2,1 libICE-1.0.8,1 libXau-1.0.8 libXdmcp-1.1.1 xproto-7.0.25. Creating bzip'd tar ball in '/usr/ports/graphics/sane-backends/work/sane-backends-1.0.24.tbz' tar: etc/sane.d/dist/abaton.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/agfafocus.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/apple.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/artec.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/artec_eplus48u.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/avision.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/bh.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/canon.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/canon630u.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/canon_dr.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/cardscan.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/coolscan.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/coolscan2.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/coolscan3.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/dc210.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/dc240.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/dc25.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/dell1600n_net.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/dll.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/dmc.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/epjitsu.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/epson.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/epson2.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/fujitsu.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/genesys.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/gt68xx.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/hp.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/hp3900.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/hp4200.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/hp5400.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/hs2p.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/ibm.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/kodak.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/kodakaio.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/leo.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/lexmark.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/ma1509.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/magicolor.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/matsushita.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/microtek.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/microtek2.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/mustek.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/mustek_usb.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/nec.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/net.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/p5.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/pie.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/pixma.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/plustek.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/plustek_pp.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/ricoh.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/rts8891.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/s9036.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/saned.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/sceptre.conf: Cannot stat: No such file or directory tar: etc/sane.d/dist/sharp.con
RE: FreeBSD 10 RC2 net/jags fails to build
Michael, Your patch seems to work though due to another issue it doesn't build the whole port. The next problem has to do with gsed-4.2.2. Added a log of the latest issue. Regards, Seniae > > Make sure you run make clean first (or just remove the work directory, > e.g. rm -rf /usr/ports/net/jags/work ). Your output doesn't show the > patch and/or configure stage, so I assume those already had been done > before you applied the patch. > > If this doesn't work, please follow these instruction: > > Start from a clean ports tree > > rm -rf /usr/ports > portsnap fetch extract > > Then apply the patch using: > > cd /usr/ports/net/jags > patch > And build: > > make > make install > > > > -- > Michael Gmelin jags_fails Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10 RC2 net/jags fails to build
On Thu, 2 Jan 2014 23:20:03 +0100 Seniae Girl wrote: > > Michael, > > > Your patch seems to work though due to another issue it doesn't build > the whole port. The next problem has to do with gsed-4.2.2. > > > Added a log of the latest issue. > > > Regards, > Seniae > (If possible, please don't top post, see http://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiquette.html) Your log shows that you were (accidentally?) building all ports in the net category, not just jags: > root@md:/usr/ports/net # make That's why you started building the following ports in alphabetical order: > ===> 3proxy > ===> 44bsd-rdist > ===> 6tunnel > ===> AquaGatekeeper > ===> DarwinStreamingServer > ===> GeoIP > ===> R-cran-twitteR > ... textproc/gsed is not a dependency of net/jags, so if all you want is to install jags I'd suggest you run "make install" from within its directory ;) cd /usr/ports/net/jags make install -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10 RC2 net/jags fails to build
hahaha omg how stupid ... let me try again lol ... i didn't even notice it -Original Message- From: Michael Gmelin Sent: Friday, January 03, 2014 12:22 AM To: Seniae Girl Cc: FreeBSD-ports Subject: Re: FreeBSD 10 RC2 net/jags fails to build On Thu, 2 Jan 2014 23:20:03 +0100 Seniae Girl wrote: Michael, Your patch seems to work though due to another issue it doesn't build the whole port. The next problem has to do with gsed-4.2.2. Added a log of the latest issue. Regards, Seniae (If possible, please don't top post, see http://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiquette.html) Your log shows that you were (accidentally?) building all ports in the net category, not just jags: root@md:/usr/ports/net # make That's why you started building the following ports in alphabetical order: ===> 3proxy ===> 44bsd-rdist ===> 6tunnel ===> AquaGatekeeper ===> DarwinStreamingServer ===> GeoIP ===> R-cran-twitteR ... textproc/gsed is not a dependency of net/jags, so if all you want is to install jags I'd suggest you run "make install" from within its directory ;) cd /usr/ports/net/jags make install -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" --- Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus-bescherming actief is. http://www.avast.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10 RC2 net/jags fails to build
Alright, I followed all steps you gave me and I still get the same error ... :(. -Original Message- From: Michael Gmelin Sent: Friday, January 03, 2014 12:22 AM To: Seniae Girl Cc: FreeBSD-ports Subject: Re: FreeBSD 10 RC2 net/jags fails to build On Thu, 2 Jan 2014 23:20:03 +0100 Seniae Girl wrote: Michael, Your patch seems to work though due to another issue it doesn't build the whole port. The next problem has to do with gsed-4.2.2. Added a log of the latest issue. Regards, Seniae (If possible, please don't top post, see http://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiquette.html) Your log shows that you were (accidentally?) building all ports in the net category, not just jags: root@md:/usr/ports/net # make That's why you started building the following ports in alphabetical order: ===> 3proxy ===> 44bsd-rdist ===> 6tunnel ===> AquaGatekeeper ===> DarwinStreamingServer ===> GeoIP ===> R-cran-twitteR ... textproc/gsed is not a dependency of net/jags, so if all you want is to install jags I'd suggest you run "make install" from within its directory ;) cd /usr/ports/net/jags make install -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" --- Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus-bescherming actief is. http://www.avast.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[QAT] r338516: 4x leftovers, 4x ???, 20x success
Part 3 at removing now useless FETCH_ARGS redifition - Build ID: 20140103015401-31295 Job owner: b...@freebsd.org Buildtime: 92 minutes Enddate: Fri, 03 Jan 2014 03:25:45 GMT Revision: r338516 Repository: https://svnweb.freebsd.org/ports?view=revision&revision=338516 - Port:deskutils/rubrica 2.0.12 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247516/rubrica-2.0.12.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247517/rubrica-2.0.12.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247518/rubrica-2.0.12.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247519/rubrica-2.0.12.log - Port:devel/py-traits 3.6.0_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247520/py27-traits-3.6.0_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247521/py27-traits-3.6.0_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247522/py27-traits-3.6.0_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247523/py27-traits-3.6.0_1.log - Port:editors/py-room 0.4.1_5 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247524/py27-room-0.4.1_5.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247525/py27-room-0.4.1_5.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247526/py27-room-0.4.1_5.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247527/py27-room-0.4.1_5.log - Port:games/openarena-data 0.8.8 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247528/openarena-data-0.8.8.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247529/openarena-data-0.8.8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247530/openarena-data-0.8.8.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247531/openarena-data-0.8.8.log - Port:misc/libmetalink 0.0.3_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247532/libmetalink-0.0.3_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247533/libmetalink-0.0.3_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247534/libmetalink-0.0.3_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247535/libmetalink-0.0.3_1.log - Port:net-mgmt/ocsinventory-agent 2.0.5,1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247536/Ocsinventory-Unix-Agent-2.0.5,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140103015401-31295-247537/Ocsinventory-Unix-Agent-2.0.5,1.log Buildgroup: 9.2-QAT/amd64 Buildstatu
