Hi Dominique,
I've got an explicit pointer to this mail[1] (I admit I was a bit distracted
at that time (flu) ).
On Sat, Mar 10, 2018 at 06:36:42PM +0100, Dominique Dumont wrote:
> Since a lot of people are going to migrate their package repo from alioth to
> salsa, I've created a small script for cme to help update debian/control file
> for this new package repository.
>
> Once you have updated your repo to the new remote (can be on salsa or
> anywhere
> else), run
>
> cme run set-vcs-git
>
> This command will update Vcs-Browser and Vcs-Git in debian/control (from the
> url of the "origin" remote) and commit the change.
I confirm this works nicely, specifically I like the "commit" feature. (My
workflow is "cme fix ...; git diff ; git commit" - at first sight I assumed
nothing had happened since `git diff` was empty ;-) )
> This new script is available from libconfig-model-dpkg-perl 2.106 (and
> requires cme package)
Thanks a lot.
In the discussion about the new lintian warning[2] I said: "I will not
change Vcs fields until cme is doing this for me." To be more precise I
would now rather say:
... before `cme fix dpkg-control` is doing it for me.
While I disagree with the opinion of Alioth admins that there should be
no chance to save anonscm.d.o ("Because it wouldn't work." is no
sensible reason for me) it seems I need to face reality that things will
not happen if I do not setup a redirector for anonscm.d.o myself. Do you
see any chance to add the set-vcs-git feature to
cme fix dpkg-control
? If lintian claims d/control is wrong cme could do this in the "fix"
step. Does this make sense to you?
BTW, can you explain the philosophy behind `cme run` and `cme fix`. Or
in other words, why is this
$ cme fix set-vcs-git
Can't locate model for application 'set-vcs-git'.
Run 'cme list' for the list of models available on your system.
You may need to install another Config::Model Perl module.
See the available models there:
https://github.com/dod38fr/config-model/wiki/Available-models-and-backends
$ cme run dpkg-control
Error: cannot find script dpkg-control
not working?
As always thanks a lot for providing very useful features for cme
Andreas.
[1] https://lists.debian.org/debian-devel/2018/03/msg00384.html
[2] https://lists.debian.org/debian-devel/2018/03/msg00382.html
--
http://fam-tille.de
