FreeBSD ports you maintain which are out of date

2014-01-14 Thread 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,

Re: security/libssh does not install ssh_threads

2014-01-14 Thread Dima Panov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 14.01.14, 9:29, Peter Klett ?: Hi, I'm currently trying to compile the nogui version of net-p2p/retroshare which has a dependency to libssh-0.5.4. In its Makefile it includes -lssh and -lssh_threads but the later is not build / installed by

cpuminer mines only on one core regardless of --threads option

2014-01-14 Thread Alexander
Hello! on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer from ports and by pkg install - result is the same - minerd mines only on one core regardless of --threads option. If I start with --threads 1 for example --threads=3 - minerd start 3 threads BUT in ONE core - so in

Re: cpuminer mines only on one core regardless of --threads option

2014-01-14 Thread Volodymyr Kostyrko
14.01.2014 15:01, Alexander написав(ла): Hello! on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer from ports and by pkg install - result is the same - minerd mines only on one core regardless of --threads option. If I start with --threads 1 for example --threads=3 - minerd

Re: cpuminer mines only on one core regardless of --threads option

2014-01-14 Thread Alexander
14.01.2014, 17:55, Volodymyr Kostyrko c.kw...@gmail.com: minerd itself doesn't bind any process/thread to any specific core. And it just works for me now. Can you show your configs or logs? What does `minerd` say, what does `limit`, is there any other changes to your default configuration

SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of --threads option)

2014-01-14 Thread Andrey Chernov
On 14.01.2014 17:01, Alexander wrote: on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer from ports and by pkg install - result is the same - minerd mines only on one core regardless of --threads option. ... # top -P CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0%

Re: SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of --threads option)

2014-01-14 Thread Subbsd
On Tue, Jan 14, 2014 at 7:43 PM, Andrey Chernov a...@freebsd.org wrote: On 14.01.2014 17:01, Alexander wrote: on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer from ports and by pkg install - result is the same - minerd mines only on one core regardless of --threads option.

Joe Marcus Clarke steps down from duties on portmgr@

2014-01-14 Thread FreeBSD Ports Management Team Secretary
Joe Marcus Clarke, aka marcus@, has stepped down from his duties on the FreeBSD Ports Management Team. Joe was our longest serving member of the team. Among his many accomplishments was being the repocopy source of authority, instrumental in championing tinderbox development and maintaining

portmgr-lurkers@ promoted to voting members of portmgr@

2014-01-14 Thread FreeBSD Ports Management Team Secretary
The FreeBSD Ports Management team is pleased to announce that Mathieu Arnold (mat@) and Antoine Brodin (antoine@) have been promoted to full voting members of the team after a successful launch of the portmgr-lurkers pilot project. Each of them brings new skills and vast experience to the team.

Maximizing the use of binary packages and minimizing building packages

2014-01-14 Thread Matt Reimer
I'd like to switch from installing and upgrading our packages using portmaster/portupgrade to using pkg + binary packages from the ports cluster as much as possible. I understand that the ports cluster builds its packages using default options, but some of our packages we need built with custom

Re: SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of --threads option)

2014-01-14 Thread Alexander
14.01.2014, 20:14, Subbsd sub...@gmail.com: On Tue, Jan 14, 2014 at 7:43 PM, Andrey Chernov a...@freebsd.org wrote:  On 14.01.2014 17:01, Alexander wrote:  on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer  from ports and by pkg install - result is the same - minerd mines  

Re: Maximizing the use of binary packages and minimizing building packages

2014-01-14 Thread Chris Rees
On 01/14/14 17:46, Matt Reimer wrote: I'd like to switch from installing and upgrading our packages using portmaster/portupgrade to using pkg + binary packages from the ports cluster as much as possible. I understand that the ports cluster builds its packages using default options, but some of

Re: Maximizing the use of binary packages and minimizing building packages

2014-01-14 Thread Matthew Seaman
On 14/01/2014 18:52, Chris Rees wrote: Mixing ports and packages is discouraged and can get messy, because upgrades can get out of sync... Although with recent developments in pkgng, that advice is going to become outdated Real Soon Now. It is already possible to use mostly binary packages but

Re: Maximizing the use of binary packages and minimizing building packages

2014-01-14 Thread Matt Reimer
That's good news. What should I watch for in order to know when Really Soon Now becomes Now? Matt On Tue, Jan 14, 2014 at 12:14 PM, Matthew Seaman matt...@freebsd.orgwrote: On 14/01/2014 18:52, Chris Rees wrote: Mixing ports and packages is discouraged and can get messy, because upgrades

Re: Maximizing the use of binary packages and minimizing building packages

2014-01-14 Thread Matthew Seaman
On 14/01/2014 19:35, Matt Reimer wrote: That's good news. What should I watch for in order to know when Really Soon Now becomes Now? The release of pkg-1.3.x Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc

INDEX build failed for 8.x

2014-01-14 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-8 - please wait../home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 199: warning: duplicate script for target pre-install ignored