Re: port upgrade outdated hangs networking

2022-01-15 Thread Ruben Di Battista
I had something similar happening to me across Wireguard VPN and it was an
MTU mismatch.

On Sat, 15 Jan 2022, 17:57 ,  wrote:

> This is extraordinary .. it presumably is a bug in MacOS.
>
> Running MacOS 10.15.7  on MacBook Pro 2016
>
> I am updating various already installed packges in the usual way:
> sudo port upgrade outdated
>
> Everything goes along fine until the software reached gd2.
> I then see:
>
> --->  Fetching archive for gd2
> --->  Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2 from
> https://packages.macports.org/gd2
> --->  Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2 from
> https://nue.de.packages.macports.org/gd2
> --->  Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2 from
> https://ema.uk.packages.macports.org/gd2
> --->  Fetching distfiles for gd2
>
> At this point the networking on the machine hangs.
> I cannot kill the port process. I cannot reach the
> offending machine even by ping; I cannot use
> the network from another terminal nor browser.
>
> Obviously, this is not a problem with Macports (is it?)
> I mean, how can an attempt to retrieve a package from
> some remote location actually hang my networking.
>
> This problem is completely replicable on my machine. I reboot the machine
> and everything is back to normal. Then fire up port again
> .. get same messages as above.. then hangs again. I
> have tried waiting for two hours before retrying --
> same result. I have tried it on a different box
> but that package was not needed. I will work on it
> further tests.
>
> It seems wildly improbable, but has anyone else experienced
> this or anything like it? I am completely baffled.
> (Except for one thing: the quality of MacOS has been in decline
> now since the demise of Jobs)
>
> Rob Stevens
>


Re: The installed version of macFUSE is too old for the operating system

2021-11-03 Thread Ruben Di Battista
Later versions are available only in binary form.

On a related note, there was a discussion about adding "binary only" ports
or variants  for this specific requirement at least, where sources are not
available. Was it finalized?

On Wed, 3 Nov 2021, 19:29 André-John Mas,  wrote:

> Ah, it looks like this the latest version and not ready:
>
> https://github.com/osxfuse/osxfuse/issues/821
>
> > On 3 Nov, 2021, at 14:19, André-John Mas 
> wrote:
> >
> > Hi,
> >
> > I am wanting to use ext4fuse, on macOS 12.0, so installed it via `sudo
> port ext4fuse` and then tried running:
> >
> > sudo ext4fuse /dev/disk2s2 ~/tmp/MY_DISK_PARTITION -o allow_other
> >
> > A dialogue popped up, saying:
> >
> >> The installed version of macFUSE is too old for the operating system.
> Please upgrade your macFUSE installation to one that is compatible with the
> currently running version of macOS.
> >
> > The version of macfuse that got installed was 4.2.1_0
> >
> > Any ideas?
> >
> > Thanks
> >
> > Andre
>
>


Re: Conflicty between MacPorts and Anaconda

2021-09-01 Thread Ruben Di Battista
Conda sera the prompt to help you remembering your within a conda
environment. It makes some sort of sense.

But the aggressive environment messing up, for me, is unacceptable. :)

On Wed, 1 Sep 2021, 11:48 Gerben Wierda via macports-users, <
macports-users@lists.macports.org> wrote:

> What happened was that I used bash, and my env was set in .profile,
> including my PATH setting for MacPorts. What Anaconda did was create a
> .bash_profile and the existence of that file prevents .profile to be read.
> Hence MacPorts commands are not available anymore in the shell.
>
> conda did a lot more (e.g. setting prompt) which I don’t want.
>
> Gerben Wierda (LinkedIn )
> R Enterprise Architecture  (main site)
> Book: Chess and the Art of Enterprise Architecture
> 
> Book: Mastering ArchiMate 
>
> On 31 Aug 2021, at 17:39, Mircea Trandafir  wrote:
>
> I have anaconda and Macports installed side-by-side, with different
> versions of python in each of them. It all runs smoothly, so it can be
> done. And I also have MacTeX installed separately, again without any issues
> with interaction with anaconda. As Ryan said, we need more information to
> figure out what is the problem with your setup.
>
> --
> Mircea Trandafir
> Associate professor
> Department of Business and Economics
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Email: mircea.tranda...@sam.sdu.dk
> Web: http://www.mirceatrandafir.com
>
> On Aug 31, 2021, at 12:54 PM, Ryan Schmidt 
> wrote:
>
> On Aug 30, 2021, at 09:32, Gerben Wierda wrote:
>
>
> I had to install Anaconda (Python environment) to collaborate with
> someone. I installed, but it adapted my shell environment in such a way
> that I’ve lost MacPorts (and LMTX ConTeXt). Does anybody have experience
> with the combination of Anaconda and MacPorts and what the correct way is
> to use them side by side?
>
>
> I don't know anything about Anaconda...
>
> When you say you've "lost MacPorts" does that mean that when you type
> "port" something it says the command is not found? If so, that means that
> your PATH environment variable is not set up correctly. When you installed
> MacPorts, it edited your shell startup script (which varies depending on
> which SHELL you are using) to add the MacPorts paths /opt/local/bin and
> /opt/local/sbin to PATH, while preserving any other additions you made.
> Maybe the Anaconda installer also modified the PATH in that same shell
> startup file but did not preserve your other PATH modifications. Or if you
> are using the Bash shell, which supports I think three possible startup
> files, maybe Anaconda edited a different one, one which takes precedence
> and causes Bash to ignore the other startup file that contained your
> MacPorts PATH settings.
>
>
>


Re: Specify port for file dependency

2021-08-30 Thread Ruben Di Battista
Yeah, no thanks for your help. I appreciate!

What I meant is at runtime, on the command line.

How do I tell "I want to install gdl3, but using `pango-devel` to provide
libpango instead of `pango`?

I might install pango-devel manually, but that would make pango-devel a
requested port.

On Mon, 30 Aug 2021, 23:17 Kurt Hindenburg, 
wrote:

> I may have misunderstood the question.  You would need to alter the
> Portfile if it doesn’t have the ability to use pango-devel.  What port are
> you trying to install?
>
> Kurt
>
> On Aug 30, 2021, at 5:10 PM, Kurt Hindenburg 
> wrote:
>
> Hi, lilypond uses this below although I’ve not tested it.
>
> # Either 'pango' or 'pango-devel' will do, thus we depend on its
> # pkgconfig file.
> depends_lib-append  path:lib/pkgconfig/pango.pc:pango \
>
>
>
> Kurt
>
> On Aug 30, 2021, at 2:45 PM, Ruben Di Battista 
> wrote:
>
> Let’s assume I want to install a port that depends on pango via a file
> dependency. How do I tell Macports to use `pango-devel` instead of `pango`?
>
>  _
> -. .´  |
>  ',  ;|∞∞
>˜˜ |∞ RdB | https://rdb.is
>,.,|∞∞
>  .'   '.  |
> -'   `’
>
>
>
>


Specify port for file dependency

2021-08-30 Thread Ruben Di Battista
Let’s assume I want to install a port that depends on pango via a file 
dependency. How do I tell Macports to use `pango-devel` instead of `pango`?
  
  _   
-. .´  | 
  ',  ;|∞∞ 
˜˜ |∞ RdB | https://rdb.is
,.,|∞∞ 
  .'   '.  | 
-'   `’



Re: Conflicty between MacPorts and Anaconda

2021-08-30 Thread Ruben Di Battista
(for easier virtualenv management and dep tracking there's poetry, that's
amazing)

On Mon, 30 Aug 2021, 17:52 Ruben Di Battista, 
wrote:

> /rant on
>
> Here we are again. I've been ranting on Twitter about this so much! Almost
> 80% of the problems I need to troubleshoot in my HPC team are associated to
> people installing Anaconda, that messes up the user environment, and
> forgetting that they did it. Anaconda messes up also when building things
> outside of conda, I've been scratching my head so many times in front of
> obscure linking errors with mismatching hdf5 libraries.
>
> My 2c: trash anaconda. Use your system package manager to install the
> minimum Python environment that allows you to use virtualenvs.
>
> Then use an individual virtualenv per project. This isolates your
> environment and its up to you to activate it when you need it. Nowadays
> most of big HPC libraries ship pre-built wheels, and if they don't, they
> should IMHO.
>
> It's not as battery included as conda related to compiled extensions, but
> you'll end up saving time because errors are more clear identifiable, and
> there's not weird environment pollution happening.
>
> /rant off
>
>
> On Mon, 30 Aug 2021, 16:33 Gerben Wierda via macports-users, <
> macports-users@lists.macports.org> wrote:
>
>> I had to install Anaconda (Python environment) to collaborate with
>> someone. I installed, but it adapted my shell environment in such a way
>> that I’ve lost MacPorts (and LMTX ConTeXt). Does anybody have experience
>> with the combination of Anaconda and MacPorts and what the correct way is
>> to use them side by side?
>>
>> Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
>> R Enterprise Architecture <https://ea.rna.nl/> (main site)
>> Book: Chess and the Art of Enterprise Architecture
>> <https://ea.rna.nl/the-book/>
>> Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
>>
>>
>>


Re: Conflicty between MacPorts and Anaconda

2021-08-30 Thread Ruben Di Battista
/rant on

Here we are again. I've been ranting on Twitter about this so much! Almost
80% of the problems I need to troubleshoot in my HPC team are associated to
people installing Anaconda, that messes up the user environment, and
forgetting that they did it. Anaconda messes up also when building things
outside of conda, I've been scratching my head so many times in front of
obscure linking errors with mismatching hdf5 libraries.

My 2c: trash anaconda. Use your system package manager to install the
minimum Python environment that allows you to use virtualenvs.

Then use an individual virtualenv per project. This isolates your
environment and its up to you to activate it when you need it. Nowadays
most of big HPC libraries ship pre-built wheels, and if they don't, they
should IMHO.

It's not as battery included as conda related to compiled extensions, but
you'll end up saving time because errors are more clear identifiable, and
there's not weird environment pollution happening.

/rant off


On Mon, 30 Aug 2021, 16:33 Gerben Wierda via macports-users, <
macports-users@lists.macports.org> wrote:

> I had to install Anaconda (Python environment) to collaborate with
> someone. I installed, but it adapted my shell environment in such a way
> that I’ve lost MacPorts (and LMTX ConTeXt). Does anybody have experience
> with the combination of Anaconda and MacPorts and what the correct way is
> to use them side by side?
>
> Gerben Wierda (LinkedIn )
> R Enterprise Architecture  (main site)
> Book: Chess and the Art of Enterprise Architecture
> 
> Book: Mastering ArchiMate 
>
>
>


Re: "port install meld" does not yield working executable

2021-03-16 Thread Ruben Di Battista
Are you up to date with the ports?

- sudo port selfupdate
- sudo port upgrade outdated

On Tue, Mar 16, 2021 at 7:47 PM joerg van den hoff 
wrote:

>
>
> On 16.03.21 19:41, Ruben Di Battista wrote:
> > If you run `port notes dbus` it should tell you how to enable the service
> > in launchd if I'm not mistaken.
>
> thanks. the notes say
>
> "sudo port load dbus" should start the service(s).
>
> I have done that right now but it did not solve the issue with `meld'...
> :(. the error message is
> now reduced to
>
> "** (meld:70489): WARNING **: 19:46:07.080: Failed to load shared library
> './gtksourceview/libgtksourceview-4.0.dylib' referenced by the typelib:
> dlopen(./gtksourceview/libgtksourceview-4.0.dylib, 9): image not found
> Meld requires GtkSourceView 4.0 or higher.
> "
>
> so, indeed, the dbus related complaint went away (but unfortunately w/o
> solving the issue).
>
> >
> > I haven't the Mac available right now, otherwise I'll give you the
> command
> > that I don't remember by heat
> >
> > (Please keep the discussion in the list replying to all...)
>
> right, sorry. my fault...
> >
> >
> > On Tue, 16 Mar 2021, 19:31 joerg van den hoff, 
> wrote:
> >
> >>
> >>
> >> On 16.03.21 19:24, Ruben Di Battista wrote:
> >>> Did you enable dbus as per its notes?
> >>
> >> that was fast... :). no, I did not. didn't see any notes either. you
> mean
> >> "notes of dbus" rather
> >> than "meld" I presume? if dbus installed/updated recently during some
> >> larger `port upgrade outdated'
> >> run, I must have overlooked those notes.
> >>
> >> how can I find those? or what do I need to do?
> >>
> >>>
> >>> On Tue, 16 Mar 2021, 19:23 joerg van den hoff, 
> >> wrote:
> >>>
> >>>> after "port install meld", on trying to start the program I get on the
> >>>> command line from which it is
> >>>> started the message
> >>>>
> >>>> "
> >>>> dbus[70231]: Dynamic session lookup supported but failed: launchd did
> >> not
> >>>> provide a socket path,
> >>>> verify that org.freedesktop.dbus-session.plist is loaded!
> >>>>
> >>>> ** (meld:70231): WARNING **: 18:11:03.149: Failed to load shared
> library
> >>>> './gtksourceview/libgtksourceview-4.0.dylib' referenced by the
> typelib:
> >>>> dlopen(./gtksourceview/libgtksourceview-4.0.dylib, 9): image not found
> >>>> Meld requires GtkSourceView 4.0 or higher.
> >>>> "
> >>>>
> >>>> and a small pop up window from the `meld' GUI telling "Meld requires
> >>>> GtkSourceView 4.0 or higher."
> >>>>
> >>>> `port installed' lists
> >>>>
> >>>>  gtksourceview4 @4.8.0_0+x11 (active)
> >>>>
> >>>>
> >>>> I don't understand the
> >>>>
> >>>> dbus[70231]: Dynamic session lookup supported but failed: launchd did
> >> not
> >>>> provide a socket path,
> >>>> verify that org.freedesktop.dbus-session.plist is loaded!
> >>>>
> >>>> hint nor what I can do about it.
> >>>>
> >>>> seen with 10.15.7 and current MacPorts.
> >>>>
> >>>> any ideas?
> >>>>
> >>>> thx/joerg
> >>>>
> >>>
> >>
> >
>


-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜   |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is


Re: "port install meld" does not yield working executable

2021-03-16 Thread Ruben Di Battista
If you run `port notes dbus` it should tell you how to enable the service
in launchd if I'm not mistaken.

I haven't the Mac available right now, otherwise I'll give you the command
that I don't remember by heat

(Please keep the discussion in the list replying to all...)


On Tue, 16 Mar 2021, 19:31 joerg van den hoff,  wrote:

>
>
> On 16.03.21 19:24, Ruben Di Battista wrote:
> > Did you enable dbus as per its notes?
>
> that was fast... :). no, I did not. didn't see any notes either. you mean
> "notes of dbus" rather
> than "meld" I presume? if dbus installed/updated recently during some
> larger `port upgrade outdated'
> run, I must have overlooked those notes.
>
> how can I find those? or what do I need to do?
>
> >
> > On Tue, 16 Mar 2021, 19:23 joerg van den hoff, 
> wrote:
> >
> >> after "port install meld", on trying to start the program I get on the
> >> command line from which it is
> >> started the message
> >>
> >> "
> >> dbus[70231]: Dynamic session lookup supported but failed: launchd did
> not
> >> provide a socket path,
> >> verify that org.freedesktop.dbus-session.plist is loaded!
> >>
> >> ** (meld:70231): WARNING **: 18:11:03.149: Failed to load shared library
> >> './gtksourceview/libgtksourceview-4.0.dylib' referenced by the typelib:
> >> dlopen(./gtksourceview/libgtksourceview-4.0.dylib, 9): image not found
> >> Meld requires GtkSourceView 4.0 or higher.
> >> "
> >>
> >> and a small pop up window from the `meld' GUI telling "Meld requires
> >> GtkSourceView 4.0 or higher."
> >>
> >> `port installed' lists
> >>
> >> gtksourceview4 @4.8.0_0+x11 (active)
> >>
> >>
> >> I don't understand the
> >>
> >> dbus[70231]: Dynamic session lookup supported but failed: launchd did
> not
> >> provide a socket path,
> >> verify that org.freedesktop.dbus-session.plist is loaded!
> >>
> >> hint nor what I can do about it.
> >>
> >> seen with 10.15.7 and current MacPorts.
> >>
> >> any ideas?
> >>
> >> thx/joerg
> >>
> >
>


Re: "port install meld" does not yield working executable

2021-03-16 Thread Ruben Di Battista
Did you enable dbus as per its notes?

On Tue, 16 Mar 2021, 19:23 joerg van den hoff,  wrote:

> after "port install meld", on trying to start the program I get on the
> command line from which it is
> started the message
>
> "
> dbus[70231]: Dynamic session lookup supported but failed: launchd did not
> provide a socket path,
> verify that org.freedesktop.dbus-session.plist is loaded!
>
> ** (meld:70231): WARNING **: 18:11:03.149: Failed to load shared library
> './gtksourceview/libgtksourceview-4.0.dylib' referenced by the typelib:
> dlopen(./gtksourceview/libgtksourceview-4.0.dylib, 9): image not found
> Meld requires GtkSourceView 4.0 or higher.
> "
>
> and a small pop up window from the `meld' GUI telling "Meld requires
> GtkSourceView 4.0 or higher."
>
> `port installed' lists
>
>gtksourceview4 @4.8.0_0+x11 (active)
>
>
> I don't understand the
>
> dbus[70231]: Dynamic session lookup supported but failed: launchd did not
> provide a socket path,
> verify that org.freedesktop.dbus-session.plist is loaded!
>
> hint nor what I can do about it.
>
> seen with 10.15.7 and current MacPorts.
>
> any ideas?
>
> thx/joerg
>


Re: How to search by package name

2021-01-24 Thread Ruben Di Battista
https://guide.macports.org/chunked/using.html

Here you can find tips on how to tune your regex. You can use a regex
expression matching just the port name

port search --name --line --regex 'sed$’

This returns all the ports ending with *sed.

Notably, what are you looking for, I guess, is gsed, i.e. GNU sed.



-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’
https://rdb.is


On 25 January 2021 at 00:50:58, Tong Sun (suntong...@gmail.com) wrote:

How to do a post search by package name?

I tried

port search sed

and astonished to find out it has "gazillion" of hits, :)


BTW, can any confirm that sed is indeed not in macport pls?

thx!


Re: Desolate Condition

2021-01-24 Thread Ruben Di Battista
What do you mean?

100% of the ports I'm using (969) are building correctly.

Do you have a specific problem with a port? Open a Ticket! :)

On Mon, Jan 25, 2021 at 12:05 AM Tom  wrote:

> MacPorts is in a desolate condition.
> Nearly nothing is building.
> Can somebody try to build everything and fix the errors?
>


-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜   |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is


Re: Qt

2020-12-29 Thread Ruben Di Battista
Hello Tom,

theoretically the QT5 ports are building correctly. Can you maybe
provide more information?

* What's your Macports version?
* What's your macOs version?
* Can you attach the build log?

On Tue, Dec 29, 2020 at 8:38 PM Tom  wrote:
>
> Hello,
>
> is there a qt port, which ist building?
> All I have tried so far, are not building.
>
> Regards



-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜   |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is


Re: Removing all non-requested ports?

2020-12-03 Thread Ruben Di Battista
`port_cutleaves`?

I think you need to install it.

`port info port_cutleaves`

  _
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’
https://rdb.is


On 3 December 2020 at 10:09:09, Michael (keybou...@gmail.com) wrote:

What's the command to remove non-requested ports again?


I keep getting the warning about CLT

2020-10-17 Thread Ruben Di Battista
Hello,

I keep getting the error described here:
https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt.

I reinstall the CLT, but it lasts until the next Xcode update. Is there a
way to fix it definitely?

  _
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’
https://rdb.is


Re: port select --set gcc not symlinking `cc` command

2020-10-14 Thread Ruben Di Battista
Ok, thanks Ryan. Any specific show stoppers? Or the reason for not
fixing it is just lack of time and low priority?

On Wed, Oct 14, 2020 at 11:30 AM Ryan Schmidt  wrote:
>
> On Oct 13, 2020, at 08:38, Ruben Di Battista wrote:
>
> > I just passed a week to solve a compiler error
> > (https://github.com/mutationpp/Mutationpp/issues/143#issuecomment-707742157)
> > associated to the fact that when selecting GCC as compiler with
> > Macports, the `cc` command does not get symlinked.
> >
> > Is this a feature or it is a bug?
>
> It is intentional that "sudo port select gcc" does not symlink cc.
>
> https://trac.macports.org/ticket/30434
>
> It is a bug that "sudo port select gcc" symlinks c++.
>
> https://trac.macports.org/ticket/48647
>


-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜   |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is


Re: Failure to upgrade outdated

2020-09-29 Thread Ruben Di Battista
I think there's no need. It's just that you had a very outdated port
collection. So if you do a `port rev-upgrade` and nothing strange pops
out, you should be good to go!

On Tue, Sep 29, 2020 at 11:42 PM list_email--- via macports-users
 wrote:
>
> I finally am able to run "port upgrade outdated" without problems, or at 
> least it reports “Nothing to upgrade,” thanks to a bit of off-list help from 
> Ruben.
>
> Here is the result I got, followed by an invitation to tile a ticket, perhaps 
> 25 times for different ports:
>
> --->  Computing dependencies for libgcc10
> --->  Fetching archive for libgcc10
> --->  Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2 from 
> https://packages.macports.org/libgcc10
> --->  Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/libgcc10
> --->  Installing libgcc10 @10.2.0_1
> --->  Activating libgcc10 @10.2.0_1
> Error: Failed to activate libgcc10: Image error: 
> /opt/local/lib/libgcc/libatomic.1.dylib is being used by the active libgcc 
> port.  Please deactivate this port first, or use 'port -f activate libgcc10' 
> to force the activation.
>
> Each time I did "port -f activate foo” I repeated the "port upgrade outdated" 
> command plus a few other things at other times.
>
> Should I file a ticket for this?
>
> Jerry
>
>
> > On Sep 26, 2020, at 10:49 PM, list_email--- via macports-users 
> >  wrote:
> >
> >
> >> On Sep 26, 2020, at 7:06 AM, Ruben Di Battista  
> >> wrote:
> >>
> >> Mh, I think that `pstoedit` port should depend on 
> >> `texlive-latex-recommended`. So try to install it (or upgrade it) before, 
> >> and then try again.
> >>
> >
> > I tried that. Here is an abbreviated copy-paste from Terminal with the 
> > current log file attached. After my efforts it seems that things ended 
> > pretty much the same way.
> >
> > Jerry
> >
> > 
> >
> >
> >
> > == Abbreviated Terminal Session 
> > ==
> >
> > sudo port upgrade texlive-latex-recommended
> > .
> > .
> > .
> > Error: Failed to build pstoedit: command execution failed
> > Error: See 
> > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_pstoedit/pstoedit/main.log
> >  for details.
> >
> > port install texlive-latex-recommended
> > .
> > .
> > .
> > --->  Activating texlive-latex-recommended @54586_0+doc
> > Error: Failed to activate texlive-latex-recommended: Image error: 
> > /opt/local/share/texmf-texlive/tex/latex/unicode-math/unicode-math-luatex.sty
> >  is being used by the active texlive-math-extra port.  Please deactivate 
> > this port first, or use 'port -f activate texlive-latex-recommended' to 
> > force the activation.
> > Error: See 
> > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_tex_texlive-latex-recommended/texlive-latex-recommended/main.log
> >  for details.
> > Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> > Error: Processing of port texlive-latex-recommended failed
> >
> > port -f activate texlive-latex-recommended
> > .
> > .
> > .
> > port upgrade outdated
> > .
> > .
> > .
> >
> > --->  Building pstoedit
> > Error: Failed to build pstoedit: command execution failed
> > Error: See 
> > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_pstoedit/pstoedit/main.log
> >  for details.
> >
>


-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜   |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is


Re: Failure to upgrade outdated

2020-09-26 Thread Ruben Di Battista
Mh, I think that `pstoedit` port should depend on
`texlive-latex-recommended`. So try to install it (or upgrade it) before,
and then try again.


  _
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’
https://rdb.is


On 26 September 2020 at 00:57:39, list_email--- via macports-users (
macports-users@lists.macports.org) wrote:

Thank you, Christopher and Ruben.

I repeated versions of port -f activate xxx 15 times each followed by
another port upgrade outdated and was hopeful that the process would
eventually succeed. However, I have now encountered the following
situation:


---> Computing dependencies for pstoedit
---> Fetching archive for pstoedit
---> Attempting to fetch pstoedit-3.75_1.darwin_15.x86_64.tbz2 from
https://packages.macports.org/pstoedit
---> Attempting to fetch pstoedit-3.75_1.darwin_15.x86_64.tbz2 from
https://ywg.ca.packages.macports.org/mirror/macports/packages/pstoedit/pstoedit
---> Attempting to fetch pstoedit-3.75_1.darwin_15.x86_64.tbz2 from
https://mse.uk.packages.macports.org/pstoedit
---> Fetching distfiles for pstoedit
---> Attempting to fetch pstoedit-3.75.tar.gz from
http://phoenixnap.dl.sourceforge.net/project/pstoedit/pstoedit/3.75
---> Verifying checksums for pstoedit
---> Extracting pstoedit
---> Applying patches to pstoedit
---> Configuring pstoedit
---> Building pstoedit
Error: Failed to build pstoedit: command execution failed
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_pstoedit/pstoedit/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.


Here attached is the indicated log. I’m sorry that I don’t understand all
of the intricacies involved here.

Should I try another port upgrade outdated?

Jerry




> On Sep 23, 2020, at 4:18 AM, Christopher Jones 
wrote:
>
> Hi,
>
> The error
>
> Error: Failed to activate libgcc10: Image error:
/opt/local/lib/libgcc/libatomic.1.dylib is being used by the active libgcc
port. Please deactivate this port first, or use 'port -f activate
>
> tells me its really been a very very long time since the ports where last
updated here. Not updating your ports regularly is really not recommended
as it can lead to problems like this when you do.
>
> try
>
> sudo port -f deactivate libgcc
>
> ignore the warning, then try updating again.
>
> Chris
>
>> On 23 Sep 2020, at 12:12 pm, Ruben Di Battista 
wrote:
>>
>> Did you already tried to do what it suggest?
>>
>> ```
>> Please deactivate this port first, or use 'port -f activate libgcc10' to
force the activation.
>> ```
>> So deactivate the libgcc port and run the upgrade again?
>> On Wed, 23 Sep 2020, 12:43 list_email--- via macports-users, <
macports-users@lists.macports.org> wrote:
>> I had not changed anything in my Macports installation for a long time.
Then I got to messing around with AquaTerm and something in the linking
stage kept crashing, so naturally I decided to freshen up my MacPorts
set-up. Here’s what happened. I have no idea what to do.
>>
>> macOS 10.11.6
>>
>> Thanks for any help.
>>
>> Jerry
>>
>>
>> MBPro-2:Aquaterm_Downloaded_September_2020 me$ sudo port selfupdate
>> Password:
>> ---> Updating MacPorts base sources using rsync
>> MacPorts base version 2.6.2 installed,
>> MacPorts base version 2.6.3 downloaded.
>> ---> Updating the ports tree
>> ---> MacPorts base is outdated, installing new version 2.6.3
>> Warning: Disabling readline support due to readline in /usr/local
>> Installing new MacPorts release in /opt/local as root:admin; permissions
0755
>>
>>
>> The ports tree has been updated. To upgrade your installed ports, you
should run
>> port upgrade outdated
>> You haven't run 'sudo port reclaim' in two weeks. It's recommended you
run this regularly to reclaim disk space. Would you like to run it now?
[Y/n]: n
>> MBPro-2:Aquaterm_Downloaded_September_2020 me$ port upgrade outdated
>> Error: Insufficient privileges to write to MacPorts install prefix.
>> MBPro-2:Aquaterm_Downloaded_September_2020 me$ sudo port upgrade
outdated
>> Password:
>> ---> Computing dependencies for libgcc10
>> ---> Fetching archive for libgcc10
>> ---> Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2 from
https://packages.macports.org/libgcc10
>> ---> Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2.rmd160
from https://packages.macports.org/libgcc10
>> ---> Installing libgcc10 @10.2.0_1
>> ---> Activating libgcc10 @10.2.0_1
>> Error: Failed to activate libgcc10: Image error:
/opt/local/lib/libgc

Re: ImageMagick port outdated

2020-09-25 Thread Ruben Di Battista
Moreover, HEIC format seems to be included here:
https://github.com/macports/macports-ports/pull/6021

Are there any problems?

On Fri, Sep 25, 2020 at 5:58 PM Ruben Di Battista
 wrote:
>
> Hello Christoph,
>
> here's there's a discussion about version 7:
> https://github.com/macports/macports-ports/pull/5014 and here
> https://trac.macports.org/ticket/51310. It probably will be provided
> as a separate port.
>
> On Fri, Sep 25, 2020 at 5:40 PM Christoph Kukulies  wrote:
> >
> > I was seeking for a means to convert Apples new HEIC/HEIF format to more 
> > traditional formats and I always remembered  ImageMagick being a good 
> > choice for that.
> > Unfortunately the macports version is quite outdated.
> > 6.9.11-29
> >
> > vs. 7.0.10-30 being the latest.
> >
> > How can I get a newer version via macports?
> >
> > —
> > Christoph
> >
>
>
> --
>   _
> -. .´  |
>   ',  ;|∞∞
> ˜˜   |∞ RdB
> ,.,|∞∞
>   .'   '.  |
> -'   `'
> https://rdb.is



-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜   |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is


Re: ImageMagick port outdated

2020-09-25 Thread Ruben Di Battista
Hello Christoph,

here's there's a discussion about version 7:
https://github.com/macports/macports-ports/pull/5014 and here
https://trac.macports.org/ticket/51310. It probably will be provided
as a separate port.

On Fri, Sep 25, 2020 at 5:40 PM Christoph Kukulies  wrote:
>
> I was seeking for a means to convert Apples new HEIC/HEIF format to more 
> traditional formats and I always remembered  ImageMagick being a good choice 
> for that.
> Unfortunately the macports version is quite outdated.
> 6.9.11-29
>
> vs. 7.0.10-30 being the latest.
>
> How can I get a newer version via macports?
>
> —
> Christoph
>


-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜   |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is


Re: Apple ARM binary codesign issue

2020-09-24 Thread Ruben Di Battista
Ok, that's what I didn't know. I thought It was mandatory for Apple Store
software and not everything... 

On Thu, 24 Sep 2020, 13:35 Ryan Schmidt,  wrote:

> On Sep 23, 2020, at 03:37, Ruben Di Battista wrote:
>
> > Can't be an easier choice to push globally  a linker switch, if it
> exists, to disable codesigning altogether for MP software?
>
> macOS 11 on ARM now require codesigning. Binaries that are not codesigned
> cannot be used at all.
>
>


Re: Failure to upgrade outdated

2020-09-23 Thread Ruben Di Battista
Did you already tried to do what it suggest?

```
Please deactivate this port first, or use 'port -f activate libgcc10' to
force the activation.
```
So deactivate the libgcc port and run the upgrade again?
On Wed, 23 Sep 2020, 12:43 list_email--- via macports-users, <
macports-users@lists.macports.org> wrote:

> I had not changed anything in my Macports installation for a long time.
> Then I got to messing around with AquaTerm and something in the linking
> stage kept crashing, so naturally I decided to freshen up my MacPorts
> set-up. Here’s what happened. I have no idea what to do.
>
> macOS 10.11.6
>
> Thanks for any help.
>
> Jerry
>
>
> MBPro-2:Aquaterm_Downloaded_September_2020 me$ sudo port selfupdate
> Password:
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.6.2 installed,
> MacPorts base version 2.6.3 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is outdated, installing new version 2.6.3
> Warning: Disabling readline support due to readline in /usr/local
> Installing new MacPorts release in /opt/local as root:admin; permissions
> 0755
>
>
> The ports tree has been updated. To upgrade your installed ports, you
> should run
>   port upgrade outdated
> You haven't run 'sudo port reclaim' in two weeks. It's recommended you run
> this regularly to reclaim disk space. Would you like to run it now? [Y/n]: n
> MBPro-2:Aquaterm_Downloaded_September_2020 me$ port upgrade outdated
> Error: Insufficient privileges to write to MacPorts install prefix.
> MBPro-2:Aquaterm_Downloaded_September_2020 me$ sudo port upgrade outdated
> Password:
> --->  Computing dependencies for libgcc10
> --->  Fetching archive for libgcc10
> --->  Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2 from
> https://packages.macports.org/libgcc10
> --->  Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2.rmd160
> from https://packages.macports.org/libgcc10
> --->  Installing libgcc10 @10.2.0_1
> --->  Activating libgcc10 @10.2.0_1
> Error: Failed to activate libgcc10: Image error:
> /opt/local/lib/libgcc/libatomic.1.dylib is being used by the active libgcc
> port.  Please deactivate this port first, or use 'port -f activate
> libgcc10' to force the activation.
> Error: See
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc10/libgcc10/main.log
> for details.
> Error: Problem while installing libgcc10
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> MBPro-2:Aquaterm_Downloaded_September_2020 me$
>
>


Re: Apple ARM binary codesign issue

2020-09-23 Thread Ruben Di Battista
Can't be an easier choice to push globally  a linker switch, if it exists,
to disable codesigning altogether for MP software?

On Wed, 23 Sep 2020, 03:09 Saagar Jha,  wrote:

> As far as I understand, ad-hoc codesigning is not actually really meant to
> protect a file on disk because you can just ad-hoc sign again when you
> modify the file; instead it simplifies some of Apple’s own code because it
> removes the special case of a binary that doesn’t have a signature (which
> until now has had a number of quirks and extra checks throughout the
> operating system). A more cynical interpretation would be that Apple would
> like to flip the switch to “paid developer account-signed software only” at
> some point in the future, but every engineer has denied that this is the
> goal when asked so I guess that if this will happen it hopefully won’t be
> anytime soon.
>
> I am still unsure why ld adds a signature but strip and install_name_tool
> don’t reapply an ad-hoc signature to a signed binary that they modify. This
> might be worth filing a feedback for.
>
> > On Sep 22, 2020, at 15:24, Ken Cunningham <
> ken.cunningham.web...@gmail.com> wrote:
> >
> >
> > On 2020-09-22, at 12:58 PM, Ryan Schmidt wrote:
> >>
> >> To me it seems unrealistic for Apple to suggest that an infinite number
> of open source projects, many of whose developers have never seen a Mac,
> should now add code to their build systems to codesign things on macOS.
> Apple made a point of stating during WWDC that they love open source
> software; imposing busy work on the open source community is not a good way
> to show that love.
> >
> > As I read it, the linker automatically codesigns the binary when you
> link, which is usually the final step in the process. So nobody has to
> change anything there.
> >
> > But if you later modify that final linked binary by stripping it (I
> guess ) or changing the libraries around with install_name_tool (which I
> believe MESON does to every single install :>)  then you invalidate the
> signature, as you should IMHO.
> >
> > I'm trying to imagine how Jeremy might prevent hackers from
> surreptitiously modifying signed binaries with strip or install_name_tool
> (which is good) while letting people modify signed binaries with strip or
> install_name_tool without invalidating the signature  -- I don't
> immediately see how you can have it both ways. But maybe Jeremy has some
> trick that works for this I can't think of.
> >
> > I won't be surprised if the solution is that you have to resign them
> after doing that, though.
> >
> > Ken
> >
>
>


Re: Weird GNUPLOT problem (but *not* just Gnuplot)

2020-09-13 Thread Ruben Di Battista
Ehi Dave,

Did you try to launch the binary from the terminal and see which errors it
spits out?

On Sun, 13 Sep 2020, 10:07 Dave Horsfall,  wrote:

> No replies?  Am I the only person on the planet having this problem?
>
> It's not confined to Gnuplot, but pretty much anything that wants to save
> a modified file, such as TextEdit (such as my prescriptions, which for me
> is pretty much a matter of life and death).
>
> I note that this crap only started happening after last Monday's weekly
> update; up until then, my MacBook had performed flawlessly...  Could the
> perp responsible please raise their hand?
>
> Should I back out that flawed update (if I can remember how) and stop
> doing any further updates until I am assured that they will actually work
> i.e. they were actually tested?  For some reason the Therac-25 (look it
> up; it's the story of an untested software update that went horribly
> wrong) springs to mind...
>
> What can I do to provide more information?  Whoever in Cupertino is
> receiving the crash reports when I abort the hung processes must be
> getting pretty sick of them by now, and that's not looking too good for
> MacPorts...
>
> Excuse my attitude, but after nearly 50 years in the IT game (probably
> longer than most people on this list have been alive) I've never seen
> anything like this.
>
> On Thu, 10 Sep 2020, Dave Horsfall wrote:
>
> > MacBook Pro (early) with Sierra (all updates); can't be more precise
> than
> > that because "About This Mac" is no longer displaying anything (SMC
> reset
> > required?) since a reboot, but that's not my immediate problem.
> >
> > Gnuplot Version 5.2 patchlevel 8last modified 2019-12-01
> >
> > When trying to save a graph (any graph) I get as far as "Save As" and I
> get
> > the dreaded spinning beachball instead of the file selection; I've
> waited up
> > to an hour before killing it by doing in AquaTerm.  This started
> happening
> > after my Monday "port upgrade outdated", so I'm guessing that I now have
> a
> > bad library somewhere as a result of the upgrade?  There were a few
> library
> > updates, as I recall...
> >
> > I'm trying to figure out whether this is a Mac/Gnuplot problem or a user
> > error, so I'm wondering whether others have seen this before I report it
> as a
> > possible Gnuplot bug (but I can't see how it could be, because it wasn't
> > touched as such).
> >
> > Thanks (and yeah, I have a few outstanding replies to follow up)
> >
> > -- Dave
> >
>
> -- Dave
>


Re: On building poppler

2020-04-12 Thread Ruben Di Battista
Hi Dave, 

That is standard practice. I don’t know the real reason for it, didn’t bother 
to investigate, but you just need to follow what is written there: that is 
deactivating Poppler before upgrading it. 

`sudo port -f deactivate popper`
`sudo port upgrade popper`.

I guess it is a safety measure to avoid breaking running programs? I guess.  
Here: https://trac.macports.org/ticket/58574 there’s probably the long answer 
to that :)

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is

On 12 April 2020 at 23:02:11, Dave Horsfall (d...@horsfall.org) wrote:

Error: poppler cannot be built while another version of poppler is active. 
Error: Please forcibly deactivate the existing copy of poppler, e.g. by 
running: 

signature.asc
Description: Message signed with OpenPGP using AMPGpg


Different environment (apparently) calling make from python subprocess

2020-04-12 Thread Ruben Di Battista
I just discovered this anomaly: https://bugs.python.org/issue40261. TL, DR: if 
I run a `make` command from within a subprocess, the build of Python from 
source behaves differently and breaks.

Could any of you try the step to reproduce and see if he/she is getting the 
same weird behavior I’m getting? 

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is


signature.asc
Description: Message signed with OpenPGP using AMPGpg


Re: Strange behaviour of subprocess_check_output with Macports Python in virtualenv

2020-03-13 Thread Ruben Di Battista
The problem has been solved with the updated of virtualenv, that is
currently in a PR for Macports. 

On Fri, 13 Mar 2020, 00:09 Ryan Schmidt,  wrote:

> I am dropping macports-dev from Cc because the question is not about
> developing MacPorts.
>
> On Feb 7, 2020, at 18:42, Ruben Di Battista wrote:
>
> > Hello,
> > I’m experiencing a problem (
> https://github.com/davidhalter/jedi/issues/1375).
> >
> > Running this on a Python installed with Macports:
> > ```
> > Python 3.8.1 (default, Feb  8 2020, 01:33:23)
> > [Clang 11.0.0 (clang-1100.0.33.16)] on darwin
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import subprocess
> > >>>
> subprocess.check_output('/Users/rubendibattista/.envs/josiepy-B4k-0ZyT/bin/python
> -c "import sys; print(sys.executable)"', shell=True)
> > b'/opt/local/bin/python\n'
> >
> > ```
> >
> > I get as result the system python executable and not the one from the
> virtualenv (created using pew).
> > While on Linux:
> >
> > ```
> > Python 3.7.3 (default, Jun  7 2019, 17:57:55)
> > [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import subprocess
> > >>>
> subprocess.check_output('/home/ruben.di-battista/.envs/josiepy/bin/python
> -c "import sys; print(sys.executable)"', shell=True)
> > b'/home/ruben.di-battista/.envs/josiepy/bin/python\n'
> >
> > ```
> >
> > Does it work for you? Is it a bug from Macports, from my particular
> configuration, from macOs or from Python build on macOs? (Or isn’t a bug?)
>
> I am not very familiar with Python and I do not have any virtualenv. I can
> however offer this result from my High Sierra system:
>
>
> $ /opt/local/bin/python3.8
> Python 3.8.2 (default, Mar  2 2020, 03:10:15)
> [Clang 9.1.0 (clang-902.0.39.2)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import subprocess
> >>> subprocess.check_output('/opt/local/bin/python3.7 -c "import sys;
> print(sys.executable)"', shell=True)
> b'/opt/local/bin/python3.7\n'
> >>> ^D
>
>
> In other words, that seems to be working correctly.
>
> Possibly relevant is that I do not have /opt/local/bin/python. If you have
> it, what is it, and do you still experience the same problem if you remove
> it?
>
>


Re: Call for contributors to macOS port of GDB

2020-02-15 Thread Ruben Di Battista
I mean, I guess you just need a registrar with an API for setting DNS records 
and a Python script to get your own DDNS service. I did for OVH, for example: 
https://pypi.org/project/ovh-dynhost/ ^^

But I guess we’re going off topic...

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is

On 15 February 2020 at 20:29:02, Jeffrey Walton (noloa...@gmail.com) wrote:

On Sat, Feb 15, 2020 at 2:12 PM Dave Horsfall  wrote:  
>  
> On Fri, 14 Feb 2020, Jeffrey Walton wrote:  
>  
> > Send over your SSH authroized_keys file, if interested. I'll send you  
> > my IP address in return.  
>  
> It's been a while since I had to set up keys, but shouldn't you be asking  
> for his public key to add to *your* authorized_keys file?  

No, someone who wishes remote access collects their public keys and  
puts them in an authorized_keys file. Then, I drop them at  
/.ssh/authorized_keys.  

Usually what happens is someone sends me a *.pub file and it gets  
cat'd into ssh/authorized_keys.  

> > The downside is, I am in a Verizon DHCP block. You will need to ping me  
> > on occasion to get my latest IP address.  
>  
> That's what dynamic DNS is for... There are various servers offering it.  

Sorry, I don't use DDNS services.  

I tried one about 15 years ago. They sold or shared my information  
with Network Solutions, which would not stop spamming me. I tried to  
get off their list for about 5 years. I tried normal support channels,  
like contacting webmaster@, postmaster@, NS legal department, NS  
support, NS executive support, Better Business Bureau complaints, FCC  
complaints and FTC complaints. I finally had to take Network Solutions  
to court to get off their damn list. Checkout Walton vs Network  
Solutions filed in Montgomery County, MD.  

I'll be damned if I go down that road again.  

Jeff  


signature.asc
Description: Message signed with OpenPGP using AMPGpg


Strange behaviour of subprocess_check_output with Macports Python in virtualenv

2020-02-07 Thread Ruben Di Battista
Hello, 
I’m experiencing a problem (https://github.com/davidhalter/jedi/issues/1375). 

Running this on a Python installed with Macports: 
```
Python 3.8.1 (default, Feb  8 2020, 01:33:23)
[Clang 11.0.0 (clang-1100.0.33.16)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> subprocess.check_output('/Users/rubendibattista/.envs/josiepy-B4k-0ZyT/bin/python
>>>  -c "import sys; print(sys.executable)"', shell=True)
b'/opt/local/bin/python\n'
```

I get as result the system python executable and not the one from the 
virtualenv (created using pew). 
While on Linux: 

```
Python 3.7.3 (default, Jun  7 2019, 17:57:55)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> subprocess.check_output('/home/ruben.di-battista/.envs/josiepy/bin/python 
>>> -c "import sys; print(sys.executable)"', shell=True)
b'/home/ruben.di-battista/.envs/josiepy/bin/python\n'
```

Does it work for you? Is it a bug from Macports, from my particular 
configuration, from macOs or from Python build on macOs? (Or isn’t a bug?)
  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is


signature.asc
Description: Message signed with OpenPGP using AMPGpg


Re: Configuring Python3 on MacOS Macports

2019-12-02 Thread Ruben Di Battista
I still need to release my muscle memory .

(in reality I don't use bare virtualenv but more pew and pipenv that I
believe use venv for Python 3)

On Tue, 3 Dec 2019, 01:42 Ralph Seichter,  wrote:

> * Ruben Di Battista:
>
> > What I suggest you is to use virtualenvs.
>
> Good advice.
>
> > * Install py-virtualenv
>
> That's not required anymore. Python 3.3 and newer have virtual
> environment support built in[1].
>
> [1] https://docs.python.org/3/library/venv.html
>
> -Ralph
>


Re: Configuring Python3 on MacOS Macports

2019-12-02 Thread Ruben Di Battista
Wait wait wait wait...

Why are you doing the `python setup.py` thing? I strongly discourage you to
use the system python to install packages globally.

What I suggest you is to use virtualenvs.

* Install py-virtualenv
* Create virtualenv
* Activate  the virtual environment
* Install things locally to the virtual env using pip
* Deactivate when finished


This way you create isolated environments for each one of your applications
without messing up with the system packages. You can then delete them if
you don't need them anymore without the fear of destroying everything... :)

There are also other tools to make this even more pleasant (pew, pipenv).


On Mon, 2 Dec 2019, 19:51 Forrest,  wrote:

> I'm new to Python and I'm trying to figure out why, for example, when I
> install aws-cli (from source) using Macports, it doesn't install
> properly vs /usr/bin/python that does the right thing and places the
> commands in proper places.   When I run "/opt/local/bin/python setup.py
> install" it ends up buried in directories under the Macports directory
> structure, which isn't usable.   Maybe I am missing some ENV variables?
>
>
>
> F
>
>


Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Ruben Di Battista
Ehi Mojca, 

Thanks for the message. :)

I managed to fix it. I got confused because recently I updated Xcode, but in 
facts the problem was completely unrelated: I had a project header file named 
“math.h”. :) Very noob mistake! Interestingly enough, this bug does not pop-out 
on Linux (using GCC). 

So I just renamed “math.h” to a custom name, and now everything is back as 
before (Ah, pay attention! Most of macOS systems have a case-insensitive 
filesystem… I firstly renamed the file from “math.h” -> “Math.h”, but it didn’t 
work either and it took a while to realize that on macOS “math.h” and “Math.h” 
are the same if the FS is case-insensitive. 

In any case thanks for your help! :)

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is

On 8 November 2019 at 18:32:13, Mojca Miklavec (mo...@macports.org) wrote:

Dear Ruben,  

This definitely looks like a bug in Xcode. I would suggest you to file  
a bug report to Apple.  

Can you please try to compile a simple hello world with just the  
following contents  

// test.cpp:  
#include   
int main() { return 0; }  

and compile it with:  
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
  
test.cpp \  
-isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
  

Mojca  

On Fri, 8 Nov 2019 at 15:27, Ruben Di Battista  
 wrote:  
>  
> Hello people,  
>  
> I saw this kind of errors quite often lately around. But this times I’m 
> hitting this with a local project, not a port in Macports. A project that 
> used to build correctly with Xcode 10, now it seems to miss stuff in  
> header.  
>  
> ninja -j 1  
> [1/48] Building CXX object src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o 
>  
> FAILED: src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o  
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
>  -DMercurve_EXPORTS -I../src/libs -isystem /opt/local/include/vtk-8.1 
> -isystem /opt/local/include -isystem /opt/local/include/mpich-mp -isystem 
> /opt/local/include/libxml2 -g -isysroot 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
>  -mmacosx-version-min=10.14 -fPIC -Wall -Wno-long-long -pedantic 
> -fcolor-diagnostics -std=gnu++11 -MD -MT 
> src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o -MF 
> src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o.d -o 
> src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o -c 
> ../src/libs/BlockMerger.cxx  
> In file included from ../src/libs/BlockMerger.cxx:21:  
> In file included from ../src/libs/BlockMerger.h:28:  
> In file included from ../src/libs/types.h:25:  
> In file included from 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/unordered_set:363:
>   
> In file included from 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/__hash_table:19:
>   
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:314:9:
>  error: no member named 'signbit' in the global namespace  
> […]  
>  
> I read a bit the tickets of other ports, but they don’t fit exactly with what 
> I have. Any fast hint? Do I need to downgrade Xcode?  
>  
> _  
> -. .´ |  
> ', ; |∞∞  
> ˜˜ |∞ RdB  
> ,., |∞∞  
> .' '. |  
> -' `’  
>  
> https://rdb.is  


signature.asc
Description: Message signed with OpenPGP using AMPGpg


XCode 11 on Mojave problem, again

2019-11-08 Thread Ruben Di Battista
Hello people, 

I saw this kind of errors quite often lately around. But this times I’m hitting 
this with a local project, not a port in Macports. A project that used to build 
correctly with Xcode 10, now it seems to miss stuff in  header.

ninja -j 1
[1/48] Building CXX object src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o
FAILED: src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
  -DMercurve_EXPORTS -I../src/libs -isystem /opt/local/include/vtk-8.1 -isystem 
/opt/local/include -isystem /opt/local/include/mpich-mp -isystem 
/opt/local/include/libxml2 -g -isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
 -mmacosx-version-min=10.14 -fPIC   -Wall -Wno-long-long -pedantic 
-fcolor-diagnostics -std=gnu++11 -MD -MT 
src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o -MF 
src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o.d -o 
src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o -c 
../src/libs/BlockMerger.cxx
In file included from ../src/libs/BlockMerger.cxx:21:
In file included from ../src/libs/BlockMerger.h:28:
In file included from ../src/libs/types.h:25:
In file included from 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/unordered_set:363:
In file included from 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/__hash_table:19:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:314:9:
 error: no member named 'signbit' in the global namespace
[…]

I read a bit the tickets of other ports, but they don’t fit exactly with what I 
have. Any fast hint? Do I need to downgrade Xcode?

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is


signature.asc
Description: Message signed with OpenPGP using AMPGpg


Re: Private ports

2019-09-25 Thread Ruben Di Battista
Yes, easiest thing is to provide a folder containing the ports you need to ship 
(even better a git repository) as a Local Portfile Repository. You’ll need to 
edit the /opt/local/etc/macports/sources.conf in order to tell macports to look 
for ports there before. 

Is this what you were looking for?

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is

On 26 September 2019 at 00:01:52, Watson Ladd (watsonbl...@gmail.com) wrote:

I'm wondering if it is possible to distribute software using Macports only 
within a company.

Sincereley,
Watson



signature.asc
Description: Message signed with OpenPGP using AMPGpg


Re: MacPorts and Anaconda

2019-08-12 Thread Ruben Di Battista
This can be applied also to virtualenv. What you need to do, imho, is to
just create conda envs. They're isolated from system interpreters and they
should not collide with anything. In these envs you can install whatever
you want... And keep it from interfering with system packages...



On Mon, 12 Aug 2019, 07:55 Fielding, Eric J (US 329A) via macports-users, <
macports-users@lists.macports.org> wrote:

> I saw the discussion the last few days about the problems with using both
> HomeBrew and MacPorts on the same system. I was wondering about problems
> with using MacPorts and Anaconda to install different packages. I have been
> using MacPorts for a long time with few problems, but sometimes I need
> newer versions of Python packages or I need to install something that is
> available as a conda package. It seems that Anaconda is specifically
> designed to keep separate copies of the things it needs and switch between
> environments, so I assume that there should be fewer problems with MacPorts
> than using something like HomeBrew.
>
>
>
> Thanks,
>
> ++Eric
>
> Pasadena, California
>


Re: apache2 error: failed to open stream...Failed opening required '/opt/local/var/db/php70/pear/pear-ini.php...

2019-04-09 Thread Ruben Di Battista
Wrong permissions on the `pear-ini.php`?

Just guessing, 

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is

On 9 April 2019 at 19:01:56, Murray Eisenberg (murrayeisenb...@gmail.com) wrote:

I’m reinstalling MacPorts 2.5.4 under macOS Mojave 10.14.4 (on a new Mac) to 
which I migrated my old MacPorts config files for apache, php, mysql, etc.

After starting apache2 (apache2 @2.4.39_0+preforkmpm) and php73-apache2handler 
@7.3.3_0 along with ports they required, syntax of httpd.conf checks out OK:

/opt/local/sbin/apachectl -t
Syntax OK

However, when I start apache (sudo /opt/local/sbin/apachectl -k start and 
browse to localhost (or 127.0.0.1) I get error page:

Warning: Unknown: failed to open stream: No such file or directory in Unknown 
on line 0

Fatal error: Unknown: Failed opening required 
'/opt/local/var/db/php70/pear/pear-ini.php' (include_path='.:') in Unknown on 
line 0

What might be the error’s cause?

My httpd.conf file (with many ommented-out lines removed) appears below.

== BEGIN httpd.conf ==
#
# This is the main Apache HTTP server configuration file.  It contains the ...
#
ServerRoot "/opt/local"

Listen 80

# Dynamic Shared Object (DSO) Support
#
LoadModule authn_file_module lib/apache2/modules/mod_authn_file.so
LoadModule authn_core_module lib/apache2/modules/mod_authn_core.so
LoadModule authz_host_module lib/apache2/modules/mod_authz_host.so
LoadModule authz_groupfile_module lib/apache2/modules/mod_authz_groupfile.so
LoadModule authz_user_module lib/apache2/modules/mod_authz_user.so
LoadModule authz_core_module lib/apache2/modules/mod_authz_core.so
LoadModule access_compat_module lib/apache2/modules/mod_access_compat.so
LoadModule auth_basic_module lib/apache2/modules/mod_auth_basic.so
LoadModule reqtimeout_module lib/apache2/modules/mod_reqtimeout.so
LoadModule include_module lib/apache2/modules/mod_include.so
LoadModule filter_module lib/apache2/modules/mod_filter.so
LoadModule mime_module lib/apache2/modules/mod_mime.so
LoadModule log_config_module lib/apache2/modules/mod_log_config.so
LoadModule env_module lib/apache2/modules/mod_env.so
LoadModule mime_magic_module lib/apache2/modules/mod_mime_magic.so
LoadModule headers_module lib/apache2/modules/mod_headers.so
LoadModule setenvif_module lib/apache2/modules/mod_setenvif.so
LoadModule version_module lib/apache2/modules/mod_version.so
LoadModule proxy_module lib/apache2/modules/mod_proxy.so
LoadModule slotmem_shm_module lib/apache2/modules/mod_slotmem_shm.so
LoadModule ssl_module lib/apache2/modules/mod_ssl.so
LoadModule unixd_module lib/apache2/modules/mod_unixd.so
LoadModule status_module lib/apache2/modules/mod_status.so
LoadModule autoindex_module lib/apache2/modules/mod_autoindex.so
LoadModule vhost_alias_module lib/apache2/modules/mod_vhost_alias.so
LoadModule negotiation_module lib/apache2/modules/mod_negotiation.so
LoadModule dir_module lib/apache2/modules/mod_dir.so
LoadModule userdir_module lib/apache2/modules/mod_userdir.so
LoadModule alias_module lib/apache2/modules/mod_alias.so
LoadModule rewrite_module lib/apache2/modules/mod_rewrite.so
LoadModule socache_shmcb_module lib/apache2/modules/mod_socache_shmcb.so
LoadModule php7_module  lib/apache2/modules/mod_php73.so
LoadModule apreq_module lib/apache2/modules/mod_apreq2.so
LoadModule perl_module  lib/apache2/modules/mod_perl.so


User daemon
Group daemon



# 'Main' server configuration

# ServerAdmin someb...@somewhere.com

ServerName localhost


    AllowOverride none
    Require all denied


DocumentRoot "/opt/local/www/apache2/html"

    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted



    DirectoryIndex index.php index.html



    Require all denied



    Order allow,deny
    Deny from all
    Satisfy All


    Order allow,deny
    Deny from all
    Satisfy All


    Order allow,deny
    Deny from all
    Satisfy All


## For MathJax

    Options Indexes FollowSymlinks
    AllowOverride None
    Order allow,deny
    Allow from all
    AddDefaultCharset off


Alias /MathJax /usr/local/share/MathJax/
#
ErrorLog "var/log/apache2/error_log"
LogLevel warn


    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" 
combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" 
%I %O" combinedio
    

    CustomLog "var/log/apache2/access_log" common




    ScriptAlias /cgi-bin/ "/opt/local/www/apache2/cgi-bin/"




    AllowOverride None
    Options None
    Require all granted



    RequestHeader unset Proxy early




    TypesConfig etc/apache2/mime.types

    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    AddHandler application/x-httpd-php .php
    AddHandler application/x-httpd-php-source .phps

 

MIMEMagicFile etc/apache2/magic

# Fancy directory 

Re: A general philosophical question about MacPorts

2019-02-20 Thread Ruben Di Battista
To complement people answer, and most of all, "Why macOS"? Well, because
there is not another Unix laptop that is as efficiently implemented. For
example, take a Windows laptop, put Linux on it, and see your battery life
drop at least of 15-20%. Well, i hate it. On my macOS I have very good
battery life with basically 99% of Linux software compiled with the help of
MacPorts.

Using a VM workflow is really a no-go for me. So laggy and time consuming.
And really, macOS is really beautiful to use and agile. The gestures are
really time saving and they're already there without pindaric flights among
Windows Managers bugs and configurations on Linux (I could achieve
something similarly agile with ArchLinux + KDE Plasma 5, but I needed to
tweak quite a lot)


On Wed, Feb 20, 2019 at 10:28 AM Riccardo Mottola via macports-users <
macports-users@lists.macports.org> wrote:

> Hi,
>
> Bill Cole wrote:
> > Because running the tools it provides in a VM is a grotesque waste of
> > RAM and disk space and puts a wall up between tools I want to use
> > occasionally and the UI where I prefer to work mostly.
>
> I second that, for me a VM is a waste and only the "last possible mean".
> Except of course if you need VM to have many different environments and
> don't want to have a multi-boot or a multi-machine setup.
>
> >
> > Also, on one old 1st generation Core Duo iMac, it helps me to build
> > and run a suite of server software and other key tools that can face
> > the Internet with reasonable safety and an attack surface that doesn't
> > quite look like any other machine while seeming irresistible to a
> > certain class of miscreants. I have a professional interest in the
> > unique behavioral intelligence I get from that machine that I cannot
> > get anywhere else. It would be a serious chore to maintain that host
> > as 'live bait' without MacPorts and I hate the idea of just discarding
> > a machine that would otherwise have no practical use.
>
> Right, MacPorts provides also an excellent way for having older Macs
> running, since it allows to get current software compiled for your
> system when perhaps a binary is not provided, to get updated
> dependencies, etc.
> Having e.g. gcc 6.5 and clang on Leopard or Snow Leopard is jsut
> excellent and can be both your goal (if you want to develop) or a tool
> to geto other applications you need.
> So are up-to-date svn and git clients!
>
> Using Gimp natively is just nice, isn't it?
>
> Riccardo
>


-- 
  _
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `'
https://rdb.is 


Re: cc/gcc programming - where are the includes?

2018-12-19 Thread Ruben Di Battista
If you are using the compiler by hand in the command line, you can set the
CPATH env variable to point to the include directory...
(/opt/local/include)

Even if the system headers should be included by default if I'm not
mistaken.



On Wed, 19 Dec 2018, 09:33 Christoph Kukulies  Does it require a special package to be installed when one wants to
> develop under cc or gcc in macOS?
>
> I was writing a little C program starting with
>
> #include 
>
> and the compiler doesn’t find anything (what I would be normally under
> /usr/include
>
> —
> Christoph
>
>


Re: mpi headers for armadillo

2018-12-04 Thread Ruben Di Battista
I don't know if it's a good example but I added the hdf5 variant to vtk
that works as expected with all the variants of mpi. Could you maybe try to
take inspiration from that?

Il giorno mar 4 dic 2018, 14:25 Marius Schamschula 
ha scritto:

> Hi all,
>
> In the PR armadillo: fix error with hdf5 +openmpi [1], we want to fix an
> issue where hdf5 has been installed with some flavor of mpi. The suggested
> patch works only for openmpi, but not it’s many sub-ports. The same issue
> exists for mpich.
>
> I’m looking for a general way to extract the path to mpi.h for the active
> variant of mpi, rather than hard coding each sub-port (as they constantly
> change, as new compilers become available).
>
> TIA
>
>
> [1] https://github.com/macports/macports-ports/pull/3102
>
> Marius
> --
> Marius Schamschula
>
>
>
>
>


Re: Gimp doesn't start

2018-11-28 Thread Ruben Di Battista
Open a new terninal and run `gimp` directly from the terminal and not from
the app directory... It's very strange.

Il giorno mer 28 nov 2018, 09:31 Christoph Kukulies  ha
scritto:

> OK, I did:
>
> Christophs-MBP:MacOS kuku$ sudo port install  gimp +quartz
> Warning: port definitions are more than two weeks old, consider updating
> them by running 'port selfupdate'.
> --->  Computing dependencies for gimp
> --->  Fetching archive for gimp
> Warning: Your DNS servers incorrectly claim to know the address of
> nonexistent hosts. This may cause checksum mismatches for some ports. See
> this page for more information: <
> https://trac.macports.org/wiki/MisbehavingServers>
> --->  Attempting to fetch gimp-2.10.6_0+quartz.darwin_18.noarch.tbz2 from
> https://packages.macports.org/gimp
> --->  Attempting to fetch gimp-2.10.6_0+quartz.darwin_18.noarch.tbz2 from
> http://nue.de.packages.macports.org/gimp
> --->  Attempting to fetch gimp-2.10.6_0+quartz.darwin_18.noarch.tbz2 from
> http://lil.fr.packages.macports.org/gimp
> --->  Fetching distfiles for gimp
> --->  Verifying checksums for gimp
> --->  Extracting gimp
> --->  Configuring gimp
> --->  Building gimp
> --->  Staging gimp into destroot
> --->  Installing gimp @2.10.6_0+quartz
> --->  Deactivating gimp @2.10.6_0
> --->  Cleaning gimp
> --->  Activating gimp @2.10.6_0+quartz
> --->  Cleaning gimp
> --->  Scanning binaries for linking errors
> --->  No broken files found.
> --->  No broken ports found.
>
> Same picture. Clicking on the Gimp icon in the launcher doesn’t result in
> anything happening and running the app ./GIMP gives the same error message.
>
>
> —
> Christoph
>
>
> Am 28.11.2018 um 09:23 schrieb Ruben Di Battista <
> rubendibatti...@gmail.com>:
>
> Try to install it with `+quartz` variant. I installed it like this on
> Mojave and it works as expected...
>
> Il giorno mer 28 nov 2018, 08:30 Christoph Kukulies 
> ha scritto:
>
>> I tried the following:
>>
>> Christophs-MBP:MacOS kuku$ pwd
>> /Applications/MacPorts/GIMP.app/Contents/MacOS
>> Christophs-MBP:MacOS kuku$ ls
>> GIMP
>> Christophs-MBP:MacOS kuku$ file GIMP
>> GIMP: Mach-O 64-bit executable x86_64
>> Christophs-MBP:MacOS kuku$ ./GIMP
>> 2018-11-28 08:23:18.176 GIMP[86714:1924234] Failed to connect
>> (cancelButton) outlet from (ScriptExecController) to (NSButton): missing
>> setter or instance variable
>> 2018-11-28 08:23:18.176 GIMP[86714:1924234] Failed to connect
>> (messageTextField) outlet from (ScriptExecController) to (NSTextField):
>> missing setter or instance variable
>> Anzeige kann nicht geöffnet werden:
>>
>>
>> This looks like similar to the usual „cannot open DISPLAY“ in X11
>>
>> I remember a lot of X11 dependencies being installed together with the
>> GIMP port.
>>
>> Well, when it would be so easy to just take the App from gimp.org, I’d
>> think it wouldn’t be worth scratching head with this
>> but OTOH, with having the whole port install being done already I might
>> be close to get it working.
>>
>>
>>
>> —
>> Christoph
>>
>> Am 28.11.2018 um 07:01 schrieb Nathan Brazil :
>>
>> Or, try downloading a native package from https://www.gimp.org/downloads/
>>
>> Btw, Gimp now runs natively on OS X, no X11 is required.
>>
>> —
>>
>> On Nov 27, 2018, at 6:34 AM, Vincent Habchi  wrote:
>>
>> macOS mojave 10.14.1.
>>
>> I did a port install gimp. In the end the icon is there in the Apps
>> launcher. Clicking on the icon results in nothing happening.
>>
>>
>> Try to launch it from Terminal and look for error messages.
>>
>> Say, like, typing a line like this at the prompt (note that “Gimp.app” is
>> a wild guess):
>>
>> /Applications/MacPorts/Gimp.app/Contents/MacOS/Gimp.app (use the TAB key
>> to trigger autocompletion)
>>
>> Also, did you install X11? I’m not 100% certain, but last time I checked
>> GIMP still needed X11 to run.
>>
>> V.
>>
>>
>>
>>
>


Re: Gimp doesn't start

2018-11-28 Thread Ruben Di Battista
Try to install it with `+quartz` variant. I installed it like this on
Mojave and it works as expected...

Il giorno mer 28 nov 2018, 08:30 Christoph Kukulies  ha
scritto:

> I tried the following:
>
> Christophs-MBP:MacOS kuku$ pwd
> /Applications/MacPorts/GIMP.app/Contents/MacOS
> Christophs-MBP:MacOS kuku$ ls
> GIMP
> Christophs-MBP:MacOS kuku$ file GIMP
> GIMP: Mach-O 64-bit executable x86_64
> Christophs-MBP:MacOS kuku$ ./GIMP
> 2018-11-28 08:23:18.176 GIMP[86714:1924234] Failed to connect
> (cancelButton) outlet from (ScriptExecController) to (NSButton): missing
> setter or instance variable
> 2018-11-28 08:23:18.176 GIMP[86714:1924234] Failed to connect
> (messageTextField) outlet from (ScriptExecController) to (NSTextField):
> missing setter or instance variable
> Anzeige kann nicht geöffnet werden:
>
>
> This looks like similar to the usual „cannot open DISPLAY“ in X11
>
> I remember a lot of X11 dependencies being installed together with the
> GIMP port.
>
> Well, when it would be so easy to just take the App from gimp.org, I’d
> think it wouldn’t be worth scratching head with this
> but OTOH, with having the whole port install being done already I might be
> close to get it working.
>
>
>
> —
> Christoph
>
> Am 28.11.2018 um 07:01 schrieb Nathan Brazil :
>
> Or, try downloading a native package from https://www.gimp.org/downloads/
>
> Btw, Gimp now runs natively on OS X, no X11 is required.
>
> —
>
> On Nov 27, 2018, at 6:34 AM, Vincent Habchi  wrote:
>
> macOS mojave 10.14.1.
>
> I did a port install gimp. In the end the icon is there in the Apps
> launcher. Clicking on the icon results in nothing happening.
>
>
> Try to launch it from Terminal and look for error messages.
>
> Say, like, typing a line like this at the prompt (note that “Gimp.app” is
> a wild guess):
>
> /Applications/MacPorts/Gimp.app/Contents/MacOS/Gimp.app (use the TAB key
> to trigger autocompletion)
>
> Also, did you install X11? I’m not 100% certain, but last time I checked
> GIMP still needed X11 to run.
>
> V.
>
>
>
>


inkscape +quartz 100% CPU all the time on Mojave

2018-11-25 Thread Ruben Di Battista
Hello, 
I just upgraded my OS to Mojave and installed all the ports. I’m encountering a 
problem with Inkscape. If I run it (both from terminal and app) it is very 
sluggish and it always gets 100% CPU. 

Any idea on how to debug this? 

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is


signature.asc
Description: Message signed with OpenPGP using AMPGpg