| View previous topic :: View next topic |
| Author |
Message |
Team_Beast
Tux's lil' helper
Joined: 16 May 2004
Posts: 97
|
 Posted: Sun Apr 17, 2005 1:07 am Post subject: Ebuild giving errors |
 |
|
If I unmerge a package, say bin2iso with ebuild I get the following error, | Code: | Traceback (most recent call last):
File "/usr/bin/ebuild", line 57, in ?
portage_util.writemsg("Could not run the required binary?\n")
NameError: name 'portage_util' is not defined
|
after the unmerge procedure. bin2iso does get unmerged but I get this error. Anyone seen this before? Also, after i have unmerged a package using ebuild, instead of emerge, I cant use ebuild to merge it again. I get the error | Code: | /usr/lib/portage/bin/ebuild.sh: line 1686: /var/db/pkg/app-cdr/bin2iso-19b-r1/bin2iso-19b-r1.ebuild: No such file or directory
!!! ERROR: app-cdr/bin2iso-19b-r1 failed.
!!! Function , Line 1686, Exitcode 1
!!! error sourcing ebuild
!!! If you need support, post the topmost build error, NOT this status message. |
However I can use emerge to merge the ebuild fine. Anyone know what is going on here? I cant even use emerge to merge the package, unmerge it and then use ebuild to merge it. ebuild will never work with that package again. Whats going on!? |
|
| Back to top |
|
 |
hjnenc
Veteran
Joined: 15 Aug 2004
Posts: 1599
Location: Vienna, Austria
|
| Posted: Sun Apr 17, 2005 7:45 am Post subject: |
|
|
| If you use the ebuild command, take the .ebuilds from /usr/portage/<category>/<package>/<package>-<version>.ebuild instead of /var/db/pkg/... |
|
| Back to top |
|
|
Team_Beast
Tux's lil' helper
Joined: 16 May 2004
Posts: 97
|
| Posted: Sun Apr 17, 2005 12:31 pm Post subject: |
|
|
I am using that ebuild source, I will post a full example to make it clearer | Code: | Beast simon # ebuild /usr/portage/app-arch/unrar/unrar-3.4.3.ebuild unmerge
No package files given... Grabbing a set.
<<< obj /usr/share/doc/unrar-3.4.3/readme.txt.gz
<<< obj /usr/bin/unrar
<<< dir /usr/share/doc/unrar-3.4.3
--- !empty dir /usr/share/doc
--- !empty dir /usr/share
--- !empty dir /usr/bin
--- !empty dir /usr
Traceback (most recent call last):
File "/usr/bin/ebuild", line 57, in ?
portage_util.writemsg("Could not run the required binary?\n")
NameError: name 'portage_util' is not defined
Beast simon # ebuild /usr/portage/app-arch/unrar/unrar-3.4.3.ebuild merge
Disabling noauto in features... merge disables it. (qmerge doesn't)
>>> md5 src_uri ;-) unrarsrc-3.4.3.tar.gz
/usr/lib/portage/bin/ebuild.sh: line 1686: /var/db/pkg/app-arch/unrar-3.4.3/unrar-3.4.3.ebuild: No such file or directory
!!! ERROR: app-arch/unrar-3.4.3 failed.
!!! Function , Line 1686, Exitcode 1
!!! error sourcing ebuild
!!! If you need support, post the topmost build error, NOT this status message. |
Any ideas? Is it a bug I'm seeing? |
|
| Back to top |
|
|
hjnenc
Veteran
Joined: 15 Aug 2004
Posts: 1599
Location: Vienna, Austria
|
| Posted: Sun Apr 17, 2005 4:25 pm Post subject: |
|
|
Does not look correct to me. What happens if you do the steps one by one (fetch, unpack, compile, install, qmerge)?
Do you have the necessary permissions in /var/db/pkg/? |
|
| Back to top |
|
|
Team_Beast
Tux's lil' helper
Joined: 16 May 2004
Posts: 97
|
| Posted: Sun Apr 17, 2005 5:29 pm Post subject: |
|
|
| Code: | Beast db # ebuild /usr/portage/app-arch/unrar/unrar-3.4.3.ebuild fetch
>>> md5 src_uri ;-) unrarsrc-3.4.3.tar.gz
Beast db # ebuild /usr/portage/app-arch/unrar/unrar-3.4.3.ebuild unpack
>>> md5 src_uri ;-) unrarsrc-3.4.3.tar.gz
/usr/lib/portage/bin/ebuild.sh: line 1686: /var/db/pkg/app-arch/unrar-3.4.3/unrar-3.4.3.ebuild: No such file or directory
!!! ERROR: app-arch/unrar-3.4.3 failed.
!!! Function , Line 1686, Exitcode 1
!!! error sourcing ebuild
!!! If you need support, post the topmost build error, NOT this status message. |
It goes wrong in the unpack stage as you can see. The permissions are all fine in the db dir - I'm begining to think I've stumbled across a bug. |
|
| Back to top |
|
|
hjnenc
Veteran
Joined: 15 Aug 2004
Posts: 1599
Location: Vienna, Austria
|
| Posted: Sun Apr 17, 2005 6:01 pm Post subject: |
|
|
I just tried it on my box and I have the same behaviour. It works the first time but after unmerging the package, it fails in the unpack step.
| Code: | # ebuild /usr/portage/app-arch/unrar/unrar-3.4.3.ebuild unpack
>>> md5 files ;-) unrar-3.4.2.ebuild
>>> md5 files ;-) unrar-3.4.1.ebuild
>>> md5 files ;-) ChangeLog
>>> md5 files ;-) metadata.xml
>>> md5 files ;-) unrar-3.4.3.ebuild
>>> md5 files ;-) files/digest-unrar-3.4.1
>>> md5 files ;-) files/digest-unrar-3.4.2
>>> md5 files ;-) files/digest-unrar-3.4.3
>>> md5 src_uri ;-) unrarsrc-3.4.3.tar.gz
/usr/lib/portage/bin/ebuild.sh: line 1702: /var/db/pkg/app-arch/unrar-3.4.3/unrar-3.4.3.ebuild: No such file or directory
!!! ERROR: app-arch/unrar-3.4.3 failed.
!!! Function , Line 1702, Exitcode 1
!!! error sourcing ebuild
!!! If you need support, post the topmost build error, NOT this status message. |
So I guess, it's time for a bug report.
edit: cleaning out /var/tmp/portage/unrar-3.4.3 brings things back to normal. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
