April 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] yast2 unusable on passwordless users
by Felix Miata 24 Apr '15

24 Apr '15

Anyone notice this? I tried to use it to adjust group memberships for individual users, but it refuses to OK out of any tab because "password" is unacceptable. Root must edit /etc/group to effect any such changes. -- "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 2

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

24 Apr '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (15 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-kdump: - Fix SSH / SFTP confusion (6 days) https://github.com/yast/yast-kdump/pull/26 Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (41 days) https://github.com/yast/yast-network/pull/284 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (35 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (28 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (199 days) https://github.com/yast/yast-docker/pull/2 -- 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] Correct solution for AutoYast: Report Unknown/Unsupported Sections
by Lukas Ocilka 23 Apr '15

23 Apr '15

Hi, I'm a little bit stuck between added-value and implementation details for the $SUBJECT bug. Long story short, we have dropped yast2-sshd package that used to implement configuration for sshd in AutoYast. Someone has tried an old AutoYast profile with <sshd/> settings and was surprised not to have sshd configured accordingly. They have asked for getting a warning / error report about it. There are several possibilities how to solve it with different level of benefit for the customer, maintenance effort in the future and cleanness of the solution. 1. Handle only sections known to be dropped Benefit: Inform about dropped support of <sshd/>, ...? Solution: Hard-coded list of dropped sections Effort: Low Maintenance: List of dropped modules Disadvantage: Doesn't report unknown sections 2. Compare the profile with what the currently installed system can configure Benefit: Inform about all unknown sections and also known sections that cannot be handled because of some missing Yast packages Solution: Using the current AutoYast functionality for parsing desktop files that maps "X-SuSE-YaST-AutoInstResource" entries to the profile (Y2ModuleConfig.ModuleMap.keys - Profile.current.keys - ["globals", "language", "networking", "user_defaults" ...]) Effort: Medium Maintenance: Hard-coded list of false-positives Disadvantage: The current implementation doesn't seem to recognize some entries, such as ["globals", "language", "networking", "user_defaults" ...], for instance, "language"/"keyboard" is hard-coded in clients/inst_autosetup.rb 3. Compare the profile with currently installed schema Benefit: Handle only unknown sections Solution: Parse /usr/share/YaST2/schema/autoyast/rng/profile.rng that should already contain all known sections Effort: Hard(er) Maintenance: Either hard-coded list of false-positives or schema Disadvantage: XML parser to read and understand profile.rng, but profile us not up to date anyway, e.g., <globals/> is missing there. I like the #2 the most, but fixing Yast to correctly evaluate some entries could lead into change of the current behaviour. There is too much hard-coded information now. So, what do you think? I don't want to over-engineer a simple thing but I'd like to bring some value too. And I don't want to cause a few new bugs ;) Thx 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

6 9

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

23 Apr '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (14 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-kdump: - Fix SSH / SFTP confusion (5 days) https://github.com/yast/yast-kdump/pull/26 Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (40 days) https://github.com/yast/yast-network/pull/284 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (34 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (27 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (198 days) https://github.com/yast/yast-docker/pull/2 -- 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] Adding the apply buttons to services
by Ancor Gonzalez Sosa 22 Apr '15

22 Apr '15

I started to implement this UI for yast-dns-server and I need some veteran's feedback. https://docs.google.com/drawings/d/1cVv4FY4tWRLAnMG96Cdfvw8asTNpzhFUdKn4TEq… Looks like most similar modules are implemented using Wizard (sometimes through CWM::DialogTree), which means only 3 buttons, namely back, abort and next. For dns-server I could abuse the slot of the back button (seems it wouldn't be the first time[1]). But looking at the screenshots at https://docs.google.com/document/d/1OA77GehzFKuoJWm0weN-bCi1BjfR2VAQNWoE1OO… it looks that wouldn't be a generic solution, since I can see some "back" buttons there (most of them disabled, but still a problem). Any chance of getting my "apply" button in a generic way keeping the usage of Wizard and CWM::DialogTree? Thanks [1] https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/W… -- 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 4

[yast-devel] Added openSUSE_13.2_Update target to YaST:Head
by Ladislav Slezak 22 Apr '15

22 Apr '15

Hi all! If you use the Yast packages from YaST:Head (you should ;-)) on 13.2 you might have seen a conflict for packages using libzypp, like yast2-pkg-bindings or libyui-*-pkg packages. The problem is that there was released a libzypp update for 13.2 which contains a new *.so library. That means it is incompatible with the original package. The solution is to build YaST:Head against the openSUSE_13.2_Update repository. The question is whether we still need to build the packages for the original openSUSE_13.2 (without updates). Using the latest YaST packages on an "old" 13.2 sounds weird to me, if you want the edge YaST packages I suppose you also want the base system to be up to date. *** IMPORTANT! *** So if nobody objects I'd remove the openSUSE_13.2 target to save the OBS resources, it does not make sense to build the packages twice. I'd remove it this Friday (Apr 24) around 14:00 CEST. Do not forget to update your YaST:Head repository URL [1]! *** IMPORTANT! *** Of course, you can use the openSUSE_13.2_Update YaST packages on the original 13.2, the packages will be the same except the packages mentioned at the beginning. So we basically move the package conflict from updated 13.2 to unpatched 13.2, that should be fine I think... [1] http://download.opensuse.org/repositories/YaST:/Head/openSUSE_13.2_Update Note: it still does not work, the repo has not been published yet although the packages have been built, the OBS is somehow slow today... :-( -- 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 22 Apr '15

22 Apr '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (13 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-kdump: - Fix SSH / SFTP confusion (4 days) https://github.com/yast/yast-kdump/pull/26 Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (39 days) https://github.com/yast/yast-network/pull/284 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (33 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (26 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (197 days) https://github.com/yast/yast-docker/pull/2 -- 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 21 Apr '15

21 Apr '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (12 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (38 days) https://github.com/yast/yast-network/pull/284 Pending requests in repository yast-registration: - Refactoring (7 days) https://github.com/yast/yast-registration/pull/183 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (32 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (25 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (196 days) https://github.com/yast/yast-docker/pull/2 -- 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] FYI: yast-metapackage repo renamed to yast-metapackage-handler
by Martin Vidner 20 Apr '15

20 Apr '15

Hi, the package yast2-metapackage-handler.rpm (AKA One Click Install) has so far resided in the repository https://github.com/yast/yast-metapackage Note the irregularity between the repo name and the RPM name. It is because I was stupid when creating the repo back when Benji Weber coded the module. Now the stupidity has biten back in the form of an L3 bug: https://bugzilla.suse.com/show_bug.cgi?id=926313 where a fix that is in 13.2 already did not make it to SLE 12. The internal Jenkins is simply missing a project for this package. I have renamed the repo on GitHub to https://github.com/yast/yast-metapackage-handler which is safe™ because it will continue to be accessible under the old name. I have also renamed the job https://ci.opensuse.org/view/Yast/job/yast-metapackage-master/ to https://ci.opensuse.org/view/Yast/job/yast-metapackage-handler-master/ and added the jobs which were missing until now: http://river.suse.de/view/YaST/job/yast-metapackage-handler-master/ (enabled) http://river.suse.de/view/Yast%20for%20SLE12/job/yast-metapackage-handler-S… (disabled like all others) Sorry for the noise, let me know if anything else needs fixing related to this. -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

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

20 Apr '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-autoinstallation: - Refactor the rest of AutoinstClass (42 days) https://github.com/yast/yast-autoinstallation/pull/103 Pending requests in repository yast-control-center: - Add appdata.xml, to show up in GNOME Software (11 days) https://github.com/yast/yast-control-center/pull/12 Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (37 days) https://github.com/yast/yast-network/pull/284 - Autoyast: do not overwrite firewall settings (88 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (66 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-packager: - Register addons from media (FATE#318505) (9 days) https://github.com/yast/yast-packager/pull/121 Pending requests in repository yast-registration: - Refactoring (6 days) https://github.com/yast/yast-registration/pull/183 Pending requests in repository yast-storage: - fix for bsc#919980 (45 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (31 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (27 days) https://github.com/yast/yast-theme/pull/52 - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (234 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (96 days) https://github.com/yast/yast-yast2/pull/310 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (25 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (24 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-auth-client: - Renovate the UI (20 days) https://github.com/yast/yast-auth-client/pull/36 - Fix boolean parameters in autoyast (32 days) https://github.com/yast/yast-auth-client/pull/32 Pending requests in repository yast-docker: - Minor typo fixes - README.md (9 days) https://github.com/yast/yast-docker/pull/7 - Start making this a gem (195 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0