February 2018 - openSUSE Features - openSUSE Mailing Lists

[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