YaST Development October 2014

yast-devel@lists.opensuse.org

14 participants
43 discussions

[yast-devel] Fixing yast2-slide-show for SLE11 SP3

by Karl Eichwalder

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 years, 10 months

[yast-devel] rspec 3.0

by Josef Reidinger

Hi, in this blog post http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3 is summary of changes in new rspec 3.0. I do not think that we will use it for SLE-12 tests, but maybe it will be used for 13.2. In general I think we should not use new syntax now, but what we can do is to not use deprecated syntax as there is already alternatives to prevent future problems. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 years, 7 months

[yast-devel] who is the maintainer?

by Arvin Schnell

Hi, while reassigning yast-maintainers bugs I noticed that once again the maintainer/bugowner information is inconsistent: The content of the MAINTAINER file in git differs from the output of 'osc maintainer' or 'osc bugowner'. This leads to confusion. We had this problem before and apparently fail to solve the inconsistency long term. So I propose to drop the MAINTAINER file in git and rely on osc. Instead we can have a AUTHORS files so that people not knowing about osc can still reach the authors. Regards, Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 years, 7 months

[yast-devel] Storage Redesign

by Arvin Schnell

Hi, my hackweek project was to evaluate using the boost graph library (BGL) in libstorage. For me the project was interesting and successful. I have documented it at https://github.com/aschnell/libstorage-bgl-eval/wiki. The code is also available there. So now I would like to redesign the storage part of YaST. Here are the main steps required: - Extend libstorage-bgl-eval to fully support disks, partitions and simply filesystems (probing, committing, testmodes, testsuite). - Try to make a compatibility layer. - Make the new API robust against API and ABI changes. - Export new API to Ruby (help would be good) for use by all YaST modules. - Get a simply installation working (two partitions, ext4 and swap). - Extend libstorage-bgl-eval to current libstorage functionality. Maybe drop a few features, e.g. loop-back devices (once used for encryption). - Make the new API suit the needs of all YaST modules (input from other developers required). If required add utility functions. - Make all code in YaST use new API (task for several developers). - Make expert partitioner use new features, e.g. use disks without partition table for filesystems. - Rewrite storage proposal (specification required!). - Finally drop target-map (as decided during workshop). - Drop compatibility layer. In the end yast2-storage would ideally only contain dialogs and no logic for other YaST modules (since all of that moved to libstorage). But if some utility functions are easier to implement in Ruby they can stay there. I assume that altogether the redesigning will take more than half a year. Anyway I think it is required to keep the code maintainable and be prepared for new feature requests. Some existing features request might already be implemented along the way (e.g. https://fate.suse.com/316251). ciao Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 years, 8 months

[yast-devel] RFC: New rules for yast-maintainers

by Lukas Ocilka

Hi, As Gabi has pointed-out today, we have a growing list of bugs reported for Yast, assigned to the default assignee: yast-maintainers. Some of the bugs cannot be fixed easily now as we do not have a single person who would take care about "that particular module", "usability" or "design". For me, this is a perfect way for fixing bugs in an agile way: - Project manager decides what needs to be fixed and when - We will find out who can fix or which expertise we need - And we'll either assign these bugs to respective people in time or try to find help outside But we need to find a way how not to get lost in bugs assigned to yast-maintainers. And there are several possibilities: 1. NEW bug needs to be checked and either reassigned or at least marked as reviewed/confirmed 2. CONFIRMED bug should have a [yast2-*] in Summary, so we know it has been reviewed already / or we could add new keyword e.g. "reviewed". The current "Yast Maintainer" must make sure that summary describes the issue well 3. IN_PROGRESS should have a real assignee, this would need cooperation with PjM/PM, so they set real priority 4. We will definitely not be able to fix all bugs, so there needs to be a way to drop as CANTFIX/WONTFIX according to given criteria 5. Features should be closed as FEATURE and the reported advised to use FATE. 6. Yast maintainer should take care only about bugs that haven't been reviewed, for that a simple search should be possible (e.g.: doesn't contain `reviewed` flag) Please review, and/or come with better ideas. I know this is yet another rule-set, maybe you'll have a better idea. Bye Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 years, 8 months

[yast-devel] Pending Pull Requests

by yast-ci＠opensuse.org

6 years, 9 months

[yast-devel] RE:Take Your Business Online & Make More Sales!

by Delight Africa Limited

Greetings, My name is Daniel and would like to have the privilege of helping you generate additional revenue by offering our cutting-edge web, seo and software services to you. Would you be interested in a possible redesign of your site or additional features that might benefit the overall usability and user experience which usually leads to increased leads and sales? You will be able to get emails such as info(a)yourcompany.com, sales(a)yourcompany.com, or yourname(a)yourcompany.com and much more Custom Dynamic Web Design starting from Ksh.s 10,000 - Mobile enabled We also have CRM - Customer Relationship management system AMS - Asset Management System DMS - Document Management System HRM - Human Resource Planning PMS - Project Management System ERP - Enterprise Resource Planning management System View some of the latest web design projects: http://www.goldenjuices.com http://www.eclipsevaluers.com http://www.interlab.co.ke Contact Details: +254(0)703 745 484 | +254(0)724 566 088 | +254 (0) 722 533771 Location: 4th Floor, Dev Towers, Biashara Street, Nairobi Kenya. Note: - Though this is not an automated email, we keep on sending out these emails to all those people whom we find eligible of using our services. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 years, 9 months

[yast-devel] Travis Support: Scripts

by Lukas Ocilka

Hi, I'm checking the current implementation of Travis support in Yast, which is a great idea indeed. One little issue I have is what the before_install: contains: - curl http://download.opensuse.org/repositories/YaST:/Head:/Travis/xUbuntu_12.04/… | sudo apt-key add - - echo "deb http://download.opensuse.org/repositories/YaST:/Head:/Travis/xUbuntu_12.04/ ./" | sudo tee -a /etc/apt/sources.list From my POV, the "xUbuntu_12.04" is a constant used for ALL Yast module and maybe even the whole before_install: section. So, I was thinking about this: what will happen when we start using newer version of Ubuntu? Will we need to change all .travis.yml files at once? Why this is not solved by a simple script, e.g. [#1]: - prepare_travis yast2-devtools yast2-testsuite \ yast2-perl-bindings yast2 yast2-pam Then we would just need to update one place (the script itself) that would start downloading Release.key from somewhere else. Automation is a great thing, but additional work in the future should be IMO limited. So, what do you think of the proposal? Thanks Lukas #1 https://github.com/yast/yast-samba-client/pull/34/files -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 years, 9 months

[yast-devel] Pending Pull Requests

by yast-ci＠opensuse.org

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: - Travis support (5 days) https://github.com/yast/yast-add-on/pull/20 Pending requests in repository yast-add-on-creator: - Travis support (5 days) https://github.com/yast/yast-add-on-creator/pull/9 Pending requests in repository yast-apparmor: - Travis support (5 days) https://github.com/yast/yast-apparmor/pull/7 Pending requests in repository yast-audit-laf: - Travis support (5 days) https://github.com/yast/yast-audit-laf/pull/3 Pending requests in repository yast-autoinstallation: - Travis support (5 days) https://github.com/yast/yast-autoinstallation/pull/88 Pending requests in repository yast-boot-server: - Travis support (5 days) https://github.com/yast/yast-boot-server/pull/1 Pending requests in repository yast-cluster: - rspec is not needed at Travis (5 days) https://github.com/yast/yast-cluster/pull/23 Pending requests in repository yast-country: - Travis support (5 days) https://github.com/yast/yast-country/pull/43 Pending requests in repository yast-dhcp-server: - Travis support (5 days) https://github.com/yast/yast-dhcp-server/pull/6 Pending requests in repository yast-dns-server: - Travis support (5 days) https://github.com/yast/yast-dns-server/pull/34 - New version for maintenance update (21 days) https://github.com/yast/yast-dns-server/pull/33 Pending requests in repository yast-drbd: - Travis (5 days) https://github.com/yast/yast-drbd/pull/7 Pending requests in repository yast-fcoe-client: - Travis support (5 days) https://github.com/yast/yast-fcoe-client/pull/31 Pending requests in repository yast-firstboot: - Travis support (5 days) https://github.com/yast/yast-firstboot/pull/9 Pending requests in repository yast-http-server: - Travis support (5 days) https://github.com/yast/yast-http-server/pull/12 Pending requests in repository yast-inetd: - Travis support (5 days) https://github.com/yast/yast-inetd/pull/13 Pending requests in repository yast-installation: - Travis support (5 days) https://github.com/yast/yast-installation/pull/239 - Allow to correct upgrade repos (bnc#889791) (12 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-instserver: - install ruby gems from rubygems.org (5 days) https://github.com/yast/yast-instserver/pull/10 Pending requests in repository yast-iplb: - Travis support (5 days) https://github.com/yast/yast-iplb/pull/5 Pending requests in repository yast-iscsi-client: - Removed unnecessary BuildRequires dependencies (7 days) https://github.com/yast/yast-iscsi-client/pull/35 - Travis support (5 days) https://github.com/yast/yast-iscsi-client/pull/34 Pending requests in repository yast-iscsi-lio-server: - Travis support (5 days) https://github.com/yast/yast-iscsi-lio-server/pull/30 Pending requests in repository yast-isns: - Travis support (5 days) https://github.com/yast/yast-isns/pull/8 Pending requests in repository yast-kdump: - Travis support (5 days) https://github.com/yast/yast-kdump/pull/24 - get rid of autotools (23 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-ldap: - Travis support (5 days) https://github.com/yast/yast-ldap/pull/23 Pending requests in repository yast-live-installer: - Travis support (5 days) https://github.com/yast/yast-live-installer/pull/4 Pending requests in repository yast-lxc: - Travis support (5 days) https://github.com/yast/yast-lxc/pull/6 Pending requests in repository yast-mail: - Travis support (5 days) https://github.com/yast/yast-mail/pull/13 Pending requests in repository yast-metapackage: - rspec is not needed at Travis (5 days) https://github.com/yast/yast-metapackage/pull/6 Pending requests in repository yast-multipath: - Travis support (5 days) https://github.com/yast/yast-multipath/pull/10 Pending requests in repository yast-network: - install ruby gems from rubygems.org (5 days) https://github.com/yast/yast-network/pull/268 - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (22 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-nfs-client: - Travis support (5 days) https://github.com/yast/yast-nfs-client/pull/27 Pending requests in repository yast-nfs-server: - Travis support (8 days) https://github.com/yast/yast-nfs-server/pull/20 Pending requests in repository yast-nis-client: - Travis support (5 days) https://github.com/yast/yast-nis-client/pull/20 Pending requests in repository yast-nis-server: - Travis support (5 days) https://github.com/yast/yast-nis-server/pull/5 Pending requests in repository yast-ntp-client: - Travis (5 days) https://github.com/yast/yast-ntp-client/pull/27 Pending requests in repository yast-online-update: - Travis support (5 days) https://github.com/yast/yast-online-update/pull/13 Pending requests in repository yast-online-update-configuration: - install ruby gems from rubygems.org (5 days) https://github.com/yast/yast-online-update-configuration/pull/7 Pending requests in repository yast-openvas-security-scanner: - Travis support (5 days) https://github.com/yast/yast-openvas-security-scanner/pull/2 Pending requests in repository yast-packager: - Travis support (5 days) https://github.com/yast/yast-packager/pull/93 Pending requests in repository yast-pam: - Travis support (5 days) https://github.com/yast/yast-pam/pull/4 Pending requests in repository yast-pkg-bindings: - Travis (9 days) https://github.com/yast/yast-pkg-bindings/pull/35 - Do not reorder baseurls by storing them in a std::set (SLE12 as well!) (14 days) https://github.com/yast/yast-pkg-bindings/pull/34 Pending requests in repository yast-pos-installation: - added COPYING (5 days) https://github.com/yast/yast-pos-installation/pull/3 Pending requests in repository yast-printer: - Travis support (5 days) https://github.com/yast/yast-printer/pull/3 Pending requests in repository yast-product-creator: - Travis support (5 days) https://github.com/yast/yast-product-creator/pull/27 Pending requests in repository yast-proxy: - Travis support (5 days) https://github.com/yast/yast-proxy/pull/4 Pending requests in repository yast-python-bindings: - Travis support (5 days) https://github.com/yast/yast-python-bindings/pull/3 Pending requests in repository yast-reipl: - Travis (5 days) https://github.com/yast/yast-reipl/pull/4 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

6 years, 9 months

[yast-devel] Pending Pull Requests

by yast-ci＠opensuse.org

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: - Travis support (4 days) https://github.com/yast/yast-add-on/pull/20 Pending requests in repository yast-add-on-creator: - Travis support (4 days) https://github.com/yast/yast-add-on-creator/pull/9 Pending requests in repository yast-apparmor: - Travis support (4 days) https://github.com/yast/yast-apparmor/pull/7 Pending requests in repository yast-audit-laf: - Travis support (4 days) https://github.com/yast/yast-audit-laf/pull/3 Pending requests in repository yast-autoinstallation: - Travis support (4 days) https://github.com/yast/yast-autoinstallation/pull/88 Pending requests in repository yast-bootloader: - install ruby gems from rubygems.org (4 days) https://github.com/yast/yast-bootloader/pull/178 Pending requests in repository yast-boot-server: - Travis support (4 days) https://github.com/yast/yast-boot-server/pull/1 Pending requests in repository yast-cluster: - rspec is not needed at Travis (4 days) https://github.com/yast/yast-cluster/pull/23 Pending requests in repository yast-country: - Travis support (4 days) https://github.com/yast/yast-country/pull/43 Pending requests in repository yast-dhcp-server: - Travis support (4 days) https://github.com/yast/yast-dhcp-server/pull/6 Pending requests in repository yast-dns-server: - Travis support (4 days) https://github.com/yast/yast-dns-server/pull/34 - New version for maintenance update (20 days) https://github.com/yast/yast-dns-server/pull/33 Pending requests in repository yast-drbd: - Travis (4 days) https://github.com/yast/yast-drbd/pull/7 Pending requests in repository yast-fcoe-client: - Travis support (4 days) https://github.com/yast/yast-fcoe-client/pull/31 Pending requests in repository yast-firstboot: - Travis support (4 days) https://github.com/yast/yast-firstboot/pull/9 Pending requests in repository yast-http-server: - Travis support (4 days) https://github.com/yast/yast-http-server/pull/12 Pending requests in repository yast-inetd: - Travis support (4 days) https://github.com/yast/yast-inetd/pull/13 Pending requests in repository yast-installation: - Travis support (4 days) https://github.com/yast/yast-installation/pull/239 - Allow to correct upgrade repos (bnc#889791) (11 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-instserver: - install ruby gems from rubygems.org (4 days) https://github.com/yast/yast-instserver/pull/10 Pending requests in repository yast-iplb: - Travis support (4 days) https://github.com/yast/yast-iplb/pull/5 Pending requests in repository yast-iscsi-client: - Removed unnecessary BuildRequires dependencies (6 days) https://github.com/yast/yast-iscsi-client/pull/35 - Travis support (4 days) https://github.com/yast/yast-iscsi-client/pull/34 Pending requests in repository yast-iscsi-lio-server: - Travis support (4 days) https://github.com/yast/yast-iscsi-lio-server/pull/30 Pending requests in repository yast-isns: - Travis support (4 days) https://github.com/yast/yast-isns/pull/8 Pending requests in repository yast-kdump: - Travis support (4 days) https://github.com/yast/yast-kdump/pull/24 - get rid of autotools (22 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-ldap: - Travis support (4 days) https://github.com/yast/yast-ldap/pull/23 Pending requests in repository yast-live-installer: - Travis support (4 days) https://github.com/yast/yast-live-installer/pull/4 Pending requests in repository yast-lxc: - Travis support (4 days) https://github.com/yast/yast-lxc/pull/6 Pending requests in repository yast-mail: - Travis support (4 days) https://github.com/yast/yast-mail/pull/13 Pending requests in repository yast-metapackage: - rspec is not needed at Travis (4 days) https://github.com/yast/yast-metapackage/pull/6 Pending requests in repository yast-multipath: - Travis support (4 days) https://github.com/yast/yast-multipath/pull/10 Pending requests in repository yast-network: - install ruby gems from rubygems.org (4 days) https://github.com/yast/yast-network/pull/268 - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (21 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-nfs-client: - Travis support (4 days) https://github.com/yast/yast-nfs-client/pull/27 Pending requests in repository yast-nfs-server: - Travis support (7 days) https://github.com/yast/yast-nfs-server/pull/20 Pending requests in repository yast-nis-client: - Travis support (4 days) https://github.com/yast/yast-nis-client/pull/20 Pending requests in repository yast-nis-server: - Travis support (4 days) https://github.com/yast/yast-nis-server/pull/5 Pending requests in repository yast-ntp-client: - Travis (4 days) https://github.com/yast/yast-ntp-client/pull/27 Pending requests in repository yast-online-update: - Travis support (4 days) https://github.com/yast/yast-online-update/pull/13 Pending requests in repository yast-online-update-configuration: - install ruby gems from rubygems.org (4 days) https://github.com/yast/yast-online-update-configuration/pull/7 Pending requests in repository yast-openvas-security-scanner: - Travis support (4 days) https://github.com/yast/yast-openvas-security-scanner/pull/2 Pending requests in repository yast-packager: - Travis support (4 days) https://github.com/yast/yast-packager/pull/93 Pending requests in repository yast-pam: - Travis support (4 days) https://github.com/yast/yast-pam/pull/4 Pending requests in repository yast-pkg-bindings: - Travis (8 days) https://github.com/yast/yast-pkg-bindings/pull/35 - Do not reorder baseurls by storing them in a std::set (SLE12 as well!) (13 days) https://github.com/yast/yast-pkg-bindings/pull/34 Pending requests in repository yast-pos-installation: - added COPYING (4 days) https://github.com/yast/yast-pos-installation/pull/3 Pending requests in repository yast-printer: - Travis support (4 days) https://github.com/yast/yast-printer/pull/3 Pending requests in repository yast-product-creator: - Travis support (4 days) https://github.com/yast/yast-product-creator/pull/27 Pending requests in repository yast-proxy: - Travis support (4 days) https://github.com/yast/yast-proxy/pull/4 Pending requests in repository yast-python-bindings: - Travis support (4 days) https://github.com/yast/yast-python-bindings/pull/3 Pending requests in repository yast-reipl: - Travis (4 days) https://github.com/yast/yast-reipl/pull/4 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

6 years, 9 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development October 2014