Question thread #9

[pauamma]

It's been way too long since the last question thread (why didn't anyone poke me?) so let's have another one!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer.

Comments

[kimira]

Weird, I have used it since the switch to github and never had a problem before. I just followed the instructions in the newbie windows guide on the wiki, which I also followed this time. Although it has been several months since the last time I was on it so I don't know if something changed since then. Will try this...

It won't let me do git remote add because remote dreamwidth already exists... But I tried it with git remote set-url and that didn't give me an error at least.

Ahhh, but then when I tried to run the dwu script, seems I'm getting that error still:

Switched to branch 'develop'
From https://github.com/dreamwidth/dw-free
* branch develop -> FETCH_HEAD
Already up-to-date.
Switched to branch 'master'
From https://github.com/dreamwidth/dw-free
* branch master -> FETCH_HEAD
Already up-to-date.
Password for 'http://kimira@github.com':
Counting objects: 5452, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (1229/1229), done.
error: RPC failed; result=22, HTTP code = 411
fatal: The remote end hung up unexpectedly
Writing objects: 100% (4654/4654), 2.93 MiB, done.
Total 4654 (delta 3403), reused 4643 (delta 3392)
fatal: The remote end hung up unexpectedly
Everything up-to-date

[denise]

hm. okay, now we're really past my knowledge! i will put up the bat-signal :)

[kimira]

Wait, think I may have figured it out. At least it worked for dwu without throwing that error so I'll see if it works for the branch push as well. From that post you linked I did "git config --list" and noticed that the remote.origin.url also wasn't https, so changed that one also and then it didn't give me that error.

Worked. for the branch push too! Yay.

[afuna]

Oh hey try opening up $LJHOME/.git/config. Look for all instances of http://... And change them to https:// manually :) should be fine after they

[kimira]

Ha thank you, yup, that was the problem. That blog post denise linked helped me figure it out. Although this would have been an easier way of changing it instead of looking up what commands I had to use. XD

[swaldman]

Yeah, git just loves its config commands, when editing the files tends to be simpler ;-)

[afuna]

Heeheehee. Glad it all worked out!