F19 Alpha Blocker Bug Review #2 Minutes

Tim Flink tflink at redhat.com
Wed Mar 20 18:08:19 UTC 2013


=================================================
#fedora-blocker-review: f19alpha-blocker-review-2
=================================================


Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.html
Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.txt
Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.log.html


Meeting summary
---------------
* Roll Call  (tflink, 16:00:13)

* Introduction  (tflink, 16:06:52)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
    (tflink, 16:07:47)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (tflink,
    16:08:18)
  * LINK:
    https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria
    (tflink, 16:08:36)
  * 11 Proposed Blockers  (tflink, 16:08:59)
  * 1 Accepted Blockers  (tflink, 16:08:59)
  * 2 Proposed Freeze Exceptions  (tflink, 16:08:59)
  * 1 Accepted Freeze Exceptions  (tflink, 16:08:59)

* (922988) virtio modules (and possibly others?) missing from installed
  system's initramfs after a Fedora 19 live (pre-Alpha TC1) install
  (tflink, 16:10:34)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922988   (tflink,
    16:10:37)
  * Proposed Blocker, anaconda, NEW  (tflink, 16:10:40)
  * AGREED: 922988 - We're not 100% clear on the impact of this bug.
    Once we have more data on its impact, we can make a decision WRT its
    impact  (tflink, 16:22:33)

* (923459) F19 pre-Alpha TC1 network installs stop at "Starting package
  installation process" (anaconda is stuck in a loop between writev and
  recvfrom)  (tflink, 16:23:56)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923459   (tflink,
    16:23:59)
  * Proposed Blocker, anaconda, NEW  (tflink, 16:24:02)
  * AGREED: 923459 - AcceptedBlocker - Violates the following F19 alpha
    release criteria for network sources "When using the dedicated
    installer images, the installer must be able to use either HTTP or
    FTP repositories (or both) as package sources."  (tflink, 16:27:42)

* (922991) dracut hook pre-pivot runs before mount hook  (tflink,
  16:27:54)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922991   (tflink,
    16:27:54)
  * Proposed Blocker, dracut, MODIFIED  (tflink, 16:27:54)
  * AGREED: 922991 - AcceptedBlocker - Violates the following F19 alpha
    release criterion: "The installer must be able to download and use
    an installer update image from an HTTP server."  (tflink, 16:31:41)

* (921896) Single quote in f19 release name breaks grub2, probably other
  stuff  (tflink, 16:32:04)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=921896   (tflink,
    16:32:07)
  * Proposed Blocker, fedora-release, NEW  (tflink, 16:32:09)
  * AGREED: 921896 - AcceptedBlocker - Violates the following F19 alpha
    release criteria as soon as the kernel is updated post-install
    "After firstboot is completed and on subsequent boots, a graphical
    install must boot to a log in screen where it is possible to log in
    to a working desktop as the user created during firstboot."
    (tflink, 16:38:42)

* (919374) /var/run not created with var_run_t leading to many boot
  avc's  (tflink, 16:39:19)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919374   (tflink,
    16:39:22)
  * Proposed Blocker, filesystem, ASSIGNED  (tflink, 16:39:25)
  * AGREED: 919374 - While this sounds like it could be a blocker, we
    want to wait until it has been reproduced by at least one other
    person before accepting it as a blocker for F19 alpha  (tflink,
    16:45:50)

* (923501) gnome-initial-setup is not visible on first boot after
  install  (tflink, 16:46:18)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923501   (tflink,
    16:46:21)
  * Proposed Blocker, gdm, NEW  (tflink, 16:46:23)
  * the criteria need to be updated to cover both firstboot and
    gnome-initial-experience  (tflink, 16:53:08)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922951 covers the
    other fail.  (adamw, 16:53:55)
  * AGREED: 923501 - AcceptedBlocker - Violates the following F19 alpha
    release criterion (substituting gnome-initial-experience for
    firstboot) A system installed with a graphical package set must boot
    to the 'firstboot' utility on the first boot after installation.
    (tflink, 16:56:51)

* (922951) gnome-initial-setup is enabled by default (and presently
  crashes)  (tflink, 16:57:23)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922951   (tflink,
    16:57:26)
  * Proposed Blocker, gnome-initial-setup, NEW  (tflink, 16:57:28)
  * AGREED: 922951 - While this seems as it it would be a blocker, we
    suspect that it has been fixed. If it isn't fixed already, will
    revisit at the next meeting  (tflink, 17:03:55)

* (922885) make sure gnome-initial-setup.service doesn't start on LiveCD
  (tflink, 17:04:14)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922885   (tflink,
    17:04:17)
  * Proposed Blocker, gnome-initial-setup, POST  (tflink, 17:04:19)
  * LINK: https://git.gnome.org/browse/gnome-initial-setup/log/
    (adamw, 17:06:15)
  * this has already been fixed, verified and will be closed  (tflink,
    17:07:46)

* (922955) GNOME Shell fails to start if gnome-screensaver is not
  installed (it is not in our default groups)  (tflink, 17:10:17)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922955   (tflink,
    17:10:20)
  * Proposed Blocker, gnome-shell, NEW  (tflink, 17:10:22)
  * this bug has been fixed and will be closed shortly  (tflink,
    17:16:50)

* (917246) gdm-simple-slave crashes on login attempt  (tflink, 17:17:05)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=917246   (tflink,
    17:17:06)
  * Proposed Blocker, gnome-shell, NEW  (tflink, 17:17:06)
  * AGREED: 917246 - AcceptedBlocker - Violates the following F19 alpha
    release criterion: "After firstboot is completed and on subsequent
    boots, a graphical install must boot to a log in screen where it is
    possible to log in to a working desktop as the user created during
    firstboot."  (tflink, 17:30:27)

* (921914) Lorax should disable dracut's 'hostonly' mode when generating
  images  (tflink, 17:30:46)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=921914   (tflink,
    17:30:49)
  * Proposed Blocker, lorax, NEW  (tflink, 17:30:52)
  * 921914 has been fixed and can be closed  (tflink, 17:36:40)

* (922335) enter not accepted in unlock screen anymore  (tflink,
  17:37:32)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922335   (tflink,
    17:37:32)
  * Proposed Freeze Exceptions, gnome-shell, NEW  (tflink, 17:37:32)
  * note that this has already been closed  (tflink, 17:40:13)

* (919935) enblend FTBFS due to doc/texinfo related issues  (tflink,
  17:43:08)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919935   (tflink,
    17:43:08)
  * Accepted Blocker, enblend, NEW  (tflink, 17:43:08)
  * this is still being worked out, leaving out kipi-plugins from the
    TC1 build is an option  (tflink, 17:46:56)

* Open Floor  (tflink, 17:50:47)
  * the next version of the blocker tracking app will be hitting fedora
    infra staging soon (hopefully this friday)  (tflink, 17:51:25)

Meeting ended at 18:02:38 UTC.




Action Items
------------





Action Items, by person
-----------------------
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* tflink (165)
* adamw (145)
* kparal (60)
* jreznik (36)
* pjones (7)
* zodbot (5)
* satellit_e (2)
* nirik (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/meetingminutes/attachments/20130320/8e9f2f9e/attachment.sig>


More information about the meetingminutes mailing list