March 2017 - 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 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-related talks/workshops in oSC'17
by Ancor Gonzalez Sosa 31 Mar '17

31 Mar '17

Just for you information, I have submitted the following two abstracts for openSUSE Conference 2017. I'm sharing them here just to keep track of the YaST-related content we will deliver. Feel free to help with "my" talk/workshop (definitely the workshop would benefit from having different speakers for each technology) or share here the ones you have submitted. FORMAT: 15 min talk TITLE: YaST: from the repository to the distributions SUBTITLE: Continuous testing and delivery, the YaST way ABSTRACT: In this talk we will briefly explore all the mechanisms and workflows used by the YaST developers in order to share as much code as possible between all the SUSE and openSUSE distributions, while ensuring the quality of all the different YaST modules. Learn how Rake, unit tests, Github, Jenkins, Travis, OBS and even Docker are used to deliver the developer's work to the already released products (via maintenance updates), to the ones still to be released and to our rolling distribution Tumbleweed. FORMAT: 3 hours workshop TITLE: Develop a YaST module in the 21st century way SUBTITLE: Enjoyable object-oriented YaST development ABSTRACT: YaST, the openSUSE beloved Swiss army knife, has been around since 1996. The history of quite some components still present in the current version can be tracked back to 1999. In 2013 the code was automatically converted from YCP, a purpose-specific procedural programming language, to Ruby, a general-purpose object oriented one. Since then, the YaST team has been trying to steady replace many YCP components and paradigms with new object-oriented, test-driven ones. In this workshop we will develop a new YaST module from scratch using the new Ruby-based approach. That is, object oriented dialogs and clients, CFA to modify the configuration files, Cheetah to execute system commands, RSpec tests and so on. Attendees are expected to be proficient with object oriented programming (preferably Ruby) and to have an recent openSUSE system (can be a virtual machine) to follow the workshop. Having read the YaST development tutorial in advance would definitely be a plus. That's all folks. 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

4 3

[yast-devel] Continued discussion on queries to the Ruby wrapper
by Ancor Gonzalez Sosa 31 Mar '17

31 Mar '17

This is a follow-up on this discussion https://github.com/yast/yast-storage-ng/pull/184#pullrequestreview-29672717 The mail is mainly targeted to Josef, so we continue the discussion in a more persistent and prominent place than a merged pull request. Don't feel guilty if you decide to ignore it. :-) Before introducing the Y2Storage wrapper classes on top of the Storage ones, we had a query API (already discussed in this list) based on the concept of Y2Storage::DevicesLists. I think we don't need that anymore with the wrapper. I would go for an approach based on pure Ruby arrays, now that we don't have to fear not-found exceptions or to care about downcasting. I would simply add the following convenience methods to Y2Storage::Device and that's it. https://github.com/yast/yast-storage-ng/pull/184/commits/0f733850786242cddf… So, how would we query the devicegraph? Let's explain it by example. Most examples are based on real cases I have seen while porting code in other packages... others are there for the sake of the challenge ;) 1) The filesystem, encrypted or not, in a partition. That is, we want the filesystem and we don't care whether there is an encryption (LUKS) layer sitting between the partition and that filesystem. 2) The filesystem directly placed in a partition, nil if no filesystem or if the filesystem is not directly there (e.g. there is an encryption layer in between). 3) The encrypted filesystem in a partition, nil if the partition is not formatted or if its directly formatted (without the intermediate encryption layer) 4) The disk that match a disk name or partition name, only if it's GPT 5) Filesystems (encrypted or not) on logical partitions of a given disk 6) Non-encrypted filesystem on logical partitions of a given disk 7) Logical partitions for the disk that match a disk name or contains partition name. 8) From a given set of volume groups, physical volumes that are not directly into a disk (or an encrypted disk) (e.g. they sit in a partition or a RAID device) 9) Checking if a given partition contains a btrfs filesystem (encrypted or not) 10) Disks hosting a given filesystem either directly or through one of its partitions. "Disks" in plural because in our devicegraphs, a filesystem can be lay across several block devices. 11) Disks "supporting" the existence of a given filesystem, for whatever technology is used. For example, if the filesystem is in a LV (LVM) and that LV sits on a VG, we want all the disks hosting the PVs of that VG, either directly or through partitions or RAID devices (yes, this is one of the examples based on real code). 12) Disks of a filesystem, only if the plain disk is directly formatted (no partitions, RAID or encryption involved). Otherwise nil 13) Disks of a filesystem, only if the disk is directly formatted (no partitions), nil otherwise, but supporting encrypted filesystems. 14) Devices with a extX filesystem (encrypted or not) 15) Partitions with a extX filesystem (encrypted or not) How would we do that just with the wrapper and plain arrays? 1) the_partition.blk_filesystem 2) the_partition.direct_blk_filesystem 3) the_partition.encrypted? ? the_partition.blk_filesystem : nil 4) disk = devgraph.disks.detect {|d| d.name_or_partition?(the_name) } (disk && disk.gpt?) ? disk : nil # or disk = Y2Storage::Disk.find_by_name_or_partition(devgraph, the_name) (disk && disk.gpt?) ? disk : nil 5) parts = the_disk.partitions.select {|p| p.type.is?(:logical) } parts.map {|p| p.blk_filesystem }.compact 6) parts = the_disk.partitions.select {|p| p.type.is?(:logical) } parts.map {|p| p.direct_blk_filesystem }.compact 7) disk = devgraph.disks.detect {|d| d.name_or_partition?(the_name) } disk.partitions.select {|p| p.type.is?(:logical) } 8) all_pvs = the_vol_groups.map(&:lvm_pvs).flatten all_pvs.reject { |pv| pv.blk_device.plain_device.disk? } 9) !!(partition.filesystem && partition.filesystem.type.is?(:btrfs)) 10) # See notes below devgraph.disks.select do |d| d.filesystem == the_filesystem || d.partitions.any? {|p| p.filesystem == the_filesystem } end # Beware, this is not equivalent because it also returns filesystems in # partitions of a software RAID or any other partitionable device that # is not a disk the_filesystem.ancestors.select do |a| (a.disk? || a.partition?) && a.filesystem == the_filesystem end 11) the_filesystem.ancestors.select(&:disk?).uniq 12) filesystem.blk_devices.select(&:disk?) 13) filesystem.plain_blk_devices.select(&:disk?) 14) all_ext = devgraph.blk_filesystems.select {|fs| fs.type.is?(:ext) } all_ext.map {|fs| fs.plain_blk_devices }.flatten 15) devgraph.partitions.select do |p| p.blk_filesystem && p.blk_filesystem.type.is?(:ext) end Feel free to provide more "challenges" and/or test alternative API against the current ones. And yes, before you ask, it would make sense to add this to BlkDevice alias_method :filesystem, :blk_filesystem alias_method :direct_filesystem, :direct_blk_filesystem Moreover, if we find ourselves too often checking for something in a disk and all its partitions, we could add a convenience method Y2Storage::Partitionable#this_and_partitions. Then some examples would change a bit, like: 10) devgraph.disks.select do |d| d.this_and_partitions.any? {|i| i.filesystem == the_filesystem } end Looking forward alternatives and/or feedback. 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 4

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 31 Mar '17

31 Mar '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: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (51 days) https://github.com/yast/yast-add-on/pull/37 - Handling in URLs (8 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-autoinstallation: - Storage ng autoyast handling (10 days) https://github.com/yast/yast-autoinstallation/pull/292 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (10 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (21 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-core: - Replace y2base (27 days) https://github.com/yast/yast-core/pull/119 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (248 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Replace y2base (27 days) https://github.com/yast/yast-installation/pull/529 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (16 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-mail: - return back MailTable to yast2-mail module from yast2 module (35 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (10 days) https://github.com/yast/yast-network/pull/503 - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (84 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (142 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (50 days) https://github.com/yast/yast-packager/pull/230 - Added yast2-sw_single-wrapper to handle rpms in Plasma (170 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (177 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (220 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (184 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (30 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (302 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-storage: - Add option to disable swap creation (148 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (148 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-theme: - Add yast2-branding-openSUSE-Oxygen (54 days) https://github.com/yast/yast-theme/pull/74 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 Mar '17

30 Mar '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: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (50 days) https://github.com/yast/yast-add-on/pull/37 - Handling in URLs (7 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-autoinstallation: - Storage ng autoyast handling (9 days) https://github.com/yast/yast-autoinstallation/pull/292 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (9 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (20 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-core: - Replace y2base (26 days) https://github.com/yast/yast-core/pull/119 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (247 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Replace y2base (26 days) https://github.com/yast/yast-installation/pull/529 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (15 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-mail: - return back MailTable to yast2-mail module from yast2 module (34 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (9 days) https://github.com/yast/yast-network/pull/503 - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (83 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (141 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (49 days) https://github.com/yast/yast-packager/pull/230 - Added yast2-sw_single-wrapper to handle rpms in Plasma (169 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (176 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (219 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (183 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (7 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-samba-server: - Fixed string comparison. (bsc#1029528) (13 days) https://github.com/yast/yast-samba-server/pull/47 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (29 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (301 days) https://github.com/yast/yast-snapper/pull/40 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 29 Mar '17

29 Mar '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: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (49 days) https://github.com/yast/yast-add-on/pull/37 - Handling in URLs (6 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-apparmor: - Systemd Service handling (16 days) https://github.com/yast/yast-apparmor/pull/9 Pending requests in repository yast-autoinstallation: - Storage ng autoyast handling (8 days) https://github.com/yast/yast-autoinstallation/pull/292 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (8 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (19 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-core: - Replace y2base (25 days) https://github.com/yast/yast-core/pull/119 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (246 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Replace y2base (25 days) https://github.com/yast/yast-installation/pull/529 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (14 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-mail: - return back MailTable to yast2-mail module from yast2 module (33 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (8 days) https://github.com/yast/yast-network/pull/503 - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (82 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (140 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (48 days) https://github.com/yast/yast-packager/pull/230 - Added yast2-sw_single-wrapper to handle rpms in Plasma (168 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (175 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (218 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (182 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Return valid repository signature flag (bsc#1009127) (40 days) https://github.com/yast/yast-pkg-bindings/pull/65 - Fixed failure when trying to save a plugin service (bsc#1021117) (4 days) https://github.com/yast/yast-pkg-bindings/pull/64 - [WIP] Build ruby-lint definitions (272 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (6 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-samba-server: - Fixed string comparison. (bsc#1029528) (12 days) https://github.com/yast/yast-samba-server/pull/47 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (28 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (300 days) https://github.com/yast/yast-snapper/pull/40 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 28 Mar '17

28 Mar '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: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (48 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-apparmor: - Systemd Service handling (15 days) https://github.com/yast/yast-apparmor/pull/9 Pending requests in repository yast-autoinstallation: - Storage ng autoyast handling (7 days) https://github.com/yast/yast-autoinstallation/pull/292 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (7 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (18 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-core: - Replace y2base (24 days) https://github.com/yast/yast-core/pull/119 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (245 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Replace y2base (24 days) https://github.com/yast/yast-installation/pull/529 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (13 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-mail: - return back MailTable to yast2-mail module from yast2 module (32 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (7 days) https://github.com/yast/yast-network/pull/503 - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (81 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (139 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (47 days) https://github.com/yast/yast-packager/pull/230 - Added yast2-sw_single-wrapper to handle rpms in Plasma (167 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (174 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (217 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (181 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Return valid repository signature flag (bsc#1009127) (39 days) https://github.com/yast/yast-pkg-bindings/pull/65 - [WIP] Build ruby-lint definitions (271 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-samba-server: - Fixed string comparison. (bsc#1029528) (11 days) https://github.com/yast/yast-samba-server/pull/47 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (27 days) https://github.com/yast/yast-security/pull/40 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 Mar '17

27 Mar '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: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (47 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-apparmor: - Systemd Service handling (14 days) https://github.com/yast/yast-apparmor/pull/9 Pending requests in repository yast-autoinstallation: - Storage ng autoyast handling (6 days) https://github.com/yast/yast-autoinstallation/pull/292 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (6 days) https://github.com/yast/yast-bootloader/pull/414 - don't create grub_installdevice and let perl-Bootloader run grub2-install (17 days) https://github.com/yast/yast-bootloader/pull/413 Pending requests in repository yast-core: - Replace y2base (23 days) https://github.com/yast/yast-core/pull/119 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (244 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Replace y2base (23 days) https://github.com/yast/yast-installation/pull/529 Pending requests in repository yast-ldap: - Manipulate system LDAP configuration rather than application LDAP configuration (12 days) https://github.com/yast/yast-ldap/pull/26 Pending requests in repository yast-mail: - return back MailTable to yast2-mail module from yast2 module (31 days) https://github.com/yast/yast-mail/pull/25 Pending requests in repository yast-network: - routing/firewall: no longer depend on SuSEfirewall2 for IPv4 forwarding (6 days) https://github.com/yast/yast-network/pull/503 - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (80 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (138 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (46 days) https://github.com/yast/yast-packager/pull/230 - Added yast2-sw_single-wrapper to handle rpms in Plasma (166 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (173 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (216 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (180 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Return valid repository signature flag (bsc#1009127) (38 days) https://github.com/yast/yast-pkg-bindings/pull/65 - [WIP] Build ruby-lint definitions (270 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-samba-server: - Fixed string comparison. (bsc#1029528) (10 days) https://github.com/yast/yast-samba-server/pull/47 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (26 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (298 days) https://github.com/yast/yast-snapper/pull/40 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