5.1 Renamed Packages

The following packages have been renamed as shown. In most, if not all, cases,
Conflicts:, Replaces:, and Provides: fields (or even dummy packages) have been
provided so the new package will either get installed automatically, and/or
will safely replace or remove the old one. This also includes packages that
have been merged into other packages as this gives the same end result as a
rename.

Although we have made every effort to complete this list, it may still not be
exhaustive.

5.2 Split Packages

Between releases 2.2 (`potato') and 3.0 (`woody'), a number of packages have
been split into two or more packages. The reason for these splits, in general,
is that the original package provided a diverse set of functionalities, and
that few, if any, users used all of these components.Some packages will display
a notice warning of the split during the installation, some mention it in the
package description, and some just ignore it.

If you find that a familiar package is lacking some or all of its
functionality, check the list below to see if you need to install additional
packages to restore the original functionality. Failing that, check the
changelog for the package, which can be found in
/usr/share/doc/package/changelog.Debian.gz.

The following is a list of packages that have been split (this list may not be
complete):

5.3 Removed packages

5.3.1 Packages removed because of no maintainer

These are packages which have been removed because no Debian maintainer was
interested in maintaining them. The number associated with the bug is included
as this provides further information on the reason why the package was removed.
To use this number visit the Bug
Tracking System and do a query based on the bugnumber.

The alternatives field lists any packages that might replace the removed
package.

5.3.2 Packages lacking upstream

These are packages which have been removed because they lack an upstream
maintainer. The number associated with the bug is included as this provides
further information on the reason why the package was removed. To use this
number visit the Bug Tracking
System and do a query based on the bugnumber.

The alternatives field lists any packages that might replace the removed
package.

5.3.3 Packages removed for other reasons

The reason for the removal of the package is listed below the name of the
package. The number associated with the bug is included as this provides
further information on the reason why the package was removed. To use this
number visit the Bug Tracking
System and do a query based on the bugnumber.

The alternatives field lists any packages that might replace the removed
package.