Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Ubuntu 16.04 Xenial LTS #23

Closed
geerlingguy opened this issue Apr 22, 2016 · 3 comments
Closed

Support Ubuntu 16.04 Xenial LTS #23

geerlingguy opened this issue Apr 22, 2016 · 3 comments
Assignees

Comments

@geerlingguy
Copy link

Currently, when attempting to install Varnish on Ubuntu 16.04 LTS, I get:

The repository 'http://repo.varnish-cache.org/ubuntu xenial Release' does not have a Release file.
Failed to fetch http://repo.varnish-cache.org/ubuntu/dists/xenial/varnish-4.0/binary-amd64/Packages  404  Not Found [IP: 194.31.39.155 80]
Failed to fetch http://repo.varnish-cache.org/ubuntu/dists/xenial/varnish-4.0/binary-i386/Packages  404  Not Found [IP: 194.31.39.155 80]

Is a Xenial release channel in the works? I know it's only been a day... :)

@lkarsten
Copy link

Which version of varnish is included in Xenial?

I don't see us building packages of 4.0 for it. I think the consideration is if we will do 4.1 packages for xenial or leave that to the distribution.

@lkarsten lkarsten self-assigned this Apr 25, 2016
@geerlingguy
Copy link
Author

It looks like 4.1.1 is included: http://packages.ubuntu.com/xenial/web/varnish

If that's the case, do you think 4.0/4.1 would ever be supported by Varnish's own PPA, or should I switch my Ansible playbook to use the system packages if on Ubuntu 16.04?

@lkarsten
Copy link

Hi.

Thanks for looking it up. At least it is 4.1, so that should be good enough.

It is still an open question if we'll add xenial packages. We're moving to a rolling 6 month release cycle starting from September, and we haven't decided how "stable" versions should be handled. Packaging takes effort away from writing code, so we prefer to avoid it if the distros can fill the gap.

Unless the trusty packages work for you, I recommend you go with the xenial default one for now.

If we can get packages that work on all recent ubuntus and debians, that would make the decision to keep builing packages easier. I haven't had time to look at this yet.

Closing this as we don't have immediate plans to do it and keeping it open just makes the buglist longer.

I'll update the web page when we have decided what to do in this space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants