The update on the 1.0-r1 version shows up when I run "emerge -pvu --deep world", but it does not show up when I try to update that package specifically. It is really weird. Here is the output: | # emerge -pvu world | | These are the packages that I would merge, in order: | | Calculating world dependencies ...done! | [...] | [ebuild U ] app-text/docbook-xml-simple-dtd-1.0-r1 [1.0] 30 kB | [ebuild U ] app-text/docbook-xsl-stylesheets-1.68.1-r1 [1.66.1] 944 kB | [...] But: | # emerge -pv app-text/docbook-xml-simple-dtd | | These are the packages that I would merge, in order: | | Calculating dependencies ...done! | [ebuild R ] app-text/docbook-xml-simple-dtd-4.1.2.4-r2 34 kB | | Total size of downloads: 34 kB Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r11 i686) ================================================================= System uname: 2.6.11-gentoo-r11 i686 AMD Athlon(tm) XP 3200+ Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 2 2005, 11:49:14)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.9.5, 1.7.9-r1, 1.5, 1.6.3, 1.4_p6, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /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/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon-xp -O3 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks notitles sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.inode.at/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo" MAKEOPTS="-j1" 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 3dnowext X adns apm avi bash-completion berkdb bitmap-fonts bzip2 caps cdparanoia cdr crypt css cups curl divx4linux dvd dvdread emacs emboss encode expat foomaticdb gd gdbm gif glade glut graphviz gtk gtk2 hardened imagemagick imlib ipv6 ithreads java javascript jce jpeg latex libg++ libwww mad mbox mikmod milter mmx mozilla mp3 mpeg mplayer ncurses normalizemime nvidia ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime rar readline real rtc spell sse ssl subtitles tetex threads tiff truetype truetype-fonts type1-fonts vorbis win32codecs xml xml2 xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
(In reply to comment #0) > The update on the 1.0-r1 version shows up when I run "emerge -pvu --deep world", > but it does not show up when I try to update that package specifically. It is > really weird. No, that's now weird, that't perfectly normal and is a feature. man emerge <snip> --deep (-D) When used in conjunction with --update, this flag forces emerge to consider the entire dependency tree of packages, instead of checking only the immediate dependencies of the packages. As an example, this catches updates in libraries that are not directly listed in the dependencies of a package. </snip>
And additionally, world != atom, so I really can't see anything weird about differences between emerge -upv some-ebuild vs. emerge -upv world app-text/docbook-xml-simple-dtd does not depend on docbook-xsl-stylesheets.
Err, I've completely misread the bug report b/c the report is mixing too many unrelated things together. The real issue here seems that: docbook-xml-simple-dtd-1.0{-r1} has SLOT="1.0" while docbook-xml-simple-dtd-4.1.2.4-r2 has SLOT="0" Sorry for the mess. Reopened.
Eh, finishing my monologue here, I still think that this is invalid. There is no reason for docbook-xml-simple-dtd-1.0-r1 upgrade to show b/c you did _not_ request any upgrade: emerge -pv app-text/docbook-xml-simple-dtd; and the old version is _still_ in portage and can be (re)installed. I.e., emerge -pvu != emerge -pv
What command do I have to enter to upgrade to "docbook-xml-simple-dtd-1.0-r1" then? Apparently I'm doing something wrong: | # emerge -pvu docbook-xml-simple-dtd | | These are the packages that I would merge, in order: | | Calculating dependencies ...done! | | Total size of downloads: 0 kB
(In reply to comment #5) > What command do I have to enter to upgrade to "docbook-xml-simple-dtd-1.0-r1" > then? Sorry, no idea... :/ CCing portage.
If you want to force stuff, first do emerge -s or simular to find the package and available versions. Then do something like emerge =app-text/docbook-xml-simple-dtd-1.0-r1 = forces what version of a package to install. But yes, how to select SLOT options when doing upgrading just by package name could need some (better) documentation.
Okay, thank you for the hint. What I don't understand is why an "update world" would update it, but telling Portage to update _this very package_ won't work (unless I explicitly state the version). I think that's counter-intuitive. Is that behavior intentional?
Re-assigning since this is not a bug in docbook-xml-simple-dtd
emerge -u and slotted packages is broken, see bug 4698. emerge docbook-xml-simple-dtd gives the correct output since you already have that version installed ( and emerge doesn't currently have a way to specify slots, which are a quasi-hack anyhow ). the upgrade catches the slot=1.0 one because it's currently broken and I don't think anyone has nailed down exactly how slots and upgrades need to work yet. Regardless the problem is known about, I'd suggest adding a dep on 4698 and/or duping this one. -Ajec
Something depends on the package slot containing the lesser version. When you ask to update the package directly, portage only looks at the latest version. *** This bug has been marked as a duplicate of 4698 ***
