Updated my ports tree via portsnap, running ``portmanager -s'' show a large number of ports needing upgrading/rebuilding (most where "built with old dependency").

Ran ``portmanager -u'', which ran for several hours then finished like this:

===>   Registering installation for gmime-2.2.3
===>   Returning to build of pan-0.116_1
===>   pan-0.116_1 depends on shared library: intl - found
===>   pan-0.116_1 depends on shared library: atk-1.0.0 - found
===>   pan-0.116_1 depends on shared library: glib-2.0.0 - found
===>   pan-0.116_1 depends on shared library: gtk-x11-2.0.0 - found
===>   pan-0.116_1 depends on shared library: pango-1.0.0 - found
===>   pan-0.116_1 depends on shared library: X11.6 - found
===>  Configuring for pan-0.116_1
checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk

.......

checking for PCRE... yes
checking for pkg-config... /usr/local/bin/pkg-config
checking for GLIB - version >= 2.4.0... yes (version 2.12.4)
checking for GMIME... yes
checking for pkg-config... (cached) /usr/local/bin/pkg-config
checking for GTK+ - version >= 2.4.0... no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GTK+ is incorrectly installed.
===>  Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh";, which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
[EMAIL PROTECTED], and attach (a)
"/usr/ports/news/pan/work/pan-0.116/config.log", (b) the output of the failed
make command, and (c) the gnomelogalyzer output. Also, it might be a good
idea to provide an overview of all packages installed on your system (i.e.
an `ls /var/db/pkg`). Put your attachment up on any website, copy-and-paste
into http://freebsd-gnome.pastebin.com, or use send-pr(1) with the attachment. Try to avoid sending any attachments to the mailing list ([EMAIL PROTECTED]),
because attachments sent to FreeBSD mailing lists are usually discarded by
the mailing list software.
*** Error code 1

Stop in /usr/ports/news/pan.
MGPMrUpdate 0.4.1_6 error: make returned an error, adding /news/pan to ignore.db reverting bsd.port.mk patch -=>cd /usr/ports/Mk; patch -R < /usr/local/share/portmanager/patch-bsd.port.mk-0.3.6;
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- /usr/ports/Mk/bsd.port.mk  Tue Nov  8 01:02:51 2005
|+++ bsd.port.mk        Wed Nov 16 02:16:57 2005
--------------------------
Patching file bsd.port.mk using Plan A...
Hunk #1 succeeded at 2336 (offset 287 lines).
done
------------------------------------------------------------------------
 Port Status Report
------------------------------------------------------------------------
00001 have:gmime-2.2.3 /mail/gmime2 CURRENT 00002 have:pkg-config-0.21 /devel/pkg-config CURRENT 00003 have:libiconv-1.9.2_2 /converters/libiconv CURRENT 00004 have:glib-2.12.4 /devel/glib20 CURRENT 00005 have:perl-5.8.8 /lang/perl5.8 CURRENT 00006 have:gettext-0.14.5_2 /devel/gettext CURRENT
========================================================================
portmanager 0.4.1_6 INFO: all ports are up to date
#

It's not the failure of news/pan to build that's the problem it's the fact that portmanager only lists 6 ports when there are 426 installed and that it reports "all ports are up to date" - running ``portmanager -s'' again reveals that there are still a large number that are NOT up to date - in fact, very few appear to have been updated!!

Can anyone shed any light on this? Is portmanager broken?

Thanks.

Regards,

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

Reply via email to