Hi Michael,

About your package at mentors uploaded there on 2012-08-03 08:00.  You wrote
this in debian/copyright :

  |  Source: http://sourceforge.net/projects/viennacl/files/
  |   The repacked source as used in the upload of this package was obtained by
  |   using git-import-orig(1) as follows:
  |     $ git import-orig --uscan --filter-pristine-tar \
  |         --filter="*/TU_Signet_CMYK.eps"
  |   .
  |   To obtain the exact same file, use the following:
  |     $ git clone git://git.debian.org/debian-science/packages/viennacl.git
  |     $ cd viennacl
  |     $ git branch -t pristine-tar origin/pristine-tar
  |     $ pristine-tar export ../viennacl_1.3.0+dfsg.orig.tar.gz
  |   .
  |   The equivalent repackaged source without using git and pristine-tar can be
  |   created by following these steps:
  |     $ wget 
http://sourceforge.net/projects/viennacl/files/1.3.x/ViennaCL-1.3.0-src.tar.gz
  |     $ gunzip ViennaCL-1.3.0-src.tar.gz
  |     $ tar --delete -f ViennaCL-1.3.0-src.tar 
ViennaCL-1.3.0-src/doc/manual/figures/TU_Signet_CMYK.eps
  |     $ mv ViennaCL-1.3.0-src.tar viennacl_1.3.0+dfsg.orig.tar
  |     $ gzip -9 viennacl_1.3.0+dfsg.orig.tar

You write "using git-import-orig(1)" but then you write "$ git import-orig",
not "$ git-import-orig".

The part about git.debian.org doesn't belong here because that is about getting
the already repackaged upstream source code, not about retrieving the upstream
source code from upstream and reproducing the repackaging.

The last part doesn't include renaming the top directory as documented here:
http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-origtargz
"A repackaged .orig.tar.{gz,bz2,xz} should use
packagename-upstream-version.orig as the name of the top-level directory in its
tarball."

Regards,

Bart Martens


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120804070806.gf27...@master.debian.org

Reply via email to