[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-dev
Subject:    Re: [GSoC] migration
From:       Umesh Singla <umeshksingla () macports ! org>
Date:       2017-09-09 0:16:54
Message-ID: CAK2-mZHoE=qk8p=3wCHwdtgQKHwL_9xDkRBiMRyaCDcSf_jU1A () mail ! gmail ! com
[Download RAW message or body]

On Sat, Sep 9, 2017 at 3:40 AM, Rainer M=C3=BCller <raimue@macports.org> wr=
ote:

> On 2017-09-08 23:33, Umesh Singla wrote:
> > When I run the `migrate` action with only one port (expat) installed, I
> > get the following:
> >
> > $ sudo ./bin/port migrate
> >
> > Taking a snapshot of the current state...
> >
> > Done: Snapshot '8':'snapshot created for migration' created at
> > 2017-09-08 21:09:21
> >
> > Migration will first uninstall all the installed ports, upgrade MacPort=
s
> > and then reinstall them again. Would you like to continue? [Y/n]: Y
>
> I would like to repeat that upgrading MacPorts from the 'port migrate'
> action is not possible. After a major upgrade of macOS we cannot
> guarantee that the old version of MacPorts runs at all on this new OS
> version. MacPorts has to be reinstalled for the new OS version in an
> extra step before.
>
> The best you can do is printing instructions on where to download MacPort=
s.


So, what could be the possible two-stage break of migrate action be? I'm
guessing immediately after uninstalling and selfupdating, I can print on
the console asking the user to run `port restore --last` in order to
complete migration. This command will now use the upgraded port command.
Any suggestions?

- Umesh

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Sep 9, 2017 \
at 3:40 AM, Rainer Müller <span dir="ltr">&lt;<a href="mailto:raimue@macports.org" \
target="_blank">raimue@macports.org</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 2017-09-08 23:33, Umesh Singla wrote:<br> \
&gt; When I run the `migrate` action with only  one port (expat) installed, I<br> \
&gt; get the following:<br> &gt;<br>
&gt; $ sudo ./bin/port migrate<br>
&gt;<br>
&gt; Taking a snapshot of the current state...<br>
&gt;<br>
&gt; Done: Snapshot &#39;8&#39;:&#39;snapshot created for migration&#39; created \
at<br> &gt; 2017-09-08 21:09:21<br>
&gt;<br>
&gt; Migration will first uninstall all the installed ports, upgrade MacPorts<br>
&gt; and then reinstall them again. Would you like to continue? [Y/n]: Y<br>
<br>
</span>I would like to repeat that upgrading MacPorts from the &#39;port \
migrate&#39;<br> action is not possible. After a major upgrade of macOS we cannot<br>
guarantee that the old version of MacPorts runs at all on this new OS<br>
version. MacPorts has to be reinstalled for the new OS version in an<br>
extra step before.<br>
<br>
The best you can do is printing instructions on where to download \
MacPorts.</blockquote><div><br></div><div>So, what could be the possible two-stage \
break of migrate action be? I&#39;m guessing immediately after uninstalling and \
selfupdating, I can print on the console asking the user to run `port restore --last` \
in order to complete migration. This command will now use the upgraded port command. \
Any suggestions?</div></div><br></div><div class="gmail_extra">- Umesh</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]