Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 35592 - portage--2.0.49-r18 and python-2.* cross-dependency
Summary: portage--2.0.49-r18 and python-2.* cross-dependency
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 35525
  Show dependency tree
 
Reported: 2003-12-11 03:38 UTC by Guillaume Baudot
Modified: 2003-12-16 03:12 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume Baudot 2003-12-11 03:38:31 UTC
I'm not sure, but I may have encountered 2 bugs at once... As I wanted to update my system, I found out that:
1/ portage wants to upgrade python while a version matches portage dep
2/ python depends on a portage version that does not exist
NB Using ACCEPT_KEYWORDS="~x86"

Reproducible: Always
Steps to Reproduce:
1.emerge -u portage (or system, or world)
2.emerge -u python
Actual Results:  
1.I have python-2.2.3-r5 installed, that should match portage dep 
(>=dev-lang/python-2.2.1), but it wants to upgrade python. Then what about 
python ?
2.There is a fantomatic dep in python-2.3.2-r2 ebuild in function pkg_setup: 
depends on >=portage-2.0.49-r16 while this revision does not exist...

Expected Results:  
1.If I'm not mistaken, portage-2.0.49-r18 should build with the already 
installed python.
2.Have to build.

First, I want to apologize for sending one bug-report for what looks more like 2 
bugs. Then, let me explain how I solved this: it was as simple as modifying the 
python ebuild, changing every ">=portage-2.0.49-r16" to ">=portage-2.0.49-r15".
Finally, what I can say is, I am far from sure it was the proper way to 
workaround, and it does not explain the python dep mismatch in portage, but that 
did the trick...
Comment 1 Marius Mauch (RETIRED) gentoo-dev 2003-12-11 10:20:38 UTC
The problem here is the -u option as it tries to update dependencies. Run `emerge portage` without -u, then it should work.
Comment 2 Guillaume Baudot 2003-12-12 04:07:37 UTC
Many thanks !
I did not try your solution, but I can tell you I was a little doubtfull when I saw your reply... and I admit I still do not understand why the update option implies update for python too, while the one installed is matching deps.
Nethertheless, someone on the forum encountered the same problem and reported sucessfull with your method: congratulations for this simple and efficient solution !
Then I believe you can feel free to mark it as FIXED.
Comment 3 Nicholas Jones (RETIRED) gentoo-dev 2003-12-12 11:27:49 UTC
I don't believe this is an issue any longer, but I'd need
more specific info to figure out exactly what you're refering
to.
Comment 4 Doug Goldstein (RETIRED) gentoo-dev 2003-12-15 15:07:58 UTC
Brand new install. Trying to do an emerge system and this is what I get.

emerge portage
Calculating dependencies ...done!
>>> emerge (1 of 2) dev-lang/python-2.3.2-r2 to /
>>> md5 src_uri ;-) Python-2.3.2.tgz
 * Dependency Failed! Requires >=sys-apps/portage-2.0.49-r16
 * Please run: emerge portage
 * before proceeding. (NOTE: do not use -u if portage wants you to upgrade python)
 
!!! ERROR: dev-lang/python-2.3.2-r2 failed.
!!! Function pkg_setup, Line 49, Exitcode 0
!!! Requires >=sys-apps/portage-2.0.49-r16
Comment 5 Guillaume Baudot 2003-12-16 03:12:54 UTC
*before proceeding. (NOTE: do not use -u if portage wants you to upgrade python)
I'm sorry: I did not see this message at the moment I tried...what does not mean it was not there !
Next time I'll try to avoid acting like a child in front of a new toy, and to give a little more time to reflexion before submitting a bugreport.