Hi Brad,
On 27 Mar 2014, at 00:14 , Bradley Giesbrecht wrote:
> Marko, do you have a link to the KDE-MAC mailing list subscription page?
> I was unaware that KDE had a Mac specific list.
Unfortunately it’s a VERY LOW VOLUME mailing list:
https://mail.kde.org/mailman/listinfo/kde-mac
:-
On 27 Mar 2014, at 00:26 , Ryan Schmidt wrote:
> https://trac.macports.org/ticket/41321
Thanks, Ryan, for pointing this out.
I see the post is already 4 months old… So, I was obviously just lucky that I
hadn’t run into this earlier already.
Greets,
Marko
___
At 3:03 PM -0700 3/26/14, Bradley Giesbrecht wrote:
On Mar 26, 2014, at 1:44 PM, MacPorts wrote:
Any suggestions on how to get the older machine to behave like the new
one? ;)
I would guess you have directives in a my.cnf file somewhere. To
test this do the following.
sudo port unload
On Mar 26, 2014, at 16:55, mk-macpo...@techno.ms wrote:
> :info:configure clang: error: invalid deployment target for -stdlib=libc++
> (requires OS X 10.7 or later)
https://trac.macports.org/ticket/41321
___
macports-dev mailing list
macports-dev@li
On Mar 24, 2014, at 04:58, and.dam...@macports.org wrote:
> Revision
> 118163
> Author
> and.dam...@macports.org
> Date
> 2014-03-24 02:58:12 -0700 (Mon, 24 Mar 2014)
> Log Message
>
> port bitcoin: switch from git fetching to tarball release, allows to cache
> local distfile; openmaintainer
>
On Mar 26, 2014, at 3:45 PM, mk-macpo...@techno.ms wrote:
> Dear devs, maintainers, users,
>
> I want to cite an invitation from Mario Fux from the KDE community posted on
> the KDE-MAC mailing list:
Marko, do you have a link to the KDE-MAC mailing list subscription page?
I was unaware that KD
I have built kmymoney4-devel’s sources without using ports, but simply did a
“cd kmymoney; mkdir build; cd build; cmake ..; make” and it turned out that
cmake ran through with a few warnings and the build finished successfully after
all.
So, that the build without “sudo port build” does not wo
Dear devs, maintainers, users,
I want to cite an invitation from Mario Fux from the KDE community posted on
the KDE-MAC mailing list:
Mario Fux wrote:
... I'm currently organizing the next edition of the Randa Meetings. The dates
are set: Saturday, 9th to Friday, 15th of August. But we're s
On Mar 26, 2014, at 1:44 PM, MacPorts wrote:
> Any suggestions on how to get the older machine to behave like the new
> one? ;)
I would guess you have directives in a my.cnf file somewhere. To test this do
the following.
sudo port unload mysql5-server
sudo mv /opt/local/etc/mysql5/my{,-old}
I hadn’t built kmymoney4-devel for a while since there had been little progress
in development.
But now that I tried it again I had to realise that it suddenly doesn’t build
anymore.
Obviously it doesn’t even configure properly...
Here is what I saw:
—
.
.
.
:info:configure -- Results of Search
On Wed, Mar 26, 2014 at 9:41 PM, Ryan Schmidt wrote:
> Changing autoreconf.cmd causes MacPorts to not automatically add the
> autoconf, automake and libtool dependencies, so you now have to add them in
> the portfile.
Noticed, portconfigure.tcl+98. Fixed in r118235.
--
Andrea
__
On Mar 25, 2014, at 13:11, and.dam...@macports.org wrote:
> Revision
> 118207
> Author
> and.dam...@macports.org
> Date
> 2014-03-25 11:11:01 -0700 (Tue, 25 Mar 2014)
> Log Message
>
> port bitcoin: call the whole autogen script, openmaintainer
> Modified Paths
>
> • trunk/dports/finance/
On Mar 26, 2014, at 10:22, Jeremy Lavergne wrote:
> From the users list: some applications are pulling up the system stub X11
> indicating that X11 is no longer available, even though MacPorts was used to
> install xorg-server.
>
> Is there a recommended solution to get MacPorts’ X11 to be us
>From the users list: some applications are pulling up the system stub X11
>indicating that X11 is no longer available, even though MacPorts was used to
>install xorg-server.
Is there a recommended solution to get MacPorts’ X11 to be used instead of the
system stub?
Begin forwarded message:
>
On Wed, Mar 26, 2014 at 10:37 AM, Joshua Root wrote:
> My reading of RFC 5322 is that the header field names are case-insensitive.
>
RFC5322 is one thing, the reality of spam traps another. De facto, it's
often assumed that non-normalized case is "suspicious". And good luck
getting major mail hu
On 2014-3-27 00:59 , Jeremy Lavergne wrote:
> Hello Shree.
>
> I wanted to point out a few possible problems I’ve noticed about emails from
> the buildbot:
> * mixed-case headers
> * too many recipients
>
> I suspect all headers should be title case while some of them are not e.g.
> Return-Pa
Hello Shree.
I wanted to point out a few possible problems I’ve noticed about emails from
the buildbot:
* mixed-case headers
* too many recipients
I suspect all headers should be title case while some of them are not e.g.
Return-Path versus current Return-path:
Return-path:
Authentication-re
17 matches
Mail list logo
