Upstream Repository Broken

[cwillhelm]

Hi, when trying to access http://repos.mesosphere.com/ubuntu/pool/main/m/marathon/marathon_1.7.189-0.1.20190125223314.ubuntu1804_all.deb I keep getting this error:

NoSuchKeyThe specified key does not exist.ubuntu/pool/main/m/marathon/marathon_1.7.189-0.1.20190125223314.ubuntu1804_all.de2742A71C895AC991Iye9mL0zDzOvQd+Ws17B7NuV/IFizyFL5s9xgQIDiTyO9tbYK7OKxj7hYqWeQHYpdH4+XJIilOU=

It would be awesome if this could get fixed soon!

[cwillhelm]

Would it be possible to get an update on this?

[inka]

Having the same issue. Just following the docs https://mesosphere.github.io/marathon/docs/native-packages.html

apt-key adv --keyserver keyserver.ubuntu.com --recv DF7D54CBE56151BF
echo "deb http://repos.mesosphere.com/ubuntu bionic main" >/etc/apt/sources.list.d/mesosphere.list
apt-get update
apt-get -y install marathon

Results in

E: Failed to fetch http://repos.mesosphere.com/ubuntu/pool/main/m/marathon/marathon_1.7.189-0.1.20190125223314.ubuntu1804_all.deb  404  Not Found [IP: 99.84.224.51 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Is bionic not supported yet?

[esoterick]

Managed to get this working on bionic by specifying a specific package version.

root@zelda:/data/genconf# apt install marathon=1.7.189-0.1.20190125215327.ubuntu1804
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  marathon
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 77.0 MB of archives.
After this operation, 83.6 MB of additional disk space will be used.
Get:1 http://repos.mesosphere.com/ubuntu bionic/main amd64 marathon all 1.7.189-0.1.20190125215327.ubuntu1804 [77.0 MB]
Fetched 77.0 MB in 3s (29.5 MB/s)
Selecting previously unselected package marathon.
(Reading database ... 146135 files and directories currently installed.)
Preparing to unpack .../marathon_1.7.189-0.1.20190125215327.ubuntu1804_all.deb ...
Unpacking marathon (1.7.189-0.1.20190125215327.ubuntu1804) ...
Setting up marathon (1.7.189-0.1.20190125215327.ubuntu1804) ...
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.```