Re: Trouble installing some (but not all) ports

[Ryan Schmidt]

On Jan 12, 2016, at 8:15 PM, Brittany B. Lott wrote:

> I’m pretty new to using MacPorts and the command line in general, so I’m 
> hoping this is an easy fix for someone who knows what they’re doing. So far, 
> I’ve had success installing fun ports that weren’t my main goal (like the 
> ports “figlet” and “add”), but the ones I can’t install are “Pallet” and 
> "auto-multiple-choice” (which is the one I really want). I’m not sure exactly 
> what information is necessary for someone to diagnose the problem, but I am 
> more than happy to provide whatever can help explain the situations better. 
> 
> Problem 1: (If they aren’t related and only one problem gets fixed, I would 
> like it to be this one!) Here is the error output when I enter the command 
> "sudo port -d install auto-multiple-choice”:
> 
> DEBUG: couldn't open 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_auto-multiple-choice/auto-multiple-choice/work/.macports.auto-multiple-choice.state":
>  permission denied
> while executing
> "open $statefile a+"
> (procedure "open_statefile" line 124)
> invoked from within
> "open_statefile"
> (procedure "check_variants" line 29)
> invoked from within
> "check_variants activate"
> invoked from within
> "$workername eval check_variants $target"
> (procedure "mportexec" line 7)
> invoked from within
> "mportexec $workername $target"
> Error: Unable to execute port: couldn't open 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_auto-multiple-choice/auto-multiple-choice/work/.macports.auto-multiple-choice.state":
>  permission denied
> 
> It turns out that the file it can’t open doesn’t exist. Any ideas?

Clean and try again?

sudo port clean auto-multiple-choice

Make sure you are using "sudo" each time you run a port command that's meant to 
modify things (like clean or install or uninstall). The error you got looks 
like the error you'd get if you sometimes forgot to use "sudo".


> Problem 2: Incidentally, I get a different error when I try to install Pallet 
> ("sudo port -d install Pallet”):
> 
> The following build commands failed:
>   CompileC 
> build/MacPorts.Framework.build/Release/MPHelperTool.build/Objects-normal/x86_64/MPHelperTool.o
>  MPHelperTool.m normal x86_64 objective-c 
> com.apple.compilers.llvm.clang.1_0.compiler
> (1 failure)
> Command failed: cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/work/MacPorts_Framework"
>  && /usr/bin/xcodebuild  -target "MacPorts" -configuration Release build 
> OBJROOT=build/ SYMROOT=build/ MACOSX_DEPLOYMENT_TARGET=10.10 ARCHS=x86_64 
> SDKROOT="" GCC_VERSION=com.apple.compilers.llvm.clang.1_0 
> CLANG_CXX_LIBRARY="libc++" 
> Exit code: 65
> Error: org.macports.build for port MacPorts_Framework returned: command 
> execution failed
> DEBUG: Error code: NONE
> DEBUG: Backtrace: command execution failed
> while executing
> "proc-org.macports.build-build-0 org.macports.build"
> ("eval" body line 1)
> invoked from within
> "eval $procedure $targetname"
> Warning: targets not executed for MacPorts_Framework: org.macports.activate 
> org.macports.build org.macports.destroot org.macports.install
> Error: Failed to install MacPorts_Framework
> DEBUG: Registry error: MacPorts_Framework not registered as installed & 
> active.
> invoked from within
> "registry_active $subport"
> invoked from within
> "$workername eval registry_active \$subport"
> Please see the log file for port MacPorts_Framework for details:
> 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/main.log
> Error: The following dependencies were not installed: MacPorts_Framework
> To report a bug, follow the instructions in the guide:
> http://guide.macports.org/#project.tickets
> Error: Processing of port Pallet failed
> 
> Reading the main.log file referenced there at the end gives pretty much the 
> same output as I’ve copied here.

At present, Pallet has numerous bugs which make it incompatible with current 
versions of MacPorts and Xcode.

https://trac.macports.org/query?status=!closed=~pallet

During Google Summer of Code 2015 Kyle was working on Pallet. I'm not sure what 
the status of that work is or whether it fixed these problems.




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: KDE Printing Question ... and KDE3

[René J . V . Bertin]

On Tuesday January 12 2016 00:12:45 Jeremy Lavergne wrote:

>MacPorts has a copy of the sources; while it may build, I cannot make
>any claims of it runs. At this point, and with John's subsequent input,
>I aim to simply remove the software.

Ah, right, that was it. I remembered setting out to look and try to build the 
beast, but forgot I stopped short when I noticed it was KDE3 software.

Someone will have to decide what to do with the KDE3 ports in MacPorts and 
before that, if and how to tackle the Qt3 port. Given the popularity KDE3 still 
has with certain followings I would hesitate to recommend removing it, but I 
suppose Qt3 would have to be made co-installable. The KDE3 ports should 
probably be aligned to the Trinity Desktop effort, if it is decided to keep 
them.

I'm not volunteering ;)

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

matplotlib + ipython notebook crashing

[Gideon Simpson]

I’m finding that when I use the OS X backend for matplotlib with ipython 
notebooks, the python application launcher crashes.  Has anyone else had this 
problem?
-gideon

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Perl5 (meta package) switched from 5.16 to 5.22 - p5-* and git not switched

[Justin Vallon]

I just did a selfupdate && upgrade, and perl5 was upgraded from perl5.16
to perl5.22.

However, my p5-string-shellquote was not automatically upgraded from
p5.16- to p5.22-, and I had to reinstall it.

Similar for git and ossp-uuid.  Each had a perl5_16 variant installed
and ugprade did nothing, but reinstalling ended up with perl5_22.

My guess is that the perl5 Portfile was changed, so upgrade rebuilt it
and thus installed perl5.22, but p5-string-shellquote was not changed,
so did not get an automatic upgrade.

Is this expected?

-- 
-Justin
justinval...@gmail.com




smime.p7s
Description: S/MIME Cryptographic Signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Perl5 (meta package) switched from 5.16 to 5.22 - p5-* and git not switched

[Justin Vallon]

On 1/12/16 3:26 PM, David Evans wrote:
> On 1/12/16 10:40 AM, Justin Vallon wrote:
>> I just did a selfupdate && upgrade, and perl5 was upgraded from perl5.16
>> to perl5.22.
>>
>> However, my p5-string-shellquote was not automatically upgraded from
>> p5.16- to p5.22-, and I had to reinstall it.
>>
>> Similar for git and ossp-uuid.  Each had a perl5_16 variant installed
>> and ugprade did nothing, but reinstalling ended up with perl5_22.
>>
>> My guess is that the perl5 Portfile was changed, so upgrade rebuilt it
>> and thus installed perl5.22, but p5-string-shellquote was not changed,
>> so did not get an automatic upgrade.
>>
>> Is this expected?
>>
> We're in the process of removing support for all perls older than perl5.22
> and perl5's default variant was recently changed from +perl5_16 to +perl5_22. 
>  This
> change causes new installs of perl5 (without specifying a specific variant)
> to be updated to perl5.22 as you say and p5.22-* to be the default version
> of the p5-* module ports.  Upgrades would have honored the old installed 
> variant
> (+perl5_16 and p5.16-* in your case).
>
> However, the older variants of perl5 were subsequently removed, breaking the
> desired upgrade behavior.  This step was premature and should have been 
> deferred
> until support for the older perls had been obsoleted from the p5-* modules
> and the old perl variants removed from ports that use them so that the 
> effected
> ports would automatically upgrade to the perl5.22 versions as you expected.
>
> It would then be safe to remove the old perl5 variants.
>
> I'm not sure what the best approach is now to heal this damage but I'm leaning
> toward restoring the older variants to perl5 until the other steps
> have been taken. You'll then be able to install perl5 +perl5_16 again and use
> your p5.16-* modules (if you haven't already upgraded them to p5.22-*
> manually).  In the interim you should be able to use your existing p5.16-* 
> modules
> as long as perl5.16 is installed.
I fixed everything by either uninstalling and reinstalling (p5-*) or
"build git && install git", which ended up picking up the new default
variant (as far as I remember).

Your discussion does not appear to solve the problem of p5-* modules not
getting upgraded/rebuilt when perl5 is changed.  Consider:

1) perl5 was installed (default version 5.16), p5-blah module is installed
2) /opt/local/bin/perl can use the "Blah" module.
3) perl5 is upgraded to 5.22.  /opt/local/bin/perl is now 5.22.  p5-blah
is not automatically switched to 5.22.
4) /opt/local/bin/perl cannot find the "Blah" module.
5) reinstall p5-blah
6) /opt/local/bin/perl can use the "Blah" module again.

-- 
-Justin
justinval...@gmail.com




smime.p7s
Description: S/MIME Cryptographic Signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Perl5 (meta package) switched from 5.16 to 5.22 - p5-* and git not switched

[David Evans]

On 1/12/16 1:19 PM, Justin Vallon wrote:
> On 1/12/16 3:26 PM, David Evans wrote:
>> On 1/12/16 10:40 AM, Justin Vallon wrote:
>>> I just did a selfupdate && upgrade, and perl5 was upgraded from perl5.16
>>> to perl5.22.
>>>
>>> However, my p5-string-shellquote was not automatically upgraded from
>>> p5.16- to p5.22-, and I had to reinstall it.
>>>
>>> Similar for git and ossp-uuid.  Each had a perl5_16 variant installed
>>> and ugprade did nothing, but reinstalling ended up with perl5_22.
>>>
>>> My guess is that the perl5 Portfile was changed, so upgrade rebuilt it
>>> and thus installed perl5.22, but p5-string-shellquote was not changed,
>>> so did not get an automatic upgrade.
>>>
>>> Is this expected?
>>>
>> We're in the process of removing support for all perls older than perl5.22
>> and perl5's default variant was recently changed from +perl5_16 to 
>> +perl5_22.  This
>> change causes new installs of perl5 (without specifying a specific variant)
>> to be updated to perl5.22 as you say and p5.22-* to be the default version
>> of the p5-* module ports.  Upgrades would have honored the old installed 
>> variant
>> (+perl5_16 and p5.16-* in your case).
>>
>> However, the older variants of perl5 were subsequently removed, breaking the
>> desired upgrade behavior.  This step was premature and should have been 
>> deferred
>> until support for the older perls had been obsoleted from the p5-* modules
>> and the old perl variants removed from ports that use them so that the 
>> effected
>> ports would automatically upgrade to the perl5.22 versions as you expected.
>>
>> It would then be safe to remove the old perl5 variants.
>>
>> I'm not sure what the best approach is now to heal this damage but I'm 
>> leaning
>> toward restoring the older variants to perl5 until the other steps
>> have been taken. You'll then be able to install perl5 +perl5_16 again and use
>> your p5.16-* modules (if you haven't already upgraded them to p5.22-*
>> manually).  In the interim you should be able to use your existing p5.16-* 
>> modules
>> as long as perl5.16 is installed.
> I fixed everything by either uninstalling and reinstalling (p5-*) or
> "build git && install git", which ended up picking up the new default
> variant (as far as I remember).
> 
> Your discussion does not appear to solve the problem of p5-* modules not
> getting upgraded/rebuilt when perl5 is changed.  Consider:
> 
> 1) perl5 was installed (default version 5.16), p5-blah module is installed
> 2) /opt/local/bin/perl can use the "Blah" module.
> 3) perl5 is upgraded to 5.22.  /opt/local/bin/perl is now 5.22.  p5-blah
> is not automatically switched to 5.22.
> 4) /opt/local/bin/perl cannot find the "Blah" module.
> 5) reinstall p5-blah
> 6) /opt/local/bin/perl can use the "Blah" module again.
> 

This is why I restored the variants.  In the future when the p5.16 - p5.20 
subports
are removed from the p5 ports, they will declared obsolete which will cause them
to update to p5.22.  Then the old variants and ultimately the old perl5.* ports 
themselves
can be removed without problems.  For now, if you reinstall perl5 +perl5_16 it 
will reset
your default perl to perl5.16 avoiding the issue.



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Need A Data Visualization/Graphing Program

[Richard L. Hamilton]

STK is _the_ commercial satellite tracking program, advanced versions do 
everything (look angle, coverage, maneuvering info, everything); but it's 
expensive (although there's a free license for a limited version), it only runs 
on Windows, and they will send you email forever.

Within MacPorts, there's xephem (although in MacPorts it's 3.7.4, should be 
updated to 3.7.7); it can plot every astronomical object, and satellites too, 
showing either sky views from specific locations, or tracks.  xephem is 
X11/Motif based (runs on anything where those can be used).  Google for it to 
find its web site (it's not the most obvious to use until you get used to it) 
including screenshots and where to get satellite data.

> On Jan 10, 2016, at 21:57, Charles Phillips  
> wrote:
> 
> All -
> 
> This is probably a simple question to answer, but I have not stumbled across 
> the answer yet. 
> 
> I have installed GPredict (satellite tracking program) on a number of Mac 
> computers (starting with my Powerbook G4 and most lately on my Mac Mini and 
> my MacBook Pro) and have been looking for a program that would easily allow 
> me to plot orbital parameters. I follow satellites. 
> 
> Right now I use Numbers for some, and have struggled with Excel. I need a 
> flexible program that allows me to enter some columns of data (perigee, 
> apogee, inclination, etc) and graph them again time of the orbital 
> description (I use Two Line Element sets from the U.S. Air Force). 
> 
> I looked in the "Math" category and have not managed to find anything. 
> MacPorts does not have a way to search for "graphing utilities" that I have 
> found?? 
> 
> I briefly tried to use a neat program called Plot2 that I ran across but I 
> could not get any support. 
> 
> There must be a ported Unix application out there that I just have not run 
> across yet??
> 
> Charles Phillips
> Spaceflight Research, LLC
> Houston, Texas
> 713-882-4578
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Need A Data Visualization/Graphing Program

[Richard L. Hamilton]

Oh, if you have an iPhone or iPad (or iPod Touch), there's the $9.99 
GoSatWatch, which ought to be easier than crunching numbers and more portable 
than something on a laptop.


> On Jan 12, 2016, at 06:57, Richard L. Hamilton  wrote:
> 
> STK is _the_ commercial satellite tracking program, advanced versions do 
> everything (look angle, coverage, maneuvering info, everything); but it's 
> expensive (although there's a free license for a limited version), it only 
> runs on Windows, and they will send you email forever.
> 
> Within MacPorts, there's xephem (although in MacPorts it's 3.7.4, should be 
> updated to 3.7.7); it can plot every astronomical object, and satellites too, 
> showing either sky views from specific locations, or tracks.  xephem is 
> X11/Motif based (runs on anything where those can be used).  Google for it to 
> find its web site (it's not the most obvious to use until you get used to it) 
> including screenshots and where to get satellite data.
> 
>> On Jan 10, 2016, at 21:57, Charles Phillips > > wrote:
>> 
>> All -
>> 
>> This is probably a simple question to answer, but I have not stumbled across 
>> the answer yet. 
>> 
>> I have installed GPredict (satellite tracking program) on a number of Mac 
>> computers (starting with my Powerbook G4 and most lately on my Mac Mini and 
>> my MacBook Pro) and have been looking for a program that would easily allow 
>> me to plot orbital parameters. I follow satellites. 
>> 
>> Right now I use Numbers for some, and have struggled with Excel. I need a 
>> flexible program that allows me to enter some columns of data (perigee, 
>> apogee, inclination, etc) and graph them again time of the orbital 
>> description (I use Two Line Element sets from the U.S. Air Force). 
>> 
>> I looked in the "Math" category and have not managed to find anything. 
>> MacPorts does not have a way to search for "graphing utilities" that I have 
>> found?? 
>> 
>> I briefly tried to use a neat program called Plot2 that I ran across but I 
>> could not get any support. 
>> 
>> There must be a ported Unix application out there that I just have not run 
>> across yet??
>> 
>> Charles Phillips
>> Spaceflight Research, LLC
>> Houston, Texas
>> 713-882-4578
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org 
>> 
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Perl5 (meta package) switched from 5.16 to 5.22 - p5-* and git not switched

[David Evans]

On 1/12/16 12:26 PM, David Evans wrote:
> On 1/12/16 10:40 AM, Justin Vallon wrote:
>> I just did a selfupdate && upgrade, and perl5 was upgraded from perl5.16
>> to perl5.22.
>>
>> However, my p5-string-shellquote was not automatically upgraded from
>> p5.16- to p5.22-, and I had to reinstall it.
>>
>> Similar for git and ossp-uuid.  Each had a perl5_16 variant installed
>> and ugprade did nothing, but reinstalling ended up with perl5_22.
>>
>> My guess is that the perl5 Portfile was changed, so upgrade rebuilt it
>> and thus installed perl5.22, but p5-string-shellquote was not changed,
>> so did not get an automatic upgrade.
>>
>> Is this expected?
>>
> 
> We're in the process of removing support for all perls older than perl5.22
> and perl5's default variant was recently changed from +perl5_16 to +perl5_22. 
>  This
> change causes new installs of perl5 (without specifying a specific variant)
> to be updated to perl5.22 as you say and p5.22-* to be the default version
> of the p5-* module ports.  Upgrades would have honored the old installed 
> variant
> (+perl5_16 and p5.16-* in your case).
> 
> However, the older variants of perl5 were subsequently removed, breaking the
> desired upgrade behavior.  This step was premature and should have been 
> deferred
> until support for the older perls had been obsoleted from the p5-* modules
> and the old perl variants removed from ports that use them so that the 
> effected
> ports would automatically upgrade to the perl5.22 versions as you expected.
> 
> It would then be safe to remove the old perl5 variants.
> 
> I'm not sure what the best approach is now to heal this damage but I'm leaning
> toward restoring the older variants to perl5 until the other steps
> have been taken. You'll then be able to install perl5 +perl5_16 again and use
> your p5.16-* modules (if you haven't already upgraded them to p5.22-*
> manually).  In the interim you should be able to use your existing p5.16-* 
> modules
> as long as perl5.16 is installed.
> 
> Dave
> 

perl5 variants +perl5_16 +perl5_18 (temporarily) restored in 
https://trac.macports.org/changeset/144563.

After updating your ports with

sudo port selfupdate

you should be able to reinstall perl5 +perl5_16

sudo port install perl5 +perl5_16

and restore things as they were.

If you've already manually changed everything from p5.16-* to p5.22-* and ports 
with
perl variants to +perl5_22 no need to go back as this is the way things will be 
in the (not too distant) future.

Let us know if you have any remaining problems and sorry for any inconvenience.

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Perl5 (meta package) switched from 5.16 to 5.22 - p5-* and git not switched

[David Evans]

On 1/12/16 10:40 AM, Justin Vallon wrote:
> I just did a selfupdate && upgrade, and perl5 was upgraded from perl5.16
> to perl5.22.
> 
> However, my p5-string-shellquote was not automatically upgraded from
> p5.16- to p5.22-, and I had to reinstall it.
> 
> Similar for git and ossp-uuid.  Each had a perl5_16 variant installed
> and ugprade did nothing, but reinstalling ended up with perl5_22.
> 
> My guess is that the perl5 Portfile was changed, so upgrade rebuilt it
> and thus installed perl5.22, but p5-string-shellquote was not changed,
> so did not get an automatic upgrade.
> 
> Is this expected?
> 

We're in the process of removing support for all perls older than perl5.22
and perl5's default variant was recently changed from +perl5_16 to +perl5_22.  
This
change causes new installs of perl5 (without specifying a specific variant)
to be updated to perl5.22 as you say and p5.22-* to be the default version
of the p5-* module ports.  Upgrades would have honored the old installed variant
(+perl5_16 and p5.16-* in your case).

However, the older variants of perl5 were subsequently removed, breaking the
desired upgrade behavior.  This step was premature and should have been deferred
until support for the older perls had been obsoleted from the p5-* modules
and the old perl variants removed from ports that use them so that the effected
ports would automatically upgrade to the perl5.22 versions as you expected.

It would then be safe to remove the old perl5 variants.

I'm not sure what the best approach is now to heal this damage but I'm leaning
toward restoring the older variants to perl5 until the other steps
have been taken. You'll then be able to install perl5 +perl5_16 again and use
your p5.16-* modules (if you haven't already upgraded them to p5.22-*
manually).  In the interim you should be able to use your existing p5.16-* 
modules
as long as perl5.16 is installed.

Dave


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: KDE Printing Question ... and KDE3

[Pierre Henri CHAUDOUARD]

I am a big fan of KDE3 for X11 that I use on my old computer (OS X Lion)! I 
have not tried to install it on my new computer (El Capitan) since there is 
little hope that it will work (as far I understand).  I would be very happy if 
there was a port of Trinity Desktop ...

Pierre-Henri

 

 

> Message du 12/01/16 10:15
> De : "René J.V. Bertin" 
> A : "Jeremy Lavergne" 
> Copie à : macports-users@lists.macosforge.org
> Objet : Re: KDE Printing Question ... and KDE3
> 
> On Tuesday January 12 2016 00:12:45 Jeremy Lavergne wrote:
> 
> >MacPorts has a copy of the sources; while it may build, I cannot make
> >any claims of it runs. At this point, and with John's subsequent input,
> >I aim to simply remove the software.
> 
> Ah, right, that was it. I remembered setting out to look and try to build the 
> beast, but forgot I stopped short when I noticed it was KDE3 software.
> 
> Someone will have to decide what to do with the KDE3 ports in MacPorts and 
> before that, if and how to tackle the Qt3 port. Given the popularity KDE3 
> still has with certain followings I would hesitate to recommend removing it, 
> but I suppose Qt3 would have to be made co-installable. The KDE3 ports should 
> probably be aligned to the Trinity Desktop effort, if it is decided to keep 
> them.
> 
> I'm not volunteering ;)
> 
> R.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: KDE Printing Question ... and KDE3

[René J . V . Bertin]

On Tuesday January 12 2016 16:45:40 Pierre Henri CHAUDOUARD wrote:
> I am a big fan of KDE3 for X11 that I use on my old computer (OS X Lion)! I 
> have not tried to install it on my new computer (El Capitan) since there is 
> little hope that it will work (as far I understand). 

I can only say: try it. Qt3 for X11 shouldn't use most of the native APIs that 
are problematic on 10.11, if any.

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Perl5 (meta package) switched from 5.16 to 5.22 - p5-* and git not switched

[Mojca Miklavec]

On 12 January 2016 at 19:40, Justin Vallon wrote:
> I just did a selfupdate && upgrade, and perl5 was upgraded from perl5.16
> to perl5.22.
>
> However, my p5-string-shellquote was not automatically upgraded from
> p5.16- to p5.22-, and I had to reinstall it.
>
> Similar for git and ossp-uuid.  Each had a perl5_16 variant installed
> and ugprade did nothing, but reinstalling ended up with perl5_22.
>
> My guess is that the perl5 Portfile was changed, so upgrade rebuilt it
> and thus installed perl5.22, but p5-string-shellquote was not changed,
> so did not get an automatic upgrade.
>
> Is this expected?

These problems should be fixed now (and you may [almost] ignore the
rest of the thread which is mostly no longer true).

Mojca

(PS: we still might have to revbump some ports though.)
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Trouble installing some (but not all) ports

[Brittany B. Lott]

Hi, 

I’m pretty new to using MacPorts and the command line in general, so I’m hoping 
this is an easy fix for someone who knows what they’re doing. So far, I’ve had 
success installing fun ports that weren’t my main goal (like the ports “figlet” 
and “add”), but the ones I can’t install are “Pallet” and 
"auto-multiple-choice” (which is the one I really want). I’m not sure exactly 
what information is necessary for someone to diagnose the problem, but I am 
more than happy to provide whatever can help explain the situations better. 

Problem 1: (If they aren’t related and only one problem gets fixed, I would 
like it to be this one!) Here is the error output when I enter the command 
"sudo port -d install auto-multiple-choice”:

DEBUG: couldn't open 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_auto-multiple-choice/auto-multiple-choice/work/.macports.auto-multiple-choice.state":
 permission denied
while executing
"open $statefile a+"
(procedure "open_statefile" line 124)
invoked from within
"open_statefile"
(procedure "check_variants" line 29)
invoked from within
"check_variants activate"
invoked from within
"$workername eval check_variants $target"
(procedure "mportexec" line 7)
invoked from within
"mportexec $workername $target"
Error: Unable to execute port: couldn't open 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_auto-multiple-choice/auto-multiple-choice/work/.macports.auto-multiple-choice.state":
 permission denied

It turns out that the file it can’t open doesn’t exist. Any ideas?

Problem 2: Incidentally, I get a different error when I try to install Pallet 
("sudo port -d install Pallet”):

The following build commands failed:
CompileC 
build/MacPorts.Framework.build/Release/MPHelperTool.build/Objects-normal/x86_64/MPHelperTool.o
 MPHelperTool.m normal x86_64 objective-c 
com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
Command failed: cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/work/MacPorts_Framework"
 && /usr/bin/xcodebuild  -target "MacPorts" -configuration Release build 
OBJROOT=build/ SYMROOT=build/ MACOSX_DEPLOYMENT_TARGET=10.10 ARCHS=x86_64 
SDKROOT="" GCC_VERSION=com.apple.compilers.llvm.clang.1_0 
CLANG_CXX_LIBRARY="libc++" 
Exit code: 65
Error: org.macports.build for port MacPorts_Framework returned: command 
execution failed
DEBUG: Error code: NONE
DEBUG: Backtrace: command execution failed
while executing
"proc-org.macports.build-build-0 org.macports.build"
("eval" body line 1)
invoked from within
"eval $procedure $targetname"
Warning: targets not executed for MacPorts_Framework: org.macports.activate 
org.macports.build org.macports.destroot org.macports.install
Error: Failed to install MacPorts_Framework
DEBUG: Registry error: MacPorts_Framework not registered as installed & active.
invoked from within
"registry_active $subport"
invoked from within
"$workername eval registry_active \$subport"
Please see the log file for port MacPorts_Framework for details:

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/main.log
Error: The following dependencies were not installed: MacPorts_Framework
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets 

Error: Processing of port Pallet failed

Reading the main.log file referenced there at the end gives pretty much the 
same output as I’ve copied here.

Thanks so much,
Brittany___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users