Laura Arjona Reina wrote:
> First, thanks for your reviews and I'm sorry you are finding problems
> to contribute more comfortably with the change of the repository from
> Subversion to Git.
I'm sorry to be always moaning about it, but git really does seem to
involve jumping through a lot of mystifying extra hoops.
[...]
> * The command you used for cloning the git repo (if you remember it)
Well, Bash remembers it! It was:
git clone git://anonscm.debian.org/publicity/dpn.git
I see now that the HowToContribute page suggests that people without
Alioth accounts should run
git clone https://anonscm.debian.org/git/publicity/dpn.git dpn
to access the repository anonymously. If "anonymously" means "in a
manner that will make it impossible to follow the rest of these
instructions", that should probably be mentioned.
> * If you cloned the DPN repo in dpn folder, it's interesting to know
> the contents of the file dpn/.git/config, in particular, the "url"
> where you push to . Mine is like this:
>
> [core]
> repositoryformatversion = 0
> filemode = true
> bare = false
> logallrefupdates = true
> [remote "origin"]
> url = ssh://git.debian.org/git/publicity/dpn.git
Aha! Mine has:
url = git://anonscm.debian.org/publicity/dpn.git
So maybe I should start again with:
git clone ssh://git.debian.org/publicity/dpn.git
And in fact I see that's mentioned on the HowToContribute page. But
when I scrub my existing dpn directory and try the above, I get:
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
