Re: [MoM] Pristine Tar Updated and Uploaded

[Andreas Tille <andreas@an3as.eu>]

Hi Ian,

On Sun, Jun 29, 2014 at 09:54:55PM -0700, Ian Wallace wrote:
> Andreas - I can't thank you enough for helping with suggestions and emails
> to fix the package.  I downloaded the changelog, copyright, etc.  Here's
> what I did to upload the pristine tar:
> 
> While on the 'master' branch in the openemr dir I did:
> mk-origtargz --repack ../openemr-4.1.2p7.tar.gz
> 
> Which produced:
> ../openemr-4.1.2p7+dfsg.orig.tar.gz

You could also add the --compress xz option to pristine-tar which would
give you a better compression.  However, I'd recommend to leave it for
the moment as is since it will mots probably not the last tarball we
need to inject.  Simply consider xz compression for the future.
 
> This stripped out the phpmyadmin files, I then:
> git rm -r phpmyadmin

As far as I know this step is not needed since the import-orig step does
the removal.  But it surely does not harm thought.
 
> on mater branch and committed the changes.
> git checkout upstream
> git import-orig --pristine-tar ../openemr_4.1.2p7+dfsg.orig.tar.gz

Hmmmm, as said previously I would not consider myself as git /
git-buildpackage expert but I think you coule (should ?) do this
step in branch master.

> git commit -m "Adding upstream 4.1.2p7+dfsg."

At least at my side I never had to do a manual commit -
`git import-orig` should do this for you.

> git push

The remote branch is lacking the according metadata:

openemr(master) $ git checkout pristine-tar
openemr(pristine-tar) $ ls
openemr_4.1.2.orig.tar.gz.delta  openemr_4.1.2.orig.tar.gz.id

May be you should try

   git push --all

??

> Things appear to build now with:
> debuild clean; debuild

Since the pristine-tar metadata is missing I can not reproduce this via
git-buildpackage but it is good that you can do this step.
 
> Which produces the usual errors/warnings for JavaScript libraries without
> source, etc.  At least the phpmyadmin files are no longer in the repository.

:-)
 
> Tomorrow I will start working on correcting some of the other
> errors/warnings.
> 
> Let me know if this is not the correct method.  I am unclear as to what
> should be in the 'pristine-tar' branch.  Was that where I was supposed to
> upload things?  I have to admit this is the first time I've done this so it
> seems a bit confusing.

Usually you do not need to do anything manually with pristine-tar.  Since
nothing endedt up in the remote repository please for a check do the same
as me above and

   git checkout pristine-tar
   ls

to see if at least your local repository is OK.  If this is the case you
can probably also `git push` from here.  If everything goes smoothly than
a simple

   git import-orig --pristine-tar <origtar>
   git push [--all]

should be perfectly sufficient.

Remark:  The metadata in the pristine-tar branch are needed to enable
git-buildpackage creating a md5sum identical tarball from the upstream
code inside the git archive.

Kind regards

       Andreas.

-- 
http://fam-tille.de