I was trying to test the new to be released ebox 0.12 and it failed.
# aptitude dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are BROKEN:
ebox-objects
The following packages will be upgraded:
ebox ebox-ca ebox-firewall ebox-mail ebox-mailfilter ebox-network ebox-ntp ebox-openvpn ebox-printers ebox-samba ebox-services ebox-squid ebox-trafficshaping
ebox-usersandgroups ebox-webserver libebox
16 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1871kB/2417kB of archives. After unpacking 184kB will be used.
The following packages have unmet dependencies:
ebox-objects: Depends: ebox (< 0.12) but 0.12-0ubuntu1~ppa4~hardy1 is to be installed.
Resolving dependencies...
The following actions will resolve these dependencies:
Remove the following packages:
ebox-firewall
ebox-mail
ebox-mailfilter
ebox-network
ebox-ntp
ebox-objects
ebox-openvpn
ebox-printers
ebox-samba
ebox-squid
ebox-trafficshaping
ebox-usersandgroups
ebox-webserver
Score is 947
Accept this solution? [Y/n/q/?]
Is this only happen to me?, cause I didn't found any other user complaining?, it seems the new ebox-objects haven't been uploaded to this repo:
deb http://ppa.launchpad.net/ebox-unstable/ubuntu hardy main
Cause look what I have as my newest packages:
# aptitude show ebox-objects
Package: ebox-objects
State: installed
Automatically installed: yes
Version: 0.11.101-0ubuntu1~ppa1
Priority: optional
Section: web
Maintainer: Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
Uncompressed Size: 365k
Depends: ebox (>= 0.11.99), ebox (< 0.12), gconf2 (>= 2.10.1-2), libnet-ip-perl
Conflicts: ebox (< 0.9.99)
Replaces: ebox (< 0.9.99)
Description: eBox - Object management
eBox is a framework for the development and deployment of security-wise network services in small and medium-sized networks, offering a simplified graphical interface to non
expert users. It can be set up as a gateway, having some extra features over a usual router.
This module adds object support, allowing to manage objects which could be used as access control lists (ACL) by other modules. Each object represents a certain number of hosts or
network, providing an abstraction to make easy its use across the eBox modules.
Any comments?
regards,
cjav