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.

Sign up for GitHub

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

Jump to bottom

Upgrading by package needs cleanup #331

Closed
martinb3 opened this issue Jul 6, 2015 · 1 comment
Closed

Upgrading by package needs cleanup #331

martinb3 opened this issue Jul 6, 2015 · 1 comment
Milestone
2.0.0 release

Comments

@martinb3
Copy link
Contributor

martinb3 commented Jul 6, 2015

Upgrading by package causes potential package manager issues, like prompts or configuration file conflicts. We should maybe handle this better?
@martinb3 martinb3 mentioned this issue Jul 7, 2015
Closed
@martinb3 martinb3 modified the milestone: 1.1.x release Jul 16, 2015
@martinb3 martinb3 modified the milestones: 2.0.0 release, 1.1.0 release Oct 16, 2015
@martinb3
Copy link
Contributor Author

I've just done some testing, upgrading from 1.7.2 to 1.7.3 using only the cookbook. Aside from making a decision about notifications to restart the service or not, upgrading seems to have gone swimmingly. Please re-open if you find this happening again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.0.0 release
Development

No branches or pull requests
1 participant
@martinb3