[Pharo-dev] [Pharo 8.0] Build #39: Ensure subMenu is opened

There is a new Pharo build available! The status of the build #39 was: SUCCESS. The Pull Request #2375 was integrated: "Ensure subMenu is opened" Pull request url: https://github.com/pharo-project/pharo/pull/2375 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url:

[Pharo-dev] [Pharo 8.0] Build #42: 2405-NewValueHolder-should-use-hook-to-get-its-value

There is a new Pharo build available! The status of the build #42 was: SUCCESS. The Pull Request #2408 was integrated: "2405-NewValueHolder-should-use-hook-to-get-its-value" Pull request url: https://github.com/pharo-project/pharo/pull/2408 Issue Url: https://pharo.fogbugz.com/f/cases/2405

[Pharo-dev] [Pharo 8.0] Build #43: 2247-Add-possibility-to-open-file-references-in-the-native-browser

There is a new Pharo build available! The status of the build #43 was: SUCCESS. The Pull Request #2248 was integrated: "2247-Add-possibility-to-open-file-references-in-the-native-browser" Pull request url: https://github.com/pharo-project/pharo/pull/2248 Issue Url:

[Pharo-dev] [Pharo 7.0] Build #145: 18764-Remove-external-dependencies-from-Kernel-Tests-

There is a new Pharo build available! The status of the build #145 was: SUCCESS. The Pull Request #1748 was integrated: "18764-Remove-external-dependencies-from-Kernel-Tests-" Pull request url: https://github.com/pharo-project/pharo/pull/1748 Issue Url:

[Pharo-dev] [Pharo 7.0] Build #144: Object-centric MetaLink integration.

There is a new Pharo build available! The status of the build #144 was: FAILURE. The Pull Request #2120 was integrated: "Object-centric MetaLink integration." Pull request url: https://github.com/pharo-project/pharo/pull/2120 Issue Url: https://pharo.fogbugz.com/f/cases/22830 Build Url:

[Pharo-dev] [Pharo 8.0] Build #40: 2309-Add-assertEmpty

There is a new Pharo build available! The status of the build #40 was: FAILURE. The Pull Request #2400 was integrated: "2309-Add-assertEmpty" Pull request url: https://github.com/pharo-project/pharo/pull/2400 Issue Url: https://pharo.fogbugz.com/f/cases/2309 Build Url:

[Pharo-dev] [Pharo 8.0] Build #41: 2310-calypso-and-the-inspector-have-wrong-icons

There is a new Pharo build available! The status of the build #41 was: SUCCESS. The Pull Request #2327 was integrated: "2310-calypso-and-the-inspector-have-wrong-icons" Pull request url: https://github.com/pharo-project/pharo/pull/2327 Issue Url: https://pharo.fogbugz.com/f/cases/2310 Build

[Pharo-dev] Contribute to pharo8.0 ?

Hi, I am trying my first contribution / PR to pharo8.0 I started with a latest zeroconfig 8.0 image/vm and I deleted my old fork and made a new one. But repairing the repository by fetching does not bring it to the detached state I also don't understand how to make an issue branch for

Re: [Pharo-dev] Contribute to pharo8.0 ?

Le 29/01/2019 à 23:47, Sven Van Caekenberghe a écrit : > Hi, > > I am trying my first contribution / PR to pharo8.0 > > I started with a latest zeroconfig 8.0 image/vm and I deleted my old fork and > made a new one. > > But repairing the repository by fetching does not bring it to the detached

Re: [Pharo-dev] Contribute to pharo8.0 ?

Hi Sven > Hi, > > I am trying my first contribution / PR to pharo8.0 Excellent > I started with a latest zeroconfig 8.0 image/vm and I deleted my old fork and > made a new one. > > But repairing the repository by fetching does not bring it to the detached > state Often I do repair and I

Re: [Pharo-dev] Contribute to pharo8.0 ?

> > There is currently a bug eating one character of the commit hash. So > Iceberg does not find the hash and thinks we need a fetch. So currently > we need to checkout Pharo8.0 in order to be in a good state :( OOPs is there a bug entry? > >> I also don't understand how to make an issue branch

Re: [Pharo-dev] Still build errors :(

ahh Tx I did not know. > On 29 Jan 2019, at 11:05, Esteban Lorenzano wrote: > > > >> On 29 Jan 2019, at 11:01, ducasse > > wrote: >> >> >> >>> On 28 Jan 2019, at 23:17, Esteban Lorenzano >> > wrote:

Re: [Pharo-dev] Still build errors :(

> On 28 Jan 2019, at 23:17, Esteban Lorenzano wrote: > > This is building against the older version. Ah I start to understand. > Relaunching the tests is not enough here, you need to close and open again > the PR (Which I just did). How do we do it? Stef > > Esteban > >> On 28 Jan

Re: [Pharo-dev] Still build errors :(

> On 29 Jan 2019, at 11:01, ducasse wrote: > > > >> On 28 Jan 2019, at 23:17, Esteban Lorenzano > > wrote: >> >> This is building against the older version. > > Ah I start to understand. >> Relaunching the tests is not enough here, you need to close and open

[Pharo-dev] [Pharo 8.0] Build #38: 2172-Color-classfromHexString-should-remove-possible-

There is a new Pharo build available! The status of the build #38 was: FAILURE. The Pull Request #2330 was integrated: "2172-Color-classfromHexString-should-remove-possible-" Pull request url: https://github.com/pharo-project/pharo/pull/2330 Issue Url: https://pharo.fogbugz.com/f/cases/2172

Re: [Pharo-dev] [Pharo-users] Class name with diacritic character and Pharo

https://github.com/pharo-project/pharo/issues/2395 > On 27 Jan 2019, at 17:03, Sven Van Caekenberghe wrote: > > Hi Dominique, > >> On 27 Jan 2019, at 11:40, Dominique Dartois wrote: >> >> Hello all. >> If a use french diacritic character in a class name, the code runs but I >> can’t

[Pharo-dev] [Pharo 8.0] Build #37: 2244-NECPreferences-set-values-at-two-places

There is a new Pharo build available! The status of the build #37 was: SUCCESS. The Pull Request #2245 was integrated: "2244-NECPreferences-set-values-at-two-places" Pull request url: https://github.com/pharo-project/pharo/pull/2245 Issue Url: https://pharo.fogbugz.com/f/cases/2244 Build