December 2015 - openSUSE Features - openSUSE Mailing Lists

[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 319895] Add btrfs subvolume options to autoyast
by fate_noreply＠suse.de 16 Jan '16

16 Jan '16

Feature added by: Robert Klein (kleinrob) Feature #319895, revision 1 Title: Add btrfs subvolume options to autoyast openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Robert Klein (kleinrob) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": - @/var/lib/libvirt/images - @/var/lib/mariadb - @/var/lib/mysql - @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. -- openSUSE Feature: https://features.opensuse.org/319895

1 2

[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 309385] Improve "Pattern" handling
by fate_noreply＠suse.de 18 Dec '15

18 Dec '15

Feature changed by: Ludwig Nussel (lnussel) Feature #309385, revision 42 Title: Improve "Pattern" handling openSUSE-11.3: Rejected by Andreas Jaeger (a_jaeger) reject date: 2013-08-09 13:10:33 reject reason: Not done for 11.3. Priority Requester: Important - openSUSE Distribution: Unconfirmed - Priority - Requester: Important Requested by: Michael Andres (mlandres) Partner organization: openSUSE.org Description: We need to clearly define the way to deal with patterns. - The code11 decision not to install pattern makes them hard to handle. The solver not knowing which patterns were actually selected by the user results in bugs like https://bugzilla.novell.com/show_bug.cgi?id=576059 or https://bugzilla.novell.com/show_bug.cgi?id=676994. It also produces poor results on upgrades, as we can only guess which patterns should be updated. - The approach on opensuse 11.2 to use a package to represent the pattern and it's dependencies might be a step into the right direction (similar to the release-package representing a product). But the link between a pattern and it's prepresenting package is missing. This leads to bugs like https://bugzilla.novell.com/show_bug.cgi?id=592640, where actions like 'set Taboo' on patterns have no effect, because we don't know, thus can't lock, the corresponding package. Another open issue is removal of patterns like in https://bugzilla.novell.com/show_bug.cgi?id=407040. Removing the pattern package with cleanup enabled could be an option. This also requires a link between pattern and package. Whithout a decision accepted by all stakeholders, libzypp/zypper won't be able to resolve several bugs satisfactory. Discussion: #19: Michael Andres (mlandres) (2014-01-27 11:35:53) Done in libzypp-14.7.0 / libsolv-0.4.2 for alpha3. We should be able to drop the old pattern metadata files. -- openSUSE Feature: https://features.opensuse.org/309385

1 0

[New: openFATE 320184] Session rescue mode
by fate_noreply＠suse.de 12 Dec '15

12 Dec '15

Feature added by: Sławomir Lach (Lachu) Feature #320184, revision 1 Title: Session rescue mode openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: There should exist (optional) way to made rescue of user session possible. Systemd-logind should use cgroups to preserve memory for session rescue process(for each session some bulk of memory should been reserved). This memory could be used only by process in specify cgroup, like process manager, window manager and X server. Other idea is to pause any process not belongs to privileged cgroup, to avoid problems with CPU/IO usage, when some keyboard combination was used. Optional idea is to allow use of reserved memory by special keyboard combination(the same, which pauses process). Access to additional memory could been made by special kernel call, but I'm not sure this is necessary. Use Case: Martin have computer with only 2GiB of memory. He wants to run broken sword installer gained from gog.com. System hangs, so he click ctrl+esc, all other processes than window manager, X and process manager pauses and not paused process could allocate additional memory. He selects broken process, kill it and click ctrl+esc to bring session work again. Business case (Partner benefit): openSUSE.org: System could have problems, while a lot of memory are used, so we need to reserve memory for special purposes. -- openSUSE Feature: https://features.opensuse.org/320184

1 0

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

04 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