When running extra/tenacity from command line it shows that there is an
issue with duplicated plugins. It ignores the duplicated plugins and
after a while it does start.
(…)
What should I do? Report a bug against a package or something else?
Hello,
[Answering taking “correction” email into account.] When running
freshly installed tenacity (1.3.3-4) with no previous configuration
files, I’m getting no warnings/errors and it starts with no delay.
Perhaps a configuration issue? I don’t know tenacity, but if there is a
setting related to plug-in paths, perhaps “/usr/lib64” got added or is a
stale entry from the past? Note I see no such settings, but I’m not
using tenacity either.
If the issue persists and it isn’t a settings issue, IMO this is a
bug to be reported upstream. If not set by the user, software shouldn’t
assume paths in POSIX systems, NTFS, or UDF are distinct.
Cheers, mpan
