diff from 68570 and 21737

Description: Circumvent Debian package dependencies
 This package provides a tool to create trivial Debian packages.
 Typically these packages contain only dependency information, but they
 can also include normal installed files like other packages do.
 .
 One use for this is to create a metapackage: a package whose sole
 purpose is to declare dependencies and conflicts on other packages so
 that these will be automatically installed, upgraded, or removed.
 .
 Another use is to circumvent dependency checking: by letting dpkg
 think a particular package name and version is installed when it
 isn't, you can work around bugs in other packages' dependencies.
 (Please do still file such bugs, though.)

Description: Circumvent Debian package dependencies
 This package provides a tool to create Debian packages that only
 contain dependency information.
 .
 One use for this is to create a metapackage: a package whose sole
 purpose is to declare dependencies and conflicts on other packages so
 that these will be automatically installed, upgraded, or removed.
 .
 Another use is to circumvent dependency checking.  If a package P is
 not installed on the system, packages that depend on P cannot normally
 be installed.  However, if functionality equivalent to P is known to
 be installed, this tool can be used to trick the Debian package
 management system into believing that package P is actually installed.
 NOTE: this should be considered a crude hack to work around awkward
 situations, not a normal solution.  If you use equivs to work around
 bugs in other Debian packages, you should also file bug reports
 against those packages.

--- 68570	Thu Jan  1 00:00:00 1970
+++ 21737	Thu Jan  1 00:00:00 1970
@@ -1,13 +1,17 @@
 Circumvent Debian package dependencies
- This package provides a tool to create trivial Debian packages.
- Typically these packages contain only dependency information, but they
- can also include normal installed files like other packages do.
+ This package provides a tool to create Debian packages that only
+ contain dependency information.
  .
  One use for this is to create a metapackage: a package whose sole
  purpose is to declare dependencies and conflicts on other packages so
  that these will be automatically installed, upgraded, or removed.
  .
- Another use is to circumvent dependency checking: by letting dpkg
+ Another use is to circumvent dependency checking.  If a package P is
- think a particular package name and version is installed when it
+ not installed on the system, packages that depend on P cannot normally
- isn't, you can work around bugs in other packages' dependencies.
+ be installed.  However, if functionality equivalent to P is known to
- (Please do still file such bugs, though.)
+ be installed, this tool can be used to trick the Debian package
+ management system into believing that package P is actually installed.
+ NOTE: this should be considered a crude hack to work around awkward
+ situations, not a normal solution.  If you use equivs to work around
+ bugs in other Debian packages, you should also file bug reports
+ against those packages.