February 2016 - YaST Development - openSUSE Mailing Lists

[yast-devel] HOWTO: Screencast recording
by Ladislav Slezak 22 Jul '17

22 Jul '17

Hi all, Yesterday I published a short blog post about recording a screencast (a desktop session) to create a video or an animated image. So if you want to have nice animated images in READMES [1] or in pull requests [2] then check this post [3]. Enjoy! [1] https://github.com/lslezak/build-rake/blob/master/README.md [2] https://github.com/yast/yast-registration/pull/240 [3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html -- 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

2 2

[yast-devel] before I file another bug about font sizes...
by Felix Miata 21 Oct '16

21 Oct '16

...I want to make sure there is a solution that I simply have not yet found. Expected (OK) fonts results (e.g.): sw_single @120 DPI in KDE3 on 13.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOK131kde3-120.png sw_single @132 DPI in KF5 on TW: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOKtwkde5-132.png Not expected (undersized) fonts results (e.g.): sw_single @108 DPI in TDE on 13.2: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall132tde-108.png sw_single @120 DPI in KDE3 on 42.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-120.p… sw_single @168 DPI in KDE3 on 42.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-168.p… Clearly sw_single (and other y2 apps) post-13.1 (except in KF5) is using smaller fonts than those used in the y2 control center and in the rest of DE UI, as if both the non-KF5 DE's font settings and QT's font setting in Trolltech.conf are being disregarded. Is there something that can be installed or removed to bring up font sizes to match the rest of the DE and y2cc in KDE3 and TDE without loading the installation with QT5 and/or KF5, or even with QT5 and/or KF5? Or, is this a bug that's already been filed, or one that needs filing? -- "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

3 4

[yast-devel] Refactoring madness: chapter three
by Ancor Gonzalez Sosa 01 Mar '16

01 Mar '16

This is the (hopefully) last part of my list of thing I considered as the obvious way to go while refactoring/reviewing code at some point but turned out to be more controversial than I expected. This week we'll probably agree in a more shared and less personal view about these topics. 1) RSpec as a design validator I like the RSpec approach to unit testing and I consider the RSpec tests of a class like the detailed documentation about its behavior. I try to write the RSpec tests relatively early in the process (without reaching the extreme of TDD) because it allows me to validate my design decisions. If I struggle to write meaningful readable RSpec test or I need a lot of non-obvious mocking during the process, then I conclude that my classes are not properly designed. In that case, I sometimes switch to TDD mode, writing the desired RSpec and then fixing my class. 2) Another note about OOP design In our new code there are some things that I consider kind of "design smells". I can be, as always, wrong but I feel like some of our code is misusing OOP as a mere way of encapsulate functionality. Going back to concrete real examples, we had this: fake_probing = Yast::Storage::FakeProbing.new devicegraph = fake_probing.devicegraph factory = Yast::Storage::FakeDeviceFactory.new(devicegraph) factory.load_yaml_file(input_file) yaml_writer = Yast::Storage::YamlWriter.new yaml_writer.write(devicegraph, output_file) The fact that we had a "new" every couple of lines is a design smell to me. The adopted solution was creating class methods, so we can do things like this. fake_probing = Yast::Storage::FakeProbing.new devicegraph = fake_probing.devicegraph Yast::Storage::FakeDeviceFactory.load_yaml_file(devicegraph, input_file) Yast::Storage::YamlWriter.write(devicegraph, output_file) Just a cosmetic fix for an issue that I consider deeper: we are writing good old procedural code dressed up as OO code. Every class has the only responsibility of implementing one step in a process and only one public method to execute that step (manipulating a set of I/O arguments). Is just one example of solutions that are perfectly correct but look quite unfamiliar to a Ruby developer's eyes and are quite hard to express as a set of RSpec behavior-oriented specs. Not saying they are wrong, just that they don't look like "the ruby way". Like this alternative which (although not perfect) is a much more "rubyist" way of writing the same: factory = Yast::Storage::DevicegraphFactory.new devicegraph = factory.create_from_file(input_file) File.open(output_file, 'w') {|f| f.write devicegraph.to_yaml } 3) Write every piece of code as something to maintain This is more related to Scrum than to Ruby or OOP. Since we are using Scrum to create YaST, I expect most PBIs to result in a YaST client that can be invoked using /sbin/yast2 or in a set of RSpecs that will be executed in every "rake test:unit" and used as a reference documentation in the future. I consider tests in the "examples" directory to be dead code. I consider that moving code from /test or /src/clients into /src/examples is the first step to have it broken with nobody ever noticing. A have a similar feeling about code used for debugging. It should be "in the right place" design-wise. Don't think in the debugging code as something temporary. If you are needing it today, you will probably need it (or something very similar) also in the future. Make it part of your design... and use mechanisms that would be useful when that code is executed as an RSpec test or yast client. That's all. Sorry again for the long text. I suck at summarizing. Cheers. -- 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

4 4

[yast-devel] new-proposal is dead...
by Ancor Gonzalez Sosa 29 Feb '16

29 Feb '16

...long live the new proposal! This mail is just for letting you know that we already deleted the "new-proposal" branch from the yast-storage git repository. All the code and commits from there are now in the yast-storage-ng repository, in the master branch. There is still work to do[1], but you should already aim to the new repo when working in the new yast-storage. Cheers. [1] https://trello.com/c/IRNNAfuY/ -- 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

1 0

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

29 Feb '16

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: - Fix install rules SLE 12 GA (31 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (45 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (33 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (145 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (125 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (86 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (88 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (32 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (68 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (24 days) https://github.com/yast/yast-yast2/pull/433 Pending requests in repository yast-auth-server: - Drop ca mgm (39 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (93 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (16 days) https://github.com/yast/aytests-tests/pull/12 -- 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 26 Feb '16

26 Feb '16

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: - Fix install rules SLE 12 GA (27 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (41 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (20 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (29 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (141 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (29 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (121 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (29 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (82 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (84 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (28 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (5 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (64 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (20 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (30 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (35 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (89 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (12 days) https://github.com/yast/aytests-tests/pull/12 -- 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 26 Feb '16

26 Feb '16

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: - Fix install rules SLE 12 GA (28 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (42 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (21 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (30 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (142 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (122 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (83 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (85 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (29 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (65 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (21 days) https://github.com/yast/yast-yast2/pull/433 Pending requests in repository yast-auth-server: - Drop ca mgm (36 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (90 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (13 days) https://github.com/yast/aytests-tests/pull/12 -- 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 proxy configuration test error
by guenter 25 Feb '16

25 Feb '16

Hi folks, because I have no Novell account nere a bug report to whom it me concern: opensuse 13.1 yast2 proxy test proxy config => returns error Details: > GET http://www.novell.com/ HTTP/1.1 > Host: www.novell.com > User-Agent: curl/7.42.1 > Accept: */* > Proxy-Connection: Keep-Alive > * HTTP 1.0, assume close after body < HTTP/1.0 301 Moved Permanently Solution: Choose another test destination Regards, guenter -- . -- 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] renamed new libstorage
by Arvin Schnell 25 Feb '16

25 Feb '16

Hi, as decided during the planning meeting I have renamed the new libstorage to libstorage-ng: Some things I renamed: RPM name to libstorage-ng (and subpackages accordingly). Library so name to libstorage-ng. Textdomain to libstorage-ng. Git repository from libstorage-bgl-eval to libstorage-ng. I also changed the version to 1.0.0 and the major library version to 3 (yes, those numbers are entirely independent). Some things I did not rename: C++ namespace (still "storage"). C++ header files (still "/usr/include/storage/..."). The name of the Python, Ruby and Perl5 modules (still "storage"). Fillup/sysconfig file (still "storage"). Regards, 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

1 0

[yast-devel] YaST: highlights of development sprint 15
by Ancor Gonzalez Sosa 25 Feb '16

25 Feb '16

Three sprints in a row and we keep blogging about YaST development! https://lizards.opensuse.org/?p=11707 Enjoy -- 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 4

[yast-devel] Refactoring madness: chapter two
by Ancor Gonzalez Sosa 24 Feb '16

24 Feb '16

This is a follow-up on my highly opinionated mail about software design. Be warned, it's much longer than chapter one. Sorry for that. This mail contains concrete examples from the recent yast2-storage rewrite in order to touch some solid ground (simplistic improvised examples didn't work very well in chapter 1). Please, please, PLEASE, don't take it as an attack to the old code or their writers. Once again, this is just as an explained dump of my very own mental checklist of things I care when writing or reviewing code. Meant as a starting point for discussion... but not via mailing list, since we want to get to a conclusion at some point. :-) 1) Responsibility distribution We all agree this is a key aspect of OOP design. But we seem to usually disagree on the result. Single responsibility principle is a nice guideline here... when not taken too far. Going for examples, the original SpaceMaker had the obvious responsibility of resizing and deleting partitions to make space, but also of holding the list of free slots (something I moved to Devicegraph) and of deciding/knowing what was the target size (:desired vs :minimum) for the following steps (something I moved one level up to the Proposal class). So the resulting SpaceMaker was more dumb... while other classes became... well, less dumb. We also had a separate DiskAnalyzer class that other classes queried to know stuff like what's the list of existing windows partitions, which media is being used for installation (we don't want to install on top of ourselves) and that kind of stuff. I "hided" the DiskAnalyzer class behind Devicegraph. So now other classes query those questions directly to the devicegraph object. After all those changes, somebody could argue that Devicegraph responsibility became to broad, against the single responsibility principle. For me it makes sense that devicegraph knows its own list of free slots or which one of its own disks are being used for installation. Simply because it makes sense(TM) and I "feel" it's its responsibility. I want my API to hide the fact that some of those calculations are delegated to a DiskAnalyzer class. The main advantage is that the "users" of Devicegraph don't have to know several other classes just to ask things about the system layout... that leads me to the next point. 2) Keep the dependencies between your classes to a minimum. Another topic in which one could thing that we are going to agree easily... but was not the case. The best thing I can do in that regard is just recommending the chapter titled "Managing dependencies" from the Sandi Metz book[1]. She simply put into words my view about the topic. Including a fairly obvious but still useful checklist on when an object has a dependency. That happens when the object knows: - The name of another class - The name of a message that it intends to send to someone other than self. - The arguments that a message requires and/or the order of those arguments Everytime I see that in a class, my dependencies alarm rings and I start asking myself: Does it make sense? How can avoid that? I really try hard to fight every dependency until I accept it must be there. And lately I find myself using dependency injection more and more. 3) Don't let singleton objects pollute your APIs In some situations, the singleton pattern is a necessary evil. But please restrict the evilness as much as possible. The original code had StorageManager.instance.probed (or similar stuff) in too many places. Several classes (DiskAnalyzer, PartitionCreator, SpaceMaker and StorageProposal) knew were to find the probed devicegraph by the holy grace of Singleton. The modified code hides that singleton behind the Devicegraph.probed class method and reads the probed devicegraph only once. Devicegraph is the only class that knows there is a singleton StorageManager. The devicegraph returned by it is then simply passed as argument to any other class needing it. Thus, DiskAnalyzer (and others) doesn't know anymore about the existence of StorageManager.instance, it just receive a devicegraph to analyze (the fact that this devicegraph is always the probed one is not DiskAnalyzer's business). The example in (4) has also to do with singleton objects. 4) Messages-driven design I can also become quite picky about who sends messages to who (like I did in [2]). In fact, that is an example of two thing I consider wrong. One is sending the messages to the wrong receiver. Another one is pollution caused by singleton. You send messages to an instance of FakeProbing to produce an effect on StorageManager.instance.probed, but there is no reference to StorageManager during that interaction. It just works because FakeProbing and the caller both know about StorageManager being singleton. Talking about messages, emitters, receivers and and all that can look too philosophical. But for me is the key factor when defining an API (I even draw UML interaction diagrams sometimes!). And for me, ending up with a sane API is the key reason for having code reviews. 5) A minor one: don't abuse well known names That's something I do all the time, but I'm trying to improve that. It really hurts the reviewer mind when something is called "factory", "singleton", "strategy", "presenter" and so on but doesn't follow the corresponding Factory, Strategy, WhatsNot patterns. To stop doing that when writing code is one of my new year's resolutions (because I suffer it when reading other's people code). 6) Single responsibility principle... again In (1) I said I can be considered slightly relaxed when applying the single responsibility principle to objects, at least to a purist eyes. I must clarify that I really observe that principle when writing methods within a class, so I end up with a lot of small methods that rely on each other. Not sure if that makes my code easier or more difficult to follow. It depends on the reader, I guess. Well, I think this is enough for a second mail. I guess I have already covered my most important reasons to "slow down" the delivery of already working code in the yast2-storage rewrite. Cheers. [1] http://www.sandimetz.com/products [2] https://github.com/yast/yast-storage/pull/193#discussion_r53643452 -- 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

2 2

Re: [yast-devel] yast2-rpm-handler
by Josef Reidinger 24 Feb '16

24 Feb '16

On Tue, 23 Feb 2016 19:16:35 +0200 "opensuse.lietuviu.kalba" <opensuse.lietuviu.kalba(a)gmail.com> wrote: > > 2016.02.23 14:27, Josef Reidinger rašė: > > Hi, I had vacation and being outside of internat waters, I will > > recheck it now. We need to find good solution for it as other > > packages maybe also need it and we should now place such workaround > > everywhere. Josef > > As /workaround everywhere/, I suggest to > 1) submit "gksu" package (as it contains `xsu`) from obs:GNOME > repository to default repositories; > 2) replace all `xdg-su -c ...` expressions into `xsu ...` . > Problem with gksu is that it require gtk...we used in past kdesu which was in kde-runtime and have similar problem with qt. As want both, it is a bit problematic. It is reason why we used to xdg-su. For me the best solution is to allow xdg-su somehow pass command as argument and not via stupid -c parameter. But it is probably long effort to do such change. I will try to write xdg-su upstream about it. Josef -- 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] GitHub and Git tips
by Ladislav Slezak 24 Feb '16

24 Feb '16

I found this interesting document [1], it's a nice collection of GitHub and Git tips and tricks. Additionally there are links to some recorded presentations about the topic at the top of the document, worth of seeing as well... HTH [1] http://git.io/sheet -- 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 24 Feb '16

24 Feb '16

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: - Fix install rules SLE 12 GA (26 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (40 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (19 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (28 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (140 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (28 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (120 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (28 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (81 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (83 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (27 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (4 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (63 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (19 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (29 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (34 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (88 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (11 days) https://github.com/yast/aytests-tests/pull/12 -- 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] Refactoring madness: chapter one
by Ancor Gonzalez Sosa 23 Feb '16

23 Feb '16

I recently invested quite some time (out of the sprint, my fault) refactoring the code of the new proposal. I didn't change the approach, the main algorithm or the produced result. So finally I changed everything for everything to stay the same. [1] I did it just because I disliked a number of things about the code organization. Code organization is a subjective question, so I though I should write a couple of mails with my reasons to make all those changes. Disclaimer: this is a highly opinionated (and veeery long) email. In this mail, I will focus on stuff that I think is kind of specific to "the Ruby way" of doing things. I will keep more general OOP stuff (like single responsibility, class dependencies, messages-driven design, etc.) out of the discussion for the time being, although it also motivated many of the introduced changes. 1) Avoid input/output arguments when possible. That is, in Ruby this puts total # => 2 total = calculator.sum(total, 3) puts total # => 5 is preferred over this puts total # => 2 calculator.sum(total, 3) puts total # => 5 Of course, in some situations this is even better... but that's not the point in my argumentation total = total.sum(3) 2) Try be as functional as possible. With methods that returns something, no matter if that thing is implemented through storage or through computation. That is, don't tell your objects what to do, tell them what you want to get. That is, this creator = PartitionCreator.new parts = creator.partitions is preferred over creator = PartitionCreator.new creator.create_partitions creator.partitions 3) Don't hesitate to create "volatile" objects and drop them, relying on the garbage collector to do its job. I will elaborate on this one. The strategy for the proposal was: use the layout read from the system (a.k.a. probed) as a starting point. Create a copy of it and run step1 on it with a set of parameters. If it failed, then discard the result and start again with a copy of "probed" trying different parameters for step1. On the other hand, if step1 was successful, consolidate that intermediate result and do a similar thing with step2 (rolling back to post-successful-step1 when needed). Good strategy... but I completely disagreed with the implementation. We have a Yast::StorageManager singleton class that acts as an interface to libstorage and that holds a catalog of devicegraphs (indexed by name). The original implementation of the proposal included the registration of three devicegraphs on that catalog: "proposal" (the working copy), "proposal_base" (the consolidated intermediate result) and "staging" (used to calculate the actions). Those devicegraphs were created as copies of any other and then passed down as I/O arguments to specialized classes performing the steps. It was usually not that obvious who had the responsibility of rolling back "proposal" to the content of "proposal_base" and so on. It was also not clear who was responsible of cleaning up the catalog after the whole process took place. My refactoring does not use that catalog at all. Moreover, it contains minimal references to that singleton object. Like here [2], in which the reference is "hidden" after a Devicegraph.probed method (in which dependency injection is used, btw). The new code creates "volatile" (in the sense of "unnamed", not indexed in a catalog) devicegraph objects. Those objects gets discarded when they are replaced with another copy resulting of a successful step (no more I/O arguments to step1) or simply when they prove to not be longer worth holding (for example, step1 failed). No globally named and registered stuff, just "a lot" of work for the garbage collector (actually trivial for the ruby GC capabilities). That's all for this mail. Sorry for the long text (and for threatening you with even more chapters), but I think that we need to agree in best practices and, even more important, on how much relevance do we want to give to them. Like "was such an investment of time in changing a perfectly working code really worth it?". I wanted to give some of my (opinionated) reasons to reply "yes". Cheers. [1] https://github.com/yast/yast-storage/pull/188 [2] https://github.com/yast/yast-storage/pull/188/files#diff-095293409316827171… -- 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

2 2

[yast-devel] Fwd: More mentors for YaST
by Ancor Gonzalez Sosa 23 Feb '16

23 Feb '16

The GSoC coordinators are asking for backup mentors. Please reach Christian if you plan to help with any project (or propose a new one). He will add you as backup maintainer. -------- Forwarded Message -------- Subject: More mentors for YaST Date: Mon, 15 Feb 2016 17:47:52 +0100 From: Christian Bruckmayer <cbruckmayer(a)suse.de> To: jreidinger(a)suse.cz, Ancor Gonzalez Sosa <ancor(a)suse.de>, Imobach González Sosa <igonzalezsosa(a)suse.de> Hey, we would like to add to each GSoC project at least one additional backup-mentor (at the moment we have less mentors than projects...). Is there anybody in the YaST team who we could ask to act as a backup-mentor to your already submitted projects? Thanks Christian -- 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-rpm-handler
by opensuse.lietuviu.kalba 23 Feb '16

23 Feb '16

Hi, I created package [1], that has program to open RPM packages in YaST2 software manager (similarly as in /usr/bin/package-manager from libzypp (<=13.9) shipped with openSUSE 13.1 and earlier). Some description is FATE [2]. I have no rights to submit package directly to YaST:Head or Factory. Please, can someone submit it there? Or [better], can someone please integrate this into yast2-packager <https://github.com/yast/yast-packager> ? [1] https://build.opensuse.org/package/show/home:embar-:Lietukas/yast2-rpm-hand… [2] https://features.opensuse.org/319376 -- Regards -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 16

[yast-devel] Generic / Repo-specific READMEs at GitHub
by Lukas Ocilka 23 Feb '16

23 Feb '16

Hi, When Christopher was in Prague, a few of us had a brainstorming about the need of having devel-documentation placed directly in a Yast/libstorage/linuxrc repository. There are no doubts that it's one of the most important parts of projects hosted at GitHub. All their howtos mention "create README[.md]" as the very first step. In fact, we'll have new hires in the team and in such situations, good documentation is one of the most important parts. Good documentation goes from very high level to lower and lower level. We have already summarized that in Yast Team Challenges, but the summary doesn't belong to this document as it's too detailed. That's why I'm putting it here as a WIP item and deleting it from that document: --- cut --- The README should at least describe the steps needed for maintenance (for a person without expert knowledge in the area) including: * What is the project good for - what does it actually do (and how), what it cannot do (unsupported scenarios), limitations * Links to the documentation, high level and low level descriptions (e.g. RFC, wikipedia articles, man pages, project documentation, openSUSE wiki), terminology * How to fetch the source code (if something outside Git is needed it should be mentioned) * What prerequisites are needed to build the sources (external libraries, gems, scripts, …) * How to build the sources (make/rake commands…) * How to setup a testing environment (e.g. iSCSI target for iSCSI client) * How to run the code to test a change (esp. needed for non trivial projects like linuxrc) * How to run automated tests * How to build a package for submission * How to submit the package (if it needs some manual steps) * Troubleshooting (how to solve typical problems) The README should be reasonably short, if some section is too long it should be moved to a separate document (or to GitHub wiki) and linked. --- cut --- The project consists of - Taking a decision where to go - How to get there - Implementing this important documentation Those two who, according to my knowledge, were working on this were Ladislav and Christopher, but there were not the only ones and a pilot project for READMEs has been done a few months ago by Martin. It's still not finished, but moving forward. 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

4 3

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

23 Feb '16

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: - Fix install rules SLE 12 GA (25 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (39 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (18 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (27 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (139 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (27 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (119 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (27 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (80 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (82 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (26 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (62 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (18 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (28 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-firewall: - Merge into Sle 12 sp1 (14 days) https://github.com/yast/yast-firewall/pull/23 Pending requests in repository yast-auth-server: - Drop ca mgm (33 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (87 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (10 days) https://github.com/yast/aytests-tests/pull/12 -- 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 22 Feb '16

22 Feb '16

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: - Fix install rules SLE 12 GA (24 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (38 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (17 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (26 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (138 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (26 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (118 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (26 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (79 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (81 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (25 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (61 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (17 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (27 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-firewall: - Merge into Sle 12 sp1 (13 days) https://github.com/yast/yast-firewall/pull/23 Pending requests in repository yast-auth-server: - Drop ca mgm (32 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (86 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (9 days) https://github.com/yast/aytests-tests/pull/12 -- 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] Using the new libstorage-bgl
by Stefan Hundhammer 19 Feb '16

19 Feb '16

There are no packages yet for libstorage-bgl-eval and the new proposal. Here is what you have to do to work with them: - Force-uninstall old libstorage: sudo rpm -e --nodeps libstorage6 libstorage-ruby libstorage-python libstorage-devel libstorage-testsuite - Check out new libstorage from github: git clone git@github.com:openSUSE/libstorage-bgl-eval.git - Build and install: cd libstorage-bgl-eval make -f Makefile.repo make sudo make install New Proposal: - Check out the "new-proposal" branch of yast2-storage - In the yast2-storage source directory, to to the lib/storage directory: cd $MYSRC/yast-storage cd src/lib/storage - Start the minimalistic test frame as root (required for hardware probing): sudo ./storage_proposal.rb - Watch the y2log and stdout Kind regards -- Stefan Hundhammer <shundhammer(a)suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) Maxfeldstr. 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

4 5

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

19 Feb '16

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: - Fix install rules SLE 12 GA (21 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (35 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (14 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (23 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (135 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (23 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (115 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (23 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (76 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (78 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (22 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (57 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (58 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (14 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (24 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-firewall: - Merge into Sle 12 sp1 (10 days) https://github.com/yast/yast-firewall/pull/23 Pending requests in repository yast-auth-server: - Drop ca mgm (29 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (83 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (6 days) https://github.com/yast/aytests-tests/pull/12 -- 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 18 Feb '16

18 Feb '16

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: - Fix install rules SLE 12 GA (20 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (34 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (13 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (22 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (134 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (22 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (114 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (22 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-registration: - [WIP] Read registration codes from a USB stick (8 days) https://github.com/yast/yast-registration/pull/241 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (75 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (77 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (21 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (56 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (57 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (13 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (23 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-firewall: - Merge into Sle 12 sp1 (9 days) https://github.com/yast/yast-firewall/pull/23 Pending requests in repository yast-auth-server: - Drop ca mgm (28 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (82 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (5 days) https://github.com/yast/aytests-tests/pull/12 -- 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] polish -> multiple license ack during upgrade installation
by Felix Miata 17 Feb '16

17 Feb '16

Just did three offline 32 bit to 64 bit upgrades, one 13.1 to 42.1, two 13.1 to 13.1. As usual, first GUI screen is license agreement ack. Then in all three upgrades, after completing partitioning screens, the license agreement ack screen returned. Is this expected? -- "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

2 3

[yast-devel] openQA Documentation
by Lukas Ocilka 17 Feb '16

17 Feb '16

Hi guys, I've got an updated documentation for the openQA project and process. We are kindly asked to provide feedback for what is missing there, what is not understandable and what is great :) The fist one is actually internal, sorry for that: https://wiki.microfocus.net/index.php?title=RD-OPS_QA/openQA_review Describes the virtual team, staging, reviewing, and ... not much more anyway The openQA process is described here: https://progress.opensuse.org/projects/openqav3/wiki openQA project, contributing, configuration, writing tests...: https://github.com/os-autoinst/openQA/tree/master/docs openQA Presentations: https://github.com/os-autoinst/documentation Anyone interested (or force-interested) in openQA should read these sources and try to contribute to better-understandable documentation, even just by summarizing what you were not able to find and/or understand. Thanks in advance 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

1 0

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

17 Feb '16

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: - WIP: Test and refactor AutoinstallIoInclude#Get (4 days) https://github.com/yast/yast-autoinstallation/pull/193 - Fix install rules SLE 12 GA (19 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (33 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (12 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (21 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (133 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (21 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (113 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (21 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-registration: - [WIP] Read registration codes from a USB stick (7 days) https://github.com/yast/yast-registration/pull/241 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (74 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (76 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (20 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (55 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (56 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (12 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (22 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-firewall: - Merge into Sle 12 sp1 (8 days) https://github.com/yast/yast-firewall/pull/23 Pending requests in repository yast-auth-server: - Drop ca mgm (27 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (81 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (4 days) https://github.com/yast/aytests-tests/pull/12 -- 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 Feb '16

16 Feb '16

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: - Fix install rules SLE 12 GA (18 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (32 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (11 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (20 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (132 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (20 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (112 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (20 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-registration: - [WIP] Read registration codes from a USB stick (6 days) https://github.com/yast/yast-registration/pull/241 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (73 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (75 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (19 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (54 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (55 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (11 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (21 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-firewall: - Merge into Sle 12 sp1 (7 days) https://github.com/yast/yast-firewall/pull/23 Pending requests in repository yast-auth-server: - Drop ca mgm (26 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (80 days) https://github.com/yast/yast.github.io/pull/55 -- 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] Scrum and yast2-storage
by Ancor Gonzalez Sosa 15 Feb '16

15 Feb '16

Last week we discussed if we were following the "potentially shippable product" with the new libstorage (looks like yes), but now the same question arises about yast2-storage. Right now, we are using the same repository for the new code and the old one. Even when using branches, you can still see mixed code in those branches. For example, the branch "new-proposal" includes the code presented during last review by HuHa that can generate proposals using only libstorage-bgl (mostly living in /lib), but also includes all the old code from yast2-storage (all the other directories). As HuHa proved during his presentation, the code works. But it has no unit tests, we don't have stats about code quality or coverage and so on. So IMHO, we need a pristine repo containing only new code that relies on libstorage-bgl (the visual partitioner that Arvin created some sprints ago, the new proposal...). For that repo, we need to have CI, coverals, rubocop and code climate, to make sure we keep the quality at acceptable levels (and installable as rpm). I guess a different branch would also make it, but I prefer to have a different repo, like we have with libstorage. We can have our own versioning schema (and changelog) and we can recreate the current branches organization for CI (master for TW, other branches for other distros) and compile it in the same OBS repo that libstorage-ng. What about yast/yast-storage-ng? What do we do with the versions? Start with 0.1? 4.0? Cheers. -- 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

1 0

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

15 Feb '16

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: - Fix install rules SLE 12 GA (17 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (31 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (10 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (19 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (131 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (19 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (111 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (19 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (72 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (74 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (18 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (53 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (54 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (10 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (20 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-firewall: - Merge into Sle 12 sp1 (6 days) https://github.com/yast/yast-firewall/pull/23 Pending requests in repository yast-auth-server: - Drop ca mgm (25 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (79 days) https://github.com/yast/yast.github.io/pull/55 -- 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 12 Feb '16

12 Feb '16

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: - Fix install rules SLE 12 GA (14 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (28 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (7 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (16 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (128 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (16 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (108 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (16 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (69 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (71 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (15 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (50 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (51 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (7 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (17 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (22 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (76 days) https://github.com/yast/yast.github.io/pull/55 -- 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 11 Feb '16

11 Feb '16

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: - Fix install rules SLE 12 GA (13 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (27 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (6 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (15 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (127 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (15 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (107 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (15 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (68 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (70 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (14 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (49 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (50 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (6 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (16 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (21 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (75 days) https://github.com/yast/yast.github.io/pull/55 -- 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 10 Feb '16

10 Feb '16

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: - Fix install rules SLE 12 GA (12 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (26 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (5 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (14 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (126 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (14 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (106 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (14 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (67 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (69 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (13 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (48 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (49 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (5 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (15 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (20 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (74 days) https://github.com/yast/yast.github.io/pull/55 -- 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] NEEDINFOs On Our Team Members
by Lukas Ocilka 09 Feb '16

09 Feb '16

Moin, I've got some complaints that some of our team members typically do not answer needinfo requests and that some might be several months old already. I know that this can be actually result of our SCRUMming, at least partly. So, please, DO answer needinfos, even if that bug is not planned for $this/$next sprint. I was told that Bugzilla can be configured in a way that periodically sends reminders, but I don't know how. Anyone? Thanks in advance 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

[yast-devel] Breaking the API
by Ancor Gonzalez Sosa 09 Feb '16

09 Feb '16

In our attempt to delete dead code, we recently removed some methods from the UsersSimple API[1]. I'm all for it (actually, I pushed for it) and I would happily remove all the methods that are not longer called from the YaST code. Death to all Perl code! The problem is that we are not the only users of our own legacy APIs. With UsersSimple it should be fairly safe because the module is supposedly only used during installation (although you can always get surprised by the extremely hacky SAP-related modules and scripts). But with other modules (say /Network/) is not so clear. We should have a mechanism to deprecate API methods and to delete them in a way in which: - We keep track of what we remove in every version bump - Interested parties (like the maintainers of the SAP modules) can get alerted of deprecation/removal, so they can adapt their stuff or oppose to the change. Otherwise, cruft will be there forever because we are too afraid to remove it. Any plan or suggestion? Cheers [1] https://github.com/yast/yast-users/pull/86 PS.- After writing $SUBJECT, I couldn't resist https://www.youtube.com/watch?v=L397TWLwrUU -- 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

2 1

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

09 Feb '16

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: - Fix install rules SLE 12 GA (11 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (25 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (13 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (125 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (13 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (105 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (13 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (66 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (68 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (12 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (47 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (48 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Count test coverage more accurately (14 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (19 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (73 days) https://github.com/yast/yast.github.io/pull/55 -- 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 08 Feb '16

08 Feb '16

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: - Fix install rules SLE 12 GA (10 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (24 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (12 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (124 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (12 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (104 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (12 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (65 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (67 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (11 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (46 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (47 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Count test coverage more accurately (13 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (18 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (72 days) https://github.com/yast/yast.github.io/pull/55 -- 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] Created YaST:SLE-12:SP1 OBS project + how to copy from IBS to OBS
by Ladislav Slezak 05 Feb '16

05 Feb '16

Hi all, I just created YaST:SLE-12:SP1 OBS project which will be used for building SP1 based commits at Jenkins. I simply copied the packages from IBS from SUSE:SLE-12-SP1:GA project and added some additional rubygems (coveralls, rubocop,...). A short how to (if you are interested in details): The "osc" tool can copy packages also between OBS instances (see -t option of the "copypac" command). For mass copying you can use "ls" command and the "xargs" tool. I have copied the packages with this command (it's a single line): osc -A https://api.suse.de ls SUSE:SLE-12-SP1:GA | grep yast | \ xargs -L 1 -I % osc -A https://api.suse.de copypac SUSE:SLE-12-SP1:GA \ % -t https://api.opensuse.org YaST:SLE-12:SP1 Maybe this trick helps you if you need something similar in the future... -- 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 05 Feb '16

05 Feb '16

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: - Fix install rules SLE 12 GA (7 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (21 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (9 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (121 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (9 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (101 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (9 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (62 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (64 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (8 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (43 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (44 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Count test coverage more accurately (10 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (15 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (69 days) https://github.com/yast/yast.github.io/pull/55 -- 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] Using the YaST hook feature on SLE12SP1
by Erico Mendonca 04 Feb '16

04 Feb '16

Hello all, I’m trying to use the hook feature as described in /usr/share/doc/packages/yast2/general/Hooks.md to execute my Ruby script. I followed the steps to copy/mount bind it to the /var/lib/YaST2/hooks/installation directory via a pre-script. I tried naming it installation_start_00_myscript.rb, but it seems like it’s not being picked up at all according to y2log. I can see that the existing script (before_rpmcopy_00_migrate_desktop.sh) runs, but not mine. The documentation says that if using autoyast (which is the case), I should name it after one of the 4 available modules (autoinit, auto setup, initial_installation_proposal and autoimage). I also tried that, but it doesn’t seem to make sense, as y2log shows that it’s trying to run hook scripts for all the 13 or so checkpoints for manual installation. Am I missing something here? Is it caching scripts somewhere earlier than the pre-scripts phase and ignoring mine? Erico M. Mendonça Dedicated Support Engineer SUSE Rua Joaquim Floriano, 466 – Ed. Corporate 12º andar, Itaim Bibi – São Paulo – SP / Brasil Tel: +55 (11) 3345-3900 Cel: + 55 (61) 8594-9557 erico.mendonca(a)suse.com www.suse.com

2 1

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

04 Feb '16

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: - Fix install rules SLE 12 GA (6 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (20 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (8 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (120 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (8 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (100 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (8 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (61 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (63 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (7 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (42 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (43 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Count test coverage more accurately (9 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (14 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (68 days) https://github.com/yast/yast.github.io/pull/55 -- 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] YaST: highlights of development sprint 14
by Ancor Gonzalez Sosa 03 Feb '16

03 Feb '16

Another three weeks sprint and another report from the YaST team. Enjoy https://lizards.opensuse.org/?p=11673 Cheers -- 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 8

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

03 Feb '16

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: - Fix install rules SLE 12 GA (5 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (19 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (7 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (119 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (7 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (99 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (7 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (60 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (62 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (6 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (41 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (42 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Count test coverage more accurately (8 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (13 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (67 days) https://github.com/yast/yast.github.io/pull/55 -- 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 02 Feb '16

02 Feb '16

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: - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (18 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (6 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (118 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (6 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (98 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (6 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (59 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (61 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Ported support for LVM proposal setting from SP1 to Master (40 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (41 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Count test coverage more accurately (7 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (12 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (66 days) https://github.com/yast/yast.github.io/pull/55 -- 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 01 Feb '16

01 Feb '16

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: - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (17 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (117 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (97 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-kdump: - Fix handling of crashkernel parameter for Xen (9 days) https://github.com/yast/yast-kdump/pull/59 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (58 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (60 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Ported support for LVM proposal setting from SP1 to Master (39 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (40 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Count test coverage more accurately (6 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (11 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (65 days) https://github.com/yast/yast.github.io/pull/55 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0