On Sun, 05 Dec 2010 00:50:08 +0100, Franci Nabalanci
wrote:
Yesterdays update to KDE 4.5.4 from 4.5.3 was without problems but when I
start KDE (startx) it show splash screen than turn to black with mouse
cursor
which works, I heard sound when looks KDE start and that is it. I switch
to
(Forgot to send to list initially)
On 12/6/2010 9:27 PM, Charlie Kester wrote:
I'm getting a strange error while trying to install the handbrake port:
===> Configuring for handbrake-0.9.3
sed:
/usr/ports/multimedia/handbrake/work/HandBrake-0.9.3//usr/ports/multimedia/handbrake/work/HandBrake-0.
On Tue 07 Dec 2010 at 14:33:24 PST Ion-Mihai Tetcu wrote:
On Tue, 7 Dec 2010 13:27:02 -0800
Charlie Kester wrote:
On Tue 07 Dec 2010 at 07:47:41 PST Peter Pentchev wrote:
>On Mon, Dec 06, 2010 at 06:27:54PM -0800, Charlie Kester wrote:
>> I'm getting a strange error while trying to install the
Hello,
I am not sure if this is the right place to ask questions about creating new
ports,
so please let me know if this not the case :-)
I was interested in getting Dropbox to work on FreeBSD. I'm running RELENG-8
and I've pulled together an initial skeleton for the 2 ports-to-be, that
current
On Tue, 7 Dec 2010 13:27:02 -0800
Charlie Kester wrote:
> On Tue 07 Dec 2010 at 07:47:41 PST Peter Pentchev wrote:
> >On Mon, Dec 06, 2010 at 06:27:54PM -0800, Charlie Kester wrote:
> >> I'm getting a strange error while trying to install the handbrake
> >> port:
> >>
> >>
> >> ===> Configuring
The Restless Daemon identified a mtree error while trying to build:
dbf2mysql-1.14_2 maintained by po...@freebsd.org
Makefile ident: $FreeBSD: ports/databases/dbf2mysql/Makefile,v 1.16 2010/12/04
21:21:14 beech Exp $
Excerpt from http://QAT.TecNik93.com/logs/8-STABLE-NPD/dbf2mysql-1.14_2.log :
> From: David Southwell
[SNIP]
> ERROR: Error installing /usr/ports/distfiles/rubygem/mail-2.2.10.gem:
> mail requires i18n (~> 0.4.1, runtime)
> *** Error code 1
>
> Stop in /usr/ports/mail/rubygem-mail.
[SNIP]
I've just submitted a PR (ports/152906 [1]) to upgrade the gem to 2.2.12
On Tue 07 Dec 2010 at 07:47:41 PST Peter Pentchev wrote:
On Mon, Dec 06, 2010 at 06:27:54PM -0800, Charlie Kester wrote:
I'm getting a strange error while trying to install the handbrake port:
===> Configuring for handbrake-0.9.3
sed:
/usr/ports/multimedia/handbrake/work/HandBrake-0.9.3//usr
Hello,
Here's an update for the irc/ngircd port from v0.15 to the latest stable
v0.17.
Thanks,
Rick
diff -ruN ngircd.orig/Makefile ngircd/Makefile
--- ngircd.orig/Makefile2010-02-26 10:07:16.0 -0800
+++ ngircd/Makefile 2010-12-07 12:16:03.707701000 -0800
@@ -6,12 +6,12 @@
#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/10 18:52, David Southwell wrote:
> ===> rubygem-mail-2.2.10 depends on package: rubygem-i18n>=0.4.1 - found
> ERROR: Error installing /usr/ports/distfiles/rubygem/mail-2.2.10.gem:
> mail requires i18n (~> 0.4.1, runtime)
> What am I
Pkg_info shows:
dns1# pkg_info |grep i18n
rubygem-i18n-0.5.0,1 New wave Internationalization support for Ruby
dns1#
However rubygem-mail-2.2.10 reports the following install failure :
dns1# make install
===> Installing for rubygem-mail-2.2.10
===> rubygem-mail-2.2.10 depends on package: ruby
On Tue, Dec 7, 2010 at 9:30 AM, wrote:
>
> portname: audio/gtkguitune
> broken because: does not fetch
> build errors: none.
> overview:
> http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gtkguitune
audio/gtkguitune is fetchable.
>
> portname:
Hi.
I found a cyclic dependency on audio/jack and audio/pulseaudio:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(snip)
===> pulseaudio-0.9.22 depends on shared library: jack.0 - not found
===>Verifying install clean for jack.0 in /usr/ports/audio/jack
==
On Mon, Dec 06, 2010 at 06:27:54PM -0800, Charlie Kester wrote:
> I'm getting a strange error while trying to install the handbrake port:
>
>
> ===> Configuring for handbrake-0.9.3
> sed:
> /usr/ports/multimedia/handbrake/work/HandBrake-0.9.3//usr/ports/multimedia/handbrake/work/HandBrake-0.9.3
In preparation for 7.4/8.2-FreeBSD, the ports tree will be in feature
freeze after Release Candidate 2 (RC2) is released, tentatively planned for
January 7, 2011.
If you have any commits with high impact planned, get them in the tree
before then and if they require an experimental build, have a re
Am 07.12.2010 12:44, schrieb Matthias Andree:
> Am 07.12.2010 08:30, schrieb lini...@freebsd.org:
>
>> portname: news/newsstar
>> broken because: does not build
>> build errors: none.
>> overview:
>> http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=
lini...@freebsd.org writes:
> portname: audio/gxmms2
> broken because: does not fetch
> build errors: none.
> overview:
> http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gxmms2
It's no longer broken, the distfile is fetchable for a few weeks.
___
Am 07.12.2010 08:30, schrieb lini...@freebsd.org:
> portname: news/newsstar
> broken because: does not build
> build errors: none.
> overview:
> http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=newsstar
>
I'm currently fixing this port. port test
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 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
23 matches
Mail list logo
