Re: Bug#782543: ITP: gpaw -- DFT and beyond within the projector-augmented wave method
On Fri, Jul 10, 2015 at 04:22:22PM +0200, Marcin Dulak wrote:
> > gbp clone ssh://git.debian.org/git/debian-science/packages/gpaw.git
>
> > (the important part is "gbp clone" - the ssh: URL is just to get a
> > non-annonymous clone to enable you commiting.)
> >
> > > $ gbp buildpackage
> > > gbp:error: upstream/0.10.0.11364 is not a valid treeish
> >
> > Sure. Git fetches only master branch. Simply use gbp (or fetch branches
> > upstream and pristine-tar manually at your preference).
> >
>
> i don't understand the process, but my impression is that somehow
> *orig.tar.gz is missing.
> What I see is that the error "gbp:error: upstream/0.10.0.11364 is not a
> valid treeish"
Strange. Could you please confirm that you cloned the repository in the
manner I suggested (first line of my quote)?
> goes away if I create gpaw_0.10.0.11364.orig.tar.gz in the .. directory.
This should not be possible since if you have a proper pristine-tar
branch - and you will have it if you use `gbp clone` than this is
created. The md5-identical creation of a tarball is the only purpose of
the pristine-tar branch. To be sure verify via
git branch
that this branch exists.
> $ git checkout upstream && ls && git checkout master
> Switched to branch 'upstream'
> Your branch is up-to-date with 'origin/upstream'.
> build config.py configuration.log debian LICENSE README.txt
> setup.py
> c config.pyc customize.py gpaw PKG-INFO setup.cfg tools
> Switched to branch 'master'
> Your branch is up-to-date with 'origin/master'.
>
> So the upstream branch contained the gpaw source.
Sounds correct.
> Then I did, inspired by
> http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html
> :
> $ gbp import-orig ../gpaw_0.10.0.11364.orig.tar.gz
This links gives a wrong inspiration since it is missing the
--pristine-tar option which is essential to recreate the tarball.
> What is the upstream version? [0.10.0.11364]
> gbp:info: Importing '../gpaw_0.10.0.11364.orig.tar.gz' to branch
> 'upstream'...
> gbp:info: Source package is gpaw
> gbp:info: Upstream version is 0.10.0.11364
> gbp:info: Merging to 'master'
> gbp:info: Successfully imported version 0.10.0.11364 of
> ../gpaw_0.10.0.11364.orig.tar.gz
> $ git push
> $ rm -rf ../gpaw*
> $ cd ..
> $ gbp clone ssh://git.debian.org/git/debian-science/packages/gpaw.git
> $ cd gpaw
> $ gbp buildpackage
> gbp:error: upstream/0.10.0.11364 is not a valid treeish
Are you sure you are in the master branch and the debian/ dir exists?
> So the orig.tar.gz seems to be needed still. With it in .., gbp
> buildpackage gives:
> ...
> E: gpaw: missing-dependency-on-numpy-abi
> ..
>
> In order to perform the build on Debian 7 I configure the Debian 7
> repository from:
> https://wiki.fysik.dtu.dk/ase/download.html#installation-with-package-manager-on-linux
> and: sudo apt-get install -y python-ase gpaw-setups
Apropos gpaw-setups: Since I can run `gbp buildpackage` in my clone her
I did so but pbuilder was running into the following error:
pbuilder-satisfydepends-dummy : Depends: gpaw-setups which is a virtual package.
It seems you need to package gpaw-setups first if this is a
build-dependency of gpaw. (BTW, please remove the ',' at the end
of the last Build-Depends.)
> this should be fixed now.
It is. :-)
Hope this helps
Andreas.
--
http://fam-tille.de
Reply to: