Hello there,
I got the following situation:
Upstream of a software package releases only a .zip-File containing only
both source and binaries. So, I need to build my own orig.tar.gz .
Now, if i build my orig-Tarball and exclude the binaries, do I have to
append something to the version string
Hi!
* Stefan Denker stefan+deb...@dn-kr.de [110623 10:03]:
Upstream of a software package releases only a .zip-File containing only
both source and binaries. So, I need to build my own orig.tar.gz .
Now, if i build my orig-Tarball and exclude the binaries, do I have to
append something to
Le jeudi 23 juin 2011 10:03:15, Stefan Denker a écrit :
Hello there,
I got the following situation:
Upstream of a software package releases only a .zip-File containing only
both source and binaries. So, I need to build my own orig.tar.gz .
Now, if i build my orig-Tarball and exclude the
Hi!
* Thomas Preud'homme robo...@celest.fr [110623 11:37]:
Now, if i build my orig-Tarball and exclude the binaries, do I have to
append something to the version string to mark that I modified the
source tarball?
Usually we use upstreamversion+dfsg1-1.
dfsg is used when the tarball was
On Thu, 23 Jun 2011 11:37:18 +0200, Thomas Preud'homme wrote:
Le jeudi 23 juin 2011 10:03:15, Stefan Denker a écrit :
Now, if i build my orig-Tarball and exclude the binaries, do I have to
append something to the version string to mark that I modified the
source tarball?
Usually we use
Le Thu, Jun 23, 2011 at 10:03:15AM +0200, Stefan Denker a écrit :
if i build my orig-Tarball and exclude the binaries, do I have to
append something to the version string to mark that I modified the
source tarball?
Dear Stefan,
please note the other recommendations when repacking upstream
Le jeudi 23 juin 2011 11:44:17, Alexander Reichle-Schmehl a écrit :
Hi!
* Thomas Preud'homme robo...@celest.fr [110623 11:37]:
Now, if i build my orig-Tarball and exclude the binaries, do I have to
append something to the version string to mark that I modified the
source tarball?
7 matches
Mail list logo