March 2017 - openSUSE Features - openSUSE Mailing Lists

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