[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#364604: marked as done (apt debug messages: could separate "has broken dep on" cases)

Your message dated Fri, 5 Nov 2010 19:40:07 +0100
with message-id <AANLkTi=EF6oq4B0OiOx0mV7SmMgG=ePtvjNbpzpCAjJe@mail.gmail.com>
and subject line Close: apt debug messages: could separate "has broken dep on" cases
has caused the Debian Bug report #364604,
regarding apt debug messages: could separate "has broken dep on" cases
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
364604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364604
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.6.43
Severity: wishlist

I have an idea for better apt debug messages.
Let's examine two messages seen upon dselect-upgrade.
1. Package rxvt-unicode-ml has broken dep on rxvt-unicode
2. Package libgdal1-dev has broken dep on libgdal1c2a
In 1, the problem was a conflict.
In 2, the problem was the user had marked libgdal1c2a for purge with
dpkg --set-selections.
Thus we see "has broken dep on" includes several different situations
that apt could mention, instead of just saying "has broken dep on" for
all cases.

--- End Message ---
--- Begin Message --- 
Version: 0.7.22

I guess the debug improvement was implemented with:

  * add depth information to the debug output and show what depends
    type triggers a autoinst (closes: #458389)

The output is now in the latest release btw:
(steadily improved over time)

Broken lintian:i386 Depends on libparse-debianchangelog-perl [ i386 ]
< 1.1.1-2.1 > ( perl ) (>= 0.6)


The responsible option for it is: Debug::pkgProblemResolver


Best regards

David Kalnischkies

--- End Message ---
Reply to: