June 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] 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] DialogTree screen list manipulation
by Karol Mroz 17 Jul '15

17 Jul '15

Hi folks, Is there any accepted way to dynamically change the listed screens when using a DialogTree? For example, on a button press that changes some state variable, I'd like my dialog tree to update itself to contain a subset of screens, etc. I can easily manipulate the contents of 'screens' passed to the DialogTree.ShowAndRun when someone navigates off the current screen, but changing the screen list _while on the screen_ doesn't behave well. Thanks in advance for any help, Karol

2 2

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

30 Jun '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-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (28 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (70 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (70 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-packager: - Recommended pkgs: Do not offer to install for already installed ones on the first run (6 days) https://github.com/yast/yast-packager/pull/127 Pending requests in repository yast-s390: - [Review] Request from 'schubi2' @ 'yast/yast-s390/review_150611_zfcpc_disk_conifuration' (6 days) https://github.com/yast/yast-s390/pull/31 Pending requests in repository yast-storage: - fix for bsc#919980 (40 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-theme: - Add icons for MATE pattern (40 days) https://github.com/yast/yast-theme/pull/55 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (33 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-yast2: - Recommended pkgs: +PKGMGR_RECOMMENDED -PKGMGR_REEVALUATE_RECOMMENDED (7 days) https://github.com/yast/yast-yast2/pull/373 - Keep routing state when disabling/stopping firewall (13 days) https://github.com/yast/yast-yast2/pull/371 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (40 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-docker: - Start making this a gem (40 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 29 Jun '15

29 Jun '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-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (27 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (69 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (69 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (39 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-theme: - Add icons for MATE pattern (39 days) https://github.com/yast/yast-theme/pull/55 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (32 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-yast2: - Recommended pkgs: +PKGMGR_RECOMMENDED -PKGMGR_REEVALUATE_RECOMMENDED (6 days) https://github.com/yast/yast-yast2/pull/373 - Keep routing state when disabling/stopping firewall (12 days) https://github.com/yast/yast-yast2/pull/371 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (39 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-docker: - Start making this a gem (39 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] SLE-Only Packages?
by Lukas Ocilka 26 Jun '15

26 Jun '15

Hi, I've this information from a SLE release manager (Stefan): There seem to be packages in SLE12 GA that are not in openSUSE:42. Here's a list of packages that are in OBS but not in openSUSE:42: yast2-add-on-creator yast2-all-packages yast2-audit-laf yast2-auth-client yast2-boot-server yast2-branding-openSUSE yast2-cio yast2-cluster yast2-control-center-gnome yast2-dbus-server yast2-dhcp-server yast2-dns-server yast2-drbd yast2-firstboot yast2-ftp-server yast2-geo-cluster yast2-http-server yast2-instserver yast2-iplb yast2-iscsi-lio-server yast2-isns yast2-live-installer yast2-nis-server yast2-online-update-configuration yast2-pkg-bindings-devel-doc yast2-product-creator yast2-rear yast2-registration yast2-reipl yast2-s390 yast2-schema yast2-slide-show yast2-slp-server yast2-squid yast2-support yast2-tftp-server Stefan is looking for suggestions what to do with them. What is openSUSE 42? See https://en.opensuse.org/openSUSE:42 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 4

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

26 Jun '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-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (24 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (66 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (66 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (36 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-theme: - Add icons for MATE pattern (36 days) https://github.com/yast/yast-theme/pull/55 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (29 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-yast2: - Keep routing state when disabling/stopping firewall (9 days) https://github.com/yast/yast-yast2/pull/371 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (36 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-docker: - Start making this a gem (36 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast-migration: - use new registration migration for repositories (7 days) https://github.com/yast/yast-migration/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] RFC: How to adapt /sbin/yast2 for running system and installation
by Lukas Ocilka 25 Jun '15

25 Jun '15

Moin, I've been working on a task to make Linuxrc: DUD=http://path.to/yast2.rpm possible. Problem description ------------------- Right now, /sbin/yast2 script (#1) on a running system either starts the Yast Control Center or a Yast module given as parameter. In inst-sys (installation), this script is replaced by a symlink to YaST2.First-Stage #2 script and additionally /sbin/yast2.ssh also links to YaST2.First-Stage. This is done in installation-images #3. Because of this solution, when yast2.rpm via normal DUD replaces this symlink with script, the Yast Control Center is started instead. Expected Behavior ----------------- When DUD=yast2.rpm is used, Installer should start, not YCC. Proposed Solution ----------------- There are obviously several possibilities how to fix it. Solution 1: - Just ignore it and do not use DUD=*.rpm and build "real" DUD. - IMO not an option Solution 2: - Do not create symlinks in inst-sys - Adapt /sbin/yast2 to check that we are in inst-sys and either call YaST2.First-Stage or continue Solution 3: - Do not create symlinks in inst-sys - Move /sbin/yast2 functionality to some other library/script - Create new /sbin/yast2 that would either call the new script or YaST2.First-Stage, depending on where we are (including all parameters) - This is my favorite Solution 4: - Let Linuxrc start YaST2.First-Stage directly - This has a big disadvantage as users are used to run Linuxrc with startshell=1 and then start yast manually (anyway, it's IMO too big change in "API") Additional Issues ----------------- We don't have a stable mechanism to tell whether we are actually in inst-sys. Steffen suggests to either check that "/usr/src/packages does not exist" or that "/.packages.root is present". We can also check whether /.instsys.config or /linuxrc.config exists. Side note: Yast itself finds out whether we are in installation when WFM.Args contain that info, so we can't use that approach. #1 https://github.com/yast/yast-yast2/blob/master/scripts/yast2 #2 https://github.com/yast/yast-installation/blob/master/startup/YaST2.First-S… #3 https://github.com/openSUSE/installation-images/blob/master/data/root/root.… Please comment, maybe you have a better idea? 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 7

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

25 Jun '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-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (23 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (65 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (65 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (35 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-theme: - Add icons for MATE pattern (35 days) https://github.com/yast/yast-theme/pull/55 Pending requests in repository yast-tune: - appstream: install metainfo.xml file (28 days) https://github.com/yast/yast-tune/pull/13 Pending requests in repository yast-yast2: - Keep routing state when disabling/stopping firewall (8 days) https://github.com/yast/yast-yast2/pull/371 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (35 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 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-migration: - use new registration migration for repositories (6 days) https://github.com/yast/yast-migration/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] Failing to build against Factory
by Imobach González Sosa 24 Jun '15

24 Jun '15

Hi all, I'm unable to build yast-dns-server against Factory. I'm getting this error when running the old testsuite (as you can see in Jenkins[1]): [ 78s] child process exited abnormally [ 78s] Running DnsServerHelperFunctions ... [ 79s] Running Read ... [ 79s] FAIL: Test case failed for Read: [ 79s] Command terminated on signal '11'! The weird thing is that it fails in the same way if I try to build the current version (without my changes) against Factory. On the other hand, it builds just fine against openSUSE_13.2_Update. Also Ancor is having the same problem with yast-yast2[2]. Finally, yast-packager is failing too but the error is different (Ruby interpreter crashing). Any idea? [1] https://ci.opensuse.org/job/yast-dns-server-master/61/console [2] https://ci.opensuse.org/job/yast-yast2-master/261/console [3] https://ci.opensuse.org/job/yast-packager-master/337/console -- Imobach González Sosa YaST Team at SUSE LINUX GmbH

3 2