[MacPorts] #29223: if an install is interrupted, a later install of the same package can fail if version number has since changed.

MacPorts noreply at macports.org
Wed Apr 20 22:42:27 PDT 2011


#29223: if an install is interrupted, a later install of the same package can fail
if version number has since changed.
----------------------------------+-----------------------------------------
 Reporter:  rogerdpack@…          |       Owner:  macports-tickets@…                   
     Type:  defect                |      Status:  new                                  
 Priority:  Normal                |   Milestone:                                       
Component:  ports                 |     Version:  1.9.2                                
 Keywords:                        |        Port:                                       
----------------------------------+-----------------------------------------
Description changed by ryandesign@…:

Old description:

> kind of explained here:
>
> https://gist.github.com/raw/933741/93ded0007937f70df19aeb3d77f523a9dbd5639c/gistfile1.txt
>
> What happened is I did a $ sudo port install mplayer
> one day.  I think I did a control+c to cancel it sometime in the middle.
> Next day, I did
> $ sudo port install mplayer
> again.
>
> m4 is a dependency of mplayer.
> With the first one, the m4 install was interrupted.
> Now, however, you can see from the gist that it was saying
> ":debug:main Skipping completed org.macports.fetch (m4)"
>
> then attempting to build from:
>
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_m4/work/m4-1.4.16
>
> $ ls
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_m4/work/
> .CC_PRINT_OPTIONS   .macports.m4.state  m4-1.4.15/
>
> So basically it appears to be skipping the fetch phase because 1.4.15 had
> already been fetched (and unpacked), then trying to go ahead and build
> 1.4.16, which of course fails.
> Less than ideal, wouldn't you agree?
>
> 10.6.7, xcode 3.2.6
> Thanks.
> -r

New description:

 kind of explained here:

 https://gist.github.com/raw/933741/93ded0007937f70df19aeb3d77f523a9dbd5639c/gistfile1.txt

 What happened is I did a $ sudo port install mplayer
 one day.  I think I did a control+c to cancel it sometime in the middle.
 Next day, I did
 {{{
 $ sudo port install mplayer
 }}}
 again.

 m4 is a dependency of mplayer.
 With the first one, the m4 install was interrupted.
 Now, however, you can see from the gist that it was saying
 {{{
 :debug:main Skipping completed org.macports.fetch (m4)
 }}}

 then attempting to build from:

 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_m4/work/m4-1.4.16

 {{{
 $ ls
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_m4/work/
 .CC_PRINT_OPTIONS   .macports.m4.state  m4-1.4.15/
 }}}

 So basically it appears to be skipping the fetch phase because 1.4.15 had
 already been fetched (and unpacked), then trying to go ahead and build
 1.4.16, which of course fails.
 Less than ideal, wouldn't you agree?

 10.6.7, xcode 3.2.6
 Thanks.
 -r

--

-- 
Ticket URL: <https://trac.macports.org/ticket/29223#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list