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
>>
>>
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
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
-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
BS
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_d
-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
> r
-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 bu
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 :
> On Sat, Sep 13, 2014 at 10:57:16PM +0200, Vincent Pr
-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
>
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
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/automodsu
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
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 i
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*)
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|
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
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 p
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 astro
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 Ginsb
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
* URL : http://astroquery.readthedocs.org/
* License :
20 matches
Mail list logo
