>>> Well, git-debrebase does, and is as compliant with DEP-14 as you'd like >>> it to be. >> >> There is gbp pq, which is probably more widely used. > > Right. Both are good.
In fact my question was more. I would like, something like dgit clone <package> or gbp clone <package> and get a a DEP-14 organized repository, where the upstream/latest point to the upstream git repository. So where do we put the upstream git URL If I read this part of DEP-14, I have the information that the remote should be named 'upstreamvcs' but nothing about where to put this url in our Debian files. If I need to find and add manually these information each time I checkout a debian package, It is not viable. --- DEP-14 [...] Coexistence with the upstream Git repository As a package maintainer, it is often helpful to have access to the upstream Git repository from one's personal checkout of the packaging Git repository. When setting up access to the upstream repository with git remote add it is recommended to use upstreamvcs as the name of the remote so that tools can more easily identify the upstream branches and commits. The naming conventions recommended in this document ensure that names of the upstream branches (ex: master, main, devel, 9.x) are unlikely to clash with the packaging branches. Despite this, it is good practice to not push any upstream branch to the packaging repository so as to not confuse anyone about the purpose of the Git repository. However to make it convenient to inspect the upstream history and compare it to the packaged version, when this doesn't have adverse consequences (such as an unreasonable repository size), the upstream history should be made available in the packaging repository by pushing the upstream release tags alongside with the tags of the packaging branches. [...] Cheers Fred
