Bug 102208 – valgrind-3.0.0 with callgrind installed results in an endless upgrade/downgrade loop

• Status: RESOLVED DUPLICATE of bug 13632
• Product: Gentoo Linux

[Description Petteri Räty (RETIRED) 2005-08-12 02:09:59 UTC]

from callgrind:
DEPEND="=dev-util/valgrind-2*
        !dev-util/calltree"

Because valgrind is not slotted this results in portage wanting to downgrade
valgrind after upgrading it and then the loop starts all over.

Reproducible: Always
Steps to Reproduce:
1.emerge callgrind
2.emerge -uD world
3.emerge -uD world




Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r1,
2.6.12-gentoo-r7 i686)
=================================================================
System uname: 2.6.12-gentoo-r7 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.12.0_pre5
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.4 [enabled]
dev-lang/python:     2.4.1-r1
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium4 -pipe -mfpmath=sse -ffast-math -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /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/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -pipe -mfpmath=sse -ffast-math -fomit-frame-pointer"
DISTDIR="/usr/src/distfiles"
FEATURES="autoaddcvs autoconfig ccache cvs distlocks fixpackages noauto sandbox
sfperms strict"
GENTOO_MIRRORS=" http://trumpetti.atm.tut.fi/gentoo 
http://lame.lut.fi/linux/gentoo "
LC_ALL="en_US.utf-8"
LINGUAS="fi"
MAKEOPTS="-j2"
PKGDIR="/home/pkg/"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/overlays/betelgeuse /usr/local/overlays/gentopia"
SYNC="cvs://[e-mail]:/var/cvsroot"
USE="x86 X aac acl acpi alsa apm audiofile avi bash-completion berkdb
bitmap-fonts browserplugin bzip2 bzlib cdb cddb cdparanoia cdr crypt cups curl
dbus divx4linux dts dvd dvdr dvdread emboss esd fam flac foomaticdb freetype gcj
gif gstreamer gtk2 hal imagemagick java jpeg kde kdeenablefinal kdexdeltas
libg++ libwww logitech-mouse lzo mad makecheck mikmod mjpeg mmx mmx2 mp3 mpeg
ncurses network nptl nptlonly nsplugin nvidia offensive ogg oggvorbis opengl pam
pdflib png python qt quicktime readline real rtc ruby samba slp spell sse sse2
ssl subversion svg symlink tcpd theora tiff truetype truetype-fonts type1-fonts
unicode usb userlocales vorbis win32codecs xine xml xml2 xv xvid zlib
video_cards_nvidia linguas_fi userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LDFLAGS

[Comment 1 Petteri Räty (RETIRED) 2005-08-12 02:12:10 UTC]

I tried emerging the latest callgrind against valgrind-3.0.0 but it does not
work out of the box:
checking for valgrind installation... in /usr
checking for valgrind version... valgrind-3.0.0
configure: error: Unsupported version. Please use 2.0.x/2.2.x/2.4.x

!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/callgrind-0.9.12/work/callgrind-0.9.12/config.log

[Comment 2 Jakub Moc (RETIRED) 2005-08-12 02:28:49 UTC]

(In reply to comment #1)
> I tried emerging the latest callgrind against valgrind-3.0.0 but it does not
> work out of the box:

That's why the valgrind-2* depend is there, don't you think? You need to resolve
the keywords/p.mask it yourself, such things happen all the time in ~arch. What
about reading the changelog before reporting bugs?

<snip>
 10 Aug 2005; Caleb Tennis <[e-mail]>
  -files/callgrind-sim-pic.patch, -callgrind-0.9.10-r1.ebuild,
  callgrind-0.9.11-r1.ebuild:
  Remove old version, make dep set to valgrind 2.0/2.2
</snip>

[Comment 3 Petteri Räty (RETIRED) 2005-08-12 03:04:29 UTC]

I think there is a problem here that should be solved. 

[Comment 4 Jakub Moc (RETIRED) 2005-08-12 03:07:38 UTC]

griffon26: Should valgrind be slotted? That's what betelgeuse suggested on IRC.

[Comment 5 Maurice van der Pot (RETIRED) 2005-08-12 04:00:07 UTC]

No, Josef Weidendorfer is working on a version for valgrind 3.0.0.
Shouldn't callgrind's deps be blocking valgrind 3.0 when trying to upgrade?

[Comment 6 Petteri Räty (RETIRED) 2005-08-12 04:53:11 UTC]

(In reply to comment #5)
> No, Josef Weidendorfer is working on a version for valgrind 3.0.0.
> Shouldn't callgrind's deps be blocking valgrind 3.0 when trying to upgrade?

It does unless you have valgrind listed in the world file. Seems like a defect
in Portage. 

[Comment 7 Petteri Räty (RETIRED) 2005-08-12 05:01:43 UTC]

*** This bug has been marked as a duplicate of 13632 ***

[Comment 8 Jakub Moc (RETIRED) 2005-08-13 13:44:17 UTC]

*** Bug 102421 has been marked as a duplicate of this bug. ***