January 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 312440] Package libbluray
by fate_noreply＠suse.de 18 Jan '12

18 Jan '12

Feature added by: Vincent Untz (vuntz) Feature #312440, revision 1 Title: Package libbluray Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Vincent Untz (vuntz) Partner organization: openSUSE.org Description: gvfs can use libbluray to access Blu-Ray metadata. http://www.videolan.org/developers/libbluray.html It should apparently be safe to integrate in openSUSE, according to the webpage. -- openSUSE Feature: https://features.opensuse.org/312440

1 3

[New: openFATE 312343] get rid of /etc/sysconfig/sysctl
by fate_noreply＠suse.de 17 Jan '12

17 Jan '12

Feature added by: Ludwig Nussel (lnussel) Feature #312343, revision 1 Title: get rid of /etc/sysconfig/sysctl openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: /etc/sysconfig/sysctl and therefore boot.proc and boot.ipconfig should be dropped in favor of directly using /etc/sysctl.conf Distro defaults should be provided via /lib/sysctl.d./*.conf so we don't produce .rpmnew files on upgrade. 1. write script to convert old setings in aaa_base's %post [ready] 2. write patch for sysctl to read /lib/sysctl.d/*.conf [ready] 3. adjust yast modules -- openSUSE Feature: https://features.opensuse.org/312343

1 10

[New: openFATE 312783] Display installation date and uptime time in the sysinfo:/ page
by fate_noreply＠suse.de 16 Jan '12

16 Jan '12

Feature added by: Eduardo Sotomayor (Easgs) Feature #312783, revision 1 Title: Display installation date and uptime time in the sysinfo:/ page openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Eduardo Sotomayor (easgs) Partner organization: openSUSE.org Description: Display installation date and uptime in the sysinfo:/ page -- openSUSE Feature: https://features.opensuse.org/312783

1 3

[New: openFATE 312407] switch off boot.clock
by fate_noreply＠suse.de 16 Jan '12

16 Jan '12

Feature added by: Ludwig Nussel (lnussel) Feature #312407, revision 1 Title: switch off boot.clock openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Nowadays the timezone and a potential local/utc offset are applied in the initrd already. The only task left for boot.clock is to adjust the clock drift. That's a rather advanced feature not known nor appreciated by the standard auto logging in user. Network installs have ntp enabled anyways. Therefore boot.clock should be switched off by default to have one less script to execute. Anyone who needs the clock drift feature can insserv boot.clock manually. Business case (Partner benefit): openSUSE.org: faster boot -- openSUSE Feature: https://features.opensuse.org/312407

1 2

[openFATE 313143] YaST LDAP client refactor/cleanup
by fate_noreply＠suse.de 16 Jan '12

16 Jan '12

Feature changed by: Ralf Haferkamp (rhafer) Feature #313143, revision 4 Title: YaST LDAP client refactor/cleanup openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: Jiri (jsuchome) an I recently discussed some cleanup work we'd like to see in the YaST ldap-client module. This feature lists the main items we'd like to see reworked to improve the Module: Remove no longer needed UI elements Candidates are: * The TLS/SSL checkbox (sssd has a hard requirement for SSL/TLS) * The "LDAP Version 2" checkbox in the advanced settings. (there is AFAIK no LDAPv2-only Server implementation left) * The "Use LDAP but Disable Login" Radio Button Restrict the UI to handle only really LDAP client related things Currently the UI contains quite some settings which are not strictly related to LDAP client (nss/pam) setup. Over the year ldap-client became a bit of a disposal site for all kinds of LDAP related things, which made the UI a bit hard to understand. We should move some things to YaST modules where make a better fit. This is mostly about the settings currently available in the "Administration Settings" Tab (in "Advanced Configuration") * The Password Policies settings seem to fit better into the ldap- server module which already contains some of this functionality * Default Configuration Objects for other YaST modules (e.g. mail, dns, dhcp). Where possible the need for those special configuration objects should be removed. When a specific service still requires those configuration objects the YaST module for that service should be able to handle those objects it self (we could still offer utils API for that in yast2-ldap/ldap-client). E.g. the user management related object should be configured from inside the yast2-users module. yast2- ldap-server could offer to create default objects during the initial LDAP server setup. * The Home Directories on This Machine checkbox seems to be better suite in the Users module as well. * The rest of the values which go to /etc/sysconfig/ldap could be written by yast2-ldap-servers. We still need to figure out how to setup /etc/sysconfig/ldap on machines which to not run the LDAP Server but need access to those settings. (yast2-mail, -dns-server, -dhcp-server) * Adapt the API: move the LDAP* functions from ldap-client (impact on other modules!) + Relations: + - related feature (feature/id: 313142) -- openSUSE Feature: https://features.opensuse.org/313143

1 0

[openFATE 313143] YaST LDAP client refactor/cleanup
by fate_noreply＠suse.de 16 Jan '12

16 Jan '12

Feature changed by: Ralf Haferkamp (rhafer) Feature #313143, revision 3 Title: YaST LDAP client refactor/cleanup openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) + Partner organization: openSUSE.org Description: Jiri (jsuchome) an I recently discussed some cleanup work we'd like to see in the YaST ldap-client module. This feature lists the main items we'd like to see reworked to improve the Module: Remove no longer needed UI elements Candidates are: * The TLS/SSL checkbox (sssd has a hard requirement for SSL/TLS) * The "LDAP Version 2" checkbox in the advanced settings. (there is AFAIK no LDAPv2-only Server implementation left) * The "Use LDAP but Disable Login" Radio Button Restrict the UI to handle only really LDAP client related things Currently the UI contains quite some settings which are not strictly related to LDAP client (nss/pam) setup. Over the year ldap-client became a bit of a disposal site for all kinds of LDAP related things, which made the UI a bit hard to understand. We should move some things to YaST modules where make a better fit. This is mostly about the settings currently available in the "Administration Settings" Tab (in "Advanced Configuration") * The Password Policies settings seem to fit better into the ldap- server module which already contains some of this functionality * Default Configuration Objects for other YaST modules (e.g. mail, dns, dhcp). Where possible the need for those special configuration objects should be removed. When a specific service still requires those configuration objects the YaST module for that service should be able to handle those objects it self (we could still offer utils API for that in yast2-ldap/ldap-client). E.g. the user management related object should be configured from inside the yast2-users module. yast2- ldap-server could offer to create default objects during the initial LDAP server setup. * The Home Directories on This Machine checkbox seems to be better suite in the Users module as well. * The rest of the values which go to /etc/sysconfig/ldap could be written by yast2-ldap-servers. We still need to figure out how to setup /etc/sysconfig/ldap on machines which to not run the LDAP Server but need access to those settings. (yast2-mail, -dns-server, -dhcp-server) * Adapt the API: move the LDAP* functions from ldap-client (impact on other modules!) -- openSUSE Feature: https://features.opensuse.org/313143

1 0

[New: openFATE 311074] Enhance Education Repository
by fate_noreply＠suse.de 13 Jan '12

13 Jan '12

Feature added by: Lars Vogdt (lrupp) Feature #311074, revision 1 Title: Enhance Education Repository Hackweek VI: Unconfirmed Priority Requester: Important Requested by: Lars Vogdt (lrupp) Partner organization: openSUSE.org Description: Right now, openSUSE have quite few scientific and educational packages. To give openSUSE more presence on universities and research centers at "final user" level, it would be necessary to review the current packages in the Education and science repositories and check for updates and new packages that are currently not on the list. Business case (Partner benefit): openSUSE.org: The Education and Science Sector is one of the most important sectors to reach new and enthusiastic users. We should offer a bunch of applications for this users fulfilling all their needs and as result, we can increase the number of openSUSE users in a very special, but also interesting and important area. -- openSUSE Feature: https://features.opensuse.org/311074

1 4

[New: openFATE 313057] Automatically enable new version branch as target
by fate_noreply＠suse.de 11 Jan '12

11 Jan '12

Feature added by: Robert Schweikert (rjschwei) Feature #313057, revision 1 Title: Automatically enable new version branch as target Buildservice: Unconfirmed Priority Requester: Important Requested by: Robert Schweikert (rjschwei) Partner organization: openSUSE.org Description: We should automatically enable the new release branch as a build target for all projects that build against factory when we branch. For all projects that build for new version -1 and factory. This avoids the hassle of maintainers having to go in and turning this on explicitly. My guess would be that there are fewer maintainers that do not want this behavior than there are maintainers that want this behavior. The other alternative would be to add yet another setting to the meta data of a project that says "build-new-target-on-release-branching" then maintainers can choose this depending on their preference. I don't think we need such a flag, but it gives control to project maintainers. -- openSUSE Feature: https://features.opensuse.org/313057

1 4

[New: openFATE 312338] Add BlueGriffon web editor to the repositories
by fate_noreply＠suse.de 08 Jan '12

08 Jan '12

Feature added by: Ricardo Martins (rikhard) Feature #312338, revision 1 Title: Add BlueGriffon web editor to the repositories Package Wishlist: Unconfirmed Priority Requester: Neutral Requested by: Ricardo Martins (rikhard) Partner organization: openSUSE.org Description: BlueGriffon is a relatively young project, but it does seem to be very good when compared to some of the other open source tools, not to mention that it's still a very active project. -- openSUSE Feature: https://features.opensuse.org/312338

1 9

[openFATE 312568] YaST: add support for systemd service in runlevel editor
by fate_noreply＠suse.de 06 Jan '12

06 Jan '12

Feature changed by: Frederic Crozat (fcrozat) Feature #312568, revision 5 - Title: YaSY: add support for systemd service in runlevel editor + Title: YaST: add support for systemd service in runlevel editor openSUSE Distribution: New Priority Requester: Important 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. -- openSUSE Feature: https://features.opensuse.org/312568

1 0