Re: How upgrade p5.20-test, p5.20-module-build

2014-12-23 Thread David Evans

On 12/22/14 12:34 PM, Murray Eisenberg wrote:

I'm trying to upgrade the indicated ports. I keep getting error messages like 
this:

   ---  Activating p5.20-test-simple @1.1.11_0
Error: org.macports.activate for port p5.20-test-simple returned: Image error: 
/opt/local/lib/perl5/vendor_perl/5.20/Test/Tester.pm is being used by the 
active p5.20-test-tester port.  Please deactivate this port first, or use 'port 
-f activate p5.20-test-simple' to force the activation.

I try deactivating or using the -f flag, but I still get similar errors. I've 
tried to uninstall but find myself in a morass of dependent modules.

How get out of this?



Fixes for p5-test-simple, p5-test-tester, p5-test-use-ok issues 
committed in r129916.

Fix for p5-module-build, p5-inc-latest issues committed in 129932.

Happy Holidays to all!

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


How upgrade p5.20-test, p5.20-module-build

2014-12-22 Thread Murray Eisenberg
I'm trying to upgrade the indicated ports. I keep getting error messages like 
this:

  ---  Activating p5.20-test-simple @1.1.11_0
Error: org.macports.activate for port p5.20-test-simple returned: Image error: 
/opt/local/lib/perl5/vendor_perl/5.20/Test/Tester.pm is being used by the 
active p5.20-test-tester port.  Please deactivate this port first, or use 'port 
-f activate p5.20-test-simple' to force the activation.

I try deactivating or using the -f flag, but I still get similar errors. I've 
tried to uninstall but find myself in a morass of dependent modules.

How get out of this?


---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334





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


Re: How upgrade p5.20-test, p5.20-module-build

2014-12-22 Thread David Evans

On 12/22/14 12:34 PM, Murray Eisenberg wrote:

I'm trying to upgrade the indicated ports. I keep getting error messages like 
this:

   ---  Activating p5.20-test-simple @1.1.11_0
Error: org.macports.activate for port p5.20-test-simple returned: Image error: 
/opt/local/lib/perl5/vendor_perl/5.20/Test/Tester.pm is being used by the 
active p5.20-test-tester port.  Please deactivate this port first, or use 'port 
-f activate p5.20-test-simple' to force the activation.

I try deactivating or using the -f flag, but I still get similar errors. I've 
tried to uninstall but find myself in a morass of dependent modules.

How get out of this?


---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334




This is a known problem which has not as yet been fixed. Basicly, 
p5-test-tester (and p5-test-use-ok) have been integrated into 
p5-test-simple and are no longer

required to build any port. See https://trac.macports.org/ticket/46300.

To work around this:

  1) make sure your ports are up-to-date
sudo port selfupdate
  2) uninstall/deactivate p5.*-test-tester and p5.*-test-use-ok
sudo port -f uninstall p5.*-test-tester and installed
sudo port -f uninstall p5.*-test-use-ok and installed
  3) clean and upgrade p5*-test-simple
sudo port clean p5*-test-simple
sudo port upgrade p5.20-test-simple

I believe this should work for you

Dave


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


Re: How upgrade p5.20-test, p5.20-module-build

2014-12-22 Thread Murray Eisenberg
What about p5.*-test-output and p5.*-module-build, which seem to be giving 
similar errors on trying to upgrade?


On 22 Dec2014, at 3:53 PM, David Evans dev...@macports.org wrote:

 On 12/22/14 12:34 PM, Murray Eisenberg wrote:
 I'm trying to upgrade the indicated ports. I keep getting error messages 
 like this:
 
   ---  Activating p5.20-test-simple @1.1.11_0
 Error: org.macports.activate for port p5.20-test-simple returned: Image 
 error: /opt/local/lib/perl5/vendor_perl/5.20/Test/Tester.pm is being used by 
 the active p5.20-test-tester port.  Please deactivate this port first, or 
 use 'port -f activate p5.20-test-simple' to force the activation.
 
 I try deactivating or using the -f flag, but I still get similar errors. 
 I've tried to uninstall but find myself in a morass of dependent modules.
 
 How get out of this?
 
 
 ---
 Murray Eisenberg murrayeisenb...@gmail.com
 503 King Farm Blvd #101  Home (240)-246-7240
 Rockville, MD 20850-6667 Mobile (413)-427-5334
 
 
 
 This is a known problem which has not as yet been fixed. Basicly, 
 p5-test-tester (and p5-test-use-ok) have been integrated into p5-test-simple 
 and are no longer
 required to build any port. See https://trac.macports.org/ticket/46300.
 
 To work around this:
 
  1) make sure your ports are up-to-date
sudo port selfupdate
  2) uninstall/deactivate p5.*-test-tester and p5.*-test-use-ok
sudo port -f uninstall p5.*-test-tester and installed
sudo port -f uninstall p5.*-test-use-ok and installed
  3) clean and upgrade p5*-test-simple
sudo port clean p5*-test-simple
sudo port upgrade p5.20-test-simple
 
 I believe this should work for you
 
 Dave
 
 

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334





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


Re: How upgrade p5.20-test, p5.20-module-build

2014-12-22 Thread David Evans

On 12/22/14 1:43 PM, Murray Eisenberg wrote:

What about p5.*-test-output and p5.*-module-build, which seem to be giving 
similar errors on trying to upgrade?



p5-test-output depends (now) on p5-test-simple, so once you have 
p5-test-simple upgraded you should be

able first clean, then upgrade p5-test-output.

p5-module-build is a different case that needs to be fixed as well.

Here p5-inc-latest (which was previously part of p5-module-build) has 
been removed from p5-module-build and
made a separate port on it's own (which the new p5-module-build now 
depends on).


To work around this case, deactivate p5-module-build first, then upgrade it.

sudo port deactivate p5*-module-build and active
sudo port upgrade p5*-module-build and installed

Sorry for the confusion.  I'm working this afternoon on fixes that will 
make these upgrades more transparent.


Let me know if you have any further problems (or if you don't for that 
matter).

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


Re: How upgrade p5.20-test, p5.20-module-build

2014-12-22 Thread Murray Eisenberg
Thanks, but ouch! I tried the first step,

  sudo port deactivate p5*-module-build and active

but I got lots of additional errors:

$ sudo port deactivate p5*-module-build and active
---  Deactivating p5.16-module-build @0.421.0_1
---  Unable to deactivate p5.16-module-build @0.421.0_1, the following ports 
depend on it:
---p5.16-module-runtime @0.14.0_1
---p5.16-params-validate @1.130.0_0
---p5.16-datetime-locale @0.450.0_4
---p5.16-test-exception @0.350.0_0
---p5.16-datetime @1.120.0_0
Error: org.macports.deactivate for port p5.16-module-build returned: Please 
uninstall the ports that depend on p5.16-module-build first.
Please see the log file for port p5.16-module-build for details:

/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_p5.16-module-build-0.421.0_1_3ec8e763eeefee6c70586d7dd1ca02089ebf80787d1bfc0da1f68830b5840348-2199/p5.16-module-build/main.log
Warning: Failed to execute portfile from registry for p5.16-module-build 
@0.421.0_1
---  Deactivating p5.16-module-build @0.421.0_1
---  Unable to deactivate p5.16-module-build @0.421.0_1, the following ports 
depend on it:
---p5.16-module-runtime @0.14.0_1
---p5.16-params-validate @1.130.0_0
---p5.16-datetime-locale @0.450.0_4
---p5.16-test-exception @0.350.0_0
---p5.16-datetime @1.120.0_0
Error: port deactivate failed: Please uninstall the ports that depend on 
p5.16-module-build first.

This is the kind of morass I was referring to!

And thanks in advance for working on a fix. Meanwhile, anything I can do to 
finesse this?


On 22 Dec2014, at 5:08 PM, David Evans dev...@macports.org wrote:

 On 12/22/14 1:43 PM, Murray Eisenberg wrote:
 What about p5.*-test-output and p5.*-module-build, which seem to be giving 
 similar errors on trying to upgrade?
 
 
 
 p5-test-output depends (now) on p5-test-simple, so once you have 
 p5-test-simple upgraded you should be
 able first clean, then upgrade p5-test-output.
 
 p5-module-build is a different case that needs to be fixed as well.
 
 Here p5-inc-latest (which was previously part of p5-module-build) has been 
 removed from p5-module-build and
 made a separate port on it's own (which the new p5-module-build now depends 
 on).
 
 To work around this case, deactivate p5-module-build first, then upgrade it.
 
sudo port deactivate p5*-module-build and active
sudo port upgrade p5*-module-build and installed
 
 Sorry for the confusion.  I'm working this afternoon on fixes that will make 
 these upgrades more transparent.
 
 Let me know if you have any further problems (or if you don't for that 
 matter).

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334





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


Re: How upgrade p5.20-test, p5.20-module-build

2014-12-22 Thread David Evans

On 12/22/14 2:12 PM, Murray Eisenberg wrote:

Thanks, but ouch! I tried the first step,

   sudo port deactivate p5*-module-build and active

but I got lots of additional errors:

$ sudo port deactivate p5*-module-build and active
---  Deactivating p5.16-module-build @0.421.0_1
---  Unable to deactivate p5.16-module-build @0.421.0_1, the following ports 
depend on it:
--- p5.16-module-runtime @0.14.0_1
--- p5.16-params-validate @1.130.0_0
--- p5.16-datetime-locale @0.450.0_4
--- p5.16-test-exception @0.350.0_0
--- p5.16-datetime @1.120.0_0
Error: org.macports.deactivate for port p5.16-module-build returned: Please 
uninstall the ports that depend on p5.16-module-build first.
Please see the log file for port p5.16-module-build for details:
 
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_p5.16-module-build-0.421.0_1_3ec8e763eeefee6c70586d7dd1ca02089ebf80787d1bfc0da1f68830b5840348-2199/p5.16-module-build/main.log
Warning: Failed to execute portfile from registry for p5.16-module-build 
@0.421.0_1
---  Deactivating p5.16-module-build @0.421.0_1
---  Unable to deactivate p5.16-module-build @0.421.0_1, the following ports 
depend on it:
--- p5.16-module-runtime @0.14.0_1
--- p5.16-params-validate @1.130.0_0
--- p5.16-datetime-locale @0.450.0_4
--- p5.16-test-exception @0.350.0_0
--- p5.16-datetime @1.120.0_0
Error: port deactivate failed: Please uninstall the ports that depend on 
p5.16-module-build first.

This is the kind of morass I was referring to!

And thanks in advance for working on a fix. Meanwhile, anything I can do to 
finesse this?



Be assertive! :-)

sudo port -f deactivate p5*-module-build and active

Dave



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