Change log for dpkg package in Ubuntu

151184 of 334 results
Superseded in gutsy-release
dpkg (1.14.5ubuntu1) gutsy; urgency=low

  Merge from debian unstable, remaining changes follow:

  Miscellaneous fixes:
  * Don't consider it a file conflict if the package contains
    a symlink to a directory where another package already contains the
    same symlink/directory and the existing and new symlinks point to the
    same place.  (Launchpad 22340, Debian #377682.)
  * mlib contains m_strdup (part of the fix for Debian #379028).
  * Fix formatting of these files:
       lib/showpkg.c
       lib/tarfn.c
       src/configure.c
       src/archives.c (function quote_filename only)
    to conform to the rest of dpkg by running them through
    expand -t2 (and in the last case using M-x indent-rigidly once).
    As discussed on debian-dpkg.  Submitted upstream as Debian #375711.
  * scripts/update-alternatives.pl: in the case where the slave is
    inapplicable do not attempt to create the slave link before removing
    it again.  This will help alleviate LP #84906 (vim upgrade problems)
    and will generally make things slightly less fragile.  Debian #411699.
  * mlib contains m_strdup (part of the fix for Debian #379028).
  * Fix the uninitialized value in string ne at /usr/sbin/update-alternatives
    line 602.  Thanks to Ubulette for this patch.  (LP: #118246)
    Patch modified by iwj not to ignore lstat failures.
  * Use i686 for lpia in cputable and triplettable.

  Launchpad integration:
  * Implement changelog-closes-bugs for Ubuntu (see
    https://wiki.ubuntu.com/ClosingBugsFromChangelog).
  * Add Launchpad-Bugs-Fixed to dpkg-genchanges too, to make it not
    complain about unknown fields.

  DebianMaintainerField:
  * scripts/dpkg-source.pl: Check that debian/control complies to
    https://wiki.ubuntu.com/DebianMaintainerField: Refuse to build a source
    package if we have an Ubuntu version number, but Maintainer: is not an
    Ubuntu address. Output a warning if there is no XSBC-Original-Maintainer:
    field for packages with an Ubuntu version number.
  * scripts/dpkg-source.pl: Only fail to build the source package if $DEBEMAIL
    contains 'ubuntu'. If not, only print a warning.
  * debian/control: Change Maintainer/XSBC-Original-Maintainer field.

  Implementation of Breaks:
  * References:
     http://lists.debian.org/debian-devel/1997/10/msg00643.html
     https://wiki.ubuntu.com/PackageDependencyFieldBreaks
     Debian #379140.
  * Manpages mention Breaks: deb-control.5, dpkg-query.1, dpkg.1.
  * Support for Breaks in dpkg-source, dpkg-gencontrol et al.
  * Support for Breaks in the code in dpkg.
  * Breaks is ignored by dselect.
  * Fix for Debian #378003 (multiple deconfigurations) is
    mixed in with Breaks implementation.
  * Declare Breaks against older dpkg-dev rather than Conflicts.
  * Decisions made:
    * Specifying Breaks: <virtual package> is fairly meaningless
      without versioned Provides but to make versioned Provides easier
      in the future we support it fully.
    * We do not transitively deconfigure things when we deconfigure
      due to Breaks, just as we don't do so when we deconfigure due
      to removal due to Conflicts (see also Debian #378009).
    * Just as for deconfiguration due to Conflicts, we don't deconfigure
      Essential packages without --force-remove-essential.
    * We aren't willing to deconfigure more than one package as a result
      of a single element of a Breaks, just as we aren't willing to
      remove more than one package as a result of a single element of
      a Conflicts.  (Note that this can only occur due to virtual
      packages so it can be worked around by specifying the individual
      real packages instead.)
    * We're happy to deconfigure a package that's on hold even if
      afterwards, due to Breaks, there might not be a way to reconfigure it.
      (This is analogous to the situation where we install a package which
      no longer satisfies the dependencies of an on-hold package; it's not
      clear what the right answer is.)
    * We invent a new --force-breaks which does much the
      same as --force-conflicts.
    * --ignore-depends works for Breaks even though it doesn't work
      for Conflicts.
    * <deconfigured's prerm> deconfigure in-favour <installing> <ver>
        as well as
      <deconfigured's prerm> deconfigure in-favour <installing> <ver> \
                                       removing <conflictor> <ver>
      and of course the corresponding
    <deconfigured's postinst> abort-deconfigure in-favour <installing> <ver>

 -- Ian Jackson <email address hidden>   Wed, 11 Jul 2007 16:26:17 +0100
Superseded in gutsy-release
dpkg (1.14.4+svn20070602r802-0ubuntu3) gutsy; urgency=low

  * Use i686 for lpia in cputable and triplettable.

 -- Matthias Klose <email address hidden>   Mon, 25 Jun 2007 15:29:05 +0200
Superseded in gutsy-release
dpkg (1.14.4+svn20070602r802-0ubuntu2) gutsy; urgency=low

  * Fix the uninitialized value in string ne at /usr/sbin/update-alternatives
    line 602.  Thanks to Ubulette for this patch.  (LP: #118246)
  * Modify Maintainer value to match Debian-Maintainer-Field Spec

 -- Sarah Hobbs <email address hidden>   Sat, 23 Jun 2007 02:35:25 +1000
Superseded in gutsy-release
dpkg (1.14.4+svn20070602r802-0ubuntu1) gutsy; urgency=low

  * Merge from Debian (upstream) svn (svn diff -r794:802 | patch).
    Changes from svn log:
      Add lpia support to ostable and triplettable.
      Bump version to 1.14.5~.
    And translations:
      Updated manpages translation to 1282t.
      vi.po: Updated Vietnamese translation.
      [pt.po] Updated to 285t
      [pt.po] Updated to 921t

 -- Ian Jackson <email address hidden>   Mon,  4 Jun 2007 15:40:14 +0100
Superseded in gutsy-release
dpkg (1.14.4ubuntu2) gutsy; urgency=low

  * scripts/dpkg-source.pl: Do not call &warn() any more, that got removed
    recently. Use warning().

 -- Martin Pitt <email address hidden>   Thu, 31 May 2007 15:11:54 +0200
Superseded in gutsy-release
dpkg (1.14.4ubuntu1) gutsy; urgency=low

  Forward-port Ubuntu changes from feisty, as follows:

  Miscellaneous fixes:
  * Don't consider it a file conflict if the package contains
    a symlink to a directory where another package already contains the
    same symlink/directory and the existing and new symlinks point to the
    same place.  (Launchpad 22340, Debian #377682.)
  * mlib contains m_strdup (part of the fix for Debian #379028).
  * Fix formatting of these files:
       lib/showpkg.c
       lib/tarfn.c
       src/configure.c
       src/archives.c (function quote_filename only)
    to conform to the rest of dpkg by running them through
    expand -t2 (and in the last case using M-x indent-rigidly once).
    As discussed on debian-dpkg.  Submitted upstream as Debian #375711.
  * scripts/update-alternatives.pl: in the case where the slave is
    inapplicable do not attempt to create the slave link before removing
    it again.  This will help alleviate LP #84906 (vim upgrade problems)
    and will generally make things slightly less fragile.  Debian #411699.
  * dpkg-source: respect g+s and umask when extracting.
    (LP 51468, submitted upstream as Debian #390915.)
    The new behaviour is that the only thing which matters about the
    permissions specified in the archive is whether an object has execute
    permission for anyone, as for chmod =X.  Set-id (of files and
    directories) and read/write permissions from the archive are ignored.
    Permissions are determined by the umask; group ownership and
    directory-setgid according the usual filesystem policies.

  Launchpad integration:
  * Implement changelog-closes-bugs for Ubuntu (see
    https://wiki.ubuntu.com/ClosingBugsFromChangelog).
  * Add Launchpad-Bugs-Fixed to dpkg-genchanges too, to make it not
    complain about unknown fields.

  DebianMaintainerField:
  * scripts/dpkg-source.pl: Check that debian/control complies to
    https://wiki.ubuntu.com/DebianMaintainerField: Refuse to build a source
    package if we have an Ubuntu version number, but Maintainer: is not an
    Ubuntu address. Output a warning if there is no XSBC-Original-Maintainer:
    field for packages with an Ubuntu version number.
  * scripts/dpkg-source.pl: Only fail to build the source package if $DEBEMAIL
    contains 'ubuntu'. If not, only print a warning.
  * debian/control: Change Maintainer/XSBC-Original-Maintainer field.

  Implementation of Breaks:
  * References:
     http://lists.debian.org/debian-devel/1997/10/msg00643.html
     https://wiki.ubuntu.com/PackageDependencyFieldBreaks
     Debian #379140.
  * Manpages mention Breaks: deb-control.5, dpkg-query.1, dpkg.1.
  * Support for Breaks in dpkg-source, dpkg-gencontrol et al.
  * Support for Breaks in the code in dpkg.
  * Breaks is ignored by dselect.
  * Fix for Debian #378003 (multiple deconfigurations) is
    mixed in with Breaks implementation.
  * Declare Breaks against older dpkg-dev rather than Conflicts.
  * Decisions made:
    * Specifying Breaks: <virtual package> is fairly meaningless
      without versioned Provides but to make versioned Provides easier
      in the future we support it fully.
    * We do not transitively deconfigure things when we deconfigure
      due to Breaks, just as we don't do so when we deconfigure due
      to removal due to Conflicts (see also Debian #378009).
    * Just as for deconfiguration due to Conflicts, we don't deconfigure
      Essential packages without --force-remove-essential.
    * We aren't willing to deconfigure more than one package as a result
      of a single element of a Breaks, just as we aren't willing to
      remove more than one package as a result of a single element of
      a Conflicts.  (Note that this can only occur due to virtual
      packages so it can be worked around by specifying the individual
      real packages instead.)
    * We're happy to deconfigure a package that's on hold even if
      afterwards, due to Breaks, there might not be a way to reconfigure it.
      (This is analogous to the situation where we install a package which
      no longer satisfies the dependencies of an on-hold package; it's not
      clear what the right answer is.)
    * We invent a new --force-breaks which does much the
      same as --force-conflicts.
    * --ignore-depends works for Breaks even though it doesn't work
      for Conflicts.
    * <deconfigured's prerm> deconfigure in-favour <installing> <ver>
        as well as
      <deconfigured's prerm> deconfigure in-favour <installing> <ver> \
                                       removing <conflictor> <ver>
      and of course the corresponding
    <deconfigured's postinst> abort-deconfigure in-favour <installing> <ver>

Superseded in gutsy-release
Obsolete in feisty-release
dpkg (1.13.24ubuntu6) feisty; urgency=low

  * scripts/dpkg-source.pl: Only fail to build the source package if $DEBEMAIL
    contains 'ubuntu'. If not, only print a warning.

 -- Martin Pitt <email address hidden>   Tue,  6 Mar 2007 10:18:39 +0100
Superseded in feisty-release
dpkg (1.13.24ubuntu5) feisty; urgency=low

  * scripts/update-alternatives.pl: in the case where the slave is
    inapplicable do not attempt to create the slave link before removing
    it again.  This will help alleviate LP #84906 (vim upgrade problems)
    and will generally make things slightly less fragile.

 -- Ian Jackson <email address hidden>   Mon, 19 Feb 2007 17:26:05 +0000
Superseded in feisty-release
dpkg (1.13.24ubuntu4) feisty; urgency=low

  [ Martin Pitt ]
  * scripts/dpkg-source.pl: Check that debian/control complies to
    https://wiki.ubuntu.com/DebianMaintainerField: Refuse to build a source
    package if we have an Ubuntu version number, but Maintainer: is not an
    Ubuntu address. Output a warning if there is no XSBC-Original-Maintainer:
    field for packages with an Ubuntu version number.
  * debian/control: Change Maintainer/XSBC-Original-Maintainer field.

  [ Colin Watson ]
  * scripts/dpkg-gencontrol.pl: Fix regular expression that special-cased
    Origin:, Bugs:, and Maintainer:. The broken one caused X[SBC]-* fields to
    go into the .deb control record unprocessed. (LP: #84850)

 -- Martin Pitt <email address hidden>   Tue, 13 Feb 2007 12:30:55 +0100
Superseded in feisty-release
dpkg (1.13.24ubuntu3) feisty; urgency=low

  * Add Launchpad-Bugs-Fixed to dpkg-genchanges too, to make it not
    complain about unknown fields.

 -- Tollef Fog Heen <email address hidden>   Thu,  8 Feb 2007 16:03:30 +0100
Superseded in feisty-release
dpkg (1.13.24ubuntu2) feisty; urgency=low

  * Implement changelog-closes-bugs for Ubuntu (see
    https://wiki.ubuntu.com/ClosingBugsFromChangelog).

 -- Tollef Fog Heen <email address hidden>   Tue,  6 Feb 2007 11:02:26 +0100
Superseded in feisty-release
dpkg (1.13.24ubuntu1) feisty; urgency=low

  * Merge from debian unstable.
    Remaining differences from Debian to Ubuntu follow:

  Miscellaneous fixes:
  * Fix for Debian #378003 (multiple deconfigurations).
  * mlib contains m_strdup (part of the fix for Debian #379028).
  * dpkg: add missing newline to an error message.
    (LP 29729, submitted upstream as Debian #390914.)
  * Fix formatting of these files:
       lib/showpkg.c
       lib/tarfn.c
       src/configure.c
       src/archives.c (function quote_filename only)
    to conform to the rest of dpkg by running them through
    expand -t2 (and in the last case using M-x indent-rigidly once).
    As discussed on debian-dpkg.  Submitted upstream as Debian #375711.
  * dpkg: describedepcon uses more l10n-friendly approach.
    (LP 63744, submitted upstream as Debian #390916.)
  * dpkg-source: respect g+s and umask when extracting.
    (LP 51468, submitted upstream as Debian #390915.)
    The new behaviour is that the only thing which matters about the
    permissions specified in the archive is whether an object has execute
    permission for anyone, as for chmod =X.  Set-id (of files and
    directories) and read/write permissions from the archive are ignored.
    Permissions are determined by the umask; group ownership and
    directory-setgid according the usual filesystem policies.
  * Don't consider it a file conflict if the package contains
    a symlink to a directory where another package already contains the
    same symlink/directory and the existing and new symlinks point to the
    same place.  (Launchpad 22340.  Apparently not reported upstream yet.)

  Implementation of Breaks:
  * References:
     http://lists.debian.org/debian-devel/1997/10/msg00643.html
     https://wiki.ubuntu.com/PackageDependencyFieldBreaks
  * Manpages mention Breaks: deb-control.5, dpkg-query.1, dpkg.1.
  * Support for Breaks in dpkg-source, dpkg-gencontrol et al.
  * Support for Breaks in the code in dpkg.
  * Breaks is ignored by dselect.

  Decisions made:
  * Specifying Breaks: <virtual package> is fairly meaningless
    without versioned Provides but to make versioned Provides easier
    in the future we support it fully.
  * We do not transitively deconfigure things when we deconfigure
    due to Breaks, just as we don't do so when we deconfigure due
    to removal due to Conflicts (see also Debian #378009).
  * Just as for deconfiguration due to Conflicts, we don't deconfigure
    Essential packages without --force-remove-essential.
  * We aren't willing to deconfigure more than one package as a result
    of a single element of a Breaks, just as we aren't willing to
    remove more than one package as a result of a single element of
    a Conflicts.  (Note that this can only occur due to virtual
    packages so it can be worked around by specifying the individual
    real packages instead.)
  * We're happy to deconfigure a package that's on hold even if
    afterwards, due to Breaks, there might not be a way to reconfigure it.
    (This is analogous to the situation where we install a package which
    no longer satisfies the dependencies of an on-hold package; it's not
    clear what the right answer is.)
  * We invent a new --force-breaks which does much the
    same as --force-conflicts.
  * --ignore-depends works for Breaks even though it doesn't work
    for Conflicts.
  * <deconfigured's prerm> deconfigure in-favour <installing> <ver>
      as well as
    <deconfigured's prerm> deconfigure in-favour <installing> <ver> \
                                       removing <conflictor> <ver>
      and of course the corresponding
    <deconfigured's postinst> abort-deconfigure in-favour <installing> <ver>

 -- Ian Jackson <email address hidden>   Thu, 23 Nov 2006 20:15:09 +0000
Superseded in dapper-updates
dpkg (1.13.11ubuntu7) dapper-updates; urgency=low

  * Backport Ian Jackson's fix for the assertion failure that occurs when
    dependency cycle breaking fails because every link involves a Provides.
  * This is probably better known to users as the obscure "process_queue:
    Assertion `dependtry <= 4' failed" bug (launchpad.net/bugs/46530)
  * Tested by Simon Law, as well as being extensively tested by me on the
    Ubuntu build daemons for nearly a month; no regressions were noticed.

 -- Adam Conrad <email address hidden>   Thu, 16 Nov 2006 17:31:26 -0800
Deleted in dapper-proposed (Reason: moved to -updates)
dpkg (1.13.11ubuntu7~proposed) dapper-proposed; urgency=low

  * Backport Ian Jackson's fix for the assertion failure that occurs when
    dependency cycle breaking fails because every link involves a Provides.
  * This is probably better known to users as the obscure "process_queue:
    Assertion `dependtry <= 4' failed" bug (launchpad.net/bugs/46530)

 -- Adam Conrad <email address hidden>   Fri, 20 Oct 2006 23:57:48 +1000
Superseded in feisty-release
Obsolete in edgy-release
dpkg (1.13.22ubuntu7) edgy; urgency=low

  * dpkg: add missing newline to an error message.  (LP 29729.)
  * dpkg: describedepcon uses more l10n-friendly approach.  (LP 63744.)
  * dpkg-source: respect g+s and umask when extracting.  (LP 51468.)
    The new behaviour is that the only thing which matters about the
    permissions specified in the archive is whether an object has execute
    permission for anyone, as for chmod =X.  Set-id (of files and
    directories) and read/write permissions from the archive are ignored.
    Permissions are determined by the umask; group ownership and
    directory-setgid according the usual filesystem policies.

 -- Ian Jackson <email address hidden>   Tue,  3 Oct 2006 18:01:06 +0100
Superseded in edgy-release
dpkg (1.13.22ubuntu6) edgy; urgency=low

  * dselect: do not abort on Breaks; ignore it instead.  (Malone 56761.)

 -- Ian Jackson <email address hidden>   Fri, 18 Aug 2006 10:59:35 +0100
Superseded in edgy-release
dpkg (1.13.22ubuntu5) edgy; urgency=low

  * Bugfix: Wrong version number was checked for versioned Breaks.
  * Support for Breaks in dpkg-source, dpkg-gencontrol et al.

 -- Ian Jackson <email address hidden>   Mon, 14 Aug 2006 16:49:11 +0100
Superseded in edgy-release
dpkg (1.13.22ubuntu4) edgy; urgency=low

  * Implement Breaks.  References:
     http://lists.debian.org/debian-devel/1997/10/msg00643.html
     https://wiki.ubuntu.com/PackageDependencyFieldBreaks

  Decisions made:
  * Specifying Breaks: <virtual package> is fairly meaningless
    without versioned Provides but to make versioned Provides easier
    in the future we support it fully.
  * We do not transitively deconfigure things when we deconfigure
    due to Breaks, just as we don't do so when we deconfigure due
    to removal due to Conflicts (see also #378009).
  * Just as for deconfigure due to Conflicts, we don't deconfigure
    Essential packages without --force-remove-essential.
  * We aren't willing to deconfigure more than one package as a result
    of a single element of a Breaks, just as we aren't willing to
    remove more than one package as a result of a single element of
    a Conflicts.  (Note that this can only occur due to virtual
    packages so it can be worked around by specifying the individual
    real packages instead.)
  * We're happy to deconfigure a package that's on hold even if
    afterwards, due to Breaks, there might not be a way to reconfigure it.
    (This is analogous to the situation where we install a package
    which no longer satisfies the dependencies of an on-hold
    package; it's not clear what the right answer is.)
  * We invent a new --force-breaks which does much the
    same as --force-conflicts.
  * --ignore-depends works for Breaks even though it doesn't work
    for Conflicts.
  * <deconfigured's prerm> deconfigure in-favour <installing> <ver>
      as well as
    <deconfigured's prerm> deconfigure in-favour <installing> <ver> \
                                       removing <conflictor> <ver>
      and of course the corresponding
    <deconfigured's postinst> abort-deconfigure in-favour <installing> <ver>

  Two other changes bundled:
  * mlib contains m_strdup (part of the fix for #379028).
  * Fix for #378003 (multiple deconfigurations).

 -- Ian Jackson <email address hidden>   Fri, 21 Jul 2006 17:22:24 +0100
Superseded in edgy-release
dpkg (1.13.22ubuntu3) edgy; urgency=low

  * Fix formatting of these files:
       lib/showpkg.c
       lib/tarfn.c
       src/configure.c
       src/archives.c (function quote_filename only)
    to conform to the rest of dpkg by running them through
    expand -t2 (and in the last case using M-x indent-rigidly once).
    As discussed on debian-dpkg.  Debian #375711.

 -- Ian Jackson <email address hidden>   Fri, 21 Jul 2006 17:17:49 +0100
Superseded in edgy-release
dpkg (1.13.22ubuntu2) edgy; urgency=low

  * `Breaks': Implement step 1 of PackageDependencyFieldBreaks:
     - Parse Breaks as a dependency field where `|' is not allowed,
       and know how to display it, etc.
     - Refuse to install an archive which contains Breaks unless
       --force-depends is specified (I think --force-depends is right
       rather than --force-conflicts or a new --force-breaks for this).
     - Explicitly ignore Breaks in the handful of places where that's
       needed, so that if a package with Breaks is somehow installed the
       Breaks field will not cause trouble (it will be ignored).

 -- Ian Jackson <email address hidden>   Tue, 11 Jul 2006 19:01:59 +0100
Superseded in edgy-release
dpkg (1.13.22ubuntu1) edgy; urgency=low

  * Resynchronise with Debian.

Superseded in edgy-release
dpkg (1.13.21ubuntu1) edgy; urgency=low

  * Resynchronise with Debian. One change remains, namely IWJ's
    symlink-to-same-directory file conflict fix in 1.13.10ubuntu4.

Superseded in edgy-release
Obsolete in dapper-release
dpkg (1.13.11ubuntu6) dapper; urgency=low

  * Completely remove md5sum diversion madness.  Instead, we Pre-Depend
    on a version of textutils which provides /usr/bin/md5sum.  We rely on
    the logic in coreutils to remove our diversions.

 -- Ian Jackson <email address hidden>   Fri,  5 May 2006 16:24:23 +0100
Superseded in dapper-release
dpkg (1.13.11ubuntu5) dapper; urgency=low

  * Add new quiet option to dpkg-source to supress warnings. Patch applied
    from 1.13.17.

 -- Matthias Klose <email address hidden>   Sun,  9 Apr 2006 12:51:12 +0200
Superseded in dapper-release
dpkg (1.13.11ubuntu4) dapper; urgency=low

  * Force reversion back to ubuntu2.

 -- Scott James Remnant <email address hidden>   Thu,  6 Apr 2006 12:07:25 +0100
Superseded in dapper-release
dpkg (1.13.11ubuntu3) dapper; urgency=low

  * Apply Nexenta Patch (Ubuntu: #4505):
    - build dependency includes selinux (look for [gnu-linux] in the patch
    - missing solaris debian architecture (look for ostable)
    - dpkg-shlibdeps does not recognize SUN's ldd output
    - checking for ENOTEMPTY-only is insufficient for other POSIX
      (but not Linux) OSes (look for ENOTEMPTY).
    - object stack (obstack) is missing.
    - strnlen() is not POSIX
    - multiple type casting errors in dselect around mvwaddstr()
    - resizeterm() is NCURSES extension

 -- Scott James Remnant <email address hidden>   Thu,  6 Apr 2006 05:11:37 +0100
Superseded in dapper-release
dpkg (1.13.11ubuntu2) dapper; urgency=low

  * Make conffile prompt about locally-deleted conffile less misleading.
    (Debian 351361.)

  Change backported from dpkg 1.13.12:
  * When linking statically, explicitly add libsepol, even if its only a
    transitive library. The proper fix should come with a pkg-config file.
    Based on a patch by Bart Martens <email address hidden>.
    Closes: #347744, #348659
  * Don't build-depend on in SELinux support on Hurd.
  * Reran autoconf.
Superseded in dapper-release
Superseded in dapper-release
dpkg (1.13.11ubuntu1) dapper; urgency=low


  * Merge Debian and Ubuntu changes into a glorious hole.

 -- Scott James Remnant <email address hidden>  Mon,  7 Nov 2005 18:33:31 -0500
Obsolete in breezy-release
dpkg (1.13.10ubuntu4) breezy; urgency=low


  * Don't consider it a file conflict if the package contains
    a symlink to a directory where another package already contains the
    same symlink/directory and the existing and new symlinks point to the
    same place.  Ubuntu 16133.

 -- Ian Jackson <email address hidden>  Sat, 24 Sep 2005 18:07:25 +0100
Obsolete in hoary-updates
dpkg (1.10.27ubuntu2) hoary-updates; urgency=low


  * When copying the forward dependency tree on unpack, blank the version
    field of each unversioned dependency rather than leaving it
    uninitialised.  Closes: Ubuntu #13306.

 -- Colin Watson <email address hidden>  Fri, 12 Aug 2005 10:02:57 +0100
Obsolete in hoary-security
dpkg (1.10.27ubuntu1.1) hoary-security; urgency=low


  * SECURITY UPDATE: Rebuild against new zlib version to fix zlib
    vulnerabilities CAN-2005-1849 and CAN-2005-2096.

 -- Martin Pitt <email address hidden>  Thu, 21 Jul 2005 11:45:24 +0000
Obsolete in hoary-release
dpkg (1.10.27ubuntu1) hoary; urgency=low


  * Take Replaces into account when installing packages; don't issue a
    "trying to overwrite" error if the file that already exists is in
    a package that Replaces the one being installed.

 -- Scott James Remnant <email address hidden>  Thu, 17 Mar 2005 02:19:23 +0000
Obsolete in warty-security
dpkg (1.10.22ubuntu2.1) warty-security; urgency=low


  * SECURITY UPDATE: Rebuild against new zlib version to fix zlib
    vulnerabilities CAN-2005-1849 and CAN-2005-2096.

 -- Martin Pitt <email address hidden>  Thu, 21 Jul 2005 11:30:16 +0000
Obsolete in warty-release
dpkg (1.10.22ubuntu2) warty; urgency=low


  * Normalise library paths in dpkg-shlibdeps so we can resolve them
    correctly on both Hurd and AMD64.

 -- Scott James Remnant <email address hidden>  Tue, 17 Aug 2004 11:39:43 +0100
151184 of 334 results