On Thu, Mar 20, 2008 at 6:42 PM, <macports-users-request@lists.macosforge.org> wrote:

Send macports-users mailing list submissions to
       macports-users@lists.macosforge.org

To subscribe or unsubscribe via the World Wide Web, visit
       http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
or, via email, send a message with subject or body 'help' to
       macports-users-request@lists.macosforge.org

You can reach the person managing the list at
       macports-users-owner@lists.macosforge.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of macports-users digest..."


Today's Topics:

  1. Re: how to delete deactivated ports (Ryan Schmidt)
  2. Re: deactivated port issue (Ryan Schmidt)
  3. Re: deactivated port issue (Ryan Schmidt)
  4. Re: ntop fials to build (David L Ballenger)
  5. Re: deactivated port issue (Mark Wilden)
  6. Re: deactivated port issue (Rainer M?ller)
  7. Re: ntop fials to build (Shawn Protsman)


----------------------------------------------------------------------

Message: 1
Date: Thu, 20 Mar 2008 17:17:39 -0500
From: Ryan Schmidt <ryandesign@macports.org>
Subject: Re: how to delete deactivated ports
To: Charlse Darwin <macports.users@gmail.com>
Cc: liste gtk <macports-users@lists.macosforge.org>
Message-ID: <1AAC64B0-C174-46E2-B3B7-25C6E43963E0@macports.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

On Mar 20, 2008, at 07:06, skip@pobox.com wrote:

>     Charlse> I have a shell script that I run when I go to bed called
>     Charlse> good-night and part of it that pertains to Macports
> goes like
>     Charlse> this:
>
>     ...
>
>     Charlse> Your thoughts please.
>
> My only thought would be to wrap the lines suitably:
>
>     #!/opt/local/bin/bash
>
>     cd "~/base/" \
>     && /opt/local/bin/svn update \
>     && PATH=/bin:/sbin:/usr/bin:/usr/sbin ./configure --enable-
> readline \
>     && /usr/bin/make \
>     && /opt/local/bin/sudo /usr/bin/make install \
>     && /usr/bin/make clean \
>     && /opt/local/bin/port -v selfupdate \
>     && /opt/local/bin/port -fvdRnu upgrade outdated \
>     && /opt/local/bin/port -fvdR clean --all installed \
>     && /opt/local/bin/port -fvdR uninstall inactive \
>     && /opt/local/bin/port -fvdR clean --all uninstalled
>
> Now that I can read what you wrote ;-)

I wish you wouldn't indiscriminately use the -f (force) flag all the
time. If it were intended to be used all the time it would have been
made the default. In particular it should only be needed for "port -f
uninstall inactive". It should not be needed for clean, and the only
times it would be needed for upgrade are in unusual situations, which
you would probably want to handle by hand individually rather than
automate.




------------------------------

Message: 2
Date: Thu, 20 Mar 2008 17:30:45 -0500
From: Ryan Schmidt <ryandesign@macports.org>
Subject: Re: deactivated port issue
To: Nehemiah Dacres <vivacarlie@gmail.com>
Cc: Users MacPorts <macports-users@delta.macosforge.org>
Message-ID: <E43D8F57-092B-414F-9326-BDA69E94C924@macports.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

On Mar 20, 2008, at 17:21, Nehemiah Dacres wrote:

> On Thu, Mar 20, 2008 at 5:13 PM, Nehemiah Dacres wrote:
>
>> On Thu, Mar 20, 2008 at 5:09 PM, Ryan Schmidt wrote:
>>
>>> On Mar 20, 2008, at 15:03, Nehemiah Dacres wrote:
>>>
>>> > when i install git core after uninstalling git-core , git-core
>>> > +no_svn  I recieve this error message
>>> >
>>> > --->  Activating git-core 1.5.3.7_0+doc
>>> > Error: Target org.macports.activate returned: Image error: /opt/
>>> > local/lib/perl5/5.8.8/darwin-2level/perllocal.pod already exists
>>> > and does not belong to a registered port.  Unable to activate port
>>> > git-core.
>>> > Error: Status 1 encountered during processing.
>>>
>>> This problem was fixed in r34462 on 2008-02-25. That means your port
>>> definitions are out of date. "sudo port selfupdate" to get the
>>> latest
>>> MacPorts and port definitions. Then "sudo port uninstall git-core
>>> @1.5.3.7_0+doc" and "sudo port install git-core", which will this
>>> time get you the current version which is 1.5.4.4.
>>
>> thanks, sorry it didn't occur to me to do that but im use to the
>> debian modle which requires network access to check the repo
>> everytime you install (so this one is superior)
>
> spoke too soon ..
> MacPorts base version 1.600 installed
>
> Downloaded MacPorts base version 1.600
>
> The MacPorts installation is not outdated and so was not updated
> selfupdate done!

That is correct. MacPorts base was not outdated, therefore MacPorts
base was not updated. However, your port definitions were outdated,
and they were updated, even if it didn't say so. Now try installing
git-core again.




------------------------------

Message: 3
Date: Thu, 20 Mar 2008 17:44:26 -0500
From: Ryan Schmidt <ryandesign@macports.org>
Subject: Re: deactivated port issue
To: "Nehemiah Dacres" <vivacarlie@gmail.com>
Cc: Users MacPorts <macports-users@delta.macosforge.org>
Message-ID: <087AEF15-0F3B-494D-98A1-8284D28EE387@macports.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

On Mar 20, 2008, at 17:40, Nehemiah Dacres wrote:

> On Thu, Mar 20, 2008 at 5:30 PM, Ryan Schmidt wrote:
>
>> On Mar 20, 2008, at 17:21, Nehemiah Dacres wrote:
>>
>> > On Thu, Mar 20, 2008 at 5:13 PM, Nehemiah Dacres wrote:
>> >
>> >> On Thu, Mar 20, 2008 at 5:09 PM, Ryan Schmidt wrote:
>> >>
>> >>> On Mar 20, 2008, at 15:03, Nehemiah Dacres wrote:
>> >>>
>> >>> > when i install git core after uninstalling git-core , git-core
>> >>> > +no_svn  I recieve this error message
>> >>> >
>> >>> > --->  Activating git-core 1.5.3.7_0+doc
>> >>> > Error: Target org.macports.activate returned: Image error: /
>> opt/
>> >>> > local/lib/perl5/5.8.8/darwin-2level/perllocal.pod already
>> exists
>> >>> > and does not belong to a registered port.  Unable to
>> activate port
>> >>> > git-core.
>> >>> > Error: Status 1 encountered during processing.
>> >>>
>> >>> This problem was fixed in r34462 on 2008-02-25. That means
>> your port
>> >>> definitions are out of date. "sudo port selfupdate" to get the
>> >>> latest
>> >>> MacPorts and port definitions. Then "sudo port uninstall git-core
>> >>> @1.5.3.7_0+doc" and "sudo port install git-core", which will this
>> >>> time get you the current version which is 1.5.4.4.
>> >>
>> >> thanks, sorry it didn't occur to me to do that but im use to the
>> >> debian modle which requires network access to check the repo
>> >> everytime you install (so this one is superior)
>> >
>> > spoke too soon ..
>> > MacPorts base version 1.600 installed
>> >
>> > Downloaded MacPorts base version 1.600
>> >
>> > The MacPorts installation is not outdated and so was not updated
>> > selfupdate done!
>>
>> That is correct. MacPorts base was not outdated, therefore MacPorts
>> base was not updated. However, your port definitions were outdated,
>> and they were updated, even if it didn't say so. Now try installing
>> git-core again.
>
> naturlaly i already tried, I should note that I am on a Tiger based
> system. should I use port clean? (how ever one might use that)

Sure, you could try port clean. "sudo port clean --work git-core".
Then try installing again. Manually cleaning shouldn't be necessary
though if the portfile was updated, since MacPorts will see that the
portfile differs and will clean automatically.

Does it try to install 1.5.4.4 now or still 1.5.3.7?

If it still doesn't work, what is the error message?

P.S: Please use Reply All when replying so everybody gets your reply,
not just me. It also helps the flow of conversation if you bottom-
post instead of top-post.