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

[MacPorts] #46832: sombrero() causes crash with GUI, produces plot w/ warnings in CLI
by MacPorts 04 Jun '16

04 Jun '16

#46832: sombrero() causes crash with GUI, produces plot w/ warnings in CLI --------------------+-------------------------------- Reporter: vjo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: octave --------------------+-------------------------------- When I attempt to display the classic "sombrero()" plot using octave in GUI mode, I get a crash. The backtrace is: Crashed Thread: 1 Dispatch queue: com.apple.libdispatch-manager Exception Type: EXC_CRASH (SIGSEGV) Exception Codes: 0x0000000000000000, 0x0000000000000000 Thread 0:: Dispatch queue: com.apple.main-thread 0 libGL.dylib 0x00007fff8d90d3e4 glMatrixMode + 15 1 __init_fltk__.oct 0x0000000112c65637 OpenGL_fltk::resize(int, int, int, int) + 33 2 libfltk.1.3.dylib 0x0000000112cd4ece Fl_Group::resize(int, int, int, int) + 540 3 libfltk.1.3.dylib 0x0000000112cb9b0d Fl_Window::resize(int, int, int, int) + 539 4 __init_fltk__.oct 0x0000000112c600ea plot_window::draw() + 438 5 libfltk.1.3.dylib 0x0000000112cb6a9e Fl_X::flush() + 80 6 libfltk.1.3.dylib 0x0000000112cb6a33 -[FLView drawRect:] + 153 7 com.apple.AppKit 0x00007fff9b77cb19 -[NSView _drawRect:clip:] + 4238 8 com.apple.AppKit 0x00007fff9b77b17a -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1875 9 com.apple.AppKit 0x00007fff9b77b57e -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 10 com.apple.AppKit 0x00007fff9b779016 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 913 11 com.apple.AppKit 0x00007fff9b778773 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 333 12 com.apple.AppKit 0x00007fff9b7752cb -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2761 13 com.apple.AppKit 0x00007fff9b753e2d -[NSView displayIfNeeded] + 1876 14 com.apple.AppKit 0x00007fff9b7711c5 -[NSWindow displayIfNeeded] + 232 15 com.apple.AppKit 0x00007fff9b7ae322 _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 936 16 com.apple.AppKit 0x00007fff9bd770e1 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_invoke1531 + 46 17 com.apple.CoreFoundation 0x00007fff9506ada7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 18 com.apple.CoreFoundation 0x00007fff9506ad00 __CFRunLoopDoObservers + 368 19 com.apple.CoreFoundation 0x00007fff9505ce08 __CFRunLoopRun + 872 20 com.apple.CoreFoundation 0x00007fff9505c858 CFRunLoopRunSpecific + 296 21 com.apple.HIToolbox 0x00007fff8e54baef RunCurrentEventLoopInMode + 235 22 com.apple.HIToolbox 0x00007fff8e54b76e ReceiveNextEventCommon + 179 23 com.apple.HIToolbox 0x00007fff8e54b6ab _BlockUntilNextEventMatchingListInModeWithFilter + 71 24 com.apple.AppKit 0x00007fff9b64ef81 _DPSNextEvent + 964 25 com.apple.AppKit 0x00007fff9b64e730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194 26 com.apple.AppKit 0x00007fff9b642593 -[NSApplication run] + 594 27 QtGui 0x00000001058e721b QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2027 28 QtCore 0x00000001066b261f QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 495 29 QtCore 0x00000001066b5857 QCoreApplication::exec() + 199 30 liboctgui.0.dylib 0x000000010491f125 octave_start_gui(int, char**, bool) + 747 31 libdyld.dylib 0x00007fff92d095c9 start + 1 Thread 1 Crashed:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff8e360232 kevent64 + 10 1 libdispatch.dylib 0x00007fff9097ca6a _dispatch_mgr_thread + 52 When I do the same w/ octave in CLI mode, the plot appears, but only after several of these errors are displayed: octave:1> sombrero() Feb 11 14:58:59 betty octave-cli-3.8.2[96682] <Error>: CGContextFillRects: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update. Feb 11 14:58:59 betty octave-cli-3.8.2[96682] <Error>: CGContextMoveToPoint: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update. Feb 11 14:58:59 betty octave-cli-3.8.2[96682] <Error>: CGContextAddLineToPoint: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update. Feb 11 14:58:59 betty octave-cli-3.8.2[96682] <Error>: CGContextDrawPath: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update. Feb 11 14:58:59 betty octave-cli-3.8.2[96682] <Error>: CGContextMoveToPoint: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update. Feb 11 14:58:59 betty octave-cli-3.8.2[96682] <Error>: CGContextAddLineToPoint: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update. Feb 11 14:58:59 betty octave-cli-3.8.2[96682] <Error>: CGContextDrawPath: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update. It appears to be related to usage of the fltk toolkit; neither of these errors occurs if I put: graphics_toolkit("gnuplot"); in my .octaverc. -- Ticket URL: <https://trac.macports.org/ticket/46832> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #48094: OpenGTL is dead
by MacPorts 03 Jun '16

03 Jun '16

#48094: OpenGTL is dead ----------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: m | Port: OpenGTL ----------------------------+-------------------------------- The OpenGTL package is no longer available upstream. See also http://pkgs.fedoraproject.org/cgit/OpenGTL.git/commit/?id=bb9462088ca0d7429… If calligra no longer depends on it, and there are no other dependent packages, I propose that we remove this port. -- Ticket URL: <https://trac.macports.org/ticket/48094> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #48959: build fails
by MacPorts 01 Jun '16

01 Jun '16

#48959: build fails ---------------------------+-------------------------------- Reporter: elfprince13@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: opencv ---------------------------+-------------------------------- "use of undeclared identifier 'avcodec_free_frame'; did you mean 'avcodec_get_name'?" in the log file - is there a mismatched dependency version or something? -- Ticket URL: <https://trac.macports.org/ticket/48959> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #47338: mecab, p5-mecab: new repository, update homepage, master_sites, livecheck
by MacPorts 31 May '16

31 May '16

#47338: mecab, p5-mecab: new repository, update homepage, master_sites, livecheck ----------------------+----------------------------- Reporter: devans@… | Owner: hum@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: mecab, p5-mecab ----------------------+----------------------------- The mecab repository has moved from googlecode to github. New home page: http://taku910.github.io/mecab/ [[BR]] GitHub repo: https://github.com/taku910/mecab -- Ticket URL: <https://trac.macports.org/ticket/47338> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #48781: cadabra @ 1.33 build failure
by MacPorts 30 May '16

30 May '16

#48781: cadabra @ 1.33 build failure -----------------------+-------------------------------- Reporter: uta1013@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: cadabra | Port: cadabra -----------------------+-------------------------------- To whom it may concern. I am interesting in making use of cadabra and tried installing, but I did not make it.I got the following error message: {{{ Error: org.macports.build for port cadabra returned: command execution failed Please see the log file for port cadabra for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_cadabra/cadabra/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port cadabra failed }}} For the log file, please see the attachment. I appreciate it very much if you could help me. Thank you very much. Sincerely. -- Ticket URL: <https://trac.macports.org/ticket/48781> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #46956: base should keep track of explicitly requested variants on install and only preserve those on upgrade
by MacPorts 30 May '16

30 May '16

#46956: base should keep track of explicitly requested variants on install and only preserve those on upgrade -------------------------+-------------------------------- Reporter: cal@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.3 Keywords: | Port: -------------------------+-------------------------------- Base currently tries to preserve all installed variants when upgrading a port. In the case of version choice variants (such as perl5_16, llvm33, ...) this leads to a situation where a user does not actively choose a variant when installing, but the variant is still preserved even when the port's default variant changes later on. Users no longer get binary archives for these non-default variants and generally end up on rather outdated systems. We should modify MacPorts to only preserve variants that have been explicitly requested. To do that, I propose we add a new database field `requested_variants` to the ports table of the registry. It should have the same format as the currently available `variants` and `negated_variants` field (which could, IMHO, be merged into one). The installation code should be modified to store the list of variants explicitly requested on the command line in this field. The upgrade code should also be modified to preserve the list of requested variants, not the list of all variants of a port. A couple pointers to a possible implementation: - The database field would have to be added along with an upgrade path in source:trunk/base/src/cregistry/sql.c - The registry sqlite access code should be modified to support the field, in source:trunk/base/src/registry2.0/entryobj.c - The registry API should be modified to support passing the field, in source:trunk/base/src/registry2.0/receipt_sqlite.c - The macports installation and upgrade routines should be modified as described above, in source:trunk/base/src/macports1.0/macports.tcl, source:trunk/base/src/port1.0/portinstall.tcl -- Ticket URL: <https://trac.macports.org/ticket/46956> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #45460: qemu-usermode
by MacPorts 29 May '16

29 May '16

#45460: qemu-usermode ----------------------------+-------------------------------- Reporter: intermediadc@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: ----------------------------+-------------------------------- 404 13:16 Fetching archive failed:: The requested URL returned error: 404 qemu-usermode-0.9.0_0.darwin_9.ppc.tbz2 doesn't seem to exist -- Ticket URL: <https://trac.macports.org/ticket/45460> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49383: MariaDB 10.1 became stable
by MacPorts 27 May '16

27 May '16

#49383: MariaDB 10.1 became stable -------------------------------+-------------------------------- Reporter: willem+macports@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: mariadb-10.1 -------------------------------+-------------------------------- The packages mariadb-10.1-server and mariadb-10.1 are still on version 10.1.4 (beta) whilst the latest release (10.1.8) is [https://mariadb.com/kb/en/mariadb/what-is-mariadb-101/ deemed stable]. Can the portfiles be updated to reflect the latest state? -- Ticket URL: <https://trac.macports.org/ticket/49383> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #45665: ilmbase compile error
by MacPorts 26 May '16

26 May '16

#45665: ilmbase compile error ---------------------------------+--------------------------------- Reporter: shuttle1978@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.2 Keywords: ilmbase ImageMagick | Port: ilmbase ImageMagick ---------------------------------+--------------------------------- Hi, I've tried to install ilmbase (for install ImageMagick), with command: sudo port install ilmbase and I receive the error: '''---> Computing dependencies for ilmbase ---> Fetching archive for ilmbase ---> Attempting to fetch ilmbase-1.0.2_0+universal.darwin_13.i386-x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/ilmbase ---> Attempting to fetch ilmbase-1.0.2_0+universal.darwin_13.i386-x86_64.tbz2 from http://lil.fr.packages.macports.org/ilmbase ---> Attempting to fetch ilmbase-1.0.2_0+universal.darwin_13.i386-x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ilmbase ---> Fetching distfiles for ilmbase ---> Verifying checksums for ilmbase ---> Extracting ilmbase ---> Applying patches to ilmbase ---> Configuring ilmbase ---> Building ilmbase ---> Staging ilmbase into destroot Error: org.macports.destroot for port ilmbase returned: command execution failed Please see the log file for port ilmbase for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ilmbase/ilmbase/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ilmbase failed''' Ho to resolve the error? I've tried also to use clean and install, but doesn't work. The error that I receive with ImageMagick is: '''Error: org.macports.destroot for port ilmbase returned: command execution failed Error: Failed to install ilmbase Please see the log file for port ilmbase for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ilmbase/ilmbase/main.log Error: The following dependencies were not installed: openexr ilmbase openjpeg urw-fonts webp To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ImageMagick failed ''' I'm using MacOS X 10.9 -- Ticket URL: <https://trac.macports.org/ticket/45665> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #49356: py26-pyqt3, py26-sip-qt3: can we remove these?
by MacPorts 25 May '16

25 May '16

#49356: py26-pyqt3, py26-sip-qt3: can we remove these? --------------------+------------------------------------- Reporter: petr@… | Owner: blair@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: py26-pyqt3 py26-sip-qt3 --------------------+------------------------------------- Can we these to ports? There are not python27 equivalents around, but I guess that is acceptable in this case. -- Ticket URL: <https://trac.macports.org/ticket/49356> MacPorts <https://www.macports.org/> Ports system for OS X

1 10