October 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] libstorage-bgl-eval transferred to openSUSE on GitHub
by Arvin Schnell 21 Oct '15

21 Oct '15

Hi, I have just transferred libstorage-bgl-eval on GitHub from aschnell to openSUSE. So the new URL is: https://github.com/openSUSE/libstorage-bgl-eval GitHub is even so cool that it redirects HTTP requests. One note for people trying to compile and check libstorage-bgl-eval: You need a newer version of swig (>= 3.0.3 (with support for C++11 strongly typed enums), released end of 2014) than most SUSE releases provide. AFAIS only Tumblewee/Factory include that version. On Leap swig is utterly outdated (2.0.x). ciao Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 21 Oct '15

21 Oct '15

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-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (4 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (4 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-core: - More diagnostic info when we get a signal (5 days) https://github.com/yast/yast-core/pull/102 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (14 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (183 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (36 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (26 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (113 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (12 days) https://github.com/yast/autoyast-integration-test/pull/30 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 20 Oct '15

20 Oct '15

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-country: - Ensure ntp is installed (when Install Recommended Packages is off) (13 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (182 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (35 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (25 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (112 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (11 days) https://github.com/yast/autoyast-integration-test/pull/30 -- 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] yast2 --qt requires unavailable libyui6
by Felix Miata 19 Oct '15

19 Oct '15

RE: http://lists.opensuse.org/opensuse-factory/2015-10/msg00474.html Is requirement of unavailable libyui6 expected behavior on TW? Shouldn't presence of libyui7 and deps cause removal of libyui6 and deps? Is this a misfortune of following widespread recommendation to use up rather than dup to upgrade TW? # rpmqa yui libyui-ncurses-pkg7-2.48.1-1.1.x86_64 libyui-ncurses6-2.47.2-1.1.x86_64 libyui-ncurses7-2.47.4-1.1.x86_64 libyui-qt-graph6-2.44.3-1.4.x86_64 libyui-qt6-2.46.18-1.3.x86_64 libyui6-3.2.0-1.1.x86_64 libyui7-3.2.3-1.1.x86_64 # yast2 --qt # rpmqa qt | grep y libyui-qt-graph6-2.44.3-1.4.x86_64 libyui-qt6-2.46.18-1.3.x86_64 yast2-control-center-qt-3.1.5-2.3.x86_64 yast2-qt-branding-openSUSE-13.2-11.3.noarch # zypper rm libyui6 Loading repository data... Reading installed packages... Resolving package dependencies... The following 4 packages are going to be REMOVED: libyui-ncurses6 libyui-qt-graph6 libyui-qt6 libyui6 4 packages to remove. After the operation, 3.3 MiB will be freed. Continue? [y/n/? shows all options] (y): y (1/4) Removing libyui-qt-graph6-2.44.3-1.4 ....................................................................................[done] (2/4) Removing libyui-qt6-2.46.18-1.3 .........................................................................................[done] (3/4) Removing libyui-ncurses6-2.47.2-1.1 .....................................................................................[done] (4/4) Removing libyui6-3.2.0-1.1 ..............................................................................................[done] big41:~ # yast2 --qt Qt GUI wanted but not found, falling back to ncurses. # zypper in libyui6 Loading repository data... Reading installed packages... 'libyui6' not found in package names. Trying capabilities. No provider of 'libyui6' found. Resolving package dependencies... Nothing to do. # zypper in libyui-qt7 ... The following NEW package is going to be installed: libyui-qt7 2.46.20-1.1 ... (1/1) Installing: libyui-qt7-2.46.20-1.1 ......................................................................................[done] committingCommitResult (total 1, done 1, error 0, skipped 0, updateMessages 0) # zypper in libyui-qt-pkg7 The following NEW package is going to be installed: libyui-qt-pkg7 2.45.4-1.1 ... (1/1) Installing: libyui-qt-pkg7-2.45.4-1.1 ...................................................................................[done] committingCommitResult (total 1, done 1, error 0, skipped 0, updateMessages 0) # yast2 --qt # -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 5

[yast-devel] attribution setting error in Yast Disk(portioner)
by Zhu Lingshan 19 Oct '15

19 Oct '15

Hi, I just fixed a bug, https://bugzilla.novell.com/show_bug.cgi?id=950685, it is a attribution setting error in fstab. When add a line in fstab to mount a iSCSI device, lines like this would work: /dev/sda1 /mount/test ext4 _netdev 1 2 While lines like this will fail: /dev/sda /ext3 ext3 acl,user_xattr 1 2 The thing is, it should be set as _nektdev, so that the system would mount it after network service run. I found we also have this bug in Yast Disk (portioner), when we try to mount a iSCSI device in yast disk, we will find it not set the device "_netdev", that will cause the system failed to boot. Shall we fix it? If you are busy, I am happy to do that, please let me know. Thanks BR Zhu Lingshan -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 19 Oct '15

19 Oct '15

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-country: - Ensure ntp is installed (when Install Recommended Packages is off) (12 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-network: - Cleanup: Put some defaults into Yaml (6 days) https://github.com/yast/yast-network/pull/346 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (181 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-slide-show: - Update Cloud product to current name (11 days) https://github.com/yast/yast-slide-show/pull/13 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (34 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (24 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (111 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (10 days) https://github.com/yast/autoyast-integration-test/pull/30 -- 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] Some notes about new storage API
by Ancor Gonzalez Sosa 16 Oct '15

16 Oct '15

Once upon a time... =================== As part of the PBI titles "Evaluate design of future-proof storage subsystem", I took a look to the content of https://github.com/aschnell/libstorage-bgl-eval/ This mail can be considered to some extend a follow up of previous evaluations and discussions in this mailing list. Most feedback received from those threads has been already taken into account into the current prototype. Thus, some topics discussed there are outdated but some information is still useful. http://lists.opensuse.org/yast-devel/2014-10/msg00045.html http://lists.opensuse.org/yast-devel/2014-12/msg00016.html First impression ================ First thing I noticed in that repository is the lack of information about building and installing. In every github's README I expect to find: (1) how to build the thing, (2) how to compile the inline docs or a link to an up-to-date compiled version, (3) in (open)SUSE related stuff I also expect instructions to download or build a rpm. That being said, I took a look to the Ruby examples and testsuite and in general I liked what I saw a lot. So first of all, congrats for the great work! Only some (maybe too Ruby-centric) comments follow. Casting and Storage.some_method =============================== Things like this look quite un-ruby: tmp1 = devicegraph.find_device(42) assert(Storage.disk?(tmp1)) assert(Storage.to_disk(tmp1)) assert(!Storage.partition_table?(tmp1)) assert_raises(Storage.DeviceHasWrongType { Storage.to_partition_table(tmp1) } I would have expected things like tmp1.disk? tmp1.to_partition_table In fact, I wouldn't expect to have to perform this kind of casts, at most I would expect to do more rubist things like tmp1.is_a?(Storage::Disk) tmp1.respond_to?(:whatever_method) Query interface =============== The API contains methods like these: device_graph.find_device(numeric_id) Storage::BlkDevice.find(device_graph, "/dev/sda") Storage::Filesystem.find_by_mountpoint(device_graph, "/") Storage::Filesystem.find_by_label(device_graph, "someLabel") Questions that come to my mind. a) Is device_graph always an object representing the whole graph? Can I do things like this to restrict the search to a subtree? disk1 = Storage::Disk.find(device_graph, "/dev/sda") sub_graph = disk1.to_device_graph # or maybe sub_graph = device_graph.sub_graph(disk1.sid) # or any other thing that makes sense Storage::Filesystem.find_by_mountpoint(sub_graph, "/") b) Adding find_by_xx at demand over time doesn't look very future-proof. I would prefer to see something like Rails's #find_by, i.e. Storage::Filesystem.find(device_graph, mountpoint: "/") Storage::Filesystem.find(device_graph, mountpoint: "/", label: "blah") Too ruby-centric and not easy to implement in a cross-language way, I guess. But asking does not hurt. :-) c) Just brainstorming. The approach in (b) could be pushed to the limit to have things like this. But actually I'm not sure if it's a good idea, just braindump. device_graph.find(sid: numeric_id) device_graph.find(type: :filesystem, mountpoint: "/") Lack of inline documentation ============================ Right now, the code is the documentation. I have to say that the code is very nicely structured, so it was really easy to me to browse for the methods I wanted to check (and they were all fairly small and understandable as well). But it's time to start adding documentation to the whole thing. Nitpicking: boolean as parameters ================================= This is something that was already mentioned by Martin in one of the mails referred at the top. Calls like this are not 100% obvious sda.descendants(false) It would be nicer to have something like sda.descendants(:direct) or sda.descendants(direct: true) Nickpicking: 42 =============== I found the usage of 42 and 43 for the sids in examples and tests a little bit confusing. I grepped the source code and found that we simply use autoincremental integer to assign the sids starting with 42. Nothing against it, but please make it more obvious (and robust, in case we decide 42 is not cool anymore) in the testsuites. :-) Epilogue ======== That's all folks! -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 19

[yast-devel] openSUSE Leap 42.1build target has been added to YaST:Head
by Ladislav Slezak 16 Oct '15

16 Oct '15

Hi all, yesterday the openSUSE Leap 42.1 RC1 version has been released, to enjoy also the latest YaST packages in the new system I added the 42.1 build target in the YaST:Head OBS repository. The URL of the repository is: http://download.opensuse.org/repositories/YaST:/Head/openSUSE_42.1/ All packages build so I do not expect any problems, but let me know if something does not work as expected... Enjoy! -- 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

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 16 Oct '15

16 Oct '15

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-country: - Ensure ntp is installed (when Install Recommended Packages is off) (9 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (178 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-slide-show: - Update Cloud product to current name (8 days) https://github.com/yast/yast-slide-show/pull/13 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (31 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (21 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-vm: - Fix loading icon (9 days) https://github.com/yast/yast-vm/pull/9 Pending requests in repository yast-auth-server: - Drop ca mgm (108 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (7 days) https://github.com/yast/autoyast-integration-test/pull/30 -- 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] Time to Branch SLE 12 SP1, Leap 42.1, and Clean Up?
by Lukas Ocilka 15 Oct '15

15 Oct '15

Hi, At this point, IIUC, we should be fixing just P1s for both SLE 12 and Leap 42.1, but we might have some fixes or we want to do some refactoring and cleanup in spare time for the $next product. So, is it the right time now? Moreover, I've just checked some projects and it seems we need to do cleanup also in branches, see [branches] in e.g.: https://github.com/yast/yast-autoinstallation or https://github.com/yast/yast-registration - there are many left behind after merged PRs. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3