Re: Fedora 33 blocker status
Action summary Accepted blockers - 1. libreport — abrt-server errors when processing zstd compressed core dumps produced by systemd-246~rc1-1.fc33 — POST ACTION: abrt maintainers to make a new release containing the fix 2. resteasy — FreeIPA deployment fails in current Rawhide due to various issues with Java 11 — NEW ACTION: resteasy maintainers to diagnose issue and fix or pass the buck as appropriate 3. sddm — login stuck when changing users repeatedly (log out, log in a different one) — NEW ACTION: sddm maintainers to diagnose issue and fix or pass the buck as appropriate 4. selinux-policy — SELinux is preventing systemd-machine from 'create' accesses on the sock_file io.systemd.Machine. — POST ACTION: selinux-policy maintainers to make a new release containing the fixes 5. tomcat — FreeIPA server deployment fails in Fedora-Rawhide-20200714.n.0 — MODIFIED ACTION: tomcat maintainers to investigate failed upgrade test 6. distribution — Workstation live x86_64 image exceeds maximum size — NEW ACTION: Workstation WG to determine whether or not to remove packages or increase size limit. 7. distribution — Everything boot x86_64 image exceeds maximum size — ASSIGNED ACTION: bcotton to get someone to determine whether or not to remove packages or increase size limit. 8. distribution — Server boot x86_64 image exceeds maximum size — NEW ACTION: Server WG to determine whether or not to remove packages or increase size limit. 9. distribution — Release-blocking Fedora 33 images have Fedora 32 backgrounds — NEW ACTION: kde-settings maintainers to update package to use new backgrounds Proposed blockers - 1. systemd — systemd-resolved.service not work with DNS server placed behind VPN (openconnect) — NEW ACTION: systemd maintainers to diagnose issue Bug-by-bug detail = Accepted blockers - 1. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=1860616 — POST abrt-server errors when processing zstd compressed core dumps produced by systemd-246~rc1-1.fc33 abrt doesn't support core dumps compressed with zstd, which is now used by systemd. Merged upstream PR uses libarchive to add support for zstd (and other compression formats): https://github.com/abrt/libreport/pull/656. 2. resteasy — https://bugzilla.redhat.com/show_bug.cgi?id=1866570 — NEW FreeIPA deployment fails in current Rawhide due to various issues with Java 11 Deploying FreeIPA fails with a traceback in pki-tomcat. This appears to be a dependency chain issue that (currently) ends at resteasy via dogtag-pki. This may not be the last layer in the Java 11 onion. 3. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1861700 — NEW login stuck when changing users repeatedly (log out, log in a different one) This is now a blocker based on a recent approval-in-principle of a release criterion related to logout and user switching. User processes linger after logout which blocks logging in when another user has logged in between the two sessions. Or when the second user logs back in. Or when a single user logs in repeatedly. Using KillUserProcesses=Yes helps the first problem, but raises on of its own. It appears to be a race condition of some kind as the behavior is not fully consistent. 4. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=1862686 — POST SELinux is preventing systemd-machine from 'create' accesses on the sock_file io.systemd.Machine. librvirt VMs and systemd-machined service fail with AVC denials. Merged upstream PRs should fix the denials mentioned in this bug: https://github.com/fedora-selinux/selinux-policy/pull/405 and https://github.com/fedora-selinux/selinux-policy/pull/407 5. tomcat — https://bugzilla.redhat.com/show_bug.cgi?id=1857043 — MODIFIED FreeIPA server deployment fails in Fedora-Rawhide-20200714.n.0 due to pki-tomcat failing to run with "java.lang.ClassNotFoundException: org.apache.tomcat.util.modeler.modules.MbeansDescriptorsIntrospectionSource" An upstream commit resulted in tomcat-coyote.jar missing packages. A previous fix (FEDORA-2020-f897a68801) moved the goalposts. tomcat-9.0.37-3 should fix this. Verification is blocked on BZ1866570, but Adam's most recent upgrade test still fails with a ClassNotFoundException for com.sun.xml.internal.bind.v2.ContextFactory. 6. distribtution — https://bugzilla.redhat.com/show_bug.cgi?id=1827915 — NEW Workstation live x86_64 image exceeds maximum size Workstation WG is evaluating whether they can reduce the size and if not will bump the threshold. 7. distribtution — https://bugzilla.redhat.com/show_bug.cgi?id=1849430 — ASSIGNED Everything boot x86_64 image exceeds maximum size Who owns this anyway? I'll try to get someone to figure out how we can save ~14 MB. 8. distribtution — https://bugzilla.redhat.com/show_bug.cgi?id=1849431 — ASSIGNED Server boot x86_64 image exceeds maximum size We need to slim it down by ~14 MB. 9. distribution —
Re: Release criteria proposal: networking requirements
That all sounds reasonable to me. Does wifi fall into this as well? Stephen On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote: > Hi folks! > > So at this week's blocker review meeting, the fact that we don't have > explicit networking requirements in the release criteria really > started > to bite us. In the past we have squeezed networking-related issues in > under other criteria, but for some issues that's really difficult, > notably VPN issues. So, we agreed we should draft some explicit > networking criteria. > > This turns out to be a big area and quite hard to cover (who'd've > thought!), but here is at least a first draft for us to start from. > My > proposal would be to add this to the Basic criteria. I have left out > some wikitext stuff from the proposal for clarity; I'd add it back in > on actually applying the proposed changes. It's just formatting > stuff, > nothing that'd change the meaning. Anyone have thoughts, complaints, > alternative approaches, supplements? Thanks! > > === Network requirements === > > Each of these requirements apply to both installer and installed > system > environments. For any given installer environment, the 'default > network > configuration tools' are considered to be those the installer > documents > as supported ways to configure networking (e.g. for anaconda-based > environments, configuration via kernel command line options, a > kickstart, or interactively in anaconda itself are included). > > Basic networking > > It must be possible to establish both IPv4 and IPv6 network > connections > using DHCP and static addressing. The default network configuration > tools for the console and for release-blocking desktops must work > well > enough to allow typical network connection configuration operations > without major workarounds. Standard network functions such as address > resolution and connections with common protocols such as ping, HTTP > and > ssh must work as expected. > > Footnote titled "Supported hardware": Supported network hardware is > hardware for which the Fedora kernel includes drivers and, where > necessary, for which a firmware package is available. If support for > a > commonly-used piece or type of network hardware that would usually be > present is omitted, that may constitute a violation of this > criterion, > after consideration of the [[Blocker_Bug_FAQ|hardware-dependent- > issues|normal factors for hardware-dependent issues]]. Similarly, > violations of this criteria that are hardware or configuration > dependent are, as usual, subject to consideration of those factors > when > determining whether they are release-blocking > > VPN connections > > Using the default network configuration tools for the console and for > release-blocking desktops, it must be possible to establish a working > connection to common OpenVPN, openconnect-supported and vpnc- > supported > VNC servers with typical configurations. > > Footnote title "Supported servers and configurations": As there are > many different VPN server applications and configurations, blocker > reviewers must use their best judgment in determining whether > violations of this criterion are likely to be encountered commonly > enough to block a release, and if so, at which milestone. As a > general > principle, the more people are likely to use affected servers and the > less complicated the configuration required to hit the bug, the more > likely it is to be a blocker. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . > net > http://www.happyassassin.net > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
[Test-Announce] 2020-08-24 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2020-08-24 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! Fedora 33 has branched, and we have a couple of criteria proposals to discuss, so let's have a meeting on Monday! If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 33 status 3. Criteria proposals: log in/out, networking... 4. Test Day / community event status 5. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
[Test-Announce] 2020-08-24 @ 16:00 UTC - Fedora 33 Blocker Review Meeting
# F33 Blocker Review meeting # Date: 2020-08-24 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have only 1 proposed Beta blocker to review at present, but more may well show up over the weekend, so let's have a Fedora 33 blocker review meeting on Monday! If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . 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. Information on the release criteria for F33 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
Release criteria proposal: networking requirements
Hi folks! So at this week's blocker review meeting, the fact that we don't have explicit networking requirements in the release criteria really started to bite us. In the past we have squeezed networking-related issues in under other criteria, but for some issues that's really difficult, notably VPN issues. So, we agreed we should draft some explicit networking criteria. This turns out to be a big area and quite hard to cover (who'd've thought!), but here is at least a first draft for us to start from. My proposal would be to add this to the Basic criteria. I have left out some wikitext stuff from the proposal for clarity; I'd add it back in on actually applying the proposed changes. It's just formatting stuff, nothing that'd change the meaning. Anyone have thoughts, complaints, alternative approaches, supplements? Thanks! === Network requirements === Each of these requirements apply to both installer and installed system environments. For any given installer environment, the 'default network configuration tools' are considered to be those the installer documents as supported ways to configure networking (e.g. for anaconda-based environments, configuration via kernel command line options, a kickstart, or interactively in anaconda itself are included). Basic networking It must be possible to establish both IPv4 and IPv6 network connections using DHCP and static addressing. The default network configuration tools for the console and for release-blocking desktops must work well enough to allow typical network connection configuration operations without major workarounds. Standard network functions such as address resolution and connections with common protocols such as ping, HTTP and ssh must work as expected. Footnote titled "Supported hardware": Supported network hardware is hardware for which the Fedora kernel includes drivers and, where necessary, for which a firmware package is available. If support for a commonly-used piece or type of network hardware that would usually be present is omitted, that may constitute a violation of this criterion, after consideration of the [[Blocker_Bug_FAQ|hardware-dependent- issues|normal factors for hardware-dependent issues]]. Similarly, violations of this criteria that are hardware or configuration dependent are, as usual, subject to consideration of those factors when determining whether they are release-blocking VPN connections Using the default network configuration tools for the console and for release-blocking desktops, it must be possible to establish a working connection to common OpenVPN, openconnect-supported and vpnc-supported VNC servers with typical configurations. Footnote title "Supported servers and configurations": As there are many different VPN server applications and configurations, blocker reviewers must use their best judgment in determining whether violations of this criterion are likely to be encountered commonly enough to block a release, and if so, at which milestone. As a general principle, the more people are likely to use affected servers and the less complicated the configuration required to hit the bug, the more likely it is to be a blocker. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Introduction
On Fri, 2020-08-21 at 02:49 +0530, Sunny Goswami wrote:
> Hello Everyone
Hello sunny078 and welcome to Fedora QA! I have sponsored you by now.
You can start off by testing updates in [
http://bodhi.fedoraproject.org/] for Fedora 31, Fedora 32, and Fedora
33. Update testing is where a tester tests a package and gives out a +1
Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora
Releases and tags viz "pending" & "testing". You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving
out feedbacks.
You can start with Release Validation testing. In Release Validation
all you need to do is to check the nightly/TC/RC against certain
criteria. For example, let's take the latest compose (Fedora 33
Branched 20200819.n.0), you can run test cases which are mentioned [2]
and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section
which will have the steps (to be executed sequentially) and if the
results match with the expected results you can mark it as pass by
editing the wiki page {{result|PASS|}}. Always make sure
to check for "Associated release criterion" which can be found on the
top of test case page, if your test case fails you can mark it fail by
editing the wiki page {{result|FAIL|}} and file a bug at
RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these
addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.
Other Blogs to read:
1.
https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/
2.
https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-2/
3.
https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-3/
[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200819.n.1_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode
(or on Telegram https://t.me/fedora_qa)
We have test days coming happening now (this week we are testing the
new Kernel 5.8)[5] which is a nice place to start, please stay tuned to
the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
[5]
https://fedoramagazine.org/contribute-at-the-fedora-kernel-and-gnome-test-days/
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora-Cloud-31-20200821.0 compose check report
No missing expected images. Passed openQA tests: 7/7 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora-Cloud-32-20200821.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-32-20200820.0): ID: 645102 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/645102 Passed openQA tests: 6/7 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora-IoT-33-20200821.0 compose check report
No missing expected images. Soft failed openQA tests: 3/16 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-IoT-33-20200820.0): ID: 645081 Test: x86_64 IoT-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/645081 ID: 645082 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/645082 ID: 645083 Test: x86_64 IoT-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/645083 Passed openQA tests: 13/16 (x86_64) New passes (same test not passed in Fedora-IoT-33-20200820.0): ID: 645087 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_server URL: https://openqa.fedoraproject.org/tests/645087 ID: 645096 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_ignition URL: https://openqa.fedoraproject.org/tests/645096 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora-33-20200821.n.0 compose check report
No missing expected images. Failed openQA tests: 22/181 (x86_64) New failures (same test not failed in Fedora-33-20200819.n.1): ID: 645029 Test: x86_64 universal install_blivet_ext3 URL: https://openqa.fedoraproject.org/tests/645029 Old failures (same test failed in Fedora-33-20200819.n.1): ID: 644920 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/644920 ID: 644924 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/644924 ID: 644932 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/644932 ID: 644933 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/644933 ID: 644938 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/644938 ID: 644955 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/644955 ID: 644961 Test: x86_64 Workstation-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/644961 ID: 644967 Test: x86_64 KDE-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/644967 ID: 644970 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/644970 ID: 644985 Test: x86_64 Silverblue-dvd_ostree-iso desktop_background URL: https://openqa.fedoraproject.org/tests/644985 ID: 645003 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/645003 ID: 645004 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/645004 ID: 645025 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/645025 ID: 645053 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/645053 ID: 645054 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/645054 ID: 645055 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/645055 ID: 645056 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/645056 ID: 645057 Test: x86_64 universal upgrade_2_minimal_uefi@uefi URL: https://openqa.fedoraproject.org/tests/645057 ID: 645061 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/645061 ID: 645075 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/645075 ID: 645078 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/645078 Soft failed openQA tests: 85/181 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-33-20200819.n.1): ID: 644951 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/644951 ID: 645020 Test: x86_64 universal install_simple_free_space URL: https://openqa.fedoraproject.org/tests/645020 Old soft failures (same test soft failed in Fedora-33-20200819.n.1): ID: 644900 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/644900 ID: 644901 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/644901 ID: 644902 Test: x86_64 Server-dvd-iso install_repository_hd_variation URL: https://openqa.fedoraproject.org/tests/644902 ID: 644905 Test: x86_64 Server-dvd-iso install_vnc_server URL: https://openqa.fedoraproject.org/tests/644905 ID: 644907 Test: x86_64 Server-dvd-iso install_vncconnect_server URL: https://openqa.fedoraproject.org/tests/644907 ID: 644909 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/644909 ID: 644910 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/644910 ID: 644915 Test: x86_64 Server-dvd-iso install_updates_nfs URL: https://openqa.fedoraproject.org/tests/644915 ID: 644916 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/644916 ID: 644917 Test: x86_64 Server-dvd-iso install_repository_nfs_variation URL: https://openqa.fedoraproject.org/tests/644917 ID: 644918 Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation URL: https://openqa.fedoraproject.org/tests/644918 ID: 644942 Test: x86_64 Everything-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/644942 ID: 644943 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/644943 ID: 644945 Test: x86_64 Workstation-live-iso install_default_upload URL:
Fedora 33 compose report: 20200821.n.0 changes
OLD: Fedora-33-20200819.n.1
NEW: Fedora-33-20200821.n.0
= SUMMARY =
Added images:2
Dropped images: 3
Added packages: 12
Dropped packages:0
Upgraded packages: 97
Downgraded packages: 0
Size of added packages: 203.38 MiB
Size of dropped packages:0 B
Size of upgraded packages: 2.45 GiB
Size of downgraded packages: 0 B
Size change of upgraded packages: -7.74 MiB
Size change of downgraded packages: 0 B
= ADDED IMAGES =
Image: Scientific vagrant-virtualbox x86_64
Path:
Labs/x86_64/images/Fedora-Scientific-Vagrant-33-20200821.n.0.x86_64.vagrant-virtualbox.box
Image: Scientific vagrant-libvirt x86_64
Path:
Labs/x86_64/images/Fedora-Scientific-Vagrant-33-20200821.n.0.x86_64.vagrant-libvirt.box
= DROPPED IMAGES =
Image: Mate live x86_64
Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-33-20200819.n.1.iso
Image: KDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-KDE-armhfp-33-20200819.n.1-sda.raw.xz
Image: Mate raw-xz armhfp
Path: Spins/armhfp/images/Fedora-Mate-armhfp-33-20200819.n.1-sda.raw.xz
= ADDED PACKAGES =
Package: AusweisApp2-1.20.1-1.fc33
Summary: Online identification with German ID card (Personalausweis)
RPMs:AusweisApp2 AusweisApp2-data AusweisApp2-doc AusweisApp2-doc-api
Size:80.17 MiB
Package: ecj-1:4.16-4.module_f33+9953+76bc174e
Summary: Eclipse Compiler for Java
RPMs:ecj
Size:2.73 MiB
Package: eclipse-usage-4.16.0-2.fc33
Summary: Usage reporting plug-ins for Eclipse
RPMs:eclipse-usage
Size:130.18 KiB
Package: f33-backgrounds-33.0.2-1.fc33
Summary: Fedora 33 default desktop background
RPMs:f33-backgrounds f33-backgrounds-base f33-backgrounds-extras-base
f33-backgrounds-extras-gnome f33-backgrounds-extras-kde
f33-backgrounds-extras-mate f33-backgrounds-extras-xfce f33-backgrounds-gnome
f33-backgrounds-kde f33-backgrounds-mate f33-backgrounds-xfce
Size:8.85 MiB
Package: ocaml-ppx-base-0.14.0-1.fc33
Summary: Base set of OCaml ppx rewriters
RPMs:ocaml-ppx-base ocaml-ppx-base-devel
Size:54.60 MiB
Package: ocaml-time-now-0.14.0-1.fc33
Summary: Get the current time in OCaml
RPMs:ocaml-time-now ocaml-time-now-devel
Size:393.96 KiB
Package: standard-test-roles-4.4-1.module_f33+9924+b4f9ba10
Summary: Standard Test Interface Ansible roles
RPMs:standard-test-roles standard-test-roles-inventory-docker
standard-test-roles-inventory-qemu
Size:69.43 KiB
Package: subversion-1.14.0-6.module_f33+9935+f565adf2
Summary: A Modern Concurrent Version Control System
RPMs:mod_dav_svn python3-subversion subversion subversion-devel
subversion-gnome subversion-javahl subversion-kde subversion-libs
subversion-perl subversion-ruby subversion-tools
Size:28.00 MiB
Package: swig-3.0.12-27.module_f33+9947+1316c140
Summary: Connects C/C++/Objective C to some high-level programming languages
RPMs:ccache-swig swig swig-doc swig-gdb
Size:11.75 MiB
Package: tomcat-1:9.0.37-4.module_f33+9953+76bc174e
Summary: Apache Servlet/JSP Engine, RI for Servlet 4.0/JSP 2.3 API
RPMs:tomcat tomcat-admin-webapps tomcat-docs-webapp tomcat-el-3.0-api
tomcat-jsp-2.3-api tomcat-jsvc tomcat-lib tomcat-servlet-4.0-api tomcat-webapps
Size:6.87 MiB
Package: varnish-6.0.6-1.module_f33+9963+f5992496
Summary: High-performance HTTP accelerator
RPMs:varnish varnish-devel varnish-docs
Size:9.44 MiB
Package: varnish-modules-0.15.0-9.module_f33+9963+f5992496
Summary: A collection of modules ("vmods") extending Varnish VCL
RPMs:varnish-modules
Size:406.38 KiB
= DROPPED PACKAGES =
= UPGRADED PACKAGES =
Package: ModemManager-1.14.2-1.fc33
Old package: ModemManager-1.14.0-1.fc33
Summary: Mobile broadband modem management service
RPMs: ModemManager ModemManager-devel ModemManager-glib
ModemManager-glib-devel ModemManager-vala
Size: 11.36 MiB
Size change: 6.22 KiB
Changelog:
* Thu Aug 20 2020 Peter Robinson - 1.14.2-1
- Update to 1.14.2
Package: awscli-1.18.123-1.fc33
Old package: awscli-1.18.122-1.fc33
Summary: Universal Command Line Environment for AWS
RPMs: awscli
Size: 1.84 MiB
Size change: 72 B
Changelog:
* Wed Aug 19 2020 Gwyn Ciesla - 1.18.123-1
- 1.18.123
Package: celestia-1.6.2-0.3.beta3.fc33
Old package: celestia-1.6.2-0.2.beta3.fc33
Summary: OpenGL real-time visual space simulation
RPMs: celestia
Size: 171.19 MiB
Size change: 5.39 MiB
Changelog:
* Thu Aug 20 2020 Tom Callaway - 1.6.2-0.3.beta3
- Successfully relicensed Scott Hudson's asteroid models to a FOSS & GPLv2+
compatible license
- generated new clean tarball
Package: clash-1.1.0-1.fc33
Old package: clash-1.0.0-4.fc33
Summary: A rule-based tunnel in Go
RPMs: clash golang-github-dreamacro-clash-devel
Size: 14.39 MiB
Size change: 290.85 KiB
Changelog:
* Tue Aug 18 2020 Qiyu Yan - 1.1.0-1
- update to 1.1.0 upstream release
Package: cmake
