February 2014 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 314662] Use a "green Adwaita" GTK theme
by fate_noreply＠suse.de 11 Nov '14

11 Nov '14

Feature added by: Michael Catanzaro (Golbats_Everywhere) Feature #314662, revision 1 Title: Use a "green Adwaita" GTK theme openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Michael Catanzaro (golbats_everywhere) Partner organization: openSUSE.org Description: openSUSE 12.1/12.2 uses the upstream Adwaita GTK theme. This is mostly good, since it's a very high-quality theme, and I believe one of our goals is to not diverge much from the upstream GNOME experience. However, GNOME's main color is blue, whereas ours is green. When highlighting text, the highlight is blue. When selecting an item in a list, the background turns blue. When selecting the scrollbar, the scrollbar turns blue. When typing into a text form, the form is outlined in blue. I propose we change the blue elements of Adwaita to green elements (by default). This should be all that is changed, so that the theme remains simple to maintain and retains the GNOME feel. I separately propose using the Sonar icon set by default in GNOME, which still works great in 12.2 and is very very close to upstream GNOME. This is not essential to the overall proposal. Screenshots of a mockup: Current: http://paste.opensuse.org/92804741 Proposed: http://paste.opensuse.org/31898989 Current: http://paste.opensuse.org/33805016 Proposed: http://paste.opensuse.org/27086964 Current: http://paste.opensuse.org/13532791 Proposed: http://paste.opensuse.org/57771364 Business case (Partner benefit): openSUSE.org: A green Adwaita theme would fit both upstream GNOME and also openSUSE, and would add a level of polish and integration to the distro. The current "blue Adwaita" theme feels out of place in openSUSE, particularly considering the attention to artistic detail in other parts of the distribution. -- openSUSE Feature: https://features.opensuse.org/314662

1 8

[New: openFATE 311336] zypper lr --active - list only active repos
by fate_noreply＠suse.de 06 Nov '14

06 Nov '14

Feature added by: Christian Boltz (cboltz) Feature #311336, revision 1 Title: zypper lr --active - list only active repos openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Christian Boltz (cboltz) Partner organization: openSUSE.org Description: I often find myself to run zypper lr | grep 'Yes *|' to get a list of all active repos on my system. A zypper option would be useful for this - something like zypper lr --active (not sure about the short version of this option, because the obvious ones (-a, -A) are already taken.) -- openSUSE Feature: https://features.opensuse.org/311336

1 1

[New: openFATE 314473] Replace pwdutils with shadow utilities
by fate_noreply＠suse.de 23 Oct '14

23 Oct '14

Feature added by: Thorsten Kukuk (kukuk) Feature #314473, revision 1 Title: Replace pwdutils with shadow utilities Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: The pwdutils are from a time where the shadow utilities did not had a maintainer and the patches every Linux distribution had were longer then the whole source code. Meanwhile the upstream project is active again and most patches where accepted. Thus we should switch to the shadow project to get all the advantages (for example acl,extended attributes,selinux support). Relations: - README.changes-pwdutils (url: https://build.opensuse.org/package/view_file?file=README.changes-pwdutils&p…) -- openSUSE Feature: https://features.opensuse.org/314473

1 7

[New: openFATE 308967] Allow Oracle Instant Packages
by fate_noreply＠suse.de 18 Oct '14

18 Oct '14

Feature added by: Ciro Iriarte (ciriarte) Feature #308967, revision 1 Title: Allow Oracle Instant Packages Buildservice: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ciro Iriarte (ciriarte) Partner organization: openSUSE.org Description: Include Oracle Instant Client in openSUSE or at least, allow for creation and store in Build Service. This was attempted before but all the work was lost because the files were deleted from OBS. The InstantClient can be redistributed and it doesn't require any license to be used, the only issue is that it doesn't include source code. This can be handled like Sun's Java or Adobe Acrobat. Ref: http://lists.opensuse.org/opensuse-buildservice/2007-08/msg00311.html (http://lists.opensuse.org/opensuse-buildservice/2007-08/msg00311.html) http://lists.suse.com/archive/suse-oracle/2007-Aug/0055.html (http://lists.suse.com/archive/suse-oracle/2007-Aug/0055.html) Use Case: Creation of dependent packages like php-oci, Perl DBD::Oracle or TOra Business case (Partner benefit): openSUSE.org: To make easier the user's life, also this feature would be very attractive, providing Oracle connectivity from CLI, GUI, PHP and Perl out of the box, or at least really fast after adding the needed repository. -- openSUSE Feature: https://features.opensuse.org/308967

1 5

[New: openFATE 310516] YaST2 DNSSEC
by fate_noreply＠suse.de 02 Oct '14

02 Oct '14

Feature added by: Peter Bowen (pzb) Feature #310516, revision 1 Title: YaST2 DNSSEC openSUSE-11.4: New Priority Requester: Important Requested by: Peter Bowen (pzb) Description: With the root zone now being signed, DNSSEC is finally seeing adoption. It would be really nice for YaST to be able to generate a signed zone. -- openSUSE Feature: https://features.opensuse.org/310516

1 8

[New: openFATE 315590] Support non-numeric names for md/raid devices.
by fate_noreply＠suse.de 30 Sep '14

30 Sep '14

Feature added by: Neil Brown (neilbrown) Feature #315590, revision 1 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. -- openSUSE Feature: https://features.opensuse.org/315590

1 13

[New: openFATE 314594] Drop ISDN support
by fate_noreply＠suse.de 03 Sep '14

03 Sep '14

Feature added by: Thorsten Kukuk (kukuk) Feature #314594, revision 1 Title: Drop ISDN support Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: ISDN package still depends on SuSEconfig, there is nobody who is able to adjust the code, ISDN is getting less and less important. -- openSUSE Feature: https://features.opensuse.org/314594

1 14

[New: openFATE 314945] No ABI extension in glibc
by fate_noreply＠suse.de 03 Sep '14

03 Sep '14

Feature added by: Andreas Jaeger (a_jaeger) Feature #314945, revision 1 Title: No ABI extension in glibc openSUSE Distribution: New Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: Currently we have the crypt-blowfish patches in glibc that add new symbol versions to it. I consider that addition wrong and propose to find a solution (might be getting the support in upstream, or using a separate library,...) that does not extend the ABI at all. The goal should be that our glibc exports exactly the same symbols as upstream glibc does. -- openSUSE Feature: https://features.opensuse.org/314945

1 8

[New: openFATE 315589] Deprecate bind-mount configuration with NFSv4 export
by fate_noreply＠suse.de 02 Sep '14

02 Sep '14

Feature added by: Neil Brown (neilbrown) Feature #315589, revision 1 Title: Deprecate bind-mount configuration with NFSv4 export Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: When NFSv4 was introduced it was not possible to export filesystems to NFSv4 the same way as for NFSv3. The "bind=" syntax was added to /etc/exports to help bridge the gaps. With current kernel and nfs-utils this is no longer an issue. By default any filesystem that is exported is exported equally to NFSv2, v3, and v4. So we should deprecate the "bind=" syntax and eventually remove it. This means: 1) yasts nfs-server module should remove knowledge of "Bindmount targets". The "bind=..." option should just be treated like any other option. 2) yasts nfs-server module should not encourage the "fsid=0" export option. Like "bind=" it must still be permitted, but it should be considered and exception rather than normal. 3) Yasts nfs-server help screens should remove mention of "bind=" and "fsid=0". 4) Any documentation that mentioned nfs export, such as http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.… should be changed to remove mention of bind= and fsid=, and should not make any distinciton between NFSv4 and NFSv3. Business case (Partner benefit): openSUSE.org: Simplifies administration, reduces possible confusion, remove unnecessary difference between SUSE and other distros. -- openSUSE Feature: https://features.opensuse.org/315589

1 10

[New: openFATE 309036] Add checkbox to yast2-dns-server whether to use NETCONFIG_DNS_FORWARDER="bind" or not
by fate_noreply＠suse.de 02 Sep '14

02 Sep '14

Feature added by: Marius Tomaschewski (mtomaschewski) Feature #309036, revision 1 Title: Add checkbox to yast2-dns-server whether to use NETCONFIG_DNS_FORWARDER="bind" or not openSUSE-11.3: New Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2-dns). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders.conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) -- openSUSE Feature: https://features.opensuse.org/309036

1 17