yes.
and please, people��� note that using ���stable��� should be the regular way.
we were using latest because we are so unstable that we needed to (and I cannot ensure we will not have other periods like that). But in general, users not trying to fix something on the edge, need to stay with the stable.
cheers!
Esteban
cheers -ben
On Mon, May 8, 2017 at 2:32 AM, Myroslava Romaniuk <
romaniuk@ucu.edu.ua> wrote:
Which one is the stable VM then?
On 7 May 2017 21:07, "Esteban Lorenzano" <estebanlm@gmail.com> wrote:
are you trying VM latest?
because you should use the stable now :)
I explain: I updated the latest VM to libgit2 0.25.1. While this works on
most of my cases, I spotted this problem too.
cheers,
Esteban
On 7 May 2017, at 18:40, Myroslava Romaniuk <romaniuk@ucu.edu.ua> wrote:
I am also trying to clone a repository and for me the command causes the
following error: LGit_GIT_ERROR: error authenticating: failed connecting
agent. I am using the latest image (60482) on Win 7 (64 bit).
On 7 May 2017 at 19:06, Elhamer <abdelkhalekdev@gmail.com> wrote:
EstebanLM wrote
Yes, there is a bug now in iceberg (I will fix it soon), for now you
can
go with:
IceRepository defaultBackendType: #IceLibgitLocalRepository.
This actually causes an Assertion failure, then a total crash:
---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Assertion failed!
Program: ...
File: e:/workspace/PharoVM-spur32/Architecture.../remote.c
Line: 430
Expression: out && repo && name
For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts
(Press Retry to debug the application - JIT must be enabled)
---------------------------
Abort Retry Ignore
---------------------------
I am using the image #60480 on a Windows 10 64bits OS
--
View this message in context:
http://forum.world.st/Iceberg-tp4945776p4945804.html
Sent from the Pharo Smalltalk Developers mailing list archive at
Nabble.com.
--
�� ��������������,
������������������ ��������������.