January 2016 - YaST Development - openSUSE Mailing Lists

[yast-devel] HOWTO: Screencast recording
by Ladislav Slezak 22 Jul '17

22 Jul '17

Hi all, Yesterday I published a short blog post about recording a screencast (a desktop session) to create a video or an animated image. So if you want to have nice animated images in READMES [1] or in pull requests [2] then check this post [3]. Enjoy! [1] https://github.com/lslezak/build-rake/blob/master/README.md [2] https://github.com/yast/yast-registration/pull/240 [3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html -- 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

2 2

[yast-devel] before I file another bug about font sizes...
by Felix Miata 21 Oct '16

21 Oct '16

...I want to make sure there is a solution that I simply have not yet found. Expected (OK) fonts results (e.g.): sw_single @120 DPI in KDE3 on 13.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOK131kde3-120.png sw_single @132 DPI in KF5 on TW: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOKtwkde5-132.png Not expected (undersized) fonts results (e.g.): sw_single @108 DPI in TDE on 13.2: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall132tde-108.png sw_single @120 DPI in KDE3 on 42.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-120.p… sw_single @168 DPI in KDE3 on 42.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-168.p… Clearly sw_single (and other y2 apps) post-13.1 (except in KF5) is using smaller fonts than those used in the y2 control center and in the rest of DE UI, as if both the non-KF5 DE's font settings and QT's font setting in Trolltech.conf are being disregarded. Is there something that can be installed or removed to bring up font sizes to match the rest of the DE and y2cc in KDE3 and TDE without loading the installation with QT5 and/or KF5, or even with QT5 and/or KF5? Or, is this a bug that's already been filed, or one that needs filing? -- "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

3 4

[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] installer can't find existing BIOS partitions
by Felix Miata 29 Jan '16

29 Jan '16

Athlon XP (32bit) I just tried twice with TW 20160126 to initialize installation. At suggested partitioning screen: No automatic proposal possible. Specify mount points manually in the 'Partitioner' dialog. YaST claims no partitions on sda, an "unused" device. On vtty2, results from fdisk (30 partitions on 160G HD[1]) and mount (success with two ext3 filesystems tried) are totally as expected. lsmod | grep ata shows ata_generic, pata_via and libata. Is this a known problem? Any way to restart YaST without reboot? This system is taking about 8 minutes to boot to the initial license screen. The installed 11.2, 11.4, 12.1, 12.2, 12.3, 13.1, 13.2, TW and Fedoras on it are/were all behaving normally when last tried. Dmesg inexplicably lists lots of floppy I/O errors and mentions of device-mapper and raid6, plus one each raid6, raid5, raid4, raid10. Also listed are all of sda1-sda30. Is this worth a bug report? logs: http://fm.no-ip.com/Tmp/SUSE/Factory/y2ltwkt400.tgz [1] http://fm.no-ip.com/Tmp/SUSE/Factory/kt400L14.txt -- "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

3 2

[yast-devel] New UI::InstallationDialog class in yast2.rpm
by Ancor Gonzalez Sosa 29 Jan '16

29 Jan '16

I sent this mail yesterday, but I have just realized it never reached the list. Retrying. Just for your information, we have a new class in yast2 to simplify the development of installation screens. It's a specialization of the already existing UI::Dialog and can be found here. http://www.rubydoc.info/github/yast/yast-yast2/UI/InstallationDialog As you can see in that documentation, defining new dialogs for installation is quite clean. You can see a real example here: https://github.com/yast/yast-users/blob/master/src/lib/users/dialogs/encryp… Enjoy. -- 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

1 0

Re: [yast-devel] y2r again -- success!
by Erico Mendonca 29 Jan '16

29 Jan '16

Got it! I managed to convert my module to Ruby using y2r. Here’s what I did: 1) install openSUSE 13.1 from scratch (don’t forget to add C/C++ development tools) 2) install all updates and reboot (important! there’s a newer yast2-core in the “oss” repo.) 3) install some needed packages: # zypper in ruby-devel libxml2-devel libxslt-devel unsquashfs 4) extract y2r-master.zip (from https://github/yast/y2r) and run (as root): # gem install y2r (beware that it needs to download some sources from the internet) 5) extract the base installation media root image: # unsquashfs <openSUSE 13.1 DVD mount point>/boot/x86_64/root This will create a “squashfs-root” directory. It contains all possible YaST modules that may be referenced in the code. 6) run y2r: # y2r2.0 -M squashfs-root/usr/share/YaST/modules <your YCP module> And the magic happens. Now on to debug the Ruby code :) Erico M. Mendonça Dedicated Support Engineer SUSE Rua Joaquim Floriano, 466 – Ed. Corporate 12º andar, Itaim Bibi – São Paulo – SP / Brasil Tel: +55 (11) 3345-3900 Cel: + 55 (61) 8594-9557 erico.mendonca(a)suse.com www.suse.com Em [DATE], "[NAME]" <[ADDRESS]> escreveu: >On Wed, 27 Jan 2016 20:05:19 +0000 >Erico Mendonca <Erico.Mendonca(a)suse.com> wrote: > >> Hello all, >> >> I finally had time to try converting my YCP module again. As >> mentioned earlier, I had to upgrade my yast2-core to something after >> 2.24.x. I tried upgrading just this package on openSUSE 12.3 (using >> the package from 13.1), but apparently it___d break a LOT of stuff. >> >> I decided to try upgrading the whole system to 13.1, recompiled >> y2r___ and now it fails further while trying to load LibStorage.so. I >> tried feeding it the LibStorage.so from the installation image via >> LD_PRELOAD, but got an ___undefined symbol: PL_thr_key___ error. >> Since the installation image used Perl 5.16.2 and I am now on Perl >> 5.18, I downgraded Perl to 5.16 with the same results. >> >> I saw in another forum that this missing symbol indicates that >> this .so module was compiled in a pthread-enabled Perl interpreter, >> and the one supplied with the system is not, which I find odd. Where >> can I find the source to LibStorage.so so I can recompile it, or is >> there a way to skip loading it in y2r? > >No, there is no way to skip it, but it looks like strange upgrade way, >as in 13.1 we do not get such bug report. > >> >> >> Erico M. Mendon__a >> Dedicated Support Engineer >> SUSE >> Rua Joaquim Floriano, 466 ___ Ed. Corporate 12__ andar, Itaim Bibi >> ___ S__o Paulo ___ SP / Brasil Tel: +55 (11) 3345-3900 >> Cel: + 55 (61) 8594-9557 >> erico.mendonca(a)suse.com >> www.suse.com >> N_____r__y___\___^__~_{.n_+__________?_r__i_m__0________-u____0_________ >-- >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 29 Jan '16

29 Jan '16

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-autoinstallation: - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (14 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (114 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (94 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-kdump: - Fix handling of crashkernel parameter for Xen (6 days) https://github.com/yast/yast-kdump/pull/59 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (55 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (57 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Ported support for LVM proposal setting from SP1 to Master (36 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (37 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-auth-server: - Drop ca mgm (8 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (62 days) https://github.com/yast/yast.github.io/pull/55 -- 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 UI::InstallationDialog class in yast2.rpm
by Ancor Gonzalez Sosa 28 Jan '16

28 Jan '16

Just for your information, we have a new class in yast2 to simplify the development of installation screens. It's a specialization of the already existing UI::Dialog and can be found here. http://www.rubydoc.info/github/yast/yast-yast2/UI/InstallationDialog As you can see in that documentation, defining new dialogs for installation is quite clean. You can see a real example here: https://github.com/yast/yast-users/blob/master/src/lib/users/dialogs/encryp… Enjoy. -- 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

1 0

[yast-devel] y2r again
by Erico Mendonca 28 Jan '16

28 Jan '16

Hello all, I finally had time to try converting my YCP module again. As mentioned earlier, I had to upgrade my yast2-core to something after 2.24.x. I tried upgrading just this package on openSUSE 12.3 (using the package from 13.1), but apparently it’d break a LOT of stuff. I decided to try upgrading the whole system to 13.1, recompiled y2r… and now it fails further while trying to load LibStorage.so. I tried feeding it the LibStorage.so from the installation image via LD_PRELOAD, but got an “undefined symbol: PL_thr_key” error. Since the installation image used Perl 5.16.2 and I am now on Perl 5.18, I downgraded Perl to 5.16 with the same results. I saw in another forum that this missing symbol indicates that this .so module was compiled in a pthread-enabled Perl interpreter, and the one supplied with the system is not, which I find odd. Where can I find the source to LibStorage.so so I can recompile it, or is there a way to skip loading it in y2r? Erico M. Mendonça Dedicated Support Engineer SUSE Rua Joaquim Floriano, 466 – Ed. Corporate 12º andar, Itaim Bibi – São Paulo – SP / Brasil Tel: +55 (11) 3345-3900 Cel: + 55 (61) 8594-9557 erico.mendonca(a)suse.com www.suse.com N��r��y隊\��^��~�{.n�+��Ǩ��r��i�m��0��ޙ��ɫ-u�ޗ�0��Ǩ�

2 1

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

28 Jan '16

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-autoinstallation: - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (13 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (113 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (93 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-kdump: - Fix handling of crashkernel parameter for Xen (5 days) https://github.com/yast/yast-kdump/pull/59 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (54 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (56 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Ported support for LVM proposal setting from SP1 to Master (35 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (36 days) https://github.com/yast/yast-storage/pull/155 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 yast.github.io: - Add some documentation about submit requests (61 days) https://github.com/yast/yast.github.io/pull/55 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0