Account Blocked

[Support]

   Dear costumer,
  You have received this email because our system has noticed some
   suspicious activities with AÏÏle ID.Â
All what you need to keep enjoying all the benefits of your id is to
confirm your identity , follow the link below to start this process .
  [1]Confirm Now >
  Wondering why you got this email?
   Some massive failed login attempts were been made from unknown location
  that didnt match with your usual one , as a result we decided to
  suspend your account temporarily in order to protect it .
  This is an automated message. Please do not reply to this email.
   Thanks,
 Customer.Â

   TM and copyright © 2014  Inc. 1 Infinite Loop, MS 96-DM, Cupertino,
  CA 95014.

 All Rights Reserved / Keep Informed / Privacy Policy / My ID

References

   1. http://goo.gl/IsbNDo
___
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: Fwd: building java/eclipse in HEAD w/ poudriere: java.lang.OutOfMemoryError: Java heap space

[Matthias Apitz]

El día Sunday, August 24, 2014 a las 07:04:06AM +0200, Matthias Apitz escribió:

> El día Saturday, August 23, 2014 a las 04:49:26PM -0500, Bryan Drewery 
> escribió:
> 
> > Sorry it would not. I am mixing multiple ideas. We need to be able to
> > both limit the amount of memory a jail can use (RCTL) but also ensure
> > applications don't think they use all of hw.physmem for building. This
> > may be actually adding a feature to limit how much memory jails can
> > think they have. The openjdk ports peer into hw.physmem and assume they
> > have a ton of memory and fail to build once they hit the limits we've
> > put in place via ulimit or rctl. Eclipse is probably doing something
> > similar regarding guessing how much memory it can use.
> > 
> > Do you have MAX_MEMORY set in poudriere.conf? This would cause the
> > openjdk ports to fail if it is largely different than how much memory
> > you actually have.
> 
> No. I will set it now to 3 GByte and will let you know. I only have had
> in loader.conf:
> 
> kern.maxdsiz="1073741824"  # in bytes 1024*1024*1024
> kern.maxssiz="671088640"   # in bytes 65536*1024*10
> 

I have set MAX_MEMORY=3 in poudriere's conf file:

# fgrep MAX_MEM /usr/local/etc/poudriere.conf
MAX_MEMORY=3

(btw: it is not visible in the log file)

and have set also in make.conf:

MAVEN_OPTS="-Xmx1792m -XX:MaxPermSize=512m"

The built stops again at the same place after ~1 hour. I'm attaching the
first 142 lines and the last 200 lines of the log.

I run in another terminal a 'top -b -d10 -I' to see the memory
usage in the moment of the crash. Here it is when the java proc
is still running and 2 secs later when it went away:

last pid: 92498;  load averages:  2.52,  2.38,  2.21  up 0+01:38:0508:11:58
94 processes:  3 running, 91 sleeping
CPU: 91.7% user,  0.0% nice,  8.3% system,  0.0% interrupt,  0.0% idle
Mem: 886M Active, 2254M Inact, 266M Wired, 49M Cache, 90M Buf, 47M Free
Swap: 4096M Total, 1431M Used, 2664M Free, 34% Inuse, 28K In

  PID USERNAMETHR PRI NICE   SIZERES STATETIMEWCPU COMMAND
46713 root 26  520   465M   395M uwait   34:41  94.67% java
  803 guru  1  200 95640K 66984K select   2:18   2.49% Xorg
  868 guru  4  200   255M 54632K select   0:17   1.19% kwin
...

last pid: 92561;  load averages:  2.52,  2.38,  2.21  up 0+01:38:0708:12:00
94 processes:  4 running, 90 sleeping
CPU: 73.6% user,  0.0% nice, 17.1% system,  0.0% interrupt,  9.3% idle
Mem: 502M Active, 2254M Inact, 288M Wired, 49M Cache, 113M Buf, 408M Free
Swap: 4096M Total, 1431M Used, 2664M Free, 34% Inuse, 144K In

  PID USERNAMETHR PRI NICE   SIZERES STATETIMEWCPU COMMAND
  803 guru  1  200 95640K 66984K select   2:18   2.12% Xorg
  868 guru  4  200   255M 54632K RUN  0:17   0.62% kwin
 1216 root  1  520 10436K  1024K wait 0:05   0.34% sh
...

as you can see there is pretty much free RAM and swap space in the
system; the limit must be soemthing in the jail or the JVM itself.

HIH

matthias

folow head and tail of the build log:

>> Building java/eclipse
build started at Sun Aug 24 07:08:30 CEST 2014
port directory: /usr/ports/java/eclipse
building for: FreeBSD freebsd-head-ports-head-job-01 11.0-CURRENT FreeBSD 
11.0-CURRENT i386
maintained by: ljboi...@gmail.com
Makefile ident:  $FreeBSD: head/java/eclipse/Makefile 361589 2014-07-11 
21:56:01Z marino $
Poudriere version: 3.1-pre
Host OSVERSION: 1100028
Jail OSVERSION: 1100028

---Begin Environment---
OSVERSION=1100028
UNAME_v=FreeBSD 11.0-CURRENT
UNAME_r=11.0-CURRENT
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
SAVED_TERM=xterm
MASTERMNT=/usr/local/poudriere/data/.m/freebsd-head-ports-head/ref
PKG_EXT=txz
FORCE_PACKAGE=yes
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
POUDRIERE_BUILD_TYPE=bulk
PKGNG=1
PKGNAME=eclipse-4.3.2_1
PKG_DELETE=/usr/local/sbin/pkg-static delete -y -f
PKG_ADD=/usr/local/sbin/pkg-static add
OLDPWD=/root
PWD=/usr/local/poudriere/data/.m/freebsd-head-ports-head/ref/.p/pool
MASTERNAME=freebsd-head-ports-head
USER=root
HOME=/root
POUDRIERE_VERSION=3.1-pre
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
PKG_VERSION=/.p/pkg-static version
PKG_BIN=/usr/local/sbin/pkg-static
---End Environment---

---Begin OPTIONS List---
===> The following configuration options are available for eclipse-4.3.2_1:
> Options available for the single INSTALLPKG: you have to select exactly 
one of them
 FULL_SDK=on: Full SDK (JDT, PDE, source, API docs)
 PLATFORM_SDK=off: Platform with source, API Docs (no Java tools)
 PLATFORM=off: Platform only (no Java tools, no source or docs)
===> Use 'make config' to modify these settings
---End OPTIONS List---

--CONFIGURE_ARGS--

--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/java/eclipse/work  
XDG_CONFIG_HOME=/wrkdirs/usr/ports/java/eclipse/work  
HOME=/wrkdirs/usr/ports/java/eclipse/work TMPDIR="/tmp" 
XDG_DATA_H

Re: [CFT] New upstream snapshot of mplayer and mencoder

[Thomas Zander]

On 23 August 2014 10:33, Thomas Zander  wrote:

> Changes:
> - Fix regression with mplayer not displaying PGS subtitles

Regression has been fixed upstream, new tarball has arrived:
https://people.freebsd.org/~riggs/m20140824.tar.xz

Note that it may take a few hours for the new distfile to become fetchable.

Let me know if you have problems or notice further regressions.
Best wishes
Riggs
___
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"

pkg 1.3.6 output bug

[andrew clarke]

Installing a package built on another system I noticed pkg 1.3.6 shows
incorrect output when installing with a dependency:

# ls -l
total 41123
-rw-r--r--  1 ozzmosis  ozzmosis  2428 24 Aug 18:07 
clang-devel-3.6.r216160.txz
-rw-r--r--  1 ozzmosis  ozzmosis  19728928 24 Aug 18:08 
llvm-devel-3.6.r216160.txz
# pkg add clang-devel-3.6.r216160.txz
Installing llvm-devel-3.6.r216160: 100%
Installing llvm-devel-3.6.r216160: 100%
# pkg -v
1.3.6

ie. llvm-devel is output twice, clang-devel not at all.

Pretty sure this is a bug?

Thanks,

Regards
Andrew
___
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"

Legal services

[Anders Klinton]

 - This mail is in HTML. Some elements may be ommited in plain text. -

We are enquiring for an experience attorney to handle a breach of contract 
negotiation or a lawsuit.
Yours Sincerely,
Anders Klinton
Supply Management
Mölnlycke Health Care
Box 13080
SE-40252 Gothenburg, Sweden
Gamlestadsvägen 3C
Phone: 46851971490
www.molnlycke.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"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
games/tuxpaint  | 0.9.21  | 0.9.22
+-+
games/tuxpaint-config   | 0.0.12  | 0.0.13
+-+
games/tuxpaint-stamps   | 2009.06.28  | 2014.08.23
+-+
math/atlas-devel| 3.9.11  | 3.11.30
+-+
sysutils/replicant  | 0.2.1   | 0.6.4
+-+


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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Kurt Jaeger]

Hi!

> If you have further questions, please ask them on the freebsd-ports@
> mailing list, and feel free to Cc: me, but do make sure your mailer does
> not break threading, and do keep the Subject line intact.

For devel/ice:

If I run portupgrade, it says:

cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: 40 
41 42 43 44 46 47 48 6. Try: make debug-bdb

while the makefile says:

USE_BDB=5
INVALID_BDB_VER=40 41 42 43 44 46 47 48 6

and pkg info | grep ^db says:

db48-4.8.30.0_2The Berkeley DB package, revision 4.8
db5-5.3.28_1   The Oracle Berkeley DB, revision 5.3
db6-6.1.19 The Oracle Berkeley DB, revision 6.1

Any idea on how to fix this ?

-- 
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: portupgrade hash error message: HASH: Out of overflow pages. Increase page size

[Kurt Jaeger]

Hi!

> >> pkg info | grep ruby
> >>
> >> ruby-2.1.2,1   Object-oriented interpreted scripting 
> >> language
> >> ruby19-1.9.3.547,1 Object-oriented interpreted scripting 
> >> language
> >> ruby19-bdb-0.6.6_3 Ruby interface to Oracle Berkeley DB 
> >> revision 2 or later
> > 
> > After removing ruby-2.1, and a little cleanup, the message did not
> > re-appear.

> If you're willing to try again please install ruby2 and
> databases/ruby-bdb for ruby2 as well.

Done, now:

pkg info | grep ^ruby
ruby19-1.9.3.547,1 Object-oriented interpreted scripting language
ruby19-bdb-0.6.6_4 Ruby interface to Oracle Berkeley DB revision 2 
or later
ruby21-2.1.2,1 Object-oriented interpreted scripting language
ruby21-bdb6-0.6.6_4Ruby interface to Oracle Berkeley DB revision 2 
or later

and portupgrade-devel installed after ruby21, it works:

[Reading data from pkg(8) ... - 2247 packages found - done]
[Updating the portsdb  in /usr/ports ... - 24485 port entries 
found 
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000.23000.24000
 . done]

-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

> On 24 Aug 2014, at 12:28, Kurt Jaeger  wrote:
> 
> Hi!
> 
>> If you have further questions, please ask them on the freebsd-ports@
>> mailing list, and feel free to Cc: me, but do make sure your mailer does
>> not break threading, and do keep the Subject line intact.
> 
> For devel/ice:
> 
> If I run portupgrade, it says:
> 
> cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: 
> 40 41 42 43 44 46 47 48 6. Try: make debug-bdb
> 
> while the makefile says:
> 
> USE_BDB=5
> INVALID_BDB_VER=40 41 42 43 44 46 47 48 6
> 
> and pkg info | grep ^db says:
> 
> db48-4.8.30.0_2The Berkeley DB package, revision 4.8
> db5-5.3.28_1   The Oracle Berkeley DB, revision 5.3
> db6-6.1.19 The Oracle Berkeley DB, revision 6.1
> 
> Any idea on how to fix this ?

Is this exclusive to portupgrade (does "make install" work)? Ice only supports 
bdb 5, so the Makefile should be correct.

> 
> -- 
> 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"
___
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Kurt Jaeger]

Hi!

> > For devel/ice:
[...]
> Is this exclusive to portupgrade (does "make install" work)? Ice
> only supports bdb 5, so the Makefile should be correct.

No, it's not exclusive. Same behaviour with

# make
===>  Ice-3.5.1_1 cannot install: no eligible BerkeleyDB version. Requested: 6, 
incompatible: 40 41 42 43 44 46 47 48 6. Try: make debug-bdb.
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/ice

-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[olli hauer]

On 2014-08-24 13:11, Kurt Jaeger wrote:
> Hi!
> 
>>> For devel/ice:
> [...]
>> Is this exclusive to portupgrade (does "make install" work)? Ice
>> only supports bdb 5, so the Makefile should be correct.
> 
> No, it's not exclusive. Same behaviour with
> 
> # make
> ===>  Ice-3.5.1_1 cannot install: no eligible BerkeleyDB version. Requested: 
> 6, incompatible: 40 41 42 43 44 46 47 48 6. Try: make debug-bdb.
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/devel/ice
> 


Hm, using USE_BDB=$numble looks wrong to me in devel/ice.

Can you test the following patch.

Index: Makefile
===
--- devel/ice/Makefile(revision 365910)
+++ devel/ice/Makefile(working copy)
@@ -27,7 +27,8 @@
 .endif

 USES=  iconv gmake
-USE_BDB=   5
+USE_BDB=   yes
+WANT_BDB_VER=  5
 INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
 USE_LDCONFIG=  yes
 BUILD_WRKSRC?= ${WRKSRC}/cpp


-- 
olli
___
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

On Sun, 24 Aug 2014 13:39:06 +0200
olli hauer  wrote:

> On 2014-08-24 13:11, Kurt Jaeger wrote:
> > Hi!
> > 
> >>> For devel/ice:
> > [...]
> >> Is this exclusive to portupgrade (does "make install" work)? Ice
> >> only supports bdb 5, so the Makefile should be correct.
> > 
> > No, it's not exclusive. Same behaviour with
> > 
> > # make
> > ===>  Ice-3.5.1_1 cannot install: no eligible BerkeleyDB version.
> > Requested: 6, incompatible: 40 41 42 43 44 46 47 48 6. Try: make
> > debug-bdb. *** Error code 1
> > 
> > Stop.
> > make: stopped in /usr/ports/devel/ice
> > 
> 
> 
> Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> 
> Can you test the following patch.
> 
> Index: Makefile
> ===
> --- devel/ice/Makefile(revision 365910)
> +++ devel/ice/Makefile(working copy)
> @@ -27,7 +27,8 @@
>  .endif
> 
>  USES=  iconv gmake
> -USE_BDB=   5
> +USE_BDB=   yes
> +WANT_BDB_VER=  5
>  INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
>  USE_LDCONFIG=  yes
>  BUILD_WRKSRC?= ${WRKSRC}/cpp
> 
> 


@Kurt: Could you test and confirm? If this works, I'll commit the patch.

@Olli: Checking Mk/bsd.databasemk it seems like you're right. It's
quite amusing how this went unnoticed for so long, it has been in
there for eight years :)

r169835 | itetcu | 2006-08-06 18:53:56 +0200 (Sun, 06 Aug 2006) | 5
lines

convert to USE_BDB

PR: ports/101409
Submitted by:   Stefan Ehmann (maintainer)


-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Kurt Jaeger]

Hi!

> > Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> > 
> > Can you test the following patch.
> > 
> > Index: Makefile
> > ===
> > --- devel/ice/Makefile(revision 365910)
> > +++ devel/ice/Makefile(working copy)
> > @@ -27,7 +27,8 @@
> >  .endif
> > 
> >  USES=  iconv gmake
> > -USE_BDB=   5
> > +USE_BDB=   yes
> > +WANT_BDB_VER=  5
> >  INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
> >  USE_LDCONFIG=  yes
> >  BUILD_WRKSRC?= ${WRKSRC}/cpp

> @Kurt: Could you test and confirm? If this works, I'll commit the patch.

Yes, it builds.

-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

On Sun, 24 Aug 2014 14:30:06 +0200
Kurt Jaeger  wrote:

> Hi!
> 
> > > Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> > > 
> > > Can you test the following patch.
> > > 
> > > Index: Makefile
> > > ===
> > > --- devel/ice/Makefile(revision 365910)
> > > +++ devel/ice/Makefile(working copy)
> > > @@ -27,7 +27,8 @@
> > >  .endif
> > > 
> > >  USES=  iconv gmake
> > > -USE_BDB=   5
> > > +USE_BDB=   yes
> > > +WANT_BDB_VER=  5
> > >  INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
> > >  USE_LDCONFIG=  yes
> > >  BUILD_WRKSRC?= ${WRKSRC}/cpp
> 
> > @Kurt: Could you test and confirm? If this works, I'll commit the
> > patch.
> 
> Yes, it builds.
> 

I created a commit request

https://reviews.freebsd.org/D679

-- 
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: pkg 1.3.6 output bug

[Michael Gmelin]

On Sun, 24 Aug 2014 18:13:10 +1000
andrew clarke  wrote:

> Installing a package built on another system I noticed pkg 1.3.6 shows
> incorrect output when installing with a dependency:
> 
> # ls -l
> total 41123
> -rw-r--r--  1 ozzmosis  ozzmosis  2428 24 Aug 18:07
> clang-devel-3.6.r216160.txz -rw-r--r--  1 ozzmosis  ozzmosis
> 19728928 24 Aug 18:08 llvm-devel-3.6.r216160.txz # pkg add
> clang-devel-3.6.r216160.txz Installing llvm-devel-3.6.r216160: 100%
> Installing llvm-devel-3.6.r216160: 100%
> # pkg -v
> 1.3.6
> 
> ie. llvm-devel is output twice, clang-devel not at all.
> 
> Pretty sure this is a bug?
> 

I created a pull request that should fix the issue:
https://github.com/freebsd/pkg/pull/982


-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[olli hauer]

On 2014-08-24 14:37, Michael Gmelin wrote:
> 
> 
> On Sun, 24 Aug 2014 14:30:06 +0200
> Kurt Jaeger  wrote:
> 
>> Hi!
>>
 Hm, using USE_BDB=$numble looks wrong to me in devel/ice.

 Can you test the following patch.

 Index: Makefile
 ===
 --- devel/ice/Makefile(revision 365910)
 +++ devel/ice/Makefile(working copy)
 @@ -27,7 +27,8 @@
  .endif

  USES=  iconv gmake
 -USE_BDB=   5
 +USE_BDB=   yes
 +WANT_BDB_VER=  5
  INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
  USE_LDCONFIG=  yes
  BUILD_WRKSRC?= ${WRKSRC}/cpp
>>
>>> @Kurt: Could you test and confirm? If this works, I'll commit the
>>> patch.
>>
>> Yes, it builds.
>>
> 
> I created a commit request
> 
> https://reviews.freebsd.org/D679
> 

Kurt, or you can commit this even w.o. PR.
The patch does not break anything but allows the port to build as required.
I assume there are even more easter eggs in the tree, specially for USE_BDB.

-- 
olli
___
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

On Sun, 24 Aug 2014 15:08:07 +0200
olli hauer  wrote:

> On 2014-08-24 14:37, Michael Gmelin wrote:
> > 
> > 
> > On Sun, 24 Aug 2014 14:30:06 +0200
> > Kurt Jaeger  wrote:
> > 
> >> Hi!
> >>
>  Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> 
>  Can you test the following patch.
> 
>  Index: Makefile
>  ===
>  --- devel/ice/Makefile(revision 365910)
>  +++ devel/ice/Makefile(working copy)
>  @@ -27,7 +27,8 @@
>   .endif
> 
>   USES=  iconv gmake
>  -USE_BDB=   5
>  +USE_BDB=   yes
>  +WANT_BDB_VER=  5
>   INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
>   USE_LDCONFIG=  yes
>   BUILD_WRKSRC?= ${WRKSRC}/cpp
> >>
> >>> @Kurt: Could you test and confirm? If this works, I'll commit the
> >>> patch.
> >>
> >> Yes, it builds.
> >>
> > 
> > I created a commit request
> > 
> > https://reviews.freebsd.org/D679
> > 
> 
> Kurt, or you can commit this even w.o. PR.
> The patch does not break anything but allows the port to build as
> required. I assume there are even more easter eggs in the tree,
> specially for USE_BDB.
> 

I already committed it.


-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

On Sun, 24 Aug 2014 15:08:07 +0200
olli hauer  wrote:

> On 2014-08-24 14:37, Michael Gmelin wrote:
> > 
> > 
> > On Sun, 24 Aug 2014 14:30:06 +0200
> > Kurt Jaeger  wrote:
> > 
> >> Hi!
> >>
>  Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> 
>  Can you test the following patch.
> 
>  Index: Makefile
>  ===
>  --- devel/ice/Makefile(revision 365910)
>  +++ devel/ice/Makefile(working copy)
>  @@ -27,7 +27,8 @@
>   .endif
> 
>   USES=  iconv gmake
>  -USE_BDB=   5
>  +USE_BDB=   yes
>  +WANT_BDB_VER=  5
>   INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
>   USE_LDCONFIG=  yes
>   BUILD_WRKSRC?= ${WRKSRC}/cpp
> >>
> >>> @Kurt: Could you test and confirm? If this works, I'll commit the
> >>> patch.
> >>
> >> Yes, it builds.
> >>
> > 
> > I created a commit request
> > 
> > https://reviews.freebsd.org/D679
> > 
> 
> Kurt, or you can commit this even w.o. PR.
> The patch does not break anything but allows the port to build as
> required. I assume there are even more easter eggs in the tree,
> specially for USE_BDB.
> 

Committed it (this time from the correct email account)

-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

On Sun, 24 Aug 2014 15:08:07 +0200
olli hauer  wrote:

> On 2014-08-24 14:37, Michael Gmelin wrote:
> > 
> > 
> > On Sun, 24 Aug 2014 14:30:06 +0200
> > Kurt Jaeger  wrote:
> > 
> >> Hi!
> >>
>  Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> 
>  Can you test the following patch.
> 
>  Index: Makefile
>  ===
>  --- devel/ice/Makefile(revision 365910)
>  +++ devel/ice/Makefile(working copy)
>  @@ -27,7 +27,8 @@
>   .endif
> 
>   USES=  iconv gmake
>  -USE_BDB=   5
>  +USE_BDB=   yes
>  +WANT_BDB_VER=  5
>   INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
>   USE_LDCONFIG=  yes
>   BUILD_WRKSRC?= ${WRKSRC}/cpp
> >>
> >>> @Kurt: Could you test and confirm? If this works, I'll commit the
> >>> patch.
> >>
> >> Yes, it builds.
> >>
> > 
> > I created a commit request
> > 
> > https://reviews.freebsd.org/D679
> > 
> 
> Kurt, or you can commit this even w.o. PR.
> The patch does not break anything but allows the port to build as
> required. I assume there are even more easter eggs in the tree,
> specially for USE_BDB.
> 

A short grep shows that the following ports are affected, the question
is if simply converting them to

USE_BDB=yes
WANT_BDB_VER=   

is the right thing to do.

archivers/rpm4/Makefile
chinese/xsim/Makefile
comms/trustedqsl/Makefile
comms/xastir/Makefile
databases/dbtool/Makefile
databases/evolution-data-server/Makefile
databases/fortytwo-bdb/Makefile
databases/libgda5/Makefile
databases/memcachedb/Makefile
databases/memcacheq/Makefile
databases/p5-BDB/Makefile
databases/p5-BerkeleyDB/Makefile
databases/py-bsddb/Makefile
databases/py-bsddb3/Makefile
databases/rdfdb/Makefile
devel/apr1/Makefile
devel/libqxt/Makefile
dns/dnshistory/Makefile
editors/nvi-devel/Makefile
graphics/fortytwo/Makefile
japanese/mutt-devel/Makefile
mail/avenger/Makefile
mail/bogofilter/Makefile
mail/dk-milter/Makefile
mail/drac/Makefile
mail/evolution-exchange/Makefile
mail/greyfix/Makefile
mail/isync/Makefile
mail/meta1/Makefile
mail/mutt/Makefile
mail/opendkim/Makefile
mail/spamprobe/Makefile
net-p2p/cdonkey/Makefile
net/freeswitch-core-devel/Makefile
net/netatalk/Makefile
net/netatalk3/Makefile
net/openldap24-server/Makefile
news/inn/Makefile
science/gramps/Makefile
security/pks/Makefile
security/sks/Makefile
sysutils/apt/Makefile
sysutils/cfengine22/Makefile
sysutils/cfengine32/Makefile
www/oops/Makefile



-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

On Sun, 24 Aug 2014 15:36:18 +0200
Michael Gmelin  wrote:

> On Sun, 24 Aug 2014 15:08:07 +0200
> olli hauer  wrote:
> 
> > On 2014-08-24 14:37, Michael Gmelin wrote:
> > > 
> > > 
> > > On Sun, 24 Aug 2014 14:30:06 +0200
> > > Kurt Jaeger  wrote:
> > > 
> > >> Hi!
> > >>
> >  Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> > 
> >  Can you test the following patch.
> > 
> >  Index: Makefile
> >  ===
> >  --- devel/ice/Makefile(revision 365910)
> >  +++ devel/ice/Makefile(working copy)
> >  @@ -27,7 +27,8 @@
> >   .endif
> > 
> >   USES=  iconv gmake
> >  -USE_BDB=   5
> >  +USE_BDB=   yes
> >  +WANT_BDB_VER=  5
> >   INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
> >   USE_LDCONFIG=  yes
> >   BUILD_WRKSRC?= ${WRKSRC}/cpp
> > >>
> > >>> @Kurt: Could you test and confirm? If this works, I'll commit
> > >>> the patch.
> > >>
> > >> Yes, it builds.
> > >>
> > > 
> > > I created a commit request
> > > 
> > > https://reviews.freebsd.org/D679
> > > 
> > 
> > Kurt, or you can commit this even w.o. PR.
> > The patch does not break anything but allows the port to build as
> > required. I assume there are even more easter eggs in the tree,
> > specially for USE_BDB.
> > 

@Kurt: I assume you have WITH_BDB_VER= 6 in your make.conf?

> 
> A short grep shows that the following ports are affected, the question
> is if simply converting them to
> 
> USE_BDB=  yes
> WANT_BDB_VER= 
> 
> is the right thing to do.
> 

To answer my own question: Probably not, as it seems legal to use
USE_BDB= , which *should* (or at least used to) have the same
effect as

USE_BDB= yes
WITH_BDB_VER= 

I'm a bit curious what the correct use of INVALID_BDB_VER is, since it
seems incompatible with using WITH_BDB_VER in make.conf, so in the end
a port always has to specify WANT_BDB_VER if you want to ensure it
builds correctly.

Also, using INVALID_BDB_VER in devel/ice seems redundant now:

USE_BDB= yes
WANT_BDB_VER= 5
INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6

I assume that

USE_BDB= yes
WANT_BDB_VER= 5

will accomplish the same.

- Michael

-- 
Michael Gmelin
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Dennis Glatting]

On Sun, 2014-08-24 at 15:08 +0200, olli hauer wrote:
> On 2014-08-24 14:37, Michael Gmelin wrote:
> > 
> > 
> > On Sun, 24 Aug 2014 14:30:06 +0200
> > Kurt Jaeger  wrote:
> > 
> >> Hi!
> >>
>  Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
> 
>  Can you test the following patch.
> 
>  Index: Makefile
>  ===
>  --- devel/ice/Makefile(revision 365910)
>  +++ devel/ice/Makefile(working copy)
>  @@ -27,7 +27,8 @@
>   .endif
> 
>   USES=  iconv gmake
>  -USE_BDB=   5
>  +USE_BDB=   yes
>  +WANT_BDB_VER=  5
>   INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
>   USE_LDCONFIG=  yes
>   BUILD_WRKSRC?= ${WRKSRC}/cpp
> >>
> >>> @Kurt: Could you test and confirm? If this works, I'll commit the
> >>> patch.
> >>
> >> Yes, it builds.
> >>
> > 
> > I created a commit request
> > 
> > https://reviews.freebsd.org/D679
> > 
> 
> Kurt, or you can commit this even w.o. PR.
> The patch does not break anything but allows the port to build as required.
> I assume there are even more easter eggs in the tree, specially for USE_BDB.
> 

Yep:

root@Junker# more databases/evolution-data-server/Makefile 

...

USE_BDB=41+






___
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Kurt Jaeger]

Hi!

> > >  Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
[...]
> > >   USES=  iconv gmake
> > >  -USE_BDB=   5
> > >  +USE_BDB=   yes
> > >  +WANT_BDB_VER=  5
> > >   INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
> > >   USE_LDCONFIG=  yes
> > >   BUILD_WRKSRC?= ${WRKSRC}/cpp

> > > Kurt, or you can commit this even w.o. PR.

Sorry, was offline since last mail...

> > > The patch does not break anything but allows the port to build as
> > > required. I assume there are even more easter eggs in the tree,
> > > specially for USE_BDB.

> @Kurt: I assume you have WITH_BDB_VER= 6 in your make.conf?

Correct.

> I'm a bit curious what the correct use of INVALID_BDB_VER is, since it
> seems incompatible with using WITH_BDB_VER in make.conf, so in the end
> a port always has to specify WANT_BDB_VER if you want to ensure it
> builds correctly.
> 
> Also, using INVALID_BDB_VER in devel/ice seems redundant now:
> 
> USE_BDB= yes
> WANT_BDB_VER= 5
> INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
> 
> I assume that
> 
> USE_BDB= yes
> WANT_BDB_VER= 5
> 
> will accomplish the same.

Many alternatives -- which one is the right one ?

-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Scot Hetzel]

On Sun, Aug 24, 2014 at 7:20 AM, Michael Gmelin  wrote:
> @Olli: Checking Mk/bsd.databasemk it seems like you're right. It's
> quite amusing how this went unnoticed for so long, it has been in
> there for eight years :)
>

As the original author of the USE_BDB code, the USE_BDB=5  had worked
in the past.  As it is supposed to mean that this port only uses that
version of BDB.  The code was changed on Aug 21 (r365599) and the
author of the new code might have forgot to test this case.

-- 
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Michael Gmelin]

On Sun, 24 Aug 2014 11:59:37 -0500
Scot Hetzel  wrote:

> On Sun, Aug 24, 2014 at 7:20 AM, Michael Gmelin 
> wrote:
> > @Olli: Checking Mk/bsd.databasemk it seems like you're right. It's
> > quite amusing how this went unnoticed for so long, it has been in
> > there for eight years :)
> >
> 
> As the original author of the USE_BDB code, the USE_BDB=5  had worked
> in the past.  As it is supposed to mean that this port only uses that
> version of BDB.  The code was changed on Aug 21 (r365599) and the
> author of the new code might have forgot to test this case.
> 

Not sure if you read the rest of the thread, but this is still working
as intended (I tested using both the old and new version).

The issue is, that USE_BDB=version means USE_BDB=yes,
WITH_BDB_VER=version, but Kurt has WITH_BDB_VER=6 in make.conf,
which overrides this version number and version =6 is invalid for
devel/ice. So basically it works as designed, Kurt wanted a specific
version of bdb, which doesn't work for devel/ice.

The fix was to add WANT_BDB_VER= 5 in devel/ice, which I guess is ok,
since this is the only version it really works with (and I guess I
could remove the INVALID directive now, since WANT means really
*want*).

My question is, what the point of INVALID_BDB_VER really is in this
case, it seems a bit pointless to me given the trouble it caused Kurt
and how we resolved this. Having a fully specified list of supported
versions in WANT_BDB_VER seems better in this case (assuming WANT
supports listing multiple versions).

-- 
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: pkg 1.3.6 output bug

[Bryan Drewery]

On 8/24/2014 7:55 AM, Michael Gmelin wrote:
> On Sun, 24 Aug 2014 18:13:10 +1000
> andrew clarke  wrote:
> 
>> Installing a package built on another system I noticed pkg 1.3.6 shows
>> incorrect output when installing with a dependency:
>>
>> # ls -l
>> total 41123
>> -rw-r--r--  1 ozzmosis  ozzmosis  2428 24 Aug 18:07
>> clang-devel-3.6.r216160.txz -rw-r--r--  1 ozzmosis  ozzmosis
>> 19728928 24 Aug 18:08 llvm-devel-3.6.r216160.txz # pkg add
>> clang-devel-3.6.r216160.txz Installing llvm-devel-3.6.r216160: 100%
>> Installing llvm-devel-3.6.r216160: 100%
>> # pkg -v
>> 1.3.6
>>
>> ie. llvm-devel is output twice, clang-devel not at all.
>>
>> Pretty sure this is a bug?
>>
> 
> I created a pull request that should fix the issue:
> https://github.com/freebsd/pkg/pull/982
> 
> 

Thanks!

This was on my list to fix before 1.3.7.

It is really noticeable in ports with poudriere as well.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

[QAT] 365614: 4x depend (ignored: is marked as broken: unfetchable in graphics/dcraw-m), 4x dud, 104x success, 4x leftovers

[Ports-QAT]

Canonicalize a few LICENSE_PERMS

With hat:   portmgr
-

  Build ID:  20140822072205-7569
  Job owner: anto...@freebsd.org
  Buildtime: 2 days
  Enddate:   Sun, 24 Aug 2014 18:53:12 GMT

  Revision:  365614
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=365614

-

Port:databases/tdbc 1.0.0

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400406/tdbc-1.0.0.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400407/tdbc-1.0.0.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400408/tdbc-1.0.0.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400409/tdbc-1.0.0.log

-

Port:devel/icu 53.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400410/icu-53.1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400411/icu-53.1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400412/icu-53.1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400413/icu-53.1.log

-

Port:devel/p5-Sys-Trace 0.03

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400414/p5-Sys-Trace-0.03.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400415/p5-Sys-Trace-0.03.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400416/p5-Sys-Trace-0.03.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400417/p5-Sys-Trace-0.03.log

-

Port:devel/p5-Thread-Apartment 0.51

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400418/p5-Thread-Apartment-0.51.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400419/p5-Thread-Apartment-0.51.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400420/p5-Thread-Apartment-0.51.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400421/p5-Thread-Apartment-0.51.log

-

Port:devel/p5-Thread-Queue-Duplex 0.92

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400422/p5-Thread-Queue-Duplex-0.92.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400423/p5-Thread-Queue-Duplex-0.92.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400424/p5-Thread-Queue-Duplex-0.92.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400425/p5-Thread-Queue-Duplex-0.92.log

-

Port:devel/tcllib 1.16

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400426/tcllib-1.16.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140822072205-7569-400427/tcllib-1.16.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https:/

Re: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Kurt Jaeger]

Hi!

There is the possible mechanism of

WITH_BDB_VER=6

in /etc/make.conf.

Is there a way to also add some

DEFAULT_VERSIONS= bdb=6

like syntax in /usr/ports/Mk/bsd.default-versions.mk to keep the
mechanism similar to other "default versions" ?

-- 
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"

net/rabbitmq-c-devel and cmake hints needed (PR 186690)

[Kurt Jaeger]

Hi!

I'm trying to upgrade net/rabbitmq-c-devel and prepared a patch
for it. If someone understands more about cmake and the magic
behind it, I would appreciate it.

It builds fine on my host populated with approx. 2200 packages:

http://people.freebsd.org/~pi/misc/non-verbose-build.txt

Building it in poudriere, some bin/ stuff is not build (why?) and
the commands are displayed, so it's much more verbose
(why is it more verbose?).

http://people.freebsd.org/~pi/misc/verbose-build.txt

Thanks for any hint!

-- 
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: net/rabbitmq-c-devel and cmake hints needed (PR 186690)

[Antoine Brodin]

On Sun, Aug 24, 2014 at 10:21 PM, Kurt Jaeger  wrote:
> Hi!
>
> I'm trying to upgrade net/rabbitmq-c-devel and prepared a patch
> for it. If someone understands more about cmake and the magic
> behind it, I would appreciate it.
>
> It builds fine on my host populated with approx. 2200 packages:
>
> http://people.freebsd.org/~pi/misc/non-verbose-build.txt
>
> Building it in poudriere, some bin/ stuff is not build (why?) and
> the commands are displayed, so it's much more verbose
> (why is it more verbose?).
>
> http://people.freebsd.org/~pi/misc/verbose-build.txt
>
> Thanks for any hint!


Hi,

>From Uses/cmake.mk:

.if defined(BATCH) || defined(PACKAGE_BUILDING)
CMAKE_VERBOSE=  yes
CMAKE_NOCOLOR=  yes
.endif

For the tools,  it seems they need POPT and you didn't select the
option in poudriere.

Cheers,

Antoine
___
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/rabbitmq-c-devel and cmake hints needed (PR 186690)

[Kurt Jaeger]

Hi!

> >From Uses/cmake.mk:
> 
> .if defined(BATCH) || defined(PACKAGE_BUILDING)
> CMAKE_VERBOSE=  yes
> CMAKE_NOCOLOR=  yes
> .endif

Ah, thanks!

> For the tools,  it seems they need POPT and you didn't select the
> option in poudriere.

Thanks! That was indeed the problem!

-- 
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: Fwd: Pecl-amqp and rabbitmq-c-devel

[Kurt Jaeger]

Hi!

> > It is possible to do something with this :
> > 
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186690
> > 
> > We very need rabbitmq-c-devel ane pecl-amqp (1.4.x) for develop ..
> 
> I updated the diff, it now builds on my testhost, but in poudriere it is
> not building, so probably some BUILD_DEPENDS is still missing.

With the help from antoine@, rabbitmq-c-devel is now updated to 0.5.1.

I'll have a look at 186691 tomorrow evening.

-- 
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"

poudriere+pkg vs ports make (re)install

[Russell L. Carter]

Greetings,

I am not understanding something about the interaction of
poudriere+pkg vs. make reinstall in the ports tree.  Perhaps
someone could enlighten me.

I am trying to track down a bug on all my systems with
print/cups-filters.

I see the bug in /var/log/cups/error_log:

Running command line for /usr/local/bin/pdftops: /usr/local/bin/pdftops
-level3 /var/spool/cups/tmp/08b655407eada -

Unable to execute pdftops program: No such file or directory

And then I run

# /usr/local/bin/pdftops 2>&1 | head
pdftops version 0.24.5
Copyright 2005-2013 The Poppler Developers - http://poppler.freedesktop.org
Copyright 1996-2011 Glyph & Cog, LLC

So the file is there, it's executable, and it's poppler's pdftops.
Looks good.

Ok.  Now here's what I don't understand.  I've updated the local
/usr/ports tree, and built and reinstalled print/cups-filters with the
default options, and pkg info shows me this:

cups-filters-1.0.57
Name   : cups-filters
Version: 1.0.57

(This procedure results in a working cups-filters that can print, BTW)

While poudriere's broken version, installed via pkg, shows me this
with pkg info:

cups-filters-1.0.57_1
Name   : cups-filters
Version: 1.0.57_1

What's going on?  My /usr/ports tree is more recent than poudriere's
(not by much), but poudriere's install version supercedes the
/usr/ports tree.  (Both use portsnap to update their trees)

Thanks,
Russell
___
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] 365676: 4x leftovers

[Ports-QAT]

net-mgmt/pandorafms_server: fix startup script

PR: 192915
Submitted by:   maintainer
-

  Build ID:  20140822165601-43729
  Job owner: w...@freebsd.org
  Buildtime: 2 days
  Enddate:   Sun, 24 Aug 2014 23:00:50 GMT

  Revision:  365676
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=365676

-

Port:net-mgmt/pandorafms_server 5.1.0_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20140822165601-43729-400858/pandora_server-5.1.0_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20140822165601-43729-400859/pandora_server-5.1.0_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20140822165601-43729-400860/pandora_server-5.1.0_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20140822165601-43729-400861/pandora_server-5.1.0_1.log


--
Buildarchive URL: 
redports 
___
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"

Update for net-mgmt/ocsinventory-agent

[Philippe BEAUMONT]

Hi,

I'm really new in the freebsd community and I want to propose my very 
first port.


I have take a look on the actual net-mgmt/ocsinventory-agent Makefile 
and I see that the current package cannot work.


For exemple, dmidecode is in build depend section or it's one of the 
most important dependence for this software to work correctly.


As the current port is not up to date, I made a patch with the last 
version and somes correction in the dependence list. I also add somes 
optionnal build options with most important as default. I have remove 
the patch and use the standard option for Makefile.PL to disable the 
post install script.


I need review to improve it if necessary.

Thanks for your time,

Philippe BEAUMONT

Index: Makefile
===
--- Makefile	(revision 366019)
+++ Makefile	(working copy)
@@ -1,10 +1,10 @@
 # $FreeBSD$
 
 PORTNAME=	Ocsinventory
-PORTVERSION=	2.0.5
+PORTVERSION=	2.1.1
 PORTEPOCH=	1
 CATEGORIES=	net-mgmt
-MASTER_SITES=	http://launchpad.net/ocsinventory-unix-agent/stable-2.0/${PORTVERSION}/+download/
+MASTER_SITES=	http://launchpad.net/ocsinventory-unix-agent/stable-2.1/${PORTVERSION}/+download/
 PKGNAMESUFFIX=	-Unix-Agent
 DISTNAME=	${PORTNAME}${PKGNAMESUFFIX}-${PORTVERSION}
 
@@ -13,17 +13,42 @@
 
 LICENSE=	GPLv2
 
-RUN_DEPENDS=	p5-libwww>=0:${PORTSDIR}/www/p5-libwww \
+RUN_DEPENDS=	lspci:${PORTSDIR}/sysutils/pciutils \
 		p5-XML-Simple>=0:${PORTSDIR}/textproc/p5-XML-Simple \
 		p5-Net-IP>=0:${PORTSDIR}/net-mgmt/p5-Net-IP \
-		p5-Proc-Daemon>=0:${PORTSDIR}/devel/p5-Proc-Daemon
-BUILD_DEPENDS=	dmidecode:${PORTSDIR}/sysutils/dmidecode \
-		lspci:${PORTSDIR}/sysutils/pciutils
+		p5-Proc-Daemon>=0:${PORTSDIR}/devel/p5-Proc-Daemon \
+		dmidecode:${PORTSDIR}/sysutils/dmidecode \
+		p5-Digest-MD5>=0:${PORTSDIR}/security/p5-Digest-MD5
 
 USES=		perl5
 USE_PERL5=	configure
+CONFIGURE_ENV=	PERL_AUTOINSTALL=1
 WRKSRC=		${WRKDIR}/${PORTNAME}${PKGNAMESUFFIX}-${PORTVERSION}
 SUB_FILES=	pkg-message
 SUB_LIST=	SITE_PERL=${SITE_PERL}
 
+# define options
+OPTIONS_DEFINE=	DAEMON IPMI SSL PRINTER SNMP
+
+DAEMON_DESC=	Daemon mode
+IPMI_DESC=	Collect information about IPMI
+SSL_DESC=	Get SSL communications working
+PRINTER_DESC=	Printers detection
+SNMP_DESC=	Scan network devices using SNMP
+
+# define default options
+OPTIONS_DEFAULT=	SSL SNMP
+
+DAEMON_RUN_DEPENDS=	p5-Proc-Daemon>=0:${PORTSDIR}/devel/p5-Proc-Daemon \
+			p5-Proc-PID-File>=0:${PORTSDIR}/devel/p5-Proc-PID-File
+IPMI_RUN_DEPENDS=	ipmitool:${PORTSDIR}/sysutils/ipmitool
+SSL_RUN_DEPENDS=	p5-Crypt-SSLeay>=0:${PORTSDIR}/security/p5-Crypt-SSLeay \
+			p5-LWP-Protocol-https>=0:${PORTSDIR}/www/p5-LWP-Protocol-https
+PRINTER_RUN_DEPENDS=	p5-Net-CUPS>=0:${PORTSDIR}/print/p5-Net-CUPS
+SNMP_RUN_DEPENDS=	p5-Net-SNMP>=0:${PORTSDIR}/net-mgmt/p5-Net-SNMP \
+			p5-Net-Netmask>=0:${PORTSDIR}/net-mgmt/p5-Net-Netmask \
+			p5-Net-Ping>=0:${PORTSDIR}/net/p5-Net-Ping \
+			p5-Nmap-Parser>=0:${PORTSDIR}/security/p5-Nmap-Parser \
+			nmap:${PORTSDIR}/security/nmap
+
 .include 
Index: distinfo
===
--- distinfo	(revision 366019)
+++ distinfo	(working copy)
@@ -1,2 +1,2 @@
-SHA256 (Ocsinventory-Unix-Agent-2.0.5.tar.gz) = 7ef1c25dce5f1e0854abc423513c1733219cc73e4c36057dbdad6757e1609a64
-SIZE (Ocsinventory-Unix-Agent-2.0.5.tar.gz) = 1707443
+SHA256 (Ocsinventory-Unix-Agent-2.1.1.tar.gz) = dc321bc23c73c7d2147e80082f993e0c3faaca8195126050b86d9d3da7cc63a3
+SIZE (Ocsinventory-Unix-Agent-2.1.1.tar.gz) = 1851193
Index: files/patch-Makefile.PL
===
--- files/patch-Makefile.PL	(revision 366019)
+++ files/patch-Makefile.PL	(working copy)
@@ -1,12 +0,0 @@
 Makefile.PL.orig	2011-01-04 17:59:37.0 +
-+++ Makefile.PL	2011-01-04 18:00:04.0 +
-@@ -11,7 +11,8 @@
- install :: all pure_install doc_install
- 	$(NOECHO) $(NOOP)';
- 
--	$re .= "\n\t[ ! -f run-postinst ] || $^X postinst.pl\n";
-+# Disable the post install script
-+#	$re .= "\n\t[ ! -f run-postinst ] || $^X postinst.pl\n";
- 
- return $re;
- }
Index: files/pkg-message.in
===
--- files/pkg-message.in	(revision 366019)
+++ files/pkg-message.in	(working copy)
@@ -1,10 +1,10 @@
 *
 
-This port disabled the post installtion script during the build
+This port disabled the post installation script during the build
 process to allow the package to be built without interaction.
 
 If you wish to run this script it is located here:
-%%SITE_PERL%%/Ocsinventory/postinst.pl
+%%SITE_PERL%%/Ocsinventory/Unix/postinst.pl
 
 Note: It may not be required to run this script depending on 
 your environment.
Index: pkg-plist
===
--- pkg-plist	(revision 366019)
+++ pkg-plist	(working copy)
@@ -1,4 +1,8 @@
 bin/ocsinventory

Re: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/15/14 13:14, Naram Qashat wrote:

On 08/12/14 14:11, Patrick Powell wrote:

On 08/09/14 18:15, Naram Qashat wrote:

On 08/09/14 19:45, Scot Hetzel wrote:

On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat  wrote:

On 08/04/14 07:28, David Wolfskill wrote:


On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote:


On 08/03/14 22:14, David Wolfskill wrote:


On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote:


...
If there is
a way to find out when any process is attempting to modify a file, that
would
probably help me narrow it down, but I'm not aware of anything that can
do that,
...



Well, "chflags schg /usr/ports/INDEX*" would *prevent* the modification


...
This was a really good suggestion.



Glad to help.  :-)

Peace,
david



OK, so while no programs have whined or complained, I get the feeling that
something on my system is running portsnap without my knowledge. When I had
set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg
flag on that as well, and now I notice there are a bunch of files called
.fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a
file called .portsnap.INDEX. As far as I know, I don't have anything
configured to run portsnap, but is there something that defaults to running
portsnap occasionally? I couldn't find anything that would do that.



Do your have a crontab entry that is running portsnap with the -I
(update INDEX) option?

http://www.pl.freebsd.org/doc/handbook/portsnap.html


As far as I can tell, no, none of my crontabs have any references to portsnap
in them. This is making me a bit stumped as to why it would be happening. I
checked the main /etc/crontab, I checked the crontabs in /var/cron/tabs. I
have searched inside of /etc and /usr/local/etc for anything related to
portsnap. Nothing that would be doing this is coming up at all.

Thanks,
Naram Qashat
___
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"


I ran into something similar once,  and found out what was happening this way.

1.  replace the portsnap executable with a shell script.  Rename portsnap to
something
  like /usr/sbin/portsnap.orig
2.  This shell script should dump the current ENV and other stuff to a log file.
Don't forget to put in a timestamp.
And then do:
   exec /usr/sbin/portsnap.orig $*

I did this and found that there was something in one of the .login scripts.
G...


I really liked this suggestion, and did just that. Unfortunately, it seems that
portsnap may not be the culprit here, as I haven't had any log files created
from my modified script nor is there a .portsnap.INDEX file being created after
I deleted the one that was there, but I still have a bunch of
.fetch.??.INDEX-9.bz2 files in /usr/ports. I've been trying to search for
anything on my system that even references INDEX-9, but I can't find anything
else that would cause this to happen.

Thanks,
Naram Qashat


Well, I finally figured out what the culprit was. Webmin was configured to do 
automatic updates and it was running "make fetchindex" on the ports tree. I 
disabled that and now it has stopped trying to download the index. I only 
managed to track that down after noticing that the fetchindex target was the 
only other thing that could have downloaded the index file, and modifying 
/usr/ports/Makefile so it would write the contents of 
/proc/${.MAKE.PPID}/cmdline to a file so I could see what was invoking make. The 
.MAKE.PPID variable was pointed out to me on IRC.


Thanks,
Naram Qashat
___
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: Does www/chromium work?

[Robert Backhaus]

The only issue I'm having with chromium is that select-and-middle-click
pasting is broken.


On 21 August 2014 00:47, Russell L. Carter  wrote:

>
>
> On 08/20/14 07:10, René Ladan wrote:
> > 2014-08-20 16:00 GMT+02:00 Russell L. Carter :
> >
> >>
> >>
> >> On 08/20/14 02:51, Ivan Voras wrote:
> >>> Hello,
> >>
> >> [...]
> >>
> >>> This is chromium-36.0.1985.143_1 on FreeBSD 10.0-RELEASE-p1. Is
> >>> anybody running chromium?
> >>>
> >>>
> >>
> >> I'm running 36.0.1985.143_1 on a somewhat fresh -current, installed from
> >> a pkg built by poudriere, using the ports protobuf library.  No
> >> segfaults, but x-selection pasting into the search bar doesn't work.
> >> Sometimes ^C/^V does work.
> >
> >
> > Indeed, as long as you do not sign in to the browser it works.
>
> Aha.  I was already logged in from the previous version and everything
> worked.  So I logged out, and then logged in.  Voila!
> Segfaults reliably now on startup.  Oops.
>
> I guess it's firefox for now.
>
> >
> > For the copy/paste issue:
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192748
> > but this is relatively minor issue I think, and chromium 37 should arrive
> > in two or three weeks.
>
> Righto.
> Thanks,
> Russell
>
> > René
> > ___
> > 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"
>
___
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: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[Scot Hetzel]

On Sun, Aug 24, 2014 at 12:16 PM, Michael Gmelin  wrote:
>
>
> On Sun, 24 Aug 2014 11:59:37 -0500
> Scot Hetzel  wrote:
>
>> On Sun, Aug 24, 2014 at 7:20 AM, Michael Gmelin 
>> wrote:
>> > @Olli: Checking Mk/bsd.databasemk it seems like you're right. It's
>> > quite amusing how this went unnoticed for so long, it has been in
>> > there for eight years :)
>> >
>>
>> As the original author of the USE_BDB code, the USE_BDB=5  had worked
>> in the past.  As it is supposed to mean that this port only uses that
>> version of BDB.  The code was changed on Aug 21 (r365599) and the
>> author of the new code might have forgot to test this case.
>>
>
> Not sure if you read the rest of the thread, but this is still working
> as intended (I tested using both the old and new version).
>
> The issue is, that USE_BDB=version means USE_BDB=yes,
> WITH_BDB_VER=version, but Kurt has WITH_BDB_VER=6 in make.conf,
> which overrides this version number and version =6 is invalid for
> devel/ice. So basically it works as designed, Kurt wanted a specific
> version of bdb, which doesn't work for devel/ice.
>
> The fix was to add WANT_BDB_VER= 5 in devel/ice, which I guess is ok,
> since this is the only version it really works with (and I guess I
> could remove the INVALID directive now, since WANT means really
> *want*).
>

Hmm, I thought I had it implemented this way at one time.  Any way.
What we should be doing with the WITH_BDB_VER is not overriding the
USE_BDB value.  Instead we should see if it is a VALID version to use
for this port, if it is not, then use the USE_BDB value.

So basically the code should be doing the following:

USE_BDB=yes
 - use the default version (48+) or the installed version if higher

USE_BDB=yes, WITH_BDB_VER=6
 - use version 6

USE_BDB=5
 - should mean the same as USE_BDB=yes, WANT_BDB_VER=5
 - shouldn't be able to override by setting WITH_BDB_VER=6
 - this would also allow the removal of the WANT_BDB_VER variable.
 - no error should be generated when WITH_BDB_VER is set to an invalid version

USE_BDB=48 6
 - use (either 48 or 6) or the installed version that matches one of
these versions
 - no error should be generated when WITH_BDB_VER is set to an invalid version

USE_BDB=5+, WITH_BDB_VER=48
 - use version 5+ or the installed version if higher
 - shouldn't allow downgrade to a lower unsupported version by setting
the WITH_BDB_VER
 -- should we still display an error in this case or just install the
port with bdb 5+?

If we make the above changes to the code, then INVALID_BDB_VER and
WANT_BDB_VER could disappear.

> My question is, what the point of INVALID_BDB_VER really is in this
> case, it seems a bit pointless to me given the trouble it caused Kurt
> and how we resolved this. Having a fully specified list of supported
> versions in WANT_BDB_VER seems better in this case (assuming WANT
> supports listing multiple versions).
>

At the time I had implemented the code, INVALID_BDB_VER was meant to
poke holes in the VER+:

USE_BDB=2+
INVALID_BDB_VER=3

So the port would be able to use version 2 and 40+, and not 3.
Probably should have just implanted it as:

USE_BDB=2 40+

 and skipped the INVALID_BDB_VER entirely.

I was also thinking that we should make WITH_BDB_HIGHEST the default.
It is used by VER+ when multiple versions of bdb are installed.   That
way we can remove this variable also.

-- 
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: Fwd: Pecl-amqp and rabbitmq-c-devel

[Kurt Jaeger]

Hi!

> I'll have a look at 186691 tomorrow evening.

pecl-amqp is now at 1.4.0.

-- 
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"