Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 152482 - sys-apps/portage-2.1.2_pre3-r7: unable to emerge packages (same problem as bug 152237)
Summary: sys-apps/portage-2.1.2_pre3-r7: unable to emerge packages (same problem as bu...
Status: VERIFIED DUPLICATE of bug 152237
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-23 02:58 UTC by Jimmy.Jazz
Modified: 2006-10-23 08:14 UTC (History)
0 users

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


Attachments
strace of portage pre3_r7 (emerge.strace.gz,151.83 KB, text/plain)
2006-10-23 03:03 UTC, Jimmy.Jazz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jimmy.Jazz 2006-10-23 02:58:06 UTC
Also sys-apps/portage-2.1.2_pre2-r9 works
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-10-23 03:00:07 UTC
Why are you filing a dupe when the original bug is still open?


*** This bug has been marked as a duplicate of 152237 ***
Comment 2 Jimmy.Jazz 2006-10-23 03:03:54 UTC
Created attachment 100258 [details]
strace of portage pre3_r7
Comment 3 Jimmy.Jazz 2006-10-23 06:54:29 UTC
(In reply to comment #1)
> Why are you filing a dupe when the original bug is still open?
> 
> 
> *** This bug has been marked as a duplicate of 152237 ***
> 

Sorry, my mistake :(

Really i do not follow your release logic. pre3_r6 isn't equal to pre3_r7, is it ?
And what does mean Resolved duplicate if it isn't resolved ?

Anyway sorry for the inconvenience.
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2006-10-23 08:14:35 UTC
(In reply to comment #3)
> Really i do not follow your release logic. pre3_r6 isn't equal to pre3_r7, is
> it ?

Until the original bug is marked as fixed, it's valid for any future portage versions.

> And what does mean Resolved duplicate if it isn't resolved ?

That it's exactly the same issue as the original bug (i.e., a duplicate).

Thanks, closing.