Ubuntu 20.04 LTS Packages Published

[Arsen Chaloyan]

Please be informed that binary packages for Ubuntu 20.04 LTS have been published and can be retrieved via the following APT repository.

deb [arch=amd64] https://username:pass...@unimrcp.org/repo/apt/ focal main

The binaries are available for the open source and commercial UniMRCP components listed below.

• UniMRCP Client and Server
• UniMRCP Dependencies
• Google SR/SS and Dialogflow
• AWS Transcribe/Polly and Lex
• Azure SR/SS and Bot Service
• Watson SR/SS
• Yandex SR/SS
• Kaldi SR
• GoVivace SR

Check out installation instructions available in the corresponding manuals.

Thank you for using UniMRCP.

--

Arsen Chaloyan
Author of UniMRCP
http://www.unimrcp.org

[Lewis Bergman]

I am probably doing something wrong but just in case it isn't me I thought I would post here. I am getting a 404 error trying to update.

I first upgraded the server (which is an LXC container) with:

do-release-upgrade -m server --allow-third-party

That upgraded without a hitch although it didn't upgrade unimrcp for the same reason and disabled third party on upgrade. I then run the following and have double checked my permissions used for logging in and they are correct. In fact, just to make sure I changed them and received the expected 403 error instead of the 404 not found:

403  Forbidden

root@uniMRCP:~# apt-get update 

Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease

Hit:2 https://unimrcp.org/repo/apt focal InRelease

Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease

Hit:4 http://archive.ubuntu.com/ubuntu focal-security InRelease

Reading package lists... Done

root@uniMRCP:~# apt-get upgrade

Reading package lists... Done

Building dependency tree       

Reading state information... Done

Calculating upgrade... Done

The following packages will be upgraded:

  umc-addons uniapr uniapr-util unigoogleapis unigrpc unigrpc-deps unilicnodegen

  unimrcp-client unimrcp-common unimrcp-demo-plugins unimrcp-gsr unimrcp-gss

  unimrcp-server unisofia-sip

14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Need to get 2983 kB/8048 kB of archives.

After this operation, 3618 kB of additional disk space will be used.

Do you want to continue? [Y/n] y

Err:1 https://unimrcp.org/repo/apt focal/main amd64 unigoogleapis amd64 1:1.4.0-focal

  404  Not Found [IP: 35.208.27.40 443]

E: Failed to fetch https://unimrcp.org/repo/apt/pool/main/u/unigoogleapis/unigoogleapis_1.4.0-focal_amd64.deb  404  Not Found [IP: 35.208.27.40 443]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

root@uniMRCP:~# 

Any ideas?

[mayama takeshi]

Hi, couldn't UniMRCP use semantic versioning for its releases?
I updated my Ubuntu 16.04 installation yesterday using apt-get and the version changed from '1.7.0' to '1.7.0'!

(but the new version is indeed not the same as there was change in behavior).

Or at least add the git commit id to the version string like 1.7.0@373d886

This would simplify reporting bugs and avoid confusion.

[Arsen Chaloyan]

Hi Lewis,

Thanks for your note. The problem with permissions on the package unigoogleapis_1.4.0-focal_amd64.deb must have been resolved.

--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/a3e3027d-a76a-4f40-89f6-603acf9d7ccan%40googlegroups.com.

[Arsen Chaloyan]

Hi Mayama,

I think there is a misunderstanding here. Please note that there has been no change in UniMRCP server, and 1.7.0 version remains current. All the binary packages for different distributions have been built from the same source tarball and provide the same functionality. The change in the behavior may come from the plugins that you use. The version numbers are provisioned separately for plugins. I guess a newer version of one or the other plugin has been installed when you have upgraded the packages.

Detailed change logs are published on every new release: http://unimrcp.org/announcements

 

--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/80b2e5a9-6256-473a-a664-560ad17a4d38n%40googlegroups.com.

[mayama takeshi]

Hi Arsen,

well, my assumption is about this:

I was seeing a scenario where unimrcp server was not sending START-OF-INPUT on DTMF detection. I even opened a ticket about it:

  https://github.com/unispeech/unimrcp/issues/288

but closed it after further investigation and realizing change of behavior after update of my unimrcp server to latest 1.7.0.

But the point is that I was already at 1.7.0.

Here is evidence I saved from my Ubuntu 16.04 shell output:

# this is when I was having problems:

root@IPX136 administrator 13:21:22]# ps -e|grep uni
32747 ?        17:41:13 unimrcpserver

# I checked the version and I was using unimrcp 1.7.0

root@IPX136 administrator 13:22:24]# /opt/unimrcp/bin/unimrcpserver --version
1.7.0

# then I tried to updated unimrcp-server and apt informed there was a new version

root@IPX136 administrator 13:22:26]# apt-get install unimrcp-server
... ABRIDGED ...
The following additional packages will be installed:
  unimrcp-client unimrcp-common unimrcp-demo-plugins

The following packages will be upgraded:

  unimrcp-client unimrcp-common unimrcp-demo-plugins unimrcp-server
4 upgraded, 0 newly installed, 0 to remove and 319 not upgraded.
Need to get 512 kB of archives.
After this operation, 23.6 kB of additional disk space will be used.

Do you want to continue? [Y/n] y

... ABRIGED ...
Installing new version of config file /opt/unimrcp/conf/unimrcpserver.xsd ...
Setting up unimrcp-demo-plugins (1:1.7.0-xenial) ...
Setting up unimrcp-client (1:1.7.0-xenial) ...
Installing new version of config file /opt/unimrcp/conf/unimrcpclient.xml ...
Installing new version of config file /opt/unimrcp/conf/client-profiles/lumenvox.xml ...
Installing new version of config file /opt/unimrcp/conf/client-profiles/nuance.xml ...
Installing new version of config file /opt/unimrcp/conf/client-profiles/unimrcp.xml ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
root@IPX136 administrator 13:23:15]#

# then I restarted unimrcp server

root@IPX136 administrator 13:25:35]# systemctl restart unimrcp.service

# then I confirmed unimrcp server restarted (PID changed):

root@IPX136 administrator 13:26:30]# ps -e|grep uni
23978 ?        00:00:00 unimrcpserver

# then I checked the version and it is 1.7.0

root@IPX136 administrator 13:26:32]# /opt/unimrcp/bin/unimrcpserver --version
1.7.0

But after the above, the problem I was seeing went away.

That is why I am assuming there are changes in code that are not always reflected in the version id.

[mayamatakeshi]

Ah. Sorry, my mistake.

I checked the logs for the versions and indeed I was using the old version of unimrcp:

/opt/unimrcp/log/unimrcpserver_2020.07.04_18.30.20.631272.log:2020-07-04 18:30:20:631503 [NOTICE] UniMRCP Server [1.6.0]
/opt/unimrcp/log/unimrcpserver_2021.03.18_13.25.27.803390.log:2021-03-18 13:25:27:803729 [NOTICE] UniMRCP Server [1.7.0]

 

Sorry to take your time.

On Sunday, March 21, 2021 at 10:35:00 AM UTC+9 Arsen Chaloyan wrote:

Hi Mayama,

I think there is a misunderstanding here. Please note that there has been no change in UniMRCP server, and 1.7.0 version remains current. All the binary packages for different distributions have been built from the same source tarball and provide the same functionality. The change in the behavior may come from the plugins that you use. The version numbers are provisioned separately for plugins. I guess a newer version of one or the other plugin has been installed when you have upgraded the packages.

Detailed change logs are published on every new release: http://unimrcp.org/announcements

 

On Thu, Mar 18, 2021 at 3:45 PM mayama takeshi <mayama...@gmail.com> wrote:

Hi, couldn't UniMRCP use semantic versioning for its releases?
I updated my Ubuntu 16.04 installation yesterday using apt-get and the version changed from '1.7.0' to '1.7.0'!

(but the new version is indeed not the same as there was change in behavior).

Or at least add the git commit id to the version string like 1.7.0@373d886

This would simplify reporting bugs and avoid confusion.

--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/80b2e5a9-6256-473a-a664-560ad17a4d38n%40googlegroups.com.

--

Arsen Chaloyan
Author of UniMRCP
http://www.unimrcp.org

--

You received this message because you are subscribed to a topic in the Google Groups "UniMRCP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/unimrcp/HxKty27NW44/unsubscribe.
To unsubscribe from this group and all its topics, send an email to unimrcp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/9113a020-974e-416f-92fc-0e1699ad417an%40googlegroups.com.

[Lewis Bergman]

I was able to upgrade the next day without changing anything so I guess so. Not sure what it was. Works good so far. 

To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/CAC5Usc%2BAOx4VN_YqK%3Dvj12Xb3gmi4ymcF8GFAvMn_eceA_8bRQ%40mail.gmail.com.