There is a bug report on this....

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384426

I suggest everyone not upgrade the sendmail till this is fixed.

Ken



On Thu, 24 Aug 2006, Robert S wrote:

> I have recently got the following output:
>
> # apt-get upgrade -s
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following packages have been kept back:
>   rmail sendmail sendmail-base sendmail-bin sendmail-cf sensible-mda
> 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
>
> If I try to install one of these packages I get:
>
> # apt-get install sendmail -s
> Reading Package Lists... Done
> Building Dependency Tree... 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:
>   sendmail: Depends: sendmail-bin (= 8.13.4-3sarge2) but
> 8.13.4-3sarge1 is to be installed
> E: Broken packages
>
> Also:
> # apt-get install -s sendmail-bin
> ------8><------- snip
> The following packages have unmet dependencies:
>   sendmail-bin: Depends: libsasl2 (>= 2.1.19.dfsg1) but
> 2.1.19-1.5sarge1 is to be installed
> E: Broken packages
>
> # cat /etc/apt/sources.list
> deb http://security.debian.org/ sarge/updates main contrib non-free
> deb http://volatile.debian.net/debian-volatile sarge/volatile main
>
> I also use the volatile-sloppy repository for spamassassin and
> volatile for clamav.  Otherwise I run a pure sarge system.  I've
> disabled volatile-sloppy for the meantime because I don't want to
> install the latest version of this until its fully tested.  I can't
> see any evidence that sendmail or sendmail-bin are in volatile or
> sloppy.
>
> Is the apt repository working OK??  How can I resolve this?
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to