update problems

[Pete Crite]

Hi, I attempted to run "sudo port upgrade outdated" today, and got a  
whole bunch of errors similar to this:

> --->  Verifying checksum(s) for libpng
> Error: No checksum set for libpng-1.2.33.tar.bz2

but also for different ports, e.g.:

> Error: No checksum set for pango-1.22.2.tar.bz2
> Error: No checksum set for libxml2-2.7.2.tar.gz
> Error: No checksum set for autoconf-2.63.tar.bz2
> Error: No checksum set for libgsf-1.14.10.tar.bz2
> Error: No checksum set for numpy-1.2.1.tar.gz
> Error: No checksum set for pycairo-1.6.4.tar.gz
> Error: No checksum set for coreutils-6.12.tar.gz
> Error: No checksum set for gnome-themes-2.24.1.tar.bz2

I googled, and found something about using "sudo port clean --all  
sqlite3", and then running the upgrades again. https://trac.macports.org/ticket/16486 
  This worked partially; I still had many errors, but sometimes a port  
might upgrade. On closer examination of the terminal messages, I found  
recursive directories mentioned, similar to the ticket mentioned.

> --->  Verifying checksum(s) for pango
> Error: Target org.macports.checksum returned: Could not open file: / 
> opt/local/var/macports/distfiles/pango/pango/pango-1.22.2.tar.bz2
> Error: Unable to upgrade port: 1

There was a related local file at /opt/local/var/macports/distfiles/ 
pango/pango/pango/pango/pango/pango/pango/pango-1.22.2.tar.bz2 (N.B.  
different amount of nested folders)

It seems that macports was putting the downloaded file in a subfolder  
of the /opt/local/var/macports/distfiles/port_name/ folder? Even for  
the ports that worked eventually, they were nested in a subfolder. I  
tried running the upgrade command a few more times. Most of the ports  
upgraded, but not two (coreutils and nautilus). I actually just moved  
these files from their sub-directories into the proper directory, and  
the update for these worked fine now.

So, I have three questions:
1) Is there a way to upgrade these final two ports?
2) Is there a problem with this strange recursive directory structure?  
Is there a way to fix it, or is the manual way I did it fine?
3) Is there a way to prevent this in the future?
4) I also tried to run "sudo port clean --all" but got an error:

> Can't map the URL 'file://.' to a port description file ("Could not  
> find Portfile in /Users/foo_bar").
> Please verify that the directory and portfile syntax are correct.
> To use the current port, you must be in a port's directory.
> (you might also see this message if a pseudo-port such as
> outdated or installed expands to no ports).
> Error: Unable to open port: Could not find Portfile in /Users/foo_bar

Has this command changed?


Cheers,
Pete.