update problems

[Bryan Blackburn]

On Wed, Nov 05, 2008 at 12:24:13PM +1100, Pete Crite said:
> Thanks for your help
>
> I ran "sudo port clean --all <port_name>", and this seemed to delete the 
> relevant port file(s) and directory from /opt/local/var/macports/ 
> distfiles
>
> Is that what it is supposed to do? Just curious, since the "clean" stage 
> during a normal install doesn't delete these files in the distfiles 
> directory...

Right, just 'port clean <portname>' will remove the work area (which is
where port performs the actual build).  Using --dist just deletes the
distfiles (usually the source tarballs), and --archive removes the packaged
archive (if you have archiving enabled).  --all does all of those, so with
it you should end up with no trace of work from port, except the actual
installed port if it was installed.  'man port' should have a bit more
detail on this, search for clean.

Bryan


>
> Cheers.
>
>
> On 05/11/2008, at 7:12 AM, Bryan Blackburn wrote:
>
>>
>> On Tue, Nov 04, 2008 at 11:09:38PM +1100, Pete Crite said:
>>> 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
>> [...]
>>>
>>> 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.
>>
>> The good news is that this should be fixed in the next MacPorts  
>> release,
>> though for now, unfortunately, you'll have to do a clean of any port  
>> that
>> hits this issue.
>>
>> [...]
>>>
>>> So, I have three questions:
>>> 1) Is there a way to upgrade these final two ports?
>>
>> Did you run the clean --all for each of those ports having issues?
>>
>>> 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?
>>
>> There was (and still is on MacPorts 1.6) but should be fixed according 
>> to
>> ticket #11971.  Normally, the distfile should end up in
>> ${prefix}/var/macports/distfiles/${portname} so just the one level of a
>> given port's name should be used there.
>>
>>> 3) Is there a way to prevent this in the future?
>>
>> Upgrade to MacPorts 1.7 when it is available, otherwise it would seem 
>> that
>> having to clean should get things to work for the moment.
>>
>>> 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
>>
>> Yeah, that needs a port name given, this error message is also improved 
>> in
>> the next release; 'sudo port clean --all <portname>' is the proper  
>> form.
>>
>> Bryan
>>
>>
>>>
>>> Has this command changed?
>>>
>>>
>>> Cheers,
>>> Pete.
>>
>