[Pkg-electronics-devel] gnucap-python package rfs

[Ruben Undheim]

Hi Felix,

> > 1. Please make the package build first. I tried with "gbp buildpackage" on the tip
> > of the master branch, but it barely starts. By reverting one commit, it gets
> > further, but still it fails building:
> > 
> > 
> > ../configure: line 3823: python3.7: command not found
> > configure:3825: $? = 127
> > configure:3830: result: no
> > configure:3832: error: Python interpreter is too old
> 
> this is strange.
> 
> for me, both "dpkg-buildpackage -rfakeroot", and "gbp buildpackage" work
> on master (commit 9029e7579). certainly after git clean -dxf or after
> creating a fresh clone + pristine-tar checkout.

pristine-tar checkout did the trick.. After you added the "debian/gbp.conf"
file, a clean "gbp buildpackage" works (if first deleting the .orig.tar file
which had already been generated). But although it now starts, it is not
an ideal solution to have pristine-tar containing the diff which is necessary
to build..  It should be investigated a bit.

> also odd: the python versions should only come from pyversions and
> py3versions (top of d/rules). on my system, only existing interpreters
> are included: 2.7, 3.6, 3.7. i must be missing something.

Try adding python3.7-dev, python3-numpy and python-numpy to build-dependencies in
the control file. python3.7 is not yet default in Debian sid.

You should set up either pbuilder or sbuild to test build in a clean environment
to verify the build-dependencies. pbuilder is fastest to use via "cowbuilder",
and cowbuilder is easy to setup.

> > 2. Also, please change the version 0.0.0 to something containing the date and
> > SHA1 of the lastest commit (since upstream probably does not make releases)
> 
> a tag in the upstream repo is considered a release, see
> debian/README.source. in fact, 0.0.0 is the release version for the
> first release, in the usual sense.

Makes sense, but since I did not know where to find the upstream source, I did
not have the chance to check it.
 
> > 3. Please put a file called "gbp.conf" in the debian folder with this content:
> > 
> > [DEFAULT]
> > pristine-tar = True
> 
> done.

Thanks

> > 4. I cannot find the upstream source in http://gnucap.org which is listed as
> > "Homepage" in debian/control, and "Source" in debian/copyright. Is this really
> > the correct upstream? Please add a debian/watch file which uniquely describes
> > where to find the upstream source.
> 
> gnucap is a collaborative project, gnucap.org hosts the wiki for
> everything related. i have now put in [1] as the homepage, which seems
> to make more sense. hope that this is acceptable somehow.
> 
> I will figure out watch, so it finds tags in the corresponding git repo.
> (i would prefer a tarball release, but neither do i know where to host
> it, nor does it seem to be common practice anymore.)

Thanks for background info. Would be great with a watch file which exactly
generates your .orig file.

> > When it builds, I will also have a look at the other formalities in the
> > package.
> 
> thanks. i will try to build on some other system. maybe i can reproduce
> the build issues or find others along the way.

I recommend cowbuilder:

 sudo apt install cowbuilder
 sudo cowbuilder --create --distribution sid
 sudo cowbuilder --build gnucap-python_0.0.0-1.dsc


Thanks :)

Cheers
Ruben