On Wednesday October 26 2016 00:25:14 Clemens Lang wrote:
Hi,
> The problem is that we don't see the difference. The code that procudes
> the error is more or less
> "source $filename"
> which can fail either because the file isn't there, or because the code
> in the file failed.
Yeah. There c
Hi,
On Wed, Oct 26, 2016 at 12:29:10AM +0200, René J.V. Bertin wrote:
> The issue I mentioned that I fixed was such an example of an
> oversight. I'd imposed the condition of reading a "companion"
> PortGroup from the same directory as the main PortGroup, and that
> condition cannot hold for copie
> On Oct 25, 2016, at 4:43 PM, René J.V. Bertin wrote:
>
> Where does one file tickets for trac?
In Trac.
vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Tuesday October 25 2016 17:06:27 Ryan Schmidt wrote:
Hi,
> > As such, Portfiles or PortGroups that haven't been written carefully can
> > trigger this warning from time to time. A common problem is checking for
> > the presence of a file, or running a tool, and not catching the errors.
>
> Ah
Hi,
On Tue, Oct 25, 2016 at 05:06:27PM -0500, Ryan Schmidt wrote:
> Ah. So the error message is just wrong? There isn't actually a problem
> opening the portfile from the registry; there's a problem running the
> portfile that was successfully opened and read?
Yes, unless of course you randomly d
> On Oct 25, 2016, at 5:04 PM, Clemens Lang wrote:
>
> Hi,
>
> On Tue, Oct 25, 2016 at 08:34:31AM -0500, Ryan Schmidt wrote:
>> I don't know the answers to your questions, but I wanted to mention
>> that I also have noticed the "Failed to open portfile from registry"
>> error far more often tha
Hi,
On Tue, Oct 25, 2016 at 08:34:31AM -0500, Ryan Schmidt wrote:
> I don't know the answers to your questions, but I wanted to mention
> that I also have noticed the "Failed to open portfile from registry"
> error far more often than seems normal to me. ("Never" would seem
> normal to me.)
Inter
On Sunday October 23 2016 17:43:56 Clemens Lang wrote:
> top bar. If you think those should be larger, feel free to suggest a
> patch to https://github.com/macports/trac.macports.org/.
Well, I'm not a web coder, so I'd prefer to file request tickets somewhere.
Also for the fact that nowadays I g
> On Oct 25, 2016, at 1:17 PM, René J.V. Bertin wrote:
>
> I've looked into putting the offending statement (`$workername eval set
> user_options($opt) $val`) in a loop, something like
>
> $workername eval set user_options($opt) ""
> foreach v $val {
>$workername eval set user_options($
> On Oct 25, 2016, at 12:17 PM, René J.V. Bertin wrote:
>
> On Tuesday October 25 2016 08:34:31 Ryan Schmidt wrote:
>
>> I don't know the answers to your questions, but I wanted to mention that I
>> also have noticed the "Failed to open portfile from registry" error far more
>> often than see
On Tuesday October 25 2016 08:34:31 Ryan Schmidt wrote:
>I don't know the answers to your questions, but I wanted to mention that I
>also have noticed the "Failed to open portfile from registry" error far more
>often than seems normal to me. ("Never" would seem normal to me.)
Yes, never would s
On Oct 24, 2016, at 2:31 PM, Rainer Müller wrote:
> Existing developers need to request to be added to this team by sending
> a mail to the macports-infra mailing list as instructed in the announcement.
of course, sorry I apparently can't read and follow directions :)
--
Daniel J. Luke
_
> On Oct 25, 2016, at 6:54 AM, Rainer Müller wrote:
>
> On 2016-10-25 10:36, Ryan Schmidt wrote:
>>
>>
>> On Oct 24, 2016, at 17:57, Clemens Lang wrote:
>>
On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
A description of how exactly one would rebase (potentially squas
> On Oct 25, 2016, at 7:30 AM, René J.V. Bertin wrote:
>
> I've been noticing "Failed to open portfile from registry" errors during
> certain operations like reinstalling (port -n upgrade --force).
I don't know the answers to your questions, but I wanted to mention that I also
have noticed th
Hi,
I've been noticing "Failed to open portfile from registry" errors during
certain operations like reinstalling (port -n upgrade --force). This turned out
due in part to something I changed in one of my own portgroups, but after
correcting that errors remained.
I've finally traced them down
On 2016-10-25 10:36, Ryan Schmidt wrote:
>
>
> On Oct 24, 2016, at 17:57, Clemens Lang wrote:
>
>>> On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
>>> A description of how exactly one would rebase (potentially squash and
>>> history-rewrite) a submitted PR onto current master sho
On Oct 24, 2016, at 17:57, Clemens Lang wrote:
>> On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
>> A description of how exactly one would rebase (potentially squash and
>> history-rewrite) a submitted PR onto current master should be on our
>> WorkingWithGit wiki page.
>
> the
17 matches
Mail list logo
