On 10/18/2012 06:33 PM, Clemens Lang wrote:
On Thu, Oct 18, 2012 at 11:26:36AM -0700, Blair Zajac wrote:
Both the new zmq port and the new zmq22 port were "svn add"ed to the
repository. They should have been "svn copy"ed from the existing port,
so that the four-year-long history of the port is p
On Thu, Oct 18, 2012 at 11:26:36AM -0700, Blair Zajac wrote:
> You need to bump the revision on all the ports you updated otherwise
> they won't pick up the new dependency.
https://trac.macports.org/changeset/98866
> Also, you added a zmq port but there was already one in sysutils/zmq
> which you
Hi,
On Thu, Oct 18, 2012 at 11:05:14AM -0700, William Siegrist wrote:
> > Error: CHILDSTATUS 19633 1: ERROR 1062 (23000) at line 114994: Duplicate
> > entry 'zmq' for key 'PRIMARY'
> There is a duplicate zmq port.
thanks, should be fixed in https://trac.macports.org/changeset/98862.
--
Clemen
On Oct 18, 2012, at 13:26, Blair Zajac wrote:
> Regarding https://trac.macports.org/changeset/98850:
>
> You need to bump the revision on all the ports you updated otherwise they
> won't pick up the new dependency.
Yes, but changing these ports' library dependencies from zmq to zmq22 makes
t
Hello,
Regarding https://trac.macports.org/changeset/98850:
You need to bump the revision on all the ports you updated otherwise
they won't pick up the new dependency.
Also, you added a zmq port but there was already one in sysutils/zmq
which you need to manage. It's for 2.2.0 and has nomai
Begin forwarded message:
> Error: CHILDSTATUS 19633 1: ERROR 1062 (23000) at line 114994: Duplicate
> entry 'zmq' for key 'PRIMARY'
There is a duplicate zmq port.
-Bill
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.
On Oct 17, 2012, at 16:09, Michaël Parchet wrote:
> Le 17 oct. 2012 à 15:55, Jeremy Lavergne a écrit :
>
>> Pretty much all of the KDE packages have a +docs variant.
>
> I have uninstall kdepim4 and re-install kdepimlibs4 with this command line
>
> sudo port -v install kdepimlibs4 +doc
The var
On 10/18/12 09:54 , Joshua Root wrote:
On 2012-10-19 02:49 , Jonathan Stickel wrote:
On 10/18/12 09:35 , Joshua Root wrote:
On 2012-10-19 02:16 , Jeremy Lavergne wrote:
I am trying to set a variable in a variant for later use in
another variant, but I am getting errors that the variable does
n
On Thu, Oct 18, 2012 at 10:49 AM, Jonathan Stickel wrote:
> On 10/18/12 09:35 , Joshua Root wrote:
>>
>> On 2012-10-19 02:16 , Jeremy Lavergne wrote:
I am trying to set a variable in a variant for later use in
another variant, but I am getting errors that the variable does
not
On 2012-10-19 02:49 , Jonathan Stickel wrote:
> On 10/18/12 09:35 , Joshua Root wrote:
>> On 2012-10-19 02:16 , Jeremy Lavergne wrote:
I am trying to set a variable in a variant for later use in
another variant, but I am getting errors that the variable does
not exist. Here are the r
On 10/18/12 09:35 , Joshua Root wrote:
On 2012-10-19 02:16 , Jeremy Lavergne wrote:
I am trying to set a variable in a variant for later use in
another variant, but I am getting errors that the variable does
not exist. Here are the relevant lines:
Try wrapping your code in "if {[variant_isset
On 2012-10-19 02:16 , Jeremy Lavergne wrote:
>> I am trying to set a variable in a variant for later use in another variant,
>> but I am getting errors that the variable does not exist. Here are the
>> relevant lines:
>
> Try wrapping your code in "if {[variant_isset ...]} {...}" rather than ins
On 2012-10-19 02:12 , Jonathan Stickel wrote:
> I am trying to set a variable in a variant for later use in another
> variant, but I am getting errors that the variable does not exist.
The scope of the variable is limited to the variant body you set it in
unless you declare it global ('man n globa
> I am trying to set a variable in a variant for later use in another variant,
> but I am getting errors that the variable does not exist. Here are the
> relevant lines:
Try wrapping your code in "if {[variant_isset ...]} {...}" rather than inside a
variant block--much like how default_variants
I am trying to set a variable in a variant for later use in another
variant, but I am getting errors that the variable does not exist. Here
are the relevant lines:
variant python26 conflicts python27 description {Configure to use Python
version 2.6} {
set python.version 26
}
variant pyth
15 matches
Mail list logo
