Bug 37868 – circular dep between autoconf-2.58 and autoconf-2.59 because of subversion-0.35.1

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Martin Ehmsen (RETIRED) 2004-01-11 02:05:54 UTC]

After upgrading autoconf to 2.59 as portage suggest, it want's to downgrade it again to 2.58.
Doing a etcat -d sys-devel/autoconf-2.58 I found that
* dev-util/subversion-0.35.1
  <=sys-devel/autoconf-2.58
And therefore creating a circular dep.
Maybe subversion should set it's RDEPEND to not contain <=autoconf-2.58 (it surely don't need autoconf to run) or else remove the <=autoconf-2.58 from the subversion ebuild.
I will try the subversion ebuild with autoconf-2.59 in a moment.

Reproducible: Always
Steps to Reproduce:




Portage 2.0.49-r20 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031222-r0, 2.6.1)
=================================================================
System uname: 2.6.1 i686 AMD Athlon(TM) XP1900+
Gentoo Base System version 1.4.3.12
ccache version 2.3 [enabled]
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3/share/config /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/env.d"
CXXFLAGS="-mcpu=athlon-xp -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache notitles sandbox"
GENTOO_MIRRORS="http://gentoo.linux.no/ "
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X alsa amd apache2 apm avi berkdb cdr crypt cups curl doc emacs
emacs-w3 encode faad fam fbcon flac foomaticdb freetype fs gdbm gif gtk gtk2
guile imagemagick imap imlib imlib2 ipv6 jabber java javascript jpeg libg++
libwww mad maildir mbox mikmod mmx motif mozilla mpeg mpeg4 ncurses nls nptl
oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline
samba scanner sdl slang spell ssl svga tcltk tcpd tetex tiff truetype type1
unicode usb x86 xml xml2 xmms xv xvid zlib"

[Comment 1 Paul de Vrieze (RETIRED) 2004-01-11 05:20:21 UTC]

I've changed the dependencies. Indeed autoconf is only needed at compile-time. I'll keep the bug open for reports if 2.59 works

[Comment 2 Martin Ehmsen (RETIRED) 2004-01-12 09:19:06 UTC]

Now portage circles between autoconf-2.59 and 2.57a-r1
So the bug is not fixed!
But why is there at constraint on autoconf? I could get subversion to compile fine with autoconf-2.59 after removing the <sys-devel/autoconf-2.58 line.

Btw. there is a similar problem with dev-lang/swig
It circles between versions 1.3.19 and 1.3.20
Should I open a separated bugreport for that?

[Comment 3 Gustavo Ribeiro Alves 2004-01-30 22:12:48 UTC]

Does this autoconf dep is really required? Can't autoconf 2.5* be disabled by setting the env var WANT_AUTOCONF_2_5=0 ?

[Comment 4 Paul de Vrieze (RETIRED) 2004-01-31 05:50:28 UTC]

Those problems are probably caused because swig / autoconf are in world themselves. subversion does not work with swig 1.3.20.

And yes, autoconf is really needed to compile subversion. Basically the trick is, it will work with any version greater than 2.50 except 2.58

[Comment 5 Martin Ehmsen (RETIRED) 2004-01-31 06:47:53 UTC]

> subversion does not work with swig 1.3.20.

subversion-0.37.0 does work fine with swig-1.3.20

[Comment 6 Jaco Kroon 2004-02-04 10:32:22 UTC]

What is the problem with autoconfig-2.58?

[Comment 7 Paul de Vrieze (RETIRED) 2004-02-04 11:46:29 UTC]

The problem is that subversion will not build with it. I don't know where the problem is, and to be honest I don't care. It works with autoconf 2.59 though.

[Comment 8 Jaco Kroon 2004-02-04 12:44:31 UTC]

There is a problem with the ebuild as it is, if autoconf is not already installed subversion will attempt to install without it.  I understand (and have finally seen) that subversion chockes on 2.58.  Hower, after unmerging 2.58 and running
USE="apache2" emerge subversion-0.37.ebuild -p I find that it tries to merge subversion without first emerging some kind of autoconf.  This is undesirable.

Since we only have version 2.57 thru 2.59 (for now), I suggest we do

DEPEND="${RDEPEND}
    || (
        =sys-devel/autoconf-2.57*
        >=sys-devel/autoconf-2.59
    )"

Which does the correct thing on my machine.  If future versions of autoconf becomes available, they will be used instead.  The correct thing being to emerge version 2.57-r1 if no autoconf installed and to downgrade to 2.57-r1 if 2.58 is installed.  A user can easily upgrade autoconf again (probably by simply installing another package that requires it).

[Comment 9 Paul de Vrieze (RETIRED) 2004-02-05 02:19:18 UTC]

I have changed the dependency accordingly