I have fixed all of those. i will be happy to get sponsor for this.
2015-01-01 22:45 GMT+02:00 Riley Baird wrote:
> Hi, I'm not a DD, so I can't sponsor your package, but I've had a look
> and here are some things I've noticed:
>
> * Your package should be a non-native package, because it isn't
>
I have a data only package on Alioth. "make" is essentially a nop because
the package is all data.
I want to create a new package that is identical to the old one except
that 1) the name of the package is changed. 2) the data files and their
names are changed.
The data files are fairly large and
On Sat, Jan 10, 2015 at 10:12 AM, Luke Diamand wrote:
> Hi!
>
> I'm trying to create a package for 'git-p4', a python script which mirrors
> between git and Perforce (the latter is a proprietary version control
> system). I'm looking for advice on the best way to do this.
>
> The source code live
On 10-01-15 20:59, Paul Gevers wrote:
>>> I think you don't need to add the version to the dpkg-gensymbols call,
>>> and if you do, why strip the Debian part of the version? Doesn't
>>> dh_makeshlibs call dpkg-gensymbols itself? So if you try to override
>>> anything, shouldn't the dpkg-gensymbols
Hello Jörg,
On 07-01-15 13:12, Jörg Frings-Fürst wrote:
> Am Montag, den 05.01.2015, 21:55 +0100 schrieb Paul Gevers:
>> On 30-12-14 21:17, Jörg Frings-Fürst wrote:
>>> Am Montag, den 29.12.2014, 11:13 +0100 schrieb Paul Gevers:
On 26-12-14 20:48, Jörg Frings-Fürst wrote:
>> Sure, saw that. I
Hi Dave,
NB: I'm not a DD, so cannot sponsor your package but I'll shall do my
best to give it a good review.
It would be great if you could file an RFS bug to track the sponsorship
of this package (https://mentors.debian.net/sponsors/rfs-howto)
On 10/01/15 12:24, Dave Maiorino wrote:
> Hello De
Hi!
I'm trying to create a package for 'git-p4', a python script which
mirrors between git and Perforce (the latter is a proprietary version
control system). I'm looking for advice on the best way to do this.
The source code lives in the upstream git repository, but isn't packaged
with the
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "pyepr":
* Package name: pyepr
Version : 0.8.2-1
Upstream Author : Antonio Valentino
* URL : http://avalentino.github.com/pyepr
* License : GPL-3.0+
Secti
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "epr-api":
* Package name: epr-api
Version : 2.3~dev20140814b-1
Upstream Author : Brockmann Consult
* URL : http://github.com/bcdev/epr-api
* License : GPL-
On Fri, 09 Jan 2015 14:00:27 +1100 Ben Finney wrote:
> Riley Baird
> writes:
[...]
> > First, it have no LICESNSE file, only main source file mention
> > modified BSD. I twice mailed author, but seems that he ignored my
> > request to add full-fledged LICENSE file.
>
> The Debian Project should
On Fri, 09 Jan 2015 13:35:49 +1100 Riley Baird wrote:
[...]
> And third, pure technical problem is that package
> provides binaries `fbpdf` and `fbpdf2`, functionally identical, but
> having different dependencies. I am not sure what to do with it.
[...]
I would suggest to prepare two distinct bi
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "osmosis"
Package name: osmosis
Version : 0.43.1-3~exp1
Upstream Author : Brett Henderson
URL : http://wiki.openstreetmap.org/wiki/Osmosis
License : public
Hello Debian Mentors,
I apologize for the wide email, but I was looking for help with getting
my package submitted into the Debian repo.
https://mentors.debian.net/package/tz-converter
Last year, I have received great help with correcting this package and
making it ready for building. I am w
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "live-f1"
* Package name: live-f1
Version : 0.2.11-1
* URL : https://code.launchpad.net/~davepusey/live-f1/live-f1
* License : GPL-2
Section
14 matches
Mail list logo
