cannot commit with gofer to sthub (HTTP 403)
Hi, It seems that I cannot commit with Gofer on STHub. I get a 403. If I do it via the regular Monticello browser, it works just fine. I am on the latest Pharo 2.0 and I use a script that goes like this: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/MooseAlgos/main/'; package: 'ConfigurationOfMooseAlgos'; commit: 'version generated by Snapshotcello' with the url being already authenticated beforehand. I also tried by passing the url:username:password: explicitly, but this has the same 403 effect. Anyone knows what the issue is? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"
which version of the image are you using? Stef
Hi,
It seems that I cannot commit with Gofer on STHub. I get a 403.
If I do it via the regular Monticello browser, it works just fine.
I am on the latest Pharo 2.0 and I use a script that goes like this: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/MooseAlgos/main/'; package: 'ConfigurationOfMooseAlgos'; commit: 'version generated by Snapshotcello'
with the url being already authenticated beforehand.
I also tried by passing the url:username:password: explicitly, but this has the same 403 effect.
Anyone knows what the issue is?
Cheers, Doru
-- www.tudorgirba.com
"Every thing has its own flow"
As I said, I was using the latest Pharo 2.0. Doru On Tue, Sep 10, 2013 at 9:36 AM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
which version of the image are you using?
Stef
Hi,
It seems that I cannot commit with Gofer on STHub. I get a 403.
If I do it via the regular Monticello browser, it works just fine.
I am on the latest Pharo 2.0 and I use a script that goes like this: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/MooseAlgos/main/'; package: 'ConfigurationOfMooseAlgos'; commit: 'version generated by Snapshotcello'
with the url being already authenticated beforehand.
I also tried by passing the url:username:password: explicitly, but this has the same 403 effect.
Anyone knows what the issue is?
Cheers, Doru
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
in the debugger, you may want to inspect the error to get more information about the problem On Tue, Sep 10, 2013 at 10:05 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
As I said, I was using the latest Pharo 2.0.
Doru
On Tue, Sep 10, 2013 at 9:36 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
which version of the image are you using?
Stef
Hi,
It seems that I cannot commit with Gofer on STHub. I get a 403.
If I do it via the regular Monticello browser, it works just fine.
I am on the latest Pharo 2.0 and I use a script that goes like this: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/MooseAlgos/main/'; package: 'ConfigurationOfMooseAlgos'; commit: 'version generated by Snapshotcello'
with the url being already authenticated beforehand.
I also tried by passing the url:username:password: explicitly, but this has the same 403 effect.
Anyone knows what the issue is?
Cheers, Doru
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
-- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Tudor Girba-2 wrote
with the url being already authenticated beforehand.
I also tried by passing the url:username:password: explicitly, but this has the same 403 effect.
Anyone knows what the issue is?
At least I know that second part: *If the repository is already present* in the image sending url:username:password: to a Gofer instance has no effect at all. So if your repository is in the image without username and password sending url:username: 'correctName' password: 'correctPassword' will change nothing. You have to manually edit the repository info. On the other hand - if you have a repository with correct username and password you can send url:username: 'someNonsense' password: 'wrongPassword' and everything will still work correctly. If you just get something via Gofer from a public repository you have the repository added by Gofer and when you later want to push to the repository via Gofer and provide your username and password - you get an error. That's why i was asking about programatically manipulating repositories: http://stackoverflow.com/questions/18100136/manipulating-repositories-for-sp... -- View this message in context: http://forum.world.st/cannot-commit-with-gofer-to-sthub-HTTP-403-tp4707412p4... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Hi, Yes, I know that. I was just saying that I tried multiple variations just in case someone wanted to know. The debugger is not particularly helpful here: I just get a 403 response which means that the authentication fails. I cannot see where the problem is. Cheers, Doru On Tue, Sep 10, 2013 at 7:22 PM, MartinW <wm@fastmail.fm> wrote:
Tudor Girba-2 wrote
with the url being already authenticated beforehand.
I also tried by passing the url:username:password: explicitly, but this has the same 403 effect.
Anyone knows what the issue is?
At least I know that second part: *If the repository is already present* in the image sending url:username:password: to a Gofer instance has no effect at all.
So if your repository is in the image without username and password sending url:username: 'correctName' password: 'correctPassword' will change nothing. You have to manually edit the repository info.
On the other hand - if you have a repository with correct username and password you can send url:username: 'someNonsense' password: 'wrongPassword' and everything will still work correctly.
If you just get something via Gofer from a public repository you have the repository added by Gofer and when you later want to push to the repository via Gofer and provide your username and password - you get an error.
That's why i was asking about programatically manipulating repositories:
http://stackoverflow.com/questions/18100136/manipulating-repositories-for-sp...
-- View this message in context: http://forum.world.st/cannot-commit-with-gofer-to-sthub-HTTP-403-tp4707412p4... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- www.tudorgirba.com "Every thing has its own flow"
participants (4)
-
Damien Cassou -
MartinW -
Stéphane Ducasse -
Tudor Girba