Antoine Jacoutot <ajacoutot@bsdfrog.org> writes:
> On Thu, Jun 29, 2017 at 02:07:08PM +0200, Jeremie Courreges-Anglas wrote:
>> Marc Espie <espie@nerim.net> writes:
>>
>> > On Wed, Jun 28, 2017 at 12:09:01AM -0400, Ted Unangst wrote:
>> >> install-info: warning: no entries found for `/usr/local/info/gpgrt.info'; nothing deleted
>> >> install-info: menu item `libgpg-error' already exists, for file `gnupg'
>> >> system(/usr/bin/install-info, --info-dir=/usr/local/info, --, /usr/local/info/gpgrt.info) failed: exit(1)
>> >> chromium-59.0.3071.109p0:libgpg-error-1.27->1.27: ok
>> >>
>> >> would adding --quiet to install-info make this go away? i guess it's not
>> >> harmful, but i have to study the message for some time to figure that out.
>> >
>> > It would be much nicer to fix those messages.
>> >
>> > In some cases, it's just a question of patching the dir entry in the info
>> > file or the texi source.
>> >
>> > In other cases, this would require an update to makeinfo, or at least
>> > get the dir parts overhauled, because they're sorely lagging behind.
>> >
>> > I don't think hiding the problem is going to make it go away.
>> >
>> > With enough nagging, somebody's going to fix it eventually.
>>
>> Looks like the following should fix it.
>>
>> ok?
>>
>> NB: machines where libgpg-error has already been installed need manual
>> intervention, a la
>>
>> sed -i 's/^\* libgpg-error: (gnupg)/* libgpg-error: (gpgrt)/' /usr/local/info/dir
>
> Could you do the same for databases/gdbm?
Does gdbm actually need something similar?
pkg_add -vvr -Dinstalled gdbm
shows no warning/error message.
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
No comments:
Post a Comment