|
Bugzilla – Full Text Bug Listing |
| Summary: | error: %post(banshee-engine-gst-0.9.7-4.3) scriptlet failed, exit status 127 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Stefan Sauer <ensonic> |
| Component: | Sound | Assignee: | Gary Ekker <gekker> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stefan Sauer
2005-11-23 17:19:14 UTC
banshee-engine-gst needs to PreReq gstreamer. This is fixed for 10.1. We won't be pushing an update out for 10.0 users. Please install gstreamer first and then banshee. he, iam a gstreamer developer and I *have* gstreamer 0.8 and 0.9 installed. So its not that what makes it fail. Any idea, how I can examine in more detail what goes wrong? Well, the scriptlet in question is: /opt/gnome/bin/gst-register-0.8 >/dev/null 2>&1 We've been assuming the problem was that banshee-engine-gst didn't prerequire gstreamer, and hence that there was no guarantee that gstreamer was installed prior to banshee-engine-gst. Try running /opt/gnome/bin/gst-register-0.8 (without directing to /dev/null) and see what it's unhappy about. hmm, that can't be the problem. I run gst-register-0.8; echo $? and it was running fine (exit code = 0) I don't know haw the package stuff via yast2 works - is there a way to just download the patch and apply it manually so that I can see the shell output. Sure, you can just download the rpm. Then install with "yast2 -i banshee.rpm".
Then you'll see if it fails with Yast.
These are the only scripts that are run when installing the banshee packages:
%post
export GCONF_CONFIG_SOURCE=`opt/gnome/bin/gconftool-2 --get-default-source`
opt/gnome/bin/gconftool-2 --makefile-install-rule etc/opt/gnome/gconf/schemas/banshee.schemas >/dev/null
%run_ldconfig
%post -n banshee-engine-gst
%{gstreamerprefix}/bin/gst-register >/dev/null 2>&1
%post -n banshee-engine-helix
%{gstreamerprefix}/bin/gst-register >/dev/null 2>&1
Perhaps there is problem installing the GConf schema?
root@hoshi:/home/ensonic/download> rpm -i banshee-0.9.11.1-9.i586.rpm
error: Failed dependencies:
banshee-engine is needed by banshee-0.9.11.1-9
root@hoshi:/home/ensonic/download> rpm -i banshee-engine-gst-0.9.11.1-9.i586.rpm
error: Failed dependencies:
banshee = 0.9.11.1 is needed by banshee-engine-gst-0.9.11.1-9
root@hoshi:/home/ensonic/download>
is there a circular dependeciy?
Btw. I've added
ftp://ftp.suse.com/pub/suse/i386/supplementary/GNOME/update_for_10.0/yast-source/
to my yast source, but none of the packages there is picked up when doing an online update.
Anyway seem to spotted one bug! --------------------------------------
%post -n banshee-engine-gst
%{gstreamerprefix}/bin/gst-register >/dev/null 2>&1
%post -n banshee-engine-helix
%{gstreamerprefix}/bin/gst-register >/dev/null 2>&1
----------------------------------------------------------------------
that must be gst-register-0.8 !
gst-register is not available in 0.10 and in the mean-time was the 0.9 development version.
Still after manually updating all packages, the online update wants to install an update :(
its not totally circular - banshee just needs one engine in order to do something useful. Just install both packages at the same time: rpm -Uvh banshee-0.9.11.1-9.i586.rpm banshee-engine-gst-0.9.11.1-9.i586.rpm The post install scripts have been fixed to use the versioned gst-register, gst-register-0.8 in this case, as we don't have 0.10 in SUSE yet.
Like JP said, it's not totally circular, you have to install one of the engines along with banshee. The banshee-engine-* packages did have a slight bug in them, where, they provided "banshee-engine", which satisfies any version. This has been fixed so that they only provide the version "Provides: banshee-engine = %{version}".
These fixes will appear in the first preview of SUSE 10.1 Professional.
no comment for 2 weeks. Please re-open if there is still an issue. in 10.0 it has not be fixed, so I just ignore the update during every online update :( I'll reopen the bug it it still fails for me on suse 10.1 |