Re: Where to include port version in 'port pkg' output?

2013-01-04 Thread Joshua Root
On 2013-1-5 10:15 , Blair Zajac wrote: > I got some feedback from the Munki people [1] and it honors any number > of integers in a version number, so to ensure that packages and > metapackages will support epoch without issue, I put in the epoch number > into the generated filenames and internal ve

Re: buildbot questions

2013-01-04 Thread Ryan Schmidt
On Jan 4, 2013, at 16:25, mk-macpo...@techno.ms wrote: > On Jan 4, 2013, at 11:16 PM, Ryan Schmidt wrote: > >> I am logged in, and I'm looking at this page: >> >> https://build.macports.org/builders >> >> If I want to force a particular port to build* on two of the buildbots, what >> field do

Re: Where to include port version in 'port pkg' output?

2013-01-04 Thread Blair Zajac
On 01/03/2013 04:16 PM, Blair Zajac wrote: On 01/03/2013 04:09 PM, Rainer Müller wrote:> On 2013-01-04 00:49, Blair Zajac wrote: >>> Also, should we put the epoch number into the generated pkg and mpkg >>> filenames? I'm going to add it to the version number: >>> >>> ${epoch}.${portversion}.

Re: buildbot questions

2013-01-04 Thread MK-MacPorts
On Jan 4, 2013, at 11:16 PM, Ryan Schmidt wrote: > I am logged in, and I'm looking at this page: > > https://build.macports.org/builders > > If I want to force a particular port to build* on two of the buildbots, what > field do I put the port name into? We've had the buildbots for so long now,

Re: buildbot questions

2013-01-04 Thread Ryan Schmidt
On Aug 2, 2011, at 11:16, Joshua Root wrote: > Any or all of the values in > the form can be blank. The portlist is actually meant to be space > separated, but a buildbot bug is currently preventing requesting more > than one port from working. I am logged in, and I'm looking at this page: http

Re: New committers: larryv and sean

2013-01-04 Thread vincent habchi
> Please join us in welcoming the following new MacPorts committers: > > - Larry Velásquez (larryv) > - Sean Farley (sean) > Cool! Have a great time here. As the French saying goes: more guests, more fun! :) Vincent ___ macports-dev mailing list macp

Re: New committers: larryv and sean

2013-01-04 Thread Lawrence Velázquez
On Jan 4, 2013, at 4:00 PM, Rainer Müller wrote: > Please join us in welcoming the following new MacPorts committers: > > - Larry Velásquez (larryv) You've probably made a horrible mistake, but thanks! vq ___ macports-dev mailing list macports-dev@l

Re: New committers: larryv and sean

2013-01-04 Thread Sean Farley
On Fri, Jan 4, 2013 at 3:00 PM, Rainer Müller wrote: > Please join us in welcoming the following new MacPorts committers: > > - Larry Velásquez (larryv) > - Sean Farley (sean) > > We look forward to continued excellent contributions from these new team > members. Thanks everyone! __

New committers: larryv and sean

2013-01-04 Thread Rainer Müller
Please join us in welcoming the following new MacPorts committers: - Larry Velásquez (larryv) - Sean Farley (sean) We look forward to continued excellent contributions from these new team members. - Joshua, Rainer, and Ryan Do you want to join the MacPorts team? If you would like to be consi

Re: 64 bit problem during the kdepim 4.9.4 compilation

2013-01-04 Thread Michael Parchet
Hello, This problem is solved Tanks for your help Best regards and happy new hear. mparchet Le 30 déc. 2012 à 00:25, Michael Parchet a écrit : > Hello, > > I tried compile the kdepim4 package on my 64 bit architecture but I have this > message during the during compile processe. > > inki

Re: [101092] trunk/dports/lang/qore-pgsql-module/Portfile

2013-01-04 Thread Ryan Schmidt
On Jan 4, 2013, at 01:41, davidnich...@macports.org wrote: > Revision: 101092 > https://trac.macports.org/changeset/101092 > Author: davidnich...@macports.org > Date: 2013-01-03 23:41:13 -0800 (Thu, 03 Jan 2013) > Log Message: > --- > added postgresql* variants, kept old non

Re: Strange failure on SL and ML buildslaves

2013-01-04 Thread Ryan Schmidt
On Jan 3, 2013, at 13:43, Adam Mercer wrote: > On Thu, Jan 3, 2013 at 4:19 AM, Joshua Root wrote: > >> The only real solution, AFAIK, is "don't do that", or handle the failure >> gracefully. > > I'm open to suggestion on how to achieve this. It's a matter to be reported to the developers of th