February 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 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

[New: openFATE 322473] Address Space Randomization for all binaries (ASLR / PIE)
by fate_noreply＠suse.de 27 Apr '18

27 Apr '18

Feature added by: Marcus Meissner (msmeissn) Feature #322473, revision 1 Title: Address Space Randomization for all binaries (ASLR / PIE) Requested by: Marcus Meissner (msmeissn) Requested by: Marcus Meissner (msmeissn) Partner organization: openSUSE.org Description: We want address space randomizaton (ASLR) for all binaries we ship. This means building all possible binaries with -fPIE -pie. openSUSE Factory is close to having this already, just some polishing steps needed. Business case (Partner benefit): openSUSE.org: unacceptable not to have it in comparison with competitors. -- openSUSE Feature: https://features.opensuse.org/322473

1 6

[New: openFATE 323510] Better separation of duties between Desktop Environments and Yast
by fate_noreply＠suse.de 22 Apr '18

22 Apr '18

Feature added by: Ney Walens De Mesquita (nwm) Feature #323510, revision 1 Title: Better separation of duties between Desktop Environments and Yast openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Ney Walens De Mesquita (nwm) Partner organization: openSUSE.org Description: Nowadays Yast has built in package installation and management. Whilst it does make sense for servers or headless installations, it does not fit well when using a desktop like KDE or Gnome. My suggestion is to rename the Yast software management module to something in the line of "Feature Management" or "Advanced Software Management". Ideally the desktop's default software manager, like Gnome Software, would then be used to install, well, Desktop software. I can see some advantages to this approach: - The desktop software manager is often faster to adapt to new technologies like PackageKit, FlatPak, Snaps, etc... - The Desktop experience is more consistent when using the desktop provided software manager Yast software manager module would then be used for Development pattern installations and more server related installations. This would also open up for a separation of duties and less redundancy in the distribution. The same idea can also be applied to printer configurations, it does not look nice when you look for printer configuration and receive three distinct options. The last printer module should be used for servers only and be completely removed from desktop focused installations. -- openSUSE Feature: https://features.opensuse.org/323510

1 1

[New: openFATE 315060] Remove double configuration-posibilities (Yast/KDE)
by fate_noreply＠suse.de 22 Apr '18

22 Apr '18

Feature added by: Thomas Langkamp (tomtomme) Feature #315060, revision 1 Title: Remove double configuration-posibilities (Yast/KDE) openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Thomas Langkamp (tomtomme) Partner organization: openSUSE.org Description: Examples: 1. For 12.2 (fresh install) I could configure ntp via yast and via kde, through different menus. The kde-method did not work the yast method worked. 2. The same for network: After a fresh 12.2 and 12.3 install manual-internet (no dhcp) connection failed until I used the Yast-network-module. A direct configuration through the KDE-configuration dialoge did not work. At cÂ´t (heise journal) I read that it even did not work for DHCP... 3. I could continue... Why all these double configuration possibilities? Please disable the one in KDE or the one in Yast (I know you can not tell KDE to stop developing those, because other distros do not have Yast, but for suse you could just disable them or remove the yast pendants, if thats ok for the other desktops like gnome etc.) Thanks, tomme -- openSUSE Feature: https://features.opensuse.org/315060

1 3

[New: openFATE 315059] Remove double configuration-posibilities (Yast/KDE)
by fate_noreply＠suse.de 22 Apr '18

22 Apr '18

Feature added by: Thomas Langkamp (tomtomme) Feature #315059, revision 1 Title: Remove double configuration-posibilities (Yast/KDE) openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Thomas Langkamp (tomtomme) Partner organization: openSUSE.org Description: Examples: 1. For 12.2 (fresh install) I could configure ntp via yast and via kde, through different menus. The kde-method did not work the yast method worked. 2. The same for network: After a fresh 12.2 and 12.3 install manual-internet (no dhcp) connection failed until I used the Yast-network-module. A direct configuration through the KDE-configuration dialoge did not work. At cÂ´t (heise journal) I read that it even did not work for DHCP... 3. I could continue... Why all these double configuration possibilities? Please disable the one in KDE or the one in Yast (I know you can not tell KDE to stop developing those, because other distros do not have Yast, but for suse you could just disable them or remove the yast pendants, if thats ok for the other desktops like gnome etc.) Thanks, tomme -- openSUSE Feature: https://features.opensuse.org/315059

1 1

[New: openFATE 318356] Add firewalld to openSUSE
by fate_noreply＠suse.de 22 Apr '18

22 Apr '18

Feature added by: Mathias Homann (lemmy04) Feature #318356, revision 1 Title: Add firewalld to openSUSE openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Mathias Homann (lemmy04) Partner organization: openSUSE.org Description: firewalld provides a dynamic firewall that can handle iptables, ip6tables and ebtables based on the connections saved in NetworkManager. With firewalld the firewall configuration can be changed "on the fly" without having to reload the whole firewall tables. Firewalld is particularly useful for computers with highly volatile network setups, i.e. mobile hardware (laptops) or virtualization hosts. it would be desirable to add firewalld as an alternative to SuSEfirewall2 for users that want it. Test Case: Test case: I have been using firewalld from home:lemmy04:firewalld for a couple of months now to no ill effect. Test case 2: firewalld in its current version is the default firewall subsystem in fedora and RHEL7... Use Case: In Network Manager you can define for each stored connection which firewall zone will be used for the interface if that connection is used. Best use case for this: wireless interface on a laptop of someone who travels a lot. Business case (Partner benefit): openSUSE.org: SuSEfirewall2 is static and according to its developer not actively developed anymore. Also, current network setups can easily call for more than three zones, which firewalld provides by default. -- openSUSE Feature: https://features.opensuse.org/318356

1 8

[New: openFATE 311089] Disable system bell by default if sound card is installed
by fate_noreply＠suse.de 21 Apr '18

21 Apr '18

Feature added by: Pieter De Decker (pdedecker) Feature #311089, revision 1 Title: Disable system bell by default if sound card is installed openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Pieter De Decker (pdedecker) Partner organization: openSUSE.org Description: One of the first things I do after installing openSUSE is disabling the system bell by adding this to ~/.inputrc: set bell-style none Its volume is needlessly high. The bell scares the hell outta me whenever it creeps up because I backspaced too much on the command line. My suggestion: disable the system bell by default, unless no sound card is installed. Business case (Partner benefit): openSUSE.org: It's a simple fix for something that has been bugging me forever. -- openSUSE Feature: https://features.opensuse.org/311089

1 7

[openFATE 308182] Create administrator tool for replicating OBS resources
by fate_noreply＠suse.de 20 Apr '18

20 Apr '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #308182, revision 1 Title: Create administrator tool for replicating OBS resources Buildservice: Evaluation Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: A tool for replicate defined projects from a remote OBS instance to a local instance would be helpfull. This should offer different levels of replication depth: * Just latest sources or including past source history (maybe with a date limiter) * Replicate binaries for :full tree ( to be able to bootstrap yourself ) or all binaries from package directories. The tools would be helpfull as CLI and/or as part of the admin web frontend. The remote instance should be access via the frontend api, while the local instance must be accessed via backend source and rep server (+ local frontend api for creating projects and packages). -- openSUSE Feature: https://features.opensuse.org/308182

1 3

[New: openFATE 323325] Make "--no-allow-vendor-change" the default option for "zypper dup"
by fate_noreply＠suse.de 28 Mar '18

28 Mar '18

Feature added by: Sekhemty - (sekhemty) Feature #323325, revision 1 Title: Make "--no-allow-vendor-change" the default option for "zypper dup" Requested by: Sekhemty - (sekhemty) Partner organization: openSUSE.org Description: By reading the forums and the mailing list, I learned that the preferred way to update Tumbleweed is to use sudo zypper dup --no-allow-vendor-change Since updating a rolling distro is a task that is to be done regularly, I think that setting the "--no-allow-vendor-change" option as the default one could be desirable Business case (Partner benefit): openSUSE.org: To have an easier and faster update process. -- openSUSE Feature: https://features.opensuse.org/323325

1 3

[New: openFATE 310652] Have an Etherpad install on openSUSE infrastructure
by fate_noreply＠suse.de 28 Mar '18

28 Mar '18

Feature added by: Jos Poortvliet (jospoortvliet) Feature #310652, revision 1 Title: Have an Etherpad install on openSUSE infrastructure openFATE: Unconfirmed Priority Requester: Important Requested by: Jos Poortvliet (jospoortvliet) Partner organization: openSUSE.org Description: Currently the marketing team in particular makes use of lots of piratepad's to work collaboratively on articles, announcements, plans and other things. Wiki's don't offer the ease and real-time collaboration features needed so piratepad is perfect. Except that it isn't. Piratepad has some serious issues (see "Why do we want this?"). So we would like to have an Etherpad install on openSUSE infrastructure. Having our 'own' Etherpad instance on an openSUSE server would solve these issues. Even just having it as a SUSE Studio virtual image so it can be run somewhere would be good enough. In general, the openSUSE servers are pretty dependable and even when not, we know who to ping to solve problems. Use Case: Usecase would be pretty much half the work the marketing team does - writing announcements, articles, planning... Business case (Partner benefit): openSUSE.org: The current 'solution' to use Piratepad has a bunch of issues: Stability is a big one - Piratepad is down quite frequently, sometimes for a whole day, making our work difficult. Another serious issue is oversight. We can't see what pads we have, resulting in lost pads (and the work we put into them) and duplication of efforts. Then there is the lack of control. All piratepads are fully public - but we have sometimes things we'd like to keep under the lid like announcements we are working on, articles, board things etcetera. Etherpad provides access control which would help us immensely. Part of that control issue is the ability (or lack there off) of deleting pads - we can't do that on Piratepad. Finally, we don't OWN Piratepad. If it went away RIGHT NOW, we would loose MANY important articles, announcements and other good work. It would be a small disaster for the marketing team and it's getting potentially worse as we do more and more work on Etherpad. -- openSUSE Feature: https://features.opensuse.org/310652

1 19

[New: openFATE 312804] Hermes integration on the openSUSE wiki
by fate_noreply＠suse.de 28 Mar '18

28 Mar '18

Feature added by: Sebastian Oliva (tian2992) Feature #312804, revision 1 Title: Hermes integration on the openSUSE wiki openSUSE Infrastructure: Unconfirmed Priority Requester: Desirable Requested by: Sebastian Oliva (tian2992) Partner organization: openSUSE.org Description: An extension to the wiki software, to add Hermes support to the Wiki software, enabling digests and advanced notifications to the Watch List. Use Case: Anna edited the openSUSE wiki, adding a tutorial to configure repositories. She subscribes to the page and enables notifications. When John edits the page, Anna gets a twitter notification, letting her know, there was an edition in the page. -- openSUSE Feature: https://features.opensuse.org/312804

1 2

[New: openFATE 320681] Admin Issue Dashboard
by fate_noreply＠suse.de 27 Mar '18

27 Mar '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #320681, revision 1 Title: Admin Issue Dashboard Buildservice: Evaluation by project manager Milestone: 2.8 Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: Turn the admin warning and error mails into a dash board. These are problems which get detected by the api or backend code and needs a helping hand by the admin. It is not supposed to be a replacement for errbit, which is for debugging developer issues. The issues need to be stored in a way that they can be identified again. If the problem get fixed they must be removed by the system again. If the same problem is changing (eg. more data becomes out-of-sync between api and backend) the same entry must get updated. -- openSUSE Feature: https://features.opensuse.org/320681

1 3

[New: openFATE 319313] Keep showing running maintenance incidents to packager
by fate_noreply＠suse.de 27 Mar '18

27 Mar '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #319313, revision 1 Title: Keep showing running maintenance incidents to packager Buildservice: New Milestone: 2.7 Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: Package maintainers want to be able to see running maintenance updates. Currently they see an update, which they have prepared only when: - their maintenance update request is not yet accepted - they keep their bugzilla entry open (which is referenced in patchinfo). This is good for the "my work" view, which should only show tasks where the packager has to act. But there is currently no easy way to see all running updates on request. There are two possible scenarios of not-yet-released updates: - open incident, still building or collecting updates - frozen incident, running release request (read being tested by QA). The open incident can be covered by a search for patchinfos where the user is listed as packager and where the project is not locked. The frozen incident situation should be covered by monitoring the request. There is fate #310145 which wants a generic monitoring of requests. We can use this by adding the packager from _patchinfo to the release request. -- openSUSE Feature: https://features.opensuse.org/319313

1 5

[New: openFATE 318339] Clone repo API support
by fate_noreply＠suse.de 27 Feb '18

27 Feb '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #318339, revision 1 Title: Clone repo API support Buildservice: Evaluation by engineering manager Milestone: 2.7 Priority Requester: Mandatory Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Requested by: Stephan Kulow (coolo) Partner organization: openSUSE.org Description: Coolo wants the obs_admin support for cloning repos as command. Rudi may also wants this. I assume we need this as background/invoked job like the project copy is implemented. -- openSUSE Feature: https://features.opensuse.org/318339

1 4

[New: openFATE 308899] allow repository specification in project meta xml
by fate_noreply＠suse.de 27 Feb '18

27 Feb '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #308899, revision 1 Title: allow repository specification in project meta xml Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: We have currently to set Type, Repotype and Patterntype in project conf data. That makes it hard to add an images repo easily with a gui that works. Before creating code interpreting the prjconf, I would like to suggest to extend repository xml element to define this as default. Opinions ? Feature is completed when we have an "Add kiwi images repository" button. -- openSUSE Feature: https://features.opensuse.org/308899

1 4

[New: openFATE 308619] Provide Kwallet integration for Firefox
by fate_noreply＠suse.de 25 Feb '18

25 Feb '18

Feature added by: Jimmy Berry (boombatower) Feature #308619, revision 1 Title: Provide Kwallet integration for Firefox openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Jimmy Berry (boombatower) Description: I have wanted such a feature for sometime and recently discoved https://addons.mozilla.org/en-US/firefox/addon/49357 via identi.ca talk. Since openSUSE 11.2 includes KDE integration for Firefox, I think this would be a great thing to either add/finish/polish or just defaultly include as part of integration. -- openSUSE Feature: https://features.opensuse.org/308619

1 3

[New: openFATE 324890] Allow 'multibuild' to be disabled per project
by fate_noreply＠suse.de 22 Feb '18

22 Feb '18

Feature added by: Ludwig Nussel (lnussel) Feature #324890, revision 1 Title: Allow 'multibuild' to be disabled per project 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/3227 filed by Dominique Multibuilds are an interesting concept and I do like it a lot - but it causes a problem for the products using rings. I'll use a package of mine as a practical example (I did not convert it to multibuild yet, knowing of this problem. * libproxy - and libproxy-plugins libproxy lives in ring1 (basic library dependencies) and libproxy-plugins lives in ring2 (full KDE and GNOME extensions on top of libproxy, which uses a plugin model) now, with multibuild, I could not have libproxy builtin ring1 and libproxy:plugins in ring2 - they would only go together. My proposal would be a way to specify ring0/1/2 that multibuild is NOT to be considered (which would easily make for libproxy:plugins not to be built for ring1); but this then still lacks a good idea to ensure libproxy:plugins can be built in ring2 (preferably it would link to ring1/libproxy - we could then add some extra information into the _link to tell it what @BUILD_FLAVOR@ to use for this package -- openSUSE Feature: https://features.opensuse.org/324890

1 1

[New: openFATE 310922] central system user registry
by fate_noreply＠suse.de 12 Feb '18

12 Feb '18

Feature added by: Ludwig Nussel (lnussel) Feature #310922, revision 1 Title: central system user registry openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Once upon a time all systems users were defined in aaa_base via the default /etc/passwd file. When the uid space below uid 100 got too small a new dynamic range between 100 and 499 was introduced. So nowadays packages dynamically create a user in %pre which gets a random uid in this range. Disadvantage: uids are different on every system. Usually this is not a problem but for programs that export files over the network it is. TV recordings made by VDR for example. useradd has a --preferred-uid option for such cases. It's possible to specify a uid and useradd tries to use it. If it's already taken another one is chosen. Thefore I'd propose to leverage that feature: - introduce a central uid registry for system users, e.g a file in aaa_base - lower SYSTEM_UID_MAX (/etc/login.defs) to e.g. 349 and assign "preferred uids" in the rage 350-499. - change useradd calls in packages to a macro that transparently decides whether a preferred uid needs to be used. Use Case: - two systems running vdr, one for recording, the other one for playback on a TV want to share recordings via nfs. -- openSUSE Feature: https://features.opensuse.org/310922

1 15

[New: openFATE 324968] clean old packages only after the whole repository has been re-built.
by fate_noreply＠suse.de 01 Feb '18

01 Feb '18

Feature added by: Ludwig Nussel (lnussel) Feature #324968, revision 1 Title: clean old packages only after the whole repository has been re-built. Buildservice: New Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: following up on https://bugzilla.suse.com/show_bug.cgi?id=482392 When a shared library package changes the soname, the resulting old binary rpms are immediately cleaned up after the new build finishes. This breaks bootstrapping if it hits eg rpm. Proposed solution would be to keep around old packages until the whole project is rebuilt -- openSUSE Feature: https://features.opensuse.org/324968

1 0

[New: openFATE 324966] add mail header to specify role of the notification
by fate_noreply＠suse.de 01 Feb '18

01 Feb '18

Feature added by: Ludwig Nussel (lnussel) Feature #324966, revision 1 Title: add mail header to specify role of the notification Buildservice: New Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: following up on https://github.com/openSUSE/open-build-service/issues/4162 when I recieve a email because someone commented on a SR and that email is sent to all members of the opensuse-reviewteam i'd like something in the headers to be different from when I get a email about a comment on a SR that I created / need to review as a maintainer / already commented on. Generally I'd like to pay alot of attention to the second type of comments, where as the first type I like to filter somewhere in my inbox so I can look at them if needed. Example B, currently I see everytime abichecker comments on a maintenance incident, in my case it would be better if I could filter it so I can discard those comments if I didn't create or am not directly involved in the maintenance incident like what happened before I was getting those emails. -- openSUSE Feature: https://features.opensuse.org/324966

1 0

[New: openFATE 324962] allow to lock requests
by fate_noreply＠suse.de 01 Feb '18

01 Feb '18

Feature added by: Ludwig Nussel (lnussel) Feature #324962, revision 1 Title: allow to lock requests Buildservice: New Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: in order to avoid developers messing up the state of an almost ready staging project, it would be good to have some kind of lock command so the state of certain requests cannot be modified by anyone except for a specific user/group anymore. Needed especially for * delete requests, as they are handled in a very special way * superseding requests. if a developer supersedes another request, release enginering can't do anything about it anymore Is also of particulare interest for SLE with strict deadlines, more elaborate human reviews that take time and yast auto submits by a CI. -- openSUSE Feature: https://features.opensuse.org/324962

1 0

[New: openFATE 324961] enhance freezelink command
by fate_noreply＠suse.de 01 Feb '18

01 Feb '18

Feature added by: Ludwig Nussel (lnussel) Feature #324961, revision 1 Title: enhance freezelink command Buildservice: New Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: In order for the staging tool to avoid handling the frozen link itself, obs needs to provide more api calls * update all entries to current version * update or add only specific entries * create links only with a limited set of packages -- openSUSE Feature: https://features.opensuse.org/324961

1 0