Bug#646301: libcwiid1: should debian use github instead of the svn as upstream?
Hi Romain! I am collaborating to a project who makes extensive use of cwiid. We are having several issues due to the obsolescence of svn-based cwiid compared to the github fork, and all of them could be fixed updating the package. Since the original reporter of this bug doesn't seemed interested anymore, I would be glad to help you in this effort. What's your mind about that? -- Andrea Colangelo | http://andreacolangelo.com Ubuntu Developer | Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646301: libcwiid1: should debian use github instead of the svn as upstream?
Hi, 2011/10/23 Erik Saule : > On Sun, Oct 23, 2011 at 02:04:09AM +0200, Romain Beauxis wrote: >> 2011/10/23 Erik Saule : >> > Dear debian developpers, >> >> Hi Erik, >> >> > Should Debian really keep on using the svn of cwiid as upstream? The >> > developement of cwiid is mainly done on github[1] these days according >> > to the main devleopper[2]. >> > >> > Actually, the bug reported in [3] is already fixed upstream by commit >> > [4]. >> >> Its funny I received your first report at the time I got back on >> working on cwiid. >> >> I have absolutely nothing against pulling a github fork for a new >> package. However, I have not been following the clones saga a lot >> concerning cwiid so I am a bit lost finding which one should be used. > > I am not too sure yet as well. But I can have a look at the different > patches proposed. There is one safe choice which is following the git > branch of the original developper. It is a direct extension of the svn > and he cherry picked patches from here and there. for instance the bug > report I was pointing to comes from a third party on git hub. > >> I see that you seem interested in having a good cwiid package in >> Debian. Would you be interested in (co)maintaining it? I would be very >> pleased to setup a shared repository. > > I am all for having good packages in Debian but I do not have so much > experience in packaging for Debian (or an other Linux distribution > actually). On a personal I am currently trying to hook up wii > controllers to my PC and change the configuration of the controller > depending on which application you are currently running. Which is why > I needed a couple patches in wminput (the patch is actually already in > github). > > I have been trying to contribute back to Debian for quite some > time. cwiid might just be the way to do that. > > For the question of which git hub variant to follow. I guess I can > have a look at which features/patches/bugfixes are available on github > and try to federate them. I am not sure why they are still forks right > now. I am not sure if there are some underlying problems (or > developpers social issues) or if they just did not see the point in > merging. I have setup a collaborative maintenance repository: http://anonscm.debian.org/gitweb/?p=collab-maint/cwiid.git You should register to alioth and request commit access to the collab-maint project there: http://alioth.debian.org/projects/collab-maint/ Some documentation on using collab-main is online there: http://wiki.debian.org/Alioth/PackagingProject Some documentation about using git for packaging is available there: http://wiki.debian.org/PackagingWithGit Let me know if you need help/information. Romain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646301: libcwiid1: should debian use github instead of the svn as upstream?
2011/10/23 Erik Saule : > Dear debian developpers, Hi Erik, > Should Debian really keep on using the svn of cwiid as upstream? The > developement of cwiid is mainly done on github[1] these days according > to the main devleopper[2]. > > Actually, the bug reported in [3] is already fixed upstream by commit > [4]. Its funny I received your first report at the time I got back on working on cwiid. I have absolutely nothing against pulling a github fork for a new package. However, I have not been following the clones saga a lot concerning cwiid so I am a bit lost finding which one should be used. I see that you seem interested in having a good cwiid package in Debian. Would you be interested in (co)maintaining it? I would be very pleased to setup a shared repository. Romain > [1] https://github.com/abstrakraft/cwiid > [2] http://abstrakraft.org/cwiid/wiki > [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636691 > [4] > https://github.com/abstrakraft/cwiid/commit/b54bd057fe6b258d6e0a99047f839891ab3bc2df > > -- System Information: > Debian Release: 6.0.2 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages libcwiid1 depends on: > ii libbluetooth3 4.66-3 Library to use the BlueZ Linux > Blu > ii libc6 2.11.2-10 Embedded GNU C Library: Shared > lib > > libcwiid1 recommends no packages. > > libcwiid1 suggests no packages. > > -- no debconf information > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646301: libcwiid1: should debian use github instead of the svn as upstream?
Package: libcwiid1 Version: 0.6.00+svn201-2+b2 Severity: wishlist Dear debian developpers, Should Debian really keep on using the svn of cwiid as upstream? The developement of cwiid is mainly done on github[1] these days according to the main devleopper[2]. Actually, the bug reported in [3] is already fixed upstream by commit [4]. [1] https://github.com/abstrakraft/cwiid [2] http://abstrakraft.org/cwiid/wiki [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636691 [4] https://github.com/abstrakraft/cwiid/commit/b54bd057fe6b258d6e0a99047f839891ab3bc2df -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libcwiid1 depends on: ii libbluetooth3 4.66-3 Library to use the BlueZ Linux Blu ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib libcwiid1 recommends no packages. libcwiid1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
