Re: updating a very old Macports install
Ok I have followed the directions, everything goes along fine for a bit, then I get a registry lock error and have to manually instal the problem package, it does not do it to every package, but I have to babysit it. I also have to comment to package out of the package list to prevent the exclusive registry lick error. Any suggestions or ideas? Thanks in advance for your time and assistance! Cheers, Bruce... On Feb 11, 2015, at 15:55, Ryan Schmidt ryandes...@macports.org wrote: On Feb 11, 2015, at 15:32, Bruce J. Carter wrote: I need some suggestions or ideas, I've been trying upgrade a Macports install that's at least 3 years old, there has been two OS upgrades in between (Mavericks Yosemite). I get to a certain point and I get errors. Some errors I've been able to over come, but I am stuck at this point, I have a bunch of built ports that won't install that are inactive. I am trying to avoid cleaning and reinstalling everything. We typically leave port upgrade paths in place for one year, so you should upgrade your ports at least that often, and hopefully much more frequently. Base upgrade paths stay in place for years. The upgrade process when you change the OS X version is to uninstall MacPorts and all ports, then reinstall: https://trac.macports.org/wiki/Migration If that's what you're trying to do and you're running into problems, let us know what they are. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
Absolutely! The only thing that changes is the package name. See below: expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing registry::exclusive_lock (procedure mportexec line 32) invoked from within mportexec $workername $install_target Unable to execute target 'install' for port 'gdbm': expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing install_ports $operationList (file ./restore_ports.tcl line 294) Cheers, Bruce... On Fri, Feb 13, 2015 at 4:19 PM, Ryan Schmidt ryandes...@macports.org wrote: On Feb 13, 2015, at 12:48 PM, Bruce J. Carter wrote: Ok I have followed the directions, everything goes along fine for a bit, then I get a registry lock error and have to manually instal the problem package, it does not do it to every package, but I have to babysit it. I also have to comment to package out of the package list to prevent the exclusive registry lick error. I'm not familiar with this. Could you show us exactly what error you get? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
On Feb 13, 2015, at 12:48 PM, Bruce J. Carter wrote: Ok I have followed the directions, everything goes along fine for a bit, then I get a registry lock error and have to manually instal the problem package, it does not do it to every package, but I have to babysit it. I also have to comment to package out of the package list to prevent the exclusive registry lick error. I'm not familiar with this. Could you show us exactly what error you get? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
sudo ./restore_ports.tcl myports.txt On Fri, Feb 13, 2015 at 6:11 PM, Ryan Schmidt ryandes...@macports.org wrote: On Feb 13, 2015, at 5:02 PM, Bruce J. Carter wrote: Absolutely! The only thing that changes is the package name. See below: expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing registry::exclusive_lock (procedure mportexec line 32) invoked from within mportexec $workername $install_target Unable to execute target 'install' for port 'gdbm': expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing install_ports $operationList (file ./restore_ports.tcl line 294) Ok, and what command were you running when you got this message? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
On Feb 13, 2015, at 5:02 PM, Bruce J. Carter wrote: Absolutely! The only thing that changes is the package name. See below: expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing registry::exclusive_lock (procedure mportexec line 32) invoked from within mportexec $workername $install_target Unable to execute target 'install' for port 'gdbm': expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing install_ports $operationList (file ./restore_ports.tcl line 294) Ok, and what command were you running when you got this message? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
On Feb 13, 2015, at 9:21 PM, Joshua Root wrote: See below: expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing registry::exclusive_lock (procedure mportexec line 32) You appear to be running trunk. You could take this opportunity to go back to a released version of base; or you could just accept this aspect of living on trunk. :) Could you elaborate? Are you saying he was running an old version of trunk before the update, or that he is running the current version of trunk now? Why does this error occur, and is it something that's going to happen for some stable-to-stable updates in the future, or is it only a problem with trunk that will be (or was) fixed before release? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
On 2015-2-14 15:01 , Ryan Schmidt wrote: On Feb 13, 2015, at 9:21 PM, Joshua Root wrote: See below: expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing registry::exclusive_lock (procedure mportexec line 32) You appear to be running trunk. You could take this opportunity to go back to a released version of base; or you could just accept this aspect of living on trunk. :) Could you elaborate? Are you saying he was running an old version of trunk before the update, or that he is running the current version of trunk now? Why does this error occur, and is it something that's going to happen for some stable-to-stable updates in the future, or is it only a problem with trunk that will be (or was) fixed before release? Current problem for trunk only. Has to do with having two flock implementations. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
updating a very old Macports install
See below: expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing registry::exclusive_lock (procedure mportexec line 32) You appear to be running trunk. You could take this opportunity to go back to a released version of base; or you could just accept this aspect of living on trunk. :) - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
Ok... I succumbed, I went to /opt/local and did an rm -rf * and reinstalled the Macports package for Yosemite... no issues... I learned something for years I have always used the trunk, now I know why I have had to troubleshoot port builds from time to time and massage them into installing. I must congratulate and thank y'all for the awesome work you have done on MacPorts and the ports tree. Cheers, Bruce... On Fri, Feb 13, 2015 at 9:21 PM, Joshua Root j...@macports.org wrote: See below: expected integer but got -exclusive obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing registry::exclusive_lock (procedure mportexec line 32) You appear to be running trunk. You could take this opportunity to go back to a released version of base; or you could just accept this aspect of living on trunk. :) - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
updating a very old Macports install
I need some suggestions or ideas, I've been trying upgrade a Macports install that's at least 3 years old, there has been two OS upgrades in between (Mavericks Yosemite). I get to a certain point and I get errors. Some errors I've been able to over come, but I am stuck at this point, I have a bunch of built ports that won't install that are inactive. I am trying to avoid cleaning and reinstalling everything. Any thoughts, ideas or suggestions? Cheers, Bruce... ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
On Feb 11, 2015, at 15:32, Bruce J. Carter wrote: I need some suggestions or ideas, I've been trying upgrade a Macports install that's at least 3 years old, there has been two OS upgrades in between (Mavericks Yosemite). I get to a certain point and I get errors. Some errors I've been able to over come, but I am stuck at this point, I have a bunch of built ports that won't install that are inactive. I am trying to avoid cleaning and reinstalling everything. We typically leave port upgrade paths in place for one year, so you should upgrade your ports at least that often, and hopefully much more frequently. Base upgrade paths stay in place for years. The upgrade process when you change the OS X version is to uninstall MacPorts and all ports, then reinstall: https://trac.macports.org/wiki/Migration If that's what you're trying to do and you're running into problems, let us know what they are. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
On Feb 11, 2015, at 4:32 PM, Bruce J. Carter cerf...@gmail.com wrote: I am trying to avoid cleaning and reinstalling everything. why? you probably want/need to do that if only because you should after an OS upgrade. Any thoughts, ideas or suggestions? https://trac.macports.org/wiki/Migration -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
I am trying to avoid cleaning and reinstalling everything. Any thoughts, ideas or suggestions? Yea, clean and re-install everything. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
On Wed, February 11, 2015 21:32, Bruce J. Carter wrote: I need some suggestions or ideas, I've been trying upgrade a Macports install that's at least 3 years old, there has been two OS upgrades in between (Mavericks Yosemite). I get to a certain point and I get errors. Some errors I've been able to over come, but I am stuck at this point, I have a bunch of built ports that won't install that are inactive. I am trying to avoid cleaning and reinstalling everything. But that's precisely what you should do... https://trac.macports.org/wiki/Migration ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: updating a very old Macports install
OK, I guess that answers that question. Not the answer I was hoping to hear, but I can live with that. Thanks for the help! Can't wait to get everything back up and running. Cheers, Bruce... On Feb 11, 2015, at 15:55, Ryan Schmidt ryandes...@macports.org wrote: On Feb 11, 2015, at 15:32, Bruce J. Carter wrote: I need some suggestions or ideas, I've been trying upgrade a Macports install that's at least 3 years old, there has been two OS upgrades in between (Mavericks Yosemite). I get to a certain point and I get errors. Some errors I've been able to over come, but I am stuck at this point, I have a bunch of built ports that won't install that are inactive. I am trying to avoid cleaning and reinstalling everything. We typically leave port upgrade paths in place for one year, so you should upgrade your ports at least that often, and hopefully much more frequently. Base upgrade paths stay in place for years. The upgrade process when you change the OS X version is to uninstall MacPorts and all ports, then reinstall: https://trac.macports.org/wiki/Migration If that's what you're trying to do and you're running into problems, let us know what they are. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
