December 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] Fixing yast2-slide-show for SLE11 SP3
by Karl Eichwalder 16 Sep '15

16 Sep '15

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 7

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 26 Dec '13

26 Dec '13

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-autoinstallation: - semi automatic installation on demand https://github.com/yast/yast-autoinstallation/pull/20 Pending requests in repository yast-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-cluster: - update yast2-cluster to adapt new corosync https://github.com/yast/yast-cluster/pull/2 Pending requests in repository yast-network: - Doc: cleanup old, add a new diagram https://github.com/yast/yast-network/pull/142 - Remove lan network from autoinstallation second stage as it is already d... https://github.com/yast/yast-network/pull/139 - propose new object API for devices https://github.com/yast/yast-network/pull/128 Pending requests in repository yast-nfs-server: - Move the screenshot from imagebin to inside the repo. https://github.com/yast/yast-nfs-server/pull/13 Pending requests in repository yast-s390: - Changed handling of unformatted DASD devices during autoinstallation (fate#313228) https://github.com/yast/yast-s390/pull/3 Pending requests in repository yast-storage: - propose dedicated /boot/zipl partition on S/390 https://github.com/yast/yast-storage/pull/14 - Kernel modules loaded on boot switched to using unified API https://github.com/yast/yast-storage/pull/13 Pending requests in repository yast-yast2: - Document and test AsciiFile https://github.com/yast/yast-yast2/pull/149 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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 25 Dec '13

25 Dec '13

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-autoinstallation: - semi automatic installation on demand https://github.com/yast/yast-autoinstallation/pull/20 Pending requests in repository yast-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-cluster: - update yast2-cluster to adapt new corosync https://github.com/yast/yast-cluster/pull/2 Pending requests in repository yast-network: - Doc: cleanup old, add a new diagram https://github.com/yast/yast-network/pull/142 - Remove lan network from autoinstallation second stage as it is already d... https://github.com/yast/yast-network/pull/139 - propose new object API for devices https://github.com/yast/yast-network/pull/128 Pending requests in repository yast-nfs-server: - Move the screenshot from imagebin to inside the repo. https://github.com/yast/yast-nfs-server/pull/13 Pending requests in repository yast-s390: - Changed handling of unformatted DASD devices during autoinstallation (fate#313228) https://github.com/yast/yast-s390/pull/3 Pending requests in repository yast-storage: - propose dedicated /boot/zipl partition on S/390 https://github.com/yast/yast-storage/pull/14 - Kernel modules loaded on boot switched to using unified API https://github.com/yast/yast-storage/pull/13 Pending requests in repository yast-yast2: - Document and test AsciiFile https://github.com/yast/yast-yast2/pull/149 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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 24 Dec '13

24 Dec '13

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-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-network: - Doc: cleanup old, add a new diagram https://github.com/yast/yast-network/pull/142 - Remove lan network from autoinstallation second stage as it is already d... https://github.com/yast/yast-network/pull/139 - propose new object API for devices https://github.com/yast/yast-network/pull/128 Pending requests in repository yast-s390: - Changed handling of unformatted DASD devices during autoinstallation (fate#313228) https://github.com/yast/yast-s390/pull/3 Pending requests in repository yast-storage: - propose dedicated /boot/zipl partition on S/390 https://github.com/yast/yast-storage/pull/14 - Kernel modules loaded on boot switched to using unified API https://github.com/yast/yast-storage/pull/13 Pending requests in repository yast-yast2: - Document and test AsciiFile https://github.com/yast/yast-yast2/pull/149 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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 Console Module is "broken"
by Günther J. Niederwimmer 23 Dec '13

23 Dec '13

Hello, Can any tell me please, witch packet i have to install for the "graphic" in console Mode There is a missing dependency for the correct drawing the frame ?. This is a minimal Install and running in init 3 mode. Thanks :) -- 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

3 5

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 23 Dec '13

23 Dec '13

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-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-network: - Doc: cleanup old, add a new diagram https://github.com/yast/yast-network/pull/142 Pending requests in repository yast-storage: - propose dedicated /boot/zipl partition on S/390 https://github.com/yast/yast-storage/pull/14 Pending requests in repository yast-yast2: - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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] new README.md
by Martin Vidner 20 Dec '13

20 Dec '13

Hi, please use https://github.com/yast/yast-nfs-server/blob/master/README.md as a template for READMEs in your repos. Note that the file mixes generic and module specific information, so if you change something generic, use https://github.com/yast/yast-devtools/tree/master/mass-tools to propagate the change to other copies (that have yet to arise). Thanks to David for the 3 drafts, Pepa for review, and sorry that it took me 10 weeks to merge. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] Example new module in pure ruby
by Josef Reidinger 20 Dec '13

20 Dec '13

Hi, I have a feature to write new module for IO channels on s390. I take it as oppurtinity to demonstrate how can look pure ruby yast module with object oriented design and easy testibility. I create pull request[1] so everyone can comment it and at final we can see how good can look yast module written in ruby. I welcome any comment in pull request. Josef [1] https://github.com/yast/yast-cio/pull/1 -- 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] Cheating in "rake osc:build"
by Ladislav Slezak 20 Dec '13

20 Dec '13

Hi, if you are testing a fix and want to be sure (you should!) that your package still builds you should run "rake osc:build" task to build the package locally. The disadvantage is that it checks that all changes are committed in Git, which might be sometimes annoying if you are experimenting with something (like yesterday I was doing some cleanup in BuildRequires which is an iterative process). You need to commit every your change, sometimes revert it, etc. Of course, you can rebase at the end, but that's inconvenient. I found this simple cheat which you can add to the Rakefile: Rake::Task["check:committed"].clear_actions It makes the action in "check:committed" blank so the check is skipped. (Note: do not forget to remove it once you are satisfied with your changes so it is not committed to Git ;-)) -- 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] Getting the Most from YaST: Some Very Helpful but Mostly Unknown Tricks
by Martin Vidner 20 Dec '13

20 Dec '13

This is an article by Thomas Goettlicher, appearing in the recent edition of our customer newsletter: https://www.suse.com/company/newsletter/suse-news-archive/suse_insider_2013… ToC: Hotkeys Themes and Stylesheet Editor Driver Update Boot Loader Speaker Remote Installation Macro Recorder BTW on http://www.suse.com/company/newsletter/ the newsletter is also available in other languages: de en_UK es fr ja pl pt_BR and zh_CN (in a zip file only) -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] yast2-apparmor
by Christian Boltz 20 Dec '13

20 Dec '13

Hello, large parts of the YaST2 AppArmor module were removed in openSUSE 13.1. Nevertheless, a quick grep on the source shows that it's still using the Immunix::* perl modules a lot. Are those code sections active, or do they contain disabled / commented out / unused code? The reason why I'm asking: upstream AppArmor is switching to python (for the tools like aa-logprof etc.), which also means the perl modules won't see too much maintenance ;-) Therefore it would be good to know if the Immunix::* perl modules are still needed by YaST. Regards, Christian Boltz -- Die SLES macht ja die gleichen Zicken, dafür kann man sich aber aufgrun der höheren Preises zumindest eines der armen Support-Würstchen greifen und erfahren: "ZEN bietet aber darüber hinaus viele Vorteile.". Grrrr. [Bernd Glueckert in 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

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 20 Dec '13

20 Dec '13

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-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-storage: - propose dedicated /boot/zipl partition on S/390 https://github.com/yast/yast-storage/pull/14 Pending requests in repository yast-yast2: - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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] broken Packet in Jenkins
by Günther J. Niederwimmer 19 Dec '13

19 Dec '13

Hello, Seven Days all hour a message from broken yast-tag-libyui :(. -- 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

2 1

[yast-devel] Better "lib/" and "control/" Yast subpath support in devtools
by Ladislav Slezak 19 Dec '13

19 Dec '13

Hi, I have added new macros for handling "lib/" and "control/" Yast subpaths in devtools. For "lib/" subpath you can now write this in Makefile.am: ylibdir = @ylibdir@/foo ylib_DATA = lib/foo/bar.rb and in *.spec: %dir %{yast_libdir}/foo %{yast_libdir}/foo/bar.rb For "control/" subpath: Makefile.am: control_DATA = foo.xml (remove the "controldir" specification if present, it's now defined globally in devtools) *.spec: %dir %{yast_controldir} %{yast_controldir}/foo.xml Note: this requires yast2-devtools >= 3.1.15, update the dependencies accordingly You can check these pull requests, if you want to see some examples: https://github.com/yast/yast-network/pull/143/files https://github.com/yast/yast-network/pull/144/files -- 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] how to span columns in a Table
by Dongmao Zhang 19 Dec '13

19 Dec '13

dear list, I met this issue, I have a table with 2 columns and the code is this: Table(Id(:memberaddr1), Header("ip","nodeid"),[]), please look at the attached picture: the column width is too narrow, it leave a big space in the right of the table which I drew a red rectangle to show it. Is there any good ways to let the column automatically occupy the whole space of the table? Dongmao zhang

4 5

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 19 Dec '13

19 Dec '13

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-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-yast2: - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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] Control files and the RNG schema moved to a separate package/GitHub repo
by Ladislav Slezak 18 Dec '13

18 Dec '13

Hi! The installation control files were part of yast-installation Git repository although they were not packaged to yast2-installation.rpm package. They had to be manually copied to skelcd-control-* packages in OBS. Moreover after updating the files in OBS they got out of sync with Git and later you need resolve potential conflicts. The problem with RNG schema is that packaging it into yast2-installation causes huge build dependencies if you just need to check validity of your control file during build. Therefore I moved the control files to a new separate GitHub repository[1] (I moved them with history, see [2] how to do it) and created a separate RPM package (not included in Factory yet [3]) I'll adapt the packages which do control file validation to use this new package, just expect some pull requests ;-) [1] https://github.com/yast/yast-installation-control [2] https://help.github.com/articles/splitting-a-subpath-out-into-a-new-reposit… [3] https://build.opensuse.org/request/show/211387 -- 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] Factory's zypper -v in zypper libzypp wants to remove YaST
by Felix Miata 18 Dec '13

18 Dec '13

Is there an ETA on this not happening any more? I don't see a bug opened on it. -- "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: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org -- 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 18 Dec '13

18 Dec '13

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-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-installation: - move the control files to a separate package/git repo https://github.com/yast/yast-installation/pull/121 Pending requests in repository yast-network: - propose new object API for devices https://github.com/yast/yast-network/pull/128 Pending requests in repository yast-nfs-server: - Replace README with README.md https://github.com/yast/yast-nfs-server/pull/12 Pending requests in repository yast-s390: - Changed handling of unformatted DASD devices during autoinstallation (fate#313228) https://github.com/yast/yast-s390/pull/3 Pending requests in repository yast-storage: - Kernel modules loaded on boot switched to using unified API https://github.com/yast/yast-storage/pull/13 - move out ui extension https://github.com/yast/yast-storage/pull/9 Pending requests in repository yast-yast2: - Document and test AsciiFile https://github.com/yast/yast-yast2/pull/149 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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 module with Ldap Support *.ldif Files
by Günther J. Niederwimmer 17 Dec '13

17 Dec '13

Hello, We have for YaST2 Module with ldap support near no Documentation :(. So I have the Question is it not possible to insert in the packages a *.ldif File for the end User? some have a external Ldap sever (SLES) and have to search for the Parameter from the YaST2 Module to configure the ldap server, but find nothing. I have make a FAT Entry. [New: openFATE 316750] *.ldif file for YaST2 Module Ldap configuration I hope this is possible ;) -- 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

1 0

[yast-devel] Please fix the zypp-team account
by Stephan Kulow 17 Dec '13

17 Dec '13

Hi, The yast modules are submitted from account zypp-team, which has set zypp-devel(a)suse.de as email. I can decline and comment as I want on such requests - the mail to the submitter just bounces. Please set the email of that account to something actually read - either by an actual team or by someone who's responsible for the submission. The current case is https://build.opensuse.org/request/show/211153 - there is no name associated with that request I can email to ;( Greetings, Stephan -- "Someone's been mean to you! Tell me who it is, so I can punch him tastefully." -- Ralph Bakshi's Mighty Mouse -- 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] Serial console in VirtualBox
by Ladislav Slezak 17 Dec '13

17 Dec '13

Hi, we have discussed serial console support several times at the meetings, without much output (except "it should work") without any idea about testing. I found out that VirtualBox supports also serial port emulation which can be used for emulating a serial console. Here is a short HowTo for emulating a serial console in VirtualBox: - Install "socat" utility ("zypper in socat", it's included in 12.3 and 13.1) - Create a new virtual machine in VBox, configure it for installing the requested product (i.e. add the selected ISO image as a virtual CD drive) - In "Settings" -> "Serial Ports" set "Enable Serial Port", "Port Number": COM1, "Port Mode": "Host Pipe" Select "Create Pipe" checkbox, enter path to the created pipe file in "Port/File Path" (e.g. "/tmp/com1") - Boot the machine - In the host run command "socat unix-connect:/tmp/com1 stdio,raw,echo=0,icanon=0" in a terminal (replace "/tmp/com1" by the path set in the serial port config) - In the VM boot prompt add "console=ttyS0,115200" option (or you can enter that using the text menu in the serial console) - Start the installation - You should see the boot process and then textmode Yast installer in the serial console terminal. Install the system as usually, there is nothing specific to serial console installation (besides it is in textmode). I have tested the latest NI ISO image and the installation was successful! After reboot you can log into the machine using the serial console as well. Summary: The feature still works, we just need to check it later once again (in some Beta, to make sure we did not break it). -- 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

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 17 Dec '13

17 Dec '13

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-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-network: - propose new object API for devices https://github.com/yast/yast-network/pull/128 Pending requests in repository yast-nfs-server: - Replace README with README.md https://github.com/yast/yast-nfs-server/pull/12 Pending requests in repository yast-s390: - Changed handling of unformatted DASD devices during autoinstallation (fate#313228) https://github.com/yast/yast-s390/pull/3 Pending requests in repository yast-storage: - Kernel modules loaded on boot switched to using unified API https://github.com/yast/yast-storage/pull/13 - move out ui extension https://github.com/yast/yast-storage/pull/9 Pending requests in repository yast-yast2: - Document and test AsciiFile https://github.com/yast/yast-yast2/pull/149 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- 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] Moving from *.spec.in to *.spec
by Ladislav Slezak 16 Dec '13

16 Dec '13

[ This change was already done some time ago, I just forgot to announce it. This announcement is mainly important for the community developers. ] Introduction ------------ For SLE12/openSUSE-13.2 we switched from *.spec.in files (which were processed by "create-spec" script from devtools during "make package-local") to directed *.spec stored in Git. This is needed because of the new CI integration (it uses "osc build" as a backend for testing build and we need an easy way to get *.spec, the old way was too complicated). This will also make the future maintenance easier, now for generating the *.spec for SLE11 you need SLE11 devtools which is the most tricky part when preparing a maintenance update. With *.spec files stored directly in Git this problem is gone... Moving from *.spec.in to *.spec -------------------------------- The *.spec.in files provided a flexibility by using some macros which were expanded by "create-spec". To keep this flexibility we moved the shared code to RPM macros [1] which is a clean and standard RPM way. I did the move for most of Yast packages (I skipped the unmaintained/obsolete ones), but some 3rd party modules will be missing the transition so here is a quick HowTo: - move *.spec.in to package/*.spec - replace the @MACROS@: - @HEADER-COMMENT@ and @HEADER@: replace by the content generated by "create-spec", look at the generated *.spec or see the generator[2] - the rest should be replaced by the respective RPM tag and an Yast RPM macro, see the example in yast2 [3] - replace the macros also in the %files section (again, see the example) - @CLEAN@ can be removed (not needed) - update the BuildRequires dependency to "yast2-devtools >= 3.0.6" (contains the new RPM macros) (You could simply use the *.spec generated by "create-spec" script but that's not recommended, it will miss some future changes as the RPM macros can be updated in the future.) If you have any questions or problems with transition in your module then just ask. [1] https://github.com/yast/yast-devtools/blob/master/build-tools/rpm/macros.ya… [2] https://github.com/yast/yast-devtools/blob/openSUSE-13_1/devtools/bin/creat… [3] https://github.com/yast/yast-yast2/commit/e0a77efcfa4feb16dfb2c88779f313b9e… -- 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 Dec '13

16 Dec '13

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-bootloader: - fix reading of MD redundcancy settings in grub/grub2 https://github.com/yast/yast-bootloader/pull/25 Pending requests in repository yast-network: - propose new object API for devices https://github.com/yast/yast-network/pull/128 Pending requests in repository yast-nfs-server: - Replace README with README.md https://github.com/yast/yast-nfs-server/pull/12 Pending requests in repository yast-s390: - Changed handling of unformatted DASD devices during autoinstallation (fate#313228) https://github.com/yast/yast-s390/pull/3 Pending requests in repository yast-storage: - Kernel modules loaded on boot switched to using unified API https://github.com/yast/yast-storage/pull/13 - move out ui extension https://github.com/yast/yast-storage/pull/9 Pending requests in repository yast-yast2: - Document and test AsciiFile https://github.com/yast/yast-yast2/pull/149 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/128 - fixed /sbin/yast2 to start correctly in non UTF-8 environment https://github.com/yast/yast-yast2/pull/127 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0