Hi all I've previously asked a question about this but didn't get any bites. I would like to know what the reasoning is for the use of 'packagename.dsc' files on Build Service. As far as I can tell, the Debian equivalent of 'packagename.spec' is a set of several files, starting with these three: 1. debian.changes 2. debian.rules 3. debian.control These correspond, as I understand it, to (1) %changelog, (2) %build and %install sections, and (3) the package headers including 'Requires' and '%description' etc. As far as I can tell, the packagename.dsc file is produced by the build process in the same way that RPM produces a .src.rpm file. In other words, it is a by-product of the build, not one of the source files. You can generate the .dsc file from the above three files, but not the other way around. There are some more files required for debian packaging in some cases, for which purpose the 'debian.tar.gz' mechanism provided by Build Service seems to be quite satisfactory. I would propose that before the Build Service evolves too far, it might be worth considering revising the way that Debian packages are built here, for consistency in the approach across different distros. Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org