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

Yum updates #2386

Closed
jwundrak opened this issue Jun 2, 2015 · 4 comments
Closed

Yum updates #2386

jwundrak opened this issue Jun 2, 2015 · 4 comments

Comments

@jwundrak
Copy link

jwundrak commented Jun 2, 2015

This is btw a feauture request.

It will be very nice, if i can see possible updates and commit them. In larger deploments there can be a notification: Server x requires updates and I commit them. The next step is somthing like a RSS, that System X needs an critical update.
Also great: Ubuntu gives you a list, what Fixes are solved. This output should also included.

Just an idea, but this is a cool feature...

@andreasn
Copy link
Contributor

andreasn commented Jun 3, 2015

There is some ongoing work on atomic ostree updates.
Mockups: https://raw.githubusercontent.com/cockpit-project/cockpit-design/master/software-updates/software-updates-ostree-v2.png
And the pull request: #2281

I would imagine that for a first stab at doing updates using rpm/yum/dnf it would follow a somewhat similar workflow (except the rollback, since rpm can't do that).

@andreasn
Copy link
Contributor

andreasn commented Jun 8, 2015

And here is the Trello card for it: https://trello.com/c/lnGL2htr

@andreasn
Copy link
Contributor

I think this is solved by #6724
@martinpitt is that correct?

@martinpitt
Copy link
Member

Yes, I agree. We do show pending updates with changelogs, bug lists, CVE links now. We don't have a "notification" as that's difficult to do from Cockpit itself - but there are distro specific mechanisms for that like Debian's apt-listchanges cron job/email.

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

No branches or pull requests

3 participants