Trying to install zerotier-cli on freshly installed Ubuntu 17.10, but it fails with
http://download.zerotier.com/debian/artful artful Release
404 Not Found [IP: 88.198.33.108 80]
Any suggestions?
P.S. apt-transport-http already installed
+1 This is more urgent since Ubuntu has EOL'd Zesty, nudging everyone that is not running LTS to use Aardvark. Issue #607 was closed because Aardvark is "now in the build farm" but apparently that build needs to make its way into actually being downloadable.
+1 Got the same issue. Would be awesome to have it fixed soon because everyone is updating to 17.10 right now.
+1 Adding my voice to the Aardvark choir.
Sadly, 3 days passed and no answer from developers.
I'm using 17.10 and I don't remember having any issues installing zerotier,
I must have installed it a few months ago, I picked 17.10 for my VM to be a
docker host since it worked by default better than Debian.
On Feb 7, 2018 6:00 AM, "Vladislav Vishnyakov" notifications@github.com
wrote:
Sadly, 3 days passed and no answer from developers.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zerotier/ZeroTierOne/issues/674#issuecomment-363761544,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJpRIr22Uce1U9xlljRuX9Nir4oSYbMks5tSZ5ngaJpZM4R4cS1
.
Artful download Coming Soon™️
You could download the script and modify it to point artful at the zesty download. Or modify the /etc/apt/sources.list.d/zerotier.list that you probably have now. I dunno.
Thanks for the update, @laduke
That's exactly what I did (modified zerotier), It's working okay but I'll patiently wait for an Artful version.
+1 please fix this.
I hit this issue as well.
The script bailed out - saying artful wasn't there.
As suggested, I edited /etc/apt/sources.list.d/zerotier.list, replacing artful with stretch.
I then ran:
sudo aptitude install zerotier-one
sudo systemctl enable zerotier-one
sudo systemctl start zerotier-one
Fixed in current build farm, will be fixed in public release with 1.2.6 release which is almost ready.
Still same issue
As mentioned above, 17.10 won't be added to the production version until 1.2.6. It's still at 1.2.4.
Although, now they also need 18.04 so they're 2 versions behind.
Oh, I thought he meant release 1.2.6 for this repo (which is already at 1.2.8). Also, victorhooi's solution worked for me, thanks for that tip :) 👍
Can we reopen this until the problem is actually resolved?
Most helpful comment
Can we reopen this until the problem is actually resolved?