On Tuesday 2016-02-23 00:19, Terry Burton wrote:
Solution: Do not supply a DEBTRANSFORM-TAR line at all.
Thanks. I seem to recall that when DEBTRANSFORM-TAR is omitted debtransform croaks because it sees both _service:tar_scm:postscriptbarcode-{VERSION}.tar and_service:recompress:tar_scm:postscriptbarcode-{VERSION}.tar.gz as candidates for the tarfile. I will test this tomorrow as it's getting late.
The former will be deleted. At least that is what I can see from just looking at /srv/obs/sources/PKG.
You could just remove the debian/ directory from the source tarball. Many projects, so I believe, have done that over the last 15 years as they realized that distro-specific code should be with the distro instead, also because it has been a bitrot factor.
I agree that this is true for most standard packages especially if the authors do not care about packaging. BWIPP is an extensive resource programmed in an atypical programming language (PostScript) and uses custom compilation routines to prepare the resources in a number of formats.
What I gather from https://github.com/bwipp/postscriptbarcode/releases is that there appears to be no C source code, so the rest is data files which can be flung into an arbitrary directory that you just have to point ghostscript to. Iff there is something to actually build/compile, then, if a Makefile/configure/etc. thing is not sufficient generate it for the user, that Makefile (or lack thereof) should be revised. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org