Package: libcap2 Severity: wishlist Tags: patch User: [email protected] Usertags: origin-ubuntu ubuntu-patch jaunty
Hi Torsten, libcap1 is now obsolete, and using that library causes the kernel to emit warnings. It would be good if we could get all the remaining libcap1 reverse-dependencies transitioned to libcap2; the most efficient way to do that, since the APIs are compatible and no packages have versioned Build-Depends on libcap-dev, is to have libcap2-dev start Providing libcap-dev. The attached (trivial) patch does this; once changed, we can schedule binNMUs in unstable for all libcap1 reverse-deps, and drop libcap1 from the archive, a plan which I've also cleared already with the libcap1 maintainer. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
diff -Nru libcap2-2.16/debian/changelog libcap2-2.16/debian/changelog --- libcap2-2.16/debian/changelog 2009-03-20 20:23:21.000000000 +0000 +++ libcap2-2.16/debian/changelog 2009-03-20 20:23:21.000000000 +0000 @@ -1,3 +1,10 @@ +libcap2 (2.16-2.1) unstable; urgency=low + + * Make libcap2-dev Provide: libcap-dev; they're API-compatible and + libcap1 is obsolete. + + -- Steve Langasek <[email protected]> Fri, 20 Mar 2009 20:17:39 +0000 + libcap2 (2.16-2) unstable; urgency=low * upload to unstable diff -Nru libcap2-2.16/debian/control libcap2-2.16/debian/control --- libcap2-2.16/debian/control 2009-03-20 20:23:21.000000000 +0000 +++ libcap2-2.16/debian/control 2009-03-20 20:23:21.000000000 +0000 @@ -13,6 +13,8 @@ Section: libdevel Architecture: any Depends: libcap2 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +Provides: libcap-dev +Replaces: libcap-dev Conflicts: libcap-dev Suggests: manpages-dev Description: development libraries and header files for libcap2
