On Wed, Nov 10, 2004 at 04:22:19PM -0500, Josh Metzler wrote: > I was thinking about this "grave" bug, and it seems that the only workable > solution to new upstream symbols being introduced in the branch (which then > make it into new debian revisions) is to have shlibs for the kde packages > updated to the latest debian version every upload. > > So, I downloaded the kdelibs source, and debian/rules, I find > > dh_mkshlibs -V > > which according to `man dh_makeshlibs` should result in shlibs being set to > the exact debian revision: > > > dh_makeshlibs -V > > > > Assuming the current version of the package is 1.0-3, generates a shlibs > file that looks something like: > > libfoobar 1 libfoobar1 (>= 1.0-3) > > But, looking at /var/lib/dpkg/info/kdelibs4.shlibs, all of the packages have > shlibs set to (>= 4:3.3.1) <- note the missing debian revision. > > So, my question is this a bug in debhelper, or am I misinterpretting > something? debhelper used to set it to exact debian revision, but changed now to just use the upstream revision with no obvious way to get the old behavior. > And, I think this bug can be downgraded to important, as upgrading to the > current versions of packages fixes it (though the real bug is that partial > upgrades are allowed by depends but can break packages). As far as I know this bug has been fixed in the version of kdepim sitting in NEW since Nov 7. Hopefully it will be processed soon. Chris
Attachment:
signature.asc
Description: Digital signature