Hello community,
here is the log from the commit of package yast2-installation for
openSUSE:Leap:15.2 checked in at 2020-04-22 14:13:12
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Leap:15.2/yast2-installation (Old)
and /work/SRC/openSUSE:Leap:15.2/.yast2-installation.new.2738 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-installation"
Wed Apr 22 14:13:12 2020 rev:165 rq:795928 version:4.2.41
Changes:
--------
--- /work/SRC/openSUSE:Leap:15.2/yast2-installation/yast2-installation.changes
2020-03-26 05:40:59.475266726 +0100
+++
/work/SRC/openSUSE:Leap:15.2/.yast2-installation.new.2738/yast2-installation.changes
2020-04-22 14:13:12.686530692 +0200
@@ -1,0 +2,7 @@
+Mon Apr 20 12:10:19 UTC 2020 - Knut Anderssen <[email protected]>
+
+- Force the use of en_US.UTF-8 when running firstboot or the
+ AutoYaST Second Stage with 'POSIX' or 'C as RC_LANG (bsc#1169017)
+- 4.2.41
+
+-------------------------------------------------------------------
Old:
----
yast2-installation-4.2.40.tar.bz2
New:
----
yast2-installation-4.2.41.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-installation.spec ++++++
--- /var/tmp/diff_new_pack.a3Rcrw/_old 2020-04-22 14:13:13.070531467 +0200
+++ /var/tmp/diff_new_pack.a3Rcrw/_new 2020-04-22 14:13:13.070531467 +0200
@@ -17,7 +17,7 @@
Name: yast2-installation
-Version: 4.2.40
+Version: 4.2.41
Release: 0
Summary: YaST2 - Installation Parts
License: GPL-2.0-only
++++++ yast2-installation-4.2.40.tar.bz2 -> yast2-installation-4.2.41.tar.bz2
++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-installation-4.2.40/CONTRIBUTING.md
new/yast2-installation-4.2.41/CONTRIBUTING.md
--- old/yast2-installation-4.2.40/CONTRIBUTING.md 2020-03-23
12:02:23.000000000 +0100
+++ new/yast2-installation-4.2.41/CONTRIBUTING.md 1970-01-01
01:00:00.000000000 +0100
@@ -1,89 +0,0 @@
-YaST Contribution Guidelines
-============================
-
-YaST is an open source project and as such it welcomes all kinds of
-contributions. If you decide to contribute, please follow these guidelines to
-ensure the process is effective and pleasant both for you and the YaST
maintainers.
-
-There are two main forms of contribution: reporting bugs and performing code
-changes.
-
-Bug Reports
------------
-
-If you find a problem, please report it either using
-[Bugzilla](https://bugzilla.suse.com/enter_bug.cgi?format=guided&product=openSUSE+Factory&component=YaST2)
-or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
-registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
-if you don't have an account yet.)
-
-When creating a bug report, please follow our [bug reporting
-guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
-
-We can't guarantee that every bug will be fixed, but we'll try.
-
-Code Changes
-------------
-
-We welcome all kinds of code contributions, from simple bug fixes to
significant
-refactorings and implementation of new features. However, before making any
-non-trivial contribution, get in touch with us first — this can prevent wasted
-effort on both sides. Also, have a look at our [development
-documentation](http://en.opensuse.org/openSUSE:YaST_development).
-
-To send us your code change, use GitHub pull requests. The workflow is as
-follows:
-
- 1. Fork the project.
-
- 2. Create a topic branch based on `master`.
-
- 3. Implement your change, including tests (if possible). Make sure you adhere
- to the [Ruby style
- guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
-
- 4. Update the package version (in `packages/*.spec`, usually by
- `rake version:bump`) and add a new entry to the `package/*.changes` file
- (by `osc vc package`).
- For bigger changes or changes which need longer discussion it is advised
to
- add this as a separate last commit so it can be easily updated when
another
- change is merged in the meantime.
-
- 5. Make sure your change didn't break anything by building the RPM package
- (`rake osc:build`). The build process includes running the full testsuite.
-
- 6. Publish the branch and create a pull request.
-
- 7. YaST developers will review your change and possibly point out issues.
- Adapt the code under their guidance until they are all resolved.
-
- 8. Finally, the pull request will get merged or rejected.
-
-See also [GitHub's guide on
-contributing](https://help.github.com/articles/fork-a-repo).
-
-If you want to do multiple unrelated changes, use separate branches and pull
-requests.
-
-### Commits
-
-Each commit in the pull request should do only one thing, which is clearly
-described by its commit message. Especially avoid mixing formatting changes and
-functional changes into one commit. When writing commit messages, adhere to
-[widely used
-conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
-
-If your commit is related to a bug in Bugzilla or an issue on GitHub, make sure
-you mention it in the commit message for cross-reference. Use format like
-bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
-autolinking](https://help.github.com/articles/github-flavored-markdown#references)
-and [openSUSE abbreviation
-reference](http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_abbreviations).
-
-Additional Information
-----------------------
-
-If you have any question, feel free to ask at the [development mailing
-list](http://lists.opensuse.org/yast-devel/) or at the
-[#yast](http://webchat.freenode.net/?channels=%23yast) IRC channel on freenode.
-We'll do our best to provide a timely and accurate answer.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-4.2.40/package/yast2-installation.changes
new/yast2-installation-4.2.41/package/yast2-installation.changes
--- old/yast2-installation-4.2.40/package/yast2-installation.changes
2020-03-23 12:02:23.000000000 +0100
+++ new/yast2-installation-4.2.41/package/yast2-installation.changes
2020-04-20 14:21:30.000000000 +0200
@@ -1,4 +1,11 @@
-------------------------------------------------------------------
+Mon Apr 20 12:10:19 UTC 2020 - Knut Anderssen <[email protected]>
+
+- Force the use of en_US.UTF-8 when running firstboot or the
+ AutoYaST Second Stage with 'POSIX' or 'C as RC_LANG (bsc#1169017)
+- 4.2.41
+
+-------------------------------------------------------------------
Fri Mar 20 14:04:48 UTC 2020 - Imobach Gonzalez Sosa <[email protected]>
- In the proposal runner, restore the scroll only when it was
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-4.2.40/package/yast2-installation.spec
new/yast2-installation-4.2.41/package/yast2-installation.spec
--- old/yast2-installation-4.2.40/package/yast2-installation.spec
2020-03-23 12:02:23.000000000 +0100
+++ new/yast2-installation-4.2.41/package/yast2-installation.spec
2020-04-20 14:21:30.000000000 +0200
@@ -16,7 +16,7 @@
#
Name: yast2-installation
-Version: 4.2.40
+Version: 4.2.41
Release: 0
Group: System/YaST
License: GPL-2.0-only
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-installation-4.2.40/startup/common/language.sh
new/yast2-installation-4.2.41/startup/common/language.sh
--- old/yast2-installation-4.2.40/startup/common/language.sh 2020-03-23
12:02:23.000000000 +0100
+++ new/yast2-installation-4.2.41/startup/common/language.sh 2020-04-20
14:21:30.000000000 +0200
@@ -73,8 +73,13 @@
export RC_LANG=en_US
fi
- # get rid of encoding and/or modifier
- export LANG=${RC_LANG%%[.@]*}.UTF-8
+ if [ "$RC_LANG" == "POSIX" ] || [ "$RC_LANG" == "C" ] ; then
+ log "\tRC_LANG is ${RC_LANG}, using LANG en_US.UTF-8 as
default..."
+ export LANG=en_US.UTF-8
+ else
+ # get rid of encoding and/or modifier
+ export LANG=${RC_LANG%%[.@]*}.UTF-8
+ fi
}
#----[ start_unicode ]-----#
