Hello community,
here is the log from the commit of package release-notes-openSUSE for
openSUSE:Factory checked in at 2014-10-14 13:25:05
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/release-notes-openSUSE (Old)
and /work/SRC/openSUSE:Factory/.release-notes-openSUSE.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "release-notes-openSUSE"
Changes:
--------
---
/work/SRC/openSUSE:Factory/release-notes-openSUSE/release-notes-openSUSE.changes
2014-08-05 21:11:25.000000000 +0200
+++
/work/SRC/openSUSE:Factory/.release-notes-openSUSE.new/release-notes-openSUSE.changes
2014-10-14 13:25:25.000000000 +0200
@@ -1,0 +2,6 @@
+Mon Oct 13 15:45:34 UTC 2014 - [email protected]
+
+- 13.2.20141013:
+* Resolve some 13.1 check-it markers.
+
+-------------------------------------------------------------------
Old:
----
release-notes-openSUSE-13.2.20140805.tar.bz2
New:
----
release-notes-openSUSE-13.2.20141013.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ release-notes-openSUSE.spec ++++++
--- /var/tmp/diff_new_pack.X5yfo0/_old 2014-10-14 13:25:26.000000000 +0200
+++ /var/tmp/diff_new_pack.X5yfo0/_new 2014-10-14 13:25:26.000000000 +0200
@@ -17,7 +17,7 @@
Name: release-notes-openSUSE
-Version: 13.2.20140805
+Version: 13.2.20141013
Release: 0
Summary: Release Notes for openSUSE
License: GFDL-1.3
++++++ release-notes-openSUSE-13.2.20140805.tar.bz2 ->
release-notes-openSUSE-13.2.20141013.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/release-notes-openSUSE-13.2.20140805/NEWS
new/release-notes-openSUSE-13.2.20141013/NEWS
--- old/release-notes-openSUSE-13.2.20140805/NEWS 2014-08-05
12:35:40.000000000 +0200
+++ new/release-notes-openSUSE-13.2.20141013/NEWS 2014-10-13
17:48:06.000000000 +0200
@@ -1,3 +1,6 @@
+13.2.20141013:
+* Resolve some 13.1 check-it markers.
+
13.2.1
* Use the openSUSE Stylesheets
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/release-notes-openSUSE-13.2.20140805/xml/release-notes.xml
new/release-notes-openSUSE-13.2.20141013/xml/release-notes.xml
--- old/release-notes-openSUSE-13.2.20140805/xml/release-notes.xml
2014-08-05 12:35:40.000000000 +0200
+++ new/release-notes-openSUSE-13.2.20141013/xml/release-notes.xml
2014-10-13 17:48:06.000000000 +0200
@@ -159,9 +159,8 @@
<section id="sec.123.uefi">
<title>UEFI—Unified Extensible Firmware Interface</title>
- <para>CHECKIT:13.1</para>
<para> Prior to installing openSUSE on a system that boots using UEFI
(Unified Extensible
- Firmware Interface) you are urgently advised to check for any firmware
updates the hardware
+ Firmware Interface), you are urgently advised to check for any firmware
updates the hardware
vendor recommends and, if available, to install such an update. A
pre-installed Windows 8 is a
strong indication that your system boots using UEFI. </para>
@@ -171,7 +170,7 @@
openSUSE minimizes the risk by not writing more than the bare minimum
required to boot the OS.
The minimum means telling the UEFI firmware about the location of the
openSUSE boot loader.
Upstream Linux Kernel features that use the UEFI storage area for storing
boot and crash
- information (<literal>pstore</literal>) have been disabled by default.
Nevertheless it is
+ information (<literal>pstore</literal>) have been disabled by default.
Nevertheless, it is
recommended to install any firmware updates the hardware vendor
recommends. </para>
</section>
@@ -179,12 +178,11 @@
<section id="sec.123.uefi-part">
<!-- bnc#850056 -->
<title>UEFI, GPT, and MS-DOS Partitions</title>
- <para>CHECKIT:13.1</para>
- <para> Together with the EFI/UEFI specification a new style of partitioning
arrived: GPT (GUID
+ <para> Together with the EFI/UEFI specification, a new style of
partitioning arrived: GPT (GUID
Partition Table). This new schema uses globally unique identifiers
(128-bit values displayed in
32 hexadecimal digits) to identify devices and partition types. </para>
<para> Additionally, the UEFI specification also allows legacy MBR (MS-DOS)
partitions. The Linux
- boot loaders (ELILO or GRUB2) try to generate automatically a GUID for
those legacy partitions,
+ boot loaders (ELILO or GRUB2) try to automatically generate a GUID for
those legacy partitions,
and write them to the firmware. Such a GUID can change frequently, causing
a rewrite in the
firmware. A rewrite consist of two different operation: removing the old
entry and creating a
new entry that replaces the first one. </para>
@@ -198,11 +196,10 @@
<section id="sec.131.secboot">
<!-- bnc#850052 -->
<title>Booting When in Secure Boot Mode</title>
- <para>CHECKIT:13.1</para>
<para> This only affects machines in UEFI mode with secure boot enabled.
</para>
<para> The new version of the shim loader allows more machines to boot with
Secure Boot enabled
- than with openSUSE 12.3. Nevertheless, in case of trouble, first update
the BIOS of your machine
- to the latest version. If the BIOS update does not help, report the model
of your machine it the
+ than with openSUSE 13.1. Nevertheless, in case of trouble, first update
the BIOS of your machine
+ to the latest version. If the BIOS update does not help, report the model
of your machine to the
wiki (http://en.opensuse.org/openSUSE:UEFI). Then we can track it for the
next release. </para>
</section>
@@ -217,49 +214,10 @@
<section id="technical">
<title>Technical</title>
- <!-- FIXME -->
- <!-- bnc#595569, 621469, 673964, 781700 -->
- <section id="sec.114.kms">
- <title>Initializing Graphics with KMS (Kernel Mode Setting)</title>
- <para>CHECKIT:13.1</para>
- <!-- 13.2: to be removed from the release notes:
- https://bugzilla.novell.com/show_bug.cgi?id=849188
- -->
- <para> With openSUSE 11.3 we switched to KMS (Kernel Mode Setting) for
Intel, ATI and NVIDIA
- graphics, which now is our default. If you encounter problems with the KMS
driver support
- (intel, radeon, nouveau), disable KMS by adding
<literal>nomodeset</literal> to the kernel boot
- command line. To set this permanently using Grub 2, the default boot
loader, add it to the
- <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> kernel default load options
line in your
- <filename>/etc/default/grub</filename> text file as root and running the
terminal command </para>
- <screen>sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg</screen>
- <para> for the changes to take effect. Else, for Grub Legacy, add it to the
kernel command line
- in <filename>/boot/grub/menu.lst</filename>, also done as root. This
option makes sure the
- appropriate kernel module (intel, radeon, nouveau) is loaded with
<literal>modeset=0</literal>
- in <filename>initrd</filename>, i.e. KMS is disabled. </para>
-
- <para> In the rare cases when loading the DRM module from
<filename>initrd</filename> is a
- general problem and unrelated to KMS, it is even possible to disable
loading of the DRM module
- in <filename>initrd</filename> completely. For this set the
<literal>NO_KMS_IN_INITRD</literal>
- sysconfig variable to <literal>yes</literal> via YaST, which then recreates
- <filename>initrd</filename> afterwards. Reboot your machine.</para>
-
- <para> On Intel without KMS the Xserver falls back to the
<literal>fbdev</literal> driver (the
- <literal>intel</literal> driver only supports KMS); alternatively, for
legacy GPUs from Intel
- the "intellegacy" driver
(<systemitem>xorg-x11-driver-video-intel-legacy</systemitem> package)
- is available, which still supports UMS (User Mode Setting). To use it, edit
- <filename>/etc/X11/xorg.conf.d/50-device.conf</filename> and change the
driver entry to
- <literal>intellegacy</literal>.</para>
-
- <para> On ATI for current GPUs it falls back to
<literal>radeonhd</literal>. On NVIDIA without
- KMS the <literal>nv</literal> driver is used (the
<literal>nouveau</literal> driver supports
- only KMS). Note, newer ATI and NVIDIA GPUs are falling back to
<literal>fbdev</literal>, if you
- specify the <literal>nomodeset</literal> kernel boot parameter.</para>
- </section>
<section id="sec.131.nouveau-inst">
<!-- bnc#850053 -->
<title>Garbage on the Screen During Installation with the Nouveau
Driver</title>
- <para>CHECKIT:13.1</para>
<para> On some systems with NVIDIA cards, the installer may show garbage on
the top part of the
screen due to problems with the default nouveau driver. If you are
affected by this problem, you
can disable the nouveau kernel module to run the installer and then enable
it again once the
@@ -273,18 +231,20 @@
</section>
+ <!--
<section>
- <!-- via mail: ddiss -->
+ <!-\- via mail: ddiss -\->
<title>Samba Version 4.1</title>
<para>CHECKIT:13.1</para>
- <para> Samba version 4.1 shipped with openSUSE 13.1 does not include
support to operate as an
+ <para> Samba version 4.1 shipped with openSUSE 13.1 does not include
support for operating as an
Active Directory style domain controller. This functionality is currently
disabled, as it lacks
integration with system-wide MIT Kerberos. </para>
</section>
+ -->
-
+ <!--
<section id="sec.131.kdeandbt">
- <!-- bnc#848969 -->
+ <!-\- bnc#848969 -\->
<title>KDE and Bluetooth</title>
<para>CHECKIT:13.1</para>
<para> The Bluetooth stack is provided by Bluez 5 (a major,
backwards-incompatbile version), a
@@ -292,28 +252,27 @@
the KDE workspace only supports Bluez version 4 in its currently-released
versions. </para>
<para> Therefore, the openSUSE KDE community team offers an unofficial
Bluedevil package
providing at least basic functionality such as device pairing or support
for bluetooth mice;
- Some other features are known not to work jet, like file transfer. </para>
- <para> For the moment, bugs should not be filed against Bluetooth support
in KDE as the Bluez 5
+ Some other features are known not to work yet, like file transfer. </para>
+ <para> For the time being, bugs should not be filed against Bluetooth
support in KDE, as the Bluez 5
port of Bluedevil is still ongoing. </para>
</section>
+ -->
<section id="sec.131.apparmor">
<!-- bnc#850058 -->
<title>AppArmor and Permission Settings</title>
- <para>CHECKIT:13.1</para>
<para> AppArmor is enabled by default. This means more security, but might
prevent services from
- working, if you run them in unexpected ways. If you encounter strange
permission problems, try
+ working if you run them in unexpected ways. If you encounter strange
permission problems, try
to switch the AppArmor profile for the affected service to complain mode
with: </para>
<screen>aa-complain /usr/bin/$your_service</screen>
<para> Complain mode means: allow everything, and log things that the
profile would not allow. </para>
- <para> Even if it helps report it as a bug! We want to fix AppArmor
profiles to cover also corner
+ <para> Even if it helps, report it as a bug! We want to fix AppArmor
profiles to also cover corner
cases. </para>
</section>
<section id="sec.131.skype">
<!-- bnc#850057 -->
<title>Skype</title>
- <para>CHECKIT:13.1</para>
<para> PulseAudio 4.0 exposes a bug in the current version of Skype for
Linux (v4.2). Until Skype
is fixed and updated, run <command>skype</command> from the command line:
</para>
<screen>PULSE_LATENCY_MSEC=60 skype</screen>
@@ -321,17 +280,19 @@
url="http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/"/>. </para>
</section>
+ <!--
<section id="sec.131.autoyast">
- <!-- bnc#851588 -->
+ <!-\- bnc#851588 -\->
<title>AutoYaST</title>
<para>CHECKIT:13.1</para>
- <para> If the autoyast profile contains entries in an
<literal><add-on></literal> section
+ <para> If the autoyast profile contains entries in an
<literal><add-on></literal> section,
there is a bug triggered that prevents information in the profile from
being transferred from
- the first stage into the second stage. Therefore, in this case all second
stage configuration
+ the first stage into the second stage, in which case, all second stage
configuration
steps are skipped, which normally leads to more or less completely
unusable installations. </para>
- <para> As a temporary workaround, avoid using
<literal><add-on></literal> sections in
+ <para> As a temporary workaround, avoid using
<literal><add-on></literal> sections in
profiles with AutoYaST in openSUSE 13.1. </para>
</section>
+ -->
</section>
<!-- START-FATE-RN -->
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
