| 1 |
<!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [ |
<!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [ |
| 2 |
<!entity % dynamicdata SYSTEM "../dynamic.ent" > %dynamicdata; |
<!entity % dynamicdata SYSTEM "../dynamic.ent" > %dynamicdata; |
| 3 |
<!entity % shareddata SYSTEM "../release-notes.ent" > %shareddata; |
<!entity % shareddata SYSTEM "../release-notes.ent" > %shareddata; |
| 4 |
<!entity docid "$Id: release-notes.en.sgml,v 1.42 2005-05-24 17:47:11 jfs Exp $"> |
<!entity docid "$Id: release-notes.en.sgml,v 1.43 2005-05-24 22:40:31 fjp Exp $"> |
| 5 |
]> |
]> |
| 6 |
|
|
| 7 |
<!-- Be careful with automatic reformatting. Please note that the indentation |
<!-- Be careful with automatic reformatting. Please note that the indentation |
| 840 |
in <file>/usr/share/doc/kernel-package</file>.</p> |
in <file>/usr/share/doc/kernel-package</file>.</p> |
| 841 |
|
|
| 842 |
</sect2> |
</sect2> |
| 843 |
</sect1> |
</sect1> |
| 844 |
</sect> |
</sect> |
| 845 |
|
|
| 846 |
<sect id="obsolete"><heading>Obsolete packages</heading> |
<sect id="obsolete"><heading>Obsolete packages</heading> |
| 847 |
|
|
| 848 |
<!-- JFS: Providing a full listing might be useful, especially if we can |
<!-- JFS: Providing a full listing might be useful, especially if we can |
| 849 |
point to the Bug that was opened when the bug was removed. This list should |
point to the Bug that was opened when the bug was removed. This list should |
| 851 |
potato to woody RN --> |
potato to woody RN --> |
| 852 |
|
|
| 853 |
<p>Introducing several thousand new packages, &releasename; also |
<p>Introducing several thousand new packages, &releasename; also |
| 854 |
retires and omits more than two thousand old packages from |
retires and omits more than two thousand old packages that were in |
| 855 |
&oldreleasename;. It provides no upgrade path for these obsolete |
&oldreleasename;. It provides no upgrade path for these obsolete |
| 856 |
packages. While nothing prevents you from continuing to use an |
packages. While nothing prevents you from continuing to use an |
| 857 |
obsolete package where desired, the Debian Project will usually |
obsolete package where desired, the Debian project will usually |
| 858 |
discontinue security support for it a year after &releasename;'s |
discontinue security support for it a year after &releasename;'s |
| 859 |
release<footnote>Or for as long as there is not another release in |
release<footnote>Or for as long as there is not another release in |
| 860 |
that time frame. Typically only two stable releases are supported |
that time frame. Typically only two stable releases are supported |
| 862 |
support in the meantime. Replacing them with available |
support in the meantime. Replacing them with available |
| 863 |
alternatives, if any, is recommended.</p> |
alternatives, if any, is recommended.</p> |
| 864 |
|
|
| 865 |
<p>There are many reasons why packages might have been removed from |
<p>There are many reasons why packages might have been removed from |
| 866 |
the distribution: they are no longer maintained in Debian; the |
the distribution: they are no longer maintained upstream, there is |
| 867 |
functionality they provide has been superseded by different |
no longer a Debian Developer interested in maintaining the packages; |
| 868 |
software (or a new version); or they are no longer considered |
the functionality they provide has been superseded by different |
| 869 |
suitable for &releasename;, due to bugs in them. In the later case, |
software (or a new version); or they are no longer considered |
| 870 |
packages might still be present in the "unstable" |
suitable for &releasename; due to bugs in them. In the later case, |
| 871 |
distribution.</p> |
packages might still be present in the "unstable" distribution.</p> |
| 872 |
|
|
| 873 |
<p>Detecting which packages in an updated system are "obsolete" is |
<p>Detecting which packages in an updated system are "obsolete" is |
| 874 |
easy since the package management front-ends will mark them as |
easy since the package management front-ends will mark them as |
| 875 |
such. If you are using <prgn>aptitude</prgn>, you will see a |
such. If you are using <prgn>aptitude</prgn>, you will see a |
| 876 |
listing of these packages in the "Obsolete and Locally Created |
listing of these packages in the "Obsolete and Locally Created |
| 877 |
Packages" entry. <prgn>Dselect</prgn> provides a similar section |
Packages" entry. <prgn>dselect</prgn> provides a similar section |
| 878 |
but the listing it presents might differ. Also, if you have used |
but the listing it presents might differ. Also, if you have used |
| 879 |
<prgn>aptitude</prgn> to manually install packages in |
<prgn>aptitude</prgn> to manually install packages in |
| 880 |
&oldreleasename; it will have kept track of those packages you |
&oldreleasename; it will have kept track of those packages you |
| 881 |
manually installed and will be able to mark as obsolete those |
manually installed and will be able to mark as obsolete those |
| 882 |
packages pulled in by dependencies alone which are no longer |
packages pulled in by dependencies alone which are no longer |
| 883 |
needed if a package has been removed. Also, <prgn>aptitude</prgn>, |
needed if a package has been removed. Also, <prgn>aptitude</prgn>, |
| 884 |
unlike <prgn>deborphan</prgn> will not mark as obsolete packages |
unlike <prgn>deborphan</prgn> will not mark as obsolete packages |
| 885 |
that you manually installed, as opposed to those that were |
that you manually installed, as opposed to those that were |
| 886 |
automaticaly installed through dependancies.</p> |
automaticaly installed through dependancies.</p> |
| 887 |
|
|
| 888 |
<p>You can also use additional tools to find obsolete packages |
<p>There are additional tools you can use to find obsolete packages |
| 889 |
such as <prgn>deborphan</prgn>, <prgn>debfoster</prgn> or |
such as <prgn>deborphan</prgn>, <prgn>debfoster</prgn> or |
| 890 |
<prgn>cruft</prgn>. <prgn>Deborphan</prgn> is highly recommended, |
<prgn>cruft</prgn>. <prgn>deborphan</prgn> is highly recommended, |
| 891 |
although it will (in default mode) only report obsolete libraries: |
although it will (in default mode) only report obsolete libraries: |
| 892 |
packages in the "libs" or "oldlibs" sections that are not used by |
packages in the "libs" or "oldlibs" sections that are not used by |
| 893 |
any other packages. Do not blindly remove the packages these tools |
any other packages. Do not blindly remove the packages these tools |
| 894 |
present, especially if you are using aggressive non-default |
present, especially if you are using aggressive non-default |
| 895 |
options that are prone to false positives. It is highly |
options that are prone to produce false positives. It is highly |
| 896 |
recommended that you manually review the packages suggested for |
recommended that you manually review the packages suggested for |
| 897 |
removal (i.e. their contents, size and description) before you |
removal (i.e. their contents, size and description) before you |
| 898 |
remove them.</p> |
remove them.</p> |
| 899 |
|
|
| 900 |
<!-- JFS: Should we recommend purging old packages? This might be |
<!-- JFS: Should we recommend purging old packages? This might be |
| 901 |
dangerous since the maintainer scripts might try to remove stuff that |
dangerous since the maintainer scripts might try to remove stuff that |
| 902 |
didn't belong to them... --> |
didn't belong to them... --> |
| 903 |
|
|
| 904 |
<p>The <url id="&url-bts;" name="Debian Bug Tracking System"> |
<p>The <url id="&url-bts;" name="Debian Bug Tracking System"> |
| 905 |
often provides additional information on why the package was |
often provides additional information on why the package was |
| 906 |
removed. You should review both the archived bug reports for the |
removed. You should review both the archived bug reports for the |
| 907 |
package and archived bug reports for the <url |
package itself and the archived bug reports for the <url |
| 908 |
id="&url-bts;/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes" |
id="&url-bts;/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes" |
| 909 |
name="ftp.debian.org pseudo-package">.</p> |
name="ftp.debian.org pseudo-package">.</p> |
| 910 |
|
|
| 911 |
|
<sect1 id="dummy"><heading>Dummy packages</heading> |
|
<sect1 id="dummy"><heading>Dummy packages</heading> |
|
| 912 |
|
|
| 913 |
<!-- JFS: If the appendix is kept this section should point there and the packages described here should be moved to that section --> |
<!-- JFS: If the appendix is kept this section should point there and the packages described here should be moved to that section --> |
| 914 |
|
|
| 915 |
<p>Improving system maintainability, &releasename; splits some of |
<p>Some packages from &oldreleasename; have been split into several |
| 916 |
&oldreleasename; packages into several packages each. To ease |
packages in &releasename;, often to improve system maintainability. To |
| 917 |
the upgrade path in such cases, &releasename; often provides |
ease the upgrade path in such cases, &releasename; often provides |
| 918 |
"dummy" packages: empty packages with dependencies which pull |
"dummy" packages: empty packages that have the same name as the old |
| 919 |
in the new packages. These "dummy" packages are considered |
package in &oldreleasename; with dependencies that cause the new |
| 920 |
|
packages to be installed. These "dummy" packages are considered |
| 921 |
obsolete packages after the upgrade and can be safely removed. |
obsolete packages after the upgrade and can be safely removed. |
| 922 |
|
|
| 923 |
<p>Most (but not all) dummy packages' descriptions indicate their |
<p>Most (but not all) dummy packages' descriptions indicate their |
| 924 |
purpose. Package descriptions for dummy packages are not uniform, |
purpose. Package descriptions for dummy packages are not uniform, |
| 925 |
however, so you might also find <prgn>deborphan</prgn> with the |
however, so you might also find <prgn>deborphan</prgn> with the |
| 926 |
<tt>--guess</tt> options useful to detect them in your |
<tt>--guess</tt> options useful to detect them in your system. |
| 927 |
system. Note that some dummy packages are not intended to be |
Note that some dummy packages are not intended to be removed after |
| 928 |
removed after an upgrade but are, instead, used to keep track of |
an upgrade but are, instead, used to keep track of the current |
| 929 |
the given version available for a program through time.</p> |
available version of a program over time.</p> |
| 930 |
|
|
| 931 |
</sect1> |
</sect1> |
| 932 |
</sect> |
</sect> |
| 933 |
</chapt> |
</chapt> |
| 934 |
|
|
| 935 |
<!-- FJP: Add more info here on dealing with obsolete packages? |
<!-- FJP: Add more info here on dealing with obsolete packages? |
Parent Directory
| 
Revision Log
| 
Patch