Re: reinstalling Macports

[Ryan Schmidt]

On Apr 18, 2018, at 23:42, Ryan Schmidt wrote:

> Thanks. I think this problem was introduced by a presumably unintentional 
> part of this commit:
> 
> https://github.com/macports/macports-ports/commit/e3710d6800e803ebaa9528d3bdb38fb2fcade513#diff-5513a677784c8c1520463fedf268a37f
> 
> I think that needs to be reverted, and the tk port's revision increased to 
> ensure any incorrect builds out there get fixed.
> 
> Vince?

The problem was brought up again in this ticket:

https://trac.macports.org/ticket/56531

I fixed by reverting Vincent's change:

https://github.com/macports/macports-ports/commit/a11b15ca0f34af6272ed560aba505e08da45e360

Re: MacPorts 2.5.0-beta1 now available for testing

[Ryan Schmidt]

On May 25, 2018, at 12:57, Zero King wrote:

> On Thu, May 17, 2018 at 11:36:39PM +1000, Joshua Root wrote:
>> It's been a week with no new tickets filed against base. I'll give it
>> one more week and then, if nothing comes up, tag a release candidate.
>> 
>> - Josh
> 
> I tried the rc1, and unar is now "broken". How can I fix it?
> 
> unar is using libstdc++ (this installation is configured to use libc++)
> Error: Port unar is still broken after rebuilding it more than 3 times.

It's "broken" in that it links with libstdc++, even though MacPorts believes it 
will link with libc++ on your system. The rev-upgrade code in previous versions 
of MacPorts did not check for this kind of "broken".

Fix it by fixing the build system to use the right C++ standard library (the 
one in the ${configure.cxx_stdlib} variable).

Re: waiting for lock

[Rainer Müller]

On 2018-05-25 04:37, Jihyun In wrote:
> I accidentally closed my terminal while updating my port. Now it says
> waiting for lock on /opt/ocal/var/macports/registry/.registry.lock I
> tried to uninstall macports so that I could reinstall it, but it still
> gives me that. What should I do? Answers would be much appreciated.
> Thank you!

This means that the port command is still running in the background
after you closed the terminal window. You have to kill this process to
free the lock. Check for "tclsh" in Activity Monitor.

Rainer

Re: waiting for lock

[pagani laurent via macports-users]

Hi,

my .registry.lock file exists and is empty.
If it is absent, you should create it
If it is present but not empty, you should try to empty it.
I have no idea whether that will work but it can’t be worse than the present 
state.

L.

> Le 25 mai 2018 à 04:37, Jihyun In  a écrit :
> 
> Hi,
> I accidentally closed my terminal while updating my port. Now it says waiting 
> for lock on /opt/ocal/var/macports/registry/.registry.lock I tried to 
> uninstall macports so that I could reinstall it, but it still gives me that. 
> What should I do? Answers would be much appreciated. Thank you!

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)