[Test-Announce] 2021-04-12 @ 16:00 UTC - Fedora 34 Blocker Review Meeting
# F34 Blocker Review meeting # Date: 2021-04-12 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 5 proposed Final blockers and 6 proposed Final freeze exceptions to review (as of now), so we'll have a Fedora 34 blocker review meeting tomorrow. 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: 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 F34 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 day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@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-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] 2021-04-12 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2021-04-12 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We didn't meet for a couple of weeks, so let's check in on that and see where we're at for the F34 release and test events. Sorry for the late notice, I only just realized I didn't send this mail! 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 34 Final status and validation 3. Outstanding proposals 4. Test Day / community event status 5. Open floor -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@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-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Podman and docker compose
El dom, 11 abr 2021 a las 23:11, Gwyn Ciesla via devel (< devel@lists.fedoraproject.org>) escribió: > Have you tried podman-compose? It's in the Fedora repos. > > > -- > Gwyn Ciesla > she/her/hers > > in your fear, seek only peace > in your fear, seek only love > -d. bowie > > > > Sent from ProtonMail mobile > > > > Original Message > On Apr 11, 2021, 7:34 PM, Sergio Belkin < seb...@gmail.com> wrote: > > > Hi, > I'm playing around with podman and docker compose, so I've read the post > at https://www.redhat.com/sysadmin/podman-docker-compose. > > The example with Gitea does not work, this the output: > > sudo docker-compose up > descargas_elasticsearch_1 is up-to-date > Creating descargas_skydive-analyzer_1 ... error > > ERROR: for descargas_skydive-analyzer_1 Cannot create container for > service skydive-analyzer: bad parameter: Link is not supported > > ERROR: for skydive-analyzer Cannot create container for service > skydive-analyzer: bad parameter: Link is not supported > ERROR: Encountered errors while bringing up the project. > > Am I doing something wrong? > > This is the log: > > abr 11 21:28:25 munster.belkin.home systemd[1]: Starting Podman API > Service... > abr 11 21:28:25 munster.belkin.home systemd[1]: Started Podman API Service. > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="/usr/bin/podman filtering > at > log level info" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="Error initializing > configured > OCI runtime kata: no valid executable found for OCI runtime kata: invalid > argument" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network podman > (typ > e=bridge) at /etc/cni/net.d/87-podman-bridge.conflist" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network > descargas_d > efault (type=bridge) at /etc/cni/net.d/descargas_default.conflist" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network > internet-mo > nitoring_back-tier (type=bridge) at > /etc/cni/net.d/internet-monitoring_back-tier.conflist" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network > internet-mo > nitoring_front-tier (type=bridge) at > /etc/cni/net.d/internet-monitoring_front-tier.conflist" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="Setting parallel job count > to > 25" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="using systemd socket > activati > on to determine API endpoint" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="using API endpoint: ''" > abr 11 21:28:25 munster.belkin.home podman[282]: > time="2021-04-11T21:28:25-03:00" level=info msg="API server listening on > \"/ru > n/podman/podman.sock\"" > abr 11 21:28:28 munster.belkin.home podman[282]: > time="2021-04-11T21:28:28-03:00" level=info > msg="APIHandler(87f3d612-9e67-4975 > -a52d-e34f8f177998) -- GET /version BEGIN" > abr 11 21:28:28 munster.belkin.home podman[282]: > time="2021-04-11T21:28:28-03:00" level=info > msg="APIHandler(f6beda6a-42c3-414c > -9d8c-0314e00c86d7) -- GET /v1.40/networks/descargas_default BEGIN" > abr 11 21:28:28 munster.belkin.home podman[282]: > time="2021-04-11T21:28:28-03:00" level=info > msg="APIHandler(60f23924-261e-41fd > -9e14-459930ec3a0b) -- GET /v1.40/info BEGIN" > abr 11 21:28:28 munster.belkin.home podman[282]: > time="2021-04-11T21:28:28-03:00" level=info > msg="APIHandler(bd218869-1c22-4faf > -878e-f2bffeaec753) -- GET /v1.40/networks/descargas_default BEGIN" > abr 11 21:28:28 munster.belkin.home podman[282]: > time="2021-04-11T21:28:28-03:00" level=info > msg="APIHandler(25b1c622-5f7d-47c6 > -8d81-cf0f0a497a2f) -- GET > /v1.40/containers/json?limit=-1=0=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp > ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D > BEGIN" > abr 11 21:28:28 munster.belkin.home podman[282]: > time="2021-04-11T21:28:28-03:00" level=info > msg="APIHandler(7af0b0a3-1e79-4f66 > -8e4d-afe5f21a336d) -- GET > /v1.40/containers/json?limit=-1=1=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp > ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D > BEGIN" > abr 11 21:28:28 munster.belkin.home podman[282]: > time="2021-04-11T21:28:28-03:00" level=info > msg="APIHandler(ad9f4acb-47ac-4699 > -aa65-e542a59912e9) -- GET > /v1.40/containers/c519bbe7f21e7c01729d62237b819b84b3bf364784a115fa536ad45153224ffc/json > BEGIN" > abr 11 21:28:28 munster.belkin.home podman[282]: >
Re: Podman and docker compose
Have you tried podman-compose? It's in the Fedora repos. \-- Gwyn Ciesla she/her/hers \ in your fear, seek only peace in your fear, seek only love \-d. bowie Sent from ProtonMail mobile \ Original Message On Apr 11, 2021, 7:34 PM, Sergio Belkin < seb...@gmail.com> wrote: > > > > Hi, > I'm playing around with podman and docker compose, so I've read the post at > https://www.redhat.com/sysadmin/podman-docker-compose. > > The example with Gitea does not work, this the output: > > sudo docker-compose up > descargas\_elasticsearch\_1 is up-to-date > Creating descargas\_skydive-analyzer\_1 ... error > > ERROR: for descargas\_skydive-analyzer\_1 Cannot create container for service > skydive-analyzer: bad parameter: Link is not supported > > ERROR: for skydive-analyzer Cannot create container for service > skydive-analyzer: bad parameter: Link is not supported > ERROR: Encountered errors while bringing up the project. > > Am I doing something wrong? > > This is the log: > > abr 11 21:28:25 munster.belkin.home systemd\[1\]: Starting Podman API > Service... > abr 11 21:28:25 munster.belkin.home systemd\[1\]: Started Podman API Service. > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="/usr/bin/podman filtering at > log level info" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="Error initializing configured > OCI runtime kata: no valid executable found for OCI runtime kata: invalid > argument" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network podman (typ > e=bridge) at /etc/cni/net.d/87-podman-bridge.conflist" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network > descargas\_d > efault (type=bridge) at /etc/cni/net.d/descargas\_default.conflist" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network internet-mo > nitoring\_back-tier (type=bridge) at > /etc/cni/net.d/internet-monitoring\_back-tier.conflist" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network internet-mo > nitoring\_front-tier (type=bridge) at > /etc/cni/net.d/internet-monitoring\_front-tier.conflist" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="Setting parallel job count to > 25" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="using systemd socket activati > on to determine API endpoint" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="using API endpoint: ''" > abr 11 21:28:25 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:25-03:00" level=info msg="API server listening on > \\"/ru > n/podman/podman.sock\\"" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(87f3d612-9e67-4975 > \-a52d-e34f8f177998) -- GET /version BEGIN" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(f6beda6a-42c3-414c > \-9d8c-0314e00c86d7) -- GET /v1.40/networks/descargas\_default BEGIN" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(60f23924-261e-41fd > \-9e14-459930ec3a0b) -- GET /v1.40/info BEGIN" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(bd218869-1c22-4faf > \-878e-f2bffeaec753) -- GET /v1.40/networks/descargas\_default BEGIN" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(25b1c622-5f7d-47c6 > \-8d81-cf0f0a497a2f) -- GET > /v1.40/containers/json?limit=-1=0=0\_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp > ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D > BEGIN" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(7af0b0a3-1e79-4f66 > \-8e4d-afe5f21a336d) -- GET > /v1.40/containers/json?limit=-1=1=0\_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp > ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D > BEGIN" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(ad9f4acb-47ac-4699 > \-aa65-e542a59912e9) -- GET > /v1.40/containers/c519bbe7f21e7c01729d62237b819b84b3bf364784a115fa536ad45153224ffc/json > BEGIN" > abr 11 21:28:28 munster.belkin.home podman\[282\]: > time="2021-04-11T21:28:28-03:00" level=info
[Bug 1948339] perl-Log-Agent-1.005 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948339 --- Comment #2 from Upstream Release Monitoring --- the-new-hotness/release-monitoring.org's scratch build of perl-Log-Agent-1.005-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=65760386 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1948339] perl-Log-Agent-1.005 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948339 --- Comment #1 from Upstream Release Monitoring --- Created attachment 1771248 --> https://bugzilla.redhat.com/attachment.cgi?id=1771248=edit [patch] Update to 1.005 (#1948339) -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1948339] New: perl-Log-Agent-1.005 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948339 Bug ID: 1948339 Summary: perl-Log-Agent-1.005 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Log-Agent Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 1.005 Current version/release in rawhide: 1.004-1.fc35 URL: http://search.cpan.org/dist/Log-Agent/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/8292/ -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Podman and docker compose
Hi, I'm playing around with podman and docker compose, so I've read the post at https://www.redhat.com/sysadmin/podman-docker-compose. The example with Gitea does not work, this the output: sudo docker-compose up descargas_elasticsearch_1 is up-to-date Creating descargas_skydive-analyzer_1 ... error ERROR: for descargas_skydive-analyzer_1 Cannot create container for service skydive-analyzer: bad parameter: Link is not supported ERROR: for skydive-analyzer Cannot create container for service skydive-analyzer: bad parameter: Link is not supported ERROR: Encountered errors while bringing up the project. Am I doing something wrong? This is the log: abr 11 21:28:25 munster.belkin.home systemd[1]: Starting Podman API Service... abr 11 21:28:25 munster.belkin.home systemd[1]: Started Podman API Service. abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="/usr/bin/podman filtering at log level info" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network podman (typ e=bridge) at /etc/cni/net.d/87-podman-bridge.conflist" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network descargas_d efault (type=bridge) at /etc/cni/net.d/descargas_default.conflist" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network internet-mo nitoring_back-tier (type=bridge) at /etc/cni/net.d/internet-monitoring_back-tier.conflist" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network internet-mo nitoring_front-tier (type=bridge) at /etc/cni/net.d/internet-monitoring_front-tier.conflist" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="Setting parallel job count to 25" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="using systemd socket activati on to determine API endpoint" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="using API endpoint: ''" abr 11 21:28:25 munster.belkin.home podman[282]: time="2021-04-11T21:28:25-03:00" level=info msg="API server listening on \"/ru n/podman/podman.sock\"" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(87f3d612-9e67-4975 -a52d-e34f8f177998) -- GET /version BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(f6beda6a-42c3-414c -9d8c-0314e00c86d7) -- GET /v1.40/networks/descargas_default BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(60f23924-261e-41fd -9e14-459930ec3a0b) -- GET /v1.40/info BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(bd218869-1c22-4faf -878e-f2bffeaec753) -- GET /v1.40/networks/descargas_default BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(25b1c622-5f7d-47c6 -8d81-cf0f0a497a2f) -- GET /v1.40/containers/json?limit=-1=0=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(7af0b0a3-1e79-4f66 -8e4d-afe5f21a336d) -- GET /v1.40/containers/json?limit=-1=1=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(ad9f4acb-47ac-4699 -aa65-e542a59912e9) -- GET /v1.40/containers/c519bbe7f21e7c01729d62237b819b84b3bf364784a115fa536ad45153224ffc/json BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(000638a6-ac24-403b -81d2-a41f4ec0cde0) -- GET /v1.40/containers/json?limit=-1=1=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp ose.project%3Ddescargas%22%2C+%22com.docker.compose.service%3Delasticsearch%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D BEG IN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info msg="APIHandler(2f67caff-4f06-496f -8abe-f7c5c698d8a9) -- GET /v1.40/containers/c519bbe7f21e7c01729d62237b819b84b3bf364784a115fa536ad45153224ffc/json BEGIN" abr 11 21:28:28 munster.belkin.home podman[282]: time="2021-04-11T21:28:28-03:00" level=info
Re: Stepping down as Fedora Jam maintainer
I'd like to volunteer to pick up the Fedora Jam project and maintain it. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On Sun, Apr 11, 2021 at 4:29 PM Pete Batard wrote: > > On 2021.04.11 21:14, Robert Scheck wrote: > > On Sun, 11 Apr 2021, Neal Gompa wrote: > >> To be absolutely clear, I completely agree with everything here. > >> However, with GRUB being completely dysfunctional upstream and all the > >> pressure from everyone else basically doing nothing, I don't know what > >> else we're supposed to do. Outside of Fedora, I help maintain GRUB for > >> other distributions, and I wound up having no choice but to use the > >> Red Hat tree to get *any* maintained improvements. If there was any > >> light at the end of the tunnel, I would say my own suggestion is > >> completely ridiculous. > >> > >> However, the *major* reason for my suggestion to use the Red Hat tree > >> is that the Btrfs driver has the SUSE patches to be able to read and > >> boot from subvolumes, which are not upstream. > > > > I am sorry, but if some folks decide to run kind of a GRUB2 fork, then > > please do it either properly (e.g. by calling it an official fork and a > > separate project that might attract other projects as GRUB2 alternative), > > or get the changes into upstream. Staying close to upstream is a Fedora > > goal: https://fedoraproject.org/wiki/Staying_close_to_upstream_projects > > > > As long as EfiFs upstream only supports a non-forked GRUB2, I won't change > > my package except when being forced officially by FESCo to do so (in that > > case I will consider orphaning the package). > > > > Anyway, as long as systemd-boot upstream does not seem to care much about > > whether vfat XBOOTLDR is working at all (even an EfiFs driver is loaded by > > UEFI itself; their own internal UEFI driver loader is not yet implemented), > > a discussion about EfiFs using the Red Hat GRUB2 fork is IMHO unnecessary. > > I'm just going to add that, since I am patching GRUB in EfiFs anyway > (https://github.com/pbatard/efifs/blob/master/0001-GRUB-fixes.patch), > mostly to fix incompatibilities with EDK2 or MSVC, then if someone can > point me to the exact subset of commits you'd like to see applied, I > *may* look into adding a second GRUB patch into my repo, that adds the > changes required to address your issue (provided that these can be > condensed to a reasonable sized patch and don't require extensive rework). > > Considering that one must already apply one patch to the GRUB tree for > EfiFs compilation anyway, this might hopefully provide a compromise that > is good enough to satisfy everyone... > > But of course, I need to know what is the minimal subset of changes, > that Fedora's GRUB has, and that you need to see applied to EfiFs's GRUB. > You can see the commits here: https://github.com/rhboot/grub2/commits/fedora-35/grub-core/fs The commits applied by "martinezjavier" on March 22 are the only commits we have in grub-core/fs that's not in mainline GRUB2. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On Sun, 11 Apr 2021, Robert Scheck wrote: > Anyway, as long as systemd-boot upstream does not seem to care much about > whether vfat XBOOTLDR is working at all (even an EfiFs driver is loaded by > UEFI itself; their own internal UEFI driver loader is not yet implemented), > a discussion about EfiFs using the Red Hat GRUB2 fork is IMHO unnecessary. Sorry, I meant: [...] whether *non*-vfat XBOOTLDR is working [...] Regards, Robert pgpNYtVhIKdJV.pgp Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On Sun, 11 Apr 2021, Neal Gompa wrote: > To be absolutely clear, I completely agree with everything here. > However, with GRUB being completely dysfunctional upstream and all the > pressure from everyone else basically doing nothing, I don't know what > else we're supposed to do. Outside of Fedora, I help maintain GRUB for > other distributions, and I wound up having no choice but to use the > Red Hat tree to get *any* maintained improvements. If there was any > light at the end of the tunnel, I would say my own suggestion is > completely ridiculous. > > However, the *major* reason for my suggestion to use the Red Hat tree > is that the Btrfs driver has the SUSE patches to be able to read and > boot from subvolumes, which are not upstream. I am sorry, but if some folks decide to run kind of a GRUB2 fork, then please do it either properly (e.g. by calling it an official fork and a separate project that might attract other projects as GRUB2 alternative), or get the changes into upstream. Staying close to upstream is a Fedora goal: https://fedoraproject.org/wiki/Staying_close_to_upstream_projects As long as EfiFs upstream only supports a non-forked GRUB2, I won't change my package except when being forced officially by FESCo to do so (in that case I will consider orphaning the package). Anyway, as long as systemd-boot upstream does not seem to care much about whether vfat XBOOTLDR is working at all (even an EfiFs driver is loaded by UEFI itself; their own internal UEFI driver loader is not yet implemented), a discussion about EfiFs using the Red Hat GRUB2 fork is IMHO unnecessary. Regards, Robert pgpDynFpQIpTC.pgp Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: Debuginfod By Default (Self-Contained Change proposal)
On Sat, Apr 10, 2021 at 9:55 AM Michael Catanzaro wrote: > On Sat, Apr 10 2021 at 08:03:09 AM -0400, Owen Taylor > wrote: > > Did you notice that it also works for the Fedora Flatpaks (thanks, > > Frank!) - basic proof of concept: > > > > $ flatpak run --command=sh --filesystem=home --share=network --devel > > org.gnome.Aisleriot > > [ org.gnome.Aisleriot ~]$ > > DEBUGINFOD_URLS=https://debuginfod.stg.fedoraproject.org/ > > DEBUGINFOD_CACHE_PATH=~/.cache/debuginfod_client gdb /app/bin/sol > > > > (Without the --filesystem=home and DEBUGINFOD_CACHE_PATH, the cache > > ends up in ~/.var/app/org.gnome.Aisleriot/cache/debuginfod_client/) > > I think that's OK for a manual debugging workflow, since it's pretty > rare to want to do that under flatpak in my experience. Normally what's > most important to me is being able to easily generate a backtrace for a > previous crash using 'flatpak-coredumpctl'. Ideally > 'flatpak-coredumpctl' would handle setting the right environment > variables and executing flatpak with the right permissions to make it > work. (In the future, ABRT could do something similar.) > I think we could store the debuginfo urls in repository metadata (ostree summary / oci json index) and have flatpak automatically set things up for 'flatpak run --devel'. This isn't Fedora specific - e.g. there's an eventual goal to have a debuginfo server for Flathub as well. For coredump+debuginfod you can actually do the backtrace with a system (or toolbox) gdb instead of downloading the SDK ... if we want to deal with that complexity, we could add a mode like that into flatpak-coredumpctl. One gap here is that it's a little hard to figure out what exact revision of the Flatpak and runtime coredumped - you can reverse-engineer that out of COREDUMP_PROC_MOUNTINFO information in the journal. As you say, the eventual goal would be ABRT support. Regards, Owen ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-34-20210411.n.0 compose check report
Missing expected images: Minimal raw-xz armhfp Xfce raw-xz armhfp Failed openQA tests: 10/127 (aarch64), 11/189 (x86_64) New failures (same test not failed in Fedora-34-20210410.n.0): ID: 852529 Test: aarch64 Server-dvd-iso install_repository_hd_variation@uefi URL: https://openqa.fedoraproject.org/tests/852529 ID: 852532 Test: aarch64 Server-dvd-iso server_freeipa_replication_master@uefi URL: https://openqa.fedoraproject.org/tests/852532 ID: 852533 Test: aarch64 Server-dvd-iso server_freeipa_replication_replica@uefi URL: https://openqa.fedoraproject.org/tests/852533 ID: 852536 Test: aarch64 Server-dvd-iso server_role_deploy_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/852536 ID: 852541 Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi URL: https://openqa.fedoraproject.org/tests/852541 ID: 852548 Test: aarch64 Server-dvd-iso server_freeipa_replication_client@uefi URL: https://openqa.fedoraproject.org/tests/852548 ID: 852556 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi URL: https://openqa.fedoraproject.org/tests/852556 ID: 852560 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi URL: https://openqa.fedoraproject.org/tests/852560 ID: 852591 Test: x86_64 universal install_lvmthin URL: https://openqa.fedoraproject.org/tests/852591 ID: 852617 Test: x86_64 universal install_xfs@uefi URL: https://openqa.fedoraproject.org/tests/852617 ID: 852675 Test: aarch64 universal install_kickstart_user_creation@uefi URL: https://openqa.fedoraproject.org/tests/852675 Old failures (same test failed in Fedora-34-20210410.n.0): ID: 852416 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/852416 ID: 852417 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/852417 ID: 852420 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/852420 ID: 852429 Test: x86_64 Server-dvd-iso realmd_join_sssd URL: https://openqa.fedoraproject.org/tests/852429 ID: 852441 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/852441 ID: 852447 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/852447 ID: 852448 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/852448 ID: 852482 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/852482 ID: 852594 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/852594 ID: 852669 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/852669 Soft failed openQA tests: 4/189 (x86_64), 6/127 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-34-20210410.n.0): ID: 852405 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/852405 ID: 852446 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/852446 ID: 852503 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/852503 ID: 852509 Test: aarch64 Minimal-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/852509 ID: 852522 Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi URL: https://openqa.fedoraproject.org/tests/852522 ID: 852547 Test: aarch64 Server-dvd-iso install_vnc_client@uefi URL: https://openqa.fedoraproject.org/tests/852547 ID: 852562 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/852562 ID: 852584 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/852584 ID: 852643 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/852643 ID: 852698 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/852698 Passed openQA tests: 111/127 (aarch64), 173/189 (x86_64) New passes (same test not passed in Fedora-34-20210410.n.0): ID: 852695 Test: aarch64 universal support_server@uefi URL: https://openqa.fedoraproject.org/tests/852695 ID: 852707 Test: aarch64 universal install_kickstart_nfs@uefi URL: https://openqa.fedoraproject.org/tests/852707 ID: 852708 Test: aarch64 universal install_iscsi@uefi URL: https://openqa.fedoraproject.org/tests/852708 ID: 852710 Test: aarch64 universal install_pxeboot@uefi URL: https://openqa.fedoraproject.org/tests/852710 Installed system changes in test x86_64 Server-boot-iso install_default: System load changed from 0.15 to
Fedora-Rawhide-20210411.n.0 compose check report
Missing expected images: Minimal raw-xz armhfp Xfce raw-xz armhfp Compose FAILS proposed Rawhide gating check! 3 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 12/127 (aarch64), 15/189 (x86_64) New failures (same test not failed in Fedora-Rawhide-20210410.n.0): ID: 852209 Test: aarch64 Server-dvd-iso base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/852209 Old failures (same test failed in Fedora-Rawhide-20210410.n.0): ID: 852087 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/852087 ID: 852088 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/852088 ID: 852091 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/852091 ID: 852100 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING** URL: https://openqa.fedoraproject.org/tests/852100 ID: 852105 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/852105 ID: 852112 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/852112 ID: 852118 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/852118 ID: 852119 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/852119 ID: 852145 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/852145 ID: 852153 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/852153 ID: 852223 Test: aarch64 Server-dvd-iso modularity_tests@uefi URL: https://openqa.fedoraproject.org/tests/852223 ID: 852225 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/852225 ID: 852265 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/852265 ID: 852314 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/852314 ID: 852321 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/852321 ID: 852336 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/852336 ID: 852337 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/852337 ID: 852340 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/852340 ID: 852343 Test: aarch64 universal install_cyrillic_language@uefi URL: https://openqa.fedoraproject.org/tests/852343 ID: 852351 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/852351 ID: 852352 Test: aarch64 universal install_european_language@uefi URL: https://openqa.fedoraproject.org/tests/852352 ID: 852369 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/852369 ID: 852370 Test: aarch64 universal upgrade_minimal_64bit@uefi URL: https://openqa.fedoraproject.org/tests/852370 ID: 852372 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/852372 ID: 852382 Test: aarch64 universal upgrade_2_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/852382 ID: 852383 Test: aarch64 universal upgrade_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/852383 Soft failed openQA tests: 64/189 (x86_64), 46/127 (aarch64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-Rawhide-20210410.n.0): ID: 852083 Test: x86_64 Server-dvd-iso install_repository_hd_variation URL: https://openqa.fedoraproject.org/tests/852083 ID: 852114 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/852114 Old soft failures (same test soft failed in Fedora-Rawhide-20210410.n.0): ID: 852068 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/852068 ID: 852069 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/852069 ID: 852075 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/852075 ID: 852076 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/852076 ID: 852080 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/852080 ID: 852082 Test: x86_64 Server-dvd-iso install_vncconnect_server URL: https://openqa.fedoraproject.org/tests/852082 ID: 852084 Test: x86_64 Server-dvd-iso
[Bug 1948301] New: perl-Graphics-TIFF-10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948301 Bug ID: 1948301 Summary: perl-Graphics-TIFF-10 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Graphics-TIFF Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 10 Current version/release in rawhide: 9-1.fc35 URL: http://search.cpan.org/dist/Graphics-TIFF/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/15735/ -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-IoT-35-20210411.0 compose check report
Missing expected images: Iot dvd aarch64 Iot dvd x86_64 Failed openQA tests: 2/16 (x86_64), 6/15 (aarch64) Old failures (same test failed in Fedora-IoT-35-20210408.0): ID: 852726 Test: x86_64 IoT-dvd_ostree-iso base_services_start URL: https://openqa.fedoraproject.org/tests/852726 ID: 852728 Test: x86_64 IoT-dvd_ostree-iso iot_rpmostree_overlay URL: https://openqa.fedoraproject.org/tests/852728 ID: 852731 Test: aarch64 IoT-dvd_ostree-iso podman@uefi URL: https://openqa.fedoraproject.org/tests/852731 ID: 852732 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/852732 ID: 852735 Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_rebase@uefi URL: https://openqa.fedoraproject.org/tests/852735 ID: 852737 Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/852737 ID: 852741 Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_overlay@uefi URL: https://openqa.fedoraproject.org/tests/852741 ID: 852743 Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi URL: https://openqa.fedoraproject.org/tests/852743 Soft failed openQA tests: 1/16 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-IoT-35-20210408.0): ID: 852715 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/852715 Passed openQA tests: 13/16 (x86_64), 9/15 (aarch64) Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default@uefi: 1 services(s) added since previous compose: dbus-parsec.service Previous test data: https://openqa.fedoraproject.org/tests/849116#downloads Current test data: https://openqa.fedoraproject.org/tests/852714#downloads Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default_upload: 1 services(s) added since previous compose: dbus-parsec.service System load changed from 0.39 to 0.17 Previous test data: https://openqa.fedoraproject.org/tests/849118#downloads Current test data: https://openqa.fedoraproject.org/tests/852716#downloads Installed system changes in test aarch64 IoT-dvd_ostree-iso install_default_upload@uefi: 1 services(s) added since previous compose: dbus-parsec.service Previous test data: https://openqa.fedoraproject.org/tests/849747#downloads Current test data: https://openqa.fedoraproject.org/tests/852730#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b26bce013a chromium-89.0.4389.90-3.el8 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-58127424cd perl-Net-Netmask-2.0001-1.el8 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4ceb7b7897 libopenmpt-0.5.7-1.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-125be1ea97 perl-Net-CIDR-Lite-0.22-1.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d8aad094e9 singularity-3.7.3-1.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-aa018d2e2a clamav-0.103.2-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing seamonkey-2.53.7-3.el8 Details about builds: seamonkey-2.53.7-3.el8 (FEDORA-EPEL-2021-781b228611) Web browser, e-mail, news, IRC client, HTML editor Update Information: Appled all the changes from the upstream 2.53.7.1 update. Fixed tab opening in background and tab choosing on a tab close. Fix updating and support of legacy javascript extensions. Update to 2.53.7 Enable support for module scripts. (To turn it off, toggle "dom.moduleScripts.enabled" in about:config). For sending mail, now "Thunderbird" is advertised in User-Agent header instead of "Firefox" (if any). Some performance fixes, including from upcoming releases. ChangeLog: * Sat Apr 10 2021 Dmitry Butskoy 2.53.7-3 - better support obsoleting javascript stuff (mozbz#1702903) - fixed selection of tab to return on tab close (mozbz#1623054) - fixed opening tabs in background in some cases (mozbz#1619108) - provide a way to auto-select es-AR locale on any Spanish one but es-ES * Fri Apr 2 2021 Dmitry Butskoy 2.53.7-2 - fix obsoleting "for each" javascript statements support - no need to provide own dictionaries (system are used anyway) * Tue Mar 30 2021 Dmitry Butskoy 2.53.7-1 - update to 2.53.7 - fix keyboard input with gtk3 >= 3.24.26 (mozbz #1701288) - backport some refresh driver improvements from upcoming 2.53.8 - avoid spurious update of intersection observers in a case of throbber animation - restore traditional security-button background (to match the location bar highlighting, revert mozbz #1593550) - for new installs add about:addons to the initial pages and don't enable inspector and calendar there by default - enable upcoming module scripts support References: [ 1 ] Bug #1944532 - seamonkey-2.53.7.source is available https://bugzilla.redhat.com/show_bug.cgi?id=1944532 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On 11.04.2021 15:22, Nico Kadel-Garcia wrote:
So would "rpm -e". It's dangerous enough for the ordinary user to
remove those that I think it's worth keeping that protection in place.
The /etc/dnf/protected.d/{shim,grub2*}.conf files are part of the grub2*
and shim* packages. It is absolutely safe to remove them.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On 11.04.2021 03:12, Chris Murphy wrote: As far as I'm aware, the only two things preventing sd-boot from reading this directory is (a) this $BOOT currently doesn't have the proper Extended Boot Loader partition type GUID, (b) it's ext4 and out of the box the firmware can't read ext4. That's why I use ESP (EFI System Partition) to store kernels and BLS configs. After removing grub2*, kernel-install will start using /boot/efi/loader/entries directory and everything works fine. Installation manual: sudo dnf remove grubby grub2\* shim\* memtest86\* sudo rm -rf /boot/grub2 sudo rm -rf /boot/loader cat /proc/cmdline | cut -d ' ' -f 2- | sudo tee /etc/kernel/cmdline sudo chmod 644 /etc/kernel/cmdline sudo bootctl --path=/boot/efi install sudo kernel-install add $(uname -r) /lib/modules/$(uname -r)/vmlinuz -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Retiring from Perl maintenance
* Petr Pisar [09/04/2021 18:04] : > > Nevertheless, if you are interested to any of them, don't hesitate and contact > me and I will reassign them to you. I will gladly take ownership of the following: * perl-CGI-FastTemplate * perl-CGI-FormBuilder * perl-Dancer-Session-Cookie * perl-HTML-Escape * perl-HTML-FormatExternal * perl-HTML-FormFu-Element-reCAPTCHA * perl-HTML-FormFu-MultiForm * perl-HTML-HTML5-Entities * perl-HTML-HTML5-Parser * perl-HTML-HTML5-Sanity * perl-HTML-HTML5-Writer * perl-MooseX-ArrayRef * perl-MooseX-AttributeShortcuts * perl-MooseX-CoercePerAttribute * perl-MooseX-MarkAsMethods * perl-MooseX-Meta-TypeConstraint-Mooish * perl-MooseX-TraitFor-Meta-Class-BetterAnonClassNames * perl-MooseX-Types-DateTime-MoreCoercions * perl-MooseX-Util * perl-MooX-Struct * perl-MouseX-Foreign Emmanuel ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
在 2021-04-11星期日的 15:59 +0200，Vitaly Zaitsev via devel写道： > On 11.04.2021 03:19, Chris Murphy wrote: > > That condition is met by efifs, ergo by wrapping GRUB file system > > modules as EFI file system drivers. > > Is it possible to install such EFI filesystem drivers without > patching > UEFI BIOS? You are not **patching** UEFI, instead you just register a driver via efibootmgr. > > -- > Sincerely, > Vitaly Zaitsev (vit...@easycoding.org) > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-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/devel@lists.fedoraproje > ct.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure signature.asc Description: This is a digitally signed message part smime.p7s Description: S/MIME cryptographic signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a1ab6f9c4e libmediainfo-21.03-1.el7 libzen-0.4.39-1.el7 mediainfo-21.03-1.el7 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d0a9c2bf03 chromium-89.0.4389.90-3.el7 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-857a9f7853 openssl11-1.1.1g-3.el7 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-dda757d4a5 libopenmpt-0.5.7-1.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-93d78fa1a6 perl-Net-CIDR-Lite-0.22-1.el7 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f08dc6b4c1 gnuchess-6.2.7-5.el7 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-13ed778e19 singularity-3.7.3-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-3f9b6786f4 clamav-0.103.2-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing seamonkey-2.53.7-3.el7 Details about builds: seamonkey-2.53.7-3.el7 (FEDORA-EPEL-2021-9daa9fc0b1) Web browser, e-mail, news, IRC client, HTML editor Update Information: Appled all the changes from the upstream 2.53.7.1 update. Fixed tab opening in background and tab choosing on a tab close. Fix updating and support of legacy javascript extensions. Update to 2.53.7 Enable support for module scripts. (To turn it off, toggle "dom.moduleScripts.enabled" in about:config). For sending mail, now "Thunderbird" is advertised in User-Agent header instead of "Firefox" (if any). Some performance fixes, including from upcoming releases. ChangeLog: * Sat Apr 10 2021 Dmitry Butskoy 2.53.7-3 - better support obsoleting javascript stuff (mozbz#1702903) - fixed selection of tab to return on tab close (mozbz#1623054) - fixed opening tabs in background in some cases (mozbz#1619108) - provide a way to auto-select es-AR locale on any Spanish one but es-ES * Fri Apr 2 2021 Dmitry Butskoy 2.53.7-2 - fix obsoleting "for each" javascript statements support - no need to provide own dictionaries (system are used anyway) * Tue Mar 30 2021 Dmitry Butskoy 2.53.7-1 - update to 2.53.7 - fix keyboard input with gtk3 >= 3.24.26 (mozbz #1701288) - backport some refresh driver improvements from upcoming 2.53.8 - avoid spurious update of intersection observers in a case of throbber animation - restore traditional security-button background (to match the location bar highlighting, revert mozbz #1593550) - for new installs add about:addons to the initial pages and don't enable inspector and calendar there by default - enable upcoming module scripts support References: [ 1 ] Bug #1944532 - seamonkey-2.53.7.source is available https://bugzilla.redhat.com/show_bug.cgi?id=1944532 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On 11.04.2021 03:19, Chris Murphy wrote: That condition is met by efifs, ergo by wrapping GRUB file system modules as EFI file system drivers. Is it possible to install such EFI filesystem drivers without patching UEFI BIOS? -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On Sat, Apr 10, 2021 at 2:35 PM Vitaly Zaitsev via devel
wrote:
>
> On 10.04.2021 20:32, Matthew Miller wrote:
> > Protected doesn't mean that it's impossible to remove
>
> Problem: The operation would result in removing the following protected
> packages: grub2-efi-x64, grub2-pc, grub2-tools-minimal, shim-x64
> (try to add '--skip-broken' to skip uninstallable packages)
>
> > rm /etc/dnf/protected.d/{shim,grub2*}.conf
>
> It works, thanks.
So would "rpm -e". It's dangerous enough for the ordinary user to
remove those that I think it's worth keeping that protection in place.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Fedora 34 compose report: 20210411.n.0 changes
OLD: Fedora-34-20210410.n.0 NEW: Fedora-34-20210411.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: LXQt live x86_64 Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-34-20210410.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
Ordinarily, no. But in this case, since GRUB 2.06~rc1 is required to solve major critical vulnerabilities and it's very difficult to pull the patch set that fixes it (>115 patches!) backwards, GRUB got moved forward instead. GRUB 2.06~rc1 was pretty much released to release the patch set... got it. then will stick with v2.06, and try to get it re-patched for Xen @ the bug. thx. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On Sun, Apr 11, 2021 at 8:23 AM PGNet Dev wrote: > > tangentially related ... > > distro update on f33 from grub 2.04-release -> 2.06-rc (re)breaks Xen boot on > EFI. > > already reopened the original bug, but a question: > > is it normal/expected to push an *rc* (grub 2.06-rc, in this case), to > 'supported' fedora (33) *release*? > unreleased f34/rawhide I can understand. Ordinarily, no. But in this case, since GRUB 2.06~rc1 is required to solve major critical vulnerabilities and it's very difficult to pull the patch set that fixes it (>115 patches!) backwards, GRUB got moved forward instead. GRUB 2.06~rc1 was pretty much released to release the patch set... -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
tangentially related ... distro update on f33 from grub 2.04-release -> 2.06-rc (re)breaks Xen boot on EFI. already reopened the original bug, but a question: is it normal/expected to push an *rc* (grub 2.06-rc, in this case), to 'supported' fedora (33) *release*? unreleased f34/rawhide I can understand. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Grub 2 protected packages
On Sun, Apr 11, 2021 at 7:22 AM Pete Batard wrote: > > Hello all, > > On 2021.04.11 04:47, Chris Murphy wrote: > > On Sat, Apr 10, 2021 at 7:54 PM Robert Scheck > > wrote: > >> > >> On Sat, 10 Apr 2021, Neal Gompa wrote: > >>> We do have those packaged in Fedora: > >>> https://src.fedoraproject.org/rpms/efifs > > Interesting. I had no idea Fedora had an EfiFs package. > > >>> The GRUB2 sources being used as an input is wrong, though. > > I think there's a major issue with the GRUB2 maintainership being > reluctant to release, even when they are critical issues (such as > BootHole) that do warrant an immediate release. > > This is causing a lot of issues downstream, with distros maintaining > their own (incompatible) forks with cherry picked patches, and, I > believe, ultimately makes people reluctant to try to upstream anything, > because, even if their patch makes it into the git repo, it may > literally be years before it appears into a dot release. > > I mentioned this explicitly on the list > (https://lists.gnu.org/archive/html/grub-devel/2020-10/threads.html#00073), > but it looks like most people there don't seem to be of the opinion that > this is a major showstopper or that dot releases are that consequential > (which, ironically, may very well due to the fact that most distros > prefer working on their own fork rather than upstream). > > If GRUB2 was what I would call a functional project, there should be no > reason for Fedora or other distros to maintain their own fork (outside > of perhaps a few supplementary patches, that shouldn't impact much of > anything), as, as is the case with other projects, I would expect distro > maintainers to be able to reach a compromise with the upstream project > to ensure that it can satisfy their needs in a timely manner, without > the need for a custom distro specific fork. > > All this to say that, the GRUB2 being used might be "wrong", but this is > really a direct result of the GRUB2 project being dysfunctional in terms > of producing releases in a timely manner, and I'd rather see pressure > being put on the GRUB 2 project to improve things in that respect, than > go with the idea that trying to upstream the patches a distro might need > has now become essentially pointless, and therefore that having each > distro maintain a fork, with a large deviation from mainline, is an > acceptable practice... > > >>> It should > >>> be using the ones from the rhboot fork: > >>> https://github.com/rhboot/grub2/commits/fedora-35 > >> > >> I am sorry, but honestly I do not have much interest to use the Red Hat > >> grub2 fork, because efifs is patching the grub2 sources as part of its > >> build process - and I am in doubt that the Red Hat grub2 fork won't break > >> this (or something else). > > I second that. You can't just ask a project to go with a dependency that > isn't mainline. Instead, issues that introduce delays with mainline > getting required updates in a timely manner need to be addressed upfront. > > >> And if I would open Pandora's box, I wonder if > >> the efifs upstream maintainer (Cc-ed) is still going to support me further > >> in case of issues (especially if caused by the Red Hat grub2 fork) - Pete? > > To be blunt: Not in a million years. > > Because EfiFs is really a side project for me (I happened to need a > read-only UEFI NTFS driver at the time, so I crafted one by reusing the > GRUB source, and, as because it was relatively easy to do, added a bunch > of file systems I didn't really need), I can't justify investing that > much time onto it, and I already have some trouble finding enough time > to address some of the issues (sometime major, such as > https://github.com/pbatard/efifs/issues/27) that get reported. > > As such, if someone comes to me with "I'm using EfiFs with non mainline > GRUB 2.0", the first thing I'll tell them is to come back if they can > replicate the issue with mainline. > > > Strictly from the perspective of, who will provide support, I think we > > want to go directly to the upstreams as much as possible. When GRUB's > > file system modules get updates, they appear first upstream, and it'll > > just delay things to have to wait for Fedora's GRUB to be rebased to > > get those updates. > > Another good point. > > This is indeed a two way street: Some of the updates Fedora might want > may ultimately take time to appear upstream, which make it easy to want > to use the Fedora fork as the source, but some critical updates may also > appear in mainline, long before Fedora picks them up (especially if they > create integration conflicts with Fedora's own changes which becomes > more an more of a probability as a fork deviates from mainline). > To be absolutely clear, I completely agree with everything here. However, with GRUB being completely dysfunctional upstream and all the pressure from everyone else basically doing nothing, I don't know what else we're supposed to do. Outside of Fedora, I help maintain GRUB for
Re: Package downgrades from Fedora 33 -> Fedora 34 (including ostree + rpm-ostree)
On Sun, Apr 11, 2021 at 11:12 AM Kalev Lember wrote:
>
> On 4/10/21 8:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > On Sat, Apr 10, 2021 at 07:33:42PM +0200, Fabio Valentini wrote:
> >> - Would it be OK if I fix a few packages where there are missing
> >> *builds* for f34 as well?
> >> (Of course, only where it is obvious that the packager just forgot to
> >> merge the same changes that already happened on rawhide and f33
> >> branches.)
> >
> > +1
>
> Go for it, I say! And thanks for doing all of this.
>
>
> >> - Would it be OK if I file freeze exceptions for the bodhi updates
> >> that fix upgrade path, or is it fine if they are just 0day-updates?
> >> (Freeze-excepting packages that land on any images would probably be a
> >> good idea, but I don't know how to check that for individual
> >> packages.)
> >
> > 0day-updates should be enough.
>
> Agreed.
Great, less work for me. ;)
All cases where the missing build was an obvious oversight should be
fixed now, and the remaining issues should just be versioning mishaps
(e.g. bumped Release only on stable branch but not on F34 / Rawhide,
instead of appending .1 after %{?dist}).
Other than that, that leaves only a handful of package downgrades that
are caused by FTBFS issues on F34+.
I'll keep an eye on this, and re-run my checks after the current batch
of bodhi updates is pushed to the testing repos, but I think all "real
issues" should be fixed now (details below).
Fabio
---
- charliecloud-0:0.22-2.fc33 > charliecloud-0:0.21-2.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-0d811a26c1
- gecode-0:6.2.0-6.fc33 > gecode-0:6.2.0-5.fc34
Bumped release and rebuilt on f35 and f34 to account for koji snafu at
f34 branch point:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-c7bafa26a5
https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea8f4e12af
- klog-0:1.4.7-2.fc33 > klog-0:1.4.4-3.fc34
All dist-git branches had up-to-date commits, but update was only
built for F33 and F32.
So ... built, and update submitted F34:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-5677441800
- libreswan-0:4.3-1.fc33 > libreswan-0:4.2-1.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-51852f56bd
- mingw32-libusbx-0:1.0.24-1.fc33 > mingw32-libusbx-0:1.0.22-7.fc34
- mingw32-libusbx-static-0:1.0.24-1.fc33 >
mingw32-libusbx-static-0:1.0.22-7.fc34
- mingw64-libusbx-0:1.0.24-1.fc33 > mingw64-libusbx-0:1.0.22-7.fc34
- mingw64-libusbx-static-0:1.0.24-1.fc33 >
mingw64-libusbx-static-0:1.0.22-7.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-cd89a72b72
- nagios-plugins-nrpe-0:4.0.3-6.fc33 > nagios-plugins-nrpe-0:4.0.3-3.fc34
- nrpe-0:4.0.3-6.fc33 > nrpe-0:4.0.3-3.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-32c0a7f123
- nsd-0:4.3.5-1.fc33 > nsd-0:4.3.2-3.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-33fcb048ee
- python3-pyunicorn-0:0.6.1-2.fc33 > python3-pyunicorn-0:0.6.1-1.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-fcfaba6d79
- ydotool-0:0.2.0-5.fc33 > ydotool-0:0.2.0-4.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-857257f9aa
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Fedora rawhide compose report: 20210411.n.0 changes
OLD: Fedora-Rawhide-20210410.n.0 NEW: Fedora-Rawhide-20210411.n.0 = SUMMARY = Added images:0 Dropped images: 3 Added packages: 0 Dropped packages:0 Upgraded packages: 40 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 1.36 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 48.02 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Scientific vagrant-virtualbox x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20210410.n.0.x86_64.vagrant-virtualbox.box Image: Scientific vagrant-libvirt x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20210410.n.0.x86_64.vagrant-libvirt.box Image: Scientific_KDE live x86_64 Path: Labs/x86_64/iso/Fedora-Scientific_KDE-Live-x86_64-Rawhide-20210410.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: apitrace-10.0-1.fc35 Old package: apitrace-9.0-0.13.git590f2bb.fc34 Summary: Tools for tracing OpenGL RPMs: apitrace apitrace-gui apitrace-libs Size: 18.64 MiB Size change: 143.33 KiB Changelog: * Sat Apr 10 2021 Sandro Mani - 10.0-1 - Update to 10.0 Package: aqbanking-6.2.9-1.fc35 Old package: aqbanking-6.2.8-1.fc35 Summary: A library for online banking functions and financial data import/export RPMs: aqbanking aqbanking-devel Size: 7.25 MiB Size change: -2.35 KiB Changelog: * Fri Feb 26 2021 Vasiliy N. Glazov - 6.2.9-1 - Update to 6.2.9 Package: baresip-1.0.0-4.fc35 Old package: baresip-1.0.0-3.fc34 Summary: Modular SIP user-agent with audio and video support RPMs: baresip baresip-alsa baresip-cairo baresip-g722 baresip-g726 baresip-gsm baresip-gst baresip-gst_video baresip-gtk baresip-jack baresip-mpa baresip-mqtt baresip-opus baresip-plc baresip-portaudio baresip-pulse baresip-rst baresip-sdl baresip-sndfile baresip-speex_pp baresip-v4l2 baresip-vp8 baresip-vp9 baresip-x11 baresip-x11grab Size: 5.52 MiB Size change: 6.25 KiB Changelog: * Sun Apr 11 2021 Robert Scheck 1.0.0-4 - Rebuilt for libre 2.0.0 and librem 1.0.0 Package: ceph-2:16.2.0-2.fc35 Old package: ceph-2:16.2.0-1.fc35 Summary: User space components of the Ceph file system RPMs: ceph ceph-base ceph-common ceph-fuse ceph-grafana-dashboards ceph-immutable-object-cache ceph-mds ceph-mgr ceph-mgr-cephadm ceph-mgr-dashboard ceph-mgr-diskprediction-local ceph-mgr-k8sevents ceph-mgr-modules-core ceph-mgr-rook ceph-mon ceph-osd ceph-prometheus-alerts ceph-radosgw ceph-resource-agents ceph-selinux ceph-test cephadm cephfs-java cephfs-mirror cephfs-shell cephfs-top libcephfs-devel libcephfs2 libcephfs_jni-devel libcephfs_jni1 libcephsqlite libcephsqlite-devel librados-devel librados2 libradospp-devel libradosstriper-devel libradosstriper1 librbd-devel librbd1 librgw-devel librgw2 python3-ceph-argparse python3-ceph-common python3-cephfs python3-rados python3-rbd python3-rgw rados-objclass-devel rbd-fuse rbd-mirror rbd-nbd Size: 432.25 MiB Size change: 3.24 MiB Changelog: * Sat Apr 10 2021 Kaleb S. KEITHLEY - 2:16.2.0-2 - 16.2.0, libamqp_mock fix (FTBFS, #1947281), rgw fix Package: coreutils-8.32-22.fc35 Old package: coreutils-8.32-21.fc35 Summary: A set of basic GNU tools commonly used in shell scripts RPMs: coreutils coreutils-common coreutils-single Size: 18.67 MiB Size change: -76 B Changelog: * Fri Apr 09 2021 Kamil Dudka - 8.32-22 - weaken the dependency on glibc-doc to reduce minimal installations - drop the last use of ncurses no longer needed (#1830318) - utimens: fix confusing arg type in internal func Package: dummy-test-package-gloster-0-3369.fc35 Old package: dummy-test-package-gloster-0-3359.fc35 Summary: Dummy Test Package called Gloster RPMs: dummy-test-package-gloster Size: 209.61 KiB Size change: 607 B Changelog: * Sat Apr 10 2021 packagerbot - 0-3360 - rebuilt * Sat Apr 10 2021 packagerbot - 0-3361 - rebuilt * Sat Apr 10 2021 packagerbot - 0-3362 - rebuilt * Sat Apr 10 2021 packagerbot - 0-3363 - rebuilt * Sat Apr 10 2021 packagerbot - 0-3364 - rebuilt * Sat Apr 10 2021 packagerbot - 0-3365 - rebuilt * Sat Apr 10 2021 packagerbot - 0-3366 - rebuilt * Sat Apr 10 2021 packagerbot - 0-3367 - rebuilt * Sun Apr 11 2021 packagerbot - 0-3368 - rebuilt * Sun Apr 11 2021 packagerbot - 0-3369 - rebuilt Package: fluidsynth-2.1.8-1.fc35 Old package: fluidsynth-2.1.1-5.fc34 Summary: Real-time software synthesizer RPMs: fluidsynth fluidsynth-devel fluidsynth-libs Size: 3.41 MiB Size change: 21.92 KiB Changelog: * Sat Apr 10 2021 Christoph Karl - 2.1.8-1 - Update to 2.1.8 Package: gecode-6.2.0-7.fc35 Old package: gecode-6.2.0-6.fc34 Summary
Re: Retiring from Perl maintenance
Hi Petr, On Fri, 9 Apr 2021 18:04:34 +0200 Petr Pisar wrote: > V Tue, Apr 06, 2021 at 12:21:46PM +0200, Petr Pisar napsal(a): > > I found a different role in Red Hat which is incompatible with > > maintaining hundreds of packages. As a result, I will reassign my > > packages with a Red Hat's interrest to Michal Spacek (mspacek) who > > replaces me at Red Hat. > > I've just given 88 packages and 259 admin roles to mspacek. I wish > him happy days with their maintenance. > > > The rest of my packages will be orphaned and available for anyone > > to take. > > > The rest counts for 526 packages. Those are Fedora Perl packages I'm > the owner. The list is attached for your reference. > > I will retain them for some time to see how large work load they will > generate. According to a sample probe, an average year of my last > commit to them is 2016. If the workload will be larger than > negligable, I will orphan them and post a list on Fedora devel > mailing list. > > Nevertheless, if you are interested to any of them, don't hesitate > and contact me and I will reassign them to you. I'm happy to take the following: perl-Function-Parameters perl-Math-Random-MT-Auto perl-Object-InsideOut perl-Perl-Critic-Deprecated perl-Perl-Critic-Lax perl-Perl-Critic-Pulp perl-PPIx-QuoteLike perl-Sereal perl-Sereal-Decoder perl-Sereal-Encoder perl-Test-UseAllModules Good luck in your new role! Cheers, Paul. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-32-20210411.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-32-20210410.0): ID: 852055 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/852055 ID: 852062 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/852062 Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package downgrades from Fedora 33 -> Fedora 34 (including ostree + rpm-ostree)
On 4/10/21 8:46 PM, Zbigniew Jędrzejewski-Szmek wrote: On Sat, Apr 10, 2021 at 07:33:42PM +0200, Fabio Valentini wrote: - Would it be OK if I fix a few packages where there are missing *builds* for f34 as well? (Of course, only where it is obvious that the packager just forgot to merge the same changes that already happened on rawhide and f33 branches.) +1 Go for it, I say! And thanks for doing all of this. - Would it be OK if I file freeze exceptions for the bodhi updates that fix upgrade path, or is it fine if they are just 0day-updates? (Freeze-excepting packages that land on any images would probably be a good idea, but I don't know how to check that for individual packages.) 0day-updates should be enough. Agreed. -- Kalev ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-33-20210411.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-33-20210410.0): ID: 852041 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/852041 ID: 852048 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/852048 Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[389-devel] 389 DS nightly 2021-04-11 - 95% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2021/04/11/report-389-ds-base-2.0.4-20210411gite542902ae.fc33.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-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/389-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
