Results 1 to 1 of 1
This originally began with me trying to install L7 protocols as such:
Code:
Floodgate:~$ sudo apt-get install ebox-l7-protocols
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some ...
- 08-04-2009 #1Just Joined!
- Join Date
- Mar 2007
- Posts
- 11
eBox Dependency Hell
This originally began with me trying to install L7 protocols as such:
I've gone through a number of other attempts to install various modules, and two errors seem to keep popping up:Code:Floodgate:~$ sudo apt-get install ebox-l7-protocols Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: ebox-l7-protocols: Depends: ebox (>= 1.1~svn) but 1.0.1-0ubuntu1~ppa1~hardy1 is to be installed E: Broken packages
And:Code:The following packages have unmet dependencies: ebox: Depends: libyaml-tiny-perl but it is not installable E: Broken packages
I've been beating my head against a wall working with this, so any help is desperately needed and greatly appreciated!Code:Removing jabber-muc ... invoke-rc.d: unknown initscript, /etc/init.d/jabberd2 not found. dpkg: error processing jabber-muc (--remove): subprocess pre-removal script returned error exit status 100 Errors were encountered while processing: jabber-muc E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover:


Reply With Quote