On Mon, 2 May 2005, Mark Baker wrote:
> Shannon Dealy wrote:
>
> >The bug previously reported in #248622 (caused by incompatible database
> >formats), and closed by this version of exim (3.36-14) still exists in
> >this version. Among the changes noted in the message closing the previous
> >bug report was that the postinst script was calling db3_upgrade to fix
> >this problem, however, if it is doing so, it doesn't do it directly and I
> >was unable to locate any indirect calls to db3_upgrade either.
> >
> >
> I remember fixing this. I'm not sure what happenened to it, maybe I
> didn't save the file or something. Without any old databases to test it
> with my testing would have been limited to checking it ran without
> errors, so I wouldn't have picked up on this.
>
> Thanks for pointing this out. I'll fix it now; no guarantees that the
> change will get into sarge now though.
Makes little difference to me personally if it makes it into Sarge, the
fix is trivial once you know what is going on, however, I am concerned
that if it fails to make it into Sarge, virtually every existing Debian
system that is upgraded is going to suffer from this bug and that means an
awful lot of people wasting time trying to figure out what is causing the
warning/error message to occur. Though the problem here is (relatively
speaking), insignificant, it seems to me that the number of people
affected probably ought to give it something of a priority boost for
making it into the new release, but I don't know the rules for releases
that well. I have heard that a freeze is going to happen "real soon now"
:-)
FWIW.
Shannon C. Dealy | DeaTech Research Inc.
[EMAIL PROTECTED] | - Custom Software Development -
| Embedded Systems, Real-time, Device Drivers
Phone: (800) 467-5820 | Networking, Scientific & Engineering Applications
or: (541) 929-4089 | www.deatech.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
