September 2013 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 313142] YaST support only SSSD for LDAP based authentication
by fate_noreply＠suse.de 05 Sep '13

05 Sep '13

Feature added by: Ralf Haferkamp (rhafer) Feature #313142, revision 1 Title: YaST support only SSSD for LDAP based authentication openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: We should remove support for nss_ldap and pam_ldap configuration from the YaST ldap-client module (note: this is not a request to remove nss_ldap and pam_ldap from the distribution) and only support SSSD for LDAP based users authentication. The nss_ldap and pam_ldap packages should still be part of future distribution to still allow manual setup. When updating an nss-/pam_ldap based system from an older release it should stay with nss-/pam_ldap. Upon first startup of yast2-ldap-client it might offer a migration to sssd. Business case (Partner benefit): openSUSE.org: Focussing on a single implementation for LDAP authentication allows us to provide a cleaner UI and should reduce the complexity of the YaST ldap-client module considerably. Making it easier to use and maintain. -- openSUSE Feature: https://features.opensuse.org/313142

1 9

[openFATE 303534] Extend BarGraph Widget
by fate_noreply＠suse.de 03 Sep '13

03 Sep '13

Feature changed by: Lukas Ocilka (locilka) Feature #303534, revision 39 Title: Extend BarGraph Widget openSUSE-11.2: Rejected by Stephan Kulow (coolo) reject date: 2009-08-12 11:57:51 reject reason: too late for 11.2 I would think, but 25 votes lets me reopen for 11.3 Priority Requester: Desirable Projectmanager: Neutral - openSUSE-11.3: Evaluation by engineering manager + openSUSE-11.3: Rejected by Lukas Ocilka (locilka) + reject date: 2013-09-03 15:23:08 + reject reason: openSUSE 11.3 has been out for ages, not delivered in + time. Priority Requester: Desirable Projectmanager: Neutral Requested by: Arvin Schnell (aschnell) Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: The latest mockups for the partitioner contain an BarGraph with additional features: * legend * several areas with same color/legend * a bit small (maybe not so important) Here is a picture (http://w3.suse.de/~aschnell/bg2.png) from the mockup. Relations: - Enhance partitioner to be more user friendly (novell/bugzilla/id: 390213) https://bugzilla.novell.com/show_bug.cgi?id=390213 - Graphical Display of Hard Disk partitions (novell/bugzilla/id: 414322) https://bugzilla.novell.com/show_bug.cgi?id=414322 - Blog Comment praising GParted (url: http://lizards.opensuse.org/2009/03/06/context-menus-in-yast-partitioner/#c…) Discussion: #1: Federico Lucifredi (flucifredi) (2008-06-13 15:15:21) Stano, if we need it it is of course M. Let me know, I just have no business reasons, this is entirely an engineering decision. #2: Stefan Hundhammer (sh-sh-sh) (2008-06-17 15:29:07) What's wrong with using the _existing_ widget with its existing features? #3: Stanislav Visnovsky (visnov) (2008-06-17 15:54:05) Agreement is that this is not needed. #4: Katarina Machalkova (kmachalkova) (2009-02-25 16:43:41) Can we please re-consider this for openSUSE 11.2 ? Some visualization of used/free space ratio on the disk/partition, or the whole disk layout in the partitioner overviews would be nice. The problem (not the only one) with current bar graph widget is that if some portion of the graph becomes too small, the text on it is no longer readable. A legend of the graph (as depicted above) would help a lot, but at the very minimum, some tooltips over the graph parts could be added #5: Michael Löffler (michl19) (2009-03-25 17:27:12) (reply to #4) It looks still like an engineering decsion. Stano please re-consider or reject ;-) #6: Arvin Schnell (aschnell) (2009-03-25 17:53:24) (reply to #5) I don't understand why this should be an engineering decision. This feature will directly influence what the users see. It's not a detail hidden deep in source code that makes geeks say "wow" if they should find it while being bored to death. This is a feature users are constantly asking for! #11: Jean-Daniel Dodin (jdd_sysop) (2009-04-08 20:53:33) gparted is much friendly than YaST. shame. jdd #12: FERNANDO RUBEN ESPINOSA RAMIREZ. (fersito) (2009-04-09 04:01:51) You must to do what ever you want Katarina so in order to learn like myself.-fernando (from Leòn GTO. Mexico)greetings. #13: Duncan Mac-Vicar (dmacvicar) (2009-04-09 11:03:22) (reply to #12) This is even a fake email. Final-Recipient: rfc822; ferub(a)att.net.mx Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; host mailin-02.mx.aol.com[64.12.137.89] said: 550 MAILBOX NOT FOUND (in reply to RCPT TO command) #14: Marc Telesha (mtelesha) (2009-05-10 08:03:28) Persoanlly I used a LiveCD of Parted Parted (Gpartitioner) before installing OpenSUSE everytime. It is much easier to do it this way when setting up a dual booting computer.I really think if it had a better GUI for partitions it would make this partitioning easier for people to understand, especially people giving Linux a try.-Marc #15: Roman Bysh (romanator) (2010-01-31 02:12:55) I agree. We should be leaders in innovation NOT followers. It's about time we start setting an example on how things are to be done in Linux. SuSE and openSUSE have been around a long time. -- openSUSE Feature: https://features.opensuse.org/303534

1 0

[openFATE 306974] Additional columns in software management
by fate_noreply＠suse.de 03 Sep '13

03 Sep '13

Feature added by: Todd R (TheBlackCat) Feature #306974, revision 1 Title: Additional columns in software management openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Todd R (theblackcat) Description: It would be nice if there were a few additional columns in the software management interface. One specific column I am interested in would be an architecture column, to show you the architecture of an installed package or the architecture the package would have if you were to install it. The other column would show the repository of the package, either the repository of an installed package or the repository the package would be downloaded from if you were to install it. -- openSUSE Feature: https://features.opensuse.org/306974

1 6

[openFATE 313535] Get rid of SuSEconfig.texlive
by fate_noreply＠suse.de 03 Sep '13

03 Sep '13

Feature changed by: Stefan Fent (sfent) Feature #313535, revision 8 Title: Get rid of SuSEconfig.texlive - openSUSE Distribution: Evaluation by engineering manager + openSUSE Distribution: Ready Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of the texlive packages as only those are affected. Relations: - Remove SuSEconfig (feature/id: 100011) -- openSUSE Feature: https://features.opensuse.org/313535

1 0

[openFATE 312568] YaST: add support for systemd service in Services Manager (replacement for Runlevel Editor)
by fate_noreply＠suse.de 02 Sep '13

02 Sep '13

Feature changed by: Lukas Ocilka (locilka) Feature #312568, revision 13 - Title: YaST: add support for systemd service in runlevel editor + Title: YaST: add support for systemd service in Services Manager + (replacement for Runlevel Editor) openSUSE Distribution: Implementation Priority Requester: Important Projectmanager: Mandatory Requested by: Frederic Crozat (fcrozat) Partner organization: openSUSE.org Description: Yast runlevel editor should be able to detect if systemd is running and allow to enable/disable systemd service (which can shadow some sysvinit services). Relations: - systemd adaptation of YaST (novell/bugzilla/id: https://bugzilla.novell.com/show_bug.cgi?id=664548) https://bugzilla.novell.com/show_bug.cgi?id=https://bugzilla.novell.com/sho… Discussion: #2: Frederic Crozat (fcrozat) (2012-01-06 11:27:40) YaST support (probably adding a service) should talk to systemd using D- Bus API (like it is already done in systemd gtk gui), so it won't have to handle merge of configuration and so on. #3: Andreas Jaeger (a_jaeger) (2013-07-19 11:14:53) Isn't this done already? #4: Frederic Crozat (fcrozat) (2013-07-19 11:33:27) (reply to #3) it is : http://kobliha-suse.blogspot.fr/2013/06/yast-runlevel-is-dead-long-live-yas… #5: Andreas Jaeger (a_jaeger) (2013-07-19 11:35:51) (reply to #4) Thanks - written in ruby. So, if we go to ruby, this is done. Thus not marking yet as done but leaving it open for evaluation until a decision is made that the ruby version will be the SLE 12 one. #6: Lukas Ocilka (locilka) (2013-07-30 14:31:47) (reply to #5) Code is here: https://github.com/yast/yast-services-manager And Ruby is set :) Anyway, some parts are still missing... #7: Jiri Srain (jsrain) (2013-08-15 14:57:26) (reply to #6) So, let's finish them :-) #8: Lukas Ocilka (locilka) (2013-09-02 16:56:49) (reply to #7) Vlado, please, take over. -- openSUSE Feature: https://features.opensuse.org/312568

1 0

[openFATE 312568] YaST: add support for systemd service in runlevel editor
by fate_noreply＠suse.de 02 Sep '13

02 Sep '13

Feature changed by: Lukas Ocilka (locilka) Feature #312568, revision 12 Title: YaST: add support for systemd service in runlevel editor - openSUSE Distribution: Evaluation by engineering manager + openSUSE Distribution: Implementation Priority Requester: Important Projectmanager: Mandatory Requested by: Frederic Crozat (fcrozat) Partner organization: openSUSE.org Description: Yast runlevel editor should be able to detect if systemd is running and allow to enable/disable systemd service (which can shadow some sysvinit services). Relations: - systemd adaptation of YaST (novell/bugzilla/id: https://bugzilla.novell.com/show_bug.cgi?id=664548) https://bugzilla.novell.com/show_bug.cgi?id=https://bugzilla.novell.com/sho… Discussion: #2: Frederic Crozat (fcrozat) (2012-01-06 11:27:40) YaST support (probably adding a service) should talk to systemd using D- Bus API (like it is already done in systemd gtk gui), so it won't have to handle merge of configuration and so on. #3: Andreas Jaeger (a_jaeger) (2013-07-19 11:14:53) Isn't this done already? #4: Frederic Crozat (fcrozat) (2013-07-19 11:33:27) (reply to #3) it is : http://kobliha-suse.blogspot.fr/2013/06/yast-runlevel-is-dead-long-live-yas… #5: Andreas Jaeger (a_jaeger) (2013-07-19 11:35:51) (reply to #4) Thanks - written in ruby. So, if we go to ruby, this is done. Thus not marking yet as done but leaving it open for evaluation until a decision is made that the ruby version will be the SLE 12 one. #6: Lukas Ocilka (locilka) (2013-07-30 14:31:47) (reply to #5) Code is here: https://github.com/yast/yast-services-manager And Ruby is set :) Anyway, some parts are still missing... #7: Jiri Srain (jsrain) (2013-08-15 14:57:26) (reply to #6) So, let's finish them :-) + #8: Lukas Ocilka (locilka) (2013-09-02 16:56:49) (reply to #7) + Vlado, please, take over. -- openSUSE Feature: https://features.opensuse.org/312568

1 0