5783 – emerge -s doesn't work fine with $PORTDIR_OVERLAY

Bug 5783 - emerge -s doesn't work fine with $PORTDIR_OVERLAY

Summary: emerge -s doesn't work fine with $PORTDIR_OVERLAY

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High major (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-07-30 13:14 UTC by Maurizio Disimino
Modified:	2011-10-30 22:18 UTC (History)
CC List:	2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Maurizio Disimino 2002-07-30 13:14:07 UTC

Portage 2.0.22

sexybit qmailadmin # emerge -s qmailadmin
Searching...
[ Results for search key : qmailadmin ]
[ Applications found : 1 ]

*  net-mail/qmailadmin
      Latest version Available: 1.0.2
      Latest version Installed: [ Not Installed ]
      Homepage:
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1361, in ?
    searchinstance.output()
  File "/usr/bin/emerge", line 425, in output
    print "     ", "Homepage:",self.getHomepage(self.getFullPath(match,
full_package))
  File "/usr/bin/emerge", line 449, in getHomepage
    file = open(ebuildPath)
IOError: [Errno 2] No such file or directory:
'/usr/portage/net-mail/qmailadmin/qmailadmin-1.0.2.ebuild'

Here's my conf.
sexybit qmailadmin # grep PORTDIR_OVERLAY /etc/make.conf
PORTDIR_OVERLAY="/usr/myportage/"
sexybit qmailadmin # find / -name 'qmailadmin*ebuild'
/usr/myportage/net-mail/qmailadmin/qmailadmin-1.0.2.ebuild

emerge -S doesn't work at all.

Maurizio Disimino

Comment 1 Daniel Robbins (RETIRED) gentoo-dev

2002-08-01 01:15:47 UTC

OK, I've rewritten the searching code to make it much cleaner and fully API
compliant; it will very likely work flawlessly.  This code will be in Portage
2.0.23; re-open this bug if you still have problems with the 2.0.23 code.