Le 24/09/13 16:56, Chris McMahon a écrit : > It seems that the File scenario is actually running the UploadWizard test? > > https://integration.wikimedia.org/ci/job/qa-browsertests-run/lastCompletedBuild/testReport/(root)/File/Logged_in_user_goes_to_file_that_does_not_exist/ > <https://integration.wikimedia.org/ci/job/qa-browsertests-run/lastCompletedBuild/testReport/%28root%29/File/Logged_in_user_goes_to_file_that_does_not_exist/>? > > on Ruby 1.9.1?
The version number there is the ruby library compatibility version. The description for the ruby1.9.3 package state: Ruby uses two parallel versioning schemes: the `Ruby library compatibility version' (1.9.1 for this package), which is similar to a library SONAME, and the `Ruby version' (1.9.3 for this package). Ruby packages in Debian are named using the Ruby library compatibility version, which is sometimes confusing for users who do not follow Ruby development closely. This package depends on the ruby1.9.1 package, and provides compatibility symbolic links from 1.9.3 executables and manual pages to their 1.9.1 counterparts. And ruby1.9.1 package description state: In the name of this package, `1.9.1' indicates the Ruby library compatibility version. This package currently provides the `1.9.3' branch of Ruby, which is compatible with the `1.9.1' branch. So the library is 1.9.1 compatible while the executable is 1.9.3: $ ruby1.9.3 --version ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] $ ruby1.9.1 --version ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] $ ls -l `which ruby1.9.3` lrwxrwxrwx 1 root root 9 Jul 8 20:18 /usr/bin/ruby1.9.3 -> ruby1.9.1* I guess we can think of it as ruby1.9.3 being fully compatible with the ruby 1.9.1 libraries. -- Antoine "hashar" Musso _______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
