On Thu, 2007-02-01 at 11:42 +0200, Dominik Zalewski wrote:
> Hi All,
>
> I've just updated my portstree and I'm trying to run portupgrade , which
> gives
> me following error:
I had the same this morning, try upgrading to the latest portupgrade
which got it working for me
_
ing key: categories] [Updating the portsdb
in /usr/ports ... - 16413 port entries
found
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16
Quoth Dominik Zalewski on Thu, Feb 01, 2007 at 11:42:13 +0200
> I've just updated my portstree and I'm trying to run portupgrade ,
> which gives me following error:
I've had the same problem last night. Sadly, the machine is at home and
I at work so I cannot do much more than say "me too". Howev
On Thursday 01 February 2007 11:46:21 am Niclas Zeising wrote:
>>This has been reported several times already, and I think it's solved
>>in a more recent portupgrade.
>>Have a look at this thread:
>>http://lists.freebsd.org/pipermail/freebsd-ports/2007-January/038395.html
>>And this commit to portu
Hi All,
I've just updated my portstree and I'm trying to run portupgrade , which gives
me following error:
[EMAIL PROTECTED] /usr/ports]# portupgrade -ai
---> Session started at: Thu, 01 Feb 2007 11:22:00 +0200
[missing key: categories] [Updating the portsdb
in /usr/ports ...
ything further than "make fetchindex".
>> Building INDEX-x takes forever (and may be overheating your machine
>> causing freezes/reboots), but building INDEX-x.db is quite fast.
>>
>> If you want to make sure everything is updated with a single command,
>&g
NDEX-x takes forever (and may be overheating your machine
> causing freezes/reboots), but building INDEX-x.db is quite fast.
>
> If you want to make sure everything is updated with a single command,
> replace the '-U' with '-F' for "portsdb -Fu" (hehe -- I love
On 05/12/06 03:20, gareth wrote:
> On Wed 2006-05-10 (11:29), Jonathan Noack wrote:
>> You are probably experiencing some of the VFS limitations in 5.3 (you'll
>> be pleasantly surprised by 6.1!). "portsdb -Uu" is very CPU and IO
>> intensive; it takes a
On Wed 2006-05-10 (11:29), Jonathan Noack wrote:
> You are probably experiencing some of the VFS limitations in 5.3 (you'll
> be pleasantly surprised by 6.1!). "portsdb -Uu" is very CPU and IO
> intensive; it takes a long time on a fast machine. "make fetchindex&qu
On 05/10/06 06:22, gareth wrote:
> On Wed 2006-05-10 (09:31), gareth wrote:
>> hey guys, i've been having this trouble on and off for
>> quite awhile, sometimes while running 'portsdb -Uu'
>> (after a cvsup) the box just freezes, along with the
>> powe
On Wed 2006-05-10 (09:31), gareth wrote:
> hey guys, i've been having this trouble on and off for
> quite awhile, sometimes while running 'portsdb -Uu'
> (after a cvsup) the box just freezes, along with the
> power? i'm running 5.3-RELEASE.
ok, i did:
cd /usr
hey guys, i've been having this trouble on and off for
quite awhile, sometimes while running 'portsdb -Uu'
(after a cvsup) the box just freezes, along with the
power? i'm running 5.3-RELEASE.
___
freebsd-stable@freebsd.o
;
> I ran cvsup with no problems. But then I ran portsdb and I get these
> warnings:
>
> [EMAIL PROTECTED] portsdb -Uu
> Updating the ports index ... Generating INDEX.tmp - please wait..
>
> Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.2
> Warning: Duplicate
You can try downloading a new index:
cd /usr/ports
make fetchindex
Then run portsdb again.
Cheers
Benjamin
signature.asc
Description: OpenPGP digital signature
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of bob self
> Sent: Thursday, August 18, 2005 08:05
> To: freebsd-stable@freebsd.org
> Subject: portsdb (Warning: Duplicate INDEX)
>
>
> My system:
>
My system:
---
FreeBSD ..org 5.4-STABLE FreeBSD 5.4-STABLE #0:
Mon Aug 15 19:06:46 EDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
The problem:
I ran cvsup with no problems. But then I ran portsdb and I get these
warnings:
[EMAIL PROTECTED
Kirill Ponomarew wrote:
On Tue, May 24, 2005 at 09:30:54PM +0100, Jayton Garnett wrote:
Hello list,
Is this a warning to be concerned about? or to not worry about?
---
jayton# portsdb -Uu
Updating the ports index ... Generating INDEX.tmp - please
wait.."/usr/ports/Mk/bsd.po
On Tue, May 24, 2005 at 09:30:54PM +0100, Jayton Garnett wrote:
> Hello list,
>
> Is this a warning to be concerned about? or to not worry about?
> ---
> jayton# portsdb -Uu
> Updating the ports index ... Generating INDEX.tmp - please
> wait.."/usr/ports/
Hello list,
Is this a warning to be concerned about? or to not worry about?
---
jayton# portsdb -Uu
Updating the ports index ... Generating INDEX.tmp - please
wait.."/usr/ports/Mk/bsd.port.mk", line 4847: warning: duplicate script
for target "add-plis
On Thu, Dec 23, 2004 at 10:24:05PM -0800, Michael C. Shultz wrote:
> On Thursday 23 December 2004 09:59 pm, Kris Kennaway wrote:
> > On Thu, Dec 23, 2004 at 09:42:37PM -0800, Brian Behlendorf wrote:
> > > >run make fetchindex not make fetch index from /usr/ports
> > >
> > > Out of curiosity, why is
On Fri, 24 Dec 2004 17:27, Michael C. Shultz wrote:
> > Because the way we used to do it required tremendous churn in the
> > CVS repository. And it was _still_ out of date.
>
> We in user land don't see that end of things :) Why does INDEX have to
> go into the CVS repository anyways? Guess that
On Fri, 24 Dec 2004 17:13, Mark Linimon wrote:
> There's really quite a bit of email in the mailing list archives
> about why this was done. The short summary is that in the short
> run there is some pain but in the long run this is a win for the
> project, and the users.
IMHO it would have been
On Thursday 23 December 2004 10:43 pm, you wrote:
> On Thu, 23 Dec 2004, Michael C. Shultz wrote:
> > Way back when, I used to get the INDEX when running cvsup unless
> > I put it in the refuse file. Of coarse it was old and useless so
> > one was better off building their own INDEX. So why cant w
On Thu, 23 Dec 2004, Michael C. Shultz wrote:
> Way back when, I used to get the INDEX when running cvsup unless
> I put it in the refuse file. Of coarse it was old and useless so one was
> better off building their own INDEX. So why cant we just receive the
> INDEX like we used to, but unlike
# cd /usr/ports && make index-> failure?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Thursday 23 December 2004 09:59 pm, Kris Kennaway wrote:
> On Thu, Dec 23, 2004 at 09:42:37PM -0800, Brian Behlendorf wrote:
> > >run make fetchindex not make fetch index from /usr/ports
> >
> > Out of curiosity, why isn't the index included in the update
> > normally?
>
> It changes dozens of t
On Thursday 23 December 2004 09:42 pm, Brian Behlendorf wrote:
> On Thu, 23 Dec 2004, Michael C. Shultz wrote:
> > On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote:
> >> These days it is best to run make fetch index from /usr/ports
> >> after you've run cvsup rather than build INDEX-5
On Thu, Dec 23, 2004 at 09:42:37PM -0800, Brian Behlendorf wrote:
> >run make fetchindex not make fetch index from /usr/ports
>
> Out of curiosity, why isn't the index included in the update normally?
It changes dozens of times per day, and the deltas would be enormous.
Kris
pgpxowY2MltXM.pgp
On Thu, 23 Dec 2004, Michael C. Shultz wrote:
On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote:
These days it is best to run make fetch index from /usr/ports
after you've run cvsup rather than build INDEX-5 for yourself.
-Mike
correction:
run make fetchindex not make fetch index from
On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote:
>
> These days it is best to run make fetch index from /usr/ports
> after you've run cvsup rather than build INDEX-5 for yourself.
>
> -Mike
correction:
run make fetchindex not make fetch index from /usr/ports
__
- Original Message -
From: "Michael C. Shultz" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 23, 2004 8:50 PM
Subject: Re: portsdb and portupgrade causes errors
> On Thursday 23 December 2004 08:37 pm, whitevamp wrote:
> > i dont know weathere this place
On Thursday 23 December 2004 08:37 pm, whitevamp wrote:
> i dont know weathere this place to be posting this to or not .. if
> not point me in the right direction to go..
>
> i have just updated my system to 5.3 frrom 4.9 and now every time i
> goto run portsdb , or portupgrad
i dont know weathere this place to be posting this to or not .. if not point
me in the right direction to go..
i have just updated my system to 5.3 frrom 4.9 and now every time i goto run
portsdb , or portupgrade iget the same error message.and i also have a nother
5.3 box that was a fresh
> On Tue, Nov 23, 2004 at 12:04:04PM -0500, Lowell Gilbert wrote:
>> "alex bustamante" <[EMAIL PROTECTED]> writes:
>>
>> > when i run portsdb -uU FreeBSD 5.3 i get this error:
>> >
>> > opium# portsdb -uU
>> > Updating the
On Tue, Nov 23, 2004 at 12:04:04PM -0500, Lowell Gilbert wrote:
> "alex bustamante" <[EMAIL PROTECTED]> writes:
>
> > when i run portsdb -uU FreeBSD 5.3 i get this error:
> >
> > opium# portsdb -uU
> > Updating the ports index ... Generating INDEX.
"alex bustamante" <[EMAIL PROTECTED]> writes:
> when i run portsdb -uU FreeBSD 5.3 i get this error:
>
> opium# portsdb -uU
> Updating the ports index ... Generating INDEX.tmp - please
> wait..openoffice-2.0.20041122: "/usr/ports/devel/bison-devel" non
Hello,
when i run portsdb -uU FreeBSD 5.3 i get this error:
opium# portsdb -uU
Updating the ports index ... Generating INDEX.tmp - please
wait..openoffice-2.0.20041122: "/usr/ports/devel/bison-devel" non-existent
-- dependency list incomplete
===> editors/openoffice-2.0-devel fai
On Tue, Sep 14, 2004 at 01:33:05AM +0100, Jacobo Arvelo UNIX4ALL wrote:
> Is there any chance to merge this patch to RELENG_5 ?
http://lists.freebsd.org/pipermail/freebsd-current/2004-September/037277.html
-Radek
___
[EMAIL PROTECTED] mailing list
http:
On Tue, 2004-09-07 at 01:08, Michael Nottebrock wrote:
> bdb_hash, then run portsdb -fu - works for me, so that also points to be some
> bug in bdb1.
Hrm. I thought bdb1 btrees were well known to be buggy, to be honest.
(I had a feeling it was going to turn out to be this issue as s
VER to bdb_btree or
bdb_hash, then run portsdb -fu - works for me, so that also points to be some
bug in bdb1.
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD
At 10:49 PM -0400 9/6/04, Sahil Tandon wrote:
kstewart wrote:
There is a bug in ruby that shows up as a bus error. Follow the
topic on [EMAIL PROTECTED] There are several ways to alter the INDEX[-5]
so that it occurs less frequently.
Occurs less frequently? That's not what I'm looking for. Is the
don't
> > use categories, which it doesn't produce.
>
> I'm using portsindexsb as a work around, but it still doesn't address or
> solve the problem which makes portsdb -Uu fail. I've tried removing and
> re-extracting the ports tree and doing whatever e
I started using portindexdb because it doesn't error off. I also don't use
categories, which it doesn't produce.
I'm using portsindexsb as a work around, but it still doesn't address or
solve the problem which makes portsdb -Uu fail. I've tried removing and
re-extr
I had to download a fresh ports.tar.gz (and extract it).
Then portsdb -Uu works.
Cheers
Günther
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sunday 05 September 2004 11:12 pm, Maxim Maximov wrote:
> Daniel O'Connor wrote:
> > On Mon, 6 Sep 2004 15:14, Maxim Maximov wrote:
> >>That doesn't help. I tried to entirely delete all /usr/ports, ruby*,
> >>portupgrade*, removed /var/db/pkg/pkgdb.db, install those all over again
> >>and still
Daniel O'Connor wrote:
On Mon, 6 Sep 2004 15:14, Maxim Maximov wrote:
That doesn't help. I tried to entirely delete all /usr/ports, ruby*,
portupgrade*, removed /var/db/pkg/pkgdb.db, install those all over again
and still get a coredump.
SIGSEGV appears in libc.so.4 in __bt_split() and it seems lik
On Mon, Sep 06, 2004 at 01:45:18AM -0400 or thereabouts, Tim Kellers wrote:
> I'm trying it again, though this time it's on Yet Another 5.3gbeta2 machine.
> I'll try it again on a production 4.10-Stable machine in a few minutes.
>
> Tim
>
I was receiving su
On Mon, 6 Sep 2004 15:14, Maxim Maximov wrote:
> That doesn't help. I tried to entirely delete all /usr/ports, ruby*,
> portupgrade*, removed /var/db/pkg/pkgdb.db, install those all over again
> and still get a coredump.
>
> SIGSEGV appears in libc.so.4 in __bt_split() and it seems like a real
> bu
and all of ruby, reinstalled portupgrade (and
> > all of ruby) and had to do a portsdb -Uu even after I did a make
> > fetchindex in /usr/ports to make the pkgdb in /var/db/pkg happy. Since
> > I've done all of those things, portupgrade is working again. I had to to
> >
49 matches
Mail list logo
