On Oct 27, 2015, at 6:07 PM, Marko Käning wrote:
>
> (When will Apple’s new admin have all those issues fixed I wonder…)
I am in communication with the admin and his manager about these issues. I
don't know how many details I should share right now but I hope to be able to
announce a solution
Thanks, Ryan,
On 28 Oct 2015, at 00:28 , Ryan Schmidt wrote:
> https://trac.macports.org/ticket/49305
for reminding me of that ticket.
Have subscribed to that and the one referenced in there as well.
Greets,
Marko
___
macports-dev mailing list
macpo
On Oct 27, 2015, at 3:04 PM, Marko Käning wrote:
> Just noticed that the waterfall doesn’t show recently committed changes to
> ports…
> … are the buildbots stuck?
Yes, as are other bits.
https://trac.macports.org/ticket/49305
___
macports-dev mai
Hi Mojca,
On 27 Oct 2015, at 23:30 , Mojca Miklavec wrote:
> On Tue, Oct 27, 2015 at 11:03 PM, Marko Käning wrote:
>> Should we forget about revbumping everything and simply rely on that the
>> sanity of our users’ MacPorts installations
>> will be taken care of by rev-upgrade?
>
> No. All por
On Tue, Oct 27, 2015 at 11:03 PM, Marko Käning wrote:
> On 27 Oct 2015, at 22:48 , Marko Käning wrote:
>
>> Answering my own question now, at least partially, since a rev-upgrade just
>> gave me this much longer list:
>
> Should we forget about revbumping everything and simply rely on that the
>
On 27 Oct 2015, at 22:48 , Marko Käning wrote:
> Answering my own question now, at least partially, since a rev-upgrade just
> gave me this much longer list:
Should we forget about revbumping everything and simply rely on that the sanity
of our users’ MacPorts installations
will be taken care
- On 27 Oct, 2015, at 19:56, Kurt Hindenburg khindenb...@macports.org wrote:
> I use ‘sudo port -t install xyz’ - Ok, now that I look at the output again
> perhaps I’m confused. It is the “not installed by a port” that has the “sip”.
>
> ---> Configuring coreutils
> Warning: The following
Answering my own question now, at least partially, since a rev-upgrade just
gave me this much longer list:
---
---> Found 38 broken port(s), determining rebuild order
---> Rebuilding in order
qtscriptgenerator @0.2.0
kdenlive @0.9.10
kdiff3 @0.9.98
litecoin @0.8.7.4
cerv
Hi Nicolas,
while building kdevelop and kdepim4 I came across some rev-upgrades… Thus I
have rebumped ports kate, libkgapi and konversation.
For instance, the latter tried to find libqca in it’s old location
---
Dyld Error Message:
Library not loaded: /opt/local/lib/libqca.2.dylib
Referenced
Just noticed that the waterfall doesn’t show recently committed changes to
ports…
… are the buildbots stuck?
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
> On Oct 27, 2015, at 2:18 PM, Clemens Lang wrote:
>
>
>
> - On 27 Oct, 2015, at 17:36, Kurt Hindenburg khindenb...@macports.org
> wrote:
>
>> Sorry perhaps I wasn’t clear
>>
>> The current output is :
>> /opt/local/var/macports/sip-workaround/502/usr/bin/perl5.18
>> I think should be :
- On 27 Oct, 2015, at 17:36, Kurt Hindenburg khindenb...@macports.org wrote:
> Sorry perhaps I wasn’t clear
>
> The current output is :
> /opt/local/var/macports/sip-workaround/502/usr/bin/perl5.18
> I think should be : /usr/bin/perl5.18
Yes, sounds like it. *Where* do you see the output,
> On Oct 27, 2015, at 12:24 PM, Clemens Lang wrote:
>
> Hey,
>
> - On 27 Oct, 2015, at 16:23, Kurt Hindenburg khindenb...@macports.org
> wrote:
>
>> The new trace seems to work fine. My only suggestion would be if you can
>> remove
>> “sip” part from the output.
>>
>> /opt/local/var/ma
Hey,
- On 27 Oct, 2015, at 16:23, Kurt Hindenburg khindenb...@macports.org wrote:
> The new trace seems to work fine. My only suggestion would be if you can
> remove
> “sip” part from the output.
>
> /opt/local/var/macports/sip-workaround/502/usr/bin/perl5.18 ->
> /usr/bin/perl5.18
Whe
> On Oct 24, 2015, at 11:45 AM, Clemens Lang wrote:
>
> Hi developers,
>
> if you are running MacPorts trunk on El Capitan, please make sure you're at
> the
> latest version and test trace mode. Originally, El Capitan's system integrity
> protection broke trace mode because all DYLD_* variable
15 matches
Mail list logo
