-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Today we upgraded some software on the Solaris login servers (willow and wolfsbane). Notable upgrades include Perl 5.10.1, Python 2.6.5, git 1.7.0.3, GNU bash 4.1 and Mercurial 1.5.
A full list of upgrades is available at https://jira.toolserver.org/browse/MNT-409
- river.
On 24 March 2010 07:49, River Tarnell river.tarnell@wikimedia.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Today we upgraded some software on the Solaris login servers (willow and wolfsbane). Notable upgrades include Perl 5.10.1, Python 2.6.5, git 1.7.0.3, GNU bash 4.1 and Mercurial 1.5.
A full list of upgrades is available at https://jira.toolserver.org/browse/MNT-409
This upgrade has caused all of my tools using the Perl MediaWiki::API module to break.
Specifically API.php returns its response in gzip format. MediaWiki::API uses the standard perl LWP module which uses the Compress::Zlib module to decode web responses in gzip format.
Compress::Zlib is not an installed module on wolfsbane
What I don't understand is how the upgrade has caused this. Could the upgrade have uninstalled a previously present Compress::Zlib or could MediaWiki::API work without Compress::Zlib before the upgrade?
Andrew Dunbar (hippietrail)
- river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkupKVMACgkQIXd7fCuc5vLdqwCfRHQmbY8Gv0kl1GWG5tl03T9l 1FwAnA0X4NtnYMbDG02gAFQdXu6Z64nF =KJ/1 -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
On 24 March 2010 18:30, Andrew Dunbar hippytrail@gmail.com wrote:
On 24 March 2010 07:49, River Tarnell river.tarnell@wikimedia.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Today we upgraded some software on the Solaris login servers (willow and wolfsbane). Notable upgrades include Perl 5.10.1, Python 2.6.5, git 1.7.0.3, GNU bash 4.1 and Mercurial 1.5.
A full list of upgrades is available at https://jira.toolserver.org/browse/MNT-409
This upgrade has caused all of my tools using the Perl MediaWiki::API module to break.
Specifically API.php returns its response in gzip format. MediaWiki::API uses the standard perl LWP module which uses the Compress::Zlib module to decode web responses in gzip format.
Compress::Zlib is not an installed module on wolfsbane
What I don't understand is how the upgrade has caused this. Could the upgrade have uninstalled a previously present Compress::Zlib or could MediaWiki::API work without Compress::Zlib before the upgrade?
Sorry please ignore. I installed Compress::Zlib locally and thought it didn't work but I didn't see I had two copies of my tool with similar names and was testing a different one to which I was modifying!
Andrew Dunbar (hippietrail)
Andrew Dunbar (hippietrail)
- river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkupKVMACgkQIXd7fCuc5vLdqwCfRHQmbY8Gv0kl1GWG5tl03T9l 1FwAnA0X4NtnYMbDG02gAFQdXu6Z64nF =KJ/1 -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
-- http://wiktionarydev.leuksman.com http://linguaphile.sf.net
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andrew Dunbar:
Compress::Zlib is not an installed module on wolfsbane
Sorry please ignore. I installed Compress::Zlib locally and thought it didn't work but I didn't see I had two copies of my tool with similar names and was testing a different one to which I was modifying!
Actually, it looks like the new Perl package was slightly broken, and didn't ship Compress::Zlib when it should have. This is fixed now.
- river
On 25 March 2010 00:55, River Tarnell river.tarnell@wikimedia.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andrew Dunbar:
Compress::Zlib is not an installed module on wolfsbane
Sorry please ignore. I installed Compress::Zlib locally and thought it didn't work but I didn't see I had two copies of my tool with similar names and was testing a different one to which I was modifying!
Actually, it looks like the new Perl package was slightly broken, and didn't ship Compress::Zlib when it should have. This is fixed now.
It seems there are some very stale old modules still installed which seem to now be considered defacto standard by the Perl community. POE and its child classes such as POE::Component::IRC for example.
I couldn't even find what was the right path for these modules for a script running on nightshade or wolfsbane and ended up installing local copies of the current versions.
Andrew Dunbar (hippietrail)
- river -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkuqGeAACgkQIXd7fCuc5vJyCACgr495X0rkw1QdlefBBpYmHEQG DJIAoMEUkVRjUEpWpFEV/kZ4sX6Q8R1P =3ktG -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 3/24/2010 11:12 PM, Andrew Dunbar wrote:
It seems there are some very stale old modules still installed which seem to now be considered defacto standard by the Perl community. POE and its child classes such as POE::Component::IRC for example.
I couldn't even find what was the right path for these modules for a script running on nightshade or wolfsbane and ended up installing local copies of the current versions.
$ perl -V
will tell you where perl looks for libraries, and
$ perl -MModule -e 'print "$Module::VERSION\n"'
will generally give you the version.
On 25 March 2010 16:06, Q overlordq@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 3/24/2010 11:12 PM, Andrew Dunbar wrote:
It seems there are some very stale old modules still installed which seem to now be considered defacto standard by the Perl community. POE and its child classes such as POE::Component::IRC for example.
I couldn't even find what was the right path for these modules for a script running on nightshade or wolfsbane and ended up installing local copies of the current versions.
$ perl -V
will tell you where perl looks for libraries, and
Aha thanks!
$ perl -MModule -e 'print "$Module::VERSION\n"'
Yes I was printing these from my bot so I new it was using ancient versions of some modules but wanted to know where they were coming from. I wonder if there is a programmatic equivalent for -V
Andrew Dunbar (hippietrail)
will generally give you the version. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBCAAGBQJLqu9NAAoJEL+AqFCTAyc2rfgH/1Kua0w7IbRgNYUN6qoHpXiv u3bEqX9OUe28MaPvasNh8jRyPJMwzYPFCr++4Niok2f0BShWX5FNTwTz1qB91pED FHltoRCBZk533RuWjH/8lmqukpaWqyveIDko43mXMczdoSnZATc0zc4G9V0ZLEXg 1KG0yaScgTB0RpElTkmNDQMT1QE7gBGPwsA8Ueea1Nc5FVRpjUeOptHFD+bX0yEw 5Dh8msrtMS+PZB9FMHcjB9zvUOoRJKw7kofGkmHJVKalG6PhZFAT8eZJ4211wxCT crOe3dfSqhmb9rHTM+Xw8OLmpIvLIXzrROCUOz0dhkULQ0n9Qd/tJlQAF8L4VuM= =u9Aw -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 3/25/2010 8:22 PM, Andrew Dunbar wrote:
Yes I was printing these from my bot so I new it was using ancient versions of some modules but wanted to know where they were coming from. I wonder if there is a programmatic equivalent for -V
$ perl -e 'print join "\n", @INC' /home/overlordq/lib/i86pc-solaris-thread-multi-64int-ld /home/overlordq/lib /opt/ts/perl/5.10/lib/5.10 /opt/ts/perl/5.10/lib/site_perl/5.10 /opt/ts/perl/5.10/lib/vendor_perl/5.10 /opt/ts/perl/5.10/lib/vendor_perl/5.10
or if you only want a single module:
$ perl -MArchive::Tar -le 'print $INC{"Archive/Tar.pm"}' /opt/ts/perl/5.10/lib/5.10/Archive/Tar.pm
if that's what you meant by programmatic equivalent.
On 26 March 2010 12:35, Q overlordq@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 3/25/2010 8:22 PM, Andrew Dunbar wrote:
Yes I was printing these from my bot so I new it was using ancient versions of some modules but wanted to know where they were coming from. I wonder if there is a programmatic equivalent for -V
$ perl -e 'print join "\n", @INC' /home/overlordq/lib/i86pc-solaris-thread-multi-64int-ld /home/overlordq/lib /opt/ts/perl/5.10/lib/5.10 /opt/ts/perl/5.10/lib/site_perl/5.10 /opt/ts/perl/5.10/lib/vendor_perl/5.10 /opt/ts/perl/5.10/lib/vendor_perl/5.10
or if you only want a single module:
$ perl -MArchive::Tar -le 'print $INC{"Archive/Tar.pm"}' /opt/ts/perl/5.10/lib/5.10/Archive/Tar.pm
if that's what you meant by programmatic equivalent.
Yes perfect! Thanks again.
Andrew Dunbar (hippietrail)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBCAAGBQJLrA9UAAoJEL+AqFCTAyc2pEsH/idFX5savPC/xrREp3ELg+lZ 36wqLK+S4rVSDS8ydP2ToTRHcgbB5FNhK+q4jXMO5n5XEpOd99lJmj4gAUuKeZMS Mceoh85VuDfwkauEIkwvr4P4IcM4fC095ML1lkzDjhh4yqIiIXXedAPxLWER4+2h jK9yTWV+FLvRGQZWmAEx5z4jA0OtHFPaVGc5/yqddM5v5wNqjxu1a+qv9Y4KSH4B +UBJUJPuISOIYTAR6o519CId1MCtC3MvQDpzbVbpOJEPj9ftD9KzLuFfqgOFQxTM vlbw8CREkBixmq81E2kRKs7yP+hkyUtyZRT4L2myaNBwfmSO31K1i527s0VuCa8= =N24Q -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andrew Dunbar:
It seems there are some very stale old modules still installed which seem to now be considered defacto standard by the Perl community. POE and its child classes such as POE::Component::IRC for example.
Are you asking for these modules to be upgraded, or something else?
I couldn't even find what was the right path for these modules for a script running on nightshade or wolfsbane and ended up installing local copies of the current versions.
I'm afraid I don't really understand what you mean here. What do you need the path for? System modules are installed in the default Perl search path, and you shouldn't need to know (or care) what that is, since Perl will search it by default.
- river.
On 26 March 2010 00:17, River Tarnell river.tarnell@wikimedia.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andrew Dunbar:
It seems there are some very stale old modules still installed which seem to now be considered defacto standard by the Perl community. POE and its child classes such as POE::Component::IRC for example.
Are you asking for these modules to be upgraded, or something else?
It's probably a good idea. Our version of POE.pm is 1.0003 from June 2008, current version is 1.287 Our version of POE::Component::IRC.pm is 5.84 current version is 6.28
I couldn't even find what was the right path for these modules for a script running on nightshade or wolfsbane and ended up installing local copies of the current versions.
I'm afraid I don't really understand what you mean here. What do you need the path for? System modules are installed in the default Perl search path, and you shouldn't need to know (or care) what that is, since Perl will search it by default.
I was trying to track down why my code wasn't working. I thought I had the include paths right for my local modules but still a documented function was missing. I was trying to find out if there was another, out of date, version of the module the sytem was pulling in or whether there was some other problem with my code that I wasn't seeing.
It turned out there were stale modules in /usr/share/perl5/ but it took me a while. Once I knew that I could be sure that there really was something wrong with how I was specifying the paths to my local modules and could focus on fixing that.
Andrew Dunbar (hippietrail)
- river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkurYmgACgkQIXd7fCuc5vIwxACfSwGTQUDzbmaIMSOu+38Wh0Vz wBsAniToJr0a77NIX5kRHulBYMyFMKJE =eI2q -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andrew Dunbar:
It turned out there were stale modules in /usr/share/perl5/
Okay, I assumed you were talking about willow (since the thread was about software upgrades on Solaris), but /usr/share/perl5 only exists on Linux. I suggest filing a TS issue and assigning it to DaB to upgrade these modules on nightshade.
- river.
toolserver-l@lists.wikimedia.org