Package: edos-debcheck Version: 1.0-6+b2 Severity: wishlist In Emdebian, we use a wrapper script called emdebcheck (part of emdebian-tools) which performs a pre-upload check on the package using the .changes file and checks that if the upload was to proceed, all dependencies of the updated/new package would already be met in the archive.
It does this by retrieving the apt-cache data for the repository concerned, reading the list of packages from the .changes file and reading the package data using dpkg -f, removing any existing data in the archive for the same source package, appending the meta data obtained directly from the new packages and then passing the modified Packages file to edos-debcheck. i.e. the wrapper provides the ability to simulate Packages "patches" using the new metadata information coming from a set of .changes. In addition, the wrapper is able to only test particular packages, independent of a .changes file. e.g. in Emdebian, a -dev package does not have to be installable, the main lib package will need to be installable. So the method should also allow for an arbitrary set of package filenames to be supplied in place of the .changes file and process these in a similar manner: remove any existing data, replace with data read directly from the .deb files using dpkg and run the edos-debcheck - just as if the packages had been uploaded. Similarly, -doc packages are commonly ignored in Emdebian. edos-debcheck doesn't need to support such filtering on the .changes file, as long as the option(s) supports both a .changes file and individual package filenames. When passed a list of individual package filenames, edos-debcheck should process them all in a single check so that if foo depends on libbar which is present in the same list, the dependency is deemed satisfied (subject to correct versioning). If edos-debcheck did have such a wrapper, I would use it on my normal Debian uploads to unstable and I suspect others might too. I don't see that it does any harm if maintainers get a chance to see if their upload will actually be installable. It beats waiting around to see if the archive debcheck routines pick it up in DDPO. Currently, pbuilder tests can ensure that the package is buildable prior to upload but if a maintainer is making a variety of changes across a range of different packages, it is all to easy to upload bar before foo and find that bar is uninstallable due to the need for the updated foo. More information (and perl source code for the existing wrapper) are available at http://www.emdebian.org and in the emdebian-tools source package (debcheckout emdebian-tools). http://www.emdebian.org/emdebian/debchecks.html System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages edos-debcheck depends on: ii libc6 2.7-12 GNU C Library: Shared libraries edos-debcheck recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
