June 2014 - YaST Development - openSUSE Mailing Lists

[yast-devel] Fixing yast2-slide-show for SLE11 SP3
by Karl Eichwalder 16 Sep '15

16 Sep '15

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 7

[yast-devel] rspec 3.0
by Josef Reidinger 17 Dec '14

17 Dec '14

Hi, in this blog post http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3 is summary of changes in new rspec 3.0. I do not think that we will use it for SLE-12 tests, but maybe it will be used for 13.2. In general I think we should not use new syntax now, but what we can do is to not use deprecated syntax as there is already alternatives to prevent future problems. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 5

[yast-devel] who is the maintainer?
by Arvin Schnell 08 Dec '14

08 Dec '14

Hi, while reassigning yast-maintainers bugs I noticed that once again the maintainer/bugowner information is inconsistent: The content of the MAINTAINER file in git differs from the output of 'osc maintainer' or 'osc bugowner'. This leads to confusion. We had this problem before and apparently fail to solve the inconsistency long term. So I propose to drop the MAINTAINER file in git and rely on osc. Instead we can have a AUTHORS files so that people not knowing about osc can still reach the authors. Regards, Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 10

[yast-devel] Yast Development after SLE 12
by Lukas Ocilka 14 Jul '14

14 Jul '14

Hi, The current Yast code that we will have in SLE 12 is partly automagically translated from YCP to kind of Ruby (also called RYCP), is still using many YCP-like methods for backward compatibility. Partly - because we have already cleaned up some pieces when touching them, following the Boy-Scout Rule [#1] and so the feel quite OK. Of course, we will not be able to cleanup everything we wanted and when SLE 12 is out, we will have to maintain the codebase for years. What we will need is the "Refactoring and Cleanup" (RAC) phase, to be a regular part of the development. Obviously, result of the RAC has to end up in SLE 12 codebase. I've already started talking with the Product Management (PM) and they are more-or-less aligned with this idea. And of course, I'd love to see the RAC in openSUSE as well. For that reason, it might make sense to develop both in the same branch as long as possible (SLE 12 GA maintenance [+ SP1 development?], openSUSE development). I'd like to improve these interconnected areas: - fewer bugs - better test coverage - better code maintainability in the future There are many open questions that need to be brainstormed before we decide and start planning, to name some: - Which parts deserve the refactoring (e.g., those that we often touch, those, that are not understandable anymore, buggy, ...)? Which are your most-favorite ones? - How deep should the refactoring be, we have to keep the current "API", but what should be considered the API as we might be the only users? - As we will have to add testcases for everything we refactor, should we also move code from "clients" and "includes" to libraries to be easier to test? - How and where to run CI tests for all supported branches? - How to measure the success? I'd love to see automatically generated metrics and code coverage. Metrics could help us to identify the most-rotten pieces. - Where and how to run automatic integration tests? Will openQA help? We could build our own installation image the same way we did it for the New Installer, testing this image automatically is just another logical step. - Additional step is to run such tests for all supported products since we have enabled users to install updates during installation - this is connected to refactoring only partly, it's essential even if we haven't refactored a single line of code A few buzzwords for the fun :) - automation (don't do manually what you don't need to do) - unification (DRYing) - standardization (use libraries, don't write it yourself) #1 http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule #2 http://martinfowler.com/articles/workflowsOfRefactoring/ Thanks for your time and I'm looking forward your ideas and opinions 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

8 16

[yast-devel] How to Change Translations after Text Freeze
by Lukas Ocilka 04 Jul '14

04 Jul '14

Hi, Text freeze will be on July 4th, but even after that deadline, we will have an option to change a few strings. It will be used in exceptional cases only! Here's the little howto: - There needs to be a bug in Bugzilla - Change the string in Git and submit the affected package - Generate new pot file (or just change the current one) - Make sure nothing else has changed - Submit new potfile to #SVN - Assign that bug (or copy of the bug) to: Shane Wims (swims(a)novell.com) - Add Karl Eichwalder (ke(a)suse.com) to Cc And that's it! Happy potting ;)! #SVN: https://svn.opensuse.org/svn/opensuse-i18n/branches/SLE12/yast/50-pot Bye Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 3

[yast-devel] Testing AutoYast in openQA
by Lukas Ocilka 30 Jun '14

30 Jun '14

Hi, Ludwig would like to give us a favor and will try to create some AutoYast test case in openQA. This is a great step towards continuous integration testing! Would you, please, help him to get some good AutoYast profile to start with? AutoYast documentation can be found here: (maybe a bit obsolete) http://doc.opensuse.org/projects/autoyast/ (maybe internal only) http://docserv.suse.de/documents/SLES12/SLES-autoyast/ Thanks in advance 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

6 9

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

30 Jun '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-bootloader: - Zipl (6 days) https://github.com/yast/yast-bootloader/pull/109 -- 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 27 Jun '14

27 Jun '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-ldap: - Do not add MenuButton to ButtonBox (13 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (14 days) https://github.com/yast/yast-ldap/pull/16 -- 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 26 Jun '14

26 Jun '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-ldap: - Do not add MenuButton to ButtonBox (12 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (13 days) https://github.com/yast/yast-ldap/pull/16 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (8 days) https://github.com/yast/yast-network/pull/168 -- 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 25 Jun '14

25 Jun '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-control-center-gnome: - ellipsize overlong icon texts and add tooltips, bnc#879959 (5 days) https://github.com/yast/yast-control-center-gnome/pull/11 Pending requests in repository yast-ldap: - Do not add MenuButton to ButtonBox (11 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (12 days) https://github.com/yast/yast-ldap/pull/16 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (7 days) https://github.com/yast/yast-network/pull/168 -- 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] RFC: Yast Team Infrastructure: Yast Jenkins Node
by Lukas Ocilka 24 Jun '14

24 Jun '14

Hi, Today we have an outage of the Yast Jenkins node because of "No space left on device". This is a virtual machine maintained by a team member (including scripts around). It's not the first time this node has died for some reason. https://ci.opensuse.org/computer/yast-jenkins/executors/0/causeOfDeath Thread has died java.io.IOException: No space left on device As this is a core infrastructure of the Yast team and everyone depends on it (as we got used to it and OBS/IBS also expects SRs to be done this way), I would like to change the current rules this way: 1. This is a core infrastructure --> it should run on a Yast-team-owned server (we have a HW ready in server room) 2. Any (core) infrastructure, including scripts, should be owned by Yast team 3. Everything needs to be at GitHub following the same (but stricter) rules for merging changes (continuous deployment from GitHub?) For instance, I'd recommend to require two different LGTMs instead of one as it is now 4. Everything needs to be well documented in a way that "everyone" in the team should be able to recover from such error or even start a new node if something goes really bad 5. Everyone in the team needs to have a root (e.g., via ssh keys) access but not to change anything they do not understand (documentation) 6. We need monitoring, maybe internal IT guys can do that for us and they might have and access to that system for urgent cases as well All this doesn't need to be changed "right now". One little step at the time. Then another. Thanks in advance 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

2 1

[yast-devel] snapper timeline_limit not working as expected...
by Zorn, Sascha 23 Jun '14

23 Jun '14

2 2

[yast-devel] libstorage plans?
by Roman Neuhauser 23 Jun '14

23 Jun '14

hello, Arvin mentioned in libstorage/pull/69 that there are "important and fundamental changes required in libstorage". i'd like to know what you (both Arvin and the team as a whole) plan in this regard? after seeing some real-world problems with libstorage, and from my short venture into its code i'd say the most pressing problem is the cylinder as the base unit for partition positions and sizes, with the broken class hierarchy (dynamic_cast...) distant second. while these two may be the "worst", it does not necessarily make sense to approach them first; it may be easier to postpone that until after some other cleanup is done to make the code clearer. in this regard, libstorage could use wider adoption of C++11 features like "auto" and range-based loops. so, what is your roadmap? -- roman -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

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

20 Jun '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-ldap: - Do not add MenuButton to ButtonBox (6 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (7 days) https://github.com/yast/yast-ldap/pull/16 -- 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 19 Jun '14

19 Jun '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-ldap: - Do not add MenuButton to ButtonBox (5 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (6 days) https://github.com/yast/yast-ldap/pull/16 -- 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 18 Jun '14

18 Jun '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-ldap: - Do not add MenuButton to ButtonBox (4 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (5 days) https://github.com/yast/yast-ldap/pull/16 -- 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] Bugs Priority: Explanation
by Lukas Ocilka 17 Jun '14

17 Jun '14

Hi, I've asked SLE 12 release managers to explain their understanding of priorities for SLE 12m this explanation comes from Thorsten Kukuk: --- cut --- P1: ship stopper for GMC, best all of them are fixed before RC1 P1s are also those bugs, that you cannot fix with a maintenance update P2: should be fixed best before GMC, but can be solved with a maintenance update, too P3: something which can wait for the next service pack P4: fix it if it is easy to fix and you have to touch the package anyway, ignore or reject otherwise P5: release manager had no time to prioritize or important info is missing --- cut --- What needs to be fixed in "the current beta/RC" is marked as "Blocker=yes". Hope this helps. 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] Pending Pull Requests
by yast-ci＠opensuse.org 17 Jun '14

17 Jun '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-network: - Fixed internal error raised when cloning config in AY moduleb (12 days) https://github.com/yast/yast-network/pull/168 -- 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 16 Jun '14

16 Jun '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-network: - Fixed internal error raised when cloning config in AY moduleb (11 days) https://github.com/yast/yast-network/pull/168 -- 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 13 Jun '14

13 Jun '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-network: - Fixed internal error raised when cloning config in AY moduleb (8 days) https://github.com/yast/yast-network/pull/168 -- 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] yast-fonts
by Petr Gajdos 12 Jun '14

12 Jun '14

Hello, JFYI I have just submitted zeroth version of yast-fonts module in: https://github.com/yast/yast-fonts/ Looking forward to your opinions and corrections! Besides: during the development, I saved time to time versions of work done. As the result, I have eleven steps from yast hello world to initial git commit: 0. 'Hello world' and 'Exit' button. 1. Two times 'Hello world' and 'Exit' button in two CWM tabs. 2. Widgets of 'Rendering' Tab. 3. Widgets of 'Prefered Families' Tab. 4. (a) Language selection dialog. (b) Family selection dialog. (c) Embedded bitmap widget logic. (d) Presets button. (e) Split sources to corresponding parts. 5. (a) Read from and write to /etc/sysconfig/fonts-config. (b) Read fc-list command to figure out installed families. 6. Refined Add Family dialog. 7. Check for installed/not installed families. 8. Added help. 9. Logging. 10. Packaging work. They are in very raw state right now, sometimes with debug messages, sometimes with traps. If you find it useful from someone who never wrote yast module and never wrote ruby code before, let me know what to do with it. Petr

2 2

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

11 Jun '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-network: - Fixed internal error raised when cloning config in AY moduleb (6 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-ntp-client: - bnc#881026 - YaST ntp-client: "sync without daemon" not documented in he... (5 days) https://github.com/yast/yast-ntp-client/pull/22 -- 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] Detecting and removing invalid UTF-8 characters
by Ladislav Slezak 10 Jun '14

10 Jun '14

Hi all, this is JFYI, some time ago I fixed a bug where Yast received an invalid UTF-8 sequence in a string from outside (bnc#876459). You can read and write such a string without problems, but if you want to process it by some Ruby methods it will likely throw an exception. For detecting invalid encoding use String#valid_encoding?, for removing String#encode! (see https://github.com/yast/yast-yast2/pull/256/files for details). So if you need to handle such situation in your code then you should know where to look... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- 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] y2makepot updated
by Ladislav Slezak 05 Jun '14

05 Jun '14

Hi all, I just have fixed a compatibility issue when extracting translatable strings from control files (see bnc#881278). So if you want to create a POT file make sure you have the latest yast2-devtools package installed (yast2-devtools >= 3.1.19). -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)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(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 Jun '14

04 Jun '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-network: - Fixed internal error raised when cloning config in AY moduleb (35 days) https://github.com/yast/yast-network/pull/168 -- 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: Integer range in YaST
by Martin Vidner 03 Jun '14

03 Jun '14

> For one of feature I have provide the range from 100000 to > 4294967295 (2^32 -1), current IntField(...) I am not able to > specify, are they any api to mention this range. Hi Suresh, (I am replying to the public ML for the benefit of the general public; please do not discuss world takeover plans here :)) Although Ruby supports arbitrarily large integers with Bignum, and YCP uses 64 bit integers, the UI library uses ordinary 32 bit unsigned integers for the IntField. The scripting API docs don't make that apparent: http://doc.opensuse.org/projects/YaST/openSUSE11.3/tdg/IntField.html but the C++ API does: https://github.com/libyui/libyui/blob/8edc4103fa5e084811c2732132e6206381258… All widgets seem to have this limitation. Adding -Wconversion to the flags of yast2-ycp-ui-bindings reveals that and much more :-/ -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

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

03 Jun '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-network: - Fixed internal error raised when cloning config in AY moduleb (34 days) https://github.com/yast/yast-network/pull/168 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0