CiteZen and Pharo 5 / Pharo4 tests

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

CiteZen and Pharo 5 / Pharo4 tests

Peter Uhnak
Hi,

I wanted to use CiteZen, but there's no Pharo 5 version (wouldn't even load),

so I tried Pharo 4 instead but the tests are not passing:
all CZBibTest fail on MessageNotUnderstood: Metaclass>>allMethodsInCategory:

is this known problem? Do I need to use a very specific build of Pharo 4?

Thanks,
Peter
Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

stepharo
I wil update it and make it load in Pharo 50


Le 16/10/15 13:17, Peter Uhnák a écrit :

> Hi,
>
> I wanted to use CiteZen, but there's no Pharo 5 version (wouldn't even
> load),
>
> so I tried Pharo 4 instead but the tests are not passing:
> all CZBibTest fail on MessageNotUnderstood:
> Metaclass>>allMethodsInCategory:
>
> is this known problem? Do I need to use a very specific build of Pharo 4?
>
> Thanks,
> Peter


Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

Stephan Eggermont-3
In reply to this post by Peter Uhnak
On 16-10-15 13:17, Peter Uhnák wrote:
> Hi,
>
> I wanted to use CiteZen, but there's no Pharo 5 version (wouldn't even
> load),
>
> so I tried Pharo 4 instead but the tests are not passing:
> all CZBibTest fail on MessageNotUnderstood: Metaclass>>allMethodsInCategory:
>
> is this known problem? Do I need to use a very specific build of Pharo 4?

Uhm, there is a green build on
https://ci.inria.fr/pharo-contribution/job/Citezen/

Stephan


Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

Peter Uhnak


On Fri, Oct 16, 2015 at 6:50 PM, Stephan Eggermont <[hidden email]> wrote:
On 16-10-15 13:17, Peter Uhnák wrote:
Hi,

I wanted to use CiteZen, but there's no Pharo 5 version (wouldn't even
load),

so I tried Pharo 4 instead but the tests are not passing:
all CZBibTest fail on MessageNotUnderstood: Metaclass>>allMethodsInCategory:

is this known problem? Do I need to use a very specific build of Pharo 4?

Uhm, there is a green build on
https://ci.inria.fr/pharo-contribution/job/Citezen/

Well that's nice, but if you install it via Catalog Browser, which should be the correct way to install packages it is not working. (Maybe because green is development and not stable).
Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

Stephan Eggermont-3
On 17-10-15 12:02, Peter Uhnák wrote:
> On Fri, Oct 16, 2015 at 6:50 PM, Stephan Eggermont <[hidden email]> wrote:
>> Uhm, there is a green build on
>> https://ci.inria.fr/pharo-contribution/job/Citezen/
>
> Well that's nice, but if you install it via Catalog Browser, which should
> be the correct way to install packages it is not working. (Maybe because
> green is development and not stable).
>

Just promote #development to #stable and copy a configuration to the
metarepo. It is a safe-to-fail experiment. Just do it. (and perhaps
als add a #pharo5 spec & build)

Stephan



Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

stepharo
Yes.
I'm sorry but I'm sick, failing also the reinstall my machine and was
trying to organise birthday party of my last son ;)

Stef


Le 17/10/15 13:21, Stephan Eggermont a écrit :

> On 17-10-15 12:02, Peter Uhnák wrote:
>> On Fri, Oct 16, 2015 at 6:50 PM, Stephan Eggermont <[hidden email]>
>> wrote:
>>> Uhm, there is a green build on
>>> https://ci.inria.fr/pharo-contribution/job/Citezen/
>>
>> Well that's nice, but if you install it via Catalog Browser, which
>> should
>> be the correct way to install packages it is not working. (Maybe because
>> green is development and not stable).
>>
>
> Just promote #development to #stable and copy a configuration to the
> metarepo. It is a safe-to-fail experiment. Just do it. (and perhaps
> als add a #pharo5 spec & build)
>
> Stephan
>
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

Stephan Eggermont-3
On 18-10-15 11:16, stepharo wrote:
> Yes.
> I'm sorry but I'm sick, failing also the reinstall my machine and was
> trying to organise birthday party of my last son ;)

No problem. I've committed a version to the MetaRepoForPharo50 as I
couldn't write in the repo. In Pharo 5 it doesn't load.
I changed the build to use the MetaRepo version and build both 4 and 5
versions.

Stephan




Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

Stephan Eggermont-3
On 18-10-15 12:31, Stephan Eggermont wrote:
> I've committed a version to the MetaRepoForPharo50 as I
> couldn't write in the repo. In Pharo 5 it doesn't load.
> I changed the build to use the MetaRepo version and build both 4 and 5
> versions.

In Citezen-Reborn-StephaneDucasse.36 there is the method
CZSingleAuthorDocBuilder class>>#latex
that doesn't compile in Pharo 5

'latex
        "self latex"
       
        | builder |
        builder := self new
                fileNamed: ''rmod.bib'';
                toLatex;
                french;
                fieldOrder: #(#author
                          #title
                          #journal
                          #booktitle
                          #volume
                          #pages
                          #publisher
                          #year
                          # school
                          #impactfactor
                          #misc); "removed doi and url since they may contain _ and the
generator does not handle that well for the moment."
                setFilteringOn;
                yourself.
        builder generateLatexFile.
        '

because of the space between # and school.

Getting from the Syntax Error: Expecting a literal type to the
compilation context is 19 levels deep on the stack. I think it would be
useful to present more information than just the error message and the
source when loading & compiling a package.

BibPhraseLibrary twice uses #allMethodsInCategory: that should be
replaced by allSelectorsInProtocol: (deprecated in Pharo 3) in
Citezen-Rendering.

In baseline1.7 the dependencies on Seaside/Grease/Pier/Magritte versions
probably need updates. Magritte2 and Pier2 have never been tried on
Pharo5 AFAIK. Smacc has moved to github.

Stephan


Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

stepharo
Oops I will fix that.



Le 18/10/15 17:33, Stephan Eggermont a écrit :

> On 18-10-15 12:31, Stephan Eggermont wrote:
>> I've committed a version to the MetaRepoForPharo50 as I
>> couldn't write in the repo. In Pharo 5 it doesn't load.
>> I changed the build to use the MetaRepo version and build both 4 and 5
>> versions.
>
> In Citezen-Reborn-StephaneDucasse.36 there is the method
> CZSingleAuthorDocBuilder class>>#latex
> that doesn't compile in Pharo 5
>
> 'latex
>     "self latex"
>
>     | builder |
>     builder := self new
>         fileNamed: ''rmod.bib'';
>         toLatex;
>         french;
>         fieldOrder: #(#author
>               #title
>               #journal
>               #booktitle
>               #volume
>               #pages
>               #publisher
>               #year
>               # school
>               #impactfactor
>               #misc); "removed doi and url since they may contain _
> and the generator does not handle that well for the moment."
>         setFilteringOn;
>         yourself.
>     builder generateLatexFile.
>     '
>
> because of the space between # and school.
>
> Getting from the Syntax Error: Expecting a literal type to the
> compilation context is 19 levels deep on the stack. I think it would
> be useful to present more information than just the error message and
> the source when loading & compiling a package.
>
> BibPhraseLibrary twice uses #allMethodsInCategory: that should be
> replaced by allSelectorsInProtocol: (deprecated in Pharo 3) in
> Citezen-Rendering.
>
> In baseline1.7 the dependencies on Seaside/Grease/Pier/Magritte
> versions probably need updates. Magritte2 and Pier2 have never been
> tried on Pharo5 AFAIK. Smacc has moved to github.
>
> Stephan
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: CiteZen and Pharo 5 / Pharo4 tests

stepharo
In reply to this post by Stephan Eggermont-3
Fixed and I pushed two new configurations of in MetaRepo 40 and 50

Le 18/10/15 17:33, Stephan Eggermont a écrit :

> On 18-10-15 12:31, Stephan Eggermont wrote:
>> I've committed a version to the MetaRepoForPharo50 as I
>> couldn't write in the repo. In Pharo 5 it doesn't load.
>> I changed the build to use the MetaRepo version and build both 4 and 5
>> versions.
>
> In Citezen-Reborn-StephaneDucasse.36 there is the method
> CZSingleAuthorDocBuilder class>>#latex
> that doesn't compile in Pharo 5
>
> 'latex
>     "self latex"
>
>     | builder |
>     builder := self new
>         fileNamed: ''rmod.bib'';
>         toLatex;
>         french;
>         fieldOrder: #(#author
>               #title
>               #journal
>               #booktitle
>               #volume
>               #pages
>               #publisher
>               #year
>               # school
>               #impactfactor
>               #misc); "removed doi and url since they may contain _
> and the generator does not handle that well for the moment."
>         setFilteringOn;
>         yourself.
>     builder generateLatexFile.
>     '
>
> because of the space between # and school.
>
> Getting from the Syntax Error: Expecting a literal type to the
> compilation context is 19 levels deep on the stack. I think it would
> be useful to present more information than just the error message and
> the source when loading & compiling a package.
>
> BibPhraseLibrary twice uses #allMethodsInCategory: that should be
> replaced by allSelectorsInProtocol: (deprecated in Pharo 3) in
> Citezen-Rendering.
>
> In baseline1.7 the dependencies on Seaside/Grease/Pier/Magritte
> versions probably need updates. Magritte2 and Pier2 have never been
> tried on Pharo5 AFAIK. Smacc has moved to github.
>
> Stephan
>
>
>