glib20

2006-05-01 Thread Arno Schleich
Dear all, after upgrading several gnome ports I am experiencing a strange problem with glib-2.10.2. It is installed (listed in the package database), and dependencies are correctly recognized (e. g. when compiling a port in this case /net/avahi the dependecy is marked as fulfilled) yet when th

Re: glib20

2006-05-02 Thread Arno Schleich
This installed glib-2.10.2 perfectly but failed to configure the build of the application as above. Thanks for the thought, but I'd still be thankful for a more definitive suggestion as to how to solve this problem. Arno From: Kris Kennaway <[EMAIL PROTECTED]> To: Arno Schleich

Re: glib20

2006-05-02 Thread Arno Schleich
arded by the mailing list software. *** Error code 1 Stop in /mnt/TrekStor120G/ports/databases/evolution-data-server. *** Error code 1 Stop in /mnt/TrekStor120G/ports/mail/evolution. ------ Thanks ! From: Kris Kennaway <[EMAIL PROTE

Re: glib20

2006-05-04 Thread Arno Schleich
proposed on www.freebsd.org/gnome for a different but structurally related problem. Thanks for all Your efforts wrt to this issue. Arno From: Adi Pircalabu <[EMAIL PROTECTED]> To: "Arno Schleich" <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED], freebsd-questions@freebsd.org Su

portupgrade

2006-05-06 Thread Arno Schleich
Dear all, I have observed the following behavior in portupgrade: The operation portugrade -a results in a repetitive rebuild of the package database whenever the database is accessed. [Updating the pkgdb in /var/db/pkg ... Inappropriate file type or format - /var/db/pkg/pkgdb; rebuild nee

Re: portupgrade

2006-05-06 Thread Arno Schleich
No, I upgraded to 6.0 a couple of days after it was released. That must have been eight or nine months ago ... m: Colin Percival <[EMAIL PROTECTED]> To: Arno Schleich <[EMAIL PROTECTED]> CC: freebsd-questions@freebsd.org Subject: Re: portupgrade Date: Sat, 06 May 2006 14:37:45

Re: portupgrade

2006-05-06 Thread Arno Schleich
Thanks, that improved the behavior. What I don't understand though is why upgrading individual ports e. g. "portupgrade xyz" never resulted in that problem ... From: Beech Rintoul <[EMAIL PROTECTED]> To: freebsd-questions@freebsd.org CC: Arno Schleich <[EMAIL