9/24/2023 0 Comments Macports rsync![]() Does the problem still persist after sudo port sync? My expectation is that it does not. The problem will resolve itself whenever in the future the revision or version of these ports is increased for any other reason thereby removing the inconsistency.ĭarwin 21 portindexes should exist on the servers now. I did this because the rebuild that this revision increase caused was exclusively intended to fix a Big Sur-specific problem and I didn't want to force users of other systems to rebuild the ports for no reason. This issue is apparently limited to those users upgrading from Big Sur to Monterey, because these two ports have an increased revision only on Big Sur. Thanks for the suggestions, I think this is probably related to the individual ports. > Installing zstd Activating zstd Cleaning zstd > Installing cyrus-sasl2 Activating cyrus-sasl2 Cleaning cyrus-sasl2 > Computing dependencies for cyrus-sasl2 > Unable to uninstall zstd the following ports depend on it: > Uninstalling cyrus-sasl2 Cleaning cyrus-sasl2 > Deactivating cyrus-sasl2 Cleaning cyrus-sasl2 > Unable to uninstall cyrus-sasl2 the following ports depend on it: √ ~ % sudo port uninstall -f cyrus-sasl2 zstd & sudo port install +kerberos & port outdated 18:59:24 I've tried forced uninstall + reinstall with specified version (see below) and still had the ports showing as outdated. However,, some other ports (p5.28-net-ssleay, p5.30-net-ssleay, and p5.32-net-ssleay) were later updated just fine. ![]() I had assumed that given the two unrelated ports were all that needed updating is that somehow MacPorts wasn't updating correctly. I'm thinking this is an issue with the individual ports, not MacPorts base. The latter led to many hours rebuilding, but left zstd and cyrus-sasl2 outdated. I also tried uninstalling+reinstalling and port -nR upgrade -force as suggested on . √ ~ % sudo port upgrade -f cyrus-sasl2 7:26:31 The following installed ports are outdated:Ĭyrus-sasl2 2.1.27_3 Scanning binaries for linking errors However, trying to update ports isn't working. The older releases prior to Erlang/OTP 18.0 were released under Erlang Public License (EPL), a derivative work of the Mozilla Public License (MPL).After completing migration steps , my MacPorts installation has been mostly reconstituted. Since Erlang/OTP 18.0, Erlang/OTP is released under Apache License 2.0. Erlang Solutions provides pre-built binary packages for Ubuntu, Debian, Fedora, CentOS and other operating systems. So Erlang Solutions provides up to date pre-built packages for the latest stable releases. The OS provided packages tend to not contain the latest version of Erlang/OTP. For ArchLinux and Manjaro: pacman -S erlang.For Ubuntu and Debian: apt-get install erlang.For MacPorts on macOS: port install erlang. ![]() For Homebrew on macOS: brew install erlang. ![]() Most OS package managers provide pre-built binary packages. They help to remove the differences between Erlang/OTP releases and the OS you are compiling on. You can also use third-party tools such as Kerl or asdf to compile Erlang. So always make sure to read the build and install instruction of the release you are compiling. If you clone the release from git, there may be some additional steps needed depending on which version of Erlang/OTP you are compiling. In a nutshell to install a pre-built archive you need only do. You can build Erlang from source on your own, following the building and installation instructions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |