- openSUSE Features

[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 326877] [LATE_ENTERED] Add option of UDF format to Yast partition manager
by fate_noreply＠suse.de 13 Dec '18

13 Dec '18

Feature added by: Matthias Eckermann (mge1512) Feature #326877, revision 1 Title: [LATE_ENTERED] Add option of UDF format to Yast partition manager Requested by: Ilya Chernykh (ansus) Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: [Copied feature: for SLE 15 SP1] UDF is an universal disk format file system, which can be used on optical rewritable and non-rewritable media, USB flash drives and hard drives. The file system is supported by all modern operating systems, including Windows, BSD, MacOS X, Solaris, OS/2|eComStation, BeOS|Haiku as well as Linux kernel, making it one of the best choices to use when transferring data between platforms. UDF also has optional built-in ability to minimize wearing-off of rewritable media with limited rewrite cycles such as flash, CD-RW and DVD-RAM by evenly distributing load over the media, including access to the allocation table. Despite this Yast2 partition manager does not suggest option to format a volume into UDF, thus forcing to use a mkudffs command line tool. Relations: - Add option of UDF format to Yast partition manager (feature/childof: 312911) - Add option of UDF format to Yast partition manager (feature/copiedfrom: 312911) -- openSUSE Feature: https://features.opensuse.org/326877

1 6

[New: openFATE 326741] zypper: use dialog to display license
by fate_noreply＠suse.de 30 Nov '18

30 Nov '18

Feature added by: Ludwig Nussel (lnussel) Feature #326741, revision 1 Title: zypper: use dialog to display license Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: >From user feedback I got at Akademy. By default zypper displays licenses to confirm in "less". That requires pressing 'q' to exit the pager. That is not intuitive for not so Linux experienced users. So to make this more user friendly, zypper could use "dialog" instead of less if available. An example call could be for example: # dialog --textbox /etc/YaST2/licenses/base/license.txt $((LINES-5)) 85 --and-widget --yesno $"Do you agree with the terms of the license?" 0 0 -- openSUSE Feature: https://features.opensuse.org/326741

1 3

[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 326928] Improve conflict resolution
by fate_noreply＠suse.de 27 Nov '18

27 Nov '18

Feature added by: Ludwig Nussel (lnussel) Feature #326928, revision 1 Title: Improve conflict resolution Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: relaying from https://lists.opensuse.org/opensuse-factory/2018-11/msg00273.html Vendor change conflicts may have a common resolution for several packages. It would be more user friendly to group them and require only a single decission from the user. -- openSUSE Feature: https://features.opensuse.org/326928

1 0

[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