the --overwrite option of dpkg-name has no effect

[Ivan Gagis]

Binary package hint: dpkg

dpkg-name --overwrite does not overwrite existing file.

the dpkg-name is a perl script and there is a bug in that script which actually is just a typo:
the overwrite word is written as overwite.

Fix:
in the dpkg-name script search for "$options{overwite}" string and change it to "$options{overwrite}"

[Ivan Gagis (igagis)]

This bug exists in debian too.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dpkg - 1.16.0~ubuntu4

---------------
dpkg (1.16.0~ubuntu4) natty; urgency=low

  * Merge from git://git.debian.org/users/hertzog/dpkg.git
    pu/multiarch/snapshot/20110314 for updated multiarch support. This
    reverts the dpkg database changes from the earlier merge in favor of a
    single-directory dpkg db again.
    - Fix typo in «dpkg-name --overwrite» argument parsing so that it
      actually works at all. Thanks to Ivan Gagis <email address hidden>.
      LP: #728708
  * Update the version checks for the multiarch db format to point to
    1.16.0~ubuntu4 instead of the (not-yet-released) 1.16.0.
  * On upgrade from 1.16.0~ubuntu[1-3], if /var/lib/dpkg/info/$arch is a
    directory, migrate the contents to var/lib/dpkg/info; and handle the
    reverse on downgrade. This does not handle metadata for packages of
    foreign architectures; if this affects you, come talk to me. :-)
    LP: #727603.
  * add new variables, DEB_HOST_MULTIARCH and DEB_BUILD_MULTIARCH, that
    return the "ideal" GNU triplet for each architecture which should be
    used as the path component for library installation.
 -- Steve Langasek <email address hidden> Mon, 14 Mar 2011 18:12:06 -0700