August 2017 - YaST Development - openSUSE Mailing Lists

[yast-devel] Re: [yast-internal] Version numbers post-SP3 (Factory / SLE-15)
by Imobach Gonzalez Sosa 09 Aug '17

09 Aug '17

On 08/09/2017 01:19 PM, Stefan Hundhammer wrote: > > The SP3 branch uses 3.2.x . > > When we keep using 3.2.x in master as well, we need to start using a > fourth digit in that branch: 3.2.x.1 etc. > > Since we are not targeting a new product, we might want to bump one of > the numbers in master: > > (a) Start with 3.3.1 > > (b) Start with 15.xxx as Jiri suggested: > (b1) 15.1 ? > (b2) 15.0.1 ? > (b3) 15.1.1 ? I like this one. We could use the first number (which is somehow fixed right now) so it will be crystal clear which is the next number to use. 15.0.x SLE 15 SP0 15.1.x SLE 15 SP1 15.2.x SLE 15 SP2 ... (We can use "4" if you do not like "15") == Bumping versions == The controversial point is when to bump those numbers and, after discussing it with Ancor and Ivan, we have reached some kind of agreement. Let's say SLE 15 (SP0) was already released and let's say we have a package yast2-example 15.0.0. Moreover, we have a SLE-15 branch in our repositories. * Every fix/change that goes as a MU, will go to branch SLE-15 and it will increment the last number (15.0.1, 15.0.2, etc.). Of course, all those changes will be merged into master but we'll keep the same number as far as we do not diverge. * The first change that introduces a divergence between SLE-15 and master branches should bump the second number: 15.1.0 (SLE 15, SP1). Fast forward: SLE 15 SP3 was released. Current yast2-example version is 15.1.5 (the package has not diverged since SLE 15 SP1). If I want to introduce a fix in the SLE-15-SP3 branch, I would bump to 15.3.0. Note that I've just ignored 15.2.x completely. So the second number will indicate the last SPX where the package diverged. 15. | +------> SP where the package diverged +------> Major SUSE version (4, 5, 15... whatever we decide) == Releasing a new open(SUSE) version == Let's suppose that, after SLE 16 has been released, we are going to publish SLE 15 SP4. I *guess* that it should be based on SLE 15 SP3. master -> 16.0.0 SLE-15-SP4 -> 15.4.0 (if already diverged from SLE 15 SP3) SLE-15-SP3 -> 15.3.X SLE-15-SP2 -> 15.1.5 (if it has not diverged since SP1) SLE-15-SP1 -> 15.1.5 SLE-15-SP0 -> 15.0.2 (for instance). Our 2 cents. Regards, Imo -- Imobach González Sosa YaST team at SUSE LINUX GmbH Blog: https://imobachgs.github.io/ Twitter: @imobachgs

1 1

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 09 Aug '17

09 Aug '17

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-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (182 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-apparmor: - Remove perl code dependency (5 days) https://github.com/yast/yast-apparmor/pull/17 Pending requests in repository yast-bootloader: - [WIP] add test to simulate double entry write (6 days) https://github.com/yast/yast-bootloader/pull/450 - Use shared RSpec examples for CWM widgets (19 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (126 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-country: - Casp merge sp2 (5 days) https://github.com/yast/yast-country/pull/128 Pending requests in repository yast-installation: - Adapt InstPreInstall to storage-ng (11 days) https://github.com/yast/yast-installation/pull/588 - Disable plymouth by a no affend method, it will not block tty device activation at first time user login(bsc#1042554). (32 days) https://github.com/yast/yast-installation/pull/584 Pending requests in repository yast-kdump: - Caasp merge (4 days) https://github.com/yast/yast-kdump/pull/89 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (126 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-live-installer: - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (55 days) https://github.com/yast/yast-live-installer/pull/15 - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (55 days) https://github.com/yast/yast-live-installer/pull/14 Pending requests in repository yast-mail: - [WIP] return back MailTable to yast2-mail module from yast2 module (125 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-multipath: - fix ycp killing bug with changing \r with space (43 days) https://github.com/yast/yast-multipath/pull/19 Pending requests in repository yast-network: - Caasp merge (4 days) https://github.com/yast/yast-network/pull/546 - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (98 days) https://github.com/yast/yast-network/pull/503 Pending requests in repository yast-ntp-client: - Caasp merge (4 days) https://github.com/yast/yast-ntp-client/pull/94 Pending requests in repository yast-packager: - Caasp merge (4 days) https://github.com/yast/yast-packager/pull/259 - [WIP] Ask when the added repository is unsigned (bsc#1009127) (181 days) https://github.com/yast/yast-packager/pull/230 Pending requests in repository yast-registration: - Caasp merge (4 days) https://github.com/yast/yast-registration/pull/328 Pending requests in repository yast-schema: - Caasp merge (4 days) https://github.com/yast/yast-schema/pull/29 Pending requests in repository yast-security: - [WIP] refactoring autoconverted ruby code into ruby code (118 days) https://github.com/yast/yast-security/pull/40 ERROR: API query limit exceeded -- 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 08 Aug '17

08 Aug '17

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-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (181 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (18 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (125 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-installation: - Adapt InstPreInstall to storage-ng (10 days) https://github.com/yast/yast-installation/pull/588 - Disable plymouth by a no affend method, it will not block tty device activation at first time user login(bsc#1042554). (31 days) https://github.com/yast/yast-installation/pull/584 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (125 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-live-installer: - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (54 days) https://github.com/yast/yast-live-installer/pull/15 - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (54 days) https://github.com/yast/yast-live-installer/pull/14 Pending requests in repository yast-mail: - [WIP] return back MailTable to yast2-mail module from yast2 module (124 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-multipath: - fix ycp killing bug with changing \r with space (42 days) https://github.com/yast/yast-multipath/pull/19 Pending requests in repository yast-network: - Use proper API for querying device name during AY installation (6 days) https://github.com/yast/yast-network/pull/543 - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (97 days) https://github.com/yast/yast-network/pull/503 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (180 days) https://github.com/yast/yast-packager/pull/230 Pending requests in repository yast-security: - [WIP] refactoring autoconverted ruby code into ruby code (117 days) https://github.com/yast/yast-security/pull/40 ERROR: API query limit exceeded -- 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 07 Aug '17

07 Aug '17

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-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (180 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (17 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (124 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-installation: - Adapt InstPreInstall to storage-ng (9 days) https://github.com/yast/yast-installation/pull/588 - Disable plymouth by a no affend method, it will not block tty device activation at first time user login(bsc#1042554). (30 days) https://github.com/yast/yast-installation/pull/584 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (124 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-live-installer: - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (53 days) https://github.com/yast/yast-live-installer/pull/15 - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (53 days) https://github.com/yast/yast-live-installer/pull/14 Pending requests in repository yast-mail: - [WIP] return back MailTable to yast2-mail module from yast2 module (123 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-multipath: - fix ycp killing bug with changing \r with space (41 days) https://github.com/yast/yast-multipath/pull/19 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (96 days) https://github.com/yast/yast-network/pull/503 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (179 days) https://github.com/yast/yast-packager/pull/230 Pending requests in repository yast-security: - [WIP] refactoring autoconverted ruby code into ruby code (116 days) https://github.com/yast/yast-security/pull/40 ERROR: API query limit exceeded -- 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] Defensive programming or "it doesn't change that often"?
by Lukas Ocilka 04 Aug '17

04 Aug '17

Dear Developers, I've just seen another PR fixing `The World Has Changed` issue at https://github.com/openSUSE/installation-images/pull/192 It's indeed a simple fix, no brainer, but it's not the first time I see such fix. That again raised a question that comes to my mind from time to time: Should YaST blindly write "something somewhere and just wish that it will work"? There is another way - Defensive Programming which checks that what we write actually makes sense/exists/... In this case, we would check whether the directory in question exists and ... either report an error and skip writing or write some default value if it doesn't. That would make the code much more robust. Another example is for instance setting the default systemd target (recent bug). What is a problem is that we'd sometimes need to know a bit more about the system/solution, e.g. which directory to check. Robust code makes also debugging easier and if path changes, we would find out the next time openQA runs the test. What's your opinion? Thx 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

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 04 Aug '17

04 Aug '17

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-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (177 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (14 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (121 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-installation: - Adapt InstPreInstall to storage-ng (6 days) https://github.com/yast/yast-installation/pull/588 - Disable plymouth by a no affend method, it will not block tty device activation at first time user login(bsc#1042554). (27 days) https://github.com/yast/yast-installation/pull/584 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (121 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-live-installer: - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (50 days) https://github.com/yast/yast-live-installer/pull/15 - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (50 days) https://github.com/yast/yast-live-installer/pull/14 Pending requests in repository yast-mail: - [WIP] return back MailTable to yast2-mail module from yast2 module (120 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-multipath: - fix ycp killing bug with changing \r with space (38 days) https://github.com/yast/yast-multipath/pull/19 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (93 days) https://github.com/yast/yast-network/pull/503 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (176 days) https://github.com/yast/yast-packager/pull/230 Pending requests in repository yast-security: - [WIP] refactoring autoconverted ruby code into ruby code (113 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-storage: - Bsc 1049108 sle12 sp3 (14 days) https://github.com/yast/yast-storage/pull/283 - Propose /boot for encrypted root on PowerPC (120 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-tune: - add docker to sle12sp2 (22 days) https://github.com/yast/yast-tune/pull/23 Pending requests in repository yast-users: - Reduce perl (121 days) https://github.com/yast/yast-users/pull/137 Pending requests in repository yast-vm: - Issue 19 tumbleweed (59 days) https://github.com/yast/yast-vm/pull/20 ERROR: API query limit exceeded -- 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] Review Request: yast-apparmor
by Goldwyn Rodrigues 03 Aug '17

03 Aug '17

Hi, I understand you get a list of projects pending review. I am sending this across as a gentle reminder for its dependency on FATE#323380. -- Goldwyn -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 3

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 03 Aug '17

03 Aug '17

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-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (176 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-apparmor: - Remove perl code dependency (5 days) https://github.com/yast/yast-apparmor/pull/17 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (13 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (120 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-installation: - Adapt InstPreInstall to storage-ng (5 days) https://github.com/yast/yast-installation/pull/588 - Disable plymouth by a no affend method, it will not block tty device activation at first time user login(bsc#1042554). (26 days) https://github.com/yast/yast-installation/pull/584 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (120 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-live-installer: - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (49 days) https://github.com/yast/yast-live-installer/pull/15 - - Use /etc/products.d/openSUSE.prod as /etc/products.d/baseproduct (49 days) https://github.com/yast/yast-live-installer/pull/14 Pending requests in repository yast-mail: - [WIP] return back MailTable to yast2-mail module from yast2 module (119 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-multipath: - fix ycp killing bug with changing \r with space (37 days) https://github.com/yast/yast-multipath/pull/19 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (92 days) https://github.com/yast/yast-network/pull/503 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (175 days) https://github.com/yast/yast-packager/pull/230 Pending requests in repository yast-security: - [WIP] refactoring autoconverted ruby code into ruby code (112 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-storage: - Bsc 1049108 sle12 sp3 (13 days) https://github.com/yast/yast-storage/pull/283 - Propose /boot for encrypted root on PowerPC (119 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-tune: - add docker to sle12sp2 (21 days) https://github.com/yast/yast-tune/pull/23 Pending requests in repository yast-users: - Reduce perl (120 days) https://github.com/yast/yast-users/pull/137 ERROR: API query limit exceeded -- 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] PoC: Running integration tests / smoke tests at Travis
by Ladislav Slezak 02 Aug '17

02 Aug '17

Hi all, Short Background ----------------- I fixed a trivial bug in the Rear YaST module [1]. The module did not work at all and crashed with "Internal error" right at the start because some files were missing in the RPM package. The nasty thing is that the bug was unnoticed for 6(!!) months. And we got a bug report just after the SP3 was released... :-( Improving it ------------ So I was thinking how to improve the situation, if anybody did a smoke test and just try to run the module the bug would have been found. That means we would need an integration test. openQA was my first idea but it's hard to maintain and we would get the result too late. But since we use Docker at Travis and we already build the YaST packages there then it should be easy to install the package and run it. Proof of Concept ---------------- I have implemented a trivial openQA equivalent using the "tmux" package which is similar to "screen". That means the tests are run using the ncurses UI which is lightweight and should work fast in Travis. Currently I can dump the screen to the Travis log (see the examples below) check what's on the screen, send keyboard presses and navigate in the workflow. For the rear module I can verify that the module starts properly, I can even change a value in the configuration, save it and then start the module again to verify it has been saved properly. This initial run shows that the module is broken [1] and displays the "Internal error" popup as reported in bugzilla. After merging the fix [2] it runs properly and runs the save and load workflow as expected, check the screen dumps in the log [3]. The integration test is implemented in a shell script [4]. It's still just a proof of concept, there are a lot of TODOs, the structure does not look nice, some functions should be moved to a separate shared file, etc... But it really shows that it could improve the test automation a lot. Advantages ---------- - Runs at Travis, the tests are run early, even _before_ we actually merge the change - Uses ncurses UI and simple "grep", no fragile screenshot comparing (It's still not ideal, but should be good enough at this point.) - You can run the same tests locally using the same Docker image => easy debugging, stable environment (more or less) - Writing smoke tests is easy even for legacy modules Disadvantages ------------- - Cannot run full installation, only modules in the installed system - So AutoYaST cannot be tested as well. On the other hand AY allows system cloning and can apply a profile to the running system so we could at least partly test the AY functionality at Travis. And many modules support interactive "configuration" mode. - Docker is container based, no HW virtualization provided, that means it cannot test HW related modules. But we can still run at least simple smoke tests that verify the module starts and displays "No printer detected" or something like that. That still makes sense. TODO/Ideas ---------- - The common functions should be shared (in yast2-devtools?), add helpers for common testing scenarios. - A shell script might not be the best tool, maybe rspec or serverspec [5] might be better. On the other hand a simple shell script has less dependencies and could be easily shared with openQA. It could run the same tests to ensure YaST still works when the external dependencies are changed. - For mocking the external tools in complex scenarios we could use shellmock [6]. What do you think about it? Any ideas, comments? Thank you in advance! [1] https://travis-ci.org/yast/yast-rear/builds/259803414#L681 [2] https://github.com/yast/yast-rear/pull/7 [3] https://travis-ci.org/yast/yast-rear/builds/260086828#L670 [4] https://github.com/yast/yast-rear/pull/8 [5] http://serverspec.org/ [6] https://github.com/gooddata/shellmock -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 4

[yast-devel] yast-rake update: send SP3 and Leap 42.3 to :Updates
by Ladislav Slezak 02 Aug '17

02 Aug '17

Hello, SLE-12-SP3 and Leap 42.3 have been released so I have updated the YaST rake tasks to submit to :Updates OBS projects now. Fixed in yast-rake-0.2.17 [1], you can install the package from YaST:Head [2] as usually. [1] https://github.com/yast/yast-rake/pull/44 [2] https://build.opensuse.org/project/show/YaST:Head -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0