Feature changed by: Michael Loeffler <michl(a)novell.com>
Feature #302047, revision 28
Title: Integrated package searching for YaST and build service
openSUSE-10.3: Rejected by Andreas Jaeger <aj(a)novell.com>
reject date: 2007-10-05 14:30:28
reject reason: still open partly - postpone the rest.
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.0: Rejected by Michael Loeffler <michl(a)novell.com>
reject date: 2008-06-10 14:01:45
reject reason: not done for 11.0
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.1: Evaluation
Priority
Requester: Important
Requested by: Duncan Mac-Vicar <dmacvicar(a)novell.com>
Partner organization: openSUSE.org
Description:
You perhaps remember the hacks Benjamin did to support "click and
install" packages (similar to Click'n run) [1]
Benjamin has another article in his blog that is worth to read.
He has been providing a wepage to search packages from repositories
like packman and build service. Now he presents an architecture to
desentralize the system, using web services an indexers, and he shows
working prototypes of YaST modules for searching, and others like web
and irc-bot clients
http://blogs.warwick.ac.uk/bweber/entry/package_search_developments/
I hope we can provide a strategy and roadmap to integrate these cool
ideas and _code_.
- Â [1]:
- http://blogs.warwick.ac.uk/bweber/entry/next_generation_package/
+ [1]: http://blogs.warwick.ac.uk/bweber/entry/next_generation_package/
Discussion:
#1: Juergen Weigert <jw(a)novell.com> (2007-05-03 15:29:13)
see also 300898
For 10.3 the installer should be able to make use of an external list
of repositories. I suggest to host such a list at
http://packages.opensuse-community.org/ together with the search
engine, which is already there.
#3: Klaas Freitag <freitag(a)novell.com> (2007-07-12 10:46:54)
Implementation on openSUSE BS already started, Adrian knows the
details.
#4: Adrian Schröter <adrian(a)novell.com> (2007-07-12 11:30:04)
We work on two approaches atm:
* YaST will support (thanks to mvidner) additional repository offers
during installation. The list gets hosted on our servers, the open
question is how to maintain this list.
* The build service End-User interface will offer .ymp files based on
pattern submissions for easy installation.
#5: Stanislav Visnovsky <visnov(a)novell.com> (2007-07-30 20:13:09)
(reply to #4)
Adrian, please, drive this. The feature for YaST should be done now
(let me know if anything is missing).
#6: Michael Loeffler <michl(a)novell.com> (2007-11-22 11:26:30)
This sounds like very useful. And it might be possible the community
(in this case Benji) helps implementing this.
#7: Andreas Jaeger <aj(a)novell.com> (2008-06-06 10:56:28)
Apparently not done - please reject and postpone for 11.1.
#8: Michael Loeffler <michl(a)novell.com> (2008-06-10 14:02:08)
PM-Priority for product openSUSE-11.0 downgraded from mandatory to
important:
not done for 11.0 - PM accepts reality ;-)
#9: Adrian Schröter <adrian(a)novell.com> (2008-06-18 17:08:16)
This is something what we should bind to the new upcomming software
portal. The software portal will be the End-User interface for searcing
and installing software and replace http://software.opensuse.org/search
. However it is still in development and not yet set up. Therefore I am
unsure if this can happen in time for 11.1.
On the other side, the 1-click-installation and integration into the
web interface is done since quite some time. The user can use the cool
technologies from Benjamin since 10.3.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=302047
Feature changed by: Michael Loeffler <michl(a)novell.com>
Feature #302047, revision 27
Title: Integrated package searching for YaST and build service
openSUSE-10.3: Rejected by Andreas Jaeger <aj(a)novell.com>
reject date: 2007-10-05 14:30:28
reject reason: still open partly - postpone the rest.
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.0: Rejected by Michael Loeffler <michl(a)novell.com>
reject date: 2008-06-10 14:01:45
reject reason: not done for 11.0
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.1: Evaluation
Priority
Requester: Important
Requested by: Duncan Mac-Vicar <dmacvicar(a)novell.com>
Partner organization: openSUSE.org
Description:
- You perhaps remember the hacks Benjamin did to support  "click and
+ You perhaps remember the hacks Benjamin did to support "click and
install" packages (similar to Click'n run) [1]
Benjamin has another article in his blog that is worth to read.
He has been providing a wepage to search packages from repositories
like packman and build service. Now he presents an architecture to
desentralize the system, using web services an indexers, and he shows
working prototypes of YaST modules for searching, and others like web
and irc-bot clients
http://blogs.warwick.ac.uk/bweber/entry/package_search_developments/
I hope we can provide a strategy and roadmap to integrate these cool
ideas and _code_.
 [1]:
http://blogs.warwick.ac.uk/bweber/entry/next_generation_package/
Discussion:
#1: Juergen Weigert <jw(a)novell.com> (2007-05-03 15:29:13)
see also 300898
For 10.3 the installer should be able to make use of an external list
of repositories. I suggest to host such a list at
http://packages.opensuse-community.org/ together with the search
engine, which is already there.
#3: Klaas Freitag <freitag(a)novell.com> (2007-07-12 10:46:54)
Implementation on openSUSE BS already started, Adrian knows the
details.
#4: Adrian Schröter <adrian(a)novell.com> (2007-07-12 11:30:04)
We work on two approaches atm:
* YaST will support (thanks to mvidner) additional repository offers
during installation. The list gets hosted on our servers, the open
question is how to maintain this list.
* The build service End-User interface will offer .ymp files based on
pattern submissions for easy installation.
#5: Stanislav Visnovsky <visnov(a)novell.com> (2007-07-30 20:13:09)
(reply to #4)
Adrian, please, drive this. The feature for YaST should be done now
(let me know if anything is missing).
#6: Michael Loeffler <michl(a)novell.com> (2007-11-22 11:26:30)
This sounds like very useful. And it might be possible the community
(in this case Benji) helps implementing this.
#7: Andreas Jaeger <aj(a)novell.com> (2008-06-06 10:56:28)
Apparently not done - please reject and postpone for 11.1.
#8: Michael Loeffler <michl(a)novell.com> (2008-06-10 14:02:08)
PM-Priority for product openSUSE-11.0 downgraded from mandatory to
important:
not done for 11.0 - PM accepts reality ;-)
#9: Adrian Schröter <adrian(a)novell.com> (2008-06-18 17:08:16)
This is something what we should bind to the new upcomming software
portal. The software portal will be the End-User interface for searcing
and installing software and replace http://software.opensuse.org/search
. However it is still in development and not yet set up. Therefore I am
unsure if this can happen in time for 11.1.
On the other side, the 1-click-installation and integration into the
web interface is done since quite some time. The user can use the cool
technologies from Benjamin since 10.3.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=302047
Feature changed by: Thomas Göttlicher <tgoettlicher(a)novell.com>
Feature #304889, revision 20
Title: needs_relogin/needs_reboot as a generic flag
openSUSE-11.1: Candidate
Priority
Requester: Neutral
Projectmanager: Mandatory
Requested by: Stanislav Brabec <sbrabec(a)novell.com>
Partner organization: openSUSE.org
Description:
There are situations, where relogin or reboot are needed to activate
update:
* package updates
* proxy settings
Now this situation is not done in a consistent way (silently ignoring
problem, note in help, abuse of License entry, pop-up...).
Providing a common way for setting these flags (via package provides,
YaST calls, sysconfig comments) (and maybe comment what will happen
ignoring it) would help in user experience (user is notified about need
of relogin/reboot in a consistent way and only once) and administration
(automatic relogin or reboot during maintenance window).
Discussion:
#1: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-26 14:15:12)
needs_reboot is properly handled by our tools. needs_relogin does not
exist.
#2: Jiri Srain <jsrain(a)novell.com> (2008-07-07 10:46:59) (reply to #1)
We handle reboot only for package management not for anything else (the
question is whether it is relevant somewhere else), thus we will need
to have a more generic solution.
Martin, would you, please, have a look and suggest a generic handler?
#3: Stanislav Brabec <sbrabec(a)novell.com> (2008-07-09 15:26:16)
needs_relogin would be useful in these situations:
* New package, which provides file in /etc/profile.d was installed (or
/etc/profile.d was singnificantly modified by the update). Example:
ladspa
* Packages, that cause that /etc/profile will evaluate environment.
Example: Install any KDE application in GNOME only system. /opt/kde3 is
not in PATH until next login
* Patches, that affect login related programs. Example: security update
of ssh-agent or gnome-keyring
* YaST settings, that cause environment variable changes. Example:
System proxy settings
#4: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:14)
Stefan, how is restart and reboot currently handled in packagekit, what
would we need for relogin?
#5: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:58)
(note, ZYpp parts are already done, applications missing )
#6: Stefan Haas <shaas(a)novell.com> (2008-08-08 09:55:52)
PackageKit has three different types for reboot/restart: -Restart
System -Restart Application -Restart Session
#7: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:11)
Stefan Haas will adapt code from PackageKit to support this flag.
#8: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:57)
Thomas, does the KDE applet handle the relogin needed flag from
PackageKit?
#10: Thomas Göttlicher <tgoettlicher(a)novell.com> (2008-08-13 14:27:08)
(reply to #8)
kde4-kupdateapplet listens to PackageKit's restart signal since version
0.8.4.
#9: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:26:53)
Ladislav, is are the current flags in YaST handled in pkg-bindings?
#11: Ladislav Slezak <lslezak(a)novell.com> (2008-08-20 12:16:02) (reply
to #9)
I just have committed the support for Patch::reloginSuggested() flag in
yast SVN. It will be in yast2-pkg-bindings-2.17.8.
I guess we also need some support in YCP... Jiri?
#12: Jiří Suchomel <jsuchome(a)novell.com> (2008-08-21 15:19:11)
Thomas/Stefan: which message does the applet show? I think we should
try to show the same one in YaST and zypper.
(BTW, zypper should be adapted as well -> Jano)
+ #13: Thomas Göttlicher <tgoettlicher(a)novell.com> (2008-08-21 17:20:24)
+ (reply to #12)
+ kupdateapplet shows "Please reboot your system as soon as possible." or
+ "Please relogin into your system as soon as possible.". If PackageKit
+ provides details, these details are shown too. Please let me know if
+ you prefer other strings.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=304889
Feature changed by: Jiří Suchomel <jsuchome(a)novell.com>
Feature #304889, revision 19
Title: needs_relogin/needs_reboot as a generic flag
openSUSE-11.1: Candidate
Priority
Requester: Neutral
Projectmanager: Mandatory
Requested by: Stanislav Brabec <sbrabec(a)novell.com>
Partner organization: openSUSE.org
Description:
There are situations, where relogin or reboot are needed to activate
update:
* package updates
* proxy settings
Now this situation is not done in a consistent way (silently ignoring
problem, note in help, abuse of License entry, pop-up...).
Providing a common way for setting these flags (via package provides,
YaST calls, sysconfig comments) (and maybe comment what will happen
ignoring it) would help in user experience (user is notified about need
of relogin/reboot in a consistent way and only once) and administration
(automatic relogin or reboot during maintenance window).
Discussion:
#1: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-26 14:15:12)
needs_reboot is properly handled by our tools. needs_relogin does not
exist.
#2: Jiri Srain <jsrain(a)novell.com> (2008-07-07 10:46:59) (reply to #1)
We handle reboot only for package management not for anything else (the
question is whether it is relevant somewhere else), thus we will need
to have a more generic solution.
Martin, would you, please, have a look and suggest a generic handler?
#3: Stanislav Brabec <sbrabec(a)novell.com> (2008-07-09 15:26:16)
needs_relogin would be useful in these situations:
* New package, which provides file in /etc/profile.d was installed (or
/etc/profile.d was singnificantly modified by the update). Example:
ladspa
* Packages, that cause that /etc/profile will evaluate environment.
Example: Install any KDE application in GNOME only system. /opt/kde3 is
not in PATH until next login
* Patches, that affect login related programs. Example: security update
of ssh-agent or gnome-keyring
* YaST settings, that cause environment variable changes. Example:
System proxy settings
#4: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:14)
Stefan, how is restart and reboot currently handled in packagekit, what
would we need for relogin?
#5: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:58)
(note, ZYpp parts are already done, applications missing )
#6: Stefan Haas <shaas(a)novell.com> (2008-08-08 09:55:52)
PackageKit has three different types for reboot/restart: -Restart
System -Restart Application -Restart Session
#7: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:11)
Stefan Haas will adapt code from PackageKit to support this flag.
#8: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:57)
Thomas, does the KDE applet handle the relogin needed flag from
PackageKit?
#10: Thomas Göttlicher <tgoettlicher(a)novell.com> (2008-08-13 14:27:08)
(reply to #8)
kde4-kupdateapplet listens to PackageKit's restart signal since version
0.8.4.
#9: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:26:53)
Ladislav, is are the current flags in YaST handled in pkg-bindings?
#11: Ladislav Slezak <lslezak(a)novell.com> (2008-08-20 12:16:02) (reply
to #9)
I just have committed the support for Patch::reloginSuggested() flag in
yast SVN. It will be in yast2-pkg-bindings-2.17.8.
I guess we also need some support in YCP... Jiri?
+ #12: Jiří Suchomel <jsuchome(a)novell.com> (2008-08-21 15:19:11)
+ Thomas/Stefan: which message does the applet show? I think we should
+ try to show the same one in YaST and zypper.
+ (BTW, zypper should be adapted as well -> Jano)
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=304889
Feature changed by: Ladislav Slezak <lslezak(a)novell.com>
Feature #304889, revision 17
Title: needs_relogin/needs_reboot as a generic flag
openSUSE-11.1: Candidate
Priority
Requester: Neutral
Projectmanager: Mandatory
Requested by: Stanislav Brabec <sbrabec(a)novell.com>
Partner organization: openSUSE.org
Description:
There are situations, where relogin or reboot are needed to activate
update:
* package updates
* proxy settings
Now this situation is not done in a consistent way (silently ignoring
problem, note in help, abuse of License entry, pop-up...).
Providing a common way for setting these flags (via package provides,
YaST calls, sysconfig comments) (and maybe comment what will happen
ignoring it) would help in user experience (user is notified about need
of relogin/reboot in a consistent way and only once) and administration
(automatic relogin or reboot during maintenance window).
Discussion:
#1: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-26 14:15:12)
needs_reboot is properly handled by our tools. needs_relogin does not
exist.
#2: Jiri Srain <jsrain(a)novell.com> (2008-07-07 10:46:59) (reply to #1)
We handle reboot only for package management not for anything else (the
question is whether it is relevant somewhere else), thus we will need
to have a more generic solution.
Martin, would you, please, have a look and suggest a generic handler?
#3: Stanislav Brabec <sbrabec(a)novell.com> (2008-07-09 15:26:16)
needs_relogin would be useful in these situations:
* New package, which provides file in /etc/profile.d was installed (or
/etc/profile.d was singnificantly modified by the update). Example:
ladspa
* Packages, that cause that /etc/profile will evaluate environment.
Example: Install any KDE application in GNOME only system. /opt/kde3 is
not in PATH until next login
* Patches, that affect login related programs. Example: security update
of ssh-agent or gnome-keyring
* YaST settings, that cause environment variable changes. Example:
System proxy settings
#4: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:14)
Stefan, how is restart and reboot currently handled in packagekit, what
would we need for relogin?
#5: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:58)
(note, ZYpp parts are already done, applications missing )
#6: Stefan Haas <shaas(a)novell.com> (2008-08-08 09:55:52)
PackageKit has three different types for reboot/restart: -Restart
System -Restart Application -Restart Session
#7: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:11)
Stefan Haas will adapt code from PackageKit to support this flag.
#8: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:57)
Thomas, does the KDE applet handle the relogin needed flag from
PackageKit?
#10: Thomas Göttlicher <tgoettlicher(a)novell.com> (2008-08-13 14:27:08)
(reply to #8)
kde4-kupdateapplet listens to PackageKit's restart signal since version
0.8.4.
#9: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:26:53)
Ladislav, is are the current flags in YaST handled in pkg-bindings?
+ #11: Ladislav Slezak <lslezak(a)novell.com> (2008-08-20 12:16:02) (reply
+ to #9)
+ I just have committed the support for Patch::reloginSuggested() flag in
+ yast SVN. It will be in yast2-pkg-bindings-2.17.8.
+ I guess we also need some support in YCP... Jiri?
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=304889
Feature changed by: Stefan Behlert <behlert(a)novell.com>
Feature #305131, revision 4
Title: connecting an unpartitioned disk should bring up a partitioner
openSUSE-11.1: Evaluation
Priority
Requester: Desirable
+ Projectmanager: Desirable
Requested by: Juergen Weigert <jw(a)novell.com>
Partner organization: openSUSE.org
Description:
USB or Firewire disks can be easily connected at runtime. For a newly
bought disk, nothing happens, when it is connected for the first time.
Unlike e.g. a USB-Memory-stick, which immediatly opens a filebrowser,
when first connected.
The technical difference is, disks come unformatted, USB-sticks come
formatted.
We should recognize this difference and pop up an easy to use
partitioner.
+ Discussion:
+ #1: Stefan Behlert <behlert(a)novell.com> (2008-08-18 12:52:42)
+ Christian, would it be possible to use HAL or something like that to
+ pop-up the Yast-partitioner? I don't think we will get a stripped down
+ partitioner at the moment for 11.1.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=305131
Feature changed by: Frank Sundermeyer <fs(a)novell.com>
Feature #303527, revision 13
Title: Resolve dependencies after ignoring package download failure
openSUSE-11.1: Candidate
Priority
Requester: Desirable
Projectmanager: Desirable
Requested by: Ján Kupec <jkupec(a)novell.com>
Partner organization: openSUSE.org
Description:
YaST and Zypper should run the solver before resuming installation if
download of a package fails and the user chooses to ignore that
package. Currently YaST continues withough solving which makes the
ignore button useful only if the user knows how the missing package
will affect the system.
References:
https://bugzilla.novell.com/show_bug.cgi?id=340345#c4http://lists.opensuse.org/zypp-devel/2008-03/msg00025.html
+ Documentation Impact:
+ Check whether this has documentation impact
Discussion:
#1: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-13 15:13:41)
bit of a corner case.
#2: Ján Kupec <jkupec(a)novell.com> (2008-06-16 11:44:24)
Well, yes. An idea to cover it easily to some extent: let's advice
users to run 'zypper verify' (or the YaST equivalent) in such case,
after the installation is finished. This will fix hard dependencies.
#3: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-24 15:32:30)
(reply to #2)
Yes, I would just suggest to add a message with instructions for the
user.
#4: Jiri Srain <jsrain(a)novell.com> (2008-07-11 10:22:19) (reply to #3)
That should be pretty simple.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=303527
Feature changed by: Frank Sundermeyer <fs(a)novell.com>
Feature #100386, revision 29
Title: Support a verbose logging mode in yast
openSUSE-10.2: Rejected by Andreas Jaeger <aj(a)novell.com>
reject date: 2006-09-30 20:43:33
reject reason: for 10.3.
Priority
Requester: Desirable
Projectmanager: Desirable
openSUSE-10.3: Rejected by Stanislav Visnovsky <visnov(a)novell.com>
reject date: 2007-08-01 10:24:26
reject reason: Postponing, needs more research.
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.0: Rejected by Federico Lucifredi <flucifredi(a)novell.com>
reject date: 2008-06-28 19:27:16
reject reason: fixing my typo. Mandatories in the past don't work
(yet).
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.1: Candidate
Priority
Requester: Important
Projectmanager: Important
SL-10.0: Rejected by Andreas Jaeger <aj(a)novell.com>
reject date: 2005-12-02 14:56:13
reject reason: not done.
Priority
Requester: Desirable
SLES-11: Candidate
Priority
Requester: Important
Projectmanager: Important
Requested by: Andreas Jaeger <aj(a)novell.com>
Partner organization: openSUSE.org
Description:
Create a verbose logging mode in yast, where any action yast performs
is logged. Any file yast touches should be logged (to
/var/log/YaST2/y2log AND clean up the structure of that log file, to
make it easier to read and interpret) and all changes on the systems
configuration. The goal is to make it really transparent what yast
does.
Documentation Impact:
Admin guide needs to contain information about the new log file.
+ Please add it to the Log file section in the troubleshooting chapter
Discussion:
#1: Edith Parzefall <emap(a)novell.com> (2006-09-28 17:17:54)
Can't be done for 10.2. Back to TPMs.
#2: Edith Parzefall <emap(a)novell.com> (2007-07-31 16:17:45)
Sorry, couldn't be done for 10.3. We need a concept for this. Even
within the team different developers have different needs. Improving
the logging to give all developers the best possible debugging
information will be difficult, but it's definitely something we should
attempt in the near future.
#3: Stanislav Visnovsky <visnov(a)novell.com> (2007-11-08 10:48:48)
Can we get some traction here finally?
#4: Stanislav Visnovsky <visnov(a)novell.com> (2007-11-28 10:16:38)
Reopening, the YaST transparency is often cited as a problem for
users.
#6: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-28 17:13:54)
I think this has enough user benefit and is trivial enough, we should
just get it done.
#7: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-28 19:28:04)
PM-Priority for product openSUSE-11.0 downgraded from mandatory to :
oops. Too many widgets for my tired brain.
#8: Stanislav Visnovsky <visnov(a)novell.com> (2008-07-01 16:49:08)
(reply to #7)
This cannot be done completely - this is non-trivial amount of work. I
suggest to start this though, having the YaST infrastructure in place
ASAP. Federico, please, downgrade the priority.
#9: Federico Lucifredi <flucifredi(a)novell.com> (2008-07-02 14:01:05)
PM-Priority for product SLES-11 downgraded from mandatory to important:
too much work for a one-off apparently.
#10: Federico Lucifredi <flucifredi(a)novell.com> (2008-07-02 14:01:27)
PM-Priority for product openSUSE-11.1 downgraded from mandatory to
important:
too much work for a one-shot.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=100386
Feature changed by: Thomas Göttlicher <tgoettlicher(a)novell.com>
Feature #304889, revision 15
Title: needs_relogin/needs_reboot as a generic flag
openSUSE-11.1: Candidate
Priority
Requester: Neutral
Projectmanager: Mandatory
Requested by: Stanislav Brabec <sbrabec(a)novell.com>
Partner organization: openSUSE.org
Description:
There are situations, where relogin or reboot are needed to activate
update:
* package updates
* proxy settings
Now this situation is not done in a consistent way (silently ignoring
problem, note in help, abuse of License entry, pop-up...).
Providing a common way for setting these flags (via package provides,
YaST calls, sysconfig comments) (and maybe comment what will happen
ignoring it) would help in user experience (user is notified about need
of relogin/reboot in a consistent way and only once) and administration
(automatic relogin or reboot during maintenance window).
Discussion:
#1: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-26 14:15:12)
needs_reboot is properly handled by our tools. needs_relogin does not
exist.
#2: Jiri Srain <jsrain(a)novell.com> (2008-07-07 10:46:59) (reply to #1)
We handle reboot only for package management not for anything else (the
question is whether it is relevant somewhere else), thus we will need
to have a more generic solution.
Martin, would you, please, have a look and suggest a generic handler?
#3: Stanislav Brabec <sbrabec(a)novell.com> (2008-07-09 15:26:16)
needs_relogin would be useful in these situations:
* New package, which provides file in /etc/profile.d was installed (or
/etc/profile.d was singnificantly modified by the update). Example:
ladspa
* Packages, that cause that /etc/profile will evaluate environment.
Example: Install any KDE application in GNOME only system. /opt/kde3 is
not in PATH until next login
* Patches, that affect login related programs. Example: security update
of ssh-agent or gnome-keyring
* YaST settings, that cause environment variable changes. Example:
System proxy settings
#4: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:14)
Stefan, how is restart and reboot currently handled in packagekit, what
would we need for relogin?
#5: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-07 22:06:58)
(note, ZYpp parts are already done, applications missing )
#6: Stefan Haas <shaas(a)novell.com> (2008-08-08 09:55:52)
PackageKit has three different types for reboot/restart: -Restart
System -Restart Application -Restart Session
#7: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:11)
Stefan Haas will adapt code from PackageKit to support this flag.
#8: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:25:57)
Thomas, does the KDE applet handle the relogin needed flag from
PackageKit?
+ #10: Thomas Göttlicher <tgoettlicher(a)novell.com> (2008-08-13 14:27:08)
+ (reply to #8)
+ kde4-kupdateapplet listens to PackageKit's restart signal since version
+ 0.8.4.
#9: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-08-11 17:26:53)
Ladislav, is are the current flags in YaST handled in pkg-bindings?
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=304889
Feature changed by: Jiří Suchomel <jsuchome(a)novell.com>
Feature #303520, revision 18
Title: Default NTP Setup
openSUSE-11.1: Candidate
Priority
Requester: Mandatory
Projectmanager: Mandatory
SLED-11: Candidate
Priority
Requester: Mandatory
Projectmanager: Mandatory
SLES-11: Candidate
Priority
Requester: Mandatory
Projectmanager: Mandatory
Requested by: Federico Lucifredi <flucifredi(a)novell.com>
Partner organization: openSUSE.org
Description:
A Yast pane should prompt for NTP set up, which should be configured by
default, but of course can also be disabled there.
Documentation Impact:
Installation guide needs to be updated.
Discussion:
#1: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-17 12:56:47)
Federico, NTP setup is already possible. Do you want it in a more
prominent place? Also I see a missing way for the product to pre-define
the value, correct?
#2: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-23 21:03:12)
(reply to #1)
right. I want to see it pre-enabled by default againt a dedicated suse.
pool.ntp.org / time.novell.com server (separate feature for that).
We are lagging a bit behind Win and Mac where the vendos provide their
own time source, and we need to catch up there.
#3: Jiri Srain <jsrain(a)novell.com> (2008-07-07 12:18:32)
We will need not only to enable NTP during installation, but display
this information in the installation proposal (and possibly time zone
dialog) as well.
+ #6: Jiří Suchomel <jsuchome(a)novell.com> (2008-08-12 13:27:44) (reply
+ to #3)
+ OK, this
+ (http://w3.suse.de/~jsuchome/screenshots/yast2-timezone-ntp-status.png) is
+ proposal how to show the info in current time zone dialog. It is
+ probably bad that status is part of the frame label, but I didn't want
+ to take more space from the whole dialog by adding new line...
#4: Stephan Kulow <coolo(a)novell.com> (2008-07-31 16:15:46)
for openSUSE it's 0.opensuse.pool.ntp.org1.opensuse.pool.ntp.org 2.
opensuse.pool.ntp.org3.opensuse.pool.ntp.org, for SLE there is no NTP
server. time.novell.com can not be used, IS&T does not provide that
level of service.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=303520