On Thu, Dec 04, 2008 at 07:00:16PM +0100, Guido G�nther wrote: > On Fri, Dec 05, 2008 at 01:40:26AM +0800, Kanru Chen wrote: > > Hi Guido, > > On Thu, Dec 04, 2008 at 06:10:46PM +0100, Guido G�nther wrote: > > > severity 507758 normal > > > thanks > > > > > > Hi Kanru, > > > On Thu, Dec 04, 2008 at 04:38:34PM +0800, Kanru Chen wrote: > > > > % git ls-tree pristine-tar > > > > 100644 blob 88d2a593066694d4bbb7dfdda2846b182f749018 > > > > libchewing_0.3.2.orig.tar.bz2.delta > > > > 100644 blob 7a84e8459fe0872b18183cb2f8e0af3b5f61ab53 > > > > libchewing_0.3.2.orig.tar.bz2.id > > > > > > > > Did I miss something? > > > Version one source format only handles tar.gz. Are you using a newer > > > source format? If you want an orig.tar.gz exported you need to import it > > > as such. But maybe I'm misunderstanding what you're trying to do. > > > -- Gudio > > > > The upstream tarball are imported by git-import-orig. The manpage says > > it can either be gzip or bzip2 compressed tar archive. > > > > All I did was import then run git-buildpackage. > Yes, git-import-orig can handle bzip2 and gzip for *import* but you'll > need a .tar.gz for *building* the package (see dpkg-source, Version 1 > Format). > So building without --pristine-tar will do what you want - it will > create an .orig.tar.gz for you from the upstream branch. > Cheers, > -- Guido
Ah, I got it. Since the .tar.bz2 must be converted to .tar.gz when building, so building with --pristine-tar makes no sense :) You can close this bug, thank you. Regards, Kanru
signature.asc
Description: Digital signature
