How to reintroduce/undelete port?
Hello all, I use the sysutils/wait_on utility, which has been removed because (recurring) unavailability of the distfiles. I have missing file and I am willing to find some new sweet home for it on my machines, so the question is - how to request removal revocation via PR? -- Ondra Knezour ___ 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: How to reintroduce/undelete port?
On 3/15/2014 09:02, Ondra Knezour wrote: Hello all, I use the sysutils/wait_on utility, which has been removed because (recurring) unavailability of the distfiles. I have missing file and I am willing to find some new sweet home for it on my machines, so the question is - how to request removal revocation via PR? Hi Ondra, You can probably just email rene@ and request a partial reversion (it was removed with a block of ports) and tell him the location of the new MASTER_SITE you are hosting. Make sure it's in place first so he can verify it and update the port accordingly. The second option is open a PR (http://www.freebsd.org/send-pr.html) with the request, but I would bet that won't be necessary after talking to René. 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: How to reintroduce/undelete port?
Dne 15.3.2014 9:18, John Marino napsal(a): On 3/15/2014 09:02, Ondra Knezour wrote: I use the sysutils/wait_on utility, which has been removed because (recurring) unavailability of the distfiles. I have missing file and I am willing to find some new sweet home for it on my machines, so the question is - how to request removal revocation via PR? You can probably just email rene@ and request a partial reversion (it was removed with a block of ports) and tell him the location of the new MASTER_SITE you are hosting. Make sure it's in place first so he can verify it and update the port accordingly. The second option is open a PR (http://www.freebsd.org/send-pr.html) with the request, but I would bet that won't be necessary after talking to René. OK, I will ask René, thanks. -- Ondra Knezour ___ 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: How to reintroduce/undelete port?
We're using too and was a little discussion about replacement of wait_on: http://lists.freebsd.org/pipermail/freebsd-ports/2014-March/090762.html I hope wait_on will not deprecated :) 2014-03-15 9:02 GMT+01:00 Ondra Knezour knez...@weboutsourcing.cz: Hello all, I use the sysutils/wait_on utility, which has been removed because (recurring) unavailability of the distfiles. I have missing file and I am willing to find some new sweet home for it on my machines, so the question is - how to request removal revocation via PR? -- Ondra Knezour ___ 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: How to reintroduce/undelete port?
Dne 15.3.2014 10:00, Zsolt Udvari napsal(a): We're using too and was a little discussion about replacement of wait_on: http://lists.freebsd.org/pipermail/freebsd-ports/2014-March/090762.html I hope wait_on will not deprecated :) The port has been resurrected by rene@ http://svnweb.freebsd.org/ports?view=revisionrevision=348299 -- Best regards Ondra Knezour ___ 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 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 +-+ shells/bashc| 3.2.33.0| 4.3 +-+ www/groupoffice | 3.7.24 | 5.0.46 +-+ 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: How to reintroduce/undelete port?
Thanks all! 2014-03-15 10:06 GMT+01:00 Ondra Knezour knez...@weboutsourcing.cz: Dne 15.3.2014 10:00, Zsolt Udvari napsal(a): We're using too and was a little discussion about replacement of wait_on: http://lists.freebsd.org/pipermail/freebsd-ports/2014-March/090762.html I hope wait_on will not deprecated :) The port has been resurrected by rene@ http://svnweb.freebsd.org/ports?view=revisionrevision=348299 -- Best regards Ondra Knezour ___ 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: Replacement for sysutils/wait_on
Good news: http://lists.freebsd.org/pipermail/freebsd-ports/2014-March/090798.html http://svnweb.freebsd.org/ports?view=revisionrevision=348299 Zsolt 2014-03-13 23:26 GMT+01:00 Andrea Venturoli m...@netfence.it: Hello. I have a script which monitors a directory and wakes up as soon as a new file appears. I'm using sysutils/wait_on for this, but this port expired a few days ago. Is there a drop in replacement? Any other suggestion? bye Thanks av. ___ 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: KDE doesn't build on 10-STABLE, needs WITH_NEW_XORG
On 10-3-2014 19:21, Craig Rodrigues wrote:
Hi,
Hi,
I have a 10-stable system, and I am trying to rely
as much on pkg as possible to install stuff so I don't
need to build my own packages from ports.
After the latest upgrade to KDE 4.12 in ports,
KDE does not build out of the box. It turns out
that x11/kde-workspace needs WITH_NEW_XORG.
In ports/Mk/bsd.port.mk, there is this:
# Enable new xorg for FreeBSD versions after Radeon KMS was imported unless
# WITHOUT_NEW_XORG is set.
.if ${OSVERSION} = 110
. if !defined(WITHOUT_NEW_XORG)
WITH_NEW_XORG?= yes
. else
.undef WITH_NEW_XORG
. endif
.endif
Would it be possible to bump that check to a lower value of OSVERSION?
radeonkms was imported into HEAD r254885, and this changeset
exists in stable/10.
We are working now on a patch to bump this to include 10.0-stable. The
reason why this wasn't bumped earlier was because it was deemed
unacceptable that there wasn't a console driver that could work with the
KMS driver. The infamous black screen when you started X, which stayed
black even if you quit X. Now that vt(9) was merged to 10.0-stable this
problem has been resolved, even if vt(9) isn't enabled by default yet.
I set WIT_NEW_XORG in my /etc/make.conf and rebuilt all my ports
and KDE works fine. My laptpo has a a Radeon:
(--) PCI:*(0:1:0:0) 1002:6760:103c:161e Advanced Micro Devices, Inc.
[AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] rev 0, Mem @
0xc000/268435456, 0xd440/131072, I/O @ 0x4000/256, BIOS @
0x/65536
On another note, it looks like with KDE 4.12 in ports, will there will
be no working
KDE desktop on FreeBSD-9?
Well I got some good news here, the radeonKMS driver was merged into
9.2-stable. And it being investigated/worked on to get vt(9) also merged
into the 9.2-stable branch. So we can switch to the new Xorg version
there too.
-Koop
--
Craig
___
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
[QAT] 348313: 6x leftovers
- Update to 0.4.100.2.1 - Build ID: 20140315105200-30183 Job owner: t...@freebsd.org Buildtime: 48 minutes Enddate: Sat, 15 Mar 2014 11:40:28 GMT Revision: 348313 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348313 - Port:math/R-cran-RcppArmadillo 0.4.100.2.1 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140315105200-30183-301588/R-cran-RcppArmadillo-0.4.100.2.1.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140315105200-30183-301589/R-cran-RcppArmadillo-0.4.100.2.1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140315105200-30183-301590/R-cran-RcppArmadillo-0.4.100.2.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140315105200-30183-301591/R-cran-RcppArmadillo-0.4.100.2.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140315105200-30183-301592/R-cran-RcppArmadillo-0.4.100.2.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140315105200-30183-301593/R-cran-RcppArmadillo-0.4.100.2.1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140315105200-30183 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
[CFT] switch default version of xorg on 10-STABLE
This mail is cross-posted across several mailing lists. Please respect reply-to! It is time to switch FreeBSD 10-stable over to the new xorg distribution. The patch at [1] will do just that, for FreeBSD 10 versions after vt(9) was merged. It also contains fixes for USES=libtool, some minor updates and some shlib version bumps. Please test it and report successes or failures to us on x...@freebsd.org Apply it using svn patch (I don't think regular patch will work) and rebuild all ports to test it. [1] http://people.freebsd.org/~zeising/xorg-switch.10.diff More information here: https://wiki.freebsd.org/Graphics Regards! -- Niclas Zeising ___ 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] 348314: 2x leftovers, 1x depend (makefile in x11-toolkits/gnustep-gui), 15x success
Add some missing distinfo With hat: portmgr - Build ID: 20140315114000-58712 Job owner: anto...@freebsd.org Buildtime: 38 minutes Enddate: Sat, 15 Mar 2014 12:17:44 GMT Revision: 348314 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348314 - Port:devel/rubygem-metaclass 0.0.1 Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301594/rubygem-metaclass-0.0.1.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301595/rubygem-metaclass-0.0.1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301596/rubygem-metaclass-0.0.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301597/rubygem-metaclass-0.0.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301598/rubygem-metaclass-0.0.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301599/rubygem-metaclass-0.0.1.log - Port:games/xshogi 1.4.2 Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301600/xshogi-1.4.2.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301601/xshogi-1.4.2.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301602/xshogi-1.4.2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301603/xshogi-1.4.2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301604/xshogi-1.4.2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301605/xshogi-1.4.2.log - Port:graphics/graphos 0.5 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301606/graphos-0.5.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301607/graphos-0.5.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301608/graphos-0.5.log Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (MAKEFILE IN X11-TOOLKITS/GNUSTEP-GUI) Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301609/gnustep-gui-0.24.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301610/graphos-0.5.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~anto...@freebsd.org/20140315114000-58712-301611/graphos-0.5.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140315114000-58712 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: devel/libkolab failing to build on 11-current
Raphael Kubo da Costa rak...@freebsd.org writes: Shawn Webb latt...@gmail.com writes: devel/libkolab has been failing for the past few weeks. Log file from an 11-current/amd64 Poudriere build here: http://pastebin.com/kfjkMpE7 I was able to reproduce it here too. It's weird that no pkg-fallout email has been sent about this failure. I've submitted a patch to the kolab development list and will backport it to the port. Thanks for the report. Fixed in r348328. ___ 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: changes to base system DNS
Warren Block writes: From dim memory of a couple of weeks ago... Making sure I understand: doing this (or the corrected version) will bring up named at the same point in the boot process as using system named in previous versions? Respectfully, Robert Huff ___ 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: net-im/prosody post install error
On Fri, Mar 14, 2014 at 9:55 PM, Ross Penner ro...@f-m.fm wrote: When I try to build prosody (on FreeBSD 9.2-RELEASE-p3), I get the following error once it gets to the installation phase. The error references already having a prosody user and group. They were created the first time I tried to install and this message is from my second attempt. === Installing for prosody-0.9.3 /bin/sh /usr/ports/net-im/prosody/work/pkg-install prosody-0.9.3 PRE-INSTALL prosody:*:242: You already have a group prosody, so I will use it. pw: user 'prosody' already exists Adding user prosody failed... *** [pre-install] Error code 1 Thanks for any help or insight you can provide. The pkg-install script should be detecting the user, what does the following command show? /usr/sbin/pw user show prosody ; echo $? On my system with no prosody user it returns with: pw: no such user `prosody` 67 It should return with a value of zero, when the port is installed: # /usr/sbin/pw user show prosody ; echo $? prosody:*:242:1::0:0:Prosody XMMP Server:/nonexistent:/usr/sbin/nologin 0 I have tried installing/deinstalling/re-installing the port, and don't get the prosody user already exists error. -- 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
[QAT] 348336: 2x leftovers, 4x success
- Convert USE_GMAKE to USES - Build ID: 20140315154600-43425 Job owner: m...@freebsd.org Buildtime: 22 minutes Enddate: Sat, 15 Mar 2014 16:07:57 GMT Revision: 348336 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348336 - Port:x11-drivers/input-wacom 40.0.15.0_3 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315154600-43425-301738/input-wacom-40.0.15.0_3.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315154600-43425-301739/input-wacom-40.0.15.0_3.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315154600-43425-301740/input-wacom-40.0.15.0_3.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315154600-43425-301741/input-wacom-40.0.15.0_3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315154600-43425-301742/input-wacom-40.0.15.0_3.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315154600-43425-301743/input-wacom-40.0.15.0_3.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140315154600-43425 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] 348339: 2x leftovers, 4x success
- Convert USE_BZIP/GMAKE to USES - While here add stage support - Build ID: 20140315162000-55043 Job owner: m...@freebsd.org Buildtime: 23 minutes Enddate: Sat, 15 Mar 2014 16:42:30 GMT Revision: 348339 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348339 - Port:x11/libgnomekbd Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162000-55043-301750/libgnomekbd-2.32.0_1.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162000-55043-301751/libgnomekbd-2.32.0_1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162000-55043-301752/libgnomekbd-2.32.0_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162000-55043-301753/libgnomekbd-2.32.0_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162000-55043-301754/libgnomekbd-2.32.0_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162000-55043-301755/libgnomekbd-2.32.0_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140315162000-55043 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] 348328: 6x leftovers
Add a patch sent upstream to fix the build with clang 3.4. clang 3.4 is pickier with the flags it accepts, and refuses to work with the GCC-specific -fno-check-new. - Build ID: 20140315143800-54137 Job owner: rak...@freebsd.org Buildtime: 2 hours Enddate: Sat, 15 Mar 2014 16:55:44 GMT Revision: 348328 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348328 - Port:devel/libkolab 0.5.0_1 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~rak...@freebsd.org/20140315143800-54137-301696/libkolab-0.5.0_1.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~rak...@freebsd.org/20140315143800-54137-301697/libkolab-0.5.0_1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~rak...@freebsd.org/20140315143800-54137-301698/libkolab-0.5.0_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~rak...@freebsd.org/20140315143800-54137-301699/libkolab-0.5.0_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~rak...@freebsd.org/20140315143800-54137-301700/libkolab-0.5.0_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~rak...@freebsd.org/20140315143800-54137-301701/libkolab-0.5.0_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140315143800-54137 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] 348342: 4x ignored: is marked as broken: fails to build with new utmpx, 6x leftovers, 26x success
- Convert USE_GMAKE to USES - Build ID: 20140315162200-41820 Job owner: m...@freebsd.org Buildtime: 68 minutes Enddate: Sat, 15 Mar 2014 17:29:34 GMT Revision: 348342 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348342 - Port:irc/anope 1.8.8 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301774/anope-1.8.8.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301775/anope-1.8.8.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301776/anope-1.8.8.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301777/anope-1.8.8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301778/anope-1.8.8.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301779/anope-1.8.8.log - Port:irc/ctrlproxy 3.0.8_6 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301780/ctrlproxy-3.0.8_6.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301781/ctrlproxy-3.0.8_6.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301782/ctrlproxy-3.0.8_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301783/ctrlproxy-3.0.8_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301784/ctrlproxy-3.0.8_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301785/ctrlproxy-3.0.8_6.log - Port:irc/slirc 0.12_4 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301786/slirc-0.12_4.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301787/slirc-0.12_4.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301788/slirc-0.12_4.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301789/slirc-0.12_4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301790/slirc-0.12_4.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301791/slirc-0.12_4.log - Port:irc/smartirc4net 0.4.5.1 Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301792/smartirc4net-0.4.5.1.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301793/smartirc4net-0.4.5.1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301794/smartirc4net-0.4.5.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301795/smartirc4net-0.4.5.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301796/smartirc4net-0.4.5.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162200-41820-301797/smartirc4net-0.4.5.1.log - Port:
[QAT] 348343: 4x leftovers, 2x clang, 18x success, 6x ignored: is marked as broken: fails to configure
- Convert USE_XZ/BZIP2/GMAKE to USES - Build ID: 20140315162601-43444 Job owner: m...@freebsd.org Buildtime: 81 minutes Enddate: Sat, 15 Mar 2014 17:46:58 GMT Revision: 348343 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348343 - Port:x11-fm/gnome-commander2 Buildgroup: 10.0-QAT/amd64 Buildstatus: IGNORED: IS MARKED AS BROKEN: FAILS TO CONFIGURE Buildgroup: 10.0-QAT/i386 Buildstatus: IGNORED: IS MARKED AS BROKEN: FAILS TO CONFIGURE Buildgroup: 8.4-QAT/amd64 Buildstatus: IGNORED: IS MARKED AS BROKEN: FAILS TO CONFIGURE Buildgroup: 8.4-QAT/i386 Buildstatus: IGNORED: IS MARKED AS BROKEN: FAILS TO CONFIGURE Buildgroup: 9.2-QAT/amd64 Buildstatus: IGNORED: IS MARKED AS BROKEN: FAILS TO CONFIGURE Buildgroup: 9.2-QAT/i386 Buildstatus: IGNORED: IS MARKED AS BROKEN: FAILS TO CONFIGURE - Port:x11-themes/fvwm-themes Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301816/fvwm-themes-0.7.0_5.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301817/fvwm-themes-0.7.0_5.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301818/fvwm-themes-0.7.0_5.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301819/fvwm-themes-0.7.0_5.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301820/fvwm-themes-0.7.0_5.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301821/fvwm-themes-0.7.0_5.log - Port:x11-toolkits/gtkextra2 2.1.2_1 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301822/gtkextra-2.1.2_1.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301823/gtkextra-2.1.2_1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301824/gtkextra-2.1.2_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301825/gtkextra-2.1.2_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301826/gtkextra-2.1.2_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301827/gtkextra-2.1.2_1.log - Port:x11-toolkits/gtkglextmm Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301828/gtkglextmm-1.2.0_7.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301829/gtkglextmm-1.2.0_7.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301830/gtkglextmm-1.2.0_7.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301831/gtkglextmm-1.2.0_7.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301832/gtkglextmm-1.2.0_7.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301833/gtkglextmm-1.2.0_7.log - Port:x11-toolkits/soqt 1.5.0_2 Buildgroup: 10.0-QAT/amd64 Buildstatus: CLANG Log: https://qat.redports.org//~m...@freebsd.org/20140315162601-43444-301834/SoQt-1.5.0_2.log Buildgroup: 10.0-QAT/i386 Buildstatus: CLANG Log:
Re: [games/traingame] Build failures with FreeBSD 10
On Thu, 13 Mar 2014 12:31:43 +0100 Rusmir Dusko wrote:
Hello
Trainm Game not build more in FreeBSD 10.
With FreeBSD 9.1, 9.2 have all good worked.
10.0-RELEASE-p4 FreeBSD 10.0-RELEASE-p4 #0: Tue Jan 14 20:48:07 UTC 2014 amd64
This is first Cmake and then GCC Port.
Have too not worked in FreeBSD 10 with older boost 1.52.0.
With Clang not works at all.
Because the port depends on a C++ library like boost, it needs to be
build with the same C++ runtime library as boost. On FreeBSD 10 that
is libc++.
I've attached a patch that makes the port build with clang/libc++ but
I haven't run-tested it.Index: games/traingame/Makefile
===
--- games/traingame/Makefile (revision 348266)
+++ games/traingame/Makefile (working copy)
@@ -22,10 +22,12 @@ LIB_DEPENDS= libfreetype.so:${PORTSDIR}/
WRKSRC= ${WRKDIR}/TrainGame-${PORTVERSION}
-USES= cmake pkgconfig
+USES= cmake compiler:c++11-lib pkgconfig
+USE_CXXSTD= gnu++11
USE_SDL= sdl image
USE_GL= glew
-USE_GCC= yes
+
+LDFLAGS+= -L${LOCALBASE}/lib
PORTDOCS= model_notes.txt models.gnuplot
Index: games/traingame/files/patch-libc++
===
--- games/traingame/files/patch-libc++ (revision 0)
+++ games/traingame/files/patch-libc++ (working copy)
@@ -0,0 +1,27 @@
+--- src/CrossoverTrack.cpp.orig
src/CrossoverTrack.cpp
+@@ -215,5 +215,5 @@
+
+ ITrackSegmentPtr make_crossover_track()
+ {
+- return ITrackSegmentPtr(new CrossoverTrack);
++ return ITrackSegmentPtr(static_castITrackSegment *(new CrossoverTrack));
+ }
+--- src/SDLWindow.cpp.orig
src/SDLWindow.cpp
+@@ -406,5 +406,5 @@
+ // Construct and initialise an OpenGL SDL window
+ IWindowPtr make_sdl_window()
+ {
+- return shared_ptrIWindow(new SDLWindow);
++ return shared_ptrIWindow(static_castIWindow *(new SDLWindow));
+ }
+--- src/StraightTrack.cpp.orig
src/StraightTrack.cpp
+@@ -259,5 +259,5 @@
+ throw runtime_error(Illegal straight track direction:
+ + lexical_caststring(a_direction));
+
+- return ITrackSegmentPtr(new StraightTrack(real_dir));
++ return ITrackSegmentPtr(static_castITrackSegment *(new StraightTrack(real_dir)));
+ }
Property changes on: games/traingame/files/patch-libc++
___
Added: svn:mime-type
## -0,0 +1 ##
+text/plain
\ No newline at end of property
Added: fbsd:nokeywords
## -0,0 +1 ##
+yes
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
___
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: [games/traingame] Build failures with FreeBSD 10
On Sat, 15 Mar 2014 19:23:12 +0100 Tijl Coosemans t...@freebsd.org wrote: On Thu, 13 Mar 2014 12:31:43 +0100 Rusmir Dusko wrote: Hello Trainm Game not build more in FreeBSD 10. With FreeBSD 9.1, 9.2 have all good worked. 10.0-RELEASE-p4 FreeBSD 10.0-RELEASE-p4 #0: Tue Jan 14 20:48:07 UTC 2014 amd64 This is first Cmake and then GCC Port. Have too not worked in FreeBSD 10 with older boost 1.52.0. With Clang not works at all. Because the port depends on a C++ library like boost, it needs to be build with the same C++ runtime library as boost. On FreeBSD 10 that is libc++. I've attached a patch that makes the port build with clang/libc++ but I haven't run-tested it. Thanks Tijl Coosemans, this changes have fixed build with Clang and FreeBSD 10 :) I have more times tested, works all, now trying to fix more.. -- Best regards, Rusmir Dusko ___ 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] 348347: 26x leftovers, 2x clang, 38x success
- Convert USE_GMAKE/BZIP2 to USES - Build ID: 20140315163400-60441 Job owner: m...@freebsd.org Buildtime: 3 hours Enddate: Sat, 15 Mar 2014 19:44:02 GMT Revision: 348347 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348347 - Port:x11-toolkits/libgtksourceviewmm Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301858/libgtksourceviewmm-1.9.5_6.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301859/libgtksourceviewmm-1.9.5_6.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301860/libgtksourceviewmm-1.9.5_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301861/libgtksourceviewmm-1.9.5_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301862/libgtksourceviewmm-1.9.5_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301863/libgtksourceviewmm-1.9.5_6.log - Port:x11-wm/ccsm Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301864/ccsm-0.8.4_4.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301865/ccsm-0.8.4_4.log Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301866/ccsm-0.8.4_4.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301867/ccsm-0.8.4_4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301868/ccsm-0.8.4_4.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301869/ccsm-0.8.4_4.log - Port:x11-wm/compiz Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301870/compiz-0.8.4_9.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301871/compiz-0.8.4_9.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301872/compiz-0.8.4_9.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301873/compiz-0.8.4_9.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301874/compiz-0.8.4_9.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301875/compiz-0.8.4_9.log - Port:x11-wm/compizconfig-backend-gconf Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301876/compizconfig-backend-gconf-0.8.4_3.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301877/compizconfig-backend-gconf-0.8.4_3.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301878/compizconfig-backend-gconf-0.8.4_3.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301879/compizconfig-backend-gconf-0.8.4_3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315163400-60441-301880/compizconfig-backend-gconf-0.8.4_3.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log:
Re: changes to base system DNS
On Sat, 15 Mar 2014, Robert Huff wrote: Warren Block writes: From dim memory of a couple of weeks ago... Making sure I understand: doing this (or the corrected version) will bring up named at the same point in the boot process as using system named in previous versions? It looks and acts the same, but I can't say definitively that it runs at the same time as before. ___ 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] 348341: 2x leftovers, 6x ignored: is marked as broken: doesn't build, 4x success
- Convert USE_BZIP/GMAKE to USES - Build ID: 20140315162001-15843 Job owner: m...@freebsd.org Buildtime: 4 hours Enddate: Sat, 15 Mar 2014 20:00:25 GMT Revision: 348341 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348341 - Port:x11/gnome-shell Buildgroup: 10.0-QAT/amd64 Buildstatus: IGNORED: IS MARKED AS BROKEN: DOESN'T BUILD Buildgroup: 10.0-QAT/i386 Buildstatus: IGNORED: IS MARKED AS BROKEN: DOESN'T BUILD Buildgroup: 8.4-QAT/amd64 Buildstatus: IGNORED: IS MARKED AS BROKEN: DOESN'T BUILD Buildgroup: 8.4-QAT/i386 Buildstatus: IGNORED: IS MARKED AS BROKEN: DOESN'T BUILD Buildgroup: 9.2-QAT/amd64 Buildstatus: IGNORED: IS MARKED AS BROKEN: DOESN'T BUILD Buildgroup: 9.2-QAT/i386 Buildstatus: IGNORED: IS MARKED AS BROKEN: DOESN'T BUILD - Port:x11/wbar 2.3.4 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162001-15843-301768/wbar-2.3.4.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315162001-15843-301769/wbar-2.3.4.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162001-15843-301770/wbar-2.3.4.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162001-15843-301771/wbar-2.3.4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162001-15843-301772/wbar-2.3.4.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315162001-15843-301773/wbar-2.3.4.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140315162001-15843 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: changes to base system DNS
On Sat, Mar 15, 2014 at 12:57 PM, Warren Block wbl...@wonkity.com wrote: On Sat, 15 Mar 2014, Robert Huff wrote: Warren Block writes: From dim memory of a couple of weeks ago... Making sure I understand: doing this (or the corrected version) will bring up named at the same point in the boot process as using system named in previous versions? It looks and acts the same, but I can't say definitively that it runs at the same time as before. rcorder /etc/rc.d/* /usr/local/etc/rc.d/* on the old and new systems and compare the locations of named vs. local_unbound? Looks like local_unbound starts a bit earlier as it does not require that the network be up and running since it is a client-only. But the full unbound does not start until after logins are enabled at the very end of the process. So it depends on what capability you are looking for as to whether it starts earlier or later. (No easy answers here.) -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.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] 348376: 6x leftovers
- Fixes resourceleak in i3bar and memoryleak in i3 - Convert to USES=tar:bzip2 PR: ports/187617 Submitted by: Johannes Jost Meixner x...@chaot.net Obtained from: i3 git (http://code.stapelberg.de/git/i3/) - Build ID: 20140315202200-41411 Job owner: b...@freebsd.org Buildtime: 54 minutes Enddate: Sat, 15 Mar 2014 21:16:25 GMT Revision: 348376 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348376 - Port:x11-wm/i3 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140315202200-41411-302146/i3-4.7.2_1.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140315202200-41411-302147/i3-4.7.2_1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140315202200-41411-302148/i3-4.7.2_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140315202200-41411-302149/i3-4.7.2_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140315202200-41411-302150/i3-4.7.2_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140315202200-41411-302151/i3-4.7.2_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140315202200-41411 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: Requesting Committer Attention for ports/184011
I'd like to bump this since it's been just shy of a month. I'm now the maintainer of net-mgmt/nagios-check_ports, and I'd like to get this update committed as part of supporting pkgng in the port in addition to reviving upstream development. Ryan On 2/16/14, 8:08 PM, Ryan Frederick wrote: I'd like to request that a committer take a gander at ports/184011 for me when possible. This is a pr I submitted three months ago and was never acted upon by the previous maintainer. Ryan ___ 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] 348350: 1x depend (linker_error in textproc/libextractor), 3x depend (ignored: is marked as broken: does not package in textproc/libextractor), 38x success, 2x assumes_gcc, 10x leftovers
- Convert USE_GMAKE/BZIP2 to USES - Build ID: 20140315164200-64394 Job owner: m...@freebsd.org Buildtime: 5 hours Enddate: Sat, 15 Mar 2014 21:44:00 GMT Revision: 348350 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348350 - Port:net-p2p/bnbt Buildgroup: 10.0-QAT/amd64 Buildstatus: ASSUMES_GCC Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301936/bnbt-8.5_1.log Buildgroup: 10.0-QAT/i386 Buildstatus: ASSUMES_GCC Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301937/bnbt-8.5_1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301938/bnbt-8.5_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301939/bnbt-8.5_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301940/bnbt-8.5_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301941/bnbt-8.5_1.log - Port:net-p2p/gnunet 0.9.3_7 Buildgroup: 10.0-QAT/amd64 Buildstatus: DEPEND (LINKER_ERROR IN TEXTPROC/LIBEXTRACTOR) Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301942/libextractor-0.6.2_15.log Buildgroup: 10.0-QAT/i386 Buildstatus: DEPEND (IGNORED: IS MARKED AS BROKEN: DOES NOT PACKAGE IN TEXTPROC/LIBEXTRACTOR) Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301944/gnunet-0.9.3_7.log Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (IGNORED: IS MARKED AS BROKEN: DOES NOT PACKAGE IN TEXTPROC/LIBEXTRACTOR) Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301946/gnunet-0.9.3_7.log Buildgroup: 9.2-QAT/i386 Buildstatus: DEPEND (IGNORED: IS MARKED AS BROKEN: DOES NOT PACKAGE IN TEXTPROC/LIBEXTRACTOR) - Port:net-p2p/gtkhx 0.9.4_6 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301948/gtkhx-0.9.4_6.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301949/gtkhx-0.9.4_6.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301950/gtkhx-0.9.4_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301951/gtkhx-0.9.4_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301952/gtkhx-0.9.4_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301953/gtkhx-0.9.4_6.log - Port:net-p2p/jigdo Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301954/jigdo-0.7.3_7.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301955/jigdo-0.7.3_7.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301956/jigdo-0.7.3_7.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301957/jigdo-0.7.3_7.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301958/jigdo-0.7.3_7.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140315164200-64394-301959/jigdo-0.7.3_7.log - Port:net-p2p/libbt 1.05_4 Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS
Re: Requesting Committer Attention for ports/184011
On 15/03/2014 21:33, Ryan Frederick wrote: I'd like to bump this since it's been just shy of a month. I'm now the maintainer of net-mgmt/nagios-check_ports, and I'd like to get this update committed as part of supporting pkgng in the port in addition to reviving upstream development. Hi, Ryan, I'll deal with this for you. However, I can't commit the patch from the PR as it stands, as it doesn't have staging support. That's absolutely required nowadays. It might be an idea to make the pkg_version/portaudit vs. pkg version/pkg audit choice be an OPTION setting with only the default based on the OS version -- plenty of people are running pkg(8) on earlier versions than 10.x. I'll be happy to show you how to do that if you are unsure. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Requesting Committer Attention for ports/184011
On 3/15/14, 5:09 PM, Matthew Seaman wrote: Hi, Ryan, I'll deal with this for you. However, I can't commit the patch from the PR as it stands, as it doesn't have staging support. That's absolutely required nowadays. It might be an idea to make the pkg_version/portaudit vs. pkg version/pkg audit choice be an OPTION setting with only the default based on the OS version -- plenty of people are running pkg(8) on earlier versions than 10.x. I'll be happy to show you how to do that if you are unsure. Cheers, Matthew I'd appreciate your help Matthew. I don't intend this patch to be an end-all and be-all commit but rather a stopgap commit as part of transitioning to a fork I've made of the original upstream (https://github.com/rfrederick/check_ports). The original author ended development three years ago, and since I use the port daily I'd like to bring it up to speed as far as pkgng and staging support goes. Ryan ___ 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: Requesting Committer Attention for ports/184011
On 15/03/2014 22:28, Ryan Frederick wrote: I'd appreciate your help Matthew. I don't intend this patch to be an end-all and be-all commit but rather a stopgap commit as part of transitioning to a fork I've made of the original upstream (https://github.com/rfrederick/check_ports). The original author ended development three years ago, and since I use the port daily I'd like to bring it up to speed as far as pkgng and staging support goes. OK -- no problem. Adding staging support is trivial. See https://redports.org/browser/matthew/net-mgmt/nagios-check_ports/Makefile?rev=24309 If you're going to switch to a new fork of the code, then lets do that. I take it that means you're going to want to host the distfiles somewhere else? You can do it from github if you need to, but it's probably easier if you just make a tarball and stick it on a webserver somewhere. Anyhow, send me what you have as a diff against the current port, and we can take it from there. Or rather, we can take it from there /tomorrow/. Time for me to retire for the night. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Requesting Committer Attention for ports/184011
On 3/15/14, 6:26 PM, Matthew Seaman wrote: On 15/03/2014 22:28, Ryan Frederick wrote: I'd appreciate your help Matthew. I don't intend this patch to be an end-all and be-all commit but rather a stopgap commit as part of transitioning to a fork I've made of the original upstream (https://github.com/rfrederick/check_ports). The original author ended development three years ago, and since I use the port daily I'd like to bring it up to speed as far as pkgng and staging support goes. OK -- no problem. Adding staging support is trivial. See https://redports.org/browser/matthew/net-mgmt/nagios-check_ports/Makefile?rev=24309 If you're going to switch to a new fork of the code, then lets do that. I take it that means you're going to want to host the distfiles somewhere else? You can do it from github if you need to, but it's probably easier if you just make a tarball and stick it on a webserver somewhere. Anyhow, send me what you have as a diff against the current port, and we can take it from there. Or rather, we can take it from there /tomorrow/. Time for me to retire for the night. Cheers, Matthew I'd like to try hosting the files from github since I'd like to try out their release functionality, but if it looks to be too much of a hassle I'll find somewhere else to host a tarball. I'm out of town right now and have a very busy week ahead of me, so I'll take things from this point when I have a chance to. Ryan ___ 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
mail/mutt doesn't compile
Updated my ports tree, and get the following: Script started on Sat Mar 15 19:26:42 2014 borg.lerctr.org /usr/ports # portmaster mail/ma[Kutt ]0;portmaster: mutt-1.5.22 === Currently installed version: mutt-1.5.22 === Port directory: /usr/ports/mail/mutt === Gathering distinfo list for installed ports === Launching 'make checksum' for mail/mutt in background === Gathering dependency list for mail/mutt from ports === Initial dependency check complete for mail/mutt ]0;portmaster: mutt-1.5.22 === Starting build for mail/mutt === === All dependencies are up to date === Cleaning for mutt-1.5.23 === Found saved configuration for mutt-1.5.22 === mutt-1.5.23 depends on file: /usr/local/sbin/pkg - found === Fetching all distfiles required by mutt-1.5.23 for building === Extracting for mutt-1.5.23 = SHA256 Checksum OK for mutt/mutt-1.5.23.tar.gz. = SHA256 Checksum OK for mutt/patch-1.5.23.rr.compressed.gz. = SHA256 Checksum OK for mutt/patch-1.5.23.vvv.initials.gz. = SHA256 Checksum OK for mutt/patch-1.5.23.vvv.quote.gz. === Patching for mutt-1.5.23 === Applying distribution patches for mutt-1.5.23 === Applying FreeBSD patches for mutt-1.5.23 No such line 3657 in input file, ignoring === mutt-1.5.23 depends on executable: ispell - found === mutt-1.5.23 depends on executable: xsltproc - found === mutt-1.5.23 depends on file: /usr/local/share/xsl/docbook/html/docbook.xsl - found === mutt-1.5.23 depends on executable: lynx - found === mutt-1.5.23 depends on file: /usr/local/bin/automake-1.14 - found === mutt-1.5.23 depends on file: /usr/local/bin/autoconf-2.69 - found === mutt-1.5.23 depends on shared library: libsasl2.so - found === mutt-1.5.23 depends on shared library: libintl.so - found === Configuring for mutt-1.5.23 === FreeBSD 10 autotools fix applied to /usr/ports/mail/mutt/work/mutt-1.5.23/aclocal.m4 === FreeBSD 10 autotools fix applied to /usr/ports/mail/mutt/work/mutt-1.5.23/configure configure.ac:16: installing './compile' configure: loading site script /usr/ports/Templates/config.site checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes /usr/ports/mail/mutt/work/mutt-1.5.23/missing: Unknown `--is-lightweight' option Try `/usr/ports/mail/mutt/work/mutt-1.5.23/missing --help' for more information configure: WARNING: 'missing' script is too old or missing checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for style of include used by make... GNU checking for gcc... cc -I/usr/local/include checking whether the C compiler works... no configure: error: in `/usr/ports/mail/mutt/work/mutt-1.5.23': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to udo.schweig...@siemens.com [maintainer] and attach the /usr/ports/mail/mutt/work/mutt-1.5.23/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make[1]: stopped in /usr/ports/mail/mutt *** Error code 1 Stop. make: stopped in /usr/ports/mail/mutt === make failed for mail/mutt === Aborting update === Killing background jobs Terminated === You can restart from the point of failure with this command line: portmaster flags mail/mutt === Exiting borg.lerctr.org /usr/ports # pkj[Kg ing[Kfo pkg.list borg.lerctr.org /usr/ports # uname -a FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #17 r262907M: Fri Mar 7 16:48:03 CST 2014 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER amd64 borg.lerctr.org /usr/ports # ^D Script done on Sat Mar 15 19:27:09 2014 I'll attach the pkg list. Ideas? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ImageMagick-6.8.0.7_5,1Image processing tools ORBit2-2.14.19 High-performance CORBA ORB with support for the C language Thunar-1.6.3_1 Xfce file manager a2ps-4.13b_5 Formats an ASCII file for printing on a postscript printer aalib-1.4.r5_9 ASCII art library adobe-cmaps-20051217_1 Adobe CMap collection alpine-2.00_4 Mail and news client descended from Pine alsa-lib-1.0.27.2_1ALSA compatibility library alsa-plugins-1.0.27_2 ALSA compatibility library plugins apache22-2.2.26Version 2.2.x of Apache web server with prefork MPM. apcupsd-3.14.10_1 Set of programs for controlling APC UPS apr-1.4.8.1.5.3Apache Portability Library argp-standalone-1.3_2 Standalone
