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

[MacPorts] #48134: p5-sdl unusable
by MacPorts 13 Jan '16

13 Jan '16

#48134: p5-sdl unusable -----------------------------+-------------------------------- Reporter: johan.schurer@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: Perl, SDL | Port: p5-sdl -----------------------------+-------------------------------- Exception message: {{{ 2015-06-21 23:21:27.233 perl[40433:507] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Error (1000) creating CGSWindow on line 263' *** First throw call stack: ( 0 CoreFoundation 0x00007fff80a3725c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff84814e75 objc_exception_throw + 43 2 CoreFoundation 0x00007fff80a3710c +[NSException raise:format:] + 204 3 AppKit 0x00007fff8b48ce95 _NSCreateWindowWithOpaqueShape2 + 1403 4 AppKit 0x00007fff8b48ba21 -[NSWindow _commonAwake] + 3720 5 AppKit 0x00007fff8b367400 -[NSWindow _commonInitFrame:styleMask:backing:defer:] + 882 6 AppKit 0x00007fff8b366882 -[NSWindow _initContent:styleMask:backing:defer:contentView:] + 1054 7 AppKit 0x00007fff8b366458 -[NSWindow initWithContentRect:styleMask:backing:defer:] + 45 8 libSDL-1.2.0.dylib 0x000000010e2ad856 -[SDL_QuartzWindow initWithContentRect:styleMask:backing:defer:] + 279 9 libSDL-1.2.0.dylib 0x000000010e2ab29b QZ_SetVideoMode + 1417 10 libSDL-1.2.0.dylib 0x000000010e2a25a9 SDL_SetVideoMode + 906 11 Video.bundle 0x000000010e4849f4 XS_SDL__Video_set_video_mode + 516 12 libperl.dylib 0x000000010e15814e Perl_pp_entersub + 1166 13 libperl.dylib 0x000000010e151366 Perl_runops_standard + 22 14 libperl.dylib 0x000000010e0dcaa5 perl_run + 901 15 perl 0x000000010e0b8ddb main + 155 16 libdyld.dylib 0x00007fff823795fd start + 1 17 ??? 0x0000000000000002 0x0 + 2 ) libc++abi.dylib: terminating with uncaught exception of type NSException Abort trap: 6 }}} Steps to reproduce:\\ Install p5-sdl, create simple file with the following contents and run it: {{{ #!/opt/local/bin/perl use strict; use warnings; use SDL; use SDLx::App; my $app = new SDLx::App( -title => 'kaboom!', -width => 1280, -height => 800, -depth => 32, ); }}} I'm running OSX 10.9.5 and Xcode: 6.1.1 (6A2008a) -- Ticket URL: <https://trac.macports.org/ticket/48134> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #49890: soxr 0.1.2 Problem while installing soxr
by MacPorts 12 Jan '16

12 Jan '16

#49890: soxr 0.1.2 Problem while installing soxr ---------------------------+-------------------------------- Reporter: yvan.strahm@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ---------------------------+-------------------------------- Unable to install soxr -- Ticket URL: <https://trac.macports.org/ticket/49890> MacPorts <https://www.macports.org/> Ports system for OS X

1 16

[MacPorts] #47792: TORA compilation errors
by MacPorts 12 Jan '16

12 Jan '16

#47792: TORA compilation errors -----------------------+-------------------------------- Reporter: iguinea@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: Compiler | Port: TORA -----------------------+-------------------------------- When trying to install tora i receive the following error when compiling,... :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_TOra/TOra/work/tora-2.1.3/src/tob rowsertable.cpp:42: :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_TOra/TOra/work/tora-2.1.3/src/uti ls.h:47: :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/list:2060:18: error: invalid operands to binary expression ('const value_type' (aka 'const toExtract::columnInfo') and 'const value_type' (aka 'const toExtract::columnInfo')) :info:build if (*__i == __x) :info:build ~~~~ ^ ~~~ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_TOra/TOra/work/tora-2.1.3/src/tobrowsertable.cpp:654:21 : note: in instantiation of member function 'std::__1::list<toExtract::columnInfo, std::__1::allocator<toExtract::columnInfo> >::remove' requested here :info:build Columns.remove(*column); :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_TOra/TOra/work/tora-2.1.3/src/toextract.h:791:14: note: candidate function not viable: 'this' argument has type 'const value_type' (aka 'const toExtract::columnInfo'), but method is not marked const :info:build bool operator ==(const columnInfo &inf) :info:build ^ :info:build /opt/local/include/QtCore/qglobal.h:2063:13: note: candidate function not viable: no known conversion from 'const value_type' (aka 'const toExtract::columnInfo') to 'QBool' for 1st argument :info:build inline bool operator==(QBool b1, bool b2) { return !b1 == !b2; } :info:build ^ :info:build /opt/local/include/QtCore/qglobal.h:2064:13: note: candidate function not viable: no known conversion from 'const value_type' (aka 'const toExtract::columnInfo') to 'bool' for 1st argument :info:build inline bool operator==(bool b1, QBool b2) { return !b1 == !b2; } :info:build ^ :info:build /opt/local/include/QtCore/qglobal.h:2065:13: note: candidate function not viable: no known conversion from 'const value_type' (aka 'const toExtract::columnInfo') to 'QBool' for 1st argument :info:build inline bool operator==(QBool b1, QBool b2) { return !b1 == !b2; } :info:build ^ :info:build /opt/local/include/QtCore/qsize.h:156:13: note: candidate function not viable: no known conversion from 'const value_type' (aka 'const toExtract::columnInfo') to 'c : -- Ticket URL: <https://trac.macports.org/ticket/47792> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #50080: clang-3.8+universal fails to build
by MacPorts 12 Jan '16

12 Jan '16

#50080: clang-3.8+universal fails to build --------------------------+-------------------------------- Reporter: nneonneo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: buildfailure | Port: clang-3.8 --------------------------+-------------------------------- While trying to upgrade clang-3.8 today, I received a build failure. I have the +universal variant selected. The problem appears to be due to ThreadSanitizer being enabled on the 32-bit build: {{{ :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_sea.us.rsync.macports.org_release_tarballs_ports_lang_llvm-3.8/clang-3.8/work/trunk/projects /compiler-rt/lib/tsan/rtl/tsan_flags.cc:18: :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_sea.us.rsync.macports.org_release_tarballs_ports_lang_llvm-3.8/clang-3.8/work/trunk/projects /compiler-rt/lib/tsan/rtl/tsan_rtl.h:44: :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_sea.us.rsync.macports.org_release_tarballs_ports_lang_llvm-3.8/clang-3.8/work/trunk/projects /compiler-rt/lib/tsan/rtl/tsan_platform.h:19:3: error: "Only 64-bit is supported" }}} The complete build log is attached. -- Ticket URL: <https://trac.macports.org/ticket/50080> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #48690: Upgrading "guile18" fails
by MacPorts 11 Jan '16

11 Jan '16

#48690: Upgrading "guile18" fails --------------------+-------------------------------- Reporter: dave@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: guile18 --------------------+-------------------------------- Uograding MacPorts failed when building "guile18": ---> Staging guile18 into destroot Error: org.macports.destroot for port guile18 returned: command execution failed Please see the log file for port guile18 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/main.log Error: Unable to upgrade port: 1 Error rebuilding guile18 while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 395) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_upgrade" line 25) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 103) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 5268) ozzie:~ dave$ -- Ticket URL: <https://trac.macports.org/ticket/48690> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #46717: xfwm4: improved stacking in rooted mode
by MacPorts 11 Jan '16

11 Jan '16

#46717: xfwm4: improved stacking in rooted mode -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: xfwm4 -------------------------+-------------------------------- Most window managers are not prepared, when running under XQuartz or similar in rooted mode, to restack X11 windows outside of the stacking location the X server is itself in. As a result, clicking on a background X11 window will make the X server active and raise the X window w.r.t. other X windows, but it will not raise the window from behind "native" (Cocoa/Aqua) windows. I'm attaching a patch that (re)enables this for "global" restacking operations (i.e. when xfwm4 does not try to restack a window w.r.t. some sibling window). Bonus screenshot: xfwm4 with the Mint-X theme, epiphany using the GTk3 theme from port:oxygen-gtk3 and the +infinality variants of port:freetype, port:fontconfig and port:cairo. -- Ticket URL: <https://trac.macports.org/ticket/46717> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[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