Did that:

Metacello new repository: 'github://svenvc/zinc:v3.0.1/repository'; 
              baseline: 'ZincHTTPComponents'; 
              ignoreImage; 
              onConflict: [ :ex | ex useIncoming ]; 
              onWarning: [ :ex | Transcript crShow: ex ]; 
              silently; 
              load; 
              lock.

Metacello new baseline: 'Employees'; 
              repository: 'tonel:///opt/pharo/employeesSource/pharo/'; 
              ignoreImage; 
              onConflict: [ :ex | ex useIncoming ];  
              onWarning: [ :ex | Transcript crShow: ex ];
              silently;
              load: #(core).

It seems it did the trick, but then I got another error:

Fetched -> Zinc-HTTP-SvenVanCaekenberghe.1542912596 --- https://github.com/svenvc/zinc.git[0327c84] --- /opt/pharo/pharo-local/iceberg/svenvc/zinc/repository (Libgit)
...RETRY->Zinc-Seaside
...RETRY->Zinc-Seaside
...FAILED->Zinc-Seaside[31mCould not resolve: Zinc-Seaside [Zinc-Seaside] in /opt/pharo/pharo-local/package-cache /opt/pharo/pharo-local/iceberg/SeasideSt/Seaside/repository (Libgit)
[0mMetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer:
[ | references nearestReference cachedReference externalReference mcVersion loadedVersionInfos |
cachedReference := nil.



On Fri, Dec 14, 2018 at 11:07 AM Vitor Medina Cruz <vitormcruz@gmail.com> wrote:
You can use the lock API in Metacello to use the dependency you want, ignoring the ones defined in the baselines.

You mean loading Zinc with lock before I load my project?

On Wed, Dec 12, 2018 at 5:21 PM Gabriel Cotelli <g.cotelli@gmail.com> wrote:
You can use the lock API in Metacello to use the dependency you want, ignoring the ones defined in the baselines.

On Wed, Dec 12, 2018 at 4:16 PM Vitor Medina Cruz <vitormcruz@gmail.com> wrote:
I can't depend on https://github.com/svenvc/zinc because this is a transitive dependency, my baseline depends of seaside that depends of Zinc. Is there a way to exclude Zinc dependency from Seaside so that I can force a Zinc dependency definition of my baseline?

On Wed, Dec 12, 2018 at 5:08 PM Sven Van Caekenberghe <sven@stfx.eu> wrote:


> On 12 Dec 2018, at 18:56, Vitor Medina Cruz <vitormcruz@gmail.com> wrote:
>
> Note it is trying to reach http://mc.stfx.eu/ZincHTTPComponents, which don't seems to be hosting Zinc anymore. Since these are transitive dependencies, I tried to define Zinc in the root of my baseline, as I did with seaside (magritte baseline had some problem with it), but the same error

Yes, that machine is partially down, the mc part will come up later, sorry. See my earlier message.

The best is to depend on https://github.com/svenvc/zinc using the baseline.