Dependency error message from the client isn't passed back to the server

Bug #921712 reported by Andreas Hasenack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Fix Released
Low
Björn Tillenius

Bug Description

For some reason, a specific version of bind9 is available on maverick but its dependencies are not:

root@ls3:~# apt-cache policy bind9
bind9:
  Installed: (none)
  Candidate: 1:9.7.1.dfsg.P2-2ubuntu0.5
  Version table:
     1:9.7.1.dfsg.P2-2ubuntu0.5 0
        500 http://security.ubuntu.com/ubuntu/ maverick-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu/ maverick-security/main i386 Packages
     1:9.7.1.dfsg.P2-2 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
root@ls3:~#

Trying to install 1:9.7.1.dfsg.P2-2:

root@ls3:~# apt-get install bind9=1:9.7.1.dfsg.P2-2
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.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bind9 : Depends: libbind9-60 (= 1:9.7.1.dfsg.P2-2) but 1:9.7.1.dfsg.P2-2ubuntu0.5 is to be installed
         Depends: libdns66 (= 1:9.7.1.dfsg.P2-2) but 1:9.7.1.dfsg.P2-2ubuntu0.5 is to be installed
         Depends: libisc60 (= 1:9.7.1.dfsg.P2-2) but 1:9.7.1.dfsg.P2-2ubuntu0.5 is to be installed
         Depends: libisccc60 (= 1:9.7.1.dfsg.P2-2) but 1:9.7.1.dfsg.P2-2ubuntu0.5 is to be installed
         Depends: libisccfg60 (= 1:9.7.1.dfsg.P2-2) but 1:9.7.1.dfsg.P2-2ubuntu0.5 is to be installed
         Depends: liblwres60 (= 1:9.7.1.dfsg.P2-2) but 1:9.7.1.dfsg.P2-2ubuntu0.5 is to be installed
         Depends: bind9utils (= 1:9.7.1.dfsg.P2-2) but 1:9.7.1.dfsg.P2-2ubuntu0.5 is to be installed
E: Broken packages
root@ls3:~#

Landscape, however, just says this:

E:Unable to correct problems, you have held broken packages.

(see screenshot)

Related branches

Revision history for this message
Andreas Hasenack (ahasenack) wrote :
Changed in landscape-client:
status: New → In Progress
assignee: nobody → Björn Tillenius (bjornt)
milestone: backlog → 12.02.1
tags: added: points-3
Changed in landscape-client:
status: In Progress → Fix Committed
Changed in landscape-client:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.