June 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 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

[New: openFATE 310410] Evaluate switching to libjpeg-turbo
by fate_noreply＠suse.de 26 Aug '13

26 Aug '13

Feature added by: Vincent Untz (vuntz) Feature #310410, revision 1 Title: Evaluate switching to libjpeg-turbo openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: Quoting http://fedoraproject.org/wiki/Features/libjpeg-turbo: ==== libjpeg-turbo is fork of the original libjpeg project. It contains numerous performance related enhancements and is at least twice faster in JPEG compression/decompression than original libjpeg on platforms with MMX/SSE instruction set. It has same API/ABI like original libjpeg and also runs on non-SSE platforms where is around 25% faster. http://sourceforge.net/projects/libjpeg-turbo ==== We should evaluate this library and see if we can replace libjpeg with it for improved performance. -- openSUSE Feature: https://features.opensuse.org/310410

1 8

[New: openFATE 313400] store gpg key in fs instead of rpmdb
by fate_noreply＠suse.de 19 Aug '13

19 Aug '13

Feature added by: Ludwig Nussel (lnussel) Feature #313400, revision 1 Title: store gpg key in fs instead of rpmdb openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: currently gpg keys used by rpm for signature verification apppar to be installed in the rpmdb as some kind of pseudo package (rpm -qa 'gpg-pubkey*'). This makes them rather clumsy to manage. It would be better to have gpg keys as regular files in the file system. In fact rpm supports that since a while via the %_keyringpath option. It's set to %{_dbpath}/pubkeys/ by default. If any keys are found in that directory the keys in the rpmdb are no longer used. Therefore I propose to: - change the openSUSE-build-key package to drop it's files into %_keyringpath - patch libzypp to prefer %_keyringpath too - add a %post snippet to rpm or openSUSE-build-key to export extra keys in rpmdb to %_keyringpath and remove them from rpmdb afterwards - make %_keyringpath an array so we can have distro provided keys in /usr and admin/locally configured keys in /etc -- openSUSE Feature: https://features.opensuse.org/313400

1 7

[openFATE 306598] Sync Tomboy/Tasque with Evernote
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Joe Brockmeier (jbrockmeier) Feature #306598, revision 1 Title: Sync Tomboy/Tasque with Evernote Requested by: Joe Brockmeier (jbrockmeier) Description: Evernote is a pretty cool service, but it doesn't have a Linux client. I'd like to be able to sync my Tomboy notes with Evernote and retrieve them from another machine. Same with Tasque -- I'd like to be able to save a to-do list to Evernote from tasque so I could use a mobile Evernote client to look up my to-dos. -- openSUSE Feature: https://features.opensuse.org/306598

1 4

[openFATE 306588] improve on software search
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Juergen Weigert (jnweiger) Feature #306588, revision 1 Title: improve on software search Requested by: Juergen Weigert (jnweiger) Description: software.o.o/search is always a case insensitive substring search. I'd like to hack into the system and add - optional case sensitivity,- exact package name search- regexp search This is an opportunity to learn ruby on rails for me. Any takers, who want to coach me, especially with Rails welcome. -- openSUSE Feature: https://features.opensuse.org/306588

1 6

[openFate 305705] Types of installation
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Agustin Chavarria (dj_ubun_1) Feature #305705, revision 1, last change by Title: Types of installation openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Agustin Chavarria (dj_ubun_1) Partner organization: openSUSE.org Description: would be good, that at the time of installation opensuse, ask what you want to install, like a template, without having to go to edit to add software. An example for that will be: Multimedia install Full install server install developer install -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305705

1 12

[New: openFATE 314470] support the technical such as "Intellicache" of xen
by fate_noreply＠suse.de 12 Aug '13

12 Aug '13

Feature added by: yi li (liyicybertan123) Feature #314470, revision 1 Title: support the technical such as "Intellicache" of xen openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: yi li (liyicybertan123) Partner organization: openSUSE.org Description: support the feature such as "Intellicache" The basic idea behind Intellicache is that it allows you take some of the pressure off of your shared storage by offloading IO onto host local storage. -- openSUSE Feature: https://features.opensuse.org/314470

1 6

[New: openFATE 309614] Activator application for SUSE Studio created appliances
by fate_noreply＠suse.de 12 Aug '13

12 Aug '13

Feature added by: Christian Hueller (chuller) Feature #309614, revision 1 Title: Activator application for SUSE Studio created appliances Requested by: Christian Hueller (chuller) Partner organization: openSUSE.org Description: Basically the idea is simple: Create an application (GUI would be nice) that can 'activate' a previously SUSE Studio built appliance. 'Activate' stands here for things like o register appliance with Novell or ISV o create users and set passwords o do other security relevant things like creating keys or add own proprietary material After the activation it would be awesome to also integrate some deployment functionality to burn isos directly to CD after activation or copy disk images to a usb stick How it might work: Basically the appliance filesystem needs to be accessed in order to modify the appliance accordingly. This could be done through either loop mounting the image or by booting it inside some hypervisor. Loop mounting requires root access, so booting might be the better solution, we only need to take care the kiwi firstboot processes do net get triggered in this activation boot. Possible features: o interaction with studio itself using its API (no manual download of the appliance e.g.) Use Case: The use case is pretty clear as this would cover the gap between the simple creation of an appliance and the frist booting of it on your hardware: The user downloads a SLES11 appliance with the 'activator', then sets the root password and enters the SLES11 registration key. Now the update repositories get added to the appliance and the password is changed without being accessible on the online server. Business case (Partner benefit): openSUSE.org: This would be a great usability improvement to the whole stusio experienc -- openSUSE Feature: https://features.opensuse.org/309614

1 2

[New: openFATE 314598] Make openSUSE for ARM available in SUSE Studio
by fate_noreply＠suse.de 12 Aug '13

12 Aug '13

Feature added by: Samuel Jones (OrangutanClyde) Feature #314598, revision 1 Title: Make openSUSE for ARM available in SUSE Studio SUSE Studio: Unconfirmed Priority Requester: Important Requested by: Samuel Jones (orangutanclyde) Partner organization: openSUSE.org Description: SUSE Studio makes openSUSE available for x86 and amd64 as architectures with the rising interest in ARM thanks to projects such as RaspPi ARM should be made available as an architecture too. Business case (Partner benefit): openSUSE.org: Easy to build, configure and maintain OS's for ARM devices and 'developer' devices like the Rasp PI are no doubt popular thanks to the huge uptake and interest on devices. openSUSE for ARM has recently reached final and no doubt has gained plenty of interest too. -- openSUSE Feature: https://features.opensuse.org/314598

1 2