Hi, Perl 5.20, as any other new perl version, requires all modules that are not purely perl code to be rebuilt. We did that for all packages in our repos. For a list of upstream changes please refer to `man perldelta`. Since users probably installed some from AUR or with CPANPLUS::Dist::Arch, I wrote a script[1] that generates a local rebuild list. [1]: https://git.server-speed.net/users/flo/bin/plain/find-broken-perl-packages.s... - raw.txt contains a list of files that generated an error - perl-modules.txt contains a list of modules the files belong to - perl-dists.txt contains a list of distributions - pacman.txt contains a list of pacman packages the files belong to Binaries linking with libperl.so will also need to be rebuilt. You can use lddd from devtools to find those. If you get an error that perl-scalar-list-utils can't be found when running -Syu install it with -S perl-scalar-list-utils. Seems to be a bug in pacman. Please report any issue you encounter.
On 01.06.2014 13:55, Florian Pritz wrote:
If you get an error that perl-scalar-list-utils can't be found when running -Syu install it with -S perl-scalar-list-utils. Seems to be a bug in pacman.
And I built that against the old perl. Please make sure you get perl-scalar-list-utils 1.38-2 when upgrading otherwise stuff will segfault. Sorry.
2014-06-01 14:56 GMT+02:00 Florian Pritz <bluewind@xinu.at>:
On 01.06.2014 13:55, Florian Pritz wrote:
If you get an error that perl-scalar-list-utils can't be found when running -Syu install it with -S perl-scalar-list-utils. Seems to be a bug in pacman.
And I built that against the old perl. Please make sure you get perl-scalar-list-utils 1.38-2 when upgrading otherwise stuff will segfault.
Sorry.
my results: ┌─┤[$]|[sl1pkn07]|[sL1pKn07]|[~/aplicaciones]| └───╼ cat /tmp/find-broken-perl-package.WrorNv1I/pacman.txt perl-datetime perl-tk subversion ┌─┤[$]|[sl1pkn07]|[sL1pKn07]|[~/aplicaciones]| └───╼ cat /tmp/find-broken-perl-package.WrorNv1I/perl-dists.txt Tk DateTime ┌─┤[$]|[sl1pkn07]|[sL1pKn07]|[~/aplicaciones]| └───╼ cat /tmp/find-broken-perl-package.WrorNv1I/perl-modules.txt SVN::_Delta SVN::_Ra SVN::_Repos SVN::_Fs SVN::_Client SVN::_Core SVN::_Wc Tk::Menubutton Tk::Entry DateTime perl-datetime [community], perl-tk [extra] and subversion [extra] needs rebuild? greetings
On 01.06.2014 13:55, Florian Pritz wrote:
[1]: https://git.server-speed.net/users/flo/bin/plain/find-broken-perl-packages.s...
The script should now also add broken packages for perl 5.20. For some reason this transition segfaults rather than printing the "Perl API version xx of xx does not match xx" error.
If you get an error that perl-scalar-list-utils can't be found when running -Syu install it with -S perl-scalar-list-utils. Seems to be a bug in pacman.
Should also be "fixed" now. So far no bug reports, I guess I'll move perl once I get enoguh signoffs.
Am 01.06.2014 13:55, schrieb Florian Pritz:
Hi,
Perl 5.20, as any other new perl version, requires all modules that are not purely perl code to be rebuilt. We did that for all packages in our repos.
For a list of upstream changes please refer to `man perldelta`.
Since users probably installed some from AUR or with CPANPLUS::Dist::Arch, I wrote a script[1] that generates a local rebuild list.
[1]: https://git.server-speed.net/users/flo/bin/plain/find-broken-perl-packages.s...
- raw.txt contains a list of files that generated an error - perl-modules.txt contains a list of modules the files belong to - perl-dists.txt contains a list of distributions - pacman.txt contains a list of pacman packages the files belong to
Binaries linking with libperl.so will also need to be rebuilt. You can use lddd from devtools to find those.
If you get an error that perl-scalar-list-utils can't be found when running -Syu install it with -S perl-scalar-list-utils. Seems to be a bug in pacman.
Please report any issue you encounter.
Hello, where can I get module-to-dist.pl from? It is called by your script, and pkgfile does not know it. Best Regards Stefan
On 04.06.2014 20:05, Stefan Husmann wrote:
where can I get module-to-dist.pl from?
It is called by your script, and pkgfile does not know it.
Also from my ~/bin repo, same dir. https://git.server-speed.net/users/flo/bin/plain/module-to-dist.pl
Am 04.06.2014 20:56, schrieb Florian Pritz:
On 04.06.2014 20:05, Stefan Husmann wrote:
where can I get module-to-dist.pl from?
It is called by your script, and pkgfile does not know it.
Also from my ~/bin repo, same dir.
https://git.server-speed.net/users/flo/bin/plain/module-to-dist.pl
Thanks, seems to work fine. But perl-term-readline-gnu and subversion are marked to be rebuild. Both were updated today by Felix and I do not see a problem. So should we take anything find-broken-perl-packages tells us for granted? Can it have false positives? Thanks and best regards again Stefan
On 04.06.2014 22:53, Stefan Husmann wrote:
But perl-term-readline-gnu and subversion are marked to be rebuild. Both were updated today by Felix and I do not see a problem.
So should we take anything find-broken-perl-packages tells us for granted? Can it have false positives?
There can be false positives. The script just logs every module that fails to load and I've seen a SVN::_* modules and TK::something being unable to load directly. SVN::Client loads fine. Use "perl -M$modulename -e1;" to see the error messages and if that crashes or prints something obvious you'll need to rebuild. DateTime was broken, I just rebuilt that.
On Wed, 2014-06-04 at 22:53 +0200, Stefan Husmann wrote:
But perl-term-readline-gnu and subversion are marked to be rebuild. Both were updated today by Felix and I do not see a problem.
So should we take anything find-broken-perl-packages tells us for granted? Can it have false positives?
[rocketmouse@archlinux ~]$ grep subversion /var/log/pacman.log [snip] [2014-06-04 20:49] [PACMAN] upgraded subversion (1.8.9-1 -> 1.8.9-2) ^^^^^ [rocketmouse@archlinux ~]$ grep subversion /tmp/find-broken-perl-package.EI1SQhNZ/pacman.txt subversion [rocketmouse@archlinux ~]$ ls -hAl /tmp/find-broken-perl-package.EI1SQhNZ/pacman.txt -rw-r--r-- 1 rocketmouse rocketmouse 104 Jun 4 22:25 /tmp/find-broken-perl-package.EI1SQhNZ/pacman.txt ^^^^^ Suspect ;)!
Irssi is segfaulting. I ran the find-broken-perl-packages.sh <https://git.server-speed.net/users/flo/bin/plain/find-broken-perl-packages.sh> script, and it indeed shows Irssi and it's perl modules to be broken. What can I do to fix this? On Wed, Jun 4, 2014 at 11:03 PM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
On Wed, 2014-06-04 at 22:53 +0200, Stefan Husmann wrote:
But perl-term-readline-gnu and subversion are marked to be rebuild. Both were updated today by Felix and I do not see a problem.
So should we take anything find-broken-perl-packages tells us for granted? Can it have false positives?
[rocketmouse@archlinux ~]$ grep subversion /var/log/pacman.log [snip] [2014-06-04 20:49] [PACMAN] upgraded subversion (1.8.9-1 -> 1.8.9-2) ^^^^^ [rocketmouse@archlinux ~]$ grep subversion /tmp/find-broken-perl-package.EI1SQhNZ/pacman.txt subversion [rocketmouse@archlinux ~]$ ls -hAl /tmp/find-broken-perl-package.EI1SQhNZ/pacman.txt -rw-r--r-- 1 rocketmouse rocketmouse 104 Jun 4 22:25 /tmp/find-broken-perl-package.EI1SQhNZ/pacman.txt ^^^^^
Suspect ;)!
On 05.06.2014 10:11, B.C. van Duuren wrote:
Irssi is segfaulting. I ran the find-broken-perl-packages.sh <https://git.server-speed.net/users/flo/bin/plain/find-broken-perl-packages.sh> script, and it indeed shows Irssi and it's perl modules to be broken. What can I do to fix this?
Sounds like an incomplete upgrade (the segfaulting part). Please verify that you have irssi 0.8.16-1. As for my script, please always verify the results yourself, the script simply checks every perl module and reports loading error, but some modules (like Irssi::{UI,TextUI,Irc}) are not supposed to be loaded directly which means you'll get false positives in the script's output. Also read up on mailing list etiquette, only quote what you need and don't top post.
On 05.06.2014 10:11, B.C. van Duuren wrote:
Irssi is segfaulting. I ran the find-broken-perl-packages.sh <https://git.server-speed.net/users/flo/bin/plain/find-broken-perl-packages.sh> script, and it indeed shows Irssi and it's perl modules to be broken. What can I do to fix this?
Sounds like an incomplete upgrade (the segfaulting part). Please verify that you have irssi 0.8.16-1. As for my script, please always verify the results yourself, the script simply checks every perl module and reports loading error, but some modules (like Irssi::{UI,TextUI,Irc}) are not supposed to be loaded directly which means you'll get false positives in the script's output. Also read up on mailing list etiquette, only quote what you need and don't top post.
On Thu, Jun 5, 2014 at 10:48 AM, Florian Pritz <bluewind@xinu.at> wrote:
Sounds like an incomplete upgrade (the segfaulting part). Please verify that you have irssi 0.8.16-1.
I do have the latest irssi. I checked the coredump and saw it segfaulted on CharWidth.so. Forced a rebuild of that module with `cpan -fi Text::CharWidth` and now irssi works again.
participants (5)
-
B.C. van Duuren
-
Florian Pritz
-
Ralf Mardorf
-
SpinFlo
-
Stefan Husmann