From Fedora Project Wiki
No edit summary
(31 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{shortcut|Arch:PPC}}
{{shortcut|Arch:PPC}}
{| style="width: 50%; float: right; margin-left: 2em;"
|-
| style="border-width: 0;" | {{admon/tip | Getting Started with Fedora for Power::|
Check out our [[Architectures/PowerPC/CurrentDevelopment|current development efforts]] and join the Fedora for Power team on IRC in {{fpchat|#fedora-ppc}} on http://freenode.net
}}
|}


= PowerPC/POWER Special Interest Group =
= PowerPC/POWER Special Interest Group =
* IRC: #fedora-ppc on irc.freenode.net
* IRC: {{fpchat|#fedora-ppc}} on irc.freenode.net
* Mailing List: [http://lists.fedoraproject.org/pipermail/ppc fedora-ppc mailing list]
* Mailing List: {{fplist|ppc}}


== Members ==
== Members ==
* Adrian Reber
* Adrian Reber
* [[KarstenHopp| Karsten Hopp]] (IBM Power 730 Express Server, PowerMac G5)
* [[KarstenHopp| Karsten Hopp]] (IBM Power 730 Express Server)
* [[User:Jskala| Jiri Skala]]
* [[User:sharkcz| Dan Horák]] (IBM IntelliStation 275)
* [[User:sharkcz| Dan Horák]] (IBM IntelliStation 275)
* [[User:dwa| David Aquilina]] (release engineer)
* Mark Hamzy
* Mark Hamzy
* Brent Baude
* Brent Baude
* Gustavo Luiz Duarte
* [[User:Gustavold| Gustavo Luiz Duarte]]


== Meetings ==
== Meetings ==
* We don't schedule any IRC meetings, although starting at the Alpha phase of any release we'll try to find some time each day to discuss open issues on our #fedora-ppc channel on IRC .
* We don't schedule any IRC meetings, although starting at the Alpha phase of any release we'll try to find some time each day to discuss open issues on our {{fpchat|#fedora-ppc}} channel on IRC .
* The next 'real' [https://fedoraproject.org/wiki/Architectures/PowerPC/Meetings/FUDCon_Lawrence_2013 meeting] of the Fedora-PPC team is planned at the FUDcon 2013 in Lawrence, Kansas.  
* The last 'real' [https://fedoraproject.org/wiki/Architectures/PowerPC/Meetings/FUDCon_Lawrence_2013 meeting] of the Fedora-PPC team took place at the FUDcon 2013 in Lawrence, Kansas.
 
== Fedora 18 ==
 
Fedora 18 for Power is currently in development. The schedule is following the one for primary as closely as possible [https://fedoraproject.org/wiki/Releases/18/Schedule Fedora 18 schedule]. As usual we have architecture specific blocker tracking bugs open for Alpha, Beta and RC:


[https://bugzilla.redhat.com/show_bug.cgi?id=F18Alphappc Fedora 18 PowerPC Alpha blocker tracker]
== Current Development ==


[https://bugzilla.redhat.com/show_bug.cgi?id=F18Betappc Fedora 18 PowerPC Beta blocker tracker]
[[Architectures/PowerPC/CurrentDevelopment]] tracks our current development efforts.


[https://bugzilla.redhat.com/show_bug.cgi?id=F18Blockerppc Fedora 18 PowerPC RC blocker tracker]
Also see the [http://ppc.koji.fedoraproject.org/koji/serverstatus dashboard] for constantly updated stats on when the most recent pushes were, number of unsigned packages, most important build failures, etc.


The current nightly composes can be found here: [http://ppc.koji.fedoraproject.org/stage/f18-latest-nightly/ppc64/ F18 latest compose]
== Stable Release, GPG keys ==


=== Fedora 18 Final Checklists ===
Fedora 20 is the latest stable release of Fedora for Power. It was announced on December 19, 2013. Please see [https://fedoraproject.org/wiki/PowerPC/F20_PPC_release_announcement the release announcement] for additional details or download it from your closest [http://fedoraproject.org/get-fedora-options#2nd_arches mirror].


[http://fedoraproject.org/wiki/F18FinalPPC_checklist Fedora 18 Final Checklist]
Fedora for Power uses different GPG keys than the primary architectures. Check [https://fedoraproject.org/keys The official Fedora GPG key list] for a list of secondary arch keys.


=== Fedora 18 Beta Checklists ===
== Supported Architectures ==


[http://fedoraproject.org/wiki/F18BetaPPC_checklist Fedora 18 Beta Checklist]
Only 64bit machines (Power5 or newer) are supported, but we still provide 32bit packages. The last Fedora release with 32bit boot images was Fedora 17. Although it might be possible to install a 32bit F17 release and then update with the latest packages, this is not supported by the Fedora PPC developers anymore. Interested developers might also be able to create their own 32bit boot images for the latest Fedora release with pungi but this is also not supported by the Fedora PPC developers.


=== Fedora 18 Alpha Release notes ===
Fedora 18 and newer also includes several optimized packages for Power7 machines. These will be installed automatically if a Power7 processor is detected.


[https://fedoraproject.org/wiki/Fedora_18_Alpha_PPC_release_notes Fedora 18 Alpha PowerPC release notes]
== Previous Releases ==


=== Fedora 18 Alpha mirrors ===
You can find information about previous Fedora for Power releases at [[Architectures/PowerPC/PreviousReleases]].


[https://mirrors.fedoraproject.org/publiclist/Fedora/18-Alpha/ppc64/ Fedora 18 Alpha PowerPC mirrorlist]
== Build System & Resources ==


== Previous Fedora for Power Releases ==
===Koji===  
 
All official Fedora PowerPC packages are built by the koji build system at the
Please refer to [[Architectures/PowerPC/PreviousReleases]] for information on previous Fedora for Power releases.
 
== Fedora rebuild efforts ==
There are currently efforts ongoing to recompile all packages and prepare a F-18 release.
 
This is the current [http://ppc.koji.fedoraproject.org/compare-f18.txt status of the package rebuild]:
 
[[File:Ppc-statistics-f18.png]]
 
 
=== Rebuild problems, TODO list ===
- yaboot is only available on 32bit PPC which means we currently need some hacks for 64bit boot images. This won't change as the PPC firmware seems to be 32bit only.
In the long term yaboot is supposed to be replaced by grub2, at the moment it is still required to boot from DVD.
 
== The PowerPC koji build system ==
 
All official Fedora PowerPC packages will be built by the koji build system at the
[http://ppc.koji.fedoraproject.org/koji PowerPC koji hub]
[http://ppc.koji.fedoraproject.org/koji PowerPC koji hub]


All non-scratch packages that haven't been deleted by the garbage-collector are available at the
Everyone with a [http://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Get_a_Fedora_Account Fedora account] can do scratch builds of packages on the PowerPC koji build system. After running fedora-packager-setup from the fedora-packager rpm
[http://ppc.koji.fedoraproject.org/packages/ package storage], scratch builds can be found for a few days at the [http://ppc.koji.fedoraproject.org/scratch scratch repository]
  ppc-koji build --scratch f20 yourpkg.src.rpm
 
== Building packages on the PowerPC koji build system ==
 
Everyone with a [http://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Get_a_Fedora_Account Fedora account] can do at least scratch builds of packages on the PowerPC koji build system, [http://fedoraproject.org/wiki/Join_the_package_collection_maintainers package maintainers] who can check changes into the git repositories can build updated packages that will later on end up in the distribution.
 
=== Doing scratch builds ===
 
After running fedora-packager-setup from the fedora-packager rpm
  ppc-koji build --scratch f17 yourpkg.src.rpm
These builds will be removed from koji automatically after a while.
 
=== 'real' builds ===


'Real' builds will be pulled into the package repositories and into the install images, unless they got replaced by later versions.
Scratch builds can be found [http://ppc.koji.fedoraproject.org/scratch/ here], and will be removed from koji automatically after a while.
After running fedora-packager-setup from the fedora-packager rpm
ppc-koji build f17 "$(fedpkg giturl)"
or
fedpkg build --target=f17
(this works only when you have a symlink from ~/.koji/ppc-config to ~/.koji/config)
(currently broken: [https://bugzilla.redhat.com/show_bug.cgi?id=785776 bugzilla 787776] )


== PPC Shell access for debugging ==
For a build to end up in the final Fedora for Power distribution, that NVR must have been built on the primary Fedora koji and then pushed as an update for that release. koji-shadow is used by Fedora for Power to track both the stable (e.g. 'f20' during f20 branched development and 'f20-updates' after GA) and updates-testing tags of each release, as well as the current rawhide tag. Please feel free to find [[user:dwa|dwa]] or [[user:karsten|Kick_]] on the #fedora-ppc IRC channel if you have questions about the koji-shadow process.
[[user:dwmw2|David Woodhouse]] ([[fas:dwmw2|dwmw2]]), [[user:jwboyer|Josh Boyer]] ([[fas:jwboyer|jwb]]) or [[user:karsten|Karsten Hopp]] ([[fas:karsten|Kick_]]) may provide you access to a PPC box for build debugging purposes. Just send them an e-mail with an request and a public SSH key.


== Documentation ==
=== PPC Shell access for debugging ===
[[user:baude|Brent Baude]] ([[fas:baude|rangerpb]]) or [[user:karsten|Karsten Hopp]] ([[fas:karsten|Kick_]]) may provide you access to a PPC box for build debugging purposes. Just send them an e-mail with an request and a public SSH key.


== Work needed ==
== Bugzilla ==
 
* [[Architectures/PowerPC/GRUB2|GRUB2]]
 
=== Bugzilla ===


* [https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&rep_platform=powerpc&rep_platform=ppc64&rep_platform=ppc&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&product=Fedora&classification=Fedora List of currently open PowerPC bugs]
* [https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&rep_platform=powerpc&rep_platform=ppc64&rep_platform=ppc&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&product=Fedora&classification=Fedora List of currently open PowerPC bugs]
* [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179260 ExcludeArch for PowerPC]
* [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179260 ExcludeArch for PowerPC]
* [[Architectures/BuildIssues|Power & s390x build issues]]


=== [[Architectures/BuildIssues|Known build issues]] ===
== ppc64p7 subarch ==
* [[ppc64p7subarch]]


== Links ==
== Links ==
* [http://www.ibm.com/chips/power/ Power homepage] <BR>
* [http://lists.fedoraproject.org/pipermail/ppc fedora-ppc mailing list] <BR>
* [http://lists.fedoraproject.org/pipermail/ppc fedora-ppc mailing list] <BR>
* [[Architectures/PowerPC/PPC-hub-serverstatus|Special files and configuration on the PPC hub]]
* [http://www.ibm.com/systems/power/ Power homepage] <BR>
* [https://www.ibm.com/developerworks/community/wikis/home/wiki/W51a7ffcf4dfd_4b40_9d82_446ebc23c550?lang=en The PowerLinux Community Wiki] <BR>
* [http://www.power.org/ Power.org] <BR>
* [http://www.power.org/ Power.org] <BR>
* [http://www.terrasoftsolutions.com/support/ YellowDogLinux support pages] <BR>
* [http://www.powerdeveloper.org/ powerdeveloper.org]
* [http://www.powerdeveloper.org/ powerdeveloper.org]
* [http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaae/lcon_Installing_Linux_on_System_p5.htm Installation docs] for IBM Power hardware <BR>




[[Category:Arch-specific SIGs]][[Category:SIGs]]
[[Category:Arch-specific SIGs]][[Category:SIGs]]
[[Category:Fedora special-interest groups|PowerPC]]
[[Category:Fedora special-interest groups|PowerPC]]

Revision as of 14:37, 26 February 2015

Shortcut:
Arch:PPC
Idea.png
Getting Started with Fedora for Power::
Check out our current development efforts and join the Fedora for Power team on IRC in #fedora-ppc[?] on http://freenode.net

PowerPC/POWER Special Interest Group

Members

Meetings

  • We don't schedule any IRC meetings, although starting at the Alpha phase of any release we'll try to find some time each day to discuss open issues on our #fedora-ppc[?] channel on IRC .
  • The last 'real' meeting of the Fedora-PPC team took place at the FUDcon 2013 in Lawrence, Kansas.

Current Development

Architectures/PowerPC/CurrentDevelopment tracks our current development efforts.

Also see the dashboard for constantly updated stats on when the most recent pushes were, number of unsigned packages, most important build failures, etc.

Stable Release, GPG keys

Fedora 20 is the latest stable release of Fedora for Power. It was announced on December 19, 2013. Please see the release announcement for additional details or download it from your closest mirror.

Fedora for Power uses different GPG keys than the primary architectures. Check The official Fedora GPG key list for a list of secondary arch keys.

Supported Architectures

Only 64bit machines (Power5 or newer) are supported, but we still provide 32bit packages. The last Fedora release with 32bit boot images was Fedora 17. Although it might be possible to install a 32bit F17 release and then update with the latest packages, this is not supported by the Fedora PPC developers anymore. Interested developers might also be able to create their own 32bit boot images for the latest Fedora release with pungi but this is also not supported by the Fedora PPC developers.

Fedora 18 and newer also includes several optimized packages for Power7 machines. These will be installed automatically if a Power7 processor is detected.

Previous Releases

You can find information about previous Fedora for Power releases at Architectures/PowerPC/PreviousReleases.

Build System & Resources

Koji

All official Fedora PowerPC packages are built by the koji build system at the PowerPC koji hub

Everyone with a Fedora account can do scratch builds of packages on the PowerPC koji build system. After running fedora-packager-setup from the fedora-packager rpm

ppc-koji build --scratch f20 yourpkg.src.rpm

Scratch builds can be found here, and will be removed from koji automatically after a while.

For a build to end up in the final Fedora for Power distribution, that NVR must have been built on the primary Fedora koji and then pushed as an update for that release. koji-shadow is used by Fedora for Power to track both the stable (e.g. 'f20' during f20 branched development and 'f20-updates' after GA) and updates-testing tags of each release, as well as the current rawhide tag. Please feel free to find dwa or Kick_ on the #fedora-ppc IRC channel if you have questions about the koji-shadow process.

PPC Shell access for debugging

Brent Baude (rangerpb) or Karsten Hopp (Kick_) may provide you access to a PPC box for build debugging purposes. Just send them an e-mail with an request and a public SSH key.

Bugzilla


Links