... and sci-libs/libgeda-1.1.1 at the same time since they don't work one without the other. This is another of those 'upstream changed their numbering scheme' cases which ends up being a pain for our users. So here's how you go about stabilizing this. First mask =sci-electronics/geda-200* in order to avoid picking up older versions. Then emerge geda (which will pull the corresponding libgeda) with USE=examples. Then simply run: gschem /usr/share/gEDA/examples/lightning_detector/lightning.sch Play with that schematic a bit (zoom in/out, pan, add/remove components, etc...) until you get bored. Don't worry, it's only a matter of seconds before you get really, really bored (or you should see a doctor and join the sci-electronics team). Once this is done I can clean-up the whole thing. Thanks for your help on this. Denis.
libgeda-1.1.1 at configure says: checking Guile version >= 1.8.0... 1.6.8 configure: error: Guile version >= 1.8.0 is required. on sparc. I'll look at marking stable guile-1.8.1-r3 then come back to this. But the libgeda-1.1.1.ebuild is not consistent with this.
(The "on sparc." part does not come from configure, of course; it comes from me. :) )
(In reply to comment #1) > libgeda-1.1.1 at configure says: > checking Guile version >= 1.8.0... 1.6.8 > configure: error: Guile version >= 1.8.0 is required. > on sparc. You're right, I had missed that. It's weird, especially knowing that versions before and after 1.1.1 only require >=guile-1.6 (I just double-checked it). This is probably the reason why I missed it. > I'll look at marking stable guile-1.8.1-r3 then come back to this. But the > libgeda-1.1.1.ebuild is not consistent with this. Please don't mark guile-1.8 stable on sparc just yet. There are no arches with a stable >=guile-1.8 right now, so there may be wider implications. Let's see with the scheme guys first. Denis.
Just as a FYI for the amd64 team, I'm working on this. It is a large download and I am going to get it a bit later, but I don't want someone to steal this. ;P
Okay, while trying to unmask everything correctly, I get this: !!! Invalid or corrupt dependency specification: invalid atom: '>=sys-devel/autoconf-FAIL' ('ebuild', '/', 'dev-libs/libstroke-0.5.1', 'merge') x11-proto/xproto x11-libs/libX11 =sys-devel/automake-1.4* >=sys-devel/autoconf-FAIL sys-devel/libtool Portage 2.1.3.9 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.5-r4, 2.6.22-gentoo-r2 x86_64) ================================================================= System uname: 2.6.22-gentoo-r2 x86_64 AMD Athlon(tm) 64 Processor 3400+ Timestamp of tree: Tue, 18 Sep 2007 01:47:01 +0000 ccache version 2.4 [disabled] app-shells/bash: 3.2_p17 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17-r1 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/distfiles" FEATURES="distlocks metadata-transfer parallel-fetch sandbox sfperms strict test unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/overlay /usr/portage/local/kde" SYNC="rsync://kv80/gentoo-portage" USE="X acl acpi aiglx aim alsa amd64 arts berkdb bitmap-fonts branding cairo cli cracklib crypt cups dbus dri dvd dvdread emboss encode esd evo fam firefox fortran gdbm gif gpm gstreamer gtk hal iconv imap ipv6 isdnlog jpeg kde kerberos mad midi mikmod mmx mp3 mpeg mpeg3 mqsli mudflap mysql ncurses nls nptl nptlonly nvidia ogg opengl openmp oss pam pcre pdf perl png pppd python qt3 qt3support quicktime readline reflection sdl session sockets spell spl sqlite3 sse sse2 ssl svg tcpd test tiff truetype truetype-fonts type1-fonts unicode vim vorbis xcomposite xine xml xorg xv 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 mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #3) > (In reply to comment #1) > > libgeda-1.1.1 at configure says: > > checking Guile version >= 1.8.0... 1.6.8 > > configure: error: Guile version >= 1.8.0 is required. > > on sparc. > > You're right, I had missed that. It's weird, especially knowing that versions > before and after 1.1.1 only require >=guile-1.6 (I just double-checked it). > This is probably the reason why I missed it. > > > I'll look at marking stable guile-1.8.1-r3 then come back to this. But the > > libgeda-1.1.1.ebuild is not consistent with this. > > Please don't mark guile-1.8 stable on sparc just yet. There are no arches with > a stable >=guile-1.8 right now, so there may be wider implications. Let's see > with the scheme guys first. > > Denis. > I wouldn't mark it stable anyway, because it fails with FEATURES=test
Thomas, for the autoconf-FAIL thing, please see bug 192892.
Thanks, Nico. Maintainers: Should this block stabilization as one of the deps don't work?
> > Please don't mark guile-1.8 stable on sparc just yet. There are no arches > > with a stable >=guile-1.8 right now, so there may be wider implications. > > Let's see with the scheme guys first. > > > > Denis. > > > I wouldn't mark it stable anyway, because it fails with FEATURES=test Tests fail only if some use flags are not enabled as the tests don't check for this yet, but maybe in a future 1.8.3. Bug 163921 is the thing that's been keeping me from requesting stabilization. Stabilization will undoubtedly uncover more incompatibilities.
Please ignore my comment 7. The correct bug for the libstroke emerge failure is bug 192942. But that problem is not related to this bug, as far as I can see.
Alright, let's postpone that for now. In a few weeks either guile-1.8 is stable and we can go ahead, or we can stabilize geda-1.2.0 instead since it can work with guile-1.6. I believe it's reasonnable to assume that the libstroke issue will be solved by then... Denis.
(In reply to comment #10) > Please ignore my comment 7. The correct bug for the libstroke emerge failure is > bug 192942. > > But that problem is not related to this bug, as far as I can see. > It is related.If a dependency does not build, that is very bad, and a blocker for stabilization. For more information on this issue, see vapier's message to gentoo-dev
(In reply to comment #12) > It is related.If a dependency does not build, that is very bad, and a blocker > for stabilization. For more information on this issue, see vapier's message to > gentoo-dev I have fixed the libstroke bug, so it's no longer an issue. Denis.
So... can we revisit this and stabilize 1.2 or something so that the broken versioning gets fixed finally?
Reopen; we need something uptodate stabilized.
(In reply to comment #15) > Reopen; we need something uptodate stabilized. As you may or may not know, I have no dev box right now and only sporadic email access. I'll take care of that when I'll be back. Denis.
CC me :)
OK, let's do it now. Please arches, stabilize sci-libs/libgeda-1.4.0 and sci-electronics/geda-1.4.0. amd64: if nobody does it I'll do it for you. Quick howto: Emerge geda-1.4.0 with USE=examples Start gschem Click on "File->Open page..." and navigate to /usr/share/gEDA/examples Open some schematics there, play with them a bit When you're bored, stabilize Thanks in advnace. Denis.
amd64 stable
Sparc stable for both. It's a bit distressing that geda does not include any internal tests, but the examples seem to generate the same results as come with them.
x86 stable
ppc stable
>amd64 stable Yes, gEDA 1.4.0 works fine with amd64. But manually masking outdated versions seems still be necessary: AMD64-X2 stefan # cat /etc/portage/package.mask =sci-electronics/geda-200* =sci-libs/libgeda-200* Would be great if someone can delete these obsolete stuff.
(In reply to comment #23) > Would be great if someone can delete these obsolete stuff. It has already been deleted. Denis.
