xorg 6.9-7.3 upgrade failure - assistance needed

[John E Hein]

Jonathan Wilkie wrote at 18:25 +0000 on Dec  1, 2007:
 > I'm dead in the water at the moment everyone, still can't upgrade and 
 > I'm fresh out of ideas.
 > 
 > My upgrade of xorg 7.3 is failing on the fact it can't find a dependency
 > 
 > configure: error: Package requirements (xproto) were not met:
 > 
 > No package 'xproto' found
 > 
 > Consider adjusting the PKG_CONFIG_PATH environment variable if you
 > installed software in a non-standard prefix.
 > 
 > Alternatively, you may set the environment variables XAU_CFLAGS
 > and XAU_LIBS to avoid the need to call pkg-config.
 > See the pkg-config man page for more details.
 > 
 > ===>  Script "configure" failed unexpectedly.
 > Please report the problem to x11 at FreeBSD.org [maintainer] and attach the
 > "/usr/ports/x11/libXau/work/libXau-1.0.3/config.log" including the full output of
 > the failure of your make command. Also, it might be a good idea to provide
 > an overview of all packages installed on your system (e.g. an `ls
 > /var/db/pkg`).

So?  Do what this suggests.  Put this info on a web page somewhere and
send an URL pointer.


 > 
 > Stop in /usr/ports/x11/xorg-libraries.
 > ** Command failed [exit code 1]: /usr/bin/script -qa 
 > /tmp/portupgrade.57022.6 env UPGRADE_TOOL=portupgrade 
 > UPGRADE_PORT=xorg-libraries-6.9.0 UPGRADE_PORT_VER=6.9.0 make 
 > -DFORCE_PKG_REGISTER reinstall
 > 
 > 
 > HOWEVER
 > 
 > BSSS# pkg_info | grep -i xproto
 > xproto-7.0.10_1     X11 protocol headers
 > 
 > Shows it to be there....... and it's the latest version available I think.

The configure script is not using 'pkg_info | grep xproto'.  If you
want to learn what it's doing that makes it think that the "package is
not found", take a look at the configure script and the config.log
output.


 > How can we get the upgrade to recognise the dependency is there?

Depends on what the real problem is.  If I had to guess - there was
some file that used to be in an old port that overlapped with some
file that's in the xproto port.  xproto got installed, then the other
port that had the hypothetical conflicting file was uninstalled later
in the upgrade process thus removing the file in question.  Thus the
xproto package has been somewhat castrated ('pkg_info -g' might
confirm that).  If you have a sym link from /usr/X11R6 -> /usr/local
that probably is the culprit here if that is done before the
portupgrade (because the conflicting file used to be in /usr/X11R6 but
gets removed from /usr/local).

For some reason, maybe different than your reason, others have had
similar problems.  Why?  Who knows.  UPDATING not followed?  Some edge
case in the way you tried to upgrade?  The above theory?  See the
archives of this list within the last few months.  Report back here
with the details about where you or the process went wrong so that
others can figure it out and stop spamming the list with this problem ;)