<@adamwill:fedora.im>
16:00:01
!startmeeting F40-blocker-review
<@meetbot:fedora.im>
16:00:02
Meeting started at 2024-04-15 16:00:01 UTC
<@meetbot:fedora.im>
16:00:02
The Meeting name is 'F40-blocker-review'
<@adamwill:fedora.im>
16:00:04
!topic Roll Call
<@adamwill:fedora.im>
16:00:07
!topic Introduction
<@adamwill:fedora.im>
16:00:14
!topic Roll Call
<@adamwill:fedora.im>
16:00:18
oops, went too far. :D
<@adamwill:fedora.im>
16:00:24
morning folks, who's here for blocker review fun?
<@tablepc:matrix.org>
16:00:26
!Hi
<@salimma:fedora.im>
16:00:31
back to roll call?
<@nhanlon:beeper.com>
16:00:40
!hi
<@davdunc:fedora.im>
16:00:41
.hi
<@zodbot:fedora.im>
16:00:42
Neil Hanlon (neil) - he / him / his
<@salimma:fedora.im>
16:00:43
adamw: you should probably change the topic back first
<@tablepc:matrix.org>
16:01:02
I've tried Screencast several times with different app's and it works.
<@salimma:fedora.im>
16:01:20
!topic Roll Call
<@salimma:fedora.im>
16:01:23
!hi
<@zodbot:fedora.im>
16:01:24
Michel Lind (salimma) - he / him / his
<@nielsenb:fedora.im>
16:01:32
!hi
<@zodbot:fedora.im>
16:01:35
Brandon Nielsen (nielsenb)
<@adamwill:fedora.im>
16:01:52
Michel Lind 🎩: i already did it
<@adamwill:fedora.im>
16:01:54
but hey, can't hurt
<@tablepc:matrix.org>
16:01:55
!Hi
<@tablepc:matrix.org>
16:02:05
Do I need to type it agasin
<@salimma:fedora.im>
16:02:11
doh, I'm blind, didn't see the third one == the first one
<@salimma:fedora.im>
16:02:21
I think it's case sensitive
<@geraldosimiao:matrix.org>
16:02:35
!hi
<@zodbot:fedora.im>
16:02:37
Geraldo S. Simião Kutz (geraldosimiao) - he / him / his
<@salimma:fedora.im>
16:02:41
starts with ! now ;) (tripped me up the first few months)
<@coremodule:fedora.im>
16:02:54
!hi
<@zodbot:fedora.im>
16:02:55
Geoffrey Marr (coremodule)
<@davdunc:fedora.im>
16:02:56
hah.
<@davdunc:fedora.im>
16:02:59
!hi
<@zodbot:fedora.im>
16:03:01
David Duncan (davdunc) - he / him / his
<@davdunc:fedora.im>
16:03:12
Thank you!
<@tablepc:matrix.org>
16:03:36
How come zodbot doesn't see me?
<@adamwill:fedora.im>
16:03:46
try a lower-case h
<@adamwill:fedora.im>
16:03:47
!hi
<@zodbot:fedora.im>
16:03:49
Adam Williamson (adamwill) - he / him / his
<@conan_kudo:matrix.org>
16:03:57
!hi
<@zodbot:fedora.im>
16:03:59
Neal Gompa (ngompa) - he / him / his
<@tablepc:matrix.org>
16:04:03
!hi
<@zodbot:fedora.im>
16:04:05
No Fedora Accounts users have the @tablepc:matrix.org Matrix Account defined
<@adamwill:fedora.im>
16:04:16
ah, there, you need to tell FAS about your matrix account, i guess
<@salimma:fedora.im>
16:04:20
your matrix account must be listed on accounts.fedoraproject.org
<@decathorpe:fedora.im>
16:04:47
!hi
<@zodbot:fedora.im>
16:04:49
Fabio Valentini (decathorpe) - he / him / his
<@adamwill:fedora.im>
16:04:52
hi fabio
<@adamwill:fedora.im>
16:04:56
okey dokey, let's get some boilerplate
<@adamwill:fedora.im>
16:05:06
!topic Introduction
<@adamwill:fedora.im>
16:05:10
Why are we here?
<@adamwill:fedora.im>
16:05:13
!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.
<@adamwill:fedora.im>
16:05:16
!info We'll be following the process outlined at:
<@adamwill:fedora.im>
16:05:18
!link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
<@adamwill:fedora.im>
16:05:20
!info The bugs up for review today are available at:
<@adamwill:fedora.im>
16:05:22
!link http://qa.fedoraproject.org/blockerbugs/current
<@adamwill:fedora.im>
16:05:26
!info The criteria for release blocking bugs can be found at:
<@adamwill:fedora.im>
16:05:29
!link https://fedoraproject.org/wiki/Basic_Release_Criteria
<@adamwill:fedora.im>
16:05:31
!link https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria
<@adamwill:fedora.im>
16:05:36
!link https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria
<@adamwill:fedora.im>
16:05:45
!info for Fedora 40 Final, we have:
<@adamwill:fedora.im>
16:05:48
!info 2 Proposed Blockers
<@adamwill:fedora.im>
16:05:51
!info 1 Accepted Previous Release Blockers
<@adamwill:fedora.im>
16:05:53
!info 4 Proposed Freeze Exceptions
<@adamwill:fedora.im>
16:05:56
!info 8 Accepted Freeze Exceptions
<@adamwill:fedora.im>
16:06:00
who wants to secretarialize?
<@coremodule:fedora.im>
16:06:56
I'll do it.
<@adamwill:fedora.im>
16:07:20
!info coremodule will secretarialize
<@adamwill:fedora.im>
16:07:27
alrighty, let's get going with
<@adamwill:fedora.im>
16:07:30
!topic Proposed Final blockers
<@adamwill:fedora.im>
16:07:36
!topic (2275099) Recording the screencast does not work properly.
<@adamwill:fedora.im>
16:07:39
!link https://bugzilla.redhat.com/show_bug.cgi?id=2275099
<@zodbot:fedora.im>
16:07:39
neil gave a cookie to coremodule. They now have 69 cookies, 2 of which were obtained in the Fedora 39 release cycle
<@adamwill:fedora.im>
16:07:42
!link https://pagure.io/fedora-qa/blocker-review/issue/1596
<@adamwill:fedora.im>
16:07:44
!info Proposed Blocker, gnome-shell, NEW
<@adamwill:fedora.im>
16:07:46
!info Ticket vote: FinalBlocker (+1,0,-0) (+lruzicka)
<@adamwill:fedora.im>
16:07:53
so, this seems to be a developing situation...
<@adamwill:fedora.im>
16:08:02
i've tried four times on two systems and haven't reproduced yet, how's everyone else doing?
<@nielsenb:fedora.im>
16:09:01
I can't make it happen.
<@nielsenb:fedora.im>
16:09:14
I guess I haven't tried a VM.
<@geraldosimiao:matrix.org>
16:09:17
At rc 1.13 I have the same results Lukas have. At 1.14 it crashed
<@salimma:fedora.im>
16:09:18
this is the one that tablepc said worked for them too I think
<@tablepc:matrix.org>
16:09:20
I've tried Screencast several times with different applications and it always works.
<@frantisekz:fedora.im>
16:09:49
!hi
<@zodbot:fedora.im>
16:09:50
František Zatloukal (frantisekz)
<@adamwill:fedora.im>
16:11:01
hum, the only major difference between 1.13 and 1.14 here should be mesa and the kernel...
<@geraldosimiao:matrix.org>
16:11:56
So mesa then?
<@frantisekz:fedora.im>
16:12:02
seems like the affected systems are all vms?
<@tablepc:matrix.org>
16:12:06
Same test machine I always test on bare metal
<@frantisekz:fedora.im>
16:12:11
if i am not missing anything
<@adamwill:fedora.im>
16:13:52
not sure about lruzicka's initial report
<@frantisekz:fedora.im>
16:14:01
@lruzicka
<@adamwill:fedora.im>
16:14:19
let me try in a VM
<@salimma:fedora.im>
16:14:28
lruzicka:
<@adamwill:fedora.im>
16:15:24
eh, have to download 1.14 first
<@nielsenb:fedora.im>
16:15:25
My VM is installing, just did another bare metal test with everything updated and it was fine
<@geraldosimiao:matrix.org>
16:15:28
Yeah mine is vm
<@adamwill:fedora.im>
16:15:30
on the whole i'm -1 or punt on this, i think
<@frantisekz:fedora.im>
16:16:04
can we cycle back to this at the end of the meeting maybe?
<@frantisekz:fedora.im>
16:16:19
we'll have more vm results by then?
<@salimma:fedora.im>
16:16:27
yeah, this close to the release if there's no clear repro or it only affects a few systems... but right maybe if someone want to test now and report at the end, we should vote then
<@adamwill:fedora.im>
16:16:47
sure...
<@adamwill:fedora.im>
16:17:00
!info we will table this bug for more testing during the meeting and proceed for now
<@adamwill:fedora.im>
16:17:06
!topic (2274830) Reinstate network service for Fedora 40
<@adamwill:fedora.im>
16:17:09
!link https://bugzilla.redhat.com/show_bug.cgi?id=2274830
<@adamwill:fedora.im>
16:17:11
!link https://pagure.io/fedora-qa/blocker-review/issue/1593
<@adamwill:fedora.im>
16:17:14
!info Proposed Blocker, initscripts, NEW
<@adamwill:fedora.im>
16:17:17
!info Ticket vote: FinalBlocker (+2,0,-0) (+geraldosimiao, +ngompa)
<@adamwill:fedora.im>
16:17:19
no votes!
<@adamwill:fedora.im>
16:17:21
nobody vote.
<@frantisekz:fedora.im>
16:17:25
😁😁
<@frantisekz:fedora.im>
16:17:32
+fesco
<@adamwill:fedora.im>
16:17:41
!info this bug is proposed as a blocker for FESCo to considering nominating it, it does not qualify as a blocker under the release criteria, so we will not vote on it
<@nielsenb:fedora.im>
16:17:42
He's suppressing our votes! Vote! Vote!
<@frantisekz:fedora.im>
16:18:01
democracy!!!
<@adamwill:fedora.im>
16:18:10
whew, it's a good thing I asked the Democratic National Committee for this phone number
<@adamwill:fedora.im>
16:18:12
...i mean uh
<@nielsenb:fedora.im>
16:18:39
What do we want? Suffrage! When do we want it? Not for this bug!
<@salimma:fedora.im>
16:18:47
I know we're not voting for this but... it worries me how we almost did not notice
<@adamwill:fedora.im>
16:19:04
i kinda agree, but otoh, there's just a whole lot of *stuff* in fedora, if you hadn't noticed :P
<@salimma:fedora.im>
16:19:09
adamw: would having a test instance of openqa on the beta release help?
<@adamwill:fedora.im>
16:19:34
openqa already tests the beta
<@salimma:fedora.im>
16:19:37
similar to how my company dogfoods ELN at work so we are not blindsided if some packages disappear
<@adamwill:fedora.im>
16:19:38
and all f40 nightlies
<@adamwill:fedora.im>
16:19:41
and all critical path updates
<@adamwill:fedora.im>
16:19:50
it is not set to fail if a random init.d service disappears
<@salimma:fedora.im>
16:19:53
oh no, I mean, run one instance of openqa itself on beta so you know if one of your dependencies is yanked
<@tablepc:matrix.org>
16:19:55
No opinion on the mmatter
<@adamwill:fedora.im>
16:20:00
heck, network-scripts isn't in a default install, so openqa hasn't seen it for years
<@adamwill:fedora.im>
16:20:05
oh, i see
<@salimma:fedora.im>
16:20:08
yeap
<@salimma:fedora.im>
16:20:25
like "are all the infra we run on fedora installable on the upcoming fedora"
<@adamwill:fedora.im>
16:20:33
i mean, in theory, sure, in practice, i don't really have time
<@adamwill:fedora.im>
16:20:46
openqa is honestly already ahead of the rest of infra, tbh
<@nielsenb:fedora.im>
16:20:49
I feel like it's the kind of thing you would only notice if you had a special need
<@adamwill:fedora.im>
16:20:57
openqa stg is usually one of the first things to go to a new release
<@nielsenb:fedora.im>
16:20:59
And if you have a special need, you probably aren't running prerelease
<@salimma:fedora.im>
16:21:11
adamw: if you point me to the ansible playbooks for deploying openqa maybe I can cook up something
<@salimma:fedora.im>
16:21:35
(also short on time, but this is one of the issues that bugs me so maybe I'll scratch that itch)
<@adamwill:fedora.im>
16:21:56
Michel Lind 🎩: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openqa , https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/openqa.yml , https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/openqa-workers.yml
<@adamwill:fedora.im>
16:22:00
it is a fairly complex deployment, unfortunately
<@adamwill:fedora.im>
16:22:18
https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/openqa-onebox-test.yml is a single system playbook which we used for testing some stuff a while back, it should still mostly work
<@salimma:fedora.im>
16:22:20
thanks! yeah I am thinking of parsing it, grabbing the packages, then try installing in mock and flag if it fails
<@decathorpe:fedora.im>
16:22:57
either way, I think a change like this should *at least* have been coordinated with maintainers of dependent packages (i.e. libteam?), or even have been a full Change Proposal. it was *mentioned* in previous change proposals, but always as something that will happen *later*
<@adamwill:fedora.im>
16:23:06
yeah
<@adamwill:fedora.im>
16:23:19
anyhow, not really ours to vote on, so...let's move on, if there's nothing else?
<@salimma:fedora.im>
16:24:10
yeah we should definitely bring this up at FESCo later today
<@adamwill:fedora.im>
16:27:27
alrgihty
<@adamwill:fedora.im>
16:27:38
!topic Proposed Final freeze exceptions
<@adamwill:fedora.im>
16:27:41
!topic (2274740) fdo-client-linuxapp.service is not enabled by default on IoT
<@adamwill:fedora.im>
16:27:44
!link https://bugzilla.redhat.com/show_bug.cgi?id=2274740
<@adamwill:fedora.im>
16:27:47
!link https://pagure.io/fedora-qa/blocker-review/issue/1591
<@adamwill:fedora.im>
16:27:49
!info Proposed Freeze Exceptions, fedora-release, ON_QA
<@adamwill:fedora.im>
16:27:51
!info Ticket vote: FinalFreezeException (+4,0,-0) (+adamwill, +geraldosimiao, +salimma, +pbrobinson)
<@adamwill:fedora.im>
16:28:05
so i was kinda holding this one for it to go through the policy requirements for a new default service
<@tablepc:matrix.org>
16:30:10
I don't test IOT
<@nirik:matrix.scrye.com>
16:30:34
I don't know if there's a way for iot to pull this without another RC... but in any case a FE seems reasonable.
<@adamwill:fedora.im>
16:31:27
I think if we push it stable, IoT can nominate a compose done tomorrow or wednesday for release
<@nielsenb:fedora.im>
16:32:52
FinalFE +1
<@nielsenb:fedora.im>
16:32:56
Though it already has the votes?
<@adamwill:fedora.im>
16:33:00
ok, Stephen Gallagher asked questions at https://src.fedoraproject.org/rpms/fedora-release/pull-request/329#comment-194357 and zbyszek answered at https://src.fedoraproject.org/rpms/fedora-release/pull-request/329#comment-194593
<@adamwill:fedora.im>
16:33:04
given the answers, I'm +1
<@adamwill:fedora.im>
16:33:15
Brandon Nielsen: yeah, i wanted to make sure the policy was complied with before approving this
<@frantisekz:fedora.im>
16:33:26
anyhow, +1 FE
<@adamwill:fedora.im>
16:34:32
proposed !agreed 2274740 - AcceptedFreezeException (Final) - this is accepted as an FE as it' affects the intended configuration of the IoT edition and cannot be fixed with a post-release update
<@adamwill:fedora.im>
16:34:40
proposed !agreed 2274740 - AcceptedFreezeException (Final) - this is accepted as an FE as it affects the intended configuration of the IoT edition and cannot be fixed with a post-release update
<@nielsenb:fedora.im>
16:35:07
ack
<@frantisekz:fedora.im>
16:35:10
ack
<@nhanlon:beeper.com>
16:35:27
ack
<@umu:catnip.ee>
16:35:39
ack
<@adamwill:fedora.im>
16:35:48
!agreed 2274740 - AcceptedFreezeException (Final) - this is accepted as an FE as it affects the intended configuration of the IoT edition and cannot be fixed with a post-release update
<@adamwill:fedora.im>
16:36:04
!topic (2263334) F40FailsToInstall: network-scripts-teamd
<@adamwill:fedora.im>
16:36:06
!link https://bugzilla.redhat.com/show_bug.cgi?id=2263334
<@adamwill:fedora.im>
16:36:08
!link https://pagure.io/fedora-qa/blocker-review/issue/1592
<@adamwill:fedora.im>
16:36:11
!info Proposed Freeze Exceptions, libteam, ON_QA, depends on other bugs
<@adamwill:fedora.im>
16:36:13
!info Ticket vote: FinalFreezeException (+1,0,-0) (+geraldosimiao)
<@adamwill:fedora.im>
16:36:30
this kinda is related to the network service one (it's how we found it), but regardless, i think we should give this an FE, fixing FTI is good
<@nirik:matrix.scrye.com>
16:37:03
+1 FE
<@nielsenb:fedora.im>
16:37:09
I agree
<@nielsenb:fedora.im>
16:37:11
FinalFE +1
<@salimma:fedora.im>
16:37:17
q: if network-scripts come back, we still don't want to restore network-scripts-teamd right?
<@nhanlon:beeper.com>
16:37:19
+1 FE
<@salimma:fedora.im>
16:37:40
since we don't really need it, and I suspect network-scripts will eventually go away (but with a proper Change Proposal ideally)
<@nirik:matrix.scrye.com>
16:37:57
probibly not? although it could come back and be retired when network-scripts is.
<@salimma:fedora.im>
16:38:07
very low-risk fix, this one - it's literally the same build with one subpackage removed
<@salimma:fedora.im>
16:38:36
right. if the upstream developer wants to re-maintain the package I'll leave that decision up to him (pending what fesco decides)
<@adamwill:fedora.im>
16:38:51
i'd say that's up to the maintainer and upstream
<@decathorpe:fedora.im>
16:39:48
have they fixed their account email address so they'll get future fedora emails? :)
<@salimma:fedora.im>
16:41:10
idk. they were in touch with Carlos it seems, so I asked him in devel to follow up
<@adamwill:fedora.im>
16:41:31
proposed !agreed 2263334 - AcceptedFreezeException (Final) - this is accepted on the general principle that we accept clean FTI fixes to ease the upgrade process
<@geraldosimiao:matrix.org>
16:42:01
Ack
<@frantisekz:fedora.im>
16:42:07
ack
<@nielsenb:fedora.im>
16:42:16
ack
<@adamwill:fedora.im>
16:42:46
!agreed 2263334 - AcceptedFreezeException (Final) - this is accepted on the general principle that we accept clean FTI fixes to ease the upgrade process
<@nhanlon:beeper.com>
16:42:48
ack
<@adamwill:fedora.im>
16:43:10
!topic (2274724) [abrt] nautilus: ptr_array_free(): nautilus killed by SIGABRT
<@adamwill:fedora.im>
16:43:14
!link https://bugzilla.redhat.com/show_bug.cgi?id=2274724
<@adamwill:fedora.im>
16:43:16
!link https://pagure.io/fedora-qa/blocker-review/issue/1590
<@adamwill:fedora.im>
16:43:18
!info Proposed Freeze Exceptions, nautilus, VERIFIED
<@adamwill:fedora.im>
16:43:21
!info Ticket vote: FinalBlocker (+0,0,-3) (-geraldosimiao, -adamwill, -catanzaro)
<@adamwill:fedora.im>
16:43:23
!info Ticket vote: FinalFreezeException (+3,0,-0) (+adamwill, +geraldosimiao, +kparal)
<@adamwill:fedora.im>
16:43:31
did i vote +1 on this? huh.
<@adamwill:fedora.im>
16:43:53
it actually feels a bit borderline to me, not sure how much file+folder compression people are doing on live images. but otoh, fix looks clear and it's been well tested
<@nirik:matrix.scrye.com>
16:44:10
I think it's ok for a FE, I don't think it's a blocker.
<@nielsenb:fedora.im>
16:44:35
I feel like it could be pretty easily fixed post release
<@adamwill:fedora.im>
16:44:57
i meant borderline FE
<@adamwill:fedora.im>
16:45:30
just because fixing it 0-day is probably fine. but ehh, maybe someone wants to compress things on the live desktop. i'm probably like 0.2. :D
<@nirik:matrix.scrye.com>
16:45:33
true... not too many people would be doing this on a live.
<@adamwill:fedora.im>
16:45:37
just because fixing it 0-day is probably fine. but ehh, maybe someone wants to compress things on the live desktop. i'm probably like +0.2. :D
<@nielsenb:fedora.im>
16:46:25
FinalFE +0
<@tablepc:matrix.org>
16:46:32
I just tried the compress twice and it worked fine.
<@nielsenb:fedora.im>
16:46:32
The fix is out there and tested
<@nielsenb:fedora.im>
16:46:37
But I don't see the point of pushing it really
<@tablepc:matrix.org>
16:46:56
Yes I did the update
<@salimma:fedora.im>
16:48:05
oh, speaking of upgrade process, right now the removed network-scripts-teamd is not properly obsoleted by a remaining subpackage. should I fix it real quick? or just leave it since I suspect it's not widely installed anyway, and maybe people who do have it installed should take manual action if they really need it
<@adamwill:fedora.im>
16:48:19
by policy it should be obsoleted
<@adamwill:fedora.im>
16:48:27
i would probably do it if it were me
<@adamwill:fedora.im>
16:48:37
but, well
<@nielsenb:fedora.im>
16:48:41
Do it
<@adamwill:fedora.im>
16:48:52
unless you plan to put it back if we put network-scripts back
<@salimma:fedora.im>
16:49:00
ok, let me pause the auto push to stable and fix this real quick
<@salimma:fedora.im>
16:49:03
we don't need to revote right?
<@nirik:matrix.scrye.com>
16:49:10
might wait to hear if they want it back or not
<@zodbot:fedora.im>
16:49:18
salimma has already given cookies to adamwill during the F39 timeframe
<@salimma:fedora.im>
16:49:32
yeah, so disable the auto push for now so it does not go to stable
<@adamwill:fedora.im>
16:50:51
no need to revote, no
<@adamwill:fedora.im>
16:51:08
okay, so for this one...
<@adamwill:fedora.im>
16:51:15
ehh, let's just accept it to move things along...:P
<@adamwill:fedora.im>
16:51:56
proposed !agreed 2274724 - AcceptedFreezeException (Final) - this is accepted as a crasher bug people could at least potentially run into on the Workstation live image. The fix is targeted and well tested.
<@nielsenb:fedora.im>
16:52:10
ack
<@geraldosimiao:matrix.org>
16:52:17
Ack
<@nhanlon:beeper.com>
16:52:32
ack
<@adamwill:fedora.im>
16:54:20
!agreed 2274724 - AcceptedFreezeException (Final) - this is accepted as a crasher bug people could at least potentially run into on the Workstation live image. The fix is targeted and well tested.
<@adamwill:fedora.im>
16:54:25
!topic (2274171) parsec 1.4.0
<@adamwill:fedora.im>
16:54:27
!link https://bugzilla.redhat.com/show_bug.cgi?id=2274171
<@adamwill:fedora.im>
16:54:29
!link https://pagure.io/fedora-qa/blocker-review/issue/1580
<@adamwill:fedora.im>
16:54:32
!info Proposed Freeze Exceptions, parsec, ON_QA
<@adamwill:fedora.im>
16:54:35
!info Ticket vote: FinalFreezeException (+2,0,-0) (+geraldosimiao, +pwhalen)
<@adamwill:fedora.im>
16:54:43
i'm not really a huge fan of this proposal, it just says "new version! we want it!"
<@adamwill:fedora.im>
16:54:52
well...why? what's it do? what's the justification for breaking freeze?
<@adamwill:fedora.im>
16:54:57
Peter Robinson: are you around for more details?
<@nielsenb:fedora.im>
16:55:24
Where's your spirit of adventure?
<@adamwill:fedora.im>
16:55:54
Brandon Nielsen: nailed to the wall, alongside my sunny, youthful nature
<@tablepc:matrix.org>
16:55:56
We want it is dangerous justification
<@nhanlon:beeper.com>
16:56:55
also; for what it's worth... 1.4.0 parsec failed in upstream CI...
<@nhanlon:beeper.com>
16:56:58
https://app.circleci.com/pipelines/github/parallaxsecond/parsec/267/workflows/72728aae-1e29-4be5-bf05-b227133859ab/jobs/242/tests
<@nhanlon:beeper.com>
16:57:01
soooo
<@salimma:fedora.im>
16:57:31
oof
<@geraldosimiao:matrix.org>
16:57:39
😯
<@salimma:fedora.im>
16:57:40
and yeah the changelog is unclear about any breaking change https://github.com/parallaxsecond/parsec/blob/main/CHANGELOG.md
<@adamwill:fedora.im>
16:58:04
that is one hell of a CI failure
<@adamwill:fedora.im>
16:58:10
def test_answer():
> assert 1 + 1 == 3
<@adamwill:fedora.im>
16:58:13
i have questions
<@geraldosimiao:matrix.org>
16:58:23
Weel ill revert my vote to
FE +0
<@nhanlon:beeper.com>
16:58:43
I'm FE-1 and investigation+2
<@geraldosimiao:matrix.org>
16:58:43
Wel ill revert my vote to
FE +0
<@geraldosimiao:matrix.org>
16:59:08
Wel I'll revert my vote to
FE +0
<@nielsenb:fedora.im>
16:59:14
FinalFE -1
<@salimma:fedora.im>
16:59:23
🤦♂️
<@adamwill:fedora.im>
16:59:43
i mean, maybe there's a reason for that, but it sure *looks* weird. :D
<@salimma:fedora.im>
17:00:27
checking the dependencies, looks like dbus-parsec depends on parsec and does not specify any version range. so... yeah it should probably be tested
<@nhanlon:beeper.com>
17:00:32
ngl, so does this https://github.com/parallaxsecond/parsec/commit/9aeb04bed071eaa87aa5a18df837a11e64d219f6
<@salimma:fedora.im>
17:02:02
that part seems reasonable though - depends on if you can still run it. tests that depend on specific hardware are annoying when they fail
<@adamwill:fedora.im>
17:02:18
proposed !agreed 2274171 - RejectedFreezeException (Final) - the proposal here provides no real justification for a freeze exception, and the request is to pull in a major new release with an unclear backwards compatibility status and some slightly odd test results. This is rejected for now, can be proposed again with a clearer justification
<@nielsenb:fedora.im>
17:02:40
ack
<@nhanlon:beeper.com>
17:02:44
ack
<@adamwill:fedora.im>
17:02:49
oh, that's counting me as FinalFE -1, sorry
<@adamwill:fedora.im>
17:02:52
which i didn't explicitly say
<@salimma:fedora.im>
17:02:53
ack
<@frantisekz:fedora.im>
17:03:08
ack
<@adamwill:fedora.im>
17:03:47
!agreed 2274171 - RejectedFreezeException (Final) - the proposal here provides no real justification for a freeze exception, and the request is to pull in a major new release with an unclear backwards compatibility status and some slightly odd test results. This is rejected for now, can be proposed again with a clearer justification
<@nhanlon:beeper.com>
17:03:54
yeah, it's probably innocuous, just in light of... recent events... I question everything :)
<@salimma:fedora.im>
17:04:20
fair
<@nhanlon:beeper.com>
17:04:42
on the less paranoid hand ... it's probably for a CVE that they're trying to not disclose yet
<@tablepc:matrix.org>
17:05:24
Please don't even think that
<@nhanlon:beeper.com>
17:06:05
i mean, the changelog notes "- Vulnerability in SQLite [\#648](https://github.com/parallaxsecond/parsec/issues/648)" so, there is at least that. Still, would like to have more justification.
<@salimma:fedora.im>
17:06:49
oh boy if this is some undisclosed bug... the fallout could be huge once we finally know the details
<@salimma:fedora.im>
17:06:53
sqlite...
<@salimma:fedora.im>
17:07:05
oh boy if this is some embargoed bug... the fallout could be huge once we finally know the details
<@salimma:fedora.im>
17:07:10
s/undisclosed/embargoed
<@decathorpe:fedora.im>
17:07:20
note that dbus-parsec has been FTBFS for a while, so fixing it if necessary would be more work than just adding a patch
<@salimma:fedora.im>
17:07:38
ah yes, I was wondering why the NVR in Rawhide is still from fc39
<@adamwill:fedora.im>
17:10:10
alrighty, that's all the proposals
<@adamwill:fedora.im>
17:10:17
let's circle back to the tabled one
<@adamwill:fedora.im>
17:10:26
!info let's circle back to our tabled blocker proposal
<@adamwill:fedora.im>
17:10:32
!topic (2275099) Recording the screencast does not work properly.
<@adamwill:fedora.im>
17:10:39
so, I did reproduce this in a VM, did everyone else try?
<@nielsenb:fedora.im>
17:10:48
Just tried again on a fresh 1.14 install, worked fine on my laptop
<@nielsenb:fedora.im>
17:11:02
In a VM, it also worked, but blue is orange
<@nielsenb:fedora.im>
17:11:13
It's been awhile since I worked in video, so I don't remember what that might mean
<@decathorpe:fedora.im>
17:12:04
bit swizzling problem? or YUV / RGB issue?
<@nielsenb:fedora.im>
17:12:37
"Color is messed up"
<@nielsenb:fedora.im>
17:13:11
But yeah, I'm guessing colorspace is set wrong somehow
<@tablepc:matrix.org>
17:13:18
I haven't had any color issue with my bare metal.
<@tablepc:matrix.org>
17:14:43
Haven't been fiddling with color either
<@adamwill:fedora.im>
17:15:47
did anyone try in a VM? can folks try that?
<@adamwill:fedora.im>
17:15:55
if we can say 'this pretty much always reproduces in a VM but not on metal', that seems helpful
<@nielsenb:fedora.im>
17:16:14
Worked for me, except the color issue noted
<@nielsenb:fedora.im>
17:16:59
I have yet to see the crash
<@nielsenb:fedora.im>
17:17:09
Feel like I'm missing out
<@nirik:matrix.scrye.com>
17:17:58
upstream report suggests latest pipewire/mesa could fix this...
<@adamwill:fedora.im>
17:19:25
well, we're on mesa 24.0.5 at least
<@adamwill:fedora.im>
17:19:35
weird note: i just tried on vmware and it doesn't offer screen recording *at all*
<@tablepc:matrix.org>
17:19:45
When you're testing with a vm do you use cockpit or boxes to set it up for test
<@adamwill:fedora.im>
17:19:51
must be some kind of detection going on there? but i dunno what about the VM would make gnome decide not to offer screen recording. huh.
<@adamwill:fedora.im>
17:20:04
tablepc: i'm using virt-manager , but they all use libvirt behind the scenes so it shouldn't matter much
<@nielsenb:fedora.im>
17:20:04
Boxes, with GPU acceleration otherwise performance is unbearable
<@nielsenb:fedora.im>
17:20:33
It checks the license fee
<@nhanlon:beeper.com>
17:20:46
insert coin to record
<@nirik:matrix.scrye.com>
17:21:07
PC LOAD LETTER
<@salimma:fedora.im>
17:22:04
gives a new meaning to token-passing
<@tablepc:matrix.org>
17:22:37
But where do you get the tokens?
<@nhanlon:beeper.com>
17:22:56
wherever gold coins are sold
<@tablepc:matrix.org>
17:23:18
But my PCs don't have coin slots
<@salimma:fedora.im>
17:23:33
put it in the HDMI port
<@nhanlon:beeper.com>
17:23:38
CMOS 😈
<@adamwill:fedora.im>
17:26:35
sooo...
<@adamwill:fedora.im>
17:27:20
i dunno, let's see if i can reliably reproduce in the vm, then try with newer pipewire...
<@adamwill:fedora.im>
17:28:20
yeah, triggered it second try too, 2/2
<@adamwill:fedora.im>
17:28:22
let's try once more
<@nhanlon:beeper.com>
17:28:34
i'm trying now too
<@nielsenb:fedora.im>
17:28:44
Must be some strange confluence of hardware and VM
<@adamwill:fedora.im>
17:28:52
"Because that fixed a timeout bug that could occur, especially without proper 3d drivers."
<@nielsenb:fedora.im>
17:29:39
I can't select the "Window" option, which is odd
<@adamwill:fedora.im>
17:29:56
yep, 3/3
<@adamwill:fedora.im>
17:30:01
always seems to happen at 25 seconds
<@nielsenb:fedora.im>
17:30:19
Oh, they need to be that long?
<@nielsenb:fedora.im>
17:31:32
50 seconds, no problem
<@adamwill:fedora.im>
17:32:09
vm or metal?
<@nielsenb:fedora.im>
17:32:30
VM that time
<@nielsenb:fedora.im>
17:32:33
Trying now on metal
<@tablepc:matrix.org>
17:32:33
Trying long
<@adamwill:fedora.im>
17:32:37
hmm
<@adamwill:fedora.im>
17:32:41
try without 3D passthru?
<@nielsenb:fedora.im>
17:32:57
50 seconds, fine on metal
<@nielsenb:fedora.im>
17:33:12
I genuinely can barely even use the desktop without that
<@nielsenb:fedora.im>
17:33:33
I'm a pretty tolerant user, but...
<@adamwill:fedora.im>
17:33:46
i mean, it's just for testing
<@adamwill:fedora.im>
17:33:58
(also i never use it because it doesn't seem to work on my system, so if i have to suck it up so do you :>)
<@nielsenb:fedora.im>
17:34:15
I'm just saying, I'm not sure I really consider that a valid use case?
<@nhanlon:beeper.com>
17:34:16
yeah just repro'd here in kvm
<@nhanlon:beeper.com>
17:34:18
25 seconds
<@nielsenb:fedora.im>
17:34:23
"Look at how bad this performs!"
<@nielsenb:fedora.im>
17:35:13
Oh yeah, look at that
<@adamwill:fedora.im>
17:35:14
okay, pipewire doesn't fix it
<@nielsenb:fedora.im>
17:35:17
Explodes right at 25s
<@adamwill:fedora.im>
17:35:21
okay
<@adamwill:fedora.im>
17:35:49
so, seems like we can say this is pretty consistently happening on VMs with 3D passthrough disabled (I think someone said they saw it even with 3d passthrough enabled, but i guess it might depend on performance or phase of the moon or something)(
<@adamwill:fedora.im>
17:35:57
i don't think anyone reproduced on metal yet
<@adamwill:fedora.im>
17:36:11
do we wanna block on that?
<@adamwill:fedora.im>
17:36:20
i kinda feel like 'no'...
<@nielsenb:fedora.im>
17:36:30
I don't, I can see the argument for it, but I don't
<@adamwill:fedora.im>
17:37:03
i guess we're technically arguing whether this is a broad enough violation of the default app and/or panel criteria
<@tablepc:matrix.org>
17:37:03
I just ran and watched one for almost 2 minutes and it was fine.
<@geraldosimiao:matrix.org>
17:37:12
Wat did we at that time when copy paste get broke on kde vm?
<@adamwill:fedora.im>
17:37:26
"All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use" and all default applications must "withstand a basic functionality test"
<@geraldosimiao:matrix.org>
17:37:34
Wat we did at that time when copy paste get broke on kde vm?
<@adamwill:fedora.im>
17:37:56
(you can trigger a recording from the panel or by launching it like an app from the overview, so i guess both are kinda applicable)
<@nhanlon:beeper.com>
17:37:57
possibly of note: I also get a crash on trying to record a screen area, whereas the 'full screen' option fails after 25s
<@adamwill:fedora.im>
17:38:03
geraldosimiao: didn't block. it's still broken.
<@adamwill:fedora.im>
17:38:18
Neil Hanlon: oh, interesting. i was always using full screen
<@geraldosimiao:matrix.org>
17:38:24
Ok, yeah
<@nielsenb:fedora.im>
17:38:33
I was doing a selection
<@geraldosimiao:matrix.org>
17:38:35
So just FE
<@adamwill:fedora.im>
17:38:35
so, i'm -1
<@adamwill:fedora.im>
17:38:43
counting nirik and brandon as -1 we're at -3
<@nhanlon:beeper.com>
17:38:45
that's even odder 😂
<@adamwill:fedora.im>
17:38:45
other votes?
<@nielsenb:fedora.im>
17:38:50
FinalBlocker -1
<@nhanlon:beeper.com>
17:38:51
-1
<@salimma:fedora.im>
17:39:05
FinalBlocker -1
<@nhanlon:beeper.com>
17:39:09
FB-1, to be clear
<@geraldosimiao:matrix.org>
17:39:10
FB -1
FE +1
<@salimma:fedora.im>
17:39:20
FinalFE +1
<@nhanlon:beeper.com>
17:39:26
FE+1
<@adamwill:fedora.im>
17:39:28
sure, FE +1
<@nirik:matrix.scrye.com>
17:40:27
FinalBlocker -1
<@geraldosimiao:matrix.org>
17:40:29
And, after all, is this gnome shell or pipewire mesa?
<@geraldosimiao:matrix.org>
17:40:42
What do you think?
<@tablepc:matrix.org>
17:40:59
I just tried a screencast on an area and it was all messed up for color
<@adamwill:fedora.im>
17:41:31
proposed !agreed 2275099 - RejectedBlocker (Final) - AcceptedFreezeException (Final) - our testing during the meeting suggests this is almost 100% reproducible on libvirt/qemu VMs (especially without 3D passthrough), but not reproducible at all on bare metal. That makes this a conditional violation of the "basic functionality" criterion for default apps and the default panel functionality criterion, but we judge that it's not severe enough to constitute a blocker, but it is bad enough to grant an FE.
<@adamwill:fedora.im>
17:41:39
geraldosimiao: dunno, we can figure that out outside the meeting I guess
<@nielsenb:fedora.im>
17:41:49
ack
<@nhanlon:beeper.com>
17:41:51
ack
<@adamwill:fedora.im>
17:42:06
tablepc: are you testing in a VM or on metal? sorry, i'm losing track :D
<@geraldosimiao:matrix.org>
17:42:09
Ack
<@tablepc:matrix.org>
17:42:22
metal
<@tablepc:matrix.org>
17:43:28
Just gor wide white and blue strips
<@adamwill:fedora.im>
17:43:30
hum, what system?
<@adamwill:fedora.im>
17:43:40
!agreed 2275099 - RejectedBlocker (Final) - AcceptedFreezeException (Final) - our testing during the meeting suggests this is almost 100% reproducible on libvirt/qemu VMs (especially without 3D passthrough), but not reproducible at all on bare metal. That makes this a conditional violation of the "basic functionality" criterion for default apps and the default panel functionality criterion, but we judge that it's not severe enough to constitute a blocker, but it is bad enough to grant an FE.
<@adamwill:fedora.im>
17:43:47
kinda sounds like you're hitting something different
<@tablepc:matrix.org>
17:44:08
Lenovo intel
<@adamwill:fedora.im>
17:44:36
hmm
<@adamwill:fedora.im>
17:44:47
just tried here on my bare metal test box and colors in an area recording seem fine
<@adamwill:fedora.im>
17:44:56
!topic Accepted blocker review
<@adamwill:fedora.im>
17:45:04
!topic (2242759) dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key
<@adamwill:fedora.im>
17:45:06
!link https://bugzilla.redhat.com/show_bug.cgi?id=2242759
<@adamwill:fedora.im>
17:45:09
!link https://pagure.io/fedora-qa/blocker-review/issue/1435
<@adamwill:fedora.im>
17:45:12
!info Accepted Previous Release Blocker, distribution, NEW
<@adamwill:fedora.im>
17:45:19
we still seem to be stuck on this one :/ no great ideas, anyone?
<@nielsenb:fedora.im>
17:46:06
So, the small service to set a clock based on file age is pretty much how I would solve it. But I don't see how you make that actually happen _before_ the update.
<@nielsenb:fedora.im>
17:46:25
At least automagically
<@tablepc:matrix.org>
17:46:59
Window worked
<@decathorpe:fedora.im>
17:47:11
isn't that what Before / After settings in unit files are for?
<@nielsenb:fedora.im>
17:47:40
Right, but how do you get that service installed and running on a system before you do the update without some kind of additional user interaction?
<@adamwill:fedora.im>
17:47:54
ah, it looks like wireplumber update fixes the screencast thing
<@nielsenb:fedora.im>
17:47:58
And running in the update environment
<@nirik:matrix.scrye.com>
17:48:51
I think the update env is just a target... just needs to add that service Before it...
<@nielsenb:fedora.im>
17:49:20
Basically, any "fix" is just as bad of a story for the user as the currently documented fix.
<@nielsenb:fedora.im>
17:49:30
At least as I see it.
<@nielsenb:fedora.im>
17:49:52
Can skip the script and just enable timesyncd or whatever the systemd thing is.
<@decathorpe:fedora.im>
17:50:52
just run it unconditionally? having the clock set to some date way in the past is *always* bad on devices like the RPi :)
<@nielsenb:fedora.im>
17:50:56
I guess by fix I mean workaround in commonbugs.
<@nirik:matrix.scrye.com>
17:51:13
I guess it would be nice to have the dnf maintainers weigh in on what they would accept?
<@adamwill:fedora.im>
17:51:17
!info we still don't have a great idea for a fix for this, we'll have to discuss further at go/no-go
<@nirik:matrix.scrye.com>
17:51:26
because it could just do this as part of the normal system-upgrade
<@nielsenb:fedora.im>
17:53:05
https://discussion.fedoraproject.org/t/f38-to-f39-40-dnf-system-upgrade-can-fail-on-raspberry-pi/92403
<@nielsenb:fedora.im>
17:53:21
Basically, touching a file is just as easy of a thing to tell a user to do, as install a package
<@nielsenb:fedora.im>
17:54:12
Side note, I feel like common issues on Discourse aren't as favored by Google as what we did before :-/
<@nielsenb:fedora.im>
17:56:11
Could make a one-shot service somehow required on update, so it would get pulled in during the "upgrade before updating releases" step maybe. But as I discovered, using gnome-software to do a regular update also hits this bug, so again, requires manual user CLI intervention
<@adamwill:fedora.im>
17:56:17
okay, let's move to open floor, as we only have five minutes left...
<@adamwill:fedora.im>
17:56:24
!topic Open floor
<@adamwill:fedora.im>
17:56:28
any other business, folks?
<@tablepc:matrix.org>
17:57:20
Looking forward to F40 Workstation
<@tablepc:matrix.org>
17:58:42
Oh QUick question is there a place to set the font size in the F40 top bar
<@adamwill:fedora.im>
17:59:33
no idea
<@tablepc:matrix.org>
17:59:55
I ask on Ask
<@adamwill:fedora.im>
18:00:22
alrighty folks, that's time
<@adamwill:fedora.im>
18:00:28
thanks for coming, everyone!
<@tablepc:matrix.org>
18:00:35
Have a Great Afternoon!
<@adamwill:fedora.im>
18:00:35
keep testing RC 1.14 :)
<@adamwill:fedora.im>
18:00:39
!endmeeting