[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: scmbug



> > > 1. Do not make package native.
> > 
> > What do I need to do to change the package into being non-native ?
> > How/where do I specify the non-native version number ?

What do I need to do to change the packaging into being non-native ?

 
> > > 2. Please create proper debian directory and not by symlink to some
> > > directory with templates and other crap in it.
> > 
> > Why not ?
> 
> Because it breaks some tools which check archive and makes NMUs
> needlessly complicated.

It sounds like some tools need to be corrected.

For example, "man dpkg-buildpackage" reports a "-c" parameter for
specifying the control file from a directory OTHER than debian/. But
this flag is not available for dpkg-buildpackage.

One should be able to provide those files in a directory with any name
they want.

> > Debian is not the only distribution this system is packaged for. I don't
> > like to have a top-level directory called "debian" in the source code
> > repository. Instead, I have a directory called packaging/debian.
> 
> There is no need to have debian packaging things in upstream.

I disagree.

> > There are no hardcoded paths in the build process. I'm not sure why this
> > error occurs. 
> 
> Have you looked at Makefile in your package? It contains this path on
> dozens of lines.

Thanks, this was an issue with cleaning up. Corrected now.

> > > 7. Source should match the one available on upstream website:
> > > $ md5sum SCMBUG_RELEASE_0-26-13.tar.gz scmbug_0.26.13.tar.gz
> > > a5c92c23e8c2fa5f67a389e12c04aacd  SCMBUG_RELEASE_0-26-13.tar.gz
> > > d5645be5bc4a620f8f9db67a11662f0b  scmbug_0.26.13.tar.gz
> > 
> > I don't understand how dpkg-buildpackage prepared this new .tar.gz file.
> 
> You should not make native package. Then tarball would match the
> original one and all packaging changes will be in separate file.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: