September 2011 - YaST Development - openSUSE Mailing Lists

[yast-devel] Re: [yast-commit] r65868 - in /trunk/kerberos-server: VERSION missing package/yast2-kerberos-server.changes yast2-kerberos-server.spec.in
by Ladislav Slezak 21 Sep '11

21 Sep '11

Dne 21.9.2011 10:27, mcalmer(a)svn2.opensuse.org napsal(a): > Author: mcalmer > Date: Wed Sep 21 10:27:22 2011 > New Revision: 65868 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=65868&view=rev > Log: > fix license in specfile > > Modified: > trunk/kerberos-server/VERSION > trunk/kerberos-server/missing ^^^^^^^ This file is generated automatically when running Makefile.cvs and is always rewritten by file from automake package and therefore it should be excluded from SVN sources (the same applies also for Makefile.am.common file). -- 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 For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Getting rid of Wizard_hw module
by Stanislav Visnovsky 19 Sep '11

19 Sep '11

Hi! The Wizard_hw module is deprecated for some time and might be a good idea to finally drop it. Unfortunatelly, a lot of modules are using it, although I've looked at some of them - it's not a real use and we could get rid of the module rather easily. I would like to start removing the usage from modules direclty in SVN. Please, let me know if you prefer a patch for your module or remove the dependency by yourself. I think I will start tomorrow (if time permits). Thanks! Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

[yast-devel] YaST2 +EFI Partition
by Günther J. Niederwimmer 15 Sep '11

15 Sep '11

Hello, a question for the size of a EFI Partition? I found a document Novell (7003263) that tell me, the partition "can be" 100-400 MB but yast2 only let me create a partition of 156 MB, in the most time a bigger Partition was mounted as /WINDOWS/C from YaST2? OK, I learning in the moment to install over (U)EFI and have no chance to set up a XEN system with EFI. OT: The Question is only the change to grub2-efi (dualboot) must I have for this a bigger partition? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] Moving SVN to GIT
by Lukas Ocilka 15 Sep '11

15 Sep '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, It's been a long time since I've read about moving our SVN to GIT for the last time. Can you tell us what's the current status? What needs to be done? Where/how can we help? Thanks in advance Lukas - -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFOcG4xVSqMdRCqTiwRAvJWAJ9xGFaoMFnpKnqE7LYm/AW9qA2hVQCfRl77 I/h+9xhR146xRqwralCzOu4= =1YLO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 4

[yast-devel] YaST++: Testing Agents
by Lukas Ocilka 14 Sep '11

14 Sep '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've fixed SCR agent for SuSEfirewall2 recently and wanted to create a testcase for this agent but I gave up after several attempts. Frankly, it's not easy to test an SCR agent in YaST and that's probably why we usually don't do that at all. This brings me to the point: If YaST++ should be shared with Studio and other projects, we need to make sure that "agents" can be easily tested. Do we already have an infrastructure for that? Could you point me to an example? Thanks and Bye Lukas - -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFOcIk3VSqMdRCqTiwRAptRAJ97TUovZEbQV1sEsaX9/C9g8Swf2ACgiSHz 3mblTd0OoQS1Mocutf2D+XU= =GWiL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] yast++ name
by Thomas Goettlicher 13 Sep '11

13 Sep '11

I wonder if 'yast++' or 'yast--' are names that might cause trouble sometime in the future because of the '+' or '-' in it. I wasn't very happy with the version number as part of the package name in yast2. Using '++' or '--' might be even worse, e.g. rpm uses '-' as delimiter. There are more examples where it might cause conflicts, I guess. What's your opinion? Thanks. Thomas -- Thomas Goettlicher 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 For additional commands, e-mail: yast-devel+help(a)opensuse.org

6 8

[yast-devel] Re: [yast-commit] r65678 - /branches/SuSE-Code-11-SP2-Branch/fcoe-client/src/FcoeClient.ycp
by Lukas Ocilka 13 Sep '11

13 Sep '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 13.9.2011 10:55, gs(a)svn2.opensuse.org napsal(a): > Author: gs > Date: Tue Sep 13 10:55:06 2011 > New Revision: 65678 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=65678&view=rev > Log: > call fipvlan only for configured interfaces > > Modified: > branches/SuSE-Code-11-SP2-Branch/fcoe-client/src/FcoeClient.ycp > > Modified: branches/SuSE-Code-11-SP2-Branch/fcoe-client/src/FcoeClient.ycp > URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/fcoe-… > ============================================================================== > --- branches/SuSE-Code-11-SP2-Branch/fcoe-client/src/FcoeClient.ycp (original) > +++ branches/SuSE-Code-11-SP2-Branch/fcoe-client/src/FcoeClient.ycp Tue Sep 13 10:55:06 2011 > ... > foreach ( map card, netcards, { > + // get first (at the moment only) state map from link list in resource map > + map state_map = card["resource", "link", 0 ]:$[]; > + > + if ( state_map["state"]:false == false ) > + { > + // call 'ifconfig <interface> up' here because it's not yet > + // clear who configures the interfaces (fipvlan command itself?) > + // -> see bnc #705171 (this applies also to installed system) > + > + string cmd_ifup = sformat( "ifconfig %1 up", card["dev_name"]:"" ); > + y2milestone( "Executing command: %1", cmd_ifup ); > + SCR::Execute( .target.bash_output, cmd_ifup ); > + > + // ifconfig up always returns 0 -> no error message can be made > + } > + } ); > + // call .probe.netcard again > + netcards = (list<map>)SCR::Read(.probe.netcard); > + > + foreach ( map card, netcards, { > + map state_map = card["resource", "link", 0]:$[]; > map info_map = $[]; > map <string, string> status_map = $[]; Maybe I'm wrong but this looks quite low-level to me and it might rather belong to Network module (yast2.rpm/library/network) instead of adding such functionality to FCoE. Bye Lukas - -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFObxxjVSqMdRCqTiwRAv9fAJ4zu6nw5MO5nYtXQgMmMkcpjJCXWACfVIS5 23a7EawE74/Vjo+fy0kdrm4= =N8E6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] Webyast contributors in github
by Josef Reidinger 13 Sep '11

13 Sep '11

Hi, I see that there is a new user in owner team that I don't know. I also think we need to split owners and contributors so I create new team and move there some people from owners team. And still I think that we should reduce push permission to force pull requests and contribution reviews to prevent any malicious or bad-style code. Josef -- Josef Reidinger Appliance Toolkit team maintaining parts of webyast and SLMS author of rubygems - studio_api and net_observer (coauthor) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 1

[yast-devel] YaST Dialog Button Order in KDE
by Lukas Ocilka 09 Sep '11

09 Sep '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've got a very nice bug - actually a never-ending story - about button order in YaST dialogs. This one is not about using ButtonBox widget (at least not from the developer's point of view) because the inconsistency is in our design of the whole Wizard dialog. See https://bugzilla.novell.com/show_bug.cgi?id=571939 Especially https://bugzillafiles.novell.org/attachment.cgi?id=339226 [Cancel] [OK] button order The root of the issue is, from my POV, the way how we define the Wizard behavior and how we later work with it, e.g., by calling SetNextButton(any id, string label). We often use this approach for configuration wizards: [/Back/][Next] [Back] [Next] [Back] [Finish] According to Keith Briscoe, who's already reported several button-order-related bugs, this is in fact a bug considering our wiki page http://old-en.opensuse.org/YaST/Development/Misc/Button_Order and also considering the KDE style that tries to follow a human-speech order. [OK] / [Apply] / [Continue] / [Finish] / [Yes] / ... always presented before [Cancel] / [No] / ... So, in Wizard, we still use the GNOME button order although YaST runs in KDE. I think that we could try to change the order in Wizard.ycp (or, in fact, in its Qt implementation) but it would be quite a big change and it needs to be discussed first. And that I wrote this e-mail :) Thanks in advance for your ideas and opinions Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk5d8kIACgkQVSqMdRCqTix2agCfel5xmACjnrjWIxtimo0B5qPN 4VkAnRHOQN3kyK7+JHYU35Cjku0voTyY =n+Ry -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 11

[yast-devel] [PATCH] enhance the network YaPI
by Justus Winter 09 Sep '11

09 Sep '11

Hey hey, attached is a series of patches that enhance the network YaPI in various ways. The patches are quite small and accompanied by tests if they add functionality. Cheers, Justus -- Justus Winter winter(a)pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH USt-IdNr.: DE263765024 Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges Jürgen Sander Axel Theilmann

4 4