Hi Gianfranco,
Thanks for sponsoring the binNEW upload of twinkle.
I had a closer look at the lintian warning issued by debomatic:
X: twinkle source: maybe-not-arch-all-binnmuable twinkle -> twinkle-common
N:
N:Tag to attempt to measure the number of packages that might have an
N:
On Tuesday, June 28 2016, Dmitry Bogatov wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "elisp-slime-nav-el"
>
> * Package name: elisp-slime-nav-el
> Version : 0.9-1
> Upstream Author : Steve Purcell
> * Url :
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "elisp-slime-nav-el"
* Package name: elisp-slime-nav-el
Version : 0.9-1
Upstream Author : Steve Purcell
* Url :
On Monday, June 20 2016, Andrey Rahmatullin wrote:
> On Mon, Jun 20, 2016 at 03:37:55PM -0400, Sergio Durigan Junior wrote:
>> > I've uploaded the package, thanks for your contribution to Debian :)
>> Thank you! I guess I will ping you again when the package has been
>> accepted, so that you can
Your message dated Tue, 28 Jun 2016 18:34:09 + (UTC)
with message-id <2111837213.5042173.1467138849062.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#828700: RFS:
twinkle/1.9.0+git20160520.0.be8b8df+dfsg-1 [binNEW] -- Voice over Internet
Protocol (VoIP) SIP Phone
has caused the
I pushed another commit that removes ${shlibs:Depends} from twinkle-common.
Peter
Hi Gianfranco,
On Tue, Jun 28, 2016 at 09:21:51AM +, Gianfranco Costamagna wrote:
> Hi, lintian is not too happy with your changes
> http://debomatic-amd64.debian.net/distribution#unstable/twinkle/1.9.0+git20160520.0.be8b8df+dfsg-1/lintian
The above report seems to be generated using an
On 06/28/2016 11:01 AM, Andreas Tille wrote:
> I admit I can not answer the question asked by upstream. The package in
> question is iqtree[1] and they said that they have different
> computational kernels implemented to respect different hardware.
> Current Git[1] does not even build - may be
Your message dated Tue, 28 Jun 2016 16:20:11 + (UTC)
with message-id <1258845587.5003950.1467130811635.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#828863: RFS: gmp-ecm/7.0.2+ds-1 [RC] -- Factor
integers using the Elliptic Curve Method
has caused the Debian Bug report #828863,
Package: sponsorship-requests
Severity: important
Dear Sponsors,
I am looking for sponsorship for the package gmp-ecm. This package
brings
the lastest patch version of [gmp-]ecm that fixes some tests failures
encountered on some 32bit architectures (#828717).
Thanks in
On 06/27/2016 10:49 PM, Andreas Tille wrote:
>> - if you use autoconf/automake, you don't need to use d-moveshlibs
>>for multiarch, dh_auto_configure / dh_auto_build / dh_auto_install
>>will do all the heavy lifting for you (just create proper .install
>>files for the packages, and
On Tue, Jun 28, 2016 at 03:42:21PM +0200, Christian Seiler wrote:
>
> (Btw. you still didn't update debian/control in git. ;-))
Ahhh, thanks for noticing ...
> Well, but the reason you get help here is so you can learn from
> it. ;-) And you don't have to be an expert in the autotools (while I
> On Mon, Jun 27, 2016 at 05:32:32PM +0300, Dmitry Bogatov wrote:
> > 2. In d/copyright, I think you need to specify copyright years for the
> > copyright holders. Just their names is not enough, since on a desert
> > island ~60 years from now with no newer versions of evil available for
> >
(Merging replies.)
On 06/28/2016 08:35 AM, Andreas Tille wrote:
> On Mon, Jun 27, 2016 at 11:57:12PM +0200, Christian Seiler wrote:
>> [Multi-Arch]
>> In your package, that's already the case, so you can just add the header
>> to debian/control.
>
> A, well, yes - I simply forgot this. In my
Your message dated Tue, 28 Jun 2016 12:25:50 + (UTC)
with message-id <2116826129.4691041.1467116750857.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#828841: RFS: yamllint/1.3.2-1
has caused the Debian Bug report #828841,
regarding RFS: yamllint/1.3.2-1
to be marked as done.
This
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "yamllint"
* Package name: yamllint
Version : 1.3.2-1
Upstream Author : Adrien Vergé
* URL : https://github.com/adrienverge/yamllint
*
> * Dmitry Bogatov , 2016-06-27, 17:32:
> >Mercurial upstream repository, and tarballs are named not after
> >version, but after hashes. I fail to extract anything useful from this
> >page: [1]
> >
> >[1] https://bitbucket.org/lyro/evil/downloads
> This seems to work for me:
On Tue, 28 Jun 2016, Andreas Tille wrote:
> I admit I can not answer the question asked by upstream. The package in
> question is iqtree[1] and they said that they have different
> computational kernels implemented to respect different hardware.
> Current Git[1] does not even build - may be due
* Dmitry Bogatov , 2016-06-27, 17:32:
Mercurial upstream repository, and tarballs are named not after
version, but after hashes. I fail to extract anything useful from this
page: [1]
[1] https://bitbucket.org/lyro/evil/downloads
This seems to work for me:
version=3
control: owner -1 !
control: tags -1 moreinfo
Hi, lintian is not too happy with your changes
http://debomatic-amd64.debian.net/distribution#unstable/twinkle/1.9.0+git20160520.0.be8b8df+dfsg-1/lintian
please fix the above if possible,
Gianfranco
Il Martedì 28 Giugno 2016 5:21, Peter Colberg
Hi,
I admit I can not answer the question asked by upstream. The package in
question is iqtree[1] and they said that they have different
computational kernels implemented to respect different hardware.
Current Git[1] does not even build - may be due to some fine tuning of
gcc options needed???
Your message dated Tue, 28 Jun 2016 09:57:09 +0200
with message-id
Hi Christian,
On Mon, Jun 27, 2016 at 11:57:12PM +0200, Christian Seiler wrote:
>
> Well, autoconf in and by itself doesn't support testing, automake does,
> which fortunately you're also using.
>
> I've added a very trivial test from the way I understand how the program
> you're using works,
Hi Christian,
On Mon, Jun 27, 2016 at 10:41:28PM +0200, Christian Seiler wrote:
> On 06/27/2016 07:49 PM, Christian Seiler wrote:
> > Other comments regarding the package:
>
> Oh btw. I just noticed that you don't install the manpage for
> the library function in the -dev package (because
24 matches
Mail list logo