> On 13 Nov 2018, at 3:49 am, Uli Wienands wrote:
>
> Given Ryan's comment I updated my Macports installation (was 2.4.2, now:
> 2.5.4),
Thats a huge jump... if you also had not updated your ports for that period as
well, no surprise you are having problems now. Its really not a good idea t
Given Ryan's comment I updated my Macports installation (was 2.4.2, now:
2.5.4), cleaned gimp2 and tried again... same error. I do this on a
10.6.8 machine, incidentally.
So is there anything else I should/could do?
Log file attached.
Thanks,
Uli
On 11/12/18 12:52 PM, Ryan Schmidt wrote:
Thx.
I’ve since tried individual port installs and that seems to be working fine.
There seems to be a lot in myports.txt that won’t be needed in any case.
Ken G. Brown
> On Nov 12, 2018, at 17:32, Ryan Schmidt wrote:
>
>
>
>> On Nov 12, 2018, at 15:52, Ken G. Brown wrote:
>>
>> Following
On Nov 12, 2018, at 15:40, Dave Horsfall wrote:
> On Mon, 12 Nov 2018, Mojca Miklavec wrote:
>
>> Since you are talking about the optical drive and 10.6: is your
>
> I take it you mean 10.12.6 (Sierra)? The OS works fine, but Mojave is
> officially not supported on this model (and I couldn'
On Nov 12, 2018, at 15:09, Mojca Miklavec wrote:
> The fun thing
> is that once I finally decided to upgrade it, I could no longer even
> download 10.11.
There are knowledge base articles from which you can download older macOS
versions. Here's the one for 10.11:
https://support.apple.com/en
On Nov 12, 2018, at 15:52, Ken G. Brown wrote:
> Following https://trac.macports.org/wiki/Migration
>
> Got to sudo ./restore_ports.tcl myports.txt
> then:
>> sudo ./restore_ports.tcl myports.txt
>> Error: we appear to be stuck, exiting...
>> infinite loop
>>while executing
>> "sort_ports
On Nov 12, 2018, at 16:52, db wrote:
> On 12 Nov 2018, at 22:32, Ryan Schmidt wrote:
>> What we really want is a web site where this information can more easily be
>> seen.
>
>> I don't really want the public making massive numbers of http requests to
>> the buildmaster (which is what the sc
On 12 Nov 2018, at 22:32, Ryan Schmidt wrote:
> What we really want is a web site where this information can more easily be
> seen.
> I don't really want the public making massive numbers of http requests to the
> buildmaster (which is what the script would do)
I just want that every build rep
On Nov 12, 2018, at 15:50, Mojca Miklavec wrote:
> On Mon, 12 Nov 2018 at 22:32, Ryan Schmidt wrote:
>> On Nov 12, 2018, at 15:25, db wrote:
>>> On 11 Nov 2018, at 13:00, Ryan Schmidt wrote:
>>>
I'll probably need to write a script to pull all the failures out of the
buildbot logs,
Personally, I always recommend *not* using the ./restore_ports.tcl script but
instead look at the requested ports file you created, and then install by hand
those you still want. The problem with the restore script is it attempts to
restore everything, exactly was it was, which is not always wan
Following https://trac.macports.org/wiki/Migration
Got to sudo ./restore_ports.tcl myports.txt
then:
> sudo ./restore_ports.tcl myports.txt
> Error: we appear to be stuck, exiting...
> infinite loop
> while executing
> "sort_ports $portList"
> invoked from within
> "set operationList [sort
On Mon, 12 Nov 2018 at 22:32, Ryan Schmidt wrote:
> On Nov 12, 2018, at 15:25, db wrote:
> > On 11 Nov 2018, at 13:00, Ryan Schmidt wrote:
> >
> >> I'll probably need to write a script to pull all the failures out of the
> >> buildbot logs, since we don't have anything set up to do that yet. If
On Mon, 12 Nov 2018, Mojca Miklavec wrote:
Since you are talking about the optical drive and 10.6: is your
I take it you mean 10.12.6 (Sierra)? The OS works fine, but Mojave is
officially not supported on this model (and I couldn't install High
Sierra).
hardware even officially supported?
On Nov 12, 2018, at 15:25, db wrote:
> On 11 Nov 2018, at 13:00, Ryan Schmidt wrote:
>
>> I'll probably need to write a script to pull all the failures out of the
>> buildbot logs, since we don't have anything set up to do that yet. If there
>> are ports you want to use, check whether any is
On 11 Nov 2018, at 13:00, macports-users-requ...@lists.macports.org wrote:
> Message: 11
> Date: Sat, 10 Nov 2018 15:27:51 -0600
> From: Ryan Schmidt
> To: Dave Horsfall
> Cc: MacPorts Users
> Subject: Re: How Mojave-ready is MacPorts?
> Message-ID: <5035eaa0-bd67-48d0-aae3-57af03245...@macports
On Mon, 12 Nov 2018 at 21:34, Dave Horsfall wrote:
> On Mon, 12 Nov 2018, Ryan Schmidt wrote:
>
> >> So I see; well, it's served me well for nine years... I only upgrade
> >> hardware when forced to, so I guess it's time to put some of my pension
> >> aside for a MacBook Air or something.
> >
> >
On Mon, 12 Nov 2018, Ryan Schmidt wrote:
So I see; well, it's served me well for nine years... I only upgrade
hardware when forced to, so I guess it's time to put some of my pension
aside for a MacBook Air or something.
There are usually ways of shoehorning newer operating systems into
unsu
On Nov 12, 2018, at 04:52, Dr M J Carter wrote:
> On Sat, Nov 10, 2018 at 03:47:26PM -0600, Ryan Schmidt wrote:
>
>> The only file MacPorts always copies into its home directory is the
>> Xcode preferences plist.
>
> Quick note: on our 10.13 build systems, I find that that preferences
> file
On Nov 12, 2018, at 04:15, Dr M J Carterwrote:
>> I'm not aware of any changes in MacPorts specific to Mojave that
>> would relate to the handling of the home directory. So I think the
>> bug you're investigating is a bug in macOS or Xcode, not MacPorts.
>
> Possibly APFS? that test's pen
On Nov 11, 2018, at 14:36, Dave Horsfall wrote:
> On Sat, 10 Nov 2018, Bill Cole wrote:
>
>>> OK, I've been talked out of trying Mojave on this thing (it's unlikely to
>>> work)
>>
>> Indeed. https://support.apple.com/kb/SP777?locale=en_US says it definitely
>> won't.
>
> So I see; well, i
On Nov 12, 2018, at 11:24, Riccardo Mottola wrote:
>>> If I try to uninstall gegl:
>>> $ sudo port uninstall gegl
>>> Note: It is not recommended to uninstall/deactivate a port that has
>>> dependents as it breaks the dependents.
>>> The following ports will break: gimp2 @2.8.22_2
>>
>>> I wo
On 12 Nov 2018, at 12:24, Riccardo Mottola via macports-users wrote:
[...]
however… when it ends it says:
---> Uninstalling curl-ca-bundle @7.61.1_3
---> Building list of distfiles still in use
[] 86.8 %Warning: All
compilers are either blackl
On Nov 12, 2018, at 12:47, Uli Wienands wrote:
> Hi, after Riccardo Mottola mentioned that he contributed a patch to gimp to
> make Gimp 2.10 run under 10.6 I tried to install it.
>
> The install went a fair amount but then died at xorg-xorgproto, whatever that
> is, with the error:
>
> Err
Hi, after Riccardo Mottola mentioned that he contributed a patch to gimp
to make Gimp 2.10 run under 10.6 I tried to install it.
The install went a fair amount but then died at xorg-xorgproto, whatever
that is, with the error:
Error: Failed to activate xorg-xorgproto: Image error:
/opt/local
Hi Bill,
On 2018-11-12 17:03:56 +0100 Bill Cole
wrote:
>> how can I try uninstalling gegl-0.2 without causing issues? I notice it is
>> the active "gegl" without version suffix.
>
> Which would reflect a port maintenance bug, if you were using a current
> version of the ports tree. 'gegl' wi
In the meanwhile, I re-upgraded outdated and both gcc5 and 7 versions
incremented again and the problem disappeared. Did not touch cctools.
But a strange thing appeared : after upgrading, I did a uninstall inactive and
a number (15) of files which were declared as broken have been removed and
On 12 Nov 2018, at 8:57, Riccardo Mottola via macports-users wrote:
Hi,
On 2018-11-09 18:43:56 +0100 Ken Cunningham
wrote:
openexr was updated a few days ago
the new library version is /opt/local/lib/libIlmImf-2_3.24.dylib
it looks like gegl (gegl-0.2) is gone now. Not sure where or whe
Hi,
On 2018-11-09 18:43:56 +0100 Ken Cunningham
wrote:
openexr was updated a few days ago
the new library version is /opt/local/lib/libIlmImf-2_3.24.dylib
it looks like gegl (gegl-0.2) is gone now. Not sure where or when it
went.
there is gegl-0.3, gegl-.04, and gegl-devel.
You should
On Sat, Nov 10, 2018 at 03:47:26PM -0600, Ryan Schmidt wrote:
> The only file MacPorts always copies into its home directory is the
> Xcode preferences plist.
Quick note: on our 10.13 build systems, I find that that preferences
file has been saved in the clone of successful nightly builds, but is
On Sat, Nov 10, 2018 at 03:47:26PM -0600, Ryan Schmidt wrote:
> Since it sounds like you have some kind of Heisenbug that disappears
> under later analysis, I'd suggest adding any analysis you can to the
> script you're running when it fails.
I'm attempting to do that, but with thin results so fa
On Fri, Nov 09, 2018 at 01:01:42PM -0500, Bill Cole wrote:
> Those imply protection by Apple's SIP *or* BSD file flags.
That's my suspicion too.
> What does 'ls -lORa /opt/local/var/macports/home/' tell you about flags?
> (the field after the group, will be '-' if no flags are set.)
Absolutely n
31 matches
Mail list logo
