On Sun, Dec 20, 2009 at 08:29:06PM -0700, Warren Block wrote:
Don't know. I'd guess not cleaning the failed build out of the work
dir with 'make clean', but portupgrade should do that automatically.
It's built now. I just did:
% cd /usr/ports/print/ghostscript8
% make deinstall
% make
Hi
I've now got a different problem when trying to portupgrade ghostscript8
and the build fails with an error: (new compiler error).
I had a problem with ghostscript the last time it need upgrading. I
think then I removed it from the system and just built the new port.
This time, I have a number
On Sun, 20 Dec 2009, Jamie Griffin wrote:
I've now got a different problem when trying to portupgrade ghostscript8
and the build fails with an error: (new compiler error).
I had a problem with ghostscript the last time it need upgrading. I
think then I removed it from the system and just built
On Sun, Dec 20, 2009 at 03:03:09PM -0700, Warren Block wrote:
The ghostscript8 problem has been fixed, so update your ports tree again
and portupgrade will work.
Hi Warren, thanks for the information. I just updated my ports tree and
tried to build it again using make first, then portupgrade
On Sun, 20 Dec 2009, Jamie Griffin wrote:
On Sun, Dec 20, 2009 at 03:03:09PM -0700, Warren Block wrote:
The ghostscript8 problem has been fixed, so update your ports tree again
and portupgrade will work.
Hi Warren, thanks for the information. I just updated my ports tree and
tried to build
On Wed, Dec 16, 2009 at 7:24 PM, Mark Linimon lini...@lonesome.com wrote:
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.
Hello all,
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 -R squid
[Gathering depends for
On Wed, 16 Dec 2009, Kevin wrote:
[...]
The only other symptoms I can identify right now are related to the
following entries in my crontab:
0 2 * * 6 /usr/local/sbin/portsclean -DD
0 2 * * 5 /usr/local/sbin/portsclean -C
The e-mailed results simply say env: ruby: No such file or
Hi,
On Wed, Dec 16, 2009 at 11:19 PM, Warren Block wbl...@wonkity.com wrote:
On Wed, 16 Dec 2009, Kevin wrote:
[...]
The only other symptoms I can identify right now are related to the
following entries in my crontab:
0 2 * * 6 /usr/local/sbin/portsclean -DD
0 2 * * 5
Glen Barber wrote:
Hi,
On Wed, Dec 16, 2009 at 11:19 PM, Warren Block wbl...@wonkity.com wrote:
On Wed, 16 Dec 2009, Kevin wrote:
[...]
The only other symptoms I can identify right now are related to the
following entries in my crontab:
0 2 * * 6 /usr/local/sbin/portsclean -DD
0
On Wed, 16 Dec 2009, Warren Block wrote:
On Wed, 16 Dec 2009, Kevin wrote:
[...]
The only other symptoms I can identify right now are related to the
following entries in my crontab:
0 2 * * 6 /usr/local/sbin/portsclean -DD
0 2 * * 5 /usr/local/sbin/portsclean -C
The e-mailed
On Sat, Oct 4, 2008 at 5:02 AM, Patrick Lamaizière
[EMAIL PROTECTED] wrote:
Portupgrade is often confused with his database on upgrade.
Delete /var/db/pkg/pkgdb.db and retry.
May be you have to delete /usr/ports/INDEX-6.db too.
Hmm. This does not inspire confidence in the tool.
Mike
--
On Mon, Oct 13, 2008 at 02:04:02PM -0400, Michael P. Soulier wrote:
On Sat, Oct 4, 2008 at 5:02 AM, Patrick Lamaizière
[EMAIL PROTECTED] wrote:
Portupgrade is often confused with his database on upgrade.
Delete /var/db/pkg/pkgdb.db and retry.
May be you have to delete
On Mon, Oct 13, 2008 at 2:05 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
So don't use it? :-) There are alternatives like portmaster.
I suppose I prefer a single, reliable, supported tool for the system.
portupgrade seems to be pushed the most in all of the documentation
that I can find, so I
On Mon, Oct 13, 2008 at 02:08:54PM -0400, Michael P. Soulier wrote:
On Mon, Oct 13, 2008 at 2:05 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
So don't use it? :-) There are alternatives like portmaster.
I suppose I prefer a single, reliable, supported tool for the system.
portupgrade
Michael P. Soulier [EMAIL PROTECTED] wrote:
On Mon, Oct 13, 2008 at 2:05 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
So don't use it? :-) There are alternatives like portmaster.
I suppose I prefer a single, reliable, supported tool for the system.
portupgrade seems to be pushed the most
Le Fri, 3 Oct 2008 13:26:33 -0400,
Michael P. Soulier [EMAIL PROTECTED] a écrit :
So, I recently upgraded from 5.5 to 6.3, and as such, ran a
portupgrade -fa to rebuild my ports against 6.3.
I just noticed this.
=== Cleaning for ruby-1.8.6.287,1
--- Cleaning out obsolete shared
So, I recently upgraded from 5.5 to 6.3, and as such, ran a portupgrade -fa
to rebuild my ports against 6.3.
I just noticed this.
=== Cleaning for ruby-1.8.6.287,1
--- Cleaning out obsolete shared libraries
[Updating the pkgdb format:dbm_hash in /var/db/pkg ... Inappropriate file
type or
Hi,
I'm trying to portupgrade my system and the only ones left are kde and OpenEXR.
Apparently OpenEXR needs to be done as dependency for kde. But my portupgrade
-R OpenEXR fail.
Following is the error message, how can I solve this?
/usr/bin/ld: warning: libIlmThread.so.4, needed by
On Saturday 17 November 2007 13:55:02 Alain G. Fabry wrote:
Hi,
I'm trying to portupgrade my system and the only ones left are kde and
OpenEXR. Apparently OpenEXR needs to be done as dependency for kde. But my
portupgrade -R OpenEXR fail.
Following is the error message, how can I solve
Ok,
I found a solution. I had the same problem as described below.
I am using portsnap so :
# portsnap fetch
# portsnap update
# cd /usr/ports/sysutils/portupgrade
# make deinstall; make install clean
This will install version portupgrade-2.2.2_2,2 which corrects the bug.
Sincerly yours.
I am having the same problem.
I have tried the make fetchindex approach but it doesn't solve it for me.
you mentioned something about /usr/ports/UPDATING, but was unable to find
a relevant entry.
can you please tell me the entry date that helped you with this problem?
Thank you,
Tomoki Taniguchi
hello list!
5. Re: freebsd-questions Digest, Vol 110, Issue 20 (David Armour)
Message: 5 WAS: * Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade84798.26 make
From: Vizion [EMAIL PROTECTED]
What were the lines before:
gmake[1]: Leaving directory
On Tuesday 06 September 2005 00:09, Yuan Jue wrote:
hello list!
5. Re: freebsd-questions Digest, Vol 110, Issue 20 (David Armour)
Message: 5 WAS: * Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade84798.26 make
From: Vizion [EMAIL PROTECTED]
What
Message: 32
Date: Tue, 6 Sep 2005 00:34:33 +0800
From: Yuan Jue [EMAIL PROTECTED]
Have you upgraded the nspr port? I have almost the same problem
when I didn't upgrade it to the newest version.
without your message, i wouldn't have noticed nspr needs updating
on my pkg_version
Hi,
I tried to upgrade firefox with portupgrade, but it fails with the
following error:
[EMAIL PROTECTED]# portupgrade firefox
Updating the ports index ... Generating INDEX.tmp - please wait..^Cfailed to
generate INDEX!
index generation error
/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:482:in
On Sat, 08 Jan 2005 18:29:51 +0100 (CET), Marco Beishuizen
[EMAIL PROTECTED] wrote:
Hi,
I tried to upgrade firefox with portupgrade, but it fails with the
following error:
[EMAIL PROTECTED]# portupgrade firefox
Updating the ports index ... Generating INDEX.tmp - please wait..^Cfailed to
On Sat, Jan 08, 2005 at 06:29:51PM +0100, Marco Beishuizen wrote:
Hi,
I tried to upgrade firefox with portupgrade, but it fails with the
following error:
[EMAIL PROTECTED]# portupgrade firefox
Updating the ports index ... Generating INDEX.tmp - please wait..^Cfailed
to generate
Marco Beishuizen wrote:
Hi,
I tried to upgrade firefox with portupgrade, but it fails with the
following error:
[EMAIL PROTECTED]# portupgrade firefox
Updating the ports index ... Generating INDEX.tmp - please
wait..^Cfailed to generate INDEX!
index generation error
On stardate Sat, 8 Jan 2005, the wise Joshua Lokken entered:
You may be able to make this problem go away by doing:
# cd /usr/ports
# make fetchindex
Yes, this did the trick. I should have read /usr/ports/UPDATING though,
because the answer was in it...
Thanks for the answers.
Marco
--
Minnie
Hello,
I'm not sure what's next: hedgehogs falling from the skies, perhaps? Mostly, I know
I'm flailing around in the newbie waters, an otherwise straightforward 5.2.1 install
(single user, desktop) gone horribly, horribly wrong. The story so far...
I got through most of the sysinstall
[EMAIL PROTECTED] wrote:
Hello,
I'm not sure what's next: hedgehogs falling from the skies, perhaps? Mostly, I know
I'm flailing around in the newbie waters, an otherwise straightforward 5.2.1 install
(single user, desktop) gone horribly, horribly wrong. The story so far...
And what have
32 matches
Mail list logo
