On 06/04/16 15:46, Andreas Tille wrote:
As for the git repository, may I ask why you need to create one? Would that be a local debian copy of the one on github? Makes me think that it would be time to synchronize our local repos and the github one...The Debian *packaging* repository is different from your development repository - at least in the most frequently used workflow for Debian packaging. This repository stores only *release tarballs* (thus my request for tagging releases) and the debian packaging is what is kept track of (which you do not want inside your upstream code).
+1 for tagging your releases. It defines from which commit the official release tarball originated, which helps for sending our patches for
inclusion upstream.
There are other workflows where the Debian repository is using a clone from Github (or whereever the repository can be found) but as I said this is an unusual case which is used very less in our team.
One such example is this one: https://anonscm.debian.org/cgit/debian-science/packages/python-arrayfire.git Regardless of the choice of packaging repository layout, the important thing is that the upstream branch (containing the upstream source) and the packaging branch (containing the debianized source) are clearly separated. Hope this helps, Ghis