YaST Development February 2009

yast-devel@lists.opensuse.org

18 participants
14 discussions

[yast-devel] Install packages by supplements from YCP?
by Arvin Schnell 26 Feb '09

26 Feb '09

Hi, is it possible to install packages from YCP by using the supplements information? E.g. xfsprogs.spec contains "Supplements: filesystem(xfs)". I want to do something like this: Package::InstallAll(["filesystem(xfs)"]); Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 7

[yast-devel] Nürnberg YaST team meeting minutes 2009-02-24
by Arvin Schnell 24 Feb '09

24 Feb '09

Nürnberg YaST team meeting minutes 2009-02-24 Present: aschnell, gs, jdsn, ma, mantel, schubi, snwint, tgoettlicher Absent: aorlovskyy, dmacvicar Minutes: aschnell aschnell: - Bug fixing - Code cleanup esp. modifications that affects other modules e.g. AutoYaST. gs: - Bug fixing jdsn: - Bug fixing - Wants to update YaST server to 11.1 ma: - Bug fixing - Explained problem that repositories on CD/DVD cannot be refreshed properly since there exists no connection between repositories and medium (only URL). So during refresh the medium present at that time is simply used even though the repository expects another medium. mantel: - Bug fixing - Working on RPM for puppet. Analysing modifications required for puppet to work on openSUSE. schubi: - Web-client code and API cleanup - Looking at translations for web-client. snwint: - Bug fixing. Some last minutes requests for SLES. - ITO: Improve X86 emulator used during monitor probing. tgoettlicher: - Looking and partly fixing bugs inherited from sh. - Recited question from Prague YaST team whether to create Code11-SP1 branch in svn now. Common opinion: No, too early. Possibly solution: Migrate to git. We all wish Duncan a quick recovery. Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- 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] Prague YaST team meeting 2009-02-19
by Jiri Srain 24 Feb '09

24 Feb '09

Czech YaST2 team (Prague) meeting 2009-02-19 ============================================ Present: jkupec, jreidinger, jsrain, jsuchome, juhliarik, kmachalkova, locilka, mvidner, mzugec Absent: lslezak Minutes: jsrain Next Minutes: jsrain (cookies forgotten) bootloader (juhliarik, jreidinger) - fixing some bugs for 11.2 - preparation on the UI refactoring user-readable YaST logs (jsuchome) - information sent out to yast-devel, please, read and comment libzypp + zypper (jkupec) - 11.2 zypper improvements, installation summary WIP - given a presentation at FOSDEM, report from event sent separately helping bugzilla screening - the team helped bugzilla screening the queue went down by 40% brainstorming site announced - see Stano's blog web service (mvidner) - helping to hunt bugs in communication with YaST sysconfig in packager (kmachalkova) - sysconfig options now read/write in ncurses packager misc - mzugec blogged about YaST UI with object oriented concepts (written in Python): http://mzugec.blogspot.com/2009/02/object-oriented-ui-for-yast.html - S/390 bugs - ping-pong with IBM (mzugec) - fixing several issues about add-on products (locilka) - 127.0.0.2 strikes back with SAP (kmachalkova) - fixes in autoinstallation for SLE11 (jsuchome) - ImageCreator bugs (jsuchome) -- 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] Re: [devel] Heavy changes due to upcoming PDB migration
by Arvin Schnell 19 Feb '09

19 Feb '09

On Thu, Feb 19, 2009 at 02:18:59PM +0100, Adrian Schröter wrote: > We have described the current use cases of the PDB, which we plan to continue > to support in future on this wiki page: > > https://wiki.innerweb.novell.com/index.php/Build_Service/PDB_Migration#Use_… "Authors handling We had a mechanism to add Authors in a standarized formated way in the descriptions. Since these data is mostly out of data in PDB, we decided to drop this feature. We recommend to maintain the upstream project URL better in future to replace this." For YaST packages we don't have project URLs. AFAIS we will lose the authors data. Any ideas? ciao Arvin -- 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] Prague YaST team meeting 2009-02-12
by Jan Kupec 19 Feb '09

19 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Minutes from Prague YaST Team Meeting: 2009-02-12 ================================================= http://en.opensuse.org/YaST/Team Present: jkupec, jreidinger, jsrain, jsuchome, juhliarik, kmachalkova, locilka, lslezak, mvidner, mzugec Minutes: jkupec Next Minutes: jsrain bootloader (juhliarik) * fixing slow installaton problems on an HP machine with huge amount of disks (1300+) - the fix will go to openSUSE 11.2 only. partitioner (kmachalkova) * Suitable default sysconfig setting of hidden fields can reduce the amount of presented (advanced) information and help to simplify partitioner UI for home users. The option to change partitioner settings to display more details will be still available for power users. package manager, ncruses (kmachalkova) * menu for setting the type of action to be done at the end of installation added (read-only until some C/C++/command-line sysconfig writer will be available - maybe augeas?) YaST d-bus service (lslezak) * Still WIP. It will provide two interfaces - a simple one using native DBus types (but some YCP types or values cannot be transferred) and an interface using an encoded structure for each value (with full support for all YCP values, but obviously more complicated for use). printer (mzugec) * printer module now supports auto-installation (AutoYaST) misc * mvidner investigated the pros and cons of using *augeas* instead of some YaST agents. http://augeas.net/ * zypper bash completion improved (jreidinger) http://lizards.opensuse.org/2009/02/12/zypper-improved-bash-completion-and-… * jkupec visited FOSDEM, made presentation about zypper * we do not mention licensing in our sources - should we include some in the headers of all source code files? misc bugfixes * SLED installation with autoconfig did not run Online Update (locilka) * some fixes in core documentation (mvidner) * fixes in s390-tools scripts (mzugec) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmdFrwACgkQgEhGpmN+6QHWEgCeNe1L9H3wcg9mWJyCZTtgEY9a utEAnipiuiFliD6bnOIQ9tQi6UacjqLR =zeQ/ -----END PGP SIGNATURE----- -- 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] user readable logging
by Jiří Suchomel 17 Feb '09

17 Feb '09

Hi! We had user requests (fate#100386) to provide the logging that would be readable to users. Such logs should provide the information what certain YaST action is really doing to the system and exclude all the internal debug info our y2logs are full of. Martin and Stano created some concept and added new logging functions y2usernote and y2useritem. These log to the new log file, /var/log/YaST2/y2changes (or $HOME/.y2changes). The question which is still not resolved is how should we use these functions? Which events our modules produce should provide description as "note" and which should provide "items"? What level of complexity should be presented to user? Should we log the real actions, just like commands passed to system agent or rather the explanations of the actions taken? Or both? Let's go to the example. I've added these functions to yast2-users, it's in svn already (update of perl-bindings is needed). At first, I started logging actions done in Write function. I deleted one user and renamed another. See the first y2changes file attached or look here http://pastebin.com/m2c5ec8fe. Now, it is not bad, but the item "File written: '/etc/group'" doesn't give much detailed info about what was done to that file. Stano proposed printing the diffs of the original and modified one: see y2changes-with-diffs file (or look at http://pastebin.com/m3bac2086) Here, the user knows more about the real changes, but the log file is getting a bit less readable again... still I think I'd prefer it. You could see on examples that I don't really use the advantage of having 2 logging functions. AFAIK Martin's original proposal was to use items to tell what actions are we going to perform and notes to log the details of such action. This is hardly achievable in yast2-users module (may be better with others), since at the time of writing we don't know the "user actions" taken, this is the info which is known when user is clicking in the UI (*). So another idea is to log directly when users is using UI and not at the time of write. See the last example, y2changes-UI (or http://pastebin.com/m23a3debb). This is not a full log this time, just part of it. I think the last method is getting more talkative and actually is not more helpful. So - comments? Proposals? Jiri (*) Actually it would need to be cached during the UI-clicking and logged at the time of writing only if user doesn't cancel the actions. -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz

2 1

[yast-devel] System Ugrade 11.0 to 11.1: Previously Used Repositories
by Tamas Sarga 15 Feb '09

15 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, There was a thread named System Ugrade: Previously Used Repositories some weeks ago about a feature request to use previously set repos at upgrade. Then I said, that it works already. But real it just worked. I used it from 10.3 to 11.0 and now I tried it from 11.0 to 11.1. I changed the repos' urls (so they was read correctly) and enabled them. After then there wasn't network check or anything. The upgrade went based on the dvd. It downgraded lot of packages, for example firefox 3.0.6 (from Mozilla repo) to 3.0.4. In addition it removed lot of my packages for example mplayer, vlc and nvidia driver. Fortunately it was just a test system mirrored from my main 11.0, so I'll export the 11.0's packages list and try to import to 11.1 when I'll have time to play with it. One more thing, after I rebooted to my upgraded system the repos weren't there, so my changes weren't saved at all. My first question is, should I open a bug report? The second question is, can it be an incorrect fix of bnc#398315? Cheers, Tamas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmYXTYACgkQsuVyj8v2Zy5nswCfWpWYIUN+FspbxUWdbr4O7/oC vewAoKSRb6GDwhZbed4h4iRFdDXW2p3W =XhBY -----END PGP SIGNATURE----- -- 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] LWN: A look at package repository proxies
by Andreas Jaeger 15 Feb '09

15 Feb '09

FY, the following might be interestingI: http://lwn.net/Articles/318658/ Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj(a)suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 3

[yast-devel] Some thoughts on the SCR D-Bus service
by Klaus Kaempf 13 Feb '09

13 Feb '09

Hi, after having learned about D-Bus in general and the YaST SCR_service in particular, I'd like to share my thoughts on what I saw. 1. service name vs. path name The service name used for SCR_service is "org.opensuse.yast.SCR", offering a single object under the path name "/SCR". This seems to duplicate the namespace (SCR) and would make further extensions (i.e. 'WFM', or 'YCP' to run pure ycp code) look like different services. We might as well use "org.opensuse.YaST" as a generic service name and have the namespace as part of the object path. Note the use of upper case for YaST which matches other service names on the system bus (org.freedesktop.Avahi, org.freedesktop.ConsoleKit, org.freedesktop.Hal) 2. path names Introspecting other D-Bus services shows that all of them repeat the service name as part of the path prefix. I.e. service org.freedesktop.Hal offers /org/freedesktop/Hal/devices/* Combined with 1. above, the YaST service would offer objects like /org/opensuse/YaST/SCR, /org/opensuse/YaST/WFM, /org/opensuse/YaST/YCP. (Alternatively, /org/opensuse/YaST/scr might get better acceptance upstream) 3. path name vs. method arguments Looking at Hal object pathes like /org/freedesktop/Hal/devices/pci_8086_3a02_scsi_host_1_scsi_device_lun0 and the SCR_service interface methods, it occured to me that the API could be simplified. Currently, the first parameter to the SCR functions (Read, Execute, ...) is a YCPPath. This should be merged with the D-Bus object path. So instead of retrieving a single /SCR object and calling res = interface.Read(".probe.cpu") [simplified code, reality looks different !] the object path should be /org/opensuse/YaST/scr/probe/cpu offering a simple 'read' function. Comments welcome ! Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 4

[yast-devel] testsuite in the hudson server
by Duncan Mac-Vicar Prett 13 Feb '09

13 Feb '09

Hi I am trying to get the testsuite to run in the hudson server, I build in a chroot, and I got this error: Running tty... The diff follows... --- tests/tty.err 2009-01-17 19:16:54.000000000 +0000 +++ tmp.err.tty 2009-02-12 13:42:54.000000000 +0000 @@ -0,0 +1,10 @@ +[liby2util] ExternalProgram.cc(start_program) openpty failed +[agent-process] ProcessAgent.cc(Execute) Program NOT started! +[Interpreter] tests/tty.ycp:7 Argument (id) to Read(...) is nil +[Interpreter] tests/tty.ycp:9 Argument (id) to Read(...) is nil +[Interpreter] tests/tty.ycp:11 Argument (out) to regexpmatch(...) is nil +[liby2util] ExternalProgram.cc(start_program) openpty failed +[agent-process] ProcessAgent.cc(Execute) Program NOT started! +[Interpreter] tests/tty.ycp:18 Argument (id) to Read(...) is nil +[Interpreter] tests/tty.ycp:20 Argument (id) to Read(...) is nil +[Interpreter] tests/tty.ycp:22 Argument (out) to regexpmatch(...) is nil FAIL: Wrong stderr for tty See the diff above. So I tried mount -t devpts -o rw,gid=5,mode=620 none /dev/pts Now I get: The diff follows... --- tests/tty.out 2009-01-17 19:16:54.000000000 +0000 +++ tmp.out.tty 2009-02-12 16:00:56.000000000 +0000 @@ -1,5 +1,5 @@ -(true) -(true) +(false) +(false) (false) (false) (false) FAIL: Wrong stdout for tty See the diff above. Any ideas? -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development February 2009