November 2015 - macports-tickets - lists.macosforge.org

[MacPorts] #49787: Mailing list messages not delivered, subscriptions disabled due to Yahoo Mail now requiring DMARC
by MacPorts 11 Jan '16

11 Jan '16

#49787: Mailing list messages not delivered, subscriptions disabled due to Yahoo Mail now requiring DMARC ----------------------------+--------------------- Reporter: ryandesign@… | Owner: admin@… Type: defect | Status: new Priority: High | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+--------------------- At 2:29 PM Central time today we received 42 mailing list subscription disabled bounces. They said things like: {{{ 552 l8Eq1r00M0drVCp018ErwH Message fails DMARC verification. }}} {{{ 554 5.7.9 Message not accepted for policy reasons. See https://help.yahoo.com/kb/postmaster/SLN7253.html }}} {{{ 550 5.7.1 The messages violates the DMARC policy of yahoo.com (d8c59a45 -921e-11e5-a822-db253d9e0b64) }}} {{{ 550 5.2.0 l8Eq1r05C0bG8YH018Er6K Message rejected due to DMARC. Please see http://postmaster.comcast.net/smtp-error-codes.php#DM000001 }}} {{{ 550 5.7.0 (COL004-MC6F14) Unfortunately, messages from (17.151.62.25) on behalf of (yahoo.com) could not be delivered due to domain owner policy restrictions. }}} It sounds like Yahoo's mail server now requires messages to be sent in compliance with [https://dmarc.org/ DMARC], and our mailing lists do not do this. The effect is that when a Yahoo Mail user who has subscribed to one of our lists sends a message to the list, it gets sent by our list to the other subscribers. For those subscribers using a mail service that checks DMARC, their mail servers reject the message because the DMARC verification fails because the message was actually sent by our server not by a Yahoo Mail server. This causes the subscriber's mail server to send a bounce back to our mailing list server, and after a few of those, our mailing list server disables the subscriber's subscription. [https://help.yahoo.com/kb/postmaster/SLN7253.html Yahoo's own page on this problem] suggests we "Follow industry standards" and: > change your sending behavior by adding the mailing lists’ address to the "From:" line, rather than the sender’s address. Also, enter the actual user/sender address into the "Reply-To:" line." I do not believe we should do this, because this contradicts RFC2822 which states: > When the "Reply-To:" field is present, it indicates the mailbox(es) to which the author of the message suggests that replies be sent. Our mailing list is not the author of the message, so our mailing list may not change the Reply-To line. See also [https://woozle.org/~neale/papers /reply-to-still-harmful.html “Reply-To” Munging Still Considered Harmful. Really.] The [https://dmarc.org/wiki/FAQ#I_operate_a_mailing_list_and_I_want_to_interoper… DMARC FAQ] has an entry about what list operators should do, but there are several choices and I don't know which, if any, are appropriate. -- Ticket URL: <https://trac.macports.org/ticket/49787> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #47403: New port: pgcli
by MacPorts 11 Jan '16

11 Jan '16

#47403: New port: pgcli ---------------------------+-------------------------------- Reporter: xeron.oskom@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: pgcli ---------------------------+-------------------------------- Portfile attached. Depends on: #47399 #47400 #47401 #47402. -- Ticket URL: <https://trac.macports.org/ticket/47403> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #49790: gpg-agent @2.0.28 high cpu
by MacPorts 11 Jan '16

11 Jan '16

#49790: gpg-agent @2.0.28 high cpu ------------------------------------+-------------------------------- Reporter: herminio.hernandezjr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: gnupg | Port: gpg-agent ------------------------------------+-------------------------------- I am gnupg2 on OSX 10.5.8 and I a seeing really high cpu usage out of gpg- agent. I will also attach a portion of my system log so you can see the error I am seeing -- Ticket URL: <https://trac.macports.org/ticket/49790> MacPorts <https://www.macports.org/> Ports system for OS X

1 18

[MacPorts] #48823: MPlayer falling back to pbuffer on OS X 10.11
by MacPorts 11 Jan '16

11 Jan '16

#48823: MPlayer falling back to pbuffer on OS X 10.11 -----------------------------+-------------------------------- Reporter: oliver.psotta@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: MPlayer @1.1_9 -----------------------------+-------------------------------- On playback of different video files MPlayer always loops this message: {{{ Fallingback to pbuffer. FBO status is 360540/ 0 7% 4% 0.3% 0 0 }}} Before the loop this message was printed: {{{ [ASPECT] Warning: No suitable new res found! Fallingback to pbuffer. FBO status is 36054 [swscaler @ 0x10e98a950]Warning: dstStride is not aligned! ->cannot do aligned memory accesses anymore [swscaler @ 0x10e98a950]Warning: data is not aligned! This can lead to a speedloss }}} OS X El Capitan Public Beta Version 6 -- Ticket URL: <https://trac.macports.org/ticket/48823> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #48420: p5.22-io-socket-ip' not found
by MacPorts 10 Jan '16

10 Jan '16

#48420: p5.22-io-socket-ip' not found ----------------------------------------+-------------------------------- Reporter: michael.francis.corcoran@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: ----------------------------------------+-------------------------------- I'm trying do do a port selfupdate/ port upgrade outdated but the upgrade fails as follows: % sudo port selfupdate Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.3.3 installed, MacPorts base version 2.3.3 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated % sudo port upgrade outdated Warning: No port p5.22-io-socket-ip found in the index. ---> Computing dependencies for p5.22-io-socket-ssl Error: Dependency 'p5.22-io-socket-ip' not found. Error: Problem while installing p5.22-io-socket-ssl To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets p5.22-io-socket-ip is listed as an available port on the macports.org available ports list, so I'm not sure what the problem is... -- Ticket URL: <https://trac.macports.org/ticket/48420> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #48862: astyle 2.05.1
by MacPorts 10 Jan '16

10 Jan '16

#48862: astyle 2.05.1 --------------------+-------------------------------- Reporter: jhi@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: --------------------+-------------------------------- http://astyle.sourceforge.net/notes.html shows Artistic Style 2.05.1 (December 2014) while macports has Artistic Style 2.04 (November 2013) -- Ticket URL: <https://trac.macports.org/ticket/48862> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #48928: tbb: update to 4.4-20150728
by MacPorts 10 Jan '16

10 Jan '16

#48928: tbb: update to 4.4-20150728 --------------------------+-------------------- Reporter: ryandesign@… | Owner: sean@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Keywords: haspatch | Port: tbb --------------------------+-------------------- This patch updates tbb to version 4.4-20150728. May I commit it? -- Ticket URL: <https://trac.macports.org/ticket/48928> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #47526: libcaca @ 0.99.beta19: add x11 variant as default
by MacPorts 10 Jan '16

10 Jan '16

#47526: libcaca @ 0.99.beta19: add x11 variant as default ----------------------+-------------------------------- Reporter: mk@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: libcaca ----------------------+-------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/47526> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49497: openssh @7.1p1: tcp_wrappers no longer supported
by MacPorts 10 Jan '16

10 Jan '16

#49497: openssh @7.1p1: tcp_wrappers no longer supported ----------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: haspatch | Port: openssh ----------------------------+-------------------------------- As of version 6.7p1 openssh no longer supports tcp_wrappers: https://lwn.net/Articles/615173/ -- Ticket URL: <https://trac.macports.org/ticket/49497> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49658: atlas fails to due to incorrectly named directory in path to libgfortran.dylib
by MacPorts 10 Jan '16

10 Jan '16

#49658: atlas fails to due to incorrectly named directory in path to libgfortran.dylib ------------------------------+-------------------------------- Reporter: robballantyne3@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ------------------------------+-------------------------------- The log file showed the following error: :info:build cd RCW_tMp ; /usr/bin/clang -O3 -fomit-frame-pointer -fPIC -march=native -mfma -dynamiclib -o ../libsatlas.dylib \ :info:build -install_name /opt/local/lib/libsatlas.dylib -current_version 3.10.2 \ :info:build -compatibility_version 3.10.2 *.o -lpthread -lm /opt/local/lib/gcc4.9/libgfortran.dylib :info:build clang: error: no such file or directory: '/opt/local/lib/gcc4.9/libgfortran.dylib' :info:build make[1]: *** [dylib] Error 1 :info:build make: *** [shared_all] Error 2 The library was available as /opt/local/lib/gcc49/libgfortran.dylib. I was able to build by use of a simple symlink (cd /opt/local/lib; ln -s gcc49 gcc4.9) -- Ticket URL: <https://trac.macports.org/ticket/49658> MacPorts <https://www.macports.org/> Ports system for OS X

1 6