YaST Development December 2013

yast-devel@lists.opensuse.org

16 participants
41 discussions

[yast-devel] Improved exception handling in Yast

by Josef Reidinger

Hi, I would like to announce, that new version of ruby bindings (3.1.2) is released. There is two changes: 1. Detect if there is invalid response type from client ( client call using component system, so only simple types are allowed ) - https://github.com/yast/yast-ruby-bindings/issues/81 2. Improved exception handling. Now if exception appear in client, then error message about internal error is shown to user. It using Report.Error so it works good in various cases ( TUI, autoyast, CLI ). After report it works as before, so client return nil and continue. Reason for this change is to reduce number of silent failures and encourage everyone to use exceptions in yast code. I think we need some rules for exceptions. My proposel is to use exceptions everywhere and every uncaught exception is bug. This behavior allows us to quickly see problem and do not have current silent failures. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 years, 7 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-bootloader: https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-network: https://github.com/yast/yast-network/pull/131 https://github.com/yast/yast-network/pull/128 Pending requests in repository yast-nfs-server: https://github.com/yast/yast-nfs-server/pull/12 Pending requests in repository yast-s390: https://github.com/yast/yast-s390/pull/3 Pending requests in repository yast-storage: https://github.com/yast/yast-storage/pull/13 https://github.com/yast/yast-storage/pull/9 Pending requests in repository yast-yast2: https://github.com/yast/yast-yast2/pull/149 https://github.com/yast/yast-yast2/pull/128 https://github.com/yast/yast-yast2/pull/127 https://github.com/yast/yast-yast2/pull/116 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 years, 7 months

[yast-devel] jenkins autosubmit to factory

by Josef Reidinger

Hi, today I plan to modify jenkins to do this stuff. It was done only partial, because when my script run, maintenance update of jenkins start ( I get no info that it is planned, Daniel and Bernhard added to CC ). So some job have it and few doesn't. I plan to run script again on Monday, so all jobs will have it. To not loose the script add it to devtools[1], so next time it will be faster ( now it took me with writting script and reading API documentation around half of hour ) and everyone can reuse it. Josef [1] https://github.com/yast/yast-devtools/pull/39 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 years, 7 months

[yast-devel] Pending Pull Requests

by yast-ci＠opensuse.org

7 years, 7 months

[yast-devel] New Installer: Sprint Review 2013-12-06

by Lukas Ocilka

Generic ------- - Please keep Trello UP-TO-DATE - Summarize and follow up on discussion about packages needed for installation images (Steffen to summarize the needs) - Find a way how to preserve network settings set in Linuxrc also in installer and on a running system (Martin, Michal, Steffen) - Backup for Yast modules DE/CZ - needs the whole team Josef ----- Done: #1 Fixed DVD - bootloader / futils #2 Remote storage (FCoE, iSCSI, ...? all from one crossroad) - waiting for Ihno to file a bug, copy the issue to Trello #3 Control file cleanup #4 auto-check pull requests - almost done, will be finished today Tasks: #1 Finish auto-checking for rotting pull requests #2 Implement AutoYaST workflow asking for missing parts Martin ------ Done: #1 Angelo's patches needed some time, will be finished early next week, building and submitting libyui Tasks: #1 Finish the patches review #2 Have a custom cmake for Qt5 next week Ladislav -------- Done: #1 2nd stage for AutoYast (works, tested, verified, fixed) #2 SCC plans / discussions - started, now having new dialog with email and reg-code, will continue together with SCC team #3 Translations issue in 13.1 - fixed Yast part Tasks: #1 Registration together with SCC team #2 Check the possibility to use Studio API gem (or the approach) for working with SCC Michal ------ Done: #1 Still ill Tasks: #1 Discuss persistence of network settings set in Linuxrc further in Yast and on the installed system Steffen ------- Done: --- Tasks: #1 add update option to linuxrc for SLE #2 Add media verify option to linuxrc for SLE Lukas ----- Done: --- (sorry) Tasks: #1 Test upgrade from 12.3 / 13.1 Jiri ---- Done: #1 Workflow summary (dialogs) - find them in Trello #2 OEM images installation - started discussing that with Marcus, will need some more time Tasks: #1 Continue with OEM images installation -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 years, 7 months

[yast-devel] Pending Pull Requests

by yast-ci＠opensuse.org

7 years, 7 months

[yast-devel] Blog about strategy how to refactoring without good tests

by Josef Reidinger

Hi, I found this blog post, that looks like really describe current yast situation and provide some hints how to deal with weak test coverage and technical debt - http://blog.codeclimate.com/blog/2013/12/05/refactoring-without-good-tests/ Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 years, 7 months

[yast-devel] Re: [yast-installation] Call hooks for installation clients (#107)

by Lukas Ocilka

On 12/03/2013 10:44 AM, vmoravec wrote: > This is the UI widget that is displayed right before the reboot dialog: > hooks-ui-widget-with-results > <https://f.cloud.github.com/assets/1215576/1662430/e6e98fb0-5bfe-11e3-80e8-5…> > > If there are several hook files with output for a single hook > checkpoint, there are concatenated into one line and separated by a > semicolon. It's a great idea to show summary of failed hooks at the end of installation. I would just tune it a bit and show the results ONLY if there were some issues. I'd skip everything that is not needed in case of success. Bye Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 years, 7 months

[yast-devel] New Installer: Sprint Review 2013-11-29

by Lukas Ocilka

Generic ------- Most annoying bugs in openSUSE need solving. - RAID - needs Arvin - Translation issues - Ladislav (L#4) - Backup for Yast modules DE/CZ - needs the whole team - Open pull requests - automatically check (J#4) - report if they are inactive for too long (e-mail) Josef ----- Done: Initial network auto-setup, getting auto-location was postponed, remote storage (3/4 done) Tasks: #1 Fix DVD - bootloader / futils #2 Remote storage (FCoE, iSCSI, ...? all from one crossroad) #3 Control file cleanup #4 auto-check pull requests Martin ------ Done: sick Tasks: #1 Continue with porting to Qt5 Ladislav -------- Done: Wicked integration review (WIP), AutoYast testing (1/2) Blocked: AutoYast by Services Manager issue Tasks: #1 2nd stage for AutoYast (should work, test, verify, fix) #2 SCC plans / discussions #3 AutoYast - ask for missing parts #4 Translations issue in 13.1 #5 VERSION files vs .spec files - finish Michal ------ Done: sick Next: ... and will continue Lukas ----- Done: Got a UI proposal from Ken, will share some next version Tasks: #1 Test upgrade from 13.1 to "our Factory" using NI Jiri ---- Done: Default Bugzilla assignee WIP Blocked: SCC is blocked now Tasks: #1 Workflow summary (dialogs) #2 OEM images installation -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 years, 7 months

[yast-devel] Submit requests to YaST:Head OBS repository have been disabled

by Ladislav Slezak

Hi all, I have disabled submit requests to YaST:Head OBS repository because the packages are developed at Github and are automatically submitted by Jenkins. If anybody (usually outside the Yast team) creates a submit request in OBS to YaST:Head we need to reject it and tell the submitter how to do it properly via Github. Therefore I decided to disable submit requests completely. >From now, if you try to send a submit request to YaST:Head it will not be allowed and you will see this error message: The YaST packages are developed at Github (https://github.com/yast or https://github.com/libyui) and are automatically submitted to YaST:Head OBS project by Jenkins CI (http://ci.opensuse.org/view/Yast/) after each Git commit (if the testsuite passes). See "CONTRIBUTING.md" file at the respective Github repository for more details. You can also contact Yast developers at #yast irc.freenode.org or yast-devel(a)opensuse.org (http://lists.opensuse.org/yast-devel/) mailing list. It is configured in "OBS:RejectRequests" attribute at https://build.opensuse.org/project/attributes/YaST:Head, feel free to improve the message if you think something is wrong or missing... Any objections to this? -- 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

7 years, 7 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 December 2013