Re: Getting a fix into a package? What am I doing wrong?
On 29 May 2018 at 03:06, Paul Wise wrote: > On Mon, May 28, 2018 at 6:01 PM, Luke Diamand wrote: > >> I'm obviously doing something terribly wrong, but I have no idea what. > > I don't think you did anything wrong. > >> Can someone tell me the correct process for getting a bug fix in? > > Exactly what you did so far. > > I think the problem here is that there are more than 400 bug reports > filed against git and the Debian package maintainer doesn't have the > time to triage them all at every upload to see which ones are easy to > fix. In addition they probably have lots of other packages to attend > to, as well as real life. > > You could try to triage the git bugs and do as much as you can with > each bug (checking if they got fixed, diagnosing symptoms, coming up > with patches, forwarding upstream etc). This would help reduce their > workload. I'll take a look, thanks. > > https://wiki.debian.org/BugTriage > > You could try to contact the most active person (Jonathan Nieder) via > mechanisms other than email, like IRC. OK. > > In the meantime, there is an easy workaround: copy the script out of > the git source tree and use it. Yes, I'm actually a part-time maintainer of git-p4 itself, so I'm fairly familiar with the process! > >> Would it be better to just create a completely new package? How do I do that? > > git-p4 is part of the git project, so that would mean duplicating the > git source package, which is generally not an acceptable solution. > > PS: you might want to move off p4 if you can, since it is a proprietary VCS. Thanks for the advice, but because of reasons, that's not really an option at the moment ;-) Thanks! Luke
Getting a fix into a package? What am I doing wrong?
Hi! A few years ago, in 2014, I submitted a bug fix for the git package to add git-p4: It's here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773245 It seems to have just been forgotten and so far my attempts to get it unforgotten have failed. I'm obviously doing something terribly wrong, but I have no idea what. Can someone tell me the correct process for getting a bug fix in? Would it be better to just create a completely new package? How do I do that? Thanks Luke
Re: git-p4 package?
Hi! Last week I followed up about how to proceed with this package On 17 January 2017 at 08:15, Luke Diamand wrote: > [+Gerrit Pape's correct email address] But p...@smarden.org seems to be bouncing. I eventually received this: > Hi. This is the qmail-send program at a.mx.smarden.org. > I'm afraid I wasn't able to deliver your message to the following addresses. > This is a permanent error; I've given up. Sorry it didn't work out. > > : > No delivery confirmation received. Is that normal for a package maintainer's email address? Thanks Luke > > On 17 January 2017 at 00:17, Sean Whitton wrote: >> Dear Luke, >> >> On Mon, Jan 16, 2017 at 11:27:22PM +, Luke Diamand wrote: >>> I put in a patch to add a git-p4 package, here: >>> >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773245 >>> >>> I was wondering what I need to do next for this to be merged? Or if >>> I've done it wrong somehow? >> >> I haven't looked at the patch, but you haven't done anything wrong with >> regard to Debian procedures. It's simply a matter of waiting for a >> response from the maintainers of the git package. >> >> You could prepare an NMU of the git package and submit a request for >> sponsorship to DEFERRED, but that would be unusual for a bug of wishlist >> severity. Please read up on NMUs in the Debian Developer's Reference, >> so that you are properly informed of your options. > > > Thanks - an NMU seems to be a bit drastic!
Re: git-p4 package?
[+Gerrit Pape's correct email address] On 17 January 2017 at 00:17, Sean Whitton wrote: > Dear Luke, > > On Mon, Jan 16, 2017 at 11:27:22PM +, Luke Diamand wrote: >> I put in a patch to add a git-p4 package, here: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773245 >> >> I was wondering what I need to do next for this to be merged? Or if >> I've done it wrong somehow? > > I haven't looked at the patch, but you haven't done anything wrong with > regard to Debian procedures. It's simply a matter of waiting for a > response from the maintainers of the git package. > > You could prepare an NMU of the git package and submit a request for > sponsorship to DEFERRED, but that would be unusual for a bug of wishlist > severity. Please read up on NMUs in the Debian Developer's Reference, > so that you are properly informed of your options. Thanks - an NMU seems to be a bit drastic!
git-p4 package?
Hi! I put in a patch to add a git-p4 package, here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773245 I was wondering what I need to do next for this to be merged? Or if I've done it wrong somehow? Thanks Luke
Bug 773245 - git-p4 package - lost in space?
Hi! I submitted a patch to the git package back in December 2014 to add the git-p4 sub-package into contrib. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773245 It seems to be lost in space somewhere, drifting alone in the cold airless vacuum between the stars, tumbling forever towards oblivion. Is there any way that we could perhaps launch a rescue mission for it, perhaps sending someone out with a jet pack and a long rope? Could we ask Nasa to divert their next mission to Mars? It's dangerous and hazardous, and after a year in space it may already be dead, but what do we think? Is there any hope for it? Thanks! Luke
Re: git-p4 package in contrib, how to proceed?
Hi! (Resurrecting ancient thread) Has this moved on any further? I couldn't see any sign that there's now a git-p4 package, or any discussion saying that it can't go ahead for some other reason. Has it just been forgotten about? Thanks Luke On 14 January 2015 at 12:18, Luke Diamand wrote: > Great, thanks! > > I left the maintainer on the package as the same as the one for the main git > package. If it would be more appropriate for me to be the maintainer, then > I'm happy to do that (not that I have the first clue what it means or > involves!). > > > > > > > On 12 January 2015 at 18:32, Jonathan Nieder wrote: >> >> reassign 773245 src:git 1:2.1.3-1 >> quit >> >> Vincent Cheng wrote: >> >> > Yes, source packages in main can generate binary packages in contrib; >> > Policy does not prevent this from happening, and there are existing >> > source packages in main, in the archive, which generate binary >> > packages in contrib. See e.g. src:nvidia-settings (and #747837 which >> > was what prompted one of the binary packages built from it to be moved >> > from contrib to main). >> >> Thanks for looking into it. I'll apply the patch for git in jessie+1. >> >> Regards, >> Jonathan > >
Re: git-p4 package in contrib, how to proceed?
Great, thanks! I left the maintainer on the package as the same as the one for the main git package. If it would be more appropriate for me to be the maintainer, then I'm happy to do that (not that I have the first clue what it means or involves!). On 12 January 2015 at 18:32, Jonathan Nieder wrote: > reassign 773245 src:git 1:2.1.3-1 > quit > > Vincent Cheng wrote: > > > Yes, source packages in main can generate binary packages in contrib; > > Policy does not prevent this from happening, and there are existing > > source packages in main, in the archive, which generate binary > > packages in contrib. See e.g. src:nvidia-settings (and #747837 which > > was what prompted one of the binary packages built from it to be moved > > from contrib to main). > > Thanks for looking into it. I'll apply the patch for git in jessie+1. > > Regards, > Jonathan >
git-p4 package in contrib, how to proceed?
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 regular 'git' package because of the proprietary nature of Perforce. I thought I'd try to create a separate package that could go into contrib instead. I've created a bug report with a patch for the git package to implement this (773245) which Jonathan Nieder was kind enough to look at, but I'm struggling to understand what I should do next! Is it going to be possible to get the regular git package to generate a secondary package in contrib? Or would I be better off with a new standalone package? Thanks! Luke -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b16b92.4060...@diamand.org
