On 2/1/07, Philip Kizer [EMAIL PROTECTED] wrote:
On 2007, Jan 31, at 18:45, Csaba Molnar wrote:
I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I
think, and
that seems to have worked.
While I was updating ports before this error showed up, the options
screen for
portupgrade
Murilo Opsfelder Araújo wrote:
Yesterday I had the same problem and garga@ helped me to solve that.
He told me to change my ports database to dbm_hash.
It's not a fix really. A fix was committed.
Well, it's worth to add a few sanity checks for DB. Really working with
DB should be complete
Hi,
Done that too (pkgdb -fu) , but didn't work for me... :(
I use FreeBSD6-stable
Vassilis
On Thu, Feb 01, 2007 at 01:45:55AM +0100, Csaba Molnar wrote:
2007. February 1. 00.34 d?tummal Joachim Bethke ezt ?rta:
Hallo,
I get the same error on two machines too. Have someone a practical
On 2/1/07, Sergey Matveychuk [EMAIL PROTECTED] wrote:
Murilo Opsfelder Araújo wrote:
Yesterday I had the same problem and garga@ helped me to solve that.
He told me to change my ports database to dbm_hash.
It's not a fix really. A fix was committed.
Well, it's worth to add a few sanity
Have you updated portupgrade to the last one (2.2.2_3,2)? Do it please.
Laganakos Vassilis wrote:
Hi,
Done that too (pkgdb -fu) , but didn't work for me... :(
I use FreeBSD6-stable
Vassilis
On Thu, Feb 01, 2007 at 01:45:55AM +0100, Csaba Molnar wrote:
2007. February 1. 00.34 d?tummal
On Thu, Feb 01, 2007 at 04:37:02PM +0300, Sergey Matveychuk wrote:
Murilo Opsfelder Araújo wrote:
Yesterday I had the same problem and garga@ helped me to solve that.
He told me to change my ports database to dbm_hash.
It's not a fix really. A fix was committed.
Well, it's worth to add
Gary Kline wrote:
On Thu, Feb 01, 2007 at 04:37:02PM +0300, Sergey Matveychuk wrote:
Murilo Opsfelder Araújo wrote:
Yesterday I had the same problem and garga@ helped me to solve that.
He told me to change my ports database to dbm_hash.
It's not a fix really. A fix was
On Thu, Feb 01, 2007 at 11:55:21AM -0800, Brian wrote:
Gary Kline wrote:
On Thu, Feb 01, 2007 at 04:37:02PM +0300, Sergey Matveychuk wrote:
Murilo Opsfelder Araújo wrote:
Yesterday I had the same problem and garga@ helped me to solve that.
He told me to change my ports database to
That worked :D
I updated portupgrade and then the portupgrade was smooth!
Thanx!
Vassilis
On Thu, Feb 01, 2007 at 09:46:59PM +0300, Sergey Matveychuk wrote:
Have you updated portupgrade to the last one (2.2.2_3,2)? Do it please.
Laganakos Vassilis wrote:
Hi,
Done that too (pkgdb
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session started at: Wed, 31 Jan 2007 15:44:44 +
[missing key:
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session started
Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele:
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the
Joel Dahl a écrit :
Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele:
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running
Joel Dahl a écrit :
Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele:
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running
* Bartosz Fabianowski ([EMAIL PROTECTED]) wrote:
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session started at:
Hi
Portupgrade problems here as well.
Rico
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
On 1/31/07, Bartosz Fabianowski [EMAIL PROTECTED] wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session
David Stanford wrote:
missing key: categories: Cannot read the portsdb!
Something broken in INDEX :(
--
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Eric Schuele wrote:
I'm seeing this as well. Though I had thought it was because my
`/usr/ports/make fetchindex` had failed.
Anyone else?
Me too, on two 6-Stable machines.
___
freebsd-ports@freebsd.org mailing list
Same here... Out of the blue...
Removing old files and directories... done.
Extracting new files:
/usr/ports/audio/prokyon3/
/usr/ports/devel/cogito/
/usr/ports/net/ipw-firmware-kmod/
/usr/ports/net/iwi-firmware-kmod/
/usr/ports/textproc/xmlto/
Something broken in INDEX :(
For the record: I am using p5-FreeBSD-Portindex-1.8 to build INDEX-6 and
have received a reply off list from somebody who has the same problems
with an INDEX-6 retrieved via make fetchindex. So, it's not just a
single broken INDEX-6 file on the server that needs
Hallo,
I get the same error on two machines too. Have someone a practical idea
http://dict.leo.org/ende?lp=endep=/gQPU.search=idea how to fix it.
Joachim
___
freebsd-ports@freebsd.org mailing list
2007. February 1. 00.34 dátummal Joachim Bethke ezt írta:
Hallo,
I get the same error on two machines too. Have someone a practical idea
http://dict.leo.org/ende?lp=endep=/gQPU.search=idea how to fix it.
Joachim
I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, and
Csaba Molnar wrote:
I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, and
that seems to have worked.
While I was updating ports before this error showed up, the options screen
for
portupgrade showed up - and option WITH_BDB4 was unchecked. I changed that
(so
On 2007, Jan 31, at 18:45, Csaba Molnar wrote:
I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I
think, and
that seems to have worked.
While I was updating ports before this error showed up, the options
screen for
portupgrade showed up - and option WITH_BDB4 was unchecked. I
25 matches
Mail list logo
