Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for "pygtail"
* Package name: pygtail
Version : 0.6.1
Upstream Author : Brad Greenlee
* URL : https://github.com/bgreenlee/pygtail
* License : GPL-2+
Section
Your message dated Wed, 11 May 2016 08:43:40 + (UTC)
with message-id <1054313194.293823.1462956220992.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#823981: RFS: aiksaurus/1.2.1+dev-0.12-6.3 [RC] [NMU]
-- an English-language thesaurus
has caused the Debian Bug report #823981,
regardin
Your message dated Wed, 11 May 2016 10:18:34 + (UTC)
with message-id <2104225818.458103.1462961914458.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#811073: RFS: lbfgsb/3.0-1 [ITP]
has caused the Debian Bug report #811073,
regarding RFS: lbfgsb/3.0-2 [ITP]
to be marked as done.
This m
Hello Forum:
my package singular [1] is marked for autoremoval while the involved bug has
been fixed for a while.
I suspect the involved bug [2] is in fact not considered as closed bug the
robots.
Any idea on how to fix it ?
Thanks in advance,
Jerome
[1] https://packages.qa.debian.org/s/singu
Hi Jerome
You need to make the package migrate into stretch if you want the autoremoval
to stop
https://buildd.debian.org/status/package.php?p=singular&suite=unstable
armhf is not build anymore, so you can choose from:
1) fixing polybori
2) file a bug against ftpmasters to remove singular [armhf]
Hi,
>license.txt
> * Removed license.txt
> As some other distributions strictly want this file, I wanted to ask
>if I may remove that file with a debian patch?
no you shouln't ever remove that file.
this is source of reject from ftpmasters.
You don't have to install it with make install,
so
also, your line closing bugs was missing a semicolon,
ITYM comma, which is indeed necessary between bug numbers. See DevRef
§5.8.4.
(I'm not sure if the bug would have been closed correctly or not)
In *.changes, there's Closes field which says exactly which bugs are
going to be closed.
On Wed, May 11, 2016 at 10:31:46AM +, Gianfranco Costamagna wrote:
> You need to make the package migrate into stretch if you want the autoremoval
> to stop
> https://buildd.debian.org/status/package.php?p=singular&suite=unstable
> armhf is not build anymore, so you can choose from:
> 1) fixi
Hello Again,
On 11/05/16 12:07, Santiago Vila wrote:
> On Wed, May 11, 2016 at 10:31:46AM +, Gianfranco Costamagna wrote:
>
>> You need to make the package migrate into stretch if you want the
>> autoremoval to stop
>> https://buildd.debian.org/status/package.php?p=singular&suite=unstable
>>
Thank you very much for the review! And sorry for the additional work that I
caused you.
> I also tweaked the changelog to be a little bit more verbose, and probably
> something more
> I put this on deferred/15, and I'm attaching it to this email or you can dget
> from there
> http://debomatic-
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "setuptools-scm"
* Package name: setuptools-scm
Version : 1.11.0-1
Upstream Author : Ronny Pfannschmidt
* URL : https://github.com/pypa/setuptools_scm
* Li
On 11/05/16 15:10, Andrew Shadura wrote:
> On 11/05/16 14:47, Julien Puydt wrote:
>> python-setuptools-scm - blessed package to manage your versions by
>> scm tags for Python 2
>> python3-setuptools-scm - blessed package to manage your versions by scm
>> tags for Python 3
>>
>> To access fur
Your message dated Wed, 11 May 2016 14:54:32 + (UTC)
with message-id <1599362089.817103.1462978472757.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#824027: RFS: setuptools-scm/1.11.0-1
has caused the Debian Bug report #824027,
regarding RFS: setuptools-scm/1.11.0-1
to be marked as don
Dear all,
I have a package (pyfr), which is meant to be used as a command-line
application only.
The main script (pyfr) is installed via setuptools'
entry_points['console_scripts'], which generates the entry-point
automatically and places it under /usr/bin. However, when I install the
implementa
[Ghislain Vaillant, 2016-05-11]
> Dear all,
>
> I have a package (pyfr), which is meant to be used as a command-line
> application only.
>
> The main script (pyfr) is installed via setuptools'
> entry_points['console_scripts'], which generates the entry-point
> automatically and places it under /
FTR:
[Piotr Ożarowski, 2016-05-11]
> dh_auto_install -- --install-lib=/usr/share/pyfr/
this one ^ should be:
dh_auto_install -- --install-args='--install-lib=/usr/share/pyfr/'
or you can:
export PYBUILD_INSTALL_ARGS=--install-lib=/usr/share/pyfr/
(thanks to Dmitry Shachnev for notici
On 2016-05-11 03:41, Benda Xu wrote:
> Hi,
>
> I am packaging a library called "casacore" which provides
>
> libcasa_python3.so.2 and libcasa_python.so.2
>
> with SONAME=2.
>
> How should them be named when the python major version and SONAME could
> cause confusion?
>
> I can think of
>
>
Christian Kastner writes:
> On 2016-05-11 03:41, Benda Xu wrote:
>> I am packaging a library called "casacore" which provides
>> libcasa_python3.so.2 and libcasa_python.so.2
>> with SONAME=2.
>> How should them be named when the python major version and SONAME could
>> cause confusion?
> Accord
On 2016-05-11 22:13, Ole Streicher wrote:
> Christian Kastner writes:
>> On 2016-05-11 03:41, Benda Xu wrote:
>>> I am packaging a library called "casacore" which provides
>>> libcasa_python3.so.2 and libcasa_python.so.2
>>> with SONAME=2.
>>> How should them be named when the python major versi
19 matches
Mail list logo
