February 2017 - YaST Development - openSUSE Mailing Lists

Re: [yast-devel] Re: SP3 and factory have different binary sources
by Ludwig Nussel 06 Feb '17

06 Feb '17

Ludwig Nussel wrote: > Josef Reidinger wrote: >> On Wed, 18 Jan 2017 17:20:26 +0100 >> Ludwig Nussel <lnussel(a)suse.com> wrote: >> >>> [if there were replies for this on the list only I didn't get them] >>> >>> Any update here? >> >> Hi, >> no update. I suggest to talk with lukas ocilka to move forward. As he >> is product owner and he prioritize work and we are currently quite >> overwhelmed with development of CAASP, so you need to convince him we >> should invest time to change way how we submitting stuff. > > Right now yast makes mine and the SLE release manager's lives for > reviewing harder as all yast packages appear in the list of not > matching packages. It's hard to tell whether there's a real and > intentional difference to Factory or just fallout from this way of > submitting things. So please invest time there. I wouldn't go so far > to say it makes release managers happy, but less grumpy at times for > sure ;-) snapper seems to use the same mechanism. The approach looks even more silly there: https://build.suse.de/package/rdiff/Devel:YaST:Head/snapper?opackage=snappe… cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 4

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

06 Feb '17

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-add-on: - Handling in URLs (282 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (46 days) https://github.com/yast/yast-bootloader/pull/393 Pending requests in repository yast-control-center-gnome: - remove useless changlog, (47 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (195 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-network: - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (31 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (89 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - Do not allow changing the plugin services (bsc#1021117) (6 days) https://github.com/yast/yast-packager/pull/225 - Added yast2-sw_single-wrapper to handle rpms in Plasma (117 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (124 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (167 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (131 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - Fixed failure when trying to save a plugin service (bsc#1021117) (6 days) https://github.com/yast/yast-pkg-bindings/pull/64 - [WIP] Build ruby-lint definitions (221 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (164 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (123 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (249 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-storage: - Add option to disable swap creation (95 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (95 days) https://github.com/yast/yast-storage/pull/155 ERROR: API query limit exceeded -- 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] Fwd: YaST2 icons
by opensuse.lietuviu.kalba 04 Feb '17

04 Feb '17

2017.02.04 09:29, nicholas rašė: > yast is awesome, but does nobody else fell like they have been transported > back to the 1990's when they open yast? on plasma the icons look 'out of > place'. Is creating a modern looking (flat) icon set part of the road map? Selecting of icon's theme is personal taste (personally I prefer Oxygen over Breeze even Plasma 5). But I agree, that icons should be consistent with desktop across software. Luckily, Oxygen icons still packaged in yast2-branding-openSUSE (and I don't see no missing icons with this theme), but it requires to be manually activated by > cd /usr/share/YaST2/theme/current/ > su -c "rm icons; ln -s '../../../icons/oxygen' icons" I don't know, why openSUSE decided to stop automatically provide Oxygen icons at least with KDE Plasma desktop. Related bugs: https://bugzilla.opensuse.org/show_bug.cgi?id=955893 https://bugzilla.suse.com/show_bug.cgi?id=942136 -- Regards -- 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 30
by Ancor Gonzalez Sosa 03 Feb '17

03 Feb '17

New year, new Scrum sprint. Check the highlights at https://lizards.opensuse.org/?p=12263 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

2 1

[yast-devel] Versioning the SLE-12-SP2-CASP branch
by Ancor Gonzalez Sosa 03 Feb '17

03 Feb '17

Josef and me are discussing how to version stuff in CASP vs SP2 when both branches are getting different subset of changes. Always taking into account that, when CaaSP is released, the SP2 branch should contain all the changes and the CASP branch should die. Let's take an example (disclaimer, you will probably need to open this mail in three windows to follow the reasoning and see the differences): Jan 1st, both SP2 and CASP are in sync. Feb 1st, we introduce change A only in CASP March 1st, we introduce change B only in CASP April 1st, we introduce change C in SP2 and we merge into CASP (remember we should merge into CASP EVERY change done to SP2) May 1st, we introduce change D in CASP and we consider the code in CASP is ready for entering the SP2 branch (remember the plan is to merge into SP2 as soon as it's safe). June 1st, we introduce change E in SP2 (and, of course, we merge in CASP July 1st, we introduce change F in CASP ... The approach suggested by Josef =============================== Josef, suggest to rewrite history in the CASP branch to make merging back to SP2 easier. After all, the CASP branch will die at some point and its history will not be relevant anymore. Status at Jan 1st CASP changelog says: 3.1.10 Blah SP2 changelog says: 3.1.10 Blah Status at Feb 1st CASP changelog says: 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.10 Blah Status at March 1st CASP changelog says: 3.1.10.2 Change B 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.10 Blah Status at April 1st (after the merge) CASP changelog says: 3.1.11.1 CASP changes (A and B) 3.1.11 Change C 3.1.10 Blah SP2 changelog says: 3.1.11 Change C 3.1.10 Blah Status at May 1st (after the merge) CASP changelog says: 3.1.12 Change D 3.1.11.1 CASP changes (A and B) 3.1.11 Change C 3.1.10 Blah SP2 changelog says: 3.1.12 Change D 3.1.11.1 CASP changes (A and B) 3.1.11 Change C 3.1.10 Blah Status at June 1st (after the merge) CASP changelog says: 3.1.13 Change E 3.1.12 Change D 3.1.11.1 CASP changes (A and B) 3.1.11 Change C 3.1.10 Blah SP2 changelog says: 3.1.13 Change E 3.1.12 Change D 3.1.11.1 CASP changes (A and B) 3.1.11 Change C 3.1.10 Blah Status at July 1st CASP changelog says: 3.1.13.1 Change F 3.1.13 Change E 3.1.12 Change D 3.1.11.1 CASP changes (A and B) 3.1.11 Change C 3.1.10 Blah SP2 changelog says: 3.1.13 Change E 3.1.12 Change D 3.1.11.1 CASP changes (A and B) 3.1.11 Change C 3.1.10 Blah The approach suggested by me ============================ The approach above constantly rewrites the CASP branch changelog to make the impression that CASP and SP2 has always evolved hand by hand. I believe the risk to create confusion (or to make-up history too much and loose information) is bigger than the gain. I propose this: Status at Jan 1st CASP changelog says: 3.1.10 Blah SP2 changelog says: 3.1.10 Blah Status at Feb 1st CASP changelog says: 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.10 Blah Status at March 1st CASP changelog says: 3.1.10.2 Change B 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.10 Blah Status at April 1st (after the merge) CASP changelog says: 3.1.11.1 Change C 3.1.10.2 Change B 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.11 Change C 3.1.10 Blah Status at May 1st (after the merge) CASP changelog says: 3.1.12 Change D 3.1.11.1 Change C 3.1.10.2 Change B 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.12 Changes A, B and D 3.1.11 Change C 3.1.10 Blah Status at June 1st (after the merge) CASP changelog says: 3.1.13 Change E 3.1.12 Change D 3.1.11.1 Change C 3.1.10.2 Change B 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.13 Change E 3.1.12 Changes A, B and D 3.1.11 Change C 3.1.10 Blah Status at July 1st CASP changelog says: 3.1.13.1 Change F 3.1.13 Change E 3.1.12 Change D 3.1.11.1 Change C 3.1.10.2 Change B 3.1.10.1 Change A 3.1.10 Blah SP2 changelog says: 3.1.13 Change E 3.1.12 Changes A, B and D 3.1.11 Change C 3.1.10 Blah What others think? -- 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

3 2

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

03 Feb '17

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-add-on: - Handling in URLs (279 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (43 days) https://github.com/yast/yast-bootloader/pull/393 - [no merge] try codecov reports (198 days) https://github.com/yast/yast-bootloader/pull/355 Pending requests in repository yast-control-center-gnome: - remove useless changlog, (44 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (192 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-network: - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (28 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (86 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - Added yast2-sw_single-wrapper to handle rpms in Plasma (114 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (121 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (164 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (128 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Build ruby-lint definitions (218 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (161 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (120 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (246 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-sound: - [WIP] (L3) SP4 soundcard DB update (196 days) https://github.com/yast/yast-sound/pull/19 Pending requests in repository yast-storage: - Add option to disable swap creation (92 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (92 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Disable buttons cwm (16 days) https://github.com/yast/yast-yast2/pull/531 - Do a full type detection when creating cache (27 days) https://github.com/yast/yast-yast2/pull/527 - Add to fstab parser only optional ending line otherwise it can cause (71 days) https://github.com/yast/yast-yast2/pull/509 - [WIP] Build ruby-lint definitions (217 days) https://github.com/yast/yast-yast2/pull/480 ERROR: API query limit exceeded -- 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] YaST Google Summer of Code projects
by Ancor Gonzalez Sosa 02 Feb '17

02 Feb '17

In only a couple of weeks the application period for organizations to Google Summer of Code will be closed. Do we plan to offer some YaST project? First of all, we could resurrect/re-offer these two if the mentors are still interested https://github.com/openSUSE/mentoring/issues/12 https://github.com/openSUSE/mentoring/issues/11 What do you think about those two? Moreover, I'm thinking about creating a new one to re-write the YaST keyboard management in a proper object oriented way. The current code is a mess, the adaptation to systemd was painful and is still not perfect and we usually get bug reports from users that confuse system-wide settings with desktop specific ones (usability problem). On the other hand, writing it from scratch should be rather easy. Is not that difficult and is not that big. Even doing everything in the proper way (implementing systemd just as one possible backend so we are ready for the next big change), it should perfectly fit into a GSoC project. What do you think this one? 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 1

[yast-devel] Solving Simplecov and Coveralls issues at Travis
by Ladislav Slezak 02 Feb '17

02 Feb '17

Hello, If you get "Unable to activate coveralls-0.8.19, because simplecov-0.13.0 conflicts with simplecov (~> 0.12.0)" error at Travis then remove the "simplecov" gem installation from the ".travis.yml" file. (See example [1].) The correct "simplecov" version will be automatically installed as a coveralls dependency. JFYI: This error can happen only in the old SP2/CASP branches, `master` already uses Docker and the packages are installed as RPMs (where the dependencies are checked before installing the gems). [1] https://github.com/yast/yast-packager/pull/227/commits/bd4e1a2693972645d591… -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- 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 Hack Week ideas
by Ancor Gonzalez Sosa 02 Feb '17

02 Feb '17

I created three Hack Week projects related to YaST. I'm still not sure in which one I will work, but I thought it was worth sharing here: yast2-storage-ng as a libstorage-ng wrapper. POC https://hackweek.suse.com/15/projects/1854 Use linear programming for the partitioning proposal https://hackweek.suse.com/15/projects/1864 yast2-journal as the new default YaST log viewer https://hackweek.suse.com/15/projects/1882 In fact, the third one is not "hackweekish" enough for us. Is something we should find time to do during our daily business. But still I will leave it there for people wanting to get started with YaST (and just in case I have a spare day at the end of the week). 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

2 1

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

02 Feb '17

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-add-on: - Handling in URLs (278 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (42 days) https://github.com/yast/yast-bootloader/pull/393 - [no merge] try codecov reports (197 days) https://github.com/yast/yast-bootloader/pull/355 Pending requests in repository yast-control-center-gnome: - remove useless changlog, (43 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (191 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-network: - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (27 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (85 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - Added yast2-sw_single-wrapper to handle rpms in Plasma (113 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (120 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (163 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (127 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Build ruby-lint definitions (217 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (160 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (119 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (245 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-sound: - [WIP] (L3) SP4 soundcard DB update (195 days) https://github.com/yast/yast-sound/pull/19 Pending requests in repository yast-storage: - Add option to disable swap creation (91 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (91 days) https://github.com/yast/yast-storage/pull/155 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0