February 2018 - openSUSE Features - openSUSE Mailing Lists

[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