Hi,
the issue is that the first line of the description (the short description)
doesn't give any information, it just paraphrases the package name and version
(I know that libvarnam/3.1.3-1 is a library and that it's about Varnam with a
3).
Something else: the mentor page is full of lintian warn
Hello Eric,
Thanks for checking out the project. Where should I improve the
project description? The debain control files has proper description
about the project. Where else should I change?
Thanks
On Sun, Mar 23, 2014 at 12:40 AM, Eric L.
wrote:
> Hi,
> I would recommend to improve the short
Your message dated Sun, 23 Mar 2014 04:25:34 +
with message-id
and subject line closing RFS: pyspatialite/3.0.1-6
has caused the Debian Bug report #742339,
regarding RFS: pyspatialite/3.0.1-6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sun, 23 Mar 2014 04:25:34 +
with message-id
and subject line closing RFS: osgearth/2.5.0+dfsg-2
has caused the Debian Bug report #742325,
regarding RFS: osgearth/2.5.0+dfsg-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Em Sat, Mar 22, 2014 at 11:29:32AM +0100, intrigeri escreveu:
> > Thanks for the review :)
>
> You're welcome. In the future, how about releasing a RC, issueing
> a call for reviews and tests, before going the full way to RFS?
Sorry about that. I'm trying the "release further, release often"
appr
Hi,
I would recommend to improve the short description. The homepage states "cross
platform transliterator for Indian languages" which sounds more informative to
me.
Eric
On 22 March 2014 07:18:18 CET, Navaneeth K N wrote:
>Package: sponsorship-requests
>Severity: normal
>
> Package: sponsorsh
Dear mentors,
I am looking for a sponsor for my package "procmeter3".
Package name: procmeter3
Version : 3.6-1
Upstream Author : [Please put procmeter
in the subject line]
URL : http://www.gedanken.org.uk/software/procmeter3/
License : GPL-2+
Se
Package: sponsorship-requests
Severity: normal
Dear mentors,
As part of the SpatiaLite transition am I looking for a sponsor for
my package "pyspatialite".
https://release.debian.org/transitions/html/libspatialite5.html
https://release.debian.org/transitions/html/librasterlite2.html
Please refe
Hi,
one more thing; the git repository
with the package is here:
http://anonscm.debian.org/gitweb/?p=collab-maint/gravit.git
Tomasz
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https:
Here it is:
- Forwarded message from "mentors.debian.net"
-
Date: Sat, 22 Mar 2014 14:54:36 + (UTC)
From: "mentors.debian.net"
To: tomasz.buch...@inria.fr
Subject: gravit uploaded to mentors.debian.net
Hi.
Your upload of the package 'gravit' to mentors.debian.net was
successful.
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "gravit":
* Package name: gravit
Version : 0.5.1-1
Upstream Author : Gerald Kaszuba
* URL : http://gravit.slowchop.com/
* License : GPL2
Section
On Sat, Mar 22, 2014 at 02:28:28PM +0100, Nico Schlömer wrote:
> >> I'm packaging a library libA which depends on a header-only library
> >> libB.
> > How?
>
> libA's CMake build script checks for libB and the public headers of
> libA #include libB headers.
So how is this different from the usual
On 22-03-14 13:33, Nico Schlömer wrote:
> Hi all,
>
> I'm packaging a library libA which depends on a header-only library
> libB. Obviously I need libB to be present whenever I build an
> executable against libA. Where in debian/control will I have to fill
> in libB?
If I am correct, you should h
>> I'm packaging a library libA which depends on a header-only library
>> libB.
> How?
libA's CMake build script checks for libB and the public headers of
libA #include libB headers.
--Nico
On Sat, Mar 22, 2014 at 2:21 PM, Andrey Rahmatullin wrote:
> On Sat, Mar 22, 2014 at 01:33:25PM +0100, N
On Sat, Mar 22, 2014 at 01:33:25PM +0100, Nico Schlömer wrote:
> I'm packaging a library libA which depends on a header-only library
> libB.
How?
--
WBR, wRAR
signature.asc
Description: Digital signature
Hi,
2014-03-22 13:33 GMT+01:00 Nico Schlömer :
> I'm packaging a library libA which depends on a header-only library
> libB. Obviously I need libB to be present whenever I build an
> executable against libA. Where in debian/control will I have to fill
> in libB?
I think it should be in Depends of
hi Mentors,
I am maintaining the freeplane package. The current version
1.3.7 that I am preparing has a different icon than freeplane 1.2.23
which is currently in the Debian archive.
Now, when installing the 1.3.7 package (not published yet, but available
here [1]), the KDE panel (and sometimes G
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "osgearth"
Package name: osgearth
Version : 2.5.0+dfsg-2
Upstream Author : Glenn Waldron
URL : http://osgearth.org/
License : LGPL-3
Section : deve
Hi all,
I'm packaging a library libA which depends on a header-only library
libB. Obviously I need libB to be present whenever I build an
executable against libA. Where in debian/control will I have to fill
in libB?
Cheers,
Nico
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.o
> No, the 'linker' does not complain.
You're right, it is the CMake dependency checker. The linking is all
right, but there's something amiss with the CMake export files. I'll
investigate.
Thanks for the comments!
--Nico
On Thu, Mar 20, 2014 at 3:31 PM, Mathieu Malaterre
wrote:
> Hi
>
> On 3/
Hi,
Silvio Rhatto wrote (18 Mar 2014 00:17:11 GMT) :
> Em Mon, Mar 17, 2014 at 10:29:12AM +0100, intrigeri escreveu:
>> Great! Here's a quick code review of the changes since 0.2.9.
> Thanks for the review :)
You're welcome. In the future, how about releasing a RC, issueing
a call for reviews an
21 matches
Mail list logo
