On May 12, 2014, at 10:08, Roberto Avanzi wrote:
> today I installed 2.3.0rc1 (using the pkg) and when I issue the command
>
>> sudo port selfupdate
>
> I get the following message
>
>> ---> Updating MacPorts base sources using rsync
>> MacPorts base version 2.3.0 installed,
>> MacPorts base
At least these two were needed here on my end:
—
$ sudo chmod o+r /opt/local/libexec/macports/lib/tcl8.5/.
$ sudo chmod o+r /opt/local/libexec/macports
—
but it looks like /opt/local/libexec/macports/lib/tcllib1.15
—
drwxr-x--x 111 root admin3774 May 11 16:22 tcllib1.15
—
is another candidate.
On May 12, 2014, at 15:20, Shiyuan wrote:
>
>Macports used to work well on Mac 10.8. After a upgrade to mac 10.9,
> :info:extract sh: /usr/bin/gnutar: No such file or directory
This error message indicates you did not reinstall MacPorts after upgrading to
OS X 10.9, which is required. Ple
Hi
I've been using the 2.3.0 beta releases and now the rc1 release and
I've just noticed that port seems to have forgotten what ports I've
explicitly requested, for example:
$ port installed requested
None of the specified ports are installed.
$
As such "port echo leaves" reports a lot of leaves
When migrating to a new OS, be sure to reinstall MacPorts.
For minimum support of MacPorts, you need the Command Line Tools, which can be
installed using xcode-select --install. If you are installing MacPorts from
source, you will also want to run sudo xcodebuild -license. Note that some
ports
Hi,
Macports used to work well on Mac 10.8. After a upgrade to mac 10.9,
`sudo port upgrade -u outdated` gives errors complaining privilege (but I
do have the `sudo` privilege and it worked well before the mac upgrade) .
The port sync is done via svn. The screenshot and main.log are attached
be
* On 12.05.2014 05:59 pm, Peter Danecek wrote:
> I just realised that `port select gcc` sets /opt/local/bin/c++ ->
> /opt/local/bin/c++-mp-4.8, while there is no corresponding link for `cc`.
Nice catch.
> Would it not be cleaner to either
> - point also cc to `/opt/local/bin/gcc`
I'm in fav
Ok thanks, I'll try that port.
Jamie.
Sent from my iPhone
> On 12 May 2014, at 16:46, "Daniel J. Luke" wrote:
>
>> On May 12, 2014, at 11:39 AM, Jamie Paul Griffin wrote:
>>
>> I've reinstalled Clamav after not using it for a while and I'm wondering
>> about getting it initiated on system
On 2014-5-13 05:01 , Clemens Lang wrote:
> Hi,
>
> Please keep the conversation on the list so others with the same problem
> can follow.
>
>> Yes! The `sandbox_enable no' hack worked around the problem.
>>
>> Can you reproduce the problem by creating a fake package and trying the
>> "test -w /v
Hi Joshua,
when trying to run mpstats submit I met a problem which is caused by the
current RC1.
On 11 May 2014, at 23:44 , Clemens Lang wrote:
> It seems your tcl8.5 directory isn't readable by your user. Which user did
> you use
> to install it? Which umask was set while you installed it? Wh
Hi,
Please keep the conversation on the list so others with the same problem
can follow.
> Yes! The `sandbox_enable no' hack worked around the problem.
>
> Can you reproduce the problem by creating a fake package and trying the
> "test -w /var/tmp"?
Yes, I can reproduce this with a minimal exa
Hi all,
I just realised that `port select gcc` sets /opt/local/bin/c++ ->
/opt/local/bin/c++-mp-4.8, while there is no corresponding link for `cc`.
It might be consistent with the fact that there is always a `c++` binary
installed by the gcc ports and there is no corresponding `cc` binary. Ho
On May 12, 2014, at 11:39 AM, Jamie Paul Griffin wrote:
>
> I've reinstalled Clamav after not using it for a while and I'm wondering
> about getting it initiated on system-startup. I've looked but don't see a
> launchd script like the there used to be.
>
> So I guess my questions are should t
Hi
I've reinstalled Clamav after not using it for a while and I'm wondering about
getting it initiated on system-startup. I've looked but don't see a launchd
script like the there used to be.
So I guess my questions are should there be one and if so, where can I get it?
Any help would be grea
On Mon, May 12, 2014 at 11:08 AM, Roberto Avanzi
wrote:
> > ---> Updating MacPorts base sources using rsync
> > MacPorts base version 2.3.0 installed,
> > MacPorts base version 2.2.1 downloaded.
> > ---> Updating the ports tree
> > ---> MacPorts base is probably trunk or a release candidat
15 matches
Mail list logo
