[PARTIAL SOLUTION] Re: Trouble building abiword in the Ports Collection

2006-09-02 Thread Perry Hutchison
> > # pkgdb -F
> > --->  Checking the package registry database
> > 
> > [Updating the pkgdb  in /var/db/pkg ...
> > /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid
> > argument; rebuild needed] [Rebuilding the pkgdb  in
> > /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format --
> > Invalid argument: Cannot update the pkgdb!]: Cannot update the pkgdb!]
> 
> OK, navigate to the /var/db/pkg directory and either delete or rename
> the 'pkg.db' file. Then run:
> 
>   pkgdb -aFfuv
> 
> Assuming that works, resume with the rest of the directions I gave you
> previously.

That enabled the portupgrade to succeed, but abiword still fails.
I've sent the logs to freebsd-gnome.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Trouble building abiword in the Ports Collection

2006-09-01 Thread Gerard Seibert
Perry Hutchison wrote:

> # pkgdb -aFfuv
> --->  Updating the pkgdb
> [Rebuilding the pkgdb  in /var/db/pkg ...
> /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid
> argument: Cannot update the pkgdb!]
> 
> > If it fails, you will have to run: pkgdb -F to fix them manually.
> 
> That doesn't work either :(
> 
> # pkgdb -F
> --->  Checking the package registry database
> 
> [Updating the pkgdb  in /var/db/pkg ...
> /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid
> argument; rebuild needed] [Rebuilding the pkgdb  in
> /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format --
> Invalid argument: Cannot update the pkgdb!]: Cannot update the pkgdb!]

OK, navigate to the /var/db/pkg directory and either delete or rename
the 'pkg.db' file. Then run:

  pkgdb -aFfuv

Assuming that works, resume with the rest of the directions I gave you
previously.


-- 
Gerard Seibert
[EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Trouble building abiword in the Ports Collection

2006-09-01 Thread Perry Hutchison
> > * Reran 'portupgrade -a' ... This time it complains about the
> >   pkgdb.
> >   ? Now what?  Is it time to "rm -rf /usr/ports /var/db/pkg"
> > and start completely over (and if so, what should I do
> > differently this time)?
> 
> Try this. Run everything as root.
> 
>   pkgdb -aFfuv
> 
> That should fix most if not all problems.

No such luck.  It still complains about the file format:

# pkgdb -aFfuv
--->  Updating the pkgdb
[Rebuilding the pkgdb  in /var/db/pkg ... 
/var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument: 
Cannot update the pkgdb!]

> If it fails, you will have to run: pkgdb -F to fix them manually.

That doesn't work either :(

# pkgdb -F
--->  Checking the package registry database

[Updating the pkgdb  in /var/db/pkg ... /var/db/pkg/pkgdb.db: 
unexpected file type or format -- Invalid argument; rebuild needed] [Rebuilding 
the pkgdb  in /var/db/pkg ... /var/db/pkg/pkgdb.db: 
unexpected file type or format -- Invalid argument: Cannot update the pkgdb!]: 
Cannot update the pkgdb!]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Trouble building abiword in the Ports Collection

2006-09-01 Thread Gerard Seibert
Perry Hutchison wrote:

> What I have done:
> * Installed 6.1, including the Ports Collection, from CD.
> * Ran portsnap fetch.
> * Attempted portsnap update.
>   ? It sez this only works after an extract.  What is the point of
> installing the collection from CD if it has to be completely
> reinstalled from a download anyway?
> * Ran portsnap extract.
> * Built richtext, apparently successfully.
> * Attempted to build abiword.  It complained about a glibc version
>   problem, and said to run gnomelogalyzer.sh.  gnomelogalyzer.sh
>   found nothing specific, but said to run 'portupgrade -a' on general
>   principles.
>   ? Why should this be needed?  Shouldn't a freshly-downloaded
> portsnap already be up to date?
> * Attempted 'portupgrade -a'.  It ran for several hours, fetching
>   and building a huge amount of stuff (most of which I don't think
>   I want), and pausing several times for answers to imponderable
>   configuration questions, before eventually failing.
>   ? Shouldn't those configuration screens have a "help" function, for
> those of us who have no clue what some of the options amount to?
> * Reran 'portupgrade -a' to get a smaller logfile, showing only the
>   errors (since presumably the successful builds won't be redone).
>   This time it complains about the pkgdb.
>   ? Now what?  Is it time to "rm -rf /usr/ports /var/db/pkg" and
> start completely over (and if so, what should I do differently
> this time)?

Try this. Run everything as root.

  pkgdb -aFfuv

That should fix most if not all problems. If it fails, you will have to
run: pkgdb -F to fix them manually.

If you have 'portupgrade' you should also have portsclean. Try running
this to clean up any crud left from you old builds.

  portsclean -CDDLP

Now run: portsnap fetch && portsnap update

Now you can run the portupgrade command. You can probably run it like
this:
  portupgrade -aFRr

That should cover all of your bases. Personally I prefer 'portmanager'
but each to his own.

Good luck!


-- 
Gerard Seibert
[EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Trouble building abiword in the Ports Collection

2006-09-01 Thread Perry Hutchison
What I have done:
* Installed 6.1, including the Ports Collection, from CD.
* Ran portsnap fetch.
* Attempted portsnap update.
  ? It sez this only works after an extract.  What is the point of
installing the collection from CD if it has to be completely
reinstalled from a download anyway?
* Ran portsnap extract.
* Built richtext, apparently successfully.
* Attempted to build abiword.  It complained about a glibc version
  problem, and said to run gnomelogalyzer.sh.  gnomelogalyzer.sh
  found nothing specific, but said to run 'portupgrade -a' on general
  principles.
  ? Why should this be needed?  Shouldn't a freshly-downloaded
portsnap already be up to date?
* Attempted 'portupgrade -a'.  It ran for several hours, fetching
  and building a huge amount of stuff (most of which I don't think
  I want), and pausing several times for answers to imponderable
  configuration questions, before eventually failing.
  ? Shouldn't those configuration screens have a "help" function, for
those of us who have no clue what some of the options amount to?
* Reran 'portupgrade -a' to get a smaller logfile, showing only the
  errors (since presumably the successful builds won't be redone).
  This time it complains about the pkgdb.
  ? Now what?  Is it time to "rm -rf /usr/ports /var/db/pkg" and
start completely over (and if so, what should I do differently
this time)?

=== logfile from second 'portupgrade -a' ===

# date ; portupgrade -a ; date
Fri Sep  1 10:34:20 PDT 2006
[Updating the pkgdb  in /var/db/pkg ... /var/db/pkg/pkgdb.db: 
unexpected file type or format -- Invalid argument; rebuild needed] [Rebuilding 
the pkgdb  in /var/db/pkg ... [Updating the pkgdb 
 in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file 
type or format -- Invalid argument; rebuild needed] [Rebuilding the pkgdb 
 in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file 
type or format -- Invalid argument: Cannot update the pkgdb!]: Cannot update 
the pkgdb!]
Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ
Fri Sep  1 10:34:24 PDT 2006
# ls -l /var/db/pkg/pkgdb.db
-rw-r--r--  1 root  wheel  5963776 Sep  1 01:42 /var/db/pkg/pkgdb.db
# file /var/db/pkg/pkgdb.db
/var/db/pkg/pkgdb.db: Berkeley DB 1.85/1.86 (Btree, version 3, native 
byte-order)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"