Proposed update to OpenSSH

A tentative macports/macports-ports PR #3835 to update OpenSSH to version 7.9p1 has been submitted to help move forward Chih-Hsuan Yen’s PR #3822 to update OpenSSL to version 1.1.1b. Per discussion on MacPorts Trac , patches to update both gsskex and hpn

Re: quick Tcl globbing question: excluding lib*.[0-9.]*.dylib

On Jun 15, 2018, at 1:39 PM, René J.V. Bertin wrote: > Is there a way to write a single glob regexp that expands to all lib*.dylib > EXCLUDING lib*.[0-9]*.dylib, lib*.[0-9]*.[0-9]*.dylib, etc? Rather than file globs, how about regular expressions: foreach f [glob -tails -dir /opt/local/lib

Re: 2.5.1

On Jun 1, 2018, at 7:36 PM, Joshua Root wrote: > > Please test the changes that are now on the release-2.5 branch. Are > there any other things that need to be fixed for a 2.5.1 release in the > very near future? Looks good, so far. SuiteSparse is happy. Added ` configure.cxx_stdlib

Re: multiple ports with stdlibc++ mismatches (all on 10.13)...

On May 31, 2018, at 11:44 AM, Dr M J Carter wrote: > > On Thu, May 31, 2018 at 07:49:23AM -0700, Ken Cunningham wrote: >> >> On 2018-05-30, at 11:04 PM, Joshua Root wrote: >> >>> On 2018-5-31 15:39 , Ken Cunningham wrote: gcc5 is using libstdc++ (this installation is configured to use

Re: macports_version

On May 21, 2018, at 5:32 AM, Ryan Schmidt wrote: > > Yes I'm talking about $xcodeversion, and I'm wondering why we don't have a > corresponding $macports_version. Why do we have to call a procedure to get > the MacPorts version, when we don't have to call a procedure

Re: macports_version

> On May 20, 2018, at 9:45 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On May 20, 2018, at 17:04, Andrew Moore wrote: > >> On May 20, 2018, at 8:23 AM, Ryan Schmidt wrote: >> >>> Why is macports_version a proc and not an option? &g

Re: macports_version

On May 20, 2018, at 8:23 AM, Ryan Schmidt wrote: > > Why is macports_version a proc and not an option? To make it read-only? It seems procs and trace are Tcl’s way of defining constants . -AM

Re: Installing nokogiri with --use-system-libraries (was: Re: Migrating the guide to AsciiDoc)

On Apr 23, 2018, at 6:23 PM, Rainer Müller wrote: > $ sudo gem2.5 install nokogiri -- --use-system-libraries > … > pkg-config could not be used to find libxml-2.0 > … > "pkg-config --exists libxml-2.0" > dyld: Symbol not found: __cg_jpeg_resync_to_restart > Referenced from:

Re: Installing nokogiri with --use-system-libraries (was: Re: Migrating the guide to AsciiDoc)

On Apr 23, 2018, at 6:23 PM, Rainer Müller <rai...@macports.org> wrote: > > On 2018-04-23 20:35, Andrew Moore wrote: >> You might try: >> >> $ sudo gem update —system >> >> which should install the latest version of bundler (you really want that),

Re: MP manpages (was: Migrating the guide to AsciiDoc)

On Apr 23, 2018, at 3:46 PM, Jan Stary wrote: > > On Apr 23 16:26:13, rai...@macports.org wrote: >> On 2018-04-23 14:27, Jan Stary wrote: These quirks are added by DocBook XSLT and are apparently required to make the output compatible. If you disagree with that, talk to

Re: Migrating the guide to AsciiDoc

On Apr 23, 2018, at 11:42 AM, Rainer Müller wrote: > > On 2018-04-22 09:29, Mojca Miklavec wrote: >> Hi, >> >> As requested during yesterday's meeting, here's the result of >> automatic conversion of our guide from xml (docbook) to asciidoc: >> >>

Re: Migrating the guide to AsciiDoc

Just to be clear, asciidoc is the format, but asciidoctor is the text processor (a superset of python asciidoc). Is that correct? -AM > On Apr 22, 2018, at 3:29 AM, Mojca Miklavec wrote: > > Hi, > > As requested during yesterday's meeting, here's the result of > automatic

Re: Buiid/install stages documentation?

I’ll offer my two cents. One overriding issue of package management is dependency resolution. In the case of ruby, multiple versions of a gem happily co-exist globally with applications loading compatible subsets based on its Gemfile.lock, by virtue of package dependency resolver, bundler.

Re: New guide section on Git and GitHub

On Apr 14, 2018, at 4:01 PM, Jonathan Stickel wrote: > > Sure, it makes perfect sense to encourage PRs while continue to consider > patches. I'm not against that at all, and I'm willing to figure it out. But > care should be taken about the tone of the message, especially

Re: New guide section on Git and GitHub

> On Apr 11, 2018, at 7:52 PM, Dave Horsfall <d...@horsfall.org> wrote: > > On Wed, 11 Apr 2018, Andrew Moore wrote: > >> Okay, so when all is said and done, am I actually prepared to make an actual >> contribution? Perhaps it merits a topic of discussion

Re: New guide section on Git and GitHub

cPorts desperately, they just don’t know it yet… -AM > On Apr 11, 2018, at 6:33 PM, Perry E. Metzger <pmetz...@macports.org> wrote: > > On Wed, 11 Apr 2018 18:19:50 -0400 Andrew Moore <slew...@gmail.com> > wrote: >> My impression from the mailing list is that

Re: New guide section on Git and GitHub

My impression from the mailing list is that going forward Trac would be used exclusively for bug reports. Any code submissions would ideally be submitted as pull requests to GitHub. If so, this change needs to put front and center, in large display type. Section 7 “MacPorts Projects” should

Re: New guide section on Git and GitHub

Um, submit pull requests, no? > On Apr 11, 2018, at 5:31 PM, Perry E. Metzger wrote: > > I just committed a new section of the guide called "Using Git > and GitHub". Please read, comment, and improve. > > Perry > -- > Perry E. Metzger pmetz...@macports.org

Re: Build Failure on ports-10.6_x86_64_legacy: libpsl, mosquitto

> On Apr 4, 2018, at 12:18 PM, Mojca Miklavec wrote > It also failed on 10.7 and 10.8. That’s more a problem with my eyes :). > I triggered new builds of mosquitto now that libpsl has been built on > all systems. Okay, so no buildbot notifications since then. Not being

Re: Build Failure on ports-10.6_x86_64_legacy: libpsl, mosquitto

If I’m reading correctly the attached report from build...@macports.org, port net/mosquitto fails for OS X <= 10.6 due to indirect dependency: libpsl. If so, this is presumably a known issue, since many ports depend upon libpsl? I don’t have the time or resources to debug the issue on legacy

Re: Changing default cxx_stdlib to libc++

With Apple now planning to phase out Server.app, might they be open to supporting MacPorts once again? Going forward, I would hope they recognize a vested interest in seeing that the open-source community continues to support them… -AM > On Mar 15, 2018, at 12:19 AM, Ryan Schmidt

Re: Upgrading Pandoc

On Mar 4, 2018, at 2:18 PM, Mark Anderson wrote:So I started trying to move pandoc from some older version to 2.1.1 but then I realized I needed to upgrade the Haskell compiler and libraries to do that. I got started, but wow, this is something else. Does anyone have tips about

Re: [MacPorts] #53974: texlive-basic: dvips exits with trap 6

I’m trying to make some time this weekend to look at it in the debugger... -AM > On Jun 1, 2017, at 3:36 PM, MacPorts wrote: > > #53974: texlive-basic: dvips exits with trap 6 > +-- > Reporter: slewsys| Owner:

Re: dvips from texlive-basic broken?

of is Xcode was upgraded to 8.3.1… -AM > On Apr 13, 2017, at 1:20 AM, Mojca Miklavec <mo...@macports.org> wrote: > > On 13 April 2017 at 01:42, Andrew Moore wrote: >> Only by moving aside dvips(1) from MacPorts texlive-basic and using >> dvips(1) from MacTeX 20

dvips from texlive-basic broken?

Only by moving aside dvips(1) from MacPorts texlive-basic and using dvips(1) from MacTeX 2016 distribution, was I able to upgrade to MacPorts asymptote 2.41 vector graphics package. asymptote 2.40 was installed about a month ago without any issues. Anyone care to confirm or dispute this