Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
On Sat, Sep 13, 2014 at 10:57:16PM +0200, Vincent Prat wrote: * I would put the http_proxy='127.0.0.1:9' as general line in rules, to make sure that during auto-build nothing is retrieved (move from the sphinx documentation) pybuild already does that for commands it runs. -- WBR, wRAR signature.asc Description: Digital signature
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Vincent, Am 13.09.2014 um 22:57 schrieb Vincent Prat: I thought the package was ready, but while testing it with pbuilder, I encountered an error, apparently with astropy-helpers documentation routines: Exception occurred: File /usr/lib/python2.7/dist-packages/astropy_helpers/sphinx/ext/automodsumm.py, line 419, in generate_automodsumm_docs name, obj, parent = import_by_name(name) ValueError: too many values to unpack Can you reproduce it? There is a new version 0.4.2 of astropy-helpers available upstream. Yesterday, my package (0.4.1) was accepted to Debian, so I will update it today or tomorrow. Let's see if it works (I remember that one reason for the update were some sphinx problems). Best Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUFVVqAAoJEHEVr9B3ENz3ex8P/1Am264sYfHwgMdLn0P+6AQd vz8S9mFJgeoK65Q37p86P8L8Kt0X2nt5U/ztjX/1yeqMy1+eupZhB4+HFkopfkAl gtpC7Jv/Yp9OzXF/4eybNvQoUE+NBRYH+R+sGsbTjxz5sRQhxNqQqongNZkZaN8z +nIDEtiPbQzSFEpLvssQpTapDQdWZ/To2rmLKKSQAwJ41gT0fAxXa/9JQ4xdsCq0 R4eeDZx1CssYJvQSGhFmq96fvtpXHSn1TCA09AL13gvzol3YeY9oeRdHVeCpeG++ KNjBPNysyf02zWcOiMu5s0Z/XImn44YrmWPhOb61S2qPNZMCLjFkB+aoOz4ZPjE0 xk5vx3NnMw2uwmQA5GEYFkii0L7CNSDFtiXOKTkJhzCBjGBIG5Fj7lGxZ7qizaJr kqdSL5Rjkw4AnZGLG2T0kuukzkc3M59hEgDq90p7eU0X1TzoRYKu+T0WaQIsmylP XUNQLv/S0IyoRymnHGLLLmFViBrxJA594pzWymhqNH7zfZxJA/+M5rXGcYc5rbdv wMZk8hK8MHs8OWsqBlvLQFZFfO/M5XZVDSFZKdgRUAok4JrNivzq7NzU+aQN3gQt J5N2+i0Ni5ynRzfX5L6Z0SHfr/fpyjEY+ybHejfKL4R/ZKEr7mDXfbvzKMwdsczH 9vzjZgROPfrt+N/kdqN0 =lhmM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hi all, Maybe one step back, why does casacore-data depend on casacore? It is just some data that could be used without casacore itself right? Why not remove the dependency? greetings, - Gijs 2014-09-14 8:22 GMT+02:00 Andrey Rahmatullin w...@debian.org: On Sat, Sep 13, 2014 at 10:57:16PM +0200, Vincent Prat wrote: * I would put the http_proxy='127.0.0.1:9' as general line in rules, to make sure that during auto-build nothing is retrieved (move from the sphinx documentation) pybuild already does that for commands it runs. -- WBR, wRAR -- Gijs Molenaar http://pythonic.nl http://gijs.pythonic.nl
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 14.09.2014 um 10:49 schrieb Gijs Molenaar: Maybe one step back, why does casacore-data depend on casacore? It is just some data that could be used without casacore itself right? Why not remove the dependency? The reason is that you need to build the casacore-data package from source. The source files are the ones that may be downloaded by casacore's measures_data.csh (right?) To build the package one needs to apply the measures_data program to it, which is integrated in the casacore framework, and this creates the dependency. Best regards Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIbBAEBAgAGBQJUFVeHAAoJEHEVr9B3ENz3SbsP+KVG5IiQnvbrPcnVpP3/pEJk z1U6rkcd9/mTnZ7JoUMAFgZILYJtlR3SRBqRTXxF7jtyJAOfzB7Wj57A2DJ3HUFX aOSrs1b1+vGCZOygFvnipew60zwtpMG0jWM8GWa68nUl3+LbUbiIoy7yOEI+t7Se R8L5EY6eGqfmWyB7h7ty1tMF7nRGEEYzIq5n+j+FcaYxC0ADRB7eLLvThpnLMDqJ y3lusYVR42SFFUizResH1cNppJPiCYMg944PS4DF1SXntzUHzdoLFip/vffY1Y+M JWhOZH76/WGUdjVBHtTaBB621Xb8hjdX3vQex0UaRptc759CXyH8ntRgyXbafc+H LnhQ4s6ZwyurUbvh5LU/uVq6jwSOJGYg67bmUhSOSTx88NDFJtjyrxhUx+kfIrAq FavnlDyd0B+fSmF6STmk4peUEaLg5VBOREbrgRnzhhsLRsycXpNp2TdHTK9uGfzf RG+4aiN04CH6p5toJ01/Wml6USpi8g1TMPTVinHGFU3hkWSdwJnCEKDgyqyHIrxO B0oREyTk12NCPFZ0aA2mtXjIw5e36OKt6VHnZ3AW14MEDAcqxh8+IYHJ2SFjXmDq 9iytCPR5TfUXX2CS29JUQQ6RThECWBh6jHDloPXt+/++qGxWdjQE0DRy7txXU62t erZ0bXy9bG9jiUSnZio= =SyBN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Vincent, Am 13.09.2014 um 22:57 schrieb Vincent Prat: I have applied all suggested changes. OK. I thought the package was ready, but while testing it with pbuilder, I encountered an error, apparently with astropy-helpers documentation routines: [...] ValueError: too many values to unpack Can you reproduce it? I tried with 0.4.2 and could build it without the error. However, I still get the following lintian error (and pedantic warning): E: astroquery source: source-is-missing astroquery/splatalogue/data/species.json P: astroquery source: source-contains-prebuilt-javascript-object astroquery/splatalogue/data/species.json means line length is about 16184 characters Could you check with upstream where this file comes from, and either override these, or provide the source file? Best Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUFXjSAAoJEHEVr9B3ENz3i2oQAJcgAPzb0uuet0fsTAH3swS1 pUS2L4xDzdQVLfHEawgh/5Y8mtqWmsq7YSEKIoq3dhpU/Qn4NL7Ae/XJVyOfOJTn e8W/EQ8J0DHNBDAWKV1RVuvm+NW328e8dMo2g5GJxhpb2n/76weoH3vfiHpE6EIo qDGVtWvVnvM9fk3j0IzoYDzk1Dxd4dgphYdTccdPBslgwRvoW6PIzgfTUUFGmfT8 SfsgUz2jM+GZgbh59kIxXCtVdo5nIW53/HgMNRoJJa0oG/SD+ZupZTFlnRddaJRA amQHzSRbij1uz/enrQwcLKZ7Oc35ByucZLe9oS8+fmYzayCwxgGyBYycPapIglUf blg8wfHn62M540+d6MdqvhGxmUo27KQ+Lbkk1AOt4DT/bz31MNqfHAvCoL5bqFkr tIy7qDN3IFetqjNGNmQ4i48JBqfhpuOk78gy2wrZAcoe5TWH1EBBH4AeQ4D6xAMs oYAbAnp/hLCXNEKHiJwkBflZqO4lW3mDf3+SQTGuN6YfAlCzmuEYvqvDm0RBMJRg IymalvFpXBGcGRN6UA/GWT91mrqGnbTydxxD3GvpRR5M1PRgFQKEpOXSsNrGGVPk XU76VePy46hPwwbl1vqzPu7yXO3uJcGLXQq5/EjvuF3EDNIPcGnIVy4MTgvcwHrh NFaQZKEoFepYXAqv84RK =tb7G -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
casacore data is this page: ftp://ftp.atnf.csiro.au/pub/software/measures_data/measures_data.tar.bz2 linked from this page: https://code.google.com/p/casacore/wiki/BuildInstructions According to astron is updated weekly, but in practice that is not the case. The people at astron use measures_data.csh to create the new measures data. But since they didn't update the measures data for a while I created a new measures_data manually. So the way I see it, casacore is required to create the measures_data (casacore-data) source tarball, but there is no build dependency on it. I'll go to astron next week and I hope to get some more clarity about these issues. 2014-09-14 10:53 GMT+02:00 Ole Streicher oleb...@debian.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 14.09.2014 um 10:49 schrieb Gijs Molenaar: Maybe one step back, why does casacore-data depend on casacore? It is just some data that could be used without casacore itself right? Why not remove the dependency? The reason is that you need to build the casacore-data package from source. The source files are the ones that may be downloaded by casacore's measures_data.csh (right?) To build the package one needs to apply the measures_data program to it, which is integrated in the casacore framework, and this creates the dependency. Best regards Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIbBAEBAgAGBQJUFVeHAAoJEHEVr9B3ENz3SbsP+KVG5IiQnvbrPcnVpP3/pEJk z1U6rkcd9/mTnZ7JoUMAFgZILYJtlR3SRBqRTXxF7jtyJAOfzB7Wj57A2DJ3HUFX aOSrs1b1+vGCZOygFvnipew60zwtpMG0jWM8GWa68nUl3+LbUbiIoy7yOEI+t7Se R8L5EY6eGqfmWyB7h7ty1tMF7nRGEEYzIq5n+j+FcaYxC0ADRB7eLLvThpnLMDqJ y3lusYVR42SFFUizResH1cNppJPiCYMg944PS4DF1SXntzUHzdoLFip/vffY1Y+M JWhOZH76/WGUdjVBHtTaBB621Xb8hjdX3vQex0UaRptc759CXyH8ntRgyXbafc+H LnhQ4s6ZwyurUbvh5LU/uVq6jwSOJGYg67bmUhSOSTx88NDFJtjyrxhUx+kfIrAq FavnlDyd0B+fSmF6STmk4peUEaLg5VBOREbrgRnzhhsLRsycXpNp2TdHTK9uGfzf RG+4aiN04CH6p5toJ01/Wml6USpi8g1TMPTVinHGFU3hkWSdwJnCEKDgyqyHIrxO B0oREyTk12NCPFZ0aA2mtXjIw5e36OKt6VHnZ3AW14MEDAcqxh8+IYHJ2SFjXmDq 9iytCPR5TfUXX2CS29JUQQ6RThECWBh6jHDloPXt+/++qGxWdjQE0DRy7txXU62t erZ0bXy9bG9jiUSnZio= =SyBN -END PGP SIGNATURE- -- Gijs Molenaar http://pythonic.nl http://gijs.pythonic.nl
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Vincent, one more point: I just discovered that you changed the license of the debian files to GPL-3+. While it is ofcourse your own choice (and I will sponsor it independently of your decision here), I would recommend to stay with upstream's BSD-3. The reason is that having the debian files as GPLv3, it makes the whole package as GPLv3, which would limit its future linking f.e. into programs that are not GPL compatible (even if they are DFSG free). Imagine that someone creates an astronomy framework using astroquery and releases it under a such a license -- we would not be able to package it in Debian. Please reconsider your decision here. Best regards Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUFaTXAAoJEHEVr9B3ENz34mUP/0UpDCdlDlb1QlaHmeYKxX9g GATrL82hHxZc7hJnl0xpOTeK06NdEhCOJA4UfjxiyRgsB7FdkDci+EWnQyNsLIS0 wr0Bcb1qL0zrFhmxSYLEVEbDvDfOt/xcTf9zxnvjZmoJtqOjnJ26l+YCgIkxJa44 D/QDSr7iqnGvoHLf1ULUYaJVALl1umQjAEpKYk3ywJVdGD3As3/dsyldShrm1rlj UliIGV4ux6w++qldot4nKDUx5RDpLBSfysMUQ6gus/1oW2D7Pr2rZsEDNwsb6r+Z 6VqakdST+L/da1gsMbjDWA1+NUmMkRna0Fzx2VtQjBCY47oO1ZL5zEXSo/4Jb07n PZ0baI0+yFlAL2TGK7N0FE+sF9vRNXzWnIgrafH7+7GDeOhsoNiyAu7ZchKxyhSP bb+U2pHDqGdgrZhfqQQJ8IsiOvp4YT0VtupLwfVi7FqV/9NXCyEngSItVjcDM+ve Y6Sz4zmD6bjLHRVmhIsiiCDeNsiVitqLIMnI1Z++PvbZPikPx5FExTfbMVDJrHhb ZOq3dmeRSdmlYGZmey5GksaOrqO6kNomJSULnMt47jxQMoimh18cUCtTCOih/06d YOU57itnZdl5RI67bwlTigx3uHGwV57Yd9yGbINDbSD2kpsIYkAk+q4itsePDX1q T1dwvU/R/paYhzjXUuf0 =aWw3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hi Ole, Agreed and modified. Best regards, Vincent Le 14/09/2014 16:23, Ole Streicher a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Vincent, one more point: I just discovered that you changed the license of the debian files to GPL-3+. While it is ofcourse your own choice (and I will sponsor it independently of your decision here), I would recommend to stay with upstream's BSD-3. The reason is that having the debian files as GPLv3, it makes the whole package as GPLv3, which would limit its future linking f.e. into programs that are not GPL compatible (even if they are DFSG free). Imagine that someone creates an astronomy framework using astroquery and releases it under a such a license -- we would not be able to package it in Debian. Please reconsider your decision here. Best regards Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUFaTXAAoJEHEVr9B3ENz34mUP/0UpDCdlDlb1QlaHmeYKxX9g GATrL82hHxZc7hJnl0xpOTeK06NdEhCOJA4UfjxiyRgsB7FdkDci+EWnQyNsLIS0 wr0Bcb1qL0zrFhmxSYLEVEbDvDfOt/xcTf9zxnvjZmoJtqOjnJ26l+YCgIkxJa44 D/QDSr7iqnGvoHLf1ULUYaJVALl1umQjAEpKYk3ywJVdGD3As3/dsyldShrm1rlj UliIGV4ux6w++qldot4nKDUx5RDpLBSfysMUQ6gus/1oW2D7Pr2rZsEDNwsb6r+Z 6VqakdST+L/da1gsMbjDWA1+NUmMkRna0Fzx2VtQjBCY47oO1ZL5zEXSo/4Jb07n PZ0baI0+yFlAL2TGK7N0FE+sF9vRNXzWnIgrafH7+7GDeOhsoNiyAu7ZchKxyhSP bb+U2pHDqGdgrZhfqQQJ8IsiOvp4YT0VtupLwfVi7FqV/9NXCyEngSItVjcDM+ve Y6Sz4zmD6bjLHRVmhIsiiCDeNsiVitqLIMnI1Z++PvbZPikPx5FExTfbMVDJrHhb ZOq3dmeRSdmlYGZmey5GksaOrqO6kNomJSULnMt47jxQMoimh18cUCtTCOih/06d YOU57itnZdl5RI67bwlTigx3uHGwV57Yd9yGbINDbSD2kpsIYkAk+q4itsePDX1q T1dwvU/R/paYhzjXUuf0 =aWw3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hi Ole, I tried with 0.4.2 and could build it without the error. However, I still get the following lintian error (and pedantic warning): E: astroquery source: source-is-missing astroquery/splatalogue/data/species.json P: astroquery source: source-contains-prebuilt-javascript-object astroquery/splatalogue/data/species.json means line length is about 16184 characters Could you check with upstream where this file comes from, and either override these, or provide the source file? I have asked upstream about this file, and it is indeed not a source file. It is generated by the script astroquery/splatalogue/build_species_table.py. They are going to remove this file from their source tarball and generate it on the fly. What should I do now? Just wait for the next release? Otherwise, I would have to repackage the source myself, right? Best regards, Vincent Best Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUFXjSAAoJEHEVr9B3ENz3i2oQAJcgAPzb0uuet0fsTAH3swS1 pUS2L4xDzdQVLfHEawgh/5Y8mtqWmsq7YSEKIoq3dhpU/Qn4NL7Ae/XJVyOfOJTn e8W/EQ8J0DHNBDAWKV1RVuvm+NW328e8dMo2g5GJxhpb2n/76weoH3vfiHpE6EIo qDGVtWvVnvM9fk3j0IzoYDzk1Dxd4dgphYdTccdPBslgwRvoW6PIzgfTUUFGmfT8 SfsgUz2jM+GZgbh59kIxXCtVdo5nIW53/HgMNRoJJa0oG/SD+ZupZTFlnRddaJRA amQHzSRbij1uz/enrQwcLKZ7Oc35ByucZLe9oS8+fmYzayCwxgGyBYycPapIglUf blg8wfHn62M540+d6MdqvhGxmUo27KQ+Lbkk1AOt4DT/bz31MNqfHAvCoL5bqFkr tIy7qDN3IFetqjNGNmQ4i48JBqfhpuOk78gy2wrZAcoe5TWH1EBBH4AeQ4D6xAMs oYAbAnp/hLCXNEKHiJwkBflZqO4lW3mDf3+SQTGuN6YfAlCzmuEYvqvDm0RBMJRg IymalvFpXBGcGRN6UA/GWT91mrqGnbTydxxD3GvpRR5M1PRgFQKEpOXSsNrGGVPk XU76VePy46hPwwbl1vqzPu7yXO3uJcGLXQq5/EjvuF3EDNIPcGnIVy4MTgvcwHrh NFaQZKEoFepYXAqv84RK =tb7G -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Am 14.09.2014 um 18:23 schrieb Vincent Prat: E: astroquery source: source-is-missing astroquery/splatalogue/data/species.json P: astroquery source: source-contains-prebuilt-javascript-object astroquery/splatalogue/data/species.json means line length is about 16184 characters Could you check with upstream where this file comes from, and either override these, or provide the source file? I have asked upstream about this file, and it is indeed not a source file. It is generated by the script astroquery/splatalogue/build_species_table.py. They are going to remove this file from their source tarball and generate it on the fly. What should I do now? Just wait for the next release? Otherwise, I would have to repackage the source myself, right? If the source is in the source tree, you may just overwrite the lintian error (please specify which file is the source in the lintian comment then) -- this is IMO the simplest solution. You can also use the Files-Excluded: field of debian/copyright; see https://wiki.debian.org/UscanEnhancements This will force uscan to create a dfsg tarball. You would need to adjust debian/watch and debian/changelog as well. Best Ole -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
On Mon, Sep 08, 2014 at 11:20:00PM +0200, Vincent Prat wrote: Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package astroquery * Package name: astroquery Version : 0.2.1-1 Upstream Author : Adam Ginsburg adam.g.ginsb...@gmail.com * URL : http://astroquery.readthedocs.org/ * License : BSD 3-Clause Section : python It builds those binary packages: python-astroquery - Python online astronomical database querying (Python 2) python-astroquery-doc - Python online astronomical database querying (documentation) python3-astroquery - Python online astronomical database querying (Python 3) To access further information about this package, please visit the following URLs: http://mentors.debian.net/package/astroquery http://anonscm.debian.org/cgit/debian-astro/packages/astroquery.git/ Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/astroquery/astroquery_0.2.1-1.dsc The latest version is 0.4. Please add a .patch extension to the patch file name. You should add information for debian/* to debian/copyright. Is it really necessary to rm astroquery.splatalogue in override_dh_python* and not in override_dh_(auto)?_install? Also, I couldn't actually build the package because of missing python3?-astropy-helpers. -- WBR, wRAR signature.asc Description: Digital signature
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hi Andrey, Thank you for the review. The latest version is 0.4. Where have you found this? On both Pypi and Github, the latest release is 0.2.2. Please add a .patch extension to the patch file name. You should add information for debian/* to debian/copyright. Is it really necessary to rm astroquery.splatalogue in override_dh_python* and not in override_dh_(auto)?_install? I will correct this. Also, I couldn't actually build the package because of missing python3?-astropy-helpers. Version 0.2 needed astropy-helpers to build, so I asked the maintainer of astropy to package astropy-helpers as well. The package is now in the NEW queue. However, it seems that astropy_helpers is now included in the astroquery source tarball. Maybe I should remove the dependencies and use the bundled version. What is your opinion about this? Best regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: Aw: Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hello, Thank you for the review. The latest version is 0.4. Where have you found this? On both Pypi and Github, the latest release is 0.2.2. The commment may refer to astropy, which is at 0.4.1. That is an associated project but not shipping astroquery itself. For astroquery, astropy points to http://www.astropy.org/astroquery/ and the zip generated for that declares itself as 0.2.2. Is there any other version declared within the source tree? Otherwise 0.2.2 seems just right. Please add a .patch extension to the patch file name. You should add information for debian/* to debian/copyright. Is it really necessary to rm astroquery.splatalogue in override_dh_python* and not in override_dh_(auto)?_install? I will correct this. Also, I couldn't actually build the package because of missing python3?-astropy-helpers. Version 0.2 needed astropy-helpers to build, so I asked the maintainer of astropy to package astropy-helpers as well. The package is now in the NEW queue. However, it seems that astropy_helpers is now included in the astroquery source tarball. Maybe I should remove the dependencies and use the bundled version. What is your opinion about this? Is it right or wrong to have the astropy-helpers shipping with astroquery? Who else is sharing that same astropy-helper module? From my immediate perception I would tend to prefer the dependency and even remove the helpers from the astroquery source tree. Best, Steffen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
On Sat, Sep 13, 2014 at 11:46:53AM +0200, Vincent Prat wrote: Hi Andrey, Thank you for the review. The latest version is 0.4. Where have you found this? On both Pypi and Github, the latest release is 0.2.2. wrar@belkar ~/tmp/astroquery-0.2.1 $ uscan --verbose --report -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/astroquery-$1\.tar\.gz/,uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ https://github.com/astropy/astroquery/tags .*/v?(\d\S*)\.tar\.gz -- Found the following matching hrefs: /astropy/astroquery/archive/v0.2.2.tar.gz (0.2.2) /astropy/astroquery/archive/v0.2.1.tar.gz (0.2.1) /astropy/astroquery/archive/v0.2.tar.gz (0.2) /astropy/astroquery/archive/v0.4.tar.gz (0.4) /astropy/astroquery/archive/v0.2-rc2.tar.gz (0.2~rc2) /astropy/astroquery/archive/v0.2-rc.tar.gz (0.2~rc) /astropy/astroquery/archive/v0.1.tar.gz (0.1) Newest version on remote site is 0.4, local version is 0.2.1 = Newer version available from https://github.com/astropy/astroquery/archive/v0.4.tar.gz -- Scan finished Also, I couldn't actually build the package because of missing python3?-astropy-helpers. Version 0.2 needed astropy-helpers to build, so I asked the maintainer of astropy to package astropy-helpers as well. The package is now in the NEW queue. Well, I cannot (at least easily) build packages depending on packages in NEW (or on any packages not in the archive, for that matter). However, it seems that astropy_helpers is now included in the astroquery source tarball. Maybe I should remove the dependencies and use the bundled version. What is your opinion about this? If it's intended to be used as a public module you need to package it as such, it doesn't matter much whether it's a separate tarball. In any case, if it's already packaged as a separate source package you shouldn't use bundled versions too. -- WBR, wRAR signature.asc Description: Digital signature
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hi, wrar@belkar ~/tmp/astroquery-0.2.1 $ uscan --verbose --report -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/astroquery-$1\.tar\.gz/,uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ https://github.com/astropy/astroquery/tags .*/v?(\d\S*)\.tar\.gz -- Found the following matching hrefs: /astropy/astroquery/archive/v0.2.2.tar.gz (0.2.2) /astropy/astroquery/archive/v0.2.1.tar.gz (0.2.1) /astropy/astroquery/archive/v0.2.tar.gz (0.2) /astropy/astroquery/archive/v0.4.tar.gz (0.4) /astropy/astroquery/archive/v0.2-rc2.tar.gz (0.2~rc2) /astropy/astroquery/archive/v0.2-rc.tar.gz (0.2~rc) /astropy/astroquery/archive/v0.1.tar.gz (0.1) Newest version on remote site is 0.4, local version is 0.2.1 = Newer version available from https://github.com/astropy/astroquery/archive/v0.4.tar.gz -- Scan finished This is probably an error, since 0.4 is older than 0.2.2. And on Pypi, which is now used as canonical source, there is no 0.4 version. Well, I cannot (at least easily) build packages depending on packages in NEW (or on any packages not in the archive, for that matter). If you want, you can build astropy-helpers from the git repository: http://anonscm.debian.org/cgit/debian-astro/packages/python-astropy-helpers.git If it's intended to be used as a public module you need to package it as such, it doesn't matter much whether it's a separate tarball. In any case, if it's already packaged as a separate source package you shouldn't use bundled versions too. Ok. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
On Sat, Sep 13, 2014 at 08:36:42PM +0200, Vincent Prat wrote: Hi, wrar@belkar ~/tmp/astroquery-0.2.1 $ uscan --verbose --report -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/astroquery-$1\.tar\.gz/,uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ https://github.com/astropy/astroquery/tags .*/v?(\d\S*)\.tar\.gz -- Found the following matching hrefs: /astropy/astroquery/archive/v0.2.2.tar.gz (0.2.2) /astropy/astroquery/archive/v0.2.1.tar.gz (0.2.1) /astropy/astroquery/archive/v0.2.tar.gz (0.2) /astropy/astroquery/archive/v0.4.tar.gz (0.4) /astropy/astroquery/archive/v0.2-rc2.tar.gz (0.2~rc2) /astropy/astroquery/archive/v0.2-rc.tar.gz (0.2~rc) /astropy/astroquery/archive/v0.1.tar.gz (0.1) Newest version on remote site is 0.4, local version is 0.2.1 = Newer version available from https://github.com/astropy/astroquery/archive/v0.4.tar.gz -- Scan finished This is probably an error, since 0.4 is older than 0.2.2. And on Pypi, which is now used as canonical source, there is no 0.4 version. Yes, looks like upstream broke their git repo. That tag and commits in it are not a part of any branch and the version is probably related to the version of -helpers. Unfortunately in DVCS there is no way to remove things you've published, even if they know about the problem. Well, I cannot (at least easily) build packages depending on packages in NEW (or on any packages not in the archive, for that matter). If you want, you can build astropy-helpers from the git repository: http://anonscm.debian.org/cgit/debian-astro/packages/python-astropy-helpers.git That's what I meant by not easy way. -- WBR, wRAR signature.asc Description: Digital signature
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
On 13/09/14 20:05, Andrey Rahmatullin wrote: Yes, looks like upstream broke their git repo. That tag and commits in it are not a part of any branch and the version is probably related to the version of -helpers. Unfortunately in DVCS there is no way to remove things you've published, even if they know about the problem. As that tag exists, and effectively breaks the uscan... why not just use pypi as the source for the watch file. I had to do this for a package I maintain due to lack of tags, you can see my watch file at [1] Regards, Daniel Lintott [1] http://anonscm.debian.org/cgit/users/dlintott-guest/buildnotify.git/tree/debian/watch signature.asc Description: OpenPGP digital signature
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hi As that tag exists, and effectively breaks the uscan... why not just use pypi as the source for the watch file. I had to do this for a package I maintain due to lack of tags, you can see my watch file at [1] That is what is done now. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Hi Ole, I have applied all suggested changes. I thought the package was ready, but while testing it with pbuilder, I encountered an error, apparently with astropy-helpers documentation routines: Exception occurred: File /usr/lib/python2.7/dist-packages/astropy_helpers/sphinx/ext/automodsumm.py, line 419, in generate_automodsumm_docs name, obj, parent = import_by_name(name) ValueError: too many values to unpack Can you reproduce it? Best regards, Vincent Le 13/09/2014 17:03, Ole Streicher a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Vincent, I have seen that you resolved some, but not all of my remarks yet: * I would silence the privacy-breach-generic warning of lintian -E, since this is on purpose * The link in python-astroquery.links should probably go to the -doc package? * I would put the http_proxy='127.0.0.1:9' as general line in rules, to make sure that during auto-build nothing is retrieved (move from the sphinx documentation) Do you disagree here with me? Or did you just not finish? (Not pressing you; just asking, since otherwise I am ready to sponsor). Best regards Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUFFzfAAoJEHEVr9B3ENz3jOwQAJVNCx5qxQEY0olOfWTwLmgA IIpK0pfI/qt0BPkZWA2P7M8AYlHJ6L4agsPuvbLaC2UwslJsvHLQZx/zP5+vlUzP jP+EGsCGNZuID3EQ/8EYfsNdSQWtPlOp73PoLlZLHfSKt8JOsSaS3npcmd+kcAok ZLWG88JRl4q+ZgR0ktyyvdWvC4DXjMeYEVaKvDdL58nadAbnX6O8XdxpvtQiu+MA /kte1WSiYsrvZSRVIhDcel+T22T4xaLkq03cLbMWzi4fJEjJoY63O7VxUe0kqZdB RzlHAtLIyuINrLazqJzRo7oj/Ec8ZRIUV2BWXYk/GHcaz8/2aB5RmGsRjh4kPo7i orD0bQXroEj8GT0+mbP6Xvkg5iOELEjcKyS7itgGjfhbgeIHRQZ1/ZkxaXXsPqfj RHYAQ+joa8m8j1Re2pMnJgpR6mvJurZf3x6LfxAIMg+Q7k0M4wKvB/t8f53PaUpG hxnX+b+cfYlCn8XBrZIpa3Vnv/ZGbZjsaOF7e1M5Hv6e8lty5bp9BSSzhEyCE9GY oEEVIQqIs7FCPdI+atwUaj5WOLYbpZ4JYgVWav1poQDCKORWr0IbmuBDYrUjEQDA OjHKEbybMttM9NFzz2rb/IwpXnCowTmKhB+9s7vU3FiXHyfVApn+E8QzYF2bnfXU S8AOtMdXpt6dXPl0dryh =WRiB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package astroquery * Package name: astroquery Version : 0.2.1-1 Upstream Author : Adam Ginsburg adam.g.ginsb...@gmail.com * URL : http://astroquery.readthedocs.org/ * License : BSD 3-Clause Section : python It builds those binary packages: python-astroquery - Python online astronomical database querying (Python 2) python-astroquery-doc - Python online astronomical database querying (documentation) python3-astroquery - Python online astronomical database querying (Python 3) To access further information about this package, please visit the following URLs: http://mentors.debian.net/package/astroquery http://anonscm.debian.org/cgit/debian-astro/packages/astroquery.git/ Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/astroquery/astroquery_0.2.1-1.dsc Regards, Vincent Prat -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
