Re: Fetched Ports index falling out of date

2012-10-17 Thread Erwin Lansing
On Tue, Oct 16, 2012 at 11:10:08PM +0100, Paul Macdonald wrote: Hi, Hi Paul, For the past 4 days or so, i have noticed an issue where the ports INDEX is out of date. e.g portupgrade-2.4.10,2 succeeds index (index has 2.4.9.9,2) sqlite3-3.7.14.1

Re: Quick status update on Squid 3.x ports

2012-10-17 Thread Любомир Григоров
Hello Thomas-Martin, Just wanted to check in if there is more info on Squid 3.2 or if you encountered a setback and are pushing the release further. Cheers and keep up the good work! -- Lyubomir Grigorov (bgalakazam) ___ freebsd-ports@freebsd.org

something had broken in *.mk?

2012-10-17 Thread Ruslan Mahmatkhanov
Hi, I got this whenever check any port with porlint -AC: [rm@smeshariki4 ~/py-pysha3] portlint -AC make: /usr/ports/Mk/bsd.port.mk line 5121: warning: duplicate script for target -depends ignored make: /usr/ports/Mk/bsd.port.mk line 5121: warning: using previous script for -depends defined

Re: something had broken in *.mk?

2012-10-17 Thread Ruslan Mahmatkhanov
Ruslan Mahmatkhanov wrote on 17.10.2012 11:59: Hi, I got this whenever check any port with porlint -AC: root@smeshariki4:/usr/ports/devel/gitg # make install clean make: /usr/ports/Mk/bsd.port.mk line 5118: warning: duplicate script for target -depends ignored make:

Re: something had broken in *.mk?

2012-10-17 Thread John Marino
You're building with bmake and not make. bmake uses :tu and :tl where make uses :U and :L, among other things. It's the :L modifier that's causing your errors. use the FreeBSD version of make instead. John On 10/17/2012 09:59, Ruslan Mahmatkhanov wrote: Hi, I got this whenever check any port

Re: something had broken in *.mk?

2012-10-17 Thread Ruslan Mahmatkhanov
John Marino wrote on 17.10.2012 14:52: You're building with bmake and not make. bmake uses :tu and :tl where make uses :U and :L, among other things. It's the :L modifier that's causing your errors. use the FreeBSD version of make instead. John Yes, you are right. I just remember that I

Re: something had broken in *.mk?

2012-10-17 Thread John Marino
You're building with bmake and not make. bmake uses :tu and :tl where make uses :U and :L, among other things. It's the :L modifier that's causing your errors. use the FreeBSD version of make instead. John On 10/17/2012 09:59, Ruslan Mahmatkhanov wrote: Hi, I got this whenever check any port

Re: something had broken in *.mk?

2012-10-17 Thread Baptiste Daroussin
On Wed, Oct 17, 2012 at 02:58:50PM +0400, Ruslan Mahmatkhanov wrote: John Marino wrote on 17.10.2012 14:52: You're building with bmake and not make. bmake uses :tu and :tl where make uses :U and :L, among other things. It's the :L modifier that's causing your errors. use the FreeBSD

Re: something had broken in *.mk?

2012-10-17 Thread Baptiste Daroussin
On Wed, Oct 17, 2012 at 01:55:37PM +0200, Baptiste Daroussin wrote: On Wed, Oct 17, 2012 at 02:58:50PM +0400, Ruslan Mahmatkhanov wrote: John Marino wrote on 17.10.2012 14:52: You're building with bmake and not make. bmake uses :tu and :tl where make uses :U and :L, among other things.

Re: something had broken in *.mk?

2012-10-17 Thread Michael Gmelin
On Wed, 17 Oct 2012 14:20:45 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Wed, Oct 17, 2012 at 01:55:37PM +0200, Baptiste Daroussin wrote: On Wed, Oct 17, 2012 at 02:58:50PM +0400, Ruslan Mahmatkhanov wrote: John Marino wrote on 17.10.2012 14:52: You're building with bmake and

Re: something had broken in *.mk?

2012-10-17 Thread Baptiste Daroussin
On Wed, Oct 17, 2012 at 02:25:38PM +0200, Michael Gmelin wrote: On Wed, 17 Oct 2012 14:20:45 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Wed, Oct 17, 2012 at 01:55:37PM +0200, Baptiste Daroussin wrote: On Wed, Oct 17, 2012 at 02:58:50PM +0400, Ruslan Mahmatkhanov wrote: John

Re: something had broken in *.mk?

2012-10-17 Thread John Marino
On 10/17/2012 14:30, Baptiste Daroussin wrote: I don't know much about this, I just know that current is going to use bmake, and the only incompatibility I have spotted so far from our make to bmake is the :L becoming :tl and :U becoming :tu Once 8.3 and 9.0 are EOLed all version of freebsd

pkg install order dependency problem

2012-10-17 Thread Adam McDougall
Short version: If you make a pkg repo with poudriere that includes java/diablo-jdk16 and tell pkg to install it, it knows pkgconf is a dep of xproto but it installs it in the wrong order so it fails. diablo-jdk16 is not on pkgbeta so I cannot test with that repo. I realize there are other jdk

Re: Portmaster/Portupgrade | pkg2ng

2012-10-17 Thread Jim Trigg
On Tue, Oct 16, 2012 at 06:51:59PM -0500, Bryan Drewery wrote: On 10/16/2012 4:11 PM, Jos Chrispijn wrote: Somewhat lost here; just read UPDATING in which is reported about an additional function support of pkgng by portupgrade and portmaster: PORTMASTER # make -C

Re: Portmaster/Portupgrade | pkg2ng

2012-10-17 Thread Bryan Drewery
On 10/17/2012 8:18 AM, Jim Trigg wrote: On Tue, Oct 16, 2012 at 06:51:59PM -0500, Bryan Drewery wrote: On 10/16/2012 4:11 PM, Jos Chrispijn wrote: Somewhat lost here; just read UPDATING in which is reported about an additional function support of pkgng by portupgrade and portmaster:

problem building Vuze

2012-10-17 Thread Robert Huff
On: FreeBSD 10.0-CURRENT #0: Tue Jul 24 08:55:46 EDT 2012 amd64 with openjdk6-b26, attempting to build last night's vuze update produces: === Cleaning for vuze-4.7.2.0 === Found saved configuration for vuze-4.7.0.0_1 === Extracting for vuze-4.7.2.0 = SHA256 Checksum OK for

Re: svn commit: r305926 - head/ports-mgmt/poudriere

2012-10-17 Thread Adam McDougall
I upgraded poudriere to 2.2 and started a build using: poudriere bulk -D -f /root/pkg-webold -j 90amd64-webold I noticed by the lack of deleting stale... and the high number of packages it was going to build that it was intending to rebuild all packages in the list. I don't seem to have a

FreeBSD Port: sge-6.2.2.1_3

2012-10-17 Thread Shaddox, William
I'm looking into the SGE for my work and handling the scheduling of our automation processes. The current setup works wonderfully but my boss and I are worried about the future since Oracle decided to not have an open source version. I was wondering, what are your thoughts about the future of

gettext or NLS changes ??

2012-10-17 Thread olli hauer
Hi, was there a change in forcing port builds with gettext or NLS in last time? I have many failing ports in tinderbox with an error similar to the following message (haven't had this issue ~10 days before) == /tb/a/builds/8.3-amd64-pkgng/tmp/make.log ==

Re: gettext or NLS changes ??

2012-10-17 Thread Greg Larkin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/17/12 3:49 PM, olli hauer wrote: Hi, was there a change in forcing port builds with gettext or NLS in last time? I have many failing ports in tinderbox with an error similar to the following message (haven't had this issue ~10 days

Re: gettext or NLS changes ??

2012-10-17 Thread olli hauer
On 2012-10-17 22:51, Greg Larkin wrote: On 10/17/12 3:49 PM, olli hauer wrote: Hi, was there a change in forcing port builds with gettext or NLS in last time? I have many failing ports in tinderbox with an error similar to the following message (haven't had this issue ~10 days before)