November 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] Branching day
by Ancor Gonzalez Sosa 05 Nov '15

05 Nov '15

Happy SP1 branching day When? ===== Today I'll do the first round of branching for SLE12-SP1 in the yast repositories. 15:00 CET sounds like a good moment for it. So you have a couple of hours to yield before I push the big red button. What I expect from you all? =========================== Just review this mail and point anything that is wrong. What that branching means? ========================== For openSUSE not much. Everything merged into master will be automagically submitted to Factory/Tumbleweed. No change there. For SLE12 things will change, stuff merged into master will not be longer automatically submitted to SUSE:SLE-11-SP1:GA, but to SUSE:SLE-11-SP2:GA Submissions to Leap will continue being coolo's and DimStar's business unless we are told otherwise. So we assume they will take care of keeping SLE12-SP1 and 42.1 in sync using updates or any other mean. What to do if you still want to modify SP1? =========================================== Easy. Just merge your stuff into the SLE-12-SP1 branch. And then, from there, run rake osc:sr That will create the SR targeting SP1 for you. Which repositories are affected =============================== In today's branching it would be these. Please review the list. - yast-add-on-creator - yast-add-on - yast-apparmor - yast-audit-laf - yast-auth-client - yast-auth-server - yast-autoinstallation - yast-boot-server - yast-bootloader - yast-branding - yast-ca-management - yast-cio - yast-cluster - yast-control-center-gnome - yast-control-center - yast-core - yast-dbus-server - yast-devtools - yast-dhcp-server - yast-dns-server - yast-drbd - yast-fcoe-client - yast-firewall - yast-firstboot - yast-ftp-server - yast-geo-cluster - yast-hardware-detection - yast-http-server - yast-inetd - yast-installation - yast-instserver - yast-iplb - yast-iscsi-client - yast-iscsi-lio-server - yast-isns - yast-journal - yast-kdump - yast-ldap - yast-live-installer - yast-mail - yast-metapackage-handler - yast-migration - yast-multipath - yast-network - yast-nfs-client - yast-nfs-server - yast-nis-client - yast-nis-server - yast-ntp-client - yast-online-update-configuration - yast-online-update - yast-packager - yast-pam - yast-perl-bindings - yast-pkg-bindings - yast-printer - yast-product-creator - yast-proxy - yast-rear - yast-registration - yast-reipl - yast-ruby-bindings - yast-s390 - yast-samba-client - yast-samba-server - yast-scanner - yast-schema - yast-security - yast-services-manager - yast-slp - yast-slp-server - yast-snapper - yast-sound - yast-squid - yast-storage - yast-sudo - yast-support - yast-sysconfig - yast-testsuite - yast-tftp-server - yast-theme - yast-transfer - yast-tune - yast-update - yast-users - yast-vm - yast-xml - yast2 The following repos are already branched, as far as I know. Am I missing any? - yast-slide-show - yast-x11 - yast-country I don't know how to proceed with the following repos. I don't understand how they work. Hints? - yast-skelcd-control-SLED - yast-skelcd-control-SLES - yast-installation-control This repositories are NOT branched because they are not under the control of the YaST Team and, thus, are not in ci.suse.de - yast-crowbar - yast-docker This repositories are NOT branched because they are in openSUSE but not in SLE12. I wonder if we should drop them from openSUSE as well - yast-python-bindings - yast-rdp What's next =========== I'll do the same branching for libyui-xx, but first I want to unify the rake tasks in libyui-rake to make them behave exactly how yast-rake does. Expect the branching of libyui-xx and yast-ycp-ui-bindings to happen tomorrow. What I'm hoping not to break ============================ I don't expect the following jobs from ci.suse.de to be affected by the branching. Ping me if I'm wrong - yast-integration-test - yast-needinfo-checker Same for the following jobs from ci.opensuse.org. I don't expect anything needed or affected there: - yast-bootloader-github-push - yast-devtools-github-push - yast-integration-test - yast-needinfo-checker - yast-pull-requests-checker - yast-rake-ci-github-pr - yast-rake-ci-github-push - yast-rake-ci-master - yast-registration-github-pr - yast-registration-github-push - yast-skelcd-control-openSUSE-LangAddOn-master - yast-skelcd-control-openSUSE-master - yast-skelcd-control-openSUSE-openSUSE-42_1 Thats all folks. -- 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

3 7

[yast-devel] Branches for Leap
by Ancor Gonzalez Sosa 05 Nov '15

05 Nov '15

First day after Leap release, first day after branching SP1... first doubt. We have assumed that the "Leap team" will take care of making sure that our fixes for SP1 end in 42.1 as well. In that perfect world we only commit to two branches on the repo (master and SLE-12-SP1). We submit stuff from master to Factory and SP2:GA and stuff from SLE-12-SP1 to SP1:GA or SP1:Update. But there are corner cases, sometimes we need to fix something that only affects Leap. The most obvious example is a YaST package that is only in openSUSE but not in SLE (not 100% of the YaST Leap packages come from SLE). Like this bug. https://bugzilla.suse.com/show_bug.cgi?id=952249 To me, it looks like we also need an openSUSE-42_1 branch in the yast-control-center repo and maybe in some others. We can create them on demand, since there is no automation involved and we probably need to check from which commit branch in a case by case basis. I hope packages coming from TW to be the only corner case for Leap. For bugs in the SLE-12-SP1 branch that only affects Leap I hope the SLE (maintenance) staff will allow us to commit the fixes there and release maintenance updates as long as we don't break SLE in the process, even if they don't fix any real SLE issue. Cheers. -- 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

3 2

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

05 Nov '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-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (14 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (14 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (29 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (9 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-network: - Dropped / moved some of old testsuites (9 days) https://github.com/yast/yast-network/pull/349 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (12 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (12 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (51 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (12 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (13 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (16 days) https://github.com/yast/autoyast-integration-test/pull/42 - Check Kdump configuration with multiple crashkernel options (4 days) https://github.com/yast/autoyast-integration-test/pull/30 -- 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] Why you get a Qt UI in your installation - or not
by Stefan Hundhammer 04 Nov '15

04 Nov '15

This might be instructive for many of us: User deselects yast2-firewall during installation, and he also doesn't get the Qt UI: https://bugzilla.suse.com/show_bug.cgi?id=952169#c19 Bottom line: There are many indirections; there is no direct 'requires', but a number of conditions: You get a yast-qt-ui if the yast2_basis pattern is fulfilled AND you are installing any of the X11 desktops. If any of the yast2_basis requirements is not fulfilled (in this case: no yast2-firewall), you won't get a yast2-qt-ui, and you'll have a hard time tracking down why not. The NCurses UI, however, is required much more often (and not in such complicated ways), so you can be pretty sure that you'll get that one. CU -- Stefan Hundhammer <shundhammer(a)suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 4

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

04 Nov '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-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (13 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (13 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (28 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (8 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-network: - Dropped / moved some of old testsuites (8 days) https://github.com/yast/yast-network/pull/349 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (11 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (11 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-slide-show: - Sle 12 sp1 (5 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (50 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (11 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (12 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (15 days) https://github.com/yast/autoyast-integration-test/pull/42 -- 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] new translation server and YaST
by Stanislav Brabec 03 Nov '15

03 Nov '15

We are now working on a launch of a new translation server: https://l10n.opensuse.org/ We just added first few projects, but we plan to migrate all translations there after the beta phase. Benefits: No more need for picking pot from GitHub, uploading it to LCN SVN, waiting, picking translations back. Weblate is built on top of GIT, and translation can be automatically uploaded to GIT. Imagine that openSUSE LCN SVN has projects, where nobody picked translations for 7 years! Weblate features translation merge across branches. We can create common translation covering both SLE and openSUSE. No more divergences in translations. The only work on developers side is (in the current version) updating of po files against the latest pot and pushing it to the git repo. (And even it can be automatized in future.) What will be needed before YaST can be added to Weblate: 1) Decide how YaST will manipulate with po files. Currently all po files for all repositories reside in a single repository (and later in a single package). It was useful in time of manual downloads and uploads, where no -lang package merging was implemented. Now it will complicate fully automatic work flow, as pot files needs to be transferred across repositories (at least until somebody invents a robot for it). 2) Decide how YaST will accept translations. Standard way is an automatic pushing of translations to git using rules defined by Weblate (currently 100% reached or no changes in last 2 hours) by dedicated user (opensuse-i18n). I was pointed to the problem that YaST developers may need to review some strings and edit their test suites. I guess that there can be techniques that can help with watching of such special changes. But in general, I think that developers have no chance to review translations. Another way is pull request (GitHub only). With pull requests, developers will get pull request on each change mentioned above. Pull request could possibly add a lot of work to you. Imagine, that 50 modules with 16 languages can generate nearly 1000 pull requests in on translation round. Third way is manual pulling from the Weblate on request. I would avoid this as much as possible. If you update po files in GitHub, you will get conflict, and problem would need manual git merge. 3) Have cleanly defined branch for SLE (and possibly other projects). I guess it is already done in a such way: All projects, where translations are maintained in parallel for different versions, need to have branch in the repository. Weblate will then be able to push the correct po file to each branch. 4) Merge openSUSE and SLE translations. openSUSE and SLE translations diverged over the time, as there is no merging process. Translation team agreed on merge of both. The merge is planned to be performed on Weblate side: 3a) GitHub will import openSUSE translations. 3b) Weblate will import SLE translations as change suggestions. 3c) Translators will be asked to perform review. 3d) The standard process will post merged translations to GitHub. Technical details: Steps that need to be done on import to Weblate: 1. The last import from LCN SVN trunk branch will be done. 2. po and pot files will be removed from LCN SVN trunk branch. 3. These translations will be pushed to GitHub (one shot). 4. Weblate web service (in GitHub webhooks) will be added to each project configuration. 5. opensuse-i18n robot will be allowed to push to your project (not needed in case of pull requests) 6. Project will be imported to l10n.opensuse.org 7. master branch will be added to that project 8. The last import from LCN SVN SLE branches. 9. po and pot files will be removed from LCN SVN SLE branches. 10. Particular SLE branches will be added to that project. 11. These translations will be added to Weblate as suggestions. 12. Translators will be asked for review and string merge. 13. When the merge will happen, robot will push merged translations to GitHub. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.com Lihovarská 1060/12 tel: +49 911 7405384547 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 29

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

03 Nov '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-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (12 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (12 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (27 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (7 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-network: - Dropped / moved some of old testsuites (7 days) https://github.com/yast/yast-network/pull/349 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (10 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (10 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (49 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (10 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (11 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (14 days) https://github.com/yast/autoyast-integration-test/pull/42 -- 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 02 Nov '15

02 Nov '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-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (11 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (11 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (26 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (6 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-network: - Dropped / moved some of old testsuites (6 days) https://github.com/yast/yast-network/pull/349 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (9 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (9 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (48 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (9 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (10 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (13 days) https://github.com/yast/autoyast-integration-test/pull/42 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0