YaST Development January 2017

yast-devel@lists.opensuse.org

11 participants
37 discussions

[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 as well), with Overcommit you can easily avoid that. I have tried several Overcommit checks: - Rubocop - runs Rubocop at "commit" - Rspec - runs the tests before "push" - Branch blacklist - can forbid direct commits to configured branches, e.g. "master" (forces using pull requests, avoids commits to master my mistake) - Commit message spellcheck - warns when there is a possible typo Check my blog post [2] for the details, esp. watch the recorded screencast where I wanted to show some mistakes which it can catch. The tool looks promising, I'll try using it for some time. If you want to try it as well check the blog post for the installation steps. Enjoy! [1] https://github.com/brigade/overcommit [2] http://blog.ladslezak.cz/2016/06/06/overcommit/ -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

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 "knowledgebase" file. If you have better tricks or find something wrong simply change it, it's a wiki ;-) Ladislav [1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks -- 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

2 1

[yast-devel] HOWTO: Screencast recording
by Ladislav Slezak 22 Jul '17

22 Jul '17

Hi all, Yesterday I published a short blog post about recording a screencast (a desktop session) to create a video or an animated image. So if you want to have nice animated images in READMES [1] or in pull requests [2] then check this post [3]. Enjoy! [1] https://github.com/lslezak/build-rake/blob/master/README.md [2] https://github.com/yast/yast-registration/pull/240 [3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

[yast-devel] YaST Google Summer of Code projects
by Ancor Gonzalez Sosa 02 Feb '17

02 Feb '17

In only a couple of weeks the application period for organizations to Google Summer of Code will be closed. Do we plan to offer some YaST project? First of all, we could resurrect/re-offer these two if the mentors are still interested https://github.com/openSUSE/mentoring/issues/12 https://github.com/openSUSE/mentoring/issues/11 What do you think about those two? Moreover, I'm thinking about creating a new one to re-write the YaST keyboard management in a proper object oriented way. The current code is a mess, the adaptation to systemd was painful and is still not perfect and we usually get bug reports from users that confuse system-wide settings with desktop specific ones (usability problem). On the other hand, writing it from scratch should be rather easy. Is not that difficult and is not that big. Even doing everything in the proper way (implementing systemd just as one possible backend so we are ready for the next big change), it should perfectly fit into a GSoC project. What do you think this one? 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 1

[yast-devel] YaST Hack Week ideas
by Ancor Gonzalez Sosa 02 Feb '17

02 Feb '17

I created three Hack Week projects related to YaST. I'm still not sure in which one I will work, but I thought it was worth sharing here: yast2-storage-ng as a libstorage-ng wrapper. POC https://hackweek.suse.com/15/projects/1854 Use linear programming for the partitioning proposal https://hackweek.suse.com/15/projects/1864 yast2-journal as the new default YaST log viewer https://hackweek.suse.com/15/projects/1882 In fact, the third one is not "hackweekish" enough for us. Is something we should find time to do during our daily business. But still I will leave it there for people wanting to get started with YaST (and just in case I have a spare day at the end of the week). 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

2 1

[yast-devel] Docker & Travis Gist
by Ladislav Slezak 31 Jan '17

31 Jan '17

Hello, I gave a short presentation about Docker and Travis internally but the short summary gist I made might be useful also for the public as a quick Docker crash course: https://gist.github.com/lslezak/ebf13dbf584685b6b86f5f3cc57ab9e7 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 31 Jan '17

31 Jan '17

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-add-on: - Handling in URLs (276 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (40 days) https://github.com/yast/yast-bootloader/pull/393 - [no merge] try codecov reports (195 days) https://github.com/yast/yast-bootloader/pull/355 Pending requests in repository yast-control-center-gnome: - remove useless changlog, (41 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (189 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-mail: - BNC#994317 yast2 mailserver does not preserve startup setting (160 days) https://github.com/yast/yast-mail/pull/22 Pending requests in repository yast-network: - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (25 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (83 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - Added yast2-sw_single-wrapper to handle rpms in Plasma (111 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (118 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (161 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (125 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Build ruby-lint definitions (215 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (158 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (117 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (243 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-sound: - [WIP] (L3) SP4 soundcard DB update (193 days) https://github.com/yast/yast-sound/pull/19 Pending requests in repository yast-storage: - Add option to disable swap creation (89 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (89 days) https://github.com/yast/yast-storage/pull/155 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] Pending Pull Requests
by yast-ci＠opensuse.org 30 Jan '17

30 Jan '17

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-add-on: - Handling in URLs (275 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (39 days) https://github.com/yast/yast-bootloader/pull/393 - [no merge] try codecov reports (194 days) https://github.com/yast/yast-bootloader/pull/355 Pending requests in repository yast-control-center-gnome: - remove useless changlog, (40 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (188 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-mail: - BNC#994317 yast2 mailserver does not preserve startup setting (159 days) https://github.com/yast/yast-mail/pull/22 Pending requests in repository yast-network: - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (24 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (82 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - Added yast2-sw_single-wrapper to handle rpms in Plasma (110 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (117 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (160 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (124 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Build ruby-lint definitions (214 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (157 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (116 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (242 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-sound: - [WIP] (L3) SP4 soundcard DB update (192 days) https://github.com/yast/yast-sound/pull/19 Pending requests in repository yast-storage: - Add option to disable swap creation (88 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (88 days) https://github.com/yast/yast-storage/pull/155 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] Pending Pull Requests
by yast-ci＠opensuse.org 27 Jan '17

27 Jan '17

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-add-on: - Handling in URLs (272 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (36 days) https://github.com/yast/yast-bootloader/pull/393 - [no merge] try codecov reports (191 days) https://github.com/yast/yast-bootloader/pull/355 Pending requests in repository yast-ca-management: - Docker at travis, build deps cleanup (6 days) https://github.com/yast/yast-ca-management/pull/13 Pending requests in repository yast-control-center-gnome: - Use Docker at Travis (7 days) https://github.com/yast/yast-control-center-gnome/pull/27 - remove useless changlog, (37 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (185 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-mail: - BNC#994317 yast2 mailserver does not preserve startup setting (156 days) https://github.com/yast/yast-mail/pull/22 Pending requests in repository yast-network: - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (21 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (79 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - Added yast2-sw_single-wrapper to handle rpms in Plasma (107 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (114 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (157 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (121 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Build ruby-lint definitions (211 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (154 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (113 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (239 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-sound: - [WIP] (L3) SP4 soundcard DB update (189 days) https://github.com/yast/yast-sound/pull/19 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] The Desktop Selection Screen
by Ladislav Slezak 26 Jan '17

26 Jan '17

Hello all, I'd like to discuss this issue https://progress.opensuse.org/issues/14936 with title "revamp the desktop selection screen". It's all about this [1] dialog. We were discussing this feature on the SCRUM planning meeting and it turned out that we actually need to better understand the reasons for the change. The problem is that the desktop selection cannot be easily replaced by the pattern selection because there are several technical and UX issues: 1) The pattern selector [2] contains the "Details" button which starts the full package selection [3]. That means the user can also select individual packages, change some package management flags, etc... That means we would need to disable (remove) that button and this would require a change in the API between the Ruby code and the libyui frontends (ncurses, Qt). 2) Another problem is that after manual pattern selection we would need to remember the selected patterns. The software selection can be reset later in the installation proposal in some specific situations. In the past there was a combobox which allowed resetting the proposal explicitly by user, that's gone. But IIRC the reset still could be invoked by YaST itself... And in that case we need to restore the original user selection. (These two issues are not critical, just be aware that the change might not be that simple as it might seem on the first look...) 3) Selecting the individual patterns might a bit strange from UX POV I think. If you choose KDE or GNOME you can still change the selected patterns or packages later in the SW proposal. Would it make more sense to just offer the "Text mode" and/or "Minimal X" options and leave the user to modify/extend that later? We would probably need to mention this fact directly at the desktop dialog as currently it's not clear that the package selection can be fine tuned (or even change completely) later... So the question is what is actually the use case behind? Ludwig, what you want to achieve or what's the problem with the current approach? The issue mentions only obsolete or unmaintained XFCE or E17n, could we simply remove them and offer something else? Any other opinions or ideas how to improve this dialog? [1] http://paste.opensuse.org/45768232 [2] http://paste.opensuse.org/67757978 [3] http://paste.opensuse.org/59910543 -- 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

3 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development January 2017