Re: How do I clear no-longer-usable packages from poudriere?

From: <robert_at_rrbrussell.com>
Date: Sun, 03 Mar 2024 20:21:23 UTC

On Sun, Mar 3, 2024, at 13:12, David Wolfskill wrote:
> On Sun, Mar 03, 2024 at 01:01:36PM -0600, robert@rrbrussell.com wrote:
>> On Sun, Mar 3, 2024, at 12:33, David Wolfskill wrote:
>> > I have a local package-builder that's (generally) been working quite
>> > well for me since Jul 2015 (through a couple of hardware replacements,
>> > sure, but the approach remains the same).
>> >
>> > Today, in trying to chase down what was causing my central "hub" machine
>> > to whine:
>> >
>> > ld-elf.so.1: /usr/local/lib/libtasn1.so.6: version LIBTASN1_0_3 
>> > required by /usr/local/lib/libgnutls.so.30 not defined
>> ...
>> Is this error in a Poudrière build log or spit out to the console when running a command on a client?
>> ....
>
> The above occurred (checking the typescript file) during "pkg install";
> I also saw it while trying to run a command on the client machine.
>
> Checking the last set of poudriere build logs, I do not find any similar
> whines in any of them, nor do I find any in the typescript (from running
> "poudriere bulk").
>
> Meanwhile, I am about to copy over a backup copy of libc.so.6 to try to
> work around the other part of this.
>
> Peace,
> david
> -- 
> David H. Wolfskill                              david@catwhisker.org
> Alexey Navalny was a courageous man; Putin has made him a martyr.
>
> See https://www.catwhisker.org/~david/publickey.gpg for my public key.
>
> Attachments:
> * signature.asc

Okay, find out which package provides libtasn1.so.6 and do a forced reinstall of it with pkg install -f. I ran into a similar issue recently with the exported symbols list being updated without a revision update that notified pkg of the change. A forced reinstall of the package solved the problem. Mine was a different library but the error message matches.