17:30:53 <roshi> #startmeeting F22-blocker-review
17:30:53 <zodbot> Meeting started Mon Feb 16 17:30:53 2015 UTC.  The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:30:53 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:30:55 <roshi> #meetingname F22-blocker-review
17:30:55 <zodbot> The meeting name has been set to 'f22-blocker-review'
17:30:58 <roshi> #topic Roll Call
17:31:01 * pschindl is here
17:31:06 <danofsatx> we went nowheres
17:31:35 * Corey84 here
17:31:52 * kparal is here
17:32:20 <roshi> is the topic showing up not Roll Call for others right now?
17:32:35 <danofsatx> I see it
17:32:52 <Corey84> seeing it here too
17:32:55 <roshi> hrm...
17:32:57 <Corey84> .fas Corey84
17:32:59 <zodbot> Corey84: corey84 'Corey84' <sheldon.corey@gmail.com>
17:32:59 <danofsatx> Top of my window says "Roll Call (Meeting topic: F22-blocker-review)
17:33:04 <roshi> I'll just ignore it then
17:33:14 <roshi> irssi just told me:
17:33:21 <roshi> verne.freenode.net changed the topic of #fedora-blocker-review to: Fedora Blocker  Bugs Review Channel - Meetings on Monday @ 17:00 UTC -  http://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
17:33:27 <Corey84> not in channel title in hexchat but /topic is
17:33:33 <kparal> I don't see #Roll call topic
17:33:44 <roshi> eh, w/e - we'll roll with it
17:33:55 <roshi> so we have 3/0/2 proposed blockers to look at
17:33:59 <Corey84> just lost it but yeah w/e
17:34:06 <roshi> if that notation makes sense :)
17:34:19 * danofsatx unnerstoot
17:34:26 <Corey84> same
17:34:29 <Corey84> same
17:34:31 <roshi> #topic Introduction
17:34:32 <roshi> Why are we here?
17:34:32 <roshi> #info Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs.
17:34:36 <roshi> #info We'll be following the process outlined at:
17:34:38 <roshi> #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
17:34:41 <roshi> #info The bugs up for review today are available at:
17:34:43 <roshi> #link http://qa.fedoraproject.org/blockerbugs/current
17:34:46 <roshi> #info The criteria for release blocking bugs can be found at:
17:34:48 <roshi> #link https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria
17:34:51 <roshi> #link https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria
17:34:54 <roshi> #link https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
17:35:08 <roshi> onto the Alphas!
17:35:09 <roshi> #topic (1192702) ImportError: cannot import name storageInitialize
17:35:12 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1192702
17:35:15 <roshi> #info Proposed Blocker, anaconda, MODIFIED
17:35:31 <roshi> +1
17:35:41 <roshi> this is the showstopper keeping us from having a TC
17:36:21 <Corey84> +1
17:36:32 <pschindl> +1
17:36:34 <danofsatx> +1
17:36:44 <Corey84> seen this at least once myself not coo
17:36:46 <roshi> under the "Installer must run" criteria: The installer must run when launched normally from the release-blocking images
17:36:48 <adamw> +1
17:36:57 <kparal> +1
17:37:28 <roshi> proposed #agreed - 1192702 - AcceptedBlocker Alpha - This bug is a clear violation of the Alpha criterion: "The installer must run when launched normally from the release-blocking images"
17:38:13 <danofsatx> +1
17:38:17 <danofsatx> erm, ack
17:38:19 <Corey84> ack
17:38:22 <pschindl> ack
17:38:32 <kparal> ack
17:39:16 <roshi> #agreed - 1192702 - AcceptedBlocker Alpha - This bug is a clear violation of the Alpha criterion: "The installer must run when launched normally from the release-blocking images"
17:39:35 <roshi> danofsatx: you running secretary duty today?
17:39:45 <danofsatx> no, no time
17:40:01 <roshi> I thought as much :) any volunteers?
17:40:10 <adamw> sure, i got it
17:40:15 <roshi> thanks :)
17:40:15 <roshi> #topic (1190610) imsettings NVR is lower in rawhide/F22
17:40:16 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1190610
17:40:16 <roshi> #info Proposed Blocker, imsettings, NEW
17:40:34 <kparal> haven't I seen this before?
17:40:45 <roshi> yeah, this just hasn'
17:40:51 <roshi> t been cleared of the tracking bug
17:40:59 <kparal> I see
17:41:00 <danofsatx> we rejected this one last week. not sure why it's still here....
17:41:15 <kparal> does not have RejectedBlocker in whiteboard
17:41:15 <roshi> there - fixed
17:41:30 * danofsatx probably missed something in the secretary duties
17:41:35 <kparal> roshi: not yet :)
17:41:43 <roshi> is too :p
17:41:56 <kparal> ok, now
17:42:02 <roshi> you, um, reloaded it ... wrong :p
17:42:20 <roshi> alright next one
17:42:20 <roshi> #topic (1191171) "Could not sync environment to dbus." (startkde)
17:42:20 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1191171
17:42:20 <roshi> #info Proposed Blocker, plasma-workspace, NEW
17:43:34 <roshi> +1
17:43:51 <adamw> as described, yeah, +1
17:44:02 <adamw> haven't reproduced it yet
17:44:15 <pschindl> +1
17:44:26 <kparal> +1, but we should reproduce
17:45:18 <roshi> proposed #agreed - 1191171 - AcceptedBlocker Alpha - This bug is a clear violation of the Alpha criterion: "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility."
17:45:22 <danofsatx> +1
17:45:24 <danofsatx> ack
17:45:40 <adamw> ack
17:45:46 <Corey84> ack, although no h/w to confirm /test on
17:45:54 <roshi> #agreed - 1191171 - AcceptedBlocker Alpha - This bug is a clear violation of the Alpha criterion: "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility."
17:46:11 <danofsatx> ack
17:46:14 <roshi> someone want to volunteer to repro?
17:46:23 <kparal> ack
17:47:14 <danofsatx> this is normally my domain, I can't commit to anything at the moment.
17:47:26 <roshi> no worries
17:47:32 <roshi> I can try it in a VM
17:47:45 <roshi> #action roshi to test 1191171 in a VM
17:48:11 <roshi> onto the final proposals
17:48:12 <roshi> #topic (1192259) Anaconda text install doesn't update spoke status
17:48:15 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1192259
17:48:17 <roshi> #info Proposed Blocker, anaconda, NEW
17:48:35 <roshi> +1 from me
17:48:38 <adamw> 2015-02-16 branched KDE nightlies: https://kojipkgs.fedoraproject.org/work/tasks/9746/8949746/Fedora-Live-KDE-x86_64-22-20150216.iso , https://kojipkgs.fedoraproject.org/work/tasks/9744/8949744/Fedora-Live-KDE-i686-22-20150216.iso
17:48:54 <danofsatx> +1
17:49:01 <Corey84> +1 had this issue last week
17:49:01 <roshi> this bug makes it so you can't finish the installation if an error presents itself sometime during config
17:49:21 <adamw> +1 for final at least, yeah
17:49:24 <Corey84> its in ..../pyanaconda/....
17:49:34 <danofsatx> why final, though?
17:49:45 <Corey84> time to fix?
17:49:53 <kparal> roshi: does this affect gui as well?
17:50:06 <roshi> well, for alpha, if you set it up correctly it works, so just start the install over
17:50:19 <roshi> kparal: I don't think so, but I haven't tested it yet
17:50:41 <kparal> +1 anyway
17:50:41 <roshi> iirc, the update spoke logic is different for gui and tui
17:50:45 <Corey84> did for me
17:51:10 <Corey84> ill try againa nd ammed report
17:51:42 <roshi> proposed #agreed - 1192259 - AcceptedBlocker Final - This bug is a clear violation of the Final criterion: "The installer must be able to complete an installation using all supported interfaces."
17:51:48 <danofsatx> ack
17:51:48 <roshi> thanks Corey84
17:51:51 <adamw> ack
17:52:08 <danofsatx> next bug is another danofsatx fail :(
17:52:22 <roshi> #agreed - 1192259 - AcceptedBlocker Final - This bug is a clear violation of the Final criterion: "The installer must be able to complete an installation using all supported interfaces."
17:52:30 <roshi> oh?
17:52:31 <roshi> #topic (1190377) SELinux is preventing polkitd from 'read' accesses on the lnk_file localtime.
17:52:34 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1190377
17:52:37 <roshi> #info Proposed Blocker, selinux-policy, NEW
17:52:59 <danofsatx> https://bugzilla.redhat.com/show_bug.cgi?id=1190377#c2
17:53:20 <kparal> seems to be already accepted
17:53:24 <roshi> yeah
17:53:26 <kparal> but a wrong keyword in whiteboard
17:53:28 <roshi> just updated the whiteboard
17:53:29 <kparal> extra _
17:53:55 <roshi> well, that's it folks :)
17:54:03 <roshi> #topic Open Floor
17:54:17 <danofsatx> .fire danofsatx for incompetence
17:54:17 <zodbot> adamw fires danofsatx for incompetence
17:55:07 <adamw> AND STAY FIRED
17:55:15 * roshi sets the fuse
17:55:16 <danofsatx> roger. will do.
17:55:30 <roshi> s/FIRED/FIRED UP!!/
17:55:57 <adamw> we're done? yay
17:55:59 <roshi> 3...
17:56:00 * adamw loving these short ones
17:56:00 <roshi> yeah
17:56:09 <kparal> after a recent discussion in our office, I should be focused on automation rather than testing if possible during F22 cycle. is it going to cause issues if I don't attend these meetings regularly?
17:56:11 * adamw looks at current accepted
17:56:23 <adamw> kparal: don't think so, we have had decent turnouts recently
17:56:31 <kparal> I can always fall back to testing if there is a crisis, or as aback up for pschindl for example
17:56:34 <roshi> should be fine, I'd think
17:56:49 <kparal> *backup
17:56:50 <kparal> ok
17:57:11 <roshi> once we have a tc I'll be moving back to full time testing, instead of tooling and whatnot I've been working on
17:57:41 <roshi> 2...
17:57:48 <roshi> anybody have anything else?
17:57:51 <adamw> not really
17:57:56 <kparal> I'll try to be lurking during these meetings anyways, just in case
17:57:59 <kparal> nothing else here
17:58:00 <adamw> still trying to grok whether the unicode bug is still valid
17:58:24 <roshi> unicode isn't going anywhere, no matter how many times you call it a bug :p
17:58:27 * roshi ducks
17:58:42 <roshi> 1...
17:58:49 <roshi> thanks for coming folks!
17:58:56 <roshi> #endmeeting