- openSUSE Announce

[opensuse-announce] English openSUSE wiki updated and moved home
by Christian Boltz 11 Jul '17

11 Jul '17

Dear openSUSE Community, the MediaWiki instance hosted behind en.opensuse.org has been moved from the old Provo cluster to the new Nuremberg opensuse network. Together with the move, the wiki also got an update from MediaWiki 1.22 to 1.27, and the VM hosting it from an old SLE version to openSUSE Leap 42.3 (yes, we are eating our own dogfood!) ‎ New features are: - including files directly from github -> https://en.opensuse.org/Help:GitHub_inclusion - namespace-specific boilerplates (page templates) when creating new pages -> https://en.opensuse.org/Help:MultiBoilerplate - better search (elasticsearch) - now searching all namespaces, but with different weight - login is now done using the Auth_remoteuser extension - but still with your openSUSE login - support for several map providers - switched extension for RSS feed integration (this needs adjustments on the pages that include RSS feeds) -> https://en.opensuse.org/Help:RSS_feeds - watching a category (when pages get added to or removed from it) is now part of MediaWiki core - removal of Hermes notifications - MediaWiki's own notifications work much better If you encounter any issue, please let us know by mail to admin(a)opensuse.org. We'll let the dust settle for some days, and plan to move and update the localized wikis next week. Regards, Christian Boltz -- > New Versions usually bring bug fixes and security fixes. ...and new bugs. Funny how people tend to forget about that. [> Michael Melcher and Michal Kubecek in opensuse-factory] -- To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-announce+help(a)opensuse.org

1 0

[opensuse-announce] openSUSE Leap 42.1 has reached end of SUSE support
by Benjamin Brunner 17 May '17

17 May '17

Hi all, With the release of release-notes-openSUSE on May 17th, 2017 the SUSE sponsored maintenance of openSUSE Leap 42.1 has ended. openSUSE Leap 42.1 is now officially discontinued and out of support by SUSE. The currently maintained stable release is openSUSE Leap 42.2, which will be maintained until the Q2/2018. See https://en.opensuse.org/Lifetime Upgrading is easy. See the links below for instructions: https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.star… https://en.opensuse.org/SDB:System_upgrade https://en.opensuse.org/SDB:Offline_upgrade openSUSE Leap 42.1 was released on November 4th 2015, making it ca. 18 months of security and bugfix support. It was the first hybrid distribution which used sources from SUSE Linux Enterprise and from our community developers to bridge a gap between matured packages and newer packages found in openSUSE Tumbleweed. Some statistics on the released patches (compared to 13.2): Total updates: 1442 (+98) Updates imported from SUSE Linux Enterprise: 507 Updates provided by community developers: 935 Security: 598 (-109) Recommended: 807 (+182) Optional: 36 (+24) Feature: 1 (1) Fixed CVE-entries: 2434 (-217) Fixed Bugs (overall): 3735 (-170) A huge thanks to our awesome packagers, community, and all involved people, who made the next great release possible! Your maintenance- and security-team -- Benjamin Brunner <bbrunner(a)suse.com>, SUSE MaintenanceSecurity SUSE LINUX GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-announce+help(a)opensuse.org

1 0

[opensuse-announce] UPDATE: openSUSE Services Outage
by Richard Brown 15 May '17

15 May '17

Hello all, The situation with that led to the distribution of openSUSE infrastructure the last few days has been resolved. The shutdown of openSUSE infrastructure was triggered by SUSE's Corporate policies designed to err on the side of caution in order to protect their assets and our data. We're pleased to be able to report that after an extensive review and audit of the systems involved we are confident that nothing was compromised and all of our code and personal information housed within was adequately protected throughout. Therefore all of the systems that were shut down are now back online. We apologise for the inconvenience or confusion caused. I'd also like to thank everyone for their understanding, and especially thank our admins who worked tirelessly over the weekend to investigate and restore services as quickly as possible. Regards, Richard Brown openSUSE Chairman -- To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-announce+help(a)opensuse.org

1 0

[opensuse-announce] Several openSUSE services disabled due to a security breach
by Richard Brown 12 May '17

12 May '17

Dear openSUSE Community, We have been informed of a security breach of the MF authentication system used by several openSUSE services. As a result, the openSUSE services using this authentication method are immediately being set to read-only mode/preventing authentication. This includes the openSUSE OBS, wiki, and forums. The scope and impact of the breach is not yet fully clear. The disabling of authentication is to ensure the protection of our systems and user data while the situation is fully investigated. Based on the information available at this time, there is a possibility that the breach is limited to users of non-openSUSE infrastructure that shares the same authentication system. Regardless, is recommended that all users of the affected services and openSUSE bugzilla change their password at the following link: https://secure-www.novell.com/selfreg/jsp/protected/manageAccount.jsp https://status.opensuse.org/ can be used to monitor the status of the services as the incident is further investigated. We do not believe any of the openSUSE Download infrastructure has been compromised, as it does not interact with the MF authentication system. Therefore www.opensuse.org , download.opensuse.org and software.opensuse.org remain operational and safe for all of our users to use. Thank you all for your understanding and support, and expect a further update as soon as we have more information. Regards, -- To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-announce+help(a)opensuse.org

1 0

[opensuse-announce] openSUSE Leap's Next Major Version Number
by Richard Brown 22 Apr '17

22 Apr '17

Hi all, On behalf of the openSUSE Board and Leap Release Management I am pleased to announce the next version of openSUSE Leap after 42.3 will be: openSUSE Leap 15 As with Leap 42.x, minor releases are expected annually for at least 3 years, so you can expect a Leap 15.1 to follow, then 15.2 and onwards. Obviously this is quite a dramatic change from the current version number of 42.x, so I will explain what justifies this change in some detail below. First, some history. When we started openSUSE Leap, the version number was an issue that needed addressing. openSUSE at that time was at 13.2, but SUSE Linux Enterprise (SLE) was at 12 and heading towards 12 SP1. As the main unique selling point of Leap compared to every other distribution is the fact it is based on SLE sources. We wanted to reflect that in the version number. This was particularly important when you consider that a major version in SLE really means something ("major architectural changes from the last version are introduced here") whereas minor versions/service packs have a very different message ("easy to upgrade to, no major workflow breaking changes"). Leap follows a similar philosophy, so we wanted a versioning scheme to reflect SLEs. But openSUSE had already had versions starting with 12, so we couldn't sync up with SLE. This is where 42.x came from. It gave us the opportunity to establish a relationship with SLE versions (SLE Version + 30 = Leap Version), reflect the major/minor nature of Leap releases, and avoid clashes with version numbers we'd already used. The choice of 42 doubled as a humorous nod to hitchhikers guide to the galaxy and the first version numbers of SuSE Linux and YaST (4.2 and 0.42 respectively). The plan was therefore for the next version of Leap to be 43 with it's release aligned with SLE 13, followed by Leap 43.1 (with SLE 13 SP1), Leap 43.2 (w. SP2), etc However, like all good plans, things change. SUSE have decided that their next version of SLE will be 15, not 13. Upon learning of SUSE's plans the Board and Leap release team have been considering our options. This included ignoring the changes to SLE and releasing Leap 43 as planned, at the cost of the link between SLE versions and Leap versions. 45 was also considered, as were some frankly hilarious ideas that made me worry about my own sanity and that of my fellow contributors. After considering the pros and cons of all the options however, the decision has been that Leap 15 will be our next version. SUSE's decision to skip SLE 13 and 14 gave us a perfect opportunity to sync up with SLE versions like we always wanted to originally with Leap. It's an opportunity we will not be able to take so easily a few years from now if we continued with Leaps current versioning. There are only a few packages in our distribution that reference the 42.x versioning, and they should be easily handled as part of a zypper dup, so we are not concerned about this decision impacting users upgrading. We are aware that this decision could be a minor annoyance for users of Leap with configuration management tools like saltstack and puppet, but the long term opportunity to simplify such configuration (by being able to treat SLE and Leap similarly) outweighed our desire to avoid a 'one-time' effort for people currently handling the overly complicated situation caused by Leap being at 42.x and SLE being at 12 SPx. Packagers should be able to look forward to an easier time of things as a result of this change. We intend to deprecate the 0%{leap_version} macro and simplify the current complex nest of suse_version and sle_versions that can make it very frustrating to build packages appropriately for Tumbleweed, Leap and SLE. 0%{suse_version} should continue to be available as a simple indicator of the major version of Leap & SLE for packagers (eg, 0%{suse_version} == 1500 is the expected value for SLE 15 and Leap 15 and all of their minor versions/service packs). 0%{sle_version} should remain as a more precise indicator when packagers need to handle specific versions of Leap and SLE (eg. 0%{sle_version} == 150000 is the expected value for SLE 15 & Leap 15, with 150100 being the expected value for SLE 15 SP1 & Leap 15.1) 0%{is_opensuse} will continue for those times when packagers need to distinguish between Leap and SLE even though they will now more closely share their versions. The above examples and what the future suse_version number will be for Tumbleweed is not yet final, so expect to see emails from ludwig in opensuse-factory(a)opensuse.org when they are set. Thanks to everyone involved in this so far, I'm looking forward to seeing what we make out of Leap 15, and even though I cross-posted this I would like to ask that any followup conversation is kept to the opensuse-project(a)opensuse.org thread. Regards, Richard Brown on behalf of the openSUSE Board -- To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-announce+help(a)opensuse.org

1 0

[opensuse-announce] Advanced discontinuation notice for openSUSE Leap 42.1
by Marcus Meissner 20 Mar '17

20 Mar '17

Hi, With the release of openSUSE Leap 42.2 the SUSE support of openSUSE Leap 42.1 will be ending in 2 months, around May 16th 2017. Please check https://en.opensuse.org/Lifetime for lifetime information. Note that the openSUSE Leap 42 class of distributions is designed to be easily upgradable within minor versions, so Leap 42.1 to Leap 42.2 update should be easy and seemless. Ciao, Marcus for the openSUSE Maintenance Team

1 0

[opensuse-announce] Scheduled downtime for lists.opensuse.org Wednesday 2017-03-08 13:00 UTC
by Theo Chatzimichos 08 Mar '17

08 Mar '17

Hello, on Wednesday 2017-03-08 from 13:00 UTC till 15:00 UTC, the VM that hosts the openSUSE Mailing lists [1] will be offline. During that time, sending or receiving mails to the openSUSE mailing lists, or viewing their archives will not be possible. All the mails that will be sent during the downtime will be delayed. The reason for the downtime is to apply major upgrades to both the operating system and the mailing list software. We will let you know of the final status with a followup announcement. [1] https://lists.opensuse.org On behalf of the openSUSE Heroes Team -- Theo Chatzimichos <tampakrap(a)opensuse.org> <tchatzimichos(a)suse.com> System Administrator SUSE Operations and Services Team

1 1

[opensuse-announce] openSUSE Elections 2016/2017 results
by Martin Pluskal 21 Feb '17

21 Feb '17

Hello It is my pleasure to announce results of openSUSE Board elections: Aaron Luna 31 votes Sarah Julia Kriesch 66 votes Christian Boltz 71 votes Andrew Wafaa 52 votes Thus, new members of openSUSE Board are Sarah Julia Kriesch and Christian Boltz, taking place of Michal Hrusecky and Kosta Koudaras I would like to use this opportunity to thank all members for voting, candidates for standing for elections and last but not least Michal and Kosta for doing great job while serving in openSUSE board. Special thanks goes to Michal for helping with elections while stepping down from elections. Have a lot of fun Martin Pluskal P.S voting poll is yet to be deactivated, but as votes have been counted trying to use it will have no effect.

1 0

[opensuse-announce] Statement Regarding the openSUSE Board Election
by Richard Brown 06 Feb '17

06 Feb '17

Due to the technical issues with connect.opensuse.org duplicating names on the candidate list for the election while simultaniously removing some others, the Board election remains on hold. Satisfactorily debugging the root cause of the problems has proven to be impossible. The volunteers working on this investigation were hidered by a temporary outage of the MySQL database during the time they had available for their investigation. While all tests seem to suggest connect.opensuse.org is working satisfactorily at the moment, there is insufficient confidence that it can be trusted for the next Board election. We have wanted to replace connect.opensuse.org for some while, but despite this desire no one has stepped up with a viable alternative. As we need to elect a new board with some urgency, we do not have the luxury of time to continue waiting. Therefore Martin Pluskal will be urgently investigating the use of an alternative service for this particular election, such as SurveyMonkey. As only openSUSE Members can vote, this will likely require using the email addresses in connect.opensuse.org to email members and direct them with an individual, one-time-use, link to the poll. Martin will provide the details once his investigations into suitable tools is complete. Meanwhile you can help by ensuring your email address details are correct in https://connect.opensuse.org Please go to https://connect.opensuse.org and login and then click on your username then "Edit Profile" (or go to https://connect.opensuse.org/pg/profile/$USERNAME/edit/ but replacing $USERNAME with your username) Please then check/edit/correct your Email in your connect profile. Once this election is complete, Tomas Chvatal and anyone else willing to help will be needed to find a suitable replacement for connect.opensuse.org for voting. We require both a voting platform (eg. Helios - https://heliosvoting.org/) and a suitable replacement database and process for approving openSUSE Members. Thank you - The openSUSE Board -- To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-announce+help(a)opensuse.org

1 0

[opensuse-announce] Elections on hold
by Martin Pluskal 25 Jan '17

25 Jan '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello I have to regretfully inform you, that due to technical difficulties in our tool connect.opensuse.org we have to put current elections on hold. I deeply apologize for any inconvenience this might have caused to you. Technical problems that many of you noticed on the mailinglist proven to have more than visual consequences and our administrators are now looking in the issue trying to figure out how to solve the underlying problem. Election team will update election schedule and inform you about next steps as soon as possible (whether we can continue/recover current poll or if we will need to start from scratch). Kind regards from election team Martin Pluskal -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwQnJ+Ps8HqIKhK3yWyRdZ/3eaFcFAliIlXQACgkQWyRdZ/3e aFfe+Q//cnIEdz/HLFq07Hb4CkW8SNqGFwMr/Lv8aDdTuPiQhP8X1+/p0+AArQZT n33DTmOYpUB4BketBuiE8SMx/rcdY9pPRVzuj/aVng/zqFu07FRNX6D0BXOyOZka rY1a2VE4S6MZWuzCq5FxJVjaLW7XZzRwG4OWBaLpNNpWFX7CRXkSLNiZ0atSIRMQ 7vdTwzPxaK3eogRGBzqBIu8l8vHoonpUbZ7rATASmzPhFkQnCOnzFpJImX92PBJL nBA4YEsiEQRULI631dM9jG1X0WLtCljKuVYDnxAZU2SKfqRd/1H3mYZjzCPyJfez ecD8UqI5rBioJk+lPZvzabObqMaZr9cUTSohTSmnT0duhh+2eb0mMbOk+ueuM5rV wq5QkHJB3e7JtaHb/+Dzhc3uI29uJlHzKnKsrklXbfOvFwsG5i+ZNNorW6E1we8o gDTL7/VgEnqUGTKHDjv8/L7jfHk56HpeqoJ+BRSxcQpDrzUYFi7VjaNj61EY7QJ5 da+j2T0qp3vbkHhX/hQstb855csRIExT8r51FZGbf9Ovh15LayY8CM8DLsQtIUcC cTvZBxgyobVfbb1534QWbUhAOFsRUD/lKTLrcMcWjJ5q9iaEZs8KM+cbvdkN7X8f OhAJIzEA9p26xpBaZ87peBlckRs1x9p2Fgt82uhDdxtXDKE/CAU= =W36B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-announce+help(a)opensuse.org

2 1