June 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306403] KOffice 2.1 in 11.2
by fate_noreply＠suse.de 08 Jun '09

08 Jun '09

Feature changed by: Ricardo Gabriel Berlasso (RGBsuse) Feature #306403, revision 8 Title: KOffice 2.1 in 11.2 openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Jean Cayron (jeancayron) Developer: Stephan Binner (beineri) Description: KOffice 2.1 will be released in november 2009, at the same time than openSUSE 11.2 ( see release plan (http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.1/Release_Plan) ). Since the 2.0 will not be feature complete, it would be great for KDE4 integration to have the latest version on the official repositories (maybe do as Firefox the RC with later update). Let make the people choose their Office Suite. Discussion: #1: Ricardo Gabriel Berlasso (rgbsuse) (2009-06-05 23:44:24) Another possibility is to implement a dedicated repository for koffice, in the same way we now have the repository for OOo. #2: Stephan Binner (beineri) (2009-06-08 09:00:58) (reply to #1) The usual KDE:Backports repository should be sufficient. + #3: Ricardo Gabriel Berlasso (rgbsuse) (2009-06-08 14:25:35) (reply to + #2) + I do not agree: enabling backport repo means enabling ALL the content on + the backport repo. I only want koffice. -- openSUSE Feature: https://features.opensuse.org/306403

1 0

[openFATE 303493] zypper: add separate messages for Required and Recomended packages
by fate_noreply＠suse.de 08 Jun '09

08 Jun '09

Feature changed by: Ján Kupec (jkupec) Feature #303493, revision 12 Title: zypper: add separate messages for Required and Recomended packages openSUSE-11.0: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-03-27 13:50:16 reject reason: Not enough time to look into this. Priority Requester: Important openSUSE-11.1: Rejected by Federico Lucifredi (flucifredi) reject date: 2008-08-01 18:27:34 reject reason: Cutting scope to match project schedule. Priority Requester: Important Projectmanager: Important openSUSE-11.2: Rejected by Stephan Kulow (coolo) reject date: 2009-04-16 13:39:02 reject reason: Out of agreed focus for 11.2 development Priority Requester: Important + openSUSE-11.3: New + Priority + Requester: Important Requested by: Cristian Rodríguez (elvigia) Description: currenly when you install a package with zypper, you just get the packages that are going to be installed, regardless if the are required or Reccommended,.. will be nice if the messages can be arranged to be more explict about what the package manager is doing. "The following NEW [required|reccomended] package is going to be installed: foo" also an informative message about Suggested packages should be shown "The following package(s) is(are) suggested but are not going to be installed foo bar " unless user pass --install-suggested or use a boolean configuration directive on zypp.conf or something, suggested packages should not be installed by default ..currently it seems to be completely ignored and does nothing. -- openSUSE Feature: https://features.opensuse.org/303493

1 0

[openFate 305735] Correctly detect keyboard model on laptops
by fate_noreply＠suse.de 08 Jun '09

08 Jun '09

Feature added by: Vincent Untz (vuntz) Feature #305735, revision 1, last change by Title: Correctly detect keyboard model on laptops openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Vincent Untz (vuntz) Partner organization: openSUSE.org Description: The default configuration of X always gives you a keyboard using the microsoftpro model. However, on laptops, it'd be better to actually use the model of this laptop -- it's certainly possible to have a script to detect this. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305735

1 5

[openFATE 305301] Central Regulatory Domain Agent (for 802.11)
by fate_noreply＠suse.de 08 Jun '09

08 Jun '09

Feature changed by: Marius Tomaschewski (mtomaschewski) Feature #305301, revision 15 Title: Central Regulatory Domain Agent (for 802.11) openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Helmut Schaa (hschaa) Description: The regulatroy domain handling for wireless cards was done by each driver seperately before mac80211/cfg80211. cfg80211 is used to unify the handling of regulatory domains for wireless devices. However cfg80211 depends on the user space configuring the regulatory domain. A user space daemon is currently developed (see [1]). It basically provides the allowed channels for all known regulatory domains. Additionally it would be nice to allow the configuration of the regulatory domain from the Yast network module. [1] http://wireless.kernel.org/en/developers/Regulatory/CRDA Partly based on bnc#392853 Discussion: #1: Helmut Schaa (hschaa) (2009-02-03 12:04:57) I've already packaged crda and wireless-regdb in my buildservice project home:hschaa:CRDA. #2: Helmut Schaa (hschaa) (2009-02-09 11:37:20) What we additionally need for this feature is some integration with Yast or NetworkManager such that the user is able to set the regulatory domain (maybe based on the selected time zone). A command line tool for setting the domain is already available (iw) but needs to be updated. #3: Helmut Schaa (hschaa) (2009-02-09 16:09:28) (reply to #2) Just submitted an update for Factory. #4: Helmut Schaa (hschaa) (2009-02-10 10:59:40) (reply to #2) wpa_supplicant 0.6.7 already has support for setting the regulatory domain. We'll get that with the next version update. #5: Helmut Schaa (hschaa) (2009-02-10 13:40:25) (reply to #2) iw, crda and wireless-regdb are part of factory now #6: Kshitij Kulshreshtha (polyconvex) (2009-03-25 11:53:33) Sometimes on a short visit abroad a user might not bother to update their timezone information on their laptop but still want to use a wireless network. In this case setting the regulatory domain based on timezone is not the right thing to do. Why not let the networkmanager applet ask the user himself to provide the country as a part of the dialog to setup the network? (A map similar to the yast timezone selector built into KNetworkManager?) + #7: Marius Tomaschewski (mtomaschewski) (2009-06-08 11:27:49) + We've already another enhancement bugs for sysconfig/wireless... so + let's just add it for 11.2. + Helmut, let's speak in the next days about the requirements on the + sysconfig side (I guess it is just one optional variable) and add this + together with the another enhancements. Michal (yast2 network) requires + the sysconfig support to implement it on the yast2 side. -- openSUSE Feature: https://features.opensuse.org/305301

1 0

[openFATE 306428] Reduction and management of the proxy users in a OES deployment
by fate_noreply＠suse.de 08 Jun '09

08 Jun '09

Feature added by: Haripriya Srinivasaraghavan (sharipriya) Feature #306428, revision 1, last change by Title: Reduction and management of the proxy users in a OES deployment Requested by: Haripriya Srinivasaraghavan (sharipriya) Description: ECO for: 1) A proxy user screen at the beginning of OES installation, where the following fields would be present * A proxy user input field which is auto-populated with a proxy user from the relevant scope - this could be a name of the user if already existing, or the name of a new user to create. The name entered in this field will become the default “OES proxy user” for all the services on that server. * A proxy user password field which will be filled by the install user. * A radio button which allows the administrator to select creation of proxy users at any of various levels/scope– * one proxy user per service per server * one proxy user per server (Default) * one proxy user per partition * one proxy user per tree * For all the services using proxy user, the proxy user and password fields will be auto-populated. The services will add the required rights or policies to this proxy user. * Based on the granularity of proxy users, this utility will allow the administrator to reset the proxy user passwords of the proxy user for all the services on a given OES box. 2) A utility to change all the proxy user passwords with one command. -- openSUSE Feature: https://features.opensuse.org/306428

1 7

[openFATE 306403] KOffice 2.1 in 11.2
by fate_noreply＠suse.de 08 Jun '09

08 Jun '09

Feature changed by: Stephan Binner (Beineri) Feature #306403, revision 7 Title: KOffice 2.1 in 11.2 openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Jean Cayron (jeancayron) Developer: Stephan Binner (beineri) Description: KOffice 2.1 will be released in november 2009, at the same time than openSUSE 11.2 ( see release plan (http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.1/Release_Plan) ). Since the 2.0 will not be feature complete, it would be great for KDE4 integration to have the latest version on the official repositories (maybe do as Firefox the RC with later update). Let make the people choose their Office Suite. Discussion: #1: Ricardo Gabriel Berlasso (rgbsuse) (2009-06-05 23:44:24) Another possibility is to implement a dedicated repository for koffice, in the same way we now have the repository for OOo. + #2: Stephan Binner (beineri) (2009-06-08 09:00:58) (reply to #1) + The usual KDE:Backports repository should be sufficient. -- openSUSE Feature: https://features.opensuse.org/306403

1 0

[openFATE 306411] Configuration files merge
by fate_noreply＠suse.de 07 Jun '09

07 Jun '09

Feature changed by: Gerald Pfeifer (GeraldPfeifer) Feature #306411, revision 7 Title: Configuration files merge - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Desirable Requested by: Michal Hrusecky (-miska-) Description: If we want to make our distribution friendly even to advanced users, I think that we shouldn't touch users configuration files. Luckily this isn't problem as in spec file Ican state that this file is configuration and I don't want to replace it if user did some manual changes. Or I can say that I want to replace it and keep backup of original one. But what I'm missing is some tool to easily merge these files. In Gentoo there is etc-update (http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=4#doc_…) or dispatch-conf (http://en.gentoo-wiki.com/wiki/Dispatch-conf) . I'll describe more precisely what feature I'm missing and why I think it's needed. Let's say that I've got some package and there was quite big change in package default configuration file which will affect most of the users. On the other hand users can have pretty complicated constructions in their configuration files and if they did something like that, it's quite possible that they don't need to update their configuration file. So it is needed to tell users that if they are experiencing problems it is most likely because they touched default configuration. I can take care of it manually, mention it in various README and such, but more easier way would be following. User installs some packages. At the end of zypper or yast installation there will be warning "You've got 42 configuration files to merge, please run etc-update/dispatch-conf/whatever". Then user will run some easy interactive tool which will state which configuration files can use some manual merging, it will allow user to see difference between them and let him choose which one he wants or let him merge them manually somehow. Same warning about unmerged configuration files should appear each time user installs something, no matter if this installation didn't add any conflict, until all conflicts are fixed. User will be warned about possible problems, hacker can play with it and keep his changes against distribution defaults and ordinary user will just click on "use distribution default for all" if he ever encounter such a problem (shouldn't happen as ordinary user wouldn't touch configuration files). I explained basic expected work flow, so now what I think should be supported: * detect configuration files, their conflicts and allow their merge - this shouldn't be a big problem as rpm already stores conflicting files as .rpmnew/.rpmold * we probably want to keep even old versions to support three way merge to achieve even better results * if we are already storing these configuration files, maybe we should let users to backup their own changes as well, add support for versioning these configuration files * warn user that he has conflicts in configuration files - will require a little bit yast/zypper integration * merging tool should support both console and graphical interface (maybe use yast as possible frontend) * support for various formats (expandable by plugins) - ordinary diff may not be the best tool for merging XML files or ini files * ordinary user who don't change anything shouldn't need to know about this tool Relations: - Debian-like dist-upgrade live system full version upgrade (feature/id: 305634) Discussion: #1: Michal Hrusecky (-miska-) (2009-06-02 09:49:38) I was thinking about this a little bit more and if we want to support some kind of versioning and we want to use plugins for getting differences, it may be a good idea to request that plugins will be capable not only of producing nice output of difference between configuration files, but it probably should be able to apply it (behave not only as a 'diff', but also as a 'patch'). And we can build some simple version control system on top of it. Advantages: * can handle non-plain text files better (via plugins) * we can implement feature to discard or merge several commits into one to save space/make commit log more readable * can handle nicelly even insane configuration files like sqlite database or compressed directory with configuration files or any other binary format Disadvantages: * probably worse handling of text files * another thing to maintain/possible source of bugs -- openSUSE Feature: https://features.opensuse.org/306411

1 0

[openFATE 306467] Sorting order within a session is not persistent
by fate_noreply＠suse.de 07 Jun '09

07 Jun '09

Feature added by: Dirk Hessing (dihess) Feature #306467, revision 1, last change by Title: Sorting order within a session is not persistent openFATE: New Priority Requester: Desirable Requested by: Dirk Hessing (dihess) Description: This issue was reported by a Novell partner: In PartnerFATE they chose alphabetic sorting order for the list of FATE entries. After editing a FATE entry and moving back (to the list of FATE entries, sorting order is not longer alphabetical. This should be fixed - sorting order should be persistent within a sessio Test Case: enter partnerFATE -> chose alphabetic sorting order for FATE list -> edit a FATE entry -> go back in browser to FATE list and verify sorting order -- openSUSE Feature: https://features.opensuse.org/306467

1 1

[openFATE 305294] Support Rotation hotkey in tablets (RANDR 1.2)
by fate_noreply＠suse.de 06 Jun '09

06 Jun '09

Feature changed by: Stefan Dirsch (sndirsch) Feature #305294, revision 10 Title: Support Rotation hotkey in tablets (RANDR 1.2) openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Federico Mena Quintero (federico-mena) Description: Tablet notebooks (especially the fancy new ones with Wacom pressure- sensitive screens) have a physical button to rotate the screen, in case you want to hold the tablet in portrait/landscape mode. We need to capture the XF86RotateWindows keysym, and rotate the laptop's display. Discussion: #1: Federico Mena Quintero (federico-mena) (2008-09-12 13:32:48) I just started a wiki page to track the status of support for laptops/tablets with these hotkeys: http://en.opensuse.org/Laptop_hotkeys_for_RANDR #2: Stefan Dirsch (sndirsch) (2009-04-15 17:16:00) Don't know how I can help here. + #3: Stefan Dirsch (sndirsch) (2009-06-06 12:36:15) + This is more for the RANDR >= 1.2 tool developers I would say. -- openSUSE Feature: https://features.opensuse.org/305294

1 0

[openFATE 306403] KOffice 2.1 in 11.2
by fate_noreply＠suse.de 05 Jun '09

05 Jun '09

Feature changed by: Ricardo Gabriel Berlasso (RGBsuse) Feature #306403, revision 6 Title: KOffice 2.1 in 11.2 openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Jean Cayron (jeancayron) Developer: Stephan Binner (beineri) Description: KOffice 2.1 will be released in november 2009, at the same time than openSUSE 11.2 ( see release plan (http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.1/Release_Plan) ). Since the 2.0 will not be feature complete, it would be great for KDE4 integration to have the latest version on the official repositories (maybe do as Firefox the RC with later update). Let make the people choose their Office Suite. + Discussion: + #1: Ricardo Gabriel Berlasso (rgbsuse) (2009-06-05 23:44:24) + Another possibility is to implement a dedicated repository for koffice, + in the same way we now have the repository for OOo. -- openSUSE Feature: https://features.opensuse.org/306403

1 0