OK, I know this is just a meta package, and not really essential to
my survival, but nonetheless, I'm hitting a brick wall with this one:
-
-- The following OPTIONAL packages could NOT be located on your system.
--
Nevermind. Turning off the KDEWEBDEV option in x11/kde4 allowed the
upgrade to succeed (forgot I had turned this on yesterday out of
curiosity).
I suppose, then, that the subject line of this thread should have been
Build failure in www/kdewebdev4 instead.
Sorry for the noise.
--
Conrad J.
On 2 November 2011 15:05, Conrad J. Sabatier conr...@cox.net wrote:
OK, I know this is just a meta package, and not really essential to
my survival, but nonetheless, I'm hitting a brick wall with this one:
-
-- The
Adam McDougall wrote:
Some of that sounds true to my experience, for a while I've noticed while
installing a new port with portupgrade that it will install the default
dependencies before prompting with the options screen to find out which
ones I want. For example if I do 'portupgrade -N
Quoting Mark Linimon lini...@lonesome.com:
On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote:
The maintainer, ruby@, is aware of this; a check of the PR
database shows multiple open PRs, none critical but many serious
going back six months and more.
As an aside, the Severity and
On Thu, Dec 17, 2009 at 10:21:02AM +0100, Jimmy Renner wrote:
Quoting Mark Linimon lini...@lonesome.com:
On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote:
The maintainer, ruby@, is aware of this; a check of the PR
database shows multiple open PRs, none critical but many
Adam McDougall wrote:
[...]
Some of that sounds true to my experience, for a while I've noticed while
installing a new port with portupgrade that it will install the default
dependencies before prompting with the options screen to find out which
ones I want. For example if I do 'portupgrade -N
Miroslav Lachman wrote:
Adam McDougall wrote:
[...]
Some of that sounds true to my experience, for a while I've noticed while
installing a new port with portupgrade that it will install the default
dependencies before prompting with the options screen to find out which
ones I want. For example
Kevin writes:
I've been having this problem for a couple of months now, but I
just recently decided to try to fix it. I'm running FreeBSD 6.4,
and if I try to use portupgrade to upgrade something, I get an
error (seems to be the same for other ports):
portupgrade (and -devel)
On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote:
The maintainer, ruby@, is aware of this; a check of the PR
database shows multiple open PRs, none critical but many serious
going back six months and more.
As an aside, the Severity and Priority fields have been so often abused
as to
Ports at FreeBSD.org:
I should have sent this also to you - it seems like it bounced from
ntar...@cs.uoi.gr
Thanks in advance for any help you can provide...
John Stubblebine
js...@jstub.com
Original Message
Subject:portupgrade failure xcb-util failure
Date
Has anyone experienced the compression of /usr/bin/gzip to /usr/bin/gzip.gz
during a portupgrade? Portupgrade obviously fails. As I use the -k option I
haven't been able to pin down what port actually causes the damage.
--
Cheers,
Cy Schubert [EMAIL PROTECTED]
FreeBSD UNIX: [EMAIL PROTECTED]
Failure:
cd /usr/ports/x11-wm/kompmgr/work/kdebase-3.5.8/kwin/kompmgr
install -c -p -s -o root -g wheel -m 555 kompmgr /usr/local/bin/kompmgr
=== Registering installation for kdebase-kompmgr-3.5.8_2
=== Cleaning for kdebase-kompmgr-3.5.8_2
--- Cleaning out obsolete shared libraries
-- Forwarded Message --
Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64
openexr issues)
Date: Tuesday 16 October 2007
From: David Southwell [EMAIL PROTECTED]
To: Mikhail Teterin [EMAIL PROTECTED]
On Monday 15 October 2007 07:48:14 you wrote
On Tuesday 16 October 2007 01:12:55 David Southwell wrote:
-- Forwarded Message --
Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure
-amd64 openexr issues)
Date: Tuesday 16 October 2007
From: David Southwell [EMAIL PROTECTED]
To: Mikhail Teterin
-- Forwarded Message --
Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64
openexr issues)
Date: Tuesday 16 October 2007
From: David Southwell [EMAIL PROTECTED]
To: Mikhail Teterin [EMAIL PROTECTED]
On Tuesday 16 October 2007 05:24:15 you wrote
On Tuesday 16 October 2007 05:55:53 David Southwell wrote:
Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure
-amd64 openexr issues)
Date: Tuesday 16 October 2007
From: David Southwell [EMAIL PROTECTED]
To: Mikhail Teterin [EMAIL PROTECTED]
On Tuesday 16 October 2007 05
On Tuesday 16 October 2007 05:55:53 David Southwell wrote:
Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure
-amd64 openexr issues)
Date: Tuesday 16 October 2007
From: David Southwell [EMAIL PROTECTED]
To: Mikhail Teterin [EMAIL PROTECTED]
On Tuesday 16 October 2007 05
-- Forwarded Message --
Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64
openexr issues)
Date: Tuesday 16 October 2007
From: David Southwell [EMAIL PROTECTED]
To: Mikhail Teterin [EMAIL PROTECTED]
On Tuesday 16 October 2007 05:44:25 you wrote
ImageMagick amd64 -- freebsd 6.1
===
1 of 696 tests failed
Please report to http://www.imagemagick.org
===
*** Error code 1
Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.3.5.
*** Error code 1
Stop in
On Monday 15 October 2007 02:27:38 David Southwell wrote:
ImageMagick amd64 -- freebsd 6.1
===
1 of 696 tests failed
Please report to http://www.imagemagick.org
===
*** Error code 1
Stop in
On понеділок 15 жовтень 2007, [EMAIL PROTECTED] wrote:
= PASS: Magick++/tests/exceptions.sh
= appendImages: unable to close module `MIFF': Invalid shared object handle
= 0x80052d000.
Module support remains broken, unfortunately, and is disabled by default.
Please, run `make config' to disable
On Monday 15 October 2007 06:07:51 Mikhail Teterin wrote:
On понеділок 15 жовтень 2007, [EMAIL PROTECTED] wrote:
= PASS: Magick++/tests/exceptions.sh
= appendImages: unable to close module `MIFF': Invalid shared object handle
= 0x80052d000.
Module support remains broken, unfortunately, and
понеділок 15 жовтень 2007 10:39 до, David Southwell Ви написали:
1. Any idea how long Module support will remain broken?
This is a difficult question to answer, because it depends on the exact
configurations -- some modules are just fine, but some others mess things up,
when ImageMagick
24 matches
Mail list logo
