November 2020

[yast-devel] Overcommit - automatic checks via Git hooks
by Ladislav Slezak 21 Dec '22

21 Dec '22

Hi, I found a quite interesting tool called Overcommit [1]. It provides an easy way for setting up Git commit hooks and provides some basic checking plugins. The nice feature of the Git commit hooks is that you can run some checks automatically and early in the development. For example with the commit hooks you can run Rubocop check automatically whenever a commit is created. And if the check fails the commit is not created. I can see "make Rubocop happy" commits quite often (happens to me … [View More]

3 3

[yast-devel] YaST Tips&Tricks
by Ladislav Slezak 25 Jan '22

25 Jan '22

Hi all, some time ago we discussed where and how we should share "Tips&Tricks" for YaST users and developers. IIRC there was no clear conclusion so I decided to start a wiki [1] to collect all our tricks we know or use. For now it's just a place for dumping your ideas, links, short howtos, etc... When we collect enough data we can probably split it to several categories or move it somewhere else. We just need the data first. I have added there some my tricks from my personal "… [View More]

2 1

[yast-devel] Innovation time: A repository with AutoYaST XML profiles (PoC )
by Ladislav Slezak 03 May '21

03 May '21

Hi all! I'm implementing some new AutoYaST feature and I found out that it's not easy to test the AutoYaST functionality. 1. Even for testing a trivial scenario you have to write your own XML file. If you do not have much experience with AutoYaST you have to read the documentation, search the internet, etc... Cloning your current system helps a bit but usually the cloned profile contains too many options so you still need to polish it a bit... 2. When you have your profile … [View More]ready you have to host it at some HTTP/FTP/NFS/... server so AutoYaST can use it for installation. I usually run simple "ruby -run -ehttpd" command to have a web server quickly, but that's quite tricky for people not familiar with Ruby. My idea is to have some repository with example XML profiles which would be publicly available and ready for instant use. We already have some XML files in the autoyast-profiles-test Git repository but writing something like autoyast=https://raw.githubusercontent.com/yast/autoyast-profiles-test/mast… on boot command line is a real pain. We could use some URL shortening service but I do not like that much. Shortened URLs do not look nice and it's not obvious where they point to (security). I'd like to have some nice URLs... So my proposal is to use the GitHub pages for building an AutoYaST profile repository. Then you could use autoyast=https://autoyast.github.io/mini/sles15.xml or autoyast=https://autoyast.github.io/mini/leap15.xml for testing a minimal SLES/Leap profile. Actually these URLs already work! :-) You can give it a try. Most likely you will need additional "netsetup=dhcp" boot option for configuring network. The profiles would be well described (what they do) and well commented (so the users can easily adapt them to their needs). The profiles could be automatically validated (via Travis) and it would be nice to use them also in openQA tests to be sure they really work. We could also link this repository from the official SUSE documentation. The proof of concept is available at https://autoyast.github.io, please check it. It is still just a concept for getting early feedback, there is a lot of work to do. See the README file in https://github.com/autoyast/autoyast.github.io What do you think about it? -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org [View Less]

2 1

[yast-devel] Reminder: verify_partial_doubles is not default
by Josef Reidinger 03 Dec '20

03 Dec '20

Hi, again I hit by thinking that verify_partial_doubles is now default in rspec3. It is not and will be in rspec4. So what it means? rspec does not check if mocked methods exists at all and it can result in many not so funny errors in test suite. I am just faced it in network, so I create non trivial commit[1] that enables it there. It includes also how to avoid failures on mocked class[2] which avoided build dependencies. From list of errors it can check is typos[3], mocking of wrong class[4] … [View More]

4 3

[yast-devel] Consolidating libyui Packaging and Build Environment
by Stefan Hundhammer 30 Nov '20

30 Nov '20

We are discussing and prototyping new packaging and a new build environment for libyui and related packages. More information here: https://github.com/libyui/libyui/issues/177 Please join the discussion in that GitHub issue if you have any concerns or maybe even a use case that we have not identified yet. Kind regards -- Stefan Hundhammer <shundhammer(a)suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

1 0

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

30 Nov '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-cluster: - bsc#1179007, Bind address should not write to configuration file when using unicast. (6 days) https://github.com/yast/yast-cluster/pull/87 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for … [View More]

1 0

[yast-devel] YaST: highlights of development sprint 113
by Ancor Gonzalez Sosa 24 Nov '20

24 Nov '20

Time for another development report from the YaST Team (temporarily transmuted in the YaST+Cockpit Team), including - Progress on the Cockpit modules for managing wicked and for transactional updates. - Improvements in the YaST Partitioner regarding management of Btrfs subvolumes. - Hibernation support configurable per product and system role. Check the whole report at https://yast.opensuse.org/blog/2020-11-24/sprint-113 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 23 Nov '20

23 Nov '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-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (9 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-online-update: - Added recommends to yast2-online-update-frontend (bsc#1177997) (… [View More]

1 0

[yast-devel] Quick testing of your changes from home office
by josef Reidinger 18 Nov '20

18 Nov '20

Hi, after my machine in office dies few weeks ago I struggle a bit with testing, as downloading isos to my home is not optimal due to bandwidth. But step by step I am improving it and now I have quick and efficient way for testing and it is possible for anyone in team ( outside contributors sadly cannot benefit from our internal server and PXE setup ). So: 1. create VM ( ideally use prefix for your machine ) with disk on our team server pong.suse.cz or autobus.suse.de ( internal only both and … [View More]

3 2

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

16 Nov '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-online-update: - Added recommends to yast2-online-update-frontend (bsc#1177997) (11 days) https://github.com/yast/yast-online-update/pull/33 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (… [View More]

1 0

[yast-devel] Innovation Time: Feedback from forums
by josef Reidinger 13 Nov '20

13 Nov '20

Hi, I use my todays innovation time to try to collect feedback from forums and as we have quite nice opensuse retrospective output, I try to focus on SLE. So I use forums.suse.com and here is few links with short description: AutoYast - looking for recommended autoyast profile for VM server http://forums.suse.com/discussion/13055/template-best-practices-and-hardeni… - problem with configuring network using autoyast ( not clear what is root of issue ) http://forums.suse.com/discussion/14165/… [View More]

2 2

[yast-devel] YaST: highlights of development sprint 112
by Ancor Gonzalez Sosa 11 Nov '20

11 Nov '20

Time has come for the YaST Team to pay the debts from the previous report: - We promised some news about Cockpit and we have a whole new Cockpit module to present. - We mentioned our talk in the openSUSE + LibreOffice Virtual Conference and now we have the video for you. - We told you we were working on several changes in YaST and it's time to present them all, including big enhancements in the Partitioner UI and other usability improvements. Check the whole report at https://yast.opensuse.… [View More]

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 09 Nov '20

09 Nov '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-devtools: - changes (35 days) https://github.com/yast/yast-devtools/pull/154 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (32 days) https://github.com/yast/yast-instserver/pull/50 … [View More]

1 0

[yast-devel] btrfs level 0 qgroups
by Arvin Schnell 02 Nov '20

02 Nov '20

Hi, users can do funny things with btrfs qgroups leading to problems: When a subvolume is created a corresponding level 0 qgroup is also created by btrfs. The subvolume id and thus the qgroup id are not predictable (see below). The user can also manually create level 0 qgroups. So the user can 1) manually create qgroup 0/260 and 2) create a subvolume that could get id 260 and the corresponding qgroup gets the id 0/260. A nice qgroup id collision. If libstorage-ng would commit such a setup … [View More]

2 4

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 02 Nov '20

02 Nov '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-autoinstallation: - [PoC] Run the unit tests in parallel (68 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (181 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending … [View More]

1 0

Main

Development

Information

Community

Social Media

Other

YaST Development