July 2020 - YaST Development - openSUSE Mailing Lists

[yast-devel] need to Add _constraints for PowerPC for libstorage-ng
by Normand 22 Jul '20

22 Jul '20

Hi there, to solve a build failure in OBS for PowerPC (1), I need to add a _constraints file as detailed in (2) But when submitting to OBS via "osc sr" I am rejected as (3) I do not know where to place this new _constraints file in https://github.com/openSUSE/libstorage-ng to have it uploaded in OBS. Could you help me on that ? (1) https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/libstorage… (2) https://build.opensuse.org/package/show/home:michel_mno:branches:YaST:Head/… (3) === $osc sr - Add _constraints for PowerPC avoid "no space left on device" build error --This line, and those below, will be ignored-- old: YaST:Head/libstorage-ng new: home:michel_mno:branches:YaST:Head/libstorage-ng rev None Index: libstorage-ng.changes =================================================================== --- libstorage-ng.changes (revision 668) +++ libstorage-ng.changes (revision 2) @@ -1,3 +1,8 @@ +------------------------------------------------------------------- +Mon Jul 20 13:49:50 UTC 2020 - Michel Normand <normand(a)linux.vnet.ibm.com> + /tmp/osc-editor6kgyj48y.diff 1,0-1 Top "/tmp/osc-editor6kgyj48y.diff" 68L, 2277C written Server returned an error: HTTP Error 403: Forbidden The target project YaST:Head is not accepting requests because: The YaST packages are developed at Github (https://github.com/yast or https://github.com/libyui) and are automatically submitted to YaST:Head OBS project by Jenkins CI (http://ci.opensuse.org/view/Yast/) after each Git commit (if the testsuite passes). See "CONTRIBUTING.md" file at the respective Github repository for more details. You can also contact Yast developers at #yast irc.freenode.org or yast-devel(a)opensuse.org (http://lists.opensuse.org/yast-devel/) mailing list. === -- Michel Normand -- 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] YaST: survey results and highlights of development sprint 104
by Ancor Gonzalez Sosa 21 Jul '20

21 Jul '20

Our latest summary includes our usual overview of two weeks of work and also the results of the survey about our blog. Regarding the first part, you will find information about all this: - Research about the differences in the look&feel of the installer and YaST Firstboot - Several fixes related to the usage of the firstboot_hostname client - More accurate detection of the installation medium type when SMT is used to mirror the repositories from SCC - Better support in the Partitioner for the different types of LVM - AutoYaST now exports the SUSE registration settings - Improved support for the so-called Repository Variables in the URL of the repositories during system upgrade - Extend the support of Repository Variables to also cover the name of the repositories - Adapted YaST to handle the new location of the krb5 files - Many internal improvements regarding AutoYaST Check the extended versions with links and also the survey results at: https://yast.opensuse.org/blog/2020-07-21/sprint-104 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] The blog post survey
by Ancor Gonzalez Sosa 20 Jul '20

20 Jul '20

These are the results of the survey about the YaST blog post. Total answers: 31 Q1.How often do you read the YaST Team reports? This is my first time: 4 (12.90%) When I find something interesting in the summary: 5 (16.13%) Regularly: 22 (70.97%) Q2.How do you value de new format compared to the traditional? The new format is basically useless: 2 (6.45%) I prefer the previous format: 11 (35.48%) Both are equally valuable to me: 12 (38.71%) I prefer the new diggest format: 6 (19.35%) The new format is the only useful one: 0 Q3.What's your relationship with (open)SUSE: SUSE employee: 6 (19.35%) User: 23 (74.19%) openSUSE Release Manager: 1 (3.23%) N/A: 1 (3.23%) The question Q3 was open, so I have performed some reasonable grouping. Those where all the exact strings, in case somebody is interested: "Employee" (x2), "SUSE Employee", "QA Sle", "Software Engineer @ SUSE", "openSUSE user and SUSE engineer", "User" (x4), "openSUSE User" (x10), "(open-)SUSE user", "openSUSE user, packager", "openSUSE contributor", "usuário", "User/Sysadmin", "opensuse tw user", "openSUSE TW RM", "openSUSE", "I use tumbleweed on a server SOHO", "openSUSE", (empty) Cheers -- Ancor González Sosa YaST Team at SUSE Software Solutions -- 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 Jul '20

20 Jul '20

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-apparmor: - Port to rake (401 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (76 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Add UPDATE_NVRAM in /etc/sysconfig/bootloader (bsc#1157550). (6 days) https://github.com/yast/yast-bootloader/pull/611 - Fix resume with uuid partition (368 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (143 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-devtools: - Y2logs analyzer (145 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (173 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (406 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - clarify that ssh_import processes host keys (bsc#1172400) (45 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (619 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (241 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (367 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (110 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (23 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-users: - Remove ag_uid to save memory at installation time (bsc#1172139) (26 days) https://github.com/yast/yast-users/pull/231 Pending requests in repository yast-yast2: - Bnc#1081441 (95 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (96 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (405 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (536 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (536 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (684 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (669 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (696 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (143 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (199 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (783 days) https://github.com/yast/yast-ruby-bindings/pull/216 ERROR: API query limit exceeded -- 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] Loading Installation System step 5/6 missing/optional
by Felix Miata 20 Jul '20

20 Jul '20

What is in that step 5 that gets skipped by the 15.2 installer? It's ominous looking, scares n00bs. -- Evolution as taught in public schools is religion, not science. 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

1 0

Re: [yast-devel] Innovation Time: autoyast and its competition
by josef Reidinger 15 Jul '20

15 Jul '20

On Mon, 13 Jul 2020 14:50:26 +1000 William Brown <wbrown(a)suse.de> wrote: > > On 11 Jul 2020, at 07:05, josef Reidinger <jreidinger(a)suse.cz> wrote: > > > > Hi, > > this friday I decide to look what competition offers for automated/unattended installation. Here are some of my notes: > > > > Available: > > debian: https://wiki.debian.org/AutomatedInstallation including FAI > > ubuntu: kickstart compatibility https://help.ubuntu.com/community/KickstartCompatibility > > redhat: kickstart https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… > > > > > > Kickstart > > text file with syntax. Recommended way for creation is cloning of manual installation. > > Also UI is available, but does not support advanced partitioning and not for everyone. > > Interesting feature is that kickstart allow to specify on failure script (both user error %onerror and program error %traceback ) which is executed when fatal failure happen. This is often used for debugging and error reporting. > > Also all pre,post,etc script has option --erroronfail which makes failure of script fatal for whole installation. > > What I really like about kickstart documentation is that they mention when it is introduced, when it is deprecated and when it is removed for each option. > > I have to say also that I found kickstart file more readable then autoyast XML. See examples at http://www.stratuslab.eu/fp7/doku.php/tutorial:baseimagecreationkickstart.h… and I think you get quickly idea what each line means. > > Kickstart allows composition using including of other files. This is used for dynamic content together with pre script and include of file generated by script. > > What surprise me that autoyast allows much more schemas to locate its file. E.g. ftp is not supported in kickstart. > > > > > > kickstart also creates a template in /root from any install so that you can *easily* recreate the system. AutoYAST doesn't do this, and because the syntax is more complex, it's really hard to start with and get a working or reproducable build. > > So maybe a start is yast creating a "/root/autoyast.xml" if you want to "recreate" the system the way you built it? Actually this works in autoyast if product wants to do it by default. It should done for SLE and not done for openSUSE ( product can control it ). And even if product does not create it by default, you can always run `yast2 clone_system` which creates it for you. If it does not work, please report a bug. > > > > > FAI > > https://fai-project.org/ > > Based on cfengine. Supports also SUSE, but main target is debian. It has also web service ( quite limited ) to generate modified installation image. > > what is nice that they has users survey publically available. So I see in some of their report that users use it even for SLE, others use autoyast and fai only for debian. would be nice to have similar survey. > > I would like to play a bit more with FAI, as I see also opportunity to contribute there and help some SUSE/openSUSE users which prefer cfengine. > > > > > > Visibility of autoyast > > When I am searching for competition I am also interested how autoYaST is visible: > > Googling "unattended installation" no chance, "unattended installation linux" nothing, "unattended installation suse" shows finally autoyast. > > "automatic installation" no chance, "automatic installation linux" autoyast is heavily beaten by fai and kickstart, autoyast is on second page at bottom, "automatic instalation suse" is clear win. > > This is probably more a reflection of how autoyast being hard to use today, which makes it so that people don't often use it, leading to lower google search rates. > > So making autoyast really really easy to use and configure would probably boost that, > If you have more ideas how to make it easier to use and configurable, do not hesitate to speak to us. Any ideas are welcome ( no guarantee to implement it :) > Hope that helps! any feedback helps. Josef > > > > > > I hope you find this useful. > > > > Josef > > -- > > To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org > > To contact the owner, e-mail: yast-devel+owner(a)opensuse.org > > > > — > Sincerely, > > William Brown > > Senior Software Engineer, 389 Directory Server > SUSE Labs > -- 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 13 Jul '20

13 Jul '20

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-apparmor: - Port to rake (394 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (69 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (361 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (136 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-devtools: - Y2logs analyzer (138 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (166 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (399 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - clarify that ssh_import processes host keys (bsc#1172400) (38 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (612 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (234 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (360 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (103 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (16 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-users: - Remove ag_uid to save memory at installation time (bsc#1172139) (19 days) https://github.com/yast/yast-users/pull/231 Pending requests in repository yast-yast2: - Bnc#1081441 (88 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (89 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (398 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (529 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (529 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (677 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (662 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (689 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 ERROR: API query limit exceeded -- 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] Innovation Time: autoyast and its competition
by josef Reidinger 10 Jul '20

10 Jul '20

Hi, this friday I decide to look what competition offers for automated/unattended installation. Here are some of my notes: Available: debian: https://wiki.debian.org/AutomatedInstallation including FAI ubuntu: kickstart compatibility https://help.ubuntu.com/community/KickstartCompatibility redhat: kickstart https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… Kickstart text file with syntax. Recommended way for creation is cloning of manual installation. Also UI is available, but does not support advanced partitioning and not for everyone. Interesting feature is that kickstart allow to specify on failure script (both user error %onerror and program error %traceback ) which is executed when fatal failure happen. This is often used for debugging and error reporting. Also all pre,post,etc script has option --erroronfail which makes failure of script fatal for whole installation. What I really like about kickstart documentation is that they mention when it is introduced, when it is deprecated and when it is removed for each option. I have to say also that I found kickstart file more readable then autoyast XML. See examples at http://www.stratuslab.eu/fp7/doku.php/tutorial:baseimagecreationkickstart.h… and I think you get quickly idea what each line means. Kickstart allows composition using including of other files. This is used for dynamic content together with pre script and include of file generated by script. What surprise me that autoyast allows much more schemas to locate its file. E.g. ftp is not supported in kickstart. FAI https://fai-project.org/ Based on cfengine. Supports also SUSE, but main target is debian. It has also web service ( quite limited ) to generate modified installation image. what is nice that they has users survey publically available. So I see in some of their report that users use it even for SLE, others use autoyast and fai only for debian. would be nice to have similar survey. I would like to play a bit more with FAI, as I see also opportunity to contribute there and help some SUSE/openSUSE users which prefer cfengine. Visibility of autoyast When I am searching for competition I am also interested how autoYaST is visible: Googling "unattended installation" no chance, "unattended installation linux" nothing, "unattended installation suse" shows finally autoyast. "automatic installation" no chance, "automatic installation linux" autoyast is heavily beaten by fai and kickstart, autoyast is on second page at bottom, "automatic instalation suse" is clear win. I hope you find this useful. 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] Very late updates for yast2-trans
by José Iván López González 07 Jul '20

07 Jul '20

Hi all, Recently, a bug report [1] was filed because translation updates are taken quite long to reach the product. It seems that it took almost 1 year and 4 months to get an updated yast2-trans package into Leap 15.2. Do you know the source of the problem? Could we do anything to improve it? Thanks! [1] https://bugzilla.suse.com/show_bug.cgi?id=1172874 -- José Iván López González YaST Team at SUSE LINUX GmbH IRC: jilopez -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 3

[yast-devel] please push Leap_15.2-GM tag to yast-translations.git
by Lubos Kocman 06 Jul '20

06 Jul '20

Hello yast team! May I ask you to push following tag to the upstream yast2-trans github repo? This is the only package where I don't have rights to do so. https://github.com/yast/yast-translations git tag Leap_15.2-GM bc4a9329cc && git push origin Leap_15.2-GM This task is otherwise tracked here https://progress.opensuse.org/issues/61551 Thank you

2 1