October 2014 - YaST Development - openSUSE Mailing Lists

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 07 Oct '14

07 Oct '14

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 missing search for program components in priority directories (39 days) https://github.com/yast/yast-core/pull/82 - search proper paths when running .target.yast2 in switched root (bnc#891... (39 days) https://github.com/yast/yast-core/pull/81 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (39 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Added test for reading of .etc.xinetd_conf.services [beware dependencies!] (39 days) https://github.com/yast/yast-yast2/pull/290 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (42 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-rake: - add support to bump version also in dsc file (12 days) https://github.com/yast/yast-rake/pull/9 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (32 days) https://github.com/yast/yast-cio/pull/7 Pending requests in repository yast-fonts: - add test suite (13 days) https://github.com/yast/yast-fonts/pull/1 -- 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] Re: [yast-commit] Build failed in Jenkins: yast-skelcd-control-SLED-SLE-12-GA #625
by Martin Vidner 06 Oct '14

06 Oct '14

This one, and its SLES buddy, has been flooding the yast-commit list, so I have disabled it before we agree how to fix it. I think the way to fix it is actually to create the SLE-12-GA branch for the skelcd-control-SLE[DS] packages. Then we can also fix all the other failures which complain that either the package does not exist in Devel:YaST:SLE-12 or the target project for SR does not exist. (use just osc:commit) On Fri, Oct 03, 2014 at 04:51:23PM +0200, hudson(a)suse.de wrote: > See <http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/625/> > > ------------------------------------------ > Started by an SCM change > Building remotely on yast-head in workspace <http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/> > Checkout:yast-skelcd-control-SLED-SLE-12-GA / <http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/> - hudson.remoting.Channel@4cc4f985:yast-head > Using strategy: Default > Checkout:yast-skelcd-control-SLED-SLE-12-GA / <http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/> - hudson.remoting.LocalChannel@4bbf48f0 > Cloning the remote Git repository > Cloning repository origin > ERROR: Error cloning remote repo 'origin' : Could not clone https://github.com/yast/yast-skelcd-control-SLED.git > ERROR: Cause: Error performing command: git clone --progress -o origin https://github.com/yast/yast-skelcd-control-SLED.git <http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/> > Command "git clone --progress -o origin https://github.com/yast/yast-skelcd-control-SLED.git <http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/"> returned status code 128: Cloning into '<http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/'...> > fatal: could not read Username for 'https://github.com': No such device or address > > Trying next repository > ERROR: Could not clone repository > FATAL: Could not clone > hudson.plugins.git.GitException: Could not clone > at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:977) > at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:908) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154) > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:287) > at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > -- > To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org > For additional commands, e-mail: yast-commit+help(a)opensuse.org > -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 06 Oct '14

06 Oct '14

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 missing search for program components in priority directories (38 days) https://github.com/yast/yast-core/pull/82 - search proper paths when running .target.yast2 in switched root (bnc#891... (38 days) https://github.com/yast/yast-core/pull/81 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (38 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Added test for reading of .etc.xinetd_conf.services [beware dependencies!] (38 days) https://github.com/yast/yast-yast2/pull/290 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (41 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-rake: - add support to bump version also in dsc file (11 days) https://github.com/yast/yast-rake/pull/9 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (31 days) https://github.com/yast/yast-cio/pull/7 Pending requests in repository yast-fonts: - add test suite (12 days) https://github.com/yast/yast-fonts/pull/1 -- 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 03 Oct '14

03 Oct '14

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 missing search for program components in priority directories (35 days) https://github.com/yast/yast-core/pull/82 - search proper paths when running .target.yast2 in switched root (bnc#891... (35 days) https://github.com/yast/yast-core/pull/81 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (35 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Added test for reading of .etc.xinetd_conf.services [beware dependencies!] (35 days) https://github.com/yast/yast-yast2/pull/290 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (38 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-rake: - add support to bump version also in dsc file (8 days) https://github.com/yast/yast-rake/pull/9 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (28 days) https://github.com/yast/yast-cio/pull/7 Pending requests in repository yast-fonts: - add test suite (9 days) https://github.com/yast/yast-fonts/pull/1 -- 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] SLE 12 bugs to be fixed (now)
by Lukas Ocilka 02 Oct '14

02 Oct '14

Hi, As we have discussed on a call, I have got a sorted list of bugs to be fixed at first. Find them in Trello (Backlog (bugs)): https://trello.com/b/njo5td7P/classical-yast This will be a live "document" as priorities might and will change in the future. That's something we can't influence for 100%. Additionally, I have marked these bugs in Bugzilla with: target Milestone: SLES12Maint-Upd. Bugs that were reported for SLED, but valid for SLES, were switched to SLES as we don't have SLED12Maint-Upd as a target yet (WIP). Bye Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management 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] openQA development restarted
by Ancor Gonzalez Sosa 02 Oct '14

02 Oct '14

Looks like some individuals and teams inside SUSE have coincidentally decided to give a hand to openQA development in the following weeks. It seems like a nice opportunity to put the focus into the things we miss for Yast testing. According to a meeting this morning, next goal will be to have openQA running on different architectures. We expect Dinar Valeev to make it run in POWER next week (shouldn't be a big deal). There are also chances of Bernhard Wiedemann putting some effort into bringing the real hardware (kvm2usb) support back. Once we have tests for POWER running succesfully, the next big thing would be aggregate the results of different architectures in just one openQA webUI (right now, workers and webUI must share the filesystem, which means a separate host with its webUI per architecture). The cheap way would be some mechanism for exporting/importing results, so we simply integrate the results of the POWER openQA into the main one. The really good way would be having distributed workers with just one central point for coordination and webUI. The former openSUSE team never had enough time and manpower to do that and always considered this to be a nice use case for SUSE's cloud technologies. Looks like now the Cloud Team, Dinar and some people from QA are eager to help in that regard. The goal of this mail is not only reporting what can we expect from the nearest future, but to collect more ideas. According to our recent thread about integration tests, we also want: - VNC (already implemented, actually). - Resurrect the OCR support. - Use cloud for parallelism and snapshots (already considered, as explained above). - Tree of requirements/snapshots, with information how to get to every state. - Improved debugging capabilities. I'd say that most of them (if not all) are already in the openQA project tracker. But there are way too many things there, so we need to rise the relevant things up. https://progress.opensuse.org/projects/openqav3/issues?per_page=100 So, time for wish-listing :-) Cheers. PS.- Quite some time ago, I did for openQA the same we are doing now for Yast, so if you are looking for a central piece of information about openQA, visit the documentation section of the landing page at http://os-autoinst.github.io/openQA/ -- Ancor González Sosa openSUSE 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 4

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 02 Oct '14

02 Oct '14

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 missing search for program components in priority directories (34 days) https://github.com/yast/yast-core/pull/82 - search proper paths when running .target.yast2 in switched root (bnc#891... (34 days) https://github.com/yast/yast-core/pull/81 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (34 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - add code climate badge (7 days) https://github.com/yast/yast-yast2/pull/297 - Added test for reading of .etc.xinetd_conf.services [beware dependencies!] (34 days) https://github.com/yast/yast-yast2/pull/290 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (37 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-rake: - add support to bump version also in dsc file (7 days) https://github.com/yast/yast-rake/pull/9 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (27 days) https://github.com/yast/yast-cio/pull/7 Pending requests in repository yast-fonts: - add test suite (8 days) https://github.com/yast/yast-fonts/pull/1 Pending requests in repository yast.github.io: - First draft for "how to write tests" for Yast code (5 days) https://github.com/yast/yast.github.io/pull/3 -- 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] Documenting maintenance model
by Josef Reidinger 01 Oct '14

01 Oct '14

Hi, to make thinks more clear and easier to understand also outsider I create document which describe how to submit fixes to maintenance branches. It is now in review[1]. Feel free to post any comment and question you have in pull request. Josef [1] https://github.com/yast/yast.github.io/pull/6 -- 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] SLE modules in openSUSE translation tree
by Alexander Melentev 01 Oct '14

01 Oct '14

Hi everybody! I am one of volunteer translators in opensuse-i18n project. I've just joined this list to clarify one issue with yast translations. As long as I am able to read the archive of this list, SLE YaST and openSUSE YaST do now come from the same master branch. This synchronization has probably lead to the issue in subject. A couple of months ago there was a commit from Lucas with the "latest" *.pot translation templates (which is good and the more often you update them the better) with several new modules, e.g. auth-client, registration, support. I wondered if these modules actually belong to openSUSE distribution or they are needed in SLE only, cause if it is the latter case they should be dropped from openSUSE translations trunk. So I decided to ask the guys in charge - YOU =) Can anybody help me with this question? -- Regards, Minton. -- 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] RFC: yast-rake task for release
by Josef Reidinger 01 Oct '14

01 Oct '14

Hi, maybe some of you still missing old script for tagging git with released version numbers. Or sometimes forgot to update spec file when changing changes file ( like me ). So I propose to add new yast-rake task "release". What it will do: 1) call "osc vc" and stop if user do not specify changes 2) call "rake version:bump" to increase version 3) create git commit with message "release #{version}" 4) tag this commit with version number like "3.1.125" It do not push change. It also require manual "push --tags" as I want to have the very last break, which allows me to check it again before I push it. What do you think about it? I welcome any comments or suggestions before I implement it. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3