Thank you, your build installs on Mint 18.3 and 19.3 for me.
I can't use it as it is missing ncurses, but it proves the point.
The dev build that fails for me is for Ubuntu 16.04 on which Linux Mint 18 is 
based.
I'd be interested to hear from the people who are downloading 16.04 - what is 
it working on?

P.O. Jonsson  <oor...@jonases.se> wrote the following on 30/01/20 21:43:23:
> Dear rm (?)
> 
> You are using an Ubuntu build maybe there is something there that does not 
> work?
> 
> I have built ooRexx 5.0.0 from source tonight for Linux Mint 19.1, 64 bit 
> version an installer specifically 
for Linux mint. Please try it out.
> 
> In my dropbox 
> <https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0> I 
> add various 
builds that are not official builds, feel free to have a look there, but I only 
add files here occasionally
> 
> Make sure to uninstall/remove the previous installation of ooRexx before 
> installing this version
> 
> 
> 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
> 
> 
> 
> > Am 30.01.2020 um 13:06 schrieb rvm--- via Oorexx-devel 
> > <oorexx-devel@lists.sourceforge.net>:
> > 
> > I am still unable to install the latest builds.
> > 
> > on ooRexx-5.0.0-11972.ubuntu1604.x86_64.deb I get :
> > Removing oorexx (5.0.0) ...
> > Removing oorexx alternatives
> > Processing triggers for man-db (2.7.5-1) ...
> > Processing triggers for desktop-file-utils (0.22+linuxmint1) ...
> > Processing triggers for mime-support (3.59ubuntu1) ...
> > Selecting previously unselected package oorexx.
> > (Reading database ... 485989 files and directories currently installed.)
> > Preparing to unpack .../ooRexx-5.0.0-11972.ubuntu1604.x86_64.deb ...
> > Unpacking oorexx (5.0.0) ...
> > Setting up oorexx (5.0.0) ...
> > update-alternatives: error: alternative path /usr/bin/rexx-oorexx doesn't 
> > exist
> > dpkg: error processing package oorexx (--install):
> > subprocess installed post-installation script returned error exit status 2
> > Processing triggers for man-db (2.7.5-1) ...
> > Errors were encountered while processing:
> > oorexx
> > 
> > on re-installing ooRexx-5.0.0-11937.ubuntu1604.x86_64.deb :
> > Removing oorexx alternatives
> > Unpacking oorexx (5.0.0) over (5.0.0) ...
> > dpkg: warning: unable to delete old directory '/usr/local/share/man/man1': 
> > Directory not empty
> > dpkg: warning: unable to delete old directory '/usr/local/share/man': 
> > Directory not empty
> > dpkg: warning: unable to delete old directory '/usr/local/share': Directory 
> > not empty
> > dpkg: warning: unable to delete old directory '/usr/local/lib': Directory 
> > not empty
> > dpkg: warning: unable to delete old directory '/usr/local/include': 
> > Directory not empty
> > Setting up oorexx (5.0.0) ...
> > update-alternatives: using /usr/bin/rexx-oorexx to provide /usr/bin/rexx 
> > (rexx) in auto mode
> > Processing triggers for desktop-file-utils (0.22+linuxmint1) ...
> > Processing triggers for mime-support (3.59ubuntu1) ...
> > Processing triggers for man-db (2.7.5-1) ...
> > 
> > I have been unable to install any builds since November.
> > I'm running Linux Mint 18.3 and 19.1 on desktops and Thinkpads, same error 
> > on all.
> > There's nothing in syslog.
> > 
> > 
> > _______________________________________________
> > Oorexx-devel mailing list
> > Oorexx-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
Dear rm (?)

You are using an Ubuntu build maybe there is something there that does not work?

I have built ooRexx 5.0.0 from source tonight for Linux Mint 19.1, 64 bit version an installer specifically for Linux mint. Please try it out.

In my dropbox I add various builds that are not official builds, feel free to have a look there, but I only add files here occasionally

Make sure to uninstall/remove the previous installation of ooRexx before installing this version


_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to