September 2010 - macports-tickets - lists.macosforge.org

[MacPorts] #25976: Add OTR Support to Weechat
by MacPorts 21 Feb '14

21 Feb '14

#25976: Add OTR Support to Weechat --------------------------------+------------------------------------------- Reporter: frenchja@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: weechat otr | Port: weechat --------------------------------+------------------------------------------- The instructions available here (http://wiki.flashtux.org/wiki/WeeChat /irc-otr) don't compile the libotr plugin for Weechat. It results in the log attached. It would be great if we could add in +otr as a configuration option. I apologize but I really can't understand the log or I'd add more detail. -- Ticket URL: <http://trac.macports.org/ticket/25976> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #26208: WeeChat 0.3.2 double plugins
by MacPorts 21 Feb '14

21 Feb '14

#26208: WeeChat 0.3.2 double plugins -----------------------------------+---------------------------------------- Reporter: f.p.verhoog@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: plugins | Port: weechat -----------------------------------+---------------------------------------- in the plugins folder of weechat "/opt/local/lib/weechat/plugins/" are symlinks of the original plugins '''and''' the original plugins. Like symlink "alias.so" and the plugin "alias.0.so". wich gives errors at startup of weechat. the symlinks should be removed or the plugins should be in another folder. -- Ticket URL: <http://trac.macports.org/ticket/26208> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #19481: openssl: integration with OS X keychain broken
by MacPorts 16 Feb '14

16 Feb '14

#19481: openssl: integration with OS X keychain broken -----------------------------------+---------------------------------------- Reporter: lhunath@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: openssh ssh-agent ssh | Port: -----------------------------------+---------------------------------------- It appears that one of the more recent updates of openssl has broken its integration with the OS X keychain. My SSH keys that are in the OS X keychain are no longer added to the ssh-agent. Running `eval "$(/usr/bin/ssh-agent)"` and then `ssh-add -l` *does* show my keys as added to the agent, so the OS X provided openssl has no issues talking to my keychain. That makes macports' openssl rather useless for me. This issue is reminiscent of another open ticket on sysutils/screen which also causes problems with interaction between CLI applications and the OS X keychain (and other OS X utilities such as pbcopy/pbpaste): #18235 -- Ticket URL: <http://trac.macports.org/ticket/19481> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16201: Upgrading openssh overwrites user-modified config files
by MacPorts 16 Feb '14

16 Feb '14

#16201: Upgrading openssh overwrites user-modified config files ---------------------------------+------------------------------------------ Reporter: vinc17(a)macports.org | Owner: wms(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ The openssh port shouldn't overwrite user-modified config files (ssh_config and sshd_config), or should introduce some mechanism to do config file upgrades safely. For instance, contents between some markers could be preserved, e.g. {{{ # BEGIN local configuration ... # END local configuration }}} In such a case, such configuration should be near the beginning of the file. The ssh_config man page says: {{{ For each parameter, the first obtained value will be used. The configu- ration files contain sections separated by ``Host'' specifications, and that section is only applied for hosts that match one of the patterns given in the specification. The matched host name is the one given on the command line. Since the first obtained value for each parameter is used, more host- spe- cific declarations should be given near the beginning of the file, and general defaults at the end. }}} I don't know about sshd_config. I suppose that the same rule is applied. -- Ticket URL: <http://trac.macports.org/ticket/16201> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #15939: port install : in need of a progressbar
by MacPorts 14 Feb '14

14 Feb '14

#15939: port install : in need of a progressbar --------------------------------------+------------------------------------- Reporter: pc(a)anykey.de | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Low | Milestone: Component: base | Version: 1.6.0 Keywords: port install progressbar | --------------------------------------+------------------------------------- Installing bigger Distributions, like texlive_texmf-full (>125MB), I was wondering if everything is allright after some minutes of nothingness. I know that other *nix-packet-managers have a progressbar (some dots or whatever) so that the user is able to track the progress, at least having an idea if everything is allright. Since now I know I just have to wait, everything is fine for me. Thinking of other users - they would sometimes appreciate to have a progressbar when installing using port, I suppose. Thinking of gentoo-users sitting next to me, I would appreciate that anyway ;) -- Ticket URL: <http://trac.macports.org/ticket/15939> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #24927: update: Update highlight Portfile to release 2.16
by MacPorts 06 Feb '14

06 Feb '14

#24927: update: Update highlight Portfile to release 2.16 ---------------------------------------+------------------------------------ Reporter: lists@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: highlight ---------------------------------------+------------------------------------ Update the highlight Portfile to the latest release. {{{ --- Portfile +++ (clipboard) @@ -3,7 +3,7 @@ PortSystem 1.0 name highlight -version 2.4.8 +version 2.16 categories textproc devel platforms darwin maintainers groovie.org:pjenvey @@ -12,14 +12,16 @@ homepage http://www.andre-simon.de master_sites ${homepage}/zip/ -checksums sha1 091689fde96c9f4e3de75ea1b7c1838e8d25708c +checksums sha1 b5fed14bb1a973fe134dd2133766bb86fdc7494e use_bzip2 yes +use_configure no + configure { - reinplace "s|/usr/share/highlight/|${prefix}/share/${name}/|g" \ - ${worksrcpath}/highlight/datadir.cpp - reinplace "s|/etc/highlight/|${prefix}/etc/highlight/|g" \ - ${worksrcpath}/highlight/datadir.cpp + reinplace "s|^PREFIX = /usr$|PREFIX = ${prefix}|g" \ + ${worksrcpath}/makefile + reinplace "s|^conf_dir = /etc/highlight/$|conf_dir = ${prefix}/etc/highlight/|g" \ + ${worksrcpath}/makefile } # Avoid stripping the binary (-s flag) during linking as this corrupts the executable. @@ -27,16 +29,15 @@ platform darwin 8 { build.args LDFLAGS="" } set conf_file "filetypes.conf" -set old_conf_files { "scriptre.conf" "extensions.conf" } destroot { - xinstall -m 755 ${worksrcpath}/highlight/highlight ${destroot}${prefix}/bin + xinstall -m 755 ${worksrcpath}/src/highlight ${destroot}${prefix}/bin xinstall -m 755 -d ${destroot}${prefix}/etc/${name} - xinstall -m 644 ${worksrcpath}/${conf_file} \ - ${destroot}${prefix}/etc/${name}/${conf_file}.sample + xinstall -m 644 ${worksrcpath}/${conf_file} \ + ${destroot}${prefix}/etc/${name}/${conf_file}.sample xinstall -m 755 -d ${destroot}${prefix}/share/${name} - foreach dir { "langDefs" "themes" "indentSchemes" "helpmsg" } { + foreach dir { "langDefs" "themes" } { file copy ${worksrcpath}/${dir} ${destroot}${prefix}/share/${name} system "chmod 644 ${destroot}${prefix}/share/${name}/${dir}/*" } @@ -46,8 +47,8 @@ ${destroot}${prefix}/share/man/man1 xinstall -m 755 -d ${destroot}${prefix}/share/doc/${name} - foreach file { "AUTHORS" "README" "README_DE" "README_INDENT" "ChangeLog" \ - "COPYING" "INSTALL" } { + foreach file { "AUTHORS" "README" "README_DE" "ChangeLog" \ + "COPYING" "INSTALL" "README_LANGLIST" "README_REGEX" } { xinstall -m 644 ${worksrcpath}/${file} \ ${destroot}${prefix}/share/doc/${name} } @@ -55,13 +56,14 @@ file copy ${worksrcpath}/examples ${destroot}${prefix}/share/doc/${name} } +set old_conf_files { "scriptre.conf" "extensions.conf" } post-activate { # copy over the sample conf file if necessary if { ![file exists ${prefix}/etc/${name}/${conf_file}] } { file copy ${prefix}/etc/${name}/${conf_file}.sample \ ${prefix}/etc/${name}/${conf_file} } - + # warn the user of deprecated conf files set deprecated_conf_files {} foreach file $old_conf_files { @@ -84,4 +86,3 @@ } } } }}} -- Ticket URL: <http://trac.macports.org/ticket/24927> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #15571: request - uniform Portfile standard to handle the different possibilities of Fortran compilers
by MacPorts 29 Jan '14

29 Jan '14

#15571: request - uniform Portfile standard to handle the different possibilities of Fortran compilers -------------------------------------+-------------------------------------- Reporter: davidh(a)ipac.caltech.edu | Owner: markd(a)macports.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.6.0 Keywords: | -------------------------------------+-------------------------------------- I don't write code in Fortran, but some of the ports I use require Fortran. Different Portfiles depend on different Fortran compilers. Contrast fftw-3(g95, gfortran/gcc4.2, gfortan/gcc4.3) pgplot(g77 on PPC, gfortran/gcc4.2 on i386) and cfitsio(gfortran/gcc42). There are at least 4 compilers to choose from. My request: formulate a standard to allow any of the compilers to be selected with a variant. The fftw-3 Portfile comes closest with variants to select any one of 3 compilers. If possible, I'd like to see g77 deprecated. -- Ticket URL: <http://trac.macports.org/ticket/15571> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #20240: Openmpi problem with universal_arch = i386 x86_64
by MacPorts 28 Jan '14

28 Jan '14

#20240: Openmpi problem with universal_arch = i386 x86_64 ----------------------------------+----------------------------------------- Reporter: lvcargnini@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.7.1 Keywords: openmpi | Port: openmpi ----------------------------------+----------------------------------------- trying to install openmpi, with universal_arch = i386 x86_64, I get the following error: --> Configuring openmpi Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_openmpi/work/build" && /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_openmpi/work/openmpi-1.3.2/configure --prefix=/opt/local --with-xgrid --sysconfdir=/opt/local/etc/openmpi --includedir=/opt/local/include/openmpi --bindir=/opt/local/lib/openmpi/bin --mandir=/opt/local/share/man --enable-f77 --enable-f90 --disable-dependency-tracking " returned error 1 Command output: checking for strings.h... no checking for inttypes.h... no checking for stdint.h... no checking for unistd.h... no checking for long long... no checking for long double... no checking for int8_t... no checking for uint8_t... no checking for int16_t... no checking for uint16_t... no checking for int32_t... no checking for uint32_t... no checking for int64_t... no checking for uint64_t... no checking for intptr_t... no checking for uintptr_t... no checking for mode_t... no checking for ssize_t... no checking for ptrdiff_t... no checking size of char... 0 checking size of short... 0 checking size of int... 0 checking size of long... 0 checking size of float... 0 checking size of double... 0 checking size of void *... 0 checking size of size_t... 0 checking alignment of char... configure: WARNING: *** Problem running configure test! configure: WARNING: *** See config.log for details. configure: error: *** Cannot continue. Error: Status 1 encountered during processing. -- Ticket URL: <http://trac.macports.org/ticket/20240> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #26424: valgrind +openmpi doesn't provide promised "libmpiwrap-<platform>.so" file
by MacPorts 28 Jan '14

28 Jan '14

#26424: valgrind +openmpi doesn't provide promised "libmpiwrap-<platform>.so" file ----------------------------------+----------------------------------------- Reporter: nilstec_inc@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: valgrind-devel ----------------------------------+----------------------------------------- I do: {{{ sudo port clean valgrind-devel sudo port -d install valgrind-devel +openmpi }}} In the output of the configure the following two lines appear: {{{ checking primary target for usable MPI2-compliant C compiler and mpi.h... no checking secondary target for usable MPI2-compliant C compiler and mpi.h... no }}} According to the [http://valgrind.org/docs/manual/mc-manual.html#mc- manual.mpiwrap Valgrind User Manual] it should say `yes, mpicc`, right? I'll supply the output of `sudo port -d install valgrind-devel +openmpi`. Thanks for your help! -- Ticket URL: <http://trac.macports.org/ticket/26424> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #17243: make openmpi compiler wrappers use currenly selected compiler
by MacPorts 28 Jan '14

28 Jan '14

#17243: make openmpi compiler wrappers use currenly selected compiler --------------------------------+------------------------------------------- Reporter: mmoll(a)macports.org | Owner: mww(a)macports.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.7.0 Keywords: openmpi gcc_select | Port: openmpi --------------------------------+------------------------------------------- It'd be nice if openmpi used gcc_select to select default compilers. Right now, the openmpi compiler wrappers (mpicc, mpicxx, mpif77) always use the C and C++ compilers in /usr/bin, even if /opt/local/bin comes first in the user's path. The changes to accomplish this are trivial: - add a dependency on port:gcc_select - patch the files in ${prefix}/share/openmpi to use /opt/local/bin/gcc instead of /usr/bin/gcc (similarly for C++ and Fortran). -- Ticket URL: <http://trac.macports.org/ticket/17243> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3