Re: [net/openntpd] pidfile support
Hi, This race also affects OpenSMTPD. In general it will affect all daemons that don't use pid files and are killing their childrens by themselves when they received SIGTERM. Regards, Tomasz Walaszek 2014-06-02 22:30 GMT+02:00 Christian Weisgerber na...@mips.inka.de: On 2014-06-02, Christian Weisgerber na...@mips.inka.de wrote: I remember seeing the error above, but on further investigation, this doesn't happen any longer... at least here on FreeBSD 10-STABLE. Strike that. Investigating with rc_debug=YES shows that SIGTERM is still sent to all child processes and the race still exists. It just doesn't show up on my new machine because, well, it's a race condition. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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 -- Pozdrawiam Tomasz Wałaszek ___ 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
staging mail/heirloom-mailx [for review]
I noticed that mail/heirloom-mailx is no longer maintained, and has
not been staged.
It looks straightforward. Did I miss anything?
--- Makefile2014-05-31 21:58:23.0 -0700
+++ Makefile-staged 2014-06-03 00:34:03.0 -0700
@@ -8,7 +8,7 @@
MASTER_SITES= SF/heirloom/heirloom-${PORTNAME}/${PORTVERSION}
PKGNAMEPREFIX= heirloom-
-MAINTAINER=po...@freebsd.org
+MAINTAINER=per...@pluto.rain.com
COMMENT= BSD mail utility with MIME, IMAP, POP3, SMTP, and S/MIME
extensions
OPTIONS_DEFINE=IPV6 DOCS
@@ -25,10 +25,10 @@
CPPFLAGS=${CPPFLAGS} \
LDFLAGS=${LDFLAGS}
-MAN1= ${PORTNAME}.1
PORTDOCS= AUTHORS COPYING ChangeLog README TODO
PLIST_FILES= bin/${PORTNAME} \
+ man/man1/${PORTNAME}.1 \
@unexec if cmp -s %D/etc/nail.rc %D/etc/nail.rc.default; then
${RM} -f %D/etc/nail.rc; fi \
etc/nail.rc.default \
@exec [ -f %B/nail.rc ] || ${CP} %B/%f %B/nail.rc
@@ -36,7 +36,6 @@
CPPFLAGS+= -I${LOCALBASE}/include
LDFLAGS+= -L${LOCALBASE}/lib
-NO_STAGE= yes
.include bsd.port.options.mk
.if ${PORT_OPTIONS:MIPV6}
@@ -44,16 +43,13 @@
.endif
do-install:
- ${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${PREFIX}/bin
- ${INSTALL_MAN} ${WRKSRC}/${MAN1} ${MAN1PREFIX}/man/man1
- ${INSTALL_DATA} ${WRKSRC}/nail.rc ${PREFIX}/etc/nail.rc.default
-.if !exists(${PREFIX}/etc/nail.rc)
- ${INSTALL_DATA} ${WRKSRC}/nail.rc ${PREFIX}/etc
-.endif
+ ${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${STAGEDIR}${PREFIX}/bin
+ ${INSTALL_MAN} ${WRKSRC}/${PORTNAME}.1 ${STAGEDIR}${MAN1PREFIX}/man/man1
+ ${INSTALL_DATA} ${WRKSRC}/nail.rc
${STAGEDIR}${PREFIX}/etc/nail.rc.default
.if ${PORT_OPTIONS:MDOCS}
- @${MKDIR} ${DOCSDIR}
+ @${MKDIR} ${STAGEDIR}${DOCSDIR}
.for i in ${PORTDOCS}
- ${INSTALL_DATA} ${WRKSRC}/${i} ${DOCSDIR}
+ ${INSTALL_DATA} ${WRKSRC}/${i} ${STAGEDIR}${DOCSDIR}
.endfor
.endif
___
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] 355707: 2x depend (compiler_error in editors/emacs21), 4x ignored: incorrect 'uses+=tar:bizp2', 1x depend (??? in graphics/netpbm), 4x ignored: you should define tgtarch and tgtabi to build port
- Convert gmake, bzip2 to USES Approved by:portmgr - Build ID: 20140529151000-34746 Job owner: m...@freebsd.org Buildtime: 5 days Enddate: Tue, 03 Jun 2014 09:35:09 GMT Revision: 355707 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355707 - Port:devel/aros-sdk 0.20060207 Buildgroup: 8.4-QAT/amd64 Buildstatus: IGNORED: IS ONLY FOR I386, WHILE YOU ARE RUNNING AMD64 (REASON: SHOULD WORK WITH A CROSS COMPILER, NEEDS TESTING) Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342007/aros-sdk-0.20060207.log Buildgroup: 9.2-QAT/amd64 Buildstatus: IGNORED: IS ONLY FOR I386, WHILE YOU ARE RUNNING AMD64 (REASON: SHOULD WORK WITH A CROSS COMPILER, NEEDS TESTING) Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342009/aros-sdk-0.20060207.log - Port:devel/asmutils 0.18_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: IGNORED: IS ONLY FOR I386, WHILE YOU ARE RUNNING AMD64 Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342011/asmutils-0.18_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: IGNORED: IS ONLY FOR I386, WHILE YOU ARE RUNNING AMD64 Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342013/asmutils-0.18_1.log - Port:devel/avr-libc 1.8.0_1,1 Buildgroup: 8.4-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342014/avr-libc-1.8.0_1,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (??? IN GRAPHICS/NETPBM) Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342015/netpbm-10.35.92.log Buildgroup: 9.2-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342016/avr-libc-1.8.0_1,1.log Buildgroup: 9.2-QAT/i386 Buildstatus: ??? Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342017/avr-libc-1.8.0_1,1.log - Port:devel/binutils 2.24 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342018/binutils-2.24.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342019/binutils-2.24.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342020/binutils-2.24.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342021/binutils-2.24.log - Port:devel/c-unit 1.1.1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342022/c-unit-1.1.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342023/c-unit-1.1.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342024/c-unit-1.1.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140529151000-34746-342025/c-unit-1.1.1.log - Port:devel/cross-binutils 2.23.2_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: IGNORED: YOU SHOULD DEFINE TGTARCH AND TGTABI TO BUILD PORT Buildgroup: 8.4-QAT/i386 Buildstatus: IGNORED: YOU SHOULD DEFINE TGTARCH AND TGTABI TO BUILD PORT Buildgroup: 9.2-QAT/amd64 Buildstatus: IGNORED: YOU SHOULD DEFINE TGTARCH AND TGTABI TO BUILD PORT Buildgroup: 9.2-QAT/i386 Buildstatus: IGNORED: YOU SHOULD DEFINE TGTARCH AND TGTABI TO BUILD PORT - Port:devel/cross-gcc 4.5.4_1 Buildgroup:
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 +-+ biology/seaview | 4.5.1 | 4.5.2 +-+ 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
Re: staging mail/heirloom-mailx [for review]
from Perry Hutchison per...@pluto.rain.com: I noticed that mail/heirloom-mailx is no longer maintained, and has not been staged. It looks straightforward. Did I miss anything? Yes, you missed something. mail/heirloom-mailx has been supsrseded by Steffen Daode Nurpmeso's S-nail. I haven't tried that yet, but remember a disturbing bug in heirloom-mailx; this was on Linux: e-newsletters from about.com each displayed as two messages. I don't know if this is fixed in S-nail. Try s-nail.sourceforge.net, you will be led to http://sdaoden.users.sourceforge.net/code.html Tom ___ 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] 355737: 4x leftovers
Fix build on 11-CURRENT (was otherwise failing due to using utmp instead of utmpx). Approved by:portmgr (bdrewery) - Build ID: 20140529194800-4149 Job owner: nwhiteh...@freebsd.org Buildtime: 5 days Enddate: Tue, 03 Jun 2014 11:29:49 GMT Revision: 355737 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355737 - Port:sysutils/condor 8.0.3 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~nwhiteh...@freebsd.org/20140529194800-4149-342394/condor-8.0.3.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~nwhiteh...@freebsd.org/20140529194800-4149-342395/condor-8.0.3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~nwhiteh...@freebsd.org/20140529194800-4149-342396/condor-8.0.3.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~nwhiteh...@freebsd.org/20140529194800-4149-342397/condor-8.0.3.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140529194800-4149 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
Re: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 2014-06-03 11:05, David Chisnall wrote: We are pleased to announce that the FreeBSD project has begin the transition from the GNATS bug-tracking system to Bugzilla. The Bugzilla installation can be found here: https://bugs.freebsd.org/bugzilla/ It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. No comment-by-email too, as far as I can tell. Are those features gone forever? Can I ask them to be restored, at least in some capacity? ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 Jun 2014, at 13:09, Vitaly Magerya vmage...@gmail.com wrote: It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. That is correct. The current leaning is towards not providing such functionality as: - It makes spamming easy - If someone can't be bothered to make an account, they are unlikely to provide the feedback required to correctly diagnose the bug. I don't know that this decision is final, but it's certainly unlikely to be high up the priority list to implement it. For FreeBSD 11, we'd like to have an HTTP-based send-pr replacement, which will not be able to enforce a valid email address, but which will at least request one. Although, again, we'll have to be careful to prevent it from being used as a spam tool (send a pr claiming to be from a different email address with a spam message and that person gets notified) and so it will likely add the bug to a private queue where it can be checked for spam before appearing in the main db. Volunteers to be spam filters welcome... No comment-by-email too, as far as I can tell. This is probably going to reappear at some point, if there is sufficient demand for it. David ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 2014-06-03 15:16, David Chisnall wrote: On 3 Jun 2014, at 13:09, Vitaly Magerya vmage...@gmail.com wrote: It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. That is correct. The current leaning is towards not providing such functionality as: - It makes spamming easy - If someone can't be bothered to make an account, they are unlikely to provide the feedback required to correctly diagnose the bug. Let my protest against such sweeping judgements be noted. No comment-by-email too, as far as I can tell. This is probably going to reappear at some point, if there is sufficient demand for it. I see. Consider me to be expressing the demand then. Anything that would allow me to participate without using an account would be very much appreciated. ___ 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: roundcube's switch to composer, anything plugin port maintainers should be doing?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Bethke ha scritto: I was in the process of upgrading a roundcube plugin (sauserprefs) and noticed that roundcube is switching/has swichted to composer. This is the first time I’ve come across composer. Should I ignore that for the moment? Is there work underway to convert the plugin ports to use composer? Should the plugin ports be removed in favor of using composer manually? Is composer production ready yet? Inquiring minds want to know… Hi Stefan, like you this is the first time I've come across 'composer'. It's a dependency manager, I have no plans to support it, you can ignore it for the moment. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlONwxgACgkQgRXp2M5fVU3XswCeLKaMnh4M+nh8FbEdFkjMp5Ny 0FwAn39S9AuaBzzezAE4XY3TAtoUSAJ7 =YSZ5 -END PGP SIGNATURE- ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 6/3/2014 14:41, Vitaly Magerya wrote: Anything that would allow me to participate without using an account would be very much appreciated. Why? You've already spent more energy protesting than it would have taken create an account. I have a feeling I'm going to cringe at an honest answer though. No spam please. If that means losing some feedback from anti-account folks, ok. John ___ 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: drop maintainership of 6 ports
Hello, devel/fpp i would take this one. Till now i wrote just some patches for PHP based ports. Whats the next step? Writing a patch to change maintainer? Greetings, Torsten ___ 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
Segfault while checking out port tree with devel/subversion
Hello,
I get segmentation fault while checking out port tree with
devel/subversion.
Following are result of my investigation:
1. With http: and https: checkout always causes segfault, while with
svn: it never happens.
2. Segfault happens only when checking out. Running 'svn cleanup'
and 'svn update' after segfault succeeds without any error.
3. It doesn't depend on server. Result is same with master(svn.FreeBSD.org)
and mirrors(svn0.{eu,us-east,us-west}.FreeBSD.org).
4. It doesn't depend on OS version. Result is same with 8.4R, 9.2R and
10.0R.
5. With svnlite(/usr/bin/svnlite) of 10.0R segfault never happens.
Does anyone experienced this?
---
Yasuhiro KIMURA
___
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: drop maintainership of 6 ports
Torsten Zuehlsdorff wrote: devel/fpp Whats the next step? Writing a patch to change maintainer? In a nutshell: 1. Check upstream to see if there's no newer version. If there is, try to update the port. 2. Change MAINTAINER, indeed. 3. If you can, mirror the distfile and add your site to MASTER_SITES. 4. See if the port has been stagified yet. If the Makefile still contains NO_STAGE=yes the port has not been stagified yet. In that case, it needs to be stagified asap. 5. Try to do as much testing as you can to see if there's anything else that needs to be done. Although a quick look suggests that this particular port appears to be in good shape. Thanks for offering to help out, AvW -- I'm not completely useless, I can be used as a bad example. pgp8NReJlZHrs.pgp Description: PGP signature
Re: Segfault while checking out port tree with devel/subversion
On 3 Jun 2014, at 07:59, Yasuhiro KIMURA y...@utahime.org wrote: Hello, I get segmentation fault while checking out port tree with devel/subversion. ... Does anyone experienced this? Yes, we are seeing the same thing, but a single cleanup doesn't always work for us. Sometimes we have to go through several svn up-cleanup-up-cleanup-... iterations to get an up-to-date ports tree. See this thread also: http://lists.freebsd.org/pipermail/freebsd-ports/2014-May/092269.html ___ 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: roundcube's switch to composer, anything plugin port maintainers should be doing?
Am 03.06.2014 um 14:44 schrieb Alex Dupre a...@freebsd.org: Signierter PGP Teil Stefan Bethke ha scritto: I was in the process of upgrading a roundcube plugin (sauserprefs) and noticed that roundcube is switching/has swichted to composer. This is the first time I’ve come across composer. Should I ignore that for the moment? Is there work underway to convert the plugin ports to use composer? Should the plugin ports be removed in favor of using composer manually? Is composer production ready yet? Inquiring minds want to know… Hi Stefan, like you this is the first time I've come across 'composer'. It's a dependency manager, I have no plans to support it, you can ignore it for the moment. The problem seems to be that plugin authors are moving to the new plugin repository, which is based around Composer. The original download link for sauserprefs is already gone. Unfortunately, for sauserprefs, there's only a snapshot version tagged (as I understand it), and the old version numbers for the plugin seem to have been abandoned. I could start doing dated snapshots from the plugins site on my own mirror, but this doesn't seem it's the right thing to do. I ll get in touch with my plugin's author to see what his take is on the situation. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
No comment-by-email too, as far as I can tell. This is probably going to reappear at some point, if there is sufficient demand for it. yes, this is probably a good idea, bug-followup@ or similar. Also, will send-pr still work? Anton ___ 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: Segfault while checking out port tree with devel/subversion
From: Jim Riggs freebsd-li...@christianserving.org Subject: Re: Segfault while checking out port tree with devel/subversion Date: Tue, 3 Jun 2014 08:15:50 -0500 Yes, we are seeing the same thing, but a single cleanup doesn't always work for us. Sometimes we have to go through several svn up-cleanup-up-cleanup-... iterations to get an up-to-date ports tree. See this thread also: http://lists.freebsd.org/pipermail/freebsd-ports/2014-May/092269.html Thank you for quick reply. I'll check it. --- Yasuhiro KIMURA ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 6/3/2014 14:41, Vitaly Magerya wrote: Anything that would allow me to participate without using an account would be very much appreciated. Why? For me it's easier to mail to bug-followup@ and to use send-pr than via an html browser. Indeed, in many cases the failures are such that there is no browser available no more. Using command line, simplest tools, might be best in such cases. Spamming is a problem, but we have to be resourceful and inventive to get the most of the new bugs system. Presumably the person dealing with a PR can easily delete obvious spam replies, or original spam PRs? Apologies if I'm talking bollocks. Anton ___ 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] 355805: 3x depend (distinfo_update in accessibility/atk), 1x leftovers
www/firefox-esr: explicitly use UNZIP_CMD This should have been included with a similar commit to www/firefox-i18n and www/seamonkey-i18n. Covered by general infrastructure blanket. - Build ID: 20140530092201-28827 Job owner: mar...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 14:16:58 GMT Revision: 355805 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355805 - Port:www/firefox-esr-i18n 24.5.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140530092201-28827-342738/firefox-esr-i18n-24.5.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (DISTINFO_UPDATE IN ACCESSIBILITY/ATK) Log: https://qat.redports.org//~mar...@freebsd.org/20140530092201-28827-342739/atk-2.8.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: DEPEND (DISTINFO_UPDATE IN ACCESSIBILITY/ATK) Log: https://qat.redports.org//~mar...@freebsd.org/20140530092201-28827-342740/atk-2.8.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: DEPEND (DISTINFO_UPDATE IN ACCESSIBILITY/ATK) Log: https://qat.redports.org//~mar...@freebsd.org/20140530092201-28827-342741/atk-2.8.0.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140530092201-28827 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
Re: drop maintainership of 6 ports
A.J. 'Fonz' van Werven wrote: Whats the next step? Writing a patch to change maintainer? In a nutshell: [snip] Which reminds me: if this is the first time you're actually going to be a maintainer, there's a thread on the Forums that you may find useful: https://forums.freebsd.org/viewtopic.php?f=5t=36243 AvW -- I'm not completely useless, I can be used as a bad example. pgpZmBt8wVhdl.pgp Description: PGP signature
[QAT] 355807: 4x leftovers
Stagify. - Build ID: 20140530092800-35273 Job owner: de...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 14:23:43 GMT Revision: 355807 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355807 - Port:graphics/py-graph-dot 1.8.2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-35273-342746/py27-graph-dot-1.8.2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-35273-342747/py27-graph-dot-1.8.2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-35273-342748/py27-graph-dot-1.8.2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-35273-342749/py27-graph-dot-1.8.2.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140530092800-35273 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] 355802: 4x depend (distinfo_update in accessibility/atk), 2x leftovers, 2x success
www/firefox(seamonkey)-i18n: explicitly use UNZIP_CMD The extraction of xpi requires zip (infozip to be precise). Rather than use variables EXTRACT_CMD and EXTRACT_BEFORE_ARGS, use UNZIP_CMD and the default -qo arguments to future-proof these ports (depending on the implemention, the original variables may default to tar arguments if they are defined at all). Covered by general infrastructure blanket. - Build ID: 20140530085201-3861 Job owner: mar...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 14:23:54 GMT Revision: 355802 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355802 - Port:www/firefox-i18n 29.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (DISTINFO_UPDATE IN ACCESSIBILITY/ATK) Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342726/atk-2.8.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (DISTINFO_UPDATE IN ACCESSIBILITY/ATK) Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342727/atk-2.8.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342728/firefox-i18n-29.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342729/firefox-i18n-29.0.log - Port:www/seamonkey-i18n 2.26 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (DISTINFO_UPDATE IN ACCESSIBILITY/ATK) Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342730/atk-2.8.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342731/seamonkey-i18n-2.26.log Buildgroup: 9.2-QAT/amd64 Buildstatus: DEPEND (DISTINFO_UPDATE IN ACCESSIBILITY/ATK) Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342732/atk-2.8.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~mar...@freebsd.org/20140530085201-3861-342733/seamonkey-i18n-2.26.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140530085201-3861 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] 355808: 4x leftovers
Stagify. - Build ID: 20140530092800-63872 Job owner: de...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 14:24:55 GMT Revision: 355808 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355808 - Port:graphics/py-graph 1.8.2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-63872-342750/py27-graph-1.8.2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-63872-342751/py27-graph-1.8.2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-63872-342752/py27-graph-1.8.2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~de...@freebsd.org/20140530092800-63872-342753/py27-graph-1.8.2.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140530092800-63872 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
Re: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 6/3/14, 5:16 AM, David Chisnall wrote: On 3 Jun 2014, at 13:09, Vitaly Magerya vmage...@gmail.com wrote: It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. That is correct. The current leaning is towards not providing such functionality as: - It makes spamming easy - If someone can't be bothered to make an account, they are unlikely to provide the feedback required to correctly diagnose the bug. I don't know that this decision is final, but it's certainly unlikely to be high up the priority list to implement it. For FreeBSD 11, we'd like to have an HTTP-based send-pr replacement, which will not be able to enforce a valid email address, but which will at least request one. Although, again, we'll have to be careful to prevent it from being used as a spam tool (send a pr claiming to be from a different email address with a spam message and that person gets notified) and so it will likely add the bug to a private queue where it can be checked for spam before appearing in the main db. Volunteers to be spam filters welcome... I think a bunch of this can be solved by using oauth or something like it. aka: login via github or facebook/twitter. -Alfred ___ 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: staging mail/heirloom-mailx [for review]
On 2014-06-03, Perry Hutchison per...@pluto.rain.com wrote:
PLIST_FILES= bin/${PORTNAME} \
+ man/man1/${PORTNAME}.1 \
@unexec if cmp -s %D/etc/nail.rc %D/etc/nail.rc.default; then
${RM} -f %D/etc/nail.rc; fi \
etc/nail.rc.default \
@exec [ -f %B/nail.rc ] || ${CP} %B/%f %B/nail.rc
You can replace this @exec/@unexec dance with @sample.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist-config.html
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist-keywords.html
--
Christian naddy Weisgerber na...@mips.inka.de
___
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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On Tue, 03 Jun 2014 07:50:33 -0700 Alfred Perlstein alf...@freebsd.org wrote: I think a bunch of this can be solved by using oauth or something like it. aka: login via github or facebook/twitter. Why not take it to the higher level, and force all FreeBSD users to replace /etc/master.passwd with Facebook login? :P -- Marko Cupać ___ 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
graphics/inventor needs new maintainer
Hi @All! Back in 2003 I ported Open Inventor to FreeBSD. Now, almost 11 years later my spare time is rather limited. I've already stopped following -current two years ago (I'm using 9.2 right now) and neither I have the environment (no FreeBSD-current, no FreeBSD-10, no poudriere, ...) nor the time to make/test staging support for that port so I think it's better to quit ownership of it. I hope there's anybody out there who can take care of it. Since the project owner (whoever that is, see http://http://oss.sgi.com/projects/inventor/) seems to no longer develop Open Inventor, maintaining that port needs almost no time. Just adapting it to the FreeBSD build environment (clang, pkgng, ...) is necessary. Thanks, Christian. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Alfred Perlstein wrote: On 6/3/14, 5:16 AM, David Chisnall wrote: On 3 Jun 2014, at 13:09, Vitaly Magerya vmage...@gmail.com wrote: It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. That is correct. The current leaning is towards not providing such functionality as: - It makes spamming easy - If someone can't be bothered to make an account, they are unlikely to provide the feedback required to correctly diagnose the bug. I don't know that this decision is final, but it's certainly unlikely to be high up the priority list to implement it. For FreeBSD 11, we'd like to have an HTTP-based send-pr replacement, which will not be able to enforce a valid email address, but which will at least request one. Although, again, we'll have to be careful to prevent it from being used as a spam tool (send a pr claiming to be from a different email address with a spam message and that person gets notified) and so it will likely add the bug to a private queue where it can be checked for spam before appearing in the main db. Volunteers to be spam filters welcome... I think a bunch of this can be solved by using oauth or something like it. aka: login via github or facebook/twitter. I for one would be highly opposed to it (facebook/twitter etc login) ... 3-4 years ago I went through 7 facebook accounts because of a vindictive little psycho kept reporting all my posts and accounts as abusive specifically to cause Facebook to delete my account... This then blocked the email address and telephone number from being used elsewhere and I lost several associated accounts as a result - including paid for services. I will never use such again, even a court order didn't get the (original) account reinstated or compensated. As for spamming, there are solutions - some make it more difficult than creating an account and logging in. That said I've had my fair share of spam through (verified email) logins... there is no easy solution, only less painful ones. :/ A tool that resides in the base OS for sending bug reports would be a good idea - even better if the tool reports basic OS parameters (uname -a, and an OS unique token) and the connecting IP (as seen by the receiving server) so that spammers cannot abuse it or be easily blocked. Just my $0.02 Michelle (from SORBS) -- Michelle Sullivan http://www.mhix.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] 355839: 4x leftovers
Staging support - Build ID: 20140530135200-45479 Job owner: ra...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 15:28:11 GMT Revision: 355839 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355839 - Port:dns/bindgraph 0.2_4 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ra...@freebsd.org/20140530135200-45479-342882/bindgraph-0.2_4.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ra...@freebsd.org/20140530135200-45479-342883/bindgraph-0.2_4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ra...@freebsd.org/20140530135200-45479-342884/bindgraph-0.2_4.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ra...@freebsd.org/20140530135200-45479-342885/bindgraph-0.2_4.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140530135200-45479 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
Re: Segfault while checking out port tree with devel/subversion
On Tue, 3 Jun 2014, Yasuhiro KIMURA wrote:
Hello,
I get segmentation fault while checking out port tree with
devel/subversion.
Following are result of my investigation:
1. With http: and https: checkout always causes segfault, while with
svn: it never happens.
2. Segfault happens only when checking out. Running 'svn cleanup'
and 'svn update' after segfault succeeds without any error.
3. It doesn't depend on server. Result is same with master(svn.FreeBSD.org)
and mirrors(svn0.{eu,us-east,us-west}.FreeBSD.org).
4. It doesn't depend on OS version. Result is same with 8.4R, 9.2R and
10.0R.
5. With svnlite(/usr/bin/svnlite) of 10.0R segfault never happens.
Does anyone experienced this?
Seen here (occasionally) when updating /usr/src on 10-stable. I suspect
www/serf, but it has always succeeded after svn cleanup, so I have not
pursued it. I use CPUTYPE?=core2 in /etc/make.conf, which might matter.
___
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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Vitaly Magerya wrote: On 2014-06-03 11:05, David Chisnall wrote: We are pleased to announce that the FreeBSD project has begin the transition from the GNATS bug-tracking system to Bugzilla. The Bugzilla installation can be found here: https://bugs.freebsd.org/bugzilla/ It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. No comment-by-email too, as far as I can tell. Are those features gone forever? Can I ask them to be restored, at least in some capacity? This is the first I have seen this GNATS to Bugzilla subject discussed. GNATS has been working just fine for many years, why the change to Bugzilla? Who makes this kind of change in a vacuum? WHO AUTHORIZED THIS Why was the ports mailing list not included in this before now? ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Hi! This is the first I have seen this GNATS to Bugzilla subject discussed. It was discussed on https://wiki.freebsd.org/Bugtracking since approx. 2004. GNATS has been working just fine for many years, why the change to Bugzilla? See the wiki page for the details. Who makes this kind of change in a vacuum? It was discussed on the committers list, and some people worked for a long time. WHO AUTHORIZED THIS The first mention to replace gnats with bugzilla apparently was around 2001 (yes, that long ago!) Why was the ports mailing list not included in this before now? It was mentioned on the ports@ list in the past, but there was no real 'driver' mentioned, but now it happened. The BSDCan 2014 meeting was the final trigger to switch over. So, it took a long time and now it happened. It will take a bit to get all the kinks out, but it looks like progress 8-) -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On Jun 3, 2014, at 8:23 AM, Michelle Sullivan miche...@sorbs.net wrote: Alfred Perlstein wrote: On 6/3/14, 5:16 AM, David Chisnall wrote: On 3 Jun 2014, at 13:09, Vitaly Magerya vmage...@gmail.com wrote: It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. That is correct. The current leaning is towards not providing such functionality as: - It makes spamming easy - If someone can't be bothered to make an account, they are unlikely to provide the feedback required to correctly diagnose the bug. I don't know that this decision is final, but it's certainly unlikely to be high up the priority list to implement it. For FreeBSD 11, we'd like to have an HTTP-based send-pr replacement, which will not be able to enforce a valid email address, but which will at least request one. Although, again, we'll have to be careful to prevent it from being used as a spam tool (send a pr claiming to be from a different email address with a spam message and that person gets notified) and so it will likely add the bug to a private queue where it can be checked for spam before appearing in the main db. Volunteers to be spam filters welcome... I think a bunch of this can be solved by using oauth or something like it. aka: login via github or facebook/twitter. I for one would be highly opposed to it (facebook/twitter etc login) ... 3-4 years ago I went through 7 facebook accounts because of a vindictive little psycho kept reporting all my posts and accounts as abusive specifically to cause Facebook to delete my account... This then blocked the email address and telephone number from being used elsewhere and I lost several associated accounts as a result - including paid for services. I will never use such again, even a court order didn't get the (original) account reinstated or compensated. As for spamming, there are solutions - some make it more difficult than creating an account and logging in. That said I've had my fair share of spam through (verified email) logins... there is no easy solution, only less painful ones. :/ A tool that resides in the base OS for sending bug reports would be a good idea - even better if the tool reports basic OS parameters (uname -a, and an OS unique token) and the connecting IP (as seen by the receiving server) so that spammers cannot abuse it or be easily blocked. Just my $0.02 Michelle (from SORBS) -- Michelle Sullivan http://www.mhix.org/ All of those parameters can easily be faked. Not sure how that would help. I still think using a form of oauth might help. Other options are email registration that results in an API key that those command line apps can use. That API key can be revoked by the bugzilla admins if needed. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 Jun 2014, at 16:18, Fbsd8 fb...@a1poweruser.com wrote: This is the first I have seen this GNATS to Bugzilla subject discussed. Then you have not been paying attention to any discussions for the past few years. Here, for example, is the Bugmeister team's entry in the status report from Q1 2013: http://www.freebsd.org/news/status/report-2013-01-2013-03.html#FreeBSD-Bugmeister-Team GNATS has been working just fine for many years No it hasn't. It's the most cited reason for people not to report bugs in FreeBSD and a lot of developers simply refuse to learn an antiquated system. Compare the number of bugs closed in the last two days (since Bugzilla went online) to the number in the last year and see. , why the change to Bugzilla? For the reasons outlined on these wiki pages: https://wiki.freebsd.org/Bugtracking/BugRelocationPlan https://wiki.freebsd.org/Bugzilla Who makes this kind of change in a vacuum? No one. The Bugmeister team made the change after spending several *years* consulting with the developer community. WHO AUTHORIZED THIS Core, after discussion with the developer community. Why was the ports mailing list not included in this before now? Huh? The discussions have taken place at DevSummits, on mailing lists, on IRC, and so on. Portmgr was involved in the migration process. They've been summarised in status reports. The one I cited earlier contains this: As always, anybody interested in helping out with the PR queue is welcome to join us in #freebsd-bugbusters on EFnet After many years of calls for help in this, people like Peter and Eitan actually did the (massive amount of) work required to move us to a modern bug-tracking system and *now* you choose to get involved, by screaming abuse at them? David ___ 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: Segfault while checking out port tree with devel/subversion
Am 03.06.2014 17:41, schrieb Warren Block:
On Tue, 3 Jun 2014, Yasuhiro KIMURA wrote:
Hello,
I get segmentation fault while checking out port tree with
devel/subversion.
Following are result of my investigation:
1. With http: and https: checkout always causes segfault, while with
svn: it never happens.
2. Segfault happens only when checking out. Running 'svn cleanup'
and 'svn update' after segfault succeeds without any error.
3. It doesn't depend on server. Result is same with
master(svn.FreeBSD.org)
and mirrors(svn0.{eu,us-east,us-west}.FreeBSD.org).
4. It doesn't depend on OS version. Result is same with 8.4R, 9.2R and
10.0R.
5. With svnlite(/usr/bin/svnlite) of 10.0R segfault never happens.
Does anyone experienced this?
Seen here (occasionally) when updating /usr/src on 10-stable. I suspect
www/serf, but it has always succeeded after svn cleanup, so I have not
pursued it. I use CPUTYPE?=core2 in /etc/make.conf, which might matter.
I have recently seen it (once) on a 9.2-STABLE-amd64 system running on
an AMD X2. No special flags or optimizations (especially no CPUTYPE)
are set on this box.
Regards, STefan
___
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: staging mail/heirloom-mailx [for review]
Am 03.06.2014 17:09, schrieb Christian Weisgerber:
On 2014-06-03, Perry Hutchison per...@pluto.rain.com wrote:
PLIST_FILES=bin/${PORTNAME} \
+man/man1/${PORTNAME}.1 \
@unexec if cmp -s %D/etc/nail.rc %D/etc/nail.rc.default; then
${RM} -f %D/etc/nail.rc; fi \
etc/nail.rc.default \
@exec [ -f %B/nail.rc ] || ${CP} %B/%f %B/nail.rc
You can replace this @exec/@unexec dance with @sample.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist-config.html
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist-keywords.html
I recently tried to find information on the semantics of the @sample
keyword, but could not easily find any ...
The pkg-create man-page contains just the (old) basic keywords, and
there is no man-page that mentions @sample or the other extensions.
Perhaps we should have a pkg-plist(5) that gives a concise overview
of all the relevant information found in the porters-handbook?
Regards, STefan
___
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] 355863: 4x leftovers
- Update to 1.6.923 - Add STAGE support PR: 190342 Submitted by: Muhammad Moinur Rahman 5u623...@gmail.com - Build ID: 20140530154800-24766 Job owner: w...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 16:38:53 GMT Revision: 355863 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355863 - Port:biology/p5-bioperl 1.6.923 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140530154800-24766-342974/p5-bioperl-1.6.923.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140530154800-24766-342975/p5-bioperl-1.6.923.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140530154800-24766-342976/p5-bioperl-1.6.923.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140530154800-24766-342977/p5-bioperl-1.6.923.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140530154800-24766 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
Re: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Le mar 3 jui 14 à 17:55:03 +0200, Alfred Perlstein bri...@mu.org écrivait : I still think using a form of oauth might help. OpenID? http://en.wikipedia.org/wiki/OpenID Regards, -- Th. Thomas. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
2014-06-03 14:16 GMT+02:00 David Chisnall thera...@freebsd.org: On 3 Jun 2014, at 13:09, Vitaly Magerya vmage...@gmail.com wrote: It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. That is correct. The current leaning is towards not providing such functionality as: - It makes spamming easy - If someone can't be bothered to make an account, they are unlikely to provide the feedback required to correctly diagnose the bug. I don't know that this decision is final, but it's certainly unlikely to be high up the priority list to implement it. For FreeBSD 11, we'd like to have an HTTP-based send-pr replacement, which will not be able to enforce a valid email address, but which will at least request one. Although, again, we'll have to be careful to prevent it from being used as a spam tool (send a pr claiming to be from a different email address with a spam message and that person gets notified) and so it will likely add the bug to a private queue where it can be checked for spam before appearing in the main db. Volunteers to be spam filters welcome... Please reconsider this. I have come up with bug reports for various projects only to find out that I'd need YET ANOTHER FRIGGING PASSWORD just to send them my bug report. In the end, the report was not send, as yes, I cannot be bothered to create another account that I'll use essentially for sending an email. I'm surely not the only one avoiding even more accounts and password. At the very least think about implementing OAuth/OpenID or whatever it's called this days. A mood point for me, as I'll need a full account, but the Project should not make reporting bugs harder than it is already ... have you considered using reCATPCHA or something to fend of at least some of the spam? Cheers and thanks for the migration!! Uli ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 03/06/2014 13:16, David Chisnall wrote: Volunteers to be spam filters welcome... Here's one :) -- Regards, Gary J. Hayers g...@hayers.org PGP Signature http://www.hayers.org/pgp In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 6/3/2014 18:57, Ulrich Spörlein wrote: 2014-06-03 14:16 GMT+02:00 David Chisnall thera...@freebsd.org: A mood point for me, as I'll need a full account, but the Project should not make reporting bugs harder than it is already ... have you considered using reCATPCHA or something to fend of at least some of the spam? Both ineffective and highly annoying continuously, not just one time like registration is. If there's a vote between captcha-any-flavor and registration, I'll vote for the latter every single time. I'm with Chisnall - it's doubtful most folks unwilling to register are about to make a meaningful report. And it's pretty much the standard today. What can you still post on anonymously / no registration that isn't policed by humans 24/7? Not much that I can think of. John ___ 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] 355878: 4x leftovers
Update math/R-cran-gss to 2.1-0. ChangeLog: * R: i) Tuned Newton iteration algorithms in ngreg and ngreg.proj. ii) Bug fixes in routines involving univariate minimization via nlm0. iii) Minor changes in makedata.x's. - Build ID: 20140530173000-41568 Job owner: d...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 17:13:32 GMT Revision: 355878 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355878 - Port:math/R-cran-gss 2.1.1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140530173000-41568-343030/R-cran-gss-2.1.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140530173000-41568-343031/R-cran-gss-2.1.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140530173000-41568-343032/R-cran-gss-2.1.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140530173000-41568-343033/R-cran-gss-2.1.1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140530173000-41568 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
Re: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 03 Jun 2014, at 19:11, John Marino freebsd.cont...@marino.st wrote: On 6/3/2014 18:57, Ulrich Spörlein wrote: 2014-06-03 14:16 GMT+02:00 David Chisnall thera...@freebsd.org: A mood point for me, as I'll need a full account, but the Project should not make reporting bugs harder than it is already ... have you considered using reCATPCHA or something to fend of at least some of the spam? Both ineffective and highly annoying continuously, not just one time like registration is. If there's a vote between captcha-any-flavor and registration, I'll vote for the latter every single time. I'm with Chisnall - it's doubtful most folks unwilling to register are about to make a meaningful report. And it's pretty much the standard today. What can you still post on anonymously / no registration that isn't policed by humans 24/7? Not much that I can Phabric.freebsd.org also allows to sign up using github and twitter, I would like to see the same for bugzilla (and maybe some other option like g+). ___ 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: Citrix Ica Port Permissions Problem
I'm not sure, but it looks like citrix_ica requires the setupwfc to run, which it won't because it is on FreeBSD. When I run just the wfica client, it cannot find libgtk-x11-2.0.so.0, which does already exist in /usr/local/lib. It seems like either it is not linking during the install, or it requires that something happen post install, which cannot actually happen on FreeBSD. /usr/local/ICAClient/wfica: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory Has anyone been able to get this port to work? The citrix_xenapp did work before. Thanks, Aric ___ 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
Thanks!
Just a big thanks to all ports maintainers and helpful fellow mailing list participants. Without your prompt responses and voluntary activities we (at least I) can run a stable updated OS and programs. Keep up the good work! Jos Chrispijn ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 June 2014 10:11, John Marino freebsd.cont...@marino.st wrote: ... it's doubtful most folks unwilling to register are about to make a meaningful report... This is *not* the reason for registation. The reason for registation is that we know from experience that having a way to talk with the reporter drastically increases the chance that the bug will get fixed. Registration offers verification of the submitters email. We would rather get fewer higher quality and more engaged bugs than what we've had in the past where bugs were a one way vent. To preempt the next question: why don't we allow users to submit via email but verify with a token? That system isn't possible with how the gateway is set up now. Its a long term possability. If someone wants to help set that up please contact me offline (at bugmeister@). What about bug followups via email? That one won't be supported for a bit as we get used to bugzilla. It certainly on the cards to support in the future. -- Eitan Adler ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On Tue, Jun 03, 2014 at 11:11:29AM -0700, Eitan Adler wrote: What about bug followups via email? That one won't be supported for a bit as we get used to bugzilla. It certainly on the cards to support in the future. I initially thought this would be a problem for me, but even in 24 hours of working with it, I've wrapped my head around it. I agree IWBN long-term. OTOH I will state as prior long-term GNATS maintainer that several times a week the email discussions had to be edited and/or forwarded to make sure they showed up in the Audit-Trail. That's been going on for years. It's a task I won't miss. mcl ___ 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
databases/sqldeveloper: observations questions
Hi. First off, a big thanks to who whoever ported this, it's a nice piece of software. I wanted to share some observations plus questions. * I have JAVA_PREFERRED_PORTS=JAVA_PORT_NATIVE_OPENJDK_JDK_1_8. Although sqldeveloper complains on startup that max logical version is =1.8, my finding is that defining SetJavaHome to openjdk7 actually does worse - Xorg freezes and needs to be restarted. openjdk 1.8+ is working quite well (on 11-C). * After starting sqldeveloper, I wanted to install plugins (Help Check Updates Updates), in particular CVS_Support. This failed due to insufficient privileges. So unlike NetBeans, sqldeveloper is trying to install some of the binaries under /usr/local? * Being the genius that I am, I did a temporary chown to my user of folder /usr/local/share/java/sqldeveloper. Plugins started to install but gave an error message at some point. Starting sqldeveloper -verbose after this step crashes with below: at org.netbeans.core.netigso.Netigso.findResources(Netigso.java:379) at org.netbeans.NetigsoModule.findResources(NetigsoModule.java:177) at org.netbeans.core.startup.NbInstaller.loadLayers(NbInstaller.java:625) at org.netbeans.core.startup.NbInstaller.loadImpl(NbInstaller.java:356) at org.netbeans.core.startup.NbInstaller.access$000(NbInstaller.java:105) at org.netbeans.core.startup.NbInstaller$1.run(NbInstaller.java:346) at org.openide.filesystems.FileUtil$2.run(FileUtil.java:431) at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:127) at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:609) at org.openide.filesystems.FileUtil.runAtomicAction(FileUtil.java:415) at org.openide.filesystems.FileUtil.runAtomicAction(FileUtil.java:435) at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:343) at org.netbeans.ModuleManager.enable(ModuleManager.java:1188) at org.netbeans.ModuleManager.enable(ModuleManager.java:1011) at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:340) at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:276) at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:301) at org.netbeans.core.startup.Main.getModuleSystem(Main.java:181) at org.netbeans.core.startup.Main.getModuleSystem(Main.java:150) at org.netbeans.core.startup.Main.start(Main.java:307) at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:123) at java.lang.Thread.run(Thread.java:745) Error: SQL Developer can't recognize the JDK version * I started NetBeans as well, but did not find any comparabel plugins with what I was trying to install in sqldeveloper. So my point is, 1. Has anyone found a way to install the plugins? 2. This software seems to share a lot with NetBeans. Maybe it's possible to import sqldeveloper as a NetBeans project? It may also be possible to install the sqldeveloper plugins under ~/.netbeans together with other oracle_java modules as the modules appear quite similar. Thanks again. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/databases-sqldeveloper-observations-questions-tp5917484.html Sent from the freebsd-ports mailing list archive at Nabble.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] 355936: 4x leftovers
- Stage support [1] - Update to 2.4.0 [1] - Reset maintainer to ports@ PR: 190365 [1] Submitted by: Muhammad Moinur Rahman 5u623...@gmail.com [1] - Build ID: 20140531052600-25498 Job owner: w...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 19:03:23 GMT Revision: 355936 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355936 - Port:math/rpy2 2.4.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052600-25498-343262/rpy2-2.4.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052600-25498-343263/rpy2-2.4.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052600-25498-343264/rpy2-2.4.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052600-25498-343265/rpy2-2.4.0.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140531052600-25498 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
x11/xterm: no coloured prompt and characters after update (BLIND!)
After today's update of port x11/xterm from xterm-304 to xterm-305, the terminals I start on the desktop (windowmaker) do not show any coloured prompt or characters - they have the same colour as the background! Flying blind! This is somehow boring! The only way to get some coloured (and therefor visible) characters is to select from VT Font menu within the xterm Use True Type - then giant chars show up, but they are coloured as expected. signature.asc Description: PGP signature
Re: Firefox chokes up for several seconds... frequently
In message 51901.1401770...@server1.tristatelogic.com, I wrote: I wrote: Since I last updated my ports a couple of weeks ago, the problem has gotten DRAMATICALLY worse. Now Firefox is choking up frequently, and for perhaps 10-20 second each time, on virutally every web site that I visit. NEVERMIND! I manually rebuilt and re-installed the nspluginwrapper and now everything with Firefox seems to magically be working A-OK again. I spoke too soon. The problem is back again. As a friend of mine used to say Problems that go away by themselves come back by themselves. I am still desperately seeking assistance to fix this problem. I have done everything I can to follow the Handbook instructions to the letter and Firefox is still choking up on the vast majority of web sites. (Apparently, almost every site on the Interwebs these days has a s**t load of embedded flash crap on it, you know, to make it look fancy schmancy. I think this is absurdly stupid, but what do I know?) ___ 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
A simple ports question
Functionally, what is the difference between: pkg_delete Y and: cd /usr/ports/X/Y; make deinstall ? P.S. Yes, yes. I know. I am _supposed_ to be only using pkgng, but if you are able to do so, please answer my question anyway. ___ 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] 355935: 4x leftovers
- Stage support [1] - Reset maintainer to ports@ PR: 190358 [1] Submitted by: Muhammad Moinur Rahman 5u623...@gmail.com [1] - Build ID: 20140531052200-15986 Job owner: w...@freebsd.org Buildtime: 4 days Enddate: Tue, 03 Jun 2014 19:09:36 GMT Revision: 355935 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355935 - Port:math/rpy 1.0.3_32 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052200-15986-343258/rpy-1.0.3_32.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052200-15986-343259/rpy-1.0.3_32.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052200-15986-343260/rpy-1.0.3_32.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~w...@freebsd.org/20140531052200-15986-343261/rpy-1.0.3_32.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140531052200-15986 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
Re: A simple ports question
On Tue, Jun 03, 2014 at 12:09:10PM -0700, Ronald F. Guilmette wrote: Functionally, what is the difference between: pkg_delete Y and: cd /usr/ports/X/Y; make deinstall ? none regards, Bapt pgpkJnM6GHEvc.pgp Description: PGP signature
[QAT] 355947: 4x leftovers
* Support STAGE * Update to latest version: 1.1.3. Approved by:wg (mentor) - Build ID: 20140531084200-18678 Job owner: ale...@freebsd.org Buildtime: 3 days Enddate: Tue, 03 Jun 2014 19:28:20 GMT Revision: 355947 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=355947 - Port:net-mgmt/percona-monitoring-plugins 1.1.3 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ale...@freebsd.org/20140531084200-18678-343310/percona-monitoring-plugins-1.1.3.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ale...@freebsd.org/20140531084200-18678-343311/percona-monitoring-plugins-1.1.3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ale...@freebsd.org/20140531084200-18678-343312/percona-monitoring-plugins-1.1.3.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~ale...@freebsd.org/20140531084200-18678-343313/percona-monitoring-plugins-1.1.3.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140531084200-18678 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
Re: staging mail/heirloom-mailx [for review]
On Tue, Jun 3, 2014 at 2:37 AM, Perry Hutchison per...@pluto.rain.com wrote:
I noticed that mail/heirloom-mailx is no longer maintained, and has
not been staged.
It looks straightforward. Did I miss anything?
--- Makefile2014-05-31 21:58:23.0 -0700
+++ Makefile-staged 2014-06-03 00:34:03.0 -0700
@@ -8,7 +8,7 @@
MASTER_SITES= SF/heirloom/heirloom-${PORTNAME}/${PORTVERSION}
PKGNAMEPREFIX= heirloom-
-MAINTAINER=po...@freebsd.org
+MAINTAINER=per...@pluto.rain.com
COMMENT= BSD mail utility with MIME, IMAP, POP3, SMTP, and S/MIME
extensions
OPTIONS_DEFINE=IPV6 DOCS
@@ -25,10 +25,10 @@
CPPFLAGS=${CPPFLAGS} \
LDFLAGS=${LDFLAGS}
-MAN1= ${PORTNAME}.1
PORTDOCS= AUTHORS COPYING ChangeLog README TODO
PLIST_FILES= bin/${PORTNAME} \
+ man/man1/${PORTNAME}.1 \
@unexec if cmp -s %D/etc/nail.rc %D/etc/nail.rc.default;
then ${RM} -f %D/etc/nail.rc; fi \
etc/nail.rc.default \
@exec [ -f %B/nail.rc ] || ${CP} %B/%f %B/nail.rc
@@ -36,7 +36,6 @@
CPPFLAGS+= -I${LOCALBASE}/include
LDFLAGS+= -L${LOCALBASE}/lib
-NO_STAGE= yes
.include bsd.port.options.mk
.if ${PORT_OPTIONS:MIPV6}
@@ -44,16 +43,13 @@
.endif
do-install:
- ${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${PREFIX}/bin
- ${INSTALL_MAN} ${WRKSRC}/${MAN1} ${MAN1PREFIX}/man/man1
- ${INSTALL_DATA} ${WRKSRC}/nail.rc ${PREFIX}/etc/nail.rc.default
-.if !exists(${PREFIX}/etc/nail.rc)
- ${INSTALL_DATA} ${WRKSRC}/nail.rc ${PREFIX}/etc
-.endif
+ ${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${STAGEDIR}${PREFIX}/bin
+ ${INSTALL_MAN} ${WRKSRC}/${PORTNAME}.1
${STAGEDIR}${MAN1PREFIX}/man/man1
+ ${INSTALL_DATA} ${WRKSRC}/nail.rc
${STAGEDIR}${PREFIX}/etc/nail.rc.default
Install nail.rc as nail.rc.sample and then use the @sample keyword in
your PLIST_FILES.
.if ${PORT_OPTIONS:MDOCS}
- @${MKDIR} ${DOCSDIR}
+ @${MKDIR} ${STAGEDIR}${DOCSDIR}
.for i in ${PORTDOCS}
- ${INSTALL_DATA} ${WRKSRC}/${i} ${DOCSDIR}
+ ${INSTALL_DATA} ${WRKSRC}/${i} ${STAGEDIR}${DOCSDIR}
.endfor
.endif
___
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
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
___
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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Am 03.06.2014 14:09, schrieb Vitaly Magerya: On 2014-06-03 11:05, David Chisnall wrote: We are pleased to announce that the FreeBSD project has begin the transition from the GNATS bug-tracking system to Bugzilla. The Bugzilla installation can be found here: https://bugs.freebsd.org/bugzilla/ It doesn't seem to be possible to post comments (or bugs) without creating an account and logging in. No comment-by-email too, as far as I can tell. I'd cast a vote against such features. I've made that experiment upstream in a project unrelated to FreeBSD, and received too many hit-and-run-style bug reports of anonymous posters that were insufficient. I asked questions back and did not receive a response, for whatever reason - and if that the reporter never checked if I commented on their bug, frustration, having moved on to other projects, you never know. Wasted time for bugs never found, never fixed. While having a valid-looking email address from a submitter does not guarantee a reply when developers have further questions, at least it raises the chance that the submitter (reporter) knows more information is needed. Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. ___ 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: Firefox chokes up for several seconds... frequently
Ronald F. Guilmette wrote: In message 51901.1401770...@server1.tristatelogic.com, I wrote: I wrote: Since I last updated my ports a couple of weeks ago, the problem has gotten DRAMATICALLY worse. Now Firefox is choking up frequently, and for perhaps 10-20 second each time, on virutally every web site that I visit. NEVERMIND! I manually rebuilt and re-installed the nspluginwrapper and now everything with Firefox seems to magically be working A-OK again. I spoke too soon. The problem is back again. As a friend of mine used to say Problems that go away by themselves come back by themselves. I am still desperately seeking assistance to fix this problem. I have done everything I can to follow the Handbook instructions to the letter and Firefox is still choking up on the vast majority of web sites. (Apparently, almost every site on the Interwebs these days has a s**t load of embedded flash crap on it, you know, to make it look fancy schmancy. I think this is absurdly stupid, but what do I know?) Try changing gfx.xrender.enabled from True to False in about:config. This solved a similar problem with scaled images for me a couple years ago. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Matthias Andree wrote: Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: https://bugs.freebsd.org/86522 https://bugs.freebsd.org/163733 https://bugs.freebsd.org/182551 Those bugs would simply not have been submitted if I had to create an account first. I strongly support anonymous bug reporting, but I'm not interested in a protracted discussion on it. The comitters can decide if they want trivial bugs reported or not as they prefer. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 6/3/2014 22:06, Stephen Hurd wrote: Matthias Andree wrote: Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: Those bugs would simply not have been submitted if I had to create an account first. If the submitter's interest in getting the bug known in order to be fixed exceeds the distaste for registration, then yes, the report would still get submitted. (For example, if that person *really* wants to access FreeBSD forums via IPv6 and nobody knows it's busted, they would probably bite the bullet). If nobody else that has an account already bothers to report it, it must not really be that big of an issue. I strongly support anonymous bug reporting, but I'm not interested in a protracted discussion on it. The comitters can decide if they want trivial bugs reported or not as they prefer. I don't concede killing anonymous means killing trivial bug reporting, but if that was the case: Oh well, I guess we have to focus on non-trivial bugs. John ___ 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
x11/xcb program unusable after upgrading to latest ports
I have a problem with xcb since updating my ports. The program starts up ok but the frame where the data in the cut buffer is displayed is so tiny that any data placed into the cutbuffer can't be read. Is anyone else seeing this behavior? Note that I am now seeing this on both my 9.2-stable and 10.0-stable systems. Thanks, Bob -- Bob Willcox| TRUST ME: b...@immure.com | Translation of the Latin caveat emptor. Austin, TX | ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 June 2014 13:41, John Marino freebsd.cont...@marino.st wrote: On 6/3/2014 22:06, Stephen Hurd wrote: Matthias Andree wrote: Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: Those bugs would simply not have been submitted if I had to create an account first. This is a legitimite concern. This is exactly why we have anonymous bug reporting on at the moment. On the hand we're *already* seeing tens of spam per hour via this exact mechanism. If the submitter's interest in getting the bug known in order to be fixed exceeds the distaste for registration, then yes, the report would still get submitted. This is true. (For example, if that person *really* wants to access FreeBSD forums via IPv6 and nobody knows it's busted, they would probably bite the bullet). There are also other mechanisms. For example, mailing lists. If nobody else that has an account already bothers to report it, it must not really be that big of an issue. This is the wrong rhetoric to be using here. We explicitly *don't* believe this is true. The concern from bugmeister's side is that we want to make sure that the bug database is *useful*. We know that some low-effort no-reply-needed bugs come in. This is true for both ports and doc. It is slightly less true in src but not non-existent in source. On the other hand the question is does this value outweigh the the value of knowing that the submitter has a valid email address. I strongly support anonymous bug reporting, but I'm not interested in a protracted discussion on it. The comitters can decide if they want trivial bugs reported or not as they prefer. At the moment this is absolutely enabled. On the other hand we will be closely watching these types of bugs. I'm not sure we have meta-data to track the source of an account (anon-report, or not) but we will soon. I don't concede killing anonymous means killing trivial bug reporting, but if that was the case: Oh well, I guess we have to focus on non-trivial bugs. Trivial bugs are important too. -- Eitan Adler ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 03 Jun 2014, at 22:41, John Marino freebsd.cont...@marino.st wrote: On 6/3/2014 22:06, Stephen Hurd wrote: Matthias Andree wrote: Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: Those bugs would simply not have been submitted if I had to create an account first. If the submitter's interest in getting the bug known in order to be fixed exceeds the distaste for registration, then yes, the report would still get submitted. (For example, if that person *really* wants to access FreeBSD forums via IPv6 and nobody knows it's busted, they would probably bite the bullet). Ah, is that the reason why I had so many issues with it lately? Could bugzilla maybe allow email verified submissions without an account? So you report a bug with your email address and have to click verify in an email response to get it to a state people will look at it. That would eliminate the whole oh no, one more account/password hassle, but reduce spam and lack of working back channels. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 June 2014 13:51, Michael Gmelin gre...@freebsd.org wrote: On 03 Jun 2014, at 22:41, John Marino freebsd.cont...@marino.st wrote: On 6/3/2014 22:06, Stephen Hurd wrote: Matthias Andree wrote: Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: Those bugs would simply not have been submitted if I had to create an account first. If the submitter's interest in getting the bug known in order to be fixed exceeds the distaste for registration, then yes, the report would still get submitted. (For example, if that person *really* wants to access FreeBSD forums via IPv6 and nobody knows it's busted, they would probably bite the bullet). Ah, is that the reason why I had so many issues with it lately? Duno. If you can, please file a bug and let us know :) Could bugzilla maybe allow email verified submissions without an account? So you report a bug with your email address and have to click verify in an email response to get it to a state people will look at it. That would eliminate the whole oh no, one more account/password hassle, but reduce spam and lack of working back channels. See above: === To preempt the next question: why don't we allow users to submit via email but verify with a token? That system isn't possible with how the gateway is set up now. Its a long term possability. If someone wants to help set that up please contact me offline (at bugmeister@). === -- Eitan Adler ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 03 Jun 2014, at 22:52, Eitan Adler li...@eitanadler.com wrote: On 3 June 2014 13:51, Michael Gmelin gre...@freebsd.org wrote: On 03 Jun 2014, at 22:41, John Marino freebsd.cont...@marino.st wrote: On 6/3/2014 22:06, Stephen Hurd wrote: Matthias Andree wrote: Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: Those bugs would simply not have been submitted if I had to create an account first. If the submitter's interest in getting the bug known in order to be fixed exceeds the distaste for registration, then yes, the report would still get submitted. (For example, if that person *really* wants to access FreeBSD forums via IPv6 and nobody knows it's busted, they would probably bite the bullet). Ah, is that the reason why I had so many issues with it lately? Duno. If you can, please file a bug and let us know :) Will test later from my home line... Could bugzilla maybe allow email verified submissions without an account? So you report a bug with your email address and have to click verify in an email response to get it to a state people will look at it. That would eliminate the whole oh no, one more account/password hassle, but reduce spam and lack of working back channels. See above: === To preempt the next question: why don't we allow users to submit via email but verify with a token? That system isn't possible with how the gateway is set up now. Its a long term possability. If someone wants to help set that up please contact me offline (at bugmeister@). === Well, I didn't mean *via* email, but specifying a valid email address in a web form. This could be done using the old web form on freebsd.org and using an email verification loop that holds submissions outside of bugzilla until the verification link has been clicked. I don't know any details of the current setup, but I would assume this is quite doable. -- Eitan Adler ___ 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-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: A simple ports question
On 2014-06-03, Ronald F. Guilmette r...@tristatelogic.com wrote: Functionally, what is the difference between: pkg_delete Y and: cd /usr/ports/X/Y; make deinstall ? The latter calls the former. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 June 2014 10:11, John Marino freebsd.cont...@marino.st wrote: ... it's doubtful most folks unwilling to register are about to make a meaningful report... This is *not* the reason for registation. The reason for registation is that we know from experience that having a way to talk with the reporter drastically increases the chance that the bug will get fixed. Registration offers verification of the submitters email. We would rather get fewer higher quality and more engaged bugs than what we've had in the past where bugs were a one way vent. To preempt the next question: why don't we allow users to submit via email but verify with a token? That system isn't possible with how the gateway is set up now. Its a long term possability. If someone wants to help set that up please contact me offline (at bugmeister@). What about bug followups via email? That one won't be supported for a bit as we get used to bugzilla. It certainly on the cards to support in the future. Will send-pr continue to work or not? Anton ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 June 2014 14:40, Anton Shterenlikht me...@bris.ac.uk wrote: Will send-pr continue to work or not? From the announce email === The send-pr script will continue functioning as a compatibility interface, but it is not guaranteed to run in a timely fashion (currently, importing bugs submitted via send-pr involves a manual step). === -- Eitan Adler ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
There are also other mechanisms. For example, mailing lists. We were repeatedly told in this list that the preferred way to let people know of the issue is to file a PR. Posting something to ports@ is the easiest route (for me, at least), however, I take the trouble to use the send-pr route. Registration is not the issue, it's the need to login every time and having to store yet another passwd that is frustrating. I get the spam issue, but perhaps the fact that the ability to send PRs with no extra login step is highly valued by some, deserves another thought. Anton ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Could bugzilla maybe allow email verified submissions without an account? So you report a bug with your email address and have to click verify in an email response to get it to a state people will look at it. That would eliminate the whole oh no, one more account/password hassle, but reduce spam and lack of working back channels. Or what about a concept of a registered FreeBSD user? Some sort of a database of users known to the project. So that the info in send-pr will be enough to accept a PR, perhaps with another id field or similar? This still wouldn't allow anonymous posting, but will remove the need to login each time. Anton ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On Tue, 3 Jun 2014 13:52:36 -0700 Eitan Adler li...@eitanadler.com wrote: On 3 June 2014 13:51, Michael Gmelin gre...@freebsd.org wrote: On 03 Jun 2014, at 22:41, John Marino freebsd.cont...@marino.st wrote: On 6/3/2014 22:06, Stephen Hurd wrote: Matthias Andree wrote: Surely there may be valid and sometimes useful comments by people who aren't the original reporter, but for the common case that the bug evolves into a discussion between a developer and a reporter having a valid BIDIRECTIONAL communications channel up front helps a lot. I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: Those bugs would simply not have been submitted if I had to create an account first. If the submitter's interest in getting the bug known in order to be fixed exceeds the distaste for registration, then yes, the report would still get submitted. (For example, if that person *really* wants to access FreeBSD forums via IPv6 and nobody knows it's busted, they would probably bite the bullet). Ah, is that the reason why I had so many issues with it lately? Duno. If you can, please file a bug and let us know :) Yep, seems like IPv6 is broken. Got my bugzilla account working, but couldn't find the forums as a component. Opened a bug to get the component in so I can file a bug :) -- 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 June 2014 15:03, Anton Shterenlikht me...@bris.ac.uk wrote: Could bugzilla maybe allow email verified submissions without an account? So you report a bug with your email address and have to click verify in an email response to get it to a state people will look at it. That would eliminate the whole oh no, one more account/password hassle, but reduce spam and lack of working back channels. Or what about a concept of a registered FreeBSD user? Some sort of a database of users known to the project. So that the info in send-pr will be enough to accept a PR, perhaps with another id field or similar? This exits. send-pr will use your email account if it exists. This still wouldn't allow anonymous posting, but will remove the need to login each time. An interesting idea would be to have send-pr reject email from accounts that don't exist (as opposed to creating them). We'll consider this as time goes on. -- Eitan Adler ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 3 June 2014 14:58, Anton Shterenlikht me...@bris.ac.uk wrote: There are also other mechanisms. For example, mailing lists. We were repeatedly told in this list that the preferred way to let people know of the issue is to file a PR. Posting something to ports@ is the easiest route (for me, at least), however, I take the trouble to use the send-pr route. Registration is not the issue, it's the need to login every time and having to store yet another passwd that is frustrating. We understand this. We expected this. I hope you understand our concern about the need to have an email that confirmed valid. At the moment anon-email works. We will be closely watching this space. I get the spam issue, but perhaps the fact that the ability to send PRs with no extra login step is highly valued by some, deserves another thought. This isn't about spam but about the need to engage bug reporters. -- Eitan Adler ___ 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] 356008: 4x leftovers, 20x success
Mark GKrellM 1.X as DEPRECATED. Approved by:portmgr (implicit) - Build ID: 20140531191401-59511 Job owner: u...@freebsd.org Buildtime: 3 days Enddate: Tue, 03 Jun 2014 22:52:53 GMT Revision: 356008 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=356008 - Port:audio/gkrellmms 0.5.8_10 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343630/gkrellmms-0.5.8_10.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343631/gkrellmms-0.5.8_10.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343632/gkrellmms-0.5.8_10.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343633/gkrellmms-0.5.8_10.log - Port:audio/gkrellmvolume 0.8_8 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343634/gkrellmvolume-0.8_8.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343635/gkrellmvolume-0.8_8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343636/gkrellmvolume-0.8_8.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343637/gkrellmvolume-0.8_8.log - Port:misc/gkrellmfmonitor 0.3_8 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343638/gkrellmfmonitor-0.3_8.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343639/gkrellmfmonitor-0.3_8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343640/gkrellmfmonitor-0.3_8.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343641/gkrellmfmonitor-0.3_8.log - Port:misc/gkrellmlaunch 0.4_8 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343642/gkrellmlaunch-0.4_8.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343643/gkrellmlaunch-0.4_8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343644/gkrellmlaunch-0.4_8.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343645/gkrellmlaunch-0.4_8.log - Port:misc/gkrellshoot 0.3.2_9 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343646/gkrellshoot-0.3.2_9.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343647/gkrellshoot-0.3.2_9.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343648/gkrellshoot-0.3.2_9.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343649/gkrellshoot-0.3.2_9.log - Port:sysutils/gkrellm 1.2.13_11 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343650/gkrellm-1.2.13_11.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~u...@freebsd.org/20140531191401-59511-343651/gkrellm-1.2.13_11.log Buildgroup: 9.2-QAT/amd64
Re: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
Eitan Adler wrote: On 3 June 2014 10:11, John Marino freebsd.cont...@marino.st wrote: ... it's doubtful most folks unwilling to register are about to make a meaningful report... This is *not* the reason for registation. The reason for registation is that we know from experience that having a way to talk with the reporter drastically increases the chance that the bug will get fixed. Registration offers verification of the submitters email. +1 ... actually +~ ... been there done than... at SORBS (attacked on a daily basis at times)... I went with the following that FreeBSD might find useful: 1/ No login, no information (static pages only) 2/ No Login + Catpcha (self generated, tho reCaptcha would work), limited information and rate limiting (on IP address) 3/ Login - email verified, admin *not verified* (ie general user) .. a little more information than in (2) and rate limits increased (and not limited to IP - though changing IP will require re-login). 4/ Login - email verified - admin verified (ie: privileged user) .. full (almost - based on permissions) access... rate limiting removed. how I could see that apply to FreeBSD (using the same numbering): 1/ static pages only 2/ can view a bug (and *maybe* log a bug - a single bug per day/week/month) 3/ can log a bug and view a bug 4/ can work on a bug, log a bug and view a bug. We would rather get fewer higher quality and more engaged bugs than what we've had in the past where bugs were a one way vent. To preempt the next question: why don't we allow users to submit via email but verify with a token? That system isn't possible with how the gateway is set up now. Its a long term possability. If someone wants to help set that up please contact me offline (at bugmeister@). I'm happy to help setup all sorts of anti-spam systems - feel free to mail me offlist. What about bug followups via email? Possibly a problem (but not really - if you're not the originator of the bug, and not logged in, you can't update it at all..) That one won't be supported for a bit as we get used to bugzilla. It certainly on the cards to support in the future. Michelle -- Michelle Sullivan http://www.mhix.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: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On Tue, Jun 03, 2014 at 10:59:54PM +0200, Michael Gmelin wrote: Well, I didn't mean *via* email, but specifying a valid email address in a web form. This could be done using the old web form on freebsd.org and using an email verification loop Hmm. Well, I think we're really hoping to deorbit the old code as soon as feasible. It's held together with hot-glue and baling wire. mcl ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On Tue, Jun 03, 2014 at 01:50:23PM -0700, Eitan Adler wrote: I don't concede killing anonymous means killing trivial bug reporting, but if that was the case: Oh well, I guess we have to focus on non-trivial bugs. Trivial bugs are important too. I'll echo eadler a bit here, but with a different emphasis. What _I_ consider a trivial bug is based on my own past experiences with FreeBSD. Someone who is new to it and is submitting their first bug may not see it as trivial. We don't wish to discourage them. Discouraging people from contributing is counterproductive. We need more contributors, not less. I know for certain that people in the past have given up after submitting PRs that were never answered. While I know we don't have the manpower to deal with all of them, that should at least be our ideal. mcl ___ 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: A simple ports question
On Tue, 3 Jun 2014 21:15:15 +0200 Baptiste Daroussin wrote: On Tue, Jun 03, 2014 at 12:09:10PM -0700, Ronald F. Guilmette wrote: Functionally, what is the difference between: pkg_delete Y and: cd /usr/ports/X/Y; make deinstall ? none There is one important difference, make deinstall passes -f to pkg_delete to force the deletion. ___ 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-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On Tue, 3 Jun 2014, Stephen Hurd wrote: I would venture that docs bugs and certain classes of website bugs rarely have communications. For example: ... There are trivial bugs in any class, but it's a mistake to think that most of any particular class are that way. I do agree that some trivial bugs will be lost due to the submitter not wanting to create Yet Another Account(TM). Still, it acts as a test of the submitter's determination and indirectly, the quality of the information they give. ___ 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] 356061: 91x success, 6x leftovers, 1x coredump, 1x threads, 1x arch, 1x ignored: doesn't build on 8.x, 31x depend (arch in graphics/sdl_gfx)
- Update graphics/sdl_gfx to version 2.0.25 - Bump PORTREVISION on ports depending on it, since the shlib version changed - Build ID: 20140601081200-65220 Job owner: m...@freebsd.org Buildtime: 3 days Enddate: Wed, 04 Jun 2014 05:16:55 GMT Revision: 356061 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=356061 - Port:devel/clanlib1 1.0.0_3 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (ARCH IN GRAPHICS/SDL_GFX) Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344046/sdl_gfx-2.0.25.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344047/clanlib1-1.0.0_3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344048/clanlib1-1.0.0_3.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344049/clanlib1-1.0.0_3.log - Port:devel/fpc-sdl 2.6.4_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (ARCH IN GRAPHICS/SDL_GFX) Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344050/sdl_gfx-2.0.25.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344051/fpc-sdl-2.6.4_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344052/fpc-sdl-2.6.4_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344053/fpc-sdl-2.6.4_2.log - Port:devel/p5-Alien-SDL 1.440_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (ARCH IN GRAPHICS/SDL_GFX) Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344054/sdl_gfx-2.0.25.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344055/p5-Alien-SDL-1.440_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344056/p5-Alien-SDL-1.440_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344057/p5-Alien-SDL-1.440_2.log - Port:devel/p5-SDL 2.540_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (ARCH IN GRAPHICS/SDL_GFX) Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344058/sdl_gfx-2.0.25.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344059/p5-SDL-2.540_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344060/p5-SDL-2.540_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344061/p5-SDL-2.540_2.log - Port:devel/rubygem-rubygame 2.6.4_5 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (ARCH IN GRAPHICS/SDL_GFX) Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344062/sdl_gfx-2.0.25.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344063/rubygem-rubygame-2.6.4_5.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344064/rubygem-rubygame-2.6.4_5.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344065/rubygem-rubygame-2.6.4_5.log - Port:games/brainparty 0.5_6 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (ARCH IN GRAPHICS/SDL_GFX) Log: https://qat.redports.org//~m...@freebsd.org/20140601081200-65220-344066/sdl_gfx-2.0.25.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS
poudriere build failure
I've got poudriere building most of a set of ports with default settings, default jail, 8.4-RELEASE amd64 both host and target. However, it's failing on a couple at the fetch stage. For example, databases/db42, db42-4.2.52_5 fails to build devel/libtool. devel/libtool direct succeeds though! May I have some help troubleshooting this please? Details below. TIA, Greg. CONFIG $ diff -u poudriere.conf.sample poudriere.conf|egrep ^[+-] -#NO_ZFS=yes +NO_ZFS=yes -FREEBSD_HOST=_PROTO_://_CHANGE_THIS_ +FREEBSD_HOST=ftp://ftp.freebsd.org WORKING BUILD (mostly) # poudriere bulk -C -j 84amd64 devel/libtool [84amd64-default] 1 packages built, 0 failures, 0 ignored, 0 skipped # tail -5 /usr/local/poudriere/data/logs/bulk/84amd64-default/2014-06-04_13h27m55s/logs/libtool-2.4.2_3.log tar: Error opening archive: Failed to open '/packages/All/libtool-2.4.2_3.tbz' tar: Error opening archive: Failed to open '/packages/All/libtool-2.4.2_3.tbz' tar: Error opening archive: Failed to open '/packages/All/libtool-2.4.2_3.tbz' I think packages should end up in this dir, but it's basically empty: $ ls -lR /usr/local/poudriere/data/packages/84amd64-default total 4 drwxr-xr-x 2 root wheel 512 Jun 4 13:28 All -rw-r--r-- 1 root wheel 174 Jun 4 13:28 INDEX-8.bz2 /usr/local/poudriere/data/packages/84amd64-default/All: total 0 FAILING BUILD # poudriere bulk -C -j 84amd64 databases/db42 Built ports: devel/libtool Failed ports: databases/db42:build-depends [84amd64-default] 1 packages built, 1 failures, 0 ignored, 0 skipped Looking in the log file for the failed db42 build, I get lots of failed fetches: = libtool-2.4.2.tar.gz doesn't seem to exist in /portdistfiles/. fetch: http://distcache.FreeBSD.org/ports-distfiles/libtool-2.4.2.tar.gz: No address record = Couldn't fetch it - please try to retrieve this = port manually into /portdistfiles/ and try again. *** Error code 1 In the build prep, it shows the following, so I figure fetch should be working: /etc/resolv.conf - /usr/local/poudriere/data/build/84amd64-default/ref/etc/resolv.conf Removing and fetching again yields the same file that's already there): # md5 /usr/ports/distfiles/libtool-2.4.2.tar.gz MD5 (/usr/ports/distfiles/libtool-2.4.2.tar.gz) = d2f3b7d4627e69e13514a40e72a24d50 PS: If this is the wrong list for this, please point me elsewhere if you know somewhere better. ___ 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
