Upload of python-networkx 1.9
Hi, As per #750233, I have uploaded python-networkx 1.9 in the DELAYED/2 queue. Considering the currently opened RC bug (ie: #750233), I couldn't wait for too long, otherwise risking AUTORM of some of my packages. The changelog is as follow: * Team upload. * New upstream release (Closes: #750233). * Ran wrap-and-sort. * debian/copyright in parseable format 1.0. * Added extend-diff-ignore = "^[^/]*[.]egg-info/" in d/source/options, and removed the clean of the egg-info folder. * Refreshed/rebased 10_doc_relocation, 20_example_dirs_remove and 30_use_local_objects.inv patches. * Removed 50_force_ordering_in_dict_to_numpy_array_functions.patch 55_fixups_to_numpy_array_functions_patch.patch 60_fix_tests_failure_due_to_py3.3_hash_randomization.patch applied upstream. * debian/control: removed python-support and added dh-python as build-dep. * Added python-3.4.patch (comes from the Ubuntu package). * Removed 40_no_setuptools_in_requires.txt (there's no setup_egg.py anymore in upstream source code). * Also cleans networkx/version.py, which is generated. * Also cleans test.*, doc/source/templates/gallery.html and fontList.cache. * Added do-not-use-sphinx_rtd_theme.patch. * debian/rules: do not use setup_egg.py, it's gone from upstream source. * Move all the doc generation stuff into the override_dh_sphinxdoc. * Removed obsolete XS-Python-Version: >= 2.6 X-Python3-Version: >= 3.2. * Adds using-local-mathjax.js.patch to avoid privacy breach in the doc. * Added missing --with python2. * Added debian/rules get-orig-src target to generate the orig.tar.xz file. * Added missing build-depends: python-decorator and python-numpydoc (needed for building docs). * Fixed watch file to handle the +dfsg1 mangling. I first tried to make the changes minimal, but it simply wasn't possible in this case. There was just too many things to do to have a working package. I tested building in a cowbuilder and it went fine. I also tested rebuilding some of the reverse dependencies that I knew were unit testing with networkx, and it went fine too. Note that since the pypi tarball was huge for no reason (it contained generated files from the documentation build process, leading to 35 MB of stuff instead of less than 1), so I used the git tag from github instead, to generate the orig.tar.xz. In the process I also cleaned some non-free files (minimized javascript). The process is now documented in debian/rules. [It would probably be best to have it done in a debian/repack file, using the watch file though, but I have no time for that yet.] If anyone opposes to this upload, it can be reverted/dcut. The diff of the debian folder is attached (missing the watch file fixes for the +dfsg1 handling). Cheers, Thomas Goirand (zigo) diff -u -N -r python-networkx-1.8.1/debian/changelog trunk/debian/changelog --- python-networkx-1.8.1/debian/changelog 2014-01-18 11:26:50.0 + +++ trunk/debian/changelog 2014-06-23 12:05:18.0 + @@ -1,3 +1,35 @@ +python-networkx (1.9+dfsg1-1) unstable; urgency=medium + + * Team upload. + * New upstream release. + * Ran wrap-and-sort. + * debian/copyright in parseable format 1.0. + * Added extend-diff-ignore = "^[^/]*[.]egg-info/" in d/source/options, and +removed the clean of the egg-info folder. + * Refreshed/rebased 10_doc_relocation, 20_example_dirs_remove and +30_use_local_objects.inv patches. + * Removed 50_force_ordering_in_dict_to_numpy_array_functions.patch +55_fixups_to_numpy_array_functions_patch.patch +60_fix_tests_failure_due_to_py3.3_hash_randomization.patch applied +upstream. + * debian/control: removed python-support and added dh-python as build-dep. + * Added python-3.4.patch (comes from the Ubuntu package). + * Removed 40_no_setuptools_in_requires.txt (there's no setup_egg.py anymore +in upstream source code). + * Also cleans networkx/version.py, which is generated. + * Also cleans test.*, doc/source/templates/gallery.html and fontList.cache. + * Added do-not-use-sphinx_rtd_theme.patch. + * debian/rules: do not use setup_egg.py, it's gone from upstream source. + * Move all the doc generation stuff into the override_dh_sphinxdoc. + * Removed obsolete XS-Python-Version: >= 2.6 X-Python3-Version: >= 3.2. + * Adds using-local-mathjax.js.patch to avoid privacy breach in the doc. + * Added missing --with python2. + * Added debian/rules get-orig-src target to generate the orig.tar.xz file. + * Added missing build-depends: python-decorator and python-numpydoc (needed +for building docs). + + -- Thomas Goirand Sun, 22 Jun 2014 07:11:42 + + python-networkx (1.8.1-1) unstable; urgency=low [ Jakub Wilk ] diff -u -N -r python-networkx-1.8.1/debian/control trunk/debian/control --- python-networkx-1.8.1/debian/control 2014-01-18 11:18:01.0 + +++ trunk/debian/control 2014-06-23 11:53:41.0 + @@ -4,10 +4,29 @@ Maintainer: Debian Python Modules Team Uploaders: Sandro Tosi Build-Depends: debhelper (>= 7.0.50~) -B
Re: Upload of python-networkx 1.9
On Wed, Jun 25, 2014 at 3:41 PM, Thomas Goirand wrote: > * New upstream release (Closes: #750233). I think you meant this instead: * New upstream release - Fixes test failures (Closes: #750233). https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-debian-changelog -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6eohzjttz4anqrrfkf+2tdyao_gw9ahaf4fvyvhpd3...@mail.gmail.com
Re: Upload of python-networkx 1.9
and where are the SVN commits for such changes? have you talked with upstream about the huge tarball? On Wed, Jun 25, 2014 at 9:41 AM, Thomas Goirand wrote: > Hi, > > As per #750233, I have uploaded python-networkx 1.9 in the DELAYED/2 > queue. Considering the currently opened RC bug (ie: #750233), I couldn't > wait for too long, otherwise risking AUTORM of some of my packages. The > changelog is as follow: > > * Team upload. > * New upstream release (Closes: #750233). > * Ran wrap-and-sort. > * debian/copyright in parseable format 1.0. > * Added extend-diff-ignore = "^[^/]*[.]egg-info/" in d/source/options, > and removed the clean of the egg-info folder. > * Refreshed/rebased 10_doc_relocation, 20_example_dirs_remove and > 30_use_local_objects.inv patches. > * Removed 50_force_ordering_in_dict_to_numpy_array_functions.patch > 55_fixups_to_numpy_array_functions_patch.patch > 60_fix_tests_failure_due_to_py3.3_hash_randomization.patch applied upstream. > * debian/control: removed python-support and added dh-python as build-dep. > * Added python-3.4.patch (comes from the Ubuntu package). > * Removed 40_no_setuptools_in_requires.txt (there's no setup_egg.py > anymore in upstream source code). > * Also cleans networkx/version.py, which is generated. > * Also cleans test.*, doc/source/templates/gallery.html and fontList.cache. > * Added do-not-use-sphinx_rtd_theme.patch. > * debian/rules: do not use setup_egg.py, it's gone from upstream source. > * Move all the doc generation stuff into the override_dh_sphinxdoc. > * Removed obsolete XS-Python-Version: >= 2.6 X-Python3-Version: >= 3.2. > * Adds using-local-mathjax.js.patch to avoid privacy breach in the doc. > * Added missing --with python2. > * Added debian/rules get-orig-src target to generate the orig.tar.xz file. > * Added missing build-depends: python-decorator and python-numpydoc > (needed for building docs). > * Fixed watch file to handle the +dfsg1 mangling. > > I first tried to make the changes minimal, but it simply wasn't possible > in this case. There was just too many things to do to have a working > package. I tested building in a cowbuilder and it went fine. I also > tested rebuilding some of the reverse dependencies that I knew were unit > testing with networkx, and it went fine too. > > Note that since the pypi tarball was huge for no reason (it contained > generated files from the documentation build process, leading to 35 MB > of stuff instead of less than 1), so I used the git tag from github > instead, to generate the orig.tar.xz. In the process I also cleaned some > non-free files (minimized javascript). The process is now documented in > debian/rules. [It would probably be best to have it done in a > debian/repack file, using the watch file though, but I have no time for > that yet.] > > If anyone opposes to this upload, it can be reverted/dcut. The diff of > the debian folder is attached (missing the watch file fixes for the > +dfsg1 handling). > > Cheers, > > Thomas Goirand (zigo) -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAB4XWXxf-Pyh=qbbl4bc-hvykpfoq_vu7kq0j-en7raufft...@mail.gmail.com
Re: Upload of python-networkx 1.9
On 06/25/2014 03:46 PM, Paul Wise wrote: > On Wed, Jun 25, 2014 at 3:41 PM, Thomas Goirand wrote: > >> * New upstream release (Closes: #750233). > > I think you meant this instead: > > * New upstream release > - Fixes test failures (Closes: #750233). > > https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-debian-changelog Thanks for this very good advice. Thomas -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53aac693.7010...@debian.org
ITP persistent and merging zope and python teams?
AFAICT, the persistent library is not yet packaged for Debian. https://pypi.python.org/pypi/persistent/4.0.8 I've search for existing packages and wnpp/ITP and not found anything. I think this is also required as a build dependency for zope.component. It's possible I've missed it though, so I'm going to file an ITP and work on the packaging, but please do let me know if it's already available. I'm aware of python-zope.component-persistentregistry, but that's a metapackage and not specifically related to the above. I plan on naming the source package `python-persistent` since claiming `persistent` seems a bit presumptuous. I'm going to put it under DPMT. As a side question, I wonder if it still makes sense to continue to segregate the ZTK packages under pkg-zope-developers. Why not fold all/most/some of those packages into DPMT? They're both under svn so it should be pretty easy to do, and the DPMT seems to be the much more active team than p-z-d. Thoughts? Cheers, -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140625105058.6716d...@anarchist.wooz.org
Re: Upload of python-networkx 1.9
On 06/25/2014 04:04 PM, Sandro Tosi wrote: > and where are the SVN commits for such changes? I was waiting for the 2 days delay before doing "git svn dcommit". It's in now. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ab06ee.5050...@debian.org
Networkx archive on pypi
Hi Aric, The Networkx archive on pypi, for the 1.9 release, is about 35 MB, while the one for 1.8.1 was a bit more than 800k. Having a look, it's looking like the PyPi tarball contains a lot of documentation generated files, which shouldn't be there. As a consequence, I used what is on github to package the new release 1.9 in Debian. Do you think you could fix the PyPi tarball in the future, to remove these? Also, there's some non-free files in your source code. Namely: - examples/javascript/force/d3 - doc/source/static/force/d3js These are considered binary blobs and non-free in Debian, so I had to remove them. It'd be nice if you could consider replacing these minimized javascript by the real source code instead. If you wish to still use minimized versions, you can use a compressor at build time in your setup.py. For example, you could use something like this to do the job: https://pypi.python.org/pypi/django_compressor/ however, it doesn't seem critical for your python module. Cheers, Thomas Goirand (zigo) P.S: Thanks a lot for writing in the Debian bug tracker about the fact that 1.9 fixed the FTBFS (Fail To Build From Source) bug. The new package using the 1.9 release will reach Debian in less than 2 days now. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ab092d.9010...@debian.org
Re: ITP persistent and merging zope and python teams?
On Wed, Jun 25, 2014 at 10:50:58AM -0400, Barry Warsaw wrote: > AFAICT, the persistent library is not yet packaged for Debian. > > https://pypi.python.org/pypi/persistent/4.0.8 > > I've search for existing packages and wnpp/ITP and not found anything. I > think this is also required as a build dependency for zope.component. It's > possible I've missed it though, so I'm going to file an ITP and work on the > packaging, but please do let me know if it's already available. > > I'm aware of python-zope.component-persistentregistry, but that's a > metapackage and not specifically related to the above. > > I plan on naming the source package `python-persistent` since claiming > `persistent` seems a bit presumptuous. I'm going to put it under DPMT. > > As a side question, I wonder if it still makes sense to continue to segregate > the ZTK packages under pkg-zope-developers. Why not fold all/most/some of > those packages into DPMT? They're both under svn so it should be pretty easy > to do, and the DPMT seems to be the much more active team than p-z-d. > Thoughts? As I mentioned before, I think it's a great idea :) I think that you should give it some time for any objections to be raised. If none are, you should go ahead. Perhaps seek out Gediminas' opinion. As he is the next most active member of pkg-zope-developers and would probably have to join DPMT to carry on with the ZRK package maintenance. > > Cheers, > -Barry > > ___ > pkg-zope-developers mailing list > pkg-zope-develop...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140625193113.GA60845@Brians-MacBook-Air.local
Re: Networkx archive on pypi
Hi Thomas, Thanks for pointing out my mistake in the PyPi tarballs. And I will fix the non-free binary blob issue so you won't have the same problem in the next release. Please let me know if there is anything else we can do to help. Thanks, Aric On Wed, Jun 25, 2014 at 11:38 AM, Thomas Goirand wrote: > Hi Aric, > > The Networkx archive on pypi, for the 1.9 release, is about 35 MB, while > the one for 1.8.1 was a bit more than 800k. Having a look, it's looking > like the PyPi tarball contains a lot of documentation generated files, > which shouldn't be there. > > As a consequence, I used what is on github to package the new release > 1.9 in Debian. Do you think you could fix the PyPi tarball in the > future, to remove these? > > Also, there's some non-free files in your source code. Namely: > - examples/javascript/force/d3 > - doc/source/static/force/d3js > > These are considered binary blobs and non-free in Debian, so I had to > remove them. It'd be nice if you could consider replacing these > minimized javascript by the real source code instead. If you wish to > still use minimized versions, you can use a compressor at build time in > your setup.py. For example, you could use something like this to do the job: > https://pypi.python.org/pypi/django_compressor/ > > however, it doesn't seem critical for your python module. > > Cheers, > > Thomas Goirand (zigo) > > P.S: Thanks a lot for writing in the Debian bug tracker about the fact > that 1.9 fixed the FTBFS (Fail To Build From Source) bug. The new > package using the 1.9 release will reach Debian in less than 2 days now. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caasinjumazwdk2oyepkzcxohkfxtzhww0__vm8gwaum-9sp...@mail.gmail.com
