DevHeads.net

Postings by Kamil Paral

vsync in VM?

Hello,

I wonder whether it's expected that vsync doesn't work in VMs. I've tested
Fedora 28/29/30 Workstation and Fedora 30 KDE guests on Fedora 30 host,
with virtio GPU (3D acceleration on and off) or QXL GPU, and in all cases,
I'm seeing hundreds or thousands of FPS in glxgears, implying that vsync is
not working.

Is that an expected state? Is there a simple way to force vsync on inside a
VM? (using virt-manager + libvirt)

Thanks a lot.
Kamil

PSA: System update fails when trying to remove rtkit-0.11-19.fc29

Recently a bug in rtkit packaging has been fixed, but the update *will
fail* on all Fedora 29 pre-release installation that have rtkit installed
(Workstation has it for sure). The details and the workaround is described
here:
<a href="https://fedoraproject.org/wiki/Common_F29_bugs#rtkit-update" title="https://fedoraproject.org/wiki/Common_F29_bugs#rtkit-update">https://fedoraproject.org/wiki/Common_F29_bugs#rtkit-update</a>

raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

(cross-posting to devel and desktop lists, ideally reply to both)

Hello,

this is a request for feedback regarding adjusting process limits to make
Steam/Wine work better on Fedora.

*A quick background:*
In August Valve announced [1] Proton [2], their own fork of Wine, to get
included in their Steam Play functionality, and allowing Linux players to
run Windows-only games transparently from Steam without any complex
configuration, just with a press of a button. Not everything works of
course, but the success rate is more than decent [3].

RFC: make $releasever return "rawhide" on Rawhide

Hello devel list,

this is a request for comments for a recent proposal I filed at releng
tracker:
<a href="https://pagure.io/releng/issue/7445" title="https://pagure.io/releng/issue/7445">https://pagure.io/releng/issue/7445</a>

In short, package managers on Rawhide would no longer replace $releasever
variable with a numerical value (like '29' at this moment, soon '30'), but
with 'rawhide' string instead. I hope this change will make life a bit
easier for third-party repos maintainers, for users, for developers and
sysadmins, and for release engineering.

Proposal to cancel: 2017-10-09 Fedora QA Meeting

Hi, we'll be heavily focusing on F27 Final testing and I don't know about
any urgent topic to discuss, so I propose we cancel this meeting. If you
have any topics, please send them to test list and we'll discuss them there.

Thanks,
Kamil

2017-10-09 @ 16:00 UTC - Fedora 27 Blocker Review Meeting

# F27 Blocker Review meeting
# Date: 2017-10-09
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! There are currently some proposed release blockers,
so let's have a Fedora 27 blocker review meeting.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

Proposal to cancel: 2017-10-02 Fedora QA Meeting

Hi, we'll be heavily focusing on F27 Final testing and I don't know about
any urgent topic to discuss, so I propose we cancel this meeting. If you
have any topics, please send them to test list and we'll discuss them there.

Thanks,
Kamil

2017-10-02 @ 16:00 UTC - Fedora 27 Blocker Review Meeting

# F27 Blocker Review meeting
# Date: 2017-10-02
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! There are currently some proposed release blockers,
so let's have a Fedora 27 blocker review meeting.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

Fedora 27 Candidate Beta-1.5 Available Now!

<a href="https://kojipkgs.fedoraproject.org/compose/27/Fedora-27-20170927.1/compose/" title="https://kojipkgs.fedoraproject.org/compose/27/Fedora-27-20170927.1/compose/">https://kojipkgs.fedoraproject.org/compose/27/Fedora-27-20170927.1/compose/</a>
They'll be later copied to
<a href="http://dl.fedoraproject.org/pub/alt/stage/27_Beta-1.5/" title="http://dl.fedoraproject.org/pub/alt/stage/27_Beta-1.5/">http://dl.fedoraproject.org/pub/alt/stage/27_Beta-1.5/</a>

According to the schedule [1], Fedora 27 Candidate Beta-1.5 is now
available for testing. Please help us complete all the validation
testing!

Fedora 27 Candidate Beta-1.3 Available Now!

According to the schedule [1], Fedora 27 Candidate Beta-1.3 is now
available for testing. Please help us complete all the validation
testing!

2017-09-25 @ 16:00 UTC - Fedora 27 Blocker Review Meeting

# F27 Blocker Review meeting
# Date: 2017-09-25
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We currently have quite a few proposed Beta blockers,
so let's have a Fedora 27 blocker review meeting.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

Proposal to cancel: 2017-09-25 Fedora QA Meeting

Hi, we'll be heavily focusing on F27 Beta testing and I don't know about
any urgent topic to discuss, so I propose we cancel this meeting. If you
have any topics, please send them to test list and we'll discuss them there.

Thanks,
Kamil

2017-09-18 @ 16:00 UTC - Fedora 27 Blocker Review Meeting

# F27 Blocker Review meeting
# Date: 2017-09-18
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We currently have quite a few proposed Beta blockers,
so let's have a Fedora 27 blocker review meeting.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

Proposal to cancel: 2017-09-18 Fedora QA Meeting

Hi, we'll be heavily focusing on F27 Beta testing and I don't know about
any urgent topic to discuss, so I propose we cancel this meeting. If you
have any topics, please send them to test list and we'll discuss them there.

Thanks,
Kamil

Power Management Test Day today (2013-11-14)

Forwarding an invite from Jan Scotka:

Hi,
There is planned Power Management testday today. If you are interested to see capabilities of your machine or measure power consumption please join us, you will see what your HW know.
Everybody with various HW configuration welcomed (Old & New & Obscure & virt guests)

info: <a href="https://fedoraproject.org/wiki/Test_Day:2013-11-14_Power_management" title="https://fedoraproject.org/wiki/Test_Day:2013-11-14_Power_management">https://fedoraproject.org/wiki/Test_Day:2013-11-14_Power_management</a>
when: today (Thursday) 14. 11.

AutoQA 0.6 released

Please read:

<a href="https://kparal.wordpress.com/2011/08/05/autoqa-0-6-released/" title="https://kparal.wordpress.com/2011/08/05/autoqa-0-6-released/">https://kparal.wordpress.com/2011/08/05/autoqa-0-6-released/</a>

Kamil

AutoQA 0.4.7 released

Please read:

<a href="http://kparal.wordpress.com/2011/04/29/autoqa-0-4-7-released/" title="http://kparal.wordpress.com/2011/04/29/autoqa-0-4-7-released/">http://kparal.wordpress.com/2011/04/29/autoqa-0-4-7-released/</a>

AutoQA will be providing comments for Fedora updates really soon...

If you're a Fedora package maintainer, you will be surely interested in this topic.

AutoQA [1] is a framework for automatic test execution written for Fedora needs. It is developed by Fedora QA [2] team. We have finally reached the state where we can experimentally share some tests results with the wide public. They were already available in the autoqa-results [3] mailing list, but that's not really what we mean by public consumption. Let's improve that.

Now prepare the drums... ready?... we are going to post the results into Fedora Update System [4] (a.k.a.

OpenLDAP/NSS Test Day - Thursday 2010-10-14

Dear Fedora Comunity,

We would like to draw your attention to forthcoming Fedora Test Day focused on
OpenLDAP [1] with TLS encryption.

The crypto implementation for TLS/SSL was recently changed from OpenSSL to
Mozilla Network Security Services (MozNSS). And there are 88 packages
depending on openldap-clients or libldap.

OpenSCAP Test Day - Thursday 2010-08-26

Greetings,

An OpenSCAP Test Day is coming up tomorrow - Thursday 26th August:

<a href="https://fedoraproject.org/wiki/Test_Day:2010-08-26_OpenSCAP" title="https://fedoraproject.org/wiki/Test_Day:2010-08-26_OpenSCAP">https://fedoraproject.org/wiki/Test_Day:2010-08-26_OpenSCAP</a>

OpenSCAP is a tool for maintaining the security of systems, such as automatically verifying the presence of patches, checking system security configuration settings, and examining systems for signs of compromise. It is accepted as a feature for the upcoming Fedora 14 [1].

Security controls that are recommended by DISA[2] and NSA[3] for RHEL5 Desktop systems were migrated into Fedora and stored in SCAP content.

gathering useful statistics for Package Maintainers

Hello,

we would like to help Package Maintainers to increase public participation in
their activities. We believe that an important step in achieving that is in
rewarding the most active participants with "fame" in different top
tens, ladders and charts. Therefore we would like to extend the current
Fedora Community website [1] with different statistics regarding user
participation in different areas relevant to your team. We have called
this project "Fedora Hall of Fame" [2].

2010-04-01 ABRT Test Day report

This is a post-event review of the ABRT test day [1].

Thank you everyone who contributed to ABRT testing. Unfortunately
there weren't many attendants, probably because it was really close
to Easter holidays.

ABRT Test Day - Thursday 2010-04-01

Yes, it’s here again, the April Fools’ Day [1]! If you don’t have your
own plans already, let me propose one for you – participate on the
ABRT test day!

ABRT is a tool that helps reporting program crashes with a few simple
mouse clicks. It is a significant part of Fedora operating system and
its functionality is important for almost every Fedora user.

Are you curious what have ABRT developers prepared for you on the
Fool’s Day? Do you want to know what surprises are awaiting you? Then
you should come and see for your own eyes!

Help us make ABRT perfect on May 1st from 11:00 to 21:00 UTC!

QA's Package update policy proposal

Hello,

I have been (together with the QA team) working on a 'Package
update policy' proposal. Because Matthew Garrett yesterday
presented his own proposal regarding this topic, we decided
to also present our proposal, albeit still unfinished.

The proposal is here:

<a href="https://fedoraproject.org/wiki/User:Kparal/Proposal:Package_update_policy" title="https://fedoraproject.org/wiki/User:Kparal/Proposal:Package_update_policy">https://fedoraproject.org/wiki/User:Kparal/Proposal:Package_update_policy</a>

I would like to stress that it is still in development and
heavily discussed (see Discussion page). The terminology
may not be correct, because I'm not a native speaker.

FESCo wants a more sane updates policy (feedback requested)

Hello,

I have seen the long thread about Updates Policy. I just wish
to inform you that I (as part of the QA team) have been working
on a draft of exactly such a policy. I suppose I will be able
to make it public during this week. I will post a link here,
so all the people will have some basis what to discuss.

The timing of this discussion is quite interesting, because
otherwise the whole discussion would be around my proposal
about a week later.

Fedora 13 Alpha TC Validation Test (Thu 02-11 to Wed 02-17)

Greetings,

As we have entered F13 test phase, now it's time for validation test
against F13 Alpha Test Compose!

new tool: rpmguard - print important differences between RPMs

Hi,

I have created a simple tool called rpmguard for checking differences
between RPM packages. It is very similar to rpmdiff, but it prints only
important changes, not all. Therefore it can be used every time a new
package is built to easily see if something hasn’t went completely wrong.

Read more on:
<a href="http://kparal.wordpress.com/2009/10/21/rpmguard-print-important-differences-between-rpms/" title="http://kparal.wordpress.com/2009/10/21/rpmguard-print-important-differences-between-rpms/">http://kparal.wordpress.com/2009/10/21/rpmguard-print-important-differen...</a>

Any comments welcome!

Kamil