New project members: jonesc

Please join us in welcoming the following new MacPorts project member: - Chris Jones (jonesc) We look forward to continued excellent contributions! - Joshua, Ryan, and Rainer Do you want to join the MacPorts team? If you would like to be considered for team membership and commit access,

Re: Trac down again

On Tue, Nov 1, 2016 at 10:17 AM, Rainer Müller wrote: > We still have some options for tuning, but as it only occurs > sporadically, we always have to wait to see if this solved it. Seems like trac is down again, just got a 503. Does it need another kick? Cheers Adam

Re: [macports-ports] branch master updated: libcxx: Bump to 3.9.0 (#52666)

> On Nov 1, 2016, at 5:47 PM, Rainer Müller wrote: > > On 2016-11-02 00:54, Jeremy Huddleston Sequoia wrote: >> Jeremy Huddleston Sequoia (jeremyhu) pushed a commit to branch master >> in repository macports-ports. >> >>

Re: Trac down again

On 2016-11-02 19:16, Adam Mercer wrote: > On Tue, Nov 1, 2016 at 10:17 AM, Rainer Müller wrote: > >> We still have some options for tuning, but as it only occurs >> sporadically, we always have to wait to see if this solved it. > > Seems like trac is down again, just got a

Kudos to Jeremy...

Who has been on a holy terror for 36 hours. Fixing the libunwind bug (on our heads for two years) and updating / advancing all the compiler infrastructure / libcxx / libcxx abi and many other ports Someone gave that man a JOLT cola! Ken ___

Re: [macports-ports] branch master updated: libcxx: Bump to 3.9.0 (#52666)

Hi, On Wed, Nov 02, 2016 at 09:57:37AM -0700, Bradley Giesbrecht wrote: > Can you pass multiple tickets (closes x y z)? Yes, space-separated, comma-separated, or because the ticket references are quite long, just with multiple Closes $ticket lines. -- Clemens

Re: New project members: jonesc

> On 02 nov 2016, at 20:07, Lawrence Velázquez wrote: > >> Please join us in welcoming the following new MacPorts project member: >> >> - Chris Jones (jonesc) >> >> We look forward to continued excellent contributions! Welcome Chris!  -- Aljaž Srebrnič a.k.a g5pw My

Re: New project members: jonesc

> On Nov 2, 2016, at 2:20 PM, Rainer Müller wrote: > > Please join us in welcoming the following new MacPorts project member: > > - Chris Jones (jonesc) > > We look forward to continued excellent contributions! Yay! vq ___

Re: New project members: jonesc

Thanks All ! > On 2 Nov 2016, at 7:07 pm, Lawrence Velázquez wrote: > >> On Nov 2, 2016, at 2:20 PM, Rainer Müller wrote: >> >> Please join us in welcoming the following new MacPorts project member: >> >> - Chris Jones (jonesc) >> >> We look

Re: New build failure emails are difficult to act on

> On Nov 2, 2016, at 12:17 AM, Jeremy Huddleston Sequoia > wrote: > > I've been having a bit of difficulty dealing with the new buildbot emails. I > would really like links to the individual failing jobs. Instead, we're given > links to each job and a list of failed

Re: GitHub usernames as maintainers

On Wed, Nov 02, 2016 at 05:27:30PM -0500, Ryan Schmidt wrote: > On Nov 2, 2016, at 1:49 AM, Mojca Miklavec wrote: > > It would be nice if "port info" would also print the github > > usernames of maintainers. > > When we were originally planning the transition to GitHub, I suggested > that we

Re: Proposal for a MacPorts'ish commit message template

On Wed, Nov 02, 2016 at 05:33:28PM -0500, Ryan Schmidt wrote: > > vim does that with syntax highlighting automatically nowadays when > > it notices you are writing a commit message. If you need an > > indication on your line width, may I suggest you configure your > > editor appropriately? > >

Re: How to handle MacPorts' handles in the future (including the email address connected to it)??

> On Nov 1, 2016, at 3:17 PM, Marko Käning wrote: > > Hi Rainer, > > On 01 Nov 2016, at 21:05 , Rainer Müller wrote: >> What do you mean by address rewriting? If you are referring to problems >> with SPF, > > I guess I do. > > >> the new mail

Re: Proposal for a MacPorts'ish commit message template

On 2016-11-02 23:46, Ryan Schmidt wrote: >> Which editor are you using? It differs by editor. > > Well, you mentioned vim. Very occasionally I use that. I don't > remember seeing any particular syntax highlighting in it when editing > a commit message. You would need these settings in your

New mailing list host: lists.macports.org

Hello, as part of the move off of macOS forge, we will migrate the mailing lists to the new mail server. We will migrate all subscriptions and user preferences and postings to the old mailing list addresses will be forwarded. However, the new hostname lists.macports.org implies that addresses and

Re: Proposal for a MacPorts'ish commit message template

> On Nov 2, 2016, at 5:43 PM, Clemens Lang wrote: > > On Wed, Nov 02, 2016 at 05:33:28PM -0500, Ryan Schmidt wrote: >>> vim does that with syntax highlighting automatically nowadays when >>> it notices you are writing a commit message. If you need an >>> indication on your

Re: Proposal for a MacPorts'ish commit message template

On Wed, Nov 02, 2016 at 05:46:16PM -0500, Ryan Schmidt wrote: > Well, you mentioned vim. Very occasionally I use that. I don't > remember seeing any particular syntax highlighting in it when editing > a commit message. You need syntax highlighting (:syntax on) and ideally color enabled.

Re: GitHub usernames as maintainers

On Nov 2, 2016, at 1:49 AM, Mojca Miklavec wrote: > It would be nice if "port info" would also print the github usernames > of maintainers. When we were originally planning the transition to GitHub, I suggested that we allow an "@" syntax in the maintainers line for GitHub usernames (i.e.

Re: Proposal for a MacPorts'ish commit message template

MacPorts used CVS commit templates 10 years ago. This was before my involvement with MacPorts, so I don't know how it was decided to do that in the first place or what developer opinions about it were. But you don't have to look at too much of the history of the repositories from 2006 and prior

Re: Github user repos?

On 11/2/16 3:39 PM, Ryan Schmidt wrote: > >> On Nov 1, 2016, at 3:49 PM, David Evans wrote: >> >> On 11/1/16 1:21 PM, Rainer Müller wrote: >>> On 2016-11-01 21:10, David Evans wrote: I see that some github user repos have been created while others (like mine ;-) )

Re: GitHub usernames as maintainers

On Wed, Nov 02, 2016 at 06:45:21PM -0400, Brandon Allbery wrote: > For me, it looks too much like an email address when combined with > other things (e.g. "maintainers openmaintainer @foo"). I think that's a formatting problem. We could just as well print https://github.com/neverpanic in the

Re: Github user repos?

On 2016-11-02 23:39, Ryan Schmidt wrote: > Contrary to Rainer's statement above, my plan was to leave unclaimed > old user repo in the macports org indefinitely. Deleting them implies > they contain no useful information; having not examined them, I'm not > in a position to make that

Re: GitHub usernames as maintainers

On 2016-11-02 23:58, Clemens Lang wrote: > On Wed, Nov 02, 2016 at 06:45:21PM -0400, Brandon Allbery wrote: >> For me, it looks too much like an email address when combined with >> other things (e.g. "maintainers openmaintainer @foo"). > > I think that's a formatting problem. We could just as

Re: Github user repos?

> On Nov 1, 2016, at 3:49 PM, David Evans wrote: > > On 11/1/16 1:21 PM, Rainer Müller wrote: >> On 2016-11-01 21:10, David Evans wrote: >>> I see that some github user repos have been created while others (like mine >>> ;-) ) have not. Is this an ongoing process >>>

Re: Working with Git

> On Oct 31, 2016, at 12:04 PM, Lawrence Velázquez wrote: > >> On Oct 31, 2016, at 11:29 AM, Ryan Schmidt wrote: >> >>> On Oct 5, 2016, at 9:53 PM, Ryan Schmidt wrote: >>> >>> How will this work on GitHub? >>> >>> The

Re: New build failure emails are difficult to act on

> On Nov 2, 2016, at 06:52, Lawrence Velázquez wrote: > > Can you open a ticket for this and assign it to me? You can just > copypaste your original email as the description or something. Thanks: https://trac.macports.org/ticket/52810#ticket > > vq > >> On Nov 2, 2016,

Update to new version of GDB 7.12

Hello The GDB debugger version in macports is currently gdb7.9, there is a newer version gdb7.12 with improved support for dynamic structures. Is it possible for Macports to upload this new version so it can be installed? The current version of GDN in macports is very outdated (GDB7.9) the

Re: port info --{build,configure}.dir ?

> On Nov 2, 2016, at 5:06 AM, René J.V. Bertin wrote: > > Would a request to provide the build and/or configure directory > variables as meta-info data be accepted? Probably not. vq ___ macports-dev mailing list

Re: GitHub usernames as maintainers

On 1 November 2016 at 19:57, Clemens Lang wrote: > On Tue, Nov 01, 2016 at 07:42:23PM +0100, Mojca Miklavec wrote: > >> At some point (rather sooner than later) we'll have to start adding >> GitHub usernames to Portfiles (we might have to extend the base to >> properly support that). > > I agree,

Re: New build failure emails are difficult to act on

Can you open a ticket for this and assign it to me? You can just copypaste your original email as the description or something. vq > On Nov 2, 2016, at 3:56 AM, Jeremy Huddleston Sequoia > wrote: > > >> On Nov 2, 2016, at 00:20, Mojca Miklavec

Re: New build failure emails are difficult to act on

On 2 November 2016 at 06:17, Jeremy Huddleston Sequoia wrote: > I've been having a bit of difficulty dealing with the new buildbot emails. I > would really like links to the individual failing jobs. Instead, we're given > links to each job and a list of failed ports, but there is no indication

port info --{build,configure}.dir ?

Hi, Would a request to provide the build and/or configure directory variables as meta-info data be accepted? Evidently it's something that's relevant to port developer only (or almost, like info --patchfiles). R. ___ macports-dev mailing list