test February 2024

test@lists.fedoraproject.org

13 participants
18 discussions

Fedora-40-20240217.n.0 won't install
by Ian Laurie 03 Mar '24

03 Mar '24

I'm guessing this is a known issue but using Fedora-Everything-netinst-x86_64-40-20240217.n.0.iso to install an Xfce workstation as a VirtualBox VM resulted in an aborted installation. Error was: === The following error occurred while installing the payload. This is a fatal error and the installation will be aborted. An error occurred during the transaction: Error in POSTIN scriptlet in rpm package dbus-common === Fedora-Everything-netinst-x86_64-Rawhide-20240216.n.0.iso from the previous day gives the same error. As a sanity check I installed Fedora 39 from Fedora-Everything-netinst-x86_64-39-1.5.iso and it worked. -- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney

2 9

[Test Day] [Final Call] GNOME 46 Apps
by Sumantro Mukherjee 26 Feb '24

26 Feb '24

Hey Flocks, This is a gentle reminder for contributors testing GNOME 46[0] to submit their contributions by EOD. We will wrap up the test week and export the results[1] to the wiki after the test day ends. [0] http://fedoraproject.org/wiki/Test_Day:2024-02-22_Fedora_40_GNOME_46_Apps [1] https://testdays.fedoraproject.org/events/176 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

2 2

2024-02-26 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 23 Feb '24

23 Feb '24

# F40 Blocker Review meeting # Date: 2024-02-26 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 7 proposed blockers and 4 proposed freeze exception for Beta, and 5 proposed blockers for Final. The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. I'll be on vacation on Monday, so Frantisek Zatloukal will be running the meeting, thanks Franta! 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/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** 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 F40 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 (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

libgsystem FTBFS (Issue 2225969)
by Jeffrey Walton 23 Feb '24

23 Feb '24

Hi Everyone, libgsystem is not building from source for F39 and F40. Cf., <https://bugzilla.redhat.com/show_bug.cgi?id=2225969>. The problem seems to stem from glibsystem-devel. libgsystem adds a step in its build process when glibsystem-devel is installed (the GISCAN below). If glibsystem-devel is not installed, then step is skipped (no GISCAN) and no error occurs. CCLD libglnx.la CCLD libgsystem.la GISCAN GSystem-1.0.gir src/gsystem-glib-compat.h:34: Warning: GSystem: symbol='g_clear_pointer': Skipping foreign symbol from namespace Gio /builddir/build/BUILD/libgsyst em-2015.2/tmp-introspectlvqqyft1/GSystem-1.0.c: In function ‘dump_properties’: /builddir/build/BUILD/libgsystem-2015.2/tmp-introspectlvqqyft1/GSystem-1.0.c:229:7: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement] 229 | const GValue *v = g_param_spec_get_default_value (prop); | ^~~~~ The fix is easy. However, tmp-introspectlvqqyft1/GSystem-1.0.c uses a random directory name, so we can't really provide a patch since the name is a moving target. Fedora's bug tracker does not have a glibsystem component to file the bug against. How to proceed? Thanks in advance.

1 0

reversible dual-boot test station
by Chris Murphy 23 Feb '24

23 Feb '24

Hi, I mentioned this in a QA meeting, and have given it enough testing that I think it's broadly usable. If desired it can be copied out of my user account and put up somewhere where QA folks will see it and can modify it as issues or improvements are discovered. What is it? The idea is to produce a system that can confidently be used for baremetal testing, without risking the primary operating system. While VM's are a great way to test, it's also a really idealized environment that tends to not expose an assortment of bugs that affect particular hardware. But then quite a lot of folks reasonably don't want to upgrade their daily use hardware early on, because they don't want to always have to debug things, or have to figure out how to undo the upgrade if it really goes badly. Therefore, I present a dual-boot setup offering: * no re-partitioning; * no installation step, instead system upgrade is used; * reversibility, or undoability, i.e. with just a few steps you can delete the "test OS". https://fedoraproject.org/wiki/User:Chrismurphy/Draft/dualboot_teststation -- Chris Murphy

2 5

How to work on Failure To Build From Sources (FTBFS) bug reports?
by Jeffrey Walton 22 Feb '24

22 Feb '24

Hi Everyone, I have a C/C++ background, and I am interested in helping clear some of the FTBFS backlogged bug reports at <https://docs.fedoraproject.org/en-US/releases/f40/> and <https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=blocked&list…>. The problem is, I don't know how to get involved, especially for projects with an orphaned owner like <https://bugzilla.redhat.com/show_bug.cgi?id=2226505>. There is no one to coordinate with. Another problem is, I don't know where to find a list for FTBFS for C and C++ projects. How do folks normally filter on their language(s) of choice? How does one participate in the process? Thanks in advance. Jeff

1 0

Re: Donate 1 minute of your time to test upgrades from F39 to F40
by Luna Jernberg 21 Feb '24

21 Feb '24

Worked good on my Thinkpad Edge laptop some weeks ago Den ons 21 feb. 2024 kl 08:12 skrev Miroslav Suchý <msuchy(a)redhat.com>: > > Do you want to make Fedora 40 better? Please spend 1 minute of your time and try to run: > > # Run this only if you use default Fedora modules > # next time you run any DNF command default modules will be enabled again > # This is last time we should do that :) > > sudo dnf module reset '*' > > dnf --releasever=40 --setopt=module_platform_id=platform:f40 \ > --enablerepo=updates-testing \ > $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \ > --assumeno distro-sync > > > This command does not replace `dnf system-upgrade`, but it will reveal potential problems. > > You may also run `dnf upgrade` before running this command. > > > The `--assumeno` will just test the transaction, but does not make the actual upgrade. > > > In case you hit dependency issues, please report it against the appropriate package. > > Or against fedora-obsolete-packages if that package should be removed in Fedora 40. Please check existing reports against fedora-obsolete-packages first: > > https://red.ht/2kuBDPu > > and also there is already bunch of "Fails to install" (F40FailsToInstall) reports: > > https://bugzilla.redhat.com/buglist.cgi?bug_id=2231790&bug_id_type=anddepen… > > > Two notes: > > * you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems. > > * this command found several issues on my workstation. One was issue with teamd that you will likely hit too: > > https://bugzilla.redhat.com/show_bug.cgi?id=2263334 > > and there was few other with missing provides/obsoletes that I reported. For convenience here is the relevant part of Fedora Guidelines: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repl… > > > Thank you > > Miroslav > -- > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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/devel@lists.fedoraproject.org > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

2 2

[Test Day] GNOME 46 Desktop & Core Apps
by Sumantro Mukherjee 19 Feb '24

19 Feb '24

Hey All, We're excited to invite you to the GNOME 46 Test Week! This is a unique opportunity to get early access to new features, identify bugs, and contribute to improving GNOME's usability and stability. Your participation is vital to ensure GNOME 46 meets our community's high standards. To join, simply download the testing image, test at your convenience, and report any issues you find. Your feedback is crucial in shaping the future of GNOME. The instructions to test can be found[0] and results can be submitted[1]. Thanks [0] https://fedoraproject.org/wiki/Test_Day:2024-02-19_Fedora_40_GNOME_46_Deskt… [1] https://testdays.fedoraproject.org/events/175 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

2024-02-19 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 17 Feb '24

17 Feb '24

# F40 Blocker Review meeting # Date: 2024-02-19 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 6 proposed blockers and 1 proposed freeze exception for Beta, and 4 proposed blockers for Final. The meeting will be on Matrix, as we're trying to move to more modern systems and the meeting bot is working on Matrix now. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. 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/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** 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 F40 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 (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2024-02-19 @ 16:00 UTC - Fedora QA Meeting
by Adam Williamson 17 Feb '24

17 Feb '24

# Fedora Quality Assurance Meeting # Date: 2024-02-19 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha… Greetings testers! It's meeting time again, and once again we'll be on Matrix. 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 40 status, including anaconda web UI test planning 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test February 2024