August 2012 - YaST Development - openSUSE Mailing Lists

[yast-devel] Disturbing branches at GitHub (broken/...)
by Lukas Ocilka 22 Mar '13

22 Mar '13

Hi, You've probably already found out that there are a lot of "broken" branches at our GitHub repositories: For instance: * upstream/broken/master * upstream/broken/openSUSE-10_0 * upstream/broken/openSUSE-10_1 * upstream/broken/openSUSE-10_2 * ... AFAIK, these branches were left there from the unsuccessful migration from SVN to GitHub. So, what are we going to do with them? From my point of view, they are not needed and just disturb there. Thanks in advance Lukas -- Lukas Ocilka, 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

6 10

[yast-devel] Assert::Equal(happy_developer, better_tests);
by Martin Vidner 23 Aug '12

23 Aug '12

Hi, hackers, as you know, currently yast2-testsuite does little to help you write good tests. See a test suite which recently acquired a new test: (hey, I was young and stupid!) https://github.com/yast/yast-nfs-server/blob/1e4975d1b8c616683c0e25f1797e03… https://github.com/yast/yast-nfs-server/blob/1e4975d1b8c616683c0e25f1797e03… However, things are improving. Please use Assert, available in yast2.rpm since SP2 I think: Assert::Equal(any expected, any actual); Assert::EqualMsg(any expected, any actual, string logged_if_it_fails); https://github.com/yast/yast-yast2/blob/master/library/modules/Assert.ycp That way you get a much better output for a failed test than true -true +false true Enjoy, and send comments, wishes and patches for even better testing! -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] [PATCH 0/3] Snapper: propose some configuration options
by Ondrej Kozina 22 Aug '12

22 Aug '12

Hi Arvin! First, let me thank you for a great tool to handle various snapshots, i've played with it for a few hours and I think it's a great piece of utility. We would like to get snapper into Fedora official repository (and hopefully extend snapper's user/test base). Unfortunately Fedora doesn't support Ext4 snapshots in any way, so I have to to disable this feature inside snapper tool. Sure, I can create private patches for Fedora only which would cut out these snapshots, but I think it would be nice to have configuration option that would disable some unwanted features eventually. So I propose some very simple patch set that let you choose what snapshot types you want to disable. With regards Ondrej Kozina Ondrej Kozina (3): Avoid segfault if unknown/unsupported filesystem is passed by parameter Add basic configuration options to disable some features Add defines into source code to support configuration time parameters configure.in | 25 +++++++++++++++++++++++++ snapper/Filesystem.cc | 28 +++++++++++++++++++++++----- snapper/Filesystem.h | 10 +++++++--- 3 files changed, 55 insertions(+), 8 deletions(-) -- 1.7.8.6 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 5

[yast-devel] QWebYaST applet moved to GitHub
by Ladislav Slezak 20 Aug '12

20 Aug '12

Hi all, we have QWebYaST tool included in WebYaST, it's a simple desktop applet which can start or stop WebYaST server easily from desktop. (Many thanks to Thomas!) Unfortunately the sources were located at internal Git server and were not publicly available. I just have moved the repository to GitHub so it is available for all users. The URL is now: https://github.com/webyast/qwebyast Enjoy! :-) -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- 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] README[.markdown|md] in your YaST project at GitHub
by Lukas Ocilka 16 Aug '12

16 Aug '12

Hi, It's a good practice to have some README file in your GitHub project. It makes the project easier to understand and use. That's why I suggest to use at least a minimalistic one, for instance the one we have in https://github.com/yast/yast-yast2 project. Here's the RAW data for README.markdown: --- cut --- # YaST ${NAME} - ${WHAT_IS_THE_PROJECT_GOOD_FOR} # This repository contains basic set of shared libraries and so-called SCR agents used for reading and writing configuration files and some even for executing commands on the system. ${REPLACE_WITH_SHORT_DESCRIPTION} ## Installation ## make -f Makefile.cvs make sudo make install ## Running Testsuites ## make check ## Links ## * See more at http://en.opensuse.org/openSUSE:YaST_development --- cut --- Thanks & Bye Lukas -- Lukas Ocilka, 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

1 0

[yast-devel] Snapper destructor
by Erik Westrup 14 Aug '12

14 Aug '12

Hello, when I issue snapper commands sometime the program leaves a logfile in CWD called "Snapper destructor" with contents like 2012-08-12 00:01:01 MIL libsnapper(725) Snapper.cc(~Snapper):85 - Snapper destructor 2012-08-12 01:01:01 MIL libsnapper(597) Snapper.cc(~Snapper):85 - Snapper destructor 2012-08-12 02:01:01 MIL libsnapper(1232) Snapper.cc(~Snapper):85 - Snapper destructor 2012-08-12 03:01:01 MIL libsnapper(634) Snapper.cc(~Snapper):85 - Snapper destructor 2012-08-12 04:01:02 MIL libsnapper(596) Snapper.cc(~Snapper):85 - Snapper destructor 2012-08-13 22:01:01 MIL libsnapper(549) Snapper.cc(~Snapper):85 - Snapper destructor I'm starting to get annoyed by these files. How come they are produced and how can I disable them? $ snapper --version snapper 0.0.13 $ uname -a Linux irvine 3.4.8-1-ARCH #1 SMP PREEMPT Thu Aug 9 21:21:22 CEST 2012 x86_64 GNU/LINUX Thanks, -- Erik Westrup <erik.westrup(a)gmail.com> (+46) 0738-286060 | 2r.se Lagerbrings väg 8E, SE-22460 Lund, Sweden ----------------------------------------- This e-mail is encrypted with 2ROT-13. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 5

[yast-devel] renaming/moving github yast-- project
by Jiří Suchomel 14 Aug '12

14 Aug '12

Hi, I think there's actually time to remove Gloves github repository (https://github.com/yast/yast--) to something reflecting the new name we've chosen. Options: 1. rename to Gloves, stay under YaST organization 2. rename to Gloves and move to a) openSUSE or b) SUSE organization 3. create own Gloves organization Option 1 would not help to see the project as independent from current YaST. I would go for 2a. Your opinions? Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 6

[yast-devel] Gloves - RFC chrooting and new calls for agents
by Josef Reidinger 14 Aug '12

14 Aug '12

Hi, automatic chrooting for config agents stop working. Reason is that now there is no layer between glove library and agents and it is called directly, so it cannot be hooked with global options ( I plan also add default env changer for scripts ). So question is how to change it. There is need to add some place where such global changes can be done. I think that it can be done in base class, but to affect child it is not possible to use same name ( otherwise inheritance take effect ). Inspired by ActiveModel I think that we can have different method to call and different method where it is in fact implemented. So proposal is to have methods read/write that is called from glove, but in config agent implementation will be in methods load/save(or store?). Jiri Suchomel argument, that methods should be similar to avoid confusion like read_implementation/write_implementation or similar method. Just to compare another approach could be some kind of block settings, so all agents contain in read/write method something like general_options(options) do #implementation end Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 4

[yast-devel] Execute something after yast dialog
by Nold 03 Aug '12

03 Aug '12

Hi, i wanted to use YaST as a gui for a script. Now everything on the ycp/script coding is done, but i can't get yast to start the script after the Dialog. Is there any other possibility then SCR::Execute? Thanks a lot! MfG Nold -- 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] WebYaST - new home page!
by Ladislav Slezak 01 Aug '12

01 Aug '12

Hi all, I'd like to announce new WebYaST home page, which is available here: http://webyast.github.com/webyast/ This should be a new home page for WebYaST project. It's focused on users who do not know WebYaST at all and are interested in basic features (what it can do, how it can be installed, etc...) This should be kind of "selling" or "marketing" page for WebYaST. We still keep wiki (http://en.opensuse.org/Portal:WebYaST) as the main technical resource (documentation, implementation details, advanced topics...) and just link some interesting articles there. I'm interested in your feedback, hints, improvements... Thanks in advance! (BTW you can create home page for any GitHub project quite easily, see https://help.github.com/articles/creating-project-pages-manually or http://pages.github.com/ ) -- 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 2