Dmitrijs Ledkovs wrote:
2009/1/29 Eduardo M KALINOWSKI edua...@kalinowski.com.br:
I'd say it depends on what you are doing. If you are building on the
work already there, keep the changelog. But if you are ignoring
upstream's debian/ directory and starting your packaging from scratch,
you
2009/1/30 Eduardo M KALINOWSKI edua...@kalinowski.com.br:
Wasn't it a debian/changelog file, describing the releases upstream has
made?
Yes, so I was thinking about just appending changes to the original file.
(If the program gets packaged in Debian, upstream agrees not to
create his own
2009/1/28 Adeodato Simó d...@net.com.org.es:
(The recommendation above is my opinion, and there are other DDs who
think different. Me, I believe having a readable diff.gz is motivation
enough as to repack the tarball.)
OTOH, reading the policy manual I get the idea that a pristine
original
Dmitrijs Ledkovs wrote:
I have a similar question. Upstream has file ./debian/files in their
tarball.
Lintian complained about that file so I've deleted it. But during build in
pbuilder it gets added back from the orig tarball. How to handle this?
That's because such change cannot be
Luca Niccoli wrote:
A related question:
The original debian/ contains a changelog, which documents the past
releases (packaged in .deb for i386 by upstream); should I get rid of
that or keep it/import it?
I'd say it depends on what you are doing. If you are building on the
work already
2009/1/29 Eduardo M KALINOWSKI edua...@kalinowski.com.br:
I'd say it depends on what you are doing. If you are building on the
work already there, keep the changelog. But if you are ignoring
upstream's debian/ directory and starting your packaging from scratch,
you can drop it.
By keep the
Hi DD,
I found a very nice little program to take pictures from a webcam, and
I would like to package it.
The original tarball already contains a debian subdirectory (which
needs some corrections anyway), how should I deal with that?
If I dh_make straight after unpacking the tarball, dh_make
Luca Niccoli wrote:
The original tarball already contains a debian subdirectory (which
needs some corrections anyway), how should I deal with that?
If I dh_make straight after unpacking the tarball, dh_make won't
modify the debian subdirectory; but I wonder if removing it beforehand
will
2009/1/28 Al Nikolov a.niko...@drweb.com:
Luca Niccoli wrote:
The original tarball already contains a debian subdirectory (which
needs some corrections anyway), how should I deal with that?
If I dh_make straight after unpacking the tarball, dh_make won't
modify the debian subdirectory; but I
Hi
Dne Wed, 28 Jan 2009 15:59:03 + (BST)
Dmitrijs Ledkovs dmitrij.led...@gmail.com napsal(a):
I have a similar question. Upstream has file ./debian/files in their tarball.
Lintian complained about that file so I've deleted it. But during build in
pbuilder
it gets added back from the
On Wed, Jan 28, 2009 at 03:59:03PM +, Dmitrijs Ledkovs wrote:
I have a similar question. Upstream has file ./debian/files in their tarball.
Lintian complained about that file so I've deleted it. But during build in
pbuilder
it gets added back from the orig tarball. How to handle this?
On Wed, 2009-01-28 at 16:17 +0100, Luca Niccoli wrote:
I found a very nice little program to take pictures from a webcam, and
I would like to package it.
The original tarball already contains a debian subdirectory (which
needs some corrections anyway), how should I deal with that?
If I
I recommend that you repack your tarball, renaming the debian
directory inside it to debian-upstream or something similar. And you
should check with upstream if they'd be willing to stop shipping
debian/* in their next releases.
(The recommendation above is my opinion, and there are other DDs who
On Thu, Jan 29, 2009 at 12:17 AM, Luca Niccoli lultimou...@gmail.com wrote:
The original tarball already contains a debian subdirectory (which
needs some corrections anyway), how should I deal with that?
Once lenny is released (hint hint) you will be able to just use the
dpkg-source v3 format,
14 matches
Mail list logo
