[EMAIL PROTECTED] wrote:
>
> this also means that you or upstream will have to be around 24/7 as your
> package is not NMU-able, as other developers don't have access to your svn.
>
Correct me if I am wrong, but a NMU should be based on the sources most
recently uploaded to Debian. The NMU diff
> This can always be done in SVN/CVS, and the Debian package version can be
> increased like +r620.
this also means that you or upstream will have to be around 24/7 as your
package is not NMU-able, as other developers don't have access to your svn.
--
Bernd Zeimetz
<[EMAIL PROTECTED]>
On Thu, 28 Jun 2007 10:32:53 +0100
Jonny Lamb <[EMAIL PROTECTED]> wrote:
> What I have found is that, assuming one is not using any
> $vcs-buildpackage tool, it's okay to have the debian/ directory in the
> appropriate directory in the vcs. However, only if you do not include it
> in EXTRA_DIST.
>
On Wed, 2007-06-27 at 11:07 -0300, Tiago Saboga wrote:
> I am working closely with upstream devs, and I am willing to manage
> the debian files in the same sourceforge cvs. I understand that the
> upstream tarball should not contain the debian files; OTOH,
> sourceforge asks that all files in cvs s
On Wed, Jun 27, 2007 at 08:49:47PM -0400, Roberto C. Sánchez wrote:
> On Thu, Jun 28, 2007 at 07:50:58AM +1000, Matthew Palmer wrote:
> > On Wed, Jun 27, 2007 at 10:59:12AM -0500, Raphael Geissert wrote:
> > > On 27/06/07, Tiago Saboga <[EMAIL PROTECTED]> wrote:
> > > >I am working closely with ups
On Thu, Jun 28, 2007 at 07:50:58AM +1000, Matthew Palmer wrote:
> On Wed, Jun 27, 2007 at 10:59:12AM -0500, Raphael Geissert wrote:
> > On 27/06/07, Tiago Saboga <[EMAIL PROTECTED]> wrote:
> > >I am working closely with upstream devs, and I am willing to manage
> > >the debian files in the same sou
On Wed, Jun 27, 2007 at 10:59:12AM -0500, Raphael Geissert wrote:
> On 27/06/07, Tiago Saboga <[EMAIL PROTECTED]> wrote:
> >I am working closely with upstream devs, and I am willing to manage
> >the debian files in the same sourceforge cvs. I understand that the
> >upstream tarball should not conta
On Wed, Jun 27, 2007 at 11:07:17AM -0300, Tiago Saboga wrote:
> I am working closely with upstream devs, and I am willing to manage
> the debian files in the same sourceforge cvs. I understand that the
> upstream tarball should not contain the debian files; OTOH,
> sourceforge asks that all files i
On 27/06/07, Pádraig Brady <[EMAIL PROTECTED]> wrote:
. I include /debian in my snapshot tarballs to allow
others to build debian packages easily
This is one of the main reasons why I want to include debian/ from upstream.
. allowing new Debian revisions without bumping the version for
2007/6/27, Pádraig Brady <[EMAIL PROTECTED]>:
Justin Pryzby noted to me previously that,
advantages for having debian/ in the .diff.gz rather
than the orig.tar.gz are:
. more conventional
. not confusing other people using other distributions
. allowing new Debian revisions without bumping the
Here's what I do to release my package,
(Well more accurately, what I will do for the next version):
http://www.pixelbeat.org/docs/linux_project_release_process/
The pertinent bits from there, relating to your question are:
. I include /debian in my upstream repository root
. I include /debian
Hello,
On 27/06/07, Tiago Saboga <[EMAIL PROTECTED]> wrote:
Hi!
I am working closely with upstream devs, and I am willing to manage
the debian files in the same sourceforge cvs. I understand that the
upstream tarball should not contain the debian files;
I'm not quite sure, but I think that
Hi
On Wed, 27 Jun 2007 11:07:17 -0300
Tiago Saboga <[EMAIL PROTECTED]> wrote:
> I have made a package for OmegaT, a computer-aided translation tool.
> Unfortunately, it is not yet suitable for inclusion in debian, because
> it depends on htmlparser which build-depends on maven2, which is being
>
Hi!
I have made a package for OmegaT, a computer-aided translation tool.
Unfortunately, it is not yet suitable for inclusion in debian, because
it depends on htmlparser which build-depends on maven2, which is being
packaged by the java team. For now, I plan to have the deb package
available on the
14 matches
Mail list logo
