Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Enrico Sorichetti via Oorexx-devel
Going back and forth between builds 12050 and 12054 Did not cause any problems on centos 8 Also using the —replacefiles clause lets You install over an existing installation without uninstalling the previous one After that the rpm -e must be qualified And uninstalling the older only

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson
Hi, It works just fine for me as well to replace and OLDER version with a NEWER version incrementally (this is what the Jenkins slaves do as well). Furthermore building from source and installing always work, irrespective of version. The problem only surfaces when you use and older rpm module

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Erich Steinböck
> > Try installing an older build (rpm module) after removing the newer build I don't think I can as the two RPM-based slaves CentOS and SLES390 I have access to don't have full sudo access. Enrico, can you maybe test what P.O. asks for? ___

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson
All my local builds are here Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 08.04.2020 um 16:34 schrieb Erich Steinböck : > > Try installing an older build (rpm module) after removing the newer build

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Erich Steinböck
Hi P.O., you may have copies of old builds hanging around, or build from an outdated SVN working copy. Our build machine builds fine on all slaves, including the CentOS slave, and uploads packages with the correct SVN build numbers. (see the console log of the sourceforge-upload job).

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson
@Enrico: did you use the rexx -v to confirm the version? For both versions? If so I have a rotten build :-( Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 08.04.2020 um 17:48 schrieb Enrico Sorichetti via Oorexx-devel > : > > Going back and forth between builds 12050 and

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread René Jansen
I have funny stuff going on also: my MacOSX build kept telling me that it was from June 2019 (which might be the last time I built on this particular mac). Checking up on it, I found that it now installs in ~/Applications/ooRexx5 instead of ~/Applications/ooRexx5.0.0 No big deal but a tad

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Rick McGuire
On Wed, Apr 8, 2020 at 5:47 PM P.O. Jonsson wrote: > Dear René, > > This was a change on my proposal, ooRexx5.0.0 is somewhat over specified > and will be incorrect as soon as ooRexx 5.0.1 arrives. ooRexx5 is > sufficient to separate it from ooRexx 4. > this should probably be at least 2

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread René Jansen
Ah ok - that is fine with me. René. > On 8 Apr 2020, at 23:46, P.O. Jonsson wrote: > > Dear René, > > This was a change on my proposal, ooRexx5.0.0 is somewhat over specified and > will be incorrect as soon as ooRexx 5.0.1 arrives. ooRexx5 is sufficient to > separate it from ooRexx 4. > >

[Oorexx-devel] New rexxpg draft, request for proofreading (Re: rexxpg test rendering (Re: DocBook 4.5 tagging

2020-04-08 Thread Rony G. Flatscher
At [1] you will find two versions of "rexxpg.pdf": * "rexxpg-before-changing-chapter-5.pdf" * and the latest draft "rexxpg.pdf" There has been a *lot* of work in correcting, completing, updating, enhancing this chapter which among other things contained outright wrong information like:

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson
Dear René, This was a change on my proposal, ooRexx5.0.0 is somewhat over specified and will be incorrect as soon as ooRexx 5.0.1 arrives. ooRexx5 is sufficient to separate it from ooRexx 4. If you try one of the dmg installers I have built here