July 2011 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310380] grub2 bootonce or bootnext command
by fate_noreply＠suse.de 09 May '12

09 May '12

Feature added by: Lee Matheson (oldcpu) Feature #310380, revision 1 Title: grub2 bootonce or bootnext command openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Lee Matheson (oldcpu) Description:  With the possibility of Grub2 being implemented soon as a default boot manager, it would be useful to add to the Grub2 packaging a small script that fully emulates the older grubonce that is provided with openSUSE-11.3 and earlier. The philosophy is from run level 3, or from a desktop that does not support the capability to selectively reboot ONCE (and only ONCE) into another boot partition, one can run a command that allows this one time reboot functionality. This was achieved with the "grubonce" command on openSUSE-11.3 (and earlier) and other distributions (for the older grub version) used perl scripts such as bootnext (on Fedora: http://www.dcheng.members.sonic.net/friends/jspaar/pub/bootnext/ ). There is an example here on openSUSE forums as to the utility of the grubonce command and how it can be applied: http://forums.opensuse.org/english/information-new-users/unreviewed-how-faq… The grub2-reboot command is lacking (in comparison to grubonce) in that it appears it can not be used to generate the re-boot selection menu. Hence I propose a small script/application be provided with openSUSE-11.4 (or 12.0) that functions similar to the scripts proposed in http://forums.opensuse.org/english/information-new-users/unreviewed-how-faq… or as a minium functions with the full capability of the "grubonce" (which grub2-reboot lacks). -- openSUSE Feature: https://features.opensuse.org/310380

1 1

[openFATE 306928] Better integration of YaST webpin client into openSUSE
by fate_noreply＠suse.de 09 May '12

09 May '12

Feature added by: Katarina Machalkova (kmachalkova) Feature #306928, revision 1 Title: Better integration of YaST webpin client into openSUSE Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Katarina Machalkova (kmachalkova) Description: <p><a href="http://hedgehogpainter.livejournal.com/#asset-hedgehogpainter-4686">YaST webpin client</a> is done and usable since quite some time already, yet its integration into platform is far from being smooth. openSUSE users have very few chances to learn about it in order to use it. This feature consists of two parts:<ul> <li> Webpin search client will be accessible and launchable from menu entry, added to Qt/Gtk/Ncurses package selectors </li><li> New package yast2-packager-webpin will be splitted off yast2-packager, containing webpin module, client + additional .desktop file </li></ul>The purpose of the latter is not to clutter YaST control centre with too many icons, installed along with yast2-packager (which is in default installation). This way, user will get extra icon only if yast2-packager-webpin</p> -- openSUSE Feature: https://features.opensuse.org/306928

1 5

[openFATE 306624] voting mechanism for membership approval on users.o.o
by fate_noreply＠suse.de 08 May '12

08 May '12

Feature added by: Hendrik Vogelsang (hennevogel) Feature #306624, revision 1 Title: voting mechanism for membership approval on users.o.o Hackweek IV: Unconfirmed Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: To be better able to vote on membership approvals the openSUSE board is looking for some ruby hacker willing to implement a voting mechanism in users.opensuse.org. users.o.o is a ruby on rails application. Pepple that want to become openSUSE members fill out an application form in users.o.o. This is then evaluated by the openSUSE board. Each application is voted upon. What is missing in users.o.o is the possiblity to vote on those applications. This would need a couple of things: Each application needs a state attribute with the following content: * New * To be Accepted * Accepted * To be Rejected * Rejected Also the respective listings in the interface are needed. And for each board member an voting field. (+1,0,-1) coupled with a free text field. -- openSUSE Feature: https://features.opensuse.org/306624

1 3

[openFATE 307436] Backup utility
by fate_noreply＠suse.de 07 May '12

07 May '12

Feature added by: Alin M Elena (ealin) Feature #307436, revision 1 Title: Backup utility openFATE: Unconfirmed Priority Requester: Desirable Requested by: Alin M Elena (ealin) Description: Hi, Would be nice if we can have an user backup application by default in kde4. I propose back-in-time http://backintime.le-web.org/ it has both kde4 and gnome interfaces and is relatively simple to use. regards, Alin -- openSUSE Feature: https://features.opensuse.org/307436

1 4

[New: openFATE 309311] GUI for PAM
by fate_noreply＠suse.de 04 May '12

04 May '12

Feature added by: The Liberator (L1B3RAT0R) Feature #309311, revision 1 Title: GUI for PAM openFATE: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Package Wishlist: Unconfirmed Priority Requester: Important Requested by: The Liberator (l1b3rat0r) Description: I would like to see some kind of YAST-like tool for implementing PAM features for all types of logins. As it is now you can attempt unlimited logins via the terminal or a locked KDE screen. If there was a GUI for PAM that allowed the user to set maximum password tries, time-frames that login is allowed, and how long a session can last, then our computers would be much more secure. I have an encrypted hard drive, but once the computer is booted up and the hard drive is decrypted, I have no way of stopping a brute force attack. For the average user, PAM is too complicated to use all its features without reading for hours. This seems like the perfect feature to add to YAST. -- openSUSE Feature: https://features.opensuse.org/309311

1 3

[New: openFATE 309577] auto remove unused dependencies using YaST and zypper
by fate_noreply＠suse.de 26 Apr '12

26 Apr '12

Feature added by: double chou (MargueriteSu) Feature #309577, revision 1 Title: auto remove unused dependencies using YaST and zypper openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: double chou (margueritesu) Description: in Debian, you can apt-get --autoremove if you uninstall a package. in Fedora, you can also find such feature. but YaST, nope, I can't. YaST only automatically install dependencies needed by packages you wanna install, but It does not automatically remove them. So after you tried lots of software to find your need. Your system will be huge and full of useless dependencies. That might cause disk over-usage or security problems. 'Coz users only do system update in the way "zypper dup" instead of " zypper update", so obselete packages that have bugs remain. Nowadays I have to write down dependencies mannually everytime I install softwares. That's boring. -- openSUSE Feature: https://features.opensuse.org/309577

1 4

[New: openFATE 310986] Software Search to arrive at most desirable options
by fate_noreply＠suse.de 18 Apr '12

18 Apr '12

Feature added by: Carl Fletcher (caf4926) Feature #310986, revision 1 Title: Software Search to arrive at most desirable options openFATE: Unconfirmed Priority Requester: Important Requested by: Carl Fletcher (caf4926) Partner organization: openSUSE.org Description: Currently the Software Search and or Webpin results in a plethora of choices, most of which are less than desirable. Ideally, search results should First offer the most stable and or suitable packages. For example. If a user comes along and searches for 'VLC' They are offered a host of unstable options. Everyone knows that 'VLC' should come from Packman. If we can't refer directly to Packman, it should be possible to link to a multi-media giuide. I'm going to guess this could be difficult. But it must be possible to flag searches by keywords to redirect to the most likely solution, but with an option to continue to search anyway. Test Case: Open here: http://software.opensuse.org/search and search: vlc Business case (Partner benefit): openSUSE.org: Avoid new user use of unstable or unsuitable repos. We should be directing to the most suitable or most likely suitable solution. At the moment it's very random. -- openSUSE Feature: https://features.opensuse.org/310986

1 14

[openFATE 305881] Add a simple way to access the rpmlint report
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Vincent Untz (vuntz) Feature #305881, revision 1, last change by Title: Add a simple way to access the rpmlint report Buildservice: Unconfirmed Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: Right now, to see the rpmlint report of a build, you have to get the complete build log, which can be slow (because it's big). Having a faster way to read the rpmlint report could result in some tools to highlight what should be fixed, and therefore in better packages. -- openSUSE Feature: https://features.opensuse.org/305881

1 6

[openFATE 307621] Provide public interface to submit patchinfos
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Dirk Mueller (dirkmueller) Feature #307621, revision 1 Title: Provide public interface to submit patchinfos Buildservice: New Priority Requester: Mandatory Requested by: Dirk Mueller (dirkmueller) Partner organization: openSUSE.org Description: For openSUSE 11.2 it should be possible for external community members to submit maintenance updates. It is already possible to submit the changed packages itself, however the patchinfo file can not be submitted by external members. The feature would be to allow to attach the information needed for a patchinfo file (maybe except for a swampid) to be submitted by an external community member. One possible implementation method would be a new submitrequest type in the buildservice API. Business case (Partner benefit): openSUSE.org: Make use of community members for providing updates -- openSUSE Feature: https://features.opensuse.org/307621

1 3

[openFATE 306849] Drop requests comment have to be public/archived
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Stephan Binner (Beineri) Feature #306849, revision 1 Title: Drop requests comment have to be public/archived Buildservice: Unconfirmed Priority Requester: Mandatory Requested by: Stephan Binner (beineri) Description: Comments of accepted drop requests should appear in opensuse-commit mails which inform about the package being dropped. -- openSUSE Feature: https://features.opensuse.org/306849

1 4