February 2012 - YaST Development - openSUSE Mailing Lists

[yast-devel] yast++ minutes -- 2012-02-13
by Vladimir Moravec 26 Mar '12

26 Mar '12

Hi, below you find minutes of the meeting from this monday. Vlado yast++ ==== https://github.com/yast/yast-- Date: ----- 13-02-2012 Present: ------- Jiri Srain, Lukas Ocilka, Martin Vidner, Josef Reidinger, Jiri Suchomel, Vladimir Moravec Minutes --------- Vladimir Moravec ToC: ======= 1. Packaging 2. File structure 3. Name 4. Portability 5. Play & test out of the Git 6. GSoC 7. Logging 8. What's next 1. Packaging ============ Main idea ---------- + how to distribute the code Proposals ---------- + gem directory structure if gem + check of local system dependencies + native extensions + stay with current rpm building and lets make it available for other distros via buildservice 2. File structure ================= + use of gem directory structure conventions 3. Name of the lib ================== Main idea --------- + to use or not to use 'yast' as a part of the name Pros ---- + established name and community, descendant of Yast + well known and easy to distinguish from others Cons ---- + not suitable if we target multiple distros + hard to find on google + hard to distinguish the name from yast + has association with 'suse only' + possible problem in the mind, with trademarked work 'yast' + makes impression that it is successor of YaST, but it is actually only extraction of part of YaST ( data processing ) Questions --------- + What are the criteria for the name? Suggestions for the name ------------------------ + ylib + anything with 'y' letter + liby + libyast Results ------- + use yast++ name as before in the meantime + change is however expected in the course of further development 4. Portability ============== Main idea --------- + make the lib available & popular for non-suse developers What are the means to achieve this ---------------------------------- + distro specific config / package script calls + other distros to be considered: Fedora, Debian, Ubuntu Random ideas ------------ + what changes are needed to include other distros as target systems + focus on other distros not from the beginning, only later after some point in development has been reached + focus from the early stage on development; past experience shows this as reasonable + talk/blog about the lib development in the public to make it aware of the project existence + show simple examples for using on other distros + currently no check for running distro + autodetection as the best way + use of plugins would be fine + distro autodetection, e.g. `cat /proc/version` Discussion -------- + too wide scope for beginning of such project (too many specifications, different needs for various distros) + too much work for small team -> rather focus on making happy well known users (studio,webyast), then use resources for others + imaginary users of debian/fedora as a too blury concept for the expected change + we need a proof of concept that it might run on different distros anyway Questions --------- + should the portability the a feature of the lib? + is the multi-distro focus meaningful? + would it be possible running it on Fedora at all? + What is needed to make the development focused on more distros? + where to implement the distro-specific configuration + how to avoid forking the lib from others and keep devs in one place => avoid splitting the community Suggestions ----------- + ylib as ideal level for customizing configuration of the lib for this 5. Play & test out of Github ============================ Main idea ---------- + make the lib developer friendly from the first touch How to achieve this -------------------- + directory with example files + using chroot for not breaking the running system (root needed) + scripts for chrooting available + alternatives for chroot: + good tutorial for developers + make appliances available Random ideas ------------ + devel-pattern for rpm packaging + appliances of other distros to play with the code + `git clone` into the pre-build VM + project on OBS / install from here + ensure modifying the local system (remounting) + using testing data (from testsuite) for development Questions --------- + how skilled is the developer who is going to use the lib? + how make the repo available for playing for other distros' developers Proposals --------- + look on other projects how they solve the system configuration change 6. GSoC ======= Main ideas --------- + portability feature + C binding for Python + support of Openstack => not needed currently + get in touch with Michal Hrusecky (GSoC/openSUSE wiki) 7. Logging ========== Main ideas ---------- + full logging in/out + filter passwords => results in slower performance + dry run - diffs in chroot - scripts + conventions for parameters + use of the test-suite to avoid wrong using of scripts + create/support official API + undef methods to block improper use of the lib 8. What's next? =============== + finish one or several modules and show the use case: + port it to to other distros + use it in the webyast Vladimir Moravec Appliances Department SUSE LINUX s.r.o., Praha

8 12

[yast-devel] YaST++ Sprint Review 2012-02-21
by Lukas Ocilka 13 Mar '12

13 Mar '12

Generic Reminders ----------------- * Keep it simple * Some parts might be projects for Google Summer of Code ACLs ---- * Bind to path * Roles defined as in WebYast * Check how the others solve this (e.g., KDE) * AI: jsuchome & jreidinger New Project Name ---------------- * Ask community * Code name (maybe something known, easy to remember) * Package name (might differ to code name, but needn’t) * AI: everyone DBUS Optional ------------- * Depends on ACLs - how we define them * Anyway, root is always without DBUS already * Modular - created as plug-in * To lower the complexity * AI: jreidinger YaST-Related Data ----------------- * Stored in /usr/share/YaST2/data/ * Separate data to a different package? YaST++ must not depend on Classical YaST * Discussion WIP -- Lukas Ocilka, Appliances 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

4 4

[yast-devel] problem installing onto LVM striped disks
by Mike Coleman 28 Feb '12

28 Feb '12

Hi, I'm trying to do an autoyast install onto LVM striped volumes. I couldn't find an example, but it seems like something similar to the following should work (it works in the unstriped variation). Specifically, in the partition planning step, I'm getting an error dialog that says "A logical volume with the requested size could not be created. Try reducing the stripe count of the volume." It doesn't seem like it can actually be running out of space, as the disks are a lot larger than the sizes specified. I've included the end of the y2log below. Is there some way to tweak this to make it work? Thanks, Mike <bootloader> <global>  <generic_mbr>true</generic_mbr> <activate>true</activate> <gfxmenu>none</gfxmenu> </global> <loader_type>grub</loader_type> </bootloader> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <use>all</use> <type config:type="symbol">CT_DISK</type> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <mount>/boot</mount> <fstopt>defaults</fstopt> <size>1G</size> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext4</filesystem> </partition> <partition> <create config:type="boolean">true</create> <lvm_group>system</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <use>all</use> <type config:type="symbol">CT_DISK</type> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <mount>/boot-sdb</mount> <fstopt>defaults</fstopt> <size>1G</size> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext4</filesystem> </partition> <partition> <create config:type="boolean">true</create> <lvm_group>system</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> </drive> <drive> <device>/dev/system</device> <initialize config:type="boolean">true</initialize> <use>all</use> <type config:type="symbol">CT_LVM</type> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <lv_name>swap_lv</lv_name> <mount>swap</mount>  <size>6G</size> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <stripes config:type="integer">2</stripes> <stripesize config:type="integer">128</stripesize> </partition> <partition> <create config:type="boolean">true</create> <lv_name>root_lv</lv_name> <mount>/</mount> <fstopt>defaults</fstopt> <size>max</size> <format config:type="boolean">true</format> <filesystem config:type="symbol">xfs</filesystem> <stripes config:type="integer">2</stripes> <stripesize config:type="integer">128</stripesize> </partition> </partitions> </drive> </partitioning> Final 30 lines of y2log: 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] LvmVg.cc(getInfo):1643 device: 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] LvmVg.cc(getInfo):1645 devices_add:/dev/sda5 /dev/sdb5 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:1601 ls=[] 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:1800 getContainerInfo container $["create":true, "cyl_count":118694, "cyl_size":4194304, "device":"/dev/system", "devices":[], "devices_add":["/dev/sda5", "/dev/sdb5"], "lvm2":true, "name":"system", "partitions":[$["create":true, "detected_fs":`none, "device":"/dev/system/swap_lv", "format":true, "fstype":"LV", "inactive":true, "mount":"swap", "mountby":`device, "name":"swap_lv", "size_k":6291456, "stripes":2, "stripesize":128, "type":`lvm, "used_fs":`swap]], "pe_free":117158, "pesize":4194304, "size_k":486170624, "type":`CT_LVM] 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] AutoinstLVM.ycp:358 calling addLogicalVolume with lv = $["create":true, "device":"/dev/system/swap_lv", "filesystem":`swap, "format":true, "lv_name":"swap_lv", "mount":"swap", "name":"swap_lv", "size":"6442450944", "size_k":6291456, "stripes":2, "stripesize":128, "type":`lvm, "used_fs":`swap] and current_vg = system 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] AutoinstLVM.ycp:360 Storage::GetTargetMap returns $["/dev/sda":$["bios_id":"0x80", "bus":"IDE", "cyl_count":30394, "cyl_size":8225280, "device":"/dev/sda", "driver":"ata_piix", "driver_module":"ata_piix", "label":"msdos", "max_logical":255, "max_primary":4, "model":"ST3250318AS", "name":"sda", "partitions":[$["create":true, "detected_fs":`unknown, "device":"/dev/sda1", "format":true, "fsid":131, "fstopt":"defaults", "fstype":"Linux native", "inactive":true, "mount":"/boot", "mountby":`id, "name":"sda1", "nr":1, "region":[0, 131], "size_k":1052257, "type":`primary, "udev_id":["ata-ST3250318AS_9VY594ER-part1", "scsi-SATA_ST3250318AS_9VY594ER-part1", "wwn-0x5000c5001fa8c8f9-part1"], "udev_path":"pci-0000:00:1f.2-scsi-0:0:0:0-part1", "used_fs":`ext4], $["create":true, "detected_fs":`unknown, "device":"/dev/sda2", "fsid":15, "fstype":"Extended", "name":"sda2", "nr":2, "region":[131, 30263], "size_k":243087547, "type":`extended, "udev_id":["ata-ST3250318AS_9VY594ER-part2", "scsi-SATA_ST3250318AS_9VY594ER-part2", "wwn-0x5000c5001fa8c8f9-part2"], "udev_path":"pci-0000:00:1f.2-scsi-0:0:0:0-part2"], $["create":true, "detected_fs":`unknown, "device":"/dev/sda5", "fsid":142, "fstype":"Linux LVM", "name":"sda5", "nr":5, "region":[131, 30263], "size_k":243087547, "type":`logical, "udev_id":["ata-ST3250318AS_9VY594ER-part5", "scsi-SATA_ST3250318AS_9VY594ER-part5", "wwn-0x5000c5001fa8c8f9-part5"], "udev_path":"pci-0000:00:1f.2-scsi-0:0:0:0-part5", "used_by":[$["device":"/dev/system", "type":`UB_LVM]], "used_by_device":"/dev/system", "used_by_type":`UB_LVM]], "proposal_name":"1. IDE Disk, 232.83 GB, /dev/sda, ST3250318AS", "sector_size":512, "size_k":244140625, "transport":`ata, "type":`CT_DISK, "udev_id":["ata-ST3250318AS_9VY594ER", "scsi-SATA_ST3250318AS_9VY594ER", "wwn-0x5000c5001fa8c8f9"], "udev_path":"pci-0000:00:1f.2-scsi-0:0:0:0", "unique":"3OOL.16E5Tj41dwA"], "/dev/sdb":$["bios_id":"0x81", "bus":"IDE", "cyl_count":30394, "cyl_size":8225280, "device":"/dev/sdb", "driver":"ata_piix", "driver_module":"ata_piix", "label":"msdos", "max_logical":255, "max_primary":4, "model":"ST3250318AS", "name":"sdb", "partitions":[$["create":true, "detected_fs":`unknown, "device":"/dev/sdb1", "format":true, "fsid":131, "fstopt":"defaults", "fstype":"Linux native", "inactive":true, "mount":"/boot-sdb", "mountby":`id, "name":"sdb1", "nr":1, "region":[0, 131], "size_k":1052257, "type":`primary, "udev_id":["ata-ST3250318AS_9VY57LLH-part1", "scsi-SATA_ST3250318AS_9VY57LLH-part1", "wwn-0x5000c5001fa5b144-part1"], "udev_path":"pci-0000:00:1f.2-scsi-1:0:0:0-part1", "used_fs":`ext4], $["create":true, "detected_fs":`unknown, "device":"/dev/sdb2", "fsid":15, "fstype":"Extended", "name":"sdb2", "nr":2, "region":[131, 30263], "size_k":243087547, "type":`extended, "udev_id":["ata-ST3250318AS_9VY57LLH-part2", "scsi-SATA_ST3250318AS_9VY57LLH-part2", "wwn-0x5000c5001fa5b144-part2"], "udev_path":"pci-0000:00:1f.2-scsi-1:0:0:0-part2"], $["create":true, "detected_fs":`unknown, "device":"/dev/sdb5", "fsid":142, "fstype":"Linux LVM", "name":"sdb5", "nr":5, "region":[131, 30263], "size_k":243087547, "type":`logical, "udev_id":["ata-ST3250318AS_9VY57LLH-part5", "scsi-SATA_ST3250318AS_9VY57LLH-part5", "wwn-0x5000c5001fa5b144-part5"], "udev_path":"pci-0000:00:1f.2-scsi-1:0:0:0-part5", "used_by":[$["device":"/dev/system", "type":`UB_LVM]], "used_by_device":"/dev/system", "used_by_type":`UB_LVM]], "proposal_name":"2. IDE Disk, 232.83 GB, /dev/sdb, ST3250318AS", "sector_size":512, "size_k":244140625, "transport":`ata, "type":`CT_DISK, "udev_id":["ata-ST3250318AS_9VY57LLH", "scsi-SATA_ST3250318AS_9VY57LLH", "wwn-0x5000c5001fa5b144"], "udev_path":"pci-0000:00:1f.2-scsi-1:0:0:0", "unique":"WZeP.SJGacGDJ4vD"], "/dev/system":$["create":true, "cyl_count":118694, "cyl_size":4194304, "device":"/dev/system", "devices":[], "devices_add":["/dev/sda5", "/dev/sdb5"], "lvm2":true, "name":"system", "partitions":[$["create":true, "detected_fs":`none, "device":"/dev/system/swap_lv", "format":true, "fstype":"LV", "inactive":true, "mount":"swap", "mountby":`device, "name":"swap_lv", "size_k":6291456, "stripes":2, "stripesize":128, "type":`lvm, "used_fs":`swap]], "pe_free":117158, "pesize":4194304, "size_k":486170624, "type":`CT_LVM]] 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] AutoinstLVM.ycp:308 max-config for striped LV found. Setting size to 486175094K 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] AutoinstLVM.ycp:314 size_k before rounding 486175094 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] AutoinstLVM.ycp:316 size_k after rounding 486174720 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:2827 CreateLvmLv vg:system name:root_lv sizeK:486174720 stripes:2 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] Storage.cc(createLvmLv):3318 vg:system name:root_lv sizeK:486174720 stripes:2 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] LvmVg.cc(createLv):316 name:root_lv sizeK:486174720 stripe:2 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] PeContainer.cc(findPe):519 dev:/dev/sda5 ret:false 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] PeContainer.cc(findPe):519 dev:/dev/sda5 ret:true 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] PeContainer.cc(findPe):519 dev:/dev/sdb5 ret:false 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] PeContainer.cc(findPe):519 dev:/dev/sdb5 ret:true 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] LvmVg.cc(createLv):356 ret:-4007 device: 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] Storage.cc(createLvmLv):3338 ret:-4007 device: 2012-02-27 13:45:58 <3> 192.168.252.64(3565) [YCP] Storage.ycp:2834 CreateLvmLv sint ret:-4007 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:1960 UpdateTargetMapDisk 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] Storage.cc(getContainers):5060 co:CType:DISK Name:sda Device:/dev/sda SizeK:244140625 Node:<8:0> alt_names:</dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 /dev/disk/by-id/ata-ST3250318AS_9VY594ER /dev/disk/by-id/scsi-SATA_ST3250318AS_9VY594ER /dev/disk/by-id/wwn-0x5000c5001fa8c8f9> 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] Storage.cc(getContainers):5060 co:CType:DISK Name:sdb Device:/dev/sdb SizeK:244140625 Node:<8:16> alt_names:</dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0 /dev/disk/by-id/ata-ST3250318AS_9VY57LLH /dev/disk/by-id/scsi-SATA_ST3250318AS_9VY57LLH /dev/disk/by-id/wwn-0x5000c5001fa5b144> 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] Storage.cc(getContainers):5060 co:CType:LVM Name:system Device:/dev/system SizeK:486170624 created 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:1853 getContainers ret:[$["device":"/dev/sda", "name":"sda", "type":`CT_DISK, "udev_id":["ata-ST3250318AS_9VY594ER", "scsi-SATA_ST3250318AS_9VY594ER", "wwn-0x5000c5001fa8c8f9"], "udev_path":"pci-0000:00:1f.2-scsi-0:0:0:0"], $["device":"/dev/sdb", "name":"sdb", "type":`CT_DISK, "udev_id":["ata-ST3250318AS_9VY57LLH", "scsi-SATA_ST3250318AS_9VY57LLH", "wwn-0x5000c5001fa5b144"], "udev_path":"pci-0000:00:1f.2-scsi-1:0:0:0"], $["device":"/dev/system", "name":"system", "type":`CT_LVM]] 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:1451 getContainerInfo $["device":"/dev/system", "name":"system", "type":`CT_LVM] 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] LvmVg.cc(getInfo):1643 device: 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [libstorage] LvmVg.cc(getInfo):1645 devices_add:/dev/sda5 /dev/sdb5 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:1601 ls=[] 2012-02-27 13:45:58 <1> 192.168.252.64(3565) [YCP] Storage.ycp:1800 getContainerInfo container $["create":true, "cyl_count":118694, "cyl_size":4194304, "device":"/dev/system", "devices":[], "devices_add":["/dev/sda5", "/dev/sdb5"], "lvm2":true, "name":"system", "partitions":[$["create":true, "detected_fs":`none, "device":"/dev/system/swap_lv", "format":true, "fstype":"LV", "inactive":true, "mount":"swap", "mountby":`device, "name":"swap_lv", "size_k":6291456, "stripes":2, "stripesize":128, "type":`lvm, "used_fs":`swap]], "pe_free":117158, "pesize":4194304, "size_k":486170624, "type":`CT_LVM] 2012-02-27 12:45:58 <1> 192.168.252.64(3565) [ui] YPushButton.cc(setFunctionKey):204 Guessing button role YOKButton for YPushButton "OK" at 0x7f6c082229e8 from function key F10 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

[yast-devel] Migrate YaST svn to git
by J. Daniel Schmidt 28 Feb '12

28 Feb '12

Dear YaST-Hackers, As we heared from various sides about a switch of the YaST source code from SVN to git - here is all information about it. History -------- Last year we (Klaus Kämpf, Lukas Ocilka, Martin Vidner and me) started to look into a migration of the YaST svn repo to git. We did not succeed back then, as our usage of svn is not that simple as in other repos. I already migrated smaller projects with git-svn within a few minutes - but this approach did not work for YaST. The topic popped up again recently and Bernhard Wiedemann and me looked into it again last week and found a new solution. Within 1.5 days we created a tool around svndumpfilter3 [1] that looks very promising. Our Goals ---------- In long discussions in 2011 the initiators agreed on these set of goals that we should meet: * have one git repo per YaST module * have all history in the repos including all branches and tags * have a kind of yast-meta repo containing scripts that are able to checkout single or all yast repos in the same style like the current svn checkout or to search within the other repos Thomas Göttlicher <tgoettlicher(a)suse.de> is collecting your usecases (like 'find latest version tag of package X in distribution Y', ...) * cleanup and unify the branch and tag names Find all details about it at: http://en.opensuse.org/YaST_SVN_to_GIT * automatically move all repos to github.com/yast/* Current Status --------------- We have some of the modules converted and published for you as a PREview. http://www3.zq1.de/bernhard/linux/yast/ Please have a look at your module and report issues to this list or directly to Bernhard and me (bwiedemann(a)suse.de , jdsn(a)suse.de) Please do NOT push these repos to github or use them for development now. These are only published for you to get a first impression and to find errors. Once everything works, we will create repos on and push the final repos to github, all automatically. Thus don't even create a repo there yet. Due to proirities Bernhard and me work on this task in our free time. But we already got so far that we think that we are able to finish the conversion within a few days (see plan below). Anyhow we do not have a fixed date yet. We have to solve a hand full of issues to make the conversion complete. Final Migration ----------------- This is our plan for the final migration once our tests succeed we will 1. announce the final switch at least two days beforehand 2. switch the svn repo to read-only on 'a' Friday afternoon 3. create a final svn dump 4. run the conversion tool (this is the most time consuming job) 5. automatically create repos on github/yast/* 6. upload the final git repos If all works well, you can find an announcement of the conversion in your inbox on Monday morning. We do not have a date yet for the conversion. So there will be another announcement. If there are any blockers or issues on your side please speak up or contact Bernhard and me (see above). Any other kind of feedback is welcome as well. [1] http://furius.ca/pubcode/pub/conf/bin/svndumpfilter3.html Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE LINUX Products GmbH Research & Development Maxfeldstr. 5 HRB 16746 (AG Nürnberg) D-90409 Nürnberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 11

[yast-devel] opensuse 12.1 DVD install showstopper: "An error occurred during initrd creation"
by Mike Coleman 27 Feb '12

27 Feb '12

Hi, When I install the final 12.1 from the DVD, it fails during the "Saving bootloader configuration..." / "Install boot manager" phase with a dialog titled "An error occurred during initrd creation." (which has no other text). I am unable to complete the install after this point. This is probably the same bug as "Bug 713316 - mkinitrd: fails to run and/or shows no text during install" (https://bugzilla.novell.com/show_bug.cgi?id=3D713316) I've tried installing on three different platforms, and I get the same bug. If I install using the Live GNOME CD on these platforms, the install completes without difficulty. Has anyone succeeded in installing on any hardware using the 12.1 DVD? Thanks, Mike

2 4

[yast-devel] Patch for perl-bindings - fix for bnc#535200
by Josef Reidinger 23 Feb '12

23 Feb '12

Hi, I found this old bug[0] when I search in bugzilla for something else and it will be enough interesting for me, that I investigate how perl and its bindings works and how it works for submodules. In the end I came with fix, that I test myself. Problem was that perl pass variable as string type and not as reference to string. So I addapt bindings to handle both situation. Martin - please review my patch. Thanks Josef [0] https://bugzilla.novell.com/show_bug.cgi?id=535200 -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger(a)suse.com SUSE

1 0

[yast-devel] Idea how to improve autoyast related code in modules
by Josef Reidinger 23 Feb '12

23 Feb '12

Hi YaST hackers, from my experience with yast modules, there is quite strange part which contain various backward compatible stuff for old autoyast profiles. It makes perfect sense to have backward compatibility in this area and I am sure that customer likes it. What can be improved is way how we do it. Now it is mixed into every module and it is not much tested, so sometime we get strange bug report, that something stop working. I see quite nice way how to solve it in kiwi, so maybe we can inspire: 1) code always support only the latest schema, no backward compatibility 2) old xml files is before usage transformed via XSLT, so backward compatibility is preserved and separated This way we have separate layer for backward compatibility. We can also provide easy tool for customers how to update to the latest schema. We can also more easily test it. It is located in one place. What do you think about such solution? Josef -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger(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

2 1

[yast-devel] New feature of infrastucture of yast++
by Josef Reidinger 22 Feb '12

22 Feb '12

Hi, I would like to inform, that infrastrucure for config agents have new feature. Agent frontend can ask what polkit permission it requires. So e.g. so can check it before it is needed or you can report which one is missing ( preparation for tool that can run YLib and only return needed permission to given task ). So how to use it? quite simple: require "config_agent/mkinitrd" ConfigAgent::Mkinitrd.polkit_permissions => {:execute => "org.opensuse.config_agent.script.mkinitrd.execute"} BTW what should be proper place to document such feature? Code is already documented via yard [0][1]? Josef [0] http://rubydoc.info/github/yast/yast--/DbusClients/FileClient#polkit_permis… [1] http://rubydoc.info/github/yast/yast--/DbusClients/ScriptClient#polkit_perm… -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger(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

2 3

[yast-devel] Re: [yast-commit] r67469 - in /trunk/nfs-client: VERSION package/yast2-nfs-client.changes src/routines.ycp testsuite/tests/r-check.out testsuite/tests/r-check.ycp testsuite/tests/r-spec.out testsuite/tests/r-spec.ycp
by Lukas Ocilka 22 Feb '12

22 Feb '12

On 02/17/2012 02:18 PM, mfilka(a)svn2.opensuse.org wrote: > - name == filterchars(name, > - "-_.0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz")) { > + name == filterchars(name, "-_.:" + String::CAlnum() )) { Good catch. Don't be afraid to use a public constant/function defined in NfsServer.ycp module or even deeper, e.g., in String.ycp (different RPM). Bye Lukas -- Lukas Ocilka, Appliances 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

2 1

[yast-devel] Google Summer Of Code
by Manu Gupta 21 Feb '12

21 Feb '12

Hi YaSTies Google Summer of Code has been announced and we want to take part in it again and so this is a call for adding your ideas and becopming mentors again like the last year. The idea list is here http://en.opensuse.org/openSUSE:GSOC_2012_Ideas#GSOC_2012_Idea_list Please add your ideas here and I can answer any questions you had like me to answer -- Regards Manu Gupta -- 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] YaST2 LDAP and scripts
by Günther J. Niederwimmer 21 Feb '12

21 Feb '12

Hello, Is it possible to find a DOC or a LINK, to find out which Schema and Index the YaST2 Modules and scripts must have? Background: When I like to Install a separate LDAP Server (XEN) and configure other XEN Instances with LDAP support the changes are never written to the LDAP Server. Afterward I found only in the Logs the Error, Index missing or a Error Schema missing usw. When a doc exist it is possible to configure the LDAP server before installing a other XEN Instance? Thanks for the Help, -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 11

[yast-devel] Re: [yast-commit] r67465 - in /trunk/nfs-client: package/yast2-nfs-client.changes src/Nfs.ycp src/ui.ycp
by Josef Reidinger 20 Feb '12

20 Feb '12

On Thu, 16 Feb 2012 13:22:20 -0000 mfilka(a)svn2.opensuse.org wrote: > Author: mfilka > Date: Thu Feb 16 14:22:19 2012 > New Revision: 67465 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=67465&view=rev > Log: > > removed some dead code, whitespaces Great, don't hesitate to move out all garbage you found ;) Just I recommend to separate removing dead code and whispaces changes to different commit, so it will be easier to detect. For whitespace correction I recommend indent tool, which can take it in one round. Josef P.S. If you find indentation rules strange, then you are not alone. -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger(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

4 6

[yast-devel] It's time to switch to GitHub
by Lukas Ocilka 17 Feb '12

17 Feb '12

Hi, As SP2 is not blocking us anymore, it's now time to switch from SVN to GitHub as we've decided earlier in 2011. I know there were some issues with importing all the history but I don't have enough details on which pieces were missing. Maybe not everything is actually needed. Let's focus on finishing the transition now, please. Thanks && Bye Lukas -- Lukas Ocilka, Appliances 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

3 2

[yast-devel] y2dir ?
by Per Jessen 16 Feb '12

16 Feb '12

I'm trying to use Y2DIR to temporarily fix an iscsi issue during installation, but I simply cannot get it to work. As far as I can tell from /var/log/yast2/y2log, my Y2DIR setting is being ignored. I've tried starting yast: a) Y2DIR=/my2 yast b) export Y2DIR=/my2 yast In /my2 I have the following: # ls -l /my2 total 120 -rw-r--r-- 1 root root 87067 Feb 15 06:49 IscsiClientLib.ybc -rw-r--r-- 1 root root 28721 Feb 15 06:49 IscsiClientLib.ycp I _know_ I had this working last year before Christmas, so it has to be something stupid, but I just cannot see it. /Per Jessen, Zürich -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

[yast-devel] Ruby-bindings and exception
by Josef Reidinger 15 Feb '12

15 Feb '12

Hi YaST hackers, there is problem with exceptions from ruby modules. Now if risen, yast crash. I found this behavior quite annoying and it should be improved. I can do it, question is what is correct behavior. Does anyone have suggestion? In yast++ we have now error variable and catch exceptions. So I can in ruby bindings ( and only in bindings so ruby code is not affected ) extend class by method that return message of last exception. So you can run code as if (Module::run == nil) y2error ("Problem with run %1",Module.yast_error); I welcome any other suggestions or comments. Also it would be nice to have uniform way....how python bindings solve such problem? And how connection to C++ code behave? Thanks for attention Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 12

[yast-devel] YaST++ isn't YaST but ...
by Lukas Ocilka 13 Feb '12

13 Feb '12

Hi, Today we had a talk about the future of YaST++ #1 project and we've found out that maybe "YaST++" isn't actually the best name. Why? Because the project should NOT replace the whole YaST. It's just a configuration library written in Ruby that can be used from several other applications (and YaST is only one of them). Additionally, it's a bit uneasy to find YaST++ project as it usually finds YaST instead. RPM/gem names look strange with "++" in it, etc. So, I'd like to ask you for your feedback on the project name. Do you feel it's appropriate? Do you have any better idea for a project code/name? Thanks in advance Lukas #1 https://github.com/yast/yast--/wiki -- Lukas Ocilka, Appliances 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] Re: [yast-commit] r67377 - in /trunk/nfs-client: VERSION package/yast2-nfs-client.changes src/ui.ycp
by Josef Reidinger 08 Feb '12

08 Feb '12

On Wed, 08 Feb 2012 12:03:58 -0000 mfilka(a)svn2.opensuse.org wrote: > Author: mfilka > Date: Wed Feb 8 13:03:57 2012 > New Revision: 67377 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=67377&view=rev > Log: > Base server hostname combobox on existing values - bnc#547983 Hi, congratulate to your first patch. I review your commit and have just small notes: > > snipped > > Modified: trunk/nfs-client/src/ui.ycp > URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-client/src/ui.ycp?rev=67377&… > ============================================================================== > --- trunk/nfs-client/src/ui.ycp (original) > +++ trunk/nfs-client/src/ui.ycp Wed Feb 8 13:03:57 2012 > @@ -58,6 +58,11 @@ > list<string> hosts = nil; > > /** > + * List of already defined nfs mount points Well, comment is not precise. If you want list of already defined nfs entries, it is exactly Nfs::nfs_entries. This variable store new state of nfs_entries ( so you have old one in Nfs and this variable store modified list by user and when user decide it is stored ). > + */ > + list< map <string,any> > nfs_entries = Nfs::nfs_entries; > + > + /** > * Let the user choose one of a list of items > * @param title selectionbox title > * @param items a list of items > @@ -178,6 +183,7 @@ > `Bottom (button) > ); > } > + > /** > * Ask user for an entry. > * @param fstab_ent $["spec": "file": "mntops":] or nil > @@ -213,6 +219,21 @@ > servers = [ proposed_server ]; > } > > + // append already defined servers - bug #547983 good to have such comment, it really helps when WTF raised :) > + foreach( map nfs_entry, nfs_entries, > + { > + term couple = SpecToServPath( nfs_entry[ "spec"]:""); > + string known_server = ""; > + > + known_server = couple[0]:""; It is confusing to have multiple lines without intention. simple: string known_server couple[0]:""; is enough in this case. Otherwise good commit. Josef > snipped -- 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] Re: YaST-- review
by Jiri Suchomel 07 Feb '12

07 Feb '12

Dne Pá 3. února 2012 18:59:56, Josef Reidinger napsal(a): > On Fri, 03 Feb 2012 17:46:50 +0100 > > "Duncan Mac-Vicar P." <dmacvicar(a)suse.de> wrote: > > Some stuff that caught my attention, not necessarily bad or good: > > From our WebYaST experience, we have to make it attractive to > > > > non-SUSE developers to try and play with our stuff. The ruby > > eco-system is much bigger and can be leveraged to other usages and > > distributions. > > > > However, the source tree still look a bit "SUSEish": > > - Centered around rpm and not around gems (I would generate the spec > > from gemspecs) I'm not sure what would be the gain. As mentioned, dbus and polkit stuff needs to be packaged, but when you run yast++ as root, these are not needed. But there are package requirements for the config agents (the lower layer) as well: the 'script agents' are running scripts that are mostly part of external packages, that need to be installed. Jiri -- 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 -- 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] 11.4 build of Yast2 failures?
by Marc Chamberlin 01 Feb '12

01 Feb '12

Hi, In order for me to try and grok the YaST bootloader setup module, I thought I would try and download the source code for YaST and compile it on my openSuSE11.4 x86_64 system. Then perhaps I can instrument the code in order to understand the model of the bootloader that YaST presents... (and yes, I have asked before for help on understanding the model, and not gotten any useful replies, just sympathy from others who like me do not have a clue what the various settings will do either.. And yes, I understand GRUB, and the GNU documentation, but the openSuSE model and the bootloader GUI remains incomprehensible to me...) I followed the instructions found at http://en.opensuse.org/openSUSE:YaST_development and one of the things these instructions did was to refer me to another tutorial - http://en.opensuse.org/openSUSE:YaST_tutorials_development_in_general which indicated that I needed to be sure to install a number of additional packages. I carefully tried to install the listed packages, but a number (shown below) were missing - gettext-devel gtk-devel there is a gtk2-devel package installed on my system. Equivalent? liby2util-devel openssl-devel there is a libopenssl-devel package installed on my system. Equivalent? pkgconfig there is a pkg-config package installed on my system. Equivalent? I dunno what to do about that, so decided to punt and go on. (Anyone got any ideas on how I should locate these packages?) Anywise, I downloaded the YaST source from the SVN (but not from trunk) using the following command - svn co http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-11_4-Branch/ which I guessed would get me the source code for the version of YaST2 that was installed in my system. The checkout proceed fine, as did the three make commands to build and install YaST2. But when I got to the step - y2tool y2makeall I got a number of errors as shown below (steps not shown appeared to build properly without errors) These may be related to the fact that I was unable to find and install all the required packages, so if that is the case, then I need to understand how to find and install those packages. Thanks in advance for helping me with this... Marc... Errors from the automatic compile of all of YaST...... Building storage make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/storage Building registration make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/registration Building sound make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/sound Building schema make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/schema Building openwsman-yast make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/openwsman-yast Building boot-server make -f Makefile.cvs make /usr/bin/sudo make install ERROR: '/usr/bin/sudo make install' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/boot-server Building cim make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/cim Building heartbeat make -f Makefile.cvs make /usr/bin/sudo make install ERROR: '/usr/bin/sudo make install' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/heartbeat Building qt-graph (cmake based) make -f Makefile.cvs cd qt-graph/build make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/qt-graph Building ruby-bindings (cmake based) make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/ruby-bindings cd ruby-bindings/build Building slide-show make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/slide-show Building you-server make -f Makefile.cvs make /usr/bin/sudo make install ERROR: '/usr/bin/sudo make install' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/you-server y2makeall summary: Success in 103 directories Failure in 12 directories: storage (base package) registration (base package) sound (base package) schema (base package) openwsman-yast boot-server cim heartbeat qt-graph ruby-bindings slide-show you-server -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2