June 2022 - YaST Development - openSUSE Mailing Lists

Pending Pull Requests
by yast-ci＠opensuse.org 13 Jun '22

13 Jun '22

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: - Sle15sp3 boo1199396 (33 days) https://github.com/yast/yast-devtools/pull/168 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (125 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Fixed a syntax error in the README (9 days) https://github.com/yast/yast-installation/pull/1047 - Remake some icons (90 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (48 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (109 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-python-bindings: - Sle15 sp1 examples fixup (23 days) https://github.com/yast/yast-python-bindings/pull/42 Pending requests in repository yast-schema: - bsc#1198848: simplify online_update_configuration format (16 days) https://github.com/yast/yast-schema/pull/138 Pending requests in repository yast-theme: - Add pantheon desktop support (194 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (117 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (79 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 (24 days) https://github.com/yast/yast.github.io/pull/324 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (124 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 in /jekyll (24 days) https://github.com/yast/helper_scripts/pull/39 Pending requests in repository yast-samba-provision: - Sle15 sp1 update (23 days) https://github.com/yast/yast-samba-provision/pull/10

1 0

"WebYaST" or rather "containerized YaST in web browser" experiment
by Ladislav Slezák 09 Jun '22

09 Jun '22

Hi all! I'm continuing with the experiments with containerized YaST. Quite often we get a request for web access for YaST. Unfortunately the YaST architecture does not allow to create a web interface easily because it is something completely different compared to the usual desktop applications. However, there is one workaround. Why not using the same graphical interface, just rendering it in a browser? Actually we already do that in the installer. If you boot with the "vnc=1" boot parameter YaST not only allows a VNC connection on port 5901 but also HTTP connection on port 5801. The trick is done via the Xvnc (X + VNC server) and novnc (VNC client written in JavaScript which can run in browser). Of course, that means the UI will still be the standard YaST Qt UI, there will be no fancy web page with modern features like responsive design, cool HTML5 tricks, CSS animations and so on.... But if you really want a remote web based access then it works and is usable. If that's the most important feature for you maybe you will accept the not so nice UI/UX. The advantage is that we would not need to change anything in YaST, we would get this "web" interface basically for free, without any significant additional work. So here are the most important questions: - Would this solution be acceptable for you? - Would you use YaST this way? How to test it: I added the "yast2_web_container" command into the yast-in-container package [1] which starts YaST inside a container with an Xvnc session. Alternatively you can run the script directly from the Git checkout [2]. The script and the container image are designed to manage an openSUSE Leap 15.4 or SLE15-SP4 systems. For security reasons the connection uses the HTTPS access. You can provide your own SSL certificate. If it is not found then the container generates a self-signed one. Also you need to set up the VNC access password. See more details in [3]. After starting "yast2_web_container" as root you can connect to https://localhost:4984/ and after providing the access password you can use YaST as usually. You can see some screenshots in [4]. Enjoy! Ladislav [1] https://build.opensuse.org/package/show/YaST:Head/yast-in-container [2] https://github.com/yast/yast-in-container/tree/master/src/scripts [3] https://github.com/yast/yast-in-container#web-https-access [4] https://github.com/yast/yast-in-container/pull/4 -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 06 Jun '22

06 Jun '22

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: - Sle15sp3 boo1199396 (26 days) https://github.com/yast/yast-devtools/pull/168 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (118 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (83 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (41 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (102 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-python-bindings: - Sle15 sp1 examples fixup (16 days) https://github.com/yast/yast-python-bindings/pull/42 Pending requests in repository yast-schema: - bsc#1198848: simplify online_update_configuration format (9 days) https://github.com/yast/yast-schema/pull/138 Pending requests in repository yast-theme: - Add pantheon desktop support (187 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (110 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (72 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 (17 days) https://github.com/yast/yast.github.io/pull/324 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (117 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 in /jekyll (17 days) https://github.com/yast/helper_scripts/pull/39 Pending requests in repository yast-samba-provision: - Sle15 sp1 update (16 days) https://github.com/yast/yast-samba-provision/pull/10 Pending requests in repository yast-sap-ha: - Sle 15 sp3 (14 days) https://github.com/yast/yast-sap-ha/pull/9 - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (14 days) https://github.com/yast/yast-sap-ha/pull/7

1 0

Talk for openSUSE Conference 2022
by Ancor Gonzalez Sosa 04 Jun '22

04 Jun '22

I plan to submit this. Feel free to provide feedback before I do it. Title: Almost two years of YaST News Subtitle: Recent changes and future plans at YaSTland Abstract: YaST, the flagship installer and configuration tool of openSUSE is in constant development. Just as its unattended companion AutoYaST. Although the YaST Team at SUSE tries to communicate progress as often as possible in the YaST Blog, it has been almost two years since we presented the "Top 25 New Features in (Auto)YaST" at openSUSE Conference 2020. So it's time for another live update! We will recap the main changes and new features that are already integrated into openSUSE Tumbleweed and that will be included at openSUSE Leap 15.4, to be released just a couple of days after the talk. We will also take a look to some ideas for future development... and we really need the feedback of the whole openSUSE community for that. So please join us and speak up! -- Ancor González Sosa YaST Team at SUSE Software Solutions

5 8

yast2 partitioner and ntfs
by Lukáš Krejza 02 Jun '22

02 Jun '22

Hello List, recently, i tried to mount a NTFS partition using yast read-write. I checked wiki [1] which states, that "Reading and writing to NTFS partitions is supported by default through the ntfs-3g driver, but NTFS partitions are not automatically mounted." which gives impression, that changing to ntfs-3g is everything you need. For that, you need to manually modify fstab by changing driver from ntfs to ntfs-3g. However, that is not enough to get NTFS writable. You also need to add options (rw,nosuid,nodev,relatime,user_id=<here your uid>,group_id=<here your gid>) - or similar. None of this is also documented (or i may have been looking on the wrong places). Second issue i got into was, that when you set the options in yast partitioner after changing fstab manually, the drive gets mounted by fuse, again without read-write support. I had to su and remount the partition manually, after which it worked. My questions are: 1) Is there any planned improvement in mounting NTFS read-write and supporting ntfs-3g directly by yast instead of using fuse? Possibly by respecting driver specified in fstab? 2) Why the wiki officially recommends editing fstab manually, when it was always been discuragued in favour of yast partitioner 3) Could that be improved for examply in some checkbox [x] Read-write support and selecting user for mounting it from a drop-down menu in yast partitioner? And/or selecting proper driver (ntfs, ntfs-3g, fuse) in partitioner via GUI? 4) Could the wiki be at least updated to reflect current situation and what needs to be really done to mount it read-write? 5) Is there anything i missed and does really Yast still not support the mounting of NTFS read-write? [1] https://en.opensuse.org/SDB:NTFS Thanks. Regards, Gryffus

2 1

partition id unknown on GPT
by Arvin Schnell 01 Jun '22

01 Jun '22

Hi, so far using parted it was not possible to see whether the partition id on GPT was "linux" or something unknown (to parted). Since parted now also reports the partition type GUID that distinction is possible. With libstorage-ng version 4.5.15 (just accepted into Factory) the GUID is used. As a consequence the id can now be ID_UNKNOWN on GPT after probing. The value ID_UNKNOWN itself is not new. ciao Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Software Solutions Germany GmbH Maxfeldstraße 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman

1 0

Re: "YaST in a container" or "YaST without YaST"
by Ladislav Slezák 01 Jun '22

01 Jun '22

Dne 01. 06. 22 v 2:10 William Brown napsal(a): > Seems super interesting! Thanks! > > So I'm assuming this works by doing something like: > > > docker run -i -t -v /:/host yast-container > > So that the yast-container can interact with the "root" filesystem from /? > Yes, that's the trick, it uses "-v /:/mnt". That's actually the same what YaST does during normal installation, in that case the target system is also mounted to "/mnt". To have full access to the host system it uses some more options, esp. the "--privileged" is important. See https://github.com/yast/yast-in-container/blob/9470635cfaae6b9e1729cb755a94… For accessing the X session in the host it needs some extra options, see https://github.com/yast/yast-in-container/blob/9470635cfaae6b9e1729cb755a94…, that might be useful if you want to run any X application in a container. >> Today I found one more interesting use case: disaster recovery. First I removed >> zypper + libzypp from the system and I was able to install it back using YaST >> package manager in a container. Then I even removed rpm (!) itself and I was >> still able to install it back to the system via the YaST container! > > This is extremely cool. :D I was also surprised from how bad situation I could easily recover... :-) -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0