[opensuse-factory] Online update messages to be improved
It is not the first time that I see such a message while applying online updates: ┌──────────────────────────────────────── │ These updates require a system reboot to function properly: │ │ openSUSE-2014-97. │ │ Reboot the system as soon as possible. │ │ [OK] └──────────────────────────────────────── What can we do to improve those messages? The user will not know what openSUSE-2014-97 is about. BTW, I searched for openSUSE-2014-97 (with DDG), but nothing helpful appears on the result page. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Hi all, Just a heads up the package that was enlightenment is now e16, hopefully that has gone seamlessly for you if not let me know and i will try and improve it. The enlightenment package will re appear in a week or two containing e18 and quite probably e19 before openSUSE 13.2 Cheers Simon Lees --- openSUSE Enlightenment maintainer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/04/2014 05:57 AM, Simon pecked at the keyboard and wrote:
Hi all, Just a heads up the package that was enlightenment is now e16, hopefully that has gone seamlessly for you if not let me know and i will try and improve it. The enlightenment package will re appear in a week or two containing e18 and quite probably e19 before openSUSE 13.2
Cheers
Simon Lees --- openSUSE Enlightenment maintainer
Let this enlighten you, you don't hit reply to a message, change the subject line and then post as a "new" thread. All you do is bury your message in an ongoing thread where it can get lost/buried. If you look at the headers you will find: References: <sh38jzfc00.fsf@frechet.suse.de> In-Reply-To: <sh38jzfc00.fsf@frechet.suse.de> Please open a "new" message and re-post your message. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/05/2014 01:47 AM, Ken Schneider - openSUSE wrote:
On 02/04/2014 05:57 AM, Simon pecked at the keyboard and wrote:
Hi all, Just a heads up the package that was enlightenment is now e16, hopefully that has gone seamlessly for you if not let me know and i will try and improve it. The enlightenment package will re appear in a week or two containing e18 and quite probably e19 before openSUSE 13.2
Cheers
Simon Lees --- openSUSE Enlightenment maintainer
Let this enlighten you, you don't hit reply to a message, change the subject line and then post as a "new" thread. All you do is bury your message in an ongoing thread where it can get lost/buried. If you look at the headers you will find:
References: <sh38jzfc00.fsf@frechet.suse.de> In-Reply-To: <sh38jzfc00.fsf@frechet.suse.de>
Please open a "new" message and re-post your message.
Sorry about that, thunderbird must have started working properly again, i used to always get complaints that i broke threading i'll make a new thread Cheers Simon -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Dienstag, 4. Februar 2014 schrieb Karl Eichwalder:
It is not the first time that I see such a message while applying online updates:
┌──────────────────────────────────────── │ These updates require a system reboot to function properly: │ │ openSUSE-2014-97. │ │ Reboot the system as soon as possible. │ │ [OK] └────────────────────────────────────────
What can we do to improve those messages? The user will not know what openSUSE-2014-97 is about.
The easiest way would be a button "[show patch details]" (or a similar "> show patch details" expandable) that shows the patch description of the patch that asked for the reboot. The BOfH way yould be to just add a text "we told you before in the patch description" ;-)
BTW, I searched for openSUSE-2014-97 (with DDG), but nothing helpful appears on the result page.
In this case, it's the AppArmor update for 13.1. Just in case you wonder why it needs a reboot - I found a bug in apparmor-parser %postun that, in combination with systemd, removes AppArmor protection from running processes when updating the apparmor-parser package. (See the patch description or changelog for details.) That's the reason why this update has the "reboot needed" flag set. If you don't want to reboot, run aa-status and restart all processes listed in the section "... processes are unconfined but have a profile defined." That said - yes, it would be nice to have a place that links "openSUSE-2014-97" to the patch details. BTW: what's "DDG"? Regards, Christian Boltz -- who needs facts if polemics are that much easier to get into. [Sven Burmeister in opensuse-factory]
On 2014-02-04 12:28, Christian Boltz wrote:
The easiest way would be a button "[show patch details]" (or a similar "> show patch details" expandable) that shows the patch description of the patch that asked for the reboot.
what about zypper? A CLI command that produces the information when given "openSUSE-2014-97" as a parameter would be nice. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
Am 04.02.2014 15:11, schrieb Carlos E. R.:
A CLI command that produces the information when given "openSUSE-2014-97" as a parameter would be nice.
zypper patch-info openSUSE-2014-97 -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-02-04 15:40, Stefan Seyfried wrote:
Am 04.02.2014 15:11, schrieb Carlos E. R.:
A CLI command that produces the information when given "openSUSE-2014-97" as a parameter would be nice.
zypper patch-info openSUSE-2014-97
Oh. I should have said that a brief information about this command line could be added to the initial message :-) -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
Christian Boltz <opensuse@cboltz.de> writes:
The easiest way would be a button "[show patch details]" (or a similar "> show patch details" expandable) that shows the patch description of the patch that asked for the reboot.
Yes, agreed. This would make sense.
The BOfH way yould be to just add a text "we told you before in the patch description" ;-)
Yeah, I already thought about that and was a little bit angry with myself that I did not do a screen shot during the update ;)
In this case, it's the AppArmor update for 13.1. Just in case you wonder why it needs a reboot - I found a bug in apparmor-parser %postun that, in combination with systemd, removes AppArmor protection from running processes when updating the apparmor-parser package. (See the patch description or changelog for details.) That's the reason why this update has the "reboot needed" flag set.
Thanks for the explanation!
If you don't want to reboot, run aa-status and restart all processes listed in the section "... processes are unconfined but have a profile defined."
Ok, maybe I'll try that.
That said - yes, it would be nice to have a place that links "openSUSE-2014-97" to the patch details.
This would be nice. Of course, you could filter for "Installed Patches" (sorting isn't perfect, though). I should probably enter enhancement bugs.
BTW: what's "DDG"?
This is the DuckDuckGo search engine ;^) -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Carlos E. R. -
Christian Boltz -
Karl Eichwalder -
Ken Schneider - openSUSE -
Simon -
Stefan Seyfried