APT - Docs


Summary |  Forums |  Bugs |  Patches |  Docs |  Source |  Files | 

View Documentation | Submit new documentation

Upgrading RPM on Linux (for PlayStation®2)

Upgrading RPM on Linux (for PlayStation2)

Upgrading RPM on Linux (for PlayStation®2)

Author: Matthew C. Rich

Sony Computer Entertainment America, Inc.

v0.20 2002/09/22

Revision History
Revision 0.202002-09-22mcr
second draft
Revision 0.102002-09-22mcr
first draft proposed

Abstract

This document describes the process by which you may upgrade the package management system of your Linux (for PlayStation®2) Kit. The package management system provided with the kit is RPM (v3.0.4), which was created by Red Hat, Inc. for their Red Hat Linux operating systems.


1. Introduction

What are the benefits? Newer versions of RPM contain many changes, not the least of which is a new version of Berkeley DB, used for data storage, but also significant changes in the format of RPM packages themselves. Upgrading to a version of RPM greater than 3.0.5 will allow you to install software packages that have been built with the new package format, or require features that exist in newer versions of RPM.

It also provides you with the ability to use APT, [1] which require at least RPM 4.0.2. This utility provides package downloads, automatic dependency resolution, and various other features beyond the scope of RPM.

1.1. Disclaimer

No liability for the contents of this document can be accepted. Use the concepts, examples and information at your own risk. This document may contain errors and inaccuracies that could be damaging to your system. Although this is highly unlikely, the author(s) do not take any responsibility for any problems you encounter. Proceed with caution. You have been warned.

All copyrights are held by their by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Naming of particular products or brands should not be seen as endorsements.

1.2. Credits / Contributors

In this document, I have the pleasure of acknowledging:

1.3. Feedback

Feedback is most certainly welcome for this document. Send your additions, comments and criticisms to the following email address : <mrich (at) users.playstation2-linux.com>.

1.4. Translations

There are currently no translations of this document available.

2. Procedure

Summary

  • Back up all RPM data.

  • Upgrade RPM to the versions provided (Linux (for PlayStation®2)).

  • Convert the RPM data to the new DB format.

  • Verify that your RPM data has been migrated correctly.

3. Back Up Your Critical Data

3.1. Back up your RPM database

It's extremely important that you backup your RPM database before attempting to upgrade RPM on your system. The RPM database contains all metadata corresponding to the installed software on your system, and upgrading from RPM 3.0.4 [2] to RPM 4.0.2 requires upgrading this database. Depending on the current state of your database, this upgrade process could result in corrupting and/or losing data. You have been warned! The good news is that any damage caused during upgrade can be both identified and repaired... provided that you have performed the backup described here.

As root execute the following

example:

       bash#  tar -zcvf /root/rpmdb-`date +%Y%m%d`-backup.tar.gz /var/lib/rpm
      

This will create an archive of your RPM database and store it as /root/rpmdb--backup.tar.gz [3].

3.2. Create A Recovery Path

As root execute the following

bash#  rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}.rpm\n' 2>&1 | sort > /root/rpmpkgs-`date +%Y%m%d`.lst

This will create a complete list of all the packages that are currently installed on your system and write it to /root/rpmpkgs-.lst [4].

It is also a good idea to backup the rpm command itself. It will be needed in order to restore the old installation if the upgrade fails. For now it can be copied into /root, along with /usr/lib/rpm/rpmrc and /usr/lib/rpm/macros, which are also required.

As root execute the following

example:

bash#  cp -a /bin/rpm /root/rpm 
bash#  cp -a /var/lib/rpm/{rpmrc,macros} /root/ 

4. Upgrading RPM

Now that you are all backed up, you can ... ha! you thought you could fool me... Go back and do the backup! I mean it!

4.1. Downloading the necessary files

Download the rpm files located in the RPM package in this project, they are:

rpm-python-4.0.2-2P.mipsel.rpm

rpm-devel-4.0.2-2P.mipsel.rpm

rpm-build-4.0.2-2P.mipsel.rpm

rpm-4.0.2-2P.mipsel.rpm

popt-1.6.2-2P.mipsel.rpm

Optional Source Code

rpm-4.0.2-2P.src.rpm

4.2. Checking the downloaded files

You should check the validity of the downloaded packages.

bash#  rpm --checksig *.rpm

4.3. Installing the new packages

To install the new RPM packages correctly, you need to perform the following exactly.

bash#  rpm -Uvh rpm-4.0.2-2P.mipsel.rpm rpm-build-4.0.2-2P.mipsel.rpm popt-1.6.2-2P.mipsel.rpm

Immediately after performing the upgrade, you need to rebuild your RPM database with the following command. Do NOT execute any rpm commands between the command above and this command. They must be executed consecutively.

bash#  rpm --rebuilddb

4.4. Verifying the Installation

It is generally a good idea to verify that the upgrade was performed correctly before using the system, or attempting to upgrade or install any new software. Two steps are required to completely verify that the upgrade was successful.

  • Verify the database integrity.
  • Verify the database content.

RPM provides a builtin command to verify the integrity of the database. This will check that the database is working correctly, and is not corrupted. To verify the integrity of the upgraded database, execute the following command.

bash#  rpm --verifydb

If it exits without error, then the upgrade was successful, and you have produced a valid database. If the verification failed, see Section 5 for information on recovering your data.

Although we have validated the database, it may still have lost package file data under certain conditions. To check the contents of the database execute the following with root permissions[5].

bash#  rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}.rpm\n' 2>&1 | sort | diff -u /root/ -
bash#  rpm -qal | grep '(contains no files)' | wc -l

The first command should show you the difference in installed packages, which means it should return nothing at all. If there are differences, packages which exist in the new database and not in the rpmpkgs file will have a + preceding the line , and packages that exist in the rpmpkgs file but not in the new database will have a - preceding the line.

The results of the second command should be '1'. If it counts more than one package that contains no files, then your DB has lost some information, see Section 5.

5. Repairing a Broken Installation

5.1. The Recovery Process

Different methods of repair are required depending on the point of failure. Repairing your system also very much depends on whether you performed the backup described at the beginning of this document. If you did not perform this backup, then go away, I can't help you... How many times did I warn you in this document? In other words, you're up the creek. Hope you still have the installation manual handy...

Determine at what point your RPM upgrade failed. The following are likely candidates:

  • Package installation.

  • Database upgrade.

  • Database verification.

  • Content verification.

5.1.1. Failed Package Installation

This failure is fairly easy to fix; if the rpm command failed during execution, simply restore the old RPM packages from the DVD, and submit a bug report to the APT PS2 Linux project page [6] describing any resulting errors. The following will restore RPM from the DVD:

Note:

You will need to mount disc 2 from the Linux Kit. See the other documentation on the PlayStation®2 Linux Community site for instructions. Be sure to mount the DVD as a UDF filesystem.

bash#  cd /mnt/cdrom/SCEI/RPMS 
bash#  rpm -Fvh rpm*.rpm
bash#  rpm -Fvh popt*.rpm

5.1.2. Failed Database Upgrade

This failure is more difficult to fix. It is identified by either a failure during rebuild of the database, or when verifying the database. It generally results in a currupted database (the worst case) or just invalid/missing data. You may even have a fully functional database that produces errors when operated upon. In any of these instances, the database is no longer functional and should be restored from the backup. However (and this is the tricky part): the old database will not work with the new version of RPM that you've installed.

With the backup copy of the RPM (v3.0.4) binary that was made before performing the upgrade, it should be much easier to restore the old version of RPM. Otherwise you'll have to extract the RPM binary from the RPM package on the DVD--not pretty--with rpm2cpio. As it is, only the following is required to restore the system to normalcy:

bash#  cd /mnt/cdrom/SCEI/RPMS 
bash#  /root/rpm -Fvh --force rpm*.rpm
bash#  /root/rpm -Fvh --force popt*.rpm

This may leave some cruft behind from the RPM installation, but it shouldn't matter once the new RPM is properly installed (it's also easy enough to remove entirely).

Now that the original database is restored, and presumably working, it's not a bad idea to verify its integrity. The most likely cause of failure during the upgrade of the database is the content being migrated. Although other causes such as problems with the Berkeley DB libraries themselves or with RPM may exist, there isn't much to do about that except file bug reports.

To verify the database, try running verifydb on it.

bash#  rpm --verifydb 

Alternatively, you can try rebuilding the contents of the database from the source packages. See Section 5.2.

5.2. Rebuilding your Database from Scratch

It is actually surprisingly simple to rebuild your RPM database from scratch. However, it will require a little scripting know-how. This isn't difficult, though, since I've done all the hard work for you. First we will need the list of packages that you created in the Section 3.2 section. It's nearly impossible to exactly restore your RPM database without this information.

To rebuild the contents of your RPM database, simply iterate through the list of packages, installing just the database information from each package as we go. You could install the entire package, but that's unnecessary and a waste of time.

Execute the following with root permissions: [7]

Note:

As before, you will need to mount disc 2 from the Linux kit, see the other documentation on the PlayStation®2 Linux Community site for instructions. Be sure to mount the DVD as a UDF filesystem.

bash#  files=`cat /root/rpmpkgs-.lst` 
bash#  for file in $files; do
>  rpm -ivh --justdb $file
>  done

6. Copyright and License

This document, Upgrading RPM on Linux (for PlayStation®2), is copyrighted (c) 2002 by Sony Computer Entertainment America, Inc.. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

6.1. GNU Free Documentation License

Version 1.1, March 2000

Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

6.1.1. PREAMBLE

The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

6.1.2. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you".

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

6.1.3. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

6.1.4. COPYING IN QUANTITY

If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

6.1.5. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

  2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five).

  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.

  4. Preserve all the copyright notices of the Document.

  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.

  8. Include an unaltered copy of this License.

  9. Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

  11. In any section entitled "Acknowledgements" or "Dedications", preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

  13. Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version.

  14. Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

6.1.6. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements."

6.1.7. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

6.1.8. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.

6.1.9. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.

6.1.10. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

6.1.11. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

6.1.12. How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. A copy of the license is included in the section entitled "GNU Free Documentation License".

If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.



[1] http://freshrpms.net/apt/

[2] The Linux (for PlayStation®2) 1.0 release version.

[3] Where is the date the command was executed on.

[4] Where is the date the command was executed on.

[5] Where is the date the command was executed on.

[6] APT PS2 Linux project is the home for this document

[7] Where is the date the command was executed on.