The best way to resolve configuration errors is to run the validator:

  (MetacelloToolBox validateConfiguration: <configurationClass>) inspect.

The class comment of MetacelloMCVersionValidator has information about the various reason codes and between the two you should be able to figure out how to repair the configuration.

Let me know if you need additional help interpreting the validation report.

Dale

On 2/7/15 11:29 AM, Thierry Goubier wrote:
Hi Sebastian,

It seems that something is amiss in the configuration. You are using a baseline in the configuration? Are you using #common, #pharoX.x tags? I am also a bit lost with some of Metacello errors, and it is usually just a typo in one of the tags, or trying to use two baselines, etc...

Thierry

2015-02-06 14:40 GMT+01:00 Sebastian Tleye <[email protected] <mailto:[email protected]>>:

    Hi Thierry,

    I still have the same problem, I managed to install and configure
    GitFiletree, I can add a remote git repository, load packages from
    it, etc.
    Also, I created a new stable version with the versioner. If I open
    the repository with Monticello I can see the history of the the
    packages, not only the last one.
    However, It's still throwing the same error, it cannot resolve the
    name of the package that it needs.

    (By the way,  the development version can be still loaded correctly)

    Any Idea of what can it be?
    I am not an expert in Metacello, so maybe is a problem with the
    Configuration file (in the baseline I tried both, reference to the
    remote git repository and to the local gitfiletree repository)


    2015-02-05 13:38 GMT+01:00 Thierry Goubier
    <[email protected] <mailto:[email protected]>>:



        2015-02-05 13:26 GMT+01:00 Sebastian Tleye
        <[email protected] <mailto:[email protected]>>:

            Ok, great, I'll try GitFileTree, we are using the standard
            port.


        Please ask if you need any help. Criticism on the lack of
        documentation and missing features accepted :)

        Thierry


            Thanks!

            2015-02-05 12:53 GMT+01:00 Serge Stinckwich
            <[email protected]
            <mailto:[email protected]>>:

                Why  not launching a kickstarter thing to have someone
                (you !) paid to have a clean integration of git/pharo
                with documentation ? I guess people, companies and
                associations like ESUG can give money for that.


                Sent from my iPhone

                On 5 févr. 2015, at 12:38, Thierry Goubier
                <[email protected]
                <mailto:[email protected]>> wrote:



                2015-02-05 11:27 GMT+01:00 Sebastian Tleye
                <[email protected]
                <mailto:[email protected]>>:

                    Thanks Yuriy and Thierry,

                    I see what I can do, I was using Bitbucket until
                    some time ago but now we moved our project to a
                    private git server!


                If you are on a private server, then GitFileTree will
                work (except if the git server is on a non-standard
                port: I will add support for that in the near future).

                Look for baselines and branches support to make your
                life (and your configurations) simpler.

                As I said during PharoDays: we now have a good chunk
                of the necessary infrastructure and we (the Pharo
                community) can develop additional support if needed.
                Asking (funding) the consortium for that could be a
                real cool way of contributing :)

                Thierry


                    2015-02-05 11:13 GMT+01:00 Thierry Goubier
                    <[email protected]
                    <mailto:[email protected]>>:

                        Hi Sebastian,

                        filetree only gives you access to the latest
                        version of your packages, and you can't
                        access the history without access to the
                        underlying version control system you are using.

                        This access for Metacello is available in two
                        ways: via Metacello github:// and
                        bitbucket:// urls and tags or branches (but
                        you need to be using either github or
                        bitbucket), or via GitFileTree if you are
                        using git.

                        Thierry

                        2015-02-05 11:03 GMT+01:00 Sebastian Tleye
                        <[email protected]
                        <mailto:[email protected]>>:

                            Hi,

                            I am using a filetree repository for my
                            project, also I have created a first
                            stable version  using the versioner tool.
                            Everything was working fine until I
                            commited more changes, now when I want to
                            install the stable version is throwing an
                            error saying that cannot resolve the
                            package that it needs, however if I load
                            the development version it works perfectly.

                            To clarify a little,

                            The development version tries to load
                            Phadeo-ImporterExporters-SebastianTleye.12 and
                            it works perfectly. The stable version
                            tries to load
                            Phadeo-ImporterExporters-SebastianTleye.10 and
                            it throws an error saying that it cannot
                            be resolve.

                            Any Idea of what is happening?
                            I read that filetree and Metacello are
                            compatibles so I don't know what's the
                            problem


                        Hi sebastian


                            Thanks in advance

                            Sebastián Tleye





-- Sebastián Tleye





-- Sebastián Tleye





-- Sebastián Tleye



Reply via email to