Re: [Pharo-dev] about spurious conflicts

2016-05-17 Thread Marcus Denker
The reason is that the merge does not find the “last common” package. There is an issue that solves this (adding temporarily the Pharo5 repo). Marcus > On 17 May 2016, at 22:08, stepharo wrote: > > Hi > > > while migrating some of the issues from 50 to 60, I noticed that many of the

Re: [Pharo-dev] fogbugz process Check seems to be stuck

2016-05-17 Thread Alistair Grant
Hi Sven, On Wed, May 18, 2016 at 07:33:10AM +0200, Sven Van Caekenberghe wrote: > Hi Alistair, > > Everything is OK. > > Once Issue Validation succeeds, your slice is ready to be integrated (a > review by another human would help too). Integration itself is a manual > process done by an integ

[Pharo-dev] File List -- MNU: RubTextEditor>>doIt

2016-05-17 Thread Martin McClure
So I open Pharo 5, and the *very* *first* thing I do is to open a file list, select a file that contains the Metacello expression to load my project, and select "Do it" from the menu. And get MNU: RubTextEditor>>doIt :-( This was on Linux, in case that makes a difference. I couldn't quickly

Re: [Pharo-dev] fogbugz process Check seems to be stuck

2016-05-17 Thread Sven Van Caekenberghe
Hi Alistair, Everything is OK. Once Issue Validation succeeds, your slice is ready to be integrated (a review by another human would help too). Integration itself is a manual process done by an integrator. The reason there was a second check is that every time a new build is done, all open i

[Pharo-dev] fogbugz process Check seems to be stuck

2016-05-17 Thread Alistair Grant
Hi All, Would someone mind clarifying the issue process for me. pharo.org states: In success, the state will be "Fix Reviewed by the Monkey". This is where humans come into the picture: your code needs to be reviewed, if possible by 2-3 people. If they accept it, the state moves to "Fix to Inclu

Re: [Pharo-dev] about spurious conflicts

2016-05-17 Thread Denis Kudriashov
Yes. It should be solved by 18251 2016-05-17 22:08 GMT+02:00 stepharo : > Hi > > > while migrating some of the issues from 50 to 60, I noticed that many of > the conflicts are > > not conflicts since the code of both me

Re: [Pharo-dev] about spurious conflicts

2016-05-17 Thread Max Leske
> On 17 May 2016, at 22:08, stepharo wrote: > > Hi > > > while migrating some of the issues from 50 to 60, I noticed that many of the > conflicts are > > not conflicts since the code of both methods and the protocols are the same. > > Does anybody experienced the same? > > Here are some ex

Re: [Pharo-dev] about spurious conflicts

2016-05-17 Thread Nicolai Hess
2016-05-17 22:08 GMT+02:00 stepharo : > Hi > > > while migrating some of the issues from 50 to 60, I noticed that many of > the conflicts are > > not conflicts since the code of both methods and the protocols are the > same. > > Does anybody experienced the same? > > Here are some examples and I'm

[Pharo-dev] [pharo-project/pharo-core] 96698c: 60010

2016-05-17 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 96698cbeb27393860effe85738f937fb4dd96338 https://github.com/pharo-project/pharo-core/commit/96698cbeb27393860effe85738f937fb4dd96338 Author: Jenkins Build Server Date: 2016-05-17 (Tue, 17 May 2016

[Pharo-dev] [pharo-project/pharo-core]

2016-05-17 Thread GitHub
Branch: refs/tags/60010 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] about spurious conflicts

2016-05-17 Thread stepharo
Hi while migrating some of the issues from 50 to 60, I noticed that many of the conflicts are not conflicts since the code of both methods and the protocols are the same. Does anybody experienced the same? Here are some examples and I'm puzzled. https://ci.inria.fr/pharo/job/Pharo-6.0-Is

Re: [Pharo-dev] UnifiedFFI Interrupted system call error on OSX

2016-05-17 Thread stepharo
Le 17/5/16 à 21:33, Jan van de Sandt a écrit : Hi, I'm helping with the port of LibGit [1] from Pharo 4 to Pharo 5 [2]. BIG THANKS This project provides Smalltalk bindings for the libgit2 library. Very useful for better Git support in Pharo. The port means using the new UnifiedFFI inst

Re: [Pharo-dev] more robust tests

2016-05-17 Thread stepharo
thanks. I would like to have the system in a state where we can release the next day :) Le 17/5/16 à 21:43, Andrei Chis a écrit : We'll have a look. Cheers, Andrei On Sun, May 15, 2016 at 3:06 PM, stepharo > wrote: Hi While integrating some changes in P6

Re: [Pharo-dev] more robust tests

2016-05-17 Thread Andrei Chis
We'll have a look. Cheers, Andrei On Sun, May 15, 2016 at 3:06 PM, stepharo wrote: > Hi > > While integrating some changes in P6.0 I got such tests failing. Only > failing on mac. > > Could you check? > > Stef > > > Regression > > GT.EventRecorder.Tests.Core.GTEventRecorderTest.testAddCollector

[Pharo-dev] UnifiedFFI Interrupted system call error on OSX

2016-05-17 Thread Jan van de Sandt
Hi, I'm helping with the port of LibGit [1] from Pharo 4 to Pharo 5 [2]. This project provides Smalltalk bindings for the libgit2 library. Very useful for better Git support in Pharo. The port means using the new UnifiedFFI instead of NativeBoost. The project is still in the alpha stage but a lot

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

2016-05-17 Thread Alistair Grant
On Tue, May 17, 2016 at 06:16:07PM +0200, Esteban Lorenzano wrote: > there was a problem with the repositorio (I forget to make it public). > now you should be able to commit (of course, you still need an smalltalkhub > user :P) > > Esteban Thanks! I've successfully uploaded the slice now. Th

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

2016-05-17 Thread Esteban Lorenzano
there was a problem with the repositorio (I forget to make it public). now you should be able to commit (of course, you still need an smalltalkhub user :P) Esteban > On 17 May 2016, at 17:54, Alistair Grant wrote: > > On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote: >>On 17 May

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

2016-05-17 Thread Alistair Grant
On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote: > On 17 May 2016, at 09:09, Sven Van Caekenberghe wrote: > On 17 May 2016, at 06:48, Max Leske wrote: > No, it’s publicly writeable. You may have found a bug. Can you link to > the .mcz you’re trying to upload?

[Pharo-dev] [pharo-project/pharo-core]

2016-05-17 Thread GitHub
Branch: refs/tags/60009 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 2c1c3f: 60009

2016-05-17 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 2c1c3fbfb52006c6c1d6aadc6518a42230638777 https://github.com/pharo-project/pharo-core/commit/2c1c3fbfb52006c6c1d6aadc6518a42230638777 Author: Jenkins Build Server Date: 2016-05-17 (Tue, 17 May 2016

Re: [Pharo-dev] PhD Thesis offer

2016-05-17 Thread jannik laval
nop, I don't know these lists. Jannik 2016-05-15 22:49 GMT+02:00 stepharo : > did you forward it to spanish speaking mailing lists? > > > Stef > > Le 4/5/16 à 12:37, jannik laval a écrit : > > Dear friends, > > I am looking for a french student (or someone speaking french) who wants > to engage

Re: [Pharo-dev] PharoVM-spur32 test newVMTestImage --> Pharo 2.0 ??

2016-05-17 Thread Esteban Lorenzano
newVMtestImage is old, yes. we are not using it for now because I’m running tests in github, before build it (but I’m missing windows tests, a situation I will fix soon (™)) Esteban > On 17 May 2016, at 12:44, Ben Coman wrote: > > In the PharoVM-spur32 CI build, newVMTestImage.sh [1] doesn't

[Pharo-dev] PharoVM-spur32 test newVMTestImage --> Pharo 2.0 ??

2016-05-17 Thread Ben Coman
In the PharoVM-spur32 CI build, newVMTestImage.sh [1] doesn't seem current? > wget http://files.pharo.org/vm/src/vm-test-image-20.zip 1>&2 > unzip vm-test-image-20.zip -d vm-test-image 1>&2 > > wget http://files.pharo.org/sources/PharoV20.sources > --output-document=vm-test-image/PharoV20.sources

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

2016-05-17 Thread Pavel Krivanek
I copied all current Pharo 6 packages to the Pharo60 and Pharo60Inbox repositories. It should solve at least part of the problems. -- Pavel 2016-05-17 11:08 GMT+02:00 Denis Kudriashov : > Copy slice from Monticello Browser also copies dependencies. > But now I always got merge conflicts from Mon

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

2016-05-17 Thread Denis Kudriashov
Copy slice from Monticello Browser also copies dependencies. But now I always got merge conflicts from Monkey while no conflicts when I merge it manually 2016-05-17 9:06 GMT+02:00 Sven Van Caekenberghe : > Yes, it is fragile. > > It's a bit like an application that saves a document as a couple of

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

2016-05-17 Thread Max Leske
> On 17 May 2016, at 09:09, Sven Van Caekenberghe wrote: > >> >> On 17 May 2016, at 06:48, Max Leske wrote: >> >>> >>> On 16 May 2016, at 22:49, Alistair Grant wrote: >>> >>> Hi, >>> >>> I'm attempting to upload a SLICE for issue 18248 to: >>> >>> MCHttpRepository >>> location: 'http

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

2016-05-17 Thread Sven Van Caekenberghe
> On 17 May 2016, at 06:48, Max Leske wrote: > >> >> On 16 May 2016, at 22:49, Alistair Grant wrote: >> >> Hi, >> >> I'm attempting to upload a SLICE for issue 18248 to: >> >> MCHttpRepository >> location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main' >> user: '' >> pa

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

2016-05-17 Thread Sven Van Caekenberghe
Yes, it is fragile. It's a bit like an application that saves a document as a couple of files. When you later copy only one file, you break the format. > On 17 May 2016, at 08:37, Peter Uhnák wrote: > > But how come saving a slice in the beginning also saves the dependents? I > thought it act

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

2016-05-17 Thread Max Leske
Done. I had no problems at all… Are you behind a proxy maybe? I seem to remember something about HTTPS behind proxies being a problem… Cheers, Max > On 17 May 2016, at 08:59, Alistair Grant wrote: > > On Tue, May 17, 2016 at 08:43:29AM +0200, Max Leske wrote: >> >>> On 17 May 2016, at 08:31,

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

2016-05-17 Thread Alistair Grant
On Tue, May 17, 2016 at 08:43:29AM +0200, Max Leske wrote: > > > On 17 May 2016, at 08:31, Alistair Grant wrote: > > > > On Tue, May 17, 2016 at 06:48:06AM +0200, Max Leske wrote: > >> > >>> On 16 May 2016, at 22:49, Alistair Grant wrote: > >>> > >>> Hi, > >>> > >>> I'm attempting to upload