Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "openconnect"
* Package name: openconnect
Version : 3.15-1
Upstream Author : David Woodhouse
* URL : http://www.infradead.org/openconnect/
* License :
Daniel Pocock writes:
> I'm just trying to establish the pattern I should be following
> a) for those projects where I have no role, no commit rights, etc, I
> presume that I should just use git-buildpackage, create a distinct
> repository to track debian/ stuff, and follow the normal structure
Charles Plessy writes:
> Le Wed, Mar 28, 2012 at 02:29:22PM +0200, Michael Wild a écrit :
>> The only unpleasant side-effect I can think of is that git-dch will
>> probably be a bit noisy.
> Same for the commit emails. This is one of the reasons I still import
> tarballs from upstream projects
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "ndpmon"
* Package name: ndpmon
Version : 1.4.0-1
Upstream Author : frederic.b...@loria.fr
* URL : http://ndpmon.sourceforge.net/index.html
* License
Le Wed, Mar 28, 2012 at 02:29:22PM +0200, Michael Wild a écrit :
>
> The only unpleasant side-effect I can think of is that git-dch will
> probably be a bit noisy.
Same for the commit emails. This is one of the reasons I still import tarballs
from upstream projects that are maintained with Git:
On 28/03/2012 13:29, Michael Wild wrote:
On 03/28/2012 01:56 PM, Paul Wise wrote:
[...]
All the above is completely up to you as maintainer of the Debian packaging.
The only unpleasant side-effect I can think of is that git-dch will
probably be a bit noisy.
Haven't tried such a scheme mysel
On 03/28/2012 01:56 PM, Paul Wise wrote:
[...]
>
> All the above is completely up to you as maintainer of the Debian packaging.
>
The only unpleasant side-effect I can think of is that git-dch will
probably be a bit noisy.
Haven't tried such a scheme myself, though, since my upstream doesn't
ha
a) for those projects where I have no role, no commit rights, etc, I presume
that I should just use git-buildpackage, create a distinct repository to
track debian/ stuff, and follow the normal structure (master and upstream
branches)
The use of a VCS is completely optional for Debian packaging
In general, we like it if upstreams follow our guide:
http://wiki.debian.org/UpstreamGuide
On Wed, Mar 28, 2012 at 5:25 PM, Daniel Pocock wrote:
> I am involved in several projects where I am either the founder of the
> project (e.g. dynalogin) or a contributor with full access to the repository
I am involved in several projects where I am either the founder of the
project (e.g. dynalogin) or a contributor with full access to the
repository (e.g. Ganglia, reSIProcate, flactag)
There are also a couple of projects where I don't have any role, but I
would like to package the code for
10 matches
Mail list logo
