On 2 Feb 2018, at 10:12, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:the pull request was against the issue branch, not the development one, so the merging of it had no real effect. I created a new one (https://github.com/pharo-project/pharo/pull/790)-- Pavel2018-02-02 9:47 GMT+01:00 Esteban Lorenzano <estebanlm@gmail.com>:yes, I asked Pavel to look at it���EstebanOn 2 Feb 2018, at 09:38, Guillermo Polito <guillermopolito@gmail.com> wrote:I've seen that the other day. The package is in the repository but is not loaded in the image. Probably somebody committed it but not added it into any baseline.On Fri, Feb 2, 2018 at 4:35 AM, Sean P. DeNigris <sean@clipperadams.com> wrote:An image with build 454 seems still not to have MCGitlabRepository present.
What am I missing?
Same for build 462 with sha 3641442f3ba0613cd9a6428181487ea29e62418c, which
has the package in its source:
https://github.com/pharo-project/pharo/tree/3641442f3ba0613c d9a6428181487ea29e62418c/src/ Metacello-Gitlab
Ditto for build 487.sha.58ee23aadcd15e0a969ed675e8141c0cfd95594a
-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
--
