- openSUSE Features

[openFate 303520] Default NTP Setup
by fate_noreply＠suse.de 12 Aug '08

12 Aug '08

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.org 1.opensuse.pool.ntp.org 2. opensuse.pool.ntp.org 3.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

1 0

[openFate 304889] needs_relogin/needs_reboot as a generic flag
by fate_noreply＠suse.de 11 Aug '08

11 Aug '08

Feature changed by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Feature #304889, revision 14 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? + #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

1 0

[openFate 304889] needs_relogin/needs_reboot as a generic flag
by fate_noreply＠suse.de 08 Aug '08

08 Aug '08

Feature changed by: Stefan Haas <shaas(a)novell.com> Feature #304889, revision 13 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 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304889

1 0

[openFate 304889] needs_relogin/needs_reboot as a generic flag
by fate_noreply＠suse.de 07 Aug '08

07 Aug '08

Feature changed by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Feature #304889, revision 12 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 ) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304889

1 0

[openFate 304889] needs_relogin/needs_reboot as a generic flag
by fate_noreply＠suse.de 07 Aug '08

07 Aug '08

Feature changed by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Feature #304889, revision 11 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? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304889

1 0

[openFate 305147] Wizard mode for Network Card configuration (in YaST)
by fate_noreply＠suse.de 04 Aug '08

04 Aug '08

Feature changed by: Andreas Jaeger <aj(a)novell.com> Feature #305147, revision 2 Title: Wizard mode for Network Card configuration (in YaST) + openSUSE-11.2: New + Priority + Requester: Neutral SLES-12: New Priority Requester: Neutral Requested by: Michal Zugec <mzugec(a)novell.com> + Partner organization: openSUSE.org Description: (based on "Internet/Intranet with external Router" in suse-beta-e) It seems some users don't know how to setup the SuSEfirewall correctly. Especially, they don't know if they should setup a network card as internal or external device. If a network card is found, YaST should ask for its usage (local network or directly connected to the internet?) - every user should know. With this information the firewall setup can be done in a useful way. See bugzilla https://bugzilla.novell.com/show_bug.cgi?id=67415 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305147

1 0

[openFate 303493] zypper: add separate messages for Required and Recomended packages
by fate_noreply＠suse.de 01 Aug '08

01 Aug '08

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #303493, revision 8 Title: zypper: add separate messages for Required and Recomended packages openSUSE-11.0: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-03-27 13:50:16 reject reason: Not enough time to look into this. Priority Requester: Important - openSUSE-11.1: Evaluation + openSUSE-11.1: Rejected by Federico Lucifredi <flucifredi(a)novell.com> + reject date: 2008-08-01 18:27:34 + reject reason: Cutting scope to match project schedule. Priority Requester: Important Projectmanager: Important - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Important - SLES-11: Evaluation + SLES-11: Rejected by Federico Lucifredi <flucifredi(a)novell.com> + reject date: 2008-08-01 18:27:10 + reject reason: Cutting scope to match project schedule. Priority Requester: Important Projectmanager: Important - SLES-11-SP1: New + SLES-11-SP1: Evaluation Priority Requester: Important Requested by: Cristian Rodriguez <crrodriguez(a)novell.com> Partner organization: openSUSE.org Description: currenly when you install a package with zypper, you just get the packages that are going to be installed, regardless if the are required or Reccommended,.. will be nice if the messages can be arranged to be more explict about what the package manager is doing. "The following NEW [required|reccomended] package is going to be installed: foo" also an informative message about Suggested packages should be shown "The following package(s) is(are) suggested but are not going to be installed foo bar " unless user pass --install-suggested or use a boolean configuration directive on zypp.conf or something, suggested packages should not be installed by default ..currently it seems to be completely ignored and does nothing. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303493

1 0

[openFate 303493] zypper: add separate messages for Required and Recomended packages
by fate_noreply＠suse.de 01 Aug '08

01 Aug '08

Feature changed by: Jiri Srain <jsrain(a)novell.com> Feature #303493, revision 7 Title: zypper: add separate messages for Required and Recomended packages openSUSE-11.0: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-03-27 13:50:16 reject reason: Not enough time to look into this. Priority Requester: Important - openSUSE-11.1: Candidate + openSUSE-11.1: Evaluation Priority Requester: Important Projectmanager: Important - SLES-11: Candidate + openSUSE-11.2: New Priority Requester: Important + SLES-11: Evaluation + Priority + Requester: Important Projectmanager: Important + SLES-11-SP1: New + Priority + Requester: Important Requested by: Cristian Rodriguez <crrodriguez(a)novell.com> Partner organization: openSUSE.org Description: currenly when you install a package with zypper, you just get the packages that are going to be installed, regardless if the are required or Reccommended,.. will be nice if the messages can be arranged to be more explict about what the package manager is doing. "The following NEW [required|reccomended] package is going to be installed: foo" also an informative message about Suggested packages should be shown "The following package(s) is(are) suggested but are not going to be installed foo bar " unless user pass --install-suggested or use a boolean configuration directive on zypp.conf or something, suggested packages should not be installed by default ..currently it seems to be completely ignored and does nothing. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303493

1 0

[openFate 303520] Default NTP Setup
by fate_noreply＠suse.de 31 Jul '08

31 Jul '08

Feature changed by: Stephan Kulow <coolo(a)novell.com> Feature #303520, revision 16 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. + #4: Stephan Kulow <coolo(a)novell.com> (2008-07-31 16:15:46) + for openSUSE it's 0.opensuse.pool.ntp.org 1.opensuse.pool.ntp.org 2. + opensuse.pool.ntp.org 3.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

1 0

[openFate 302921] Testing openSUSE Feature Tracking
by fate_noreply＠suse.de 29 Jul '08

29 Jul '08

Feature changed by: Juergen Weigert <jw(a)novell.com> Feature #302921, revision 22 Title: Testing openSUSE Feature Tracking openSUSE-10.3: Done Priority Requester: Mandatory Requested by: Andreas Jaeger <aj(a)novell.com> Partner organization: openSUSE.org Description: Just a test - should go to opensuse-features(a)opensuse.org Discussion: #1: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:00:36) blah blah blah #2: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:02:35) (reply to #1) blubb lubb lbuib #13: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:57:04) (reply to #1) dsdsdwsd #14: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:59:12) (reply to #13) wsdsdsds #15: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 14:01:10) (reply to #13) dsdsds #16: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 14:11:35) (reply to #13) ddsddds #3: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:12:39) this is working #4: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:16:03) (reply to #3) or bnot #10: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:48:53) (reply to #3) dwsdsdsd #5: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:27:44) swsasaas #6: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:33:36) sqsqasas #7: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:36:11) wdwdswd #8: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:38:00) dwsdsds #9: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:46:33) wswdds #11: Michael Loeffler <michl(a)novell.com> (2007-10-30 13:49:14) wjnd sd s�dlkj sid #12: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 13:52:27) (reply to #11) sasasas #17: Hendrik Vogelsang <hvogel(a)novell.com> (2007-10-30 14:48:56) (reply to #12) xdsdsds #18: Gerald Pfeifer <gp(a)novell.com> (2007-11-02 21:51:25) Moving from openSUSE 10.3 to openSUSE 11.0. + #19: Juergen Weigert <jw(a)novell.com> (2008-07-29 21:53:03) + ping-pong. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=302921

1 0