On 14/04/08 07:29, Mark Lucas wrote:
>>Wireshark must be run via sudo to sniff interfaces.
> Thanks, yes I know. sudo -b wireshark has always worked for me. I have
> wireshark 1.0 working on an intel iMac so I'm assuming this is a
> problem specific to PPC. the point is my PPC version of Wireshark
On 13/04/08 18:00, Mark Lucas wrote:
> On a PPC machine running 10.5.2, having done a clean install of
> MacPorts and then Wireshark 1.0.0_0+darwin_9, Wireshark fails to
> display any interfaces in the Interfaces dialog or any other
> preferences dialog .
>
> dumpcap -D and wireshark - D from the
On 27/11/07 07:31, Brian Matzon wrote:
> Can anyone confirm that the 'warning: run-time library vs. compile-time
> header version mismatch:
> OpenSSL 0.9.8 may not be compatible with OpenSSL 0.9.7' issue has been fixed
> for Postfix using TLS?
If you recompiled openssl try to uninstall and reins
On 04/11/07 21:54, Erwan David wrote:
> > > I'm experiencing some issues with the latest release of mutt-devel and
> > > header caching. Basically, without changing the configuration from
> > > 1.5.16, header caching for my maildirs stopped working.
> > > That's the bug report I filed for on the mu
I'm experiencing some issues with the latest release of mutt-devel and
header caching. Basically, without changing the configuration from
1.5.16, header caching for my maildirs stopped working.
That's the bug report I filed for on the mutt trac,
http://dev.mutt.org/trac/ticket/2978 , does it work f
On 09/05/07 18:49, Tabitha McNerney wrote:
> Thank you for the suggestions. Indeed, in postfix-script, everywhere (only
> three places, lines 200, 211 and 225) there was a bare "ls" I replaced it
> with "/bin/ls" and those errors then disappeared.
Ok, fine.
> I also changed the ownership of
On 09/05/07 01:27, Tabitha McNerney wrote:
> # postfix start
>
> /opt/local/etc/postfix/postfix-script: line 200: ls: command not found
> postfix/postfix-script: warning: not owned by root:
> /opt/local/libexec/postfix
<...>
> The warnings about the command "ls" not being found in the postfi
On 21/04/07 00:56, Алексей Муранов wrote:
> Hello,
> i have a small problem.
> I have just installed MascPorts, and tried
> $ man port
> but received
> No manual entry for portgroup
Maybe your $MANPATH doesn't include /opt/local/share/man/, if you add
export
MANPATH=/opt/local/share/man:/opt/loc
On 19/01/07 16:23, Sbranzo wrote:
> There's a patch for the tls and sasl variants of the postfix ports.
> The version currently available is broken for tls (links against the
> wrong library http://trac.macports.org/projects/macports/ticket/10679)
> and sasl need another compi
On 21/01/07 12:02, Daniel J. Luke wrote:
> It finds an appropriate tar when you install it.
>
> I would move aside fink (or at least remove it from your path) and
> reinstall macports from source.
It worked flawlessy. Thanks a lot.
Gufo
___
macports-
I used to have fink installed, because I needed a working postfix. Now
postfix is ok under macports so I want to remove fink.
If I move /sw to /sw-old, for example, here's what I have If I try to
install some new program in macports:
sudo port -vc install unix2dos
[...]
---> Extracting unix2dos-2
There's a patch for the tls and sasl variants of the postfix ports.
The version currently available is broken for tls (links against the
wrong library http://trac.macports.org/projects/macports/ticket/10679)
and sasl need another compile time switch to enable cyrus-sasl
(http://trac.macports.org/pr
I finally wrote and tested a port for the cvs snapshot of slrn, the same
used in debian experimental.
It works on tiger, maybe it won't work on phanter because it could have a
different automake version installed, but I don't know.
Since this is my firt port I'm not sure all things are done well, a
I thinks there's a bug in the way port names are handled.
I'm trying to compile a cvs snapshot of slrn, the same present in debian
experimental. The debian maintainer assigned 0.9.8.1pl2~cvs20061116 as
version number, and I wish to keep this convention.
If I manually change some links before the .
On 03/01/07 08:58, Mark Duling wrote:
> >2) Inside the autoconf directory a couple of links are wrong. They point
> >to /usr/share/automake-1.9/ and on tiger I have automake-1.6.
> >Is this a common problem? (which is a different way of asking for a common
> >solution ;-)
>
> I'm not sure the
Hi,
I'm trying to write a new slrn-dev port using the same cvs snapshot used
in debian-unstable.
To do this I think I need to execute some commands between the
various phases of the automated process:
1) The name of the sources tarball is
slrn_0.9.8.1pl2~cvs20061116.orig.tar.gz, but the enclosed
16 matches
Mail list logo
