To clarify:
Only people serving packages for distribution need to rebuild so that
their users have fixed packages. If you are running
Poudriere/Tinderbox/Custom and are serving packages to other people or
machines, you should rebuild them on the build system AFTER 1.3.7 is
out. Running pkg check
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as broken in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as broken in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as forbidden in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port,
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as forbidden in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port,
Hi!
So I've been getting a lot of issues being directed at me due to the
recent devel/doxygen update to 1.8.7. While I'm not sure why these
issues only cropped up after that update and not before, I would like to
try addressing a few things.
Those discussions always pop up if something
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,
Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386 releases once all ports properly
respect LDFLAGS.
To enable, just add WITH_SSP=yes to your make.conf and
On 08/21/14 05:17, Kurt Jaeger wrote:
Hi!
So I've been getting a lot of issues being directed at me due to the
recent devel/doxygen update to 1.8.7. While I'm not sure why these
issues only cropped up after that update and not before, I would like to
try addressing a few things.
Those
On Wed, 20 Aug 2014 18:34:22 +0200, Bryan Drewery bdrew...@freebsd.org
wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386
On 08/20/14 12:34, Bryan Drewery wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386 releases once all ports properly
respect
Hi,
I found your contact over the web and wanted to send you a quick note. With
the help of Search Engine Optimization and Web Development, your business
can achieve better ranking on prominent search engines like Google, Bing
others to generate more leads/sales.
This may look like one of
On Mi, 2014-08-20 at 11:34 -0500, Bryan Drewery wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386 releases once all ports
On Thu, 21 Aug 2014 16:05:46 +0200, Mathias Picker stated:
On Mi, 2014-08-20 at 11:34 -0500, Bryan Drewery wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Reference:
From: Frederic Culot cu...@freebsd.org
Date: Thu, 21 Aug 2014 07:06:46 +0200
Hi,
Frederic Culot wrote:
[1] http://youtu.be/LiFq5D-zmBs
There's no sound ! I thought my sound had failed, but as a test
there Is sound on adjacent unrelated:
Am 21.08.2014 um 13:27 schrieb Naram Qashat:
Well, I'd already put in a bug for this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192732
It does mean that, yes, by default, it'll pull in a lot of dependencies.
I'm not sure if having a uses for doxygen really makes much sense,
On 8/21/2014 5:34 AM, Mark Martinec wrote:
Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386 releases once all ports properly
respect LDFLAGS.
To
On 8/21/2014 6:56 AM, Ronald Klop wrote:
On Wed, 20 Aug 2014 18:34:22 +0200, Bryan Drewery bdrew...@freebsd.org
wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
On 8/21/2014 8:32 AM, Nikolai Lifanov wrote:
On 08/20/14 12:34, Bryan Drewery wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier
On 8/21/2014 9:31 AM, Jerry wrote:
On Thu, 21 Aug 2014 16:05:46 +0200, Mathias Picker stated:
On Mi, 2014-08-20 at 11:34 -0500, Bryan Drewery wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older
To clarify:
Only people serving packages for distribution need to rebuild so that
their users have fixed packages. If you are running
Poudriere/Tinderbox/Custom and are serving packages to other people or
machines, you should rebuild them on the build system AFTER 1.3.7 is
out. Running pkg check
On 8/21/2014 10:53 AM, Bryan Drewery wrote:
On 8/21/2014 5:34 AM, Mark Martinec wrote:
Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386 releases once all
Greetings,
The time has now come to remove these db4* ports, Berkeley DB versions
4.0 to 4.7, inclusively. Most of their dependent ports can cope with
upgrades to db48, db5, or db6, most of the others could be patched to work.
I will wait a few hours after this announcement has appeared on the
I've been trying to figure out why this port was marked broken then
removed. The claim is that there were no public distfiles. However...
http://www.goodhumans.com/Misc/lib_mysqludf/lib_mysqludf_preg-LATEST.tar.gz
appears to exist and is downloadable.
Can someone clarify what is going on?
Jos Chrispijn:
After I installed ImageMagic port, I got stuck at the installation of
Webp:
Just installed ImageMagic again and the installation went perfect -
thanks for your support!
BR, Jos Chrispijn
___
freebsd-ports@freebsd.org mailing
On 8/21/2014 3:12 PM, Kurt Jaeger wrote:
Hi!
If I run
portupgrade -arR -m BATCH=yes
I currently get this error on 10.0-amd64:
[Updating the portsdb format:dbm_hash in /usr/ports ... - 24478 port
entries found
Hi!
portupgrade -arR -m BATCH=yes
I currently get this error on 10.0-amd64:
[Updating the portsdb format:dbm_hash in /usr/ports ... - 24478 port
entries found
Am 21.08.2014 um 22:36 schrieb Kurt Jaeger:
Hi!
portupgrade -arR -m BATCH=yes
I currently get this error on 10.0-amd64:
[Updating the portsdb format:dbm_hash in /usr/ports ... - 24478 port
entries found
On 8/21/2014 3:36 PM, Kurt Jaeger wrote:
Hi!
portupgrade -arR -m BATCH=yes
I currently get this error on 10.0-amd64:
[Updating the portsdb format:dbm_hash in /usr/ports ... - 24478 port
entries found
Hi
There is a problem in caja with default manual sort order option,
I have mentioned it here:
http://forums.mate-desktop.org/viewtopic.php?f=2t=3093
Applying:
# cd /usr/ports/x11-fm/caja/files
# fetch http://tmp.ttmath.org/patch-src_file-manager_fm-icon-view.c
# cd ..
# make all reinstall clean
Hi!
What version of ruby do you have?
Do you have ruby-bdb installed? (May be ruby19-bdb or ruby20-bdb)
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
31 matches
Mail list logo
