YaST Development

yast-devel@lists.opensuse.org

11 participants
4273 discussions

Bumping (almost) all YaST packages to version 4.4.x (15.4.x)

by Ladislav Slezak

Version Bump ------------ https://yastgithubio.readthedocs.io/en/latest/versioning/#new-schema-versio… TLDR: For next Leap 15.4/SLE 15-SP4 we need to bump all package versions to 4.4.x. Unfortunately we forgot to do that in 15.3/SP3 so not all YaST packages have version 4.3.x there. :-( So to avoid this situation again we did the version bump right now. **All YaST packages have been updated to 4.4.0 unless they already use a 4.4.x version.** Exceptions ---------- The skelcd-control-* and system-role-* packages use the product version so I updated them to version 15.4.0. Skipped Packages ---------------- skelcd-control-suse-manager-proxy, skelcd-control-suse-manager-server - these packages use the SUSE Manager version yast-rake - this is a Ruby gem, not an YaST module, it uses usual semantic versioning patterns-yast-20201210 - it uses date as the version These packages do not use 4.x version so I kept them untouched, they are maintained by other teams and I do not know their versioning schema: yast-hana-firewall-2.0.4 yast-hana-update-1.2.1 yast-rmt-1.3.2 yast-samba-provision-1.0.4 yast-sap-ha-1.0.9 yast2-aduc-2.2 yast2-gpmc-1.5.1 If you do not have any particular reason for that versioning it would be nice if you unified the package versions to 4.4.x. Then next time the version bump would happen globally with the other YaST packages. If you have any questions, just ping me. -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

2 hours, 1 minute

AMD GPU problem with Kernel 5.11.x

by Not So Sordid

For more than a month I'm having a crash problem with the kernel 5.11. It boots up, but when loadaded the display manager (tried SDDM and GDM), the system freezes. It occurs in a Dell Inspiron laptop with AMD GPU Radeon R7. Well, I finally found a solution in the Bugzilla of kernel [https://bugzilla.kernel.org/show_bug.cgi?id=212133]. The solution is add the 'modprobe.blacklist=amdgpu 3' parameter to the GRUB kernel line. It works! The only problem is having to start the graphical server manually. I opened this thread to make developers aware of the problem, if they are not already. I am hopeful for a better and definitive solution soon.

1 day, 12 hours

Pending Pull Requests

by yast-ci＠opensuse.org

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-installation: - Master base product logging (65 days) https://github.com/yast/yast-installation/pull/907 - Replace old splash commands with plymouth ones (89 days) https://github.com/yast/yast-installation/pull/904 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (156 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-metapackage-handler: - Extend unit test for existing functions (97 days) https://github.com/yast/yast-metapackage-handler/pull/23 Pending requests in repository yast-online-update: - Improved openSUSE/SLE detection (bsc#1184243) (17 days) https://github.com/yast/yast-online-update/pull/35 - Added recommends to yast2-online-update-frontend (bsc#1177997) (165 days) https://github.com/yast/yast-online-update/pull/33 Pending requests in repository yast-packager: - Adding NFS repository: Checking user input e.g. white spaces in serve… (130 days) https://github.com/yast/yast-packager/pull/543 - Include some hints in the "Priority" label (bsc#1154693) (198 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-python-bindings: - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP3 into master) (17 days) https://github.com/yast/yast-python-bindings/pull/39 - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP2 into SLE-15-SP3) (17 days) https://github.com/yast/yast-python-bindings/pull/38 Pending requests in repository yast-registration: - Master base product logging (65 days) https://github.com/yast/yast-registration/pull/529 Pending requests in repository yast-theme: - Add pattern-budgie icon (boo#1176164) (59 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-users: - add document with usage of users module (18 days) https://github.com/yast/yast-users/pull/241 Pending requests in repository yast-yast2: - Logging all available products information into directory /var/log/Y… (11 days) https://github.com/yast/yast-yast2/pull/1135 Pending requests in repository yast-ycp-ui-bindings: - Failing autowrap (131 days) https://github.com/yast/yast-ycp-ui-bindings/pull/64 - New UI Example for ComboBox (146 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository yast-ruby-bindings: - Logging all available products information into directory /var/log/Ya… (65 days) https://github.com/yast/yast-ruby-bindings/pull/267 Pending requests in repository skelcd-control-openSUSE: - Ntp servers (97 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository yast-auth-client: - Fix help (13 days) https://github.com/yast/yast-auth-client/pull/99 - Fix reading of LDAP TLS setting (bsc#1181927) and help (bsc#1172340) (13 days) https://github.com/yast/yast-auth-client/pull/98 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (205 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (662 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast.github.io: - blog post UCMT (14 days) https://github.com/yast/yast.github.io/pull/283 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (195 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Partial fix for bug#176140 (152 days) https://github.com/yast/yast-storage-ng/pull/1166 - Display pathnames correctly in a Right-to-Left context (bsc#1128091) (146 days) https://github.com/yast/yast-storage-ng/pull/873 Pending requests in repository helper_scripts: - [dependencies] Bump kramdown from 2.3.0 to 2.3.1 in /jekyll (20 days) https://github.com/yast/helper_scripts/pull/25 - [dependencies] Bump nokogiri from 1.10.10 to 1.11.2 in /jekyll (33 days) https://github.com/yast/helper_scripts/pull/24 Pending requests in repository docker-yast-ruby: - drop travis (83 days) https://github.com/yast/docker-yast-ruby/pull/37 Pending requests in repository docker-yast-cpp: - drop travis (83 days) https://github.com/yast/docker-yast-cpp/pull/26 Pending requests in repository skelcd-control-leanos: - Default ntp servers (97 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - Fix tests (11 days) https://github.com/yast/yast-rmt/pull/60 - Add metadata into packages (196 days) https://github.com/yast/yast-rmt/pull/51 - use docker image from OBS (215 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (215 days) https://github.com/yast/yast-rmt/pull/40 Pending requests in repository skelcd-control-MicroOS: - sync with SLE (137 days) https://github.com/yast/skelcd-control-MicroOS/pull/27 - unify proposed partition sizes with openSUSE MicroOS (138 days) https://github.com/yast/skelcd-control-MicroOS/pull/26 Pending requests in repository skelcd-control-SMO: - install the microos-selinux pattern by default (69 days) https://github.com/yast/skelcd-control-SMO/pull/6

1 day, 16 hours

Revamping yast2-users: the UI

by David Díaz

Hi there! In the context of revamping yast2-users[1], I spent some days looking for an alternative layout that could help to improve the current UI by reducing the number of tabs and grouping form fields to make better use of available space. However, due to our resolution constraints (UI must fit well in an 80x24 terminal) and some UI library limitations[2], looks like there is not too much room for big changes and our best bet is to keep the layout almost as it is, just making some necessary adjustments[3]. Summarizing them a lot, those changes will consist of adding a top menu bar for making easier the user navigation, moving all settings to the same dialog, improving filters by using a popup, making small changes in forms, and adding some summary views. Of course, nothing is written in stone and it would be nice to know your feedback and/or ideas too. So, please, keep reading the following links if you are interested and tell us what do you think. Is there anything we overlooked? Some other ideas we should evaluate? Remember that you can reach us by email, on IRC, or even by directly leaving a comment in those Github issues. Thanks! [1] "Revamping yast2-users" mailing list thread - https://lists.opensuse.org/archives/list/yast-devel@lists.opensuse.org/thre… [2] "UI library limitations" https://github.com/yast/yast-users-ng/issues/8 [3] "Revamping yast2-users UI: an initial proposal" https://github.com/yast/yast-users-ng/issues/6 -- David Díaz YaST Team at SUSE LINUX GmbH IRC: dgdavid

4 days, 19 hours

[yast-devel] https://en.opensuse.org/SDB:Linuxrc in need of edit???

by Felix Miata

NameScheme=by-label on installer cmdline has had no effect I have observed for a lot longer than I can remember, several years at least, continuing in 15.3 build 117.13. Has it been removed and the linuxrc page need matching update? Is this a broken installer option? Am I not understanding why it's listed on the linuxrc page? Shouldn't it prevent me from needing to change default mount by in the expert partitioner? -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

5 days, 12 hours

Error reporting API

by Imobach Gonzalez Sosa

Hi all, Recently, we got a bug report about YaST crashing[1] when the BOOTPROTO value in an ifcfg-* file is invalid. How to handle this situation? 1) We could detect that problem and inform the user through the Yast::Report module but, to be honest, I do not like having calls to Yast::Report.Error all over the place (we are somehow mixing business and UI logic). 2) We could raise an exception and report it to the user. But 1) it stops the workflow, and 2) we will raise an exception for each error we find. Moreover, sometimes you can recover from the error easily (but you might want to tell the user about it). So I thought it would be nice to have something similar to the AutoinstIssues mechanism[2]. Basically, you register any error you find and, at the end of the process, you report all the problems to the user at a single point. I have written some details and many open questions in a pull request[3]. I think the error classes (we might need a better name) should live in yast2.rpm, but for the discussion, let's keep everything in the same repository. Anyone interested, please, have a look at the pull request and add your thoughts about it. Thanks! Regards, Imo [1] https://bugzilla.suse.com/show_bug.cgi?id=1181296 [2] https://github.com/yast/yast-yast2/blob/master/library/general/src/lib/ installation/autoinst_issues.rb [3] https://github.com/yast/yast-network/pull/1204 -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

6 days, 10 hours

Revamping yast2-users

by José Iván López González

Hi! As you probably already know, in the YaST team we sometimes dedicate part of our human resources to improve some key modules. For example, yast-storage was rewritten from scratch as yast-storage-ng. Other examples are yast-network and autoYaST, which were heavily refactored. That effort on improving the code base has allowed us to prepare the field in order to bring new great features. And of course, as result, we have a better designed code, with good unit tests coverage. Now we are focusing on yast-users. This module takes care of managing users, not only local ones but also NIS, LDAP, Samba, Kerberos, etc. And we want to revamp it. As part of this work we would like to redesign its UI completely, and integrate it with some functionalities like sudo. We are now in a research phase, where we are trying to understand all the supported use-cases and how the module integrates with other modules like yast-samba-server or yast-auth-server. And of course, we would like to hearing from you too. So, please, tell us what use-cases you want to see in the new yast-users. Is there anything that you miss now? What use-cases would you like to keep? We would be very appreciated with your feedback. You can tell us your suggestions by email, on IRC or even by opening an issue in this repo [1]. Whatever better fits to you. Thanks a lot! Regards, The YaST Team [1] https://github.com/yast/yast-users-ng -- José Iván López González YaST Team at SUSE LINUX GmbH IRC: jilopez

6 days, 10 hours

web server

by Ricardo Sousa

could you guys redesign your http server for add this tools like this Add Hostname add name of the host add port 80 choose port 443 will have to add the certificate browse certificate or create new one choose the php version to use php 5.4 php 5.6 php 7.0 browse files index.php start.php default.php choose the files in a list box as add ftp user and password if need it user name and password add to a list all domains is hosted on the server to view all hostnames in the list ----------------------------------------------------------------------------------- IP | Hostname | Port | WWW | ---------------------------------------------------------------------------------- 127.0.0.1 | suse.com | 80 | www/php/suse.com | active | modify | delete ---------------------------------------------------------------------------------- 127.0.0.1 | opera.com | 443 | www/php/suse.com | active | modify | delete ----------------------------------------------------------------------------------- 127.0.0.1 | hello.com | 80 | www/php/suse.com | active | modify | delete ---------------------------------------------------------------------------------- 127.0.0.1 | su45e.com | 80 | www/php/suse.com | active | modify | delete

1 week

RTMP Server

by Ricardo Sousa

1 week

multi php version to use and choose

by Ricardo Sousa

web server does not have multi php versions to choose it should have a combobox with multi php to choose 5.4 5.6 7.1 7.2 choose the php version we want to use and the web server apache pr nginxy if i want to use the php 5.6 i need to install on another server the opensuse to use php 5.6 then i have to install another server opensuse to use php 7 so i will have to install 10 servers each one opensuse for use each php version server 1 - opensuse15.2 - php 5.4 server 2 - opensuse15.2 - php 5.5 server 3 - opensuse15.2 - php 5.6 server 4 - opensuse15.2 - php 7.0 server 5 - opensuse15.2 - php 7.1 well you guys can use one server for do this to be all in one use one server only

1 week

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development