Re: best practices for security branches in pkg-java SVN repo

2011-02-14 Thread tony mancill
On 02/13/2011 11:13 AM, Vincent Fourmond wrote: > On Sun, Feb 13, 2011 at 7:42 PM, tony mancill wrote: >>> On 12/02/2011 19:02, Vincent Fourmond wrote: A question: do you think it is a good idea to update the debian/control Vcs fields to point to the branch directory ? My opinion

Re: best practices for security branches in pkg-java SVN repo

2011-02-13 Thread Vincent Fourmond
On Sun, Feb 13, 2011 at 7:42 PM, tony mancill wrote: >> On 12/02/2011 19:02, Vincent Fourmond wrote: >>>   A question: do you think it is a good idea to update the >>> debian/control Vcs fields to point to the branch directory ? My >>> opinion is that it should be, so that the control file of the

Re: best practices for security branches in pkg-java SVN repo

2011-02-13 Thread tony mancill
On 02/12/2011 02:24 PM, Giovanni Mascellani wrote: > Hi. > > On 12/02/2011 19:02, Vincent Fourmond wrote: >> A question: do you think it is a good idea to update the >> debian/control Vcs fields to point to the branch directory ? My >> opinion is that it should be, so that the control file of th

Re: best practices for security branches in pkg-java SVN repo

2011-02-12 Thread Giovanni Mascellani
Hi. On 12/02/2011 19:02, Vincent Fourmond wrote: > A question: do you think it is a good idea to update the > debian/control Vcs fields to point to the branch directory ? My > opinion is that it should be, so that the control file of the package > uploaded to squeeze-security corresponds to the

Re: best practices for security branches in pkg-java SVN repo

2011-02-12 Thread Vincent Fourmond
On Sat, Feb 12, 2011 at 6:51 PM, tony mancill wrote: > Are there established practices (i.e. naming conventions) for branching > in the SVN repo in order to provide support over the lifetime of stable? > > I need to prepare a security update for tomcat6 for squeeze and would > like to continue to

best practices for security branches in pkg-java SVN repo

2011-02-12 Thread tony mancill
Are there established practices (i.e. naming conventions) for branching in the SVN repo in order to provide support over the lifetime of stable? I need to prepare a security update for tomcat6 for squeeze and would like to continue to use the SVN repo, but also want to move forward for unstable.