Architectures/s390x/20

From FedoraProject

< Architectures | s390x(Difference between revisions)
Jump to: navigation, search
(issues found in F-20 pre-Beta 20130121)
Line 22: Line 22:
 
'''Boot status:''' OK
 
'''Boot status:''' OK
  
== issues found in F-20 pre-Beta 20130121 ==
+
== issues found in F-20 pre-Beta 20131021 ==
using anaconda-20.15-1.fc20
+
using anaconda-20.25-1.fc20
  
 
'''Installation status:''' OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
 
'''Installation status:''' OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
Line 29: Line 29:
  
 
'''Boot status:''' OK
 
'''Boot status:''' OK
 +
 +
== issues found in F-20 Beta 20131111 ==
 +
using anaconda-20.25.6-1.fc20
 +
 +
'''Installation status:''' N/A (graphical), N/A (kickstart with VNC), N/A (kickstart with text)
 +
 +
'''Boot status:''' N/A
  
 
== general anaconda/lorax/pungi/... issues ==
 
== general anaconda/lorax/pungi/... issues ==

Revision as of 09:49, 11 November 2013

Contents

Release Notes

for older notes see Architectures/s390x/19

  • none yet

Developer information

Global info

Image composes are run on F-20 with

  • pungi-3.00-1.fc20.noarch
  • lorax-20.1-1.fc20.s390x

The test composes are available from http://s390.koji.fedoraproject.org/test/

issues found in F-20 Alpha 20130923

using anaconda-20.18-1.fc20

Installation status: OK (graphical), N/A (kickstart with VNC), N/A (kickstart with text)

  • only minimal set tested, GNOME has broken deps

Boot status: OK

issues found in F-20 pre-Beta 20131021

using anaconda-20.25-1.fc20

Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)

  • both minimal set and GNOME installs fine, GNOME is killed due OOM on 1GB VM

Boot status: OK

issues found in F-20 Beta 20131111

using anaconda-20.25.6-1.fc20

Installation status: N/A (graphical), N/A (kickstart with VNC), N/A (kickstart with text)

Boot status: N/A

general anaconda/lorax/pungi/... issues