May 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 22 May '15

22 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - fix more compilation warnings (7 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (7 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (31 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (31 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (56 days) https://github.com/yast/yast-ruby-bindings/pull/140 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 21 May '15

21 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - fix more compilation warnings (6 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (6 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (30 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (30 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (55 days) https://github.com/yast/yast-ruby-bindings/pull/140 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 20 May '15

20 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (41 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-core: - fix more compilation warnings (5 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (5 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-kdump: - Fix SSH / SFTP confusion (19 days) https://github.com/yast/yast-kdump/pull/26 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (29 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (29 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (29 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (61 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (29 days) https://github.com/yast/yast-theme/pull/52 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (29 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (54 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-fonts: - add Source Han Sans CFF font (8 days) https://github.com/yast/yast-fonts/pull/12 Pending requests in repository yast-docker: - Start making this a gem (225 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Error: Internal error. Please report a bug with logs.
by Felix Miata 19 May '15

19 May '15

I get this popup opening 'yast2 bootloader' from Konsole on a TW installation with grub2* uninstalled, and grub and gfxboot installed. Is this expected now that installation no longer offers Grub Legacy at installation time. I wanted to try using YaST2 instead of cmdline configure the gfx menu, but apparently that is not currently an option. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 19 May '15

19 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (40 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-kdump: - Fix SSH / SFTP confusion (18 days) https://github.com/yast/yast-kdump/pull/26 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (28 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (28 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (28 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (60 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (28 days) https://github.com/yast/yast-theme/pull/52 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (28 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (53 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-fonts: - add Source Han Sans CFF font (7 days) https://github.com/yast/yast-fonts/pull/12 Pending requests in repository yast-docker: - Start making this a gem (224 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] "A Little Chaos" in Yast Network - Changes / Versions
by Lukas Ocilka 18 May '15

18 May '15

Hi, I just wanted to create another PR porting change I've made in SLE 12 to master and I've found out, that although SLE 12 still use versions in format X.Y.Z, changelogs do not match. What's actually really bad, we have the same versions in SLE 12 / SLE 12 SP1 + openSUSE 13.3, but the content do not match, see: SLE 12 ------ https://github.com/yast/yast-network/blob/SLE-12-GA/package/yast2-network.c… SLE 12 SP1 / openSUSE 13.3 -------------------------- https://github.com/yast/yast-network/blob/master/package/yast2-network.chan… Branch `master` started to diverge in November 2014 already! When SLE 12 (non-master version) starts to diverge, we should switch to using X.Y.Z.A versions instead of X.Y.Z only, while master should keep using X.Y.Z. Please, see also my e-mail "Re: [yast-devel] [RFC] Versioning: master vs SLE-12-GA branches", sent 17.10.2014 08:28. Anyway, what to do now? We have different content but the same versions. Should I just "branch" SLE 12 GA with new version 3.1.113.1? Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 18 May '15

18 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (39 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-kdump: - Fix SSH / SFTP confusion (17 days) https://github.com/yast/yast-kdump/pull/26 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (27 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (27 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (27 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (59 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (27 days) https://github.com/yast/yast-theme/pull/52 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (27 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (52 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-fonts: - add Source Han Sans CFF font (6 days) https://github.com/yast/yast-fonts/pull/12 Pending requests in repository yast-docker: - Start making this a gem (223 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Services UI strikes back
by Ancor Gonzalez Sosa 15 May '15

15 May '15

Last week we implemented a prototype of a reusable component to manage services in YaST modules and applied it to yast-dns-server. So I updated the infamous "YaST service management" document[1] to show the two alternatives of usage of the new component. Feedback (from UI expert or anybody else) is appreciated so we can decide which option (labeled "A" and "B") in the document is better in general. The first page of the document is unchanged, so you can skip it if you already know the problem. Cheers. [1] https://docs.google.com/document/d/1TQO-bdqagSOUssGqJsf3eEeMDh2w40BujdOFP9-… -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 22

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 15 May '15

15 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (36 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-kdump: - Fix SSH / SFTP confusion (14 days) https://github.com/yast/yast-kdump/pull/26 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (24 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (24 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (24 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (56 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (24 days) https://github.com/yast/yast-theme/pull/52 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (24 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (49 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (220 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] SUSE firewalling
by Karol Mroz 15 May '15

15 May '15

Hello YaST-Developers, We (me with the support/insight of Olaf, Scott, Coolo and Ludwig) are looking at a firewall solution overhaul for SLE/openSUSE. Reaching out to Lucas, the suggestion was to post a writeup here in the hopes of garnering some interest from the YaST community. After discussions on opensuse-factory, and some research, we decided that "firewalld" appears to be an attractive project that we could leverage. It is under active development, supports zones, network services, has both command and graphical interfaces and speaks dbus. Our goal is to provide a modern firewall solution that integrates well with our network management, and with our system as a whole. At the heart of this integration, is YaST. For the time being, firewalld is strictly an alternative/option to our existing SuSEFirewall2. There is still much to do before it can stand on it's own two feet. The bulk of the work thus far has been centered in the core yast module, specifically the SuSEFirewall module/class. A Firewall 'factory' class has been added that checks which backend packages are installed/enabled when instantiating the SuSEFirewall instance constant. Some of the common functionality has been moved into the factory class, and a basic firewalld module has been added to provide the initial interface between YaST and firewalld. From here, a little augmentation of CWMFirewallInterfaces allowed for the beginnings to support punching holes in the firewalld-based firewall, occurring from our various network service modules (NIS, NTP, NFS). Initial provisioning for unit tests has also been made (no actual tests yet) and investigating SF2 configuration file support is beginning. There was also time spent, very early on, enabling the yast-firewall module to start/stop/enable the two different backends (though this was work done early on to get a feel for YaST development and has not been the focus of late). The next immediate challenges are: 1. Supporting existing /etc/sysconfig/SuSEfirewall2 configuration files Initial thoughts would be to convert as much of these configurations to running firewalld configurations as possible. Conversion would be one-way only (ie. changes made from firewalld would not be reflected in SF2). If firewalld becomes the only solution we support, this would at least allow for smoother adoption. 2. yast-firewall module Keeping in mind that both backends will, for the moment, co-exist, how should our yast-firewall module handle them? Do we leave yast-firewall to allow legacy support for generating SuSEfirewall2 configurations? Do we incorporate "some" support for firewalld? Do we drop yast-firewall altogether? 3. Unit tests While the skeleton for writing firewalld-based unit tests is present, interacting with the firewalld APIs (CLI, etc) require firewalld to be running. How can we leverage the build-time testing infrastructure to support this? 4. dbus Currently, the firewalld support module uses the shell interface. Ultimately, tapping into dbus would be ideal. This is also interesting as we could look into building interfaces with Wicked and allow for firewalld control from within our network management tools. 5. TBD :D If you've read this far and find this work of interest, we'd like to hear from you! Any suggestions, comments or potential for collaboration would be most welcome. If you'd like to have a look at the current state of things, you can find the core stuff here: https://github.com/yast/yast-yast2/compare/master...kmroz:firewalld-oo Regards, Karol

1 0