Re: always have broken files at the end of a self-update
On Apr 9, 2024, at 19:13, Alexander Newman wrote: > > I have exactly the same problem, but with rygel as another affected build. > I've uninstalled rygel but left webkit2-gtk in place. I now just ignore the > rev-upgrade suggestion (n). It seems to be associated with gstreamer and > cmake (cmake recently updated on my Ventura machine). Last time I looked (two > days ago) the macports page was showing a healthy port (Sonoma on down). The problems are occurring because gstreamer and related ports were recently updated to new major versions and not all ports are compatible with these new versions. In the case of webkit2-gtk, gstreamer1-gst-plugins-base was updated in such a way that its optional gstreamergl function was disabled. webkit2-gtk linked with that component which is why rev-upgrade reports it as broken. webkit2-gtk relies on that component which is why rebuilding webkit2-gtk now fails. In the case of rygel, it was a different problem related to the gstreamer update that I have filed as https://trac.macports.org/ticket/69707. The fact that cmake was recently updated is unrelated. Port health indicators on the ports web site are not authoritative. They merely reflect what happened the last time an attempt to build those ports on the build system was made—usually (sometimes build results are lost). It does not indicate what will happen if you try to build the port today. Its dependencies could for example have been updated to incompatible versions since the last time the port was built.
Re: always have broken files at the end of a self-update
I have exactly the same problem, but with rygel as another affected build. I've uninstalled rygel but left webkit2-gtk in place. I now just ignore the rev-upgrade suggestion (n). It seems to be associated with gstreamer and cmake (cmake recently updated on my Ventura machine). Last time I looked (two days ago) the macports page was showing a healthy port (Sonoma on down). Cheers, Alex. > On 10 Apr 2024, at 4:20 AM, Ryan Schmidt wrote: > > >> On Apr 9, 2024, at 13:02, Kenneth Wolcott wrote: >> >> At the end of each self-update I get the following error message, in >> spite of whether I respond with yes or no: >> >> >> ---> Updating database of binaries >> >> ---> Scanning binaries for linking errors >> >> Could not open /opt/local/lib/libgstgl-1.0.0.dylib: Error opening or >> reading file (referenced from >> /opt/local/lib/libwebkit2gtk-4.0.37.44.4.dylib) >> >> ---> Found 6 broken files, matching files to ports >> >> ---> Found 1 broken port, determining rebuild order >> >> You can always run 'port rev-upgrade' again to fix errors. >> >> The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 > > This problem will continue until this ticket is resolved: > > https://trac.macports.org/ticket/69640 >
Re: always have broken files at the end of a self-update
Thank you for the explanation. Thanks, Ken Wolcott On Tue, Apr 9, 2024 at 11:19 AM Ryan Schmidt wrote: > > On Apr 9, 2024, at 13:02, Kenneth Wolcott wrote: > > > At the end of each self-update I get the following error message, in > spite of whether I respond with yes or no: > > > ---> Updating database of binaries > > ---> Scanning binaries for linking errors > > Could not open /opt/local/lib/libgstgl-1.0.0.dylib: Error opening or > reading file (referenced from > /opt/local/lib/libwebkit2gtk-4.0.37.44.4.dylib) > > ---> Found 6 broken files, matching files to ports > > ---> Found 1 broken port, determining rebuild order > > You can always run 'port rev-upgrade' again to fix errors. > > The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 > > > This problem will continue until this ticket is resolved: > > https://trac.macports.org/ticket/69640 >
Re: always have broken files at the end of a self-update
On Apr 9, 2024, at 13:02, Kenneth Wolcott wrote: > > At the end of each self-update I get the following error message, in > spite of whether I respond with yes or no: > > > ---> Updating database of binaries > > ---> Scanning binaries for linking errors > > Could not open /opt/local/lib/libgstgl-1.0.0.dylib: Error opening or > reading file (referenced from > /opt/local/lib/libwebkit2gtk-4.0.37.44.4.dylib) > > ---> Found 6 broken files, matching files to ports > > ---> Found 1 broken port, determining rebuild order > > You can always run 'port rev-upgrade' again to fix errors. > > The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 This problem will continue until this ticket is resolved: https://trac.macports.org/ticket/69640
always have broken files at the end of a self-update
At the end of each self-update I get the following error message, in spite of whether I respond with yes or no: ---> Updating database of binaries ---> Scanning binaries for linking errors Could not open /opt/local/lib/libgstgl-1.0.0.dylib: Error opening or reading file (referenced from /opt/local/lib/libwebkit2gtk-4.0.37.44.4.dylib) ---> Found 6 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 I get the following warning: sudo port diagnose Password: Warning: found dylibs in your /usr/local/lib directory. These are known to cause problems. We'd recommend you remove them. Warning: found header files in your /usr/local/include directory. These are known to cause problems. We'd recommend you remove them. ls /usr/local/lib cmake docker libgmp.a libgmp.la libprimesieve.a perl5 pkgconfig sudo /bin/rm /usr/local/lib/libgmp.a sudo /bin/rm /usr/local/lib/libgmp.la sudo /bin/rm /usr/local/lib/libprimesieve.a ls /usr/local/include pari primesieve primesieve.hpp sudo /bin/rm /usr/local/include/primesieve.hpp sudo port diagnose [no output!] Now when doing self-update when there's nothing new in ports I get this: port outdated The following installed ports are outdated: borgbackup 1.2.7_1 < 1.2.8_1 mpv0.37.0_2 < 0.37.0_3 octave 8.4.0_2 < 9.1.0_0 This is a different issue which I will discuss in a different email. Now when I have an upgrade or install will I still have a broken link error message at the end of the port upgrade or install process? I have a build log (attached, since it is very small). Thanks, Ken Wolcott build_failed_webkit2-gtk.log Description: Binary data
