lbdb warning when searching MacOS contacts

[Richard Cobbe]

MacOS 10.12.4, MacPorts v2.4.1, lbdb 0.42_0+gpg2.

I've recently noticed that lbdbq issues noisy warnings when querying the
MacOS contacts:

    [ridcully:~]$ lbdbq cobbe
    CoreData: warning: dynamic accessors failed to find @property implementation for 'uniqueId' for entity ABCDInfo while resolving selector 'uniqueId' on class 'ABCDInfo'.  Did you remember to declare it @dynamic or @synthesized in the @implementation ?
    CoreData: warning: dynamic accessors failed to find @property implementation for 'uniqueId' for entity ABCDContact while resolving selector 'uniqueId' on class 'ABCDContact'.  Did you remember to declare it @dynamic or @synthesized in the @implementation ?
    CoreData: warning: dynamic accessors failed to find @property implementation for 'uniqueId' for entity ABCDEmailAddress while resolving selector 'uniqueId' on class 'ABCDEmailAddress'.  Did you remember to declare it @dynamic or @synthesized in the @implementation ?
    CoreData: warning: dynamic accessors failed to find @property implementation for 'address' for entity ABCDEmailAddress while resolving selector 'address' on class 'ABCDEmailAddress'.  Did you remember to declare it @dynamic or @synthesized in the @implementation ?
    CoreData: warning: dynamic accessors failed to find @property implementation for 'label' for entity ABCDEmailAddress while resolving selector 'label' on class 'ABCDEmailAddress'.  Did you remember to declare it @dynamic or @synthesized in the @implementation ?
    CoreData: warning: dynamic accessors failed to find @property implementation for 'isPrimary' for entity ABCDEmailAddress while resolving selector 'isPrimary' on class 'ABCDEmailAddress'.  Did you remember to declare it @dynamic or @synthesized in the @implementation ?
    CoreData: warning: dynamic accessors failed to find @property implementation for 'orderingIndex' for entity ABCDEmailAddress while resolving selector 'orderingIndex' on class 'ABCDEmailAddress'.  Did you remember to declare it @dynamic or @synthesized in the @implementation ?
    lbdbq:       17 matches
    <<matches omitted for privacy>>

It does print the matches, but after generating a lot of noise that kind of
interferes with using it in mutt, for example.  My .lbdbrc file:

    METHODS="m_osx_addressbook"

The precise warning text and number of messages vary depending on what I'm
searching for, but the general shape of the messages is similar to the
above example.  I've worked around this by wrapping lbdbq in a script that
sends stderr to /dev/null, but that's kind of fragile.

I've only just started to use lbdb again after a long period of not using
it, so I can't say when this behavior was introduced.

Have others noticed this?  Should I file a bug against the package, or
let the upstream authors know?  (Does anyone else even use lbdb?  The
package has no maintainer, and the last post to the mailing list that I
could find about this port was from me, about a different problem, 4 years
ago.)

Thanks,

Richard