Hi,
2008/5/31 Brian A. Seklecki <[EMAIL PROTECTED]>:
> Normally I would say that this PR may be approaching the point where we
> override the maintainer -- the problem is that I haven't received any
> feedback from anyone other than my development team.
I committed for devel/php5-phing port, but
Quoting Alexey Shuvaev <[EMAIL PROTECTED]>:
On Sun, Aug 17, 2008 at 10:21:30AM -0500, eculp wrote:
I've been trying to build multimedia/mplayer for a couple of days now
and end with the following error:
In file included from ../libavutil/bswap.h:30,
from ../mpbswap.h:4,
> Tuc at T-B-O-H.NET writes:
>
> > Even though you hijacked the thread, can you mention WHAT you
> > upgraded?
>
> Which was not the intention. pav is the listed aintainer for
> boinc-client, which was upgraded within the last seven days. I do
> not believe boinc-setiathome-enhanc
Hi!
I took an interest in installing [EMAIL PROTECTED] earlier today, but I
couldn't get it started up properly. Some friends of mine enlightened
me that the current FBSD-version (5.04) is way outdated and may not
work. The most recent version is 6.02, and I would feel much better if
it w
Tuc at T-B-O-H.NET writes:
> Even though you hijacked the thread, can you mention WHAT you
> upgraded?
Which was not the intention. pav is the listed aintainer for
boinc-client, which was upgraded within the last seven days. I do
not believe boinc-setiathome-enhanced (my on
>
>
> [added CC: to [EMAIL PROTECTED] as maintaner of setiathome]
>
> Peter Jeremy writes:
>
> > I notice that [EMAIL PROTECTED] have stopped generating S5R3
> > workunits and a new client is needed to handle the new S5R4
> > workunits. Do you have any plans to upgrade the port?
>
>
[added CC: to [EMAIL PROTECTED] as maintaner of setiathome]
Peter Jeremy writes:
> I notice that [EMAIL PROTECTED] have stopped generating S5R3
> workunits and a new client is needed to handle the new S5R4
> workunits. Do you have any plans to upgrade the port?
I am also no
On Sun, Aug 17, 2008 at 8:32 AM, <[EMAIL PROTECTED]> wrote:
> 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. [...]
> portname: japanese/lyx
> broken beca
Quoting Kris Kennaway <[EMAIL PROTECTED]>:
eculp wrote:
I have been having issues as I have posted on [EMAIL PROTECTED]
compiling kdenetwork4. It always breaks at
/usr/ports/net/kdenetwork4/work/kdenetwork-4.1.0/kopete/protocols/jabber/libiris/iris/xmpp-im/xmpp_task.cpp:21:27: error: qplatf
Peter Jeremy píše v po 18. 08. 2008 v 05:11 +1000:
> I notice that [EMAIL PROTECTED] have stopped generating S5R3 workunits and
> a new client is needed to handle the new S5R4 workunits. Do you have
> any plans to upgrade the port?
I will update the port but unfortunately FreeBSD app for S5R4 is
Hi Pav,
I notice that [EMAIL PROTECTED] have stopped generating S5R3 workunits and
a new client is needed to handle the new S5R4 workunits. Do you have
any plans to upgrade the port?
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either
On Sun, Aug 17, 2008 at 10:21:30AM -0500, eculp wrote:
> I've been trying to build multimedia/mplayer for a couple of days now
> and end with the following error:
>
> In file included from ../libavutil/bswap.h:30,
> from ../mpbswap.h:4,
> from ao_pcm.c:8:
> ../li
eculp wrote:
I have been having issues as I have posted on [EMAIL PROTECTED]
compiling kdenetwork4. It always breaks at
/usr/ports/net/kdenetwork4/work/kdenetwork-4.1.0/kopete/protocols/jabber/libiris/iris/xmpp-im/xmpp_task.cpp:21:27:
error: qplatformdefs.h: No such file or directory
*** Err
I have been having issues as I have posted on [EMAIL PROTECTED]
compiling kdenetwork4. It always breaks at
/usr/ports/net/kdenetwork4/work/kdenetwork-4.1.0/kopete/protocols/jabber/libiris/iris/xmpp-im/xmpp_task.cpp:21:27: error: qplatformdefs.h: No such file or
directory
*** Error code 1
D
I've been trying to build multimedia/mplayer for a couple of days now
and end with the following error:
In file included from ../libavutil/bswap.h:30,
from ../mpbswap.h:4,
from ao_pcm.c:8:
../libavutil/common.h:98: error: redefinition of 'av_log2'
/usr/local/in
On Sun, Aug 17, 2008 at 08:42:52AM -0600, hideo wrote:
> > Apparently, whatever worked for you hasn't done me any good:
> >
> > ===> Patching for ruby-1.8.6.287,1
> > ===> Applying FreeBSD patches for ruby-1.8.6.287,1
> > Ignoring previously applied (or reversed) patch.
> > 3 out of 3 hu
On Sun, Aug 17, 2008 at 04:41:37PM +0200, Marcin Cieslak wrote:
>
> One of my ports breaks badly on the tinderbox:
> The error message is:
>
> ===> commonist-0.3.28 depends on executable: unzip - found
> (cd /work/a/ports/www/commonist/work/commonist-0.3.28 &&
> /usr/local/diablo-jdk1.5.0/bin/j
Jack Raats (Sat 08/16/08 09:28):
> Chad,
>
> This error is the same I got this morning. After the new commit this problem
> was solved.
> Please update the ports tree and try again.
>
> Jack
>
>
> - Original Message -
> From: "Chad Perrin" <[EMAIL PROTECTED]>
> To:
> Sent: Saturday,
Hello,
One of my ports breaks badly on the tinderbox:
portname: www/commonist
broken because: does not extract
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20080809191637/commonist-0.3.28.log
(Sun Aug 10 00:58:14 UTC 2008)
overview:
http://portsmon.Fre
On Sun, Aug 17, 2008 at 09:45:38AM -0400, Eduardo Cerejo wrote:
>
> ===> Patching for ruby-1.8.6.287,1
> ===> Applying FreeBSD patches for ruby-1.8.6.287,1
> Ignoring previously applied (or reversed) patch.
> 3 out of 3 hunks ignored--saving rejects to lib/cgi.rb.rej
> => Patch patch-lib_cgi.rb
I'm running FBSD 7 stable and I'm using portupgrade and ruby18 is the only port
that refuses to upgrade. I'm getting this error when I run portupgrade.
---> Upgrading 'ruby-1.8.6.111_4,1' to 'ruby-1.8.6.287,1' (lang/ruby18)
---> Building '/usr/ports/lang/ruby18'
===> Cleaning for ruby-1.8.6.2
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 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 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 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
26 matches
Mail list logo
