All,

Being the stupid can't-let-it-go idiot I am :-)

I have a working frescobaldi. I had to  download the latest popplerqt4 from
the poppler source. I did the bad thing and installed it over the old, but
I have a working frescobaldi and that's the important thing.

Thanks to all three of you for taking the time to look through my problem.
I *greatly* appreciate it.

Guy Stalnaker
jimmyg...@gmail.com


On Tue, Sep 17, 2013 at 12:26 AM, Philippe Massart <phili...@philmassart.net
> wrote:

> I had the same error a few weeks ago, before trying the frescobaldi port
> file. But, it occurred with the "manually installed" version of frescobaldi
> (more precisely: the "manually installed" version of python-poppler-qt4).
>
> The python-poppler-qt4 I had manually installed had been compiled a long
> time ago and didn't recognize the new versions of the Sip API (installed by
> macport). The solution was tho rebuild and re-install the "manually
> installed" python-poppler-qt4, but since your python-poppler-qt4 was
> successfully installed by macport, I guess the problem lies elsewhere.
>
> I'll continue to look at it.
>
> Philippe
>
> Le 17 sept. 2013 à 07:04, Guy Stalnaker <jimmyg...@gmail.com> a écrit :
>
> Well, this is certainly been an adventure. Sorry for the delay in
> acknowledging your and Davide's replies, but I've had to jettison using
> FileVault to regain space on the local harddrive. Somehow FileVault was
> holding 30Gb of space and refusing to release it, causing me no end of
> grief in downloading MacPort source and then compiling.
>
> So, finally, I have had to restart this from scratch. I'm afraid I was a
> bit rash in trying to troubleshoot the situation so your proffered solution
> cannot help (but you do describe what I did a year ago when I first
> installed Frescobaldi "python setup.py install"). What I've now done:
>
> 1. remove all traces (port uninstall/rm -rf) of poppler and frescobaldi
> 2. run "sudo port clean" to remove temp files, etc.
> 3. run "sudo port selfupdate" to get things up to date after the clean and
> FileVault issues (this took well over SIX hours -- good gawd)
> 4. run "sudo port install poppler +qt4 +quartz" which completed
> successfully
> 5. run "sudo port install frescobaldi-devel +app" which completed
> succefully
>
> But ...
>
> Frescobaldi crashes on startup:
>
> <quote>
> [Lots of traceback calls]
>     import popplerqt4
> RuntimeError: the sip module implements API v10.0 to v10.1 but the
> popplerqt4 module requires API v9.1
> </quote>
>
> "port installed" shows:
>
> <quote>
> Anorien% sudo port installed | grep sip
>   py27-sip @4.13.3_0
>   py27-sip @4.14.2_0
>   py27-sip @4.15.1_0 (active)
> Anorien [sudo port installed | grep sip] ~
>                                  13-09-16 10:45PM
> Anorien% sudo port installed | grep poppler
>   poppler @0.20.5_0+qt4+quartz
>   poppler @0.22.0_0+qt4+quartz
>   poppler @0.24.1_0+qt4+quartz (active)
>   poppler-data @0.4.6_0 (active)
>   py27-python-poppler-qt4 @0.16.3_1 (active)
> </quote>
>
> I cannot deactivate the active py27-sip or poppler. I get a dependency
> errors.
>
> <quote>
> Anorien% sudo port deactivate py27-sip @4.15.1_0
> Password:
> --->  Deactivating py27-sip @4.15.1_0
> --->  Unable to deactivate py27-sip @4.15.1_0, the following ports depend
> on it:
> --->    py27-pyqt4 @4.10.3_1
> --->    py27-python-poppler-qt4 @0.16.3_1
> ...
> Anorien% sudo port deactivate poppler @0.24.1_0+qt4+quartz
> --->  Deactivating poppler @0.24.1_0+qt4+quartz
> --->  Unable to deactivate poppler @0.24.1_0+qt4+quartz, the following
> ports depend on it:
> --->    py27-python-poppler-qt4 @0.16.3_1
> --->    texlive-bin @2013_2+x11
> </quote>
>
> I installed the non-devel frescobaldi and get the exact same error on
> running from terminal.
>
> I "port uninstalled" all old sip/poppler ports and both frescobaldi ports
> and reinstalled, but the API error persists. So I cannot remove it due to
> dependencies (the texlive dependency is especially weighty - there are
> *many* that arise if I try to remove texlive as well).
>
> Any ideas?
>
> <sigh>
>
> It's always frustrating when folks post at how it just works for them LOL
> This stuff never just works for me.
>
> Guy Stalnaker
> jimmyg...@gmail.com
>
>
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to