Hi Al, On Mon, Mar 21, 2005 at 01:25:47PM -0700, Al Stone wrote: > I'm a little puzzled. The package 'oprofile-source' does build > from source using dpkg-buildpackage. I just now built a brand new > sid chroot for i386, and ran 'dpkg-buildpackage' without a problem > (after adding build-essential and the build-deps).
> Perhaps it is not clear from the description, but this package is > only supposed to provide the _source_ needed to build an oprofile > kernel module for 2.4.x kernels. It is not supposed to provide > the modules themselves. Hence, I build the module packages personally > and upload them as a convenience for using, using the source provided > in 'oprofile-source.' Is it this module building part that you're > suggesting I automate? If it is, that's fine -- I just want to make > sure I understand what part is unacceptable. Yes, the problem is this second part, which results in binary packages in the archive that are not built as a result of ./debian/rules binary. This is non-standard, and in particular complicates the matter of security support post-release. If these are merely convenience packages that nothing depends on, it may be best to remove them from the archive and just ship the oprofile-source package. If so, please reassign this bug to ftp.debian.org. Cheers, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
