Re: Trac down again

2016-10-26 Thread Clemens Lang
On Wed, Oct 26, 2016 at 09:13:33PM +0200, Marko Käning wrote: > Where is our trac again? I've kicked it. Not exactly sure what causes these outages, it's probably some crawler that fills a queue with requests and causes all of them to be dropped due to timeout after a while. We're keeping an eye

Re: Git tools for managing patchsets

2016-10-26 Thread Marko Käning
On 26 Oct 2016, at 17:54 , Michael wrote: > Interesting that you mention "Quilt". There is another tool -- Stacked Git -- > that is modeled after Quilt. I don’t see the point of these additional tools on top of git? If git provides branches, why do I need extra magic to work with them? Yet, e

Re: Trac down again

2016-10-26 Thread Lawrence Velázquez
It’s back. I have seen this error a couple of times since the Trac migration. vq > On Oct 26, 2016, at 3:18 PM, Marius Schamschula wrote: > > Hmm. > > Service Unavailable > > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please

Re: Trac down again

2016-10-26 Thread Marius Schamschula
Hmm. Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.4.10 (Debian) Server at trac.macports.org Port 443 Wow. apache24-devel is @2.4.23, but then again the Debian folks back-port pat

Trac down again

2016-10-26 Thread Marko Käning
Where is our trac again? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

2016-10-26 Thread René J . V . Bertin
On Wednesday October 26 2016 18:50:33 Clemens Lang wrote: > On Wed, Oct 26, 2016 at 02:17:53AM +0200, René J.V. Bertin wrote: > > Yeah. There could be a check if the Portfile exists to catch the 1st > > possibility > > That would introduce a race condition, wouldn't it? Checking whether a > file

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

2016-10-26 Thread Clemens Lang
Hi, On Wed, Oct 26, 2016 at 02:17:53AM +0200, René J.V. Bertin wrote: > Yeah. There could be a check if the Portfile exists to catch the 1st > possibility That would introduce a race condition, wouldn't it? Checking whether a file exists before doing something with it is a classic mistake. > and

Re: Git tools for managing patchsets

2016-10-26 Thread Michael
On 2016-10-26, at 12:25 AM, Joshua Root wrote: > On 2016-10-25 10:03 , Michael wrote: >> >> On 2016-10-24, at 2:57 PM, Marko Käning wrote: >> >>> Hi folks, >>> >>> when I read only the first two paragraphs of this thread... >>> >>> On 24 Oct 2016, at 18:37 , Michael wrote: So since Ma

Re: "Failed to open portfile from registry" while reinstalling because of configure.optflags

2016-10-26 Thread René J . V . Bertin
Follow-up : I do NOT see the error (due to configure.optflags) when I do `port -n upgrade`. I think this suggests that `upgrade --force` does something recursive which is responsible for the substitution/dereferencing. R. ___ macports-dev mailing list

Re: Git tools for managing patchsets

2016-10-26 Thread Joshua Root
On 2016-10-25 10:03 , Michael wrote: On 2016-10-24, at 2:57 PM, Marko Käning wrote: Hi folks, when I read only the first two paragraphs of this thread... On 24 Oct 2016, at 18:37 , Michael wrote: So since MacPorts is moving to git, and from what I saw in the "how to use git" docs you men