On 2014-11-28 10:03 , Leo Singer wrote:
> Hi,
>
> I have a port, ds9, that supports only certain Mac OS variants (Lion or
> newer). This is currently enforced as :
>
> platform darwin {
> if {${os.major} <= 10} {
> depends_lib
> depends_run
> ui_error "$name requires
On 28.11.2014 12:03 am, Leo Singer wrote:
> But this causes buildbot failures for the unsupported Mac OS versions. How do
> I suppress the buildbot failures?
In short, you don't. There's no way to silence them.
It's noisy and redundant, but I don't know of a workaround. Quite a few of my
package
Hi,
I have a port, ds9, that supports only certain Mac OS variants (Lion or newer).
This is currently enforced as :
platform darwin {
if {${os.major} <= 10} {
depends_lib
depends_run
ui_error "$name requires Mac OS X Lion or later."
error "unsupported platform
On 2011-11-29 09:24 , Christoph Iserlohn wrote:
> Am 28.11.11 21:29, schrieb Jeremy Lavergne:
>> Lots of
>> file:path_eval([".","/var/root"],".erlang"): permission denied
>>
>>
>> Used the compile -> stdio log.
>>
>> http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/3342/steps
Am 28.11.11 21:29, schrieb Jeremy Lavergne:
> Lots of
> file:path_eval([".","/var/root"],".erlang"): permission denied
>
>
> Used the compile -> stdio log.
>
> http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/3342/steps/compile/logs/stdio
>
Ah, thanks!
I'm not familar with b
On Nov 28, 2011, at 14:29, Jeremy Lavergne wrote:
> Lots of
> file:path_eval([".","/var/root"],".erlang"): permission denied
So this might get fixed if we implement #31827.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.m
The real error appears to be:
mkdir -p dist/rabbit_common-0.0.0/ebin
cp rabbit_common.app dist/rabbit_common-0.0.0/ebin/
( cp ../rabbitmq-server/ebin/=ERROR.beam dist/rabbit_common-0.0.0/ebin/ );
( cp ../rabbitmq-server/ebin/REPORT.beam
dist/rabbit_common-0.0.0/ebin/ ); ( cp
../rabbitmq-serv
Lots of
file:path_eval([".","/var/root"],".erlang"): permission denied
Used the compile -> stdio log.
http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/3342/steps/compile/logs/stdio
___
macports-dev mailing list
macports-dev@lis
After I committed r87609 I received a builbot failure notice:
http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/3342
I would like to fix the problem, but it works fine on my machine
(10.6.8/x86_64) and the error message is not very helpful in analyzing
the problem either:
>
On Nov 18, 2011, at 3:43 PM, Jordan K. Hubbard wrote:
>
> Indeed. We actually keep things pretty compatible at the syscall level from
> release to release, but I agree that at the minimum, the major version number
> should match for the host. What is the current status of trace mode,
> anywa
On Nov 17, 2011, at 10:41 PM, Joshua Root wrote:
> There's certainly a lot more that could and should be done in the realm
> of trace mode and sandboxing. The problem with an actual chroot is
> mainly that modern OS X relies on a lot of sockets to get anything done
> (DNS lookups was the one that
On 2011-11-18 10:37 , Jordan K. Hubbard wrote:
>
> On Nov 14, 2011, at 12:39 PM, Ryan Schmidt wrote:
>
>> I think it would be astronomically difficult to get anything like that
>> working on OS X. We can't even get a chroot at all working on Snow
>> Leopard and up; other MacPorts developers have
On Nov 14, 2011, at 12:39 PM, Ryan Schmidt wrote:
>> osc build --ccache Fedora_15 foobar
>>
>> then all the build environment for fedora is created in my /tmp, chrooted
>> (or something similar) and all is built locally so I won't take online
>> resources for testing.
>
> I think it would be
On Nov 14, 2011, at 00:01, Petr Vanek wrote:
> On Nov 14, 2011 (Monday), at 6:48 AM, Joshua Root wrote:
>
>> On 2011-11-14 16:35 , Petr Vanek wrote:
>>>
>>> On Nov 14, 2011 (Monday), at 1:18 AM, Ryan Schmidt wrote:
>>>
The buildbot has a case-sensitive filesystem. The file is Qlipper.app,
On Nov 14, 2011 (Monday), at 6:48 AM, Joshua Root wrote:
> On 2011-11-14 16:35 , Petr Vanek wrote:
>>
>> On Nov 14, 2011 (Monday), at 1:18 AM, Ryan Schmidt wrote:
>>
>>> The buildbot has a case-sensitive filesystem. The file is Qlipper.app, not
>>> qlipper.app.
>>>
>>
>> thanks a lot. All is
On 2011-11-14 16:35 , Petr Vanek wrote:
On Nov 14, 2011 (Monday), at 1:18 AM, Ryan Schmidt wrote:
The buildbot has a case-sensitive filesystem. The file is Qlipper.app, not
qlipper.app.
thanks a lot. All is fixed now.
BTW is there any way how to test buildbot locally? Like "port builbot m
On Nov 13, 2011, at 23:35, Petr Vanek wrote:
> BTW is there any way how to test buildbot locally? Like "port builbot myport"?
Nope. The buildbot is just running MacPorts, on a case-sensitive filesystem,
with no ports installed; every build run is basically from a fresh empty
installation. So t
On Nov 14, 2011 (Monday), at 1:18 AM, Ryan Schmidt wrote:
>
> On Nov 13, 2011, at 14:06, Petr Vanek wrote:
>
>>
>> On Nov 13, 2011 (Sunday), at 9:03 PM, Jeremy Lavergne wrote:
>>
The only thing changed in portfile was version and checksum...
>>>
>>> The error:
>>> DEBUG: Backtrace: erro
On Nov 13, 2011, at 14:09, Jeremy Lavergne wrote:
> Back to the error message, where did this path come from?
>> _Volumes_work_mports_dports_aqua_qlipper
That's simply where the buildbot has its ports tree. No problem there.
___
macports-dev mailing
On Nov 13, 2011, at 14:06, Petr Vanek wrote:
>
> On Nov 13, 2011 (Sunday), at 9:03 PM, Jeremy Lavergne wrote:
>
>>> The only thing changed in portfile was version and checksum...
>>
>> The error:
>> DEBUG: Backtrace: error copying
>> "/opt/local/var/macports/build/_Volumes_work_mports_dports_
> yep, I found it. But how is buildbot environment valid or is it just a
> reference to some "what if" checking environment? I mean I tried to compile
> the port before I committed it and it worked (and works when I try port
> uninstall/install).
It precompiles software for any MacPorts user to
On Nov 13, 2011 (Sunday), at 9:03 PM, Jeremy Lavergne wrote:
>> The only thing changed in portfile was version and checksum...
>
> The error:
> DEBUG: Backtrace: error copying
> "/opt/local/var/macports/build/_Volumes_work_mports_dports_aqua_qlipper/qlipper/work/qlipper-1.8.2/qlipper.app":
> n
> The only thing changed in portfile was version and checksum...
The error:
DEBUG: Backtrace: error copying
"/opt/local/var/macports/build/_Volumes_work_mports_dports_aqua_qlipper/qlipper/work/qlipper-1.8.2/qlipper.app":
no such file or directory
smime.p7s
Description: S/MIME cryptographic s
hi all,
how I should react on buildbot errors? Is it something like showstopper or only
a warning?
When I try to compile my Port (qlipper) all works (tested on SnowLeopard and
Leopard machine). But I received buildbot error message via email.
http://build.macports.org/builders/buildports
24 matches
Mail list logo
