May 2018 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 319035] Make YaST (incl. modules available in GNOME Software
by fate_noreply＠suse.de 22 Dec '19

22 Dec '19

Feature added by: Dominique Leuenberger (dimstar) Feature #319035, revision 1 Title: Make YaST (incl. modules available in GNOME Software openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Dominique Leuenberger (dimstar) Partner organization: openSUSE.org Description: GNOME Software is an other way of handling installations. Instead of being package centric, it is application centric. An application is being represented by means of an appdata.xml file in it's setup (installed to /usr/share/appdata), then a metadata parser extracts this info and produces 'AppStream' metadata (to be consumed by software centers) In order to make extensions/plugins to applications discoverable, a package can add a metainfo.xml file to the same location and have itself listed as an extension/addon to the application. For YaST, this results in: - an appdata.xml file being provided together with YaST.desktop (done) - For all yast modules to install a metainfo.xml file, describin their extensive nature to yast. -- openSUSE Feature: https://features.opensuse.org/319035

1 4

[New: openFATE 324909] speed up staging setup and rebuild
by fate_noreply＠suse.de 15 Aug '19

15 Aug '19

Feature added by: Ludwig Nussel (lnussel) Feature #324909, revision 1 Title: speed up staging setup and rebuild Buildservice: New Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Staging projects have to rebuild quite often which takes a lot of time and resources. Maybe OBS could speed that up by taking some shortcuts. Some ideas by an unqualified external: * using ccache to speed up rebuilds without source changes. Could be implemented by project or project group for example. * have some cloning feature that also copies binaries and does not lead to immediate rebuild. That would allow to setup a new staging or rebase one in no time by cloing all packages including their binaries from rings. -- openSUSE Feature: https://features.opensuse.org/324909

1 5

[New: openFATE 318458] Reading user process memory
by fate_noreply＠suse.de 26 Apr '19

26 Apr '19

Feature added by: Sławomir Lach (Lachu) Feature #318458, revision 1 Title: Reading user process memory Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Reading user's process memory or writting to it is very bad think. Malware can stole passwords or change settings of application. I have two idea about solving this issue: 1. Dissallow to debug(reading/writting memory) process placed in /bin, /sbin, /usr/bin, /usr/sbin 2. Dissallow to debug(reading/writting memory) process of file not belonging to user, who execute file. -- openSUSE Feature: https://features.opensuse.org/318458

1 1

[New: openFATE 323500] Kernel: Add support for new AppArmor rule types
by fate_noreply＠suse.de 20 Mar '19

20 Mar '19

Feature added by: Christian Boltz (cboltz) Feature #323500, revision 1 Title: Kernel: Add support for new AppArmor rule types openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Christian Boltz (cboltz) Partner organization: openSUSE.org Description: [forwarded from https://bugzilla.opensuse.org/show_bug.cgi?id=1042082 ] Support for several new AppArmor rule types is on the way to the upstream kernel: * dbus * mount * signal * ptrace * pivot_root * unix Also, support for profile stacking will be added and policy namespace support improved. Those new rule types are needed to make Snappy secure - without them, it's hard or even impossible to make sure snaps don't do something they shouldn't. For example, it would be impossible to restrict dbus access to only the required parts. Of course those new rules will also be useful for "normal" applications. Note that adding support for those rules in a service pack is a bad idea because it might need profile updates, therefore it would be a *very* good idea to backport them to whatever kernel will be shipped in Leap 15/SLE 15. The first base patches are already in 4.11. The next bunch is on its way to 4.12, and the goal is to get the final parts into 4.13 and 4.14. Upstream (especially John Johansen) promised to send the pull request for 4.13 in the next days. The remaining patches for 4.14 will follow in about two months - or a bit earlier if you don't insist on the final version of those patches. Addition by John: Unfortunately upstream 4.13 will not be sufficient. The goal now is to get the remaining changes into 4.14. If backporting to an older kernel I would use the git://kernel.ubuntu.com/jj/linux-apparmor-backports tree. A new series of branches will be added based on the 4.13 version of apparmor. It will provide a small patch series (2 base patches - 1 securityfs, 1 apparmor and then any necessary backport patches for the target kernel version). The final version of the 4.13 backport branch will not be available until at earliest the close of the 4.13 merge window. But a early version could be made available next week. -- openSUSE Feature: https://features.opensuse.org/323500

1 23

[New: openFATE 323318] OBS WEBUI: User role selector on task list
by fate_noreply＠suse.de 21 Feb '19

21 Feb '19

Feature added by: Adrian Schröter (adrianSuSE) Feature #323318, revision 1 Title: OBS WEBUI: User role selector on task list Buildservice: New Milestone: 2.9 Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Requested by: Ruediger Oertel (oertel) Partner organization: openSUSE.org Description: OBS Webui shall support filtering open tasks for a user by his workflow role there. The role is defined via a group for now. Details for planing can be found in this trello card: https://trello.com/c/H0fZCfFi/319-allow-filtering-of-requests-reviews-and-b… This request is just for tracking and connecting involved people. -- openSUSE Feature: https://features.opensuse.org/323318

1 3

[New: openFATE 320873] Remove copy_to_system from control.xml and AutoYaST
by fate_noreply＠suse.de 20 Feb '19

20 Feb '19

Feature added by: Ancor Gonzalez Sosa (ancorgs) Feature #320873, revision 1 Title: Remove copy_to_system from control.xml and AutoYaST openSUSE Distribution: New Priority Requester: Desirable Requested by: Ancor Gonzalez Sosa (ancorgs) Partner organization: openSUSE.org Description: In 2006 an generic mechanism to (silently) copy files from an existing filesystem to the system being installed was introduced in YaST as part of the implementation of two different features (fate#120103 and fate#300421). Any information to the user about the files being copied was intentionally left out (see comments in #300421). In 2008 the list of files was moved to control.xml and the AutoYaST profile (fate#305019). But the documentation and schema for the AutoYaST profile were never updated to reflect the change. We have received several bug reports and Fate entries about it since then, from incomplete lists of files (bug#956515, bug#956976) to non-intuitive or incomplete behavior (fate#319624, bug#956976) and everything in between. Starting with yast2-installation 3.1.187 and yast2-users 3.1.49, the original features do not longer need to use "copy_to_system" and the corresponding section is now empty in the control files of both SLE and openSUSE. I would like to completely drop the "copy_to_system" feature since it's obscure (everything happen behind user's back), problematic (quite some bug reports), not necessary (not longer needed by the originating features) and poorly documented (not even in the AutoYaST schema). -- openSUSE Feature: https://features.opensuse.org/320873

1 12

[New: openFATE 310701] package byobu in an opensuse repository
by fate_noreply＠suse.de 28 Jan '19

28 Jan '19

Feature added by: Divan Santana (divansantana7) Feature #310701, revision 1 Title: package byobu in an opensuse repository openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Divan Santana (divansantana7) Description: Would be great if anyone using opensuse could zypper in byobu . Unfortunately it's not in any opensuse repo despite it being a great tool for administrating linux servers. I'm quite surprised this isn't already available for opensuse. Would be a nice addition for 11.4 -- openSUSE Feature: https://features.opensuse.org/310701

1 7

[New: openFATE 324570] make GDM blackground image configurable
by fate_noreply＠suse.de 18 Jan '19

18 Jan '19

Feature added by: Ludwig Nussel (lnussel) Feature #324570, revision 1 Title: make GDM blackground image configurable Requested by: Ludwig Nussel (lnussel) Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: GDM only has very limited theming posibilites. To change the actual wallpaper one has to modify a binary file a rather nasty and not upgradable way: https://wiki.archlinux.org/index.php/GDM#Log-in_screen_background_image Please implement some more convenient way to allow custom deployments to override the wallpaper in GDM. -- openSUSE Feature: https://features.opensuse.org/324570

1 20

[New: openFATE 322073] yast should not override ip_forward setting
by fate_noreply＠suse.de 16 Jan '19

16 Jan '19

Feature added by: Bernhard Wiedemann (bmwiedemann) Feature #322073, revision 1 Title: yast should not override ip_forward setting openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Bernhard Wiedemann (bmwiedemann) Partner organization: openSUSE.org Description: someone thought, this bugfix qualifies as feature: http://bugzilla.suse.com/show_bug.cgi?id=1010036 Test Case: echo net.ipv4.ip_forward = 1 > /etc/sysctl.d/50-ip-forward.conf sysctl --system 2>/dev/null |grep "ip_forward = " net.ipv4.ip_forward = 1 Use Case: as a system administrator I want to override ip_forward setting in an easily scripted manner by writing my preferred values to /etc/sysctl.d/50-ip-forward.conf Business case (Partner benefit): openSUSE.org: manual configuration is deprecated and yast overriding admin's settings should be a thing of the past. -- openSUSE Feature: https://features.opensuse.org/322073

1 3

[New: openFATE 324964] visualize development process
by fate_noreply＠suse.de 07 Jan '19

07 Jan '19

Feature added by: Ludwig Nussel (lnussel) Feature #324964, revision 1 Title: visualize development process Buildservice: New Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: following up on https://github.com/openSUSE/obs_factory/issues/101 It is fairly common to see contributors confused about the state of their submit request to Factory and it is understandable given the lack of communication about the process present through the interface (or elsewhere for that matter). As an attempt to address that shortcoming and potentially gain contributions to the release tooling I propose a staging workflow plugin to be displayed on requests. The plugin should react to the various states in the process to highlight what has been done and what remains to be done. Additionally, links should be provided to the tools responsible for each stage and any relevant documentation. -- openSUSE Feature: https://features.opensuse.org/324964

1 2

[New: openFATE 308445] Tor is not working out of box
by fate_noreply＠suse.de 29 Nov '18

29 Nov '18

Feature added by: Algimantas B (algyzas) Feature #308445, revision 1 Title: Tor is not working out of box Package Wishlist: Unconfirmed Priority Requester: Neutral Requested by: Algimantas B (algyzas) Description: Let's say I installed tor, it is came alone, without privoxy. One should download it manually. And then if I try :~> screen torify konqueror hich: no tsocks in (/home/senis/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.) /usr/bin/torify: Can't find tsocks in PATH. Perhaps you haven't installed it? [screen is terminating] There is a guide http://en.opensuse.org/Privoxy_tor_squid how to setup it, I'll try it, but in some other distributions it works out of box like this. -- openSUSE Feature: https://features.opensuse.org/308445

1 1

[New: openFATE 309627] Enhance 'Safely Remove' to spin-down and power-off usb HDDs
by fate_noreply＠suse.de 07 Nov '18

07 Nov '18

Feature added by: Pete Clayson (Olmy) Feature #309627, revision 1 Title: Enhance 'Safely Remove' to spin-down and power-off usb HDDs openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Pete Clayson (olmy) Description: 'Safely remove' should (as far as possible) allow for genuine safe removal of all media. Under certain other OSs, the 'safely remove' option on usb devices will... 1/ On usb pen drive with a power/activity led, switch it off (trivial nicety, but reassuring). 2/ On usb HDDs, spin down the disk and power off. This seems more important. There is some discussion about this, for example, http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.… (http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.…) I know that the latest version of Ubuntu does this and there is a script offered in the above link. However, the script, as it stands and run on my installation of OpenSUSE, does not seem to work (in the same way as WinXP or Ubuntu, anyway - my WD600D036 disk does not power off) despite the positive messages in verbose mode. Perhaps this is the CONFIG_USB_SUSPEND option mentioned? -- openSUSE Feature: https://features.opensuse.org/309627

1 6

[New: openFATE 323785] generic translation of pattern-category
by fate_noreply＠suse.de 30 Oct '18

30 Oct '18

Feature added by: Ludwig Nussel (lnussel) Feature #323785, revision 1 Title: generic translation of pattern-category Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: pattern packages have special tags for the category, e.g. pattern-category() = Base%20Technologies Also, translations are contained directly in the package, ie pattern-category(de) = Basistechnologien pattern-category(zh_CN) = %E5%9F%BA%E7%A1%80%E6%8A%80%E6%9C%AF The translations come from a perl script in patterns-rpm-macros: https://build.opensuse.org/package/view_file/openSUSE:Factory/patterns-rpm-… Ie not via weblate. Also putting localized strings in package metadata is uncommon on (open)SUSE. So instead of using a custom special method we should use the regular package metadata translation mechanism we also use for summary and description: https://l10n.opensuse.org/projects/packages-i18n/patterns-master/ Furthermore, how about instead of using this extra provides tag, use the rpm group tag, like e.g. Group: patterns/Base Technologies -- openSUSE Feature: https://features.opensuse.org/323785

1 9

[New: openFATE 325606] Support picking single multibuild containers
by fate_noreply＠suse.de 01 Oct '18

01 Oct '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #325606, revision 1 Title: Support picking single multibuild containers Buildservice: New Milestone: 2.10 Priority Requester: Mandatory Requested by: Adrian Schröter (adriansuse) Requested by: Dominique Leuenberger (dimstar) Partner organization: openSUSE.org Description: Factory Ring setup needs a way to pick single multibuild containers only. Current proposal is to a _link file with a special flavor element, which can be used to filter from defined _multibuild flavors. -- openSUSE Feature: https://features.opensuse.org/325606

1 2

[New: openFATE 320385] Let Zypper know the version number of openSUSE
by fate_noreply＠suse.de 19 Sep '18

19 Sep '18

Feature added by: Philipp Bielefeldt (pbiel) Feature #320385, revision 1 Title: Let Zypper know the version number of openSUSE openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Philipp Bielefeldt (pbiel) Partner organization: openSUSE.org Description: All repo names in openSUSE are structured to have the version number/name in it, such as http://download.opensuse.org/repositories/science/ openSUSE_Leap_42.1 / (for 42.1); I do a lot of repo handling via bash scripts and I find myself over and over again telling someone: "Here, this is a script to install all the software you'll need right nowâ¦ But you have to specify your version string in the repo's name before running it" â 50% chance I will get asked "What do you mean? Where shall I put what?!" I think it was more convenient and less error prone if zypper commands yould use a variable such as osVersion that can be put to replace the string. On openSUSE Leap 42.1 zypper ar -f http://download.opensuse.org/repositories/science/$osVersion/ "Science" would than automatically change to zypper ar -f http://download.opensuse.org/repositories/science/openSUSE_Leap_42.1/ "Science" and so forthâ¦ Business case (Partner benefit): openSUSE.org: This feature would it make easier for admins to write scripts that handle software management/installation on different versions of openSUSE. It would also facilitate writing advice to people on the internet (e.g. the openSUSE wiki) on how to perform certain actions that concern repo management. -- openSUSE Feature: https://features.opensuse.org/320385

1 5

[New: openFATE 314778] Use polkit for YaST privilege management
by fate_noreply＠suse.de 14 Sep '18

14 Sep '18

Feature added by: Dainius Masiliunas (GreatEmerald) Feature #314778, revision 1 Title: Use polkit for YaST privilege management openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Dainius Masiliunas (greatemerald) Partner organization: openSUSE.org Description: At the moment of writing, YaST relies on having root privileges through a graphical sudo in order to view and carry out most tasks. However, there is no reason why simply displaying those tasks should be restricted like that. YaST should always be started with user privileges, and only ask for additional privileges when they are truly needed - when the selected tasks should be carried out. This can be achieved by using polkit. It also brings a lot of other benefits. Use Case: Users who do not have access to the root password currently also do not have access to a lot of functionality that does not actually require the password, such as searching for package information. Users that do administrative tasks are also subjecting the system to possible security risks by running YaST with full root privileges. Using polkit would increase security and prevent potential user mistakes. Business case (Partner benefit): openSUSE.org: Using polkit, the graphical interface of YaST would always be run as a normal user. That means that code that should not have elevated privileges - like GUI - would not run with them. More could be done without needing to enter the root password - package information query, printer setup, device information overview, reviewing network configuration options etc. In a restrictive environment, the system administrator could set certain tasks to be available for use by regular users, or to allow certain tasks to be run by certain users only. The authentication screen would provide more information about what tasks are about to be carried out for increased security. For instance, if a custom YaST module requests permission to modify the partition table, while it claims to only set up the date and time, it would be clear to the user that the module is either fraudulent or is malfunctioning. In order to not have to authenticate after every single change a module wishes to do, a global queue for the changes could be created (like what is shown by the /etc/sysconfig editor once its changes are to be applied). Once the global "apply" button is pressed, the user would be informed of what actions will be carried out and what privileges will be given to carry them out. Then, once the user confirms that by supplying a password, all the changes are applied. -- openSUSE Feature: https://features.opensuse.org/314778

1 8

[New: openFATE 319626] Check password strength for encrypted LVM
by fate_noreply＠suse.de 21 Aug '18

21 Aug '18

Feature added by: Arnold Mesper (amesper) Feature #319626, revision 1 Title: Check password strength for encrypted LVM openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Arnold Mesper (amesper) Partner organization: openSUSE.org Description: A simple password check is done only when selecting encrypted LVM in the main installation screen. No check is done, when creating encrypted LVM via expert partitioner. The same check as performed for user passwords (using cracklib) should be available for encrypted LVMs too - both in the main installation screen as well as in the expert partitioner. The user must be able to accept using a weak password, thus the password strength check must only issue a warning (and not mandate a minimum password length like now in the main installation screen). This is necessary in order to allow testing an installation without having to remember a complex password. Business case (Partner benefit): openSUSE.org: Especially novice users must be warned if password is weak for LVM, as with weak passwords, full disk encryption is useless. -- openSUSE Feature: https://features.opensuse.org/319626

1 1

[New: openFATE 314606] Improved Btrfs subvolume management in YaST Partitioner
by fate_noreply＠suse.de 21 Aug '18

21 Aug '18

Feature added by: Dainius Masiliunas (GreatEmerald) Feature #314606, revision 1 Title: Improved Btrfs subvolume management in YaST Partitioner openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Dainius Masiliunas (greatemerald) Partner organization: openSUSE.org Description: The current implementation of Btrfs subvolume management is a bit too simplistic. It allows adding and removing subvolumes, but that is all. Expanding this to view subvolumes as actual subvolumes would be beneficial. Perhaps something akin to LVM configuration, as Btrfs subvolumes can handle much of what LVM does. At the same time, this could allow easier interfacing with Snapper. Use Case: When using Btrfs as the main file system, it is useful to have a single Btrfs partition for both / and /home, as it allows for more efficient disk space use. When reinstalling and upgrading, it is now a problem, as there is no way to remove certain subvolumes and leave others, and keeping /home between installations is often useful. Another case is when a multi-device Btrfs volume is desirable. The YaST partitioner only allows creating "regular" Btrfs partitions right now. A feature like that would also be useful for tighter Snapper integration. It would be a convenient place to set which volumes should be monitored by it, and which are not. In addition, it would help resolve a few bugs, such as the failure to automatically create subvolumes for excluding directories from Snapper monitoring when choosing to format the Btrfs partition. -- openSUSE Feature: https://features.opensuse.org/314606

1 9

[New: openFATE 314529] Add XFCE and LXDE live cds in software.opensuse.org
by fate_noreply＠suse.de 19 Jul '18

19 Jul '18

Feature added by: Narayansamy S (vazhavandan) Feature #314529, revision 1 Title: Add XFCE and LXDE live cds in software.opensuse.org openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Narayansamy S (vazhavandan) Partner organization: openSUSE.org Description: There is urgent need to Add XFCE and LXDE live cds in software.opensuse.org page as many Linux users are moving away from traditional DEs(KDE,GNOME) after some rather controversial changes from KDE3.X==>DE4.X and GNOME2.x==>GNOME3.X Many users moving to LXDE and XFCE can try out th DE environments using the live cds provided in the software download page Business case (Partner benefit): openSUSE.org: To test hardware issues Smaller download compared to DVD Many users are preferring LXDE and XFCE over GNOME and KDE One can keep using live cds in case of system crashes DVD download doesn't support live boots -- openSUSE Feature: https://features.opensuse.org/314529

1 4

[New: openFATE 318341] Include "fixparts" on the live rescue CD
by fate_noreply＠suse.de 19 Jul '18

19 Jul '18

Feature added by: Neil Rickert (nrickert) Feature #318341, revision 1 Title: Include "fixparts" on the live rescue CD openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Neil Rickert (nrickert) Partner organization: openSUSE.org Description: The "fixparts" utililty (package "gptfdisk-fixparts") is useful for repairing corrupted partition tables, such as occur when a user tries to convert a disk from GPT partitioning to legacy MBR partitioning. It would be useful to include that on live media -- at least the live rescue -- so that we can point people to a way to fix their install problems. -- openSUSE Feature: https://features.opensuse.org/318341

1 1

[New: openFATE 314607] formatting
by fate_noreply＠suse.de 18 Jul '18

18 Jul '18

Feature added by: Francesco Noacco (FireLink) Feature #314607, revision 1 Title: formatting openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Francesco Noacco (firelink) Partner organization: openSUSE.org Description: Can format and save data in the partitions stored in any fs and not just fat32 (after installation). Use Case: I solved it with "disk manager" Debian testing (3.0.2 by Red Hat, 2009) In the formatting parameters allows disk usage by users other than root. And to think that I had just complained because the utility from a new disc without mbr creates one that is not compatible with other distributions (gparted from an alert message). Business case (Partner benefit): openSUSE.org: Operations should be for everyone. -- openSUSE Feature: https://features.opensuse.org/314607

1 1

[New: openFATE 315592] retire /etc/ssl/certs as r/w for admins
by fate_noreply＠suse.de 11 Jul '18

11 Jul '18

Feature added by: Ludwig Nussel (lnussel) Feature #315592, revision 1 Title: retire /etc/ssl/certs as r/w for admins Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Since the introduction of update-ca-certificates in openSUSE 11.2 /etc/ssl/certs has been an automatically managed location for SSL certificates. Adminstrators are no longer meant to put their own files there but instead have update-ca-certificates install symlinks to the actual files there. Having scripts regularly mess with /etc is ugly. Therefore placing individual symlinks in /etc/ssl/certs needs to be retired. /etc/ssl/certs should point to a location in /var instead. This could either be done with a symlink or with a bind mount. -- openSUSE Feature: https://features.opensuse.org/315592

1 9

[New: openFATE 322297] Yast2 working in wayland
by fate_noreply＠suse.de 06 Jul '18

06 Jul '18

Feature added by: Andreas Winter (netzheimer) Feature #322297, revision 1 Title: Yast2 working in wayland openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Andreas Winter (netzheimer) Partner organization: openSUSE.org Description: Wayland is coming with big steps. First distributions (eg fedora) already use it as default. Gnome should be already stable with it, Plasmas support is getting better and better. Some other DE already support it out of the box. Wayland is a lot more secure than Xserver and it is the future. I think it is time to bring Yast2's support for this. At the moment a user who wants to run wayland has just 2 solutions: - Running yast in textmode (which is not a solution for non-geek users) - Switch to another distribution, which offers better support -- openSUSE Feature: https://features.opensuse.org/322297

1 17

[New: openFATE 314706] New default theme
by fate_noreply＠suse.de 05 Jul '18

05 Jul '18

Feature added by: Sharque uddin Ahmed Farooqui (safknw) Feature #314706, revision 1 Title: New default theme openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Sharque uddin Ahmed Farooqui (safknw) Partner organization: openSUSE.org Description: Currently OpenSuse comes this slightly modified default theme from DE. For example KDE default theme is not very different from vanilla KDE default theme. So does not distinctive feeling. I believe having a separate for DE will be it much better feeling to end user also it provide unique look and feel to user. We can have a look at ROSA as case. -- openSUSE Feature: https://features.opensuse.org/314706

1 2

[New: openFATE 312838] Hook up fwzs to NetworkManager
by fate_noreply＠suse.de 19 Jun '18

19 Jun '18

Feature added by: Ludwig Nussel (lnussel) Feature #312838, revision 1 Title: Hook up fwzs to NetworkManager Hackweek VII: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Switching zones in the firewall zone switcher is currently a manual task. NM needs to provide hooks to make fwzs adjust the firewall automatically. http://lizards.opensuse.org/2009/08/28/firewall-zone-switcher-updated/ http://lizards.opensuse.org/2009/07/10/1453/ -- openSUSE Feature: https://features.opensuse.org/312838

1 2

[New: openFATE 324891] fix excessive rebuilding in transitive mode
by fate_noreply＠suse.de 04 Jun '18

04 Jun '18

Feature added by: Ludwig Nussel (lnussel) Feature #324891, revision 1 Title: fix excessive rebuilding in transitive mode Buildservice: New Priority Requester: Mandatory Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Following up on https://github.com/openSUSE/open-build-service/issues/3749 For packages in a build cycle obs normally stops the rebuilding at some point when all packages have been built with all others. From observations when building distributions that however doesn't work if build-compare is enabled. When starting Leap 42.3 in December 2016 I from scratch I could show that gcc was built 101 times. So as workaround we always have to be careful to either switch rebuild mode to direct or disable build compare when checking in base packages. -- openSUSE Feature: https://features.opensuse.org/324891

1 1

[New: openFATE 318196] Redesign YaST Storage Code
by fate_noreply＠suse.de 25 May '18

25 May '18

Feature added by: Arvin Schnell (aschnell) Feature #318196, revision 1 Title: Redesign YaST Storage Code Requested by: Arvin Schnell (aschnell) Partner organization: openSUSE.org Description: The structure of the target-map (holding almost all storage data in YaST) is outdated and not documented. Adding new features, e.g. use whole disk for filesystem, bcache, dm-cache or switching to and from partitions on MD RAID, is difficult and error-prone. Thus a redesign is required to be prepared for new features and make the software more robust. During hackweek I evaluated using the boost graph library for libstorage. The result was announced and is explained, see references. I consider the redesign to be mandatory but not for a specific version (although as soon as possible). Note: This feature is about a redesign, new functionality must by requested as individual feature requests. Relations: - Evaluation Project on GitHub (url: https://github.com/aschnell/libstorage-bgl-eval/wiki) - Announcment on yast-devel (url: http://lists.opensuse.org/yast-devel/2014-10/msg00045.html) -- openSUSE Feature: https://features.opensuse.org/318196

1 14