On Tue, Apr 05, 2011 at 05:49:19PM -0430, Miguel Landaeta wrote:
> On Tue, Apr 05, 2011 at 12:27:16PM -0430, Miguel Landaeta wrote:
> > Anyway, maybe what I already did[1] could be useful to update sshuttle to
> > a newer version.
> 
> Hi, it's me again...

Hi there.

> I'm not a DD/DM or anything, but I attached a debdiff that could be
> useful and below is the changelog of the updated version that I'm
> using while the version in Debian is updated:

Thanks for the info, many of the patches upstream I made do not apply anymore
because I allready provided them to Avery Pennarun and he kindly included
them in the upstream version.

>   * Add patch to document missing flag in manpage.

This patch should probably go upstream, did you report it?

>   * Drop manpage from Debian in favor of the one provided by upstream.

Well, I believe upstream's is actually the one I wrote so I guess this is OK.

>   * Update Homepage and Vcs-* fields. Vcs-* field should point to Debian
>     packaging repositories.

Not unless the maintainer (me) decides he wants to use the packaging repos
you propose :)

>   * Disabled debian-changes* patches since they don't apply cleanly anymore.
>     They weren't dropped because I don't know if upstream solved those issues.

I think I submitted all upstream, but I have to double check.

> Also, I created a git repo for this package in Alioth (collab-maint),
> but I really don't know if that is compatible with the workflow of
> the maintainer.

It is not compatible with the current workflow, but I don't mind introducing
collab-maint if others want to cooperate in the maintenance of the package.

> 
> Anyway, I think this package should be maintained with some kind of
> repository.

I don't usually feel the need to put it up in an online repository unless
there is somebody that wants to co-maintain the package. If you want to
contribute and co-maintain to the package I'm open to using collab-maint as
the main repository, even if that is not what I'm using now.

I would, however, like to import the past history of the package to the
repository first instead of starting from this upstream version.

Regards

Javier

Attachment: signature.asc
Description: Digital signature

Reply via email to