[MacPorts] #30302: port selfupdate to 2.0 incomplete (archives in var/macports/software)

[MacPorts]

#30302: port selfupdate to 2.0 incomplete (archives in var/macports/software)
--------------------------------+-------------------------------------------
 Reporter:  bgschaid@…          |       Owner:  macports-tickets@…                   
     Type:  defect              |      Status:  new                                  
 Priority:  Normal              |   Milestone:                                       
Component:  ports               |     Version:  2.0.0                                
 Keywords:                      |        Port:                                       
--------------------------------+-------------------------------------------
 Hi

 Today I pressed selfupdate in Porticus. Wasn't aware that this would do a
 major upgrade to 2.0. Otherwise I would have taken precautions.

 During the update the machine ran out of discspace. I freed some space and
 the script kept running. Afterwards porticus said that the selfupdate
 failed but offered no further explanation.

 The next selfupdate (from the command line) said that everything is in
 order. All the utilities that were installed run as expected. Only I do
 have significantly less discspace (the cause of the initial failure I
 guess).

 What seems odd to me is that in /opt/local/var/macports/software there is
 a directory for every installed package with a tbz2-archive with all the
 files of that package in it.

 According to
 http://guide.macports.org/#internals.hierarchy
 it should be a bunch of files which are hardlinked to the installation
 places.

 My theory (but you'll know better) is that to prepare the upgrade these
 archives were created. During that phase the machine ran out of disc-
 space. The other archives were created (I saw as much in top). But the
 next stage (I guess unpacking the archives again) was never started
 because some archives failed and now my installation is in limbo.

 Is that so? Or is this the new directory structure and I'll have to live
 with the extra discspace for the archives)

 Is there anything I can do about it (except scratching the whole MacPorts
 installation and recompiling everything)?

 I'd suggest that for the next major upgrade selfupdate fails if there is
 not an extra option specified (--force-major-update or so). That would
 make people aware that this is not an update like every other and allow
 them to take precautions

 Bernhard

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