On 04/15/2015 02:32 PM, A.J. Fonz van Werven wrote:
Carsten Jensen wrote:
Installing updates... install:
///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory
[snip]
mkdir -p /usr/src/crypto/openssl/util/
fixes the problem when trying to run freebsd-update
Carsten Jensen wrote:
Installing updates... install:
///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory
[snip]
mkdir -p /usr/src/crypto/openssl/util/
fixes the problem when trying to run freebsd-update install again.
do I need to create a PR for this
it seems there's a minor inconvenience in freebsd-update.
I was doing updates today and several times this occured.
Installing updates... install:
///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory
I've run into similar issues before and I think the
On Wed, Apr 15, 2015 at 4:22 AM, Matthew Seaman matt...@freebsd.org wrote:
On 2015/04/15 12:03, Mike Clarke wrote:
Many thanks, that provided the essential clue. beefy6.nyi.freebsd.org
provides
logs for 101amd64-default and 84amd64-default.
A bit of digging around enabled me to put
On Wed, Apr 15, 2015 at 08:55:23AM -0700, Kevin Oberman wrote:
My thanks to whoever made this possible. New hardware of this sort is a bit
expensive and the time of those who can integrate it all is invaluable.
I'm not the one working on this so I'm somewhat butting in, however:
You guys
I've updated the script to make use of your information and did some
other tweaks.
https://gist.github.com/reedacartwright/8622973baf89b263a6d7
On Wed, Apr 15, 2015 at 4:03 AM, Mike Clarke
jmc-freeb...@milibyte.co.uk wrote:
On Tuesday 14 Apr 2015 11:30:19 Don Lewis wrote:
On 14 Apr, Mike
Hi there!
Do you plan to upgrade the port to pnp-0.6.25 in the near future?
I ask because the current pnp used in the port is buggy when used with php5.6.
Thanks very much for a short reply!
Best regards,
Thomas
___
freebsd-ports@freebsd.org mailing
On 15 Apr 2015, at 09:41, Walter Schwarzenfeld w.schwarzenf...@utanet.at
wrote:
does not compile with clang (but compiles fine with gcc).
Error Message:
cc -O2 -pipe -fstack-protector -fno-strict-aliasing -fstack-protector -o
.libs/goom2 -Wl,-rpath -Wl,/usr/local/lib frame_rate_tester.o
Rapid evolution of pkgng! :D Thanks for your great work!
On 4/14/15, Baptiste Daroussin b...@freebsd.org wrote:
Hi all,
Final pkg 1.5.0 has been released.
What happened since pkg 1.4.0:
- Initial provides/requires support
- Lots of new regression tests have been added
- Initial support
Hi!
I'm trying to do a general upgrade:
# pkg upgrade
Updating opsec repository catalogue...
opsec repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (491 candidates): 100%
Processing candidates (491 candidates): 100%
pkg: Cannot solve problem using
Hallo !!
does not compile with clang (but compiles fine with gcc).
Error Message:
cc -O2 -pipe -fstack-protector -fno-strict-aliasing -fstack-protector -o
.libs/goom2 -Wl,-rpath -Wl,/usr/local/lib frame_rate_tester.o gmtimer.o
gtk-callbacks.o gtk-interface.o gtk-support.o pixeldoubler.o
On Wed, Apr 15, 2015 at 10:57:28AM +0100, Big Lebowski wrote:
On Tue, Apr 14, 2015 at 9:05 PM, Baptiste Daroussin b...@freebsd.org wrote:
Hi all,
Final pkg 1.5.0 has been released.
Best regards,
Bapt
Congratulations to entire pkg team and thanks for your hard work!
I've one
On Tue, Apr 14, 2015 at 9:05 PM, Baptiste Daroussin b...@freebsd.org wrote:
Hi all,
Final pkg 1.5.0 has been released.
Best regards,
Bapt
Congratulations to entire pkg team and thanks for your hard work!
I've one question - how does the OSX support work? What are plans for
it? What
On 2015/04/15 10:57, Big Lebowski wrote:
I've one question - how does the OSX support work? What are plans for
it? What packages are working? And so on...
OSX support is at a fairly preliminary stage. At the moment, pkg(8) can
be compiled and should work equivalently on OSX as it does on
On Tuesday 14 Apr 2015 11:30:19 Don Lewis wrote:
On 14 Apr, Mike Clarke wrote:
[snip]
The problem is that 101amd64-default hasn't been built on
beefy2.isc.freebsd.org since version 381523 on 2015-03-18_03h47m09s.
The mystery is where do we get the logs from now?
Look for
On 2015/04/15 12:03, Mike Clarke wrote:
Many thanks, that provided the essential clue. beefy6.nyi.freebsd.org
provides
logs for 101amd64-default and 84amd64-default.
A bit of digging around enabled me to put together the following list:
beefy1.isc.freebsd.org
93i386-default
16 matches
Mail list logo