[yast-devel] Branching day
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@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, 4 Nov 2015 13:20:02 +0100 Ancor Gonzalez Sosa <ancor@suse.de> wrote:
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
SLE12! in both case
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 see in some of these incorrect Rakefile, so please fix it as part of branching. Thanks
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
it is control files. Please branch it so we have history but maintenance work is basically zero, as it is part of iso.
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
Please write mail to jsuchome@suse.com, maybe he want to set up autosubmissions
- yast-docker
Please write mail to fcasteli@suse.com, maybe he want to set up autosubmissions
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
basically dead
- yast-rdp
it is some HA specific stuff I think.
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.
yast-ycp-ui-bindings is yast module not libyui, so I think it make sense to branch it together with other yast modules.
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
this is skelcd for opensuse. already branched, so not affect.
- yast-skelcd-control-openSUSE-openSUSE-42_1
Thats all folks.
Thanks for doing branching so this time it is not upon me :) Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11/04/2015 01:20 PM, Ancor Gonzalez Sosa wrote:
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.
It was a little bit later than expected. But it's done.
[...]
Which repositories are affected =============================== In today's branching it would be these. Please review the list. [...]
All repositories in the stripped huge list got branched (although I still have to fix some minor Rubocop issues in a few repos). From now on, commits to master will be automatically submitted to SP2 and not longer to SP1, as proved by https://build.suse.de/request/show/77855 SLE-12-SP1 branch was created for all of them if you still need to fix stuff there.
The following repos are already branched, as far as I know. Am I missing any? - yast-slide-show - yast-x11 - yast-country
Actually I was missing also yast-security and yast-network. I temporarily disabled the jenkins jobs for those 5 repos. I will enable them again tomorrow in the morning, when we are in front of the computer to fix any issue. I'll let you know when they are operative again.
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
These were also branched as the regular ones.
[...]
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.
This still stands. I hope to branch the libyui stuff tomorrow.
[...]
Thats all folks.
For today. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11/04/2015 06:29 PM, Ancor Gonzalez Sosa wrote:
On 11/04/2015 01:20 PM, Ancor Gonzalez Sosa wrote:
All repositories in the stripped huge list got branched (although I still have to fix some minor Rubocop issues in a few repos).
Issues fixed. The only one that remains failing in Travis is control-center-gnome, but I don't see any connection between the branching and failure. Looks like a mission to somebody understanding some C. https://travis-ci.org/yast/yast-control-center-gnome/builds/89257573 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 4.11.2015 v 18:52 Ancor Gonzalez Sosa napsal(a):
On 11/04/2015 06:29 PM, Ancor Gonzalez Sosa wrote:
On 11/04/2015 01:20 PM, Ancor Gonzalez Sosa wrote:
All repositories in the stripped huge list got branched (although I still have to fix some minor Rubocop issues in a few repos).
Issues fixed. The only one that remains failing in Travis is control-center-gnome, but I don't see any connection between the branching and failure. Looks like a mission to somebody understanding some C.
https://travis-ci.org/yast/yast-control-center-gnome/builds/89257573
The error is: undefined reference to `g_clear_pointer' This has been added in glib version 2.34 [1]. However, the version shipped in Ubuntu 12.04 is 2.32.1 [2]. Therefore in the past I added the ppa:ricotz/testing [3] repository from launchpad (which is something similar to OBS for openSUSE). It contained glib in version 2.34.1 [4]. Now that package is gone and unfortunately in my quick scan I could not find a different repository providing the package... :-( So for now ignore the build errors, later we either find a repo with the required package or we will remove the Travis support completely. [This problem is one of the reasons for the move from Travis to Jenkins and using "osc build" for running the tests.] Ladislav [1] https://developer.gnome.org/glib/stable/glib-Memory-Allocation.html#g-clear-... [2] http://packages.ubuntu.com/precise/libglib2.0-0 [3] https://launchpad.net/~ricotz/+archive/ubuntu/testing [4] https://travis-ci.org/yast/yast-control-center-gnome/builds/78007680#L377 -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, 4 Nov 2015 18:52:04 +0100 Ancor Gonzalez Sosa <ancor@suse.de> wrote:
On 11/04/2015 06:29 PM, Ancor Gonzalez Sosa wrote:
On 11/04/2015 01:20 PM, Ancor Gonzalez Sosa wrote:
All repositories in the stripped huge list got branched (although I still have to fix some minor Rubocop issues in a few repos).
Issues fixed. The only one that remains failing in Travis is control-center-gnome, but I don't see any connection between the branching and failure. Looks like a mission to somebody understanding some C.
https://travis-ci.org/yast/yast-control-center-gnome/builds/89257573
Cheers.
quick look indicate possible issue: 1) old version on ubuntu gnome-control-center.c: In function ‘shell_show_overview_page’: gnome-control-center.c:313:3: warning: implicit declaration of function ‘g_clear_pointer’ [-Wimplicit-function-declaration] CCLD y2controlcenter-gnome gnome-control-center.o: In function `shell_show_overview_page': /home/travis/build/yast/yast-control-center-gnome/src/gnome-control-center.c:313: undefined reference to `g_clear_pointer' gnome-control-center.o: In function `_shell_set_active_panel_from_id': /home/travis/build/yast/yast-control-center-gnome/src/gnome-control-center.c:1062: undefined reference to `g_clear_pointer' First line say that we define on our own method and rest say, that it really does not find it. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11/04/2015 06:29 PM, Ancor Gonzalez Sosa wrote:
On 11/04/2015 01:20 PM, Ancor Gonzalez Sosa wrote:
The following repos are already branched, as far as I know. Am I missing any? - yast-slide-show - yast-x11 - yast-country
Actually I was missing also yast-security and yast-network. I temporarily disabled the jenkins jobs for those 5 repos. I will enable them again tomorrow in the morning, when we are in front of the computer to fix any issue. I'll let you know when they are operative again.
I have just reconfigured and enabled them all. I also triggered new builds. Everything looks fine so far, but keep an eye on those five. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11/04/2015 06:29 PM, Ancor Gonzalez Sosa wrote:
On 11/04/2015 01:20 PM, Ancor Gonzalez Sosa wrote:
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.
This still stands. I hope to branch the libyui stuff tomorrow.
That's also done now. We have SLE-12-SP1 branches for the following repositories: libyui, libyui-qt, libyui-qt-pkg, libyui-qt-graph, libyui-ncurses, libyui-ncurses-pkg. And the master branch should be being submitted to SP2. As usual, we'll need to keep an eye on it for the next commit, just to make sure it works as expected. With that, I declare the SP1 branching done. :-) Now, let's write some documentation. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Ancor Gonzalez Sosa -
Josef Reidinger -
Ladislav Slezak