Re: KDE community seeks cooperation with MacPorts enthusiasts by inviting them to come to Randa (Switzerland) in August 2014

2014-03-26 Thread MK-MacPorts 
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

:-/

KDE-DEVEL makes more sense:

https://mail.kde.org/mailman/listinfo/kde-devel

Greets,
Marko

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: month-old CMake update to 2.8.12.2 with side-effects for Qt?

2014-03-26 Thread MK-MacPorts 
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
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #43088: mysql5 @5.1.72 uses /tmp for socket

2014-03-26 Thread Craig Treleaven 

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 mysql5-server
sudo mv /opt/local/etc/mysql5/my{,-old}.cnf


A stray my.cnf was the problem; ticket updated.

Thanks

Craig

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: month-old CMake update to 2.8.12.2 with side-effects for Qt?

2014-03-26 Thread Ryan Schmidt 

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@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [118163] trunk/dports/finance/bitcoin/Portfile

2014-03-26 Thread Ryan Schmidt 

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
> Modified Paths
> 
>   • trunk/dports/finance/bitcoin/Portfile
> Diff
> 
> Modified: trunk/dports/finance/bitcoin/Portfile (118162 => 118163)
> 
> --- trunk/dports/finance/bitcoin/Portfile 2014-03-24 09:53:36 UTC (rev 
> 118162)
> +++ trunk/dports/finance/bitcoin/Portfile 2014-03-24 09:58:12 UTC (rev 
> 118163)
> 
> @@ -16,9 +16,11 @@
> 
>  operating through the nodes of the network. 
> 
>  homepagehttp://www.bitcoin.org/
>  
> 
> -fetch.type  git
> -git.url 
> https://github.com/bitcoin/bitcoin.git
> 
> -git.branch  v${version} 
> 
> +master_siteshttps://github.com/[string
>  repeat "$name/" 2]archive/
> +distnamev${version}
> +worksrcdir  ${name}-${version}

Could we simplify this by using the github portgroup?



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: KDE community seeks cooperation with MacPorts enthusiasts by inviting them to come to Randa (Switzerland) in August 2014

2014-03-26 Thread Bradley Giesbrecht 
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 KDE had a Mac specific list.


Regards,
Bradley Giesbrecht (pixilla)

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: month-old CMake update to 2.8.12.2 with side-effects for Qt?

2014-03-26 Thread MK-MacPorts 
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 work can only mean that 
my port file is not properly configuring something, right?


—
$ cmake ..
.
.
.
Good - your configure finished.
Now type 'make' to build KMyMoney. For more help, consult README.cmake

-- Configuring done
CMake Warning (dev) in kmymoney/widgets/CMakeLists.txt:
  Policy CMP0022 is not set: INTERFACE_LINK_LIBRARIES defines the link
  interface.  Run "cmake --help-policy CMP0022" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  Target "kmm_widgets" has an INTERFACE_LINK_LIBRARIES property which differs
  from its LINK_INTERFACE_LIBRARIES properties.

  INTERFACE_LINK_LIBRARIES:

KDE4__kdeui;Qt4::QtGui;Qt4::QtCore;KDE4__kdecore

  LINK_INTERFACE_LIBRARIES:



This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in kmymoney/mymoney/CMakeLists.txt:
  Policy CMP0022 is not set: INTERFACE_LINK_LIBRARIES defines the link
  interface.  Run "cmake --help-policy CMP0022" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  Target "kmm_mymoney" has an INTERFACE_LINK_LIBRARIES property which differs
  from its LINK_INTERFACE_LIBRARIES properties.

  INTERFACE_LINK_LIBRARIES:


KDE4__kdeui;Qt4::QtGui;Qt4::QtXml;Qt4::QtCore;KDE4__kdecore;KDE4__kio;/opt/local/lib/libgmp.dylib;/opt/local/lib/libalkimia.dylib;kmm_storage

  LINK_INTERFACE_LIBRARIES:



This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in kmymoney/plugins/CMakeLists.txt:
  Policy CMP0022 is not set: INTERFACE_LINK_LIBRARIES defines the link
  interface.  Run "cmake --help-policy CMP0022" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  Target "kmm_plugin" has an INTERFACE_LINK_LIBRARIES property which differs
  from its LINK_INTERFACE_LIBRARIES properties.

  INTERFACE_LINK_LIBRARIES:


KDE4__kdeui;KDE4__kio;KDE4__kutils;/opt/local/lib/libgmp.dylib;/opt/local/lib/libalkimia.dylib

  LINK_INTERFACE_LIBRARIES:



This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in libkdchart/src/CMakeLists.txt:
  Policy CMP0022 is not set: INTERFACE_LINK_LIBRARIES defines the link
  interface.  Run "cmake --help-policy CMP0022" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  Target "kmm_kdchart" has an INTERFACE_LINK_LIBRARIES property which differs
  from its LINK_INTERFACE_LIBRARIES properties.

  INTERFACE_LINK_LIBRARIES:

Qt4::QtSvg;Qt4::QtXml;Qt4::QtGui;Qt4::QtCore

  LINK_INTERFACE_LIBRARIES:



This warning is for project developers.  Use -Wno-dev to suppress it.

-- Generating done
-- Build files have been written to: 
/Users/okram/WC/GIT/kmymoney.online-balance_highlighting_extended/build

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

KDE community seeks cooperation with MacPorts enthusiasts by inviting them to come to Randa (Switzerland) in August 2014

2014-03-26 Thread MK-MacPorts 
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 still setting 
together the groups that come to Randa.

The main focus this year shall be KF5, more platforms and a KDE SDK. So we 
definitely need some KDE/Mac people. Anybody here interested? Do you have 
questions? Ideas?

Best regards,
Mario


http://www.randa-meetings.ch/
http://randa-meetings.ch/2014/02/19/randa-meetings-2014-the-date-is-set-please-register/




---


In various discussion threads during the last weeks the KDE community expressed 
that they would welcome anyone willing to do some bridge-building between KDE 
on Linux and OSX/MacPorts! KDE is considering to also get a CI system based on 
OSX up and running which shall improve code quality notably.

In the past years there has been a lot of trouble porting KDE to MacPorts 
(which has luckily become much smoother lately) and it would be worthwhile to 
have more people active in this field.

This is especially true for the upcoming KF5 which needs a MacPorts-Qt5 - for 
which an experienced maintainer is necessary.

Anyone out there interested to improve the MacPorts’ contact to KDE on Linux?

Anyone willing to contribute and support the Randa meeting in summer?

I could imagine that the KDE guys would be interested in how MacPorts’ core 
team has set up MacPorts' buildbot infrastructure with respect to hard/software 
and its maintenance requirements.



Get in touch! :-)


Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #43088: mysql5 @5.1.72 uses /tmp for socket

2014-03-26 Thread Bradley Giesbrecht 

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}.cnf
sudo port deactivate mysql5-server mysql5
sudo port activate mysql5-server mysql5
sudo port load mysql5-server
mysql5 -uroot -p -e 'SHOW VARIABLES LIKE "%socket%";'

If the above shows your socket at "/opt/local/var/run/mysql5/mysqld.sock" then 
examine the contents of /opt/local/etc/mysql5/my-old.cnf for a socket path 
influencing directive.


Regards,
Bradley Giesbrecht (pixilla)

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

month-old CMake update to 2.8.12.2 with side-effects for Qt?

2014-03-26 Thread MK-MacPorts 
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 for Phonon
:info:configure --  -> PHONON_VERSION is 4.7.1
:info:configure --  -> PHONON_INCLUDE_DIR is /opt/local/include
:info:configure --  -> PHONON_LIBRARY is /opt/local/lib/libphonon.dylib
:info:configure Change Dir: 
/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_kmymoney4-devel/kmymoney4-devel/work/build/CMakeFiles/CMakeTmp
:info:configure
:info:configure Run Build Command:/opt/local/bin/gmake 
"cmTryCompileExec446391939/fast"
:info:configure /opt/local/bin/gmake -f 
CMakeFiles/cmTryCompileExec446391939.dir/build.make 
CMakeFiles/cmTryCompileExec446391939.dir/build
:info:configure gmake[1]: Entering directory 
'/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_kmymoney4-devel/kmymoney4-devel/work/build/CMakeFiles/CMakeTmp'
:info:configure /opt/local/bin/cmake -E cmake_progress_report 
/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_kmymoney4-devel/kmymoney4-devel/work/build/CMakeFiles/CMakeTmp/CMakeFiles
 1
:info:configure Building CXX object 
CMakeFiles/cmTryCompileExec446391939.dir/check_qt_visibility.cpp.o
:info:configure /usr/bin/clang++-pipe -Os -arch x86_64 -stdlib=libc++  
-fno-common -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align 
-Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security 
-Woverloaded-virtual -fno-common -fvisibility=hidden -Werror=return-type 
-fvisibility-inlines-hidden -Wno-return-type-c-linkage  -arch x86_64 
-I/opt/local/include/QtXmlPatterns -I/opt/local/include/QtXml 
-I/opt/local/include/QtWebKit -I/opt/local/include/QtUiTools 
-I/opt/local/include/QtTest -I/opt/local/include/QtSvg 
-I/opt/local/include/QtSql -I/opt/local/include/QtScriptTools 
-I/opt/local/include/QtScript -I/opt/local/include/QtOpenGL 
-I/opt/local/include/QtNetwork -I/opt/local/include/QtMultimedia 
-I/opt/local/include/QtHelp -I/opt/local/include/QtDesigner 
-I/opt/local/include/QtDeclarative -I/opt/local/include/QtDBus 
-I/opt/local/include/Qt3Support -I/opt/local/include/QtGui 
-I/opt/local/include/QtCore -I/opt/local/include 
-I/opt/local/share/qt4/mkspecs/default-o 
CMakeFiles/cmTryCompileExec446391939.dir/check_qt_visibility.cpp.o -c 
/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_kmymoney4-devel/kmymoney4-devel/work/build/CMakeTmp/check_qt_visibility.cpp
:info:configure clang: error: invalid deployment target for -stdlib=libc++ 
(requires OS X 10.7 or later)
:info:configure CMakeFiles/cmTryCompileExec446391939.dir/build.make:60: recipe 
for target 'CMakeFiles/cmTryCompileExec446391939.dir/check_qt_visibility.cpp.o' 
failed
:info:configure gmake[1]: *** 
[CMakeFiles/cmTryCompileExec446391939.dir/check_qt_visibility.cpp.o] Error 1
:info:configure gmake[1]: Leaving directory 
'/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_kmymoney4-devel/kmymoney4-devel/work/build/CMakeFiles/CMakeTmp'
:info:configure Makefile:117: recipe for target 
'cmTryCompileExec446391939/fast' failed
:info:configure gmake: *** [cmTryCompileExec446391939/fast] Error 2
:info:configure
:info:configure CMake Error at 
/opt/local/share/apps/cmake/modules/FindKDE4Internal.cmake:1377 (message):
:info:configure   Qt compiled without support for -fvisibility=hidden.  This 
will break
:info:configure   plugins and linking of some applications.  Please fix your Qt 
installation
:info:configure   (try passing --reduce-exports to configure).
:info:configure Call Stack (most recent call first):
:info:configure   /opt/local/share/cmake-2.8/Modules/FindKDE4.cmake:95 
(find_package)
:info:configure   CMakeLists.txt:56 (FIND_PACKAGE)
:info:configure
:info:configure
:info:configure -- Configuring incomplete, errors occurred!
:info:configure See also 
"/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_kmymoney4
-devel/kmymoney4-devel/work/build/CMakeFiles/CMakeOutput.log".
:info:configure See also 
"/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_kmymoney4
-devel/kmymoney4-devel/work/build/CMakeFiles/CMakeError.log".
—

Any idea what’s going there about "invalid deployment target for -stdlib=libc++ 
(requires OS X 10.7 or later)” ?

I am puzzled…

Could this be related to the cmake upgrade a month ago?

Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [118207] trunk/dports/finance/bitcoin/Portfile

2014-03-26 Thread Andrea D'Amore 
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
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [118207] trunk/dports/finance/bitcoin/Portfile

2014-03-26 Thread Ryan Schmidt 

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/bitcoin/Portfile
> Diff
> 
> Modified: trunk/dports/finance/bitcoin/Portfile (118206 => 118207)
> 
> --- trunk/dports/finance/bitcoin/Portfile 2014-03-25 18:06:16 UTC (rev 
> 118206)
> +++ trunk/dports/finance/bitcoin/Portfile 2014-03-25 18:11:01 UTC (rev 
> 118207)
> 
> @@ -34,7 +34,8 @@
> 
>  port:protobuf-cpp
> 
>  
> 
>  use_autoreconf  yes
> 
> -autoreconf.args-append --force
> 
> +autoreconf.cmd  ./autogen.sh
> +autoreconf.args

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.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Jeremy Huddleston Sequoia 

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 used instead of 
> the system stub?

The stubs are there for projects that linked against /usr/X11.  All you really 
need to do is setup symlinks to redirect them to your MP prefix.  I recommend 
starting with the XQuartz hook (which is installed on the system to setup the 
links to /opt/X11) and then just changing them to the MacPorts prefix 
(/opt/local in the example below):

sudo port -v install xorg
launchctl load -w /Library/LaunchAgents/org.macports.startx.plist
sudo /usr/X11/libexec/xquartz_postinst.sh
sudo rm /usr/X11
sudo rm /usr/X11R6
sudo ln -s /opt/local /usr/X11
sudo ln -s /opt/local /usr/X11R6

Note that loading the launchd.plist requires logout and login for $DISPLAY to 
propagate.

--Jeremy

> Begin forwarded message:
> 
>> From: Kevin Reid 
>> Subject: Re: How do I cause standalone X11 apps to use MacPorts X11?
>> Date: March 26, 2014 at 13:12:54 EDT
>> To: MacPorts Users 
>> 
>> On Mar 26, 2014, at 10:07, Jeremy Lavergne  
>> wrote:
>> 
>>> This might really depend on the application: is it checking for x11 or 
>>> giving up based on the OS?
>> 
>> The dialog does not come from the application but from the system-provided 
>> X11.app (this is observable by Dock/menu bar) which is a nonfunctional stub 
>> (this is what my research says).
>> 
>> It sounds like the assumption is that when you install third-party X11 as 
>> instructed by the dialog, it will _replace_ the system-provided X11. But 
>> MacPorts doesn't replace system files as a rule -- I'm looking for a 
>> solution which fits into MacPorts's way of working.
>> 
>> -- 
>> Kevin Reid  
>> 
>> ___
>> macports-users mailing list
>> macports-us...@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Fwd: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Jeremy Lavergne 
>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:

> From: Kevin Reid 
> Subject: Re: How do I cause standalone X11 apps to use MacPorts X11?
> Date: March 26, 2014 at 13:12:54 EDT
> To: MacPorts Users 
> 
> On Mar 26, 2014, at 10:07, Jeremy Lavergne  wrote:
> 
>> This might really depend on the application: is it checking for x11 or 
>> giving up based on the OS?
> 
> The dialog does not come from the application but from the system-provided 
> X11.app (this is observable by Dock/menu bar) which is a nonfunctional stub 
> (this is what my research says).
> 
> It sounds like the assumption is that when you install third-party X11 as 
> instructed by the dialog, it will _replace_ the system-provided X11. But 
> MacPorts doesn't replace system files as a rule -- I'm looking for a solution 
> which fits into MacPorts's way of working.
> 
> -- 
> Kevin Reid  
> 
> ___
> macports-users mailing list
> macports-us...@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: buildbot emails

2014-03-26 Thread Brandon Allbery 
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 hubs to make exceptions just for us.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: buildbot emails

2014-03-26 Thread Joshua Root 
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-Path versus current Return-path:
> Return-path: 
> Authentication-results: symauth.service.identifier
> Envelope-to: jeremy@...
> Delivery-date: Sun, 23 Mar 2014 23:41:22 -0400
> Content-transfer-encoding: base64
> Content-type: text/plain; charset=utf8
> Message-id: <20140324034119.ab017140...@build.macports.org>

My reading of RFC 5322 is that the header field names are case-insensitive.

   "Characters will be specified either by a decimal value
   (e.g., the value %d65 for uppercase A and %d97 for lowercase A) or by
   a case-insensitive literal value enclosed in quotation marks (e.g.,
   "A" for either uppercase or lowercase A)."

...

"   message-id  =   "Message-ID:" msg-id CRLF

   in-reply-to =   "In-Reply-To:" 1*msg-id CRLF

   references  =   "References:" 1*msg-id CRLF"

> When there are many builds, the recipient list can be quite large. Email 
> services tend to think a huge, sorted list of recipients is spammy. Could we 
> possibly become BCC on the email? Or one email generated per recipient?

Buildbot doesn't appear to offer those options.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

buildbot emails

2014-03-26 Thread Jeremy Lavergne 
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-results: symauth.service.identifier
Envelope-to: jeremy@...
Delivery-date: Sun, 23 Mar 2014 23:41:22 -0400
Content-transfer-encoding: base64
Content-type: text/plain; charset=utf8
Message-id: <20140324034119.ab017140...@build.macports.org>

When there are many builds, the recipient list can be quite large. Email 
services tend to think a huge, sorted list of recipients is spammy. Could we 
possibly become BCC on the email? Or one email generated per recipient?

Thanks for looking into these.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev