Unable to setup Jamulus repository

[ksjdragon]

When running sudo apt update, apt is unable to pull the InRelease file.

Err:17 https://github.com/jamulussoftware/jamulus/releases/latest/download ./ InRelease
401 Unauthorized [IP: 185.199.109.133 443]
Reading package lists... Done
E: Failed to fetch https://github.com/jamulussoftware/jamulus/releases/latest/download/./InRelease 401 Unauthorized [IP: 185.199.109.133 443]
E: The repository 'https://github.com/jamulussoftware/jamulus/releases/latest/download ./ InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Of course, I can go to the URL there and download it without an issue. Any ideas as to what the issue could be?

[pljones]

Could you please provide a console log in full of what commands you've entered prior to the error.

[rdica]

I don't see an update to 2.4.10 for Ubuntu 20.04.
How did you upgrade apt?

[ksjdragon]

I'm on linux mint, I guess I was on an older version of it, so i figured I might as well update it...

I think I saw some ways to install a newer version of apt / an apt with fixes that people pulled
https://launchpad.net/~gpxbv/+archive/ubuntu/apt-urlfix

But I wasn't on ubuntu, so I didn't try it. (I probably could have, since Linux Mint is basically using the ubuntu repositories anyway, but I just didn't want to bother)

[rdica]

The expectation is one keeps their system up to date before installing new software.
I'm glad you got something working but it appears there's an issue with at least Ubuntu 20.04.
Of course a workaround is to manually download the pkg and install it from local disk but then no autoupdating with the rest of the system.

Bug report?

[ksjdragon]

Well, it's not like my system is that out-of-date or anything, it was just on the previous version. I got the repository for the apt-urlfix from here, which was the bug report, seeming to correspond to the same issue with git.

https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1950095

[pljones]

I'm glad you got something working but it appears there's an issue with at least Ubuntu 20.04.

Yeah, we could probably do with a bug for that, if we say we support 20.04 still.

[rdica]

Shall I submit a bug report then?

[ann0see]

Best, add a warning to the website.

[houbsta]

Thanks for the links and information. I can indeed see that Ubuntu 20.04 has an issue with signed repositories with a certain type of URL with unencoded query strings.

I have tried :

• Updating apt to use focal-proposed, which shunts the apt version to 2.0.10
• Setting [trusted=yes] in /etc/sources.list.d/jamulus.list
• Importing the keys manually with apt-key add

Since none of this worked, I cannot see a reasonable workaround for Ubunto 20.04, which means the repo is not supported under Ubuntu 20.04 (you already knew that, I'm just confirming).

So I'm updating to Ubuntu 22.04. For regular users installing the package manually under Ubuntu 20.04 works and is the best solution for them. The repo should be marked as unsupported. Indeed, you might even detect 20.04 in setup-repo.sh and state it isn't supported, since it will throw errors for every apt update and apt upgrade operation once installed, which adds to the confusion for the neophyte.

[ann0see]

Indeed, you might even detect 20.04

Yes, I think that's a good solution. Can you open an issue for that please? I think it should be possible to detect the faulty apt version.

For regular users installing the package manually under Ubuntu 20.04 works and is the best solution for them.

That's probably true, but if I were in their case, I'd just upgrade.