Re: Migration Assistant moved MacPorts home directories

[db]

On 2 Mar 2017, at 01:21, Brandon Allbery  wrote:
> In fact only one change is needed: you do some of the early steps on the 
> origin system instead of all of it on the destination. I've used an adjusted 
> version of that a few times to do migrations, including with Apple's 
> Migration Assistant in play.

Could you elaborate?

Re: Migration Assistant moved MacPorts home directories

[Rainer Müller]

On 2017-03-02 00:34, Brandon Allbery wrote:
> 
> On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt  > wrote:
> 
> I'm not talking about an unusual case. I'm talking about the
> completely normal case that I expect all users will undergo when
> moving to a new computer: complete the setup assistant and use it to
> transfer data from their old computer. If they accept the defaults
> of that operation, as I did, they are left in the situation I am now
> left in.
> 
> 
> But there's not a lot that MacPorts can do about Apple's defaults, and
> after the fact it's a bit difficult to try to undo the damage it does.

Of course we cannot change the Migration Assistant itself.

However, this observation probably means we are not using the right
naming convention or flags to exclude these accounts from a migration to
a new machine...

Rainer

Re: Migration Assistant moved MacPorts home directories

[mf2k]

> On Mar 1, 2017, at 5:26 PM, Bradley Giesbrecht  wrote:
> 
>> On Mar 1, 2017, at 4:13 PM, Ryan Schmidt  wrote:
>> I'm just unclear why I'm the first to report this problem. Has nobody used 
>> migration assistant? Or has everybody just ended up with broken 
>> installations and either not realized or not bothered to report it?
> 
> I have used migration assistant with the approach I mentioned, I migrated 
> only my “home” account and followed the MacPorts migration instructions. If I 
> ended up with broken ports I yet to notice. Perhaps we could register the 
> accounts port creates along with file permissions and provide “fix 
> permissions” functionality similar to Disk Utility.

I have used the Migration Assistant many times. I too only ever migrate the 
real user account(s) I am interested in. I do not migrate those system level 
accounts. 

I then re-install Macports from scratch when moving to a new machine. I install 
the ports I actually want as I need them. So I would not use the migration 
instructions for this case. I also normally re-install all non-Macports 
applications on a new machine and do not try to migrate them. 


Cheers!
Frank

Re: path to sources.conf?

[Bill Christensen]

Thanks y'all.

On 2/28/17 9:49 PM, Joshua Root wrote:

Dave Horsfall wrote:

On Tue, 28 Feb 2017, Ryan Williamson via macports-users wrote:


Try "sudo find / -name sources.conf"


Or better still, use the "locate" command (and run locate.updatedb every
so often).


As of 2.4.0 we have some shiny new documentation. You can now simply 
run 'man sources.conf' (or 'port help sources.conf') to find the 
desired information, in the FILES section near the end.


- Josh




--
Bill Christensen
http://SustainableSources.com
http://LinkedIn.com/in/billc108

Re: Migration Assistant moved MacPorts home directories

[Ryan Schmidt]

> On Mar 2, 2017, at 08:52, m...@macports.org wrote:
> 
> 
>> On Mar 1, 2017, at 5:26 PM, Bradley Giesbrecht  wrote:
>> 
>>> On Mar 1, 2017, at 4:13 PM, Ryan Schmidt  wrote:
>>> I'm just unclear why I'm the first to report this problem. Has nobody used 
>>> migration assistant? Or has everybody just ended up with broken 
>>> installations and either not realized or not bothered to report it?
>> 
>> I have used migration assistant with the approach I mentioned, I migrated 
>> only my “home” account and followed the MacPorts migration instructions. If 
>> I ended up with broken ports I yet to notice. Perhaps we could register the 
>> accounts port creates along with file permissions and provide “fix 
>> permissions” functionality similar to Disk Utility.
> 
> I have used the Migration Assistant many times. I too only ever migrate the 
> real user account(s) I am interested in. I do not migrate those system level 
> accounts. 

I guess that answers one of my questions: By unchecking those checkboxes next 
to those accounts/directories, you're saying that neither the account nor its 
home directory get migrated?

Did you verify whether any of those accounts owned any other files -- logfiles, 
directories, for example -- and what happened to them after you reinstalled 
those ports on the new system, presumably resulting in those accounts now 
having different ids?

Re: Migration Assistant moved MacPorts home directories

[Ryan Schmidt]

> On Mar 2, 2017, at 08:02, Rainer Müller  wrote:
> 
> On 2017-03-02 00:34, Brandon Allbery wrote:
>> 
>> On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt > > wrote:
>> 
>>I'm not talking about an unusual case. I'm talking about the
>>completely normal case that I expect all users will undergo when
>>moving to a new computer: complete the setup assistant and use it to
>>transfer data from their old computer. If they accept the defaults
>>of that operation, as I did, they are left in the situation I am now
>>left in.
>> 
>> 
>> But there's not a lot that MacPorts can do about Apple's defaults, and
>> after the fact it's a bit difficult to try to undo the damage it does.
> 
> Of course we cannot change the Migration Assistant itself.
> 
> However, this observation probably means we are not using the right
> naming convention or flags to exclude these accounts from a migration to
> a new machine...

My guess is that the migration assistant knows that user ids under 500 are 
system accounts and should not be presented. I don't know how it handles system 
accounts... (Whether it migrates or discards the contents of their home 
directories.)