On Fri, Jan 23, 2009 at 10:35 PM, Dominic Fandrey kamik...@bsdforen.de wrote:
This is the list of ports that I require to rebuild after the upgrade.
This list only contains ports directly linked to an now outdated
library. It has been generated with the command:
# pkg_libchk -qo
pkg_libchk is
Hello,
Did you run portupgrade -rf libxcb?
On a related note: I ran above command _before_ doing a full
portupgrade -a. A whole bunch of ports failed to upgrade because
of old versions of X-related header files. I tracked down xproto,
glproto and inputproto via the build logs. To be on the safe
Christoph Moench-Tegeder writes:
Is that me mis-understanding UPGRADING and doing it the wrong way
round?
While acknowledging this is a work-in-progress ... am I the
only one who finds the UPDATING pretty minimal for something that
affects so many things?
Christoph Moench-Tegeder wrote:
Did you run portupgrade -rf libxcb?
On a related note: I ran above command _before_ doing a full
portupgrade -a. A whole bunch of ports failed to upgrade because
A mixture of -rf and a -a upgrade is always problematic, unless you were
up-to-date before the
## Jan Henrik Sylvester (m...@janh.de):
Did you run portupgrade -rf libxcb?
On a related note: I ran above command _before_ doing a full
portupgrade -a. A whole bunch of ports failed to upgrade because
A mixture of -rf and a -a upgrade is always problematic, unless you were
up-to-date
Florent Thoumie wrote:
On Fri, Jan 23, 2009 at 10:35 PM, Dominic Fandrey kamik...@bsdforen.de
wrote:
This is the list of ports that I require to rebuild after the upgrade.
This list only contains ports directly linked to an now outdated
library. It has been generated with the command:
#
Robert Huff wrote:
Christoph Moench-Tegeder writes:
Is that me mis-understanding UPGRADING and doing it the wrong way
round?
While acknowledging this is a work-in-progress ... am I the
only one who finds the UPDATING pretty minimal for something that
affects so many things?
No --
