Hi On Thu, Jul 27, 2006 at 01:59:32AM +0200, Luigi Gangitano wrote: > Hi Michael, > I suspect that this is a bug in Smart Package Manager. Upgrading from > previous version of squid with apt-get and aptitude works correctly.
But how is the Smart Package Manager supposed to know that it can't upgrade squid-common without upgrading squid if there is nothing to tell it that the older squid package conflicts with the newer squid-common package? I am not a Debian developer, and I haven't read the packaging policy, but I don't see any way for smart to know that it should first uninstall squid, then upgrade squid-common, and then install the new squid. I would have thought if it was not possible to install the older squid package with the newer squid-common package then the newer squid-common package should conflict with the older squid package. Is that not the way it works? How do apt-get and aptitude do it? -- Michael Wood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
