Before you give up, try this:
Install (or reinstall) git from https://git-scm.com/ and make sure to set
up the option to use Windows Secure Channel library.

[image: image.png]

It has solved a lot of issues for me with pharo + git on windows, and not
being able to clone via https.


On Tue, 23 Mar 2021 at 11:08, David Pennington <da...@totallyobjects.com>
wrote:

> This is way to complicated for 70 year old developer. Running the code on
> the github page loaded Seaside,inifile and Ston without fuss so why is it
> so difficult on Windows?
> I have given up and decided to set my Mac up to be on with the lid down
> and use that as a server as this is a low traffic Web site.
> Thanks for all your help.
> David
>
> On 23 Mar 2021 07:32, Sven Van Caekenberghe <s...@stfx.eu> wrote:
>
>
>
> > On 22 Mar 2021, at 19:05, Stéphane Ducasse <stephane.duca...@inria.fr>
> wrote:
> >
> > david
> >
> > did you succeed to clone or checkout a github repo from this machine and
> without pharo at all?
>
> This is indeed step one: make sure that you can check out code from
> git(hub) on the command line in Windows. Only if that works you can do the
> next steps.
>
> BTW, once you have a repository checked out, you can just point Iceberg to
> it and load code.
>
> PS: yes, you will also have to learn the basic of git(hub).
>
> > Because Pharo is just using libgit.
> >
> > S.
> >
> >> On 22 Mar 2021, at 18:58, David Pennington <da...@totallyobjects.com>
> wrote:
> >>
> >> Tried that. I got the following
> >>
> >> Failed to get server certificate: the handle is in the wrong state for
> the requested operation.
> >>
> >> I assume that someone thinks that this is helpful:-)
> >>
> >> On 22 Mar 2021 16:06, Sanjay Minni <s...@planage.com> wrote:
> >> Hi David,
> >>
> >> I have repeatedly installed Seaside on Pharo 8 / 9 64 bit - Windows 10
> >> without any issues and I have done it both ssh and https
> >>
> >> I do it quickly / simply by
> >>
> >> tools->iceberg->[+ add]    (on top panel right)
> >> on popup select: 'clone from github.com'
> >> fill in owner: SeasideSt                            (case does not
> matter)
> >>        project: seaside
> >>        local directory:                           (leave the default
> for
> >> now)
> >>        protocol                                      try https first
> (not
> >> sure if github requires a password)
> >>                                                          or ssh which
> may be
> >> slightly complicated
> >> once seaside libraries are pulled in and seaside appears in the iceberg
> >> panel then
> >> right click on seaside
> >>          on popup scroll down to metacello->install baseline (default)
> >>
> >> hope that works
> >>
> >>
> >>
> >>
> >> Long Haired David wrote
> >> > Hi everyone.
> >> >
> >> > I have been developing a new web site using Seaside on my M1
> MacBookAir
> >> > and I have had no issues.
> >> >
> >> > To deploy it, I have to install Pharo on either a Windows 10 or a
> Windows
> >> > Server 2012 server. Pharo has installed on both without any issues.
> >> > However, I am having problems installing Seaside.
> >> >
> >> > I have Pharo 8.0 installed on both (64 bit version).
> >> >
> >> > If I try and install from the Catalog, I get the following error in
> the
> >> > Transcript.
> >> >
> >> > IceGenericError: Failed to stat file
> >> > 'C:/Users/david/Documents/Pharo/images/Pharo 8.0 - 64bit
> >> > (stable)/pharo-local.
> >> >
> >> > If I try using Monticello, I get the following:
> >> >
> >> > Metacello new
> >> > baseline:'Seaside3';
> >> > repository: 'github://SeasideSt/Seaside:master/repository';
> >> > load
> >> > I got an error while cloning: There was an authentication error while
> >> > trying to execute the operation: .
> >> > This happens usually because you didn't provide a valid set of
> >> > credentials.
> >> > You may fix this problem in different ways:
> >> >
> >> > 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in
> your
> >> > command line.
> >> > 2. adding your keys in settings (open settings browser search for
> "Use
> >> > custom SSH keys" and
> >> > add your public and private keys).
> >> > 3. using HTTPS instead SSH (Just use an url in the form
> HTTPS://etc.git).
> >> > I will try to clone the HTTPS variant.
> >> >
> >> > Can you help please?
> >> >
> >> > David
> >> > Totally Objects
> >>
> >>
> >>
> >>
> >>
> >> -----
> >> cheers,
> >> Sanjay
> >> --
> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> >>
> >>
> >
> > --------------------------------------------
> > Stéphane Ducasse
> > http://stephane.ducasse.free.fr / http://www.pharo.org
> > 03 59 35 87 52
> > Assistant: Aurore Dalle
> > FAX 03 59 57 78 50
> > TEL 03 59 35 86 16
> > S. Ducasse - Inria
> > 40, avenue Halley,
> > Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
> > Villeneuve d'Ascq 59650
> > France
> >
>
>
>

Reply via email to