October 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] Generic / Repo-specific READMEs at GitHub
by Lukas Ocilka 23 Feb '16

23 Feb '16

Hi, When Christopher was in Prague, a few of us had a brainstorming about the need of having devel-documentation placed directly in a Yast/libstorage/linuxrc repository. There are no doubts that it's one of the most important parts of projects hosted at GitHub. All their howtos mention "create README[.md]" as the very first step. In fact, we'll have new hires in the team and in such situations, good documentation is one of the most important parts. Good documentation goes from very high level to lower and lower level. We have already summarized that in Yast Team Challenges, but the summary doesn't belong to this document as it's too detailed. That's why I'm putting it here as a WIP item and deleting it from that document: --- cut --- The README should at least describe the steps needed for maintenance (for a person without expert knowledge in the area) including: * What is the project good for - what does it actually do (and how), what it cannot do (unsupported scenarios), limitations * Links to the documentation, high level and low level descriptions (e.g. RFC, wikipedia articles, man pages, project documentation, openSUSE wiki), terminology * How to fetch the source code (if something outside Git is needed it should be mentioned) * What prerequisites are needed to build the sources (external libraries, gems, scripts, …) * How to build the sources (make/rake commands…) * How to setup a testing environment (e.g. iSCSI target for iSCSI client) * How to run the code to test a change (esp. needed for non trivial projects like linuxrc) * How to run automated tests * How to build a package for submission * How to submit the package (if it needs some manual steps) * Troubleshooting (how to solve typical problems) The README should be reasonably short, if some section is too long it should be moved to a separate document (or to GitHub wiki) and linked. --- cut --- The project consists of - Taking a decision where to go - How to get there - Implementing this important documentation Those two who, according to my knowledge, were working on this were Ladislav and Christopher, but there were not the only ones and a pilot project for READMEs has been done a few months ago by Martin. It's still not finished, but moving forward. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE 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] new translation server and YaST
by Stanislav Brabec 03 Nov '15

03 Nov '15

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

7 29

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

30 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (8 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (8 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (23 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (6 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (6 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (45 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (6 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (7 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (10 days) https://github.com/yast/autoyast-integration-test/pull/42 - Check Kdump configuration with multiple crashkernel options (6 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

29 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (7 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (7 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (22 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (5 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (5 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-slide-show: - Sle 12 sp1 (9 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (44 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (5 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (6 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (9 days) https://github.com/yast/autoyast-integration-test/pull/42 - Check Kdump configuration with multiple crashkernel options (5 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

28 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (6 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (6 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (21 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (4 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (4 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-slide-show: - Sle 12 sp1 (8 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (43 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (4 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (5 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (8 days) https://github.com/yast/autoyast-integration-test/pull/42 - Check Kdump configuration with multiple crashkernel options (4 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

27 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (20 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-slide-show: - Sle 12 sp1 (7 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (42 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (7 days) https://github.com/yast/autoyast-integration-test/pull/42 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] High level notes about new storage API
by Josef Reidinger 26 Oct '15

26 Oct '15

Hi, let me do some high level user oriented review of new storage API. At first I think it is good that design decisions are documented, which is nice. Also having goals and requirements is documented which is fine to understand some decisions. What I miss is all requirements, I think it would be nice to write down all features old libstorage have and maybe discuss if it still make sense in new libstorage. Now first note. I do not see in decisions why C++ is used as language for this library. I think it would be nice to document it why it is needed as currently from document I see that planned users are machinery ( which use ruby ), Yast (ruby) and kiwi (perl). Is there any performance reasons, availability of bindings, libraries or any other reason to use it? As libstorage basically use CLI of other programs, so question is why not use more high level language. Now lets move to examples. From my user POV there is some confusing API calls and parameters. For example lets use find1.cc as example which I comment (I can do this for all examples). // creating some global storage is fine Devicegraph* devicegraph = new Devicegraph(); // this looks strange for me // 1) how disk can be created? I expect disk is detected or proposed // 2) why saying that disk have "/dev/sda" what if I am on qemu which // have "/dev/vda"? Disk* sda = Disk::create(devicegraph, "/dev/sda"); // this looks fine for me, creating partition table on disk PartitionTable* gpt = sda->create_partition_table(PtType::GPT); // here I do not get why I need to pass "/dev/sda1" ? Let me say it // this way, if I have generic code that generate partition for passed // partition table how I can know if it is hda, sda or vda? and why // I need to know number of partition? cannot it by default create next // available one and pass number as optional parameter? gpt->create_partition("/dev/sda1", PRIMARY); Partition* sda2 = gpt->create_partition("/dev/sda2", PRIMARY); // here I create top level container, looks fine for me LvmVg* system = LvmVg::create(devicegraph, "/dev/system"); // this is very confusing, why I need devicegraph here? Why exposing it // to user? From doc I know that both sda2 and system have reference to // it so why it need to be passed? // And also why it need User::create? Why it is not simple // `system.add(sda2)` call which is more intuitive for me? User::create(devicegraph, sda2, system); // in general it looks fine for me, just is there reason to pass // whole device name? who not having thing like // `system->create_lvm_lv("root")` LvmLv* system_root = system->create_lvm_lv("/dev/system/root"); // creation of filesystem, intuitive and easy Filesystem* filesystem = system_root->create_filesystem(EXT4); // quite confusing, what is adding mountpoint to filesystem? // filesystem do not know about mount points, I expect something like // `devicegraph.mountpoint.add("/", filesystem)` filesystem->add_mountpoint("/"); // some debug output, nothing to comment, not sure if it is needed to // be public methods cout << "num_devices: " << devicegraph->num_devices()<< endl; cout << "num_holders: " << devicegraph->num_holders() << endl; cout << endl; // validation of storage, easy and intuitive... does it raise exception // if failed? devicegraph->check(); // printing of object, fine and intuitive C++ code cout << devicegraph << endl; // printing graphiz image, easy and intuitive API call devicegraph->write_graphviz("test1.gv"); // looking for all filesystems that are mounted as root mountpoint // is confusing. why it do not return single filesystem? for (const Filesystem* filesystem : Filesystem::find_by_mountpoint(devicegraph, "/")) { // I am not sure if I can imagine what is ancestor of filesystem? // I hope there is better name for it // second note is boolean parameter, it is really hard to read it and // hard to remember what such parameter mean. see e.g //http://programmers.stackexchange.com/questions/147977/is-it-wrong-to-use-a-boolean-parameter-to-determine-behavior for (const Device* device : filesystem->get_ancestors(false)) { // this a bit break polymophysm, but it is explained in design // document, so fine for me if (dynamic_cast<const LvmLv*>(device)) cout << "mount point \"/\" somehow uses a logical volume" << endl; } } delete devicegraph; So in general, I think that we should now more focus on API and its usability as it is hard to change it in future. When having good API, some cleaning or refactoring of implementation later is easier ( current code in new libstorage is short and easy, but I worry in future with more features, we need to be prepared to clean it also). I think it make sense to write down an example ( or better test case in something like rspec) for each requirement and talk how its usage looks for target user and if it easy to use and intuitive. Also this examples can be something to show for review for potentional users of library and they can said if it fits their needs or if they missing something. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 13

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

26 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (19 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-slide-show: - Sle 12 sp1 (6 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (41 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository autoyast-integration-test: - Test that network settings are applied (bsc#949193). (6 days) https://github.com/yast/autoyast-integration-test/pull/42 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

23 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (16 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (38 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (28 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (14 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

22 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - More diagnostic info when we get a signal (6 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (15 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (37 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (27 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (114 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (13 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] libstorage-bgl-eval transferred to openSUSE on GitHub
by Arvin Schnell 21 Oct '15

21 Oct '15

Hi, I have just transferred libstorage-bgl-eval on GitHub from aschnell to openSUSE. So the new URL is: https://github.com/openSUSE/libstorage-bgl-eval GitHub is even so cool that it redirects HTTP requests. One note for people trying to compile and check libstorage-bgl-eval: You need a newer version of swig (>= 3.0.3 (with support for C++11 strongly typed enums), released end of 2014) than most SUSE releases provide. AFAIS only Tumblewee/Factory include that version. On Leap swig is utterly outdated (2.0.x). ciao Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (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

2 1

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

21 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (4 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (4 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-core: - More diagnostic info when we get a signal (5 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (14 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (183 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (36 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (26 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (113 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (12 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

20 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (13 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (182 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (35 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (25 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (112 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (11 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] yast2 --qt requires unavailable libyui6
by Felix Miata 19 Oct '15

19 Oct '15

RE: http://lists.opensuse.org/opensuse-factory/2015-10/msg00474.html Is requirement of unavailable libyui6 expected behavior on TW? Shouldn't presence of libyui7 and deps cause removal of libyui6 and deps? Is this a misfortune of following widespread recommendation to use up rather than dup to upgrade TW? # rpmqa yui libyui-ncurses-pkg7-2.48.1-1.1.x86_64 libyui-ncurses6-2.47.2-1.1.x86_64 libyui-ncurses7-2.47.4-1.1.x86_64 libyui-qt-graph6-2.44.3-1.4.x86_64 libyui-qt6-2.46.18-1.3.x86_64 libyui6-3.2.0-1.1.x86_64 libyui7-3.2.3-1.1.x86_64 # yast2 --qt # rpmqa qt | grep y libyui-qt-graph6-2.44.3-1.4.x86_64 libyui-qt6-2.46.18-1.3.x86_64 yast2-control-center-qt-3.1.5-2.3.x86_64 yast2-qt-branding-openSUSE-13.2-11.3.noarch # zypper rm libyui6 Loading repository data... Reading installed packages... Resolving package dependencies... The following 4 packages are going to be REMOVED: libyui-ncurses6 libyui-qt-graph6 libyui-qt6 libyui6 4 packages to remove. After the operation, 3.3 MiB will be freed. Continue? [y/n/? shows all options] (y): y (1/4) Removing libyui-qt-graph6-2.44.3-1.4 ....................................................................................[done] (2/4) Removing libyui-qt6-2.46.18-1.3 .........................................................................................[done] (3/4) Removing libyui-ncurses6-2.47.2-1.1 .....................................................................................[done] (4/4) Removing libyui6-3.2.0-1.1 ..............................................................................................[done] big41:~ # yast2 --qt Qt GUI wanted but not found, falling back to ncurses. # zypper in libyui6 Loading repository data... Reading installed packages... 'libyui6' not found in package names. Trying capabilities. No provider of 'libyui6' found. Resolving package dependencies... Nothing to do. # zypper in libyui-qt7 ... The following NEW package is going to be installed: libyui-qt7 2.46.20-1.1 ... (1/1) Installing: libyui-qt7-2.46.20-1.1 ......................................................................................[done] committingCommitResult (total 1, done 1, error 0, skipped 0, updateMessages 0) # zypper in libyui-qt-pkg7 The following NEW package is going to be installed: libyui-qt-pkg7 2.45.4-1.1 ... (1/1) Installing: libyui-qt-pkg7-2.45.4-1.1 ...................................................................................[done] committingCommitResult (total 1, done 1, error 0, skipped 0, updateMessages 0) # yast2 --qt # -- "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

4 5

[yast-devel] attribution setting error in Yast Disk(portioner)
by Zhu Lingshan 19 Oct '15

19 Oct '15

Hi, I just fixed a bug, https://bugzilla.novell.com/show_bug.cgi?id=950685, it is a attribution setting error in fstab. When add a line in fstab to mount a iSCSI device, lines like this would work: /dev/sda1 /mount/test ext4 _netdev 1 2 While lines like this will fail: /dev/sda /ext3 ext3 acl,user_xattr 1 2 The thing is, it should be set as _nektdev, so that the system would mount it after network service run. I found we also have this bug in Yast Disk (portioner), when we try to mount a iSCSI device in yast disk, we will find it not set the device "_netdev", that will cause the system failed to boot. Shall we fix it? If you are busy, I am happy to do that, please let me know. Thanks BR Zhu Lingshan -- 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 19 Oct '15

19 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (12 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-network: - Cleanup: Put some defaults into Yaml (6 days) https://github.com/yast/yast-network/pull/346 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (181 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-slide-show: - Update Cloud product to current name (11 days) https://github.com/yast/yast-slide-show/pull/13 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (34 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (24 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (111 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (10 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Some notes about new storage API
by Ancor Gonzalez Sosa 16 Oct '15

16 Oct '15

Once upon a time... =================== As part of the PBI titles "Evaluate design of future-proof storage subsystem", I took a look to the content of https://github.com/aschnell/libstorage-bgl-eval/ This mail can be considered to some extend a follow up of previous evaluations and discussions in this mailing list. Most feedback received from those threads has been already taken into account into the current prototype. Thus, some topics discussed there are outdated but some information is still useful. http://lists.opensuse.org/yast-devel/2014-10/msg00045.html http://lists.opensuse.org/yast-devel/2014-12/msg00016.html First impression ================ First thing I noticed in that repository is the lack of information about building and installing. In every github's README I expect to find: (1) how to build the thing, (2) how to compile the inline docs or a link to an up-to-date compiled version, (3) in (open)SUSE related stuff I also expect instructions to download or build a rpm. That being said, I took a look to the Ruby examples and testsuite and in general I liked what I saw a lot. So first of all, congrats for the great work! Only some (maybe too Ruby-centric) comments follow. Casting and Storage.some_method =============================== Things like this look quite un-ruby: tmp1 = devicegraph.find_device(42) assert(Storage.disk?(tmp1)) assert(Storage.to_disk(tmp1)) assert(!Storage.partition_table?(tmp1)) assert_raises(Storage.DeviceHasWrongType { Storage.to_partition_table(tmp1) } I would have expected things like tmp1.disk? tmp1.to_partition_table In fact, I wouldn't expect to have to perform this kind of casts, at most I would expect to do more rubist things like tmp1.is_a?(Storage::Disk) tmp1.respond_to?(:whatever_method) Query interface =============== The API contains methods like these: device_graph.find_device(numeric_id) Storage::BlkDevice.find(device_graph, "/dev/sda") Storage::Filesystem.find_by_mountpoint(device_graph, "/") Storage::Filesystem.find_by_label(device_graph, "someLabel") Questions that come to my mind. a) Is device_graph always an object representing the whole graph? Can I do things like this to restrict the search to a subtree? disk1 = Storage::Disk.find(device_graph, "/dev/sda") sub_graph = disk1.to_device_graph # or maybe sub_graph = device_graph.sub_graph(disk1.sid) # or any other thing that makes sense Storage::Filesystem.find_by_mountpoint(sub_graph, "/") b) Adding find_by_xx at demand over time doesn't look very future-proof. I would prefer to see something like Rails's #find_by, i.e. Storage::Filesystem.find(device_graph, mountpoint: "/") Storage::Filesystem.find(device_graph, mountpoint: "/", label: "blah") Too ruby-centric and not easy to implement in a cross-language way, I guess. But asking does not hurt. :-) c) Just brainstorming. The approach in (b) could be pushed to the limit to have things like this. But actually I'm not sure if it's a good idea, just braindump. device_graph.find(sid: numeric_id) device_graph.find(type: :filesystem, mountpoint: "/") Lack of inline documentation ============================ Right now, the code is the documentation. I have to say that the code is very nicely structured, so it was really easy to me to browse for the methods I wanted to check (and they were all fairly small and understandable as well). But it's time to start adding documentation to the whole thing. Nitpicking: boolean as parameters ================================= This is something that was already mentioned by Martin in one of the mails referred at the top. Calls like this are not 100% obvious sda.descendants(false) It would be nicer to have something like sda.descendants(:direct) or sda.descendants(direct: true) Nickpicking: 42 =============== I found the usage of 42 and 43 for the sids in examples and tests a little bit confusing. I grepped the source code and found that we simply use autoincremental integer to assign the sids starting with 42. Nothing against it, but please make it more obvious (and robust, in case we decide 42 is not cool anymore) in the testsuites. :-) Epilogue ======== That's all folks! -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 19

[yast-devel] openSUSE Leap 42.1build target has been added to YaST:Head
by Ladislav Slezak 16 Oct '15

16 Oct '15

Hi all, yesterday the openSUSE Leap 42.1 RC1 version has been released, to enjoy also the latest YaST packages in the new system I added the 42.1 build target in the YaST:Head OBS repository. The URL of the repository is: http://download.opensuse.org/repositories/YaST:/Head/openSUSE_42.1/ All packages build so I do not expect any problems, but let me know if something does not work as expected... Enjoy! -- 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 16 Oct '15

16 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (9 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (178 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-slide-show: - Update Cloud product to current name (8 days) https://github.com/yast/yast-slide-show/pull/13 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (31 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (21 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-vm: - Fix loading icon (9 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-auth-server: - Drop ca mgm (108 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (7 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Time to Branch SLE 12 SP1, Leap 42.1, and Clean Up?
by Lukas Ocilka 15 Oct '15

15 Oct '15

Hi, At this point, IIUC, we should be fixing just P1s for both SLE 12 and Leap 42.1, but we might have some fixes or we want to do some refactoring and cleanup in spare time for the $next product. So, is it the right time now? Moreover, I've just checked some projects and it seems we need to do cleanup also in branches, see [branches] in e.g.: https://github.com/yast/yast-autoinstallation or https://github.com/yast/yast-registration - there are many left behind after merged PRs. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE 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

3 3

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

15 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - More diagnostic info when we get a signal (8 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (8 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - - fixed typo (variable name and log message) (8 days) https://github.com/yast/yast-installation/pull/315 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (177 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-slide-show: - Update Cloud product to current name (7 days) https://github.com/yast/yast-slide-show/pull/13 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (30 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (20 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-vm: - Fix loading icon (8 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Add AArch64 (6 days) https://github.com/yast/yast-yast2/pull/403 Pending requests in repository yast-auth-server: - Drop ca mgm (107 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (6 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] RSpec is green but... can you spot the problem?
by Martin Vidner 14 Oct '15

14 Oct '15

I've made this mistake today: #!/usr/bin/rspec require "yaml" describe "WTF" do it "works" do filename = "/usr/share/YaST2/data/sndcards.yml" expect { YAML.load_file(filename).to_not raise_error } end end I caught it early because I also ran the test in failing mode (by making a deliberate syntax error in the YAML file). -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

3 3

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

14 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - More diagnostic info when we get a signal (7 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (7 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (7 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-installation: - - fixed typo (variable name and log message) (7 days) https://github.com/yast/yast-installation/pull/315 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (176 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-slide-show: - Update Cloud product to current name (6 days) https://github.com/yast/yast-slide-show/pull/13 - Sle 12 sp1 (7 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (29 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (19 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-vm: - Fix loading icon (7 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Add AArch64 (5 days) https://github.com/yast/yast-yast2/pull/403 - Fail tests if mocked method does not exist (7 days) https://github.com/yast/yast-yast2/pull/381 Pending requests in repository yast-auth-server: - Drop ca mgm (106 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (5 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

13 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - More diagnostic info when we get a signal (6 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (6 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (6 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-installation: - - fixed typo (variable name and log message) (6 days) https://github.com/yast/yast-installation/pull/315 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (175 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-slide-show: - Sle 12 sp1 (6 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (28 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (18 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-vm: - Fix loading icon (6 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Fail tests if mocked method does not exist (6 days) https://github.com/yast/yast-yast2/pull/381 Pending requests in repository yast-auth-server: - Drop ca mgm (105 days) https://github.com/yast/yast-auth-server/pull/21 -- 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 Oct '15

12 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (174 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (27 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (17 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (104 days) https://github.com/yast/yast-auth-server/pull/21 -- 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 09 Oct '15

09 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (171 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (24 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (14 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (101 days) https://github.com/yast/yast-auth-server/pull/21 -- 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] KVM images installed from recent openSUSE builds
by Martin Vidner 08 Oct '15

08 Oct '15

Hi, If you want an image of a system installed from a recent build of openSUSE, you can find it in https://openqa.opensuse.org/ if you know where to look. And these places are the "install-gnome-image" and "textmode-image" tests: For example https://openqa.opensuse.org/tests/87242/asset/8285 is discoverable, ahem, easily, as follows: - https://openqa.opensuse.org/ - "openSUSE Tumbleweed" group: https://openqa.opensuse.org/group_overview/1 - most recent build: https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumblewe… - Colored circle next to the "install-gnome-image" or "textmode-image" tests: https://openqa.opensuse.org/tests/87242 https://openqa.opensuse.org/tests/87241 - "Logs & Assets" tab: (no working link!) - 00087242-gnome_image.qcow2 (5.4 GB) The text mode image is much smaller, 470 MB. To run it, you must use the same drivers as openQA did when installing the image. I used: qemu-kvm \ -m 1024 \ -vga cirrus \ -netdev user,id=qanet0 \ -device virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 \ -drive if=virtio,file=00087242-gnome_image.qcow2 Happy testing! -- Martin Vidner, YaST 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 08 Oct '15

08 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (170 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (23 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (13 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (100 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - [do not merge] Check Kdump configuration with multiple crashkernel options (42 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] leap installer cannot find server from which HTTP installation was initiated
by Felix Miata 07 Oct '15

07 Oct '15

I spent half an hour configuring partitioning and custom package selection and tabooing after a perfectly normal HTTP startup from Grub with source http://mirrors.us.kernel.org/opensuse/distribution/leap/42.1-Current/repo/o… on kernel cmdline. Then when clicking to proceed after finishing selection, "Cannot access installation media". Retries for 20+ minutes are changing nothing, while this PC has no problem accessing the very same URL. This can't be right. Can the installer be kicked somehow to reprobe DNS or something to make it access what clearly *is* accessible, or does Yesterday's upload to the mirrors have a broken installer WRT network 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] Pending Pull Requests
by yast-ci＠opensuse.org 07 Oct '15

07 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (169 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (22 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (12 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (99 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - [do not merge] Check Kdump configuration with multiple crashkernel options (41 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending pull requests
by Josef Reidinger 06 Oct '15

06 Oct '15

Hi, due to not yet known reasons mailx do not send mails on our jenkins worker. So until I fix it I at least send here pending pull request, that we should solve: 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-add-on: - Change deprecated module PackageCallbacksInit for PackagesCallbacks (66 days) https://github.com/yast/yast-add-on/pull/23 Pending requests in repository yast-core: - More diagnostic info when we get a signal (24 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (60 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (126 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-installation: - - fixed typo (variable name and log message) (6 days) https://github.com/yast/yast-installation/pull/315 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (168 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-pkg-bindings: - Use zypp built-in asKind cast rather than assuming Resolvable::Ptr-ty�� (60 days) https://github.com/yast/yast-pkg-bindings/pull/47 Pending requests in repository yast-slide-show: - Sle 12 sp1 (19 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (21 days) https://github.com/yast/yast-storage/pull/155 - don'\''t create btrfs subvolumes outside the root fs (bsc#940797) (11 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-theme: - rename yast-sshd to yast-ssh-server (7 days) https://github.com/yast/yast-theme/pull/58 - Add icons for the MATE patterns (17 days) https://github.com/yast/yast-theme/pull/57 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (131 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-vm: - Fix loading icon (66 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Fail tests if mocked method does not exist (83 days) https://github.com/yast/yast-yast2/pull/381 Pending requests in repository yast-auth-server: - Drop ca mgm (98 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast-docker: - Start making this a gem (138 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository autoyast-integration-test: - [do not merge] Check Kdump configuration with multiple crashkernel options (40 days) https://github.com/yast/autoyast-integration-test/pull/30' Josef -- 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 06 Oct '15

06 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - Change deprecated module PackageCallbacksInit for PackagesCallbacks (66 days) https://github.com/yast/yast-add-on/pull/23 Pending requests in repository yast-core: - More diagnostic info when we get a signal (24 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (60 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (126 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-installation: - - fixed typo (variable name and log message) (6 days) https://github.com/yast/yast-installation/pull/315 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (168 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-pkg-bindings: - Use zypp built-in asKind cast rather than assuming Resolvable::Ptr-ty… (60 days) https://github.com/yast/yast-pkg-bindings/pull/47 Pending requests in repository yast-slide-show: - Sle 12 sp1 (19 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (21 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (11 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-theme: - rename yast-sshd to yast-ssh-server (7 days) https://github.com/yast/yast-theme/pull/58 - Add icons for the MATE patterns (17 days) https://github.com/yast/yast-theme/pull/57 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (131 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-vm: - Fix loading icon (66 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Fail tests if mocked method does not exist (83 days) https://github.com/yast/yast-yast2/pull/381 Pending requests in repository yast-auth-server: - Drop ca mgm (98 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast-docker: - Start making this a gem (138 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository autoyast-integration-test: - [do not merge] Check Kdump configuration with multiple crashkernel options (40 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

05 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - Change deprecated module PackageCallbacksInit for PackagesCallbacks (65 days) https://github.com/yast/yast-add-on/pull/23 Pending requests in repository yast-core: - More diagnostic info when we get a signal (23 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (59 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (125 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (167 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-pkg-bindings: - Use zypp built-in asKind cast rather than assuming Resolvable::Ptr-ty… (59 days) https://github.com/yast/yast-pkg-bindings/pull/47 Pending requests in repository yast-slide-show: - Sle 12 sp1 (18 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (20 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (10 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-theme: - rename yast-sshd to yast-ssh-server (6 days) https://github.com/yast/yast-theme/pull/58 - Add icons for the MATE patterns (16 days) https://github.com/yast/yast-theme/pull/57 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (130 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-vm: - Fix loading icon (65 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Fail tests if mocked method does not exist (82 days) https://github.com/yast/yast-yast2/pull/381 Pending requests in repository yast-auth-server: - Drop ca mgm (97 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast-docker: - Start making this a gem (137 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository autoyast-integration-test: - [do not merge] Check Kdump configuration with multiple crashkernel options (39 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] New package: rubygem-libyui-rake
by Imobach González Sosa 02 Oct '15

02 Oct '15

Hi all, We have a new package, rubygem-libyui-rake, which implement some rake tasks for libyui related projects (just like rubygem-yast-rake does for YaST). The idea is that every libyui package will contain its own Rakefile. For most cases, requiring "libyui/rake" will be enough. If you're feeling curious, take a look at documentation, specially to submit_to method (proposed by Josef), which is likely to be ported to yast- rake. [1] https://github.com/libyui/libyui-rake [2] https://build.opensuse.org/package/show/YaST:Head/rubygem-libyui-rake -- Imobach González Sosa YaST Team at SUSE LINUX GmbH

1 0

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

02 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - Change deprecated module PackageCallbacksInit for PackagesCallbacks (62 days) https://github.com/yast/yast-add-on/pull/23 Pending requests in repository yast-core: - More diagnostic info when we get a signal (20 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (56 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (122 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (164 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-pkg-bindings: - Use zypp built-in asKind cast rather than assuming Resolvable::Ptr-ty… (56 days) https://github.com/yast/yast-pkg-bindings/pull/47 Pending requests in repository yast-slide-show: - Sle 12 sp1 (15 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (17 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (7 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-theme: - Add icons for the MATE patterns (13 days) https://github.com/yast/yast-theme/pull/57 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (127 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-vm: - Fix loading icon (62 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Fail tests if mocked method does not exist (79 days) https://github.com/yast/yast-yast2/pull/381 Pending requests in repository yast-auth-server: - Drop ca mgm (94 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast-docker: - Start making this a gem (134 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository autoyast-integration-test: - [do not merge] Check Kdump configuration with multiple crashkernel options (36 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Text Freeze, SP1
by Lukas Ocilka 01 Oct '15

01 Oct '15

Hi, Texts should be frozen now, if you still really need a text change or a completely new text, please, write to: Shane Wims and Karl Eichwalder. Thanks & Bye Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE 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 01 Oct '15

01 Oct '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - Change deprecated module PackageCallbacksInit for PackagesCallbacks (61 days) https://github.com/yast/yast-add-on/pull/23 Pending requests in repository yast-core: - More diagnostic info when we get a signal (19 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (55 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (121 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (163 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-pkg-bindings: - Use zypp built-in asKind cast rather than assuming Resolvable::Ptr-ty… (55 days) https://github.com/yast/yast-pkg-bindings/pull/47 Pending requests in repository yast-slide-show: - Sle 12 sp1 (14 days) https://github.com/yast/yast-slide-show/pull/9 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (16 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (6 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-theme: - Add icons for the MATE patterns (12 days) https://github.com/yast/yast-theme/pull/57 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (126 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-vm: - Fix loading icon (61 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-yast2: - Fail tests if mocked method does not exist (78 days) https://github.com/yast/yast-yast2/pull/381 Pending requests in repository yast-auth-server: - Drop ca mgm (93 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast-docker: - Start making this a gem (133 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository autoyast-integration-test: - [do not merge] Check Kdump configuration with multiple crashkernel options (35 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0