253170 – esync (esearch-0.7.1) does not work with current version of portage

Bug 253170 - esync (esearch-0.7.1) does not work with current version of portage

Summary: esync (esearch-0.7.1) does not work with current version of portage

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High normal
Assignee:	Portage Tools Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2008-12-30 18:15 UTC by Sergey Belyashov
Modified:	2008-12-30 18:25 UTC (History)
CC List:	0 users

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 Sergey Belyashov 2008-12-30 18:15:36 UTC

app-portage/esearch-0.7.1 does not work with sys-apps/portage-2.1.6.4 (sync removed from it).


Reproducible: Always

Steps to Reproduce:
1. emerge esearch
2. esync -v

Actual Results:  
/usr/lib/portage/pym/output.py:39: DeprecationWarning: DEPRECATION NOTICE: The output module was replaced by portage.output
 * Importing old portage tree
 * Doing '/usr/bin/emerge sync' now
Calculating dependencies ... done!

emerge: there are no ebuilds to satisfy "sync".

Expected Results:  
/usr/lib/portage/pym/output.py:39: DeprecationWarning: DEPRECATION NOTICE: The output module was replaced by portage.output
 * Importing old portage tree
 * Doing '/usr/bin/emerge --sync' now

Also this problem discussed in Bug 124601

Comment 1 Paul Varner (RETIRED) gentoo-dev

2008-12-30 18:25:01 UTC

This is fixed in esearch-0.7.1-r5