Re: Frescobaldi on MacOS 10.15 with MacPorts
> On 21 Oct 2019, at 01:24, Davide Liessi wrote: > > Il giorno sab 19 ott 2019 alle ore 20:31 Hans Åberg > ha scritto: >> Instead I experienced further corruption, and decided to reinstall the whole >> of MacPorts from scratch. I do not want to try it again. > > 10.15 is new, so it is expected that problems are being discovered in > these first weeks. > That said, the errors you had for librsvg and py37-poppler-qt5 (which > are now solved) cannot have corrupted your whole installation, so I am > inclined to believe there was some other (unrelated) problem with your > MacPorts installation. First xorg-server broke, and libxml2, and removing the latter and its dependencies also removed gcc9, so pretty much everything essential was gone. Unclear what caused it. https://trac.macports.org/ticket/59377 > I understand that you don't want to risk wasting more time, especially > now that a 10.15 builder is not available yet (so MacPorts needs to > compile everything on your machine). > Once the builder is in place, it will build all ports, which means > that most problems will be spotted and that most dependencies of > frescobaldi-devel will be available as prebuilt binary packages. > If at that (or any previous or later) point you want to try again, > feel free to contact me (on or off list) and let me know of any > problems. In MacPorts 2.6.1 and 2.6.2 there are now checksum errors for frescobaldi-.tar.gz. Also there is a somewhat mysterious call for 32-bit in the log file: :debug:sysinfo macOS 10.15 (darwin/19.0.0) arch i38 In addition, another X11 program is mysteriously slow on MacOS 10.15. So perhaps it is better to focus on the Application. The reason MacPorts came into focus for lilypond is that it is hard to get it otherwise. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frescobaldi on MacOS 10.15 with MacPorts
Il giorno sab 19 ott 2019 alle ore 20:31 Hans Åberg ha scritto: > Instead I experienced further corruption, and decided to reinstall the whole > of MacPorts from scratch. I do not want to try it again. 10.15 is new, so it is expected that problems are being discovered in these first weeks. That said, the errors you had for librsvg and py37-poppler-qt5 (which are now solved) cannot have corrupted your whole installation, so I am inclined to believe there was some other (unrelated) problem with your MacPorts installation. I understand that you don't want to risk wasting more time, especially now that a 10.15 builder is not available yet (so MacPorts needs to compile everything on your machine). Once the builder is in place, it will build all ports, which means that most problems will be spotted and that most dependencies of frescobaldi-devel will be available as prebuilt binary packages. If at that (or any previous or later) point you want to try again, feel free to contact me (on or off list) and let me know of any problems. Best wishes. Davide ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frescobaldi on MacOS 10.15 with MacPorts
> On 19 Oct 2019, at 19:53, Davide Liessi wrote:
>
> Dear Hans,
>
> Il giorno sab 19 ott 2019 alle ore 19:01 Hans Åberg
> ha scritto:
>> For some reason, MacPorts ‘port install frescobaldi-devel’ failed on MacOS
>> 10.15, and a ticket could not resolve it. So perhaps somebody here might
>> want giving it a try.
>
> I'm the maintainer of the frescobaldi{,-devel} ports and of its
> dependencies py-poppler-qt{4,5}.
> I have already committed a fix for your ticket
> https://trac.macports.org/ticket/59370 two days ago.
> Please update the port definitions, clean the failed port and try
> again to install frescobaldi-devel, i.e. run
>
> sudo port selfupdate
> sudo port clean py37-poppler-qt5
> sudo port install frescobaldi-devel
>
> (Cleaning the port should not be necessary, MacPorts should discard
> the previous build attempt since the port was changed, but cleaning it
> explicitly does no harm.)
It did not help.
> If the original problem persists, please report on the original ticket.
> If you encounter any other problems, please open corresponding tickets.
Instead I experienced further corruption, and decided to reinstall the whole of
MacPorts from scratch. I do not want to try it again.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Frescobaldi on MacOS 10.15 with MacPorts
Dear Hans,
Il giorno sab 19 ott 2019 alle ore 19:01 Hans Åberg
ha scritto:
> For some reason, MacPorts ‘port install frescobaldi-devel’ failed on MacOS
> 10.15, and a ticket could not resolve it. So perhaps somebody here might want
> giving it a try.
I'm the maintainer of the frescobaldi{,-devel} ports and of its
dependencies py-poppler-qt{4,5}.
I have already committed a fix for your ticket
https://trac.macports.org/ticket/59370 two days ago.
Please update the port definitions, clean the failed port and try
again to install frescobaldi-devel, i.e. run
sudo port selfupdate
sudo port clean py37-poppler-qt5
sudo port install frescobaldi-devel
(Cleaning the port should not be necessary, MacPorts should discard
the previous build attempt since the port was changed, but cleaning it
explicitly does no harm.)
If the original problem persists, please report on the original ticket.
If you encounter any other problems, please open corresponding tickets.
Best wishes.
Davide
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Frescobaldi on MacOS 10.15 with MacPorts
For some reason, MacPorts ‘port install frescobaldi-devel’ failed on MacOS 10.15, and a ticket could not resolve it. So perhaps somebody here might want giving it a try. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
