On Tue, Jan 5, 2010 at 11:45 PM, Doug Barton do...@freebsd.org wrote:
Martin Cracauer wrote:
Doug Barton wrote on Tue, Jan 05, 2010 at 01:58:57PM -0800:
Are you saying there are binary packages for 8-stable?
I thought I can only have them for -RELEASE?
There have always been binary packages
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports
On Tue, Jan 05, 2010 at 08:24:26PM -, Simon Griffiths wrote:
Hello,
-Original Message-
From: owner-freebsd-spar...@freebsd.org [mailto:owner-freebsd-
spar...@freebsd.org] On Behalf Of Anton Shterenlikht
Sent: 18 December 2009 13:41
To: Andrew Belashov
Cc:
On Tue, 05 Jan 2010 14:45:05 -0800
Doug Barton do...@freebsd.org wrote:
Martin Cracauer wrote:
RELENG_8 will lift be out of binary ports, at least as far as
portupgrade is concerned.
Sorry, I don't understand that sentence.
I would guess this should read will be left out of... Follows
On Mon, 2010-01-04 at 18:31 +0100, Beat Gaetzi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
First of all thanks a lot for all the valuable feedback. We have updated
the ports
Works without a problem here on FreeBSD 8.0-STABLE #0 r201431 i386
with Windows XP and Debian Lenny
Gary Jennejohn wrote on Wed, Jan 06, 2010 at 04:31:48PM +0100:
On Tue, 05 Jan 2010 14:45:05 -0800
Doug Barton do...@freebsd.org wrote:
Martin Cracauer wrote:
RELENG_8 will lift be out of binary ports, at least as far as
portupgrade is concerned.
Sorry, I don't understand that
On Wed, 6 Jan 2010, Martin Cracauer wrote:
So the verdict is to hunt down OpenOffice packages manually and
install them so that portupgrade ignores them, then go from there.
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/
seems to have what `portupgrade -P` should expect,
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100:
On Wed, 6 Jan 2010, Martin Cracauer wrote:
So the verdict is to hunt down OpenOffice packages manually and
install them so that portupgrade ignores them, then go from there.
On Wed, 6 Jan 2010, Martin Cracauer wrote:
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100:
On Wed, 6 Jan 2010, Martin Cracauer wrote:
So the verdict is to hunt down OpenOffice packages manually and
install them so that portupgrade ignores them, then go from there.
Erwin Lansing wrote:
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest
Hi,
I am new to building ports, however I have started to get the hang of
things.
I am not building any ports that I intend on submitting to FreeBSD, yet,
however maybe that isn't too far off :)
I've used a guide I found to create a local ports repository that is working
out wonderfully with
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 09:43:21PM +0100:
On Wed, 6 Jan 2010, Martin Cracauer wrote:
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100:
On Wed, 6 Jan 2010, Martin Cracauer wrote:
So the verdict is to hunt down OpenOffice packages manually and
On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
Dear Sirs,
We use a software package for scientific imagery processing from USGS,
ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
3.1.21 and since this version, the software intensively uses
libprotobuf.so.
On Wed, Jan 06, 2010 at 08:46:38PM +0100, Peter Ulrich Kruppa wrote:
On Wed, 6 Jan 2010, Martin Cracauer wrote:
So the verdict is to hunt down OpenOffice packages manually and
install them so that portupgrade ignores them, then go from there.
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 schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
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,
20 matches
Mail list logo
