This is an ebuild for Soya 0.10.1 - released today. It is in addition to the Soya 0.10 ebuild I submitted last week (which is also not been looked at since??).
Created attachment 66425 [details] /usr/local/portage/dev-python/soya/soya-0.10.1.ebuild The ebuild.
Yay. This works good and it made Slune 1.0.7 to run again. Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-r1, 2.6.12-gentoo-r10 i686) ================================================================= System uname: 2.6.12-gentoo-r10 i686 AMD Athlon(tm) XP 2200+ Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.8.1-r1, 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig candy distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo" LANG="de_DE.utf8" LC_ALL="de_DE.utf8" LINGUAS="de en" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowex X aalib alsa apache2 apm avi beepmp berkdb bitmap-fonts bmp cdr crypt cups curl directfb dvdr eds emboss encode fam fbcon ffmpeg flac font-server foomaticdb gcj gd gdbm gif gimpprint gnome gnutls gpm gstreamer gtk gtk2 gtkhtml guile hal imagemagick imlib ipv6 java jikes joystick jpeg junit lcms libg libg++ libwww mad mikmod mmx mng motif mozilla mp3 mpeg mysql ncurses network nfs nls nptl offensive ogg oggvorbis openal opengl pam pdflib png ppds python quicktime readline ruby scanner sdl slang speex spell sse ssl svg svga tcpd tetex theora tiff truetype truetype-fonts type1-fonts unicode usb vorbis xine xml xml2 xv zlib linguas_de linguas_en userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS
*** Bug 102766 has been marked as a duplicate of this bug. ***
Please, don't file duplicate bugs next time. Attach the ebuild for new version the open bug, mark the old one as obsolete and change the summary to reflect the new version.
the 0.10 ebuild is not obsolete, it's needed for some applications which may not run with 0.10.1. Soya's API isn't stabilized yet.
Created attachment 67778 [details] /usr/local/portage/dev-python/soya/soya-0.10.ebuild Yes, this is also required, and these are TWO SEPERATE EBUILDS. The 0.10 version may be needed for some software due to API changes, since in it's current state, users of Soya have to work around it's bugs (and when they're fixed, the application may no longer function properly). I'm getting really frustrated by the beaucratic bull being thrown at me while my contributions haven't even been looked at in over two weeks. Quite the community building spirit, guys. Good work.
(In reply to comment #7) > Created an attachment (id=67778) [edit] > /usr/portage/dev-python/soya/soya-0.10.ebuild > I'm getting really frustrated by the beaucratic bull being thrown at me while > my contributions haven't even been looked at in over two weeks. > > Quite the community building spirit, guys. Good work. As I have explained via email, there are almost 1,000 ebuilds waiting for maintainer that will commit and maintain them. Sorry, but don't expect that it will be done in two weeks, or even in two months. Our resources are limited. And this has nothing to do with bureaucracy, if everyone opened a new bug for every new version that is released before his ebuild gets into portage (may take over a year sometimes), the noone would be able to handle the bugzilla mess. Any ebuild needs to be checked, tested and needs a maintainer that will have time to fix the problems when they arise. We cannot just put it into portage and then say sorry, we don't have time to fix the problems.
Arc, I've done most (all?) maintainance of the soya ebuilds so far but I've been away the last 10 days and I'm generally rather busy so two weeks isn't long at all in that light. I'll get around to bumping soya as soon as possible but I have a fair amount of more important bugs on my plate right now that I need to take care of first. Hope this explains why nothing have happened yet and that it might even be a couple of weeks yet.
Ebuilds committed to cvs.
