February 2011 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308964] Network Services in Yasts Conflict with KDE Configure Desktop
by fate_noreply＠suse.de 12 Apr '11

12 Apr '11

Feature added by: Scott Couston - Resigned No Confidence (zczc2311) Feature #308964, revision 1 Title: Network Services in Yasts Conflict with KDE Configure Desktop openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Scott Couston - Resigned No Confidence (zczc2311) Description:  Network Services and their ability to function is often in conflict between KDE's Configure Desktop and Yast. In 11.2 a user cannot configure a Samba server using Yast and Configure Desktop with an MS Workgroup. The Yast>Network Services>Samba Server Interface will simply not work on its own to provide a New or existing shared RW Directory or Publish an Existing Printer. There is conflict between the Interfaces Configure Desktop/Yast Samba Server/The (Dolfin) Directory Properties Rights/The (Dolfin) Directories Properties> Shared Configuration. The Interface in Configure Desktop >Advanced>Samba cannot add a Shared Printer where the Printer is configured by HPLIP. Using ANY or all 3 Interfaces in 11.2 is just NOT possible to create a functional Samba Server By itself HPLIP DOES seamlessly interfaces with Yast>Printer its great. Many Network Service type Interfaces from KDE's Configure Desktop are in conflict. Desktop Search conflicts with Beagle. Configure Desktop Hardware conflicts with Yast Network Connections and others particularly with IFUP. Task Scheduler conflicts with Auto-Start. We need to test out own Interface conflicts between Yast and Configure Desktop settings before we release our integrated KDE Software/Yast Package. Auto-Spell just failed in this text box of FATE. KDE Server and Desktop software needs to work out of the box. (The Fate Error " There were errors: * The description is not valid richtext: Error: Element p is not declared in p list of possible children at :0." does not help anyone -- openSUSE Feature: https://features.opensuse.org/308964

1 3

[New: openFATE 308959] Sheet-local range name
by fate_noreply＠suse.de 12 Apr '11

12 Apr '11

Feature added by: Kohei Yoshida (kohei_yoshida) Feature #308959, revision 1 Title: Sheet-local range name Requested by: Kohei Yoshida (kohei_yoshida) Description: Support range names that are local to sheet. Calc currently supports global range names only. We need this for VBA interop as well as Excel interop reasons. Lack of this feature is also blocking upstream integration of Excel range name support. -- openSUSE Feature: https://features.opensuse.org/308959

1 3

[New: openFATE 308977] Support more than 3 conditions in conditional formatting
by fate_noreply＠suse.de 12 Apr '11

12 Apr '11

Feature added by: Kohei Yoshida (kohei_yoshida) Feature #308977, revision 1 Title: Support more than 3 conditions in conditional formatting Requested by: Kohei Yoshida (kohei_yoshida) Description: Calc currently only supports up to 3 conditions in the conditional formatting dialog. We should extend that to allow perhaps semi-unlimited number of conditions. -- openSUSE Feature: https://features.opensuse.org/308977

1 7

[openFATE 306609] KDE SDK
by fate_noreply＠suse.de 12 Apr '11

12 Apr '11

Feature added by: Cornelius Schumacher (cschum) Feature #306609, revision 1 Title: KDE SDK Requested by: Cornelius Schumacher (cschum) Description: Developing KDE application is not hard, but involves quite a bit ofmachinery. You have to get in place the development environment, tools,documentation for all involved components. Creating a KDE SDK appliance, whichputs all this together in a pre-configured and easily accessible way, could makeit even easier to get started with KDE development. -- openSUSE Feature: https://features.opensuse.org/306609

1 3

[New: openFATE 308658] Restart button in Firefox
by fate_noreply＠suse.de 08 Apr '11

08 Apr '11

Feature added by: Thorsten Kukuk (kukuk) Feature #308658, revision 1 Title: Restart button in Firefox openSUSE-11.3: New Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Description: We release a lot of MozillaFirefox updates. Every update has the risk, that parts of an already running firefox don't work anymore. Especially popup-windows are very often empty afterwards. Because of the broken popup windows, it is not always possible to close firefox and start it again without loosing the current sessions. If you configure themes and/or plugins, MozillaFirefox offers sometimes a "restart" button. We shoud provide this functionality in the standard menu, too, so that customers can restart firefox without loosing data. -- openSUSE Feature: https://features.opensuse.org/308658

1 14

[New: openFATE 311184] Create Maintenace Update request
by fate_noreply＠suse.de 04 Apr '11

04 Apr '11

Feature added by: Adrian Schröter (adrianSuSE) Feature #311184, revision 1 Title: Create Maintenace Update request Buildservice: Evaluation by project manager Milestone: 2.3 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Project Manager: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: OBS needs to support to open a Maintenance project on request. This project is used to prepare, test and document and contain all sources and binaires for a maintenance incident. The project should get a unique ID to identify the incident. The request may also include an entire project used as source for the maintenance incident. The following xml layout is suggested (for example): action type="maintenance" source project="home:adrian:OBS_Maintenance:libqt4" optional, take this project as source target project="openSUSE:Maintenance" required target sourceupdate cleanup sourceupdate optional, will remove source project on update action On accept, the project openSUSE:Maintenance:$ID will get created and the sources from source project will get copied in. Binaries will get rebuild. Having the source project optional makes sense if the maintenance project owner wants to build up a maintenance project manually or for a later feature, when maintenance creates such a project to request to some maintainers to fix a certain issue (basically maintenance would start the process, not the user). -- openSUSE Feature: https://features.opensuse.org/311184

1 3

[New: openFATE 311185] Release packages via merge request
by fate_noreply＠suse.de 04 Apr '11

04 Apr '11

Feature added by: Adrian Schröter (adrianSuSE) Feature #311185, revision 1 Title: Release packages via merge request Buildservice: Evaluation by project manager Milestone: 2.3 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Project Manager: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: To release binaries and sources without changes from one project to another one, we need a request for this. The binaries needs to be merged into an existing repository, but they must not be rebuild in any case. The merge request can be used in multiple ways action type="merge" source project="..." package="..." repository="..." target project="..." package="..." repository="..." /action The only hard required information of this request is the source project. It would lead to merge all sources and binaries to the source linked package sources and all binaries to the repos linked via path. All other attributes may be used to filter the merge sources or targets. Using no filters may have a disadvantage in using the request search later on. -- openSUSE Feature: https://features.opensuse.org/311185

1 1

[New: openFATE 311189] handheld optimized webui
by fate_noreply＠suse.de 04 Apr '11

04 Apr '11

Feature added by: Adrian Schröter (adrianSuSE) Feature #311189, revision 1 Title: handheld optimized webui Buildservice: Evaluation by project manager Milestone: 2.3 Priority Requester: Desirable Requested by: Roland Haidl (rhaidl) Project Manager: (Novell) Partner organization: openSUSE.org Description: The webui is not fully usable on cell phones and other handhelds. Tom works on an optimized interface for Smartphones. -- openSUSE Feature: https://features.opensuse.org/311189

1 3

[New: openFATE 311069] Simple default file share config (ala Ubuntu/MacOSX)
by fate_noreply＠suse.de 02 Apr '11

02 Apr '11

Feature added by: Roger Luedecke (Shadowolf7) Feature #311069, revision 1 Title: Simple default file share config (ala Ubuntu/MacOSX) openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Roger Luedecke (shadowolf7) Partner organization: openSUSE.org Description: Enable simple Share and Dropbox folders by default on each account. Home network filesharing should be easy for the home user. Ubuntu does this very elegantly, with simple sharing and permission management. Current tools in most distros are very confusing to the point of being nearly unusable, including OpenSUSE. I recommend cloning the samba etc. technique as used in Ubuntu/Kubuntu. -- openSUSE Feature: https://features.opensuse.org/311069

1 1

[openFate 305587] Yast template for theming
by fate_noreply＠suse.de 01 Apr '11

01 Apr '11

Feature added by: Jakub Steiner <jimmac(a)novell.com> Feature #305587, revision 1, last change by Title: Yast template for theming openSUSE-11.2: New Priority Requester: Important Requested by: Jim McEldowney <jimmac(a)erie.net> Partner organization: openSUSE.org Description: To be able to skin the Yast installer properly, I would welcome the existence of a YCP template to include all of the widgets included in the actual installer. Business case (Partner benefit): openSUSE.org: Without such a testbed it's extremely hard and error prone to create new styling. In some cases it's impossible to see the implications of a style change until after it has been submitted to build and new distribution snapshot released. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305587

1 6