October 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 313077] New PAM modules must not be deployed unnoticed by sec team
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Sebastian Krahmer (krahmer) Feature #313077, revision 1 Title: New PAM modules must not be deployed unnoticed by sec team openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Sebastian Krahmer (krahmer) Partner organization: openSUSE.org Description: New PAM modules should be reviewed by security team. Just like any suid/daemon/DBUS service. In particular if they are installed by default. -- openSUSE Feature: https://features.opensuse.org/313077

1 4

[New: openFATE 311163] packaging firefox add-ons
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Ludwig Nussel (lnussel) Feature #311163, revision 1 Title: packaging firefox add-ons Hackweek VI: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: We lack a way to be able to easily package firefox add-ons as rpm. Packages of add-ons are useful both for the distro vendor and for admins. Distro (or appliance) vendors may install some add-ons by default. Admins want all users to have certain add-ons by default. Moreover some add-ons are not noarch (like bonjourfoxy) and need to be compiled specifically for each distro so a package is unavoidable. To make all of that possible the firefox package needs to provide rpm macros so spec files for add-ons become really simple. By creating a script that downloads version, description etc from addons.mozilla.org and automatically creates spec files the task of packaging add-ons becomes a piece of cake. See home:lnussel:firefox for current status. -- openSUSE Feature: https://features.opensuse.org/311163

1 6

[New: openFATE 316562] Add fs.protected_hardlinks=1
by fate_noreply＠suse.de 15 Mar '16

15 Mar '16

Feature added by: Sebastian Krahmer (krahmer) Feature #316562, revision 1 Title: Add fs.protected_hardlinks=1 Requested by: Sebastian Krahmer (krahmer) Partner organization: openSUSE.org Description: In order to disallow hard linking to suid files etc we should enable hardlink protection: fs.protected_hardlinks=1 or via apropriate /proc entry. -- openSUSE Feature: https://features.opensuse.org/316562

1 9

[New: openFATE 309362] Re-implement Download on Demand (DoD) feature
by fate_noreply＠suse.de 01 Mar '16

01 Mar '16

Feature added by: Adrian Schröter (adrianSuSE) Feature #309362, revision 1 Title: Re-implement Download on Demand (DoD) feature Buildservice: Done Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: The DoD features was dropped for 1.7. LinuxFoundation has re-implemented it in a cleaner way for 1.8 release. -- openSUSE Feature: https://features.opensuse.org/309362

1 8

[openFATE 305838] Integrate ReviewBoard in Buildservice
by fate_noreply＠suse.de 12 Feb '16

12 Feb '16

Feature added by: Klaas Freitag (kfreitag) Feature #305838, revision 1, last change by Title: Integrate ReviewBoard in Buildservice Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Klaas Freitag (kfreitag) Description: ReviewBoard is a code change review system. It should be considered to integrate it to the openSUSE Buildservice infrastructure to ease collaboration. It might be an option that submit requests to packages can be handled in the review board. -- openSUSE Feature: https://features.opensuse.org/305838

1 4

[New: openFATE 318951] YaST should log time like dmesg and journalctl
by fate_noreply＠suse.de 09 Feb '16

09 Feb '16

Feature added by: Joachim Werner (joachimwerner) Feature #318951, revision 1 Title: YaST should log time like dmesg and journalctl Requested by: Arvin Schnell (aschnell) Partner organization: openSUSE.org Description: YaST should log the time in its log-file like 'dmesg' and 'journalctl --output short-monotonic' so that times in the various logs can be compared and events can be synchronized. Relations: - YaST should log time like dmesg and journalctl (feature/copiedfrom: 318921) Business case (Partner benefit): openSUSE.org: Easier to analyse logs in bug reports. -- openSUSE Feature: https://features.opensuse.org/318951

1 4

[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