As glad as I am that this has been fixed in Edgy and that now we've got
mail-notification 3.0 with Evolution support, I don't think it makes
sense to backport this package until this related bug has been fixed:
https://launchpad.net/bugs/44078
In any case, the backport should be requested there fi
Is this going to be back-ported to dapper?
On Sun, 2006-07-30 at 08:56 +, Whoopie wrote:
> Fixed in Edgy with mail-notification 3.0.dfsg.1-3ubuntu1.
>
> ** Changed in: mail-notification (Ubuntu)
>Status: Confirmed => Fix Released
>
--
No Evolution support
https://launchpad.net/bugs/
Fixed in Edgy with mail-notification 3.0.dfsg.1-3ubuntu1.
** Changed in: mail-notification (Ubuntu)
Status: Confirmed => Fix Released
--
No Evolution support
https://launchpad.net/bugs/37474
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
Debian package >= 3.0.dfsg.1-1 provides evolution support.
--
No Evolution support
https://launchpad.net/bugs/37474
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Mail-Notification v2.0 appears to be compiled without Evolution (v2.6.1)
support.
~$ mail-notification -l
Compiled-in mailbox backends: mbox, MH, Maildir, POP3, IMAP, Gmail, Sylpheed
Compiled-in POP3 and IMAP features: SASL, IPv6
If I start up Evolution and then manually run mail-notification, it
