On Mar 22 12:53:15, rai...@macports.org wrote:
> On 2017-03-21 21:43, Jan Stary wrote:
> > +echo "Remember to set your environment:"
> > +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH."
> > +echo "Prepend ${MANPAGES} to MANPATH if you use MANPA
On Mar 22 14:32:03, h...@stare.cz wrote:
> On Mar 22 12:53:15, rai...@macports.org wrote:
> > On 2017-03-21 21:43, Jan Stary wrote:
> > > +echo "Remember to set your environment:"
> > > +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH."
> &g
hans@macbook:~$ find /opt/local/var/macports/logs
/opt/local/var/macports/logs
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_mail_mutt
On Mar 30 20:47:15, jer...@lavergne.me wrote:
> The difference in paths indicates the logs you see are from the default
> prefix, but you have since configured MacPorts to use a different prefix.
>
> /opt/local versus /opt/mports
Ah, yes.
Thanks.
Jans
This is 2.4.99 on 10.6.8
$ sudo port clean --all opencore-amr
---> Cleaning opencore-amr
$ port livecheck opencore-amr
Error: livecheck failed for opencore-amr: extracted version '0.1.2' is
older than livecheck.version '0.1.3'
$ find /opt/local/var/macports/ -name \*opencore\*
This is MacPorts 2.4.1 on MacOSX 10.6.8.
A build of audio/sox starts with the following warning:
$ sudo port install -d sox
Warning: All compilers are either blacklisted or unavailable; defaulting to
first fallback option
Warning: All compilers are either blacklisted or unavailable; defaulting
On Mar 21 14:43:12, allber...@gmail.com wrote:
> On Tue, Mar 21, 2017 at 4:37 AM, Jan Stary <h...@stare.cz> wrote:
>
> > Why are they unavailable? The gcc and clang from Xcode work just fine.
>
>
> "Works for random stuff I tried it on" does not guarant
On Apr 13 08:59:56, io...@macports.org wrote:
> On 04/01/2017 06:13 AM, Ryan Schmidt wrote:
> > Since it looks like speex has been superseded by opus, I guess there won't
> > be any further major development on speex, so I agree having -devel ports
> > isn't useful anymore.
>
> Well, probably
On Jul 01 19:39:19, mo...@macports.org wrote:
> One advantage of a pull request is that there's now an automated build
> running after you submit it and it's slightly easier to discuss the
> code line-by-line when needed.
>
> And that there are currently slightly above 30 open pull requests,
>
On Jul 03 03:28:30, j...@macports.org wrote:
> > This is MacOSX 10.6.8 running various compilers provided by MacPorts.
> > Compiling the following C++ source
> >
> > #include
> >
> > int main(void)
> > {
> > double d = std::log2(2.3456789f);
> > return 0;
> >
On Jul 04 20:27:43, h...@stare.cz wrote:
> > Clang can support C++11 if you use -stdlib=libc++.
> Yes it does: clang++-mp-3.4 -stdlib=libc++ prog.cc
On Jul 02 13:02:44, ryandes...@macports.org wrote:
> But on Snow Leopard, since it does not include libc++, you'd have to install
> it first (the
On Jul 04 13:47:27, ken.cunningham.web...@gmail.com wrote:
> >>
> >> Perfect would be if I just wrote it into the clang code directly.
> >> I am almost to the point where I could do that, actually. I know where it
> >> would go, I think.
> >
> > I don't get it. Do you mean to mess with the
On Jul 05 08:28:40, ken.cunningham.web...@gmail.com wrote:
>
> On 2017-07-05, at 2:31 AM, Jan Stary wrote:
>
> > On Jul 04 13:47:27, ken.cunningham.web...@gmail.com wrote:
> >>>>
> >>>> Perfect would be if I just wrote it into the clang code dire
On Apr 26 11:05:51, davide.lie...@gmail.com wrote:
> 2017-04-26 9:26 GMT+02:00 Jan Stary <h...@stare.cz>:
> > Yet port(1) always says
> >
> > Warning: port definitions are more than two weeks old, consider updating
> > them by running 'port selfupdate'.
>
On Apr 26 11:10:22, h...@stare.cz wrote:
> On Apr 26 11:05:51, davide.lie...@gmail.com wrote:
> > 2017-04-26 9:26 GMT+02:00 Jan Stary <h...@stare.cz>:
> > > Yet port(1) always says
> > >
> > > Warning: port definitions are more than two weeks old, consi
$ port livecheck sox
sox seems to have been updated (port version: 14.4.2, new version: 14.4.2rc2)
Of course, 'rc2' is the release candidate before 14.4.2.
SoX does not specify any specific livecheck rules; what is
the right place where the default could possibly be tweaked?
Jan
On Jun 02 15:30:53, rai...@macports.org wrote:
> On 2018-06-02 08:25, Jan Stary wrote:
> > $ git log -1
> > 33mcommit 101e557b4b08974559402a3c5cf6e247561ef5e7m33m (m1;36mHEAD ->
> > m1;32mmasterm33m, m1;31morigin/masterm33m,
> > m1;31mm33mm33mm1;36mm1;32mm33mm1;3
I am using git to work with MP, both to pull the current
version from g...@github.com:macports/macports-ports.git
and to create pull requests in my fork.
Now, I a pull from upstream, as always, but:
$ git branch --list
* master
ssl
$ git status
On branch master
Your branch is up to date with
https://github.com/macports/macports-ports/pull/1182
Is anyone using opencore-amr at all? This is what grep says:
* We have audio/libfdk-aac which implements the same
* `gstreamer010-gst-plugins-ugly` depends on it (nomaintainer)
* `gstreamer1-gst-plugins-ugly` depends on it (nomaintainer)
*
On Nov 10 07:37:31, rm...@orange.fr wrote:
> It was fixed on my demand two years ago by the developer
> Thomas Dickey (a FreeBSD developer!)
> I will revert to 2.8.8 to see if it is the culprit.
> >> Hello The lynx macport still crashes
> >> when renaming a file or folder.
I don't get it: when
On Nov 22 23:42:58, ryandes...@macports.org wrote:
>
> On Nov 21, 2017, at 11:31, db wrote:
>
> > Is it possible to set this? I checked man pages for both port-livecheck and
> > port but couldn't find a way. I have a shell function for a list of ports
> > that stucks on gnutls too long, for
On Nov 28 14:32:01, rlha...@smart.net wrote:
> I can see ditching the telnet server, but the client remains useful for
> debugging various protocols, and in rare cases of accessing ancient systems
> (or emulations of them) which don't support ssh.
>
> Likewise, there remain times a command-line
On Jan 10 15:53:59, dl...@geeklair.net wrote:
> On Jan 10, 2018, at 2:49 PM, Jan Stary <h...@stare.cz> wrote:
> > these ports specify a hard dependency on openssl with "port:openssl".
>
> is libressl now ABI compatible with openssl? IIRC some ports moved
On Jan 11 06:23:11, ryandes...@macports.org wrote:
> >>> $ port installed depends:libressl
> >>> None of the specified ports are installed.
> >>
> >> This result means: of the ports that specify a dependency containing the
> >> substring "libressl", you don't have any installed.
> >
> > OK,
Dear users and maintainers of
qt5
qt55
qt56
qt57
qt58
qt59
fbthrift
folly
lua-luasec
qca
wangle
scummvm
libstrophe
profanity
qpid-proton
snort
On Jan 10 20:49:21, h...@stare.cz wrote:
> path:lib/libssl.dylib:openssl
>
> This means a 'lib/libssl.dylib' needs to be present in $prefix,
> and if it's not, it gets installed by installing openssl.
> The point of specifying the dependency this way is that
> some port other than openssl
On Jan 10 20:49:21, h...@stare.cz wrote:
> Could you, the users and maintainers, please test this with your port
> and report success or failure here, or preferably at
https://github.com/macports/macports-ports/pull/1216
(sorry, I sent before pasting this).
Jan
On Jan 15 13:39:34, macint...@mathiesen.info wrote:
> Apple shouldn't disable the root account through a supplementary update
> when I've chosen to activate it. They have _never_ done this before !
I agree that Apple shouldn't be touching the users setup,
such as enable/disable account's login.
On Jan 17 16:48:02, mo...@macports.org wrote:
> On 16 January 2018 at 18:07, islaind via macports-users wrote:
> > can macports be less strict with aux packages download?
> > ---
> > (on osx 10.8.5, port version 2.4.2)
> >
> > In installing xpdf
On Jan 15 22:33:56, ryandes...@macports.org wrote:
>
> On Jan 14, 2018, at 14:47, Mojca Miklavec wrote:
>
> > On 14 January 2018 at 11:40, Chris Jones wrote:
> >>
> >> A buildbot exists for PPC, but not intel
> >>
> >> The assumption I believe being if you have an intel machine, you should
>
> > > The reasons for not having a 10.5 Intel builder are that
> > > no users should need it (all users on 10.5 Intel should upgrade to 10.6)
> >
> > Why?
>
> many reasons. For instance security. In my view users should always migrate
> their machines to the most up to date OS they can run,
On Jan 14 21:47:43, mo...@macports.org wrote:
> On 14 January 2018 at 11:40, Chris Jones wrote:
> >
> > A buildbot exists for PPC, but not intel
> >
> > The assumption I believe being if you have an intel machine, you should
> > update at least to 10.6... the 10.5 buildbot exists because that is
> The issue is not whether or not I'm using the root account or not ;
> neither how and why I'm using it on my boxes - that's purely my own
> business ; and -frankly- please stay out of that !
It's Apple messing with your root account, not Ryan,
who, on the contrary, makes your system more
How far back are the MacOS releases supported with binary packages?
I am currently installing SoX on 10.5.8, and it seems each and every
dependency (including apple-gcc42 for some reason) has to be built
form source.
Jan
On Jan 16 06:16:07, ken.cunningham.web...@gmail.com wrote:
> > I am stuck with 10.5.8 on this particular machine anyway.
>
> Are you sure about that? Even my most ancient intel machines, 32bit, can go
> up past there.
> even a macbook 1,1 can do 10.6.8
>
On Jan 16 09:49:32, jon...@hep.phy.cam.ac.uk wrote:
> > > I find it useful to have a ppc builder available to have at least some
> > > feedback about problems on that platform, but also because any PPC
> > > machine is super slow and MacPorts is often the most important part
> > > that actually
On Jan 19 06:48:37, rlha...@smart.net wrote:
> By default, macOS (like Windows with NTFS filesystem)
> is case-preserving but NOT case-sensitive.
> In other words, names that differ only by case
> refer to the same file.
That's exactly what I was missing. Thanks.
> For a case-preserving but
On Jan 19 14:18:00, jon...@hep.phy.cam.ac.uk wrote:
> The point is third party applications (and perhaps even some Apple stuff) is
> not well tested on anything other than the defaults. So its far from
> impossible for there to be applications that internally are not consistent
> with their
This is of course not MP related;
please kindly point me to the appropriate Apple forum.
Create a local file:
user@local$ echo local > /tmp/file
Prepare a file on a remote machine,
with the "same" name, but uppercase:
user@remote$ echo remote > /tmp/FILE
Now copy the remote
On Jan 14 10:40:23, jon...@hep.phy.cam.ac.uk wrote:
> PPC or Intel ?
> A buildbot exists for PPC, but not intel
Ah, right, my machine is Intel. Thanks.
Jan
On Jan 15 02:26:31, macint...@mathiesen.info wrote:
> !!! WARNING !!!
>
> The 10.13.2 supplemental update in-activates the root account if enabled
> Luckily, on the machines I've updated, I also had a normal admin
> account, so no big deal ; but I also have a machine with no normal admin
>
On Jan 15 10:21:05, macint...@mathiesen.info wrote:
> Jan Stary wrote:
> > I don't get it. 10.13.2 does _not_ have a root account by default? Why?
> > And if it does, how is that a problem? It's UNIX, of course there is
> > a 'root' account.
>
> macOS out-of-the-
Looking at
https://build.macports.org/builders/ports-10.8_x86_64_legacy-builder/builds/49810/steps/install-port/logs/stdio
it seems that the buildbot failed to even download the tarball:
---> Attempting to fetch lowdown-0.3.1.tar.gz from
https://kristaps.bsd.lv/lowdown/snapshots/
Error: Failed
> PS: Does sndfile-play actually work for you then, i.e. plays files?
> For me, it has been saying
>
> OS X 10.8 and later have a new Audio API.
> Someone needs to write code to use that API.
>
> since 10.5
... probably meaning the Darwin version, as in
Darwin mb.stare.cz 10.8.0
Hi Thomas,
https://github.com/erikd/libsndfile/pull/355
If you have a problem with libsndfile itself,
discuss this at the libsndfile mailing list.
If you have a problem specifically with the MacPort of lbsndfile,
discuss it on the macports-users mailing list.
Jan
> >> I have an old
e.g. https://opensource.apple.com/source/copyfile/
contains various subdirectories with version numbers.
Can someone please explain how these correspond
to the actual MacOSX releases?
https://opensource.apple.com/source/copyfile/copyfile-146
seems the contain the most recent manpage.
Jan
kdep
$ ls -l /usr/bin/mkdep
-rwxr-xr-x 1 root wheel 18288 Jan 19 09:32 /usr/bin/mkdep
$ file /usr/bin/mkdep
/usr/bin/mkdep: Mach-O 64-bit executable x86_64
Jan
> Le 13.02.2018 à 09:21, Jan Stary a écrit :
> > This is 10.13.2 with XCode 9.2
> >
> > $ mkdep *.c
On Feb 13 06:50:20, ryandes...@macports.org wrote:
>
> On Feb 13, 2018, at 05:07, Jan Stary wrote:
>
> > On Feb 13 10:08:02, miniu...@free.fr wrote:
> >> Are you sure the command line development tools from Xcode are properly
> >> installed ?
> >>
>
This is 10.13.2 with XCode 9.2
$ mkdep *.c
mkdep: error: unable to find utility "mkdep", not a developer tool or in PATH
$ which mkdep
/usr/bin/mkdep
$ echo $PATH
/Users/hans/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
Am I missing something obvious?
Why is it that one of those variants is required?
Is there any problem with having glib2 without both?
Jan
On Feb 22 17:09:22, rai...@macports.org wrote:
> On 2018-02-21 20:14, Jan Stary wrote:
> > If I am reading https://guide.macports.org/chunked/reference.phases.html
> > right, there is are no "fetch dependencies". Would it make sense
> > to introduce fetch depen
On Feb 22 18:54:18, h...@stare.cz wrote:
> One of the libraries in MP providing SSL functionality is WolfSSL.
> Only two other ports mention it:
>
> sysutils/gearmand explicitly disables it
> net/curl has a +wolfssl variant (beside +ssl, +darwinssl, etc).
>
> Is anyone using it? Would there be
On Feb 22 19:04:41, h...@stare.cz wrote:
> > depends_fetch exists, but apparently is not documented in the guide.
>
> Thanks for the insight. Currently, nothing is using it,
> except: these explicitly clear it (why?)
Is there a default nonempty value for depends_fetch
that makes these ports want
One of the libraries in MP providing SSL functionality is WolfSSL.
Only two other ports mention it:
sysutils/gearmand explicitly disables it
net/curl has a +wolfssl variant (beside +ssl, +darwinssl, etc).
Is anyone using it? Would there be any objections to removing it?
While here, curl also
On Feb 22 12:31:24, billc_li...@greenbuilder.com wrote:
> A single port crane, done as a line drawing in the O'Reilly book cover
> style (possibly anthropomorphized) would work well as a logo and could
> probably be made into a plush toy if someone really wanted to take it that
> far.
A plush toy
Recently, I have tweaked textproc/lowdown
https://github.com/macports/macports-ports/pull/1245
to download the distfile from a http master site, not a https one,
because the https server rejects the weak ssl of some older MacOS systems,
which could not download the distfile then.
That worked for
Hi Ken,
when I created the textproc/lowdown port not long ago
https://github.com/macports/macports-ports/pull/1241
you kindly advised me to use
PortGroup snowleopard_fixes 1.0
so that older MacOS sysem without e.g. strndup(3)
can still compile lowdown.
However, it seems that the
On Feb 21 12:43:28, h...@stare.cz wrote:
> A more general proposed solution was to bunlde a newer curl with MP,
> in partcular one built against a newer SSL/TLS library:
> https://trac.macports.org/ticket/51516
It was also suggested there to recompile MP
using its own already installed curl port.
On Feb 21 08:46:21, ken.cunningham.web...@gmail.com wrote:
> lowdown uses it's own completely unique methods for configure
It's a hand written ./configure shell script, as opposed to the auto* hell.
https://github.com/kristapsdz/oconfigure
Some other portable projects do the same.
> and library
On Feb 21 08:11:26, ken.cunningham.web...@gmail.com wrote:
> I should have been more descriptive about the /opt/bootstrap part of the post
> below.
>
> Like you, I didn't like the circular dependency. If you "sudo port uninstall
> active", you're hooped. So here's what I actually do on all
> > >> During the GSOC meeting in Mountain View we had some fruitful evening
> > discussions where we were heavily criticised for not having our own happy
> > fluffy animal mascot (like a flying platypus?) which we could take to every
> > meeting or hacking event where we show up.
On Feb 22 19:04:41, h...@stare.cz wrote:
> On Feb 22 17:09:22, rai...@macports.org wrote:
> > On 2018-02-21 20:14, Jan Stary wrote:
> > > If I am reading https://guide.macports.org/chunked/reference.phases.html
> > > right, there is are no "fetch de
On Feb 22 18:04:23, ken.cunningham.web...@gmail.com wrote:
> >> You are done. No more circular dependency.
> > Yes. One installation of MP depends on another installation.
> >
>
> That's not circular. Circular is when an installation of MacPorts depends on
> itself,
> and is therefore fragile.
On Dec 26 11:12:58, rm...@orange.fr wrote:
> > Could you be more specific about what you mean by "add anything" and
> > "renaming a file/folder"? What series of steps would we need to perform on
> > our systems to observe the problem?
>
> sorry, my english is not very concease, but here is how
Hi Craig,
> > On Jan 1, 2018, at 6:40 PM, Jan Stary <h...@stare.cz> wrote:
> > I would like to remove man2htl from macports.
> > I see that liirc (which you maintain) requires it
> > as a build dependency. Why exactly is it required please?
On Jan 01 21:00:03,
On Jan 02 11:07:21, h...@stare.cz wrote:
> Hi Craig,
>
> > > On Jan 1, 2018, at 6:40 PM, Jan Stary <h...@stare.cz> wrote:
> > > I would like to remove man2htl from macports.
> > > I see that liirc (which you maintain) requires it
> > > as a bui
opt/local/share/doc/bibclean/README
/opt/local/share/man/man1/bibclean-2.17.1.gz
/opt/local/share/man/man1/bibclean.1.gz
i.e. there is no html version of any manpage being built.
So let's just drop it.
Jan
>
> >
> > > On Jan 1, 2018, at 6:44 PM, Jan Stary <h...@sta
Deactivatng e.g. man warns me that
Note: It is not recommended to uninstall/deactivate a port that has
dependents as it breaks the dependents.
The following ports will break: lirc @0.9.4d_3
It's a build dependency, not a run dependency or a lib dependency.
Does the deactivate/uninstall
What's with the Travis checks recently? For example,
https://github.com/macports/macports-ports/pull/1185
-> "All checks have failed"
https://travis-ci.org/macports/macports-ports/jobs/323828523
"./_ci/bootstrap.sh: line 57: shell_session_update: command not found"
Jn
On Jan 01 19:14:53, h...@stare.cz wrote:
> What's with the Travis checks recently? For example,
> https://github.com/macports/macports-ports/pull/1185
> -> "All checks have failed"
>
> https://travis-ci.org/macports/macports-ports/jobs/323828523
> "./_ci/bootstrap.sh: line 57:
On Jan 02 14:37:00, ryandes...@macports.org wrote:
> On Jan 2, 2018, at 13:33, Jan Stary wrote:
> >
> > Deactivatng e.g. man warns me that
> >
> > Note: It is not recommended to uninstall/deactivate a port that has
> > dependents as it breaks the dep
I just built "bitcoin +qt5", only to realize its "bitcoin +gui".
While build the noneexistent +qt5 variant, the default variant
was buit (which happens to be +daemon+wallet).
Is it intentional that a nonexistent variant is _silently_ ignored?
Wouldn't it be less surprising if MP stopped with an
Attached please find a full log of
sudo port -vs install octave -app -docs +gfortran -graphicsmagick -java -qt5
+sound -universal
It eventually fails with undefined symbols.
Am I missing something obvious?
Jan
main.log.gz
Description: application/gunzip
> to show the actual link command? - MLD
How do I do that on port(1) level?
Or do I need to tweak the actual Portfile with
something like --disable-silent-rules?
Thanks,
Jan
> On Mon, Jul 23, 2018, at 3:26 PM, Jan Stary wrote:
> > Attached please find a full
ay for certain. Maybe add some verbosity to
> > the build stage to show the actual link command? - MLD
New log attached, with full commands.
Jan
>
> > On Mon, Jul 23, 2018, at 3:26 PM, Jan Stary wrote:
> > > Attached please find a full log of
> > >
&
In a recent thread, I came over the folowing:
On Jul 24 09:26:18, h...@stare.cz wrote:
> On Jul 23 15:51:49, michae...@macports.org wrote:
> > Looks like the link command is missing LAPACK or the equivalent (e.g.
> > maybe: Atlas, OpenBLAS, Eigen), but since the log doesn't include the
> >
> [twill] /Users/jam [230]% ssh -vv haycorn.home
> [versions match etc]
> debug1: Authentications that can continue: publickey,password
> debug1: Next authentication method: publickey
> debug1: Offering public key: RSA
> SHA256:/FjP5L3Grrw1P4KXIq5SsfkEy5RWhmeVehgG5+8k5rk /Users/jam/.ssh/id_rsa
>
Just to be sure: as your ~/.ssh/authorized_keys only contains
this one pubkey, the file should be identical to the corresponding
~/.ssh/id_rsa.pub on the client side. Please verify that it is
haycorn$ cksum ~/.ssh/authorized_keys
twill$ cksum ~/.ssh/id_rsa.pub
On Sep 05 08:08:29, h...@stare.cz
On Sep 06 12:41:56, j...@tigger.ws wrote:
> This does not (identical keys and config files)
The sshd from the openssh port uses a different config.
> [haycorn] /Users/jam [291]% sshd --help
> OpenSSH_7.6p1, OpenSSL 1.0.2p 14 Aug 2018
What happens if you run the ysstem sshd on haycorn?
On Sep 06 11:40:41, j...@tigger.ws wrote:
> > What is the difference between what this server says in the logs,
> > and what the previous server says in the logs?
>
> I was able to do password-less login to another High Sierra machine
> exactly as you would expect !!!
Yes, we already know that.
On Sep 06 12:41:56, j...@tigger.ws wrote:
> Hi All
>
> just in case this is the issue, both machines being “up to date”, and it
> affects others
>
> This works (passwd-less login):
>
> [pussycat] /Users/mary [501]% sshd --help
> OpenSSH_7.5p1, LibreSSL 2.5.4
This is presumably the system sshd
On Jan 20 02:27:23, ryandes...@macports.org wrote:
>
> On Jan 19, 2018, at 15:42, Jan Stary wrote:
>
> > On Jan 19 14:18:00, Chris Jones wrote:
> >> The point is third party applications (and perhaps even some Apple stuff)
> >> is
> >> not well tested o
> But it looks like Adobe's installer goes a step further and actively prevents
> you from installing on case-sensitive volumes, and they have a knowledge base
> article explaining that.
>
> https://helpx.adobe.com/creative-suite/kb/error-case-sensitive-drives-supported.html
Beautiful.
On Apr 16 19:39:11, rlha...@smart.net wrote:
> "In fall 2018, Apple will stop bundling open source services such as Calendar
> Server, Contacts Server, the Mail Server, DNS, DHCP, VPN Server, and Websites
> with macOS Server. Customers can get these same services directly from
> open-source
On Apr 18 23:17:44, ryandes...@macports.org wrote:
> > Also, the following require a specific version:
> >
> > devel/libpdel lib:libssl.0.9:openssl
> > mail/qpopperlib:libssl.0:openssl
> > mail/sylpheed-devel (+ssl) lib:libssl.0.9:openssl
> >
I prepared a PR to upgrade LibreSSL to 2.7.2
https://github.com/macports/macports-ports/pull/1626
Three changes that seem most relevant to me
(quoting directly from the release notes):
* Fixed builds macOS 10.11 and older.
* Added support for many OpenSSL 1.0.2 and 1.1 APIs, based on
On Mar 24 14:14:37, mojca.miklavec.li...@gmail.com wrote:
> On 24 March 2018 at 13:54, Jan Starý wrote:
> > The 'platforms' field of a Portfile is currently
> > both _required_ and _ignored_. By the Guide,
> >
> > A list of the platforms on which the port has been tested.
> >
Hi Jeremy,
what is the plan really with libressl and libressl-devel?
We have 2.5.5 in security/libressl, 2.6.2 in security/libressl-devel,
and now 2.7.1 is out.
I would just prepare an udate of libressl to 2.7.1,
but I want to as kfirst: why do we have "devel".
LibreSSL themselves make no such
On Mar 04 10:19:51, keybou...@gmail.com wrote:
> I was able to download a precompiled binary for ffmpeg, and ffprobe.
> In both cases, it was a single file. In both cases it just worked.
Good.
> Right now, trying to deal with a current version that won't compile,
Current version of what?
> If I am reading https://guide.macports.org/chunked/reference.phases.html
> right, there is are no "fetch dependencies". Would it make sense
> to introduce fetch dependencies just like we have build dependencies
> and run dependencies, so that the affected ports could specify
On Sep 01 14:24:34, j...@tigger.ws wrote:
> but directly related to a port
What port?
> I want password-less ssh login
Create a password-less key and copy it into
~/.ssh/authorized_keys on the remote site.
Make sure that ~/.ssh is chmod 700 and authorized_keys is chmod 600
if you are creating
> Password-less login to 10.13.6 works for me just fine,
> with the method described above (put your *.pub to the authorized_keys).
> That's the system /usr/sbin/sshd, which is OpenSSH_7.6, LibreSSL 2.6.2.
> Below is a log of such a session, from OpenBSD 6.3 to MacOS 10.13.6.
Same works between
On Sep 03 21:50:35, j...@tigger.ws wrote:
> Jan I must assume that you have never done a password-less login
> to a high sierra machine and the tone of your questions betrays that.
Password-less login to 10.13.6 works for me just fine,
with the method described above (put your *.pub to the
93 matches
Mail list logo
