Re: help on restore

2019-01-27 Thread Ryan Schmidt



On Jan 27, 2019, at 14:02, Comer Duncan wrote:

> Well it crapped out just the same way after I removed all +universal 
> instances in my ports list.  Am I now looking at putting back my original 
> ports by hand?

Hopefully that's not required. However I'm not sure what to try next. Maybe 
someone else can help.

Some problems with the restore process have been posted to the mailing list 
before. Maybe you can find those messages in the archive; maybe they contain 
helpful suggestions.

It could be there's a problem with the dependency chain of one of the ports 
(such as a circular dependency, which isn't allowed) which was introduced 
sometime after you last updated your ports. I see you last updated in 
September, so that's quite a long time -- quite a lot of changes to the ports 
tree in that time -- so it's tough to say at this moment if that's likely to be 
the reason.

Migration time can be an opportunity to streamline your set of installed ports. 
Instead of reinstalling all the ports you had installed, you could just 
reinstall the ports you actually need. (If you followed the optional steps of 
the migration instructions, that list of ports would be in requested.txt.) That 
may take less time, and may coincidentally resolve whatever issue is preventing 
the full set from being installed.




Re: help on restore

2019-01-27 Thread Chris Jones
Hi,

Personally, I think this is anyway a better approach. I never follow the 
migration instructions word for word. I create the lists of all ports and 
requested ports, but instead of just blindly reinstalling them all, I manually 
reinstall those I want via the requested list. It is usually not that long a 
list. The reason I do this is default variants and deps can and do change over 
time, and can be different for different OS versions. So just blindly 
reinstalling them as as per the old OS often just does not work.

So, yes, I recommend you just manually reinstall them one by want, using the 
default variants as of now, unless there are some explicit changes you need.

Chris

> On 27 Jan 2019, at 8:02 pm, Comer Duncan  wrote:
> 
> Ryan,
> 
> Well it crapped out just the same way after I removed all +universal 
> instances in my ports list.  Am I now looking at putting back my original 
> ports by hand?
> 
> Thanks.
> 
> Comer



Re: help on restore

2019-01-27 Thread Ryan Schmidt



On Jan 27, 2019, at 13:30, Comer Duncan wrote:

> Well it failed with the same message as before. I'm attaching my myports.txt. 
>  I've changed the sources.conf file in the way you suggested. I'm attaching 
> it as well.

Hmm. Well, you should definitely remove "+universal" everywhere it appears in 
that file. Universal building is not supported on Mojave or later.


> By the way, my gmail does not recognize lists.macports.org as a legit 
> address!  What gives?

Not sure. https://lists.macports.org is a valid web site and 
macports-users@lists.macports.org is a valid email address.



Re: help on restore

2019-01-27 Thread Ryan Schmidt
On Jan 27, 2019, at 13:05, Comer Duncan wrote:

> Hi Ryan,
> 
> I'm attaching the existing sources.conf file that's on my system.  Seems a 
> bit pecular and I don't know how long the line
> rsync://rsync.macports.org/release/tarballs/ports.tar
> has been there!  Can you suggest a nifty change?  

There needs to be exactly one non-commented line that ends with " [default]"; 
your config file has none.

Also, please change the URL to 
rsync://rsync.macports.org/macports/release/tarballs/ports.tar -- while the old 
URL still works, it is deprecated and we are trying to phase it out.

P.S: Remember to Reply All so that the conversation stays on the mailing list.



Re: help on restore

2019-01-27 Thread Ryan Schmidt



On Jan 27, 2019, at 12:37, Comer Duncan wrote:

> I've followed the steps on the macports page 
> https://trac.macports.org/wiki/Migration under Reinstall Ports.  When I 
> execute sudo ./restore_ports.tcl myports.txt after a few seconds I get the 
> output:
> 
> ComerMacProRetina:~ comerduncan$ sudo ./restore_ports.tcl myports.txt
> Password:
> Warning: No default port source specified in 
> /opt/local/etc/macports/sources.conf, using last source as default
> Error: we appear to be stuck, exiting...
> infinite loop
> while executing
> "sort_ports $portList"
> invoked from within
> "set operationList [sort_ports $portList]"
> (file "./restore_ports.tcl" line 285)
> 
> Can someone please advise on what to do next to find out what is wrong?  I'm 
> migrating to Mohave from High Sierra.

My first question would be: what's in sources.conf?

P.S: Please use the lists.macports.org hostname when addressing your mailing 
list messages. The old hostname you used was retired in 2016. Mail to the old 
hostname forwards to the new one, but some users cannot see those forwarded 
messages because of restrictions imposed by their email providers.