Hi Vincent. On Wed, May 11, 2016 at 09:43:33PM +0200, Vincent Zweije wrote: > > In the mean time, I've cloned upstream git from > https://github.com/xelerance/xl2tpd.git and checked it out. It seems > to build fine. I still have to figure out what current bugs are fixed > upstream, I'll get onto that. > > There are some commits by you but I guess that is not the history that > you're talking about. I'd like to take a look at your repo. If you can > put it up somewhere I'll clone it. Do you mind if I make it public? > I'm sorry I missed your previous mail. I am apparently not subscribed to this bug. I have pushed my local xl2tpd repository here: http://anonscm.debian.org/cgit/users/roberto/xl2tpd.git/ Of course, you are welcome to make it public :-) As far as the upstream repository goes, upstream previously tried to always merge my Debian packaging into their repository. Of course, they did it on the master branch (probably owing to the fact that they were probably still on Subversion when they began this practice). In any event, it caused problems every time I tried to make a new upstream release. If you look in the debian/ directory if repo I just published, you will see a repack.sh script. That script removes upstream's debian/ directory and a non-free RFC text that they ship in their tarball. Let me know if you have any other questions or if you require any additional information. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
Attachment:
signature.asc
Description: Digital signature