December 2010 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310100] YaST Software Manager - Installation after download
by fate_noreply＠suse.de 18 Dec '16

18 Dec '16

Feature added by: Muhammad Javaid (BrownieCat) Feature #310100, revision 1 Title: YaST Software Manager - Installation after download openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Muhammad Javaid (browniecat) Description: Once a package install/system update has begun in Software Manager it's not very easy to stop it. The 'Abort' button doesn't really seem to work and if you force kill the process, you likely end up with broken packages. It would be nice if first all the packages were downloaded, and then installed (like it is in Ubuntu), rather than the sequence of: Download Package 1, install package 1, download package 2, install package 2 and so on. That way the installation could be aborted safely during the downloading part with no fear of broken packages. -- openSUSE Feature: https://features.opensuse.org/310100

1 4

[New: openFATE 310888] We fail at...
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: tys lefering (twlevo) Feature #310888, revision 1 Title: We fail at... openSUSE.org: Unconfirmed Priority Requester: Desirable Requested by: tys lefering (twlevo) Partner organization: openSUSE.org Description: the 'startx twm' should start twm window manager but that does not work for years and needs hacking scripts to use it. twm is used to run 1 graphic program with lower mem+cpu usage during tests. -- openSUSE Feature: https://features.opensuse.org/310888

1 2

[New: openFATE 310658] bypass "partitioning" option for pre-partitioned installation targets
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Felix Miata (mrmazda) Feature #310658, revision 1 Title: bypass "partitioning" option for pre-partitioned installation targets openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Felix Miata (mrmazda) Description: Mandriva provides installation cmdline option that I always use: readonly=1 This causes normal partitioning steps to be bypassed. No creatiion, deletion, or modification of existing partitions is possible. Instead is presented a list of Linux native partitions for mountpoint selection, mount options selection, whether to format, and format to use. This is handy for both advanced users like myself, and for frequently repeated installs, such as development milestones. It can save significant time initializing an installation, and it can avoid some opportunities for mistakes in one of the more dangerous and difficult installation phases. It would be excellent for openSUSE to have a similar installation option. -- openSUSE Feature: https://features.opensuse.org/310658

1 2

[New: openFATE 308343] external screen detection
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: marco mendoza (marcomendoza) Feature #308343, revision 1 Title: external screen detection Package Wishlist: Unconfirmed Priority Requester: Important Requested by: marco mendoza (marcomendoza) Description: Dear Suse comunity, Im proud to say Im getting involved into the Suse world, and even though Im a simple user of the OS systems, I found essential to have a performing OS in order to perform my current work. Whereas I got in love to Opensuse (I did start with it wo knowing anything...ubuntu or Suse...I have taken Suse and Im loving it), there is a couple of current options from comercial OS systems that I feel it is missing even in the last version of Opensuse. Particulary I would like to suggest the necessity of having an external screen detection system, I heart that some people manages to do it manually, but I think that such functionality should be part of an OS at the level of Opensuse. I have in in mind other couple of whishes, I will come with them in a following post in case my suggestions are taken in consideration. Thanks for commenting on this idea and the feasibility of it. greetings Marco A. -- openSUSE Feature: https://features.opensuse.org/308343

1 7

[New: openFATE 310236] KDE-metapackages for avoid mixing packages versions from different repos
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Alex Savin (alexqwesa) Feature #310236, revision 1 Title: KDE-metapackages for avoid mixing packages versions from different repos openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Alex Savin (alexqwesa) Description: KDE have many repos and often user get mismatch of packages versions and various strange bugs due this. create KDE-metapackages for avoid mixing packages versions from different repos -- openSUSE Feature: https://features.opensuse.org/310236

1 1

[openFATE 308138] Easy way to install corresponding debuginfo RPM for all existing packages
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Silviu Marin-Caea (silviumc) Feature #308138, revision 1 Title: Easy way to install corresponding debuginfo RPM for all existing packages openFATE: Unconfirmed Priority Requester: Important Requested by: Silviu Marin-Caea (silviumc) Partner organization: openSUSE.org Description: KDE4 applications crash more often than they should. The bugreporting helper that pops up is not user friendly. It expects the user to know what particular debuginfo RPMs to install in order to get a useful bug report. It also expects the user to toil through a long "wizard" that asks a lot of questions. It's not cool to punish the user on top of an application crash. Does KDE hate us or what? The user shouldn't have to do anything more than giving the accept to send the crash information or not. Examples: Firefox, Windows. If KDE couldn't come up with something easier than this, at least SUSE should do something to work around it. My suggestion would be a way to install all debuginfo RPMs for every package that's already installed. This way, all bugreports will be useful. Business case (Partner benefit): openSUSE.org: We want to get statistic data so we can focus on bugs that crash KDE applications -- openSUSE Feature: https://features.opensuse.org/308138

1 8

[New: openFATE 310431] Create automatic private group for new user
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Steven Bert (dodydog) Feature #310431, revision 1 Title: Create automatic private group for new user openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Steven Bert (dodydog) Description: In Yast user management, add an option in the new user dialog to have a new, private group created for the user. The group should be named as the user. The reason for this feature is to allow simple data sharing between users based on projects with a project group and a default umask giving read permisssions to group members (which is the default right now). The only measure to share a file with a project is to set group ownership to the appropriate group. As of now additional file permisssions would have to be changed. -- openSUSE Feature: https://features.opensuse.org/310431

1 2

[New: openFATE 310322] Install, uninstall and change desktop environments easier.
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: jpxviii jpxviii (jpxviii) Feature #310322, revision 1 Title: Install, uninstall and change desktop environments easier. Hackweek V: Unconfirmed Priority Requester: Important openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: jpxviii jpxviii (jpxviii) Description: Some people use and prefer a single desk and others prefer to use multiple. It would be good for non-technical users can make installations and removals of each desktop environments and change KDM - GDM - so easy. -- openSUSE Feature: https://features.opensuse.org/310322

1 3

[New: openFATE 309296] YaST2-Qt : Add "Action after Installation" option
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Rémy Marquis (Spyhawk) Feature #309296, revision 1 Title: YaST2-Qt : Add "Action after Installation" option openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Rémy Marquis (spyhawk) Description: YaST-Qt package manager module should have an additional option in Configuration menu, similarly to the ncurse version (yast sw_single > Configuration > Action after Package Installation). Use Case: * A user wants to change the default behavior, but doesn't know that he needs to change PKGMGR_ACTION_AT_EXIT in /etc/sysconfig/yast2 * A user that have used ncurse yast expects that this option is also in the Qt interface, -- openSUSE Feature: https://features.opensuse.org/309296

1 10

[New: openFATE 310604] Push repository Status to Users
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Tejas Guruswamy (MasterPatricko) Feature #310604, revision 1 Title: Push repository Status to Users Buildservice: Unconfirmed Priority Requester: Important openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Tejas Guruswamy (masterpatricko) Description: One of the major complaints from users of the OBS is that it is too hard to identify which package out of multiple available ones is the correct, "safe", one to install. Also repository changes have no way of being noticed except with zypp refreshes suddenly start failing. The OBS provides an amazing, amazing service but still little complications arise; repositories disappear, change content, etc. Three parts would need to be implemented: 1) A "status" or "stability" attribute for all repositories on the OBS. It could have values like * UNSTABLE - This repository contains unreleased software / alpha-quality, possibly direct from source control. Bugs are to be expected. (e.g. KDE:Unstable:Distro ) * FACTORY (or LATEST?) - This repository contains the latest released software from this upstream project, to be submitted to openSUSE Factory. Bugs are possible, please report them. (e.g. KDE:Distro:Factory) * STABLE - This repository contains software as it was in the last stable release of openSUSE, possibly with some additional bugfixes. Bugs should be infrequent. (e.g. KDE:Distro:Stable) * HOME(?) - This repository is someone's Home project. Packages may be added and removed at any time. (maybe not necessary) * VERSION(?) - This repository contains a snapshot of a specific released version of this software. (maybe not necessary) (e.g. KDE:SC:45) I know the OBS supports attributes, so maybe that infrastructure can be used. The current solution of trying to explain it in the repository name is not sufficient as people have conflicting ideas of what "Factory" means, etc. With the explanations side-by-side, there can be no confusion. What would need to be added is * integration with software.opensuse.org and webpin - so repository state is clearly visible in search results, with the explanations of each state also visible on the same page. * integration with Yast2/zypper - in the repository configuration, the repository state should be shown (does it need to be updated every so often? will repositories ever change their state?) 2) A NEWS/ChangeLog file/attribute for every repository on the OBS. This allows the repository owner/maintainer to communicate with the users letting them know of important changes that affect them. This would be downloaded with the repository metadata. This would need to be integrated into: * OBS - easy way to edit this file should be possible (maybe it can be based on the repository description?) * Yast2/zypper/updateapplet - when refreshing a repository, if a changed NEWS is detected, inform the user. something like > zypper ref Repository "foobar" has updated its NEWS file. [Read/Ignore/Skip]: where you can choose to read the changes now, leave it till next time, or ignore it completely. Currently the build service project page is the only place where such information is put, but users never read that. Otherwise you have to resort to the mailing lists, but most users aren't subscribed there until they have a problem. The NEWS file would be used to pass on information including: * Significant changes to the purpose or content of the repository (e.g. KDE:Distro:Factory switching from KDE SC 4.5 to 4.6) * Repository renames, obsoletions, deletions (e.g. KDE:KDE4:Community -> KDE:Extra) Obviously this can't be done too frequently as it would annoy the user, but it is clear that there needs to be some communications channel to let them know what's going on. 3) Improved software search - software.opensuse.org and webpin could become a lot more new-user friendly. Some of my suggestions * Exclude HOME and UNSTABLE projects * Exclude debuginfo and debugsource packages by default * Exclude devel packages by default * Default to only searching for the current, released version of openSUSE. * Display repository status as detailed above I think this could make an absolutely huge difference to how users use the OBS, and most of all, make it a lot more safe - reducing complaints. I know that repository stability attributes have been mentioned by many people many times - but now the infrastructure is there - lets take it one step further... (BTW Forgive my KDE examples, it's just what I am familiar with) -- openSUSE Feature: https://features.opensuse.org/310604

1 7