Summary: | PORTAGE problem (the ding-dong effect) pinning gvim and vim to the does not work with KEYWORDS=~x86 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Y-z <eyez> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | CC: | agriffis |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Y-z
2003-05-13 16:25:57 UTC
I've got some more output, which might indicate it's indeed an interdependency problem: % emerge -vdup world These are the packages that I would merge, in order: Calculating world dependencies / Parent: ebuild / app-editors/gvim-6.1-r8 merge Depstring: >=sys-apps/portage-2.0.45-r3 >=sys-apps/sed-4 sys-devel/autoconf dev-util/cscope vim-with-x? ( virtual/x11 ) gpm? ( >=sys-libs/gpm-1.19.3 ) ncurses? ( >=sys-libs/ncurses-5.2-r2 ) : ( sys-libs/libtermcap-compat ) perl? ( dev-lang/perl ) python? ( dev-lang/python ) ruby? ( =dev-lang/ruby-1.6* ) ~app-editors/vim-core-6.1 x11-base/xfree gtk2? ( >=x11-libs/gtk+-2.1 virtual/xft ) : ( gnome? ( gnome-base/gnome-libs ) : ( gtk? ( =x11-libs/gtk+-1.2* ) ) ) !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) Candidates: ['>=sys-libs/ncurses-5.2-r2', 'dev-lang/perl', '>=sys-apps/sed-4', 'sys-devel/patch', 'dev-lang/python', 'x11-base/xfree', '>=sys-apps/portage-2.0.45-r3', '>=sys-libs/gpm-1.19.3', 'dev-util/cscope', 'sys-devel/autoconf', '~app-editors/vim-core-6.1', '=x11-libs/gtk+-1.2*'] ebuild: sys-libs/ncurses-5.3-r1 -ebuild: dev-lang/perl-5.8.0-r10 ebuild: sys-apps/sed-4.0.7 \ebuild: sys-devel/patch-2.5.4-r5 |ebuild: dev-lang/python-2.2.2-r1 /ebuild: x11-base/xfree-4.3.0-r2 -ebuild: sys-apps/portage-2.0.48_pre6 ebuild: sys-libs/gpm-1.20.0-r6 \ebuild: dev-util/cscope-15.3 |ebuild: sys-devel/autoconf-2.57-r1 /ebuild: app-editors/vim-core-6.1-r5 - Parent: ebuild / app-editors/vim-core-6.1-r5 merge Depstring: >=sys-apps/portage-2.0.45-r3 >=sys-apps/sed-4 sys-devel/autoconf dev-util/cscope vim-with-x? ( virtual/x11 ) gpm? ( >=sys-libs/gpm-1.19.3 ) ncurses? ( >=sys-libs/ncurses-5.2-r2 ) : ( sys-libs/libtermcap-compat ) perl? ( dev-lang/perl ) python? ( dev-lang/python ) ruby? ( =dev-lang/ruby-1.6* ) !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) Candidates: ['dev-lang/python', '>=sys-libs/ncurses-5.2-r2', '>=sys-apps/portage-2.0.45-r3', 'dev-lang/perl', '>=sys-apps/sed-4', '>=sys-libs/gpm-1.19.3', 'sys-devel/autoconf', 'sys-devel/patch', 'dev-util/cscope'] ebuild: dev-lang/python-2.2.2-r1 ebuild: sys-libs/ncurses-5.3-r1 ebuild: sys-apps/portage-2.0.48_pre6 ebuild: dev-lang/perl-5.8.0-r10 ebuild: sys-apps/sed-4.0.7 ebuild: sys-libs/gpm-1.20.0-r6 ebuild: sys-devel/autoconf-2.57-r1 ebuild: sys-devel/patch-2.5.4-r5 ebuild: dev-util/cscope-15.3 Exiting... ebuild / app-editors/vim-core-6.1-r5 merge ebuild: x11-libs/gtk+-1.2.10-r10 \Exiting... ebuild / app-editors/gvim-6.1-r8 merge - Parent: ebuild / app-editors/vim-6.1-r21 merge Depstring: >=sys-apps/portage-2.0.45-r3 >=sys-apps/sed-4 sys-devel/autoconf dev-util/cscope vim-with-x? ( virtual/x11 ) gpm? ( >=sys-libs/gpm-1.19.3 ) ncurses? ( >=sys-libs/ncurses-5.2-r2 ) : ( sys-libs/libtermcap-compat ) perl? ( dev-lang/perl ) python? ( dev-lang/python ) ruby? ( =dev-lang/ruby-1.6* ) ~app-editors/vim-core-6.1 !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) Candidates: ['dev-lang/python', '>=sys-libs/ncurses-5.2-r2', '>=sys-apps/portage-2.0.45-r3', 'dev-lang/perl', '>=sys-apps/sed-4', '>=sys-libs/gpm-1.19.3', 'sys-devel/patch', 'sys-devel/autoconf', '~app-editors/vim-core-6.1', 'dev-util/cscope'] ebuild: dev-lang/python-2.2.2-r1 ebuild: sys-libs/ncurses-5.3-r1 ebuild: sys-apps/portage-2.0.48_pre6 ebuild: dev-lang/perl-5.8.0-r10 ebuild: sys-apps/sed-4.0.7 ebuild: sys-libs/gpm-1.20.0-r6 ebuild: sys-devel/patch-2.5.4-r5 ebuild: sys-devel/autoconf-2.57-r1 ebuild: app-editors/vim-core-6.1-r5 ebuild: dev-util/cscope-15.3 Exiting... ebuild / app-editors/vim-6.1-r21 merge - Parent: ebuild / sys-devel/prelink-20030505 merge Depstring: >=dev-libs/elfutils-0.72 !dev-libs/libelf >=sys-libs/glibc-2.3.1 >=sys-devel/binutils-2.13.90.0.10 !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) Candidates: ['>=sys-devel/binutils-2.13.90.0.10', '!dev-libs/libelf', '>=sys-libs/glibc-2.3.1', 'sys-devel/patch', '>=dev-libs/elfutils-0.72'] ebuild: sys-devel/binutils-2.14.90.0.2 \ebuild: sys-libs/glibc-2.3.2-r1 ebuild: sys-devel/patch-2.5.4-r5 ebuild: dev-libs/elfutils-0.76-r2 Exiting... ebuild / sys-devel/prelink-20030505 merge ...done! [ebuild UD] app-editors/vim-core-6.1-r5 [6.2_pre3] -gnome +gpm +gtk -gtk2 +ncurses +nls +perl +python -ruby -vim-with-x +X [ebuild UD] app-editors/gvim-6.1-r8 [6.2_pre3] -gnome +gpm +gtk -gtk2 +ncurses +nls +perl +python -ruby -vim-with-x +X [ebuild UD] app-editors/vim-6.1-r21 [6.2_pre3] -gnome +gpm +gtk -gtk2 +ncurses +nls +perl +python -ruby -vim-with-x +X [ebuild U ] sys-devel/prelink-20030505 [20030217] OK. This is weird behaviour. An emerge just DOWNgraded the version of all *vim* builds to the REQUIRED 6.1* version. But a new upgrade AGAIN shows this: emerge -up world ~goddess These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] app-editors/vim-core-6.2_pre3 [6.1-r5] [ebuild U ] app-editors/vim-6.2_pre3 [6.1-r21] What on earth could be happening? Rather frustrating, talking to myself, like this... The fact is that the versions now change with every emerge -u world: # emerge -up world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] app-editors/vim-core-6.1-r5 [6.2_pre5] [ebuild UD] app-editors/vim-6.1-r21 [6.2_pre5] [ let them build ... ] # emerge -u world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] app-editors/vim-core-6.2_pre5 [6.1-r5] [ebuild UD] app-editors/vim-6.2_pre5 [6.1-r21] This can be repeated ad infinitum... this has been going on for quite some time now. I have the same problem with netpbm. What's going on? How to find out which app has the broken dependancy? Thank god ccache makes the rebuild after downgrade fast. Nevertheless it's annoying. I think the problem lies in this, that a package requires a certain version of a certain package, ignoring the version specified in the world file. But the next emerge (the previous requirement now being satisfied) sees then the specified version, and installs it. To answer your question, though: I did an emerge -vdup world, but my guess is that an emerge -vdup <package> may also contain the hints; see the Additional Comment 1. And yes, this is rather annoying! I hope it gets fixed soon (although vim 6.2 is now stable, and I do not have the problem anymore ;) |