Josh
The rsync command that is failing is something like this
buildbot@build buildbot]$ grep rsync deploy_archives.sh
rsync -rlDzv --ignore-existing ${ULPATH}/ ${DLHOST}:${DLPATH}
rsync -rlDzv --ignore-existing ${ULPATH}/ ${DLPATH}
[buildbot@build buildbot]$
I need some help in
Hi MacPorts devs,
how is the schedule for release of the next MP release which will - I gather -
include the opt-in-able mpstats?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
After it's fixed I'll re-run all the port builds since it broke.
- Josh
On 2014-3-20 05:29 , Shreeraj Karulkar wrote:
Nope, I am looking into it.
Shree
On Mar 19, 2014, at 8:56 AM, Eric A. Borisch ebori...@macports.org
mailto:ebori...@macports.org wrote:
Just making sure this hasn't
Hi,
Despite the fact that I kept pushing a couple of other projects to
switch to a different version control system (mostly from CVS to git),
MacPorts is one of those projects where the current system (trac with
nice linking between tickets and commits, subversion, buildbots, email
accounts, ...)
I would like to introduce a tests variant for a port.
Can someone point me to a port which successfully installs a test variant?
I know that I can build and run tests when building ports (i.e. when I only run
“sudo port build; cd build; ctest …”).
But I want that all needed test files get
On 2014-3-20 12:29 , Marcus Santos wrote:
Can you help me with some questions I have about base/src/port/port.tcl and
base/src/macports1.0.tcl?
First of all I need to understand how they work together and what is the role
of each one. I have been around the code of the progress bar to
Hi,
On 2014-3-20 12:29 , Marcus Santos wrote:
Can you help me with some questions I have about base/src/port/port.tcl and
base/src/macports1.0.tcl?
First of all I need to understand how they work together and what is the
role of each one. I have been around the code of the progress
On Thu, Mar 20, 2014 at 12:11 AM, David Evans dev...@macports.org wrote:
If that is what is happening then you must be using the MacPorts Python
ports as well.
Yes I am.
The intent of the patch is for the macro to determine the
correct Python installation paths for whichever Python is
Brining back to dev list; seems like the right place.
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley s...@macports.org wrote:
Adam Mercer r...@macports.org writes:
On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley s...@macports.org wrote:
I tend to agree with you but need help seeing how this
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley s...@macports.org wrote:
Before: my project installed into /path/foo/a
After: my project installed into /path/foo/b
Got you, if I configured using: ./configure --prefix=$HOME/opt
the the Python modules would be installed in:
On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch ebori...@macports.org wrote:
I think the issue here is that automake is getting patched to *only* support
MacPorts-managed builds, but really automake should still be available for
use to build non-MP software.
Agreed, that's one of the main
Adam Mercer r...@macports.org writes:
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley s...@macports.org wrote:
Before: my project installed into /path/foo/a
After: my project installed into /path/foo/b
Got you, if I configured using: ./configure --prefix=$HOME/opt
the the Python modules
On Thursday, March 20, 2014, Sean Farley
s...@macports.orgjavascript:_e(%7B%7D,'cvml','s...@macports.org');
wrote:
Adam Mercer r...@macports.org writes:
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley s...@macports.org wrote:
Before: my project installed into /path/foo/a
After: my
Eric A. Borisch ebori...@macports.org writes:
On Thursday, March 20, 2014, Sean Farley
s...@macports.orgjavascript:_e(%7B%7D,'cvml','s...@macports.org');
wrote:
Adam Mercer r...@macports.org writes:
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley s...@macports.org wrote:
Before: my
On 3/20/14 2:57 PM, Adam Mercer wrote:
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley s...@macports.org wrote:
Before: my project installed into /path/foo/a
After: my project installed into /path/foo/b
Got you, if I configured using: ./configure --prefix=$HOME/opt
the the Python modules
On Thu, Mar 20, 2014 at 5:57 PM, David Evans dev...@orindasoftware.com wrote:
What's your motivation for installing it elsewhere? Trying to
understand but I guess I'm being dense.
Simply because I'm installing manually from source, it isn't part of
MacPorts and shouldn't be installed in the
On Mar 20, 2014, at 03:07, mk-macpo...@techno.ms wrote:
I would like to introduce a tests variant for a port.
Can someone point me to a port which successfully installs a test variant?
I know that I can build and run tests when building ports (i.e. when I only
run “sudo port build; cd
David Evans dev...@orindasoftware.com writes:
On 3/20/14 2:57 PM, Adam Mercer wrote:
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley s...@macports.org wrote:
Before: my project installed into /path/foo/a
After: my project installed into /path/foo/b
Got you, if I configured using: ./configure
On Mar 20, 2014, at 02:46, Mojca Miklavec wrote:
Despite the fact that I kept pushing a couple of other projects to
switch to a different version control system (mostly from CVS to git),
MacPorts is one of those projects where the current system (trac with
nice linking between tickets and
On 21 Mar 2014, at 00:14 , Ryan Schmidt ryandes...@macports.org wrote:
I’m not aware of any ports that do that, or any tests that are designed to
work that way.
OK, in just now I have made it work by simply chown'ing the port’s work
directory and executing ctest by the logged in user.
That
sync certainly works with git as well.
--Mark
___
Mark E. Anderson e...@emer.net
On Thu, Mar 20, 2014 at 7:19 PM, Ryan Schmidt ryandes...@macports.orgwrote:
On Mar 20, 2014, at 02:46, Mojca Miklavec wrote:
Despite the fact that I kept pushing a couple of other projects
On 3/20/14 3:01 PM, Adam Mercer wrote:
On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch ebori...@macports.org
wrote:
I think the issue here is that automake is getting patched to *only* support
MacPorts-managed builds, but really automake should still be available for
use to build non-MP
I submitted the patch that was committed in r118041.
I will try to explain my tortured logic.
mysql was already silently using g++ as the C++ compiler for 32-bit builds.
Apparently, clang caused a problem at some point (See #42943 for more details).
Some possible solutions were:
1) Blacklist
On Mar 20, 2014, at 19:13, Marcus Calhoun-Lopez wrote:
I submitted the patch that was committed in r118041.
I will try to explain my tortured logic.
mysql was already silently using g++ as the C++ compiler for 32-bit builds.
Apparently, clang caused a problem at some point (See #42943 for
On Thu, Mar 20, 2014 at 7:19 PM, Ryan Schmidt ryandes...@macports.orgwrote:
On Mar 20, 2014, at 02:46, Mojca Miklavec wrote:
Despite the fact that I kept pushing a couple of other projects to
switch to a different version control system (mostly from CVS to git),
MacPorts is one of those
David Evans dev...@macports.org writes:
On 3/20/14 3:01 PM, Adam Mercer wrote:
On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch ebori...@macports.org
wrote:
I think the issue here is that automake is getting patched to *only* support
MacPorts-managed builds, but really automake should
On Mar 20, 2014, at 19:21, Eric Gallager wrote:
That said, a git/hg mirror on GitHub/ButBucket would definitely be nice.
Why would that be nicer than the read-only git mirror that Mac OS Forge
already provides here:
http://www.macosforge.org/post/git-mirrors/
Try to avoid thinking of
27 matches
Mail list logo
