https://fedoraproject.org/w/api.php?action=feedcontributions&user=Kkofler&feedformat=atomFedora Project Wiki - User contributions [en]2024-03-28T18:53:24ZUser contributionsMediaWiki 1.39.4https://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=613574User:Smani/QtwebkitRemoval2021-04-26T14:07:40Z<p>Kkofler: /* Detailed Description */ Mention that the replacement for qlandkartegt is qmapshack.</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kde-workspace<br />
=> Can be patched to compile without kdelibs-webkit support, it has been done by RHEL.<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire. The replacement is qmapshack, Obsoletes can be added.<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Build against QTextBrowser instead, which is supported as a fallback. This will degrade rendering quality, but it is better than dropping the package entirely.<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop the demos that depend on QtWebKit (or the entire subpackage)<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackage<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop the examples that depend on QtWebKit (or the entire subpackage)<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Subpackage of the Plasma 4 Public Transport applet (kde-plasma-publictransport), last activity in 2013. Retire.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be modified to disable QtWebKit support:<br />
* kde-runtime-libs<br />
* kde-workspace<br />
* kdepim4 (knode-libs)<br />
* krecipes<br />
* qt-assistant<br />
* qt-demos<br />
* qt-examples<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kde-plasma-publictransport (timetablemate)<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator (qtscriptbindings)<br />
* rekonq<br />
<br />
The following subpackages will be removed, and obsoleted by the corresponding main package:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-designer-plugin-webkit<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=SIGs/Games/WishList&diff=600543SIGs/Games/WishList2021-01-14T01:18:10Z<p>Kkofler: /* Games */ Remove the licensing warning for Hearts, the issue was fixed.</p>
<hr />
<div>= ROADMAP =<br />
Scratchpad of ideas for reviving Fedora Games SIG<br />
<br />
== General Goals / Objectives ==<br />
<br />
* Bringing more games into Fedora to support it as an ideal distribution for gaming with free and open source software (Four Foundations: Freedom, Features, First)<br />
<br />
* Supporting developer libraries / tools for creating games and making it easier for game developers to create and make the existance of these libraries more apparently to onlooking developers.<br />
<br />
* Trying to create collaboration between projects, and promote sharing of the projects where possible (be it assets, developer time) to take advantage of the tenets and spirit of free software.<br />
<br />
== Short-term vision ==<br />
<br />
* We should set up some projects we actively cover and endorse and give support to. And projects can apply to achieve the status of our endorsement, we should have requirements that these projects must adhere to.<br />
<br />
* Identifying lists of FOSS games public and well-known, seeing if we can package and get them into the distribution<br />
<br />
* Create resources for game developers who are looking to get started with Fedora (e.g. "How to game dev with Fedora")<br />
<br />
* Create an area where community members can post articles that they found helpful with their game (like my VLC playlist idea)<br />
<br />
* Create criteria for what we deem acceptable (the FSF free software definition would work for this) in terms of software. And Free Culture licesnes according to the Creative Commons people.<br />
<br />
== Long-term vision ==<br />
<br />
* To create a movement to endorse, encourage, support, and hold social solidarity with projects and aspiring individuals who are commited to user freedom.<br />
<br />
* Improved communication and visibility of existing resources for anyone wanting to create games for Fedora<br />
<br />
* "Quick" place to look for information, clearly visible, in more places than just a wiki page<br />
<br />
* Demonstrate the capabilities of free and open source gaming and its advancements with Fedora<br />
<br />
== Next steps for moving forward ==<br />
<br />
* Grow interest with the SIG, gain new members, build up membership by explaining what our objectives our and sharing that across the project (see: Community Blog, even Fedora Magazine, maybe)<br />
<br />
* Begin working on some of the short-term vision items<br />
<br />
* Setting up a weekly or every other week meeting time for the SIG may be useful to coordinate time to discuss and work on objectives. I have a mumble server, but perhaps someone would be willing to give us a server for this purpose.<br />
<br />
* Good opportunity to address questions like gathering resources (where are they? where do we put them? how are they communicated to a wider audience? – this isn't libraries / tools, per say, but resources for getting access to those tools)<br />
<br />
<br />
== Other details / notes ==<br />
<br />
* We should be as inclusive of other people as possible, even when individuals have opinions that are deemed unpopular.<br />
<br />
* Try to get people to collaborate more often, and remove unneeded fragmentation between projects (try to unify the workforce)<br />
<br />
* But to do this we need to create an environment where someone can show up, tell us what kind of game they want to be involved with and we can get them to a person involved in that project as soon as possible.<br />
<br />
* Reaching out to certain software projects (either games or resources for game developers) and querying their interest for packaging Fedora (working closely with upstream should always be a priority) (e.g.engines such as https://godotengine.org/ which are not currently packaged)<br />
<br />
= Fedora Games WishList =<br />
<br />
== Games ==<br />
* [http://www.blackvoxel.com/ Blackvoxel] - a new sandbox game based on a voxel engine PENDING ON FREE ASSETS<br />
* [http://crrcsim.berlios.de/wiki/ CRRCsim] - rc model flight simulator (GPL)<br />
* [http://www.freeorion.org/ freeorion] - moo rewrite<br />
* [http://selectparks.net/~julian/levelhead/ levelhead] - Augmented Reality logic game using webcam and printed out cubes. Check out video: [http://www.youtube.com/watch?v=dsb76pva4s4 youtube]<br />
* [https://github.com/nikki-and-the-robots/nikki Nikki and the Robots] - Cute non-violent gameplay with wall-jumping and remote robot controlling<br />
* [http://www.oolite.org/ oolite] - elite remake - under [https://bugzilla.redhat.com/show_bug.cgi?id=459211 review]<br />
* [http://repo.or.cz/w/pachi.git Pachi] - Strong text based (GTP) Go player. Best together with GoGui.<br />
* [http://pathological.sourceforge.net/ Pathological] - Marble Puzzle Game<br />
* [http://paxbritannica.henk.ca/ pax-britannica] - one-button real-time strategy game<br />
* [http://sourceforge.net/projects/raceintospace Race into Space] - full opensource release of a once closed source game, including vorbis sounds / music and theora videos!<br />
* [http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ Simon Tatham's Portable Puzzle Collection] is a collection of one-player puzzle games.<br />
* [http://ufo2000.sourceforge.net/ UFO2000] is free and opensource turn based tactical squad simulation multiplayer game.<br />
* [http://www.unvanquished.net/ Unvanquished] - Fork of Tremulous that is getting active development. Probably requires [https://github.com/Unvanquished/Unvanquished/issues/306 this NaCl issue to be resolved first...] and also depends on librocket (unpackaged).<br />
* [http://dangerdeep.sourceforge.net danger from the deep] 3d submarine simulation<br />
* [http://zero-k.info/ Zero-K] free, multiplatform, open-source RTS game based on the Spring engine<br />
* [https://andrettin.github.io/ Wyrmsun] A strategy game which features elements of mythology, history and fiction.<br />
* [http://te4.org/ Tales of Maj'Eyal] Tales of Maj'Eyal (ToME) is a free, open source roguelike RPG, featuring tactical turn-based combat and advanced character building. Play as one of many unique races and classes in the lore-filled world of Eyal, exploring random dungeons, facing challenging battles, and developing characters with your own tailored mix of abilities and powers.<br />
* [https://violetland.github.io/ Violetland] In this game the player should help a girl by name of Violet to struggle with hordes of monsters. For this purpose the various weapon, and also the special abilities of the heroine which are opening with experience can be used. In game there are elements of RPG in the form of strength-agility-vitality and derivatives. Also there is an unique feature: dynamic change of day and night.<br />
* [http://jag.xlabsoft.com/index.php Jag] Simple puzzle game<br />
* [http://www.zeroballistics.com/ Zero Ballistics] Zero Ballistics is a unique blend of first person shooter and tank combat, focusing on multiplayer gaming exclusively.<br />
* [http://pipewalker.sourceforge.net/ PipeWalker] This is a puzzle game in which you need to combine the components into a single circuit:connect all computers to a network server, bring water to the taps, etc.<br />
* [http://triplea.sourceforge.net/mywiki TripleA] TripleA is a turn based strategy game and board game engine, similar to Axis & Allies or Risk. Free to play online<br />
* [https://sourceforge.net/projects/bloodfrontier/ Blood Frontier] Blood Frontier was a single-player and multi-player first-person shooter game, built as a total conversion of Cube Engine 2 (Sauerbraten).<br />
* [https://rigsofrods.github.io/en/ Rigs of Rods] Rigs of Rods is a sandbox-style vehicle simulator.<br />
* [https://github.com/SimHacker/micropolis Micropolis] Micropolis is one of the oldest and grandest of city simulation games.<br />
* [https://www.lcdf.org/xmahjongg/ Xmahjongg] Xmahjongg is a simple implementation of the popular solitaire Mah Jongg game. The object is to remove all 144 tiles from the playing area by matching them two at a time. Xmahjongg is the classical version with little in the way of requirements and enough aesthetical and gameplay features to provide hours and hours of fun.<br />
* [http://spring1944.net/ Spring 1944] Spring:1944 is a WWII themed game based on the open source Spring Engine. Our goal is to create four fully functional sides (US, Germany, USSR, Britain) with period-accurate units and strengths. Realism is a primary design goal, second only to creating a game that is fun and accessible to play.<br />
* [http://freeminer.org/ Freeminer] Freeminer is a Minecraft-inspired sandbox game.<br />
* [http://www.terminal-overload.org/ Terminal Overload] Free and open-source first person shooter / spiritual successor to Revenge Of The Cats: Ethernet<br />
* [https://sourceforge.net/projects/nimuh/ Nimuh] Nimuh is a project puzzle game destined to improve the knowledge of Andalusia.<br />
* [https://launchpad.net/battleship battleship] You play versus a computer controlled opponent.Instead of firing blindly you get hints about the enemy's ships' positions.<br />
* [https://github.com/freegish/freegish Freegish] A free version of the game Gish<br />
* [http://www.braingames.getput.com/mog/ Maze of Galious] A very addictive game where you have to kill thousands of enemies, collect items in order to obtain new powers and defeat some really great demons at the end of each level<br />
* [http://toycars.sourceforge.net/Welcome.html Toy Cars] Toy Cars is a physics based 2-D racer.<br />
* [https://github.com/jazztickets/choria choria] An MMORPG that's all about grinding and doing chores.<br />
* [http://megamek.info/ MegaMek] MegaMek is an unofficial, online version of the Classic BattleTech board game. MegaMek is open source, free software. It is licenced under the GPL.<br />
* [http://zod.sourceforge.net/ Zod] Zod Engine is a remake of the 1996 classic game by Bitmap Brothers called Z. Z is a capture the flag style RTS. In this game you command robots and vehicles with the purpose of destroying the enemy's fort.<br />
* [https://github.com/xiaoyong/2048-Qt 2048-Qt] The 2048 Game implemented in Qt<br />
* [http://stuntrally.tuxfamily.org/ StuntRally] Stunt Rally game with Track Editor, based on VDrift and OGRE.<br />
* [http://bombermaaan.sourceforge.net/ bombermaaan] A classic Bomberman game with multiplayer support, cloned on original SNES games. Also similar to Dynablaster.<br />
* [http://trainsportedgame.no-ip.org/index.php trainspoted] TrAInsported is a game about trains, Artificial Intelligence and lots and lots of passengers.<br />
* [http://goatattack.net/ goatattack] Probably the best game involving goats and shotguns!<br />
* [http://7kfans.com/ Seven kingdoms, Ancient Adversaries] RTS game in a medieval world. Opensourced since 2009 under GPL (without some music and translations).<br />
* [http://en.cataclysmdda.com/ Cataclysm: Dark Days Ahead] Terminal-based post-apocalyptic survival game.<br />
* [https://github.com/Rescator7/Hearts Hearts] The card game Hearts for Qt 5 and liballegro 5 (for sound support). (We have not had a Hearts game in Fedora since gnome-hearts was dropped as part of the Python 2 removal. This one is actively maintained, in C++, with AI and online/offline modes. See also [https://github.com/Rescator7/Hearts.server Hearts.server]. The code is MIT-licensed, the [https://github.com/Rescator7/Hearts/blob/master/Credits artwork licenses] are also free: GNU LGPL, CC-BY, CC0, Public Domain.)<br />
<br />
== Tools ==<br />
* [https://github.com/aseprite-gpl/aseprite aseprite] - sprite editor tool. Originally GPLv2, upstream recently made proprietary, this is a fork to continue the FOSS version.<br />
* [https://github.com/TTimo/doom3.gpl Doom3] - now opensourced! (GPLv3)<br />
* [http://fuego.sourceforge.net/ Fuego] - Text based (GTP) Go player using Monte-Carlo tree search. Best together with GoGui.<br />
* [http://gogui.sourceforge.net/ GoGui] is a graphical user interface to programs that play the board game Go and support the Go Text Protocol, such as gnugo and Fuego.<br />
* [http://disenchant.net/engine.html tyrquake] - Conservative Quake 1 engine ([http://cachalot.mine.nu/10/SRPMS/ initial SRPM], needs desktop entry/icon, integration with autodownloader for data files)<br />
* [http://dev.ryzom.com/ ryzom] free 3d mmorpg client/server<br />
* [https://godotengine.org/ Godot Engine] free 2d/3d game engine<br />
<br />
= Games with Dead upstream or other issues=<br />
<br />
The packaging of the following games is not recommended. The packager should be able to fix any reported bugs. In some cases upstreaming them may not possible so a lot of downstream patches will have to be included in the package, revival or forks of the projects are other options. These also probably include half of the games in our wishlist at the moment.<br />
<br />
<br />
* [http://automanic.sourceforge.net/ automaniac] - 3d car deathmatch game <br />
** Last Release: August 2006<br />
** Last Commit: July 2008<br />
<br />
* [http://user.cs.tu-berlin.de/~kunegis/babychess/ BabyChess]<br />
** Last Release: March 2005<br />
<br />
* [http://antargis.berlios.de/ Battles of Antargis] - goodlooking free RTS '''Upstream is not dead, but it's not very active'''<br />
** Last Release: December 2007<br />
** Last Commit: July 2009<br />
<br />
* [http://www.bloodmasters.com/ Bloodmasters] - Arcade, oldschool multiplayer and bloodshed.That's what the game Bloodmasters is about. Play with friends on your LAN or online and experience this oldschool top-down shooter. The game supports Deathmatch, Team Deathmatch, Capture The Flag and Scavenger game modes. The game is completely freeware and without ads, spyware or other unwanted garbage. <br />
** Last Release: February 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://www.biniax.com/ Biniax-2] puzzle game with higly original game mechanics (will need to be patched to look for datas elsewhere than beside the binary, preliminary spec [http://www.bachelot.org/fedora/SPECS/biniax2.spec here], feel free to grab)<br />
** Last Release: '''v1.30 released in May 2009'''<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://bilious.homelinux.org/~paxed/brickshooter/ brickshooter] - puzzle game <br />
** Last Release: May 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://web.archive.org/web/20050305231257/www.swoogan.com/clanship.html ClanShip] - battleship game ([http://www.sourcefiles.org/Games/Strategy/Warfare/Battleships/ClanShip-1.0.5f.zip source])<br />
** Dead Upstream<br />
* [http://dungeonhack.sourceforge.net Dungeonhack] - Ambitious RPG that never got past a minimal demo state.<br />
** Dead Upstream<br />
<br />
* [http://gnukem.sourceforge.net/ Dave Gnukem] - platform game inspired by Duke Nukem 1 (might be too similar)<br />
** Last Release: August 2004<br />
** Is this fully GPLv2+ and only?<br />
<br />
* [http://sourceforge.net/projects/gillo gillo] is a two player game in a 3D ellipsoid playground<br />
** Last Release: July 2005<br />
* [http://www.tweeler.com/goollie_linux.html Go Ollie] Nice platform game using TuxCap<br />
** Last Release: '''June 2009 - Upstream active'''<br />
** Last Commit: ''No public VCS'' <br />
** ''May not compile on x86_64'' '''No longer true. It compile fine under x64_64 with TuxCap 1.4.0.'''<br />
<br />
* [http://jvgs.sourceforge.net/ JVGS] - a "minimalistic platform game" with elements based on [http://xkcd.com/ xkcd]. Music is non-commercial use only, [https://bugzilla.redhat.com/show_bug.cgi?id=914798 closed pkg review]<br />
<br />
* [http://kraptor.sourceforge.net/ Kraptor] is a classic shoot 'em up scroller game, where you must fight against tons of bad dudes (will need to be rebranded, raptor is a trademark for a very similar game).<br />
** Last Release: April 2004<br />
<br />
* [http://kursk.sourceforge.net/newfiles/Projects.htm Operation Citadel] - Operation Citadel is a WWII, turn based platoon, company level war game on the Eastern Front. The game is somewhere in between CLose Combat® and Steel Panthers®.<br />
** Last Release: ''Unknown. Seems old''<br />
** Last Commit: ''No public VCS'' <br />
** ''source is distribute as MSVC 6.0 project, I guess it will not compile, upstream seems dead''<br />
<br />
* [http://openquartz.sourceforge.net/ Open Quartz] Free GPL data combined with the Quake 1 GPL engine <br />
** Last Release: Aug 2004<br />
<br />
* [http://openraider.sourceforge.net/ Open Raider]. Not sure if it'd qualify, but it's a Tomb Raider clone.<br />
** Last Commit: 2004<br />
<br />
* [http://gnomefiles.org/app.php/Peg_Solitaire Peg Solitaire] - A simple peg-jumping game similar to Hi-Q. No idea if Hi-Q has trademark protection. <br />
** Last Release: Jan 2008<br />
<br />
* [http://race.sourceforge.net Race] - 3D top view racing game <br />
** Last Release: Jan 2003<br />
<br />
* [http://joey101.net/snowballz/ Snowballz] - fun RTS game (with penguins!) [https://bugzilla.redhat.com/show_bug.cgi?id=458598 Review Request (cancelled)]<br />
<br />
* [http://www.braingames.getput.com/stransball2/default.asp Super Transball 2] <br />
** Last Release: 2005<br />
<br />
* [http://tuxfootball.sourceforge.net/ tux-football] - 2d soccer game<br />
** Last Release: Nov 2004<br />
<br />
* [http://jasonwoof.org/vor VoR] - Dodge rocks until you die. "it's fast-paced, difficult and addictive." -- Linux Format <br />
** ''Deesn't seem active I may be wrong''<br />
<br />
* [http://wolfsinger.com/~wolfpack/XShipWars/ XShipWars] A 2d Multiplayer Space battle game.<br />
** ''Uses ESD, so it needs to be cleaned up for PulseAudio compatibility or would need to also package developers own YIFF Sound System, http://freshmeat.net/projects/yiff and their own JSW joystick support program, http://freshmeat.net/projects/libjsw'' <br />
** ''Upstream doesn't seem active''<br />
* [http://zatacka.sourceforge.net/ Zatacka] - arcade multiplayer game for 2-6 players on one keyboard <br />
** Last Release: 2007<br />
** Last Commit: Oct 2007<br />
** [https://bugzilla.redhat.com/show_bug.cgi?id=494557 Review request]<br />
<br />
<br />
== References ==<br />
<br />
* http://wiki.debian.org/Games/Suggested<br />
<br />
[[Category:Wishlist]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=SIGs/Games/WishList&diff=600012SIGs/Games/WishList2021-01-10T23:51:33Z<p>Kkofler: /* Games */ Hearts: Add link to issue about the backgrounds.</p>
<hr />
<div>= ROADMAP =<br />
Scratchpad of ideas for reviving Fedora Games SIG<br />
<br />
== General Goals / Objectives ==<br />
<br />
* Bringing more games into Fedora to support it as an ideal distribution for gaming with free and open source software (Four Foundations: Freedom, Features, First)<br />
<br />
* Supporting developer libraries / tools for creating games and making it easier for game developers to create and make the existance of these libraries more apparently to onlooking developers.<br />
<br />
* Trying to create collaboration between projects, and promote sharing of the projects where possible (be it assets, developer time) to take advantage of the tenets and spirit of free software.<br />
<br />
== Short-term vision ==<br />
<br />
* We should set up some projects we actively cover and endorse and give support to. And projects can apply to achieve the status of our endorsement, we should have requirements that these projects must adhere to.<br />
<br />
* Identifying lists of FOSS games public and well-known, seeing if we can package and get them into the distribution<br />
<br />
* Create resources for game developers who are looking to get started with Fedora (e.g. "How to game dev with Fedora")<br />
<br />
* Create an area where community members can post articles that they found helpful with their game (like my VLC playlist idea)<br />
<br />
* Create criteria for what we deem acceptable (the FSF free software definition would work for this) in terms of software. And Free Culture licesnes according to the Creative Commons people.<br />
<br />
== Long-term vision ==<br />
<br />
* To create a movement to endorse, encourage, support, and hold social solidarity with projects and aspiring individuals who are commited to user freedom.<br />
<br />
* Improved communication and visibility of existing resources for anyone wanting to create games for Fedora<br />
<br />
* "Quick" place to look for information, clearly visible, in more places than just a wiki page<br />
<br />
* Demonstrate the capabilities of free and open source gaming and its advancements with Fedora<br />
<br />
== Next steps for moving forward ==<br />
<br />
* Grow interest with the SIG, gain new members, build up membership by explaining what our objectives our and sharing that across the project (see: Community Blog, even Fedora Magazine, maybe)<br />
<br />
* Begin working on some of the short-term vision items<br />
<br />
* Setting up a weekly or every other week meeting time for the SIG may be useful to coordinate time to discuss and work on objectives. I have a mumble server, but perhaps someone would be willing to give us a server for this purpose.<br />
<br />
* Good opportunity to address questions like gathering resources (where are they? where do we put them? how are they communicated to a wider audience? – this isn't libraries / tools, per say, but resources for getting access to those tools)<br />
<br />
<br />
== Other details / notes ==<br />
<br />
* We should be as inclusive of other people as possible, even when individuals have opinions that are deemed unpopular.<br />
<br />
* Try to get people to collaborate more often, and remove unneeded fragmentation between projects (try to unify the workforce)<br />
<br />
* But to do this we need to create an environment where someone can show up, tell us what kind of game they want to be involved with and we can get them to a person involved in that project as soon as possible.<br />
<br />
* Reaching out to certain software projects (either games or resources for game developers) and querying their interest for packaging Fedora (working closely with upstream should always be a priority) (e.g.engines such as https://godotengine.org/ which are not currently packaged)<br />
<br />
= Fedora Games WishList =<br />
<br />
== Games ==<br />
* [http://www.blackvoxel.com/ Blackvoxel] - a new sandbox game based on a voxel engine PENDING ON FREE ASSETS<br />
* [http://crrcsim.berlios.de/wiki/ CRRCsim] - rc model flight simulator (GPL)<br />
* [http://www.freeorion.org/ freeorion] - moo rewrite<br />
* [http://selectparks.net/~julian/levelhead/ levelhead] - Augmented Reality logic game using webcam and printed out cubes. Check out video: [http://www.youtube.com/watch?v=dsb76pva4s4 youtube]<br />
* [https://github.com/nikki-and-the-robots/nikki Nikki and the Robots] - Cute non-violent gameplay with wall-jumping and remote robot controlling<br />
* [http://www.oolite.org/ oolite] - elite remake - under [https://bugzilla.redhat.com/show_bug.cgi?id=459211 review]<br />
* [http://repo.or.cz/w/pachi.git Pachi] - Strong text based (GTP) Go player. Best together with GoGui.<br />
* [http://pathological.sourceforge.net/ Pathological] - Marble Puzzle Game<br />
* [http://paxbritannica.henk.ca/ pax-britannica] - one-button real-time strategy game<br />
* [http://sourceforge.net/projects/raceintospace Race into Space] - full opensource release of a once closed source game, including vorbis sounds / music and theora videos!<br />
* [http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ Simon Tatham's Portable Puzzle Collection] is a collection of one-player puzzle games.<br />
* [http://ufo2000.sourceforge.net/ UFO2000] is free and opensource turn based tactical squad simulation multiplayer game.<br />
* [http://www.unvanquished.net/ Unvanquished] - Fork of Tremulous that is getting active development. Probably requires [https://github.com/Unvanquished/Unvanquished/issues/306 this NaCl issue to be resolved first...] and also depends on librocket (unpackaged).<br />
* [http://dangerdeep.sourceforge.net danger from the deep] 3d submarine simulation<br />
* [http://zero-k.info/ Zero-K] free, multiplatform, open-source RTS game based on the Spring engine<br />
* [https://andrettin.github.io/ Wyrmsun] A strategy game which features elements of mythology, history and fiction.<br />
* [http://te4.org/ Tales of Maj'Eyal] Tales of Maj'Eyal (ToME) is a free, open source roguelike RPG, featuring tactical turn-based combat and advanced character building. Play as one of many unique races and classes in the lore-filled world of Eyal, exploring random dungeons, facing challenging battles, and developing characters with your own tailored mix of abilities and powers.<br />
* [https://violetland.github.io/ Violetland] In this game the player should help a girl by name of Violet to struggle with hordes of monsters. For this purpose the various weapon, and also the special abilities of the heroine which are opening with experience can be used. In game there are elements of RPG in the form of strength-agility-vitality and derivatives. Also there is an unique feature: dynamic change of day and night.<br />
* [http://jag.xlabsoft.com/index.php Jag] Simple puzzle game<br />
* [http://www.zeroballistics.com/ Zero Ballistics] Zero Ballistics is a unique blend of first person shooter and tank combat, focusing on multiplayer gaming exclusively.<br />
* [http://pipewalker.sourceforge.net/ PipeWalker] This is a puzzle game in which you need to combine the components into a single circuit:connect all computers to a network server, bring water to the taps, etc.<br />
* [http://triplea.sourceforge.net/mywiki TripleA] TripleA is a turn based strategy game and board game engine, similar to Axis & Allies or Risk. Free to play online<br />
* [https://sourceforge.net/projects/bloodfrontier/ Blood Frontier] Blood Frontier was a single-player and multi-player first-person shooter game, built as a total conversion of Cube Engine 2 (Sauerbraten).<br />
* [https://rigsofrods.github.io/en/ Rigs of Rods] Rigs of Rods is a sandbox-style vehicle simulator.<br />
* [https://github.com/SimHacker/micropolis Micropolis] Micropolis is one of the oldest and grandest of city simulation games.<br />
* [https://www.lcdf.org/xmahjongg/ Xmahjongg] Xmahjongg is a simple implementation of the popular solitaire Mah Jongg game. The object is to remove all 144 tiles from the playing area by matching them two at a time. Xmahjongg is the classical version with little in the way of requirements and enough aesthetical and gameplay features to provide hours and hours of fun.<br />
* [http://spring1944.net/ Spring 1944] Spring:1944 is a WWII themed game based on the open source Spring Engine. Our goal is to create four fully functional sides (US, Germany, USSR, Britain) with period-accurate units and strengths. Realism is a primary design goal, second only to creating a game that is fun and accessible to play.<br />
* [http://freeminer.org/ Freeminer] Freeminer is a Minecraft-inspired sandbox game.<br />
* [http://www.terminal-overload.org/ Terminal Overload] Free and open-source first person shooter / spiritual successor to Revenge Of The Cats: Ethernet<br />
* [https://sourceforge.net/projects/nimuh/ Nimuh] Nimuh is a project puzzle game destined to improve the knowledge of Andalusia.<br />
* [https://launchpad.net/battleship battleship] You play versus a computer controlled opponent.Instead of firing blindly you get hints about the enemy's ships' positions.<br />
* [https://github.com/freegish/freegish Freegish] A free version of the game Gish<br />
* [http://www.braingames.getput.com/mog/ Maze of Galious] A very addictive game where you have to kill thousands of enemies, collect items in order to obtain new powers and defeat some really great demons at the end of each level<br />
* [http://toycars.sourceforge.net/Welcome.html Toy Cars] Toy Cars is a physics based 2-D racer.<br />
* [https://github.com/jazztickets/choria choria] An MMORPG that's all about grinding and doing chores.<br />
* [http://megamek.info/ MegaMek] MegaMek is an unofficial, online version of the Classic BattleTech board game. MegaMek is open source, free software. It is licenced under the GPL.<br />
* [http://zod.sourceforge.net/ Zod] Zod Engine is a remake of the 1996 classic game by Bitmap Brothers called Z. Z is a capture the flag style RTS. In this game you command robots and vehicles with the purpose of destroying the enemy's fort.<br />
* [https://github.com/xiaoyong/2048-Qt 2048-Qt] The 2048 Game implemented in Qt<br />
* [http://stuntrally.tuxfamily.org/ StuntRally] Stunt Rally game with Track Editor, based on VDrift and OGRE.<br />
* [http://bombermaaan.sourceforge.net/ bombermaaan] A classic Bomberman game with multiplayer support, cloned on original SNES games. Also similar to Dynablaster.<br />
* [http://trainsportedgame.no-ip.org/index.php trainspoted] TrAInsported is a game about trains, Artificial Intelligence and lots and lots of passengers.<br />
* [http://goatattack.net/ goatattack] Probably the best game involving goats and shotguns!<br />
* [http://7kfans.com/ Seven kingdoms, Ancient Adversaries] RTS game in a medieval world. Opensourced since 2009 under GPL (without some music and translations).<br />
* [http://en.cataclysmdda.com/ Cataclysm: Dark Days Ahead] Terminal-based post-apocalyptic survival game.<br />
* [https://github.com/Rescator7/Hearts Hearts] The card game Hearts for Qt 5 and liballegro 5 (for sound support). (We have not had a Hearts game in Fedora since gnome-hearts was dropped as part of the Python 2 removal. This one is actively maintained, in C++, with AI and online/offline modes. See also [https://github.com/Rescator7/Hearts.server Hearts.server]. '''Warning:''' <code>backgrounds/*.jpg</code> added in 1.8 are under the [https://unsplash.com/license Unsplash license] ([https://phabricator.kde.org/D18078#401394 non-free], [https://github.com/Rescator7/Hearts/issues/2 issue filed]). The other [https://github.com/Rescator7/Hearts/blob/master/Credits artwork licenses] are free: GNU GPL, GNU LGPL, CC-BY-SA, CC-BY, CC0.)<br />
<br />
== Tools ==<br />
* [https://github.com/aseprite-gpl/aseprite aseprite] - sprite editor tool. Originally GPLv2, upstream recently made proprietary, this is a fork to continue the FOSS version.<br />
* [https://github.com/TTimo/doom3.gpl Doom3] - now opensourced! (GPLv3)<br />
* [http://fuego.sourceforge.net/ Fuego] - Text based (GTP) Go player using Monte-Carlo tree search. Best together with GoGui.<br />
* [http://gogui.sourceforge.net/ GoGui] is a graphical user interface to programs that play the board game Go and support the Go Text Protocol, such as gnugo and Fuego.<br />
* [http://disenchant.net/engine.html tyrquake] - Conservative Quake 1 engine ([http://cachalot.mine.nu/10/SRPMS/ initial SRPM], needs desktop entry/icon, integration with autodownloader for data files)<br />
* [http://dev.ryzom.com/ ryzom] free 3d mmorpg client/server<br />
* [https://godotengine.org/ Godot Engine] free 2d/3d game engine<br />
<br />
= Games with Dead upstream or other issues=<br />
<br />
The packaging of the following games is not recommended. The packager should be able to fix any reported bugs. In some cases upstreaming them may not possible so a lot of downstream patches will have to be included in the package, revival or forks of the projects are other options. These also probably include half of the games in our wishlist at the moment.<br />
<br />
<br />
* [http://automanic.sourceforge.net/ automaniac] - 3d car deathmatch game <br />
** Last Release: August 2006<br />
** Last Commit: July 2008<br />
<br />
* [http://user.cs.tu-berlin.de/~kunegis/babychess/ BabyChess]<br />
** Last Release: March 2005<br />
<br />
* [http://antargis.berlios.de/ Battles of Antargis] - goodlooking free RTS '''Upstream is not dead, but it's not very active'''<br />
** Last Release: December 2007<br />
** Last Commit: July 2009<br />
<br />
* [http://www.bloodmasters.com/ Bloodmasters] - Arcade, oldschool multiplayer and bloodshed.That's what the game Bloodmasters is about. Play with friends on your LAN or online and experience this oldschool top-down shooter. The game supports Deathmatch, Team Deathmatch, Capture The Flag and Scavenger game modes. The game is completely freeware and without ads, spyware or other unwanted garbage. <br />
** Last Release: February 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://www.biniax.com/ Biniax-2] puzzle game with higly original game mechanics (will need to be patched to look for datas elsewhere than beside the binary, preliminary spec [http://www.bachelot.org/fedora/SPECS/biniax2.spec here], feel free to grab)<br />
** Last Release: '''v1.30 released in May 2009'''<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://bilious.homelinux.org/~paxed/brickshooter/ brickshooter] - puzzle game <br />
** Last Release: May 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://web.archive.org/web/20050305231257/www.swoogan.com/clanship.html ClanShip] - battleship game ([http://www.sourcefiles.org/Games/Strategy/Warfare/Battleships/ClanShip-1.0.5f.zip source])<br />
** Dead Upstream<br />
* [http://dungeonhack.sourceforge.net Dungeonhack] - Ambitious RPG that never got past a minimal demo state.<br />
** Dead Upstream<br />
<br />
* [http://gnukem.sourceforge.net/ Dave Gnukem] - platform game inspired by Duke Nukem 1 (might be too similar)<br />
** Last Release: August 2004<br />
** Is this fully GPLv2+ and only?<br />
<br />
* [http://sourceforge.net/projects/gillo gillo] is a two player game in a 3D ellipsoid playground<br />
** Last Release: July 2005<br />
* [http://www.tweeler.com/goollie_linux.html Go Ollie] Nice platform game using TuxCap<br />
** Last Release: '''June 2009 - Upstream active'''<br />
** Last Commit: ''No public VCS'' <br />
** ''May not compile on x86_64'' '''No longer true. It compile fine under x64_64 with TuxCap 1.4.0.'''<br />
<br />
* [http://jvgs.sourceforge.net/ JVGS] - a "minimalistic platform game" with elements based on [http://xkcd.com/ xkcd]. Music is non-commercial use only, [https://bugzilla.redhat.com/show_bug.cgi?id=914798 closed pkg review]<br />
<br />
* [http://kraptor.sourceforge.net/ Kraptor] is a classic shoot 'em up scroller game, where you must fight against tons of bad dudes (will need to be rebranded, raptor is a trademark for a very similar game).<br />
** Last Release: April 2004<br />
<br />
* [http://kursk.sourceforge.net/newfiles/Projects.htm Operation Citadel] - Operation Citadel is a WWII, turn based platoon, company level war game on the Eastern Front. The game is somewhere in between CLose Combat® and Steel Panthers®.<br />
** Last Release: ''Unknown. Seems old''<br />
** Last Commit: ''No public VCS'' <br />
** ''source is distribute as MSVC 6.0 project, I guess it will not compile, upstream seems dead''<br />
<br />
* [http://openquartz.sourceforge.net/ Open Quartz] Free GPL data combined with the Quake 1 GPL engine <br />
** Last Release: Aug 2004<br />
<br />
* [http://openraider.sourceforge.net/ Open Raider]. Not sure if it'd qualify, but it's a Tomb Raider clone.<br />
** Last Commit: 2004<br />
<br />
* [http://gnomefiles.org/app.php/Peg_Solitaire Peg Solitaire] - A simple peg-jumping game similar to Hi-Q. No idea if Hi-Q has trademark protection. <br />
** Last Release: Jan 2008<br />
<br />
* [http://race.sourceforge.net Race] - 3D top view racing game <br />
** Last Release: Jan 2003<br />
<br />
* [http://joey101.net/snowballz/ Snowballz] - fun RTS game (with penguins!) [https://bugzilla.redhat.com/show_bug.cgi?id=458598 Review Request (cancelled)]<br />
<br />
* [http://www.braingames.getput.com/stransball2/default.asp Super Transball 2] <br />
** Last Release: 2005<br />
<br />
* [http://tuxfootball.sourceforge.net/ tux-football] - 2d soccer game<br />
** Last Release: Nov 2004<br />
<br />
* [http://jasonwoof.org/vor VoR] - Dodge rocks until you die. "it's fast-paced, difficult and addictive." -- Linux Format <br />
** ''Deesn't seem active I may be wrong''<br />
<br />
* [http://wolfsinger.com/~wolfpack/XShipWars/ XShipWars] A 2d Multiplayer Space battle game.<br />
** ''Uses ESD, so it needs to be cleaned up for PulseAudio compatibility or would need to also package developers own YIFF Sound System, http://freshmeat.net/projects/yiff and their own JSW joystick support program, http://freshmeat.net/projects/libjsw'' <br />
** ''Upstream doesn't seem active''<br />
* [http://zatacka.sourceforge.net/ Zatacka] - arcade multiplayer game for 2-6 players on one keyboard <br />
** Last Release: 2007<br />
** Last Commit: Oct 2007<br />
** [https://bugzilla.redhat.com/show_bug.cgi?id=494557 Review request]<br />
<br />
<br />
== References ==<br />
<br />
* http://wiki.debian.org/Games/Suggested<br />
<br />
[[Category:Wishlist]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=SIGs/Games/WishList&diff=600011SIGs/Games/WishList2021-01-10T23:45:35Z<p>Kkofler: /* Games */ Add link about the non-freeness of the Unsplash license: at least KDE considers it non-free.</p>
<hr />
<div>= ROADMAP =<br />
Scratchpad of ideas for reviving Fedora Games SIG<br />
<br />
== General Goals / Objectives ==<br />
<br />
* Bringing more games into Fedora to support it as an ideal distribution for gaming with free and open source software (Four Foundations: Freedom, Features, First)<br />
<br />
* Supporting developer libraries / tools for creating games and making it easier for game developers to create and make the existance of these libraries more apparently to onlooking developers.<br />
<br />
* Trying to create collaboration between projects, and promote sharing of the projects where possible (be it assets, developer time) to take advantage of the tenets and spirit of free software.<br />
<br />
== Short-term vision ==<br />
<br />
* We should set up some projects we actively cover and endorse and give support to. And projects can apply to achieve the status of our endorsement, we should have requirements that these projects must adhere to.<br />
<br />
* Identifying lists of FOSS games public and well-known, seeing if we can package and get them into the distribution<br />
<br />
* Create resources for game developers who are looking to get started with Fedora (e.g. "How to game dev with Fedora")<br />
<br />
* Create an area where community members can post articles that they found helpful with their game (like my VLC playlist idea)<br />
<br />
* Create criteria for what we deem acceptable (the FSF free software definition would work for this) in terms of software. And Free Culture licesnes according to the Creative Commons people.<br />
<br />
== Long-term vision ==<br />
<br />
* To create a movement to endorse, encourage, support, and hold social solidarity with projects and aspiring individuals who are commited to user freedom.<br />
<br />
* Improved communication and visibility of existing resources for anyone wanting to create games for Fedora<br />
<br />
* "Quick" place to look for information, clearly visible, in more places than just a wiki page<br />
<br />
* Demonstrate the capabilities of free and open source gaming and its advancements with Fedora<br />
<br />
== Next steps for moving forward ==<br />
<br />
* Grow interest with the SIG, gain new members, build up membership by explaining what our objectives our and sharing that across the project (see: Community Blog, even Fedora Magazine, maybe)<br />
<br />
* Begin working on some of the short-term vision items<br />
<br />
* Setting up a weekly or every other week meeting time for the SIG may be useful to coordinate time to discuss and work on objectives. I have a mumble server, but perhaps someone would be willing to give us a server for this purpose.<br />
<br />
* Good opportunity to address questions like gathering resources (where are they? where do we put them? how are they communicated to a wider audience? – this isn't libraries / tools, per say, but resources for getting access to those tools)<br />
<br />
<br />
== Other details / notes ==<br />
<br />
* We should be as inclusive of other people as possible, even when individuals have opinions that are deemed unpopular.<br />
<br />
* Try to get people to collaborate more often, and remove unneeded fragmentation between projects (try to unify the workforce)<br />
<br />
* But to do this we need to create an environment where someone can show up, tell us what kind of game they want to be involved with and we can get them to a person involved in that project as soon as possible.<br />
<br />
* Reaching out to certain software projects (either games or resources for game developers) and querying their interest for packaging Fedora (working closely with upstream should always be a priority) (e.g.engines such as https://godotengine.org/ which are not currently packaged)<br />
<br />
= Fedora Games WishList =<br />
<br />
== Games ==<br />
* [http://www.blackvoxel.com/ Blackvoxel] - a new sandbox game based on a voxel engine PENDING ON FREE ASSETS<br />
* [http://crrcsim.berlios.de/wiki/ CRRCsim] - rc model flight simulator (GPL)<br />
* [http://www.freeorion.org/ freeorion] - moo rewrite<br />
* [http://selectparks.net/~julian/levelhead/ levelhead] - Augmented Reality logic game using webcam and printed out cubes. Check out video: [http://www.youtube.com/watch?v=dsb76pva4s4 youtube]<br />
* [https://github.com/nikki-and-the-robots/nikki Nikki and the Robots] - Cute non-violent gameplay with wall-jumping and remote robot controlling<br />
* [http://www.oolite.org/ oolite] - elite remake - under [https://bugzilla.redhat.com/show_bug.cgi?id=459211 review]<br />
* [http://repo.or.cz/w/pachi.git Pachi] - Strong text based (GTP) Go player. Best together with GoGui.<br />
* [http://pathological.sourceforge.net/ Pathological] - Marble Puzzle Game<br />
* [http://paxbritannica.henk.ca/ pax-britannica] - one-button real-time strategy game<br />
* [http://sourceforge.net/projects/raceintospace Race into Space] - full opensource release of a once closed source game, including vorbis sounds / music and theora videos!<br />
* [http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ Simon Tatham's Portable Puzzle Collection] is a collection of one-player puzzle games.<br />
* [http://ufo2000.sourceforge.net/ UFO2000] is free and opensource turn based tactical squad simulation multiplayer game.<br />
* [http://www.unvanquished.net/ Unvanquished] - Fork of Tremulous that is getting active development. Probably requires [https://github.com/Unvanquished/Unvanquished/issues/306 this NaCl issue to be resolved first...] and also depends on librocket (unpackaged).<br />
* [http://dangerdeep.sourceforge.net danger from the deep] 3d submarine simulation<br />
* [http://zero-k.info/ Zero-K] free, multiplatform, open-source RTS game based on the Spring engine<br />
* [https://andrettin.github.io/ Wyrmsun] A strategy game which features elements of mythology, history and fiction.<br />
* [http://te4.org/ Tales of Maj'Eyal] Tales of Maj'Eyal (ToME) is a free, open source roguelike RPG, featuring tactical turn-based combat and advanced character building. Play as one of many unique races and classes in the lore-filled world of Eyal, exploring random dungeons, facing challenging battles, and developing characters with your own tailored mix of abilities and powers.<br />
* [https://violetland.github.io/ Violetland] In this game the player should help a girl by name of Violet to struggle with hordes of monsters. For this purpose the various weapon, and also the special abilities of the heroine which are opening with experience can be used. In game there are elements of RPG in the form of strength-agility-vitality and derivatives. Also there is an unique feature: dynamic change of day and night.<br />
* [http://jag.xlabsoft.com/index.php Jag] Simple puzzle game<br />
* [http://www.zeroballistics.com/ Zero Ballistics] Zero Ballistics is a unique blend of first person shooter and tank combat, focusing on multiplayer gaming exclusively.<br />
* [http://pipewalker.sourceforge.net/ PipeWalker] This is a puzzle game in which you need to combine the components into a single circuit:connect all computers to a network server, bring water to the taps, etc.<br />
* [http://triplea.sourceforge.net/mywiki TripleA] TripleA is a turn based strategy game and board game engine, similar to Axis & Allies or Risk. Free to play online<br />
* [https://sourceforge.net/projects/bloodfrontier/ Blood Frontier] Blood Frontier was a single-player and multi-player first-person shooter game, built as a total conversion of Cube Engine 2 (Sauerbraten).<br />
* [https://rigsofrods.github.io/en/ Rigs of Rods] Rigs of Rods is a sandbox-style vehicle simulator.<br />
* [https://github.com/SimHacker/micropolis Micropolis] Micropolis is one of the oldest and grandest of city simulation games.<br />
* [https://www.lcdf.org/xmahjongg/ Xmahjongg] Xmahjongg is a simple implementation of the popular solitaire Mah Jongg game. The object is to remove all 144 tiles from the playing area by matching them two at a time. Xmahjongg is the classical version with little in the way of requirements and enough aesthetical and gameplay features to provide hours and hours of fun.<br />
* [http://spring1944.net/ Spring 1944] Spring:1944 is a WWII themed game based on the open source Spring Engine. Our goal is to create four fully functional sides (US, Germany, USSR, Britain) with period-accurate units and strengths. Realism is a primary design goal, second only to creating a game that is fun and accessible to play.<br />
* [http://freeminer.org/ Freeminer] Freeminer is a Minecraft-inspired sandbox game.<br />
* [http://www.terminal-overload.org/ Terminal Overload] Free and open-source first person shooter / spiritual successor to Revenge Of The Cats: Ethernet<br />
* [https://sourceforge.net/projects/nimuh/ Nimuh] Nimuh is a project puzzle game destined to improve the knowledge of Andalusia.<br />
* [https://launchpad.net/battleship battleship] You play versus a computer controlled opponent.Instead of firing blindly you get hints about the enemy's ships' positions.<br />
* [https://github.com/freegish/freegish Freegish] A free version of the game Gish<br />
* [http://www.braingames.getput.com/mog/ Maze of Galious] A very addictive game where you have to kill thousands of enemies, collect items in order to obtain new powers and defeat some really great demons at the end of each level<br />
* [http://toycars.sourceforge.net/Welcome.html Toy Cars] Toy Cars is a physics based 2-D racer.<br />
* [https://github.com/jazztickets/choria choria] An MMORPG that's all about grinding and doing chores.<br />
* [http://megamek.info/ MegaMek] MegaMek is an unofficial, online version of the Classic BattleTech board game. MegaMek is open source, free software. It is licenced under the GPL.<br />
* [http://zod.sourceforge.net/ Zod] Zod Engine is a remake of the 1996 classic game by Bitmap Brothers called Z. Z is a capture the flag style RTS. In this game you command robots and vehicles with the purpose of destroying the enemy's fort.<br />
* [https://github.com/xiaoyong/2048-Qt 2048-Qt] The 2048 Game implemented in Qt<br />
* [http://stuntrally.tuxfamily.org/ StuntRally] Stunt Rally game with Track Editor, based on VDrift and OGRE.<br />
* [http://bombermaaan.sourceforge.net/ bombermaaan] A classic Bomberman game with multiplayer support, cloned on original SNES games. Also similar to Dynablaster.<br />
* [http://trainsportedgame.no-ip.org/index.php trainspoted] TrAInsported is a game about trains, Artificial Intelligence and lots and lots of passengers.<br />
* [http://goatattack.net/ goatattack] Probably the best game involving goats and shotguns!<br />
* [http://7kfans.com/ Seven kingdoms, Ancient Adversaries] RTS game in a medieval world. Opensourced since 2009 under GPL (without some music and translations).<br />
* [http://en.cataclysmdda.com/ Cataclysm: Dark Days Ahead] Terminal-based post-apocalyptic survival game.<br />
* [https://github.com/Rescator7/Hearts Hearts] The card game Hearts for Qt 5 and liballegro 5 (for sound support). (We have not had a Hearts game in Fedora since gnome-hearts was dropped as part of the Python 2 removal. This one is actively maintained, in C++, with AI and online/offline modes. See also [https://github.com/Rescator7/Hearts.server Hearts.server]. '''Warning:''' <code>backgrounds/*.jpg</code> added in 1.8 are under the [https://unsplash.com/license Unsplash license] ([https://phabricator.kde.org/D18078#401394 non-free]). The other [https://github.com/Rescator7/Hearts/blob/master/Credits artwork licenses] are free: GNU GPL, GNU LGPL, CC-BY-SA, CC-BY, CC0.)<br />
<br />
== Tools ==<br />
* [https://github.com/aseprite-gpl/aseprite aseprite] - sprite editor tool. Originally GPLv2, upstream recently made proprietary, this is a fork to continue the FOSS version.<br />
* [https://github.com/TTimo/doom3.gpl Doom3] - now opensourced! (GPLv3)<br />
* [http://fuego.sourceforge.net/ Fuego] - Text based (GTP) Go player using Monte-Carlo tree search. Best together with GoGui.<br />
* [http://gogui.sourceforge.net/ GoGui] is a graphical user interface to programs that play the board game Go and support the Go Text Protocol, such as gnugo and Fuego.<br />
* [http://disenchant.net/engine.html tyrquake] - Conservative Quake 1 engine ([http://cachalot.mine.nu/10/SRPMS/ initial SRPM], needs desktop entry/icon, integration with autodownloader for data files)<br />
* [http://dev.ryzom.com/ ryzom] free 3d mmorpg client/server<br />
* [https://godotengine.org/ Godot Engine] free 2d/3d game engine<br />
<br />
= Games with Dead upstream or other issues=<br />
<br />
The packaging of the following games is not recommended. The packager should be able to fix any reported bugs. In some cases upstreaming them may not possible so a lot of downstream patches will have to be included in the package, revival or forks of the projects are other options. These also probably include half of the games in our wishlist at the moment.<br />
<br />
<br />
* [http://automanic.sourceforge.net/ automaniac] - 3d car deathmatch game <br />
** Last Release: August 2006<br />
** Last Commit: July 2008<br />
<br />
* [http://user.cs.tu-berlin.de/~kunegis/babychess/ BabyChess]<br />
** Last Release: March 2005<br />
<br />
* [http://antargis.berlios.de/ Battles of Antargis] - goodlooking free RTS '''Upstream is not dead, but it's not very active'''<br />
** Last Release: December 2007<br />
** Last Commit: July 2009<br />
<br />
* [http://www.bloodmasters.com/ Bloodmasters] - Arcade, oldschool multiplayer and bloodshed.That's what the game Bloodmasters is about. Play with friends on your LAN or online and experience this oldschool top-down shooter. The game supports Deathmatch, Team Deathmatch, Capture The Flag and Scavenger game modes. The game is completely freeware and without ads, spyware or other unwanted garbage. <br />
** Last Release: February 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://www.biniax.com/ Biniax-2] puzzle game with higly original game mechanics (will need to be patched to look for datas elsewhere than beside the binary, preliminary spec [http://www.bachelot.org/fedora/SPECS/biniax2.spec here], feel free to grab)<br />
** Last Release: '''v1.30 released in May 2009'''<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://bilious.homelinux.org/~paxed/brickshooter/ brickshooter] - puzzle game <br />
** Last Release: May 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://web.archive.org/web/20050305231257/www.swoogan.com/clanship.html ClanShip] - battleship game ([http://www.sourcefiles.org/Games/Strategy/Warfare/Battleships/ClanShip-1.0.5f.zip source])<br />
** Dead Upstream<br />
* [http://dungeonhack.sourceforge.net Dungeonhack] - Ambitious RPG that never got past a minimal demo state.<br />
** Dead Upstream<br />
<br />
* [http://gnukem.sourceforge.net/ Dave Gnukem] - platform game inspired by Duke Nukem 1 (might be too similar)<br />
** Last Release: August 2004<br />
** Is this fully GPLv2+ and only?<br />
<br />
* [http://sourceforge.net/projects/gillo gillo] is a two player game in a 3D ellipsoid playground<br />
** Last Release: July 2005<br />
* [http://www.tweeler.com/goollie_linux.html Go Ollie] Nice platform game using TuxCap<br />
** Last Release: '''June 2009 - Upstream active'''<br />
** Last Commit: ''No public VCS'' <br />
** ''May not compile on x86_64'' '''No longer true. It compile fine under x64_64 with TuxCap 1.4.0.'''<br />
<br />
* [http://jvgs.sourceforge.net/ JVGS] - a "minimalistic platform game" with elements based on [http://xkcd.com/ xkcd]. Music is non-commercial use only, [https://bugzilla.redhat.com/show_bug.cgi?id=914798 closed pkg review]<br />
<br />
* [http://kraptor.sourceforge.net/ Kraptor] is a classic shoot 'em up scroller game, where you must fight against tons of bad dudes (will need to be rebranded, raptor is a trademark for a very similar game).<br />
** Last Release: April 2004<br />
<br />
* [http://kursk.sourceforge.net/newfiles/Projects.htm Operation Citadel] - Operation Citadel is a WWII, turn based platoon, company level war game on the Eastern Front. The game is somewhere in between CLose Combat® and Steel Panthers®.<br />
** Last Release: ''Unknown. Seems old''<br />
** Last Commit: ''No public VCS'' <br />
** ''source is distribute as MSVC 6.0 project, I guess it will not compile, upstream seems dead''<br />
<br />
* [http://openquartz.sourceforge.net/ Open Quartz] Free GPL data combined with the Quake 1 GPL engine <br />
** Last Release: Aug 2004<br />
<br />
* [http://openraider.sourceforge.net/ Open Raider]. Not sure if it'd qualify, but it's a Tomb Raider clone.<br />
** Last Commit: 2004<br />
<br />
* [http://gnomefiles.org/app.php/Peg_Solitaire Peg Solitaire] - A simple peg-jumping game similar to Hi-Q. No idea if Hi-Q has trademark protection. <br />
** Last Release: Jan 2008<br />
<br />
* [http://race.sourceforge.net Race] - 3D top view racing game <br />
** Last Release: Jan 2003<br />
<br />
* [http://joey101.net/snowballz/ Snowballz] - fun RTS game (with penguins!) [https://bugzilla.redhat.com/show_bug.cgi?id=458598 Review Request (cancelled)]<br />
<br />
* [http://www.braingames.getput.com/stransball2/default.asp Super Transball 2] <br />
** Last Release: 2005<br />
<br />
* [http://tuxfootball.sourceforge.net/ tux-football] - 2d soccer game<br />
** Last Release: Nov 2004<br />
<br />
* [http://jasonwoof.org/vor VoR] - Dodge rocks until you die. "it's fast-paced, difficult and addictive." -- Linux Format <br />
** ''Deesn't seem active I may be wrong''<br />
<br />
* [http://wolfsinger.com/~wolfpack/XShipWars/ XShipWars] A 2d Multiplayer Space battle game.<br />
** ''Uses ESD, so it needs to be cleaned up for PulseAudio compatibility or would need to also package developers own YIFF Sound System, http://freshmeat.net/projects/yiff and their own JSW joystick support program, http://freshmeat.net/projects/libjsw'' <br />
** ''Upstream doesn't seem active''<br />
* [http://zatacka.sourceforge.net/ Zatacka] - arcade multiplayer game for 2-6 players on one keyboard <br />
** Last Release: 2007<br />
** Last Commit: Oct 2007<br />
** [https://bugzilla.redhat.com/show_bug.cgi?id=494557 Review request]<br />
<br />
<br />
== References ==<br />
<br />
* http://wiki.debian.org/Games/Suggested<br />
<br />
[[Category:Wishlist]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=SIGs/Games/WishList&diff=600010SIGs/Games/WishList2021-01-10T23:41:29Z<p>Kkofler: /* Games */ Hearts: Warn about the Unsplash license for backgrounds.</p>
<hr />
<div>= ROADMAP =<br />
Scratchpad of ideas for reviving Fedora Games SIG<br />
<br />
== General Goals / Objectives ==<br />
<br />
* Bringing more games into Fedora to support it as an ideal distribution for gaming with free and open source software (Four Foundations: Freedom, Features, First)<br />
<br />
* Supporting developer libraries / tools for creating games and making it easier for game developers to create and make the existance of these libraries more apparently to onlooking developers.<br />
<br />
* Trying to create collaboration between projects, and promote sharing of the projects where possible (be it assets, developer time) to take advantage of the tenets and spirit of free software.<br />
<br />
== Short-term vision ==<br />
<br />
* We should set up some projects we actively cover and endorse and give support to. And projects can apply to achieve the status of our endorsement, we should have requirements that these projects must adhere to.<br />
<br />
* Identifying lists of FOSS games public and well-known, seeing if we can package and get them into the distribution<br />
<br />
* Create resources for game developers who are looking to get started with Fedora (e.g. "How to game dev with Fedora")<br />
<br />
* Create an area where community members can post articles that they found helpful with their game (like my VLC playlist idea)<br />
<br />
* Create criteria for what we deem acceptable (the FSF free software definition would work for this) in terms of software. And Free Culture licesnes according to the Creative Commons people.<br />
<br />
== Long-term vision ==<br />
<br />
* To create a movement to endorse, encourage, support, and hold social solidarity with projects and aspiring individuals who are commited to user freedom.<br />
<br />
* Improved communication and visibility of existing resources for anyone wanting to create games for Fedora<br />
<br />
* "Quick" place to look for information, clearly visible, in more places than just a wiki page<br />
<br />
* Demonstrate the capabilities of free and open source gaming and its advancements with Fedora<br />
<br />
== Next steps for moving forward ==<br />
<br />
* Grow interest with the SIG, gain new members, build up membership by explaining what our objectives our and sharing that across the project (see: Community Blog, even Fedora Magazine, maybe)<br />
<br />
* Begin working on some of the short-term vision items<br />
<br />
* Setting up a weekly or every other week meeting time for the SIG may be useful to coordinate time to discuss and work on objectives. I have a mumble server, but perhaps someone would be willing to give us a server for this purpose.<br />
<br />
* Good opportunity to address questions like gathering resources (where are they? where do we put them? how are they communicated to a wider audience? – this isn't libraries / tools, per say, but resources for getting access to those tools)<br />
<br />
<br />
== Other details / notes ==<br />
<br />
* We should be as inclusive of other people as possible, even when individuals have opinions that are deemed unpopular.<br />
<br />
* Try to get people to collaborate more often, and remove unneeded fragmentation between projects (try to unify the workforce)<br />
<br />
* But to do this we need to create an environment where someone can show up, tell us what kind of game they want to be involved with and we can get them to a person involved in that project as soon as possible.<br />
<br />
* Reaching out to certain software projects (either games or resources for game developers) and querying their interest for packaging Fedora (working closely with upstream should always be a priority) (e.g.engines such as https://godotengine.org/ which are not currently packaged)<br />
<br />
= Fedora Games WishList =<br />
<br />
== Games ==<br />
* [http://www.blackvoxel.com/ Blackvoxel] - a new sandbox game based on a voxel engine PENDING ON FREE ASSETS<br />
* [http://crrcsim.berlios.de/wiki/ CRRCsim] - rc model flight simulator (GPL)<br />
* [http://www.freeorion.org/ freeorion] - moo rewrite<br />
* [http://selectparks.net/~julian/levelhead/ levelhead] - Augmented Reality logic game using webcam and printed out cubes. Check out video: [http://www.youtube.com/watch?v=dsb76pva4s4 youtube]<br />
* [https://github.com/nikki-and-the-robots/nikki Nikki and the Robots] - Cute non-violent gameplay with wall-jumping and remote robot controlling<br />
* [http://www.oolite.org/ oolite] - elite remake - under [https://bugzilla.redhat.com/show_bug.cgi?id=459211 review]<br />
* [http://repo.or.cz/w/pachi.git Pachi] - Strong text based (GTP) Go player. Best together with GoGui.<br />
* [http://pathological.sourceforge.net/ Pathological] - Marble Puzzle Game<br />
* [http://paxbritannica.henk.ca/ pax-britannica] - one-button real-time strategy game<br />
* [http://sourceforge.net/projects/raceintospace Race into Space] - full opensource release of a once closed source game, including vorbis sounds / music and theora videos!<br />
* [http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ Simon Tatham's Portable Puzzle Collection] is a collection of one-player puzzle games.<br />
* [http://ufo2000.sourceforge.net/ UFO2000] is free and opensource turn based tactical squad simulation multiplayer game.<br />
* [http://www.unvanquished.net/ Unvanquished] - Fork of Tremulous that is getting active development. Probably requires [https://github.com/Unvanquished/Unvanquished/issues/306 this NaCl issue to be resolved first...] and also depends on librocket (unpackaged).<br />
* [http://dangerdeep.sourceforge.net danger from the deep] 3d submarine simulation<br />
* [http://zero-k.info/ Zero-K] free, multiplatform, open-source RTS game based on the Spring engine<br />
* [https://andrettin.github.io/ Wyrmsun] A strategy game which features elements of mythology, history and fiction.<br />
* [http://te4.org/ Tales of Maj'Eyal] Tales of Maj'Eyal (ToME) is a free, open source roguelike RPG, featuring tactical turn-based combat and advanced character building. Play as one of many unique races and classes in the lore-filled world of Eyal, exploring random dungeons, facing challenging battles, and developing characters with your own tailored mix of abilities and powers.<br />
* [https://violetland.github.io/ Violetland] In this game the player should help a girl by name of Violet to struggle with hordes of monsters. For this purpose the various weapon, and also the special abilities of the heroine which are opening with experience can be used. In game there are elements of RPG in the form of strength-agility-vitality and derivatives. Also there is an unique feature: dynamic change of day and night.<br />
* [http://jag.xlabsoft.com/index.php Jag] Simple puzzle game<br />
* [http://www.zeroballistics.com/ Zero Ballistics] Zero Ballistics is a unique blend of first person shooter and tank combat, focusing on multiplayer gaming exclusively.<br />
* [http://pipewalker.sourceforge.net/ PipeWalker] This is a puzzle game in which you need to combine the components into a single circuit:connect all computers to a network server, bring water to the taps, etc.<br />
* [http://triplea.sourceforge.net/mywiki TripleA] TripleA is a turn based strategy game and board game engine, similar to Axis & Allies or Risk. Free to play online<br />
* [https://sourceforge.net/projects/bloodfrontier/ Blood Frontier] Blood Frontier was a single-player and multi-player first-person shooter game, built as a total conversion of Cube Engine 2 (Sauerbraten).<br />
* [https://rigsofrods.github.io/en/ Rigs of Rods] Rigs of Rods is a sandbox-style vehicle simulator.<br />
* [https://github.com/SimHacker/micropolis Micropolis] Micropolis is one of the oldest and grandest of city simulation games.<br />
* [https://www.lcdf.org/xmahjongg/ Xmahjongg] Xmahjongg is a simple implementation of the popular solitaire Mah Jongg game. The object is to remove all 144 tiles from the playing area by matching them two at a time. Xmahjongg is the classical version with little in the way of requirements and enough aesthetical and gameplay features to provide hours and hours of fun.<br />
* [http://spring1944.net/ Spring 1944] Spring:1944 is a WWII themed game based on the open source Spring Engine. Our goal is to create four fully functional sides (US, Germany, USSR, Britain) with period-accurate units and strengths. Realism is a primary design goal, second only to creating a game that is fun and accessible to play.<br />
* [http://freeminer.org/ Freeminer] Freeminer is a Minecraft-inspired sandbox game.<br />
* [http://www.terminal-overload.org/ Terminal Overload] Free and open-source first person shooter / spiritual successor to Revenge Of The Cats: Ethernet<br />
* [https://sourceforge.net/projects/nimuh/ Nimuh] Nimuh is a project puzzle game destined to improve the knowledge of Andalusia.<br />
* [https://launchpad.net/battleship battleship] You play versus a computer controlled opponent.Instead of firing blindly you get hints about the enemy's ships' positions.<br />
* [https://github.com/freegish/freegish Freegish] A free version of the game Gish<br />
* [http://www.braingames.getput.com/mog/ Maze of Galious] A very addictive game where you have to kill thousands of enemies, collect items in order to obtain new powers and defeat some really great demons at the end of each level<br />
* [http://toycars.sourceforge.net/Welcome.html Toy Cars] Toy Cars is a physics based 2-D racer.<br />
* [https://github.com/jazztickets/choria choria] An MMORPG that's all about grinding and doing chores.<br />
* [http://megamek.info/ MegaMek] MegaMek is an unofficial, online version of the Classic BattleTech board game. MegaMek is open source, free software. It is licenced under the GPL.<br />
* [http://zod.sourceforge.net/ Zod] Zod Engine is a remake of the 1996 classic game by Bitmap Brothers called Z. Z is a capture the flag style RTS. In this game you command robots and vehicles with the purpose of destroying the enemy's fort.<br />
* [https://github.com/xiaoyong/2048-Qt 2048-Qt] The 2048 Game implemented in Qt<br />
* [http://stuntrally.tuxfamily.org/ StuntRally] Stunt Rally game with Track Editor, based on VDrift and OGRE.<br />
* [http://bombermaaan.sourceforge.net/ bombermaaan] A classic Bomberman game with multiplayer support, cloned on original SNES games. Also similar to Dynablaster.<br />
* [http://trainsportedgame.no-ip.org/index.php trainspoted] TrAInsported is a game about trains, Artificial Intelligence and lots and lots of passengers.<br />
* [http://goatattack.net/ goatattack] Probably the best game involving goats and shotguns!<br />
* [http://7kfans.com/ Seven kingdoms, Ancient Adversaries] RTS game in a medieval world. Opensourced since 2009 under GPL (without some music and translations).<br />
* [http://en.cataclysmdda.com/ Cataclysm: Dark Days Ahead] Terminal-based post-apocalyptic survival game.<br />
* [https://github.com/Rescator7/Hearts Hearts] The card game Hearts for Qt 5 and liballegro 5 (for sound support). (We have not had a Hearts game in Fedora since gnome-hearts was dropped as part of the Python 2 removal. This one is actively maintained, in C++, with AI and online/offline modes. See also [https://github.com/Rescator7/Hearts.server Hearts.server]. '''Warning:''' <code>backgrounds/*.jpg</code> added in 1.8 are under the [https://unsplash.com/license Unsplash license] (non-free?). The other [https://github.com/Rescator7/Hearts/blob/master/Credits artwork licenses] are free: GNU GPL, GNU LGPL, CC-BY-SA, CC-BY, CC0.)<br />
<br />
== Tools ==<br />
* [https://github.com/aseprite-gpl/aseprite aseprite] - sprite editor tool. Originally GPLv2, upstream recently made proprietary, this is a fork to continue the FOSS version.<br />
* [https://github.com/TTimo/doom3.gpl Doom3] - now opensourced! (GPLv3)<br />
* [http://fuego.sourceforge.net/ Fuego] - Text based (GTP) Go player using Monte-Carlo tree search. Best together with GoGui.<br />
* [http://gogui.sourceforge.net/ GoGui] is a graphical user interface to programs that play the board game Go and support the Go Text Protocol, such as gnugo and Fuego.<br />
* [http://disenchant.net/engine.html tyrquake] - Conservative Quake 1 engine ([http://cachalot.mine.nu/10/SRPMS/ initial SRPM], needs desktop entry/icon, integration with autodownloader for data files)<br />
* [http://dev.ryzom.com/ ryzom] free 3d mmorpg client/server<br />
* [https://godotengine.org/ Godot Engine] free 2d/3d game engine<br />
<br />
= Games with Dead upstream or other issues=<br />
<br />
The packaging of the following games is not recommended. The packager should be able to fix any reported bugs. In some cases upstreaming them may not possible so a lot of downstream patches will have to be included in the package, revival or forks of the projects are other options. These also probably include half of the games in our wishlist at the moment.<br />
<br />
<br />
* [http://automanic.sourceforge.net/ automaniac] - 3d car deathmatch game <br />
** Last Release: August 2006<br />
** Last Commit: July 2008<br />
<br />
* [http://user.cs.tu-berlin.de/~kunegis/babychess/ BabyChess]<br />
** Last Release: March 2005<br />
<br />
* [http://antargis.berlios.de/ Battles of Antargis] - goodlooking free RTS '''Upstream is not dead, but it's not very active'''<br />
** Last Release: December 2007<br />
** Last Commit: July 2009<br />
<br />
* [http://www.bloodmasters.com/ Bloodmasters] - Arcade, oldschool multiplayer and bloodshed.That's what the game Bloodmasters is about. Play with friends on your LAN or online and experience this oldschool top-down shooter. The game supports Deathmatch, Team Deathmatch, Capture The Flag and Scavenger game modes. The game is completely freeware and without ads, spyware or other unwanted garbage. <br />
** Last Release: February 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://www.biniax.com/ Biniax-2] puzzle game with higly original game mechanics (will need to be patched to look for datas elsewhere than beside the binary, preliminary spec [http://www.bachelot.org/fedora/SPECS/biniax2.spec here], feel free to grab)<br />
** Last Release: '''v1.30 released in May 2009'''<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://bilious.homelinux.org/~paxed/brickshooter/ brickshooter] - puzzle game <br />
** Last Release: May 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://web.archive.org/web/20050305231257/www.swoogan.com/clanship.html ClanShip] - battleship game ([http://www.sourcefiles.org/Games/Strategy/Warfare/Battleships/ClanShip-1.0.5f.zip source])<br />
** Dead Upstream<br />
* [http://dungeonhack.sourceforge.net Dungeonhack] - Ambitious RPG that never got past a minimal demo state.<br />
** Dead Upstream<br />
<br />
* [http://gnukem.sourceforge.net/ Dave Gnukem] - platform game inspired by Duke Nukem 1 (might be too similar)<br />
** Last Release: August 2004<br />
** Is this fully GPLv2+ and only?<br />
<br />
* [http://sourceforge.net/projects/gillo gillo] is a two player game in a 3D ellipsoid playground<br />
** Last Release: July 2005<br />
* [http://www.tweeler.com/goollie_linux.html Go Ollie] Nice platform game using TuxCap<br />
** Last Release: '''June 2009 - Upstream active'''<br />
** Last Commit: ''No public VCS'' <br />
** ''May not compile on x86_64'' '''No longer true. It compile fine under x64_64 with TuxCap 1.4.0.'''<br />
<br />
* [http://jvgs.sourceforge.net/ JVGS] - a "minimalistic platform game" with elements based on [http://xkcd.com/ xkcd]. Music is non-commercial use only, [https://bugzilla.redhat.com/show_bug.cgi?id=914798 closed pkg review]<br />
<br />
* [http://kraptor.sourceforge.net/ Kraptor] is a classic shoot 'em up scroller game, where you must fight against tons of bad dudes (will need to be rebranded, raptor is a trademark for a very similar game).<br />
** Last Release: April 2004<br />
<br />
* [http://kursk.sourceforge.net/newfiles/Projects.htm Operation Citadel] - Operation Citadel is a WWII, turn based platoon, company level war game on the Eastern Front. The game is somewhere in between CLose Combat® and Steel Panthers®.<br />
** Last Release: ''Unknown. Seems old''<br />
** Last Commit: ''No public VCS'' <br />
** ''source is distribute as MSVC 6.0 project, I guess it will not compile, upstream seems dead''<br />
<br />
* [http://openquartz.sourceforge.net/ Open Quartz] Free GPL data combined with the Quake 1 GPL engine <br />
** Last Release: Aug 2004<br />
<br />
* [http://openraider.sourceforge.net/ Open Raider]. Not sure if it'd qualify, but it's a Tomb Raider clone.<br />
** Last Commit: 2004<br />
<br />
* [http://gnomefiles.org/app.php/Peg_Solitaire Peg Solitaire] - A simple peg-jumping game similar to Hi-Q. No idea if Hi-Q has trademark protection. <br />
** Last Release: Jan 2008<br />
<br />
* [http://race.sourceforge.net Race] - 3D top view racing game <br />
** Last Release: Jan 2003<br />
<br />
* [http://joey101.net/snowballz/ Snowballz] - fun RTS game (with penguins!) [https://bugzilla.redhat.com/show_bug.cgi?id=458598 Review Request (cancelled)]<br />
<br />
* [http://www.braingames.getput.com/stransball2/default.asp Super Transball 2] <br />
** Last Release: 2005<br />
<br />
* [http://tuxfootball.sourceforge.net/ tux-football] - 2d soccer game<br />
** Last Release: Nov 2004<br />
<br />
* [http://jasonwoof.org/vor VoR] - Dodge rocks until you die. "it's fast-paced, difficult and addictive." -- Linux Format <br />
** ''Deesn't seem active I may be wrong''<br />
<br />
* [http://wolfsinger.com/~wolfpack/XShipWars/ XShipWars] A 2d Multiplayer Space battle game.<br />
** ''Uses ESD, so it needs to be cleaned up for PulseAudio compatibility or would need to also package developers own YIFF Sound System, http://freshmeat.net/projects/yiff and their own JSW joystick support program, http://freshmeat.net/projects/libjsw'' <br />
** ''Upstream doesn't seem active''<br />
* [http://zatacka.sourceforge.net/ Zatacka] - arcade multiplayer game for 2-6 players on one keyboard <br />
** Last Release: 2007<br />
** Last Commit: Oct 2007<br />
** [https://bugzilla.redhat.com/show_bug.cgi?id=494557 Review request]<br />
<br />
<br />
== References ==<br />
<br />
* http://wiki.debian.org/Games/Suggested<br />
<br />
[[Category:Wishlist]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=SIGs/Games/WishList&diff=600009SIGs/Games/WishList2021-01-10T23:18:59Z<p>Kkofler: /* Games */ Add Hearts.</p>
<hr />
<div>= ROADMAP =<br />
Scratchpad of ideas for reviving Fedora Games SIG<br />
<br />
== General Goals / Objectives ==<br />
<br />
* Bringing more games into Fedora to support it as an ideal distribution for gaming with free and open source software (Four Foundations: Freedom, Features, First)<br />
<br />
* Supporting developer libraries / tools for creating games and making it easier for game developers to create and make the existance of these libraries more apparently to onlooking developers.<br />
<br />
* Trying to create collaboration between projects, and promote sharing of the projects where possible (be it assets, developer time) to take advantage of the tenets and spirit of free software.<br />
<br />
== Short-term vision ==<br />
<br />
* We should set up some projects we actively cover and endorse and give support to. And projects can apply to achieve the status of our endorsement, we should have requirements that these projects must adhere to.<br />
<br />
* Identifying lists of FOSS games public and well-known, seeing if we can package and get them into the distribution<br />
<br />
* Create resources for game developers who are looking to get started with Fedora (e.g. "How to game dev with Fedora")<br />
<br />
* Create an area where community members can post articles that they found helpful with their game (like my VLC playlist idea)<br />
<br />
* Create criteria for what we deem acceptable (the FSF free software definition would work for this) in terms of software. And Free Culture licesnes according to the Creative Commons people.<br />
<br />
== Long-term vision ==<br />
<br />
* To create a movement to endorse, encourage, support, and hold social solidarity with projects and aspiring individuals who are commited to user freedom.<br />
<br />
* Improved communication and visibility of existing resources for anyone wanting to create games for Fedora<br />
<br />
* "Quick" place to look for information, clearly visible, in more places than just a wiki page<br />
<br />
* Demonstrate the capabilities of free and open source gaming and its advancements with Fedora<br />
<br />
== Next steps for moving forward ==<br />
<br />
* Grow interest with the SIG, gain new members, build up membership by explaining what our objectives our and sharing that across the project (see: Community Blog, even Fedora Magazine, maybe)<br />
<br />
* Begin working on some of the short-term vision items<br />
<br />
* Setting up a weekly or every other week meeting time for the SIG may be useful to coordinate time to discuss and work on objectives. I have a mumble server, but perhaps someone would be willing to give us a server for this purpose.<br />
<br />
* Good opportunity to address questions like gathering resources (where are they? where do we put them? how are they communicated to a wider audience? – this isn't libraries / tools, per say, but resources for getting access to those tools)<br />
<br />
<br />
== Other details / notes ==<br />
<br />
* We should be as inclusive of other people as possible, even when individuals have opinions that are deemed unpopular.<br />
<br />
* Try to get people to collaborate more often, and remove unneeded fragmentation between projects (try to unify the workforce)<br />
<br />
* But to do this we need to create an environment where someone can show up, tell us what kind of game they want to be involved with and we can get them to a person involved in that project as soon as possible.<br />
<br />
* Reaching out to certain software projects (either games or resources for game developers) and querying their interest for packaging Fedora (working closely with upstream should always be a priority) (e.g.engines such as https://godotengine.org/ which are not currently packaged)<br />
<br />
= Fedora Games WishList =<br />
<br />
== Games ==<br />
* [http://www.blackvoxel.com/ Blackvoxel] - a new sandbox game based on a voxel engine PENDING ON FREE ASSETS<br />
* [http://crrcsim.berlios.de/wiki/ CRRCsim] - rc model flight simulator (GPL)<br />
* [http://www.freeorion.org/ freeorion] - moo rewrite<br />
* [http://selectparks.net/~julian/levelhead/ levelhead] - Augmented Reality logic game using webcam and printed out cubes. Check out video: [http://www.youtube.com/watch?v=dsb76pva4s4 youtube]<br />
* [https://github.com/nikki-and-the-robots/nikki Nikki and the Robots] - Cute non-violent gameplay with wall-jumping and remote robot controlling<br />
* [http://www.oolite.org/ oolite] - elite remake - under [https://bugzilla.redhat.com/show_bug.cgi?id=459211 review]<br />
* [http://repo.or.cz/w/pachi.git Pachi] - Strong text based (GTP) Go player. Best together with GoGui.<br />
* [http://pathological.sourceforge.net/ Pathological] - Marble Puzzle Game<br />
* [http://paxbritannica.henk.ca/ pax-britannica] - one-button real-time strategy game<br />
* [http://sourceforge.net/projects/raceintospace Race into Space] - full opensource release of a once closed source game, including vorbis sounds / music and theora videos!<br />
* [http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ Simon Tatham's Portable Puzzle Collection] is a collection of one-player puzzle games.<br />
* [http://ufo2000.sourceforge.net/ UFO2000] is free and opensource turn based tactical squad simulation multiplayer game.<br />
* [http://www.unvanquished.net/ Unvanquished] - Fork of Tremulous that is getting active development. Probably requires [https://github.com/Unvanquished/Unvanquished/issues/306 this NaCl issue to be resolved first...] and also depends on librocket (unpackaged).<br />
* [http://dangerdeep.sourceforge.net danger from the deep] 3d submarine simulation<br />
* [http://zero-k.info/ Zero-K] free, multiplatform, open-source RTS game based on the Spring engine<br />
* [https://andrettin.github.io/ Wyrmsun] A strategy game which features elements of mythology, history and fiction.<br />
* [http://te4.org/ Tales of Maj'Eyal] Tales of Maj'Eyal (ToME) is a free, open source roguelike RPG, featuring tactical turn-based combat and advanced character building. Play as one of many unique races and classes in the lore-filled world of Eyal, exploring random dungeons, facing challenging battles, and developing characters with your own tailored mix of abilities and powers.<br />
* [https://violetland.github.io/ Violetland] In this game the player should help a girl by name of Violet to struggle with hordes of monsters. For this purpose the various weapon, and also the special abilities of the heroine which are opening with experience can be used. In game there are elements of RPG in the form of strength-agility-vitality and derivatives. Also there is an unique feature: dynamic change of day and night.<br />
* [http://jag.xlabsoft.com/index.php Jag] Simple puzzle game<br />
* [http://www.zeroballistics.com/ Zero Ballistics] Zero Ballistics is a unique blend of first person shooter and tank combat, focusing on multiplayer gaming exclusively.<br />
* [http://pipewalker.sourceforge.net/ PipeWalker] This is a puzzle game in which you need to combine the components into a single circuit:connect all computers to a network server, bring water to the taps, etc.<br />
* [http://triplea.sourceforge.net/mywiki TripleA] TripleA is a turn based strategy game and board game engine, similar to Axis & Allies or Risk. Free to play online<br />
* [https://sourceforge.net/projects/bloodfrontier/ Blood Frontier] Blood Frontier was a single-player and multi-player first-person shooter game, built as a total conversion of Cube Engine 2 (Sauerbraten).<br />
* [https://rigsofrods.github.io/en/ Rigs of Rods] Rigs of Rods is a sandbox-style vehicle simulator.<br />
* [https://github.com/SimHacker/micropolis Micropolis] Micropolis is one of the oldest and grandest of city simulation games.<br />
* [https://www.lcdf.org/xmahjongg/ Xmahjongg] Xmahjongg is a simple implementation of the popular solitaire Mah Jongg game. The object is to remove all 144 tiles from the playing area by matching them two at a time. Xmahjongg is the classical version with little in the way of requirements and enough aesthetical and gameplay features to provide hours and hours of fun.<br />
* [http://spring1944.net/ Spring 1944] Spring:1944 is a WWII themed game based on the open source Spring Engine. Our goal is to create four fully functional sides (US, Germany, USSR, Britain) with period-accurate units and strengths. Realism is a primary design goal, second only to creating a game that is fun and accessible to play.<br />
* [http://freeminer.org/ Freeminer] Freeminer is a Minecraft-inspired sandbox game.<br />
* [http://www.terminal-overload.org/ Terminal Overload] Free and open-source first person shooter / spiritual successor to Revenge Of The Cats: Ethernet<br />
* [https://sourceforge.net/projects/nimuh/ Nimuh] Nimuh is a project puzzle game destined to improve the knowledge of Andalusia.<br />
* [https://launchpad.net/battleship battleship] You play versus a computer controlled opponent.Instead of firing blindly you get hints about the enemy's ships' positions.<br />
* [https://github.com/freegish/freegish Freegish] A free version of the game Gish<br />
* [http://www.braingames.getput.com/mog/ Maze of Galious] A very addictive game where you have to kill thousands of enemies, collect items in order to obtain new powers and defeat some really great demons at the end of each level<br />
* [http://toycars.sourceforge.net/Welcome.html Toy Cars] Toy Cars is a physics based 2-D racer.<br />
* [https://github.com/jazztickets/choria choria] An MMORPG that's all about grinding and doing chores.<br />
* [http://megamek.info/ MegaMek] MegaMek is an unofficial, online version of the Classic BattleTech board game. MegaMek is open source, free software. It is licenced under the GPL.<br />
* [http://zod.sourceforge.net/ Zod] Zod Engine is a remake of the 1996 classic game by Bitmap Brothers called Z. Z is a capture the flag style RTS. In this game you command robots and vehicles with the purpose of destroying the enemy's fort.<br />
* [https://github.com/xiaoyong/2048-Qt 2048-Qt] The 2048 Game implemented in Qt<br />
* [http://stuntrally.tuxfamily.org/ StuntRally] Stunt Rally game with Track Editor, based on VDrift and OGRE.<br />
* [http://bombermaaan.sourceforge.net/ bombermaaan] A classic Bomberman game with multiplayer support, cloned on original SNES games. Also similar to Dynablaster.<br />
* [http://trainsportedgame.no-ip.org/index.php trainspoted] TrAInsported is a game about trains, Artificial Intelligence and lots and lots of passengers.<br />
* [http://goatattack.net/ goatattack] Probably the best game involving goats and shotguns!<br />
* [http://7kfans.com/ Seven kingdoms, Ancient Adversaries] RTS game in a medieval world. Opensourced since 2009 under GPL (without some music and translations).<br />
* [http://en.cataclysmdda.com/ Cataclysm: Dark Days Ahead] Terminal-based post-apocalyptic survival game.<br />
* [https://github.com/Rescator7/Hearts Hearts] The card game Hearts for Qt 5 and liballegro 5 (for sound support). (We have not had a Hearts game in Fedora since gnome-hearts was dropped as part of the Python 2 removal. This one is actively maintained, in C++, with AI and online/offline modes. See also [https://github.com/Rescator7/Hearts.server Hearts.server].)<br />
<br />
== Tools ==<br />
* [https://github.com/aseprite-gpl/aseprite aseprite] - sprite editor tool. Originally GPLv2, upstream recently made proprietary, this is a fork to continue the FOSS version.<br />
* [https://github.com/TTimo/doom3.gpl Doom3] - now opensourced! (GPLv3)<br />
* [http://fuego.sourceforge.net/ Fuego] - Text based (GTP) Go player using Monte-Carlo tree search. Best together with GoGui.<br />
* [http://gogui.sourceforge.net/ GoGui] is a graphical user interface to programs that play the board game Go and support the Go Text Protocol, such as gnugo and Fuego.<br />
* [http://disenchant.net/engine.html tyrquake] - Conservative Quake 1 engine ([http://cachalot.mine.nu/10/SRPMS/ initial SRPM], needs desktop entry/icon, integration with autodownloader for data files)<br />
* [http://dev.ryzom.com/ ryzom] free 3d mmorpg client/server<br />
* [https://godotengine.org/ Godot Engine] free 2d/3d game engine<br />
<br />
= Games with Dead upstream or other issues=<br />
<br />
The packaging of the following games is not recommended. The packager should be able to fix any reported bugs. In some cases upstreaming them may not possible so a lot of downstream patches will have to be included in the package, revival or forks of the projects are other options. These also probably include half of the games in our wishlist at the moment.<br />
<br />
<br />
* [http://automanic.sourceforge.net/ automaniac] - 3d car deathmatch game <br />
** Last Release: August 2006<br />
** Last Commit: July 2008<br />
<br />
* [http://user.cs.tu-berlin.de/~kunegis/babychess/ BabyChess]<br />
** Last Release: March 2005<br />
<br />
* [http://antargis.berlios.de/ Battles of Antargis] - goodlooking free RTS '''Upstream is not dead, but it's not very active'''<br />
** Last Release: December 2007<br />
** Last Commit: July 2009<br />
<br />
* [http://www.bloodmasters.com/ Bloodmasters] - Arcade, oldschool multiplayer and bloodshed.That's what the game Bloodmasters is about. Play with friends on your LAN or online and experience this oldschool top-down shooter. The game supports Deathmatch, Team Deathmatch, Capture The Flag and Scavenger game modes. The game is completely freeware and without ads, spyware or other unwanted garbage. <br />
** Last Release: February 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://www.biniax.com/ Biniax-2] puzzle game with higly original game mechanics (will need to be patched to look for datas elsewhere than beside the binary, preliminary spec [http://www.bachelot.org/fedora/SPECS/biniax2.spec here], feel free to grab)<br />
** Last Release: '''v1.30 released in May 2009'''<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://bilious.homelinux.org/~paxed/brickshooter/ brickshooter] - puzzle game <br />
** Last Release: May 2008<br />
** Last Commit: ''No public VCS''<br />
<br />
* [http://web.archive.org/web/20050305231257/www.swoogan.com/clanship.html ClanShip] - battleship game ([http://www.sourcefiles.org/Games/Strategy/Warfare/Battleships/ClanShip-1.0.5f.zip source])<br />
** Dead Upstream<br />
* [http://dungeonhack.sourceforge.net Dungeonhack] - Ambitious RPG that never got past a minimal demo state.<br />
** Dead Upstream<br />
<br />
* [http://gnukem.sourceforge.net/ Dave Gnukem] - platform game inspired by Duke Nukem 1 (might be too similar)<br />
** Last Release: August 2004<br />
** Is this fully GPLv2+ and only?<br />
<br />
* [http://sourceforge.net/projects/gillo gillo] is a two player game in a 3D ellipsoid playground<br />
** Last Release: July 2005<br />
* [http://www.tweeler.com/goollie_linux.html Go Ollie] Nice platform game using TuxCap<br />
** Last Release: '''June 2009 - Upstream active'''<br />
** Last Commit: ''No public VCS'' <br />
** ''May not compile on x86_64'' '''No longer true. It compile fine under x64_64 with TuxCap 1.4.0.'''<br />
<br />
* [http://jvgs.sourceforge.net/ JVGS] - a "minimalistic platform game" with elements based on [http://xkcd.com/ xkcd]. Music is non-commercial use only, [https://bugzilla.redhat.com/show_bug.cgi?id=914798 closed pkg review]<br />
<br />
* [http://kraptor.sourceforge.net/ Kraptor] is a classic shoot 'em up scroller game, where you must fight against tons of bad dudes (will need to be rebranded, raptor is a trademark for a very similar game).<br />
** Last Release: April 2004<br />
<br />
* [http://kursk.sourceforge.net/newfiles/Projects.htm Operation Citadel] - Operation Citadel is a WWII, turn based platoon, company level war game on the Eastern Front. The game is somewhere in between CLose Combat® and Steel Panthers®.<br />
** Last Release: ''Unknown. Seems old''<br />
** Last Commit: ''No public VCS'' <br />
** ''source is distribute as MSVC 6.0 project, I guess it will not compile, upstream seems dead''<br />
<br />
* [http://openquartz.sourceforge.net/ Open Quartz] Free GPL data combined with the Quake 1 GPL engine <br />
** Last Release: Aug 2004<br />
<br />
* [http://openraider.sourceforge.net/ Open Raider]. Not sure if it'd qualify, but it's a Tomb Raider clone.<br />
** Last Commit: 2004<br />
<br />
* [http://gnomefiles.org/app.php/Peg_Solitaire Peg Solitaire] - A simple peg-jumping game similar to Hi-Q. No idea if Hi-Q has trademark protection. <br />
** Last Release: Jan 2008<br />
<br />
* [http://race.sourceforge.net Race] - 3D top view racing game <br />
** Last Release: Jan 2003<br />
<br />
* [http://joey101.net/snowballz/ Snowballz] - fun RTS game (with penguins!) [https://bugzilla.redhat.com/show_bug.cgi?id=458598 Review Request (cancelled)]<br />
<br />
* [http://www.braingames.getput.com/stransball2/default.asp Super Transball 2] <br />
** Last Release: 2005<br />
<br />
* [http://tuxfootball.sourceforge.net/ tux-football] - 2d soccer game<br />
** Last Release: Nov 2004<br />
<br />
* [http://jasonwoof.org/vor VoR] - Dodge rocks until you die. "it's fast-paced, difficult and addictive." -- Linux Format <br />
** ''Deesn't seem active I may be wrong''<br />
<br />
* [http://wolfsinger.com/~wolfpack/XShipWars/ XShipWars] A 2d Multiplayer Space battle game.<br />
** ''Uses ESD, so it needs to be cleaned up for PulseAudio compatibility or would need to also package developers own YIFF Sound System, http://freshmeat.net/projects/yiff and their own JSW joystick support program, http://freshmeat.net/projects/libjsw'' <br />
** ''Upstream doesn't seem active''<br />
* [http://zatacka.sourceforge.net/ Zatacka] - arcade multiplayer game for 2-6 players on one keyboard <br />
** Last Release: 2007<br />
** Last Commit: Oct 2007<br />
** [https://bugzilla.redhat.com/show_bug.cgi?id=494557 Review request]<br />
<br />
<br />
== References ==<br />
<br />
* http://wiki.debian.org/Games/Suggested<br />
<br />
[[Category:Wishlist]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=593314User:Smani/QtwebkitRemoval2020-11-06T19:09:40Z<p>Kkofler: /* Scope */ Remove kwooty from the list of packages to retire, it does not depend on QtWebKit, only on kde-workspace-libs, which we should be able to keep.</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kde-workspace<br />
=> Can be patched to compile without kdelibs-webkit support, it has been done by RHEL.<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Build against QTextBrowser instead, which is supported as a fallback. This will degrade rendering quality, but it is better than dropping the package entirely.<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop the demos that depend on QtWebKit (or the entire subpackage)<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackage<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop the examples that depend on QtWebKit (or the entire subpackage)<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Subpackage of the Plasma 4 Public Transport applet (kde-plasma-publictransport), last activity in 2013. Retire.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be modified to disable QtWebKit support:<br />
* kde-runtime-libs<br />
* kde-workspace<br />
* kdepim4 (knode-libs)<br />
* krecipes<br />
* qt-assistant<br />
* qt-demos<br />
* qt-examples<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kde-plasma-publictransport (timetablemate)<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator (qtscriptbindings)<br />
* rekonq<br />
<br />
The following subpackages will be removed, and obsoleted by the corresponding main package:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-designer-plugin-webkit<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=593313User:Smani/QtwebkitRemoval2020-11-06T19:08:10Z<p>Kkofler: /* Scope */ Update to match the changes in Detailed Description, and to obsolete subpackages from the main package (no need to use fedora-obsolete-packages).</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kde-workspace<br />
=> Can be patched to compile without kdelibs-webkit support, it has been done by RHEL.<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Build against QTextBrowser instead, which is supported as a fallback. This will degrade rendering quality, but it is better than dropping the package entirely.<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop the demos that depend on QtWebKit (or the entire subpackage)<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackage<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop the examples that depend on QtWebKit (or the entire subpackage)<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Subpackage of the Plasma 4 Public Transport applet (kde-plasma-publictransport), last activity in 2013. Retire.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be modified to disable QtWebKit support:<br />
* kde-runtime-libs<br />
* kde-workspace<br />
* kdepim4 (knode-libs)<br />
* krecipes<br />
* qt-assistant<br />
* qt-demos<br />
* qt-examples<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kde-plasma-publictransport (timetablemate)<br />
* kwooty<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator (qtscriptbindings)<br />
* rekonq<br />
<br />
The following subpackages will be removed, and obsoleted by the corresponding main package:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-designer-plugin-webkit<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=593312User:Smani/QtwebkitRemoval2020-11-06T19:04:53Z<p>Kkofler: /* Detailed Description */ Remove separate entry for ksysguard-libs (kde-workspace subpackage).</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kde-workspace<br />
=> Can be patched to compile without kdelibs-webkit support, it has been done by RHEL.<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Build against QTextBrowser instead, which is supported as a fallback. This will degrade rendering quality, but it is better than dropping the package entirely.<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop the demos that depend on QtWebKit (or the entire subpackage)<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackage<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop the examples that depend on QtWebKit (or the entire subpackage)<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Subpackage of the Plasma 4 Public Transport applet (kde-plasma-publictransport), last activity in 2013. Retire.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kdepim4<br />
* krecipes<br />
* kwooty<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator<br />
* rekonq<br />
* timetablemate<br />
<br />
The following subpackages will be removed, and added to fedora-obsolete-packages:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-assistant<br />
* qt-demos<br />
* qt-designer-plugin-webkit<br />
* qt-examples<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=593307User:Smani/QtwebkitRemoval2020-11-06T18:19:03Z<p>Kkofler: /* Detailed Description */ Clarify timetablemate. (This one should be OK to drop, because it's a subpackage of a Plasma 4 (!), not 5, applet.)</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kde-workspace<br />
=> Can be patched to compile without kdelibs-webkit support, it has been done by RHEL.<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* ksysguard-libs-1:4.11.22-28.fc33.x86_64<br />
=> Part of kde-workspace, see below.<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Build against QTextBrowser instead, which is supported as a fallback. This will degrade rendering quality, but it is better than dropping the package entirely.<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop the demos that depend on QtWebKit (or the entire subpackage)<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackage<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop the examples that depend on QtWebKit (or the entire subpackage)<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Subpackage of the Plasma 4 Public Transport applet (kde-plasma-publictransport), last activity in 2013. Retire.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kdepim4<br />
* krecipes<br />
* kwooty<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator<br />
* rekonq<br />
* timetablemate<br />
<br />
The following subpackages will be removed, and added to fedora-obsolete-packages:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-assistant<br />
* qt-demos<br />
* qt-designer-plugin-webkit<br />
* qt-examples<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=593306User:Smani/QtwebkitRemoval2020-11-06T18:16:15Z<p>Kkofler: /* Detailed Description */ Update Qt 4 subpackages.</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kde-workspace<br />
=> Can be patched to compile without kdelibs-webkit support, it has been done by RHEL.<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* ksysguard-libs-1:4.11.22-28.fc33.x86_64<br />
=> Part of kde-workspace, see below.<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Build against QTextBrowser instead, which is supported as a fallback. This will degrade rendering quality, but it is better than dropping the package entirely.<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop the demos that depend on QtWebKit (or the entire subpackage)<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackage<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop the examples that depend on QtWebKit (or the entire subpackage)<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Plasma 5 applet, last activity in 2013. Retire.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kdepim4<br />
* krecipes<br />
* kwooty<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator<br />
* rekonq<br />
* timetablemate<br />
<br />
The following subpackages will be removed, and added to fedora-obsolete-packages:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-assistant<br />
* qt-demos<br />
* qt-designer-plugin-webkit<br />
* qt-examples<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=593275User:Smani/QtwebkitRemoval2020-11-06T11:57:37Z<p>Kkofler: /* Detailed Description */ We do not want to retire kde-workspace, either.</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kde-workspace<br />
=> Can be patched to compile without kdelibs-webkit support, it has been done by RHEL.<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* ksysguard-libs-1:4.11.22-28.fc33.x86_64<br />
=> Part of kde-workspace, which can be retired, see below.<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Plasma 5 applet, last activity in 2013. Retire.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kdepim4<br />
* krecipes<br />
* kwooty<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator<br />
* rekonq<br />
* timetablemate<br />
<br />
The following subpackages will be removed, and added to fedora-obsolete-packages:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-assistant<br />
* qt-demos<br />
* qt-designer-plugin-webkit<br />
* qt-examples<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Smani/QtwebkitRemoval&diff=593273User:Smani/QtwebkitRemoval2020-11-06T11:49:15Z<p>Kkofler: Add some information about individual packages.</p>
<hr />
<div>= Qtwebkit removal =<br />
<br />
== Summary ==<br />
Qtwebkit (qt4 era package) is dead upstream, and has hundreds of known CVEs. Also, it requires qt-location, which does not build against current proj versions. It's time to remove qtwebkit from the distribution. See also [https://bugzilla.redhat.com/show_bug.cgi?id=1711519 #1711519]<br />
<br />
== Owner ==<br />
* Name: [[User:smani| Sandro Mani]]<br />
* Email: manisandro@gmail.com<br />
<br />
== Current status ==<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
[[Category:SystemWideChange]]<br />
<br />
* Targeted release: [[Releases/34 | Fedora 34 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
* FESCo issue: <will be assigned by the Wrangler><br />
* Tracker bug: <will be assigned by the Wrangler><br />
* Release notes tracker: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Here is a current list of packages depending on qtwebkit, and the relative proposals of how to deal with them:<br />
<br />
* amarok-0:2.9.0-9.fc33.x86_64<br />
=> Musicplayer. Switch to a current git master snapshot, which is KF5 based (https://invent.kde.org/multimedia/amarok)<br />
* arora-0:0.11.0-23.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* brewtarget-0:2.1.0-16.fc33.x86_64<br />
=> Upgrade to 2.3.0 release which supports Qt5 <br />
* gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64<br />
=> Drop subpackage<br />
* kde-runtime-libs-0:17.08.3-15.fc33.x86_64<br />
=> Can be compiled without kdelibs-webkit support<br />
* kdelibs-webkit-6:4.14.38-23.fc34.x86_64<br />
=> Drop subpackage<br />
* knode-libs-0:4.14.10-44.fc33.x86_64<br />
=> Required by knode, an newsreading application, part of kdepim4. It should be possible to build kdepim4 with QTextBrowser as the HTML viewer instead (KDEPIM_NO_WEBKIT CMake flag), we need to give this a try. Retiring kdepim4 is not an option because there is no replacement for KNode.<br />
* krecipes-0:2.1.0-12.fc33.x86_64<br />
=> Recipes application, dead upstream. This one uses mainly KHTML. The QtWebKit dependency is used only in a workaround for printing because KHTML has bugs with printing. We can either drop the workaround, or find another workaround, or disable printing entirely. There is no replacement, and the QtWebKit dependency can be dropped, so we should not retire this package. See [https://bugzilla.redhat.com/show_bug.cgi?id=1711519#c12].<br />
* ksysguard-libs-1:4.11.22-28.fc33.x86_64<br />
=> Part of kde-workspace, which can be retired, see below.<br />
* libkfbapi-0:1.0-16.fc32.x86_64<br />
=> Leaf, retire<br />
* python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64<br />
=> Leaf, retire<br />
* qlandkartegt-0:1.8.1-28.fc33.x86_64<br />
=> Retire<br />
* qmc2-0:0.195-14.fc34.x86_64<br />
=> Latest trunk supports Qt5<br />
* qt-assistant-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt-demos-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt-examples-1:4.8.7-57.fc34.x86_64<br />
=> Drop subpackae<br />
* qt4pas-0:2.5-21.fc33.x86_64<br />
=> Leaf, retire<br />
* qtscriptbindings-0:0.2.0-23.fc33.x86_64<br />
=> Part of qtscriptgenerator, Only required by amarok. Retire.<br />
* rekonq-0:2.4.2-17.fc33.x86_64<br />
=> Browser. Retire, no-one should be using this considering the CVEs in qtwebkit. Users should use a QtWebEngine browser such as Falkon instead. Obsoletes can be added to the falkon package.<br />
* timetablemate-0:0.10-0.24.20111204git.fc32.x86_64 <br />
=> Plasma 5 applet, last activity in 2013. Retire.<br />
<br />
kde-workspace:<br />
* kcm_colors-4.11.22-28.fc33.x86_64<br />
=> Obsolete KDE4 desktop component<br />
* kde-platform-plugin-4.11.22-28.fc33.x86_64<br />
=> Obsolete KDE4 desktop component<br />
* kde-workspace-devel-4.11.22-28.fc33.x86_64<br />
=> Leaf<br />
* kdm-4.11.22-28.fc33.x86_64<br />
=> Leaf, obsolete<br />
* kgreeter-plugins<br />
=> Obsolete KDE4 desktop component<br />
* ksysguard-libs<br />
=> Only required by kde-workspace-devel<br />
* ksystraycmd<br />
=> Obsolete KDE4 desktop component<br />
* libkworkspace<br />
=> Required by kwooty "Kwooty is a NZB usenet binary download application for KDE 4", which is dead since 2018.<br />
<br />
== Feedback ==<br />
<br />
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --><br />
<br />
== Benefit to Fedora ==<br />
<br />
Removal obsolete and insecure packages<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
The following packages will be updated:<br />
* amarok: latest git<br />
* brewtarget: 2.3.0<br />
* qmc2: latest trunk<br />
<br />
The following packages will be retired:<br />
* arora<br />
* kdepim4<br />
* krecipes<br />
* kwooty<br />
* libkfbapi<br />
* qlandkartegt<br />
* qt4pas<br />
* qtscriptgenerator<br />
* rekonq<br />
* timetablemate<br />
<br />
The following subpackages will be removed, and added to fedora-obsolete-packages:<br />
* gambas3-gb-qt4-webkit<br />
* kdelibs-webkit<br />
* qt-assistant<br />
* qt-demos<br />
* qt-designer-plugin-webkit<br />
* qt-examples<br />
<br />
* Other developers:<br />
No work should be needed from other developers.<br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed)<br />
<br />
* Policies and guidelines:<br />
No policy or guidelines updates necessary.<br />
<br />
== Upgrade/compatibility impact ==<br />
Retired subpackages will be obsoleted by fedora-obsolete-packages. Others will remain as leafs.<br />
<br />
== How To Test ==<br />
Nothing to test really, packages will just disappear.<br />
<br />
== User Experience ==<br />
Some old applications will disappear.<br />
<br />
== Dependencies ==<br />
See above.<br />
<br />
== Contingency Plan ==<br />
None.<br />
<br />
== Release Notes ==<br />
Fedora 34 will drop the unmaintained and insecure qtwebkit package.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Talk:Changes//x86-64_micro-architecture_update&diff=548416Talk:Changes//x86-64 micro-architecture update2019-07-22T21:35:50Z<p>Kkofler: Add a comment.</p>
<hr />
<div>I don't think this stands a chance in hell. It's hard enough convincing people we can live without i686; "we're gonna make Fedora stop working with all CPUs made before 2013" has zero chance whatsoever. [[User:Adamwill|Adamwill]] ([[User talk:Adamwill|talk]])<br />
: In fact, even some CPU made in 2013. I have a server (in a DC) with a Intel Atom® Processor C233, who was launched in [https://ark.intel.com/content/www/us/en/ark/products/77976/intel-atom-processor-c2338-1m-cache-1-70-ghz.html|Q3 2013], avx2 is not supported (and the server was installed 2 or 3 years ago). --[[User:Misc|Misc]] ([[User talk:Misc|talk]]) 17:42, 15 July 2019 (UTC)<br />
::I'm going to go out on a limb here and say that unless this optimization is done as a runtime function switch (if AVX2 is present it uses an AVX2 optimized function, and if not it uses an older slower but compatible function. I believe there's distros out there that can/are doing this), then this is a SERIOUS issue. As noted above things like Atom CPUs (and their ilk) have a tendency to resurrect old micro-architectures and put them on new processes which improves them greatly, but won't include that functionality, as well as actively trying to throw away a lot of still very usable hardware (even ~2011 hardware is still very usable for many applications). --[[User:warthog9|warthog9]] ([[User talk:warthog9|talk]])<br />
<br />
== Concerns around AVX2 requirement ==<br />
<br />
Over the next few years, there will be a growing number of alternative implementations of x86 available, many without AVX2 support. It seems to be highly premature, then, to mandate AVX2 as the minimum requirement, especially without evidence of a performance improvement or data showing number of impacted users (presumably quite large). This is a premature change. Premature by about 5-10 years in my own opinion, but that is debatable.<br />
<br />
== Unacceptable ==<br />
<br />
This is absolutely unacceptable and would force me to look for a new distribution. Not even my Sandy Bridge Core i7 supports AVX2, not to mention my Core 2 Duo notebook that still runs Fedora perfectly fine right now. Sure, the notebook is 11 years old and the desktop 8 years, but those machines work perfectly fine and the desktop doesn't even perform that badly. '''If I have to choose between replacing the computers or replacing the distribution, my choice will be made fairly quickly.'''<br />
<br />
My desktop's CPU only supports AVX 1, my notebook's CPU only up to SSSE3 (no SSE4 nor AVX).<br />
<br />
[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/5JQ7NOKYJVGZO6ZYGUZQ3H5ME72Y6LTX/ Read more… (on the devel mailing list)]<br />
<br />
--[[User:Kkofler|Kkofler]] ([[User talk:Kkofler|talk]]) 21:35, 22 July 2019 (UTC)</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/MySQL_8&diff=531399Changes/MySQL 82019-01-06T00:35:24Z<p>Kkofler: Mention that a libmysqld is provided by MariaDB.</p>
<hr />
<div>= MySQL 8 =<br />
<br />
== Summary ==<br />
Update of MySQL ( community-mysql package) in Fedora from 5.7 to 8.0 version.<br />
<br />
== Owner ==<br />
* Name: [[User:mschorm| Michal Schorm]]<br />
* Email: mschorm@redhat.com<br />
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/29 | Fedora 29 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1582618 #1582618]<br />
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/174 #174]<br />
<br />
== Detailed Description ==<br />
<br />
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --><br />
<br />
Update of MySQL package in Fedora from 5.7 version to 8.0 version.<br />
<br />
== Benefit to Fedora ==<br />
<br />
I'm cooperating with the upstream to bring the latest stable software to Fedora users.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
**Release MySQL 8.0.11 to Rawhide (done)<br />
**Check software that requires community-mysql package (done, only mysql-connector-odbc)<br />
**Gather user input on the changes between mysql 5.7 and 8.0<br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: [https://pagure.io/releng/issue/7486 Releng issue number 7486] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. <br />
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
<br />
The 'libmysqld' embedded server library has been removed by upstream. (Though, applications requiring 'libmysqld' can be (re)built against `mariadb-embedded-devel`, which Provides `mysql-embedded-devel` and ships a `libmysqld.so` symlink to `libmariadbd.so.*`.)<br />
<br />
Downgrade from MySQL 8 to MySQL 5.7 is not supported.<br />
<br />
== How To Test ==<br />
<br />
Usual testing as when upgrading between major MySQL versions.<br />
<br />
Test that all other software runs well with MySQL 8. Report any issues, so I can reach the different upstreams and check if they plan update their software to support MySQL 8 and when.<br />
<br />
== User Experience ==<br />
<br />
The users will have to migrate their applications and databases, if the y want to use MySQL 8.<br />
<br />
If the users want to stick with MySQL 5.7 for a little longer, I'm providing [https://copr.fedorainfracloud.org/coprs/mschorm/mysql-5.7/ COPR repo] with MySQL 5.7 built from f28 branch for Rawhide.<br />
<br />
Also, module with MySQL 5.7 is planned.<br />
<br />
== Dependencies ==<br />
mysql-connector-odbc<br />
*also maintained by me<br />
*currently FTBFS against the MySQL 8.0.11, working on the fix. However for MariaDB there is mariadb-connector-odbc, so users don't depend on this piece of software.<br />
<br />
There may be more software, which does not support MySQL 8 yet. For such occurences, COPR repo with MySQL 5.7 was created.<br />
<br />
== Contingency Plan ==<br />
<br />
The COPR repository until F29 freeze seems enough to me. For F29, there should be a module available with MySQL 5.7 to cover users that can't / don't want to upgrade.<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: COPR and Module with MySQL 5.7 available<br />
* Contingency deadline: beta freeze<br />
* Blocks release? N/A (not a System Wide Change)<br />
* Blocks product? N/A (not a System Wide Change) <br />
<br />
== Documentation ==<br />
<br />
Upgrading and incompatibilities: https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html<br />
<br />
Upgrade startegy: https://dev.mysql.com/doc/refman/8.0/en/upgrading-strategies.html<br />
<br />
== Release Notes ==<br />
<br />
Release notes for each release: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/<br />
<br />
Overall overview of the changes in 8.0: https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html<br />
<br />
[[Category:ChangeAcceptedF29]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Astigmatic_Grand_Hotel_Fonts&diff=508812Astigmatic Grand Hotel Fonts2018-01-07T16:41:56Z<p>Kkofler: Call the font "script" rather than "cursive" because that's the term used elsewhere, and because this is an upright script font, so "cursive" might be confusing.</p>
<hr />
<div>{{CompactHeader|fonts-sig}}<br />
<br />
<br />
<!-- <br />
◆ Use this template to create « Name_Fonts » pages:<br />
— « Name_Fonts » should be « Foo_fonts » and not « FooFonts_fonts » or « FooFont_fonts ». <br />
— use the « Foundry Name » convention if necessary.<br />
⇒ See also Packaging:FontsPolicy#Naming we try to follow the same conventions for our wiki pages.<br />
◆ Please remove the « lorem ipsum » filers once they are no longer necessary. Do the same for those comments.<br />
◆ Do not forget to update the page categorization each time the font described in this page passes one packaging step.<br />
--><br />
<br />
''Display sans-serif fonts''<br />
<br />
<!--<br />
◆ Requester: replace the preceding line with a package summary proposal. For example: A decorative font inspired from xxx.<br />
◆ Packager: correct the proposal and replace it with the final package summary.<br />
--><br />
<br />
<br />
== Description ==<br />
A condensed script (handwriting) font created by Brian J. Bonislawsky and Jim Lyles DBA [http://www.astigmatic.com/ Astigmatic].<br />
<br />
<br />
<!--<br />
◆ Requester: replace the preceding paragraph with a package description proposal:<br />
— who designed this font family,<br />
— how can its style be described,<br />
— what unusual world scripts does it add support for,<br />
— what's its intended use (Titling…).<br />
◆ Packager: correct the proposal and replace it with the final package description.<br />
--><br />
<br />
== Characteristics ==<br />
<br />
{|<br />
|-<br />
! Homepage<br />
! Format & features<br />
! License<br />
! Review reference<br />
! Koji page<br />
! pkgdb page<br />
|-<br />
| [https://www.fontsquirrel.com/fonts/grand-hotel Font Squirrel page]<br />
| OTF<br />
| OFL<br />
| [[rhbug:1368606|1368606]]<br />
| [[koji:astigmatic-grand-hotel-fonts|astigmatic-grand-hotel-fonts]]<br />
| [[pkgdb:astigmatic-grand-hotel-fonts|astigmatic-grand-hotel-fonts]]<br />
|}<br />
<br />
<br />
{|<br />
! colspan="5" | Style<br />
! colspan="5" | Faces<br />
! colspan="4" | Scripts<br />
|-<br />
! colspan="2" | Sans<br />
! colspan="2" | Serif<br />
! rowspan="2" | Other<br />
! rowspan="2" | R<br />
! rowspan="2" | B<br />
! rowspan="2" | I<br />
! rowspan="2" | BI<br />
! rowspan="2" | Other<br />
! rowspan="2" | Latin<br />
! rowspan="2" | Greek<br />
! rowspan="2" | Cyrillic<br />
! rowspan="2" | Other<br />
|-<br />
! Variable<br />
! Monospace<br />
! Variable<br />
! Monospace<br />
|-<br />
| <br />
| ✘<br />
|<br />
|<br />
| <br />
| ✘<br />
|<br />
|<br />
|<br />
| <br />
| ✘<br />
|<br />
| ✘<br />
| <br />
|}<br />
<br />
<!--<br />
◆ Requester:<br />
— Add as many lines as necessary in the preceding table. Be careful not to mix faces with different characteristics on the same line (for example if a font bundle includes a serif font with a regular and bold face, and a sans-serif font with regular, bold, italic and bold-italic faces, use two different lines).<br />
— Use ✘s to indicate a common feature is present.<br />
— « Other » features can be filled this way:<br />
‣ other styles ①: fantasy, cursive, etc<br />
‣ other faces ②: condensed, extralight, etc<br />
‣ other scripts ③: list the corresponding IS0 15924 codes.<br />
⇒ http://www.unicode.org/iso15924/iso15924-codes.html<br />
⇒ tools you can use to check coverage: gucharmap, fontforge, http://www.fileformat.info/info/unicode/font/custom.htm<br />
--><br />
<br />
== Caveats ==<br />
<br />
# Only regular size available<br />
<br />
<!--<br />
◆ Requester and packager: list there the elements you know of that will impact packaging activity, such as licensing that needs clarifying, an upstream that uses a specific non-english language to communicate, broken or incomplete build scripts, etc.<br />
◆ Packager: take care of those items and remove them from the page once they've been dealt with.<br />
--><br />
<br />
<br />
== Additional information ==<br />
<br />
None<br />
<br />
<!--<br />
◆ Requester and packager: if you have some additional information that does not fit in the previous sections, add it there.<br />
--><br />
<br />
<br />
{{:Fonts_SIG_signature}} [[Category:Fonts SIG|Template for describing fonts]] [[Category:International fonts]] [[Category:Packaged fonts]]<br />
<br />
<!--<br />
◆ Requester: replace existing categories with « Category:Font wishlist »<br />
◆ Packager: replace the « Category:Font wishlist » by<br />
— « Category:In-progress fonts » for a font being worked on, but not available in Fedora yet. Typically in packaging review stage.<br />
— « Category:Packaged fonts » for a packaged font, available in Fedora.<br />
— « Category:Rejected and retired fonts » for a font we decided not to package after review, or removed from current Fedora repositories for some other reason.<br />
◆ Requester and packager: you may additionally tag your page with one of the following categories:<br />
— « Category:Decorative fonts » for a font used in titles and other short runs of text, typically requested by the Artwork team<br />
— « Category:International fonts » for a font with unusual unicode coverage, typically requested by the I18N or L10N teams<br />
— « Category:Technical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).<br />
--></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Astigmatic_Grand_Hotel_Fonts&diff=508811Astigmatic Grand Hotel Fonts2018-01-07T16:38:28Z<p>Kkofler: Fix review bug ID.</p>
<hr />
<div>{{CompactHeader|fonts-sig}}<br />
<br />
<br />
<!-- <br />
◆ Use this template to create « Name_Fonts » pages:<br />
— « Name_Fonts » should be « Foo_fonts » and not « FooFonts_fonts » or « FooFont_fonts ». <br />
— use the « Foundry Name » convention if necessary.<br />
⇒ See also Packaging:FontsPolicy#Naming we try to follow the same conventions for our wiki pages.<br />
◆ Please remove the « lorem ipsum » filers once they are no longer necessary. Do the same for those comments.<br />
◆ Do not forget to update the page categorization each time the font described in this page passes one packaging step.<br />
--><br />
<br />
''Display sans-serif fonts''<br />
<br />
<!--<br />
◆ Requester: replace the preceding line with a package summary proposal. For example: A decorative font inspired from xxx.<br />
◆ Packager: correct the proposal and replace it with the final package summary.<br />
--><br />
<br />
<br />
== Description ==<br />
A condensed cursive (handwriting) font created by Brian J. Bonislawsky and Jim Lyles DBA [http://www.astigmatic.com/ Astigmatic].<br />
<br />
<br />
<!--<br />
◆ Requester: replace the preceding paragraph with a package description proposal:<br />
— who designed this font family,<br />
— how can its style be described,<br />
— what unusual world scripts does it add support for,<br />
— what's its intended use (Titling…).<br />
◆ Packager: correct the proposal and replace it with the final package description.<br />
--><br />
<br />
== Characteristics ==<br />
<br />
{|<br />
|-<br />
! Homepage<br />
! Format & features<br />
! License<br />
! Review reference<br />
! Koji page<br />
! pkgdb page<br />
|-<br />
| [https://www.fontsquirrel.com/fonts/grand-hotel Font Squirrel page]<br />
| OTF<br />
| OFL<br />
| [[rhbug:1368606|1368606]]<br />
| [[koji:astigmatic-grand-hotel-fonts|astigmatic-grand-hotel-fonts]]<br />
| [[pkgdb:astigmatic-grand-hotel-fonts|astigmatic-grand-hotel-fonts]]<br />
|}<br />
<br />
<br />
{|<br />
! colspan="5" | Style<br />
! colspan="5" | Faces<br />
! colspan="4" | Scripts<br />
|-<br />
! colspan="2" | Sans<br />
! colspan="2" | Serif<br />
! rowspan="2" | Other<br />
! rowspan="2" | R<br />
! rowspan="2" | B<br />
! rowspan="2" | I<br />
! rowspan="2" | BI<br />
! rowspan="2" | Other<br />
! rowspan="2" | Latin<br />
! rowspan="2" | Greek<br />
! rowspan="2" | Cyrillic<br />
! rowspan="2" | Other<br />
|-<br />
! Variable<br />
! Monospace<br />
! Variable<br />
! Monospace<br />
|-<br />
| <br />
| ✘<br />
|<br />
|<br />
| <br />
| ✘<br />
|<br />
|<br />
|<br />
| <br />
| ✘<br />
|<br />
| ✘<br />
| <br />
|}<br />
<br />
<!--<br />
◆ Requester:<br />
— Add as many lines as necessary in the preceding table. Be careful not to mix faces with different characteristics on the same line (for example if a font bundle includes a serif font with a regular and bold face, and a sans-serif font with regular, bold, italic and bold-italic faces, use two different lines).<br />
— Use ✘s to indicate a common feature is present.<br />
— « Other » features can be filled this way:<br />
‣ other styles ①: fantasy, cursive, etc<br />
‣ other faces ②: condensed, extralight, etc<br />
‣ other scripts ③: list the corresponding IS0 15924 codes.<br />
⇒ http://www.unicode.org/iso15924/iso15924-codes.html<br />
⇒ tools you can use to check coverage: gucharmap, fontforge, http://www.fileformat.info/info/unicode/font/custom.htm<br />
--><br />
<br />
== Caveats ==<br />
<br />
# Only regular size available<br />
<br />
<!--<br />
◆ Requester and packager: list there the elements you know of that will impact packaging activity, such as licensing that needs clarifying, an upstream that uses a specific non-english language to communicate, broken or incomplete build scripts, etc.<br />
◆ Packager: take care of those items and remove them from the page once they've been dealt with.<br />
--><br />
<br />
<br />
== Additional information ==<br />
<br />
None<br />
<br />
<!--<br />
◆ Requester and packager: if you have some additional information that does not fit in the previous sections, add it there.<br />
--><br />
<br />
<br />
{{:Fonts_SIG_signature}} [[Category:Fonts SIG|Template for describing fonts]] [[Category:International fonts]] [[Category:Packaged fonts]]<br />
<br />
<!--<br />
◆ Requester: replace existing categories with « Category:Font wishlist »<br />
◆ Packager: replace the « Category:Font wishlist » by<br />
— « Category:In-progress fonts » for a font being worked on, but not available in Fedora yet. Typically in packaging review stage.<br />
— « Category:Packaged fonts » for a packaged font, available in Fedora.<br />
— « Category:Rejected and retired fonts » for a font we decided not to package after review, or removed from current Fedora repositories for some other reason.<br />
◆ Requester and packager: you may additionally tag your page with one of the following categories:<br />
— « Category:Decorative fonts » for a font used in titles and other short runs of text, typically requested by the Artwork team<br />
— « Category:International fonts » for a font with unusual unicode coverage, typically requested by the I18N or L10N teams<br />
— « Category:Technical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).<br />
--></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Astigmatic_Grand_Hotel_Fonts&diff=508810Astigmatic Grand Hotel Fonts2018-01-07T16:37:10Z<p>Kkofler: Fix authorship information (see the contents of the ZIP file), homepage (point where the font is actually available), description (cursive, not sans-serif).</p>
<hr />
<div>{{CompactHeader|fonts-sig}}<br />
<br />
<br />
<!-- <br />
◆ Use this template to create « Name_Fonts » pages:<br />
— « Name_Fonts » should be « Foo_fonts » and not « FooFonts_fonts » or « FooFont_fonts ». <br />
— use the « Foundry Name » convention if necessary.<br />
⇒ See also Packaging:FontsPolicy#Naming we try to follow the same conventions for our wiki pages.<br />
◆ Please remove the « lorem ipsum » filers once they are no longer necessary. Do the same for those comments.<br />
◆ Do not forget to update the page categorization each time the font described in this page passes one packaging step.<br />
--><br />
<br />
''Display sans-serif fonts''<br />
<br />
<!--<br />
◆ Requester: replace the preceding line with a package summary proposal. For example: A decorative font inspired from xxx.<br />
◆ Packager: correct the proposal and replace it with the final package summary.<br />
--><br />
<br />
<br />
== Description ==<br />
A condensed cursive (handwriting) font created by Brian J. Bonislawsky and Jim Lyles DBA [http://www.astigmatic.com/ Astigmatic].<br />
<br />
<br />
<!--<br />
◆ Requester: replace the preceding paragraph with a package description proposal:<br />
— who designed this font family,<br />
— how can its style be described,<br />
— what unusual world scripts does it add support for,<br />
— what's its intended use (Titling…).<br />
◆ Packager: correct the proposal and replace it with the final package description.<br />
--><br />
<br />
== Characteristics ==<br />
<br />
{|<br />
|-<br />
! Homepage<br />
! Format & features<br />
! License<br />
! Review reference<br />
! Koji page<br />
! pkgdb page<br />
|-<br />
| [https://www.fontsquirrel.com/fonts/grand-hotel Font Squirrel page]<br />
| OTF<br />
| OFL<br />
| [[rhbug:1368611|1368611]]<br />
| [[koji:astigmatic-grand-hotel-fonts|astigmatic-grand-hotel-fonts]]<br />
| [[pkgdb:astigmatic-grand-hotel-fonts|astigmatic-grand-hotel-fonts]]<br />
|}<br />
<br />
<br />
{|<br />
! colspan="5" | Style<br />
! colspan="5" | Faces<br />
! colspan="4" | Scripts<br />
|-<br />
! colspan="2" | Sans<br />
! colspan="2" | Serif<br />
! rowspan="2" | Other<br />
! rowspan="2" | R<br />
! rowspan="2" | B<br />
! rowspan="2" | I<br />
! rowspan="2" | BI<br />
! rowspan="2" | Other<br />
! rowspan="2" | Latin<br />
! rowspan="2" | Greek<br />
! rowspan="2" | Cyrillic<br />
! rowspan="2" | Other<br />
|-<br />
! Variable<br />
! Monospace<br />
! Variable<br />
! Monospace<br />
|-<br />
| <br />
| ✘<br />
|<br />
|<br />
| <br />
| ✘<br />
|<br />
|<br />
|<br />
| <br />
| ✘<br />
|<br />
| ✘<br />
| <br />
|}<br />
<br />
<!--<br />
◆ Requester:<br />
— Add as many lines as necessary in the preceding table. Be careful not to mix faces with different characteristics on the same line (for example if a font bundle includes a serif font with a regular and bold face, and a sans-serif font with regular, bold, italic and bold-italic faces, use two different lines).<br />
— Use ✘s to indicate a common feature is present.<br />
— « Other » features can be filled this way:<br />
‣ other styles ①: fantasy, cursive, etc<br />
‣ other faces ②: condensed, extralight, etc<br />
‣ other scripts ③: list the corresponding IS0 15924 codes.<br />
⇒ http://www.unicode.org/iso15924/iso15924-codes.html<br />
⇒ tools you can use to check coverage: gucharmap, fontforge, http://www.fileformat.info/info/unicode/font/custom.htm<br />
--><br />
<br />
== Caveats ==<br />
<br />
# Only regular size available<br />
<br />
<!--<br />
◆ Requester and packager: list there the elements you know of that will impact packaging activity, such as licensing that needs clarifying, an upstream that uses a specific non-english language to communicate, broken or incomplete build scripts, etc.<br />
◆ Packager: take care of those items and remove them from the page once they've been dealt with.<br />
--><br />
<br />
<br />
== Additional information ==<br />
<br />
None<br />
<br />
<!--<br />
◆ Requester and packager: if you have some additional information that does not fit in the previous sections, add it there.<br />
--><br />
<br />
<br />
{{:Fonts_SIG_signature}} [[Category:Fonts SIG|Template for describing fonts]] [[Category:International fonts]] [[Category:Packaged fonts]]<br />
<br />
<!--<br />
◆ Requester: replace existing categories with « Category:Font wishlist »<br />
◆ Packager: replace the « Category:Font wishlist » by<br />
— « Category:In-progress fonts » for a font being worked on, but not available in Fedora yet. Typically in packaging review stage.<br />
— « Category:Packaged fonts » for a packaged font, available in Fedora.<br />
— « Category:Rejected and retired fonts » for a font we decided not to package after review, or removed from current Fedora repositories for some other reason.<br />
◆ Requester and packager: you may additionally tag your page with one of the following categories:<br />
— « Category:Decorative fonts » for a font used in titles and other short runs of text, typically requested by the Artwork team<br />
— « Category:International fonts » for a font with unusual unicode coverage, typically requested by the I18N or L10N teams<br />
— « Category:Technical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).<br />
--></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Kkofler&diff=505532User:Kkofler2017-11-11T02:13:05Z<p>Kkofler: /* Activities within Fedora */ Updated link to owned or comaintained packages. The new link does not distinguish between the different levels of maintainership, but it is the best I found.</p>
<hr />
<div>= Kevin Kofler =<br />
<br />
<!-- An (optional) photo of yourself (image attached to the page).<br />
--><br />
<!-- Comment out the following line if you don't have one.<br />
--><br />
<!-- ||<tableclass="floatright">[[Image:KevinKofler_FirstnameLastname-head.png]]||<br />
--><br />
<br />
See [http://www.tigen.org/kevin.kofler/ my web page] for more information about me.<br />
<br />
== Contact ==<br />
<br />
* '''Email''': kevin AT tigcc DOT ticalc DOT org<br />
* '''IRC''': Kevin_Kofler<br />
* '''GPG key''': 1634F842<br />
* '''Fedora Account''': kkofler<br />
<br />
== Activities within Fedora ==<br />
<br />
* [https://src.fedoraproject.org/user/kkofler Currently owned or comaintained packages] <br />
* I'm interested in [[KDE| KDE on Fedora]]. I was a member of the [[SIGs/KDE| Fedora KDE SIG]] for 8 years (2007-2015).<br />
* I might also submit packages for cross-compilation tools for TI calculators (such as the TIGCC toolchain I'm the current upstream maintainer of).</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User_talk:Luya/Changes/amdgpu_default_for_GCN_cards&diff=501932User talk:Luya/Changes/amdgpu default for GCN cards2017-09-24T15:02:52Z<p>Kkofler: Ask for more precise wording.</p>
<hr />
<div>I think this feature page could benefit from more precise wording:<br />
* The page does not explain anywhere what "GCN" means. Putting something like "GCN ([https://en.wikipedia.org/wiki/Graphics_Core_Next Graphics Core Next])" (including the wikipedia link) into the summary would help. (In principle, adding the matching marketing names would be even better, but the marketing naming is [https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units a mess], so I'm not insisting on that.)<br />
* The "Summary" section says "drop radeon driver.", whereas the "Benefits to Fedora" section says "Radeon driver will be reserved for R600 models and below." I hope the latter is accurate! I would hate to lose support for my older pre-GCN Radeon. So please also clarify this in the summary.<br />
--[[User:Kkofler|Kkofler]] ([[User talk:Kkofler|talk]]) 15:02, 24 September 2017 (UTC)</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Architectures/x86&diff=497442Architectures/x862017-07-12T22:50:38Z<p>Kkofler: /* Get Involved with Fedora ARM */ s/ARM/x86/ (copy&paste error fix)</p>
<hr />
<div><br />
= Fedora x86 (Intel/AMD 32 bit)=<br />
<br />
* IRC: {{fpchat|#fedora-x86}} on freenode.net<br />
* Mailing List: TBD<br />
* Regular IRC meetings: TBD<br />
<br />
== Introduction ==<br />
<br />
The X86 architecture has been built from the very beginning of Red Hat Linux, but is no longer the primary build target with X86_64 replacing it. This change has happened over the last decade, and the lack of attention by most developers has left the system not as used as before.<br />
<br />
This page and targeting is aimed at trying to fix this problem.<br />
<br />
== Targets ==<br />
=== short term goals ===<br />
* To Be Filled out by Team<br />
<br />
=== long term goals ===<br />
* To Be Filled Out by Team<br />
<br />
== Accomplished ==<br />
* To Be Filled out by Team<br />
<br />
== People ==<br />
* [[User:Smooge|Stephen Smoogen]]<br />
<br />
== History ==<br />
The x86 architecture itself has a long and storied history which are better outlined in the [[https://en.wikipedia.org/wiki/IA-32|Wikipedia ia-32]] and [[https://en.wikipedia.org/wiki/X86 |X86]] articles. Because of the fact that the name of the architecture is confusing with ia64 not being ia32 with a 64 bit bus, and similar items, Fedora has either used i386 or x86 to refer to the architecture. <br />
<br />
<br />
<br />
== Supported Hardware ==<br />
<br />
Currently only later models in the 'i686' architecture are supported: Pentium II and above.<br />
<br />
== Release Notes == <br />
<br />
== Tips ==<br />
<br />
== Known Runtime Issues ==<br />
=== F25 ===<br />
<br />
=== F26 ===<br />
<br />
* [https://bugzilla.redhat.com/show_bug.cgi?id=1375732 BZ#1375732] Anaconda reclaim space is broken on x86<br />
<br />
=== F27 ===<br />
<br />
== [[Architectures/BuildIssues|Known build issues]] ==<br />
<br />
== Notes for application developers and package maintainers ==<br />
<br />
== Submitting builds ==<br />
As of 2017-07-12 there should be no need for a maintainer to do a regular build, they are automagically processed through the primary koji.<br />
<br />
== Packages under review ==<br />
<br />
= Get Involved with Fedora x86 =<br />
<br />
== Bug Reporting ==<br />
Bugs should be reported against their prospective packages as per standard Fedora process. Other methods may be added by x86 team later<br />
<br />
<br />
== Getting help with x86 build issues ==</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Talk:Changes//Stop_Building_i686_Kernels&diff=497384Talk:Changes//Stop Building i686 Kernels2017-07-11T23:47:24Z<p>Kkofler: Since this effectively amounts to desupporting Fedora on i686 hardware, this is very much a system-wide change.</p>
<hr />
<div>Since this effectively amounts to desupporting Fedora on i686 hardware, this is very much a system-wide change.<br />
--[[User:Kkofler|Kkofler]] ([[User talk:Kkofler|talk]]) 23:47, 11 July 2017 (UTC)</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Talk:Changes//IDNA2008&diff=492475Talk:Changes//IDNA20082017-05-09T09:47:13Z<p>Kkofler: Add question about drop-in replacement.</p>
<hr />
<div>Why don't you make idna.h a symlink to or a transitive #include of idn2.h (which is supposed to be a drop-in replacement) instead of forcing us to change every single package using the library? --[[User:Kkofler|Kkofler]] ([[User talk:Kkofler|talk]]) 09:47, 9 May 2017 (UTC)</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=History_of_Red_Hat_Linux&diff=478845History of Red Hat Linux2016-11-06T23:42:13Z<p>Kkofler: Fix typo: gcc 2.96RH, not "2.69RH".</p>
<hr />
<div>{{autolang|base=yes}}<br />
== Abstract ==<br />
<br />
There has been over a decade of Linux development at Red Hat. This document describes that history, particularly focusing on the development themes for each release of Linux provided by Red Hat.<br />
Release History<br />
<br />
“You know, it's a funny thing. We go ahead and do things, and afterward, people go and start making history out of it.” — Fred Weick, Aircraft Designer. For the first decade or so, we did not set out to write the history of Red Hat Linux, so some of this data is a bit fuzzy or conflicting. We hope to do more research into our own past to give more useful data. This history is embryonic. It is intended to give some sense of where we have been, to help build a shared understanding of what we did right, as well as what we have done wrong, in order to continue a tradition of excellence.<br />
<br />
In the following table, the Version number is prefaced by "RHL" for Red Hat Linux, "RHEL" for Red Hat Enterprise Linux, and "FC" for Fedora Core.<br />
<br />
{| border="1"<br />
|- style="width: 100% ;color: white; background-color: #3074c2; font-weight: bold" <br />
| Date || Version || Code Name (or Release Name) || Description<br />
|-<br />
| July 29 1994 || n/a || Preview (or Beta) || Initial test release, not distributed widely or publicly, built on Red Hat's original package management system, RPP. This was called "Red Hat Software Linux" and abbreviated "RHS Linux" in the manuals and other accompanying documentation, and was provided on a single CD with an unmarked solid red label. The letter accompanying it thanked the recipient for purchasing the beta version and was signed by Marc Ewing (Red Hat's founder) and Damien Neil (Red Hat's first employee, a summer intern). It used a 1.1.18 development series kernel. Reports of a version number for this product appear to be exaggerated.<br />
|-<br />
| October 31 1994 || RHL 0.9 || Halloween || First widely-available beta release of Red Hat Linux. It was still a purchased beta, but at least now it came with documentation. Users had their choice of the 1.0.9 (stable) or 1.1.54 (development) Linux kernel. The manual still referred in at least one place to the 1.1.18 kernel shipped just a few months previously. The manual also suggested that most users would not use the rpp program to install software; instead, they would use the Tcl/Tk LIM (Linux Installation Manager) graphical front end. <BR><BR>One of the critical factors that made RHS Linux a success even as a beta was the focus on graphical configuration tools; even this early beta had graphical tools to configure users and groups, /etc/fstab, time and date (this tool even had an easter egg!), and most importantly, networking. Few people today recall the pain of setting up networking on Linux completely from scratch, following steps in a long HOWTO document, and then going through the process again after installing (not upgrading to) every new version of their distribution they installed.<br />
|-<br />
| May 1995 || RHL 1.0 || Mother's Day || First non-beta release of Red Hat Linux, it was not released on the 13th (Mothers' Day that year) but that was the closest holiday, and so it got its name. Built on the 1.2.8 kernel, this release introduced the name "Red Hat Commercial Linux" instead of "Red Hat Software Linux", and replaced the very tall top hat logo with an image of a man walking quickly, carrying a briefcase, and holding on to a red hat. This was the first release done after ACC Bookstores (Bob Young) bought out Red Hat Software, Inc. (Mark Ewing) and adopted the better name. (ACC Bookstores was so named in order to appear first alphabetically.)<br />
|-<br />
| Late Summer 1995 || RHL 1.1 || Mother's Day+0.1 || Bug fix release. 1.2.11 or 1.2.13 kernel, depending on exactly which version you got! Known in at least one incarnation as "The Official Red Hat Commercial Linux". The name, for reasons lost in time has always been pronounced "Mother's Day Plus One".<br />
|-<br />
| Later Summer 1995 || RHL 2.0 beta || ? || Beta of first release to use RPM, which meant that upgrades from earlier releases were not supported. This version of RPM was written in Perl for quick development. First release using the ELF format for libraries and executables; previous releases used the "a.out" format.<br />
|-<br />
| Early Fall 1995 || RHL 2.0 || ? || First formal release using RPM. Marketing typography called this "Red Hat LiNUX".<br />
|-<br />
| November 1995 || RHL 2.1 || Bluesky || Bug fix release. Digital (remember them?) did a promotional CD of "Red Hat 2.1 LiNUX" for the x86 platform as a teaser for the forthcoming release of a Red Hat Software product for their Alpha platform; "Red Hat Linux/Alpha 2.1" was released in January 1996. Included the 1.2.13 (stable) and 1.3.32 (development) kernels.<br />
|-<br />
| March 15 1996 || RHL 3.0.3 || Picasso || Engineers intended this release to be called "2.2" but marketing (i.e. Bob Young) decided it would sell better if it were called "3.0.3" ("3.03" in some places). Red Hat is still in business today, so maybe Bob was right. The release was now called "Official" Red Hat LiNUX' (yes, the quotes around 'Official' were part of the name, at least on the CD and some of the box copy; in other places, it was in italic typeface instead). This was to separate the version Red Hat sold from the versions sold by third parties such as Infomagic. It was also called "Red Hat™; Software, Inc. LiNUX", "RED HAT LINUX", and "Red Hat Linux" on the box. <BR><BR> This was the first approximately concurrent multi-architecture release; the (then) Digital Alpha platform was supported. (The binary file format was still a.out for the Alpha platform because the ELF standard for Alpha was not yet ratified; there were no shared libraries on Alpha, either.) <BR><BR> This was also the first release to feature the proprietary Metro-X accelerated X server as a feature of the release. It was also the first to include glint, the "Graphical Linux INstallation Tool", as a graphical front end for RPM. It also included graphical printer configuration.<br />
|-<br />
| July-August 1996 || RHL 3.0.4/3.95 || Rembrandt || Beta leading up to the 4.0 release. RPM re-written in C (I think for this beta). First release with Pluggable Authentication Modules (PAM). New configuration tools being written in Python with Tk<code></code>Inter instead of TCL/TK; first example was a new network configuration tool. Thanks to the new 2.0 kernel, this was the first release to use kernel modules; before this, there were 72 different kernels from which users had to choose to match their hardware. Now, hardware differences could be handled by loading different modules.<br />
|-<br />
| October 3 1996 || RHL 4.0 || Colgate || Three architectures supported: x86, Alpha, and SPARC. Alpha was able to use the ELF file format in this release, since the standard was ratified and tool support implemented. This release also introduced our current Shadowman™ logo. Based on the 2.0.18 kernel. First release to include documentation freely available in electronic form as well as "dead tree" format in the box. First release to ship the spyglass-derived "Red Baron" browser as a proprietary value-add.<br />
|-<br />
| February 3 1997 || RHL 4.1 || Vanderbilt || Bug fix release. Kernel 2.0.27. <BR><BR>Info<code></code>World, Best of 1996, Operating Systems.<br />
|-<br />
| May 19 1997 || RHL 4.2 || Biltmore || Continued to use a slightly old version of libc (5.3) instead of newer 5.4 version because of instability and gratuitous incompatibility in the new version. One of the first really widely-criticized technical decisions between versions of software in Red Hat Linux, this decision was vindicated, at least for the distribution developers, by the flood of bug reports and demonstrated instability on other distributions that shipped libc 5.4. Last release to ship the Red Baron browser, which proved very buggy.<br />
|-<br />
| August 27, September 16 1997 || RHL 4.8/4.8.1/4.95 || Thunderbird || First release to use glibc 2.0. First formal beta release program.<br />
|-<br />
| October 7, 16 1997 || RHL 4.9/4.9.1/4.96 || Mustang || Another set of beta releases; the massive changes introduced by changing C library versions made it critical that Red Hat ran a two-cycle beta instead of just one or even zero cycles as before. The experience we had of the gain in quality from this very public beta process was a formative experience and cemented a resolve to have strong beta processes for future releases.<br />
|-<br />
| December 1 1997 || RHL 5.0 || Hurricane || Released in time for Christmas sales, Hurricane was named partly in recognition (it is hard to call it honor) of the hurricane that had swept over Red Hat a few months before and done a great deal of damage to the surrounding area, but essentially spared the Red Hat offices. First release to include BRU2000-PE™ backup and Real Audio™ client and server software as proprietary value-add components.<BR><BR>1997 Info<code></code>World Product of the Year.<br />
|-<br />
| June 1 1998 || RHL 5.1 || Manhattan || Debuted the Linux Applications CD, a disk with primarily proprietary applications from third-party companies that worked on Red Hat Linux. Some pieces of GNOME were included for building a few applications, and a preview release of GNOME was included in a separate directory, though it wasn't part of the installation. First release to ship linuxconf as a centralized configuration tool. First release to include the proprietary Netscape browser. Last release to have a live filesystem tree on the CD; after this the size of the software outgrew the space for it. <BR><BR>PC Magazine Technical Innovation Awards: Editorial Fellows' Award Winner, 1998; Australian Personal Computer, Editor's Choice, and Just Plain Cool Award, 1998.<br />
|-<br />
| October 12 1998 || RHL 5.2 || Apollo || Technology preview of GNOME included in a separate directory. <BR><BR>LinuxWorld, Show Favorite: Software.<br />
|-<br />
| March 17, 1999 || RHL 5.9 || Starbuck ||<br />
|-<br />
| April 19 1999 || RHL 6.0 || Hedwig || glibc 2.1, egcs, 2.2 kernel, GNOME integrated.<BR><BR>Desktop Engineering, Readers' Choice Award, 1999; Wired for 3D, 1999 Editor's Choice Award Winner<br />
|-<br />
| September 6 1999 || RHL 6.0.50 || Lorax || First beta release with graphical installer (anaconda); the installer was completely re-written, including implementing graphical mode and reimplementing text mode, in Python.<br />
|-<br />
| October 4 1999 || RHL 6.1 || Cartman || Info<code></code>World, 1999 Product of the Year, Operating Systems; Information Week, 1999 Product of the year; Internet Week, 1999 Best of Breed and 1999 Approved; Popular Science, 1999 Award for Computer and Software; International Engineering Consortium, Infovision 2000 Award, Private Networks; Network Magazine, 2000 Product of the Year, Server OS.<br />
|-<br />
| February 9 2000 || RHL 6.1.92 || Piglet || The world did not end.<br />
|-<br />
| March 27 2000 || RHL 6.2 || Zoot || First release to ship ISO images for FTP download.<br />
|-<br />
| July 31 2000 || RHL 6.9.5 || Pinstripe ||<br />
|-<br />
| September 25 2000 || RHL 7.0 || Guinness || glibc 2.2. 2.4 kernel just didn't make it in time, we decided that glibc version was a bigger user-space distinguisher than kernel version. First release that supported Red Hat Network out of the box.<BR><BR> This release introduced what Red Hat called gcc 2.96 in this release, and later re-named gcc 2.96RH. The gcc developers who had been working for Cygnus Solutions when it was a separate company recommended that Red Hat base its work on a stabilized snapshot in order to get much better C++ support. Due to misunderstanding, this was not discussed with other gcc maintainers first, and a flame war erupted afterward about Red Hat using this version number, thus the renaming to gcc 2.96RH in future versions. Red Hat provides an official response to this altercation.<br />
|-<br />
| January 31 2001 || RHL 7.0.90 || Fisher || Introduced the 2.4 kernel.<br />
|-<br />
| February 21 2001 || RHL 7.0.91 || Wolverine ||<br />
|-<br />
| April 16 2001 || RHL 7.1 || Seawolf || First non-"point-zero" release to include a new stable kernel stream. This release was considerably delayed internally, but barely externally due to heroics on the part of project management, by a major fight to resolve a very subtle data corruption issue in the kernel. This was also the first release to simultaneously support all supported languages, including CJK (Chinese, Japanese, and Korean). <BR><BR> This was the first release to ship with Mozilla.<br />
|-<br />
| August 2, 21 2001 || RHL 7.1.93, 7.1.94 || Roswell || The ext3 journaling filesystem become the default filesystem, and the installer offers to convert ext2 filesystems to ext3 as part of the installation process. Grub replaces LILO as default boot manager.<br />
|-<br />
| October 22 2001 || RHL 7.2 || Enigma || GNOME 1.4, KDE 2.2. This was the development basis for Red Hat Enterprise Linux 2.1 AS, originally marketed as Red Hat Advanced Server 2.1, though RHEL 2.1 AS also included some fixes that also ended up being included in Red Hat Linux 7.3. <BR><BR>Network Computing, 2002 Well-Connected Awards Finalist.<br />
|-<br />
| March 22 2002 || RHL 7.2.91 || Skipjack || Despite the fact that we always said that we did not pre-announce version numbers, and that there was no guarantee that we would always do a ".0" release, a ".1" release, and a ".2" release, there had been a strong pattern so far through the 4, 5, 6, and 7 releases. We finally broke the mold when it became obvious that it was going to take too long to get gcc3, GTK+ 2, Python2, etc. all mature for a timely Red Hat Linux 8.0 release. Therefore, not long before this beta, we cut out the new stuff, rebuilt with the old compiler, and set off to chart new ".3" territory.<br />
|-<br />
| May 6 2002 || RHL 7.3 || Valhalla || The last release to carry the proprietary Netscape browser.<br />
|-<br />
| May 6 2002 || RHEL 2.1 AS || (Pensacola) || Red Hat Enterprise Linux 2.1 AS (originally launched as Red Hat Linux Advanced Server 2.1), Red Hat's first Enterprise offering (Red Hat Linux 6.2E was essentially a version of Red Hat Linux 6.2 with different support levels, and was not separately engineered) was based on Red Hat Linux 7.2, but included important fixes from Red Hat Linux 7.3. Explicitly supported by many ISVs, it provided much higher support levels with smaller changes than Red Hat had provided in the past. Red Hat has concentrated its commercial support activities on this line of products.<br />
|-<br />
| July 4, 29; August 19 2002 || RHL 7.3.29, 7.3.93, 7.3.94 || Limbo/(null) || Due to the circumstances causing this name change in the middle of this release cycle, all our code names now need to be approved by Red Hat's legal department. Tested 700MB ISO images, but they caused too much trouble.<br />
|-<br />
| September 30, 2002 || RHL 8.0 || Psyche || Lots of new technology in this release. gcc 3.2, glibc 2.3 release candidate (officially approved and requested by upstream maintainer!), Open<code></code>Office.org 1.0.1, GNOME 2, KDE 3.0.3.<BR><BR>Bluecurve™ was also introduced with the goal of providing a pleasant, unified look across the two desktops and many applications included in the release. Despite being slightly controversial to a select few, Bluecurve™ was a smashing success. Several other distributions took notice and began to follow in the footsteps of providing a better user experience through cohesive cross-desktop default themes, which was the major rationale of the Red Hat Artwork project.<br />
|-<br />
| March 31 2003 || RHL 9 || Shrike || Start of some new directions. In the past, Red Hat worked to maintain both forward and backward compatibility within a major version series. In the future, Red Hat will not be trying to enable building software on newer releases that runs on older releases, thus the change in versoning.<BR><BR>First release to include NPTL (Native POSIX Thread Library) support, using glibc 2.3.2 and kernel 2.4.20 with NPTL support backported from the 2.5.x development kernels. Also, KDE 3.1 and GNOME 2.2.<BR><BR>This release is the basis of Red Hat Enterprise Linux 3.<br />
|-<br />
| July 21 2003 || RHL 9.0.93 || Severn || Final Red Hat Linux beta release; this release started Red Hat's process of creating an open development process.<br />
|-<br />
| September 25 2003 || FC 0.94 || Severn || A week after Red Hat announced that its open development process was in the process of merging with the pre-existing Fedora Linux project to create the Fedora Project, the renamed second beta came out: Fedora Core 1 test 2, version 0.94. This was the first test release to have a really functional version of the exec-shield security-enhancing patch.<br />
|-<br />
| N/A || Fedora Release || .. || See [[Releases/HistoricalSchedules| Historical Fedora Release Schedules]] for its Date and Code Name.<br />
|}<br />
<br />
== Naming convention ==<br />
<br />
Starting with Picasso, Red Hat has given releases of Red Hat Linux code names. (These names are included in the /etc/redhat-release file, with the version number.) The code names follow a strict pattern — at least, we have tried to make them follow a strict pattern. Name n and n+1 must share an is-a (not a has-a) relationship, but n and n+2 must not share an is-a relationship. (Extra credit for finding the small mistakes we made; we are now aware that we have at least one case where n and n+2 share an is-a relationship. The best-laid plans of mice and men gang aft a-gley.) Sometimes the name has changed from one beta release to another; more often it has not. There is no subtle message encoded in whether the name changes from one beta release to the next. Red Hat Enterprise Linux releases have not had code names; only release names which have also been used in place of code names.<br />
<br />
In the past few years, there have also been a set of release names applied to each release by product management; these names are per formal release, where the beta has the same name as the follow-on product. Red Hat has not formally published these names, but several of them have become common knowledge anyway. These names have been geographical; they were originally the birthplaces of various members of the product management team, but those ran out and we had to find other geographical names.<br />
<br />
Red Hat Enterprise Linux have only release names, no code names. Fedora Core will have only code names, not release names, except that we had already chosen the name "Cambridge" as a release name for the project that became Fedora Core 1.<br />
<br />
Neither set of names has a long queue of new names already chosen and waiting for it. Therefore, as common practice, we use C syntax to refer to future releases. For example, the release code-named "Shrike" has the release name "Gin Gin"; the next release we informally referred to as "Gin Gin++" until we chose the release name "Cambridge."<br />
<br />
== Other Historical Information ==<br />
<br />
For historical information specific to the Fedora logo, please refer to [[Logo/History | the Fedora logo history page]].<br />
<br />
== Thanks ==<br />
<br />
For several years, there have been at least two web pages maintaining a bit of history of Red Hat Linux, one by [http://www.smoogespace.com/documents/behind_the_names.html Stephen Smoogen] one by [http://freshrpms.net/misc/redhat-releases/ Matthias Saou] that were valuable summaries we used while writing this document. Kudos to Smooge and Matthias for maintaining them! Thanks to Thomas Chung for writing this page.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/QtWebEngine&diff=443689Changes/QtWebEngine2016-04-20T22:35:02Z<p>Kkofler: /* Scope */ Mark the GStreamer backend port as deferred, it will likely not make the Fedora 24 release.</p>
<hr />
<div>= QtWebEngine =<br />
<br />
== Summary ==<br />
QtWebEngine will be packaged for Fedora, initially at version 5.6. In addition, the QupZilla browser will be upgraded to the QtWebEngine-based QupZilla 2.<br />
<br />
== Owner ==<br />
* Name: [[User:Kkofler| Kevin Kofler]]<br />
* Email: Kevin [AT] tigcc [DOT] ticalc [DOT] org<br />
* Release notes owner:<!-- [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])<br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/24 | Fedora 24 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1303611 #1303611]<br />
<br />
== Detailed Description ==<br />
<br />
QtWebEngine is the new web engine by the Qt project based on Chromium, effectively replacing QtWebKit, though it is not a drop-in replacement. QtWebEngine will be available in Fedora as an '''additional''' option. QtWebKit will remain available for the foreseeable future, and thus applications currently using QtWebKit are '''not''' impacted by this change, unless and until upstream ports them to QtWebEngine. The version initially packaged for Fedora 24 will be QtWebEngine 5.6.<br />
<br />
QupZilla is a modern, lightweight and fast browser written in Qt. QupZilla 1 was based on QtWebKit. It will be replaced by the new QupZilla 2, which is instead based on QtWebEngine.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Since the Qt upstream project has deprecated QtWebKit in Qt 5.5 and is no longer officially supporting it in Qt 5.6, more and more Qt applications will require QtWebEngine. QtWebKit is based on an old WebKit branch that was discontinued by upstream WebKit long ago, meaning it lags behind current web standards and even security fixes. QtWebEngine is based on a recent version of Chromium (QtWebEngine 5.6 is based on Chromium 45), gets backported security fixes, and will be rebased to a newer Chromium at new Qt releases, as QtWebKit was in the past.<br />
<br />
With QupZilla 2, a web browser supporting the latest web standards will be available to our users (and to spin maintainers), as an alternative to Firefox. Compared to QupZilla 1 and other QtWebKit-based browsers, both compatibility with websites and security will be significantly higher.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Package QtWebEngine 5.6.0 beta, based on [[User:Heliocastro| Helio Castro]]'s initial work: <span style="color:green">DONE</span><br />
** Remove patent-encumbered codecs from the upstream tarball using the scripts from [[User:Spot| spot]]'s Chromium packages: <span style="color:green">DONE</span><br />
** Get <code>qt5-qtwebengine</code> through review [https://bugzilla.redhat.com/show_bug.cgi?id=1295549]: <span style="color:green">DONE</span><br />
** Unbundle all libraries that can be unbundled: <span style="color:green">DONE</span><br />
** Make the package run on i686 machines without SSE2, while degrading performance for SSE2-enabled machines as little as possible: <span style="color:green">DONE</span> [http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/tree/qtwebengine-opensource-src-5.6.0-beta-no-sse2.patch]<br />
** Package a QupZilla 1.9.99 snapshot: <span style="color:green">DONE</span> [http://copr-dist-git.fedorainfracloud.org/cgit/kkofler/qtwebengine/qupzilla.git/tree/]<br />
** Upgrade the <code>qupzilla</code> package in Rawhide to 1.9.99 / 2.0.0 [https://bugzilla.redhat.com/show_bug.cgi?id=1298145]: <span style="color:green">DONE</span><br />
** (<s>Nice-to-have: Look into backporting Samsung's Chromium GStreamer backend [https://github.com/Samsung/ChromiumGStreamerBackend]</s>: DEFERRED)<br />
<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
QtWebEngine:<br />
* The package will be a new package. It will '''not''' replace the QtWebKit package. Therefore, no changes are required to applications.<br />
* From the user's point of view, it will simply be a new library, that may or may not get installed as a dependency by upgrades to their existing packages.<br />
<br />
QupZilla:<br />
* The user-visible changes will be of the amount expected for a new major version of a leaf application.<br />
* Manual configuration should not be needed, though some settings from the old QtWebKit-based version may no longer apply to QtWebEngine.<br />
* The most noticeable difference will be the actual web engine. Web pages may render slightly differently. Some web pages that previously did not work will start working. Some web pages that were using obsolete constructs may break, though hopefully that will not be the case. One issue may be support for patent-encumbered codecs: I hope to get GStreamer support working, which was exactly what QtWebKit used.<br />
<br />
'''There will be no impact on other packages from this change, which is why I consider it self-contained.'''<br />
<br />
== How To Test ==<br />
(A test plan is not required for a self-contained change, but here's a short one:)<br />
<br />
The easiest way to test QtWebEngine is through QupZilla 2. Just install the <code>qupzilla</code> package, version 2.x.x (1.9.99 or higher). (On Fedora 24 and Rawhide, you should be getting the new version out of the box. If you wish to try it out on Fedora 22 or 23, you can get it from the Copr repository at [https://copr.fedoraproject.org/coprs/kkofler/qtwebengine/].) The <code>qt5-qtwebengine</code> package should be installed as a dependency; if not, you did something wrong (you are probably installing the old QupZilla 1.8.x instead). Then surf the web with QupZilla as you would with any other browser.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
* http://doc.qt.io/qt-5/qt5-intro.html#web-engine-and-html5<br />
* http://doc.qt.io/qt-5/qtwebengine-index.html<br />
* https://wiki.qt.io/QtWebEngine<br />
* https://www.qupzilla.com/<br />
* http://blog.qupzilla.com/2016/03/qupzilla-200-released-with-qtwebengine.html<br />
<br />
== Release Notes ==<br />
Fedora now includes the new QtWebEngine library, a Qt port of the Chromium web engine. Application developers are encouraged to use QtWebEngine instead of QtWebKit, which was deprecated by the Qt project in favor of QtWebEngine. QupZilla, a modern, lightweight and fast browser written in Qt, is now based on QtWebEngine instead of QtWebKit, bringing it up to date with modern web and security standards. Other QtWebKit browsers such as Konqueror (with the KWebKitPart) and Rekonq are still available, but their users may find QupZilla 2 with QtWebEngine to be a more modern alternative.<br />
<br />
[[Category:ChangeAcceptedF24]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/QtWebEngine&diff=443661Changes/QtWebEngine2016-04-20T18:32:51Z<p>Kkofler: /* How To Test */ Update the instructions.</p>
<hr />
<div>= QtWebEngine =<br />
<br />
== Summary ==<br />
QtWebEngine will be packaged for Fedora, initially at version 5.6. In addition, the QupZilla browser will be upgraded to the QtWebEngine-based QupZilla 2.<br />
<br />
== Owner ==<br />
* Name: [[User:Kkofler| Kevin Kofler]]<br />
* Email: Kevin [AT] tigcc [DOT] ticalc [DOT] org<br />
* Release notes owner:<!-- [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])<br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/24 | Fedora 24 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1303611 #1303611]<br />
<br />
== Detailed Description ==<br />
<br />
QtWebEngine is the new web engine by the Qt project based on Chromium, effectively replacing QtWebKit, though it is not a drop-in replacement. QtWebEngine will be available in Fedora as an '''additional''' option. QtWebKit will remain available for the foreseeable future, and thus applications currently using QtWebKit are '''not''' impacted by this change, unless and until upstream ports them to QtWebEngine. The version initially packaged for Fedora 24 will be QtWebEngine 5.6.<br />
<br />
QupZilla is a modern, lightweight and fast browser written in Qt. QupZilla 1 was based on QtWebKit. It will be replaced by the new QupZilla 2, which is instead based on QtWebEngine.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Since the Qt upstream project has deprecated QtWebKit in Qt 5.5 and is no longer officially supporting it in Qt 5.6, more and more Qt applications will require QtWebEngine. QtWebKit is based on an old WebKit branch that was discontinued by upstream WebKit long ago, meaning it lags behind current web standards and even security fixes. QtWebEngine is based on a recent version of Chromium (QtWebEngine 5.6 is based on Chromium 45), gets backported security fixes, and will be rebased to a newer Chromium at new Qt releases, as QtWebKit was in the past.<br />
<br />
With QupZilla 2, a web browser supporting the latest web standards will be available to our users (and to spin maintainers), as an alternative to Firefox. Compared to QupZilla 1 and other QtWebKit-based browsers, both compatibility with websites and security will be significantly higher.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Package QtWebEngine 5.6.0 beta, based on [[User:Heliocastro| Helio Castro]]'s initial work: <span style="color:green">DONE</span><br />
** Remove patent-encumbered codecs from the upstream tarball using the scripts from [[User:Spot| spot]]'s Chromium packages: <span style="color:green">DONE</span><br />
** Get <code>qt5-qtwebengine</code> through review [https://bugzilla.redhat.com/show_bug.cgi?id=1295549]: <span style="color:green">DONE</span><br />
** Unbundle all libraries that can be unbundled: <span style="color:green">DONE</span><br />
** Make the package run on i686 machines without SSE2, while degrading performance for SSE2-enabled machines as little as possible: <span style="color:green">DONE</span> [http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/tree/qtwebengine-opensource-src-5.6.0-beta-no-sse2.patch]<br />
** Package a QupZilla 1.9.99 snapshot: <span style="color:green">DONE</span> [http://copr-dist-git.fedorainfracloud.org/cgit/kkofler/qtwebengine/qupzilla.git/tree/]<br />
** Upgrade the <code>qupzilla</code> package in Rawhide to 1.9.99 / 2.0.0 [https://bugzilla.redhat.com/show_bug.cgi?id=1298145]: <span style="color:green">DONE</span><br />
** (Nice-to-have: Look into backporting Samsung's Chromium GStreamer backend [https://github.com/Samsung/ChromiumGStreamerBackend]: <span style="color:red">TODO</span>)<br />
<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
QtWebEngine:<br />
* The package will be a new package. It will '''not''' replace the QtWebKit package. Therefore, no changes are required to applications.<br />
* From the user's point of view, it will simply be a new library, that may or may not get installed as a dependency by upgrades to their existing packages.<br />
<br />
QupZilla:<br />
* The user-visible changes will be of the amount expected for a new major version of a leaf application.<br />
* Manual configuration should not be needed, though some settings from the old QtWebKit-based version may no longer apply to QtWebEngine.<br />
* The most noticeable difference will be the actual web engine. Web pages may render slightly differently. Some web pages that previously did not work will start working. Some web pages that were using obsolete constructs may break, though hopefully that will not be the case. One issue may be support for patent-encumbered codecs: I hope to get GStreamer support working, which was exactly what QtWebKit used.<br />
<br />
'''There will be no impact on other packages from this change, which is why I consider it self-contained.'''<br />
<br />
== How To Test ==<br />
(A test plan is not required for a self-contained change, but here's a short one:)<br />
<br />
The easiest way to test QtWebEngine is through QupZilla 2. Just install the <code>qupzilla</code> package, version 2.x.x (1.9.99 or higher). (On Fedora 24 and Rawhide, you should be getting the new version out of the box. If you wish to try it out on Fedora 22 or 23, you can get it from the Copr repository at [https://copr.fedoraproject.org/coprs/kkofler/qtwebengine/].) The <code>qt5-qtwebengine</code> package should be installed as a dependency; if not, you did something wrong (you are probably installing the old QupZilla 1.8.x instead). Then surf the web with QupZilla as you would with any other browser.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
* http://doc.qt.io/qt-5/qt5-intro.html#web-engine-and-html5<br />
* http://doc.qt.io/qt-5/qtwebengine-index.html<br />
* https://wiki.qt.io/QtWebEngine<br />
* https://www.qupzilla.com/<br />
* http://blog.qupzilla.com/2016/03/qupzilla-200-released-with-qtwebengine.html<br />
<br />
== Release Notes ==<br />
Fedora now includes the new QtWebEngine library, a Qt port of the Chromium web engine. Application developers are encouraged to use QtWebEngine instead of QtWebKit, which was deprecated by the Qt project in favor of QtWebEngine. QupZilla, a modern, lightweight and fast browser written in Qt, is now based on QtWebEngine instead of QtWebKit, bringing it up to date with modern web and security standards. Other QtWebKit browsers such as Konqueror (with the KWebKitPart) and Rekonq are still available, but their users may find QupZilla 2 with QtWebEngine to be a more modern alternative.<br />
<br />
[[Category:ChangeAcceptedF24]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/QtWebEngine&diff=443659Changes/QtWebEngine2016-04-20T18:28:59Z<p>Kkofler: /* Documentation */ Add more upstream documentation links.</p>
<hr />
<div>= QtWebEngine =<br />
<br />
== Summary ==<br />
QtWebEngine will be packaged for Fedora, initially at version 5.6. In addition, the QupZilla browser will be upgraded to the QtWebEngine-based QupZilla 2.<br />
<br />
== Owner ==<br />
* Name: [[User:Kkofler| Kevin Kofler]]<br />
* Email: Kevin [AT] tigcc [DOT] ticalc [DOT] org<br />
* Release notes owner:<!-- [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])<br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/24 | Fedora 24 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1303611 #1303611]<br />
<br />
== Detailed Description ==<br />
<br />
QtWebEngine is the new web engine by the Qt project based on Chromium, effectively replacing QtWebKit, though it is not a drop-in replacement. QtWebEngine will be available in Fedora as an '''additional''' option. QtWebKit will remain available for the foreseeable future, and thus applications currently using QtWebKit are '''not''' impacted by this change, unless and until upstream ports them to QtWebEngine. The version initially packaged for Fedora 24 will be QtWebEngine 5.6.<br />
<br />
QupZilla is a modern, lightweight and fast browser written in Qt. QupZilla 1 was based on QtWebKit. It will be replaced by the new QupZilla 2, which is instead based on QtWebEngine.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Since the Qt upstream project has deprecated QtWebKit in Qt 5.5 and is no longer officially supporting it in Qt 5.6, more and more Qt applications will require QtWebEngine. QtWebKit is based on an old WebKit branch that was discontinued by upstream WebKit long ago, meaning it lags behind current web standards and even security fixes. QtWebEngine is based on a recent version of Chromium (QtWebEngine 5.6 is based on Chromium 45), gets backported security fixes, and will be rebased to a newer Chromium at new Qt releases, as QtWebKit was in the past.<br />
<br />
With QupZilla 2, a web browser supporting the latest web standards will be available to our users (and to spin maintainers), as an alternative to Firefox. Compared to QupZilla 1 and other QtWebKit-based browsers, both compatibility with websites and security will be significantly higher.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Package QtWebEngine 5.6.0 beta, based on [[User:Heliocastro| Helio Castro]]'s initial work: <span style="color:green">DONE</span><br />
** Remove patent-encumbered codecs from the upstream tarball using the scripts from [[User:Spot| spot]]'s Chromium packages: <span style="color:green">DONE</span><br />
** Get <code>qt5-qtwebengine</code> through review [https://bugzilla.redhat.com/show_bug.cgi?id=1295549]: <span style="color:green">DONE</span><br />
** Unbundle all libraries that can be unbundled: <span style="color:green">DONE</span><br />
** Make the package run on i686 machines without SSE2, while degrading performance for SSE2-enabled machines as little as possible: <span style="color:green">DONE</span> [http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/tree/qtwebengine-opensource-src-5.6.0-beta-no-sse2.patch]<br />
** Package a QupZilla 1.9.99 snapshot: <span style="color:green">DONE</span> [http://copr-dist-git.fedorainfracloud.org/cgit/kkofler/qtwebengine/qupzilla.git/tree/]<br />
** Upgrade the <code>qupzilla</code> package in Rawhide to 1.9.99 / 2.0.0 [https://bugzilla.redhat.com/show_bug.cgi?id=1298145]: <span style="color:green">DONE</span><br />
** (Nice-to-have: Look into backporting Samsung's Chromium GStreamer backend [https://github.com/Samsung/ChromiumGStreamerBackend]: <span style="color:red">TODO</span>)<br />
<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
QtWebEngine:<br />
* The package will be a new package. It will '''not''' replace the QtWebKit package. Therefore, no changes are required to applications.<br />
* From the user's point of view, it will simply be a new library, that may or may not get installed as a dependency by upgrades to their existing packages.<br />
<br />
QupZilla:<br />
* The user-visible changes will be of the amount expected for a new major version of a leaf application.<br />
* Manual configuration should not be needed, though some settings from the old QtWebKit-based version may no longer apply to QtWebEngine.<br />
* The most noticeable difference will be the actual web engine. Web pages may render slightly differently. Some web pages that previously did not work will start working. Some web pages that were using obsolete constructs may break, though hopefully that will not be the case. One issue may be support for patent-encumbered codecs: I hope to get GStreamer support working, which was exactly what QtWebKit used.<br />
<br />
'''There will be no impact on other packages from this change, which is why I consider it self-contained.'''<br />
<br />
== How To Test ==<br />
(A test plan is not required for a self-contained change, but here's a short one:)<br />
<br />
The easiest way to test QtWebEngine is through QupZilla 2. Just install the <code>qupzilla</code> package, version 1.9.99 or higher. For now, you can get it from the Copr repository at [https://copr.fedoraproject.org/coprs/kkofler/qtwebengine/]. The <code>qt5-qtwebengine</code> package should be installed as a dependency; if not, you did something wrong (you're probably installing the old QupZilla 1.8.x instead). Then surf the web with QupZilla as you would with any other browser.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
* http://doc.qt.io/qt-5/qt5-intro.html#web-engine-and-html5<br />
* http://doc.qt.io/qt-5/qtwebengine-index.html<br />
* https://wiki.qt.io/QtWebEngine<br />
* https://www.qupzilla.com/<br />
* http://blog.qupzilla.com/2016/03/qupzilla-200-released-with-qtwebengine.html<br />
<br />
== Release Notes ==<br />
Fedora now includes the new QtWebEngine library, a Qt port of the Chromium web engine. Application developers are encouraged to use QtWebEngine instead of QtWebKit, which was deprecated by the Qt project in favor of QtWebEngine. QupZilla, a modern, lightweight and fast browser written in Qt, is now based on QtWebEngine instead of QtWebKit, bringing it up to date with modern web and security standards. Other QtWebKit browsers such as Konqueror (with the KWebKitPart) and Rekonq are still available, but their users may find QupZilla 2 with QtWebEngine to be a more modern alternative.<br />
<br />
[[Category:ChangeAcceptedF24]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/QtWebEngine&diff=443658Changes/QtWebEngine2016-04-20T18:27:39Z<p>Kkofler: /* Scope */ Move the GStreamer nice-to-have to the end. (It is likely to be deferred.)</p>
<hr />
<div>= QtWebEngine =<br />
<br />
== Summary ==<br />
QtWebEngine will be packaged for Fedora, initially at version 5.6. In addition, the QupZilla browser will be upgraded to the QtWebEngine-based QupZilla 2.<br />
<br />
== Owner ==<br />
* Name: [[User:Kkofler| Kevin Kofler]]<br />
* Email: Kevin [AT] tigcc [DOT] ticalc [DOT] org<br />
* Release notes owner:<!-- [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])<br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/24 | Fedora 24 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1303611 #1303611]<br />
<br />
== Detailed Description ==<br />
<br />
QtWebEngine is the new web engine by the Qt project based on Chromium, effectively replacing QtWebKit, though it is not a drop-in replacement. QtWebEngine will be available in Fedora as an '''additional''' option. QtWebKit will remain available for the foreseeable future, and thus applications currently using QtWebKit are '''not''' impacted by this change, unless and until upstream ports them to QtWebEngine. The version initially packaged for Fedora 24 will be QtWebEngine 5.6.<br />
<br />
QupZilla is a modern, lightweight and fast browser written in Qt. QupZilla 1 was based on QtWebKit. It will be replaced by the new QupZilla 2, which is instead based on QtWebEngine.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Since the Qt upstream project has deprecated QtWebKit in Qt 5.5 and is no longer officially supporting it in Qt 5.6, more and more Qt applications will require QtWebEngine. QtWebKit is based on an old WebKit branch that was discontinued by upstream WebKit long ago, meaning it lags behind current web standards and even security fixes. QtWebEngine is based on a recent version of Chromium (QtWebEngine 5.6 is based on Chromium 45), gets backported security fixes, and will be rebased to a newer Chromium at new Qt releases, as QtWebKit was in the past.<br />
<br />
With QupZilla 2, a web browser supporting the latest web standards will be available to our users (and to spin maintainers), as an alternative to Firefox. Compared to QupZilla 1 and other QtWebKit-based browsers, both compatibility with websites and security will be significantly higher.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Package QtWebEngine 5.6.0 beta, based on [[User:Heliocastro| Helio Castro]]'s initial work: <span style="color:green">DONE</span><br />
** Remove patent-encumbered codecs from the upstream tarball using the scripts from [[User:Spot| spot]]'s Chromium packages: <span style="color:green">DONE</span><br />
** Get <code>qt5-qtwebengine</code> through review [https://bugzilla.redhat.com/show_bug.cgi?id=1295549]: <span style="color:green">DONE</span><br />
** Unbundle all libraries that can be unbundled: <span style="color:green">DONE</span><br />
** Make the package run on i686 machines without SSE2, while degrading performance for SSE2-enabled machines as little as possible: <span style="color:green">DONE</span> [http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/tree/qtwebengine-opensource-src-5.6.0-beta-no-sse2.patch]<br />
** Package a QupZilla 1.9.99 snapshot: <span style="color:green">DONE</span> [http://copr-dist-git.fedorainfracloud.org/cgit/kkofler/qtwebengine/qupzilla.git/tree/]<br />
** Upgrade the <code>qupzilla</code> package in Rawhide to 1.9.99 / 2.0.0 [https://bugzilla.redhat.com/show_bug.cgi?id=1298145]: <span style="color:green">DONE</span><br />
** (Nice-to-have: Look into backporting Samsung's Chromium GStreamer backend [https://github.com/Samsung/ChromiumGStreamerBackend]: <span style="color:red">TODO</span>)<br />
<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
QtWebEngine:<br />
* The package will be a new package. It will '''not''' replace the QtWebKit package. Therefore, no changes are required to applications.<br />
* From the user's point of view, it will simply be a new library, that may or may not get installed as a dependency by upgrades to their existing packages.<br />
<br />
QupZilla:<br />
* The user-visible changes will be of the amount expected for a new major version of a leaf application.<br />
* Manual configuration should not be needed, though some settings from the old QtWebKit-based version may no longer apply to QtWebEngine.<br />
* The most noticeable difference will be the actual web engine. Web pages may render slightly differently. Some web pages that previously did not work will start working. Some web pages that were using obsolete constructs may break, though hopefully that will not be the case. One issue may be support for patent-encumbered codecs: I hope to get GStreamer support working, which was exactly what QtWebKit used.<br />
<br />
'''There will be no impact on other packages from this change, which is why I consider it self-contained.'''<br />
<br />
== How To Test ==<br />
(A test plan is not required for a self-contained change, but here's a short one:)<br />
<br />
The easiest way to test QtWebEngine is through QupZilla 2. Just install the <code>qupzilla</code> package, version 1.9.99 or higher. For now, you can get it from the Copr repository at [https://copr.fedoraproject.org/coprs/kkofler/qtwebengine/]. The <code>qt5-qtwebengine</code> package should be installed as a dependency; if not, you did something wrong (you're probably installing the old QupZilla 1.8.x instead). Then surf the web with QupZilla as you would with any other browser.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
* http://doc.qt.io/qt-5/qt5-intro.html#web-engine-and-html5<br />
* http://doc.qt.io/qt-5/qtwebengine-index.html<br />
* https://www.qupzilla.com/<br />
<br />
== Release Notes ==<br />
Fedora now includes the new QtWebEngine library, a Qt port of the Chromium web engine. Application developers are encouraged to use QtWebEngine instead of QtWebKit, which was deprecated by the Qt project in favor of QtWebEngine. QupZilla, a modern, lightweight and fast browser written in Qt, is now based on QtWebEngine instead of QtWebKit, bringing it up to date with modern web and security standards. Other QtWebKit browsers such as Konqueror (with the KWebKitPart) and Rekonq are still available, but their users may find QupZilla 2 with QtWebEngine to be a more modern alternative.<br />
<br />
[[Category:ChangeAcceptedF24]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/QtWebEngine&diff=433449Changes/QtWebEngine2016-02-02T14:33:30Z<p>Kkofler: /* Scope */ QupZilla 1.9.99 is now in Rawhide, also add the Bugzilla link.</p>
<hr />
<div>= QtWebEngine =<br />
<br />
== Summary ==<br />
QtWebEngine will be packaged for Fedora, initially at version 5.6. In addition, the QupZilla browser will be upgraded to the QtWebEngine-based QupZilla 2.<br />
<br />
== Owner ==<br />
* Name: [[User:Kkofler| Kevin Kofler]]<br />
* Email: Kevin [AT] tigcc [DOT] ticalc [DOT] org<br />
* Release notes owner: <To be assigned by docs team> <!-- [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/24 | Fedora 24 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1303611 #1303611]<br />
<br />
== Detailed Description ==<br />
<br />
QtWebEngine is the new web engine by the Qt project based on Chromium, effectively replacing QtWebKit, though it is not a drop-in replacement. QtWebEngine will be available in Fedora as an '''additional''' option. QtWebKit will remain available for the foreseeable future, and thus applications currently using QtWebKit are '''not''' impacted by this change, unless and until upstream ports them to QtWebEngine. The version initially packaged for Fedora 24 will be QtWebEngine 5.6.<br />
<br />
QupZilla is a modern, lightweight and fast browser written in Qt. QupZilla 1 was based on QtWebKit. It will be replaced by the new QupZilla 2, which is instead based on QtWebEngine.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Since the Qt upstream project has deprecated QtWebKit in Qt 5.5 and is no longer officially supporting it in Qt 5.6, more and more Qt applications will require QtWebEngine. QtWebKit is based on an old WebKit branch that was discontinued by upstream WebKit long ago, meaning it lags behind current web standards and even security fixes. QtWebEngine is based on a recent version of Chromium (QtWebEngine 5.6 is based on Chromium 45), gets backported security fixes, and will be rebased to a newer Chromium at new Qt releases, as QtWebKit was in the past.<br />
<br />
With QupZilla 2, a web browser supporting the latest web standards will be available to our users (and to spin maintainers), as an alternative to Firefox. Compared to QupZilla 1 and other QtWebKit-based browsers, both compatibility with websites and security will be significantly higher.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Package QtWebEngine 5.6.0 beta, based on [[User:Heliocastro| Helio Castro]]'s initial work: <span style="color:green">DONE</span><br />
** Remove patent-encumbered codecs from the upstream tarball using the scripts from [[User:Spot| spot]]'s Chromium packages: <span style="color:green">DONE</span><br />
** Get <code>qt5-qtwebengine</code> through review [https://bugzilla.redhat.com/show_bug.cgi?id=1295549]: <span style="color:green">DONE</span><br />
** Unbundle all libraries that can be unbundled: <span style="color:green">DONE</span><br />
** Make the package run on i686 machines without SSE2, while degrading performance for SSE2-enabled machines as little as possible: <span style="color:green">DONE</span> [http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/tree/qtwebengine-opensource-src-5.6.0-beta-no-sse2.patch]<br />
** (Nice-to-have: Look into backporting Samsung's Chromium GStreamer backend [https://github.com/Samsung/ChromiumGStreamerBackend]: <span style="color:red">TODO</span>)<br />
** Package a QupZilla 1.9.99 snapshot: <span style="color:green">DONE</span> [http://copr-dist-git.fedorainfracloud.org/cgit/kkofler/qtwebengine/qupzilla.git/tree/]<br />
** Upgrade the <code>qupzilla</code> package in Rawhide to 1.9.99 / 2.0.0 [https://bugzilla.redhat.com/show_bug.cgi?id=1298145]: <span style="color:green">DONE</span><br />
<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
QtWebEngine:<br />
* The package will be a new package. It will '''not''' replace the QtWebKit package. Therefore, no changes are required to applications.<br />
* From the user's point of view, it will simply be a new library, that may or may not get installed as a dependency by upgrades to their existing packages.<br />
<br />
QupZilla:<br />
* The user-visible changes will be of the amount expected for a new major version of a leaf application.<br />
* Manual configuration should not be needed, though some settings from the old QtWebKit-based version may no longer apply to QtWebEngine.<br />
* The most noticeable difference will be the actual web engine. Web pages may render slightly differently. Some web pages that previously did not work will start working. Some web pages that were using obsolete constructs may break, though hopefully that will not be the case. One issue may be support for patent-encumbered codecs: I hope to get GStreamer support working, which was exactly what QtWebKit used.<br />
<br />
'''There will be no impact on other packages from this change, which is why I consider it self-contained.'''<br />
<br />
== How To Test ==<br />
(A test plan is not required for a self-contained change, but here's a short one:)<br />
<br />
The easiest way to test QtWebEngine is through QupZilla 2. Just install the <code>qupzilla</code> package, version 1.9.99 or higher. For now, you can get it from the Copr repository at [https://copr.fedoraproject.org/coprs/kkofler/qtwebengine/]. The <code>qt5-qtwebengine</code> package should be installed as a dependency; if not, you did something wrong (you're probably installing the old QupZilla 1.8.x instead). Then surf the web with QupZilla as you would with any other browser.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
* http://doc.qt.io/qt-5/qt5-intro.html#web-engine-and-html5<br />
* http://doc.qt.io/qt-5/qtwebengine-index.html<br />
* https://www.qupzilla.com/<br />
<br />
== Release Notes ==<br />
Fedora now includes the new QtWebEngine library, a Qt port of the Chromium web engine. Application developers are encouraged to use QtWebEngine instead of QtWebKit, which was deprecated by the Qt project in favor of QtWebEngine. QupZilla, a modern, lightweight and fast browser written in Qt, is now based on QtWebEngine instead of QtWebKit, bringing it up to date with modern web and security standards. Other QtWebKit browsers such as Konqueror (with the KWebKitPart) and Rekonq are still available, but their users may find QupZilla 2 with QtWebEngine to be a more modern alternative.<br />
<br />
[[Category:ChangeAcceptedF24]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/QtWebEngine&diff=432587Changes/QtWebEngine2016-01-20T02:22:55Z<p>Kkofler: Initial submission, set to ChangeReadyForWrangler</p>
<hr />
<div>= QtWebEngine =<br />
<br />
== Summary ==<br />
QtWebEngine will be packaged for Fedora, initially at version 5.6. In addition, the QupZilla browser will be upgraded to the QtWebEngine-based QupZilla 2.<br />
<br />
== Owner ==<br />
* Name: [[User:Kkofler| Kevin Kofler]]<br />
* Email: Kevin [AT] tigcc [DOT] ticalc [DOT] org<br />
* Release notes owner: <To be assigned by docs team> <!-- [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/24 | Fedora 24 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
QtWebEngine is the new web engine by the Qt project based on Chromium, effectively replacing QtWebKit, though it is not a drop-in replacement. QtWebEngine will be available in Fedora as an '''additional''' option. QtWebKit will remain available for the foreseeable future, and thus applications currently using QtWebKit are '''not''' impacted by this change, unless and until upstream ports them to QtWebEngine. The version initially packaged for Fedora 24 will be QtWebEngine 5.6.<br />
<br />
QupZilla is a modern, lightweight and fast browser written in Qt. QupZilla 1 was based on QtWebKit. It will be replaced by the new QupZilla 2, which is instead based on QtWebEngine.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Since the Qt upstream project has deprecated QtWebKit in Qt 5.5 and is no longer officially supporting it in Qt 5.6, more and more Qt applications will require QtWebEngine. QtWebKit is based on an old WebKit branch that was discontinued by upstream WebKit long ago, meaning it lags behind current web standards and even security fixes. QtWebEngine is based on a recent version of Chromium (QtWebEngine 5.6 is based on Chromium 45), gets backported security fixes, and will be rebased to a newer Chromium at new Qt releases, as QtWebKit was in the past.<br />
<br />
With QupZilla 2, a web browser supporting the latest web standards will be available to our users (and to spin maintainers), as an alternative to Firefox. Compared to QupZilla 1 and other QtWebKit-based browsers, both compatibility with websites and security will be significantly higher.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Package QtWebEngine 5.6.0 beta, based on [[User:Heliocastro| Helio Castro]]'s initial work: <span style="color:green">DONE</span><br />
** Remove patent-encumbered codecs from the upstream tarball using the scripts from [[User:Spot| spot]]'s Chromium packages: <span style="color:green">DONE</span><br />
** Get <code>qt5-qtwebengine</code> through review [https://bugzilla.redhat.com/show_bug.cgi?id=1295549]: <span style="color:green">DONE</span><br />
** Unbundle all libraries that can be unbundled: <span style="color:green">DONE</span><br />
** Make the package run on i686 machines without SSE2, while degrading performance for SSE2-enabled machines as little as possible: <span style="color:green">DONE</span> [http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/tree/qtwebengine-opensource-src-5.6.0-beta-no-sse2.patch]<br />
** (Nice-to-have: Look into backporting Samsung's Chromium GStreamer backend [https://github.com/Samsung/ChromiumGStreamerBackend]: <span style="color:red">TODO</span>)<br />
** Package a QupZilla 1.9.99 snapshot: <span style="color:green">DONE</span> [http://copr-dist-git.fedorainfracloud.org/cgit/kkofler/qtwebengine/qupzilla.git/tree/]<br />
** Upgrade the <code>qupzilla</code> package in Rawhide to 1.9.99 / 2.0.0: <span style="color:red">TODO</span><br />
<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
QtWebEngine:<br />
* The package will be a new package. It will '''not''' replace the QtWebKit package. Therefore, no changes are required to applications.<br />
* From the user's point of view, it will simply be a new library, that may or may not get installed as a dependency by upgrades to their existing packages.<br />
<br />
QupZilla:<br />
* The user-visible changes will be of the amount expected for a new major version of a leaf application.<br />
* Manual configuration should not be needed, though some settings from the old QtWebKit-based version may no longer apply to QtWebEngine.<br />
* The most noticeable difference will be the actual web engine. Web pages may render slightly differently. Some web pages that previously did not work will start working. Some web pages that were using obsolete constructs may break, though hopefully that will not be the case. One issue may be support for patent-encumbered codecs: I hope to get GStreamer support working, which was exactly what QtWebKit used.<br />
<br />
'''There will be no impact on other packages from this change, which is why I consider it self-contained.'''<br />
<br />
== How To Test ==<br />
(A test plan is not required for a self-contained change, but here's a short one:)<br />
<br />
The easiest way to test QtWebEngine is through QupZilla 2. Just install the <code>qupzilla</code> package, version 1.9.99 or higher. For now, you can get it from the Copr repository at [https://copr.fedoraproject.org/coprs/kkofler/qtwebengine/]. The <code>qt5-qtwebengine</code> package should be installed as a dependency; if not, you did something wrong (you're probably installing the old QupZilla 1.8.x instead). Then surf the web with QupZilla as you would with any other browser.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
* http://doc.qt.io/qt-5/qt5-intro.html#web-engine-and-html5<br />
* http://doc.qt.io/qt-5/qtwebengine-index.html<br />
* https://www.qupzilla.com/<br />
<br />
== Release Notes ==<br />
Fedora now includes the new QtWebEngine library, a Qt port of the Chromium web engine. Application developers are encouraged to use QtWebEngine instead of QtWebKit, which was deprecated by the Qt project in favor of QtWebEngine. QupZilla, a modern, lightweight and fast browser written in Qt, is now based on QtWebEngine instead of QtWebKit, bringing it up to date with modern web and security standards. Other QtWebKit browsers such as Konqueror (with the KWebKitPart) and Rekonq are still available, but their users may find QupZilla 2 with QtWebEngine to be a more modern alternative.<br />
<br />
[[Category:ChangeReadyForWrangler]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Flock_2016_Vienna_proposal&diff=430075Flock 2016 Vienna proposal2015-12-13T00:37:07Z<p>Kkofler: /* Travel by train/bus */ Grammar fix.</p>
<hr />
<div><br />
== Staff ==<br />
* Daniel Jahre <daja@linuxwochen.at><br />
* Chris Jeitler <chris@linuxwochen.at><br />
<br />
== Vienna ==<br />
<br />
Vienna German: Wien is the capital and largest city of Austria, and one of the nine states of Austria. Vienna is Austria's primary city, with a population of about 1.8 million[1] (2.6 million within the metropolitan area,[4] nearly one third of Austria's population), and its cultural, economic, and political centre. It is the 6th-largest city by population within city limits in the European Union. Until the beginning of the 20th century it was the largest German-speaking city in the world, and before the splitting of the Austro-Hungarian Empire in World War I the city had 2 million inhabitants.[7] Today it has the second most number of German speakers after Berlin.[8][9] Vienna is host to many major international organizations, including the United Nations and OPEC. The city lies in the east of Austria and is close to the borders of the Czech Republic, Slovakia, and Hungary. These regions work together in a European Centrope border region. Along with nearby Bratislava, Vienna forms a metropolitan region with 3 million inhabitants. In 2001, the city centre was designated a UNESCO World Heritage Site.[10]<br />
<br />
[https://en.wikipedia.org/wiki/Vienna Wikpedia Vienna]<br />
<br />
== Transportation ==<br />
Vienna is best accessed by its public transportation system. The Ticket price for one week is €16,20 and includes subway, tramway, and all busses and ÖBB trains (S-Bahn etc.) within the city borders.<br />
Cabs are availabe at €3,80 + €1,42 per kilometer.<br />
<br />
===Travel by train/bus===<br />
<br />
(Prices are one way, multiply by 2 for return.)<br />
*Brno - Vienna train: €9,- second class first minute<ref name="first">Včasná jízdenka (ČD) / City-Star (MÁV) / SparSchiene (ÖBB) – cheap non-refundable tickets bound to a specific train, limited contingent; each time the contingent for a given price runs out, the price increases by 10€</ref>, €29,- first class first minute<ref name="first"/>, €27,- second class, €44,80 first class; bus (Student Agency)<ref name="cheapest">the cheapest operator we could find – feel free to edit if you know anything cheaper</ref>: €8,-<br />
*Praha - Vienna train: €19,- second class first minute<ref name="first"/>, €39,- first class first minute<ref name="first"/>, €62,60 second class, €98,20 first class; bus (Student Agency)<ref name="cheapest"/>: €9,90 to 14,-<br />
*Budapest - Vienna train: €19,- second class first minute<ref name="first"/>, €29,- first class first minute<ref name="first"/>, €38,40 second class, €61,40 first class; bus (OrangeWays)<ref name="cheapest"/>: €10,- to 17,-<br />
<br />
<references/><br />
<br />
=== Travel by plane===<br />
<br />
*US - Vienna €1000-€1300<br />
*Berlin - Vienna €120-€180<br />
*Madrid - Vienna €120-€180<br />
<br />
== Proposed Venue ==<br />
<br />
[http://www.technikum-wien.at/en/ University of Applied Sciences FH Technikum Wien]<br />
The venue has two larger lecture rooms for about 200 people each and several smaller rooms for BOF sessions and smaller lectures. Some of the rooms are fully equipped with poweroutlets for laptops to enable hack sessions.<br />
<br />
== Lodging ==<br />
Estimated lodging costs are listed below. We expect to get a good discount on all of them if we find one lodging location that fits the needs of everybody.<br />
<br />
===Hostelprices===<br />
<br />
€18,- to €55,- per night and bed.<br />
<br />
===Hotelprices===<br />
<br />
€45,- to €99,- single room<br />
<br />
€55,- to €145,- double room<br />
<br />
breakfast costs between €10 and €15, sometimes it is included in the room prices<br />
<br />
== Tourist Attractions ==<br />
* [https://en.wikipedia.org/wiki/Hofburg_Palace Hofburg Imperial Palace]<br />
* [https://en.wikipedia.org/wiki/Wiener_Riesenrad Wiener Riesenrad]<br />
* [https://en.wikipedia.org/wiki/St._Stephen's_Cathedral,_Vienna St. Stephen's Cathedral and the historic town centre]<br />
* [https://en.wikipedia.org/wiki/Spanish_Riding_School Spanisch Riding School]<br />
* [https://en.wikipedia.org/wiki/Sch%C3%B6nbrunn_Palace Schönbrunn Palace]<br />
* [https://en.wikipedia.org/wiki/United_Nations_Office_at_Vienna United Nations Office at Vienna]<br />
* lots of more famous places and buildings<br />
<br />
== Social Event ==<br />
<br />
We suggest to have the social event at a Heuriger wine tavern. It is typical for Vienna and most of the conferences that are held in Vienna have at least one social event at one of these locations. The event would include traditional food & music.<br />
<br />
{{admon/note|Heuriger is the name given to Eastern Austrian wine taverns in which specially licensed local winemakers serve their most recent year's wines for short periods following the growing season. They are renowned for their atmosphere of Gemütlichkeit shared among a throng enjoying young wine, simple food, and traditional music.}}<br />
[https://en.wikipedia.org/wiki/Heuriger Wikipedia Heuriger]<br />
<br />
===Prices===<br />
Estimated prices €80,- to €150,- per person.<br />
<br />
[[Category:Flock]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Flock_2016_Vienna_proposal&diff=430073Flock 2016 Vienna proposal2015-12-13T00:33:39Z<p>Kkofler: /* Travel by train/bus */ Consistent spelling of "Student Agency"</p>
<hr />
<div><br />
== Staff ==<br />
* Daniel Jahre <daja@linuxwochen.at><br />
* Chris Jeitler <chris@linuxwochen.at><br />
<br />
== Vienna ==<br />
<br />
Vienna German: Wien is the capital and largest city of Austria, and one of the nine states of Austria. Vienna is Austria's primary city, with a population of about 1.8 million[1] (2.6 million within the metropolitan area,[4] nearly one third of Austria's population), and its cultural, economic, and political centre. It is the 6th-largest city by population within city limits in the European Union. Until the beginning of the 20th century it was the largest German-speaking city in the world, and before the splitting of the Austro-Hungarian Empire in World War I the city had 2 million inhabitants.[7] Today it has the second most number of German speakers after Berlin.[8][9] Vienna is host to many major international organizations, including the United Nations and OPEC. The city lies in the east of Austria and is close to the borders of the Czech Republic, Slovakia, and Hungary. These regions work together in a European Centrope border region. Along with nearby Bratislava, Vienna forms a metropolitan region with 3 million inhabitants. In 2001, the city centre was designated a UNESCO World Heritage Site.[10]<br />
<br />
[https://en.wikipedia.org/wiki/Vienna Wikpedia Vienna]<br />
<br />
== Transportation ==<br />
Vienna is best accessed by its public transportation system. The Ticket price for one week is €16,20 and includes subway, tramway, and all busses and ÖBB trains (S-Bahn etc.) within the city borders.<br />
Cabs are availabe at €3,80 + €1,42 per kilometer.<br />
<br />
===Travel by train/bus===<br />
<br />
(Prices are one way, multiply by 2 for return.)<br />
*Brno - Vienna train: €9,- second class first minute<ref name="first">Včasná jízdenka (ČD) / City-Star (MÁV) / SparSchiene (ÖBB) – cheap non-refundable tickets bound to a specific train, limited contingent; each time the contingent price runs out, the price increases by 10€</ref>, €29,- first class first minute<ref name="first"/>, €27,- second class, €44,80 first class; bus (Student Agency)<ref name="cheapest">the cheapest operator we could find – feel free to edit if you know anything cheaper</ref>: €8,-<br />
*Praha - Vienna train: €19,- second class first minute<ref name="first"/>, €39,- first class first minute<ref name="first"/>, €62,60 second class, €98,20 first class; bus (Student Agency)<ref name="cheapest"/>: €9,90 to 14,-<br />
*Budapest - Vienna train: €19,- second class first minute<ref name="first"/>, €29,- first class first minute<ref name="first"/>, €38,40 second class, €61,40 first class; bus (OrangeWays)<ref name="cheapest"/>: €10,- to 17,-<br />
<br />
<references/><br />
<br />
=== Travel by plane===<br />
<br />
*US - Vienna €1000-€1300<br />
*Berlin - Vienna €120-€180<br />
*Madrid - Vienna €120-€180<br />
<br />
== Proposed Venue ==<br />
<br />
[http://www.technikum-wien.at/en/ University of Applied Sciences FH Technikum Wien]<br />
The venue has two larger lecture rooms for about 200 people each and several smaller rooms for BOF sessions and smaller lectures. Some of the rooms are fully equipped with poweroutlets for laptops to enable hack sessions.<br />
<br />
== Lodging ==<br />
Estimated lodging costs are listed below. We expect to get a good discount on all of them if we find one lodging location that fits the needs of everybody.<br />
<br />
===Hostelprices===<br />
<br />
€18,- to €55,- per night and bed.<br />
<br />
===Hotelprices===<br />
<br />
€45,- to €99,- single room<br />
<br />
€55,- to €145,- double room<br />
<br />
breakfast costs between €10 and €15, sometimes it is included in the room prices<br />
<br />
== Tourist Attractions ==<br />
* [https://en.wikipedia.org/wiki/Hofburg_Palace Hofburg Imperial Palace]<br />
* [https://en.wikipedia.org/wiki/Wiener_Riesenrad Wiener Riesenrad]<br />
* [https://en.wikipedia.org/wiki/St._Stephen's_Cathedral,_Vienna St. Stephen's Cathedral and the historic town centre]<br />
* [https://en.wikipedia.org/wiki/Spanish_Riding_School Spanisch Riding School]<br />
* [https://en.wikipedia.org/wiki/Sch%C3%B6nbrunn_Palace Schönbrunn Palace]<br />
* [https://en.wikipedia.org/wiki/United_Nations_Office_at_Vienna United Nations Office at Vienna]<br />
* lots of more famous places and buildings<br />
<br />
== Social Event ==<br />
<br />
We suggest to have the social event at a Heuriger wine tavern. It is typical for Vienna and most of the conferences that are held in Vienna have at least one social event at one of these locations. The event would include traditional food & music.<br />
<br />
{{admon/note|Heuriger is the name given to Eastern Austrian wine taverns in which specially licensed local winemakers serve their most recent year's wines for short periods following the growing season. They are renowned for their atmosphere of Gemütlichkeit shared among a throng enjoying young wine, simple food, and traditional music.}}<br />
[https://en.wikipedia.org/wiki/Heuriger Wikipedia Heuriger]<br />
<br />
===Prices===<br />
Estimated prices €80,- to €150,- per person.<br />
<br />
[[Category:Flock]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Flock_2016_Vienna_proposal&diff=430065Flock 2016 Vienna proposal2015-12-13T00:25:51Z<p>Kkofler: /* Transportation */ More accurate train/bus prices. Mention that public transport tickets also include ÖBB trains within the city borders.</p>
<hr />
<div><br />
== Staff ==<br />
* Daniel Jahre <daja@linuxwochen.at><br />
* Chris Jeitler <chris@linuxwochen.at><br />
<br />
== Vienna ==<br />
<br />
Vienna German: Wien is the capital and largest city of Austria, and one of the nine states of Austria. Vienna is Austria's primary city, with a population of about 1.8 million[1] (2.6 million within the metropolitan area,[4] nearly one third of Austria's population), and its cultural, economic, and political centre. It is the 6th-largest city by population within city limits in the European Union. Until the beginning of the 20th century it was the largest German-speaking city in the world, and before the splitting of the Austro-Hungarian Empire in World War I the city had 2 million inhabitants.[7] Today it has the second most number of German speakers after Berlin.[8][9] Vienna is host to many major international organizations, including the United Nations and OPEC. The city lies in the east of Austria and is close to the borders of the Czech Republic, Slovakia, and Hungary. These regions work together in a European Centrope border region. Along with nearby Bratislava, Vienna forms a metropolitan region with 3 million inhabitants. In 2001, the city centre was designated a UNESCO World Heritage Site.[10]<br />
<br />
[https://en.wikipedia.org/wiki/Vienna Wikpedia Vienna]<br />
<br />
== Transportation ==<br />
Vienna is best accessed by its public transportation system. The Ticket price for one week is €16,20 and includes subway, tramway, and all busses and ÖBB trains (S-Bahn etc.) within the city borders.<br />
Cabs are availabe at €3,80 + €1,42 per kilometer.<br />
<br />
===Travel by train/bus===<br />
<br />
(Prices are one way, multiply by 2 for return.)<br />
*Brno - Vienna train: €9,- second class first minute<ref name="first">Včasná jízdenka (ČD) / City-Star (MÁV) / SparSchiene (ÖBB) – cheap non-refundable tickets bound to a specific train, limited contingent; each time the contingent price runs out, the price increases by 10€</ref>, €29,- first class first minute<ref name="first"/>, €27,- second class, €44,80 first class; bus (Student Agency)<ref name="cheapest">the cheapest operator we could find – feel free to edit if you know anything cheaper</ref>: €8,-<br />
*Praha - Vienna train: €19,- second class first minute<ref name="first"/>, €39,- first class first minute<ref name="first"/>, €62,60 second class, €98,20 first class; bus (StudentAgency)<ref name="cheapest"/>: €9,90 to 14,-<br />
*Budapest - Vienna train: €19,- second class first minute<ref name="first"/>, €29,- first class first minute<ref name="first"/>, €38,40 second class, €61,40 first class; bus (OrangeWays)<ref name="cheapest"/>: €10,- to 17,-<br />
<br />
<references/><br />
<br />
=== Travel by plane===<br />
<br />
*US - Vienna €1000-€1300<br />
*Berlin - Vienna €120-€180<br />
*Madrid - Vienna €120-€180<br />
<br />
== Proposed Venue ==<br />
<br />
[http://www.technikum-wien.at/en/ University of Applied Sciences FH Technikum Wien]<br />
The venue has two larger lecture rooms for about 200 people each and several smaller rooms for BOF sessions and smaller lectures. Some of the rooms are fully equipped with poweroutlets for laptops to enable hack sessions.<br />
<br />
== Lodging ==<br />
Estimated lodging costs are listed below. We expect to get a good discount on all of them if we find one lodging location that fits the needs of everybody.<br />
<br />
===Hostelprices===<br />
<br />
€18,- to €55,- per night and bed.<br />
<br />
===Hotelprices===<br />
<br />
€45,- to €99,- single room<br />
<br />
€55,- to €145,- double room<br />
<br />
breakfast costs between €10 and €15, sometimes it is included in the room prices<br />
<br />
== Tourist Attractions ==<br />
* [https://en.wikipedia.org/wiki/Hofburg_Palace Hofburg Imperial Palace]<br />
* [https://en.wikipedia.org/wiki/Wiener_Riesenrad Wiener Riesenrad]<br />
* [https://en.wikipedia.org/wiki/St._Stephen's_Cathedral,_Vienna St. Stephen's Cathedral and the historic town centre]<br />
* [https://en.wikipedia.org/wiki/Spanish_Riding_School Spanisch Riding School]<br />
* [https://en.wikipedia.org/wiki/Sch%C3%B6nbrunn_Palace Schönbrunn Palace]<br />
* [https://en.wikipedia.org/wiki/United_Nations_Office_at_Vienna United Nations Office at Vienna]<br />
* lots of more famous places and buildings<br />
<br />
== Social Event ==<br />
<br />
We suggest to have the social event at a Heuriger wine tavern. It is typical for Vienna and most of the conferences that are held in Vienna have at least one social event at one of these locations. The event would include traditional food & music.<br />
<br />
{{admon/note|Heuriger is the name given to Eastern Austrian wine taverns in which specially licensed local winemakers serve their most recent year's wines for short periods following the growing season. They are renowned for their atmosphere of Gemütlichkeit shared among a throng enjoying young wine, simple food, and traditional music.}}<br />
[https://en.wikipedia.org/wiki/Heuriger Wikipedia Heuriger]<br />
<br />
===Prices===<br />
Estimated prices €80,- to €150,- per person.<br />
<br />
[[Category:Flock]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Kkofler&diff=426296User:Kkofler2015-10-29T22:29:51Z<p>Kkofler: /* Activities within Fedora */ Update.</p>
<hr />
<div>= Kevin Kofler =<br />
<br />
<!-- An (optional) photo of yourself (image attached to the page).<br />
--><br />
<!-- Comment out the following line if you don't have one.<br />
--><br />
<!-- ||<tableclass="floatright">[[Image:KevinKofler_FirstnameLastname-head.png]]||<br />
--><br />
<br />
See [http://www.tigen.org/kevin.kofler/ my web page] for more information about me.<br />
<br />
== Contact ==<br />
<br />
* '''Email''': kevin AT tigcc DOT ticalc DOT org<br />
* '''IRC''': Kevin_Kofler<br />
* '''GPG key''': 1634F842<br />
* '''Fedora Account''': kkofler<br />
<br />
== Activities within Fedora ==<br />
<br />
* [https://admin.fedoraproject.org/pkgdb/packager/kkofler/ Currently owned or comaintained packages] <br />
* I'm interested in [[KDE| KDE on Fedora]]. I was a member of the [[SIGs/KDE| Fedora KDE SIG]] for 8 years (2007-2015).<br />
* I might also submit packages for cross-compilation tools for TI calculators (such as the TIGCC toolchain I'm the current upstream maintainer of).</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Linuxwochen_Wien_2015&diff=405938Linuxwochen Wien 20152015-03-09T03:28:19Z<p>Kkofler: /* Available event Swag/Tools/Equipment */ I will bring hand-burned KDE media.</p>
<hr />
<div>{{header|events}}<br />
<br />
= Fedora Events: Linuxwochen Wien 2015, Vienna, Austria =<br />
<br />
The [http://www.linuxwochen.at/Wien/ Linuxwochen Wien] are an Event with a broad Scope at Users, Beginners, Developers, Administrators, Companies, and Government.<br />
It features Talks, Presentations and Workshops, and a trade-show as well. <br />
<br />
== When and Where ==<br />
* 07.-9. May 2015<br />
* Event timing has been cleared, gates are opening at 9 AM.<br />
* The event place is:<br />
<br />
FH Technikum Wien<br />
Hoechstaedtplatz 5<br />
1200 Wien<br />
<br />
* [http://osm.org/go/0JrJIIxH-- Vienna]<br />
* [http://www.openstreetmap.org/?lat=48.239145&lon=16.378125&zoom=17&layers=M&mlat=48.23966&mlon=16.37769 Location in OpenStreetmap]<br />
* It is confirmed that it's very expensive and difficult to park down in the inner town of Vienna, from 8-22 h there is a so called "short time parking zone" with fees. We could have some slots possibly for free at hotel/event side.<br />
<br />
* the event will be held this year in the new constracted building [https://maps.google.com/maps?saddr=Hoechstaedtplatz+5+1200+Wien&hl=de&ll=48.239573,16.37774&spn=0.002567,0.005284&sll=37.0625,-95.677068&sspn=35.357014,86.572266&mra=ls&t=h&z=18 google maps]<br />
<br />
== Booth Personal ==<br />
<br />
{|<br />
|Name||from||till||comment<br />
|-<br />
|[[User:Gnokii|Sirko Kemter (gnokii)]]||6th||10th||event owner<br />
|-<br />
|[[User:raphgro|Raphael Groner]]||6th||10th||if my talk proposal gets accepted and nothing more important happens meanwhile<br />
|-<br />
|}<br />
<br />
== Booth ==<br />
What we will get/will have:<br />
<br />
* Space<br />
* 2 meter table (longer available, or we get one more)<br />
* 2 chairs (if we need more we could have it)<br />
* Wireless or better wired Internet Access<br />
* electricity<br />
* Fully equipped talk rooms (Micro-port, projector, and so on)<br />
* Catering: Not included, but there is available to purchase anything in shop - water, and the more important coffee :)<br />
* demo devices to play with? like laptops ...<br />
<br />
== Available event Swag/Tools/Equipment ==<br />
<br />
* Table cloth, rollup banner (gnokii)<br />
* Fedora KDE DVD+Rs (kkofler)<br />
<br />
== Talks ==<br />
<br />
=Linuxwochen=<br />
<br />
The CfP formular can be found [https://cfp.linuxwochen.at/de/LWW15/cfp/session/new here], '''Deadline for submissions is the 15. March 2015'''<br />
<br />
{| border="1" align="center"<br />
! Speaker !! Topic !! Status<br />
|-<br />
| Your name || Your talk || {{check}}=accepted, {{caution}}=rejected<br />
|-<br />
| Raphael G. || Multimodale Testautomatisierung mit Open Source am Beispiel Smart Home || TBD<br />
|-<br />
| Kevin Kofler || Calamares – ein distributionsunabhängiges Installationsprogramm für GNU/Linux || TBD<br />
|-<br />
|}<br />
<br />
<br />
== Accomodation ==<br />
<br />
If enough persons come together gnokii will rent a apartment again. Note, you should stay '''all days''' then!<br />
<br />
== Advertisement ==<br />
<br />
* LinuxWochen Official logo [http://www.linuxwochen.at/images/stories/LWW/Austria/LWW_Austria_Logo.gif]<br />
<br />
== Status ==<br />
<br />
<br />
== Reports ==<br />
<br />
<br />
== Pictures ==<br />
<br />
<br />
== History ==<br />
<br />
[[Category:Events]] [[Category:Events 2015]] [[Category:Linuxwochen]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Linuxwochen_Wien_2015&diff=405937Linuxwochen Wien 20152015-03-09T03:27:00Z<p>Kkofler: /* Linuxwochen */ Add my talk submission.</p>
<hr />
<div>{{header|events}}<br />
<br />
= Fedora Events: Linuxwochen Wien 2015, Vienna, Austria =<br />
<br />
The [http://www.linuxwochen.at/Wien/ Linuxwochen Wien] are an Event with a broad Scope at Users, Beginners, Developers, Administrators, Companies, and Government.<br />
It features Talks, Presentations and Workshops, and a trade-show as well. <br />
<br />
== When and Where ==<br />
* 07.-9. May 2015<br />
* Event timing has been cleared, gates are opening at 9 AM.<br />
* The event place is:<br />
<br />
FH Technikum Wien<br />
Hoechstaedtplatz 5<br />
1200 Wien<br />
<br />
* [http://osm.org/go/0JrJIIxH-- Vienna]<br />
* [http://www.openstreetmap.org/?lat=48.239145&lon=16.378125&zoom=17&layers=M&mlat=48.23966&mlon=16.37769 Location in OpenStreetmap]<br />
* It is confirmed that it's very expensive and difficult to park down in the inner town of Vienna, from 8-22 h there is a so called "short time parking zone" with fees. We could have some slots possibly for free at hotel/event side.<br />
<br />
* the event will be held this year in the new constracted building [https://maps.google.com/maps?saddr=Hoechstaedtplatz+5+1200+Wien&hl=de&ll=48.239573,16.37774&spn=0.002567,0.005284&sll=37.0625,-95.677068&sspn=35.357014,86.572266&mra=ls&t=h&z=18 google maps]<br />
<br />
== Booth Personal ==<br />
<br />
{|<br />
|Name||from||till||comment<br />
|-<br />
|[[User:Gnokii|Sirko Kemter (gnokii)]]||6th||10th||event owner<br />
|-<br />
|[[User:raphgro|Raphael Groner]]||6th||10th||if my talk proposal gets accepted and nothing more important happens meanwhile<br />
|-<br />
|}<br />
<br />
== Booth ==<br />
What we will get/will have:<br />
<br />
* Space<br />
* 2 meter table (longer available, or we get one more)<br />
* 2 chairs (if we need more we could have it)<br />
* Wireless or better wired Internet Access<br />
* electricity<br />
* Fully equipped talk rooms (Micro-port, projector, and so on)<br />
* Catering: Not included, but there is available to purchase anything in shop - water, and the more important coffee :)<br />
* demo devices to play with? like laptops ...<br />
<br />
== Available event Swag/Tools/Equipment ==<br />
<br />
* Table cloth, rollup banner (gnokii)<br />
<br />
== Talks ==<br />
<br />
=Linuxwochen=<br />
<br />
The CfP formular can be found [https://cfp.linuxwochen.at/de/LWW15/cfp/session/new here], '''Deadline for submissions is the 15. March 2015'''<br />
<br />
{| border="1" align="center"<br />
! Speaker !! Topic !! Status<br />
|-<br />
| Your name || Your talk || {{check}}=accepted, {{caution}}=rejected<br />
|-<br />
| Raphael G. || Multimodale Testautomatisierung mit Open Source am Beispiel Smart Home || TBD<br />
|-<br />
| Kevin Kofler || Calamares – ein distributionsunabhängiges Installationsprogramm für GNU/Linux || TBD<br />
|-<br />
|}<br />
<br />
<br />
== Accomodation ==<br />
<br />
If enough persons come together gnokii will rent a apartment again. Note, you should stay '''all days''' then!<br />
<br />
== Advertisement ==<br />
<br />
* LinuxWochen Official logo [http://www.linuxwochen.at/images/stories/LWW/Austria/LWW_Austria_Logo.gif]<br />
<br />
== Status ==<br />
<br />
<br />
== Reports ==<br />
<br />
<br />
== Pictures ==<br />
<br />
<br />
== History ==<br />
<br />
[[Category:Events]] [[Category:Events 2015]] [[Category:Linuxwochen]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Releases/22/Schedule&diff=404037Releases/22/Schedule2015-02-16T03:55:06Z<p>Kkofler: /* Upstream Project Schedules */ Add KDE schedules.</p>
<hr />
<div>{{autolang}}<br />
{{admon/note | Fedora 22 Schedule | This is the release schedule for Fedora 22. Historical schedules are maintained on [[Releases/HistoricalSchedules|a separate page]].}}<br />
<br />
== Changes ==<br />
<br />
* [[Releases/22/ChangeSet| Fedora 22 Accepted Changes]]<br />
* Before the accepted Change set is finalized, proposed changes can be found in [[:Category:ChangeAnnounced]] or [[:Category:ChangeReadyForWrangler]]<br />
<br />
== Key Milestones ==<br />
{|<br />
|-<br />
| 2014-12-09 || Fedora 21 Release<br />
|-<br />
| 2015-01-20 || Change Checkpoint: Proposal submission deadline (System Wide Changes) <br />
|-<br />
| 2015-02-06 || Side Tag Builds Deadline<br />
|- <br />
| <strike>not scheduled for F22</strike>|| <strike>Mass Rebuild</strike><br />
|-<br />
| 2015-02-10 || Branch Fedora 22 from Rawhide<br />
|-<br />
|rowspan="4"| 2015-02-24 || [[Milestone freezes | Alpha Freeze]]<br />
|-<br />
| [[ReleaseEngineering/StringFreezePolicy|Software String Freeze]]<br />
|-<br />
| [[Changes/Policy#Change freeze|Change Checkpoint: Completion deadline (testable)]]<br />
|-<br />
| [[Updates Policy#Bodhi activation|Bodhi activation point]]<br />
|-<br />
| 2015-03-10 || Alpha Release<br />
|-<br />
|rowspan="3"| 2015-03-31 || [[L10N_Freezes#Translation_Deadline| Software Translation Deadline]]<br />
|-<br />
|[[Milestone freezes |Beta Freeze]]<br />
|-<br />
| [[Changes/Policy#Beta_deadline.2Faccepted_changes_100.25_complete|Change Checkpoint: 100% Code Complete Deadline]]<br />
|-<br />
| 2015-04-14 || Beta Release<br />
|-<br />
| 2015-05-05 || [[Milestone freezes | Final Freeze]]<br />
|-<br />
| 2015-05-19 || [[Fedora_22_Final_Release_Criteria | Fedora 22 Final Release]]<br />
|}<br />
<br />
== Detailed Schedules ==<br />
* [http://fedorapeople.org/groups/schedule/f-22/ All Detailed Schedules and iCal files]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-design-tasks.html Design]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-devel-tasks.html Development]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-docs-tasks.html Documentation]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-marketing-tasks.html Marketing]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-releng-tasks.html Release Engineering]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-quality-tasks.html Quality Assurance]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-trans-tasks.html Translation]<br />
* [http://fedorapeople.org/groups/schedule/f-22/f-22-web-tasks.html Web Sites]<br />
<br />
== Upstream Project Schedules ==<br />
<br />
Links to other significant project schedules--useful for seeing how Fedora aligns with them.<br />
<br />
* Gnome 3.16 -- [https://wiki.gnome.org/ThreePointFifteen (Date...)]<br />
* KDE Plasma 5.3.0 -- [https://techbase.kde.org/Schedules/Plasma_5 2015-04-28]<br />
* KDE Applications 15.04 -- [https://techbase.kde.org/Schedules/Applications/15.04_Release_Schedule 2015-04-15]<br />
<br />
Feel free to add any other significant projects schedules!</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=User:Kkofler&diff=402765User:Kkofler2015-02-05T17:29:55Z<p>Kkofler: /* Activities within Fedora */ Update pkgdb link.</p>
<hr />
<div>= Kevin Kofler =<br />
<br />
<!-- An (optional) photo of yourself (image attached to the page).<br />
--><br />
<!-- Comment out the following line if you don't have one.<br />
--><br />
<!-- ||<tableclass="floatright">[[Image:KevinKofler_FirstnameLastname-head.png]]||<br />
--><br />
<br />
See [http://www.tigen.org/kevin.kofler/ my web page] for more information about me.<br />
<br />
== Contact ==<br />
<br />
* '''Email''': kevin AT tigcc DOT ticalc DOT org<br />
* '''IRC''': Kevin_Kofler<br />
* '''GPG key''': 1634F842<br />
* '''Fedora Account''': kkofler<br />
<br />
== Activities within Fedora ==<br />
<br />
* [https://admin.fedoraproject.org/pkgdb/packager/kkofler/ Currently owned or comaintained packages] <br />
* I'm interested in [[KDE| KDE on Fedora]] and a member of the [[SIGs/KDE| Fedora KDE SIG]] .<br />
* I'll also be submitting packages for cross-compilation tools for TI calculators (such as the TIGCC toolchain I'm the current upstream maintainer of).</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/Plasma_5&diff=401369Changes/Plasma 52015-01-20T15:32:47Z<p>Kkofler: Set to Category:ChangeReadyForWrangler</p>
<hr />
<div>= Plasma 5 =<br />
<br />
== Summary ==<br />
Plasma 5 is successor to KDE Plasma 4 created by the KDE Community. It is based on Qt 5 and [[Changes/KDE_Frameworks_5 | KDE Frameworks 5]] and brings many changes and improvements over previous versions, including new look & feel as well as important changes under the hood.<br />
<br />
== Owner ==<br />
[[SIGs/KDE | KDE SIG]]<br />
* Names: [[User:Dvratil | Daniel Vrátil]], [[User:ltinkl | Lukáš Tinkl]], [[User:jgrulich | Jan Grulich]], [[User:rdieter | Rex Dieter]], [[User:than | Than Ngo]], [[User:kkofler | Kevin Kofler]]<br />
<br />
* Email: dvratil@redhat.com, jgrulich@redhat.com, ltinkl@redhat.com, rdieter@fedoraproject.org, than@redhat.com, kevin@tigcc.ticalc.org<br />
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/22 | Fedora 22 ]] <br />
* Last updated: 2014-01-20<br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: <will be assigned by the Wrangler><br />
<br />
<br />
* Plasma 5 Tracker: [https://bugzilla.redhat.com/show_bug.cgi?id=plasma5 plasma5]<br />
* Currently imported ~18 packages, ~8 packages are waiting for review or to be imported <br />
* Some packages are missing a port to Qt 5 and [[Changes/KDE_Frameworks_5 | KDE Frameworks 5]] or they are already being ported and were not officially released<br />
<br />
== Detailed Description ==<br />
<br />
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --><br />
<br />
Plasma 5 is a new major version of KDE's workspaces. It has a new theme called Breeze, which has cleaner visuals and better readability, improves certain work-flows and provides overal more consistent and polished interface. <br />
<br />
Changes under the hood include switch to Qt 5 and KDE Frameworks 5 and migration to fully hardware-accelerated graphics stack based on OpenGL(ES).<br />
<br />
Note that Plasma 5 only includes the actual shell, decorations, icons and a few applications coupled with workspace (e.g. KWin, System Settings, KSysGuard). It does not include "regular" applications like Dolphin, Okular, Konqueror, etc. which are part of KDE Applications product and released independently of Plasma 5.<br />
<br />
Plasma 5 gets a new feature release every three months, and each feature release has monthly bugfix releases. Plasma 5.2 is scheduled to be released on January 27. KDE SIG intends to ship Plasma 5.2.2 or Plasma 5.3, depending on the final schedules.<br />
<br />
== Benefit to Fedora ==<br />
<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--><br />
<br />
KDE is a popular, feature rich and stable desktop environment used by a lot of Fedora users. Plasma 5 brings the latest release of KDE workspace yet to Fedora.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Submit, review and import new packages for Plasma 5 to rawhide/F22<br />
** Modify existing KDE 4 packages to ensure smooth upgrade path to Plasma 5<br />
** Retire KDE 4 packages not compatible with Plasma 5, or available in Plasma 5 under different names/components<br />
<br />
* Other developers:<br />
Optionally, maintainers of 3rd party KDE Workspace 4 packages such as Plasma applets or KCMs may want to consult upstream regarding Qt 5/Frameworks versions of their packages, and eventually update them to Frameworks version, so that they are available in Plasma 5.<br />
<br />
* Release engineering: <br />
No, this change requires no coordination with rel-eng.<br />
<br />
* Policies and guidelines:<br />
No, this change requires no update to packaging guidelines or policies.<br />
<br />
== Upgrade/compatibility impact ==<br />
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --><br />
<br />
Plasma 5 is not coinstallable with KDE Workspace 4 and is treated as an update instead. Users with KDE 4 installed will be updated to Plasma 5 through regular update mechanism without any need for manual intervention. KDE SIG will work to make sure the upgrade path is smooth for all users. Configuration files will be migrated automatically by kconfupdate and by individual applications after first login to Plasma 5.<br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this change? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the change is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
Latest stable versions of Plasma 5 are currently available in [https://copr.fedoraproject.org/coprs/dvratil/plasma-5 dvratil/plasma-5 Copr], and Plasma 5.2 beta (5.1.95) is available in [https://copr.fedoraproject.org/coprs/dvratil/plasma-5-beta dvratil/plasma-5-beta Copr]. We recommend testing the 5.2 beta as it's much closer to what will land in Fedora 22. KDE SIG is currently working on importing the Plasma 5 packages from Copr to Fedora rawhide/22.<br />
<br />
Testing can be done on any hardware. Since Plasma 5 requires hardware acceleration, KDE SIG is interested in collecting feedback from as many different GPUs and drivers as possible to ensure Plasma 5 performs well on wide variaty of hardware.<br />
<br />
Individual components of Plasma 5 can be tested by simply installing Plasma 5 and using it.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<br />
KDE 4 users will find Plasma 5 environment familiar and will have no troubles orienting in the new environment. Although Plasma 5 improves and streamlines certain work-flows, the core patterns are left intact. The user interface is more polished and consistent than it was in KDE 4, which makes Plasma 5 easier to use and adopt by new users.<br />
<br />
Plasma 5 supports only applets written in QML 2 or C++, so KDE 4 applets written in QML1, JavaScript, Python or other scripting languages supported in KDE 4 will not work. This means that some users might find that their favourite applets are not available in Plasma 5 yet. Most of the core applets shipped with KDE 4 has already been ported and are available in Plasma 5, but mostly 3rd party applets are not available for Plasma 5 yet. This should change in future as Plasma 5 gains wider adoption amongst users and developers.<br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
Plasma 5 depends most notably on Qt 5 and KDE Frameworks 5 packages, all of which are already available in Fedora.<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: Rolling back to KDE 4 and shipping KDE Workspace 4.11.X. As rawhide would already have packages with version 5.x.y, we would have to increase the epoch number of all affected KDE 4 packages, and making them Obsolete their Plasma 5 equivalents (since some Plasma 5 packages have been renamed or split from larger KDE 4 packages)<br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: Before F22 beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
<br />
* [https://www.kde.org/announcements/plasma5.0/ Plasma 5.0 release announcement]<br />
* [https://www.kde.org/announcements/plasma-5.1/ Plasma 5.1 release announcement]<br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. <br />
<br />
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. <br />
--><br />
<br />
'''TODO'''<br />
<br />
[[Category:ChangeReadyForWrangler]]<br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
<!-- [[Category:SelfContainedChange]] --><br />
[[Category:SystemWideChange]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/Plasma_5&diff=401368Changes/Plasma 52015-01-20T15:31:23Z<p>Kkofler: /* Owner */ Use the e-mail address I use on Bugzilla, to prevent issues with the tracking bugs.</p>
<hr />
<div>= Plasma 5 =<br />
<br />
== Summary ==<br />
Plasma 5 is successor to KDE Plasma 4 created by the KDE Community. It is based on Qt 5 and [[Changes/KDE_Frameworks_5 | KDE Frameworks 5]] and brings many changes and improvements over previous versions, including new look & feel as well as important changes under the hood.<br />
<br />
== Owner ==<br />
[[SIGs/KDE | KDE SIG]]<br />
* Names: [[User:Dvratil | Daniel Vrátil]], [[User:ltinkl | Lukáš Tinkl]], [[User:jgrulich | Jan Grulich]], [[User:rdieter | Rex Dieter]], [[User:than | Than Ngo]], [[User:kkofler | Kevin Kofler]]<br />
<br />
* Email: dvratil@redhat.com, jgrulich@redhat.com, ltinkl@redhat.com, rdieter@fedoraproject.org, than@redhat.com, kevin@tigcc.ticalc.org<br />
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/22 | Fedora 22 ]] <br />
* Last updated: 2014-01-20<br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: <will be assigned by the Wrangler><br />
<br />
<br />
* Plasma 5 Tracker: [https://bugzilla.redhat.com/show_bug.cgi?id=plasma5 plasma5]<br />
* Currently imported ~18 packages, ~8 packages are waiting for review or to be imported <br />
* Some packages are missing a port to Qt 5 and [[Changes/KDE_Frameworks_5 | KDE Frameworks 5]] or they are already being ported and were not officially released<br />
<br />
== Detailed Description ==<br />
<br />
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --><br />
<br />
Plasma 5 is a new major version of KDE's workspaces. It has a new theme called Breeze, which has cleaner visuals and better readability, improves certain work-flows and provides overal more consistent and polished interface. <br />
<br />
Changes under the hood include switch to Qt 5 and KDE Frameworks 5 and migration to fully hardware-accelerated graphics stack based on OpenGL(ES).<br />
<br />
Note that Plasma 5 only includes the actual shell, decorations, icons and a few applications coupled with workspace (e.g. KWin, System Settings, KSysGuard). It does not include "regular" applications like Dolphin, Okular, Konqueror, etc. which are part of KDE Applications product and released independently of Plasma 5.<br />
<br />
Plasma 5 gets a new feature release every three months, and each feature release has monthly bugfix releases. Plasma 5.2 is scheduled to be released on January 27. KDE SIG intends to ship Plasma 5.2.2 or Plasma 5.3, depending on the final schedules.<br />
<br />
== Benefit to Fedora ==<br />
<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--><br />
<br />
KDE is a popular, feature rich and stable desktop environment used by a lot of Fedora users. Plasma 5 brings the latest release of KDE workspace yet to Fedora.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Submit, review and import new packages for Plasma 5 to rawhide/F22<br />
** Modify existing KDE 4 packages to ensure smooth upgrade path to Plasma 5<br />
** Retire KDE 4 packages not compatible with Plasma 5, or available in Plasma 5 under different names/components<br />
<br />
* Other developers:<br />
Optionally, maintainers of 3rd party KDE Workspace 4 packages such as Plasma applets or KCMs may want to consult upstream regarding Qt 5/Frameworks versions of their packages, and eventually update them to Frameworks version, so that they are available in Plasma 5.<br />
<br />
* Release engineering: <br />
No, this change requires no coordination with rel-eng.<br />
<br />
* Policies and guidelines:<br />
No, this change requires no update to packaging guidelines or policies.<br />
<br />
== Upgrade/compatibility impact ==<br />
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --><br />
<br />
Plasma 5 is not coinstallable with KDE Workspace 4 and is treated as an update instead. Users with KDE 4 installed will be updated to Plasma 5 through regular update mechanism without any need for manual intervention. KDE SIG will work to make sure the upgrade path is smooth for all users. Configuration files will be migrated automatically by kconfupdate and by individual applications after first login to Plasma 5.<br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this change? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the change is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
Latest stable versions of Plasma 5 are currently available in [https://copr.fedoraproject.org/coprs/dvratil/plasma-5 dvratil/plasma-5 Copr], and Plasma 5.2 beta (5.1.95) is available in [https://copr.fedoraproject.org/coprs/dvratil/plasma-5-beta dvratil/plasma-5-beta Copr]. We recommend testing the 5.2 beta as it's much closer to what will land in Fedora 22. KDE SIG is currently working on importing the Plasma 5 packages from Copr to Fedora rawhide/22.<br />
<br />
Testing can be done on any hardware. Since Plasma 5 requires hardware acceleration, KDE SIG is interested in collecting feedback from as many different GPUs and drivers as possible to ensure Plasma 5 performs well on wide variaty of hardware.<br />
<br />
Individual components of Plasma 5 can be tested by simply installing Plasma 5 and using it.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<br />
KDE 4 users will find Plasma 5 environment familiar and will have no troubles orienting in the new environment. Although Plasma 5 improves and streamlines certain work-flows, the core patterns are left intact. The user interface is more polished and consistent than it was in KDE 4, which makes Plasma 5 easier to use and adopt by new users.<br />
<br />
Plasma 5 supports only applets written in QML 2 or C++, so KDE 4 applets written in QML1, JavaScript, Python or other scripting languages supported in KDE 4 will not work. This means that some users might find that their favourite applets are not available in Plasma 5 yet. Most of the core applets shipped with KDE 4 has already been ported and are available in Plasma 5, but mostly 3rd party applets are not available for Plasma 5 yet. This should change in future as Plasma 5 gains wider adoption amongst users and developers.<br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
Plasma 5 depends most notably on Qt 5 and KDE Frameworks 5 packages, all of which are already available in Fedora.<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: Rolling back to KDE 4 and shipping KDE Workspace 4.11.X. As rawhide would already have packages with version 5.x.y, we would have to increase the epoch number of all affected KDE 4 packages, and making them Obsolete their Plasma 5 equivalents (since some Plasma 5 packages have been renamed or split from larger KDE 4 packages)<br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: Before F22 beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
<br />
* [https://www.kde.org/announcements/plasma5.0/ Plasma 5.0 release announcement]<br />
* [https://www.kde.org/announcements/plasma-5.1/ Plasma 5.1 release announcement]<br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. <br />
<br />
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. <br />
--><br />
<br />
'''TODO'''<br />
<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
<!-- [[Category:SelfContainedChange]] --><br />
[[Category:SystemWideChange]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Changes/Plasma_5&diff=401366Changes/Plasma 52015-01-20T15:29:17Z<p>Kkofler: /* Owner */ Fix my info.</p>
<hr />
<div>= Plasma 5 =<br />
<br />
== Summary ==<br />
Plasma 5 is successor to KDE Plasma 4 created by the KDE Community. It is based on Qt 5 and [[Changes/KDE_Frameworks_5 | KDE Frameworks 5]] and brings many changes and improvements over previous versions, including new look & feel as well as important changes under the hood.<br />
<br />
== Owner ==<br />
[[SIGs/KDE | KDE SIG]]<br />
* Names: [[User:Dvratil | Daniel Vrátil]], [[User:ltinkl | Lukáš Tinkl]], [[User:jgrulich | Jan Grulich]], [[User:rdieter | Rex Dieter]], [[User:than | Than Ngo]], [[User:kkofler | Kevin Kofler]]<br />
<br />
* Email: dvratil@redhat.com, jgrulich@redhat.com, ltinkl@redhat.com, rdieter@fedoraproject.org, than@redhat.com, kkofler@fedoraproject.org<br />
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/22 | Fedora 22 ]] <br />
* Last updated: 2014-01-20<br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: <will be assigned by the Wrangler><br />
<br />
<br />
* Plasma 5 Tracker: [https://bugzilla.redhat.com/show_bug.cgi?id=plasma5 plasma5]<br />
* Currently imported ~18 packages, ~8 packages are waiting for review or to be imported <br />
* Some packages are missing a port to Qt 5 and [[Changes/KDE_Frameworks_5 | KDE Frameworks 5]] or they are already being ported and were not officially released<br />
<br />
== Detailed Description ==<br />
<br />
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --><br />
<br />
Plasma 5 is a new major version of KDE's workspaces. It has a new theme called Breeze, which has cleaner visuals and better readability, improves certain work-flows and provides overal more consistent and polished interface. <br />
<br />
Changes under the hood include switch to Qt 5 and KDE Frameworks 5 and migration to fully hardware-accelerated graphics stack based on OpenGL(ES).<br />
<br />
Note that Plasma 5 only includes the actual shell, decorations, icons and a few applications coupled with workspace (e.g. KWin, System Settings, KSysGuard). It does not include "regular" applications like Dolphin, Okular, Konqueror, etc. which are part of KDE Applications product and released independently of Plasma 5.<br />
<br />
Plasma 5 gets a new feature release every three months, and each feature release has monthly bugfix releases. Plasma 5.2 is scheduled to be released on January 27. KDE SIG intends to ship Plasma 5.2.2 or Plasma 5.3, depending on the final schedules.<br />
<br />
== Benefit to Fedora ==<br />
<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--><br />
<br />
KDE is a popular, feature rich and stable desktop environment used by a lot of Fedora users. Plasma 5 brings the latest release of KDE workspace yet to Fedora.<br />
<br />
== Scope ==<br />
* Proposal owners:<br />
** Submit, review and import new packages for Plasma 5 to rawhide/F22<br />
** Modify existing KDE 4 packages to ensure smooth upgrade path to Plasma 5<br />
** Retire KDE 4 packages not compatible with Plasma 5, or available in Plasma 5 under different names/components<br />
<br />
* Other developers:<br />
Optionally, maintainers of 3rd party KDE Workspace 4 packages such as Plasma applets or KCMs may want to consult upstream regarding Qt 5/Frameworks versions of their packages, and eventually update them to Frameworks version, so that they are available in Plasma 5.<br />
<br />
* Release engineering: <br />
No, this change requires no coordination with rel-eng.<br />
<br />
* Policies and guidelines:<br />
No, this change requires no update to packaging guidelines or policies.<br />
<br />
== Upgrade/compatibility impact ==<br />
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --><br />
<br />
Plasma 5 is not coinstallable with KDE Workspace 4 and is treated as an update instead. Users with KDE 4 installed will be updated to Plasma 5 through regular update mechanism without any need for manual intervention. KDE SIG will work to make sure the upgrade path is smooth for all users. Configuration files will be migrated automatically by kconfupdate and by individual applications after first login to Plasma 5.<br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this change? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the change is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
Latest stable versions of Plasma 5 are currently available in [https://copr.fedoraproject.org/coprs/dvratil/plasma-5 dvratil/plasma-5 Copr], and Plasma 5.2 beta (5.1.95) is available in [https://copr.fedoraproject.org/coprs/dvratil/plasma-5-beta dvratil/plasma-5-beta Copr]. We recommend testing the 5.2 beta as it's much closer to what will land in Fedora 22. KDE SIG is currently working on importing the Plasma 5 packages from Copr to Fedora rawhide/22.<br />
<br />
Testing can be done on any hardware. Since Plasma 5 requires hardware acceleration, KDE SIG is interested in collecting feedback from as many different GPUs and drivers as possible to ensure Plasma 5 performs well on wide variaty of hardware.<br />
<br />
Individual components of Plasma 5 can be tested by simply installing Plasma 5 and using it.<br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<br />
KDE 4 users will find Plasma 5 environment familiar and will have no troubles orienting in the new environment. Although Plasma 5 improves and streamlines certain work-flows, the core patterns are left intact. The user interface is more polished and consistent than it was in KDE 4, which makes Plasma 5 easier to use and adopt by new users.<br />
<br />
Plasma 5 supports only applets written in QML 2 or C++, so KDE 4 applets written in QML1, JavaScript, Python or other scripting languages supported in KDE 4 will not work. This means that some users might find that their favourite applets are not available in Plasma 5 yet. Most of the core applets shipped with KDE 4 has already been ported and are available in Plasma 5, but mostly 3rd party applets are not available for Plasma 5 yet. This should change in future as Plasma 5 gains wider adoption amongst users and developers.<br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
Plasma 5 depends most notably on Qt 5 and KDE Frameworks 5 packages, all of which are already available in Fedora.<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: Rolling back to KDE 4 and shipping KDE Workspace 4.11.X. As rawhide would already have packages with version 5.x.y, we would have to increase the epoch number of all affected KDE 4 packages, and making them Obsolete their Plasma 5 equivalents (since some Plasma 5 packages have been renamed or split from larger KDE 4 packages)<br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: Before F22 beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
<br />
* [https://www.kde.org/announcements/plasma5.0/ Plasma 5.0 release announcement]<br />
* [https://www.kde.org/announcements/plasma-5.1/ Plasma 5.1 release announcement]<br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. <br />
<br />
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. <br />
--><br />
<br />
'''TODO'''<br />
<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
<!-- [[Category:SelfContainedChange]] --><br />
[[Category:SystemWideChange]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Upgrading_from_EOL_Fedora_using_package_manager&diff=399153Upgrading from EOL Fedora using package manager2014-12-22T19:24:14Z<p>Kkofler: /* Fedora 17 -> Fedora 18 */ Make the link work. (Copying&pasting the whole line still works.)</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{admon/note|Read [[Upgrading Fedora using yum]] as well|This page is an addendum to [[Upgrading Fedora using yum]]. It contains the problems you might encounter running <code>yum update</code> between specific EOL Fedora releases. Please be sure to read [[Upgrading Fedora using yum]] for an overview of the entire process as well as notes on upgrading from the oldest supported release to the current release.}}<br />
<br />
== (Legacy) Instructions to upgrade using yum ==<br />
<br />
=== 1. Back up your system ===<br />
<br />
Back up any personal data to an external hard drive or to another machine. If there is some unrecoverable error that requires a fresh install, you don't want to lose any data.<br />
<br />
=== 2. Read about common problems ===<br />
<br />
Further down in this page there is a list of common problems for specific versions. Some of them require attention before the upgrade.<br />
<br />
General advice on upgrading Fedora can be found on the [[Upgrading]] page. You should also read the [http://docs.fedoraproject.org/install-guide/ Installation Guide] and [http://docs.fedoraproject.org/release-notes/ Release Notes] for the version you plan to upgrade to - they contain important information regarding upgrading issues. Finally, check the list of [[Common {{FedoraVersion|short}} bugs]].<br />
<br />
=== 3. Clean Stuff ===<br />
<br />
Review and remove all .rpmsave and .rpmnew files before and after upgrading. (And if you have selinux enabled then remember to check security context if you move config files around.)<br />
<br />
{{admon/tip|Find unused config files|Merge and resolve the changes found by the following script: <code>for a in $(find /etc /var -name '*.rpm?*'); do diff -u $a ${a%.rpm?*}; done</code>}}<br />
<br />
Now is a good time to remove packages you don't use - especially non-standard packages.<br />
<br />
{{admon/tip|Find and review "unused" packages| You can find packages not required by other packages with the tool <code>package-cleanup</code> from the <code>yum-utils</code> package: <code>yum install yum-utils; package-cleanup --leaves</code>. These packages could be candidates for removal, but check to see whether you use them directly or if they are used by applications not backed by rpm packages. Remove them with <code>yum remove package-name-and-version</code>.<br/><br />
Another useful tool for cleaning up unused packages is <code>rpmreaper</code>. It's an ncurses application that lets you view rpm dependency graph and mark packages for deletion. Marking one package can make other packages leaf, which you can see immediately, so you don't have to run the tool several times to get rid of whole sub-tree of unused packages. Install with: <code>yum install rpmreaper</code>.<br />
}}<br />
<br />
{{admon/tip|Find and review "lost" packages| You can find orphaned packages (ie packages not in the repositories anymore) with: <code>package-cleanup --orphans</code>. This will also show packages which have been partially uninstalled but where the "%postun" script failed.}}<br />
<br />
Then remove all traces of the version you are leaving from the yum cache in <code>/var/cache/yum</code>.<br />
<br />
<pre><br />
yum clean all<br />
</pre><br />
<br />
=== 4. Switch repositories ===<br />
<br />
Update the packages that decide which yum repositories to use.<br />
<br />
<pre><br />
rpm -Uhv http://archives.fedoraproject.org/pub/fedora/linux/releases/<ReleaseNumber>/Fedora/i386/os/Packages/fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
(The architecture doesn't matter for this <code>noarch</code> package.)<br />
<br />
For archived versions of Fedora (e.g., from 14 included downwards):<br />
<pre><br />
rpm -Uhv http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/<ReleaseNumber>/Fedora/i386/os/Packages/fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
<br />
'''Note:''' Some users have reported that attempting to download through rpm returns a 550 response and "transfer failed" messages. If this is the case, you can download the rpms and install locally. Consider:<br />
<pre><br />
wget ftp://dl.fedoraproject.org/pub/fedora/linux/releases/<ReleaseNumber>/Fedora/<Arch>/os/Packages/fedora-release-*.noarch.rpm<br />
rpm -Uvh fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
For archived versions of Fedora (e.g., from 14 included downwards):<br />
<pre><br />
wget ftp://dl.fedoraproject.org/pub/archive/fedora/linux/releases/<ReleaseNumber>/Fedora/<Arch>/os/Packages/fedora-release-*.noarch.rpm<br />
rpm -Uvh fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
Make sure the new repo files isn't placed as <code>.rpmnew</code> files, perhaps by<br />
<br />
<pre><br />
mv /etc/yum.repos.d/fedora-updates.repo.rpmnew /etc/yum.repos.d/fedora-updates.repo<br />
mv /etc/yum.repos.d/fedora.repo.rpmnew /etc/yum.repos.d/fedora.repo<br />
</pre><br />
<br />
If you have 3rd party repositories configured, you may need to adjust them for the new Fedora version. If you switch from one Fedora release to another there is often nothing that needs to be done. If you switch to Rawhide from a standard Fedora release (or vice versa) then most of the time you will need to install the Rawhide release RPMs from the 3rd party repository as well (or the standard ones, if switching back).<br />
<br />
Note that the upgrade is likely to fail if there are outdated dependencies from packages not backed by a yum repository or backed by a repository which isn't ready for the new version.<br />
<br />
=== 5. Do the upgrade ===<br />
<br />
If using selinux make sure it is in permissive mode - neither disabled nor enforcing.<br />
<br />
It is a good idea to do the upgrade outside the graphical environment. Log out of your graphical desktop and then go to a text console<br />
<br />
<pre><br />
ctrl + alt + F2<br />
</pre><br />
<br />
log in as root, and go into runlevel 3<br />
<br />
<pre><br />
telinit 3<br />
</pre><br />
<br />
{{admon/warning|Once a live upgrade is started do not stop the upgrade by rebooting, killing the process, or by any other method until it is complete, doing so will cause the affected system to be in a mixed state. Partially the old release and partially the new release. In this state the system will not be reliable and will not operate as expected. The only way to recover from this is to reinstall if it occurs.}}<br />
<br />
{{admon/tip|Update all packages at once| Although you can try to update the update machinery first with <code>yum update rpm\* yum\*</code> or with <code>glibc</code>, in both cases dependencies might expand it to an almost full upgrade anyway, and simply doing a full upgrade might be more safe (but your mileage may vary). (In particular, do not upgrade rpm and yum separately if upgrading to a system with a different version of python e.g. 2.4 to 2.5.)<br />
}}<br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
<code>yum</code> might complain about conflicts or requirements. That is probably because you have used non-standard repositories or installed non-standard packages manually. Try to guess which packages cause the problem (or at least is a part of the dependency chain) - uninstall them and try again. Remember to install the packages again if they are essential.<br />
<br />
Ensure that all (new) essential packages from the new version are installed with<br />
<br />
<pre><br />
yum groupupdate Base<br />
</pre><br />
<br />
You might want to update other groups too, see<br />
<br />
<pre><br />
yum grouplist<br />
</pre><br />
<br />
For example<br />
<br />
<pre><br />
yum groupupdate "GNOME Desktop Environment" \<br />
"Development Tools" "Server Configuration Tools" \<br />
"Hardware Support" "Sound and Video" \<br />
"Graphical Internet" "Fonts" \<br />
"Games and Entertainment" "Printing Software" \<br />
"Administration Tools" "Office/Productivity" "System Tools"<br />
</pre><br />
<br />
=== 6. Preparing for reboot ===<br />
<br />
Before booting you should usually install the bootloader from your new grub by running<br />
<pre><br />
/sbin/grub-install BOOTDEVICE<br />
</pre><br />
- where BOOTDEVICE is usually <code>/dev/sda</code> (If you get an error '/dev/sda does not have any corresponding BIOS drive' from that, then try <tt>/sbin/grub-install --recheck /dev/sda</tt>.)<br />
<br />
Also, the order of init scripts could have changed from the previous version. A command to reset the order is:<br />
<pre><br />
cd /etc/rc.d/init.d; for f in *; do /sbin/chkconfig $f resetpriorities; done<br />
</pre><br />
<br />
Again, run <code>package-cleanup --orphans</code> to find packages that haven't been upgraded.<br />
<br />
== Version specific notes for EOL releases ==<br />
<br />
{{Anchor|18-19}}<br />
=== Fedora 18 -> Fedora 19 ===<br />
<br />
{{admon/warning|Incompatible systemd cgroups hierarchy layout|<br />
systemd in F19 lays out its cgroups hierarchy differently than in previous Fedora releases.<br />
<br />
The new hierarchy has some advantages, but it is incompatible with the old one. No live conversion of the hierarchy is performed during the package upgrade,<br />
so the upgraded systemd will not understand the previous state of the system correctly. This is known to affect the tracking of user sessions by systemd-logind ([[rhbug:962983|bug #962983]]).<br />
<br />
Expect breakage in active user sessions and make sure to reboot soon after performing the upgrade. If your screen locks during the upgrade, you may not be able to log back in due to the cgroup changes. Running the upgrade in a screen(1) session has been reported as a workaround (re-attach from a vt). }}<br />
<br />
Install the new Fedora 19 gpg key and upgrade: <br />
# rpm --import https://fedoraproject.org/static/FB4B18E6.txt<br />
# yum update yum<br />
# yum clean all<br />
# yum --releasever=19 --disableplugin=presto distro-sync<br />
# <br />
<br />
If you use Fedora ARM, run these commands instead:<br />
# rpm --import https://fedoraproject.org/static/BA094068.txt<br />
# yum update yum<br />
# yum clean all<br />
# yum --releasever=19 distro-sync<br />
{{Anchor|17-18}}<br />
=== Fedora 17 -> Fedora 18 ===<br />
<br />
{{admon/note | Recommended Upgrade Method (Fedora 17 and newer)|Upgrading with FedUp is the recommended way to upgrade your system!Please check [https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F How Can I Upgrade My System with FedUp?]}}<br />
<br />
<br />
'''Note: One user has reported problems trying to upgrade an Intel Mac UEFI installation using this method, including the manual bootloader migration.''' [http://anee.me/dont-update-fedora-17-to-18-using-yum-on-macbook-pro/ Read more]<br />
<br />
# Install the new Fedora 18 gpg key: {{command|su -c 'rpm --import [https://fedoraproject.org/static/DE7F38BD.txt https://fedoraproject.org/static/DE7F38BD.txt]'}}<br />
# If you are using SELinux in Enforcing mode, make sure your selinux-policy is up to date: {{command|su -c 'yum update selinux-policy'}}<br />
# Upgrade all packages:<br />
## {{command|su -c 'yum update yum'}}<br />
## {{command|su -c 'yum clean all'}}<br />
## {{command|su -c 'yum --releasever<nowiki>=</nowiki>18 --disableplugin<nowiki>=</nowiki>presto distro-sync' }} '''It is recommended that updates be enabled for this step, for best results.'''<br />
# Rebuild rpm database: {{command|su -c 'rpm --rebuilddb'}}, or rpm -qa will not work due to an upgrade of rpm<br />
<br />
If you used an outdated <code>selinux-policy</code> package in Enforcing mode during the upgrade, you may notice errors in the yum output when several packages attempt to create users and/or groups, and after the upgrade you may have problems related to these packages, including issues with logging in via GDM (you may just see a spinning cursor) and/or performing actions requiring administrative privileges. This is a result of [[rhbug:844167|bug #844167]]. If you have this problem, you should re-install the affected packages with {{command|su -c 'yum reinstall (packagenames)'}}, and then reboot. Affected packages may include libvirt-daemon and polkit: {{command|su -c 'yum reinstall libvirt-daemon polkit'}}<br />
<br />
Due to [[Features/DisplayManagerRework]], the upgrade may leave you without a display manager enabled. To solve this problem, use {{command|su -c 'systemctl enable ''yourdm''.service'}}, replacing ''yourdm'' with the display manager you intend to use, e.g. <code>gdm</code> or <code>kdm</code>.<br />
<br />
{{Anchor|16-17}}<br />
<br />
=== Fedora 16 -> Fedora 17 ===<br />
<br />
{{admon/warning||There is a general warning about upgrading via. yum being unsupported [[Upgrading_Fedora_using_yum#Upgrading_Fedora_using_yum_directly | at the top of this page]]. However Fedora 17 is '''very special'''. You should '''seriously consider''' stopping now and just using anaconda via. DVD or preupgrade, unlike all previous releases it's what the yum/rpm developers recommend. Continue at your own risk. }}<br />
<br />
First install the new Fedora 17 gpg key<br />
<br />
rpm --import https://fedoraproject.org/static/1ACA3465.txt<br />
<br />
Fedora 17 will locate the entire base operating system in /usr. The directories<br />
/bin, /sbin, /lib, /lib64 will only be symlinks:<br />
<br />
/bin → /usr/bin<br />
/sbin → /usr/sbin<br />
/lib → /usr/lib<br />
/lib64 → /usr/lib64<br />
<br />
Some reasoning behind this change is outlined here:<br />
<br />
http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge<br />
<br />
Currently installed systems need some manual steps to convert the current system<br />
to match the layout of Fedora 17. After that, the system can continue to<br />
be updated with YUM as usual.<br />
<br />
Some RPM packages in Fedora 17 are carrying an RPM dependency guard, which<br />
will make sure, they can only be installed when /bin, /sbin, /lib, /lib64 are<br />
symlinks and not directories like in Fedora 16 and older.<br />
<br />
The installed system’s base filesystem layout can not be safely altered, while<br />
the system itself is running on top of it. Dracut, the initramfs used to find<br />
and mount the root filesystem, can be instructed to convert the filesystem to<br />
match Fedora 17’s expectations.<br />
<br />
If your system has a split-off /usr, a separate mount point, the dracut /usr<br />
mount conversion logic might not work. If /usr resides on the net, then you should add "rd.neednet=1" and the network settings like "ip=dhcp" on the kernel command line.<br />
/usr on iSCSI, FCoE, NBD also is supported, as long as “netroot=...” is<br />
specified on the kernel command line for these disks (see man dracut.kernel(7)).<br />
If you have /usr on LVM, MD raid or DM raid, make sure the kernel command line has either all settings like "rd.lvm.lv=..." to ensure the /usr device is accessible in dracut or just remove all restrictions like "rd.lvm...", "rd.md...", "rd.dm...". Either way, you should probably use anaconda to update, if you are experiencing problems with a separate /usr.<br />
<br />
You will have to manually convert "/var/run" and "/var/lock" to a symbolic link.<br />
<br />
# mv -f /var/run /var/run.runmove~<br />
# ln -sfn ../run /var/run<br />
# mv -f /var/lock /var/lock.lockmove~<br />
# ln -sfn ../run/lock /var/lock<br />
<br />
Here are the steps to prepare your system, to convert it, and to be able to<br />
continue updating your installed system with yum:<br />
<br />
Download and install the most recent dracut packages:<br />
# yum update dracut<br />
<br />
You should at least have [http://harald.fedorapeople.org/downloads/dracut/dracut-009-15.fc15/dracut-009-15.fc15.noarch.rpm dracut-009-15.fc15] for Fedora 15 or [https://admin.fedoraproject.org/updates/dracut-013-22.fc16 dracut-013-22.fc16] for Fedora 16.<br />
<br />
Turn off any "hostonly" settings in /etc/dracut.conf*, if you turned on "hostonly".<br />
<br />
Update the installed initramfs image for your current kernel, and instruct<br />
dracut to include the dracut module to convert your current filesystem:<br />
# dracut --force --add convertfs<br />
<br />
If your system has a split-off /usr, a separate mount point, and you don't know the kernel command line parameter to add, you can also try (dracut tries to generate them internally), but you have to install at least [https://admin.fedoraproject.org/updates/dracut-018-55.git20120606.fc16 dracut-018].<br />
# dracut -H --force --add convertfs<br />
<br />
If dracut detects ‘rd.convertfs’ on the kernel command line at bootup, it starts<br />
the filesystem conversion of the root filesystem. If it is already converted, it will just do nothing.<br />
<br />
{{admon/warning||<code>dracut</code> will by default update the initramfs for the currently running kernel. Make sure that no new kernel has been installed since last boot and that you really will boot into the updated initramfs.}}<br />
<br />
Change the following kernel commandline parameter directly in the bootloader<br />
menu, which is shown during bootup, or edit the line in <code>/etc/grub*.cfg</code> to remove ro and rhgb and append <code>rw rd.info rd.convertfs enforcing=0</code><br />
<br />
Explanation of the options:<br />
<br />
- remove “ro” (read only)<br />
- append “rw” (read write) to let dracut mount your root filesystem writeable<br />
- remove “rhgb” (Red Hat graphical boot) to disable the graphical bootsplash<br />
- append “rd.info” to get a more verbose output from dracut<br />
- append “rd.convertfs” to enable the /usr-move conversion script in dracut<br />
- append “enforcing=0” to disable SELinux enforcement<br />
<br />
During bootup, dracut will now convert your filesystem, and /lib, /lib64, /bin<br />
and /sbin should then all be symbolic links to the corresponding directories in<br />
/usr.<br />
<br />
After the conversion, the system needs to be immediately updated to Fedora 17. No<br />
packages from Fedora 16 or Fedora 15, or older rawhide packages must be installed anymore.<br />
Make sure to disable any Fedora 15 and Fedora 16 repositories in yum!<br />
<br />
Any files with conflicting names, which the conversion could not resolve, will<br />
be backed up to files named *.usrmove~ residing in /usr/lib, /usr/lib64,<br />
/usr/bin and /usr/sbin.<br />
<br />
Verify that dracut really completed the conversion. The log messages, which dracut has generated during bootup, can be retrieved with:<br />
# dmesg | grep dracut<br />
<br />
After a successful conversion, revert the changes made to the kernel command<br />
line in the bootloader config file /etc/grub*.cfg.<br />
<br />
Then run, <br />
<br />
# rm -f /var/lib/rpm/__*<br />
# rpm --rebuilddb<br />
# yum --releasever=17 update rpm<br />
# rm -f /var/lib/rpm/__*<br />
# rpm --rebuilddb<br />
# yum --releasever=17 --disableplugin=presto distro-sync<br />
# fixfiles onboot <br />
<br />
After upgrading, all should be set and done.<br />
<br />
Have fun with your system and say “Good bye” to /bin, /sbin, /lib, /lib64 and<br />
meet them in /usr.<br />
<br />
{{Anchor|15-16}}<br />
<br />
=== Fedora 15 -> Fedora 16 ===<br />
<br />
First install the new fedora 16 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/A82BA4B7.txt<br />
</pre><br />
<br />
Next run {{command|chkconfig --list}} and note the enabled services; you will need to re-enable these with {{command|systemctl enable ''xxxxx''.service}} after you reboot, as the {{package|sysvinit}} settings aren't propagated into {{package|systemd}}. See [http://fedoraproject.org/wiki/Common_F16_bugs#Upgrade_from_previous_releases_resets_the_enablement_status_of_services release notes] for more details.<br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=16 --disableplugin=presto distro-sync<br />
</pre><br />
<br />
{{admon/warning|Bootloader change|After the upgrade, you will have the {{package|grub2}} and {{package|grub-efi}} packages installed and the {{package|grub}} package removed. However, grub will still be installed to the MBR and booting should still work. You can follow the instructions below to switch to grub2 if you choose. If installed, the {{package|firstaidkit-plugin-grub}} package may prevent the upgrade; do simply remove that package if that is the case.}}<br />
<br />
If your system uses a BIOS, or you installed Fedora via BIOS emulation mode on an EFI system (not native EFI mode), you can switch to Fedora 16's supported grub2 bootloader with the following instructions. If your system was installed by native EFI boot, do not switch to grub2, as its EFI support is still unreliable. Fedora 16's supported bootloader for native EFI installations is still grub-legacy, so you should simply continue to use the system without making any special changes to the bootloader configuration.<br />
<br />
To switch to grub2, run the command {{command|su -c '/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg'}}, then proceed as described [[#6._Preparing_for_reboot|above]] with reinstalling the bootloader, but call {{command|grub2-install /dev/XXX}} instead of{{command| grub-install /dev/XXX}}.<br />
<br />
Known you upgrade -specific issues (for common problems, see references above):<br />
* Bug [https://bugzilla.redhat.com/show_bug.cgi?id=743022 743022] - F15->F16 yum update fails with IMSM (BIOS) raid<br />
<br />
<br />
{{Anchor|14-15}}<br />
<br />
=== Fedora 14 -> Fedora 15 ===<br />
<br />
First install the new fedora 15 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/069C8460.txt<br />
</pre><br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=15 --disableplugin=presto distro-sync<br />
</pre><br />
<br />
* Do not run this from within an X terminal. Testing shows that X might hang while updating bitmap font packages.<br />
* There exist .drpms, but they don't match, due to a format change, so better disable the presto plugin by adding the option "--disableplugin=presto" (without quotes) when running yum.<br />
* The F15 <code>screen</code> client is not capable of attaching to F14 <code>screen</code> sessions. Thus, if you want to run the upgrade under <code>screen</code>, you should either upgrade <code>screen</code> itself in a separate operation or make a separate copy of <code>screen</code> to use throughout the process.<br />
* mysql 5.5.20 shipped with F15 uses InnoDB as default storage engine. After upgrading, mysqld could refuse to start-up with error ''Unknown/unsupported storage engine: InnoDB'' if argument ''skip-innodb'' is given on command line or configuration file ''/etc/my.cnf''. Workarounds are removing the line (InnoDB will be run as default engine), or adding ''default-storage-engine'' command options specifying some other storage engine.<br />
<br />
==== VirtualBox guest upgrades ====<br />
The steps above work perfectly for upgrading a Fedora 14 guest to Fedora 15, but you also need to remove the Guest Additions. If you forget, F14 -> F15 upgrades will seem to fail after the first reboot. If that happens, log in to the console with CTRL+ALT+F2 and reinstall the guest additions manually:<br />
<br />
<pre><br />
mount /dev/cdrom /media<br />
# if /dev/cdrom does not exist, try:<br />
# mount /dev/sr0 /media<br />
/bin/sh /media/VBoxLinuxAdditions.run<br />
reboot<br />
</pre><br />
<br />
{{Anchor|13-14}}<br />
<br />
=== Fedora 13 -> Fedora 14 ===<br />
<br />
First install the new fedora 14 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/97A1071F.txt<br />
</pre><br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=14 distro-sync<br />
</pre><br />
<br />
* If using VirtualBox from the Oracle repository, you must remove the VirtualBox-3.1 package before upgrading. After the upgrade is finished, install VirtualBox-3.2.<br />
<br />
If you are running SELinux you may be locked out of your machine and required to boot to single user mode to fix up your machine. [[rhbug:702865|Redhat bug 702865]] describes a fix as:<br />
<ol><br />
<li><code>setenforce 0</code><br />
<li><code>yum remove selinux-policy selinux-policy-targeted</code><br />
<li><code>rm -rf /etc/selinux/targeted</code><br />
</ol><br />
<br />
If, after upgrading you want selinux back:<br />
<ol><br />
<li><code>yum install selinux-policy selinux-policy-targeted</code><br />
<li><code>fixfiles restore</code><br />
<li><code>reboot</code><br />
</ol><br />
<br />
{{Anchor|12-13}}<br />
<br />
=== Fedora 12 -> Fedora 13 ===<br />
<br />
First install the new fedora 13 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/E8E40FDE.txt<br />
</pre><br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=13 distro-sync<br />
</pre><br />
<br />
* Testing shows that upgrading within X will cause X to hang when installing <code>bitmap-fonts-compat</code>, but it can be done anyway by making sure that <code>bitmap-fonts-compat</code> is the last package to update ... YMMV.<br />
* Intel video no longer works without Kernel Mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.<br />
* nVidia video no longer works without kernel mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.<br />
* It may be necessary to run "db_recover -h /var/lib/ldap/ ; chown ldap:ldap /var/lib/ldap/*" once in order for slapd to start.<br />
<br />
{{Anchor|11-12}}<br />
<br />
=== Fedora 11 -> Fedora 12 ===<br />
<br />
* All Fedora 12 RPM packages use XZ/LZMA compression, which is only supported by the [https://admin.fedoraproject.org/updates/F11/FEDORA-2009-7986 rpm-4.7.1-1 update] (or later) for Fedora 11. Before upgrading from Fedora 11, run <code>yum update rpm</code>.<br />
* It is not possible to update directly from Fedora 10 or earlier with yum. To upgrade from Fedora 10, first update to Fedora 11, and then upgrade from Fedora 11 to Fedora 12. If you are using a release before Fedora 10, use one of the official upgrade methods or backup your data, perform a fresh installation, and restore from backup.<br />
* Upgrades from Fedora 11 might currently fail with missing dependencies (for example related to {{package|totem-gstreamer}} or {{package|PolicyKit-kde}}). The dependencies are ok, but Fedora 11 {{package|yum}} has problems resolving them ([[rhbug:519172|bug 519172]]).<br />
* If your root filesystem does not mount with 'defaults' options, you will need to add the root filesystem's mount options to grub.conf with the kernel flag <code>rootflags</code> - initramfs does not pick up the options the way initrd used to. e.g. if you mount your root with the flags <code>data=journal,relatime</code> then you would add to the end of the 'kernel' line in grub.conf: <code>rootflags=data=journal,relatime</code> . After updating to dracut-004-4.fc12 or later, this kernel flag can be removed.<br />
<br />
{{Anchor|10-11}}<br />
<br />
=== Fedora 10 -> Fedora 11 ===<br />
<br />
* It is only possible to upgrade to Fedora 11 from an updated Fedora 10. Older systems must be upgraded to Fedora 10 first. The RPM format has been changed for Fedora 11, so the older <code>rpmlib</code> must be updated first. Otherwise the process will fail with <code>rpmlib(FileDigests)</code> dependency problems. Support for the new format has been backported to Fedora 10 in an update.<br />
<pre><br />
yum update rpm<br />
</pre><br />
* New <code>initrd</code> built when installing a new kernel while running Fedora 10 might fail. To solve that boot with an old kernel (to get the new userspace) and (re)install the new kernel.<br />
* Systems with PAE support (indicated by <code>pae</code> in <code>/proc/cpuinfo</code>) should use <code>kernel-PAE.i686</code>. The new kernel must be changed/installed manually: Set <code>DEFAULTKERNEL=kernel-PAE</code> in <code>/etc/sysconfig/kernel</code> and <code>yum install kernel-PAE</code>. Refer to [http://www.codemonkey.org.uk/?p=142 Dave Jones' blog post] for details.<br />
* The yum update step should NOT be run inside a gnome desktop session/gnome-terminal. [[rhbug:494046|494046]] could result in a unusable install when gnome-terminal segfaults during the upgrade. Update should be run in a vty, runlevel 3, or a screen session.<br />
* fedora-release-11-1.noarch changes the yum mirrorlist URL so that it uses a "metalink", but the version of yum currently in F10 doesn't understand this syntax, leading to yum downloads failing with this error message:<br />
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.<br />
Eg. </metalink>/<br />
This is [[rhbug:498720|498720]]. Workaround is to manually edit the URL in /etc/yum.repos.d/fedora.repo as described at https://www.redhat.com/archives/fedora-list/2009-June/msg00783.html<br />
* Some packages in Fedora 10 are regarded as newer than those supplied by Fedora 11 and its updates repository. These include ntpd, ntpdate ([[rhbug:506040|506040]], [[rhbug:504980|504980]]), unique, unique-devel, eclipse-changelog, eclipse-svnkit and svnkit. You may wish to remove these before performing the upgrade, then reinstall them afterwards. Doing so may require <code>--nodeps</code>.<br />
* Some i386 packages in Fedora 10 are replaced with i586, i686 or x86_64 packages in Fedora 11. These include gpm.i386, glibc-2.9-3.i386. You may wish to remove these before performing the upgrade, then reinstall them afterwards. Doing so may require <code>--nodeps</code>.<br />
* mplayer-1.0-0.104.20090204svn.fc10 from the RPM Fusion repository has a dependency on libfaad.so.0 that the depsolve doesn't find, but rpm_check_debug does. You may wish to remove mplayer before performing the upgrade, then reinstall them afterwards. Doing so may require <code>--nodeps</code>.<br />
<br />
{{Anchor|9-10}}<br />
<br />
=== Fedora 9 -> Fedora 10 ===<br />
<br />
* Check the [http://docs.fedoraproject.org/install-guide/f10/en_US/ Fedora 10 Installation Guide] and [http://docs.fedoraproject.org/release-notes/f10/en_US/ Fedora 10 Release Notes]<br />
* <code>fedora-release</code> packages can be found at <code>rpm -Uvh ftp://dl.fedoraproject.org/pub/fedora/linux/releases/10/Fedora/i386/os/Packages/fedora-release-*.noarch.rpm</code><br />
* GDM starts on tty1 by default, not tty7.<br />
* anaconda by default now refers to encrypted devices by UUID, not by device name, to better handle device name changes. An encrypted device using partition <code>/dev/sda1</code> with UUID <code>12345678-1234-1234-1234-123456789012</code> would now be called <code>/dev/mapper/luks-12345678-1234-1234-1234-123456789012</code> instead of <code>/dev/mapper/luks-sda1</code>. You may wish to make the same changes on your system on upgrade; if you do, make sure to run <code>mkinitrd</code> afterwards.<br />
* If you use non-root encrypted devices, you will need to re-run <code>mkinitrd</code> for any older kernels that you want to still boot on the system.<br />
* It's been reported that there are problems with Pidgin i.e.:<br />
** <code>pidgin-2.5.2-2.fc9.i386 from installed has depsolving problems - Error: Missing Dependency: libedataserver-1.2.so.9 is needed by package pidgin-2.5.2-2.fc9.i386 (installed)</code><br />
** the fix was to remove Pidgin<br />
<br />
{{Anchor|8-9}}<br />
=== Fedora 8 -> Fedora 9 ===<br />
<br />
* Check the [http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Installer.html#Upgrade-Related-Issues Installer section in Release Notes])<br />
* After "the incident" you should use updated fedora-release packages from <code>rpm -Uvh ftp://dl.fedoraproject.org/pub/fedora/linux/updates/9/i386.newkey/fedora-release-*.noarch.rpm</code><br />
* If you are running as a <code>xen</code> Host (Dom0) you should not upgrade to Fedora 9. [http://www.redhat.com/archives/fedora-xen/2008-March/msg00013.html] <br />
* Upgrading the thunderbird package will [[rhbug:446351|fail]] . The current workaround is <code>yum remove thunderbird; yum install thunderbird></code>.<br />
* If you are upgrading to Fedora 9 and use <code>emacs</code>, you must upgrade to the latest version of <code>emacs</code> for your prior release to ensure a clean upgrade. Fedora 8 users must have <code>emacs-22.1-10.fc8</code> or later, while Fedora 7 users must have <code>emacs-22.1-7.fc7</code>. Bug report [[rhbug:239745|here]].<br />
* Due to the switch from sysvinit to [http://fedoraproject.org/wiki/Features/Upstart Upstart] , it is recommended that users who do an upgrade on a live filesystem to Fedora 9 reboot soon afterwards. If you do not reboot, you may want to take careful note of any '/etc/inittab.rpmsave' or '/etc/inittab.rpmnew' files. When rebooting after an upgrade then be aware that sysvinit that was used to start the system can't be used to shut it down.<br />
* You may find that after upgrading, you can no longer log in to GNOME. If this is the case, use ctrl-alt-F1 to access command prompt, then check the tail of .xsession-errors. If you see a comment like "(named color or font does not exist)", then you may be able to fix this using http://matthew.peach.net.nz/2008/05/18/how-to-fix-badname-named-color-or-font-does-not-exist-error/.<br />
<br />
{{Anchor|7-8}}<br />
=== Fedora 7 -> Fedora 8 ===<br />
<br />
* New pulseaudio and flash support packages must be installed manually:<br />
<br />
<pre><br />
yum groupinstall sound-and-video gnome-desktop (if you are using Gnome)<br />
yum groupinstall sound-and-video kde-desktop (if you are using KDE)<br />
yum install libflashsupport paman padevchooser<br />
</pre><br />
<br />
* The Fedora 7 avahi packagage fails to uninstall; remove it manually with<br />
<br />
<pre><br />
rpm -e --noscripts avahi-0.6.17-1.fc7<br />
</pre><br />
<br />
* On 64 bit machines (x86_64) you may have to remove some 32 bit libraries. For example dbus:<br />
<br />
<pre><br />
yum erase dbus.i386<br />
</pre><br />
<br />
* You may find it easier to use the yum shell to stack these commands in a single transaction:<br />
<br />
<pre><br />
yum shell<br />
> erase dbus.i386<br />
> update<br />
> run<br />
</pre><br />
<br />
* A lot of KDE packages are no longer multilib in F8. If you are on x86_64, you will need to erase the i386 versions of these packages by hand, like so:<br />
<br />
<pre><br />
yum erase kde{accessibility{,-devel},base,edu,graphics,multimedia{,-extras},network,sdk,utils{,-devel},webdev}.i386<br />
</pre><br />
<br />
* Various other packages including Beryl are no longer in F8 and not obsoleted:<br />
<br />
<pre><br />
yum erase beryl\*<br />
</pre><br />
<br />
{{Anchor|6-7}}<br />
=== Fedora Core 6 -> Fedora 7 ===<br />
<br />
* Fedora 7 replaces the old IDE subsystem with libata. Drive device names which previously started /dev/hd.. will become /dev/sd.. after the upgrade. /dev/hda1 will usually become /dev/sda1, although there may not be a direct relationship between the old and new device names (for example hdd does not necessarily become sdd). Before you reboot be sure to change all references to /dev/hd.. in your config, especially /etc/fstab - where it however may be simpler to refer to filesystems by label (check out the programs blkid, tune2fs, and mlabel). LVM Volume names are not affected. In /boot/grub/device.map change /dev/hd.. to /dev/sd.. before running grub-install - and don't change (hd0). Changing /boot/grub/grub.conf may also be required.<br />
<br />
* The libata layer represents all hard disks as SCSI disks, which are limited to 15 partitions in the kernel. IDE hard disks with more than 15 partitions are not supported in Fedora 7.<br />
<br />
* On a system which has been upgraded from releases prior to FC6 you may need to remove up2date and rhnlib <code>rpm -e rhnlib up2date</code><br />
<br />
* If you see the message <code>package gpm-1.20.1-84.fc6 (which is newer than gpm-1.20.1-83.fc7) is already installed</code> when performing a <code>yum update</code> uninstall and reinstall the gpm package.<br />
<br />
* If you had installed Suns jre it might be removed during upgrade. Be aware that <code>jre-6u1</code>/<code>jre-1.6.0_01-fcs</code> requires <code>compat-libstdc++-33</code>.<br />
<br />
* If you get <code>Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python</code> and/or <code>Error: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python</code> during your <code>yum upgrade</code> ensure you have done a <code>yum clean all</code> and check that both the <code>base</code> and <code>updates</code> repositories are available from your mirror. You will need the <code>updates</code> repo for the upgrade to succeed.<br />
<br />
* Since Fedora Core 6 uses python 2.4 and Fedora 7 uses python 2.5, do not try and run <code>yum upgrade yum\* rpm\*</code> before upgrading everything else - this succeeds but leaves yum in an unusable state.<br />
<br />
=== Fedora Core 5 -> Fedora Core 6 ===<br />
<br />
* After upgrading, you cannot use the DVD ISO loopback mounted as a repository directly (e.g. no <code>baseurl=file:///mnt/fc6/</code>) because the repodata files contain URLs of type <code>media://</code> which yum can't handle. You can use the loopback-mounted DVD for the initial upgrade from FC5 -> FC6, just not thereafter. After removing the <code>baseurl=file:///</code> option from your <code>fedora-core.repo</code> file, remember to <code>yum clean all</code>.<br />
<br />
=== Fedora Core 4 -> Fedora Core 5 ===<br />
<br />
* Before upgrading update your kernel first.<br />
<br />
* Make sure you have the latest kernel ABOVE 2.6.14 and uninstall all kernel versions before it, otherwise initscripts and a few other packages will conflict and prevent the ugprade. Use something like the command below<br />
<br />
* Install <code>fedora-release</code> in the Fedora Core 5 version. Check our [http://fedora.redhat.com/Download/mirrors.html mirror sites] for a faster download.<br />
<br />
* Update your system<br />
<br />
* After upgrading, selinux permissions may be incorrect, causing interesting failures such as metacity not starting. As suggested below, to fix this, run <code>touch /.autorelabel</code> and reboot<br />
<br />
=== Fedora Core 3 -> Fedora Core 4 ===<br />
<br />
* make sure you're on the latest version of yum for FC3:<br />
<code> yum update yum </code><br />
* Download fedora-release for FC4:<br />
* wget http://yourmirrorhere/pub/fedora/linux/core/4/$yourarch/os/Fedora/RPMS/fedora-release-4-2.noarch.rpm<br />
* <code>rpm -Uvh /path/to/fedora-release-4-2.noarch.rpm</code><br />
* yum update ( This will start the upgradation process to FC4)<br />
* Once you have updated, run: <code>yum groupinstall "GNOME Desktop Environment"</code> (change GNOME to KDE if appropriate). That'll get you some new packages that were added in FC4 like Evince and NetworkManager.<br />
* Some new groups were added - <code> yum grouplist </code> - check out Eclipse and Java Development in particular.<br />
<br />
Problems:<br />
<br />
* Postgres database in FC4 has a newer incompatible format from the previous versions. Manual dump and restoration is required if you using this database. Look at the postgres documentation for more details on this.<br />
<br />
* kernel requires kernel-utils (or vice-versa) run:<br />
<pre><br />
yum update kernel<br />
reboot<br />
yum remove kernel-2.6.11\*FC3\*<br />
yum upgrade<br />
reboot<br />
</pre><br />
<br />
* Takes forever and a day and hangs at:<br />
<code> Reading repository metadata in from local files </code><br />
This means you have too much crap in your rpmdb and it's taking a while to go through it. Check out how many kernels you have installed: rpm -q kernel kernel-smp and remove the old ones you may also try running: rpm --rebuilddb and see if it helps any. I've found that removing old kernels and rebuilding the rpmdb helped this problem.<br />
<br />
* x86_64 upgrade requires removal of certain i386 packages before update<br />
<pre><br />
yum remove perl.i386<br />
TODO: Add list of bonobo i386 packages to remove here<br />
</pre><br />
* Error: Missing Dependency: libpython2.3.so.1.0 is needed by package koffice<br />
koffice was removed from Fedora Core and not moved to extras - so there's no way to complete an upgrade to FC4<br />
without removing it. run:<br />
<pre><br />
yum remove koffice<br />
</pre><br />
then your update should complete.<br />
<br />
* x86_64 systems seems to hang during "Running Transaction Test"<br />
<br />
Seems related to bug [[rhbug:155730|155730]] -- Maybe a update to the "rpm-4.3.3-3.0.fc3" (currently in updates-testing) might solve this. Ugly workaround (to be done as root):<br />
<pre><br />
: > /var/log/lastlog<br />
</pre><br />
<br />
* GPG check fails with this message :<br />
<pre><br />
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID db42a60e<br />
public key not available for <some_package><br />
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora<br />
<br />
The GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora (0x4F2A6FD2)<br />
is already installed but is not the correct key for this package.<br />
Check that this is the correct key for the "Fedora Core 4 - i386 - Base" repository.<br />
</pre><br />
Edit /etc/yum.repos.d/fedora.repo and replace the line<br />
<pre><br />
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora<br />
</pre><br />
with:<br />
<pre><br />
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY<br />
</pre><br />
<br />
* SELinux gets messed up. I had to redownload the selinux-policy-targeted RPM from my mirror, do a forced uninstall of the old package, clean out the .rpmnew and .rpmsave files then install the new policy. Then I had to run "/sbin/fixfiles relabel" and wait. If I didn't do that, I found I couldn't log in.<br />
* If SELinux does give you problems, it can be disabled on bootup by pressing "a" on the grub bootup menu, then adding "enforcing=off" to the arguments list.<br />
<br />
* RPM complains about missing diskspace, but there is a lot free. If you are really sure your diskspace is enough, set<br />
<pre><br />
diskspacecheck=0<br />
</code> in <code>/etc/yum.conf</code>.<br />
The RPM transaction will need a lot of diskspace temporarily (much more than one might think), so be careful.<br />
Don't forget to remove that later after the upgrade.<br />
<br />
* Yum complains about files conflicting in the GCC package. This system was upgraded from Fedora Core 1. Remove the gcc32 package:<br />
<pre><br />
sudo rpm -e gcc32<br />
</pre><br />
<br />
* Some of your modules don't load after the upgrade. When you investigate modprobe doesn't work as expected. Run depmod:<br />
<pre><br />
sudo depmod -ae -F /boot/System.map-[your <code>uname -a</code> kernel version here] <br />
</pre><br />
<br />
* Yum has been reported to be hanging after upgrading. Updating the pysqlite package might fix it.<br />
<br />
=== Fedora Core 2 -> Fedora Core 3 ===<br />
<br />
Go here for most of this info:<br />
https://web.archive.org/web/20080430083623/http://linux.duke.edu/~skvidal/misc/fc2-fc3-update-with-yum.txt<br />
<br />
=== Fedora Core 1 -> Fedora Core 2 ===<br />
<br />
Just Upgrade using anaconda - save yourself a world of pain. But if you really want to try, there's these hints by Seth Vidal: https://web.archive.org/web/20080720005856/http://linux.duke.edu/~skvidal/misc/fc1-fc2-yum-hints.txt<br />
<br />
[[Category:FAQ]][[Category:How to]][[Category:Documentation]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Upgrading_from_EOL_Fedora_using_package_manager&diff=399084Upgrading from EOL Fedora using package manager2014-12-21T11:38:08Z<p>Kkofler: Fix broken links for the FC1→FC2 and FC2→FC3 hints, courtesy of the Internet Archive Wayback Machine.</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{admon/note|Read [[Upgrading Fedora using yum]] as well|This page is an addendum to [[Upgrading Fedora using yum]]. It contains the problems you might encounter running <code>yum update</code> between specific EOL Fedora releases. Please be sure to read [[Upgrading Fedora using yum]] for an overview of the entire process as well as notes on upgrading from the oldest supported release to the current release.}}<br />
<br />
== (Legacy) Instructions to upgrade using yum ==<br />
<br />
=== 1. Back up your system ===<br />
<br />
Back up any personal data to an external hard drive or to another machine. If there is some unrecoverable error that requires a fresh install, you don't want to lose any data.<br />
<br />
=== 2. Read about common problems ===<br />
<br />
Further down in this page there is a list of common problems for specific versions. Some of them require attention before the upgrade.<br />
<br />
General advice on upgrading Fedora can be found on the [[Upgrading]] page. You should also read the [http://docs.fedoraproject.org/install-guide/ Installation Guide] and [http://docs.fedoraproject.org/release-notes/ Release Notes] for the version you plan to upgrade to - they contain important information regarding upgrading issues. Finally, check the list of [[Common {{FedoraVersion|short}} bugs]].<br />
<br />
=== 3. Clean Stuff ===<br />
<br />
Review and remove all .rpmsave and .rpmnew files before and after upgrading. (And if you have selinux enabled then remember to check security context if you move config files around.)<br />
<br />
{{admon/tip|Find unused config files|Merge and resolve the changes found by the following script: <code>for a in $(find /etc /var -name '*.rpm?*'); do diff -u $a ${a%.rpm?*}; done</code>}}<br />
<br />
Now is a good time to remove packages you don't use - especially non-standard packages.<br />
<br />
{{admon/tip|Find and review "unused" packages| You can find packages not required by other packages with the tool <code>package-cleanup</code> from the <code>yum-utils</code> package: <code>yum install yum-utils; package-cleanup --leaves</code>. These packages could be candidates for removal, but check to see whether you use them directly or if they are used by applications not backed by rpm packages. Remove them with <code>yum remove package-name-and-version</code>.<br/><br />
Another useful tool for cleaning up unused packages is <code>rpmreaper</code>. It's an ncurses application that lets you view rpm dependency graph and mark packages for deletion. Marking one package can make other packages leaf, which you can see immediately, so you don't have to run the tool several times to get rid of whole sub-tree of unused packages. Install with: <code>yum install rpmreaper</code>.<br />
}}<br />
<br />
{{admon/tip|Find and review "lost" packages| You can find orphaned packages (ie packages not in the repositories anymore) with: <code>package-cleanup --orphans</code>. This will also show packages which have been partially uninstalled but where the "%postun" script failed.}}<br />
<br />
Then remove all traces of the version you are leaving from the yum cache in <code>/var/cache/yum</code>.<br />
<br />
<pre><br />
yum clean all<br />
</pre><br />
<br />
=== 4. Switch repositories ===<br />
<br />
Update the packages that decide which yum repositories to use.<br />
<br />
<pre><br />
rpm -Uhv http://archives.fedoraproject.org/pub/fedora/linux/releases/<ReleaseNumber>/Fedora/i386/os/Packages/fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
(The architecture doesn't matter for this <code>noarch</code> package.)<br />
<br />
For archived versions of Fedora (e.g., from 14 included downwards):<br />
<pre><br />
rpm -Uhv http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/<ReleaseNumber>/Fedora/i386/os/Packages/fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
<br />
'''Note:''' Some users have reported that attempting to download through rpm returns a 550 response and "transfer failed" messages. If this is the case, you can download the rpms and install locally. Consider:<br />
<pre><br />
wget ftp://dl.fedoraproject.org/pub/fedora/linux/releases/<ReleaseNumber>/Fedora/<Arch>/os/Packages/fedora-release-*.noarch.rpm<br />
rpm -Uvh fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
For archived versions of Fedora (e.g., from 14 included downwards):<br />
<pre><br />
wget ftp://dl.fedoraproject.org/pub/archive/fedora/linux/releases/<ReleaseNumber>/Fedora/<Arch>/os/Packages/fedora-release-*.noarch.rpm<br />
rpm -Uvh fedora-release-*.noarch.rpm<br />
</pre><br />
<br />
Make sure the new repo files isn't placed as <code>.rpmnew</code> files, perhaps by<br />
<br />
<pre><br />
mv /etc/yum.repos.d/fedora-updates.repo.rpmnew /etc/yum.repos.d/fedora-updates.repo<br />
mv /etc/yum.repos.d/fedora.repo.rpmnew /etc/yum.repos.d/fedora.repo<br />
</pre><br />
<br />
If you have 3rd party repositories configured, you may need to adjust them for the new Fedora version. If you switch from one Fedora release to another there is often nothing that needs to be done. If you switch to Rawhide from a standard Fedora release (or vice versa) then most of the time you will need to install the Rawhide release RPMs from the 3rd party repository as well (or the standard ones, if switching back).<br />
<br />
Note that the upgrade is likely to fail if there are outdated dependencies from packages not backed by a yum repository or backed by a repository which isn't ready for the new version.<br />
<br />
=== 5. Do the upgrade ===<br />
<br />
If using selinux make sure it is in permissive mode - neither disabled nor enforcing.<br />
<br />
It is a good idea to do the upgrade outside the graphical environment. Log out of your graphical desktop and then go to a text console<br />
<br />
<pre><br />
ctrl + alt + F2<br />
</pre><br />
<br />
log in as root, and go into runlevel 3<br />
<br />
<pre><br />
telinit 3<br />
</pre><br />
<br />
{{admon/warning|Once a live upgrade is started do not stop the upgrade by rebooting, killing the process, or by any other method until it is complete, doing so will cause the affected system to be in a mixed state. Partially the old release and partially the new release. In this state the system will not be reliable and will not operate as expected. The only way to recover from this is to reinstall if it occurs.}}<br />
<br />
{{admon/tip|Update all packages at once| Although you can try to update the update machinery first with <code>yum update rpm\* yum\*</code> or with <code>glibc</code>, in both cases dependencies might expand it to an almost full upgrade anyway, and simply doing a full upgrade might be more safe (but your mileage may vary). (In particular, do not upgrade rpm and yum separately if upgrading to a system with a different version of python e.g. 2.4 to 2.5.)<br />
}}<br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum upgrade<br />
</pre><br />
<br />
<code>yum</code> might complain about conflicts or requirements. That is probably because you have used non-standard repositories or installed non-standard packages manually. Try to guess which packages cause the problem (or at least is a part of the dependency chain) - uninstall them and try again. Remember to install the packages again if they are essential.<br />
<br />
Ensure that all (new) essential packages from the new version are installed with<br />
<br />
<pre><br />
yum groupupdate Base<br />
</pre><br />
<br />
You might want to update other groups too, see<br />
<br />
<pre><br />
yum grouplist<br />
</pre><br />
<br />
For example<br />
<br />
<pre><br />
yum groupupdate "GNOME Desktop Environment" \<br />
"Development Tools" "Server Configuration Tools" \<br />
"Hardware Support" "Sound and Video" \<br />
"Graphical Internet" "Fonts" \<br />
"Games and Entertainment" "Printing Software" \<br />
"Administration Tools" "Office/Productivity" "System Tools"<br />
</pre><br />
<br />
=== 6. Preparing for reboot ===<br />
<br />
Before booting you should usually install the bootloader from your new grub by running<br />
<pre><br />
/sbin/grub-install BOOTDEVICE<br />
</pre><br />
- where BOOTDEVICE is usually <code>/dev/sda</code> (If you get an error '/dev/sda does not have any corresponding BIOS drive' from that, then try <tt>/sbin/grub-install --recheck /dev/sda</tt>.)<br />
<br />
Also, the order of init scripts could have changed from the previous version. A command to reset the order is:<br />
<pre><br />
cd /etc/rc.d/init.d; for f in *; do /sbin/chkconfig $f resetpriorities; done<br />
</pre><br />
<br />
Again, run <code>package-cleanup --orphans</code> to find packages that haven't been upgraded.<br />
<br />
== Version specific notes for EOL releases ==<br />
<br />
{{Anchor|18-19}}<br />
=== Fedora 18 -> Fedora 19 ===<br />
<br />
{{admon/warning|Incompatible systemd cgroups hierarchy layout|<br />
systemd in F19 lays out its cgroups hierarchy differently than in previous Fedora releases.<br />
<br />
The new hierarchy has some advantages, but it is incompatible with the old one. No live conversion of the hierarchy is performed during the package upgrade,<br />
so the upgraded systemd will not understand the previous state of the system correctly. This is known to affect the tracking of user sessions by systemd-logind ([[rhbug:962983|bug #962983]]).<br />
<br />
Expect breakage in active user sessions and make sure to reboot soon after performing the upgrade. If your screen locks during the upgrade, you may not be able to log back in due to the cgroup changes. Running the upgrade in a screen(1) session has been reported as a workaround (re-attach from a vt). }}<br />
<br />
Install the new Fedora 19 gpg key and upgrade: <br />
# rpm --import https://fedoraproject.org/static/FB4B18E6.txt<br />
# yum update yum<br />
# yum clean all<br />
# yum --releasever=19 --disableplugin=presto distro-sync<br />
# <br />
<br />
If you use Fedora ARM, run these commands instead:<br />
# rpm --import https://fedoraproject.org/static/BA094068.txt<br />
# yum update yum<br />
# yum clean all<br />
# yum --releasever=19 distro-sync<br />
{{Anchor|17-18}}<br />
=== Fedora 17 -> Fedora 18 ===<br />
<br />
{{admon/note | Recommended Upgrade Method (Fedora 17 and newer)|Upgrading with FedUp is the recommended way to upgrade your system!Please check [https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F How Can I Upgrade My System with FedUp?]}}<br />
<br />
<br />
'''Note: One user has reported problems trying to upgrade an Intel Mac UEFI installation using this method, including the manual bootloader migration.''' [http://anee.me/dont-update-fedora-17-to-18-using-yum-on-macbook-pro/ Read more]<br />
<br />
# Install the new Fedora 18 gpg key: {{command|su -c 'rpm --import https://fedoraproject.org/static/DE7F38BD.txt'}}<br />
# If you are using SELinux in Enforcing mode, make sure your selinux-policy is up to date: {{command|su -c 'yum update selinux-policy'}}<br />
# Upgrade all packages:<br />
## {{command|su -c 'yum update yum'}}<br />
## {{command|su -c 'yum clean all'}}<br />
## {{command|su -c 'yum --releasever<nowiki>=</nowiki>18 --disableplugin<nowiki>=</nowiki>presto distro-sync' }} '''It is recommended that updates be enabled for this step, for best results.'''<br />
# Rebuild rpm database: {{command|su -c 'rpm --rebuilddb'}}, or rpm -qa will not work due to an upgrade of rpm<br />
<br />
If you used an outdated <code>selinux-policy</code> package in Enforcing mode during the upgrade, you may notice errors in the yum output when several packages attempt to create users and/or groups, and after the upgrade you may have problems related to these packages, including issues with logging in via GDM (you may just see a spinning cursor) and/or performing actions requiring administrative privileges. This is a result of [[rhbug:844167|bug #844167]]. If you have this problem, you should re-install the affected packages with {{command|su -c 'yum reinstall (packagenames)'}}, and then reboot. Affected packages may include libvirt-daemon and polkit: {{command|su -c 'yum reinstall libvirt-daemon polkit'}}<br />
<br />
Due to [[Features/DisplayManagerRework]], the upgrade may leave you without a display manager enabled. To solve this problem, use {{command|su -c 'systemctl enable ''yourdm''.service'}}, replacing ''yourdm'' with the display manager you intend to use, e.g. <code>gdm</code> or <code>kdm</code>.<br />
<br />
{{Anchor|16-17}}<br />
=== Fedora 16 -> Fedora 17 ===<br />
<br />
{{admon/warning||There is a general warning about upgrading via. yum being unsupported [[Upgrading_Fedora_using_yum#Upgrading_Fedora_using_yum_directly | at the top of this page]]. However Fedora 17 is '''very special'''. You should '''seriously consider''' stopping now and just using anaconda via. DVD or preupgrade, unlike all previous releases it's what the yum/rpm developers recommend. Continue at your own risk. }}<br />
<br />
First install the new Fedora 17 gpg key<br />
<br />
rpm --import https://fedoraproject.org/static/1ACA3465.txt<br />
<br />
Fedora 17 will locate the entire base operating system in /usr. The directories<br />
/bin, /sbin, /lib, /lib64 will only be symlinks:<br />
<br />
/bin → /usr/bin<br />
/sbin → /usr/sbin<br />
/lib → /usr/lib<br />
/lib64 → /usr/lib64<br />
<br />
Some reasoning behind this change is outlined here:<br />
<br />
http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge<br />
<br />
Currently installed systems need some manual steps to convert the current system<br />
to match the layout of Fedora 17. After that, the system can continue to<br />
be updated with YUM as usual.<br />
<br />
Some RPM packages in Fedora 17 are carrying an RPM dependency guard, which<br />
will make sure, they can only be installed when /bin, /sbin, /lib, /lib64 are<br />
symlinks and not directories like in Fedora 16 and older.<br />
<br />
The installed system’s base filesystem layout can not be safely altered, while<br />
the system itself is running on top of it. Dracut, the initramfs used to find<br />
and mount the root filesystem, can be instructed to convert the filesystem to<br />
match Fedora 17’s expectations.<br />
<br />
If your system has a split-off /usr, a separate mount point, the dracut /usr<br />
mount conversion logic might not work. If /usr resides on the net, then you should add "rd.neednet=1" and the network settings like "ip=dhcp" on the kernel command line.<br />
/usr on iSCSI, FCoE, NBD also is supported, as long as “netroot=...” is<br />
specified on the kernel command line for these disks (see man dracut.kernel(7)).<br />
If you have /usr on LVM, MD raid or DM raid, make sure the kernel command line has either all settings like "rd.lvm.lv=..." to ensure the /usr device is accessible in dracut or just remove all restrictions like "rd.lvm...", "rd.md...", "rd.dm...". Either way, you should probably use anaconda to update, if you are experiencing problems with a separate /usr.<br />
<br />
You will have to manually convert "/var/run" and "/var/lock" to a symbolic link.<br />
<br />
# mv -f /var/run /var/run.runmove~<br />
# ln -sfn ../run /var/run<br />
# mv -f /var/lock /var/lock.lockmove~<br />
# ln -sfn ../run/lock /var/lock<br />
<br />
Here are the steps to prepare your system, to convert it, and to be able to<br />
continue updating your installed system with yum:<br />
<br />
Download and install the most recent dracut packages:<br />
# yum update dracut<br />
<br />
You should at least have [http://harald.fedorapeople.org/downloads/dracut/dracut-009-15.fc15/dracut-009-15.fc15.noarch.rpm dracut-009-15.fc15] for Fedora 15 or [https://admin.fedoraproject.org/updates/dracut-013-22.fc16 dracut-013-22.fc16] for Fedora 16.<br />
<br />
Turn off any "hostonly" settings in /etc/dracut.conf*, if you turned on "hostonly".<br />
<br />
Update the installed initramfs image for your current kernel, and instruct<br />
dracut to include the dracut module to convert your current filesystem:<br />
# dracut --force --add convertfs<br />
<br />
If your system has a split-off /usr, a separate mount point, and you don't know the kernel command line parameter to add, you can also try (dracut tries to generate them internally), but you have to install at least [https://admin.fedoraproject.org/updates/dracut-018-55.git20120606.fc16 dracut-018].<br />
# dracut -H --force --add convertfs<br />
<br />
If dracut detects ‘rd.convertfs’ on the kernel command line at bootup, it starts<br />
the filesystem conversion of the root filesystem. If it is already converted, it will just do nothing.<br />
<br />
{{admon/warning||<code>dracut</code> will by default update the initramfs for the currently running kernel. Make sure that no new kernel has been installed since last boot and that you really will boot into the updated initramfs.}}<br />
<br />
Change the following kernel commandline parameter directly in the bootloader<br />
menu, which is shown during bootup, or edit the line in <code>/etc/grub*.cfg</code> to remove ro and rhgb and append <code>rw rd.info rd.convertfs enforcing=0</code><br />
<br />
Explanation of the options:<br />
<br />
- remove “ro” (read only)<br />
- append “rw” (read write) to let dracut mount your root filesystem writeable<br />
- remove “rhgb” (Red Hat graphical boot) to disable the graphical bootsplash<br />
- append “rd.info” to get a more verbose output from dracut<br />
- append “rd.convertfs” to enable the /usr-move conversion script in dracut<br />
- append “enforcing=0” to disable SELinux enforcement<br />
<br />
During bootup, dracut will now convert your filesystem, and /lib, /lib64, /bin<br />
and /sbin should then all be symbolic links to the corresponding directories in<br />
/usr.<br />
<br />
After the conversion, the system needs to be immediately updated to Fedora 17. No<br />
packages from Fedora 16 or Fedora 15, or older rawhide packages must be installed anymore.<br />
Make sure to disable any Fedora 15 and Fedora 16 repositories in yum!<br />
<br />
Any files with conflicting names, which the conversion could not resolve, will<br />
be backed up to files named *.usrmove~ residing in /usr/lib, /usr/lib64,<br />
/usr/bin and /usr/sbin.<br />
<br />
Verify that dracut really completed the conversion. The log messages, which dracut has generated during bootup, can be retrieved with:<br />
# dmesg | grep dracut<br />
<br />
After a successful conversion, revert the changes made to the kernel command<br />
line in the bootloader config file /etc/grub*.cfg.<br />
<br />
Then run, <br />
<br />
# rm -f /var/lib/rpm/__*<br />
# rpm --rebuilddb<br />
# yum --releasever=17 update rpm<br />
# rm -f /var/lib/rpm/__*<br />
# rpm --rebuilddb<br />
# yum --releasever=17 --disableplugin=presto distro-sync<br />
# fixfiles onboot <br />
<br />
After upgrading, all should be set and done.<br />
<br />
Have fun with your system and say “Good bye” to /bin, /sbin, /lib, /lib64 and<br />
meet them in /usr.<br />
<br />
{{Anchor|15-16}}<br />
<br />
=== Fedora 15 -> Fedora 16 ===<br />
<br />
First install the new fedora 16 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/A82BA4B7.txt<br />
</pre><br />
<br />
Next run {{command|chkconfig --list}} and note the enabled services; you will need to re-enable these with {{command|systemctl enable ''xxxxx''.service}} after you reboot, as the {{package|sysvinit}} settings aren't propagated into {{package|systemd}}. See [http://fedoraproject.org/wiki/Common_F16_bugs#Upgrade_from_previous_releases_resets_the_enablement_status_of_services release notes] for more details.<br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=16 --disableplugin=presto distro-sync<br />
</pre><br />
<br />
{{admon/warning|Bootloader change|After the upgrade, you will have the {{package|grub2}} and {{package|grub-efi}} packages installed and the {{package|grub}} package removed. However, grub will still be installed to the MBR and booting should still work. You can follow the instructions below to switch to grub2 if you choose. If installed, the {{package|firstaidkit-plugin-grub}} package may prevent the upgrade; do simply remove that package if that is the case.}}<br />
<br />
If your system uses a BIOS, or you installed Fedora via BIOS emulation mode on an EFI system (not native EFI mode), you can switch to Fedora 16's supported grub2 bootloader with the following instructions. If your system was installed by native EFI boot, do not switch to grub2, as its EFI support is still unreliable. Fedora 16's supported bootloader for native EFI installations is still grub-legacy, so you should simply continue to use the system without making any special changes to the bootloader configuration.<br />
<br />
To switch to grub2, run the command {{command|su -c '/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg'}}, then proceed as described [[#6._Preparing_for_reboot|above]] with reinstalling the bootloader, but call {{command|grub2-install /dev/XXX}} instead of{{command| grub-install /dev/XXX}}.<br />
<br />
Known you upgrade -specific issues (for common problems, see references above):<br />
* Bug [https://bugzilla.redhat.com/show_bug.cgi?id=743022 743022] - F15->F16 yum update fails with IMSM (BIOS) raid<br />
<br />
<br />
{{Anchor|14-15}}<br />
<br />
=== Fedora 14 -> Fedora 15 ===<br />
<br />
First install the new fedora 15 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/069C8460.txt<br />
</pre><br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=15 --disableplugin=presto distro-sync<br />
</pre><br />
<br />
* Do not run this from within an X terminal. Testing shows that X might hang while updating bitmap font packages.<br />
* There exist .drpms, but they don't match, due to a format change, so better disable the presto plugin by adding the option "--disableplugin=presto" (without quotes) when running yum.<br />
* The F15 <code>screen</code> client is not capable of attaching to F14 <code>screen</code> sessions. Thus, if you want to run the upgrade under <code>screen</code>, you should either upgrade <code>screen</code> itself in a separate operation or make a separate copy of <code>screen</code> to use throughout the process.<br />
* mysql 5.5.20 shipped with F15 uses InnoDB as default storage engine. After upgrading, mysqld could refuse to start-up with error ''Unknown/unsupported storage engine: InnoDB'' if argument ''skip-innodb'' is given on command line or configuration file ''/etc/my.cnf''. Workarounds are removing the line (InnoDB will be run as default engine), or adding ''default-storage-engine'' command options specifying some other storage engine.<br />
<br />
==== VirtualBox guest upgrades ====<br />
The steps above work perfectly for upgrading a Fedora 14 guest to Fedora 15, but you also need to remove the Guest Additions. If you forget, F14 -> F15 upgrades will seem to fail after the first reboot. If that happens, log in to the console with CTRL+ALT+F2 and reinstall the guest additions manually:<br />
<br />
<pre><br />
mount /dev/cdrom /media<br />
# if /dev/cdrom does not exist, try:<br />
# mount /dev/sr0 /media<br />
/bin/sh /media/VBoxLinuxAdditions.run<br />
reboot<br />
</pre><br />
<br />
{{Anchor|13-14}}<br />
<br />
=== Fedora 13 -> Fedora 14 ===<br />
<br />
First install the new fedora 14 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/97A1071F.txt<br />
</pre><br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=14 distro-sync<br />
</pre><br />
<br />
* If using VirtualBox from the Oracle repository, you must remove the VirtualBox-3.1 package before upgrading. After the upgrade is finished, install VirtualBox-3.2.<br />
<br />
If you are running SELinux you may be locked out of your machine and required to boot to single user mode to fix up your machine. [[rhbug:702865|Redhat bug 702865]] describes a fix as:<br />
<ol><br />
<li><code>setenforce 0</code><br />
<li><code>yum remove selinux-policy selinux-policy-targeted</code><br />
<li><code>rm -rf /etc/selinux/targeted</code><br />
</ol><br />
<br />
If, after upgrading you want selinux back:<br />
<ol><br />
<li><code>yum install selinux-policy selinux-policy-targeted</code><br />
<li><code>fixfiles restore</code><br />
<li><code>reboot</code><br />
</ol><br />
<br />
{{Anchor|12-13}}<br />
<br />
=== Fedora 12 -> Fedora 13 ===<br />
<br />
First install the new fedora 13 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.<br />
<br />
<pre><br />
rpm --import https://fedoraproject.org/static/E8E40FDE.txt<br />
</pre><br />
<br />
Upgrade all packages with<br />
<br />
<pre><br />
yum update yum<br />
yum clean all<br />
yum --releasever=13 distro-sync<br />
</pre><br />
<br />
* Testing shows that upgrading within X will cause X to hang when installing <code>bitmap-fonts-compat</code>, but it can be done anyway by making sure that <code>bitmap-fonts-compat</code> is the last package to update ... YMMV.<br />
* Intel video no longer works without Kernel Mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.<br />
* nVidia video no longer works without kernel mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.<br />
* It may be necessary to run "db_recover -h /var/lib/ldap/ ; chown ldap:ldap /var/lib/ldap/*" once in order for slapd to start.<br />
<br />
{{Anchor|11-12}}<br />
<br />
=== Fedora 11 -> Fedora 12 ===<br />
<br />
* All Fedora 12 RPM packages use XZ/LZMA compression, which is only supported by the [https://admin.fedoraproject.org/updates/F11/FEDORA-2009-7986 rpm-4.7.1-1 update] (or later) for Fedora 11. Before upgrading from Fedora 11, run <code>yum update rpm</code>.<br />
* It is not possible to update directly from Fedora 10 or earlier with yum. To upgrade from Fedora 10, first update to Fedora 11, and then upgrade from Fedora 11 to Fedora 12. If you are using a release before Fedora 10, use one of the official upgrade methods or backup your data, perform a fresh installation, and restore from backup.<br />
* Upgrades from Fedora 11 might currently fail with missing dependencies (for example related to {{package|totem-gstreamer}} or {{package|PolicyKit-kde}}). The dependencies are ok, but Fedora 11 {{package|yum}} has problems resolving them ([[rhbug:519172|bug 519172]]).<br />
* If your root filesystem does not mount with 'defaults' options, you will need to add the root filesystem's mount options to grub.conf with the kernel flag <code>rootflags</code> - initramfs does not pick up the options the way initrd used to. e.g. if you mount your root with the flags <code>data=journal,relatime</code> then you would add to the end of the 'kernel' line in grub.conf: <code>rootflags=data=journal,relatime</code> . After updating to dracut-004-4.fc12 or later, this kernel flag can be removed.<br />
<br />
{{Anchor|10-11}}<br />
<br />
=== Fedora 10 -> Fedora 11 ===<br />
<br />
* It is only possible to upgrade to Fedora 11 from an updated Fedora 10. Older systems must be upgraded to Fedora 10 first. The RPM format has been changed for Fedora 11, so the older <code>rpmlib</code> must be updated first. Otherwise the process will fail with <code>rpmlib(FileDigests)</code> dependency problems. Support for the new format has been backported to Fedora 10 in an update.<br />
<pre><br />
yum update rpm<br />
</pre><br />
* New <code>initrd</code> built when installing a new kernel while running Fedora 10 might fail. To solve that boot with an old kernel (to get the new userspace) and (re)install the new kernel.<br />
* Systems with PAE support (indicated by <code>pae</code> in <code>/proc/cpuinfo</code>) should use <code>kernel-PAE.i686</code>. The new kernel must be changed/installed manually: Set <code>DEFAULTKERNEL=kernel-PAE</code> in <code>/etc/sysconfig/kernel</code> and <code>yum install kernel-PAE</code>. Refer to [http://www.codemonkey.org.uk/?p=142 Dave Jones' blog post] for details.<br />
* The yum update step should NOT be run inside a gnome desktop session/gnome-terminal. [[rhbug:494046|494046]] could result in a unusable install when gnome-terminal segfaults during the upgrade. Update should be run in a vty, runlevel 3, or a screen session.<br />
* fedora-release-11-1.noarch changes the yum mirrorlist URL so that it uses a "metalink", but the version of yum currently in F10 doesn't understand this syntax, leading to yum downloads failing with this error message:<br />
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.<br />
Eg. </metalink>/<br />
This is [[rhbug:498720|498720]]. Workaround is to manually edit the URL in /etc/yum.repos.d/fedora.repo as described at https://www.redhat.com/archives/fedora-list/2009-June/msg00783.html<br />
* Some packages in Fedora 10 are regarded as newer than those supplied by Fedora 11 and its updates repository. These include ntpd, ntpdate ([[rhbug:506040|506040]], [[rhbug:504980|504980]]), unique, unique-devel, eclipse-changelog, eclipse-svnkit and svnkit. You may wish to remove these before performing the upgrade, then reinstall them afterwards. Doing so may require <code>--nodeps</code>.<br />
* Some i386 packages in Fedora 10 are replaced with i586, i686 or x86_64 packages in Fedora 11. These include gpm.i386, glibc-2.9-3.i386. You may wish to remove these before performing the upgrade, then reinstall them afterwards. Doing so may require <code>--nodeps</code>.<br />
* mplayer-1.0-0.104.20090204svn.fc10 from the RPM Fusion repository has a dependency on libfaad.so.0 that the depsolve doesn't find, but rpm_check_debug does. You may wish to remove mplayer before performing the upgrade, then reinstall them afterwards. Doing so may require <code>--nodeps</code>.<br />
<br />
{{Anchor|9-10}}<br />
<br />
=== Fedora 9 -> Fedora 10 ===<br />
<br />
* Check the [http://docs.fedoraproject.org/install-guide/f10/en_US/ Fedora 10 Installation Guide] and [http://docs.fedoraproject.org/release-notes/f10/en_US/ Fedora 10 Release Notes]<br />
* <code>fedora-release</code> packages can be found at <code>rpm -Uvh ftp://dl.fedoraproject.org/pub/fedora/linux/releases/10/Fedora/i386/os/Packages/fedora-release-*.noarch.rpm</code><br />
* GDM starts on tty1 by default, not tty7.<br />
* anaconda by default now refers to encrypted devices by UUID, not by device name, to better handle device name changes. An encrypted device using partition <code>/dev/sda1</code> with UUID <code>12345678-1234-1234-1234-123456789012</code> would now be called <code>/dev/mapper/luks-12345678-1234-1234-1234-123456789012</code> instead of <code>/dev/mapper/luks-sda1</code>. You may wish to make the same changes on your system on upgrade; if you do, make sure to run <code>mkinitrd</code> afterwards.<br />
* If you use non-root encrypted devices, you will need to re-run <code>mkinitrd</code> for any older kernels that you want to still boot on the system.<br />
* It's been reported that there are problems with Pidgin i.e.:<br />
** <code>pidgin-2.5.2-2.fc9.i386 from installed has depsolving problems - Error: Missing Dependency: libedataserver-1.2.so.9 is needed by package pidgin-2.5.2-2.fc9.i386 (installed)</code><br />
** the fix was to remove Pidgin<br />
<br />
{{Anchor|8-9}}<br />
=== Fedora 8 -> Fedora 9 ===<br />
<br />
* Check the [http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Installer.html#Upgrade-Related-Issues Installer section in Release Notes])<br />
* After "the incident" you should use updated fedora-release packages from <code>rpm -Uvh ftp://dl.fedoraproject.org/pub/fedora/linux/updates/9/i386.newkey/fedora-release-*.noarch.rpm</code><br />
* If you are running as a <code>xen</code> Host (Dom0) you should not upgrade to Fedora 9. [http://www.redhat.com/archives/fedora-xen/2008-March/msg00013.html] <br />
* Upgrading the thunderbird package will [[rhbug:446351|fail]] . The current workaround is <code>yum remove thunderbird; yum install thunderbird></code>.<br />
* If you are upgrading to Fedora 9 and use <code>emacs</code>, you must upgrade to the latest version of <code>emacs</code> for your prior release to ensure a clean upgrade. Fedora 8 users must have <code>emacs-22.1-10.fc8</code> or later, while Fedora 7 users must have <code>emacs-22.1-7.fc7</code>. Bug report [[rhbug:239745|here]].<br />
* Due to the switch from sysvinit to [http://fedoraproject.org/wiki/Features/Upstart Upstart] , it is recommended that users who do an upgrade on a live filesystem to Fedora 9 reboot soon afterwards. If you do not reboot, you may want to take careful note of any '/etc/inittab.rpmsave' or '/etc/inittab.rpmnew' files. When rebooting after an upgrade then be aware that sysvinit that was used to start the system can't be used to shut it down.<br />
* You may find that after upgrading, you can no longer log in to GNOME. If this is the case, use ctrl-alt-F1 to access command prompt, then check the tail of .xsession-errors. If you see a comment like "(named color or font does not exist)", then you may be able to fix this using http://matthew.peach.net.nz/2008/05/18/how-to-fix-badname-named-color-or-font-does-not-exist-error/.<br />
<br />
{{Anchor|7-8}}<br />
=== Fedora 7 -> Fedora 8 ===<br />
<br />
* New pulseaudio and flash support packages must be installed manually:<br />
<br />
<pre><br />
yum groupinstall sound-and-video gnome-desktop (if you are using Gnome)<br />
yum groupinstall sound-and-video kde-desktop (if you are using KDE)<br />
yum install libflashsupport paman padevchooser<br />
</pre><br />
<br />
* The Fedora 7 avahi packagage fails to uninstall; remove it manually with<br />
<br />
<pre><br />
rpm -e --noscripts avahi-0.6.17-1.fc7<br />
</pre><br />
<br />
* On 64 bit machines (x86_64) you may have to remove some 32 bit libraries. For example dbus:<br />
<br />
<pre><br />
yum erase dbus.i386<br />
</pre><br />
<br />
* You may find it easier to use the yum shell to stack these commands in a single transaction:<br />
<br />
<pre><br />
yum shell<br />
> erase dbus.i386<br />
> update<br />
> run<br />
</pre><br />
<br />
* A lot of KDE packages are no longer multilib in F8. If you are on x86_64, you will need to erase the i386 versions of these packages by hand, like so:<br />
<br />
<pre><br />
yum erase kde{accessibility{,-devel},base,edu,graphics,multimedia{,-extras},network,sdk,utils{,-devel},webdev}.i386<br />
</pre><br />
<br />
* Various other packages including Beryl are no longer in F8 and not obsoleted:<br />
<br />
<pre><br />
yum erase beryl\*<br />
</pre><br />
<br />
{{Anchor|6-7}}<br />
=== Fedora Core 6 -> Fedora 7 ===<br />
<br />
* Fedora 7 replaces the old IDE subsystem with libata. Drive device names which previously started /dev/hd.. will become /dev/sd.. after the upgrade. /dev/hda1 will usually become /dev/sda1, although there may not be a direct relationship between the old and new device names (for example hdd does not necessarily become sdd). Before you reboot be sure to change all references to /dev/hd.. in your config, especially /etc/fstab - where it however may be simpler to refer to filesystems by label (check out the programs blkid, tune2fs, and mlabel). LVM Volume names are not affected. In /boot/grub/device.map change /dev/hd.. to /dev/sd.. before running grub-install - and don't change (hd0). Changing /boot/grub/grub.conf may also be required.<br />
<br />
* The libata layer represents all hard disks as SCSI disks, which are limited to 15 partitions in the kernel. IDE hard disks with more than 15 partitions are not supported in Fedora 7.<br />
<br />
* On a system which has been upgraded from releases prior to FC6 you may need to remove up2date and rhnlib <code>rpm -e rhnlib up2date</code><br />
<br />
* If you see the message <code>package gpm-1.20.1-84.fc6 (which is newer than gpm-1.20.1-83.fc7) is already installed</code> when performing a <code>yum update</code> uninstall and reinstall the gpm package.<br />
<br />
* If you had installed Suns jre it might be removed during upgrade. Be aware that <code>jre-6u1</code>/<code>jre-1.6.0_01-fcs</code> requires <code>compat-libstdc++-33</code>.<br />
<br />
* If you get <code>Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python</code> and/or <code>Error: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python</code> during your <code>yum upgrade</code> ensure you have done a <code>yum clean all</code> and check that both the <code>base</code> and <code>updates</code> repositories are available from your mirror. You will need the <code>updates</code> repo for the upgrade to succeed.<br />
<br />
* Since Fedora Core 6 uses python 2.4 and Fedora 7 uses python 2.5, do not try and run <code>yum upgrade yum\* rpm\*</code> before upgrading everything else - this succeeds but leaves yum in an unusable state.<br />
<br />
=== Fedora Core 5 -> Fedora Core 6 ===<br />
<br />
* After upgrading, you cannot use the DVD ISO loopback mounted as a repository directly (e.g. no <code>baseurl=file:///mnt/fc6/</code>) because the repodata files contain URLs of type <code>media://</code> which yum can't handle. You can use the loopback-mounted DVD for the initial upgrade from FC5 -> FC6, just not thereafter. After removing the <code>baseurl=file:///</code> option from your <code>fedora-core.repo</code> file, remember to <code>yum clean all</code>.<br />
<br />
=== Fedora Core 4 -> Fedora Core 5 ===<br />
<br />
* Before upgrading update your kernel first.<br />
<br />
* Make sure you have the latest kernel ABOVE 2.6.14 and uninstall all kernel versions before it, otherwise initscripts and a few other packages will conflict and prevent the ugprade. Use something like the command below<br />
<br />
* Install <code>fedora-release</code> in the Fedora Core 5 version. Check our [http://fedora.redhat.com/Download/mirrors.html mirror sites] for a faster download.<br />
<br />
* Update your system<br />
<br />
* After upgrading, selinux permissions may be incorrect, causing interesting failures such as metacity not starting. As suggested below, to fix this, run <code>touch /.autorelabel</code> and reboot<br />
<br />
=== Fedora Core 3 -> Fedora Core 4 ===<br />
<br />
* make sure you're on the latest version of yum for FC3:<br />
<code> yum update yum </code><br />
* Download fedora-release for FC4:<br />
* wget http://yourmirrorhere/pub/fedora/linux/core/4/$yourarch/os/Fedora/RPMS/fedora-release-4-2.noarch.rpm<br />
* <code>rpm -Uvh /path/to/fedora-release-4-2.noarch.rpm</code><br />
* yum update ( This will start the upgradation process to FC4)<br />
* Once you have updated, run: <code>yum groupinstall "GNOME Desktop Environment"</code> (change GNOME to KDE if appropriate). That'll get you some new packages that were added in FC4 like Evince and NetworkManager.<br />
* Some new groups were added - <code> yum grouplist </code> - check out Eclipse and Java Development in particular.<br />
<br />
Problems:<br />
<br />
* Postgres database in FC4 has a newer incompatible format from the previous versions. Manual dump and restoration is required if you using this database. Look at the postgres documentation for more details on this.<br />
<br />
* kernel requires kernel-utils (or vice-versa) run:<br />
<pre><br />
yum update kernel<br />
reboot<br />
yum remove kernel-2.6.11\*FC3\*<br />
yum upgrade<br />
reboot<br />
</pre><br />
<br />
* Takes forever and a day and hangs at:<br />
<code> Reading repository metadata in from local files </code><br />
This means you have too much crap in your rpmdb and it's taking a while to go through it. Check out how many kernels you have installed: rpm -q kernel kernel-smp and remove the old ones you may also try running: rpm --rebuilddb and see if it helps any. I've found that removing old kernels and rebuilding the rpmdb helped this problem.<br />
<br />
* x86_64 upgrade requires removal of certain i386 packages before update<br />
<pre><br />
yum remove perl.i386<br />
TODO: Add list of bonobo i386 packages to remove here<br />
</pre><br />
* Error: Missing Dependency: libpython2.3.so.1.0 is needed by package koffice<br />
koffice was removed from Fedora Core and not moved to extras - so there's no way to complete an upgrade to FC4<br />
without removing it. run:<br />
<pre><br />
yum remove koffice<br />
</pre><br />
then your update should complete.<br />
<br />
* x86_64 systems seems to hang during "Running Transaction Test"<br />
<br />
Seems related to bug [[rhbug:155730|155730]] -- Maybe a update to the "rpm-4.3.3-3.0.fc3" (currently in updates-testing) might solve this. Ugly workaround (to be done as root):<br />
<pre><br />
: > /var/log/lastlog<br />
</pre><br />
<br />
* GPG check fails with this message :<br />
<pre><br />
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID db42a60e<br />
public key not available for <some_package><br />
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora<br />
<br />
The GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora (0x4F2A6FD2)<br />
is already installed but is not the correct key for this package.<br />
Check that this is the correct key for the "Fedora Core 4 - i386 - Base" repository.<br />
</pre><br />
Edit /etc/yum.repos.d/fedora.repo and replace the line<br />
<pre><br />
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora<br />
</pre><br />
with:<br />
<pre><br />
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY<br />
</pre><br />
<br />
* SELinux gets messed up. I had to redownload the selinux-policy-targeted RPM from my mirror, do a forced uninstall of the old package, clean out the .rpmnew and .rpmsave files then install the new policy. Then I had to run "/sbin/fixfiles relabel" and wait. If I didn't do that, I found I couldn't log in.<br />
* If SELinux does give you problems, it can be disabled on bootup by pressing "a" on the grub bootup menu, then adding "enforcing=off" to the arguments list.<br />
<br />
* RPM complains about missing diskspace, but there is a lot free. If you are really sure your diskspace is enough, set<br />
<pre><br />
diskspacecheck=0<br />
</code> in <code>/etc/yum.conf</code>.<br />
The RPM transaction will need a lot of diskspace temporarily (much more than one might think), so be careful.<br />
Don't forget to remove that later after the upgrade.<br />
<br />
* Yum complains about files conflicting in the GCC package. This system was upgraded from Fedora Core 1. Remove the gcc32 package:<br />
<pre><br />
sudo rpm -e gcc32<br />
</pre><br />
<br />
* Some of your modules don't load after the upgrade. When you investigate modprobe doesn't work as expected. Run depmod:<br />
<pre><br />
sudo depmod -ae -F /boot/System.map-[your <code>uname -a</code> kernel version here] <br />
</pre><br />
<br />
* Yum has been reported to be hanging after upgrading. Updating the pysqlite package might fix it.<br />
<br />
=== Fedora Core 2 -> Fedora Core 3 ===<br />
<br />
Go here for most of this info:<br />
https://web.archive.org/web/20080430083623/http://linux.duke.edu/~skvidal/misc/fc2-fc3-update-with-yum.txt<br />
<br />
=== Fedora Core 1 -> Fedora Core 2 ===<br />
<br />
Just Upgrade using anaconda - save yourself a world of pain. But if you really want to try, there's these hints by Seth Vidal: https://web.archive.org/web/20080720005856/http://linux.duke.edu/~skvidal/misc/fc1-fc2-yum-hints.txt<br />
<br />
[[Category:FAQ]][[Category:How to]][[Category:Documentation]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Talk:Changes//LibinputForXorg&diff=398491Talk:Changes//LibinputForXorg2014-12-15T17:07:26Z<p>Kkofler: Also note my objections here.</p>
<hr />
<div>As I wrote on the mailing list:<br />
<br />
''> KDE: limits itself to standard X11 mouse config interfaces, no changes needed.''<br />
<br />
Not true. We ship kcm_touchpad on the KDE spin, which definitely does depend<br />
on synaptics interfaces (search for "synaptics" in:<br />
https://projects.kde.org/projects/playground/utils/kcm-touchpad/repository/revisions/master/entry/src/backends/x11/xlibbackend.cpp ).<br />
Anything that does not use the synaptics driver is not considered a<br />
touchpad. And kcm_touchpad is also in the process of becoming a core part of<br />
upstream Plasma. (It is currently in the git.kde.org playground.)<br />
<br />
Therefore, porting kcm_touchpad (the rewritten 1.x series we currently ship,<br />
not the old, obsolete, 0.3.x version, please make sure you look at the<br />
correct version) is an essential requirement before we can move away from<br />
the synaptics driver.<br />
<br />
<br />
An additional objection I have to this change proposal is that libinput<br />
(deliberately) only implements a small subset of the configurability of the<br />
old drivers, and thus, if we are going to remove the old drivers entirely,<br />
we are taking away flexibility from our users.<br />
--[[User:Kkofler|Kkofler]] ([[User talk:Kkofler|talk]]) 17:07, 15 December 2014 (UTC)</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Upgrading_Fedora_using_package_manager&diff=398391Upgrading Fedora using package manager2014-12-14T23:51:26Z<p>Kkofler: /* Fedora 20 -> Fedora 21 */ Fix F21 GPG key file name.</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
This page contains information explaining how to upgrade Fedora using {{command|yum}}.<br />
<br />
== Upgrading Fedora using yum directly ==<br />
<br />
{{admon/warning| Upgrading using the yum method described here is not recommended for new users. Use FedUp instead |<br />
<br />
For upgrades, the recommended upgrade method is the [[FedUp]] tool. [[FedUp#How_Can_I_Upgrade_My_System_with_FedUp?|This section]] has instructions on using FedUp to upgrade.<br />
<br />
Although upgrades with yum do work, they are not explicitly tested as part of the release process by the [[QA|Fedora QA]] and are not documented in the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersion}}/html/Installation_Guide/index.html Fedora installation guide]. If you are not prepared to resolve issues on your own if things break, you should probably use the recommended installation methods instead.}}<br />
<br />
When upgrading with yum you don't get any help from FedUp or Anaconda, but with a typical system it might be able to upgrade systems remotely over ssh and with limited downtime. (You will still need to reboot to get the new kernel and system libraries/services running). <br />
<br />
A live upgrade with yum usually works well with a typical installation and when following the advice below.<br />
<br />
== Participate ==<br />
<br />
If you are upgrading using Yum and it shows any general dependency issues, please file them in http://bugzilla.redhat.com. But please read this page, all references pages and search the mailing list archives before filing bugs. And of course, please help keep this page updated.<br />
<br />
If you want to help make live upgrades work smoothly, join the [[SIGs/LiveUpgrade | Live Upgrade Special Interest Group]].<br />
<br />
== Instructions to upgrade using yum ==<br />
<br />
=== 1. Backup your system ===<br />
<br />
Backup any personal data to an external hard drive or to another machine. If there is some unrecoverable error that requires a fresh install, you don't want to lose any data.<br />
<br />
=== 2. Read about common problems ===<br />
<br />
Further down in this page there is a list of common problems specific to yum upgrades for specific versions. Some of them require attention before the upgrade.<br />
<br />
General advice on upgrading Fedora can be found on the [[Upgrading]] page. You should also read the [http://docs.fedoraproject.org/install-guide/ Installation Guide] and [http://docs.fedoraproject.org/release-notes/ Release Notes] for the version you plan to upgrade to - they contain important information regarding upgrading issues. Finally, check the list of [[Common bugs]].<br />
<br />
=== 3. Clean Stuff ===<br />
<br />
Review and remove all .rpmsave and .rpmnew files before and after upgrading. (And if you have selinux enabled then remember to check security context if you move config files around.)<br />
<br />
{{admon/tip|Find unused config files|Merge and resolve the changes found by the following script: <code>yum install rpmconf; rpmconf -a</code><br />
Now find and remove old config which nobody owns: <code>find /etc /var -name '*?.rpm?*'</code>}}<br />
<br />
Now is a good time to remove packages you don't use - especially non-standard packages.<br />
<br />
{{admon/tip|Find and review "unused" packages| You can find packages not required by other packages with the tool <code>package-cleanup</code> from the <code>yum-utils</code> package: <code>yum install yum-utils; package-cleanup --leaves</code>. These packages could be candidates for removal, but check to see whether you use them directly or if they are used by applications not backed by rpm packages. Remove them with <code>yum remove package-name-and-version</code>.<br/><br />
Another useful tool for cleaning up unused packages is <code>rpmreaper</code>. It's an ncurses application that lets you view rpm dependency graph and mark packages for deletion. Marking one package can make other packages leaf, which you can see immediately, so you don't have to run the tool several times to get rid of whole sub-tree of unused packages. Install with: <code>yum install rpmreaper</code>.<br />
}}<br />
<br />
{{admon/tip|Find and review "lost" packages| You can find orphaned packages (ie packages not in the repositories anymore) with: <code>package-cleanup --orphans</code>. This will also show packages which have been partially uninstalled but where the "%postun" script failed.}}<br />
<br />
=== 4. Do the upgrade ===<br />
<br />
If you have 3rd party repositories configured, you may need to adjust them for the new Fedora version. If you switch from one Fedora release to another there is often nothing that needs to be done. If you switch to Rawhide from a standard Fedora release (or vice versa) then most of the time you will need to install the Rawhide release RPMs from the 3rd party repository as well (or the standard ones, if switching back).<br />
<br />
Note that the upgrade is likely to fail if there are outdated dependencies from packages not backed by a yum repository or backed by a repository which isn't ready for the new version.<br />
<br />
It is a good idea to do the upgrade outside the graphical environment. Log out of your graphical desktop and then<br />
<br />
==== fedora-upgrade ====<br />
<br />
A small script named fedora-upgrade is available which aims to automate the process outlined below. To run it, do the following<br />
<br />
<pre>$ sudo yum install fedora-upgrade <br />
$ sudo fedora-upgrade<br />
</pre><br />
<br />
<br />
Alternatively, follow the manual steps:<br />
<br />
==== Go to a text console ====<br />
<br />
<pre><br />
ctrl + alt + F2<br />
</pre><br />
<br />
(or)<br />
<br />
log in as root, and go into runlevel 3<br />
<br />
<pre><br />
init 3<br />
</pre><br />
<br />
==== Update yum to latest version available in your Fedora version ====<br />
<br />
<pre><br />
# yum update yum<br />
</pre><br />
<br />
==== Install the new fedora gpg key for the version you are updating to ====<br />
<br />
Keys you may find and verify at<br />
<br />
https://fedoraproject.org/keys<br />
<br />
or see a version specific update instructions at the bottom.<br />
<br />
==== Clean the cache ====<br />
<br />
Then remove all traces of the version you are leaving from the yum cache in <code>/var/cache/yum</code>.<br />
<br />
<pre><br />
# yum clean all<br />
</pre><br />
<br />
==== Upgrade all packages ====<br />
<br />
{{admon/warning|Once a live upgrade is started, do not stop the upgrade by rebooting, killing the process, or by any other method until it is complete. Interrupting an upgrade will cause the affected system to be in a mixed state -- partially the old release and partially the new release. In this state, the system will not be reliable and will not operate as expected. You can try running yum distro-sync and package-cleanup --problems to try and fix the problems. }}<br />
<br />
<pre><br />
# yum --releasever=<release_number_you_want_to_sync_to> distro-sync<br />
</pre><br />
<br />
{{admon/warning|If you experience any dependency problems, you have to solve them manually. Most often it is enough to remove several problematic package(s). Be very careful when doing so however.<br />
}}<br />
<br />
'''Note:''' While it is recommended to upgrade to intermediate releases if upgrading from an older release (for example upgrading from Fedora 19 to 20, then 20 to 21), depending on what version you are upgrading from, this step may fail with an error about GPG keys being in the wrong format. To overcome this, you can add the "--nogpgcheck" switch to the above yum distro-sync command.<br />
<br />
=== 5. Make sure Fedora is upgraded ===<br />
<br />
Distro-sync will usually take care of upgrades for the third party repositories you have enabled as well. Confirm with <pre> yum repolist </pre> after the upgrade process is over. <code>yum</code> might complain about conflicts or requirements. That is probably because you have used non-standard repositories or installed non-standard packages manually. Try to guess which packages cause the problem (or at least is a part of the dependency chain) - uninstall them and try again. Remember to install the packages again if they are essential. <br />
<br />
Ensure that all (new) essential packages from the new version are installed with<br />
<br />
<pre><br />
# yum groupupdate 'Minimal Install'<br />
</pre><br />
<br />
You might want to update other groups too, see<br />
<br />
<pre><br />
# yum grouplist<br />
</pre><br />
<br />
For example<br />
<br />
<pre><br />
# yum groupupdate "GNOME Desktop" \<br />
"Development Tools" "Sound and Video" \<br />
"Games and Entertainment" "Administration Tools" \<br />
"Office/Productivity" "System Tools"<br />
</pre><br />
<br />
=== 6. Preparing for reboot ===<br />
<br />
{{Anchor|bootloader}}<br />
<br />
Before booting you should usually install the bootloader from your new grub by running<br />
<pre><br />
/usr/sbin/grub2-install BOOTDEVICE<br />
</pre><br />
- where BOOTDEVICE is usually <code>/dev/sda</code> (If you get an error '/dev/sda does not have any corresponding BIOS drive' from that, then try <tt>/usr/sbin/grub2-install --recheck /dev/sda</tt>).<br />
<br />
It might also be necessary to update the grub config file:<br />
<pre><br />
cp --backup=numbered -a /boot/grub2/grub.cfg{,.bak} # create backup copy<br />
/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg # update config file<br />
</pre><br />
<br />
Also, the order of init scripts could have changed from the previous version. A command to reset the order is:<br />
<pre><br />
cd /etc/rc.d/init.d; for f in *; do [ -x $f ] && /sbin/chkconfig $f resetpriorities; done<br />
</pre><br />
<br />
Again, run <code>package-cleanup --orphans</code> to find packages that haven't been upgraded.<br />
<br />
== Version specific notes ==<br />
<br />
=== From pre-release ===<br />
<br />
If you are upgrading to a final release from an alpha, beta, preview, or other [[Releases/Rawhide|Rawhide]] release, please see [[Upgrading from pre-release to final]].<br />
<br />
{{Anchor|Rawhide}}<br />
=== To rawhide ===<br />
<br />
See the [[Releases/Rawhide|Rawhide]] release page for more information on Rawhide. <br />
<br />
<pre><br />
# yum install fedora-release-rawhide yum-utils<br />
# yum-config-manager --disable fedora updates updates-testing<br />
# yum-config-manager --enable rawhide<br />
# yum update yum<br />
# yum --releasever=rawhide distro-sync --nogpgcheck<br />
</pre><br />
<br />
If you are upgrading from {{FedoraVersion|21}} or later, replace the first command with {{command|yum install fedora-release-rawhide yum-utils}}.<br />
<br />
<br />
{{Anchor|20-21}}<br />
<br />
=== Fedora 20 -> Fedora 21 ===<br />
<br />
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-$(uname -i)<br />
# yum update yum<br />
# yum clean all<br />
# yum --releasever=21 distro-sync<br />
<br />
Fedora 21 split into different products. Execute '''one''' of those commands:<br />
<br />
# yum install system-release-workstation<br />
# yum install system-release-cloud<br />
# yum install system-release-server<br />
<br />
or this one if you want to have non-productized Fedora<br />
<br />
# yum install system-release-nonproduct<br />
<br />
If you change your mind, you can easily switch between products. <br />
<br />
# yum swap system-release-cloud system-release-workstation<br />
<br />
Swapping to workstation sometimes may require you to use {{command|yum shell}} as it may require multiple packages to be swapped.<br />
<br />
Many people report (e.g. bugs 1035326, 1044184, 1002331) that after upgrade some files have incorect SELinux context. It is recommend to run:<br />
<br />
# restorecon -R /<br />
<br />
{{Anchor|19-20}}<br />
<br />
=== Fedora 19 -> Fedora 20 ===<br />
<br />
Install the new Fedora 20 gpg key and upgrade: <br />
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-$(uname -i)<br />
# yum update yum<br />
# yum clean all<br />
# yum --releasever=20 --setopt=deltarpm=0 distro-sync<br />
<br />
=== Upgrading from legacy end of life (EOL) Fedoras ===<br />
{{admon/note|Yum upgrading from older versions|Upgrading from older versions of Fedora is archived here: [[Upgrading from EOL Fedora using yum]]}}<br />
<br />
[[Category:FAQ]]<br />
[[Category:How to]]<br />
[[Category:Documentation]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Common_F21_bugs&diff=398114Common F21 bugs2014-12-11T02:18:07Z<p>Kkofler: /* KDE issues */ kde-apper: Status update.</p>
<hr />
<div><!--<br />
This header (down to the first "Issues" section below) is generated by '''SUBSTITUTING''' [[Template:Common_bugs_header_stable_release]] at the time the release goes stable: <nowiki>{{subst:Common_bugs_header_stable_release}}</nowiki>. This should replace the entire pre-release header text. Please do this rather than copy/pasting. If you are making improvements to the header text, please make them also in the [[Template:Common_bugs_header_stable_release]], [[Template:Common_bugs_header_prerelease]] and [[Template:Common_bugs_header_shared]] templates as appropriate, so future pages will contain the same improvements.<br />
--><br />
{{autolang|base=yes}}<br />
<br />
This page documents common bugs in Fedora 21 and, if available, fixes or workarounds for these problems. If you find your problem in this page, ''please do not file a bug for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included.<br />
<br />
== Release Notes ==<br />
Read the [[F21_release_announcement|Fedora 21 release announcement]] and the [http://docs.fedoraproject.org/en-US/Fedora/21/html/Release_Notes/ Fedora 21 release notes] for specific information about changes in Fedora 21 and other general information.<br />
<br />
{{Common_bugs_header_shared}}<br />
<br />
== Installation issues ==<br />
{{Common bugs issue|bootloader-target-disk|Cannot place bootloader target partition (e.g. {{filename|/boot/efi}}) on a disk other than the first in custom partitioning|1168118}}<br />
<br />
You may encounter this bug when doing custom partitioning with more than one disk, and installing on a system whose firmware requires a partition as the location for the bootloader stage1 - e.g. {{filename|/boot/efi}} for UEFI systems, {{filename|/boot/uboot}} for some ARM systems, or a PReP boot partition for PowerPC systems.<br />
<br />
If you attempt to create the partition on a disk other than the first (which will be the disk shown furthest to the left on the disk selection screen), the installer may complain that a valid bootloader partition has not been created.<br />
<br />
A simple way to work around this is to place the boot partition on the first disk, if this is not inconvenient or impossible for your desired layout.<br />
<br />
If you do want or need the boot partition to be on a later disk, you can work around the error. To do this, configure the desired layout, and complete custom partitioning despite the error message (by clicking ''Done'' twice). Go back into the ''Installation Destination'' screen, and click ''Full disk summary and bootloader...''. Select the disk on which you placed the boot partition, and click ''Set as Boot Device''. Click ''Close'', then click ''Done'', and click ''Done'' again on the custom partitioning screen without changing anything. This should clear the error condition and cause the installer to be happy with the boot partition being on the chosen disk.<br />
<br />
Note that selecting the desired 'boot disk' before entering custom partitioning and creating your layout will not work (though it ought to - the fact that it does not is a related bug). You must use this slightly more unusual workaround instead. We do apologize for the inconvenience.<br />
<br />
An [[Anaconda/Updates|installer updates image]] which fixes this bug is also available at https://adamwill.fedorapeople.org/updates/updates-1168118.img .<br />
<br />
{{Common bugs issue|anaconda-initramfs-regeneration|All initramfs files in shared {{filename|/boot}} re-generated during install|1074358}}<br />
<br />
If you use a {{filename|/boot}} partition shared with another installation of Fedora or any other Linux distribution, the Fedora 21 installation process will likely attempt to re-generate all the initramfs files present on the partition. In some cases, the re-generated initramfs files may not work correctly.<br />
<br />
Due to the issue we would strongly advise against the use of shared {{filename|/boot}} partitions with Fedora 21. If you do wish to use one, we would recommend you back up all its contents before installing Fedora 21, so that you can recover from any issues caused by the installation process.<br />
<br />
{{Common bugs issue|anaconda-part-multi|Various issues caused by multiple trips through ''Installation Destination'' (partitions re-ordered on ''Reclaim Space'' screen, crash during install)|1158975|1166598}}<br />
<br />
Some circumstances have been discovered in Fedora 21 testing where multiple trips through the ''Installation Destination'' installer spoke can cause problems. One known case involves various scenarios where you select different sets of disks as install targets on multiple trips, and visit the ''Reclaim space'' screen each time. Sometimes, when doing this, partitions will be displayed in a different order on the ''Reclaim space'' screen. In some particular circumstances, the attributes of different partitions - their numbers and sizes - may be confused. In this case, we would recommend rebooting and restarting the installation process to avoid any possibility of inadvertently deleting or resizing the wrong partition.<br />
<br />
[[rhbug:1158975|Bug #1158975]] reports two or three cases where multiple trips through ''Installation Destination'' and ''Reclaim space'' resulted in the installation process crashing during the partitioning phase.<br />
<br />
In general we would recommend you try to avoid too many trips through the ''Installation Destination'' spoke. If you do run into either problem, retrying the installation without multiple trips through the spoke should result in a successful installation.<br />
<br />
The installer development team is investigating various possible approaches to reducing the likelihood of the installer being confused by complex cases such as this for future releases.<br />
<br />
{{Common bugs issue|custom-escape-done|Cannot leave custom partitioning screen by clicking ''Done''|1167014}}<br />
<br />
In some unusual situations, you may find that you seem to be unable to leave the installer's custom partitioning screen by clicking the ''Done'' button. If you find yourself in this situation, clicking the ''Update settings'' button on the right hand side of the screen should resolve the issue, allowing you to leave the next time you click ''Done''.<br />
<br />
This bug happens when the ''Done'' button does not refresh the screen's state in the same way as the ''Update settings'' button does (which it is intended to do), and then the installer refuses to leave the screen because the state is not consistent.<br />
<br />
{{Common bugs issue|netinst-universal|Network install image offers all package groups|1134524}}<br />
<br />
This is no longer considered a bug, exactly, but remains documented here for clarity. Initial Fedora 21 plans envisaged Server and Workstation releases each having their own network install images which, by default, would offer only the package groups relevant to that Product. However, it became clear that this design was difficult to implement and not really particularly desired by anyone.<br />
<br />
For Fedora 21 Final, there will be a single designated network install image, built from the [[Server]] tree, which defaults to the Fedora Server package set but allows installation of all package groups. In practical terms it is little different from the network install image shipped with Fedora 20 and earlier except that it defaults to the Server package group rather than the GNOME desktop, and has Server visual branding.<br />
Despite this branding, in practice it is a universal network install image allowing deployment of all Fedora package sets. It can be used for doing network installs of the [[Workstation]] product in cases where this is preferable to installing from the live image (e.g. mass deployments).<br />
<br />
{{Common bugs issue|i686-server-branding|32-bit Server DVD and network install images use generic installer artwork|1170582}}<br />
<br />
The 32-bit Server DVD and network install images use the generic installer artwork (down the side or across the top of the various screens) which simply uses the Fedora logo, rather than the Server product logo seen on the 64-bit versions of the same media. This is an entirely cosmetic issue, and the images are clearly identified as Server in various text labels.<br />
<br />
== Upgrade issues ==<br />
{{Common bugs issue|fedup-repo-keys|Downloading failed: Didn't install any keys|1066044}}<br />
<br />
If you have enabled any third party repositories that are not included with the default installation of Fedora, you may run into this issue. If you did not import the GPG key for a particular repository after you installed it, fedup will fail because it does not have the necessary keys imported.<br />
<br />
A quick and easy way to fix this is to just reinstall the repository package. You can use the command {{command|su -c 'yum reinstall packagename'}} to reinstall the package. When it prompts you to import the key, press y, and afterwards, try running the fedup tool again.<br />
<br />
{{Common bugs issue|fedup-product-firewall|Firewall configuration overwritten on upgrade to Server or Workstation|1172862}}<br />
<br />
If you pass {{command|--product server}} or {{command|--product workstation}} to {{command|fedup}} when upgrading, the {{package|firewalld-config-server}} or {{package|firewalld-config-workstation}} package will be installed. These contain the default firewall configurations for those Products. Unfortunately, these default configurations will replace - rather than merging with - your existing configuration, including any changes you have made to the defaults.<br />
<br />
The Cloud product and "nonproduct" use the {{package|firewalld-config-standard}} package, which specifies no actual ports or services, and so existing configurations aren't replaced when fedup is run with {{command|--product nonproduct}} or {{command|--product cloud}}.<br />
<br />
If you do want your upgraded system to be Fedora Workstation or Fedora Server, but you wish to maintain your firewall configuration modifications, you should note your existing configuration before the upgrade, and re-apply it with {{command|firewall-cmd}} or {{command|firewall-config}} after the upgrade process. We apologize for the inconvenience, and if possible we will release an update to resolve this issue for future upgrades.<br />
<br />
{{Common bugs issue|fedup-freeipa|FreeIPA configuration upgrade required after fedup}}<br />
<br />
If you upgrade a system running as a FreeIPA server to Fedora 21 using fedup, FreeIPA will not be able to entirely complete its configuration updates during the upgrade process. As explained in [http://www.freeipa.org/page/Releases/4.1.1 the FreeIPA release notes], you must run {{command|su -c 'ipa-ldap-updater --upgrade'}} followed by {{command|su -c 'ipa-upgradeconfig'}} after booting the upgraded system. Until you complete the update in this way, various elements of FreeIPA will not work correctly (including the web interface), and there will be error messages in the system logs.<br />
<br />
== GNOME issues ==<br />
{{Common bugs issue|gis-keyboard-crash|GNOME Initial Setup crashes if no keyboard is selected|1154171}}<br />
<br />
On first use of a Fedora 21 Workstation system (or other Fedora 21 installation with the GNOME desktop), an 'initial setup' process is run (the same as described in the previous issue). One of the early stages asks you to pick a keyboard layout. Depending on your earlier choice of language and location, it is possible that no layout will be pre-selected on the initial list of layout choices. If no layout is selected, and you do not select one but simply click Next, the initial setup tool will crash.<br />
<br />
The workaround for this issue is to make sure you select a keyboard layout. If none of the layouts is the one you want, clicking the '...' choice at the bottom of the list will cause the full list of layouts to be provided.<br />
<br />
== KDE issues ==<br />
{{Common bugs issue|kde-default-failsafe|Default KDE session after installation or on re-login to live session is failsafe|1164783}}<br />
{{Common_bugs_update_testing|FEDORA-2014-16304}}<br />
<br />
Due to an issue with how the sddm session manager orders desktop sessions, the failsafe session - "KDE Plasma (failsafe)" - will be the default session for interactive logins. This means that after installing Fedora 21 KDE in any way, or if you log out from a live session and log in again through the login screen, the default session choice will be the failsafe session. However, the session used on initial boot of the live image is not affected.<br />
<br />
To work around this issue, simply select the "KDE Plasma Workspace" session instead of "KDE Plasma (failsafe)" when you log in to KDE. You should only need to make this choice once for each user account - when you select a session, that session is stored as that user's default choice, so subsequent logins with that user will use the same session until you choose another.<br />
<br />
{{Common bugs issue|widget-drag-crash|Crash when adding new widget to panel via drag-and-drop|1170535}}<br />
<br />
You may encounter a crash in the Plasma Desktop Shell while adding a widget to the panel. If you open the 'Add widgets...' panel pop-up and try to drag a new widget from it to the panel, if you cross the button for a running application in the task manager widget while dragging, the crash will be triggered. The shell will respawn automatically and the session will continue to work correctly.<br />
<br />
To work around this issue simply be careful not to cross the task manager area of the panel when dragging. The Fedora KDE team will work to come up with a fix for this issue as soon as possible.<br />
<br />
{{Common bugs issue|kde-apper|Graphical package manager missing some PackageKit features|1098735}}<br />
<br />
In Fedora 21 Beta, {{package|apper}} (KDE's default graphical package manager and update tool) is missing some features, due to the replacement of the backend it previously used. Notably the ability to search within package groups is missing.<br />
<br />
A source code fix has been submitted to the PackageKit project. As a result, updated {{package|PackageKit}} packages resolving this issue should become available for testing shortly.<br />
<br />
== Network issues ==<br />
{{Common bugs issue|dhcp-identifier-fail|IP address discovery via DHCP does not work|1154200}}<br />
<br />
Several users have reported that Fedora 21 does not successfully discover an IP address via DHCP on their systems. An investigation of this issue has indicated that badly-behaving routers are the source of the problem, but some commonly-used router hardware and software appear to have the problematic behaviour by default. This at least appears to affect systems connected to Cisco RV320 routers, and possibly Windows Server systems acting as network routers. The issue may be more likely to occur in cases where the router is configured to assign specific IP addresses to specific systems based on their MAC addresses.<br />
<br />
To work around the issue, create a file {{filename|/etc/dhcp/dhclient.conf}} with the contents:<br />
send dhcp-client-identifier = hardware;<br />
or add that line to the file, if it already exists, and then try establishing the network connection again.<br />
<br />
We will attempt to find a way in which Fedora can cope with these problematic router configurations and provide an update to address this issue as soon as possible.<br />
<br />
== Hardware issues ==<br />
{{Common bugs issue|lenovo-nvidia-hang|Boot hangs when using NVIDIA discrete graphics on some Thinkpad models (W530)|752613}} <br />
<br />
This issue has been present [[Common_F19_bugs#lenovo-nvidia-hang|since at least Fedora 19]].<br />
<br />
Multiple testers have reported that various Thinkpad models - including at least the W530, and likely the W520 and T420 - that have hybrid Intel/NVIDIA graphics will fail to boot Fedora 19, 20, or 21 when using the discrete NVIDIA graphics adapter. Using the onboard Intel adapter, Fedora will boot successfully.<br />
<br />
Further testing indicates that this bug is an interaction between several features of these systems and of Fedora: the [http://software.intel.com/en-us/blogs/2009/06/25/understanding-vt-d-intel-virtualization-technology-for-directed-io VT-d advanced virtualization feature], the [https://en.wikipedia.org/wiki/X2APIC X2APIC level APIC], and the NVIDIA adapter. If all three of these things are used together, boot fails. If any one is removed from the equation, boot succeeds.<br />
<br />
So, if you are affected by this bug, you can choose to boot with any two of those things, but not all three together. You can disable the VT-d feature and select which graphics adapter to use through the system firmware. You can disable X2APIC functionality by passing the kernel parameter ''nox2apic''. In this way, you should be able to determine which of the features you want to use.<br />
<br />
The kernel developers plan to address this issue in a future kernel update by blacklisting X2APIC functionality on affected systems, when the NVIDIA adapter is in use.<br />
<br />
== ARM issues ==<br />
<br />
== Fedora Server issues ==<br />
{{Common bugs issue|rolekit-entropy|Rolekit fails to deploy a Domain Controller on a VM, returning error 256}}<br />
<br />
Creation of a Domain Controller role requires the system to have a sufficient amount of entropy available to securely create the keys for the included certificate authority and Kerberos key distribution center. It is very common when deploying on a virtual machine that has just been created that there will not be sufficient entropy available, which will result in the Domain Controller deployment timing out waiting on /dev/random and then failing with error code 256.<br />
<br />
On VM hosts that support it (such as KVM on Fedora 20 and 21), it is recommended to create the VM using the virt-RNG device (which the Fedora Server 21 guest will automatically detect). This will allow it to collect entropy from the host machine and should reduce the likelihood of encountering this issue. As a workaround (if you do not have a host capable of providing entropy), you can also run {{command|su -c '/usr/sbin/rngd -r /dev/urandom'}} to make the system use the <b>less-secure</b> /dev/urandom entropy device.<br />
<br />
{{Common bugs issue|ipa-start-race|FreeIPA startup fails due to timing issues|1071356}}<br />
<br />
This bug appears to occur only occasionally. Sometimes, startup of a FreeIPA server - {{filename|ipa.service}} - may fail, apparently due to some kind of race / timing issue between it, {{filename|named.service}} and {{filename|dirsrv.target}}. It does appear to happen only rarely, and when it happens, just starting {{filename|ipa.service}} again should succeed.<br />
<br />
== Other issues ==<br />
{{Common bugs issue|environment-product-conflicts|Installation of 'environment groups' fails due to conflicts between fedora-release packages|1160917}}<br />
<br />
Due to some limitations in how Fedora's package group mechanism works and some changes made to support the introduction of "Products" in Fedora 21, you may often encounter conflicts when trying to install the 'environment groups' seen in {{command|yum grouplist}} after installing Fedora 21. If you install a Fedora Product - Workstation, Cloud, or Server - it is likely that attempting to install any other 'environment group' will fail. If you use a non-Product install - for instance, install from a desktop live image - it is likely that you will be able to successfully install other non-Product environment groups, but not the environment groups associated with each Product.<br />
<br />
The most common case in which you're likely to encounter this is trying to add extra desktops to a Workstation or other desktop installation. If you install Workstation and then want to add any other desktop, or install another desktop and then want to add GNOME and decide to try and use the 'Workstation' group, you will likely run into this problem.<br />
<br />
Fortunately there is a fairly simple workaround for this problem: just add {{command|--exclude fedora-release\*}} to your command, e.g. {{command|yum groupinstall kde-desktop-environment --exclude fedora-release\*}}.<br />
<br />
It may not be possible to resolve this fully for Fedora 21. The bug report contains the detailed explanation of the problem, and solutions for it will likely be discussed there, if you wish to keep up to date.<br />
<br />
{{Common bugs issue|rendering-assamese-bengali|Rendering problems of Assamese and Bengali language content|1170135}}<br />
{{Common bugs update testing|FEDORA-2014-16196}}<br />
<br />
A rendering issue was found in Lohit Assamese and Bengali last upstream release 2.91.0. Due to this issue conjucts break if followed by any Bengali matra. Unfortunately this got detected during the final phase of Fedora 21 release. <br />
<br />
Anyone creating or viewing Assamese or Bengali language content in Fedora will encounter this issue.</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=FedUp&diff=397707FedUp2014-12-08T00:57:03Z<p>Kkofler: /* Important Changes in the Upgrade process to Fedora 21 */ Better use of emphasis.</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
= What is FedUp? =<br />
<br />
FedUp (FEDora UPgrader) is the name of a new system for upgrading Fedora installs in Fedora 18 and later. It replaces all of the previously recommended upgrade methods ([[PreUpgrade]] and DVD) that were been used in previous Fedora releases. Anaconda, the Fedora installer, has no built-in upgrade functionality in Fedora 18 or later. It has been completely delegated to FedUp.<br />
<br />
Currently, FedUp is capable of handling upgrades between all still-supported Fedora releases using a network repository or a DVD image as the package source. Upgrades from EOL Fedora releases may work, but are not supported. More methods for upgrade are currently planned and this page will be updated as those features are completed.<br />
<br />
= What Does FedUp do? =<br />
<br />
The FedUp system consists of two parts - the client used to download packages and prepare for the upgrade and a pre-boot environment which does the actual upgrade using [[Systemd|systemd]] and yum. More details are available in [http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ a blog post written by FedUp's primary author].<br />
<br />
Files are downloaded to /var/tmp/system-upgrade (or the specified --cachedir [to be implemented?]) and will be automatically cleaned up after the upgrade process is finished.<br />
<br />
== The FedUp Client ==<br />
<br />
The FedUp client runs on the system to be upgraded. It gathers the packages needed for upgrade in addition to downloading the required initramfs and kernel needed for the actual upgrade. At this time, only the fedup command-line interface is implemented but a GUI interface is expected...sometime.<br />
<br />
== The Upgrade ==<br />
<br />
The actual upgrade takes place when the system has been rebooted after running the FedUp client. The filesystems are mounted during boot, the already downloaded packages are installed and some upgrade-related tasks are performed. During the upgrade process, a special plymouth theme is used which has a progress bar to indicate current upgrade progress.<br />
<br />
== The Aftermath ==<br />
<br />
Once the upgrade is complete, FedUp will reboot the system automatically. This is so you can run this part of the process unattended and return to the upgraded system, but if you leave any bootable media attached to the system during the upgrade process, the system may boot from that medium instead of the hard disk once the upgrade is complete. If you leave your system upgrading, come back, and see the Fedora installer or something similar...that's probably what happened!<br />
<br />
= Frequently Asked Questions =<br />
== Why does my upgrade to Fedora 20 fail (immediately reboot to my old Fedora)? ==<br />
Because we messed up! Sorry about that. FedUp 0.7, which was in the Fedora 18 and 19 stable repositories at the time of Fedora 20's release, cannot successfully upgrade to Fedora 20. FedUp 0.8, though, can do it just fine. You should use FedUp 0.8 to upgrade to Fedora 20. If you're upgrading from Fedora 18, you'll need to pass <tt>--nogpgcheck</tt>. See [[Common_F20_bugs#fedup-07-fail|the Common Bugs page]] for all the details.<br />
<br />
== How do I report issues that I find with upgrades? ==<br />
First see [[Common F19 bugs]] or [[Common F20 bugs]] to check if the problem is a very prominent issue we already know of. If it is not there, the component for reporting problems depends on the exact issue that you hit:<br />
<br />
=== Issues with upgrade preparation ===<br />
If you hit issues when using the FedUp client ({{package|fedup}}) before reboot, [https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=fedup&resolution=--- search] or file a bug against FedUp using the version you are upgrading '''from'''.<br />
<br />
=== Issues During Upgrade ===<br />
If you hit issues after upgrade preparation and the initial reboot, [https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=fedup-dracut&resolution=--- search] or file a bug against {{package|fedup-dracut}} using the version you are upgrading '''to'''.<br />
<br />
=== Issues After Upgrade ===<br />
If you hit issues after upgrade with a specific package, file a bug against the package with which you are having issues.<br />
<br />
== How do I Debug Issues During Upgrade? ==<br />
A troubleshooting and debug guide will be written at some point and linked to from here.<br />
<br />
== Does FedUp verify the software it runs or installs during upgrade? ==<br />
Since version 0.8, it does so by default. The package signing keys for newer Fedora releases are now sent to older Fedora releases in order to allow FedUp to verify the integrity of the packages it downloads. You can disable this function with the --nogpgcheck parameter if you need to do so for any reason.<br />
<br />
== Will packages in third party repositories be upgraded? ==<br />
<br />
Yes, if they are set up like regular yum repositories and do not hard code the repository path. Commonly-used third party repositories usually work fine, but if you attempt to upgrade prior to or soon after an official Fedora release, they may not have updated their repository paths yet, and FedUp may be unable to find their packages. This will usually not prevent the upgrade running successfully, though, and you can update the packages from the third-party repository later.<br />
<br />
== Can I use FedUp to upgrade to a pre-release (e.g. a beta)? ==<br />
<br />
Yes. After a Fedora release has been branched, it should be possible to upgrade to it using FedUp. It should also work after the Alpha and Beta releases. Of course, this function is as subject to temporary breakage as any other aspect of a pre-release.<br />
<br />
See this [http://lists.fedoraproject.org/pipermail/devel/2013-May/183508.html email to the Fedora devel mailing list] for more details.<br />
<br />
= How Can I Upgrade My System with FedUp? =<br />
As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.<br />
<br />
Before you start doing anything, be sure to have a look at [[Common F20 bugs#Upgrade_issues]] and read about the most common bugs found.<br />
<br />
==Important Changes in the Upgrade process to Fedora 21==<br />
In order to select one of the new Fedora flavors, FedUp has new option, "--product=<PRODUCT>". To upgrade to the new Fedora Workstation, use <code>--product=workstation</code>. (This will also '''install ''all'' packages from the default Workstation installation''', including the GNOME 3 desktop environment, in addition to upgrading the packages you already had installed.) If you would prefer to remain on the general, custom "track", use <code>--product=nonproduct</code>.<br />
<br />
Here is the explanation given in the source code of fedup (https://github.com/wgwoods/fedup/blob/master/fedup/commandline.py):<br />
<pre><br />
This installation of Fedora does not belong to a product, so you<br />
must provide the --product=PRODUCTNAME option to specify what product<br />
you want to upgrade to. PRODUCTNAME should be one of:<br />
<br />
workstation: the default Fedora experience for laptops and desktops,<br />
powered by GNOME.<br />
<br />
server: the default Fedora experience for servers<br />
<br />
cloud: a base image for use on public and private clouds<br />
<br />
nonproduct: choose this if none of the above apply; in particular,<br />
choose this if you are using an alternate-desktop spin of Fedora<br />
Selecting a product will also install its standard package-set in<br />
addition to upgrading the packages already on your system. If you<br />
prefer to maintain your current set of packages, select 'nonproduct'<br />
</pre><br />
<br />
== Preparing for the Upgrade ==<br />
{{admon/important|Latest fedup|Make sure that you install the latest version of the fedup client on the system to be upgraded. At the time of this writing (2013-12-17), that is fedup-0.8.0-3.}}<br />
# Do a full system update and reboot to ensure that any kernel changes are running<br />
# Install {{package|fedup}}<br />
#* Usually, it is best to try first with the latest fedup available in the stable update repository for the release you are running. If you encounter problems with the upgrade, and a newer fedup is available in the updates-testing repository for your current release, you may wish to try with this newer version: {{command|yum --enablerepo<nowiki>=</nowiki>updates-testing install fedup}} at the command line)<br />
<br />
There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc).<br />
<br />
{{admon/important|Network upgrade is strongly recommended|It is strongly recommended to use the network upgrade instead of offline update modes (ISO, local device). Network upgrade will ensure you receive the latest packages from the target release. If you use local media containing older packages, you might end up with a mixture of packages from your former and target release, and the system might not work properly until you fully update it after reboot (if it boots at all).}}<br />
<br />
=== Network ===<br />
Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading.<br />
<br />
# Start the upgrade prep by executing following commands<br />
#* {{command|sudo yum update fedup fedora-release}}<br />
#* {{command|sudo fedup --network 20}}<br />
# Once the preparations have completed, check the {{filename|/var/log/fedup.log}} file if any errors show up in the output from {{command|fedup}}<br />
<br />
=== ISO File ===<br />
In order to use an ISO file, it needs to exist locally on the filesystem of the system to be upgraded. The documentation is written as if that file is /home/user/fedora-20.iso but you will need to replace all instances of that path with the actual path of the ISO. Updates will be pulled in if you have network access on the machine to be upgraded.<br />
<br />
# Download the Fedora {{FedoraVersion}} ISO appropriate for the arch that you are running<br />
#* For the sake of example, we will assume that the ISO exists at {{filename|/home/user/fedora-20.iso}} but it can be anywhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO. Make sure you have downloaded Fedora DVD ISO image otherwise you will get an error "The given ISO probably isn't an install DVD image" when run {{command|fedup-cli}} command.<br />
# Start the upgrade prep by executing the following command<br />
#* {{command|sudo fedup-cli --iso /home/user/fedora-20.iso}}<br />
# Once the preparations have completed, check the {{filename|/var/log/fedup.log}} file if any errors show up in the output from {{command|fedup-cli}}<br />
<br />
=== Other Device ===<br />
Optical drives and other mountable storage can also be used as a package source for upgrade preparations.<br />
<br />
# Mount the source material<br />
#* For the sake of example, we will assume that this source is mounted at {{filename|/mnt/fedora}} but you can mount it anywhere as long as you replace {{filename|/mnt/fedora}} in the command below with the actual mounted location of the upgrade source.<br />
# Start the upgrade preparations by executing the following command<br />
#* {{command|sudo fedup-cli --device /mnt/fedora --debuglog<nowiki>=</nowiki>fedupdebug.log}}<br />
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}<br />
<br />
== Executing the Upgrade ==<br />
# Reboot the system if {{command|fedup}} has completed without error.<br />
# Once the system reboots, there should be a new entry in the GRUB menu titled {{command|'''System Upgrade'''}}.<br />
#* If you add <code>rd.upgrade.debugshell</code> boot argument, you will get a login shell on VT2, allowing you to tinker with the system in case something goes wrong<br />
# Select the {{command|'''System Upgrade'''}} option from the GRUB menu<br />
#*'''Remark:''' If the {{command|'''System Upgrade'''}} item is not shown in the grublist at boot, it is most often caused by having a different grub, most often installed by another Linux distribution you may have in multiboot. To correct this quickly: reinstall grub:<br />
#*# grub2-mkconfig -o /boot/grub2/grub.cfg<br />
#*# grub2-install /dev/sda '''(replace /dev/sda by any other device you prefer to boot from)'''<br />
# The system should boot into the upgrade process and a plymouth boot screen should be displayed<br />
#* Press 'esc' to see a more detailed log. If you switch back to the graphical progress indicator, it will show 0% for the remainder of the upgrade but that does not mean the upgrade has stopped.<br />
# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|current}} will be on the grub menu<br />
<br />
== Cleaning Up Post Upgrade ==<br />
<br />
<!-- Some of the stuff from [http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup this post upgrade cleanup guide] might be wise --><br />
<br />
It is worth rebuilding the RPM DB to prevent RPMDB checksum error when doing a distribution sync:<br />
<br />
{{command|sudo rpm --rebuilddb}}<br />
<br />
There are a collection of post-upgrade things to do. Some of which are fixed by doing a distro sync:<br />
<br />
{{command|sudo yum distro-sync --setopt<nowiki>=</nowiki>deltarpm<nowiki>=</nowiki>0}}<br />
<br />
If you are using google-chrome from the Google repository, you must re-install google-chrome due to a packaging bug on the Google side of things. Make sure to adjust the command to the build type you would like to install:<br />
<br />
{{command|sudo yum remove google-chrome-\* && sudo yum install google-chrome-[beta,stable,unstable]}}<br />
<br />
= Docs TODO =<br />
* Write fedup troubleshooting and debug guide<br />
* add note about blob drivers if needed</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=FedUp&diff=397706FedUp2014-12-08T00:55:52Z<p>Kkofler: /* Important Changes in the Upgrade process to Fedora 21 */ Make clear what "--product=workstation" really does.</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
= What is FedUp? =<br />
<br />
FedUp (FEDora UPgrader) is the name of a new system for upgrading Fedora installs in Fedora 18 and later. It replaces all of the previously recommended upgrade methods ([[PreUpgrade]] and DVD) that were been used in previous Fedora releases. Anaconda, the Fedora installer, has no built-in upgrade functionality in Fedora 18 or later. It has been completely delegated to FedUp.<br />
<br />
Currently, FedUp is capable of handling upgrades between all still-supported Fedora releases using a network repository or a DVD image as the package source. Upgrades from EOL Fedora releases may work, but are not supported. More methods for upgrade are currently planned and this page will be updated as those features are completed.<br />
<br />
= What Does FedUp do? =<br />
<br />
The FedUp system consists of two parts - the client used to download packages and prepare for the upgrade and a pre-boot environment which does the actual upgrade using [[Systemd|systemd]] and yum. More details are available in [http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ a blog post written by FedUp's primary author].<br />
<br />
Files are downloaded to /var/tmp/system-upgrade (or the specified --cachedir [to be implemented?]) and will be automatically cleaned up after the upgrade process is finished.<br />
<br />
== The FedUp Client ==<br />
<br />
The FedUp client runs on the system to be upgraded. It gathers the packages needed for upgrade in addition to downloading the required initramfs and kernel needed for the actual upgrade. At this time, only the fedup command-line interface is implemented but a GUI interface is expected...sometime.<br />
<br />
== The Upgrade ==<br />
<br />
The actual upgrade takes place when the system has been rebooted after running the FedUp client. The filesystems are mounted during boot, the already downloaded packages are installed and some upgrade-related tasks are performed. During the upgrade process, a special plymouth theme is used which has a progress bar to indicate current upgrade progress.<br />
<br />
== The Aftermath ==<br />
<br />
Once the upgrade is complete, FedUp will reboot the system automatically. This is so you can run this part of the process unattended and return to the upgraded system, but if you leave any bootable media attached to the system during the upgrade process, the system may boot from that medium instead of the hard disk once the upgrade is complete. If you leave your system upgrading, come back, and see the Fedora installer or something similar...that's probably what happened!<br />
<br />
= Frequently Asked Questions =<br />
== Why does my upgrade to Fedora 20 fail (immediately reboot to my old Fedora)? ==<br />
Because we messed up! Sorry about that. FedUp 0.7, which was in the Fedora 18 and 19 stable repositories at the time of Fedora 20's release, cannot successfully upgrade to Fedora 20. FedUp 0.8, though, can do it just fine. You should use FedUp 0.8 to upgrade to Fedora 20. If you're upgrading from Fedora 18, you'll need to pass <tt>--nogpgcheck</tt>. See [[Common_F20_bugs#fedup-07-fail|the Common Bugs page]] for all the details.<br />
<br />
== How do I report issues that I find with upgrades? ==<br />
First see [[Common F19 bugs]] or [[Common F20 bugs]] to check if the problem is a very prominent issue we already know of. If it is not there, the component for reporting problems depends on the exact issue that you hit:<br />
<br />
=== Issues with upgrade preparation ===<br />
If you hit issues when using the FedUp client ({{package|fedup}}) before reboot, [https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=fedup&resolution=--- search] or file a bug against FedUp using the version you are upgrading '''from'''.<br />
<br />
=== Issues During Upgrade ===<br />
If you hit issues after upgrade preparation and the initial reboot, [https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=fedup-dracut&resolution=--- search] or file a bug against {{package|fedup-dracut}} using the version you are upgrading '''to'''.<br />
<br />
=== Issues After Upgrade ===<br />
If you hit issues after upgrade with a specific package, file a bug against the package with which you are having issues.<br />
<br />
== How do I Debug Issues During Upgrade? ==<br />
A troubleshooting and debug guide will be written at some point and linked to from here.<br />
<br />
== Does FedUp verify the software it runs or installs during upgrade? ==<br />
Since version 0.8, it does so by default. The package signing keys for newer Fedora releases are now sent to older Fedora releases in order to allow FedUp to verify the integrity of the packages it downloads. You can disable this function with the --nogpgcheck parameter if you need to do so for any reason.<br />
<br />
== Will packages in third party repositories be upgraded? ==<br />
<br />
Yes, if they are set up like regular yum repositories and do not hard code the repository path. Commonly-used third party repositories usually work fine, but if you attempt to upgrade prior to or soon after an official Fedora release, they may not have updated their repository paths yet, and FedUp may be unable to find their packages. This will usually not prevent the upgrade running successfully, though, and you can update the packages from the third-party repository later.<br />
<br />
== Can I use FedUp to upgrade to a pre-release (e.g. a beta)? ==<br />
<br />
Yes. After a Fedora release has been branched, it should be possible to upgrade to it using FedUp. It should also work after the Alpha and Beta releases. Of course, this function is as subject to temporary breakage as any other aspect of a pre-release.<br />
<br />
See this [http://lists.fedoraproject.org/pipermail/devel/2013-May/183508.html email to the Fedora devel mailing list] for more details.<br />
<br />
= How Can I Upgrade My System with FedUp? =<br />
As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.<br />
<br />
Before you start doing anything, be sure to have a look at [[Common F20 bugs#Upgrade_issues]] and read about the most common bugs found.<br />
<br />
==Important Changes in the Upgrade process to Fedora 21==<br />
In order to select one of the new Fedora flavors, FedUp has new option, "--product=<PRODUCT>". To upgrade to the new Fedora Workstation, use <code>--product=workstation</code>. ('''This will also install all packages from the default Workstation installation, including the GNOME 3 desktop environment, in addition to upgrading the packages you already had installed.''') If you would prefer to remain on the general, custom "track", use <code>--product=nonproduct</code>.<br />
<br />
Here is the explanation given in the source code of fedup (https://github.com/wgwoods/fedup/blob/master/fedup/commandline.py):<br />
<pre><br />
This installation of Fedora does not belong to a product, so you<br />
must provide the --product=PRODUCTNAME option to specify what product<br />
you want to upgrade to. PRODUCTNAME should be one of:<br />
<br />
workstation: the default Fedora experience for laptops and desktops,<br />
powered by GNOME.<br />
<br />
server: the default Fedora experience for servers<br />
<br />
cloud: a base image for use on public and private clouds<br />
<br />
nonproduct: choose this if none of the above apply; in particular,<br />
choose this if you are using an alternate-desktop spin of Fedora<br />
Selecting a product will also install its standard package-set in<br />
addition to upgrading the packages already on your system. If you<br />
prefer to maintain your current set of packages, select 'nonproduct'<br />
</pre><br />
<br />
== Preparing for the Upgrade ==<br />
{{admon/important|Latest fedup|Make sure that you install the latest version of the fedup client on the system to be upgraded. At the time of this writing (2013-12-17), that is fedup-0.8.0-3.}}<br />
# Do a full system update and reboot to ensure that any kernel changes are running<br />
# Install {{package|fedup}}<br />
#* Usually, it is best to try first with the latest fedup available in the stable update repository for the release you are running. If you encounter problems with the upgrade, and a newer fedup is available in the updates-testing repository for your current release, you may wish to try with this newer version: {{command|yum --enablerepo<nowiki>=</nowiki>updates-testing install fedup}} at the command line)<br />
<br />
There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc).<br />
<br />
{{admon/important|Network upgrade is strongly recommended|It is strongly recommended to use the network upgrade instead of offline update modes (ISO, local device). Network upgrade will ensure you receive the latest packages from the target release. If you use local media containing older packages, you might end up with a mixture of packages from your former and target release, and the system might not work properly until you fully update it after reboot (if it boots at all).}}<br />
<br />
=== Network ===<br />
Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading.<br />
<br />
# Start the upgrade prep by executing following commands<br />
#* {{command|sudo yum update fedup fedora-release}}<br />
#* {{command|sudo fedup --network 20}}<br />
# Once the preparations have completed, check the {{filename|/var/log/fedup.log}} file if any errors show up in the output from {{command|fedup}}<br />
<br />
=== ISO File ===<br />
In order to use an ISO file, it needs to exist locally on the filesystem of the system to be upgraded. The documentation is written as if that file is /home/user/fedora-20.iso but you will need to replace all instances of that path with the actual path of the ISO. Updates will be pulled in if you have network access on the machine to be upgraded.<br />
<br />
# Download the Fedora {{FedoraVersion}} ISO appropriate for the arch that you are running<br />
#* For the sake of example, we will assume that the ISO exists at {{filename|/home/user/fedora-20.iso}} but it can be anywhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO. Make sure you have downloaded Fedora DVD ISO image otherwise you will get an error "The given ISO probably isn't an install DVD image" when run {{command|fedup-cli}} command.<br />
# Start the upgrade prep by executing the following command<br />
#* {{command|sudo fedup-cli --iso /home/user/fedora-20.iso}}<br />
# Once the preparations have completed, check the {{filename|/var/log/fedup.log}} file if any errors show up in the output from {{command|fedup-cli}}<br />
<br />
=== Other Device ===<br />
Optical drives and other mountable storage can also be used as a package source for upgrade preparations.<br />
<br />
# Mount the source material<br />
#* For the sake of example, we will assume that this source is mounted at {{filename|/mnt/fedora}} but you can mount it anywhere as long as you replace {{filename|/mnt/fedora}} in the command below with the actual mounted location of the upgrade source.<br />
# Start the upgrade preparations by executing the following command<br />
#* {{command|sudo fedup-cli --device /mnt/fedora --debuglog<nowiki>=</nowiki>fedupdebug.log}}<br />
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}<br />
<br />
== Executing the Upgrade ==<br />
# Reboot the system if {{command|fedup}} has completed without error.<br />
# Once the system reboots, there should be a new entry in the GRUB menu titled {{command|'''System Upgrade'''}}.<br />
#* If you add <code>rd.upgrade.debugshell</code> boot argument, you will get a login shell on VT2, allowing you to tinker with the system in case something goes wrong<br />
# Select the {{command|'''System Upgrade'''}} option from the GRUB menu<br />
#*'''Remark:''' If the {{command|'''System Upgrade'''}} item is not shown in the grublist at boot, it is most often caused by having a different grub, most often installed by another Linux distribution you may have in multiboot. To correct this quickly: reinstall grub:<br />
#*# grub2-mkconfig -o /boot/grub2/grub.cfg<br />
#*# grub2-install /dev/sda '''(replace /dev/sda by any other device you prefer to boot from)'''<br />
# The system should boot into the upgrade process and a plymouth boot screen should be displayed<br />
#* Press 'esc' to see a more detailed log. If you switch back to the graphical progress indicator, it will show 0% for the remainder of the upgrade but that does not mean the upgrade has stopped.<br />
# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|current}} will be on the grub menu<br />
<br />
== Cleaning Up Post Upgrade ==<br />
<br />
<!-- Some of the stuff from [http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup this post upgrade cleanup guide] might be wise --><br />
<br />
It is worth rebuilding the RPM DB to prevent RPMDB checksum error when doing a distribution sync:<br />
<br />
{{command|sudo rpm --rebuilddb}}<br />
<br />
There are a collection of post-upgrade things to do. Some of which are fixed by doing a distro sync:<br />
<br />
{{command|sudo yum distro-sync --setopt<nowiki>=</nowiki>deltarpm<nowiki>=</nowiki>0}}<br />
<br />
If you are using google-chrome from the Google repository, you must re-install google-chrome due to a packaging bug on the Google side of things. Make sure to adjust the command to the build type you would like to install:<br />
<br />
{{command|sudo yum remove google-chrome-\* && sudo yum install google-chrome-[beta,stable,unstable]}}<br />
<br />
= Docs TODO =<br />
* Write fedup troubleshooting and debug guide<br />
* add note about blob drivers if needed</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Using_UEFI_with_QEMU&diff=395419Using UEFI with QEMU2014-11-22T04:51:11Z<p>Kkofler: /* EDK2 Licensing Issues */ Fix/update the link to the upstream wiki.</p>
<hr />
<div><br />
= Testing secureboot with KVM =<br />
<br />
This page documents how to test Fedora 18+ [[Secureboot]] support inside<br />
a KVM VM. The audience here is QA folks that want to test secureboot, and<br />
any other curious parties.<br />
<br />
== Install OVMF ==<br />
<br />
OVMF (Open Virtual Machine Firmware) is basically UEFI for KVM. It comes<br />
from EDK2 (EFI Development Kit), which is the UEFI reference implementation.<br />
<br />
Unfortunately there are licensing issues which prevent us getting EDK2/OVMF<br />
into Fedora (see [[#EDK2 Licensing Issues]] at the end of this document for more info). So we<br />
have to grab external packages.<br />
<br />
== Running EDK2/OVMF nightly builds ==<br />
<br />
Gerd Hoffman, Red Hatter and QEMU developer, has a yum repo on his personal<br />
site that provides nightly builds of a whole bunch of QEMU/KVM firmware,<br />
including EDK2/OVMF.<br />
<br />
Here's how to pull down the nightly builds:<br />
<br />
sudo wget http://www.kraxel.org/repos/firmware.repo -O /etc/yum.repos.d/firmware.repo<br />
<br />
# Disable by default, likely preferred for QA<br />
sudo sed -i -e "s/enabled=1/enabled=0/g" /etc/yum.repos.d/firmware.repo<br />
sudo yum --enablerepo=qemu-firmware-jenkins install edk2.git-ovmf-x64<br />
<br />
The OVMF image is at:<br />
<br />
/usr/share/edk2.git/ovmf-x64/OVMF-pure-efi.fd<br />
<br />
Since these are nightly builds, occasionally things break. To work around this, use the following commands to get the February<br />
26th 2014 nightly build:<br />
<br />
sudo wget http://drsmith2.fedorapeople.org/edk2.git/edk2.git-0-20140226.b491.gb9b77ab.x86_64.rpm<br />
sudo wget http://drsmith2.fedorapeople.org/edk2.git/edk2.git-ovmf-ia32-0-20140226.b491.gb9b77ab.x86_64.rpm<br />
sudo rpm -ivh edk2.git-0-20140226.b491.gb9b77ab.x86_64.rpm edk2.git-ovmf-ia32-0-20140226.b491.gb9b77ab.x86_64.rpm<br />
<br />
== Install an F18+ VM with UEFI ==<br />
<br />
First we need to install a guest using UEFI instead of traditional bios.<br />
Anaconda will put all the right bits in place for us. You can probably<br />
convert an existing bios guest to use UEFI but I haven't found steps to do<br />
so.<br />
<br />
Newer OVMF builds can use a network install, older builds were slow when using a network install. If the network install seems slow, switch to using a DVD install.<br />
<br />
Here's an example F20 install:<br />
<br />
sudo virt-install --name f20-uefi --ram 2048 --boot loader=/usr/share/edk2.git/ovmf-x64/OVMF-pure-efi.fd --disk /var/lib/libvirt/images/f20-uefi.qcow,format=qcow2,size=10 --os-variant fedora20 --cdrom /path/to/Fedora-20-x86_64-netinst.iso<br />
<br />
(If you'd like to create a rawhide guest, you combine the above command with the following info: <https://fedoraproject.org/wiki/Releases/Rawhide?rd=Rawhide#Point_installer_to_Rawhide>)<br />
<br />
Follow the install to completion, log in and do firstboot, then move along.<br />
Secure boot isn't set up yet.<br />
<br />
== Booting the VM with OVMF ==<br />
<br />
If Fedora doesn't boot, try the following steps. First you'll need to be at the EFI Internal Shell. If you see a 'Shell> ' prompt you are in the shell.<br />
If OVMF doesn't drop you into the EFI Internal Shell automatically, do the following:<br />
<br />
# Wait until the TianoCore splash screen pops up, hit ESC<br />
# Select 'Boot Manager'<br />
# Select 'EFI Internal Shell'<br />
<br />
Once in the EFI Internal Shell, here are the commands you need to boot Fedora (assuming your guest only has a CDROM attached):<br />
<br />
fs0:<br />
\EFI\fedora\shim.efi<br />
<br />
The above commands just get Fedora going, we haven't set up secure boot yet.<br />
<br />
== Grab LockDown_ms.efi ==<br />
<br />
Since OVMF doesn't ship with any SecureBoot keys installed, we need to<br />
install some to mimic what an MS certified UEFI machine will ship with.<br />
But here's a crappy thing about OVMF and KVM: right now there's no way to<br />
persist UEFI config across VM start/stop, although we'll come close with the script we'll create below.<br />
{{admon/note|Improvements in Fedora 20|<br />
With qemu 1.6 and later, a ''-pflash bios.bin'' option, is supposed to enable persistent EFI variables. This may or may not also require ''-no-kvm''.}}<br />
So if we want to test SecureBoot,<br />
we need to install the MS keys and enable secureboot on every VM restart.<br />
<br />
Luckily there's a tool that does all this for us, called LockDown_ms.efi.<br />
This is derived from code in [http://git.kernel.org/?p=linux/kernel/git/jejb/efitools.git;a=summary efitools.git].<br />
<br />
Inside the guest, do:<br />
<br />
sudo wget http://fedorapeople.org/~crobinso/secureboot/LockDown_ms.efi -O /boot/efi/EFI/fedora/LockDown_ms.efi<br />
<br />
== Automate SecureBoot startup ==<br />
<br />
As mentioned above, we have to install the MS keys and enable secureboot on every VM restart. Luckily, OVMF by default runs a script at startup, called startup.nsh. We'll use this to automate startup. All we really need in the script are the following commands:<br />
<br />
fs0:<br />
\EFI\fedora\LockDown_ms.efi<br />
\EFI\fedora\shim.efi<br />
<br />
But, life is complicated by the fact that if you are rebooting the VM where LockDown_ms.efi has been loaded, it can't be loaded a second time (without powering off the VM). If you try, you'll get a "Error reported: Security Violation" message when loading LockDown_ms.efi and the script will stop. So, the script needs to check if SecureBoot is already on before trying to load LockDown_ms.efi.<br />
<br />
Inside the guest, as root edit /boot/efi/startup.nsh and add the following text:<br />
<br />
fs0:<br />
# If we don't have the secure boot dmp file, assume this is the first<br />
# time this script has been run and secure boot is off.<br />
set __lockdown 0<br />
if not exist SecureBoot.dmp then<br />
set __lockdown 1<br />
# Otherwise we check the current state of the 'SecureBoot' variable<br />
# to see if LockDown_ms.efi has already been loaded.<br />
else<br />
dmpstore SecureBoot -s SecureBoot.tmp<br />
comp SecureBoot.dmp SecureBoot.tmp<br />
if not %lasterror% == 0 then<br />
set __lockdown 1<br />
endif<br />
rm SecureBoot.tmp<br />
endif<br />
if %__lockdown% == 1 then<br />
\EFI\fedora\LockDown_ms.efi<br />
dmpstore SecureBoot -s SecureBoot.dmp<br />
endif<br />
\EFI\fedora\shim.efi<br />
<br />
== Verify SecureBoot ==<br />
<br />
At this point reboot the guest. After logging in, you should see 'Secure boot enabled' in dmesg. Success!<br />
<br />
= Misc bits =<br />
<br />
== EDK2 Licensing Issues ==<br />
<br />
EDK2 contains a FAT filesystem driver that is licensed under terms that<br />
make it not acceptable for packaging in Fedora. Particularly that there's<br />
a usage restricition only allowing the code to be used in a UEFI<br />
implementation. More details here at [http://tianocore.sourceforge.net/wiki/Edk2-fat-driver Edk2-fat-driver]<br />
<br />
The driver is critical functionality so removing it is not an option.<br />
<br />
== Pointing an existing guest at OVMF ==<br />
<br />
To alter an existing guest to use OVMF, or change the OVMF build it uses, do<br />
<code>sudo virsh edit $vmname</code> and add<br />
<br />
<domain><br />
...<br />
<os><br />
...<br />
<loader>/path/to/OVMF-pure-efi.fd</loader><br />
<br />
You will also need to ensure the 'shim' package is installed in the guest.<br />
<br />
== Testing F18 DVD Secure Boot in a VM ==<br />
<br />
Since we can't easily alter the DVD to add LockDown_ms.efi, we get it into<br />
the VM using a mini disk image:<br />
<br />
wget http://fedorapeople.org/~crobinso/secureboot/lockdown.qcow2<br />
sudo virsh attach-disk $VMNAME --target hdb --source lockdown.qcow2 --subdriver qcow2 --config<br />
<br />
Then do<br />
<br />
* Launch the VM, drop to the EFI shell<br />
* If your guest only has a CDROM attached, lockdown.qcow2 should be fs0<br />
* <code>Shell> fs0:</code><br />
* <code>fs0:\> LockDown_ms.efi </code><br />
* <code>fs0:\> exit </code><br />
* Back in the config screen, Select 'Boot Manager'<br />
* Select 'EFI DVD/CDROM'<br />
* Once anaconda starts, grab shell, log in, verify secure boot is enabled<br />
<br />
== Extra links ==<br />
<br />
* [https://wiki.ubuntu.com/SecurityTeam/SecureBoot Ubuntu secureboot page]<br />
* [http://en.opensuse.org/openSUSE:UEFI_Secure_boot_using_qemu-kvm OpenSUSE secureboot page]<br />
* [http://www.linux-kvm.org/page/OVMF KVM wiki OVMF page]<br />
<br />
[[Category:Virtualization]] [[Category:QA]]</div>Kkoflerhttps://fedoraproject.org/w/index.php?title=Test_Results:Fedora_21_Beta_RC4_Desktop&diff=393323Test Results:Fedora 21 Beta RC4 Desktop2014-10-30T10:33:56Z<p>Kkofler: /* Release-blocking desktops: ARM */ Add bug ID for the (longstanding) Konqueror download directory bug.</p>
<hr />
<div><br />
{{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=RC4}}<br />
<br />
== '''Test Matrix''' ==<br />
<br />
<onlyinclude><br />
<br />
{{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=RC4}}<br />
<br />
== '''Test Matrix''' ==<br />
<br />
<onlyinclude><br />
<br />
{{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=RC4}}<br />
<br />
== '''Test Matrix''' ==<br />
<br />
<onlyinclude><br />
<br />
{{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=RC4}}<br />
<br />
== '''Test Matrix''' ==<br />
<br />
<onlyinclude><br />
==== Release-blocking desktops: '''x86 / x86_64''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Workstation]] !! [[KDE]]<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|pass|adamwill}}{{result|pass|roshi}}<br />
| {{result|warn|jreznik|705086}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|pass|adamwill}}{{result|pass|roshi}}<br />
| {{result|pass|jreznik}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|pass|roshi}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|pass|adamwill}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|pass|adamwill}}{{result|pass|roshi}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|pass|adamwill}}{{result|pass|roshi}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}{{result|pass|roshi}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_workstation_core_applications]]<br />
| {{result|pass|adamwill}}{{result|pass|roshi}}<br />
| style="background:lightgrey;"|<br />
|-<br />
| Beta<br />
| [[QA:Testcase_workstation_theming]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[KDE]]<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|warn|yselkowitz}} <ref>Default download directory in Konqueror is ~/Documents, not ~/Downloads. (kkofler: This is #705086, an architecture-independent bug also noted by jreznik for x86.)</ref><br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|inprogress|yselkowitz}}<ref>PIM Setting Exporter listed under both Internet and Office, and is missing icon</ref><br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''x86 / x86_64''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Workstation]] !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_workstation_core_applications]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_workstation_theming]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Sugar (non-blocking, all arches) ====<br />
<br />
{{admon/note|Sugar test cases|The Sugar desktop differs significantly from a typical desktop, so it gets its own test cases. At present these live [http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases on the Sugar wiki].}}<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Test Case !! x86 !! ARM<br />
|-<br />
| QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#1_-_SoaS_boots_to_the_.28name.29_selection_screen. SoaS boots to the (name) selection screen]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#2_-_SoaS_installed_to_hard_disk_with_liveinst_from_root_terminal.2C SoaS installed to hard disk with {{Code|liveinst}} from root terminal]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#3_-_Jabber.sugarlabs.org_should_connect_and_display_XO_.22Buddies.22 Jabber.sugarlabs.org should connect and display XO "Buddies"]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#4_-_When_a_USB_storage_device_is_inserted.2C_it_should_show_up_in_the_Frame. When a USB storage device is inserted, it should show up in the Frame]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#5_-Functions_in_My_Settings_.28Sugar_control_panel.29. Functions in My Settings (Sugar control panel)]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#6_-_Applications_in_the_Home_Screen Applications in the ''Home Screen'']<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#7_-Sugar-desktop_installed_in_another_Desktop Sugar-desktop installed in another Desktop]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/></onlyinclude><br />
<br />
[[Category:Desktop_validation_testing]]<br />
[[Category:Fedora_21_Beta_Test_Results|Desktop]]<br />
<br />
==== Release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[KDE]]<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|warn|yselkowitz}} <ref>Default download directory in Konqueror is ~/Documents, not ~/Downloads.</ref><br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|inprogress|yselkowitz}}<ref>PIM Setting Exporter listed under both Internet and Office, and is missing icon</ref><br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''x86 / x86_64''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Workstation]] !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_workstation_core_applications]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_workstation_theming]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Sugar (non-blocking, all arches) ====<br />
<br />
{{admon/note|Sugar test cases|The Sugar desktop differs significantly from a typical desktop, so it gets its own test cases. At present these live [http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases on the Sugar wiki].}}<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Test Case !! x86 !! ARM<br />
|-<br />
| QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#1_-_SoaS_boots_to_the_.28name.29_selection_screen. SoaS boots to the (name) selection screen]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#2_-_SoaS_installed_to_hard_disk_with_liveinst_from_root_terminal.2C SoaS installed to hard disk with {{Code|liveinst}} from root terminal]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#3_-_Jabber.sugarlabs.org_should_connect_and_display_XO_.22Buddies.22 Jabber.sugarlabs.org should connect and display XO "Buddies"]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#4_-_When_a_USB_storage_device_is_inserted.2C_it_should_show_up_in_the_Frame. When a USB storage device is inserted, it should show up in the Frame]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#5_-Functions_in_My_Settings_.28Sugar_control_panel.29. Functions in My Settings (Sugar control panel)]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#6_-_Applications_in_the_Home_Screen Applications in the ''Home Screen'']<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#7_-Sugar-desktop_installed_in_another_Desktop Sugar-desktop installed in another Desktop]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/></onlyinclude><br />
<br />
[[Category:Desktop_validation_testing]]<br />
[[Category:Fedora_21_Beta_Test_Results|Desktop]]<br />
<br />
==== Release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[KDE]]<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|warn|yselkowitz}} <ref>Default download directory in Konqueror is ~/Documents, not ~/Downloads.</ref><br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|inprogress|yselkowitz}}<ref>PIM Setting Exporter listed under both Internet and Office, and is missing icon</ref><br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''x86 / x86_64''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Workstation]] !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_workstation_core_applications]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_workstation_theming]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Sugar (non-blocking, all arches) ====<br />
<br />
{{admon/note|Sugar test cases|The Sugar desktop differs significantly from a typical desktop, so it gets its own test cases. At present these live [http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases on the Sugar wiki].}}<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Test Case !! x86 !! ARM<br />
|-<br />
| QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#1_-_SoaS_boots_to_the_.28name.29_selection_screen. SoaS boots to the (name) selection screen]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#2_-_SoaS_installed_to_hard_disk_with_liveinst_from_root_terminal.2C SoaS installed to hard disk with {{Code|liveinst}} from root terminal]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#3_-_Jabber.sugarlabs.org_should_connect_and_display_XO_.22Buddies.22 Jabber.sugarlabs.org should connect and display XO "Buddies"]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#4_-_When_a_USB_storage_device_is_inserted.2C_it_should_show_up_in_the_Frame. When a USB storage device is inserted, it should show up in the Frame]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#5_-Functions_in_My_Settings_.28Sugar_control_panel.29. Functions in My Settings (Sugar control panel)]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#6_-_Applications_in_the_Home_Screen Applications in the ''Home Screen'']<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#7_-Sugar-desktop_installed_in_another_Desktop Sugar-desktop installed in another Desktop]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/></onlyinclude><br />
<br />
[[Category:Desktop_validation_testing]]<br />
[[Category:Fedora_21_Beta_Test_Results|Desktop]]<br />
<br />
==== Release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[KDE]]<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|warn|yselkowitz}} <ref>Default download directory in Konqueror is ~/Documents, not ~/Downloads.</ref><br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|inprogress|yselkowitz}}<ref>PIM Setting Exporter listed under both Internet and Office, and is missing icon</ref><br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|pass|yselkowitz}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''x86 / x86_64''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Non release-blocking desktops: '''ARM''' ====<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Milestone !! Test Case !! [[Workstation]] !! [[Xfce]] !! [[LXDE]] !! MATE !! Cinnamon !! GNOME Classic<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_browser]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_terminal]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_desktop_updates]] (installation)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_login]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_audio_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_panel_basic]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_automount]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_desktop_updates]] (notification)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Beta<br />
| [[QA:Testcase_workstation_core_applications]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_error_checks]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_menus]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_panel_advanced]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_desktop_keyring]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_workstation_theming]]<br />
| {{result|none}}<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
| style="background:lightgrey;"|<br />
|-<br />
|}<br />
<references/><br />
<br />
==== Sugar (non-blocking, all arches) ====<br />
<br />
{{admon/note|Sugar test cases|The Sugar desktop differs significantly from a typical desktop, so it gets its own test cases. At present these live [http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases on the Sugar wiki].}}<br />
<br />
{| class="wikitable sortable collapsible" width=100%<br />
! Test Case !! x86 !! ARM<br />
|-<br />
| QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#1_-_SoaS_boots_to_the_.28name.29_selection_screen. SoaS boots to the (name) selection screen]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#2_-_SoaS_installed_to_hard_disk_with_liveinst_from_root_terminal.2C SoaS installed to hard disk with {{Code|liveinst}} from root terminal]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#3_-_Jabber.sugarlabs.org_should_connect_and_display_XO_.22Buddies.22 Jabber.sugarlabs.org should connect and display XO "Buddies"]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#4_-_When_a_USB_storage_device_is_inserted.2C_it_should_show_up_in_the_Frame. When a USB storage device is inserted, it should show up in the Frame]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#5_-Functions_in_My_Settings_.28Sugar_control_panel.29. Functions in My Settings (Sugar control panel)]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#6_-_Applications_in_the_Home_Screen Applications in the ''Home Screen'']<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|QA:Testcase_[http://wiki.sugarlabs.org/go/Fedora/Sugar_test_cases#7_-Sugar-desktop_installed_in_another_Desktop Sugar-desktop installed in another Desktop]<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/></onlyinclude><br />
<br />
[[Category:Desktop_validation_testing]]<br />
[[Category:Fedora_21_Beta_Test_Results|Desktop]]</div>Kkofler