Bug#973435: biosig build-depends on python3-all-dev, but only builds for the default python3 version
On Thu, Nov 12, 2020 at 11:46:43PM +0100, Alois Schlögl wrote:
>
> Thanks for the hint on py3versions, this helped solving the issue for v2.1.0.
You are welcome.
> I believe bug #972684, #973435 are fixed now.
Hmmm, regarding bug #972684: In d/rukes you use
override_dh_auto_build:
... py3versions -d ...
(so you build against default Python3 version) and
override_dh_auto_install:
...
$(cd biosig4c++/python && foreach py,$(shell py3versions -s), (${py}
setup.py install --prefix=debian/${py}-biosig) )
an install for more than one version - specifically install to
non-existing packages (python3.8-biosig and python3.9-biosig but
we have only python3-biosig!)
Without trying to build this - it looks not like a proper solution
and I need to admit I can not spent any more time on this package
which I absolutely not use myself. Please ask Yaroslav for sponsering.
> Debian packages of biosig 2.1.0-1 are now availab
> https://pub.ist.ac.at/~schloegl/biosig/debian/unstable/?C=M;O=D
I do not think it is a good idea to provide Debian packages on
other places than official Debian mirrors.
Kind regards
Andreas.
>
> On 11/10/20 11:28 AM, Andreas Tille wrote:
> > Hi again,
> >
> > On Tue, Nov 10, 2020 at 10:10:21AM +0100, Alois Schlögl wrote:
> > > Ok, I see. Biosig can be build with any python version (it is just using
> > > the
> > > general API for module extension which is not)
> > >
> > > That means, building it for any python version will work like this
> > >
> > > (cd biosig4c++/python && python3 setup.py sdist )
> > >
> > > (cd biosig4c++/python && python2.7 setup.py install )
> > This is not needed since python2.7 will be removed.
> >
> > > (cd biosig4c++/python && python3.8 setup.py install )
> > > (cd biosig4c++/python && python3.9 setup.py install )
> > This would be
> >
> > for py in $(py3versions -s) ; do
> > (cd biosig4c++/python && $py setup.py install )
> > > The question is: when packaging this in debian, how to tell which python
> > > versions are available, and how to trigger the build for that version ?
> > See above.
> > > Will there be a python3.8-biosig and python3.9-biosig package, and how
> > > does
> > > this affect debian/control ?
> > It does not affect debian/control but debian/rules. OK, if you want
> > the *easy* solutition just use
> >
> > s/python3-all-dev/python3-dev/
> > in d/control, which solves the issue since only the default python3
> > will be used (py3versions -d). This is the *quick* fix for the bug.
> > It simply depends what you *want* from your users. I hope Michael
> > or Yaroslav could comment on this. I'm out at this point since I'm
> > not a user of this package.
> >
> > > I've reverted the change, and partially fixed the build. Some issues
> > > remain
> > > unsolved - as described before.
> > Hope this helps. Other hints might be given by
> > debian-pyt...@lists.debian.org.
> >
> > Kind regards
> >
> > Andreas.
> >
>
--
http://fam-tille.de
Bug#973435: biosig build-depends on python3-all-dev, but only builds for the default python3 version
Thanks for the hint on py3versions, this helped solving the issue for v2.1.0. I believe bug #972684, #973435 are fixed now. Debian packages of biosig 2.1.0-1 are now availab https://pub.ist.ac.at/~schloegl/biosig/debian/unstable/?C=M;O=D On 11/10/20 11:28 AM, Andreas Tille wrote: Hi again, On Tue, Nov 10, 2020 at 10:10:21AM +0100, Alois Schlögl wrote: Ok, I see. Biosig can be build with any python version (it is just using the general API for module extension which is not) That means, building it for any python version will work like this (cd biosig4c++/python && python3 setup.py sdist ) (cd biosig4c++/python && python2.7 setup.py install ) This is not needed since python2.7 will be removed. (cd biosig4c++/python && python3.8 setup.py install ) (cd biosig4c++/python && python3.9 setup.py install ) This would be for py in $(py3versions -s) ; do (cd biosig4c++/python && $py setup.py install ) The question is: when packaging this in debian, how to tell which python versions are available, and how to trigger the build for that version ? See above. Will there be a python3.8-biosig and python3.9-biosig package, and how does this affect debian/control ? It does not affect debian/control but debian/rules. OK, if you want the *easy* solutition just use s/python3-all-dev/python3-dev/ in d/control, which solves the issue since only the default python3 will be used (py3versions -d). This is the *quick* fix for the bug. It simply depends what you *want* from your users. I hope Michael or Yaroslav could comment on this. I'm out at this point since I'm not a user of this package. I've reverted the change, and partially fixed the build. Some issues remain unsolved - as described before. Hope this helps. Other hints might be given by debian-pyt...@lists.debian.org. Kind regards Andreas.
Bug#973435: biosig build-depends on python3-all-dev, but only builds for the default python3 version
Hi again, On Tue, Nov 10, 2020 at 10:10:21AM +0100, Alois Schlögl wrote: > > Ok, I see. Biosig can be build with any python version (it is just using the > general API for module extension which is not) > > That means, building it for any python version will work like this > > (cd biosig4c++/python && python3 setup.py sdist ) > > (cd biosig4c++/python && python2.7 setup.py install ) This is not needed since python2.7 will be removed. > (cd biosig4c++/python && python3.8 setup.py install ) > (cd biosig4c++/python && python3.9 setup.py install ) This would be for py in $(py3versions -s) ; do (cd biosig4c++/python && $py setup.py install ) > The question is: when packaging this in debian, how to tell which python > versions are available, and how to trigger the build for that version ? See above. > Will there be a python3.8-biosig and python3.9-biosig package, and how does > this affect debian/control ? It does not affect debian/control but debian/rules. OK, if you want the *easy* solutition just use s/python3-all-dev/python3-dev/ in d/control, which solves the issue since only the default python3 will be used (py3versions -d). This is the *quick* fix for the bug. It simply depends what you *want* from your users. I hope Michael or Yaroslav could comment on this. I'm out at this point since I'm not a user of this package. > I've reverted the change, and partially fixed the build. Some issues remain > unsolved - as described before. Hope this helps. Other hints might be given by debian-pyt...@lists.debian.org. Kind regards Andreas. -- http://fam-tille.de
Bug#973435: biosig build-depends on python3-all-dev, but only builds for the default python3 version
Package: src:biosig Version: 2.0.6-1 Severity: normal User: debian-pyt...@lists.debian.org Usertags: python3.9 biosig build-depends on: python3-all-dev but only builds for the default python3 version. So either build for all supported python3 versions, or replace the python3-all-dev b-d with python3-dev.
