Summary: | emerge 2.1.4.4 crashes when finding packages with EAPI=2 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Antonio Augusto Santos <khaoticmind> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | bkohler, DrWilken, geo, polynomial-c, sebastian |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 240304 | ||
Attachments: | handle InvalidDependString exception when searching |
Description
Antonio Augusto Santos
2008-10-03 19:20:43 UTC
This is fixed in svn r11602. (In reply to comment #1) > This is fixed in svn r11602. > What does this mean...? Shouldn't the fix be included in a new version of portage...? Yes, when one is released. There isn't an immediate new release of portage for each and every teeny tiny bug found and fixed. Be patient. Created attachment 167477 [details, diff]
handle InvalidDependString exception when searching
If this patch is saved as /tmp/search_invalid.patch, then it can be applied as follows:
patch /usr/lib/portage/bin/emerge /tmp/search_invalid.patch
(In reply to comment #4) > Created an attachment (id=167477) [edit] > handle InvalidDependString exception when searching > > If this patch is saved as /tmp/search_invalid.patch, then it can be applied as > follows: > > patch /usr/lib/portage/bin/emerge /tmp/search_invalid.patch > Just tried the patch here, and it seens to solve the problem just fine. Any ideas when this will be released officialy? Other problems i'll keep in touch. (In reply to comment #4) > Created an attachment (id=167477) [edit] > handle InvalidDependString exception when searching > > If this patch is saved as /tmp/search_invalid.patch, then it can be applied as > follows: > > patch /usr/lib/portage/bin/emerge /tmp/search_invalid.patch > Thanks... Works ;) With this patch applied to version 2.1.4.4 and 2.1.5.6 I get the following output from packages which only exist as EAPI-2 ebuilds: # emerge -s kdessh Searching... [ Results for search key : kdessh ] [ Applications found : 1 ] * kde-base/kdessh [ Masked ] Latest version available: 4.1.2 Latest version installed: [ Not Installed ] Size of files: Unknown (getfetchlist(): 'kde-base/kdessh-4.1.2' has unsupported EAPI: '2') Homepage: http://www.kde.org/ Description: KDE frontend to ssh License: GPL-2 (In reply to comment #7) > With this patch applied to version 2.1.4.4 and 2.1.5.6 I get the following > output from packages which only exist as EAPI-2 ebuilds: > > # emerge -s kdessh > Searching... > [ Results for search key : kdessh ] > [ Applications found : 1 ] > > * kde-base/kdessh [ Masked ] > Latest version available: 4.1.2 > Latest version installed: [ Not Installed ] > Size of files: Unknown (getfetchlist(): 'kde-base/kdessh-4.1.2' has > unsupported EAPI: '2') > Homepage: http://www.kde.org/ > Description: KDE frontend to ssh > License: GPL-2 > I can confirm this. Portage 2.1.4.4 (In reply to comment #7) > * kde-base/kdessh [ Masked ] > Latest version available: 4.1.2 > Latest version installed: [ Not Installed ] > Size of files: Unknown (getfetchlist(): 'kde-base/kdessh-4.1.2' has > unsupported EAPI: '2') > Homepage: http://www.kde.org/ > Description: KDE frontend to ssh > License: GPL-2 That's the intended behavior. It's not possible for portage-2.1.x to determine the file size. In order to get that information, you'll need at least portage-2.2_rc11 which includes support for EAPI 2. *** Bug 240640 has been marked as a duplicate of this bug. *** This is fixed in portage-2.1.4.5. |