September 2019 - devel - Fedora Mailing-Lists

Fedora-31-20190911.0 compose check report

by Fedora compose checker

No missing expected images. Failed openQA tests: 3/152 (x86_64), 1/2 (arm) ID: 448775 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/448775 ID: 448810 Test: x86_64 KDE-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/448810 ID: 448813 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/448813 ID: 448816 Test: x86_64 Silverblue-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/448816 Soft failed openQA tests: 2/152 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 448791 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/448791 ID: 448926 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/448926 Passed openQA tests: 147/152 (x86_64) Skipped non-gating openQA tests: 1 of 154 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

4 years, 7 months

1
0
0 / 0

Unresponsive maintainers: Alex Chernyakhovsky & Othman Madjoudj

by Robbie Harwood

4 years, 7 months

3
2
0 / 0

Interest in doing Fedora CI with test subpackages

by Neil Horman

Hey all- I was starting to setup CI for one of my packages in Fedora (cscope), which requires that I have access to the sources to run my test (cscope uses its own source tree to search for various symbols to confirm that its working properly). Getting the sources in the CI environment is a bit of a pain, so I started working on trying to do this by creating a test subpackage (specifically named -citest) to package up the sources solely for the purpose of getting them installed and available during CI runs. It occured to me that this offers several advantages, among them: 1) the ability to codify dependencies within the ame spec file, rather than having to copy them to the test.yml file, and keep them in sync 2) The ability to use a file format (rpm spec files) that I'm more familiar with 3) Easy access to tests that are embedded in the source tree 4) minimizing the test harness setup in test.yml For anyone interested, I've got a pull request started here: https://src.fedoraproject.org/rpms/cscope/pull-request/2 If anyone wants to take a look at the changes I had to make to do this (fair warning, its still very rough). That all said, I was wondering if perhaps there was general interest in making this kind of test model somewhat more formal (i.e. creating an rpm macro library to make test package generation a bit easier, creating a standard entry point to run tests, etc). Thoughts welcome

4 years, 7 months

3
3
0 / 0

[Test-Announce] Fedora 31 Candidate Beta-1.1 Available Now!

by rawhide＠fedoraproject.org

According to the schedule [1], Fedora 31 Candidate Beta-1.1 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/31 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_31_Beta_1.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_31_Beta_1.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_31_Beta_1.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_31_Beta_1.1_Server https://fedoraproject.org/wiki/Test_Results:Fedora_31_Beta_1.1_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_31_Beta_1.1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_31_Beta_1.1_Security_Lab All Beta priority test cases for each of these test pages [2] must pass in order to meet the Beta Release Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5]. Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-31/f-31-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_31_Beta_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-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/test-announce@lists.fedorap...

4 years, 7 months

1
0
0 / 0

Fedora 32 Self-Contained Change proposal: MariaDB 10.4

by Ben Cotton

https://fedoraproject.org/wiki/Changes/MariaDB_10.4 = MariaDB 10.4 = == Summary == Update of MariaDB ('mariadb' package) in Fedora from 10.3 to 10.4 version. == Owner == * Name: [[User:mschorm| Michal Schorm]] * Email: mschorm(a)redhat.com == Detailed Description == Update of MariaDB package in Fedora from 10.3 version to 10.4 version. == Benefit to Fedora == I'm cooperating with the upstream to bring the latest stable software to Fedora users. 10.4 series introduces number of enhancements, which cannot be found in previous series. Apart from that, MariaDB Galera Cluster has been significantly reworked and enhanced. (galera 3 updated to galera 4) == Scope == * Proposal owners: **Prepare MariaDB 10.4 as a module for Rawhide and atleast one stable Fedora release (done) **Prepare MariaDB 10.3 as a module for Rawhide, so there would be a failover in case of problems (done) **Release MariaDB 10.4 to Rawhide (blocked by #1724283; solving with upstream) **Check software that requires or depends on 'mariadb' or 'galera' package for incompatibilities **Gather user input on the changes between MariaDB 10.3 and 10.4 * Other developers: N/A * Policies and guidelines: N/A * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == The MariaDB client library is compatible, so the shouldn't be any issues and / or need for rebuild of dependent packages. Galera package bumped version from 25.3 to 25.4 which introduces bigger changes. However since no other project in Fedora than MariaDB use Galera, I don't expect any issue here. == How To Test == Usual testing as when upgrading between major MariaDB versions. Test that all other software runs well with MariaDB 10.4. Report any issues, so I can reach the different upstreams and check if they plan update their software to support MariaDB 10.4 and when. == User Experience == The users will have to upgrade their databases the same way as between major MariaDB versions. If the users want to stick with MariaDB for a little longer, I provide MariaDB 10.3 module. If the users want to test it beforehand, I provide MariaDB 10.4 module. == Dependencies == There should be absolute minimum amountof packages, that use MariaDB as a BuildRequires. Since the separation of MariaDB client library, only packages that build server plugins may use MariaDB as a BuildRequires. Since the client library ('mariadb-connector-c') is not changing, dependent software should work fine. == Contingency Plan == Modules will provide the functional version of MariaDB 10.3, available to all users. * Contingency mechanism: Fedora Modules available * Contingency deadline: beta freeze == Documentation == Upgrade startegy: https://mariadb.com/kb/en/library/upgrading-from-mariadb-103-to-mariadb-104/ Upgrading and incompatibilities: https://mariadb.com/kb/en/library/upgrading-from-mariadb-103-to-mariadb-1... == Release Notes == Release notes for each release: https://mariadb.com/kb/en/library/release-notes-mariadb-104-series/ Overall overview of the changes and improvements: https://mariadb.com/kb/en/library/changes-improvements-in-mariadb-104/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

4 years, 7 months

1
0
0 / 0

Please help with youtube-dl and possibly other packages of mine.

by Till Maas

Hi, Please help with updating youtube-dl and possibly other packages of mine because I cannot do it and my comaintainers do not seem to be able to do it as well. Thank you and kind regards Till

4 years, 7 months

4
4
0 / 0

translucent gnome top bar gone in F31?

by Zbigniew Jędrzejewski-Szmek

Hi, I upgraded to F31 recently, and I now I noticed that the gnome top bar is always black. I miss the old translucent blue bar that would only go black if window was moved adjacent. I'm not sure though when this changed... Zbyszek

4 years, 7 months

10
17
0 / 0

failing push for un-orphaned package

by Dave Love

What to I need to do to be able to push to the repo of something I've got un-orphaned? I currently see: $ fedpkg push Counting objects: 10, done. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 877 bytes | 0 bytes/s, done. Total 7 (delta 4), reused 0 (delta 0) remote: Branch refs/heads/master is unsupported remote: Denied push for ref 'refs/heads/master' for user 'loveshack' remote: All changes have been rejected To ssh://loveshack@pkgs.fedoraproject.org/rpms/powerman ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'ssh://loveshack@pkgs.fedoraproject.org/rpms/powerman' Could not execute push: Failed to execute command. Although I haven't changed them, none of the hooks under the project settings show as active.

4 years, 7 months

3
4
0 / 0

Minimization Objective report

by Adam Samalik

This is the Minimization Objective [0] update. Status: Discovery phase == Use case analysis == Removing Systemd dependency from container use cases: -- nginx -- * Pull request to drop systemd as a runtime requirement [1] -- httpd -- * Pull request to drop systemd as a runtime requirement [2] * They have one binary that requires systemd, will have a further discussion with them to figure out how to shrink the container/runtime size -- anaconda -- * Pull request to move flatpack-libs from anaconda-core to anaconda-gui [3] * Determined that flatpack-libs was in the correct space -- mariadb -- * Investigating removing systemd and perl from depenencies. * Perl is in two mongodb (client package) scripts. Possibly move it to mongodb-utils, similar to how mongodb-server-utils has the perl scripts for mongodb-server. * Still investigating if systemd could be removed safely or if something other than .service files need it. -- mozjs60 -- * This is a 25-30M installed package (different size on different arches). Do all packages really need it? -- IoT -- * Added it to the Feedback Pipeline [4] [5] * Researched anaconda minimizing [6] == Feedback Pipeline == Added issues to the github repo [7] to attract additional contributions + to indicate where the service is going. Looking into automation. == Ecosystems exploration == Collecting specific use cases [8] and making sure that each has its own issue in the tracker [43] and is added to the Feedback Pipeline [9]. == Admin == Issues in our tracker [43] now have labels corresponding to the focus areas in the action plan [42]. == How to get involved == See if there is anything interesting to you on action plan [42], or reach out with something you think is useful but is missing there. Open a ticket in the tracker [43] or discuss in #fedora-devel on IRC. Cheers, Adam [0] Objective: https://docs.fedoraproject.org/en-US/minimization/ [1] https://src.fedoraproject.org/rpms/nginx/pull-request/5 [2] https://src.fedoraproject.org/rpms/httpd/pull-request/7 [3] https://src.fedoraproject.org/rpms/anaconda/pull-request/5 [4] https://minimization.github.io/reports/report-by-use-case--iot--rawhide.html [5] https://minimization.github.io/reports/report-by-use-case--iot-x86_64--ra... [6] https://src.fedoraproject.org/rpms/anaconda/pull-request/5 [7] https://github.com/minimization/feedback-pipeline/issues [8] https://pagure.io/minimization/issue/11 [9] https://minimization.github.io/reports/view--use-cases-on-bases.html [42] Action plan: https://docs.fedoraproject.org/en-US/minimization/action-plan/ [43] Issue tracker: https://pagure.io/minimization/issues -- Adam Šamalík --------------------------- Senior Software Engineer Red Hat

4 years, 7 months

1
0
0 / 0

Minimization Team Meeting notes 2019-09-11

by Adam Samalik

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/minimizatio... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/minimizatio... Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/minimizatio... ============================================ #fedora-meeting-1: Minimization Team Meeting ============================================ Meeting started by asamalik at 15:00:27 UTC. The full logs are available athttps://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/minimizat... . Meeting summary --------------- * Roll call (asamalik, 15:00:27) * === Admin === (asamalik, 15:04:56) * the issue tracker now has labels that correspond to the four focus areas https://pagure.io/minimization/issues (asamalik, 15:06:11) * ...focus areas in the action plan: https://docs.fedoraproject.org/en-US/minimization/action-plan/ (asamalik, 15:06:39) * I'm mirroring the Feedback Pipeline code to github and I created issues there to attract potential contributors: https://github.com/minimization/feedback-pipeline (asamalik, 15:10:55) * === Focus & what's next? === (asamalik, 15:11:32) * looking for specific use cases, people are welcome to suggest some: https://pagure.io/minimization/issue/11 (asamalik, 15:42:33) * we'll focus on the one listed in the Feedback Pipeline for now https://minimization.github.io/reports/view--use-cases-on-bases.html (asamalik, 15:43:20) * ... each one will get an issue in the tracker: https://pagure.io/minimization/issues (asamalik, 15:43:40) * === Open Floor === (asamalik, 15:45:42) Meeting ended at 15:47:40 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * asamalik (54) * zodbot (12) * feborges (10) * tdawson (8) * zbyszek (6) * ignatenkobrain (0) * salimma (0) * jaruga (0) * pbrobinson (0) * Son_Goku (0) * lorbus (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Adam Šamalík --------------------------- Senior Software Engineer Red Hat

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel September 2019