January 2020 - YaST Development - openSUSE Mailing Lists

[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] 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] YaST at the openSUSE Summit Dublin
by Ancor Gonzalez Sosa 07 Feb '20

07 Feb '20

Douglas DeMaio asked if me or any other YaST developer was planning to give a talk at openSUSE Summit Dublin[1]. I have to admit that was out of my radar. That summit is a small event that takes place right after SUSECON[2] in the same location, reusing part of its infrastructure. So it sounds like a nice place to meet people who are both openSUSE enthusiasts and SUSE customers. To be honest, YaST had almost not presence In the latest openSUSE Conference and that felt pretty wrong. Imo and me … [View More]

3 4

[yast-devel] Fwd: openSUSE - Google Summer of Code 2020
by Ancor Gonzalez Sosa 05 Feb '20

05 Feb '20

openSUSE is considering to apply for Google Summer of Code this year. We offered some projects in the past, some of them were indeed executed([1],[2]). [1] Alternatives YaST Module https://github.com/openSUSE/mentoring/issues/13 [2] Rewrite Keyboard Management - Done out of GSoC https://github.com/openSUSE/mentoring/issues/79 Others never made it to GSoC for several reasons, although some of them were finally implemented by the YaST Team itself ([3],[4],[5]) [3] REST API for testing … [View More]

4 10

Re: [yast-devel] Re: Partitioner: changing the default tab
by Lukas Ocilka 31 Jan '20

31 Jan '20

On 1/24/20 10:57 AM, Ancor Gonzalez Sosa wrote: > First of all, I'm moving this discussion to the yast-devel mailing list. > This is not internal team stuff. > > On 1/23/20 3:36 PM, David Díaz wrote: >> Hi folks! >> >> As part of my current PBI[1], I must raise a discussion about the >> default behavior of pages with tabs in the Partitioner :) >> >> The question is simple, should we really display the "Overview" tab by >> default? During … [View More]

6 10

Re: [yast-devel] Online Search: module/extension dependencies
by Imobach González Sosa 31 Jan '20

31 Jan '20

On Thu, 2020-01-30 at 17:16 +0000, Kenneth Wimer wrote: > Allowing users to select packages for installation without having > registered the product seems like your creating a situation in which > the installation process itself will become over-complicated and > confusing. I would seriously think about registering the product > before the installation overview. Well, zypper allows to do that (searching without being registered). But it is a different case, as zypper won't let … [View More]

1 0

[yast-devel] Online Search: module/extension dependencies
by Imobach González Sosa 30 Jan '20

30 Jan '20

Hi all, I am extending the online search feature[1] to work on unregistered systems and I have found out that you need to be registered to get the list of available modules/extensions. Basically, when you search for a package, you get this information: { "data": [ { "id": 19795225, "name": "apache2-mod_php7", "arch": "x86_64", "version": "7.3.13", "release": "1.7", "products": [ { "id": 1976, "name": "Web and Scripting … [View More]

2 2

Re: [yast-devel] Online Search: module/extension dependencies
by Imobach González Sosa 30 Jan '20

30 Jan '20

On Thu, 2020-01-30 at 15:40 +0000, Kenneth Wimer wrote: > From a SLES point of view, if the user has to register the products > necessary to get the additional packages he/she is searching for, > then the base-system definitely needs to be registered. Yes, but you can search for the packages before deciding whether to register the system or not. Moreover, zypper does allow to search without registering the base system, and YaST should be on-par with zypper. > Is there a use-case … [View More]

1 0

Re: [yast-devel] Re: Partitioner: changing the default tab
by Lukas Ocilka 30 Jan '20

30 Jan '20

On 1/29/20 10:25 AM, Ancor Gonzalez Sosa wrote: >> - YaST Disk starts at "Available storage on *" and I never found it any >> useful as it contains everything mixed together > > BTW, we improved a bit that view in the latest sprint (still not visible > in Tumbleweed) so all devices can be managed directly from there thanks > to the contextual buttons. > See https://github.com/yast/yast-storage-ng/pull/1024 OK, good to have those buttons, but I still see it "a bit"… [View More] overfilled with content. My "Available storage *" contains 10 items: two disks, LVM. Imagine an overview with RAID, LVM, three disks... >> I'd probably really expect >> >> - To see only disks, when I click on Hard Disks >> - To go directly to partitions when selecting a disk > > Always? Also for hard disks that are formatted directly (without > partition table) or fully empty? Good question if I hadn't written "Obviously all this comes from use-cases." a few lines below :D For my use-case, yes. > Same question applies to software RAIDs, that traditionally were used as > "virtual partitions" (i.e. formatted directly) but since storage-ng can > also be partitioned (so they are seen more like "virtual disks" now). > Would you also expect to land in "partitions" for them? In that regard, > I couldn't say which one of the use-cases (formatting them or > partitioning) is more common or more useful . Maybe the problem is that we call it "Partitions" while we actually show "how the disk is divided into partitions (or not)" ;) We should not stick to old naming especially as we currently allow more than in the past where we were (most probably) just working with partitions. > And same question applies to Bcache devices, that (like disks and > RAIDs), can also be formatted/mounted directly or partitioned. Would > "partitions" also be your expected tab there? I don't have any expectations there as I don't use btrfs myself. >> Obviously all this comes from use-cases. You have a different use-case >> when installing a machine and different use case when you want to tune >> your partitioning or get more info about disks/partitions on your >> running system. >> >> Of course, there are more ideas that I'd write here just after seeing >> the partitioner after a few weeks without using it but this is >> already enough. > > Yes, the whole think needs to be redesigned from the ground. But we > still lack that new "vision" that really rings the bell about how things > should be. I would not dare to say "redesigned", I'd say "rethought". So, what are my expectations? The UI should be... 1. Understandable for the first sight 2. Based on real use-cases (we need to collect them first) 3. Fewer is more (in meaning: better) 4. But not too few (insufficient) 5. We might need Wizards to setup complex things too 6. Using more UI possibilities if that helps (e.g., Device graph) Don't let me think http://www.scottsdevelopers.com/dont-make-me-think-revisited.pdf Anyway, please, don't get me wrong. I believe that the team does a great job making the YaST Disk better and better and especially I do thank Ancor for driving that thing! :) -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌍 It's not too late to changee ourselves ⧖ ☂ Handle with care - Your reply can be stored in the cloud 🎃 IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org [View Less]

1 0

[yast-devel] Moving past CSS for the Installer
by Stasiek Michalski 30 Jan '20

30 Jan '20

Hi, I have been thinking about this for quite a while, and decided it might be a good time to take action in this direction. As you might know, we use an extensive set of CSS files to make our installation medium look like it looks. However since those CSS files are CSS2, because Qt pretty much abandoned CSS in Qt entirely, and it's probably going to be removed at some point. I have asked KDE maintainers how hard it would be to compile Breeze without Kfluff, and while possible, it's not … [View More]

2 2

[yast-devel] YaST:Head - removed "openSUSE Leap 15.0" build target
by Ladislav Slezak 29 Jan '20

29 Jan '20

Hi all, JFYI: because openSUSE Leap 15.0 is out of support for almost 2 months and to save some OBS build power I have removed that distribution from YaST:Head. -- 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

1 0

[yast-devel] YaST Sprint 92 Report
by Martin Vidner 27 Jan '20

27 Jan '20

* Partitioner: An Actionable Overview Screen * Not only Partitioner: Numeric Sorting in Tables * Improving the NFS Module * Package Installation: * Installation Progress Improvements * Doomsday Preparations: Retracted Packages * Qt Package Selection Gets Faster https://lizards.opensuse.org/2020/01/24/highlights-of-yast-development-spri… -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner

1 0

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

27 Jan '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 (226 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (193 days) https://github.com/yast/yast-bootloader/pull/564 … [View More]

1 0

[yast-devel] Re: Partitioner: changing the default tab
by Ancor Gonzalez Sosa 24 Jan '20

24 Jan '20

First of all, I'm moving this discussion to the yast-devel mailing list. This is not internal team stuff. On 1/23/20 3:36 PM, David Díaz wrote: > Hi folks! > > As part of my current PBI[1], I must raise a discussion about the > default behavior of pages with tabs in the Partitioner :) > > The question is simple, should we really display the "Overview" tab by > default? During the planning, it seems to some of us that it is useless > most of the time. Taking a disk … [View More]with three partitions as an example, we > think it could be more practical to directly land in the "Partitions" tab. > > As it is related to the UI, I put Ken as CC since I'd like to involve > him in the discussion. > > So, what do you think? Let's clarify what we are discussing here. David is implementing something that, so far, has been agreed as a reasonable first step. Let's say you are in the "Partitions" tab of sda with the second partition selected on the table. Then you jump to another device, and then another and another, and finally you click in "sda" again. You will land in the "Partitions" tab with the second partition pre-selected in the table (if that partition still exists). So far, so good. But what we are discussing here is which should be the active tab the very first time you visit a given device. As said, currently is always the first one... and that one is "Overview" for all devices. Is that the most useful tab? Maybe not in all cases. Why are we landing there then? The point is that the time in which you used a disk only to create partitions on it and a software RAID only as some kind of virtual partition are gone. Now you can use a disk to directly format it, something relatively common for pendrives and for data volumes in servers. And you can use a software RAID as some kind of virtual disk in which you create partitions, apart from formatting the RAID directly (which was the only option in the old partitioner). And the same applies to Bcache devices, that you can also format directly or break into partitions... That's why we decided to always land in the first tab, that is "Overview" for all devices... as the most simplistic approach. This week Iván suggested to auto-select the default tab based on the content of the device. If the disk/RAID already contains a partition table, the default tab would be "Partitions". If not, it would be "Overview". It makes a lot of sense and it's likely the best way to reduce the number of clicks. But I fear it can be confusing. Many users will not realize why the hell the Partitioner chooses one tab or another for different devices. Arvin pointed that the old Partitioner tries to always keep the same tab as long as you are visiting devices of the same type. I mean, if you go to sda->partitions and then click on sdb, you will land in the "Partitions" tab of sdb because that's where you were in the previous disk. Same applies to LVM (being in "vg0->physical volumes" and clicking on vg1 will take you to "vg1->physical volumes") and other kind of devices. So we are not sure what is the best approach here. All the ideas has pros and cons. Cheers > > [1] Remember tabs per node - https://trello.com/c/KlqgBHnp -- 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 [View Less]

1 0

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

20 Jan '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 (219 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (186 days) https://github.com/yast/yast-bootloader/pull/564 … [View More]

1 0

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

13 Jan '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 (212 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (179 days) https://github.com/yast/yast-bootloader/pull/564 … [View More]

1 0

[yast-devel] Refactoring areas and/or modules with several bugs
by Ancor Gonzalez Sosa 07 Jan '20

07 Jan '20

I've gone through the full list of bugs assigned to the YaST Team or some of its members with the intention of closing obsolete stuff that are not real issues anymore. In the process I found out there are some YaST modules or areas that have quite some open bugs. Some of them are modules that never receive attention (no-man shows, as HuHa likes to call them). Localization bugs (mainly problems with non-latin languages): 22 open bugs dns-server && dhcp-server (they are so related that … [View More]

5 5

[yast-devel] I have ported yast-storage-ng to Crystal
by Ancor Gonzalez Sosa 06 Jan '20

06 Jan '20

Ok, and now that I got your attention, let's rephrase the subject into something more realistic: "I'm starting to port to Crystal a very small and limited subset of yast-storage-ng". See more details at https://github.com/ancorgs/y3storage Is something I wanted to do in the past Hack Week... and in the previous one... and so on. So finally I used the downtimes of my recent trip to Nuremberg and some vacation time to get it started. Since next Hack Week will take place soon, I hope to … [View More]

3 8

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

06 Jan '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 (205 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (172 days) https://github.com/yast/yast-bootloader/pull/564 … [View More]

1 0