Re: /usr/ports/UPDATING entry September 04, 2013
On 10/13/13 18:40, Joe Nosay wrote: Will the pkg upgrade work with applications built from ports and not pkg add $APPLICATION? I'm not sure What you mean. the pkg upgrade command works only using binary packages, which can come and official repository or your own one. This is going to work. If you have a system where you used to build packages yourself and want to change to binary packages, things are more complicated. First of all if you have any port built with custom options you are going to loose those customizations, since the binary packages don't have them. I think pkg will try to handle that upgrade but I have never tried, it could work but you could also end up with come misalignment in your ports. It is generally not a good idea to mix ports and pkgs, it can work but problems will come up. -- Guido Falsi madpi...@freebsd.org ___ 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: /usr/ports/UPDATING entry September 04, 2013
On Mon, Oct 14, 2013 at 3:43 AM, Guido Falsi madpi...@freebsd.org wrote: On 10/13/13 18:40, Joe Nosay wrote: Will the pkg upgrade work with applications built from ports and not pkg add $APPLICATION? I'm not sure What you mean. the pkg upgrade command works only using binary packages, which can come and official repository or your own one. This is going to work. If you have a system where you used to build packages yourself and want to change to binary packages, things are more complicated. First of all if you have any port built with custom options you are going to loose those customizations, since the binary packages don't have them. I think pkg will try to handle that upgrade but I have never tried, it could work but you could also end up with come misalignment in your ports. It is generally not a good idea to mix ports and pkgs, it can work but problems will come up. -- Guido Falsi madpi...@freebsd.org Thanks much. ___ 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: accidently removed /usr/ports/.svn/pristine
On Sun, 13 Oct 2013, the wise Larry Rosenman wrote: re-checkout the tree I did a re-checkout but I'm still getting errors: Updating '/usr/ports': svn: E02: Can't open file '/usr/ports/.svn/pristine/3d/3d137a82c6597c2c70a7f77b171e7456196e847e.svn-base': No such file or directory svn: E02: Additional errors: svn: E02: Can't open file '/usr/ports/.svn/pristine/3d/3d137a82c6597c2c70a7f77b171e7456196e847e.svn-base': No such file or directory Marco -- Quality Control, n.: The process of testing one out of every 1,000 units coming off a production line to make sure that at least one out of 100 works. ___ 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: accidently removed /usr/ports/.svn/pristine
On Mon, 14 Oct 2013 10:53:56 +0200 (CEST) Marco Beishuizen mb...@xs4all.nl wrote: On Sun, 13 Oct 2013, the wise Larry Rosenman wrote: re-checkout the tree I did a re-checkout but I'm still getting errors: Updating '/usr/ports': svn: E02: Can't open file '/usr/ports/.svn/pristine/3d/3d137a82c6597c2c70a7f77b171e7456196e847e.svn-base': No such file or directory svn: E02: Additional errors: svn: E02: Can't open file '/usr/ports/.svn/pristine/3d/3d137a82c6597c2c70a7f77b171e7456196e847e.svn-base': No such file or directory rm -fr /usr/ports svn co .. Marco -- wbr, tiger ___ 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: accidently removed /usr/ports/.svn/pristine
On Mon, 14 Oct 2013, the wise Sergey V. Dyatko wrote: rm -fr /usr/ports svn co .. I did this too but still no new ports tree: root@yokozuna:/home/marco# svn co svn://svn.freebsd.org/ports/head ports Checked out revision 330285. root@yokozuna:/home/marco# svn up /usr/ports Skipped '/usr/ports' Summary of conflicts: Skipped paths: 1 Marco -- It is better to wear chains than to believe you are free, and weight yourself down with invisible chains. ___ 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: accidently removed /usr/ports/.svn/pristine
## Marco Beishuizen (mb...@xs4all.nl): I did this too but still no new ports tree: root@yokozuna:/home/marco# svn co svn://svn.freebsd.org/ports/head ports Checked out revision 330285. Your freshly checked out ports tree now lives in /home/marco/ports (if your line was really copypasted). Regards, Christoph -- Spare Space ___ 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: accidently removed /usr/ports/.svn/pristine
On Mon, 14 Oct 2013, the wise Christoph Moench-Tegeder wrote: Your freshly checked out ports tree now lives in /home/marco/ports (if your line was really copypasted). You are right. After I redid all the steps (this time the right way) all seems well now. Thanks for all the help! Regards, Marco -- By doing just a little every day, you can gradually let the task completely overwhelm you. ___ 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
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description f ports/182958[update] devel/json-c to 0.11 o ports/182957[maintainer update] math/ess 13.05 - 13.09 + STAGEDIR o ports/182947www/apache22-peruser-mpm reload fix o ports/182946[maintainer-update] devel/awscli - update to 1.1.2 o ports/182939[maintainer-update] clang fix for devel/psptoolchain-g o ports/182938bug fix for building net/tcpillust o ports/182928[PATCH] Add stagedir support to x11/tint and cleanup o ports/182923some ports still require WITH_PKGNG=1 o ports/182915net/proxychains - multiple issues o ports/182913[MAINTAINER-UPDATE] Update games/stonesoup and games/s o ports/182909Ports should sanitize the environment f ports/182900[patch] graphics/inventor -- fix build with modern com o ports/182893multimedia/dv2sub - fix brokenness of package build wh f ports/182892Make devel/atf create a tests user o ports/182875graphics/dri: make: /usr/ports/graphics/dri/Makefile f ports/182869minicron install error f ports/182865fontconfig errors in x11-fonts/wqy f ports/182853ports/textproc/urlview: regex - pcreregex f ports/182848[maintainer update] [stagedir] multimedia/ffmpegthumbn f ports/182840net-mgmt/smokeping build with perl 5.18 installed f ports/182834ports/www/dummyflash/Makefile add BUILD_DEPENDS= gcc:p o ports/182829sysutils/linux-afaapps: missing dependency (devel/linu f ports/182826deskutils/fet update to 5.20.1 o ports/182821gmake strangeness on 10.0 Alpha 4 o ports/182815Core dump in net/mDNSResponder-379.38.1 using IPv6 o ports/182802science/gwyddion: Update to version 2.32 o ports/182801emulators/mame: Update to version 0.150 o ports/182800science/qcl: Update to version 0.6.3 o ports/182797games/xdeblock: Fix build with clang o ports/182796x11-wm/jwm: Update to version 2.1.0 a ports/182793Updating graphics/ImageMagick f ports/182792dns/knot: knotd startup script no longer works o ports/182791New port: multimedia/livestreamer pipe video streams i f ports/182780Port sysutils/ddrescue version 1.17 upgrade [patch] o ports/182776net-mgmt/nrpe Fails to Build (Hangs After Distfile Fet o ports/182774[MAINTAINER-UPDATE]: graphics/apvlv Link to pthread di o ports/182772graphics/aaphoto cannot be built because of the defaul o ports/182771new port devel/gitlab_git o ports/182770new port textproc/gitlab-grit o ports/182769[patch] Update games/stockfish to version 4 o ports/182767new port www/gitlab-grack o ports/182766new port net/gitlab_omniauth-ldap o ports/182763new port devel/font-awesome-rails o ports/182762new port www/jquery-atwho-rails f ports/182758[patch update] security/ipsec-tools: fix build on 10a4 o ports/182754[maintainer-update] games/urbanterror-data f ports/182752[patch update] net/ndisc6 compile fix for 10-ALPHA4, a o ports/182735new port textproc/github-linguist o ports/182732new port rubygem-jquery-turbolinks o ports/182723graphics/dri fails to build on 9.2-Stable o ports/182717ports: www/fcgiwrap building broken, dependency on dev f ports/182712Port audio/audacity tries to build the entire project f ports/182709Port dns/ldns: ldns-config is not an example [patch] o ports/182699new port net/omniauth-github o ports/182683multimedia/libquicktime fails to build (post-patch bot f ports/182662[Patch] Update mail/imapsync to version 1.567 o ports/182652new port www/bootstrap-sass o ports/182639databases/libmongo-client: stage support o ports/182638x11-wm/stumpwm 0.9.7_13 is marked as broken f ports/182635[patch] Update sysutils/condor to 8.0.3 o ports/182628New port: print/cups-lexmark-cs310 CUPS/foomatic drive o ports/182626[PATCH] Mk/bsd.options.mk: add more helpers and remove f ports/182624deskutils/fet update f ports/182619mail/qmailadmin-devel: Remove port o ports/182612newly built ports report problems when verifying with o ports/182597[PATCH] net/scribe: [SUMMARIZE CHANGES] o
Current problem reports assigned to po...@freebsd.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. No matches to your query ___ 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: stagedir vs. jail
Do I understand this situation correctly: Users are having issues with building/installing packages with STAGEDIR enabled in lightweight jails that use symlinks to share parts of the base system between many jails to make it easier to upgrade the jails and avoid duplication/wasted disk space? It seems that the handbook and ezjails may both replicate this behavior. http://www.freebsd.org/doc/handbook/jails-application.html If this is correct, the only workaround may be for you to use a private package repository constructed by poudriere and to not actually build your packages within the jails you intend to use them in. The types of jails you are using are certainly a supported method for running jails, but I can see the severe limitations it imposes on the newer package building method which is designed to ensure packages are built as accurately and reliably as possible. Maybe bapt co can find a workaround for this, but this does sound like an edge case. Please keep in mind that there are some growing pains as the ports team attempts to mature packages on FreeBSD so we can one day go from 90% users build from ports and only 10% using packages to a reality where 90% of the users are able to use packages and only 10% have to build from ports. I should note that I successfully run these types of jails but I run poudriere from the host to have private package repositories. It makes it very easy to pop into a jail and run pkg upgrade and instantly the jail is updated and I can restart services or quickly restart the entire jail. ___ 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: stagedir vs. jail
I have actually noticed many times earlier that using symlinks for /usr/ports, /usr/src and the related directories do cause problems, jails or not. -Kimmo ___ 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] r330316: 4x leftovers
- Convert to USES+=tk - STAGE-clean - Build ID: 20131014130800-53018 Job owner: g...@freebsd.org Buildtime: 2 hours Enddate: Mon, 14 Oct 2013 15:29:13 GMT Revision: r330316 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=330316 - Port:x11-toolkits/tktable 2.10_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~g...@freebsd.org/20131014130800-53018-207048/tktable-2.10_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~g...@freebsd.org/20131014130800-53018-207049/tktable-2.10_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~g...@freebsd.org/20131014130800-53018-207050/tktable-2.10_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~g...@freebsd.org/20131014130800-53018-207051/tktable-2.10_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131014130800-53018 redports https://qat.redports.org/ ___ 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] r330275: 46x success, 3x depend_package, 1x depend (runaway_process in java/openjdk6), 4x compiler_error, 4x ignored: is marked as broken: does not build with recent boost, 1x fail, 1x depend (?
Fix package name collision - Build ID: 20131014065401-5671 Job owner: b...@freebsd.org Buildtime: 9 hours Enddate: Mon, 14 Oct 2013 15:36:53 GMT Revision: r330275 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=330275 - Port:chinese/phpbb3-tw 3.0.11 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206836/zh-phpbb3-tw-3.0.11.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206837/zh-phpbb3-tw-3.0.11.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206838/zh-phpbb3-tw-3.0.11.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206839/zh-phpbb3-tw-3.0.11.log - Port:databases/adodb5 5.18 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206840/adodb5-5.18.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206841/adodb5-5.18.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206842/adodb5-5.18.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206843/adodb5-5.18.log - Port:databases/mysql++1 1.7.40_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206844/mysql++1-mysql55-1.7.40_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206845/mysql++1-mysql55-1.7.40_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206846/mysql++1-mysql55-1.7.40_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206847/mysql++1-mysql55-1.7.40_2.log - Port:devel/autoconf213 2.13.000227_6 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206848/autoconf213-2.13.000227_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206849/autoconf213-2.13.000227_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206850/autoconf213-2.13.000227_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206851/autoconf213-2.13.000227_6.log - Port:devel/gitolite2 2.3.1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206852/gitolite2-2.3.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206853/gitolite2-2.3.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206854/gitolite2-2.3.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206855/gitolite2-2.3.1.log - Port:devel/llvm33 3.3_4 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206856/llvm33-3.3_4.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20131014065401-5671-206857/llvm33-3.3_4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log:
Re: stagedir vs. jail
On Sun, Oct 13, 2013 at 9:27 AM, Dewayne dewayne.gerag...@heuristicsystems.com.au wrote: My setup is slightly different, where I do use as Matthew recommends, nullfs is used without symlinks; and pkg_* and portmaster are used for the build process. We've been using jails to build ports for different architectures for years, the builds are currently on a FreeBSD 9.2Stable (Built from source on Oct 8) system. Building all ports after a complete wipe, using the portmaster commands fails due to missing file + portmaster --no-term-title --no-confirm -H -K -D -g -G -B -v -m __MAKE_CONF=/etc/make_P3.conf -m -DBUILD__PRODUCTION mail/sendmail tar: etc/rc.d/saslauthd: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 In fact the file does exist: # ls -lh /usr/staging/usr/local/etc/rc.d/saslauthd -r-xr-xr-x 1 root wheel 940B Oct 14 00:55 /usr/staging/usr/local/etc/rc.d/saslauthd and not in /usr/local/etc/rc.d/ As you can see sendmail builds saslauthd as a prerequisite. The build process also fails in the same way, missing file in etc/rc.d/... for samba36, samba4, isc-dhcp42-server and cyrus-sasl2-saslauthd, but works correctly for some 40 other packages. The make.conf includes: WRKDIRPREFIX=/var/ports DISTDIR=/distfiles TMPDIR=/tmp PACKAGES=/packages STAGEDIR=/usr/staging FAVORITE_COMPILER=gcc DEFAULT_VERSIONS=perl5=5.16 python=2.7 python2=2.7 apache=22 DISABLE_LICENSES=yes # Not that I want to, only that it prevented the build (a PR existed for this) WITH_CCACHE_BUILD=yes MAKE_JOBS_UNSAFE=yes I suspect the problem lies within the if/then block .if !target(install-rc-script) in bsd.port.mk, but lack the know-how to proceed further. I have sent PR 182972 regarding this issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=182972 The cause of the issue is due to setting STAGEDIR in /etc/make.conf and Mk/bsd.port.mk not undefining STAGEDIR when NO_STAGE is set. Which causes the install-rc-script to look in the STAGEDIR for the file. Scot ___ 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: Port build failure -- security/hydra
Ronald F. Guilmette wrote on 06.10.2013 01:34: make -V FETCH_CMD Results: /usr/bin/fetch -AFpr on your system? What FreeBSD version you are using? FreeBSD segfault.tristatelogic.com 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Yes, I now see the issue. If I understand correctly /usr/bin/fetch got SSL support since FreeBSD 9.2, so is why it isn't work to you. PS. Yes, packetstorm has different distifile at the moment. No no. As I said, *all* of the mirrors appear to have the tarball that is 681552 bytes long, and only just the thc.org copy fo teh tarball has the size 681784. Packetstorm just updated the distfile on their mirrors, so now all should work. === hydra-7.5 depends on file: /usr/local/sbin/pkg - found = hydra-7.5.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://dl.packetstormsecurity.net/groups/thc/hydra-7.5.tar.gz hydra-7.5.tar.gz 100% of 665 kB 249 kBps 00m03s -- Regards, Ruslan T.O.S. Of Reality ___ 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
ports/182960: Re: security/cyrus-sasl2-saslauthd erroneously asserts wrong openldap version
Hi,
On Mon, 14 Oct 2013 05:49:36 GMT
Dewayne dewayne.gerag...@heuristicsystems.com.au said:
I cannot reproduce it even with openldap24-sasl-client, here.
Since this message is from bsd.ldap.mk, this PR should be assigned to
the maintainer of bsd.ldap.mk rather than individual ports such as
cyrus-sasl2-saslauthd.
Sincerely,
--
Hajimu UMEMOTO
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.mahoroba.org/~ume/
___
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: ports/182960: security/cyrus-sasl2-saslauthd erroneously asserts wrong openldap version
Synopsis: security/cyrus-sasl2-saslauthd erroneously asserts wrong openldap version Responsible-Changed-From-To: ume-ports Responsible-Changed-By: ume Responsible-Changed-When: Mon Oct 14 16:20:20 UTC 2013 Responsible-Changed-Why: It seems this is not for individual ports. http://www.freebsd.org/cgi/query-pr.cgi?pr=182960 ___ 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: Port build failure -- security/hydra
On Mon, 14 Oct 2013 20:13:51 +0400 Ruslan Makhmatkhanov cvs-...@yandex.ru wrote: Ronald F. Guilmette wrote on 06.10.2013 01:34: make -V FETCH_CMD Results: /usr/bin/fetch -AFpr on your system? What FreeBSD version you are using? FreeBSD segfault.tristatelogic.com 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Yes, I now see the issue. If I understand correctly /usr/bin/fetch got SSL support since FreeBSD 9.2, so is why it isn't work to you. Fetch had basic SSL support for many years, what changed is that in 10-CURRENT and 9-STABLE proper checking of certificates has been implemented, which is disabled for the ports system though (since it's using checksums and size checks anyway). So this is not the problem. Michael -- 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: ports/164190: [PATCH] devel/liboil: Fix build with clang
Synopsis: [PATCH] devel/liboil: Fix build with clang Responsible-Changed-From-To: mm-ports Responsible-Changed-By: mm Responsible-Changed-When: Mon Oct 14 17:54:58 UTC 2013 Responsible-Changed-Why: Reassign back to ports@ as I no longer maintain liboil http://www.freebsd.org/cgi/query-pr.cgi?pr=164190 ___ 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: ports/182960: security/cyrus-sasl2-saslauthd erroneously asserts wrong openldap version
The following reply was made to PR ports/182960; it has been noted by GNATS. From: Dewayne dewayne.gerag...@heuristicsystems.com.au To: bug-follo...@freebsd.org, dewayne.gerag...@heuristicsystems.com.au Cc: Subject: Re: ports/182960: security/cyrus-sasl2-saslauthd erroneously asserts wrong openldap version Date: Tue, 15 Oct 2013 15:59:21 +1100 Please close this PR. The patch to the Makefile enabled this port to create a package. No, not magic, refer: http://svnweb.freebsd.org/ports/head/security/cyrus-sasl2-saslauthd/Makefile?r1=327769r2=330241 Ume's inability to reproduce the fault, lay in the timing between when I updated my ports which was a few hours before reporting the fault; and, I suspect, when he endevoured to reproduce, after the new patch was applied. No doubt you were already working the conversion to staging, before my PR. Thank-you. Dewayne. ___ 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
