Hi,
Ryan Carsten Schmidt wrote:
rev-upgrade detect broken packages which did not receive a bump and not listed
as top be upgraded
We need to know the names of each of those ports so that we can add the libxml2
dependency to them and revbump them. If you have time, you could submit bug
reports showing the relevant part of the rev-upgrade debug output or even file
pull requests to fix them.
no problem.. can do that for all systems affected, but how can we know
if they are due to a libxml2 dependency or "other" update stuff? It is a
chain after all
The only one I am certain about is xar, which is only detected by
rev-upgrade and not outdated.
e.g. here on 10.13, I have:
---> Scanning binaries for linking errors
Could not open /opt/local/lib/libxml2.2.dylib: Error opening or reading
file (referenced from /opt/local/lib/libgtksourceview-4.0.dylib)
Could not open /opt/local/lib/libgpgme.11.dylib: Error opening or
reading file (referenced from /opt/local/lib/libpoppler.136.0.0.dylib)
Could not open /opt/local/lib/libgpgmepp.6.dylib: Error opening or
reading file (referenced from /opt/local/lib/libpoppler.136.0.0.dylib)
---> Found 13 broken files, matching files to ports
---> Found 9 broken ports, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
shared-mime-info @2.4
librsvg @2.58.5
xar @1.8.0.501
emacs-app @30.2+nativecomp+rsvg+treesitter
emacs @30.2+nativecomp+treesitter
gtksourceview4 @4.8.4+quartz
poppler @24.04.0+boost
llvm-19 @19.1.7
llvm-21 @21.1.8
Continue? [Y/n]:
which means libgtksourceview is broken due to xml2, but no mention of xar.
Sorry for the "dumbness" perhaps it is obvious.
Riccardo
