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

[MacPorts] #49921: xorg-randrproto
by MacPorts 07 Dec '15

07 Dec '15

#49921: xorg-randrproto -----------------------------+-------------------------------- Reporter: dawsonpaul@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: xorg-randrproto | Port: xorg-randrproto -----------------------------+-------------------------------- Trying to install scapy: HOST: Darwin MYMACHINE.local 13.4.0 Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64 OUTPUT: ---> Building xorg-randrproto make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_x11_xorg-randrproto/xorg- randrproto/work/randrproto-1.5.0' CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_x11_xorg-randrproto/xorg- randrproto/work/randrproto-1.5.0/missing aclocal-1.13 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_x11_xorg-randrproto/xorg- randrproto/work/randrproto-1.5.0/missing: line 81: aclocal-1.13: command not found WARNING: 'aclocal-1.13' is missing on your system. You should only need it if you modified 'acinclude.m4' or 'configure.ac' or m4 files included by 'configure.ac'. The 'aclocal' program is part of the GNU Automake package: <http://www.gnu.org/software/automake> It also requires GNU Autoconf, GNU m4 and Perl in order to run: <http://www.gnu.org/software/autoconf> <http://www.gnu.org/software/m4/> <http://www.perl.org/> make: *** [aclocal.m4] Error 127 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_x11_xorg-randrproto/xorg- randrproto/work/randrproto-1.5.0' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_x11_xorg-randrproto/xorg- randrproto/work/randrproto-1.5.0" && /usr/bin/make -j8 -w all Exit code: 2 Error: org.macports.build for port xorg-randrproto returned: command execution failed Warning: targets not executed for xorg-randrproto: org.macports.activate org.macports.build org.macports.destroot org.macports.install Please see the log file for port xorg-randrproto for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_x11_xorg-randrproto/xorg-randrproto/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port xorg-randrproto failed -- Ticket URL: <https://trac.macports.org/ticket/49921> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

Re: [MacPorts] #45262: files hosted on ftp sites aren't getting mirrored
by MacPorts 07 Dec '15

07 Dec '15

#45262: files hosted on ftp sites aren't getting mirrored -----------------------------+--------------------- Reporter: jchauvel@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by jeremyhu@…): Replying to [comment:16 dluke@…]: > Replying to [comment:15 ryandesign@…]: > > I don't know much about IPv6. > > There's a bunch of info online if you want to learn - I've heard good things about https://ipv6.he.net/certification/ (although I haven't gone through any of it). You should. It's quite a good resource, and at the end, you get a nifty T-Shirt ;) > For our purposes here, there is a block of addresses for MacOS Forge. If everything is on the same broadcast domain, it's probably a /64 (IPv6 addresses are 128 bits long and almost always a /64). I think the MacOSForge servers aren't configured for IPv6 access. xquartz and xquartz-dl only have link local IPv6 addresses, so I suspect the others are in the same boat. -- Ticket URL: <https://trac.macports.org/ticket/45262#comment:20> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #45262: files hosted on ftp sites aren't getting mirrored
by MacPorts 07 Dec '15

07 Dec '15

#45262: files hosted on ftp sites aren't getting mirrored -----------------------------+--------------------- Reporter: jchauvel@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by dluke@…): Replying to [comment:18 ryandesign@…]: > I did look at the `ifconfig` output of all the machines that would be connecting to your proxy, and they each only have a single ipv6 address starting with `fe80::`. fe80::/64 is IPv6 link-local (see RFC 4291) Let me know whenever you get IPv6 set up and I'll adjust the firewall and squid config on my side. -- Ticket URL: <https://trac.macports.org/ticket/45262#comment:19> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #45262: files hosted on ftp sites aren't getting mirrored
by MacPorts 07 Dec '15

07 Dec '15

#45262: files hosted on ftp sites aren't getting mirrored -----------------------------+--------------------- Reporter: jchauvel@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by ryandesign@…): Replying to [comment:16 dluke@…]: > One way, would be to look at the ifconfig output on the machine(s) / VMs. I did look at the `ifconfig` output of all the machines that would be connecting to your proxy, and they each only have a single ipv6 address starting with `fe80::`. -- Ticket URL: <https://trac.macports.org/ticket/45262#comment:18> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #45262: files hosted on ftp sites aren't getting mirrored
by MacPorts 07 Dec '15

07 Dec '15

#45262: files hosted on ftp sites aren't getting mirrored -----------------------------+--------------------- Reporter: jchauvel@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by ryandesign@…): Replying to [comment:15 ryandesign@…]: > I'll be watching for whether [ticket:49378 mesa 11.0.6] [https://distfiles.macports.org/mesa/ gets mirrored]. It did get mirrored. -- Ticket URL: <https://trac.macports.org/ticket/45262#comment:17> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #49405: VLC fails to upgrade from 2.1.5_4 to 2.1.5_6
by MacPorts 06 Dec '15

06 Dec '15

#49405: VLC fails to upgrade from 2.1.5_4 to 2.1.5_6 --------------------+-------------------------------- Reporter: igs@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: vlc --------------------+-------------------------------- Attempted to upgrade multiple outdated ports. VLC progresses to the build stage and quits. Conducted a port clean and a second upgrade attempt with trace mode activated. Log files from the first and second attempts attached. -- Ticket URL: <https://trac.macports.org/ticket/49405> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49908: gimp-jp2 fails to install
by MacPorts 06 Dec '15

06 Dec '15

#49908: gimp-jp2 fails to install --------------------+-------------------------------- Reporter: igs@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: --------------------+-------------------------------- Attempting to update outdated ports. The updating stops after attempting to update gimp-jp2, with a message stating gimp2 must be installed without +quartz. How important is the port and is there a work-around? Log file is included. -- Ticket URL: <https://trac.macports.org/ticket/49908> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

Re: [MacPorts] #45262: files hosted on ftp sites aren't getting mirrored
by MacPorts 06 Dec '15

06 Dec '15

#45262: files hosted on ftp sites aren't getting mirrored -----------------------------+--------------------- Reporter: jchauvel@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by dluke@…): Replying to [comment:15 ryandesign@…]: > I don't know much about IPv6. There's a bunch of info online if you want to learn - I've heard good things about https://ipv6.he.net/certification/ (although I haven't gone through any of it). For our purposes here, there is a block of addresses for MacOS Forge. If everything is on the same broadcast domain, it's probably a /64 (IPv6 addresses are 128 bits long and almost always a /64). > How can I find this information? One way, would be to look at the ifconfig output on the machine(s) / VMs. For example, the host that I run squid on has ifconfig that looks something like this: {{{ en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV> ether 10:dd:b1:a9:66:f9 inet6 fe80::12dd:b1ff:fea9:66f9%en0 prefixlen 64 scopeid 0x4 inet6 2001:418:1401:62::3 prefixlen 64 inet 129.250.34.3 netmask 0xfffffff8 broadcast 129.250.34.7 nd6 options=1<PERFORMNUD> media: autoselect (1000baseT <full-duplex,flow-control>) status: active }}} So you can see I have an IPv4 /29 and and IPv6 /64 that the host is numbered out of (along with the link-local IPv6 address that we can ignore for now). > The servers whose configurations I know how to examine (the Mac servers) have their IPv6 addresses obtained automatically (whereas their IPv4 addresses are entered manually). I can run `ifconfig` and see the inet6 address of all the servers, but I don't know if they're externally accessible. From a host that would be connecting to the proxy do `ping6 geeklair.net` and see if you get a reply. or, if the stupid firewall policy blocks ICMP, you could to `telnet -6 geeklair.net 80` and see if you can make a tcp connection. If either (or both) of those succeed, we'll need to figure out which IPv6 block or blocks to add access to - or those hosts may try to connect via IPv6 and will be blocked by my local firewall (and denied by my squid configuration). > For example, I found the purported IPv6 address of the distfiles server, but entering it into Safari produces and error message. According to an IPv6 readiness checker, our web sites are not IPv6 ready, first of all because we don't have an AAAA record. So I'm not sure to what extent, if any, IPv6 connections are occurring within the Mac OS Forge infrastructure. That's probably also something you should get working (AAAA records in DNS, website and any other services available over IPv6), but is not directly relevant to whether the machines are going to try to make outbound IPv6 connections or not. -- Ticket URL: <https://trac.macports.org/ticket/45262#comment:16> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #49923: flac +universal does not build on 10.5.8
by MacPorts 06 Dec '15

06 Dec '15

#49923: flac +universal does not build on 10.5.8 --------------------+-------------------------------- Reporter: hans@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: flac --------------------+-------------------------------- While flac itself builds fine on 10.5.8, the +universal variant fails to build, with the following error message: {{{ cpu.c: In function â~@~XFLAC__cpu_xgetbv_x86â~@~Y: :info:build cpu.c:480: error: impossible constraint in â~@~Xasmâ~@~Y :info:build lipo: can't open input file: /opt/local/var/macports/buil /_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_flac/flac/work/.tmp/ccRyImnG.out (No such file or directory) }}} -- Ticket URL: <https://trac.macports.org/ticket/49923> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #49920: Dependencies Conflicts for Nemesis Package
by MacPorts 06 Dec '15

06 Dec '15

#49920: Dependencies Conflicts for Nemesis Package ---------------------------+-------------------------------- Reporter: victor.roig@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ---------------------------+-------------------------------- bash-3.2# port install nemesis ---> Computing dependencies for nemesis Error: Can't install libnet because conflicting ports are active: libnet11 Error: Follow http://guide.macports.org/#project.tickets to report a bug. Error: Processing of port nemesis failed -- Ticket URL: <https://trac.macports.org/ticket/49920> MacPorts <https://www.macports.org/> Ports system for OS X

1 1