Hi! There are few issues related to debian files. Let me know if I misunderstood something. 1. Unexpected errors when debian directory and files are included in tarball *and* debian files ( these debian. prefixed ) added to project at the same time. There should be clear distinction whether the ones added to project or those included in tarball should be used. At least user friendly error should be thrown with any information that files conflict each other. 2. No way to define architecture in control files. If i386 is used it fails on building amd64 packages. It requires special ugly hacks made in rules file to automatically define/replace packages' architecture. 3. Dependencies taken into account must be included in dsc file which is absolutely not debian way as devel packages also must be included there. Build dependencies and normal binary deps should be included in control file but those are simply and silently ignored. 4. dsc file itself is needed if package is build from source package. It's absolutely not required if built from scratch. So either dsc is taken into account and source packages are also built or this one is ignored in favour of custom debian files. I expect that system doesn't focus on debian packages, but there must be few hacks added to build "propper" debs. On the longer term, package built this way are not valid debian packages and build proccess should be refactored if one would like to have lintian or linda error&warning free binaries. Piotras --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org