Pharo 1.2 broken on Hudson due to XMLSupport changes

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

Pharo 1.2 broken on Hudson due to XMLSupport changes

Torsten Bergmann
Whatever has changed from
ConfigurationOfXMLSupport-DaleHenrichs.46 up to
...
ConfigurationOfXMLSupport-OttoBehrens.56

It broke the Pharo 1.2 build on Hudson since 2 days:

Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/p


See
https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/151/console

- ConfigurationOfPharo uses project: 'XMLSupport' with: '1.1.6'.
- but 1.1.6 has package: 'XML-Tests-Parser' with: 'XML-Tests-Parser-JAAyer.6'
- when I look at Otto's changes in ConfigurationOfXMLSupport
  then 1.1.7 was marked as broken only for Gemstone and a new 1.1.8/1.1.9
  was introduced - so no changes for 1.1.6 version

Any comments?

Thx
T.
--
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Reply | Threaded
Open this post in threaded view
|

Re: Pharo 1.2 broken on Hudson due to XMLSupport changes

otto
> It broke the Pharo 1.2 build on Hudson since 2 days:

Sorry about that

> Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/p

This tells me that it can't find the file in the repository, specified
to be on gemsource, excerpt below. I am confident that I published the
XMLParser package on gemsource, but since I don't see it there, I have
doubts. I can try to get it published. Best would be if I can get
access to the XMLSupport project on squeaksource.

package: 'XML-Parser'
                                        with: [
                                                        spec

repository: 'http://seaside.gemstone.com/ss/XMLSupport';

> See
> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/151/console

Sorry, the stupid bluecoat server on this corporate network of my
client blocks this site because of the certificate, so I can't see the
console output.

> - ConfigurationOfPharo uses project: 'XMLSupport' with: '1.1.6'.
> - but 1.1.6 has package: 'XML-Tests-Parser' with: 'XML-Tests-Parser-JAAyer.6'

I can't see how this influences the error message

> - when I look at Otto's changes in ConfigurationOfXMLSupport
>  then 1.1.7 was marked as broken only for Gemstone and a new 1.1.8/1.1.9
>  was introduced - so no changes for 1.1.6 version

Yes! The later versions should not influence the 1.1.6 version.

Reply | Threaded
Open this post in threaded view
|

Re: Pharo 1.2 broken on Hudson due to XMLSupport changes

otto
I attach the XML-Parser monticello file; perhaps someone can get it in
the right place so that it does not break the build, please? I don't
know what else to do.

On Thu, Feb 24, 2011 at 6:16 PM, Otto Behrens <[hidden email]> wrote:

>> It broke the Pharo 1.2 build on Hudson since 2 days:
>
> Sorry about that
>
>> Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/p
>
> This tells me that it can't find the file in the repository, specified
> to be on gemsource, excerpt below. I am confident that I published the
> XMLParser package on gemsource, but since I don't see it there, I have
> doubts. I can try to get it published. Best would be if I can get
> access to the XMLSupport project on squeaksource.
>
> package: 'XML-Parser'
>                                        with: [
>                                                        spec
>
> repository: 'http://seaside.gemstone.com/ss/XMLSupport';
>
>> See
>> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/151/console
>
> Sorry, the stupid bluecoat server on this corporate network of my
> client blocks this site because of the certificate, so I can't see the
> console output.
>
>> - ConfigurationOfPharo uses project: 'XMLSupport' with: '1.1.6'.
>> - but 1.1.6 has package: 'XML-Tests-Parser' with: 'XML-Tests-Parser-JAAyer.6'
>
> I can't see how this influences the error message
>
>> - when I look at Otto's changes in ConfigurationOfXMLSupport
>>  then 1.1.7 was marked as broken only for Gemstone and a new 1.1.8/1.1.9
>>  was introduced - so no changes for 1.1.6 version
>
> Yes! The later versions should not influence the 1.1.6 version.
>

XML-Parser-OttoBehrens.125.mcz (119K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Pharo 1.2 broken on Hudson due to XMLSupport changes

otto
And the tests file...

On Thu, Feb 24, 2011 at 9:30 PM, Otto Behrens <[hidden email]> wrote:

> I attach the XML-Parser monticello file; perhaps someone can get it in
> the right place so that it does not break the build, please? I don't
> know what else to do.
>
> On Thu, Feb 24, 2011 at 6:16 PM, Otto Behrens <[hidden email]> wrote:
>>> It broke the Pharo 1.2 build on Hudson since 2 days:
>>
>> Sorry about that
>>
>>> Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/p
>>
>> This tells me that it can't find the file in the repository, specified
>> to be on gemsource, excerpt below. I am confident that I published the
>> XMLParser package on gemsource, but since I don't see it there, I have
>> doubts. I can try to get it published. Best would be if I can get
>> access to the XMLSupport project on squeaksource.
>>
>> package: 'XML-Parser'
>>                                        with: [
>>                                                        spec
>>
>> repository: 'http://seaside.gemstone.com/ss/XMLSupport';
>>
>>> See
>>> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/151/console
>>
>> Sorry, the stupid bluecoat server on this corporate network of my
>> client blocks this site because of the certificate, so I can't see the
>> console output.
>>
>>> - ConfigurationOfPharo uses project: 'XMLSupport' with: '1.1.6'.
>>> - but 1.1.6 has package: 'XML-Tests-Parser' with: 'XML-Tests-Parser-JAAyer.6'
>>
>> I can't see how this influences the error message
>>
>>> - when I look at Otto's changes in ConfigurationOfXMLSupport
>>>  then 1.1.7 was marked as broken only for Gemstone and a new 1.1.8/1.1.9
>>>  was introduced - so no changes for 1.1.6 version
>>
>> Yes! The later versions should not influence the 1.1.6 version.
>>
>

XML-Tests-Parser-OttoBehrens.7.mcz (38K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Pharo 1.2 broken on Hudson due to XMLSupport changes

Johan Brichau-2
In reply to this post by otto
Otto,

The changes you made to the configuration mean that the XMLParser packages are fetched from the gemsource repository for *all* platforms, and not only for GemStone.
I don't think this should be the intention. The official code for the XMLParser for Pharo and Squeak are located in a squeaksource repository.


On 24 Feb 2011, at 17:16, Otto Behrens wrote:

>> It broke the Pharo 1.2 build on Hudson since 2 days:
>
> Sorry about that
>
>> Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/p
>
> This tells me that it can't find the file in the repository, specified
> to be on gemsource, excerpt below. I am confident that I published the
> XMLParser package on gemsource, but since I don't see it there, I have
> doubts. I can try to get it published. Best would be if I can get
> access to the XMLSupport project on squeaksource.
>
> package: 'XML-Parser'
>                                        with: [
>                                                        spec
>
> repository: 'http://seaside.gemstone.com/ss/XMLSupport';


Reply | Threaded
Open this post in threaded view
|

Re: Pharo 1.2 broken on Hudson due to XMLSupport changes

otto
Johan,

> The changes you made to the configuration mean that the XMLParser packages are fetched from the gemsource repository for *all* platforms, and not only for GemStone.
> I don't think this should be the intention. The official code for the XMLParser for Pharo and Squeak are located in a squeaksource repository.

My idea actually was to get an XML-Parser package that works on all
platforms, which is the case now. I know that the removal of the
Observer trait is not nice, but I think it is easier to mainain 1
package that works on Pharo / Squeak as well as GemStone. And when
GemStone supports traits, I'd gladly put it back.

Cheers
Otto