Re: buildbot and binary archives ...

On 2014-2-21 12:17 , Ryan Schmidt wrote: > > On Feb 20, 2014, at 09:44, Peter Danecek wrote: > >> On 20 Feb 2014, at 16:00, Jeremy Lavergne wrote: >> >>> packages.macports.org/PACKAGENAME/ >> >> So looking up `http://packages.macports.org/py-obspy/` reveals that a binary >> archives were produce

Re: buildbot and binary archives ...

On Feb 20, 2014, at 09:44, Peter Danecek wrote: > On 20 Feb 2014, at 16:00, Jeremy Lavergne wrote: > >> packages.macports.org/PACKAGENAME/ > > So looking up `http://packages.macports.org/py-obspy/` reveals that a binary > archives were produces some time ago. These are marked "noarch", which i

Re: revision bump?

Correct. It keeps these archives locally, regardless of the ability to distribute them. On Feb 20, 2014, at 14:07, Blair Zajac wrote: > Just to be clear, my understanding is that a buildbot will only attempt a > rebuild of a port if there is no binary archive for it when the Portfile > change

Re: revision bump?

On Feb 20, 2014, at 10:53 AM, Frank Schima wrote: > > On Feb 20, 2014, at 11:36 AM, Peter Danecek wrote: > >> Is it necessary to revision bump a port to force the build of a binary >> archive? >> >> I am fixing one of my ports. It was possible to install the port in some >> cases, in other

Re: revision bump?

On Feb 20, 2014, at 11:36 AM, Peter Danecek wrote: > Is it necessary to revision bump a port to force the build of a binary > archive? > > I am fixing one of my ports. It was possible to install the port in some > cases, in other it failed, depending on the personal setup. For the details >

revision bump?

Hi all, Is it necessary to revision bump a port to force the build of a binary archive? I am fixing one of my ports. It was possible to install the port in some cases, in other it failed, depending on the personal setup. For the details here the ticket: http://trac.macports.org/ticket/42576. H

Re: buildbot and binary archives ...

On 20 Feb 2014, at 16:00, Jeremy Lavergne wrote: > packages.macports.org/PACKAGENAME/ So looking up `http://packages.macports.org/py-obspy/` reveals that a binary archives were produces some time ago. These are marked "noarch", which is probably wrong. There are compiled extensions. I do not

Re: [MacPorts] howto/Subversion modified

On Feb 20, 2014, at 10:24 AM, Rainer Müller wrote: > > On 2014-02-20 16:07, MacPorts wrote: >> Page "howto/Subversion" was changed by ulr...@familie-schulte.net >> Diff URL: >> >> Revision 7 >> Changes: >> ---8<--8<-

Re: [MacPorts] howto/Subversion modified

Hello, On 2014-02-20 16:07, MacPorts wrote: > Page "howto/Subversion" was changed by ulr...@familie-schulte.net > Diff URL: > > Revision 7 > Changes: > ---8<--8<--8<--8<--8<--8<--8<--8<

Re: buildbot and binary archives ...

packages.macports.org/PACKAGENAME/ so, for pspp-devel for example, packages.macports.org/pspp-devel/ Perhaps it’s the license of the package that prevents the binaries? The logs area available on the buildbot master for the mavericks post slave: https://build.macports.org/buildslaves/apple-maver

Re: buildbot and binary archives ...

Hi, The first thing you should check is if the license in the Port file allows for the binaries to be distributed ? Chris On 20/02/14 14:54, Peter Danecek wrote: Hi all, from a user report I realised that there is probably no binary archive available for Maverick of one port I am maintain

commit rights ...

Hi, just a short one. I have applied for commit rights some time ago, and am wondering now how long it usually takes until these requests are evaluated or if there is some way to have a status feedback. Thanks! ~petr smime.p7s Description: S/MIME cryptographic signature ___

buildbot and binary archives ...

Hi all, from a user report I realised that there is probably no binary archive available for Maverick of one port I am maintaining. I am now, wondering if there is a way to obtain more information, e.g. - Which binary archives exist and when these were produced? - Are there problems with the bu