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

bash-completion broken #4

Closed
AnrDaemon opened this issue Feb 13, 2016 · 11 comments
Closed

bash-completion broken #4

AnrDaemon opened this issue Feb 13, 2016 · 11 comments

Comments

@AnrDaemon
Copy link
Contributor

c388fda broke bash-completion on 12.04

_have: command not found
@ohmer1
Copy link

ohmer1 commented Feb 16, 2016

I confirm, same problem here.

@stgraber
Copy link
Member

Unfortunately reverting this would break bash completion on more the latest versions of bash & bash-completion so I don't expect us to revert this what with Ubuntu 12.04 LXC being a best effort automatic backport (no supported version of LXC for 12.04).

@stgraber
Copy link
Member

Well, someone could potentially make yet another debian/rules hack to sed _have for have in the bash completion file and I probably would merge it. Just won't be working on it myself.

@AnrDaemon
Copy link
Contributor Author

Or just remove 2.0 packaging for 12.04. That could be an option as well.

@stgraber
Copy link
Member

The PPA is auto-generated, if we remove 2.0, you'll end up with the release time LXC of version 0.7, not sure you'll like that downgrade :)

@AnrDaemon
Copy link
Contributor Author

shrug >.<

@AnrDaemon
Copy link
Contributor Author

Ok, which file you were mentioning? Github slows down to a crawl each time I try to browse commits.

@stgraber
Copy link
Member

https://github.com/lxc/lxc-pkg-ubuntu/blob/dpm-xenial/debian/rules

It'd need some more override_dh_install logic

@AnrDaemon
Copy link
Contributor Author

It may need a move down the block, if 13.10 is also affected. But I do not have a system ready to check.

@evgeni
Copy link
Contributor

evgeni commented Feb 19, 2017

@stgraber @AnrDaemon this can be closed then?

@stgraber
Copy link
Member

yup

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

No branches or pull requests

4 participants