Aaron - so far looks like it is working as expected. What a relief!
Paul, I was able to install the 2.0.3-1 by specifying
apt-get install dbmail-pgsql=2.0.3-1
forcing a "downgrade" from the one named 2.0.4-0.20050116 I installed
yesterday which didn't have Aaron's dsn.c patch. Got a few errors doing
that but Petru says:
"
socket <irc://chat.outboundindex.net/socket,isnick> not sure what was
wrong with the postinst script
socket <irc://chat.outboundindex.net/socket,isnick> but since it
wasn't trying to do anything on the upgrade path
socket <irc://chat.outboundindex.net/socket,isnick> I just put an exit
statement at the top
socket <irc://chat.outboundindex.net/socket,isnick> thus avoiding the
error
"
and the system is working and forwarding to multiple aliases even where
the userid is equivalent to the delivery email address.
I was curious why the 2.0.3-1 was so much smaller than yesterday's
2.0.4-0.20050116
The deb was 7xxkB yesterday but 232kB today... and when downgrading:
The following packages will be DOWNGRADED:
dbmail-pgsql
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 121 not
upgraded.
Need to get 232kB of archives.
After unpacking 1315kB disk space will be freed.
Thanks again to both Aaron and Paul,
- April
Paul J Stevens wrote:
Matthew T. O'Connor wrote:
Shouldn't the package be named 2.0.3-x where the x is a package
version. This would allow you to include post 2.0.3 bug fixes. I
think to have a package named 2.0.4 before DBMail has released a
2.0.4 is confusing.
I can't do that until after uploading the packages to debian.org. The
first package of an upstream release *must* always be -1, that's why I
use -0 to indicate a prerelease.
Btw, it looks like dbmail-2 will be uploaded to debian as
dbmail2-mysql and dbmail2-pgsql. The problems arising from the
migration scripts are potentially just too big, esp. so shortly before
sarge release. Before an official upload however, I will *have* to fix
the current libtool mess. Debian policy really doesn't like the
current rpath /usr/lib/dbmail/ setup.
Anyway, on debian.nfgd.net you'll currently find 2.0.3-1 which
includes the dsn fix by Aaron, and some search speedups by yours
truly. But it doesn't include the bug-fix for bug #158 which *is* in cvs.
I'll start creating a separate repository for my exchanges with debian
tomorrow, so it won't interfere with users of debian.nfgd.net.
