unstable package app-text/poppler-0.5.0 should depend on poppler-bindings-0.5.0. currently, an emerge of app-text/poppler-0.5.0-r2 fails, as poppler-bindings-0.4.3-r2 is installed as a dependency. unmasking poppler-bindings corrects the problem. emerge --info Portage 2.0.54 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r2, 2.6.14-gentoo-r2 i686) ================================================================= System uname: 2.6.14-gentoo-r2 i686 AMD Athlon(tm) XP 3000+ Gentoo Base System version 1.12.0_pre15 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [disabled] dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo.chem.wisc.edu/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowex X a52 aac aalib acl alsa apache2 apm audiofile avi berkdb bitmap-fonts bonobo bzip2 caps cdda cddb cdio cdparanoia cdr crypt cups curl dts dvd dvdr dvdread eds emboss encode esd exif expat fam fbcon ffmpeg flac foomaticdb fortran freetype gdbm ggi gif glut gmp gnome gphoto2 gpm gtk gtk2 gtkhtml guile hal idn imagemagick imlib ipv6 ithreads jack java joystick jpeg kde lcms libcaca libg++ libwww mad mikmod mjpeg mmx mmx2 mng motif mozilla mp3 mpeg mysql ncurses nls nptl nvidia odbc ogg oggvorbis openal opengl oss pam pcre pda pdflib perl png povray ppds python qt quicktime readline real samba scanner sdl slang speex spell sqlite sse ssl stream svga tcltk tcpd tiff truetype truetype-fonts type1-fonts udev usb v4l vcd vorbis wifi wmf xine xml xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
Don't mix stable and ~arch packages; poppler doesn't depend on poppler-bindings, it's the other way round and the dependency is correct. So - what exactly are you requesting here?
(In reply to comment #1) well, this happened during an update world, poppler-0.4.3 had been previously unmasked for kpdf-3.5.0. during world update, poppler wanted to update to 0.5, but failed because poppler-bindings did not first update, staying at 0.4.3. i filed the bug report after 2 other confirmations at forum thread http://forums.gentoo.org/viewtopic.php?p=3088571#3088571 so if i mixed software branches, does this negate my usefulness at filing a bug report? i was under the assumption that package.keywords was an acceptable way of doing this, to test new software, ie kde 3.5. thanks for the reply, and sorry to file an unnecessary bug. i hope i can learn how to properly use bugs.gentoo.org in the near future. :)
OK, so what you want to tell is that >=poppler-0.5.0 fails to compile when <poppler-bindings-0.5.0 is installed? So it should block those lower versions? (b/c it can't depend on poppler-bindings, that would create circular dependency).
yes, that is what i was trying to say, thank you :) perhaps then >kde-base/kpdf-3.5.0 should depend on >poppler-bindings-0.5.0? or as you said, blocking older versions. would portage then inform the user that poppler-bindings must be unmasked?
This needs to be solved in poppler ebuilds. If poppler doesn't compile when older version of poppler-bindings is installed, it should block it.
They were both made stable simultaneously .. and none of them is masked, they are just ~arch :) A blocker would not work because you need to upgrade poppler before poppler-bindings
(In reply to comment #6) this is actaully because of kde-base/kpdf-3.5.1, not 3.5.0. sorry for the confusion; however, poppler-bindings-0.5.0 did in fact have to be installed before poppler-0.5.0-r2, which would otherwise fail. The poppler-bindings dependency was satisfied with poppler-0.4.3*, which was previously installed to for kpdf-3.5.0.
where exactly do I need to change deps? I wont put a blocker in there because that really breaks things ..
can kpdf-3.5.1 depend on poppler-bindings?
it does already. Next question?
ok, then kpdf-3.5.1 should depend on >=poppler-bindings-0.5.0. kpdf-3.5.1 was satisfied having poppler-bindings-0.4.3, but poppler was not.
# grep poppler /usr/portage/kde-base/kpdf/kpdf-3.5.1-r2.ebuild >=app-text/poppler-0.5.0-r1 >=app-text/poppler-bindings-0.5.0" ahem, where is your problem?
To amplify: poppler doesn't care if poppler-bindings is installed, how which version it is. poppler-bindings deps on poppler, not the other way around.
poppler will fail to compile if <poppler-bindings-0.5 is previously installed.
Poppler 5 builds fine here with poppler-bindings < 5, and without it installed. And, in fact, I cannot build poppler-bindings 5 without poppler 5 already installed.
