On Tue, May 22, 2012 at 08:41:52AM +0200, Armin Pirkovitsch wrote:
> On 2012-05-22 04:06, Jason Hellenthal wrote:
> > Can someone please update devel/git-subversion
> >
> > ===> License check disabled, port has not defined LICENSE
> > ===> Found saved configuration for git-subversion-1.7.9.6
>
On 2012-05-22 04:06, Jason Hellenthal wrote:
Can someone please update devel/git-subversion
===> License check disabled, port has not defined LICENSE
===> Found saved configuration for git-subversion-1.7.9.6
=> git-htmldocs-1.7.10.2.tar.gz is not in
/usr/ports/devel/git-subversion/../git/disti
On 21.05.2012 22:20 (UTC+1), coder.tuxfamily wrote:
Seems to be a problem with python.
Here the diff that i made yesterday.
Courtesly.
This patch applies fine, but I get exact the same errors as before (see
below).
There seems to be a problem within extensions/gdal_wrap.cpp.
Rainer
Le
On Tue, May 15, 2012 at 12:51 PM, Robert Simmons wrote:
> On Tue, May 15, 2012 at 5:46 AM, Dewayne Geraghty
> wrote:
>> Thanks for the updates Robert.
>>
>> I've pursued building heimdal on a custom FreeBSD9-Stable jail built without
>> crypto (openssl, heimdal,...); and forced the selection of b
On вт, 22 тра 2012 01:04:49 Jason Helfman wrote:
> I am working on the following pr, and would like to get others approval to
> the following patch:
> http://people.freebsd.org/~jgh/files/pre-patch.txt
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/165994
>
> This patch is fixing several us
Can someone please update devel/git-subversion
===> License check disabled, port has not defined LICENSE
===> Found saved configuration for git-subversion-1.7.9.6
=> git-htmldocs-1.7.10.2.tar.gz is not in
/usr/ports/devel/git-subversion/../git/distinfo.
=> Either /usr/ports/devel/git-subversion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/21/12 15:04, Jason Helfman wrote:
> I am working on the following pr, and would like to get others
> approval to the following patch:
> http://people.freebsd.org/~jgh/files/pre-patch.txt
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/16
Thanks for doing this work. A quick review looks to me to be TRT.
I would suggest some minor fixes but only for style: for me, it makes
it a bit clearer what's going on if the pre.mk include isn't among
the various WITH_* definitions, e.g. net/skystar2. Or maybe just
having a blank line before t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am working on the following pr, and would like to get others approval to
the following patch:
http://people.freebsd.org/~jgh/files/pre-patch.txt
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/165994
This patch is fixing several use cases of SRC_B
Seems to be a problem with python.
Here the diff that i made yesterday.
Courtesly.
Le 21.05.2012 22:13, Rainer Hurling a écrit :
On 21.05.2012 21:37 (UTC+1), coder.tuxfamily wrote:
Hello,
It's a problem know by GDAL.
In the 1.9.0 with PGSQL, gdal don't build because of include in
cpl_reco
On 21.05.2012 21:37 (UTC+1), coder.tuxfamily wrote:
Hello,
It's a problem know by GDAL.
In the 1.9.0 with PGSQL, gdal don't build because of include in
cpl_recode_iconv.cpp.
You can corrige this with include "${CPPFLAGS}" in configure files.
You can see the trac on OSGeo : http://trac.osgeo.o
On 21/05/2012 20:03, Etienne Robillard wrote:
On 05/21/2012 02:51 PM, George Kontostanos wrote:
On Mon, May 21, 2012 at 6:36 PM, Chris Rees wrote:
On May 21, 2012 4:17 PM, "George Kontostanos"
wrote:
Dear all,
I just wanted to understand why did php54 became the default php port.
Consider
Hello,
It's a problem know by GDAL.
In the 1.9.0 with PGSQL, gdal don't build because of include in
cpl_recode_iconv.cpp.
You can corrige this with include "${CPPFLAGS}" in configure files.
You can see the trac on OSGeo : http://trac.osgeo.org/gdal/ticket/4525
That will be fix on 1.9.1 versi
Thanks for the update of graphics/gdal to version 1.9.0.
It builds fine on 9.0 (amd64), but fails on 10.0-CURRENT (amd64):
[..snip..]
libtool: compile: c++ -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3
-Wall -DOGR_ENABLED -I/usr/local/include
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
On 05/21/2012 02:51 PM, George Kontostanos wrote:
On Mon, May 21, 2012 at 6:36 PM, Chris Rees wrote:
On May 21, 2012 4:17 PM, "George Kontostanos"
wrote:
Dear all,
I just wanted to understand why did php54 became the default php port.
Considering that the majority of my clients want to sti
On Mon, 2012-05-21 at 18:40 +0200, Miroslav Lachman wrote:
> I think that the best will be to not have any default "php5" port and
> just use php52, php53, php54, php5X, php60... as we have apache20,
> apache22, apache24, or mysql50-server, mysql51-server, mysql55-server.
+1
I really appreciate
On Mon, May 21, 2012 at 6:36 PM, Chris Rees wrote:
>
> On May 21, 2012 4:17 PM, "George Kontostanos"
> wrote:
>>
>> Dear all,
>>
>> I just wanted to understand why did php54 became the default php port.
>>
>> Considering that the majority of my clients want to stick with php53
>> with the susosin
On Mon, May 21, 2012 at 06:40:11PM +0200, Miroslav Lachman wrote:
> Jason Hellenthal wrote:
> >
> >
> > On Mon, May 21, 2012 at 11:38:50AM -0400, Michael Scheidell wrote:
> >>
> >>
> >> On 5/21/12 11:36 AM, Chris Rees wrote:
> >>> When would have been a better time?
> >>>
> >> after it was regres
Jason Hellenthal wrote:
On Mon, May 21, 2012 at 11:38:50AM -0400, Michael Scheidell wrote:
On 5/21/12 11:36 AM, Chris Rees wrote:
When would have been a better time?
after it was regression tested?
after the security posture (susosin patch) wasn't downgraded?
after a announcement in por
Oxford Business News
Wenn diese E-Mail nicht richtig angezeigt wird, klicken Sie bitte hier.
Jetzt Strom und Gas bis zu 20 Prozent günstiger sichern!
Gerade in wirtschaftlich herausfordernden Zeiten überprüfen clevere Unternehmer
ihre laufenden Kosten auf Einsparpo
After a reasonable amount of time has passed so more applications properly
support it
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@fre
On Mon, May 21, 2012 at 11:38:50AM -0400, Michael Scheidell wrote:
>
>
> On 5/21/12 11:36 AM, Chris Rees wrote:
> > When would have been a better time?
> >
> after it was regression tested?
> after the security posture (susosin patch) wasn't downgraded?
after a announcement in ports/UPDATING s
On 5/21/12 11:36 AM, Chris Rees wrote:
When would have been a better time?
after it was regression tested?
after the security posture (susosin patch) wasn't downgraded?
--
Michael Scheidell, CTO
>*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheid
On May 21, 2012 4:17 PM, "George Kontostanos"
wrote:
>
> Dear all,
>
> I just wanted to understand why did php54 became the default php port.
>
> Considering that the majority of my clients want to stick with php53
> with the susosin patch, I can't blame them, it is really very annoying
> that we
On 5/21/12 11:17 AM, George Kontostanos wrote:
Because currently there is no other way to do it unless you delete all
your php5 packages and recompile them again under php53.
I think there was a published 'hack' to let you rename everything
php5->php53 in /var/db/pkg and /var/db/ports.
This
Dear all,
I just wanted to understand why did php54 became the default php port.
Considering that the majority of my clients want to stick with php53
with the susosin patch, I can't blame them, it is really very annoying
that we have to schedule a down time window so that we migrate from
php to p
___
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"
2012-05-21 06:55, coder.tuxfamily skrev:
Hello,
For "Problem load font file" it's a problem with you conf.
Run wbar-config. Go into "Preferences" and choose your font.
Usually : /usr/local/lib/X11/fonts/dejavu/DejaVuSans
Le 09.05.2012 13:41, Leslie Jensen a écrit :
I've upgraded one syste
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsol
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: py27-django-threaded-multihost-1.4.1_1: no entry for
/usr/ports/devel/py-setuptools_hg
make_index: py27-django-caching-app-plugins-0.1.3_1: no entry for
/usr/ports/devel/py-setuptools_hg
make_index: py27-django-l
On 05/14/12 12:55, Andrea Venturoli wrote:
# cd
/usr/local/local/storage/alamartmp/usr/ports/editors/openoffice-3/work/aoo-3.4.0/main/bridges
# gmake
gmake: *** No targets specified and no makefile found. Stop.
# ls
inc prj source test unotypes unxfbsdi.pro version.mk
Meanwhile, I tried anoth
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, inclu
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 probl
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 th
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 probl
35 matches
Mail list logo
