• Ports
• ToDo
• IPv6

IPv6 Ports TODO

This page aims to be a collection of open IPv6 ports tasks. This contains an analyze of the current impact of (missing) IPv6 support of port distribution servers and a coordination of promote the support of IPv6.

Statistic about the impact of IPv6 availability on the ports-tree

At 2015-12-14 there were 25.522 ports in the ports-tree.

Statistic about hosts (not) supporting IPv6

The files for this ports were fetched from 5.344 different hosts. Different subdomains (example: sub1.domain.tld and sub2.domain.tld) are considered as different hosts, because they normally are different server. Of course a host can have multiple IPv4 and IPv6 addresses. If the DNS lists at least one IPv6 address for the server, its stated there is IPv6 support. Same for IPv4.

When there is an IPv6 addresses i *assumed* IPv6 support. I did not fetch files or check for wrong configuration. The real support could be worse than stated.

• Out of 5.344 hosts there are 3.925 hosts which have only an IPv4 address.
• Out of 5.344 hosts there are 0 hosts which have only an IPv6 address.
• Out of 5.344 hosts there are 359 hosts without resolvable DNS record. (The affected ports are all broken)

1.419 out of 5.344 hosts support IPv4 and IPv6. Therefore 73.44 % of the hosts did not support IPv6.

Statistic about ports not fetchable because of missing supporting IPv6

Out of 25.522 ports there are 10.308 which are not fetchable via IPv6, rendering the ports unable to build. This means that 40.38 % of the portstree are not buildable when having an IPv6 only connection.

Statistic about ports not buildable because of missing supporting IPv6

Ports have dependencies. LibreOffice for example is a big port with 277 dependencies at all. When building LibreOffice every dependency must be available, otherwise it could not be build. This means whenever a single port is not fetchable through IPv6 every other port depending at it is also not buildable.

When iterating through our 25.522 ports and do a "make all-depends-list" to get a list of all dependencies a single port has, we get a list of 1.696.351 dependencies. Now back to the remaining question "how many ports are not buildable because of missing IPv6 support of their distribution servers?".

Answer: 17.715

In conclusion: if you having an IPv6 only machine, you could not build 69.4 % of the ports.

This includes major ports like Firefox and Thunderbird, because releases.mozilla.org and ftp.mozilla.org does not support IPv6 - but mozilla.org itself does. It includes also for example LibreOffice because some dependencies are not fetchable through IPv6.

TOP 25 hosts with missing IPv6 support

These are the TOP 25 missing IPv6 hosts with the number of ports rendered unfetchable by them (no dependencies included):

Next Steps

In the next step a number of volunteers will contact the different projects and ask for IPv6 support. The reasons for the missing support a various - unawareness, no experience, missing technical infrastructure, etc. We will support the projects individually; answering questions or even find a solution if there is no technical infrastructure for them. Hopefully we can promote IPv6 much more and make the missing support to an exception.

Taken Steps

Created Bugtracker-Entries:

• pypi.python.org -> http://bugs.python.org/issue26021

• ftp.mozilla.org -> https://bugzilla.mozilla.org/show_bug.cgi?id=1237199

• vault.centos.org -> https://bugs.centos.org/view.php?id=10108

• mirror.centos.org -> https://bugs.centos.org/view.php?id=10108

• pecl.php.net -> https://bugs.php.net/bug.php?id=71308

• pear.php.net -> http://pear.php.net/bugs/bug.php?id=21017

• download.gna.org -> http://gna.org/support/?3353

Success

The following sites now support IPv6 directly or through a workaround:

• mirror.amdmi3.ru
• vault.centos.org
• mirror.centos.org
• gstreamer.freedesktop.org
• people.freebsd.org

CategoryIpv6 CategoryTodo CategoryPorts