Bug 476024 - errors.py file required by sabayon-apply
Summary: errors.py file required by sabayon-apply
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sabayon
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 470157 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-11 16:01 UTC by Daniel Walsh
Modified: 2015-03-03 22:33 UTC (History)
3 users (show)

Fixed In Version: 2.25.0-4.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-27 07:12:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Daniel Walsh 2008-12-11 16:01:16 UTC
Description of problem:

sabayon-apply 
Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 43, in <module>
    from sabayon import errors
ImportError: cannot import name errors

If you do not have sabayon installed this package blows up.

Comment 1 Bug Zapper 2009-06-09 10:14:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Matthias Clasen 2009-06-17 02:05:36 UTC
*** Bug 470157 has been marked as a duplicate of this bug. ***

Comment 3 Daniel Walsh 2009-10-20 14:01:39 UTC
Tomas can we get this fixed in F12?  I will do the fix if this is ok?

Comment 4 Fedora Update System 2009-10-23 12:43:15 UTC
sabayon-2.25.0-4.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/sabayon-2.25.0-4.fc11

Comment 5 Tomáš Bžatek 2009-10-23 12:44:39 UTC
Fixed in sabayon-2.25.0-4.fc11, sabayon-2.28.0-2.fc12 and sabayon-2.28.0-2.fc13

Comment 6 Fedora Update System 2009-10-27 07:12:30 UTC
sabayon-2.25.0-4.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.


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