on emerging dev-python/4suite-1.0.2-r1 I get a strange python error: File "setup.py", line 88, in <module> requires_python=['>=2.2.1'], File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/__init__.py", line 48, in setup return _setup(**attrs) File "/usr/lib/python2.5/distutils/core.py", line 151, in setup dist.run_commands() File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 546, in run_commands for dist in self.get_distributions(): File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 420, in get_distributions distributions = self._sort_distributions(distributions) File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 477, in _sort_distributions installed_provides.update(get_provides(package)) File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 467, in get_provides package_version = Version.CommonVersion(package.get_version()) File "/usr/lib/python2.5/distutils/version.py", line 40, in __init__ self.parse(vstring) File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/Version.py", line 57, in parse raise ValueError("invalid version number: %r" % vstring) ValueError: invalid version number: 'DS1-R36' This is with python-2.5.2-r8 Thanks for looking into it, Helmut. Reproducible: Always emerge --info Portage 2.2_rc14 (default/linux/x86/2008.0, gcc-4.3.2, glibc-2.8_p20080602-r0, 2.6.26-gentoo-r2 i686) ================================================================= System uname: Linux-2.6.26-gentoo-r2-i686-Intel-R-_Pentium-R-_III_CPU_family_1266MHz-with-glibc2.0 Timestamp of tree: Fri, 14 Nov 2008 07:45:03 +0000 ccache version 2.4 [disabled] app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7, 2.1.6-r1 dev-lang/python: 2.5.2-r8 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.6.2 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.3.0-r1 sys-apps/sandbox: 1.2.20_alpha2-r1 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.19 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="buildpkg distlocks parallel-fetch preserve-libs protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo " LANG="en_US.iso88591" LDFLAGS="-Wl,-O1" LINGUAS="en de" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/portage/layman/java-overlay" SYNC="rsync://rsync.informatik.RWTH-Aachen.de/gentoo-portage" USE="X acl avahi berkdb bitmap-fonts bzip2 cairo cdr cli cracklib crypt cups dbus doc dri dvd fortran gdbm gnome gpm gtk gtk2 iconv ipv6 isdnlog jpeg kde midi mmx mudflap ncurses nls nptl nptlonly opengl openmp pam pcre pdf perl png pppd python qt readline reflection session spl sqlite sqlite3 sse ssl svg sysfs tcl tcpd tetex tiff tk truetype truetype-fonts type1-fonts unicode x86 xorg xulrunner zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 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 authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en de" USERLAND="GNU" VIDEO_CARDS="nv" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
I had a similar problem: Traceback (most recent call last): File "setup.py", line 88, in <module> requires_python=['>=2.2.1'], File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/__init__.py", line 48, in setup return _setup(**attrs) File "/usr/lib64/python2.5/distutils/core.py", line 151, in setup dist.run_commands() File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 546, in run_commands for dist in self.get_distributions(): File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 420, in get_distributions distributions = self._sort_distributions(distributions) File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 477, in _sort_distributions installed_provides.update(get_provides(package)) File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/PackageManager.py", line 467, in get_provides package_version = Version.CommonVersion(package.get_version()) File "/usr/lib64/python2.5/distutils/version.py", line 40, in __init__ self.parse(vstring) File "/var/tmp/portage/dev-python/4suite-1.0.2-r1/work/4Suite-XML-1.0.2/Ft/Lib/DistExt/Version.py", line 57, in parse raise ValueError("invalid version number: %r" % vstring) ValueError: invalid version number: 'T-0.3.18 (BitTornado)' And I solved by uninstalling bittornado, installing 4suite, and reinstalling bittornado back.
Slightly different here It didn't like sci-misc/pythoncad which was at version DS1-R36 temporarily unmerging is a work-around (not more)
I dont have either of those apps installed, how did you figure what was giving you those issues
(In reply to comment #3) > I dont have either of those apps installed, how did you figure what was giving > you those issues > The error message i get is "Invalid version number 'UNKNOWN'" build.log http://dpaste.com/32282/
The problem comes because 4suite is expecting all version information to match the StrictVersion definition in Distutils and that isn't true for some packages. I added a DEBUG=1 line in Ft/Lib/DistExt/PackageManager.py and got the list of packages being loaded. On my system, the following packages failed the StrictVersion test: happydoc, cfgparse, mercurial, cherryflow. I unmerged all of these packages and then 4suite emerged successfully. After emerging 4suite, it should be possible to re-emerge the packages you had to remove. The real fix is to eliminate the StrictVersion requirement in 4suite. I am going to suggest this upstream FWIW.
upstream report: http://sourceforge.net/tracker/?func=detail&atid=428292&aid=2785387&group_id=39954
Version-info "unknown" occurs with mercurial. As others have suggested, unmerging/remerging is a workaround, albeit an incredibly annoying one. Has upstream reacted to the bugreport in any way?
(In reply to comment #7) > Has upstream reacted to the bugreport in any way? No.
I checked today and found that work is progressing on amara2 and akara (replacing 4suite). Perhaps the Python herd would want to check this out and bump to the latest releases. They seem to be in active development of the new versions. Homepages: amara2: http://wiki.xml3k.org/Amara2 akara: http://wiki.xml3k.org/Akara
(In reply to comment #9) > I checked today and found that work is progressing on amara2 and akara > (replacing 4suite). Perhaps the Python herd would want to check this out and > bump to the latest releases. They seem to be in active development of the new > versions. > > Homepages: > amara2: http://wiki.xml3k.org/Amara2 > akara: http://wiki.xml3k.org/Akara I started to work on that some time ago. Traces of that effort can be found in my overlay as my own version of the expat ebuild (in my overlay) supporting wide-unicode support in expat, which seemed to be a requirement for amara2.
... otherwise Amara2 inherits the same bad habits of 4suite by bundling it's own version of expat.
an older version of amara2 (alpha1) is also in my overlay. It's a piece of cake to update the unbundling patch from there to the alpha4. I could put that in the tree on the weekend, provided I get the permissions to touch expat.
(In reply to comment #11) > ... otherwise Amara2 inherits the same bad habits of 4suite by bundling it's > own version of expat. I'm not sure I understand your comment. Is the bundled version of expat different than the vanilla expat code? If so, what are the changes (just a summary is sufficient)?
(In reply to comment #13) > (In reply to comment #11) > > ... otherwise Amara2 inherits the same bad habits of 4suite by bundling it's > > own version of expat. > > I'm not sure I understand your comment. Is the bundled version of expat > different than the vanilla expat code? If so, what are the changes (just a > summary is sufficient)? No, but you can compile expat with different char-types and amara2 seems to require an expat built with XML_UNICODE_WCHAR_T. To not break other rev.deps of expat, my ebuild of expat builds a second (and third) set of the libraries with "-DXML_UNICODE" resp. "-DXML_UNICODE_WCHAR_T" resulting in libexpatu.so, resp. libexpatw.so.
(In reply to comment #14) > (In reply to comment #13) > > ... Is the bundled version of expat > > different than the vanilla expat code? If so, what are the changes (just a > > summary is sufficient)? > No, but you can compile expat with different char-types and amara2 seems to > require an expat built with XML_UNICODE_WCHAR_T. To not break other rev.deps of > expat, my ebuild of expat builds a second (and third) set of the libraries with > "-DXML_UNICODE" resp. "-DXML_UNICODE_WCHAR_T" resulting in libexpatu.so, resp. > libexpatw.so. Then I think adding USE flags to the expat ebuild and requiring them as dependencies of amara2 is the way to go. Is it hard (administratively in Gentoo) to do this? (I would assume that both the modified expat ebuild and amara2 would be marked unstable at first.)
(In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > ... Is the bundled version of expat > > > different than the vanilla expat code? If so, what are the changes (just a > > > summary is sufficient)? > > No, but you can compile expat with different char-types and amara2 seems to > > require an expat built with XML_UNICODE_WCHAR_T. To not break other rev.deps of > > expat, my ebuild of expat builds a second (and third) set of the libraries with > > "-DXML_UNICODE" resp. "-DXML_UNICODE_WCHAR_T" resulting in libexpatu.so, resp. > > libexpatw.so. > > Then I think adding USE flags to the expat ebuild and requiring them as > dependencies of amara2 is the way to go. Is it hard (administratively in > Gentoo) to do this? (I would assume that both the modified expat ebuild and > amara2 would be marked unstable at first.) Not at all :-) I've done that in my overlay already.
ok, I rechecked everything. Seems we need yet another variation of the expat library (one with XML_Char=unsigned int/long). Contacted amara2 devs to hear what they have to say...
I have committed the patch, which should fix this bug.