I can not install version 2.4.2. [SOLVED]

It is strange that you write about version 2.3.3 as inaccessible to Ubuntu 16.04. Although it was easily and without problems installed with updates when it came out.

And why do you think the updates for 16.04 have stopped? I got regular updates yesterday. And periodically the kernel of the operating system is updated.

See: Ubuntu release cycle | Ubuntu

All recent updates.

Start-Date: 2020-07-02 13:52:55
Commandline: apt-get remove --autoremove audacity audacity-data
Requested-By: djw (1000)
Remove: linux-modules-4.15.0-99-lowlatency:amd64 (4.15.0-99.100~16.04.1), linux-image-4.15.0-99-lowlatency:amd64 (4.15.0-99.100~16.04.1), linux-headers-4.15.0-99:amd64 (4.15.0-99.100~16.04.1), linux-modules-4.15.0-101-lowlatency:amd64 (4.15.0-101.102~16.04.1), audacity-data:amd64 (1:2.3.3-dmo1), linux-headers-4.15.0-101-lowlatency:amd64 (4.15.0-101.102~16.04.1), linux-headers-4.15.0-99-lowlatency:amd64 (4.15.0-99.100~16.04.1), linux-headers-4.15.0-101:amd64 (4.15.0-101.102~16.04.1), linux-image-4.15.0-101-lowlatency:amd64 (4.15.0-101.102~16.04.1)
End-Date: 2020-07-02 13:54:19

Start-Date: 2020-07-02 13:59:57
Commandline: apt install audacity
Requested-By: djw (1000)
Install: audacity:amd64 (2.1.2-1), audacity-data:amd64 (2.1.2-1, automatic)
End-Date: 2020-07-02 14:00:48

Start-Date: 2020-07-03 11:58:24
Commandline: aptdaemon role=‘role-commit-packages’ sender=‘:1.74’
Upgrade: libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.27, 2:4.3.11+dfsg-0ubuntu0.16.04.28), samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.27, 2:4.3.11+dfsg-0ubuntu0.16.04.28), firefox-locale-en:amd64 (77.0.1+build1-0ubuntu0.16.04.1, 78.0.1+build1-0ubuntu0.16.04.1), firefox-locale-ru:amd64 (77.0.1+build1-0ubuntu0.16.04.1, 78.0.1+build1-0ubuntu0.16.04.1), libsmbclient:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.27, 2:4.3.11+dfsg-0ubuntu0.16.04.28), firefox:amd64 (77.0.1+build1-0ubuntu0.16.04.1, 78.0.1+build1-0ubuntu0.16.04.1), libjson-c2:amd64 (0.11-4ubuntu2.5, 0.11-4ubuntu2.6)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2020-07-03 11:58:49

Start-Date: 2020-07-03 12:01:21
Commandline: aptdaemon role=‘role-commit-packages’ sender=‘:1.99’
Upgrade: libgnutls-openssl27:amd64 (3.4.10-4ubuntu1.7, 3.4.10-4ubuntu1.8), libgnutls30:amd64 (3.4.10-4ubuntu1.7, 3.4.10-4ubuntu1.8)
End-Date: 2020-07-03 12:01:24

There is no contradiction at all. Ubuntu 16.04 is supported til 2021 April but Ubuntu studio 16.04 has reached eol (like other unofficial flavours) What that means is that components common to official Ubuntu will still be updated and supported (since repos for 16.04 are still maintained) but components specific to the flalvours won’t (e.g kde stuffs won’t be maintained for kubuntu 16.04 but it will still get updates for kernels, firefox etc)

As for why you had 2.3.3 before from official repo that sounds kind of strange as 2.3.3 is not published in the official repos from everything I can find online (and there is no trace that it has ever been) Maybe you did add a ppa but later removed and forgot about it, that is the only possible explanation I can come up with. If you have an alternative theory I would like to hear it.

I didn’t change anything. All versions were subsequently updated, and updated to 2.3.3. And in May Audacity updated to 2.4.1. For example, I have Linux Mint - Sarah. And there, along with updates, Audacity 2.4.1 was installed. Although this is also the OS of 2016.

Hi

I also cannot install 2.4.2. I am on Linux Mint 19.3.

Before getting the Audacity source (which I am not comfortable building as I think I will mess something up), I tried building wxwidgets from source and I seemed to get so far before giving me errors and exiting out. I was building the GTK version which I think is right - is there any easy way to sort this or should I wait for a version of widgets and Audacity to appear in the officical repos?

If you are not comfortable building, I would recommend waiting for the official repos. Even though I build Audacity from source for testing, I generally have the repo version on my production machine.

Thanks Steve, I will wait. I think I could manage building Audacity I think but the widgets throw me.

Audacity 2.4.2 can be built without having to manually build WxWidgets.

Do you know which version of Cmake Mint 19.3 has?

Ah interestingly it says it’s not installed?

That’s normal. Don’t install it, at least not yet.

What’s the output from:

apt-cache madison cmake



    cmake | 3.10.2-1ubuntu2.18.04.1 | http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
     cmake | 3.10.2-1ubuntu2 | http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

If I can get this new version of Audacity working, can I drop most of my old plug in’s back?

Thank you for the help!

Which version of Audacity do you currently use? Audacity 2.2.1?

Hi Steve

Yes, it’s 2.2.1

I’d expect most, if not all plug-ins that work with Audacity 2.2.1, to also work with Audacity 2.4.2.
Also, some plug-ins that didn’t work with 2.2.1 now work with 2.4.2.


Cmake 3.10 is too old for building Audacity, but fortunately it’s reasonably easy to install the latest version. I’ve posted step by step instructions here: https://forum.audacityteam.org/t/building-audacity-2-4-2-on-debian-10-with-cmake-3-18/58352/1
If you get to step 7 and it says that you have cmake 3.18 , then you’re ready to build Audacity 2.4.2.

Don’t attempt to build Audacity 2.4.2 until Cmake 3.18 is successfully installed.

When Cmake 3.18 is installed, follow these instructions exactly as written: https://forum.audacityteam.org/t/building-audacity-2-4-2-on-ubuntu-20-04/57719/1

Good luck :slight_smile:

Hi

Absolutely brilliant! It works straight off! Thank you!

All plug in’s automatically there!

I have another super quick question but am I best to start a new thread? (It’s super quick and I think it will be a yes/no answer!)

Thank you again!
Kyle

PS) Can I delete the downloaded files now that I used to install everything?

Yes, please start a new thread.
I’ll close this topic as “solved” as it may be helpful for other Mint users.

Yes, that should be fine, but if in doubt, send it to the recycle bin so that you can rescue / restore it if anything breaks.

Thank you!