Re: Debuild issue
Hi Gregory,
On Mon, Dec 16, 2013 at 04:10:29PM -0800, Gregory Sharp wrote:
> >The source tarball should not contain the Debian revision number. The
> >"-1" in the end is the Debian package version which will be increased
> >if there would be a need to change the packaging.
> >
> >> Should I just rename the .tar.gz file and go about my business?
> >
> >Yes, definitely. The name should be
> >
> > plastimatch_1.5.15+dfsg.orig.tar.gz
>
>
> Definitely I was misunderstanding this. Now I understand and
>
> my problem was easily resolved.
>
>
> But I still have a kind of philosophical question.
>
> With change of Debian revision number, couldn't the content of source
> tarball change?
No. If the content of the source tarball changes it is per definition a
new upstream tarball and usually you will start with Debian revision
number 1 again.
> For example removing an additional file from upstream.
> Then you would have different Debian versions, with different
>
> source tarballs, but the same filename.
The source file name should change by increasing its version number.
>
> >I also think that if I will sponsor the package I will consider using
> >the enhanced uscan[1] to create the upstream source and allows better
> >compression option.
>
>
> The new uscan looks very promising. I would like to use it.
It is now in devscripts - unfortunately the option to choose the
compression method is not yet implemented (see #730768).
> So far I ran into two problems, so I stick with the old method
>
> until I can resolve.
>
>
> - In Files-Excluded I have a pattern doc/*.pdf, but one of the
>
> files with this pattern did not actually get removed.- I like to run get-orig-source as a shell script on the local file
> for testing if files are being removed correctly. But uscan seems only
> to support downloading the tarball from ftp or http.
Ahhh - that's a bug which seems to happen due to a space in the name of
the PDF in question. I need to track this down.
Currently the get-orig-script is written in a way that the downloader /
creator of the orig source tarball us using the new uscan feature if it
is installed on his machine. So if I download the tarball than it is
just used. This is a consequence of the fact that in our SVN workflow
the source code is not stored in SVN. It would be different when using
Git since there the original tarball is stored as pristine-tar inside
the Git repository.
> >For simplicity you can simply care for commiting your packaging code as
> >usual to SVN and ping this list. We will care for an upload.
>
> Thanks!! The new plastimatch seems ready. I hope error building
>
> on sparc, mips will be resolved.
I just uploaded. Thanks for your preparation
Andreas.
--
http://fam-tille.de
Reply to: