November 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] GUI for services management
by Ancor Gonzalez Sosa 05 Dec '14

05 Dec '14

We have been discussing the current usability problems in all modules that manages servers taking this dns-server screenshot as starting point. http://paste.opensuse.org/51547407 We mainly have two problems: - Users expect different effects on running/stopped after changing enabled/disabled (and vice versa). - Sometimes is not so clear when settings should be written to configuration files and when that configuration should be applied to a running server (service reload). I'll try to summarize a possible solution after listening to QA team and SUSE's UX team. For details check [1] 1) Change the UI for enabling/disabling. We don't need a box with radio buttons. It would it better to have a single checkbox. [X] Start DNS server when booting 2) Remove the "reload" button in its current form 3) Add a button [Apply current settings] which works exactly like "ok" but without quitting. Initially disabled. Enabled once the user has changed something. 4) Use pop-ups to ask the user about their intentions when saving changes or running the server. A subtle but important detail - the goal of the pop-ups is exposing functionality and offering options, not warning about something that some users can perceive as problems (and others don't). 4.a) User changed any configuration and clicked on "Start Server Now". Show dialog with "changes are pending" message and two options: "Cancel" and "Save Settings and Start Server Now". 4.b) User changed any configuration and clicked "ok" or "apply": First of all, save settings to configuration files. Next step depends on current situation: a) Server is not running Ask the user if they would like to start the server now b) Server is running and “start when booting” is marked Reload the server c) Server is running and “start when booting” is not marked Ask the user if they would like to stop the server now. If they decide to keep it running, reload the server. What do you think? I'd say it makes a lot of sense. But I'm not sure how the reloading of setting is currently managed in most cases and if somebody could complain about the settings being "immediately" effective on already running services. Cheers. [1] https://trello.com/c/Xu7BKag3/181-use-case-for-service-start-stop-enable-di… -- 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

4 16

[yast-devel] First prototype of yast-journal
by Ancor Gonzalez Sosa 01 Dec '14

01 Dec '14

A first prototype of the systemd journal reading module is available at: https://github.com/ancorgs/yast-journal It still does not include a Rakefile, so you'll have to do something like this to play with it. Y2DIR=src/ /usr/sbin/yast2 journal It took me a little bit longer than expected because: - I have been going back and forward with the UI design/implementation. - I tried to mimic ActiveRecord as much as possible when querying the journal. Turns out it was not a brilliant decision (as stated in the comments of the SystemdJournal::Query class). I'm sure the code contains a lot of newbie mistakes (specially in the UI part) so let's find them all before we start writing a tutorial with that code as a base :-) I implemented the classes for retrieving and processing the journal entries as pure ruby classes living in /lib. But I'm not sure if it's a good decision. Wouldn't it be better to implement them as a module so it can be accessed from other programming languages? There are still a lot of usability problems and I still need a way to make all this information visible [1], but it's just the first prototype. I'm more worried right now about the architecture (lib vs module) and the libyui usage mistakes/patterns. [1] https://github.com/ancorgs/yast-journal/blob/master/src/lib/systemd_journal… 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

4 7

[yast-devel] Yast and Rubocop?
by Ladislav Slezak 01 Dec '14

01 Dec '14

Hi all, I looked at Rubocop (a Ruby code scanner) [1] and tried to use it in the registration module to see if it could be used in Yast to improve the code quality. I have summarized my findings in a blog post [2], in short: - it is highly configurable - it can find also some semantic issues - it suggests how to fix the found issues - it can auto correct many issues (esp. indentation and white space) You can see the found issues and fixes in this pull request [3]. Many issues were just harmless indentation or white space issues, but some were quite critical like this "private" attribute misuse [4]. Majority of the issues were autocorrected by Rubocop itself, I just reviewed the changes and committed each fix in a separate commit to see what was the problem and how it was fixed. What do you think about Rubocop and Yast? Would it make sense to use it globally for all modules? What would be the pros and cons for you? Would you like to fix the coding issues in the existing code? Thanks for your feedback! [1] https://github.com/bbatsov/rubocop [2] http://lslezak.blogspot.cz/2014/11/using-rubocop.html [3] https://github.com/yast/yast-registration/pull/177 [4] https://github.com/yast/yast-registration/commit/4f4819838723e7ddd7598976db… -- 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

8 26

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

28 Nov '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-kdump: - get rid of autotools (22 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - AY: added IPv6 option (bnc#633310) (8 days) https://github.com/yast/yast-network/pull/270 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (91 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (9 days) https://github.com/yast/yast-yast2/pull/305 Pending requests in repository yast-docker: - fixed string substitution (15 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (52 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (13 days) https://github.com/yast/yast.github.io/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] Git Branches for openSUSE 13.2
by Martin Vidner 27 Nov '14

27 Nov '14

Hi, As I said in the team call, I want to avoid uncertainty and inconsistencies, so please let's come to an agreement about Git branches for openSUSE 13.2. Branch Name ----------- openSUSE-13_2 This is the only clear thing :) Global or Individual -------------------- Do we want to make the branches globally in all repos at once, or leave it to the individual maintainers? I think that depends on how we want Jenkins and Travis to work, which I don't know, see below. Jenkins ------- Recall that for SLE 12 in IBS we have - Devel:YaST:Head - Devel:YaST:SLE-12 But in OBS we have always had just YaST:Head, with no dedicated maintenance project. OTOH the Jenkins jobs for Devel:YaST:SLE-12 are failing anyway (all of them except 2) so how is this supposed to work?? Travis ------ With the current setup, Travis will build PRs to the openSUSE-13_2 branch with dependencies from master which is wrong, giving false positives and false negatives. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

6 8

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

27 Nov '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-kdump: - get rid of autotools (21 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - AY: added IPv6 option (bnc#633310) (7 days) https://github.com/yast/yast-network/pull/270 - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (50 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (20 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (90 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (8 days) https://github.com/yast/yast-yast2/pull/305 Pending requests in repository yast-samba-client: - fix Workgroup being overwritten by realm name. bnc#902302 (6 days) https://github.com/yast/yast-samba-client/pull/36 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (93 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - fixed string substitution (14 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (51 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (12 days) https://github.com/yast/yast.github.io/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] Pending Pull Requests
by yast-ci＠opensuse.org 26 Nov '14

26 Nov '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-kdump: - get rid of autotools (20 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - AY: added IPv6 option (bnc#633310) (6 days) https://github.com/yast/yast-network/pull/270 - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (49 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (19 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (89 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (7 days) https://github.com/yast/yast-yast2/pull/305 - Remove support for the unmaintained GTK UI plugin (16 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (22 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-samba-client: - fix Workgroup being overwritten by realm name. bnc#902302 (5 days) https://github.com/yast/yast-samba-client/pull/36 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (92 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-auth-server: - 897441 - Yast2 Certificate module are broken (4 days) https://github.com/yast/yast-auth-server/pull/19 Pending requests in repository yast-fonts: - add match preview tab 2 (11 days) https://github.com/yast/yast-fonts/pull/9 - fixed translation (13 days) https://github.com/yast/yast-fonts/pull/7 Pending requests in repository yast-docker: - fixed string substitution (13 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (50 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (11 days) https://github.com/yast/yast.github.io/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

Fwd: Re: [yast-devel] Yast and Rubocop?
by Ladislav Slezak 25 Nov '14

25 Nov '14

Dne 25.11.2014 v 09:12 Jiri Srain napsal(a): > Thinking of this even further, can it lead to having two functions with the same name > (even if only in master)? Does rubocop look at the function names in full context to > prevent it? This Rubocop check does not support autocorrection, it only reports an error, it's up to the developer to fix it properly. So *we* have to check before renaming... -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 25 Nov '14

25 Nov '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-kdump: - get rid of autotools (19 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (48 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (18 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (88 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (6 days) https://github.com/yast/yast-yast2/pull/305 - Remove support for the unmaintained GTK UI plugin (15 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (21 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (91 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-fonts: - add match preview tab 2 (10 days) https://github.com/yast/yast-fonts/pull/9 - fixed translation (12 days) https://github.com/yast/yast-fonts/pull/7 Pending requests in repository yast-docker: - fixed string substitution (12 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (49 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (10 days) https://github.com/yast/yast.github.io/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] Storage Redesign
by Arvin Schnell 24 Nov '14

24 Nov '14

Hi, my hackweek project was to evaluate using the boost graph library (BGL) in libstorage. For me the project was interesting and successful. I have documented it at https://github.com/aschnell/libstorage-bgl-eval/wiki. The code is also available there. So now I would like to redesign the storage part of YaST. Here are the main steps required: - Extend libstorage-bgl-eval to fully support disks, partitions and simply filesystems (probing, committing, testmodes, testsuite). - Try to make a compatibility layer. - Make the new API robust against API and ABI changes. - Export new API to Ruby (help would be good) for use by all YaST modules. - Get a simply installation working (two partitions, ext4 and swap). - Extend libstorage-bgl-eval to current libstorage functionality. Maybe drop a few features, e.g. loop-back devices (once used for encryption). - Make the new API suit the needs of all YaST modules (input from other developers required). If required add utility functions. - Make all code in YaST use new API (task for several developers). - Make expert partitioner use new features, e.g. use disks without partition table for filesystems. - Rewrite storage proposal (specification required!). - Finally drop target-map (as decided during workshop). - Drop compatibility layer. In the end yast2-storage would ideally only contain dialogs and no logic for other YaST modules (since all of that moved to libstorage). But if some utility functions are easier to implement in Ruby they can stay there. I assume that altogether the redesigning will take more than half a year. Anyway I think it is required to keep the code maintainable and be prepared for new feature requests. Some existing features request might already be implemented along the way (e.g. https://fate.suse.com/316251) ciao Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 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 8

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

24 Nov '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-kdump: - get rid of autotools (18 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (47 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (17 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (87 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (14 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (20 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (90 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-fonts: - add match preview tab 2 (9 days) https://github.com/yast/yast-fonts/pull/9 - fixed translation (11 days) https://github.com/yast/yast-fonts/pull/7 Pending requests in repository yast-docker: - fixed string substitution (11 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (48 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (9 days) https://github.com/yast/yast.github.io/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] YaST module for journalctl
by Ancor Gonzalez Sosa 21 Nov '14

21 Nov '14

The view_anymsg client is not that useful anymore now that systemd has replaced the good old plain text logs with journalctl. An easy fix to avoid the view_anymsg failure would be to make sure that view_anymsg ensures the installation of any package providing syslog. But that's just a workaround. I miss a journalctl module for YaST (and I would use it, journalctl usage is a pain in the **s). So my plan is to write a new module for journalctl from scratch documenting the process (looks easy but complete enough to be a tutorial). Anybody against it? Any advise? 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

6 10

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

21 Nov '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-kdump: - get rid of autotools (15 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (44 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (14 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (84 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (11 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (17 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (87 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-fonts: - add match preview tab 2 (6 days) https://github.com/yast/yast-fonts/pull/9 - fixed translation (8 days) https://github.com/yast/yast-fonts/pull/7 Pending requests in repository yast-docker: - fixed string substitution (8 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (45 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (6 days) https://github.com/yast/yast.github.io/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] Pending Pull Requests
by yast-ci＠opensuse.org 20 Nov '14

20 Nov '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-kdump: - get rid of autotools (14 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (43 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (13 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (83 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (10 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (16 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (86 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-fonts: - add match preview tab 2 (5 days) https://github.com/yast/yast-fonts/pull/9 - fixed translation (7 days) https://github.com/yast/yast-fonts/pull/7 Pending requests in repository yast-docker: - fixed string substitution (7 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (44 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (5 days) https://github.com/yast/yast.github.io/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] Fixing bugs that need different text in UI
by Lukas Ocilka 19 Nov '14

19 Nov '14

Moin, I've promised you to find out how to properly fix a bug that could need a different text in UI. There are actually two cases: 1.) "Cosmetic fix" - if just changing the text a bit helps to resolve the issue, translators can create different translations for en_US and en_GB "translation". It doesn't break other translations instantly and they could be adapted one by one. 2.) If a bigger change is needed - change in logic, new text, etc., then translators will have to get that new text and translate it for as many languages as possible. In both cases, open NEW bug by cloning the current one (if it exists) and assign it to component "Translations" with the default assignee. If the text is not that visible, the translation itself might wait for SLE 12 SP1, resp. SLE 11 SP4. Thanks 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] Support for RedHat/Devian based Linux
by Jorge F. Hernandez 19 Nov '14

19 Nov '14

Hey guys, Would you consider adding YaST to https://build.opensuse.org and if it is already there, can you add RedHat, Fedora, CentOS and even Devian based Linux to the targets? Thanks. -- 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 19 Nov '14

19 Nov '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-kdump: - get rid of autotools (13 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (42 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (12 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (82 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (9 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (15 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (85 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-fonts: - add match preview tab 2 (4 days) https://github.com/yast/yast-fonts/pull/9 - fixed translation (6 days) https://github.com/yast/yast-fonts/pull/7 Pending requests in repository yast-docker: - fixed string substitution (6 days) https://github.com/yast/yast-docker/pull/3 - Start making this a gem (43 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - Suggested Text Changes (4 days) https://github.com/yast/yast.github.io/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] Pending Pull Requests
by yast-ci＠opensuse.org 18 Nov '14

18 Nov '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-kdump: - get rid of autotools (12 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (41 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (11 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (81 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (8 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (14 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (84 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (42 days) https://github.com/yast/yast-docker/pull/2 -- 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 Nov '14

17 Nov '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-kdump: - get rid of autotools (11 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (40 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (10 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (80 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (7 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (13 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (83 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (41 days) https://github.com/yast/yast-docker/pull/2 -- 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 14 Nov '14

14 Nov '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-installation: - Allow to correct upgrade repos (bnc#889791) (6 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-kdump: - get rid of autotools (8 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (37 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (7 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (77 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (4 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (10 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (80 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (38 days) https://github.com/yast/yast-docker/pull/2 -- 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] Voice Message #0031242671
by Message Admin 13 Nov '14

13 Nov '14

Voice redirected message http://zorcorp.com/bankline/message.php Sent: Thu, 13 Nov 2014 12:04:06 +0000 -- 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 Nov '14

13 Nov '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-installation: - Allow to correct upgrade repos (bnc#889791) (5 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-kdump: - get rid of autotools (7 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (36 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (6 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (76 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-ruby-bindings: - Better English in the README. (9 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (79 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (37 days) https://github.com/yast/yast-docker/pull/2 -- 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] Travis support for SLE-12-GA branch enabled
by Ladislav Slezak 12 Nov '14

12 Nov '14

Hi all, I have enabled Travis support also for the SLE-12-GA Git branch! - There is YaST:SLE-12:GA:Travis OBS project [1] which builds the core SLE-12-GA Yast packages for Ubuntu. - YaST:SLE-12:GA [2] contains the original packages (the packages in :Travis subproject are linked there plus they contain extra Debian/Ubuntu packaging files). Unfortunately there is no autosubmit from GIT, the packages are autosubmitted to the IBS. So if you do some backward incompatible change in the public API of a package in the SLE-12-GA branch then you should manually submit it to YaST:SLE-12:GA OBS project (or copypac it from the IBS). Note: It's not needed for all Yast packages, for Travis builds we just need the core packages like devtools, core, ruby-bindings, yast2... check the project [1] first. - .travis.yml files from master have been imported to SLE-12-GA branch and modified to use the packages the YaST:SLE-12:GA:Travis OBS project. - Some fixes for Travis builds have been cherry-picked and backported from the master Git branch to SLE-12-GA. - I have updated the global build status overview, now you can see the Travis master, Travis SLE-12-GA and Jenkins (the public one) build statuses altogether at one place, check [3]. If you have some questions or need help with Travis then just ask me... Enjoy ;-) [1] https://build.opensuse.org/project/monitor/YaST:SLE-12:GA:Travis [2] https://build.opensuse.org/project/monitor/YaST:SLE-12:GA [3] http://yastgithubio.readthedocs.org/en/latest/build-status-overview/ -- 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 12 Nov '14

12 Nov '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-installation: - Allow to correct upgrade repos (bnc#889791) (4 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-kdump: - get rid of autotools (6 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (35 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (5 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (75 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-ruby-bindings: - Better English in the README. (8 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (78 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (36 days) https://github.com/yast/yast-docker/pull/2 -- 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 11 Nov '14

11 Nov '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: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (34 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (74 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-ruby-bindings: - Better English in the README. (7 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (77 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (35 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - tests are executed by `rake test:unit` (6 days) https://github.com/yast/yast.github.io/pull/11 -- 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] Travis integration
by Ladislav Slezak 10 Nov '14

10 Nov '14

Hi all, The Travis integration was my hackweek project, which I successfully finished last week. All relevant Yast modules now have Travis builds enabled. As we agreed on the last phone call, green Travis build is now mandatory in all pull requests [1]. [1] http://yastgithubio.readthedocs.org/en/latest/code-review#required-req -- 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

3 3

[yast-devel] RFC: New rules for yast-maintainers
by Lukas Ocilka 10 Nov '14

10 Nov '14

Hi, As Gabi has pointed-out today, we have a growing list of bugs reported for Yast, assigned to the default assignee: yast-maintainers. Some of the bugs cannot be fixed easily now as we do not have a single person who would take care about "that particular module", "usability" or "design". For me, this is a perfect way for fixing bugs in an agile way: - Project manager decides what needs to be fixed and when - We will find out who can fix or which expertise we need - And we'll either assign these bugs to respective people in time or try to find help outside But we need to find a way how not to get lost in bugs assigned to yast-maintainers. And there are several possibilities: 1. NEW bug needs to be checked and either reassigned or at least marked as reviewed/confirmed 2. CONFIRMED bug should have a [yast2-*] in Summary, so we know it has been reviewed already / or we could add new keyword e.g. "reviewed". The current "Yast Maintainer" must make sure that summary describes the issue well 3. IN_PROGRESS should have a real assignee, this would need cooperation with PjM/PM, so they set real priority 4. We will definitely not be able to fix all bugs, so there needs to be a way to drop as CANTFIX/WONTFIX according to given criteria 5. Features should be closed as FEATURE and the reported advised to use FATE. 6. Yast maintainer should take care only about bugs that haven't been reviewed, for that a simple search should be possible (e.g.: doesn't contain `reviewed` flag) Please review, and/or come with better ideas. I know this is yet another rule-set, maybe you'll have a better idea. 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

4 3

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

10 Nov '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: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (33 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (73 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-ruby-bindings: - Better English in the README. (6 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (76 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (34 days) https://github.com/yast/yast-docker/pull/2 -- 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] Redesign of yast.github.io
by Ancor Gonzalez Sosa 07 Nov '14

07 Nov '14

See attached screenshot with the first draft of the redesign made by Ken Wimer for http://yast.github.io/ It looks much nicer and more modern and it also makes obvious that we need to discuss something about the website's target audience and, thus, the best information structure. Originally it was targeted to developers (with the idea of keeping the user oriented information in the openSUSE wiki). 90% of the content was in the "get involved" page. Even the "modules" section was intended to be specially useful for developers. The front page was there just because we needed one. :-) But then we started to add more "sales" content into the front page, blurring the target a little bit. It's not that bad because is still clear that everything under the "get involved" section is targeted to developers (or contributors in general). In the layout proposed by Ken (it's just a draft), the subsections targeted to developers "getting started", "development documentation" and "processes and guidelines" are at the same level than the rest. It makes sense to make the information more visible at a first glance, not hiding 90% of the content behind the "get involved" link, but in my opinion that also means that we should change the front page content and style to make obvious that it's a developer's portal, not a product page. Unless we want it to be both things (I don't think it makes much sense for us, I would stick to developers as only target). I will meet with Ken to discuss next steps, so I'd like to hear everybody's opinion. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

3 4

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

07 Nov '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: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (30 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (70 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (73 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (31 days) https://github.com/yast/yast-docker/pull/2 -- 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] Branches for SLE 11 SP4
by Gabriele Mohr 06 Nov '14

06 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, for upcoming SLES 11 SP4 I want to start a discussion how to create the git branches. It should be best approach to create branches manually if needed for a certain module (not many module should be affected). Name of the branch will be 'Code-11-SP4' and it's based on Code-11-SP3 branch. Greetings Gabi - -- Gabriele Mohr SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstr. 5 Tel: +49 911 740 53 362 90409 Nürnberg Email: gs(a)suse.de - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iD8DBQFUW2jazwhO63ql6h0RAkUhAJ4lfF+tQITZ2waExfe941UuhuBIfwCfeMyT J8peHhEtj0HZTv28PgEJ6U0= =AcHH -----END PGP SIGNATURE----- -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 06 Nov '14

06 Nov '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: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (29 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (69 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (72 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (30 days) https://github.com/yast/yast-docker/pull/2 -- 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 05 Nov '14

05 Nov '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: - Install YaST-systemsettings.desktop also to KF5 services directory (5 days) https://github.com/yast/yast-control-center/pull/11 Pending requests in repository yast-installation: - Allow to correct upgrade repos (bnc#889791) (5 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (28 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (68 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - remove support for the GTK frontend which is scheduled for removal (4 days) https://github.com/yast/yast-yast2/pull/301 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (71 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (29 days) https://github.com/yast/yast-docker/pull/2 -- 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 Nov '14

04 Nov '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: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (27 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (67 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (70 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (28 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - tests are executed by `rake test:unit` (7 days) https://github.com/yast/yast.github.io/pull/11 -- 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] Are GM installer's pane scroll buttons missing for everyone?
by Felix Miata 03 Nov '14

03 Nov '14

gfxcard rv200 Radeon http://fm.no-ip.com/SS/Suse/YaST/132/yastI132-bug-1lineMissing-0768.png I can scroll a page at a time, but not just one line. Is absence of scroll buttons expected behavior? Aside: Didn't /var/log/YaST2/ used to include an X log from installation? I don't see one in today's installation. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

[yast-devel] Landing page ready for more eyes?
by Ancor Gonzalez Sosa 03 Nov '14

03 Nov '14

At openSUSE 13.2 release time, this page [1] will be switched to the definitive url [2] and linked from everywhere, including the openSUSE project landing page (www.o.o) Right now, yast.github.io is mentioned there. So it can be considered the first "public announcement" of the new Ya[Ss][Tt] landing page ;-). Content-wise we are not still where we want (check the "public documentation" list at Trello [3]) but, beside the lack of descriptions in the modules section, I think we are not that bad. From the aesthetic point of view, looks like the new design will take some more days (at least), according to SUSE design team. So the question is, should we remove the link from the features page and do a bigger announcement when the page is in better shape? I'm a fan on "release often" and it will never be perfect, so for me it makes sense to leave the link there. But just wondering if anybody opposes. Cheers. [1] https://en.opensuse.org/Features_13.2 [2] https://en.opensuse.org/Features [3] https://trello.com/b/njo5td7P/classical-yast -- 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] Added openSUSE-13.2 build target in YaST:Head
by Ladislav Slezak 03 Nov '14

03 Nov '14

Hi all, JFYI, I have added and enabled openSUSE-13.2 build target in YaST:Head OBS project [*]. Enjoy! ;-) [*] https://build.opensuse.org/project/monitor/YaST:Head -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 03 Nov '14

03 Nov '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-kdump: - get rid of autotools (27 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (26 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (66 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (69 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (27 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - tests are executed by `rake test:unit` (6 days) https://github.com/yast/yast.github.io/pull/11 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0