From root@hilbert.suse.de Tue Oct 14 11:27:26 2014 From: root@hilbert.suse.de To: commit@lists.opensuse.org Subject: commit release-notes-openSUSE for openSUSE:Factory Date: Tue, 14 Oct 2014 13:25:26 +0200 Message-ID: <20141014112526.B5EF0AE059@hilbert.suse.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1670701173966793724==" --===============1670701173966793724== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello community, here is the log from the commit of package release-notes-openSUSE for openSUS= E: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-open= SUSE.changes 2014-10-14 13:25:25.000000000 +0200 @@ -1,0 +2,6 @@ +Mon Oct 13 15:45:34 UTC 2014 - ke(a)suse.de + +- 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 @@ =20 =20 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=3DCVS' '--exclude=3D.cvsignore' '--exclude=3D.svn' '--ex= clude=3D.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.0000000= 00 +0200 +++ new/release-notes-openSUSE-13.2.20141013/NEWS 2014-10-13 17:48:06.0000000= 00 +0200 @@ -1,3 +1,6 @@ +13.2.20141013: +* Resolve some 13.1 check-it markers. + 13.2.1 * Use the openSUSE Stylesheets =20 diff -urN '--exclude=3DCVS' '--exclude=3D.cvsignore' '--exclude=3D.svn' '--ex= clude=3D.svnignore' old/release-notes-openSUSE-13.2.20140805/xml/release-note= s.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 @@ =20
UEFI—Unified Extensible Firmware Interface - CHECKIT:13.1 Prior to installing openSUSE on a system that boots using UEFI (Un= ified Extensible - Firmware Interface) you are urgently advised to check for any firmware u= pdates 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-in= stalled Windows 8 is a strong indication that your system boots using UEFI. =20 @@ -171,7 +170,7 @@ openSUSE minimizes the risk by not writing more than the bare minimum re= quired to boot the OS. The minimum means telling the UEFI firmware about the location of the op= enSUSE boot loader. Upstream Linux Kernel features that use the UEFI storage area for storin= g boot and crash - information (pstore) have been disabled by default. N= evertheless it is + information (pstore) have been disabled by default. N= evertheless, it is recommended to install any firmware updates the hardware vendor recommen= ds.
=20 @@ -179,12 +178,11 @@
UEFI, GPT, and MS-DOS Partitions - CHECKIT:13.1 - Together with the EFI/UEFI specification a new style of partitioni= ng arrived: GPT (GUID + Together with the EFI/UEFI specification, a new style of partition= ing 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. Additionally, the UEFI specification also allows legacy MBR (MS-DO= S) partitions. The Linux - boot loaders (ELILO or GRUB2) try to generate automatically a GUID for t= hose legacy partitions, + boot loaders (ELILO or GRUB2) try to automatically generate a GUID for t= hose legacy partitions, and write them to the firmware. Such a GUID can change frequently, causi= ng 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. @@ -198,11 +196,10 @@
Booting When in Secure Boot Mode - CHECKIT:13.1 This only affects machines in UEFI mode with secure boot enabled. = The new version of the shim loader allows more machines to boot wi= th 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 mode= l 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 mode= l of your machine to the wiki (http://en.opensuse.org/openSUSE:UEFI). Then we can track it for th= e next release.
=20 @@ -217,49 +214,10 @@ =20
Technical - - -
- Initializing Graphics with KMS (Kernel Mode Setting) - CHECKIT:13.1 - - With openSUSE 11.3 we switched to KMS (Kernel Mode Setting) for In= tel, ATI and NVIDIA - graphics, which now is our default. If you encounter problems with the K= MS driver support - (intel, radeon, nouveau), disable KMS by adding nomodeset to the kernel boot - command line. To set this permanently using Grub 2, the default boot loa= der, add it to the - GRUB_CMDLINE_LINUX_DEFAULT kernel default load optio= ns line in your - /etc/default/grub text file as root and running th= e terminal command - sudo /usr/sbin/grub2-mkconfig --output=3D/boot/grub2/grub.cfg - for the changes to take effect. Else, for Grub Legacy, add it to t= he kernel command line - in /boot/grub/menu.lst, also done as root. This opt= ion makes sure the - appropriate kernel module (intel, radeon, nouveau) is loaded with modeset=3D0 - in initrd, i.e. KMS is disabled. - - In the rare cases when loading the DRM module from initr= d is a - general problem and unrelated to KMS, it is even possible to disable loa= ding of the DRM module - in initrd completely. For this set the NO_= KMS_IN_INITRD - sysconfig variable to yes via YaST, which then recrea= tes - initrd afterwards. Reboot your machine. - - On Intel without KMS the Xserver falls back to the fbdev<= /literal> driver (the - intel driver only supports KMS); alternatively, for = legacy GPUs from Intel - the "intellegacy" driver (xorg-x11-driver-video-intel-legacy= package) - is available, which still supports UMS (User Mode Setting). To use it, e= dit - /etc/X11/xorg.conf.d/50-device.conf and change the= driver entry to - intellegacy. - - On ATI for current GPUs it falls back to radeonhd. On NVIDIA without - KMS the nv driver is used (the nouveau driver supports - only KMS). Note, newer ATI and NVIDIA GPUs are falling back to = fbdev, if you - specify the nomodeset kernel boot parameter. -
=20
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 affec= ted by this problem, you can disable the nouveau kernel module to run the installer and then enab= le it again once the @@ -273,18 +231,20 @@ </section> =20 =20 + <!-- <section> - <!-- via mail: ddiss --> + <!-\- via mail: ddiss -\-> <title>Samba Version 4.1 CHECKIT:13.1 - Samba version 4.1 shipped with openSUSE 13.1 does not include supp= ort to operate as an + Samba version 4.1 shipped with openSUSE 13.1 does not include supp= ort for operating as an Active Directory style domain controller. This functionality is currentl= y disabled, as it lacks integration with system-wide MIT Kerberos.
+ --> =20 - + + KDE and Bluetooth CHECKIT:13.1 The Bluetooth stack is provided by Bluez 5 (a major, backwards-inc= ompatbile version), a @@ -292,28 +252,27 @@ the KDE workspace only supports Bluez version 4 in its currently-release= d versions. Therefore, the openSUSE KDE community team offers an unofficial Bl= uedevil 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. - 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. + For the time being, bugs should not be filed against Bluetooth sup= port in KDE, as the Bluez 5 port of Bluedevil is still ongoing.
+ --> =20
AppArmor and Permission Settings - CHECKIT:13.1 AppArmor is enabled by default. This means more security, but migh= t prevent services from - working, if you run them in unexpected ways. If you encounter strange pe= rmission problems, try + working if you run them in unexpected ways. If you encounter strange per= mission problems, try to switch the AppArmor profile for the affected service to complain mode= with: aa-complain /usr/bin/$your_service Complain mode means: allow everything, and log things that the pro= file would not allow. - Even if it helps report it as a bug! We want to fix AppArmor profi= les to cover also corner + Even if it helps, report it as a bug! We want to fix AppArmor prof= iles to also cover corner cases.
=20
Skype - CHECKIT:13.1 PulseAudio 4.0 exposes a bug in the current version of Skype for L= inux (v4.2). Until Skype is fixed and updated, run skype from the command line= : PULSE_LATENCY_MSEC=3D60 skype @@ -321,17 +280,19 @@ url=3D"http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/"/>.
=20 + + AutoYaST CHECKIT:13.1 - If the autoyast profile contains entries in an <add-on= > section + If the autoyast profile contains entries in an <add-on= > section, there is a bug triggered that prevents information in the profile from b= eing transferred from - the first stage into the second stage. Therefore, in this case all secon= d stage configuration + the first stage into the second stage, in which case, all second stage c= onfiguration steps are skipped, which normally leads to more or less completely unusa= ble installations. - As a temporary workaround, avoid using <add-on> sections in + As a temporary workaround, avoid using <add-on> sections in profiles with AutoYaST in openSUSE=C2=A013.1.
+ --> =20 --=20 To unsubscribe, e-mail: opensuse-commit+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-commit+help(a)opensuse.org --===============1670701173966793724==--