Description of problem: Fails to run, even test suits, giving the error: perl: symbol lookup error: /usr/local/lib64/perl5/auto/Text/BibTeX/BibTeX.so: undefined symbol: Perl_Gthr_key_ptr Version-Release number of selected component (if applicable): perl-Text-BibTeX-0.70-4.fc22.x86_64 perl-5.20.2-325.fc22.x86_64 How reproducible: every time Steps to Reproduce: 1. dnf install perl-Text-BibTeX 2. (and install the source); cd ~/rpmbuild/BUILD/Text-BibTeX-0.70/t 3. perl bib.t Actual results: 1..42 perl: symbol lookup error: /usr/local/lib64/perl5/auto/Text/BibTeX/BibTeX.so: undefined symbol: Perl_Gthr_key_ptr Expected results: (I don't know, but something about those 42 tests running!) Additional info: Same problem when I rebuild the package from source. In addition, then I get conflicts on install file /usr/lib64/perl5/vendor_perl/Text from install of perl-Text-BibTeX-0.70-4.fc22.x86_64 conflicts with file from package perl-Text-Soundex-3.04-294.fc22.x86_64 file /usr/lib64/perl5/vendor_perl/auto/Text from install of perl-Text-BibTeX-0.70-4.fc22.x86_64 conflicts with file from package perl-Text-Soundex-3.04-294.fc22.x86_64 file /usr/lib64/perl5/vendor_perl/Text from install of perl-Text-BibTeX-0.70-4.fc22.x86_64 conflicts with file from package perl-Text-CSV_XS-1.17-1.fc22.x86_64 file /usr/lib64/perl5/vendor_perl/auto/Text from install of perl-Text-BibTeX-0.70-4.fc22.x86_64 conflicts with file from package perl-Text-CSV_XS-1.17-1.fc22.x86_64 (but that should be a separate bug report)
I should add: this bug looks like bug #1227175, but isn't solved by rebuilding the package.
Grumb, that should have been: this bug looks like bug #723202
(In reply to John Heidemann from comment #0) > Description of problem: > Fails to run, even test suits, giving the error: > > perl: symbol lookup error: > /usr/local/lib64/perl5/auto/Text/BibTeX/BibTeX.so: undefined symbol: > Perl_Gthr_key_ptr > The /usr/local stuff your not delivered by any Fedora RPM package. It's your private module built using older perl which you try to load with a new perl now. Please note that major perl releases are not guaranteed to be ABI-comptatible which is exactly the error you see now. Solution is either to remove all content from /usr/local/share/perl5 and /usr/local/lib64/perl5 or rebuild your private module using current perl. (You used cpan tool probably.) > Same problem when I rebuild the package from source. > Then something is fishy with the source. It should test just built modules from ./blib, not from system paths. > In addition, then I get conflicts on install > file /usr/lib64/perl5/vendor_perl/Text from install of > perl-Text-BibTeX-0.70-4.fc22.x86_64 conflicts with file from package > perl-Text-Soundex-3.04-294.fc22.x86_64 This looks like the two packages disagree on mode or ownership of /usr/lib64/perl5/vendor_perl/Text directory. This is a packaging bug. The correct ownership should be root:root and mode 0755.
(In reply to Petr Pisar from comment #3) > (In reply to John Heidemann from comment #0) > > In addition, then I get conflicts on install > > file /usr/lib64/perl5/vendor_perl/Text from install of > > perl-Text-BibTeX-0.70-4.fc22.x86_64 conflicts with file from package > > perl-Text-Soundex-3.04-294.fc22.x86_64 > > This looks like the two packages disagree on mode or ownership of > /usr/lib64/perl5/vendor_perl/Text directory. This is a packaging bug. The > correct ownership should be root:root and mode 0755. I checked the two packages and they are fine. Even I can install both of them at the same time. I guess the packages are not genuine Fedora 22 packages.
Thanks for the quick reply. Sigh, you're correct. I should have seen it was /usr/local and so my fault. I will close this as NOTABUG. Wrt the conflict on /usr/lib64/perl5/vendor_perl/Text, Text::BibTeX's spec calls %{_fixperms}. I don't know if that is The Right Thing or not. But I will leave that for another ticket.
I cannot reproduce the conflict. Can you file another bug and explain how to see it? Thanks.
Oops notice that Petr also cannot reproduce. So if you can reliably reproduce with Fedora packages, then file another bug :-)