[Neurodebian-devel] Uploading pyqtgraph packages

[Luke Campagnola]

OK! After much reading and re-reading and soul-crushing failure (it's ok; I
have no soul to crush  :)  I have managed this:

python-pyqtgraph_0.9.8-1_amd64.build    OK      5:13.29 real, 58.24 user,
15.27 sys, 959328 out
python-pyqtgraph_0.9.8-1~nd60+1_amd64.build     FAILED  0:00.03 real, 0.00
user, 0.00 sys, 0 out
python-pyqtgraph_0.9.8-1~nd70+1_amd64.build     FAILED  4:49.38 real, 30.94
user, 9.31 sys, 989024 out
python-pyqtgraph_0.9.8-1~nd80+1_amd64.build     OK      7:36.04 real, 57.46
user, 18.46 sys, 949448 out
python-pyqtgraph_0.9.8-1~nd+1_amd64.build       OK      5:52.32 real, 58.42
user, 16.64 sys, 962472 out
python-pyqtgraph_0.9.8-1~nd10.04+1_amd64.build  FAILED  0:48.73 real, 4.98
user, 22.58 sys, 128552 out
python-pyqtgraph_0.9.8-1~nd12.04+1_amd64.build  OK      6:00.95 real, 51.42
user, 16.41 sys, 938288 out
python-pyqtgraph_0.9.8-1~nd12.10+1_amd64.build  OK      4:45.70 real, 43.95
user, 12.12 sys, 873248 out
python-pyqtgraph_0.9.8-1~nd13.04+1_amd64.build  OK      5:15.18 real, 49.03
user, 12.15 sys, 966632 out
python-pyqtgraph_0.9.8-1~nd13.10+1_amd64.build  OK      5:12.23 real, 50.29
user, 12.98 sys, 977928 out

I now have a debian branch pushed to github as you suggested, and the
contents of debian/ is based on this document:
https://wiki.debian.org/Python/LibraryStyleGuide?action=recall&rev=21

The packages are lintian clean, but documentation is being packaged
incorrectly into python-pyqtgraph and I haven't done anything about the
examples yet.

I was only able to locate an error message for one of the failures:

  nd+ubuntu lucid:
  The following packages have unmet dependencies:
    pbuilder-satisfydepends-dummy: Depends: python-all (>= 2.6.6-3~) but it
is not installable
                                 Depends: python-sphinx (>= 1.0.7+dfsg) but
it is not installable

Obviously this might be fixed in debian/control, but I'm not sure what the
correct version numbers should be.. (and if that's ubuntu 10.04, then we
can probably just skip it?)


On Tue, Jan 14, 2014 at 11:37 PM, Yaroslav Halchenko
<debian at onerussian.com>wrote:

> >      >    From there you can run `python setup.py sdist deb
> >      --force-version=0.9.8`.
> >      >    The 'deb' command just creates a deb_build directory and
> populates
> >      it with
> >      >    the necessary pieces before calling `dh -us -uc`.
>
> >      brrr ;-)  why not just debian/ directory?  your setup would
> >      complicate contributions from debian folks etc... you would need to
> >      provide
> >      us the generated source package anyways.  I would recommend just
> >      carrying debian/ and using git-buildpackage
>
> >    I like to keep the package root as clean as possible. For a package
> that
> >    claims to run on all flavors of windows, osx, and linux, it doesn't
> make a
> >    lot of sense (to me) for 'debian' to appear at the root.  Can you give
> >    examples of how this complicates contributions from debian folks? In
> any
> >    case, at least the changelog needs to be generated, so *some* command
> must
> >    be run.
>
> it doens't have to be anywhere actually.  You would just need a separate
> branch -- e.g. debian -- where you will keep your packaging.
> I believe I had some arguments for docker.io guys somewhere.. e.g.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706060#30


I was not able to get git-buildpackage to work; ran into a variety of
problems before deciding that the currently-working `python setup.py deb`
is good enough, and probably does more or less what git-buildpackage would
have done (it has many other features that do not interest me at present).


Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/neurodebian-devel/attachments/20140122/da17ab86/attachment.html>