It appears that sys-devel/distcc-3.1-r5 and r6 don't properly parse IPv6 addresses, even with USE ipv6 enabled and confirming that --enable-rfc2553 was passed to the configure script. # distccd --allow fd00:1234::c0a8:200/120 distccd[5062] (dcc_parse_mask) ERROR: can't parse internet address "fd00:1234::c0a8:200" Digging on Google pops up this post on the distccd ML from June of 2011: http://old.nabble.com/Re%3A-IPv6-support-in-distccd--p31819589.html Which suggests that the issue is that distccd doesn't handle CIDRs >32. The issue appears fixed in distcc-3.2, however, so I would suggest that 3.1 be re-evaluated and IPv6 support either fixed via a backport or the USE flag and support removed entirely.
Portage 2.1.10.65 (hardened/linux/amd64, gcc-4.5.3, glibc-2.15-r2, 3.3.6-hardened x86_64) ================================================================= System uname: Linux-3.3.6-hardened-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q9550_@_2.83GHz-with-gentoo-2.1 Timestamp of tree: Sat, 16 Jun 2012 06:30:01 +0000 distcc 3.2rc1 x86_64-pc-linux-gnu [disabled] ccache version 3.1.7 [disabled] app-shells/bash: 4.2_p29 dev-lang/python: 2.5.4-r4, 2.6.8, 2.7.3-r2, 3.2.3-r1 dev-util/ccache: 3.1.7 dev-util/cmake: 2.8.7-r5 dev-util/pkgconfig: 0.26 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.10.3 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.4_p6-r1, 1.5-r1, 1.8.5-r4, 1.9.6-r3, 1.10.3, 1.11.5, 1.12.1 sys-devel/binutils: 2.22-r1 sys-devel/gcc: 4.5.3-r2, 4.6.3 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r3 sys-kernel/linux-headers: 3.4 (virtual/os-headers) sys-libs/glibc: 2.15-r2 Repositories: gentoo x-local ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=core2 -mtune=core2 -mfpmath=sse -msse -msse2 -mssse3 -mcx16 -msahf -O2 -pipe -fomit-frame-pointer -fforce-addr -falign-functions=64 -ftracer -fweb -maccumulate-outgoing-args" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/init.d /etc/pam.d /etc/php/apache2-php5.4/ext-active/ /etc/php/cgi-php5.4/ext-active/ /etc/php/cli-php5.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-march=core2 -mtune=core2 -mfpmath=sse -msse -msse2 -mssse3 -mcx16 -msahf -O2 -pipe -fomit-frame-pointer -fforce-addr -falign-functions=64 -ftracer -fweb -maccumulate-outgoing-args" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests binpkg-logs candy config-protect-if-modified distlocks ebuild-locks fixlafiles news parallel-fetch parse-eapi-ebuild-head protect-owned sfperms sign unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv" FFLAGS="" GENTOO_MIRRORS="http://distfiles.gentoo.org" LDFLAGS="-Wl,-z,now -Wl,-z,relro" LINGUAS="en" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/ramfs" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="acl amd64 apache2 berkdb bzip2 cli cracklib curl cxx dbus dri encode gd gdbm hardened ipv6 justify ldap mmx modules mudflap multilib ncurses nptl nptlonly offensive openmp pam pax_kernel pcre pppd readline rtc session sse sse2 ssl tcpd unicode urandom xml xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en" PHP_TARGETS="php5-3" PYTHON_TARGETS="python3_2 python2_7" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="vesa vga fbdev" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
+1 for that 3.2_rc1 seems fine, but ebuild is slightly outdate(it is still EAPI="3"). So we should either backport this change from 3.2_rc1 or at least unmask 3.2_rc1
ping, what we will do here? 3.2_rc1-r3 is unmasked now and i see no problems using it. Should we put it into stable?
Maintainer timeout, using my QA hat to begin stabilization Arches, please test and mark stable =sys-devel/distcc-3.2_rc1-r3 Target keywords: alpha amd64 arm arm64 hppa ia64 m68k ppc ppc64 s390 sh sparc x86
Stable for HPPA PPC64.
amd64 stable
ppc stable
Stable on alpha.
*** Bug 564722 has been marked as a duplicate of this bug. ***
Thanks, I couldn't find this bug stabilization request. I was all set to claim stable too, but then I used the distcc-config tool, which over-wrote my /etc/distcc/hosts file without making a backup. Now I cannot get distcc to export tasks properly, when using cpp,lzo or distcc-pump, as I have no idea what I had initially within the /etc/distcc/hosts file. I have a good idea, but distcc-pump mode still fails. Common distcc without using distcc-pump work fine. (I'm pushing compile tasks from an x86 32 bit platform to a 64 bit platform, and using a 32 bit cross compiler.)
The distcc-config script should definitely have a "cp /etc/distcc/hosts /etc/distcc/hosts.$date.$increment" statement, to prevent over-writing any current files.
x86 stable
I have x86 stable when cross-compiling onto a 64 bit platform, but using pump (ie. cpp,lzo option) I get a segmentation fault on both, local and distributed clients. (Packages across servers/clients are now compiled using USE=crossdev.) When the compile task is locally compiled using pump (ie. cpp, lzo options), I get a "core dumped" message within distcc logs, but the emerge & install appear fine in the other console. Shrugs. Sounds like a check task is getting a segment fault, but only the distributed task completely fails. On one core dump, the core file states the segment fault occurred within the make process, but no symbols, else I'm targeting the wrong executable. Shrugs. I say mark x86 stable regardless. My issue could be merrily a white space issue within the config file for all I know at this point!
Just traced my problem back to lzo1x_decompress_safe.
sparc stable
arm stable
ia64 stable
s390 stable
Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa
arm64 stable, closing.
I thought x86 distcc-3.2_rc1-r4 was queried as stable? Yet portage still shows distcc-3.2_rc1-r4 not stable.
(In reply to Roger from comment #21) > I thought x86 distcc-3.2_rc1-r4 was queried as stable? > > Yet portage still shows distcc-3.2_rc1-r4 not stable. Can you please show the commandline and output that produces that information? It was stabilized with this commit dating back in 2015 commit 4b84d6dfb001a28a303b2a2a0f6dd1a294016cb5 Author: Agostino Sarubbo <ago@gentoo.org> Date: Tue Nov 3 17:17:21 2015 +0100 sys-devel/distcc: x86 stable wrt bug #421481 Package-Manager: portage-2.2.20.1 RepoMan-Options: --include-arches="x86" diff --git a/sys-devel/distcc/distcc-3.2_rc1-r4.ebuild b/sys-devel/distcc/distcc-3.2_rc1-r4.ebuild index 6a4295705c..38f0ba544b 100644 --- a/sys-devel/distcc/distcc-3.2_rc1-r4.ebuild +++ b/sys-devel/distcc/distcc-3.2_rc1-r4.ebuild @@ -15,7 +15,7 @@ SRC_URI="https://distcc.googlecode.com/files/${MY_P}.tar.bz2" LICENSE="GPL-2" SLOT="0" -KEYWORDS="alpha amd64 ~arm ~arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh ~sparc ~x86 ~sparc-fbsd ~x86-fbsd" +KEYWORDS="alpha amd64 ~arm ~arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh ~sparc x86 ~sparc-fbsd ~x86-fbsd" IUSE="avahi crossdev gnome gssapi gtk hardened ipv6 selinux xinetd" RESTRICT="test"
Disregard. After the last sync here, x32 & x64 distcc versions appear to be in sync now. I don't know what happened, as I frequently sync the x32 laptop weekly. Shrugs.
