March 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 313233] Get Zypper to remove installed patterns
by fate_noreply＠suse.de 15 Jan '16

15 Jan '16

Feature added by: Drew Adams (Druonysus) Feature #313233, revision 1 Title: Get Zypper to remove installed patterns openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Drew Adams (druonysus) Partner organization: openSUSE.org Description: Get Zypper to remove a pattern. Zypper can install a pattern nut when going to remove that same pattern, Zypper does not remove that pattern... When do a: "zypper rm -t pattern <pattern name>" Zypper, just tells you: "Uninstallation of a pattern is currently not defined and implemented." You CAN remove a pattern in YaST so I would think that there should be a way to remove the pattern with Zypper. "yum groupremove <group name>" works on Fedora/CentOS/RHEL... we should really have this working to keep up with them. Use Case: If I build a bare openSUSE image on SUSE Studio, and I decide not to install yast and only Zypper... I will only be able to install patterns but NO way to remove it. -- openSUSE Feature: https://features.opensuse.org/313233

1 2

[New: openFATE 312293] Option to disable disk check on certian volumes in YaST
by fate_noreply＠suse.de 04 Jan '16

04 Jan '16

Feature added by: Dean Hilkewich (deanjo13) Feature #312293, revision 1 Title: Option to disable disk check on certian volumes in YaST openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Dean Hilkewich (deanjo13) Partner organization: openSUSE.org Description: This is one really really really annoying feature in yast. Here is the scenario, you have a machine with a bunch of storage drives, drives that are normally kept full. Everytime you enter something like package management in YaST it pops up a low disk space warning. This warning should only apply for volumes where YaST utilizes for it's files (such as download cache, home, etc). A HTPC for example often has volumes full to the max. -- openSUSE Feature: https://features.opensuse.org/312293

1 1

[New: openFATE 318082] [Shell][Scripting] Shell-reqs command
by fate_noreply＠suse.de 19 Dec '15

19 Dec '15

Feature added by: Sławomir Lach (Lachu) Feature #318082, revision 1 Title: [Shell][Scripting] Shell-reqs command openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Idea is about creating tool, which checks that given programs are installed. If some program aren't installed then it call special program(dependent on user is working on console and GUI environment), which displays cnf output for missing programs. On program missing return code is not 0, so script can terminate. Idea was proposed by some Red Hat's developers many years ago, but this idea was about to automatically install tools from standard repositories. Use Case: Marek is normal computer user. He decided to download script, but to run correctly script needs some command. This script can looks like this: #!/bin/bash shell-reqs command1 command2 if [ $? -eq 1 ]; then exit fi; command1 parameter1 parameter2 command2 parameter1 parameter2 parameter3 When he run this script, desktop environment reports that command1 and command2 is missing and suggest how to install these commands. Marek will install these commands and rerun script. -- openSUSE Feature: https://features.opensuse.org/318082

1 2

[openFATE 305914] PAC support for 'system wide proxy configuration'
by fate_noreply＠suse.de 05 Dec '15

05 Dec '15

Feature added by: Dominique Leuenberger (dimstar) Feature #305914, revision 1, last change by Title: PAC support for 'system wide proxy configuration' openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Dominique Leuenberger (dimstar) Description: The distribution now contains libproxy and we should try to make as much use of it as possible. A big advantage is the ability to parse PAC (Proxy AutoConfiguration) without the need for this in every application. Simply linking against libproxy with it's very simple API (3 API calls, 2 without parameters) is enugh to have the advantage of no longer needing to 'guess' what proxy to use. What is now: - You can set in yast / proxy a general proxy to be used (http://foo.proxy.com:1234) This is bascially put into http_proxy envvar. In gnome you can set user proxy configuration as: - Use System Proxy (as configured in yast) - Use proxy configuration (static, same options as in yast) - Use automatic proxy configuration script Yast lacks the option to specify a PAC script on system wide level. This is only possible in the user sessions configuration. This made sense as most applications don't know how to handle pac files anyway. But with libroxy, this hurdle can be taken away from every single application and can thus be offered. I'm glad to elaborate on questions; I'm sure there are some :-) -- openSUSE Feature: https://features.opensuse.org/305914

1 17

[New: openFATE 318203] Let's drop commandline support from Yast
by fate_noreply＠suse.de 20 Nov '15

20 Nov '15

Feature added by: Lukas Ocilka (locilka) Feature #318203, revision 1 Title: Let's drop commandline support from Yast Requested by: Lukas Ocilka (locilka) Partner organization: openSUSE.org Description: Yast provides some kind of a commandline interface which is based on the same functions provided by standard Yast application (Qt, ncurses). Comandline could be used for scripting, but there are already tools that do it better: AutoYast, Chef, Puppet, SUSE Manager, sed (just to name some). Yast commadline has several drawbacks: * not used, not tested, not maintained, too much of obsolete code - too much maintenance for nothing * architecturally wrong - commandline interface to an app that uses commandline tools (e.g., commandline for Services Manager? This is obviously systemctl) * implemented as kind of a hack What do we lose if we remove it? * Possbility for scripting, but as Yast only builds on other cmdline tools or files, there are replacements Another possibility would be to replace commandline with a static information advicing user which tools to use to configure a particular service manually. Business case (Partner benefit): openSUSE.org: Less unused code to maintain == more time to do something that really matters -- openSUSE Feature: https://features.opensuse.org/318203

1 19

[New: openFATE 312747] Backport fix for Okular printing in KDE4 for KDE 4.7
by fate_noreply＠suse.de 18 Nov '15

18 Nov '15

Feature added by: Mindaugas Baranauskas (embar-) Feature #312747, revision 1 Title: Backport fix for Okular printing in KDE4 for KDE 4.7 openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Mindaugas Baranauskas (embar-) Partner organization: openSUSE.org Description: Please include this patch http://commits.kde.org/okular/e001fbab55aceef62ad9ca2bb87a170dacfe3fdd Kevin Kofler 2011-07-27 23:50:46 wrote: I forgot to put in a FIXED-IN tag, so let's make it clear: This fix will be in 4.8.0. 4.7.0 has already been released, and the fix requires new APIs in the Okular core, so I'm probably not supposed to backport it for 4.7.x. See https://bugs.kde.org/show_bug.cgi?id=181290#c118 -- openSUSE Feature: https://features.opensuse.org/312747

1 6

[New: openFATE 310712] Constantly usable Factory
by fate_noreply＠suse.de 18 Nov '15

18 Nov '15

Feature added by: Christoph Obexer (cobexer) Feature #310712, revision 1 Title: Constantly usable Factory openSUSE-11.4: Unconfirmed Priority Requester: Mandatory Requested by: Christoph Obexer (cobexer) Partner organization: openSUSE.org Description: I recently read about the Debain CUT project, ( http://cut.debian.net/ (http://cut.debian.net/) , http://kitenet.net/~joey/code/debian/cut/ (http://kitenet.net/~joey/code/debian/cut/) ) looking at the current situation with openSuSE Factory i see that it is dangerous to use, unstable alpha or beta packages come into Factory all the time, while other packages become out of date. The result is a system that is pretty much unusable. Only allowing stable packages to enter Factory would make that a lot better, and if one finds bugs chances are that those bugs aren't already fixed in a newer svn/git snapshot, but are real bugs. This would save a lot of time for testers and developers in dealing with "invalid", or "temporary" bugs. I think that a robust, "stable" Factory would lead to more people using it full time and thus a better quality of the next openSuSE version. I see that this would have negative aspects as well, but i think most devel projects have unstable/testing repositories set up already and those could still contain the snapshots of upcoming versions, testers of those specific projects could use tose repositories then. Doing a release of openSuSE would be easier then too, simply snapshot Factory, and declare it as openSuSE $VERSION. The transition from the current state to a "constantly usable Factory" would be smooth too. And it's also in line with the openSuSE vision, stable rather than bleeding edge. Business case (Partner benefit): openSUSE.org: More users using Factory -> better stability of Factory -> better stability of openSuSE $VERSION -> openSuSE back where it should be - the Linux for professionals. -- openSUSE Feature: https://features.opensuse.org/310712

1 4

[New: openFATE 309700] Advanced uninstall/Rollback support in package management, zypper
by fate_noreply＠suse.de 30 Oct '15

30 Oct '15

Feature added by: Nikanth K (nikanth) Feature #309700, revision 1 Title: Advanced uninstall/Rollback support in package management, zypper openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Nikanth K (nikanth) Description: # Zypper install evolution This will install say 13 packages, evolution and its dependencies including evolution-data-server etc.... #zypper remove evolution This will remove only evolution. Leaving the dependencies installed. The 12 packages are left installed. Instead provide an easy way to rollback/uninstall all those packages using say a transaction-id from the history. So that, say we have foo.rpm which needs bar.rpm #zypper install foo #zypper remove foo will not leave bar installed in the system. -- openSUSE Feature: https://features.opensuse.org/309700

1 4

[New: openFATE 309070] Allow auth
by fate_noreply＠suse.de 27 Oct '15

27 Oct '15

Feature added by: Adrian Schröter (adrianSuSE) Feature #309070, revision 1 Title: Allow auth Buildservice: Evaluation Priority Requester: Important Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: Implement authentification plugin for api which allows authentification against remote http web server. This may need changes in session handling. We want to use this plugin and setup for opensuse.org and connect api.o.o and build.o.o directly to internet without iChain proxy. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-23 12:06:04) Tom, we need your expertise here, what is possible with rails and what makes sense. -- openSUSE Feature: https://features.opensuse.org/309070

1 7

[New: openFATE 310233] skip repo update when installing packages with zypper
by fate_noreply＠suse.de 24 Sep '15

24 Sep '15

Feature added by: Denny Beyer (lumnis) Feature #310233, revision 1 Title: skip repo update when installing packages with zypper openFATE: Unconfirmed Priority Requester: Important Requested by: Denny Beyer (lumnis) Description: When installing a new package with zypper etc. everytime you run zypper, repos get updated and the user has to wait. Because a general user needs several extra repos, this waiting time always seems to be too long. Why not running 'zypper ref' as a low priority task after startup/time intervall has passed and give the used immidiate access to install a software package? -- openSUSE Feature: https://features.opensuse.org/310233

1 18