Home Home > 2010 > 02 > 20 > openSUSE Weekly News, Issue 111 is out!
Sign up | Login

openSUSE Weekly News, Issue 111 is out!

February 20th, 2010 by

news Issue #111 of openSUSE Weekly News is now out!

  • openSUSE News: Number Two Always Tries Harder: openSUSE Milestone 2
  • Linux User & Developer/Kunal Deo: Another ten essential Python tips
  • Gabriel Burt: Banshee Community Extensions
  • How to Make sure I didn’t get a Virus?
  • Jason McDonald: Qt 4.6.2 Released

For a list of available translations see this page:

http://en.opensuse.org/OpenSUSE_Weekly_News/111/Translations.

Both comments and pings are currently closed.

One Response to “openSUSE Weekly News, Issue 111 is out!”

  1. CS

    With respect to the Security Notices/Vulnerabilities listed in Weekly News it is not quite clear how they are installed.
    The inference is that any openSUSE versions will auto update via Yast or Update Applet for both i32 and X64 and PCC.
    Its great if everyone just lets normal updates take their course however
    if anyone attempts to manually install an RPM file, they need to know exactly what they are doing.
    Can we have some CLEAR indications on these GREY areas of applying security updates.
    How we get notified they are available and how to apply them.
    For the open versions we dont need to do anything much unusual.
    Many of us get emails from Novell on security updates and ‘Service Packs’ and thease create huge confusion.
    Together with URL’s on security updates in Weekly News that take ANY user directly to .RPM downloads without qualification.
    There is a lot of confusion on exactly what a user of an OPEN version needs to do and an Enterprise user should do
    Can we ALL have Very Clear Procedures and Clear Understanding of what an OPEN user should do in contrast with Enterprise.
    We also need to clarify what, if anything, we need to do with emails from Novell Containing Security Update Notifications.
    Can we please have accurate, published procedures without delay! Inferring OPEN user need do little is NOT sufficient!
    TA