Help test recent xulrunner updates.

July 21, 2008 at 6:07 pm (linux, PlanetFedora) (, )

Recently there were problems with a new version of xulrunner being sent as an update to Fedora 9. Several packages that are built against xulrunner were not rebuilt to the new version and submitted to the repositories before xulrunner was. This issue would cause a dependency issue resolving error that might look like this:

Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
 * livna: mirrors.tummy.com
 * fedora: mirror.anl.gov
 * updates: mirror.anl.gov
Setting up Update Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: gecko-libs = 1.9 for package: Miro
--> Processing Dependency: gecko-libs = 1.9 for package: gnome-python2-gtkmozembed
---> Package pilot-link.i386 2:0.12.3-14.fc9 set to be updated
---> Package rsync.i386 0:3.0.3-0.fc9 set to be updated
---> Package totem-mozplugin.i386 0:2.23.2-5.fc9 set to be updated
---> Package xulrunner.i386 0:1.9.0.1-1.fc9 set to be updated
---> Package system-config-language.noarch 0:1.3.1-2.fc9 set to be updated
---> Package selinux-policy.noarch 0:3.3.1-78.fc9 set to be updated
---> Package nfs-utils-lib.i386 0:1.1.1-5.fc9 set to be updated
---> Package xen-libs.i386 0:3.2.0-14.fc9 set to be updated
---> Package binutils.i386 0:2.18.50.0.6-4.fc9 set to be updated
---> Package totem-gstreamer.i386 0:2.23.2-5.fc9 set to be updated
---> Package qemu-img.i386 0:0.9.1-6.fc9 set to be updated
---> Package selinux-policy-targeted.noarch 0:3.3.1-78.fc9 set to be updated
---> Package libvirt.i386 0:0.4.4-2.fc9 set to be updated
---> Package qemu.i386 0:0.9.1-6.fc9 set to be updated
---> Package cpio.i386 0:2.9-8.fc9 set to be updated
---> Package yelp.i386 0:2.22.1-4.fc9 set to be updated
---> Package nspluginwrapper.i386 0:1.1.0-3.fc9 set to be updated
---> Package libvirt-python.i386 0:0.4.4-2.fc9 set to be updated
---> Package device-mapper-multipath.i386 0:0.4.7-16.fc9 set to be updated
---> Package firefox.i386 0:3.0.1-1.fc9 set to be updated
---> Package dmraid.i386 0:1.0.0.rc14-8.fc9 set to be updated
---> Package totem.i386 0:2.23.2-5.fc9 set to be updated
---> Package kpartx.i386 0:0.4.7-16.fc9 set to be updated
--> Finished Dependency Resolution
gnome-python2-gtkmozembed-2.19.1-16.fc9.i386 from installed has depsolving problems
  --> Missing Dependency: gecko-libs = 1.9 is needed by package gnome-python2-gtkmozembed-2.19.1-16.fc9.i386 (installed)
Miro-1.2.4-1.fc9.i386 from installed has depsolving problems
  --> Missing Dependency: gecko-libs = 1.9 is needed by package Miro-1.2.4-1.fc9.i386 (installed)
Error: Missing Dependency: gecko-libs = 1.9 is needed by package gnome-python2-gtkmozembed-2.19.1-16.fc9.i386 (installed)
Error: Missing Dependency: gecko-libs = 1.9 is needed by package Miro-1.2.4-1.fc9.i386 (installed)

There is an update in Bodhi to correct this dependency issue. However, this update needs people to download, install, and test it. Then report on Bodhi what the results were. Usually either that it worked great or that there was issues.

Here are the steps to do the test and report to Bodhi the results:

  1. Run
    yum update
  2. From the output determine what packages are missing for you, you are looking for dependencies that could not be resolved. For this issue they should all be related to Miro and gnome-python2
  3. In a web browser go to the Bodhi page for this update: https://admin.fedoraproject.org/updates/F9/pending/Miro-1.2.4-2.fc9,gnome-python2-extras-2.19.1-17.fc9
  4. Towards the top of the page you will see a section called Builds:. Open a new browser tab/window for each build listed. This will take you to the test build for each package in Koji.
  5. On the Koji page, look for the section called RPMs. Look for each package of the right architecture that you need.
  6. Create a temporary directory to download each of these files to. In my case I created a directory called testingUpdates:
    [jfenner@localhost Download]$ mkdir testingUpdates
    [jfenner@localhost Download]$ cd testingUpdates/
  7. Download all of the RPMs that you need from Koji into the temporary directory. I used wget to do this because I think it’s the easiest way. However, use whatever method works best for you.
  8. Once you’ve done that, then localinstall all of the packages in the temporary directory.
    [jfenner@localhost testingUpdates]$ sudo yum --nogpgcheck localinstall *
  9. Note: You have to turn off the gpg signing check above, because at this stage the packages have not been signed yet. This will happen once they’ve been pushed to stable.
  10. Assuming that you were able to install all packages with no errors, now run a normal yum update. This should also run with no more dependency errors.
    [jfenner@localhost testingUpdates]$ yum update
  11. Excellent! Now do a test run of Firefox and Miro, if you have them installed and make sure that they appear to be working right.
  12. Now you have concluded testing this pending update. The last step is to submit your findings to Bodhi to help get this update sent to the world. Go back to this update’s page on Bodhi. At the bottom of the page, enter your name and click on the appropriate radio button for your findings. If everything worked fine click on Works for Me. Enter a brief comment if you’d like. Fill out the captcha and click Add comment.

That’s all there is to it. You just helped improve QA for the Fedora community. The test you conducted and feedback you provided will help this update go out to all the Fedora repositories fast and of higher quality. I encourage you to check back often at Bodhi and test other packages that appy to your system and provide your feedback. The more of the community that does this, the higher the quality of the updates we receive will be.

Advertisements

4 Comments

  1. Stephen Smoogen said,

    Is there anyway to get these things linked in with package manager? There are a lot of steps in there… and I am lost on when I should have done them or do them in the future. Buttons in the package-manager that pop these up automagically would help so much.

  2. Mehmet Yanki Yonel said,

    Thanks for nice article

  3. Alex said,

    I’d like to know how such a chaotic b0rkfest got pushed to updates in the first place. Did the security team forget about QA? Did QA have an inadequate process in place? These questions are important if you’re serious about preventing such blunders from happening again and not sticking end users with picking up the pieces for you on a regular basis.

  4. dragg said,

    i dont know why some softwares are not user friendly to install

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: