Hi Ryan,
I just replaced git: with http: and git was able to retrieve the sources…
> ---
> git.url http://anongit.kde.org/kmymoney
> git.branch 6f28b1c9fa3c0684d184d3bfc1d638de933a1f91
> ---
…but I still get this error:
> ---
> $ git log -1
> error: packfile
> .git/objects/
On Nov 14, 2011, at 1:19 AM, Ryan Schmidt wrote:
> Yes except you should use an http or https url instead of a git url if
> available because the buildbot cannot fetch from git urls.
Hmm, but, the problem is that I am not even testing this on buildbot, but
locally in a port tree of mine.
OK, I'll
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:38 , Ryan Schmidt wrote:
I wasn't sure what would happen when you change the case of the port name like
that. Will users who had qlipper @1.8.2_0 installed get prompted to upgrade to
Qlipper @1.8.2_1? I don't think this is a case we ever deliberately considered,
so if it does
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:38, Ryan Schmidt wrote:
> On Nov 13, 2011, at 23:06, pva...@macports.org wrote:
>
>> Revision: 87201
>> http://trac.macports.org/changeset/87201
>> Author: pva...@macports.org
>> Date: 2011-11-13 21:06:30 -0800 (Sun, 13 Nov 2011)
>> Log Message:
>> ---
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 13, 2011, at 23:06, pva...@macports.org wrote:
> Revision: 87201
> http://trac.macports.org/changeset/87201
> Author: pva...@macports.org
> Date: 2011-11-13 21:06:30 -0800 (Sun, 13 Nov 2011)
> Log Message:
> ---
> qlipper: buildbot fix (case sensitive paths)
>
> Mod
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
I have made the same (simple) change in several ports since upgrading to XCode
4.2.
If I remember correctly, I had to apply the opposite conditional swap in some
ports while using XCode <4.0.
Reproducing user-reported bugs could become tricky if compilers change
significantly and frequently and
You don't appear to actually be using clang in the output you quoted,
but rather 'cc', which is linked to llvm-gcc-4.2 on your system. I don't
know if clang -E would behave significantly differently, but it's well
worth checking.
- Josh
On 2011-11-14 13:19 , Matthew Cottrell wrote:
Using "$(
On 2011-11-14 13:48 , Ryan Schmidt wrote:
On Nov 13, 2011, at 20:33, rmstonecip...@macports.org wrote:
Revision: 87198
http://trac.macports.org/changeset/87198
Author: rmstonecip...@macports.org
Date: 2011-11-13 18:33:36 -0800 (Sun, 13 Nov 2011)
Log Message:
---
x11/xor
On Nov 13, 2011, at 20:33, rmstonecip...@macports.org wrote:
> Revision: 87198
> http://trac.macports.org/changeset/87198
> Author: rmstonecip...@macports.org
> Date: 2011-11-13 18:33:36 -0800 (Sun, 13 Nov 2011)
> Log Message:
> ---
> x11/xorg-libX11 changed configure.compi
Using "$(CC) -E" did not succeed because it left an input file unused.
:info:build cc -E -IMENUS ARB_GDEmenus.source >ARB_GDEmenus
:info:build i686-apple-darwin11-llvm-gcc-4.2: ARB_GDEmenus.source: linker input
file unused because linking not done
Would it be too brittle to simply use /usr/bin/c
On Nov 13, 2011, at 19:27, Matthew Cottrell wrote:
> I'm trying to use the right compiler, but ${configure.cpp} is empty on my
> system. How do I satisfy a port that needs cpp?
>
> I do have the other stuff
>
> ${configure.cc}=/Developer/usr/bin/clang
> ${configure.cxx}=/Developer/usr/bin/cla
I'm trying to use the right compiler, but ${configure.cpp} is empty on my
system. How do I satisfy a port that needs cpp?
I do have the other stuff
${configure.cc}=/Developer/usr/bin/clang
${configure.cxx}=/Developer/usr/bin/clang++
--
Matthew Cottrell
Lewes, DE 19958
http://www.mattcottrell.
On Nov 13, 2011, at 13:50, Marko Käning wrote:
> I used the following to specify the sources to be fetched, where git.branch
> denotes the latest changeset detected in a locally run "git pull":
> ---
> git.url git://anongit.kde.org/kmymoney
> git.branch 6f28b1c9fa3c0684d184d
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-snowl
Hi guys,
I thought I'd quickly update MacPorts' port kmymoney4-devel from SVN to GIT,
but ran into a problem after the sources were fetched "successfully" via git!
I used the following to specify the sources to be fetched, where git.branch
denotes the latest changeset detected in a locally run
24 matches
Mail list logo
