bug#21971: 25.1.50; EUDC conversion to BBDB 3 incompatibility

[Thomas Fitzsimmons]

Hi George,

George McNinch <gmcninch@gmail.com> writes:

[...]

> In fact, a record *has* been inserted into the bbdb; in this case it
> looks like
>
> ["George" "McNinch" nil "George.McNinch@tufts.edu" nil nil nil nil 
> ((creation-date . "2015-11-21 14:13:29 +0000") (timestamp . "2015-11-21 
> 14:13:29 +0000")) nil]
>
> (assuming McNinch was not already in the bbdb, of course).
>
> This record seems "mangled" from the point-of-view of BBDB3 - the email
> address should be "in a list" inside this record-vector. Perhaps other
> things are amiss, as well.

Thank you for the detailed description of how to replicate the issue.

> Note also that the setting of eudc-ldap-bbdb-conversion-alist I made
> above isn't quite the original value. If I instead use the original
> value, e.g. by instead using the original value
>
> [which amounts to:
>
>   (setq eudc-ldap-bbdb-conversion-alist
>       `((name . cn)
>         (net . mail)
>         (address eudc-bbdbify-address postaladdress "Address")
>         (phone
>          (eudc-bbdbify-phone telephonenumber "Phone")))
>
>
> in the initialization of EUDC],
>
> then when I press "b" on a record
> in the *Directory Query Results* buffer, I get the error
>
> eudc-bbdbify-phone: Symbol’s function definition is void:
> bbdb-parse-phone-number

OK, this seems like a separate issue.  I haven't investigated it yet.

With your eudc-ldap-bbdb-conversion-alist workaround still enabled, can
you try the attached patch to see if it fixes exporting for you?

Thanks,
Thomas

0001-Add-BBDB-3-support-for-EUDC-export.patch
Description: Text Data