Strange behaviour of pkg_ commands

[Jim Hatfield]

While upgrading ports/packages on a 4.5 machine I
noticed some strange behaviour of the pkg_ commands.

For example pkg_info with no parameters produces output
which ends:

>bash-2.05b.007      The GNU Bourne Again Shell
>pkg_info: read_plist: bad command '@conflicts bison-[0-9]+'

And now I cannot pkg_delete any package which would
appear after bison in the pkg_info list. Weird.