Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#48634 - [bbdb] Update to 3.1.2-1 breaks gnus/message integration without configuraton changes.
Attached to Project:
Community Packages
Opened by Shawn Nock (nocko) - Saturday, 19 March 2016, 14:09 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 19 March 2016, 20:18 GMT
Opened by Shawn Nock (nocko) - Saturday, 19 March 2016, 14:09 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 19 March 2016, 20:18 GMT
|
DetailsDescription:
Upon updating to bbdb-3.1.2-1; running (bbdb-initialize 'gnus 'message): Gnus will not start, but fails with: Symbol's function definition is void: bbdb-insinuate-gnus . Message bombs with a similar missing symbol. As it turns out, the initialization for bbdb-3 is abjectly stupid. The old way (makes sense): (require 'bbdb) (bbdb-initialize 'gnus 'message) The new way (hurrah!, garbage boilerplate): (require 'bbdb-loaddefs) (require 'bbdb) (bbdb-initialize 'gnus 'message) (bbdb-mua-auto-update-init 'gnus 'message) Please add a gnus breakage section to to the install message and release -2. It'll save poor saps like me some time. |
This task depends upon