On 05/13/2014 01:58 PM, James Cloos wrote:
>>>>>> "CM" == Christoph Martin <mar...@uni-mainz.de> writes:
> 
> CM> sks depends on db-util which depends on the current db utils package.
> CM> The current db-util in testing/jessie has version 5.3 and depends on
> CM> db5.3-utils.
> 
> CM> So this should be no problem. Maybe at the time of your install there
> CM> was an old version of db-util installed.
> 
> IIRC, the bug is that a newer version of db5.x-utils got installed, the
> old version was removed, and apt permitted said removal even though sks
> needed said old version.
> 
> I think sks has to depend on the exact version of db5.x-utils it uses,
> to ensure that it always can recover the db.
> 
> Unless there is a better way to ensure that the proper recovery tool
> is available.

Hm, please see the discussion on https://bugs.debian.org/664768 -- it
looks like the sks packaging history has gone in both directions on this
in the past.

See also the changelog for sks 1.1.1+dpkgv3-6.1:

sks (1.1.1+dpkgv3-6.1) unstable; urgency=low

  * Non-maintainer upload.
  * Remove XA environment usage (patch from upstream) and use generic -ldb
    library to link with (Closes: #621384)
  * Add automagick upgrade of Berkeley DB databases (Closes: #606183)
  * Change db4.7-util to Recommends: db4.7-util and Depends: db-util

 -- Ondřej Surý <ond...@debian.org>  Fri, 13 May 2011 12:33:13 +0200


(i've cc'ed Ondřej here in case he has any insights about how these
changes might have lead toward #740775)

        --dkg

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to