Re: Postfix, CAfile and Macports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25.01.17 22:28 Daniel J. Luke wrote: > What does `openssl s_client -connect 78.46.5.205:25 -starttls > smtp` > say? "verify return: 1" sounds like problems, but "Verify return code: 0 (ok)" at the end sounds ok. >> openssl s_client -connect 78.46.5.205:25 -starttls smtp > CONNECTED(0003) depth=2 C = US, O = GeoTrust Inc., CN = > GeoTrust Global CA verify return:1 depth=1 C = US, O = GeoTrust > Inc., CN = RapidSSL SHA256 CA - G3 verify return:1 depth=0 OU = > GT60799501, OU = See www.rapidssl.com/resources/cps (c)14, OU = > Domain Control Validated - RapidSSL(R), CN = *.your-server.de > verify return:1 --- Certificate chain 0 s:/OU=GT60799501/OU=See > www.rapidssl.com/resources/cps (c)14/OU=Domain Control Validated > - RapidSSL(R)/CN=*.your-server.de i:/C=US/O=GeoTrust > Inc./CN=RapidSSL SHA256 CA - G3 1 s:/C=US/O=GeoTrust > Inc./CN=RapidSSL SHA256 CA - G3 i:/C=US/O=GeoTrust > Inc./CN=GeoTrust Global CA 2 s:/C=US/O=GeoTrust Inc./CN=GeoTrust > Global CA i:/C=US/O=Equifax/OU=Equifax Secure Certificate > Authority --- Server certificate -BEGIN CERTIFICATE- > [snipped] -END CERTIFICATE- subject=/OU=GT60799501/OU=See > www.rapidssl.com/resources/cps (c)14/OU=Domain Control Validated > - RapidSSL(R)/CN=*.your-server.de issuer=/C=US/O=GeoTrust > Inc./CN=RapidSSL SHA256 CA - G3 --- No client certificate CA > names sent Peer signing digest: SHA512 Server Temp Key: DH, 2048 > bits --- SSL handshake has read 4814 bytes and written 661 bytes > --- New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-GCM-SHA384 Server > public key is 2048 bit Secure Renegotiation IS supported > Compression: NONE Expansion: NONE No ALPN negotiated > SSL-Session: Protocol : TLSv1.2 Cipher: > DHE-RSA-AES256-GCM-SHA384 Session-ID: > 33A4A8F6FC9B4EFAC46E1D7351535704B2890DC738C5DB02550AC5CE5F9CB871 > Session-ID-ctx: Master-Key: > 338B12D3D7664BA2F34E55B6B778CB2C52BC47E54CE220F7940075444BED347F1627 2695D8965B4130EBE18010260C55 > > Key-Arg : None > PSK identity: None PSK identity hint: None SRP username: None TLS > session ticket lifetime hint: 200 (seconds) TLS session ticket: > - 63 af 28 f0 5c 0c 7c ff-de 10 0e 6c 0b c6 bb 8b > c.(.\.|l 0010 - fd 5b 88 59 b0 b9 a2 3e-37 1c dc bc b5 70 > bd 20 .[.Y...>7p. 0020 - e1 be 99 56 36 37 95 6b-12 89 f0 > 12 67 bb b7 d1 ...V67.kg... 0030 - 9a 3b a3 aa 64 33 84 > 74-80 d9 eb 27 46 11 59 ef .;..d3.t...'F.Y. 0040 - 77 b0 99 2d > 34 11 20 02-9e 96 48 71 be 2f cb e1 w..-4. ...Hq./.. 0050 - af > 16 85 2d aa 98 75 a7-10 5a 9c 8e a0 26 76 a5 ...-..u..Z... > 0060 - 50 de 1d 1a 62 70 16 c9-4b d7 31 33 3d 78 b5 a7 > P...bp..K.13=x.. 0070 - df 87 3b 37 24 3a c6 f4-30 b2 5d d7 84 73 > 89 0c ..;7$:..0.]..s.. 0080 - 0d 31 d1 99 56 a6 a7 7f-79 24 4b > ea 98 7a 37 41 .1..V...y$K..z7A 0090 - 7d 6c d9 0d d0 31 28 > c7-7e 13 af 7b 42 ea 08 33 }l...1(.~..{B..3 > > Start Time: 1485414417 Timeout : 300 (sec) Verify return code: > 0 (ok) --- 250 HELP Johannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAliJoQQACgkQzi3gQ/xETbLSagCcCKjiFNnkfbtsuybEQ3QRBuTc jxMAni691pMqnRXbp7sp6+HzpeEgy+VI =5rPY -END PGP SIGNATURE-
Re: Qt5 on 10.7?
You are not missing anything. That was my mistake. I will fix it as soon as I get the chance. Sorry about that. -Marcus > On Jan 25, 2017, at 1:39 PM, Michael Dickenswrote: > > When using Mac OS X 10.7 and I try to get info on any port that uses the > Qt5 PortGroup, I get the error that "Port qt56-qtbase not found". A > little searching finds that in the qt5-1.0 PortGroup, the proc > "qt5.get_default_name" returns "qt56" for this OS version, which is then > used as the base for the Qt5 ports: qt56-qtbase, etc The issue is > that there are no qt56* ports -- "port search qt56" returns "No match > for qt56 found". If I insert "set qt_name qt5" -before- the qt5 > PortGroup is called, then everything works as expected, and I can > install qt5-qtbase (5.6.2) and it works, plus or minus. Am I missing > something? - MLD
Nudge typesafe-activator submission
any update for the acceptance of the typesafe-activator port submission??? https://github.com/macports/macports-ports/pull/130 https://trac.macports.org/ticket/53177 Cheers, John
Qt5 on 10.7?
When using Mac OS X 10.7 and I try to get info on any port that uses the Qt5 PortGroup, I get the error that "Port qt56-qtbase not found". A little searching finds that in the qt5-1.0 PortGroup, the proc "qt5.get_default_name" returns "qt56" for this OS version, which is then used as the base for the Qt5 ports: qt56-qtbase, etc The issue is that there are no qt56* ports -- "port search qt56" returns "No match for qt56 found". If I insert "set qt_name qt5" -before- the qt5 PortGroup is called, then everything works as expected, and I can install qt5-qtbase (5.6.2) and it works, plus or minus. Am I missing something? - MLD
Re: Postfix and the system.log
On Jan 25, 2017, at 1:39 PM, Johannes Kastlwrote: > > I just tried to get the macports postfix running on my macos Sierra > machine. But I could not get useful logs out of it. you're looking in the wrong place. For stuff built on Sierra, logging goes through apple's new logging system. see the 'log' manpage. To replicate tail -f /var/log/mail.log you'd do something like: log stream --style syslog --type log --predicate '(processImagePath contains "postfix")' -- Daniel J. Luke
Re: question for the "base gurus"
On Wed, Jan 25, 2017 at 4:10 AM, René J.V. Bertinwrote: > Why yes indeed, but then the question becomes why the umask would > sometimes get set to 0255. Does that sound like a value that base might use > in certain conditions? I never use umask myself, one of those things I > shoot myself in the foot with too easily. There was at least one past bugfix where the code (for "install" of directories, iirc?) was inappropriately using the umask directly. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
Re: Your message to macports-changes awaits moderator approval
On 2017-01-25 13:50, John Patrick wrote: > I'm getting these emails too for pull requests I created that have > been approved. > > Is someone able to whitelist github sending emails to the > macport-changes list... Sorry for the inconvenience, these mails are certainly not intended to go out to you. This is not GitHub, we generate these mails using git-multimail after receiving the WebHook notification, with the JSON being piped into the trac-github-update.py hook [1]. For example, this is the corresponding report: --- Your message was held for moderation because SpamAssassin gave the message a score of 6.2 for the following reasons: HEADER_FROM_DIFFERENT_DOMAINS, HEADER_SPAM, HTML_MESSAGE, HTML_MIME_NO_HTML_TAG, MIME_HTML_ONLY, NO_RELAYS, TO_NO_BRKTS_HTML_ONLY, URIBL_BLOCKED --- Unfortunately, this report does not include the individual scores, but probably the highest score was given for the spoofed From address and the HTML only content. Maybe we should change to only one static sender instead of spoofing the >From address, which would also avoid this backscatter of moderation notices. Thoughts? SpamAssassin is integrated into mailman via the global pipeline [2], such that all posts for all mailing lists are filtered through that first. Before being handed off to mailman, postfix already adds an Approved header with the corresponding list post password to the mail. This is apparently not enough to circumvent/pass the spam filter. I manually moderated all the mails in the queue right now. Rainer [1] https://github.com/macports/trac.macports.org/blob/master/plugins/hooks/trac-github-update.py [2] http://www.jamesh.id.au/articles/mailman-spamassassin/
Re: [macports-ports] branch master updated: emacs: Rev-bump due to imagemagick changes
> On Jan 24, 2017, at 15:20, Jeremy Huddleston Sequoia> wrote: > > >> On Jan 24, 2017, at 01:32, Ryan Schmidt wrote: >> >> >>> On Jan 23, 2017, at 21:05, Jeremy Huddleston Sequoia >>> wrote: >>> commit b45c6c288b90421df0407b17a5885033bfb4efdd >>> >>> Author: Jeremy Huddleston Sequoia >>> AuthorDate: Mon Jan 23 19:05:04 2017 -0800 >>> >>> >>> emacs: Rev-bump due to imagemagick changes >>> >> I didn't include that in >> https://github.com/macports/macports-ports/commit/f8d86e8444b1c125ca3e3724deabb0d51021163c >> because emacs doesn't actually use ImageMagick; see >> https://trac.macports.org/ticket/53315. > > If by "doesn't actually use" you mean that it's linking the library without > any purpose (no symbol linkage, no initializers, etc), then that should > certainly be fixed, but it would still require a revbump (unless the link is > weak). > > In this particular case, it does indeed look like emacs is making use of > ImageMagick: > > ~ $ nm -m /opt/local/bin/emacs | grep libMagick > (undefined) external _AcquireExceptionInfo (from > libMagickCore-6.Q16) > (undefined) external _CloneMagickWand (from libMagickWand-6.Q16) > (undefined) external _DestroyExceptionInfo (from > libMagickCore-6.Q16) > (undefined) external _DestroyMagickWand (from > libMagickWand-6.Q16) > (undefined) external _DestroyPixelIterator (from > libMagickWand-6.Q16) > (undefined) external _DestroyPixelWand (from > libMagickWand-6.Q16) > (undefined) external _DestroyString (from libMagickCore-6.Q16) > (undefined) external _GetMagickList (from libMagickCore-6.Q16) > (undefined) external _MagickCropImage (from libMagickWand-6.Q16) > (undefined) external _MagickExportImagePixels (from > libMagickWand-6.Q16) > (undefined) external _MagickGetException (from > libMagickWand-6.Q16) > (undefined) external _MagickGetImage (from libMagickWand-6.Q16) > (undefined) external _MagickGetImageDelay (from > libMagickWand-6.Q16) > (undefined) external _MagickGetImageDispose (from > libMagickWand-6.Q16) > (undefined) external _MagickGetImageHeight (from > libMagickWand-6.Q16) > (undefined) external _MagickGetImagePage (from > libMagickWand-6.Q16) > (undefined) external _MagickGetImageSignature (from > libMagickWand-6.Q16) > (undefined) external _MagickGetImageWidth (from > libMagickWand-6.Q16) > (undefined) external _MagickGetNumberImages (from > libMagickWand-6.Q16) > (undefined) external _MagickMergeImageLayers (from > libMagickWand-6.Q16) > (undefined) external _MagickReadImage (from libMagickWand-6.Q16) > (undefined) external _MagickReadImageBlob (from > libMagickWand-6.Q16) > (undefined) external _MagickRelinquishMemory (from > libMagickWand-6.Q16) > (undefined) external _MagickRotateImage (from > libMagickWand-6.Q16) > (undefined) external _MagickScaleImage (from > libMagickWand-6.Q16) > (undefined) external _MagickSetFilename (from > libMagickWand-6.Q16) > (undefined) external _MagickSetImageBackgroundColor (from > libMagickWand-6.Q16) > (undefined) external _MagickSetIteratorIndex (from > libMagickWand-6.Q16) > (undefined) external _MagickWandGenesis (from > libMagickWand-6.Q16) > (undefined) external _MagickWandTerminus (from > libMagickWand-6.Q16) > (undefined) external _NewMagickWand (from libMagickWand-6.Q16) > (undefined) external _NewPixelIterator (from > libMagickWand-6.Q16) > (undefined) external _NewPixelWand (from libMagickWand-6.Q16) > (undefined) external _PixelGetAlpha (from libMagickWand-6.Q16) > (undefined) external _PixelGetMagickColor (from > libMagickWand-6.Q16) > (undefined) external _PixelGetNextIteratorRow (from > libMagickWand-6.Q16) > (undefined) external _PixelSetBlue (from libMagickWand-6.Q16) > (undefined) external _PixelSetGreen (from libMagickWand-6.Q16) > (undefined) external _PixelSetIteratorRow (from > libMagickWand-6.Q16) > (undefined) external _PixelSetMagickColor (from > libMagickWand-6.Q16) > (undefined) external _PixelSetRed (from libMagickWand-6.Q16) > (undefined) external _PixelSyncIterator (from > libMagickWand-6.Q16) > > --Jeremy > No, I meant the configure script determined that ImageMagick was not installed and emacs therefore wasn't using ImageMagick in any way at all. Looks like it's different on your system than on mine.
Your message to macports-changes awaits moderator approval
On 1/25/17 7:50 AM, macports-changes-ow...@lists.macports.org wrote: Your mail to 'macports-changes' with the subject [macports-ports] branch master updated: miredo: adopt and update to 1.2.6 Is being held until the list moderator can review it for approval. The reason it is being held: SpamAssassin identified this message as possible spam (score 6.2) Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: https://lists.macports.org/mailman/confirm/macports-changes/...