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
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
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
On 2014-08-29 Peter wrote:
[...]
> I am looking for a sponsor for my package "tkinfo"
Hello Peter,
thanks for adopting this package, I occasionally use it and will be
happy to sponsor.
[...]
> Changes since the last upload:
[...]
>* Add dh-installmime to binary-indep (Closes: #723710)
J
Dear mentors,
in debian-astro, we have a problem with a circular dependency on two
packages that are currently prepared [1], [2]:
- the "casacore" needs the "casacore-data" package for unit tests
- the "casacore-data" needs "casacore" to be build from the source data.
The source data of casacor
Hi!
2014-09-13 20:01 GMT+07:00 Ole Streicher :
> Dear mentors,
>
> in debian-astro, we have a problem with a circular dependency on two
> packages that are currently prepared [1], [2]:
>
> - the "casacore" needs the "casacore-data" package for unit tests
>
> - the "casacore-data" needs "casacore"
On Sep 13, 2014 3:01 PM, "Ole Streicher" wrote:
>
> Dear mentors,
>
> in debian-astro, we have a problem with a circular dependency on two
> packages that are currently prepared [1], [2]:
>
> - the "casacore" needs the "casacore-data" package for unit tests
>
> - the "casacore-data" needs "casacor
Am 13.09.2014 um 15:09 schrieb Mattia Rizzolo:
> On Sep 13, 2014 3:01 PM, "Ole Streicher" wrote:
>> - the "casacore" needs the "casacore-data" package for unit tests
>> - the "casacore-data" needs "casacore" to be build from the source data.
>
> What's about upload casacore with the tests disable
Hi,
Quoting Ole Streicher (2014-09-13 15:20:36)
> Am 13.09.2014 um 15:09 schrieb Mattia Rizzolo:
> > On Sep 13, 2014 3:01 PM, "Ole Streicher" wrote:
> >> - the "casacore" needs the "casacore-data" package for unit tests
> >> - the "casacore-data" needs "casacore" to be build from the source data.
On 13/09/14 12:57, Andreas Metzler wrote:
> On 2014-08-29 Peter wrote:
> [...]
>> I am looking for a sponsor for my package "tkinfo"
> Hello Peter,
> thanks for adopting this package, I occasionally use it and will be
> happy to sponsor.
>
> [...]
>> Changes since the last upload:
> [...]
>>
On Sep 13, 2014 3:20 PM, "Ole Streicher" wrote:
> Still, the packages would have a circular build dependency, which I think
should be avoided, right?
>
Well, compilers often build-depend on them own, which is even worse.
If a circular dependency could be avoided, better, but I don't care that
muc
Hello,
I fixed the errors and some of the warnings and reuploaded the package.
Regards,
Le 18/08/2014 04:13, Eriberto Mota a écrit :
tags 757966 moreinfo
thanks
Hi Pierre,
I saw your package in mentors.debian.org and it has several Lintian messages.
IMHO, to get a sponsor you must, at least
On 13/09/14 15:01, Ole Streicher wrote:
> Dear mentors,
>
> in debian-astro, we have a problem with a circular dependency on two
> packages that are currently prepared [1], [2]:
>
> - the "casacore" needs the "casacore-data" package for unit tests
>
> - the "casacore-data" needs "casacore" to be
On Fri, 12 Sep 2014 08:11:42 +0100, Azazel wrote:
>> Just out of curiosity, the source package I uploaded,
>> http://mentors.debian.net/debian/pool/main/h/histring/
histring_1.1.0-2.dsc
>> should be working according to your above principle, but why it is
>> failing?
>
> Because you weren't using
Hi Pierre,
You have several important messages yet. If you don
2014-09-13 12:48 GMT-03:00 Pierre Rudloff :
> Hello,
>
> I fixed the errors and some of the warnings and reuploaded the package.
>
> Regards,
>
> Le 18/08/2014 04:13, Eriberto Mota a écrit :
>
>> tags 757966 moreinfo
>> thanks
>>
>> H
Hi Pierre,
You have several important messages yet[1]. If you don't fix it, will
be very hard get a sponsor.
[1] http://mentors.debian.net/package/lutris
Cheers,
Eriberto
2014-09-13 13:53 GMT-03:00 Eriberto :
> Hi Pierre,
>
> You have several important messages yet. If you don
>
> 2014-09-13
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
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 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*)
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
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-ment
Hello,
I have fixed every Lintian warning except those which depend on upstream:
no-upstream-changelog
debian-watch-may-check-gpg-signature
and these two which look like false positives:
desktop-mime-but-no-exec-code
package-contains-timestamped-gzip
Regards,
Le 13/09/2014 18:54, Eriberto a éc
On Fri, 12 Sep 2014 09:10:10 +0600, Andrey Rahmatullin wrote:
> On Fri, Sep 12, 2014 at 02:28:34AM +, T o n g wrote:
>> Hi,
>>
>> My histring has this "binary file contents changed" error, how to fix
>> it?
>>
>> Here is the build log:
>>
>> dpkg-source: info: using options from histring-
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 Alexander,
Alexander Wolf writes:
> Hi!
>
> A separate "casacore-data" on two packages - "casacore-data" &
> "casacore-tests"?
I don't see it feasible to separate. all the present contents of
casacore-data are needed for the test.
Cheers,
Benda
--
To UNSUBSCRIBE, email to debian-mentors-
Hi Gijs and Tomasz,
Gijs Molenaar writes:
> i don't think that would work, the releases of casacore-data and
> casacore are not in sync.
>
> 2014-09-13 18:31 GMT+02:00 Tomasz Buchert :
>
> Hi guys,
> if I get this right, this is only build-time dependency, right?
> What about "mergin
Alexander Wolf writes:
> A separate "casacore-data" on two packages - "casacore-data" &
> "casacore-tests"?
Sorry Alexander, I misunderstood your point at the first sight.
As later Johannes Schauer put more precisely,
> 1. split the source package as Alexander Wolf suggested so that the
> unit
On Sat, Sep 13, 2014 at 07:54:22PM +, T o n g wrote:
> >> My histring has this "binary file contents changed" error, how to fix
> >> it?
> >>
> >> Here is the build log:
> >>
> >> dpkg-source: info: using options from histring-1.1.0/debian/source/
> >> options: --extend-diff-ignore=^Makefil
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
29 matches
Mail list logo
