Error installing new MacPorts base
I had an email saying that MacPorts 2.3.5 was available so I ran 'sudo port selfupdate’. The following, between ‘——‘ lines, appeared: - Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.3.4 installed, MacPorts base version 2.3.5 downloaded. ---> Updating the ports tree ---> MacPorts base is outdated, installing new version 2.3.5 Installing new MacPorts release in /opt/local as gbs:admin; permissions 0755 Error: Error installing new MacPorts base: command execution failed Please run `port -v selfupdate' for details. Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed - I ran ‘sudo port -v selfupdate’ and the result is in the attachment. I have no idea how to proceed so I am asking for help and will be pleased for any suggestions regarding what to do next. Barrie. result Description: Binary data
Re: Error installing new MacPorts base
On 2016-11-21 10:39, Barrie Stott wrote: > - > Password: > ---> Updating MacPorts base sources using rsync > MacPorts base version 2.3.4 installed, > MacPorts base version 2.3.5 downloaded. > ---> Updating the ports tree > ---> MacPorts base is outdated, installing new version 2.3.5 > Installing new MacPorts release in /opt/local as gbs:admin; permissions 0755 > > Error: Error installing new MacPorts base: command execution failed > Please run `port -v selfupdate' for details. > Error: /opt/local/bin/port: port selfupdate failed: Error installing new > MacPorts base: command execution failed > - > > I ran ‘sudo port -v selfupdate’ and the result is in the attachment. I have > no idea how to proceed so I am asking for help and will be pleased for any > suggestions regarding what to do next. The error is: checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base': configure: error: C compiler cannot create executables See `config.log' for more details We would need to see the contents of the config.log file to tell the exact details while the compiler execution failed: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base/config.log A similar case was described in: https://trac.macports.org/ticket/49169 You could try to execute /usr/bin/cc directly to see what error messages it returns. Maybe you have not accepted the Xcode license terms. Rainer
Re: p5.22-specio failed to uninstall
> On Nov 20, 2016, at 12:38 PM, Lawrence Velázquez wrote: > >> On Nov 19, 2016, at 7:52 PM, Dave Horsfall wrote: >> >> Doing my weekly "port -u uninstall", I get: >> >> ---> Unable to uninstall p5.22-specio @0.280.0_0, the following ports >> depend on it: >> ---> p5.22-datetime-locale @1.80.0_0 >> ---> p5.22-datetime-timezone @2.50.0_0 >> Error: org.macports.uninstall for port p5.22-specio returned: Please >> uninstall the ports that depend on p5.22-specio first. >> >> Shouldn't those dependencies have been uninstalled for me? > > (a) You mean dependents. > > (b) No, MacPorts does not automatically uninstall either dependencies or > dependents. You have to tell it to explicitly do so: > > sudo port uninstall --follow-dependencies foo > sudo port uninstall --follow-dependents foo He's not naming a specific port; instead, he's using "sudo port -u uninstall", which is the same as "sudo port uninstall inactive". Why would an inactive replaced port have dependents?
Re: Error installing new MacPorts base
> On 21 Nov 2016, at 09:59, Rainer Müller wrote: > > On 2016-11-21 10:39, Barrie Stott wrote: >> - >> Password: >> ---> Updating MacPorts base sources using rsync >> MacPorts base version 2.3.4 installed, >> MacPorts base version 2.3.5 downloaded. >> ---> Updating the ports tree >> ---> MacPorts base is outdated, installing new version 2.3.5 >> Installing new MacPorts release in /opt/local as gbs:admin; permissions 0755 >> >> Error: Error installing new MacPorts base: command execution failed >> Please run `port -v selfupdate' for details. >> Error: /opt/local/bin/port: port selfupdate failed: Error installing new >> MacPorts base: command execution failed >> - >> >> I ran ‘sudo port -v selfupdate’ and the result is in the attachment. I have >> no idea how to proceed so I am asking for help and will be pleased for any >> suggestions regarding what to do next. > > The error is: > > Maybe you have not accepted the Xcode license > terms. That was the problem! I now get: - ---> Updating MacPorts base sources using rsync MacPorts base version 2.3.4 installed, MacPorts base version 2.3.5 downloaded. ---> Updating the ports tree ---> MacPorts base is outdated, installing new version 2.3.5 Installing new MacPorts release in /opt/local as gbs:admin; permissions 0755 The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated - I do apologise. I had no idea that I had not accepted the Xcode licence and I’m very grateful for the help, Rainer. No reply is needed; I feel I’ve used up enough good will! Barrie.
Re: p5.22-specio failed to uninstall
> On Nov 21, 2016, at 5:06 AM, Ryan Schmidt wrote: > > He's not naming a specific port; instead, he's using "sudo port -u > uninstall", which is the same as "sudo port uninstall inactive". Ah, I was not aware of that. > Why would an inactive replaced port have dependents? I'm not sure. vq
Certbot port?
Any chance of a Certbot port? https://certbot.eff.org/ They've got an install with Homebrew, but I'd rather do everything with MacPorts. (yeah, I know, I could learn to build ports myself and become the maintainer. And maybe I will at some point, but not right now)
Re: Certbot port?
Hi Bill
Looks like the certbot-auto also has some support for Macports
curl -O https://dl.eff.org/certbot-auto
LINE 435:
BootstrapMac() {
if hash brew 2>/dev/null; then
echo "Using Homebrew to install dependencies..."
pkgman=brew
pkgcmd="brew install"
elif hash port 2>/dev/null; then
echo "Using MacPorts to install dependencies..."
pkgman=port
pkgcmd="$SUDO port install"
else
echo "No Homebrew/MacPorts; installing Homebrew..."
ruby -e "$(curl -fsSL
https://raw.githubusercontent.com/Homebrew/install/master/install)"
pkgman=brew
pkgcmd="brew install"
fi
Although it looks like it insists on setting up a python virtualenv for you.
and then pulls in python dependancies with pip, which is not the normal
macports way.
https://letsencrypt.readthedocs.org/en/latest/contributing.html#prerequisites
I'll set up a VM and try it and let you know (don't want to break my main Mac).
Mike
> On 22/11/2016, at 10:38 AM, Bill Christensen
> wrote:
>
> Any chance of a Certbot port? https://certbot.eff.org/
>
Re: Certbot port?
Mike,
I have py-certbot installed locally, using MacPorts for all prerequisites as
well. I haven’t uploaded it to the macports-ports repository, as I no longer
have a web server running macOS, so I have not tested most current versions.
See
https://github.com/Schamschula/macports/blob/master/python/py-certbot/Portfile
On Nov 21, 2016, at 5:34 PM, Mike Savory wrote:
> Hi Bill
>
> Looks like the certbot-auto also has some support for Macports
> curl -O https://dl.eff.org/certbot-auto
>
> LINE 435:
>
> BootstrapMac() {
> if hash brew 2>/dev/null; then
> echo "Using Homebrew to install dependencies..."
> pkgman=brew
> pkgcmd="brew install"
> elif hash port 2>/dev/null; then
> echo "Using MacPorts to install dependencies..."
> pkgman=port
> pkgcmd="$SUDO port install"
> else
> echo "No Homebrew/MacPorts; installing Homebrew..."
> ruby -e "$(curl -fsSL
> https://raw.githubusercontent.com/Homebrew/install/master/install)"
> pkgman=brew
> pkgcmd="brew install"
> fi
>
> Although it looks like it insists on setting up a python virtualenv for you.
> and then pulls in python dependancies with pip, which is not the normal
> macports way.
> https://letsencrypt.readthedocs.org/en/latest/contributing.html#prerequisites
>
> I'll set up a VM and try it and let you know (don't want to break my main
> Mac).
>
> Mike
>
>> On 22/11/2016, at 10:38 AM, Bill Christensen
>> wrote:
>>
>> Any chance of a Certbot port? https://certbot.eff.org/
>>
>> They've got an install with Homebrew, but I'd rather do everything with
>> MacPorts.
>>
>> (yeah, I know, I could learn to build ports myself and become the
>> maintainer. And maybe I will at some point, but not right now)
>
Marius
--
Marius Schamschula
Broken ports?
Hi, I am on macOS 10.6.8, and was at MacPorts 2.3.4. I use MacPorts intermittently, so I am not that familiar with edge cases and figuring out failures. I just tried this: $ port info surf Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'. surf @1.0.6 (math) Variants: [+]gui, universal Description: surf is a tool to visualize some real algebraic geometry: plane algebraic curves, algebraic surfaces and hyperplane sections of surfaces. surf is script driven and has (optionally) a nifty GUI using the Gtk widget set. Homepage: http://surf.sourceforge.net/ Library Dependencies: gmp, flex, jpeg, tiff, xorg-libX11, gtk1, xorg-libXmu Platforms:darwin License: GPL-2 Maintainers: shreevatsa.pub...@gmail.com, openmaintai...@macports.org Then I did a selfupgrade, which took me to 2.3.5. Then this: $ so port install surf Warning: Skipping surf (not in the ports tree) ---> Scanning binaries for linking errors ---> No broken files found. Then I upgraded the outdated ports, which wandered around for a while, and ended with this: ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 4 broken file(s), matching files to ports Warning: No port surf found in the index; can't rebuild ---> Broken files found, but all associated ports are not in the index and so cannot be rebuilt. Since this didn't give me much to go on, I looked in the manual, and decided to try $ so port -v rev-upgrade ---> Scanning binaries for linking errors Could not open /opt/local/lib/libglib-1.2.0.dylib: Error opening or reading file (referenced from /opt/local/bin/surf) Could not open /opt/local/lib/libgmodule-1.2.0.dylib: Error opening or reading file (referenced from /opt/local/bin/surf) Could not open /opt/local/lib/libgdk-1.2.0.dylib: Error opening or reading file (referenced from /opt/local/bin/surf) Could not open /opt/local/lib/libgtk-1.2.0.dylib: Error opening or reading file (referenced from /opt/local/bin/surf) ---> Found 4 broken file(s), matching files to ports Warning: No port surf found in the index; can't rebuild ---> Broken files found, but all associated ports are not in the index and so cannot be rebuilt. Surf is installed, -rwxr-xr-x 1 root admin 615928 Sep 3 2014 /opt/local/bin/surf but obviously broken. Is this no longer supported? Thanks for any help/pointers. Justin -- Justin C. Walker Curmudgeon-at-large -- Network, n., Difference between work charged for and work done
Re: Broken ports?
Justin, See https://trac.macports.org/changeset/154370 On Nov 21, 2016, at 6:39 PM, Justin C. Walker wrote: > Hi, > > I am on macOS 10.6.8, and was at MacPorts 2.3.4. I use MacPorts > intermittently, so I am not that familiar with edge cases and figuring out > failures. > > I just tried this: > > $ port info surf > Warning: port definitions are more than two weeks old, consider updating them > by running 'port selfupdate'. > surf @1.0.6 (math) > Variants: [+]gui, universal > > Description: surf is a tool to visualize some real algebraic > geometry: plane algebraic > curves, algebraic surfaces and hyperplane sections of > surfaces. surf is > script driven and has (optionally) a nifty GUI using the > Gtk widget set. > Homepage: http://surf.sourceforge.net/ > > Library Dependencies: gmp, flex, jpeg, tiff, xorg-libX11, gtk1, xorg-libXmu > Platforms:darwin > License: GPL-2 > Maintainers: shreevatsa.pub...@gmail.com, openmaintai...@macports.org > > > Then I did a selfupgrade, which took me to 2.3.5. Then this: > > > $ so port install surf > Warning: Skipping surf (not in the ports tree) > ---> Scanning binaries for linking errors > ---> No broken files found. > > > Then I upgraded the outdated ports, which wandered around for a while, and > ended with this: > > > ---> Updating database of binaries > ---> Scanning binaries for linking errors > ---> Found 4 broken file(s), matching files to ports > Warning: No port surf found in the index; can't rebuild > ---> Broken files found, but all associated ports are not in the index and > so cannot be rebuilt. > > > Since this didn't give me much to go on, I looked in the manual, and decided > to try > > $ so port -v rev-upgrade > ---> Scanning binaries for linking errors > Could not open /opt/local/lib/libglib-1.2.0.dylib: Error opening or reading > file (referenced from /opt/local/bin/surf) > Could not open /opt/local/lib/libgmodule-1.2.0.dylib: Error opening or > reading file (referenced from /opt/local/bin/surf) > Could not open /opt/local/lib/libgdk-1.2.0.dylib: Error opening or reading > file (referenced from /opt/local/bin/surf) > Could not open /opt/local/lib/libgtk-1.2.0.dylib: Error opening or reading > file (referenced from /opt/local/bin/surf) > ---> Found 4 broken file(s), matching files to ports > Warning: No port surf found in the index; can't rebuild > ---> Broken files found, but all associated ports are not in the index and > so cannot be rebuilt. > > > Surf is installed, > -rwxr-xr-x 1 root admin 615928 Sep 3 2014 /opt/local/bin/surf > > but obviously broken. Is this no longer supported? > > Thanks for any help/pointers. > > Justin > > -- > Justin C. Walker > Curmudgeon-at-large > -- > Network, n., Difference between work > charged for and work done > > > Marius -- Marius Schamschula
Re: Broken ports?
On Nov 21, 2016, at 17:04 , Marius Schamschula wrote: > Justin, > > See https://trac.macports.org/changeset/154370 That explains a lot! Thanks. Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds --- If it weren't for carbon-14, I wouldn't date at all. ---
Re: p5.22-specio failed to uninstall
On Mon, 21 Nov 2016, Lawrence Velázquez wrote: > > Why would an inactive replaced port have dependents? > > I'm not sure. Well, I've come to a grinding halt because of this. What further information can I supply so this can be fixed? Note that I don't even know what that port is (I assume it's to do with Perl), as it's required by something else. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Re: p5.22-specio failed to uninstall
> On Nov 21, 2016, at 10:29 PM, Dave Horsfall wrote: > >> On Mon, 21 Nov 2016, Lawrence Velázquez wrote: >> >>> Why would an inactive replaced port have dependents? >> >> I'm not sure. > > Well, I've come to a grinding halt because of this. What further > information can I supply so this can be fixed? What does "port installed p5.22-specio" output? vq
