For example, I have installed version of app-emacs/ecb and such line in /etc/portage/package.keywords: app-emacs/ecb ~x86 Normaly when I run emerge --update world, it update also "ecb" to last "~x86" version, but several days ago this feature is broken. When I type $ emerge -pvuD world These are the packages that I would merge, in order: Calculating world dependencies ...done! Total size of downloads: 0 kB $ emerge -pvu app-emacs/ecb These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] app-emacs/ecb-2.32-r1 [2.32] +java 0 kB Total size of downloads: 0 kB The same happend with vim-7.0, gcc and many other packages.
Portage 2203-svn (default-linux/x86/2005.0, gcc-4.1.0, glibc-2.4-r1, 2.6.16-gentoo-r6 i686) ================================================================= System uname: 2.6.16-gentoo-r6 i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 dev-python/pycrypto: [Not Present] dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] 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-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 -mfpmath=sse -msse -mmmx -m3dnow -pipe" 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.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /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/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -mfpmath=sse -msse -mmmx -m3dnow -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.du.se/pub/os/gentoo" LANG="ru_RU.UTF-8" LC_ALL="" LINGUAS="en ru" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/evgeniy/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X acl alsa apache2 apm arts audiofile avi bash-completion berkdb bitmap-fonts bzip2 cdr cjk cli crypt cscope cups curl dlloader doc dri eds emacs emboss encode esd exif expat fam fbcon firefox flac font-server foomaticdb fortran gd gdbm gif gimpprint glut gmp gpm gstreamer gtk gtk2 gtkhtml idn imagemagick imlib ipv6 isdnlog java jpeg junit kde kdeenablefinal kdexdeltas lcms libcaca libg++ libwww logrotate lua mad maildir mhash mikmod ming mmx mng motif mp3 mpeg mysql ncurses nls nptl nptlonly ogg oggvorbis opengl oss pam pcre pdflib perl png ppds pppd python qt quicktime readline recode reflection ruby scanner sdl session slang speex spel spell spl sqlite sse ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts udev unicode usb vorbis wmf xml xml2 xorg xv xvid zlib linguas_en linguas_ru userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_RSYNC_OPTS
The `emerge -uD` world command will not update app-emacs/ecb unless it is a dependency of either your world or system sets. If it's not, you can use `emerge --noreplace app-emacs/ecb` to have it added to your world set automatically.
>The `emerge -uD` world command will not update app-emacs/ecb unless it is a >dependency of either your world or system sets. I don't understand. Lets for clearness forget about "-D". I have installed version of "ecb": 2.32 I unmasked it: app-emacs/ecb ~x86 There is new version: 2.32-r1, but emerge -pu world didn't update it to last version. Because of it installed, it should situtated in "world" class of packages, am I wrong?
s/emerge -pu world didn't update it to last version/emerge -pu world didn't show that avaiable update/g
One more thing: emerge -pv --newuse world show nothing, but before last update of portage it show several packages. I seems to me that "world list" was deleted during update of "portage", or it calculated in new way. Is it normal? emerge --noreplace app-emacs/ecb add ecb to "world class" and now "emerge -vu world" update ecb. But the similar situation with all packages in my system. in "world class" only packages that installed after last update of "portage".
(In reply to comment #3) > Because of it installed, it should situtated in "world" class of packages, > am I wrong? You are wrong. We plan to implement a different "all" set that will have that behavior. See bug 96088.
(In reply to comment #5) > emerge -pv --newuse world > > show nothing, > but before last update of portage it show several packages. Please provide a specific example, include the other version of portage that does not have this problem. You may also want to try the latest ~arch version (currently 2.1_pre10-r5) which is relatively safe to use because we're nearing the release candidate stage.
(In reply to comment #6) > You are wrong. We plan to implement a different "all" set that will have that But what is this message mean, it appear after each installation: >>> Recording category/package in "world" favorites file... is it also wrong?
(In reply to comment #8) > But what is this message mean, it appear after each installation: > >>> Recording category/package in "world" favorites file... > is it also wrong? If it appears after *every* installation, then yes, it's wrong. It should only appear when a package is merged explicitly (rather than pulled in as a dependency).
(In reply to comment #7) > (In reply to comment #5) > > emerge -pv --newuse world > > > > show nothing, > > but before last update of portage it show several packages. > > Please provide a specific example, include the other version of portage that > does not have this problem. At now I have sys-apps/portage-2.0.54-r1, all version before it worked fine. I supposed now recoil to previous version of portage didn't help, because of now "/var/lib/portage/world" contains only packages installed after portage update.
(In reply to comment #10) > At now I have sys-apps/portage-2.0.54-r1, > all version before it worked fine. > I supposed now recoil to previous version of portage didn't help, > because of now "/var/lib/portage/world" contains only packages installed after > portage update. It's a known issue that portage-2.0.x can corrupt the world file (2.1 takes special precautions to prevent this). There is `regenworld` script included with portage that can (more or less) regenerate the world file from /var/log/emerge.log.
(In reply to comment #11) > because of now "/var/lib/portage/world" contains only packages installed after > portage update. If this is more that a regenworld issue then please reopen.
