March 2012 - openSUSE Features - openSUSE Mailing Lists

[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 313205] Restrict to whole-line comments in CodeMirror spec syntax
by fate_noreply＠suse.de 19 Apr '12

19 Apr '12

Feature added by: Christopher Yeleighton (yecril71pl) Feature #313205, revision 1 Title: Restrict to whole-line comments in CodeMirror spec syntax Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Christopher Yeleighton (yecril71pl) Partner organization: openSUSE.org Description: When you edit an RPM spec (http://rpm.org/) file, the CodeMirror engine (https://static.opensuse.org/hosts/build2.o.o/javascripts/cm2/mode/spec.js?1…) interprets the hash mark (#) as starting a comment and greys out the trailing part of the line. This should happen only when the line starts with the hash mark (#) when trimmed. Test Case: %{lua:print(#"");} Use Case: The hash mark is the length operator in lua (http://rpm.org/wiki/PackagerDocs/RpmLua) . Business case (Partner benefit): openSUSE.org: Even if trailing comments in RPM spec (http://rpm.org/) were supported, their use should be discouraged. -- openSUSE Feature: https://features.opensuse.org/313205

1 2

[New: openFATE 313109] improve http://software.opensuse.org/search, group results, search for content
by fate_noreply＠suse.de 18 Apr '12

18 Apr '12

Feature added by: Joerg Steffens (steffens) Feature #313109, revision 1 Title: improve http://software.opensuse.org/search, group results, search for content openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Joerg Steffens (steffens) Partner organization: openSUSE.org Description: openSUSE ist a good distribution and the openSUSE Build Service is a fantastic tool to build packages for it. However, this solutions would be far more effient, if all the available packages can be found easily. The interface through http://software.opensuse.org/search needs improvment. E.g. searching for libreoffice for openSUSE-12.1 results in more than 80 pages (!), because the search function returns not only the package "libreoffice" but also all packages that contain "libreoffice" as a substring of there name. All found packages are displayed with full information, like repository, package namem package version, description, manual download of i586, x86_64, src, 1-click install, link to OBS Improvements: - optional: distinguish between basic and advanced search - in advanced search - by default, only return exact matches - allow regex based searches (or at least wildcards) - most important: group the search results: * package name * version: repository, more info (OBS, 1-Click install, ...) E.g. * libreoffice * 3.4.2.6-4.2.2 openSUSE:12.1/standard * 3.4.4.3-2.1 LibreOffice:Stable/openSUSE_Tumbleweed * ... * libreoffice-base-drivers-mysql * 3.4.2.6-4.2.2 openSUSE:12.1/standard * 3.4.4.3-2.1 LibreOffice:Stable/openSUSE_Tumbleweed * 3.4.4.3-84.1 LibreOffice:Unstable/openSUSE_12.1 * ... * ... because normaly I'm interessted in installing a package and therefore finding the best repository to add (LibreOffice:Stable sounbd more suitable than LibreOffice:Unstable or home:mytest) I also always liked the package search from Debian http://www.debian.org/distrib/packages, where it is easily possible to search for the content of packages. SUSEs approach to this has always been limited and the search from http://packages.opensuse-community.org/ (webpin) is out of order. The "official" site http://search.opensuse.org/packages/ results in an internal server error. Even as this has worked, some month ago, you had to know the full path of the file you are looking for. A package content based search over the full openSUSE reposiory would be a real benifit that makes ot a lot easier to use OBS in all its power. -- openSUSE Feature: https://features.opensuse.org/313109

1 3

[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

[New: openFATE 309852] improve spec file editor in buildservice
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Michal Seben (mseben) Feature #309852, revision 1 Title: improve spec file editor in buildservice Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Michal Seben (mseben) Description: if you try to edit spec file in buildservice you get clean,not highlighted text, it would be fine if we have spec editor build in (with auto-completion and syntax higlight) maybe we could use codemirror : http://marijn.haverbeke.nl/codemirror/jstest.html (http://marijn.haverbeke.nl/codemirror/jstest.html) ? -- openSUSE Feature: https://features.opensuse.org/309852

1 9

[New: openFATE 311187] Anonymous source package download from web interface using disturl
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Ciaran Farrell (babelworx) Feature #311187, revision 1 Title: Anonymous source package download from web interface using disturl Buildservice: Unconfirmed Priority Requester: Important Requested by: Ciaran Farrell (babelworx) Partner organization: openSUSE.org Description: Using the disturl tag of our rpm package it is possible to find out exactly where the corresponding source for the binary rpm is located. For example, using osc: osc co -r <HASH> <project> <package> will download the exact source code for the binary rpm. However, to use osc a novell.com/buildservice account is necessary. Suggested is a corresponding web interface feature where even anonymous users can download the exact corresponding source to a binary rpm. Business case (Partner benefit): openSUSE.org: To make it easy for anyone with a rpm to quickly and easily download the exact corresponding source code -- openSUSE Feature: https://features.opensuse.org/311187

1 2

[New: openFATE 312279] OBS issuetracker integration
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Bernhard Wiedemann (bmwiedemann) Feature #312279, revision 1 Title: OBS issuetracker integration Buildservice: Unconfirmed Priority Requester: Important Requested by: Bernhard Wiedemann (bmwiedemann) Partner organization: openSUSE.org Description: build.opensuse.org webui should display hyperlinks to issue-trackers when seeing e.g. bnc#654321 or fate#345678 mentioned in commit messages. This allows for easier review of submit-requests. There are probably other places/clients where such links can be useful. -- openSUSE Feature: https://features.opensuse.org/312279

1 2