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-specific-monticello-packages-programatically



--
View this message in context: http://forum.world.st/cannot-commit-with-gofer-to-sthub-HTTP-403-tp4707412p4707523.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.