> Step (1) is done, I am now ready to proceed with (2). Unfortunately,
> the release team seems to have changed their mind in the mean time,
> and have indicated that exim 3.36-16sarge1 would not be accepted for
> the next sarge point release with the changed description.
>
> I happen to strongly
On Sun, Jul 30, 2006 at 02:08:23PM +0200, Martin Schulze wrote:
> Marc Haber wrote:
> > (2) Update exim3 with the warning message in sarge via s-p-u and a
> > point release.
>
> If this is a required step upon the upgrade/removal, then your path
> is flawed.
No, it is not requied, but an addi
Marc Haber wrote:
> (2) Update exim3 with the warning message in sarge via s-p-u and a
> point release.
If this is a required step upon the upgrade/removal, then your path
is flawed. You cannot expect all users who upgrade from sarge to
etch to have the most recent updates installed. There a
Hi,
currently, Debian etch still contains a package of exim 3, an outdated
version of our Default MTA which is still in wide use, but has been
unsupported by upstream for years. Even its maintainer has stopped
using it in the mean time, so exim 3 users _really_ _really_ should
upgrade.
Unfortunat
4 matches
Mail list logo