Re: Donate 1 minute of your time to test upgrades from F38 to F39
On Fri, Aug 25, 2023 at 09:08:23PM -0700, Samuel Sieb wrote: > No, it's a demonstration of applications that aren't being properly > maintained when they're still using functions that have been deprecated for > 6 releases which is also that many years. Python core is very stable. So... you're saying that the fact that *every* python release in the past decade carries backwards-incompatible core changes is somehow an indication of its "stability"? (If you want "stability" in python you have to pin absolutely everything in a per-applicaiton venv, including every [sub-]dependency and the interpreter version. And $deity help you if you need some relatively-bleeding-edge modules or have dependencies with conflicting version needs. I spent the majority of my time at $dayjob-1 keeping on top of the constant CI failures caused by the turtles-all-the-way-down dependencies changing out from under us) If you want a platform that is actually stable, take perl. They have an explicit policy of never breaking existing software even if it means carrying bugs forward indefinitely, and scripts/modules have to explicitly opt into behavioral changes. I have twenty-year-old perl scripts that still work just fine, but in my experience, even couple-years-old python code most likely won't. If perl is "write once, read nowhere" python is "write once, fix forever". /rant - Solomon -- Solomon Peachypizza at shaftnet dot org (email) @pizza:shaftnet dot org (matrix) Dowling Park, FL speachy (libra.chat) signature.asc 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
On 8/25/23 20:51, Solomon Peachy via devel wrote: On Fri, Aug 25, 2023 at 06:55:17PM -0700, Adam Williamson wrote: It's a lot of output, but not *so* many problems when you boil it down. Yeah, it's ultimately another example (or four) of how Python is utterly worthless as a "stable" application platform. No, it's a demonstration of applications that aren't being properly maintained when they're still using functions that have been deprecated for 6 releases which is also that many years. Python core is very stable. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
Only this errors, none of them look like real problems: Erro: Problema 1: problema com o pacote instalado telegram-desktop-4.8.4-3.fc38.x86_64 - telegram-desktop-4.8.4-3.fc38.x86_64 from @System does not belong to a distupgrade repository - nothing provides qt6-qtbase(x86-64) = 6.5.1 needed by telegram-desktop-4.8.4-2.fc39.x86_64 from rpmfusion-free Problema 2: problema com o pacote instalado igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System requires libprocps.so.8()(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora requires libprocps.so.8()(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora-modular requires libprocps.so.8()(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-modular requires libprocps.so.8()(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-testing-modular requires libprocps.so.8()(64bit), but none of the providers can be installed - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-testing-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be insta lled - procps-ng-3.3.17-11.fc38.x86_64 from @System does not belong to a distupgrade repository (tente adicionar '--skip-broken' para pular pacotes desinstaláveis) Em qua., 23 de ago. de 2023 às 15:23, Miroslav Suchý escreveu: > Do you want to make Fedora 39 better? Please spend 1 minute of your time > and try to run: > > # Run this only if you use default Fedora modules > # next time you run any DNF command default modules will be enabled again > sudo dnf module reset '*' > > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \ > --enablerepo=updates-testing \ > $(rpm -q fedora-repos-modular >/dev/null && echo > --enablerepo=updates-testing-modular) \ > --assumeno distro-sync > > > This command does not replace `dnf system-upgrade`, but it will reveal > potential problems. > > You may also run `dnf upgrade` before running this command. > > The `--assumeno` will just test the transaction, but does not make the > actual upgrade. > > > In case you hit dependency issues, please report it against the > appropriate package. > > Or against fedora-obsolete-packages if that package should be removed in > Fedora 39. Please check existing reports against fedora-obsolete-packages > first: > > https://red.ht/2kuBDPu > > and also there is already bunch of "Fails to install" (F39FailsToInstall) > reports: > > https://bugzilla.redhat.com/buglist.cgi?bug_id= > 2168845_id_type=anddependson=tvp_id=12486533 > > > Two notes: > > * you may want to run the same command with dnf5 to help test new dnf. > > * this command found zero issues on my personal system - great work all > everybody! > > > Thank you > Miroslav > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
On Fri, Aug 25, 2023 at 06:55:17PM -0700, Adam Williamson wrote: > It's a lot of output, but not *so* many problems when you boil it down. Yeah, it's ultimately another example (or four) of how Python is utterly worthless as a "stable" application platform. > I suppose we could just vendor asynchat and asyncore back into > fail2ban, but that feels pretty ugly. Maybe worth doing in extremis if > upstream can't get it ported before F39 Final, since I think fail2ban > is quite popular? Everything is important to someone, but I would think that fail2ban would result in some serious teeth-gnashing if it got dropped. - Solomon -- Solomon Peachypizza at shaftnet dot org (email) @pizza:shaftnet dot org (matrix) Dowling Park, FL speachy (libra.chat) signature.asc 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5120258393 ImageMagick-6.9.12.93-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing sasl-xoauth2-0.24-1.el8 Details about builds: sasl-xoauth2-0.24-1.el8 (FEDORA-EPEL-2023-8450c927fc) The xoauth2 plugin for cyrus-sasl Update Information: First package in Fedora (#2208250) ChangeLog: * Mon Aug 7 2023 Jakub Jelen - 0.24-1 - First package in Fedora (#2208250) References: [ 1 ] Bug #2208250 - Review Request: sasl-xoauth2 - a SASL plugin that enables client-side use of OAuth 2.0 https://bugzilla.redhat.com/show_bug.cgi?id=2208250 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2234803] Broken dependency for perl-IO-Interactive-tests
https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2023-46db0ae756 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-46db0ae756 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202234803%23c3 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2183997] perl-Math-BigInt-FastCalc-0.5014 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2183997 Fedora Update System changed: What|Removed |Added Resolution|RAWHIDE |ERRATA Fixed In Version|perl-Math-BigInt-FastCalc-0 |perl-Math-BigInt-FastCalc-0 |.501.400-1.fc39 |.501.400-1.fc39 ||perl-Math-BigInt-FastCalc-0 ||.501.400-1.fc38 --- Comment #3 from Fedora Update System --- FEDORA-2023-9254fef7a1 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2183997 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202183997%23c3 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
On Fri, 2023-08-25 at 20:32 -0400, Solomon Peachy via devel wrote: > On Wed, Aug 23, 2023 at 08:22:42PM +0200, Miroslav Suchý wrote: > > Do you want to make Fedora 39 better? Please spend 1 minute of your time > > and try to run: > > I ran this on a bunch of my fleet, lots of problems, and they all seem > to be related to the Python 3.12 bump. It's a lot of output, but not *so* many problems when you boil it down. A lot of it is fail2ban, which is not working with Python 3.12 because it uses asynchat , which has been removed in Python 3.12: https://docs.python.org/3.12/whatsnew/3.12.html#removed Upstream is aware of this and working on it, but it's not done yet: https://github.com/fail2ban/fail2ban/issues/3487 so, there's not much we can do about this, unless we want to write the port for them. (Not me! I don't volunteer!) I suppose we could just vendor asynchat and asyncore back into fail2ban, but that feels pretty ugly. Maybe worth doing in extremis if upstream can't get it ported before F39 Final, since I think fail2ban is quite popular? openocd seems to not be building ATM: https://bugzilla.redhat.com/show_bug.cgi?id=2226064 I think this is likely due to libgpiod getting a major bump (from 1.6 to 2.0). There's an upstream ticket on this: https://sourceforge.net/p/openocd/tickets/306/ but last update from upstream was in 2021. pbrobinson pinged it in March with no response. Again not much we can do here unless we want to do the porting work for upstream. PyDrive was retired nine months ago: https://src.fedoraproject.org/rpms/PyDrive/c/17c7af2339900db6584b15b89c0be88a2853cfd5?branch=rawhide it probably needs to be obsoleted as part of https://bugzilla.redhat.com/show_bug.cgi?id=2233409 . I've added a comment there. python-pathtools is FTBFS: https://bugzilla.redhat.com/show_bug.cgi?id=2226277 because it uses the imp module that was removed in Python 3.12. This is a pretty common case, we've fixed several packages for this, but not this one yet. It's using it for something pretty stupid, so I've done an equally stupid patch to fix it: https://bodhi.fedoraproject.org/updates/FEDORA-2023-9235b56665 There's some discussion about async-generator here: https://bugzilla.redhat.com/show_bug.cgi?id=2220121 seems it may get retired (which would mean we'd need to obsolete it). matrix-synapse has a bunch of test suite failures, it looks like: https://kojipkgs.fedoraproject.org//work/tasks/8799/104998799/build.log upstream seem to be working on this: https://github.com/matrix-org/synapse/pull/16099 so I guess the next version or so might succeed, or the maintainer could bump to 1.91.0rc1 and backport that PR if they're really keen... I *think* that's everything in your list. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
On Wed, Aug 23, 2023 at 08:22:42PM +0200, Miroslav Suchý wrote: > Do you want to make Fedora 39 better? Please spend 1 minute of your time and > try to run: I ran this on a bunch of my fleet, lots of problems, and they all seem to be related to the Python 3.12 bump. F38 Workstation #1: Problem 1: problem with installed package openocd-0.12.0-2.fc38.x86_64 - openocd-0.12.0-2.fc38.x86_64 from @System does not belong to a distupgrade repository - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from fedora - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from fedora-modular - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from updates-modular - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from updates-testing-modular Problem 2: package python3-PyDrive-1.3.1-21.fc37.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed - python3-3.11.4-1.fc38.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-PyDrive-1.3.1-21.fc37.noarch Problem 3: problem with installed package python3-pathtools-0.1.2-30.fc38.noarch - package python3-pathtools-0.1.2-30.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed - python3-libs-3.11.4-1.fc38.x86_64 from @System does not belong to a distupgrade repository Problem 4: problem with installed package python3-devel-3.11.4-1.fc38.x86_64 - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System - problem with installed package python3-async-generator-1.10-16.fc38.noarch - package python3-async-generator-1.10-16.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed - package python3-async-generator-1.10-16.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed - package python3-async-generator-1.10-16.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-async-generator-1.10-16.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-async-generator-1.10-16.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed - python3-devel-3.11.4-1.fc38.x86_64 from @System does not belong to a distupgrade repository F38 Workstation #2: Problem 1: problem with installed package python3-pathtools-0.1.2-30.fc38.noarch - package python3-pathtools-0.1.2-30.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-pathtools-0.1.2-30.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed - python3-3.11.4-1.fc38.x86_64 from @System does not belong to a distupgrade repository Problem 3: problem with installed package python3-async-generator-1.10-16.fc38.noarch - package python3-async-generator-1.10-16.fc38.noarch from @System
[Test-Announce] 2023-08-28 @ 16:00 UTC - Fedora 39 Blocker Review Meeting
# F39 Blocker Review meeting # Date: 2023-08-28 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have a huge list of proposals (8 proposed blockers, 22 proposed FEs) to review, so let's have a meeting on Monday. It would be **REALLY APPRECIATED** if folks can vote in tickets over the weekend so we don't have to have a marathon meeting! See a bit further down for instructions. If you have time tonight, 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 F39 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Missing boot options - who is to blame?
Hi, On 8/25/23 22:05, Alexander Ploumistos wrote: > On Fri, Aug 25, 2023 at 7:27 PM Hans de Goede wrote: >> >> If there is a /etc/kernel/cmdline file then that will be used >> for the generated /boot/loader/entries/*.conf files. >> >> (I was recently bitten by this myself) > > Yes, there is and its contents are those of the problematic > /boot/loader/entries/*.conf files. Should I delete it? I think that if you delete it the contents of new entries will be grabbed from /proc/cmdline of the running kernel (I think). Alternatively you can put the cmdline which you actually want inside that file. That is what I've done to fix a similar issue. > # rpm -qf /etc/kernel/cmdline > file /etc/kernel/cmdline is not owned by any package > > Where does it come from? I think it is generated by grubby, not sure why / when though. Regards, Hans ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Missing boot options - who is to blame?
On Fri, Aug 25, 2023 at 7:27 PM Hans de Goede wrote: > > If there is a /etc/kernel/cmdline file then that will be used > for the generated /boot/loader/entries/*.conf files. > > (I was recently bitten by this myself) Yes, there is and its contents are those of the problematic /boot/loader/entries/*.conf files. Should I delete it? # rpm -qf /etc/kernel/cmdline file /etc/kernel/cmdline is not owned by any package Where does it come from? ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On 8/25/23 20:24, Richard Hughes wrote: > On Fri, 25 Aug 2023 at 16:00, Benson Muite wrote: >> Better as optional rather than default-enabled. It would likely be >> helpful for computers in an institutional setting where the LAN is well >> controlled. > > So that's the thing; if it's default disabled then I can say with > certainty that almost nobody will use it and we won't see any > reduction in network traffic at all. a) The default time for checking for updates can be increased. b) In some places, internet access is charged per byte downloaded, so there will be quite some interest in local caching, and an easy to use Squid Proxy replacement ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
That sounds very good, and having a libs package desirable anyway should more consumers pop up On 25.08.23 20:43, Richard Hughes wrote: On Fri, 25 Aug 2023 at 19:34, Richard Hughes wrote: Yes, that's what I have right now. I do need to split out a passim-libs so that you can remove the daemon and just leave the tiny client library. Something like this perhaps? diff --git a/passim.spec b/passim.spec index bc51e57..3ad7ccc 100644 --- a/passim.spec +++ b/passim.spec @@ -21,10 +21,18 @@ BuildRequires: systemd-rpm-macros BuildRequires: systemd >= %{systemd_version} Requires: glib2%{?_isa} >= %{glib2_version} +Requires: %{name}-libs%{?_isa} = %{version}-%{release} %description Passim is a daemon that allows software to share files on your local network. +%package libs +Summary: Local caching server library + +%description libs +libpassim is a library that allows software to share files on your local network +using the passimd daemon. + %package devel Summary: Development package for %{name} Requires: %{name}%{?_isa} = %{version}-%{release} @@ -69,12 +77,15 @@ appstream-util validate-relax --nonet %{buildroot}%{_metainfodir}/*.metainfo.xml %{_datadir}/dbus-1/system-services/org.freedesktop.Passim.service %{_datadir}/icons/hicolor/scalable/apps/org.freedesktop.Passim.png %{_datadir}/metainfo/org.freedesktop.Passim.metainfo.xml -%{_libdir}/libpassim.so.1* %{_libdir}/girepository-1.0/Passim-1.0.typelib %{_libexecdir}/passimd %{_mandir}/man1/passim.1* %{_unitdir}/passim.service +%files libs +%license LICENSE +%{_libdir}/libpassim.so.1* + %files devel %{_datadir}/gir-1.0/Passim-1.0.gir %dir %{_includedir}/passim-1 ...then fwupd would hard depend on passim-libs (automatically, via the shared library use) and would "recommend" passim (the daemon) -- so the latter could be easily removed. Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 19:34, Richard Hughes wrote: > Yes, that's what I have right now. I do need to split out a > passim-libs so that you can remove the daemon and just leave the tiny > client library. Something like this perhaps? diff --git a/passim.spec b/passim.spec index bc51e57..3ad7ccc 100644 --- a/passim.spec +++ b/passim.spec @@ -21,10 +21,18 @@ BuildRequires: systemd-rpm-macros BuildRequires: systemd >= %{systemd_version} Requires: glib2%{?_isa} >= %{glib2_version} +Requires: %{name}-libs%{?_isa} = %{version}-%{release} %description Passim is a daemon that allows software to share files on your local network. +%package libs +Summary: Local caching server library + +%description libs +libpassim is a library that allows software to share files on your local network +using the passimd daemon. + %package devel Summary: Development package for %{name} Requires: %{name}%{?_isa} = %{version}-%{release} @@ -69,12 +77,15 @@ appstream-util validate-relax --nonet %{buildroot}%{_metainfodir}/*.metainfo.xml %{_datadir}/dbus-1/system-services/org.freedesktop.Passim.service %{_datadir}/icons/hicolor/scalable/apps/org.freedesktop.Passim.png %{_datadir}/metainfo/org.freedesktop.Passim.metainfo.xml -%{_libdir}/libpassim.so.1* %{_libdir}/girepository-1.0/Passim-1.0.typelib %{_libexecdir}/passimd %{_mandir}/man1/passim.1* %{_unitdir}/passim.service +%files libs +%license LICENSE +%{_libdir}/libpassim.so.1* + %files devel %{_datadir}/gir-1.0/Passim-1.0.gir %dir %{_includedir}/passim-1 ...then fwupd would hard depend on passim-libs (automatically, via the shared library use) and would "recommend" passim (the daemon) -- so the latter could be easily removed. Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 19:26, Marcus Müller wrote: > I fully agree with that assessment. "Here's a knob you turn that has the > potential to make > your firmware update 2s faster and is generally good for the ecosystem, but > you will have > set it on every machine you set up" will not lead to significant deployment. Agree. > Question: I presume you only want to share the metadata, and never downloaded > fw images, > right? I think for phase 1 that's completely correct. > If that's the case, it'd alleviate a lot of the privacy concerns I'd have > with my > laptop sharing with a campus network all of the devices for which I've lately > downloaded > firmware. There are concerns with sharing firmware, I totally agree. It's non-free software (which you have permission to redistribute, but still unpalatable for many) -- the compromise I've done for people changing the default to "metadata,firmware" is that you need to reboot into the new firmware before the published firmware gets shared; on the logic that you don't want to advertise to the world that you're currently running insecure firmware. > Can I suggest we make this at most a "Recommends:" dependence for fwupd in > any case, so > that one might uninstall passim without disabling fwupd? Yes, that's what I have right now. I do need to split out a passim-libs so that you can remove the daemon and just leave the tiny client library. > I'd actually love if I knew of a way my fedora containers could automagically > find > local package and metadata sources. Knowing that "change dnf to pull data from > mDNS-announced sources *by default*" is a big change, flying the fwupd > balloon first seems > very attractive to me. Yup, totally agree. I think it's a nice self contained test that if successful we could extend out to DNF metadata and other container-y stuff. Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
Hi Richard, On 25.08.23 19:24, Richard Hughes wrote: So that's the thing; if it's default disabled then I can say with certainty that almost nobody will use it and we won't see any reduction in network traffic at all. I fully agree with that assessment. "Here's a knob you turn that has the potential to make your firmware update 2s faster and is generally good for the ecosystem, but you will have set it on every machine you set up" will not lead to significant deployment. Question: I presume you only want to share the metadata, and never downloaded fw images, right? If that's the case, it'd alleviate a lot of the privacy concerns I'd have with my laptop sharing with a campus network all of the devices for which I've lately downloaded firmware. Can I suggest we make this at most a "Recommends:" dependence for fwupd in any case, so that one might uninstall passim without disabling fwupd? I'm wondering a bit whether you might be reinventing something that the cloud ops folks already have as "service recovery compatible cache" or something? Feels like if I pull up a lot of docker containers which in turn start fetching data, I'd want to have a happy fallover mechanism in case some main repository for some artifacts goes down. Or, maybe, this is a common problem? I, for one, find myself working with mock and on containers for my small CI network, and I get to download a lot of package metadata a lot of times, same for packages, and I don't want to modify the base layers to use my local repo mirror (not am I inclined to set up such). I'd actually love if I knew of a way my fedora containers could automagically find local package and metadata sources. Knowing that "change dnf to pull data from mDNS-announced sources *by default*" is a big change, flying the fwupd balloon first seems very attractive to me. Best, Marcus ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
hyperkitty update
Move mailman to newer release of Fedora or CentOS https://pagure.io/fedora-infrastructure/issue/8455 https://gitlab.com/mailman/hyperkitty It looks like a good amount of work is already done on this. Nice job! ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Heads-up: updating usd (OpenUSD) from 23.05 to 23.08 in Rawhide and F39
In one week, 2023-09-01, I plan to update the usd package (OpenUSD) from 23.05 to 23.08 [1][2] in Rawhide/F40 and in F39. There are only very minor API changes, but the ABI is incompatible and the SONAME version is bumped. I will rebuild the sole dependent package, blender, in a side tag for each release. Anyone further updating Blender in F39 during the Beta Freeze should re-use the same side tag, or at least tag in the USD 23.08 build to a new side tag. Let me know if you are planning such an update, and I’ll be happy to answer questions or take care of the builds myself. [1] https://src.fedoraproject.org/rpms/usd/pull-request/12 [2] https://github.com/PixarAnimationStudios/OpenUSD/blob/v23.08/CHANGELOG.md#2308---2023-07-21 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 15:59, Peter Robinson wrote: > Is this something where you could enable it on one specific device and > have a systemd time to pull the metadata and it advertises it to the > network so you can designate a single device to run the service? Yes, not a bad idea at all. Can you file it as an issue https://github.com/hughsie/passim/issues and I'll get to this next week. Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 16:27, Stephen Smoogen wrote: > It depends on the scanning from ports open to unknown shared files to 'why > did our network costs go up so much?' Surely if you're on a local network with bandwidth costs you'd turn off avahi or lock down the firewall? Lots of stuff blasts out mDNS traffic these days. > Going from other things it has been a way to inject bad packages, bad > metadata, mass system slowdowns across a fleet, using the service on N > systems as a DDOS against third parties (which they then charge fees for), > etc. All good things to document in the README, thanks. I think it helps that if you're on a LAN with 25 machines all offering the same file we choose one *at random* so if there's one bad actor we don't degrade things for everybody all at the same time. And the fallback for "someone on my LAN has given me garbage" is "fall back to the CDN" anyway. > chained flaw in say a compression routine which 'should never happen with > legitimate data'.) Agree. I'm less worried about this one as the first thing we do is compare the SHA-256 checksum, and the next is check the signature using GnuTLS. I'll update the README with some of those points next week, thanks. Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Missing boot options - who is to blame?
Hi, On 8/25/23 17:53, Alexander Ploumistos wrote: > Hello, > > On one of my computers, for the last couple of kernel updates I'm not > getting the proper options in the corresponding *.conf files in > /boot/loader/entries. Some of the options specified in > /etc/default/grub are there, but anything related to the root > partition and some other options are consistently being left out, > which results in a machine unable to boot, until I manually add the > uuids and everything else that's missing. > In the past I knew that grubby took care of these things, but some > rather recent threads here have suggested this is no longer the case. > Against which component should I file a bug report? It's an F38, > Workstation edition. If there is a /etc/kernel/cmdline file then that will be used for the generated /boot/loader/entries/*.conf files. (I was recently bitten by this myself) Regards, Hans ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 16:00, Benson Muite wrote: > Better as optional rather than default-enabled. It would likely be > helpful for computers in an institutional setting where the LAN is well > controlled. So that's the thing; if it's default disabled then I can say with certainty that almost nobody will use it and we won't see any reduction in network traffic at all. Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2234803] Broken dependency for perl-IO-Interactive-tests
https://bugzilla.redhat.com/show_bug.cgi?id=2234803 --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2023-46db0ae756 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-46db0ae756 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202234803%23c2 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2234803] Broken dependency for perl-IO-Interactive-tests
https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Petr Pisar changed: What|Removed |Added Fixed In Version||perl-IO-Interactive-1.025-1 ||.el7.1 Status|ASSIGNED|MODIFIED -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2234803 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
On Thu, Aug 24, 2023 at 11:08:14PM +0200, Sandro wrote: ...snip... > > I see. Could some sysadmin with supercow powers insert a tag globally? Or > would that be treading on a great many toes? We looked at adding some 'standard' tags, but they would need to be added to each package seperately. So, 30,000+ things per tag. It didn't seem worth the churn. When/if we move to some other setup, having some standard tags seems like a nice idea though. kevin signature.asc 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Missing boot options - who is to blame?
Hello, On one of my computers, for the last couple of kernel updates I'm not getting the proper options in the corresponding *.conf files in /boot/loader/entries. Some of the options specified in /etc/default/grub are there, but anything related to the root partition and some other options are consistently being left out, which results in a machine unable to boot, until I manually add the uuids and everything else that's missing. In the past I knew that grubby took care of these things, but some rather recent threads here have suggested this is no longer the case. Against which component should I file a bug report? It's an F38, Workstation edition. Thank you, A. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2234803] Broken dependency for perl-IO-Interactive-tests
https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED Doc Type|--- |If docs needed, set a value --- Comment #1 from Petr Pisar --- Thanks for the report. This is a bug in my packaging. An upstream increased a minimal version of Test::More without a reason. I reverted in list of build-time dependencies, but forgot do the same in a list of run-time dependencies. And because EPEL build system does not have automatic installation test, it slipped through the cracks. I will fix it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202234803%23c1 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 10:31, Richard Hughes wrote: > On Fri, 25 Aug 2023 at 13:19, Stephen Smoogen wrote: > > My understanding was that Microsoft found their own 'share updates' not > working as much as expected > > Hmm, I heard the opposite; can you give any more info? They have way > No, I only have some chatter from sysadmins at enterprise sites who had to deal with audits, failed updates, and being told to turn it off to fix them. So let's just assume I am talking to too many cranky old sysadmins and I believed their fish stories too much. > more telemetry than we do, and I was told it would not "be feasible" > to continue WU without the peer-to-peer functionality built into > windows. According to them they even have some kind of IPv6 tunnel > thing going on which seems alarming if true. > > either by network scans > > As in "port 27500 exists you have a security problem" kind of scans? > > It depends on the scanning from ports open to unknown shared files to 'why did our network costs go up so much?' > > or just the fact that as soon as someone puts up a service like this.. > it is profitable for the crooks to abuse it. > > Probably my naivety, but what kind of things did you have in mind? > > The following are just things I have seen from blackhat/defcon over the years and criminal gang stories. I don't expect (m)any of them may be related to passim, but most of the time the problems are with a protocol/service which says "Here we've assuming your local network (aka LAN) is a nice and friendly place, without evil people trying to overwhelm your system or feed you fake files." So when I read that these days, I get anxious. Going from other things it has been a way to inject bad packages, bad metadata, mass system slowdowns across a fleet, using the service on N systems as a DDOS against third parties (which they then charge fees for), etc. The bad packages are more of a problem because of stolen keys being used to sign something. The 'onion' layers of protection that might have been in place is that you get updates on that from a subset of 'secure' places. Instead now, this could be any system which presents the signed data on a distributed service which says its legitimate. [And depending on the P2P, it can be that like cockroaches the bad data will keep popping up and spreading so you need to make sure you have somewhere else a blacklist to remove things.. though you need to make sure that blacklist can't be manipulated also.] Mass slowdowns are where you find that the sharing does some sort of scan which can somehow be overloaded in some sort of CPU or disk usage loop (this is usually a chained flaw in say a compression routine which 'should never happen with legitimate data'.) DDOS are where the metadata being shared points everyone to download something from some place which isn't expecting it. [Or some packet lookup that the P2P service expects] > Richard. > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On 8/25/23 14:42, Richard Hughes wrote: > Hi all, > > I was thinking of adding Passim as a default-installed and > default-enabled dep of fwupd in the Fedora 40 release. Before I create > lots of unnecessary drama, is there any early feedback on what's > described in https://github.com/hughsie/passim/blob/main/README.md > please. > Better as optional rather than default-enabled. It would likely be helpful for computers in an institutional setting where the LAN is well controlled. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, Aug 25, 2023 at 12:43 PM Richard Hughes wrote: > > Hi all, > > I was thinking of adding Passim as a default-installed and > default-enabled dep of fwupd in the Fedora 40 release. Before I create > lots of unnecessary drama, is there any early feedback on what's > described in https://github.com/hughsie/passim/blob/main/README.md > please. > > The tl;dr: is I want to add a mDNS server that reshares the public > firmware update metadata from the LVFS on your LAN. The idea is that > rather than 25 users in an office downloading the same ~2MB file from > the CDN every day, the first downloads from the CDN and the other 24 > download from the first machine. All machines still download the > [tiny] jcat file from the CDN still so we know the SHA256 to search > for and verify. > > The backstory is that as the fwupd grows and grows (to ChromeOS, > FreeBSD, Windows and macOS) we need to scale things up a couple of > orders of magnitude. This isn't specific to firmware stuff, although I > think it makes a great testcase which we could add dnf or ostree > content to in the future. Comments and questions are most welcome. > Thanks, Is this something where you could enable it on one specific device and have a systemd time to pull the metadata and it advertises it to the network so you can designate a single device to run the service? ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 13:19, Stephen Smoogen wrote: > My understanding was that Microsoft found their own 'share updates' not > working as much as expected Hmm, I heard the opposite; can you give any more info? They have way more telemetry than we do, and I was told it would not "be feasible" to continue WU without the peer-to-peer functionality built into windows. According to them they even have some kind of IPv6 tunnel thing going on which seems alarming if true. > either by network scans As in "port 27500 exists you have a security problem" kind of scans? > or just the fact that as soon as someone puts up a service like this.. it is > profitable for the crooks to abuse it. Probably my naivety, but what kind of things did you have in mind? Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, Aug 25, 2023, at 7:42 AM, Richard Hughes wrote: > Hi all, > > I was thinking of adding Passim as a default-installed and > default-enabled dep of fwupd in the Fedora 40 release. Before I create > lots of unnecessary drama, is there any early feedback on what's > described in https://github.com/hughsie/passim/blob/main/README.md > please. Since this isn't really Fedora specific I started https://github.com/hughsie/passim/discussions/7 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 13:50, Petr Pisar wrote: > I see you wrote "metadata". It's not the firmware itself .Sill my concert is > the same: what's a license of the metada? Can I redistribute them? The metadata is explicitly CC0-1.0 -- but even if we later did firmware one of the things I negotiated with the vendors uploading firmware to the LVFS was that we have the transferable permission to redistribute the firmware -- which is how big companies can "mirror the entire LVFS" when servers have no internet access. Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2234803] New: Broken dependency for perl-IO-Interactive-tests
https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Bug ID: 2234803 Summary: Broken dependency for perl-IO-Interactive-tests Product: Fedora EPEL Version: epel7 Status: NEW Component: perl-IO-Interactive Assignee: ppi...@redhat.com Reporter: ed.abdulli...@gmail.com QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Hello! I tried to install "perl-IO-Interactive-tests" package from epel-7 repository, but it failed with the following error: Problem 1: conflicting requests - nothing provides perl(Test::More) >= 1 needed by perl-IO-Interactive-tests-1.025-1.el7.noarch [root@localhost ~]# dnf repoquery --whatprovides "perl(Test::More)" Last metadata expiration check: 0:07:13 ago on Tue 22 Aug 2023 01:32:45 AM EDT. perl-Test-Simple-0:0.98-243.el7.noarch [root@localhost ~]# dnf repoquery --provides perl-Test-Simple Last metadata expiration check: 0:08:31 ago on Tue 22 Aug 2023 01:32:45 AM EDT. perl(Test::Builder) = 0.98 perl(Test::Builder::IO::Scalar) = 2.110 perl(Test::Builder::Module) = 0.98 perl(Test::Builder::Tester) = 1.22 perl(Test::Builder::Tester::Color) = 1.22 perl(Test::Builder::Tester::Tie) perl(Test::More) = 0.98 perl(Test::Simple) = 0.98 perl-Test-Simple = 0.98-243.el7 perl-Test-Simple-tests = 0.98-243.el7 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2234803 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202234803%23c0 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 39 compose report: 20230825.n.0 changes
OLD: Fedora-39-20230824.n.0 NEW: Fedora-39-20230825.n.0 = SUMMARY = Added images:0 Dropped images: 0 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 = = 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
V Fri, Aug 25, 2023 at 12:42:34PM +0100, Richard Hughes napsal(a): > The tl;dr: is I want to add a mDNS server that reshares the public > firmware update metadata from the LVFS on your LAN. I see you wrote "metadata". It's not the firmware itself .Sill my concert is the same: what's a license of the metada? Can I redistribute them? -- Petr signature.asc 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
On Sun, 2023-08-20 at 12:19 +0200, Miroslav Suchý wrote: > Over the time we had several workshops about SPDX. Some people did > the SPDX migrations for others (me included). From file https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final-maintainers.txt I retrieve packages with my fas user and adapt one script to mass update my packages https://github.com/sergiomb2/herlper_scripts/blob/main/fedora/license-invalid-as-spdx.sh But I still have these to commit [1], the question is can you generate all PR(s) for trivial licenses (automatically) ? Thank you [1] dh-make - can be trivially converted to GPL-3.0-or-later docker-compose - can be trivially converted to Apache-2.0 dvdauthor - can be trivially converted to GPL-2.0-or-later fedora-dockerfiles - can be trivially converted to GPL-2.0-only fedora-review-plugin-java - can be trivially converted to GPL-2.0-or- later frei0r-plugins - can be trivially converted to GPL-2.0-or-later gammu - can be trivially converted to GPL-2.0-or-later ganyremote - can be trivially converted to GPL-3.0-or-later golang-github-containerd-aufs - can be trivially converted to Apache- 2.0 golang-github-containerd-btrfs - can be trivially converted to Apache- 2.0 golang-github-containerd-imgcrypt - can be trivially converted to Apache-2.0 golang-github-mitchellh-cli - can be trivially converted to MPL-2.0 google-gson - can be trivially converted to Apache-2.0 jdependency - can be trivially converted to Apache-2.0 kanyremote - can be trivially converted to GPL-3.0-or-later keychain - can be trivially converted to GPL-2.0-only libkgapi - can be trivially converted to GPL-2.0-or-later libprojectM - can be trivially converted to GPL-2.0-or-later libsmbios - can be trivially converted to GPL-2.0-or-later OR OSL-2.1 megaglest - can be trivially converted to GPL-3.0-or-later AND GPL-1.0- or-later movit - can be trivially converted to GPL-2.0-or-later pdfbox - can be trivially converted to Apache-2.0 perl-File-FcntlLock - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl perl-Git-Wrapper - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl perl-Mail-Box - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl perl-Mail-Transport-Dbx - can be trivially converted to GPL-2.0-or- later AND ( GPL-1.0-or-later OR Artistic-1.0-Perl ) perl-Object-Realize-Later - can be trivially converted to GPL-1.0-or- later OR Artistic-1.0-Perl perl-User-Identity - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl platform - can be trivially converted to GPL-2.0-or-later po-debconf - can be trivially converted to GPL-2.0-or-later po4a - can be trivially converted to GPL-1.0-or-later python-apt - can be trivially converted to GPL-2.0-or-later python-gammu - can be trivially converted to GPL-2.0-or-later python-html2text - can be trivially converted to GPL-3.0-only python-libnacl - can be trivially converted to Apache-2.0 rawstudio - can be trivially converted to GPL-2.0-or-later redhat-lsb - can be trivially converted to GPL-2.0-only smb4k - can be trivially converted to GPL-2.0-or-later tetrinetx - can be trivially converted to GPL-2.0-only ufraw - can be trivially converted to GPL-2.0-or-later usb_modeswitch - can be trivially converted to GPL-2.0-or-later vid.stab - can be trivially converted to GPL-2.0-or-later webalizer - can be trivially converted to GPL-2.0-or-later -- Sérgio M. B. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding Passim as a Fedora 40 feature?
On Fri, 25 Aug 2023 at 07:44, Richard Hughes wrote: > Hi all, > > I was thinking of adding Passim as a default-installed and > default-enabled dep of fwupd in the Fedora 40 release. Before I create > lots of unnecessary drama, is there any early feedback on what's > described in https://github.com/hughsie/passim/blob/main/README.md > please. > > The tl;dr: is I want to add a mDNS server that reshares the public > firmware update metadata from the LVFS on your LAN. The idea is that > rather than 25 users in an office downloading the same ~2MB file from > the CDN every day, the first downloads from the CDN and the other 24 > download from the first machine. All machines still download the > [tiny] jcat file from the CDN still so we know the SHA256 to search > for and verify. > > I am not sure how much this will actually help things. My understanding was that Microsoft found their own 'share updates' not working as much as expected and causing way too many security headaches even on 'nice friendly networks' either by network scans or just the fact that as soon as someone puts up a service like this.. it is profitable for the crooks to abuse it. I am not against it, but I think the days of "Here we've assuming your local network (aka LAN) is a nice and friendly place, without evil people trying to overwhelm your system or feed you fake files." is dead and whatever tool applied needs to be designed with the fact that it only takes 0.01% of 'evil people' in the population to make things crap. > The backstory is that as the fwupd grows and grows (to ChromeOS, > FreeBSD, Windows and macOS) we need to scale things up a couple of > orders of magnitude. This isn't specific to firmware stuff, although I > think it makes a great testcase which we could add dnf or ostree > content to in the future. Comments and questions are most welcome. > Thanks, > > Richard. > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
On Fri, Aug 25, 2023 at 1:28 PM Leigh Scott wrote: > > Hi Leigh, > > > > On Fri, Aug 25, 2023 at 10:03 AM Leigh Scott > > wrote: > > > > > > As I'm on my laptop again, I was able to try to run the rebase again and > > for Philip it was about rpmfusion-nonfree-updates, but I'm hitting: > > > > error: Updating rpm-md repo 'rpmfusion-free-updates': cannot update repo > > 'rpmfusion-free-updates': Cannot prepare internal mirrorlist: Status > code: > > 404 for > > > https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-. > .. > > (IP: 78.47.223.143); Last error: Status code: 404 for > > > https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-. > .. > > (IP: 158.69.60.128) > > > > Tom > > I will need to get the mirrormanager admin to add updates for f39 even > though it's unused until fedora final release. > Can you disable repos on silverblue? > Yes, one can disable them by editing the files under /etc/yum.repos.d. I'm not that worried about myself, but rather about others. But to confirm disabling them works. Tom ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230825.n.0 changes
OLD: Fedora-Rawhide-20230824.n.0 NEW: Fedora-Rawhide-20230825.n.0 = SUMMARY = Added images:2 Dropped images: 3 Added packages: 5 Dropped packages:1 Upgraded packages: 70 Downgraded packages: 0 Size of added packages: 3.61 MiB Size of dropped packages:661.70 KiB Size of upgraded packages: 3.64 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 26.06 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Sericea dvd-ostree x86_64 Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230825.n.0.iso Image: i3 live aarch64 Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-Rawhide-20230825.n.0.iso = DROPPED IMAGES = Image: LXQt live aarch64 Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20230824.n.0.iso Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230824.n.0.iso Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230824.n.0.iso = ADDED PACKAGES = Package: gogextract-0^20161009git6601b32-1.fc40 Summary: Script for unpacking GOG Linux installers RPMs:gogextract Size:9.18 KiB Package: passim-0.1.1-1.fc40 Summary: Local caching server RPMs:passim passim-devel Size:890.03 KiB Package: pianobar-2022.04.01-6.fc40 Summary: Console-based client for Pandora RPMs:pianobar pianobar-devel pianobar-libs Size:373.95 KiB Package: rust-annotate-snippets-0.9.1-1.fc40 Summary: Library for building code annotations RPMs:rust-annotate-snippets+color-devel rust-annotate-snippets+default-devel rust-annotate-snippets+yansi-term-devel rust-annotate-snippets-devel Size:67.86 KiB Package: rust-libheif-sys-1.16.1-2.fc40 Summary: Libheif bindings RPMs:rust-libheif-sys+default-devel rust-libheif-sys+use-bindgen-devel rust-libheif-sys-devel Size:2.30 MiB = DROPPED PACKAGES = Package: deepin-network-utils-5.4.13-4.fc38 Summary: Deepin desktop-environment - network utils RPMs:deepin-network-utils deepin-network-utils-devel Size:661.70 KiB = UPGRADED PACKAGES = Package: awscli2-2.13.12-1.fc40 Old package: awscli2-2.13.11-1.fc40 Summary: Universal Command Line Environment for AWS, version 2 RPMs: awscli2 Size: 11.70 MiB Size change: -948 B Changelog: * Thu Aug 24 2023 Packit - 2.13.12-1 - [packit] 2.13.12 upstream release Package: bacula-13.0.3-3.fc40 Old package: bacula-13.0.3-2.fc39 Summary: Cross platform network backup for Linux, Unix, Mac and Windows RPMs: bacula-client bacula-common bacula-console bacula-console-bat bacula-devel bacula-director bacula-libs bacula-libs-sql bacula-logwatch bacula-storage bacula-traymonitor nagios-plugins-bacula Size: 22.12 MiB Size change: -15.26 KiB Changelog: * Wed Aug 16 2023 Yaakov Selkowitz - 13.0.3-3 - Disable Qt components in RHEL builds Package: binutils-2.41-4.fc40 Old package: binutils-2.41-3.fc40 Summary: A GNU collection of binary utilities RPMs: binutils binutils-devel binutils-gold binutils-gprofng Size: 68.76 MiB Size change: -67.71 KiB Changelog: * Wed Aug 23 2023 Nick Clifton - 2.41-4 - Add fixes for linker testsuite failures for the RISCV-64 target. Package: boxes-2.2.1-1.fc40 Old package: boxes-2.2.0-3.fc39 Summary: Command line ASCII boxes unlimited! RPMs: boxes boxes-vim Size: 345.23 KiB Size change: -545 B Changelog: * Thu Aug 24 2023 Artem Polishchuk - 2.2.1-1 - chore(update): 2.2.1 Package: cmake-3.27.4-1.fc40 Old package: cmake-3.27.3-1.fc40 Summary: Cross-platform make system RPMs: cmake cmake-data cmake-doc cmake-filesystem cmake-gui cmake-rpm-macros Size: 61.50 MiB Size change: -41.88 KiB Changelog: * Thu Aug 24 2023 Bj??rn Esser - 3.27.4-1 - cmake-3.27.4 Fixes rhbz#2233852 Package: cppunit-1.15.1-17.fc40 Old package: cppunit-1.15.1-16.fc39 Summary: C++ unit testing framework RPMs: cppunit cppunit-devel cppunit-doc Size: 34.15 MiB Size change: 3.60 KiB Changelog: * Thu Aug 24 2023 Mattia Verga - 1.15.1-17 - Backport patch to run tests in deterministic order Package: dietlibc-0.34-15.fc40 Old package: dietlibc-0.34-13.fc39 Summary: Small libc implementation RPMs: dietlibc dietlibc-devel Size: 2.56 MiB Size change: -285.40 KiB Changelog: * Wed Jul 19 2023 Fedora Release Engineering - 0.34-14 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Thu Aug 24 2023 Gwyn Ciesla - 0.34-15 - Fix FTBFS Package: elfutils-0.189-6.fc40 Old package: elfutils-0.189-4.fc39 Summary: A collection of utilities and DSOs to handle ELF files and DWARF data RPMs: elfutils elfutils-debuginfod elfutils-debuginfod-client elfutils-debuginfod-client-devel elfutils-default-yama-scope elfutils-devel elfutils-libelf
Adding Passim as a Fedora 40 feature?
Hi all, I was thinking of adding Passim as a default-installed and default-enabled dep of fwupd in the Fedora 40 release. Before I create lots of unnecessary drama, is there any early feedback on what's described in https://github.com/hughsie/passim/blob/main/README.md please. The tl;dr: is I want to add a mDNS server that reshares the public firmware update metadata from the LVFS on your LAN. The idea is that rather than 25 users in an office downloading the same ~2MB file from the CDN every day, the first downloads from the CDN and the other 24 download from the first machine. All machines still download the [tiny] jcat file from the CDN still so we know the SHA256 to search for and verify. The backstory is that as the fwupd grows and grows (to ChromeOS, FreeBSD, Windows and macOS) we need to scale things up a couple of orders of magnitude. This isn't specific to firmware stuff, although I think it makes a great testcase which we could add dnf or ostree content to in the future. Comments and questions are most welcome. Thanks, Richard. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
> Hi Leigh, > > On Fri, Aug 25, 2023 at 10:03 AM Leigh Scott wrote: > > > As I'm on my laptop again, I was able to try to run the rebase again and > for Philip it was about rpmfusion-nonfree-updates, but I'm hitting: > > error: Updating rpm-md repo 'rpmfusion-free-updates': cannot update repo > 'rpmfusion-free-updates': Cannot prepare internal mirrorlist: Status code: > 404 for > https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-... > (IP: 78.47.223.143); Last error: Status code: 404 for > https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-... > (IP: 158.69.60.128) > > Tom I will need to get the mirrormanager admin to add updates for f39 even though it's unused until fedora final release. Can you disable repos on silverblue? ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2229718] perl-Mozilla-CA-20230821 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2229718 --- Comment #8 from Michal Josef Spacek --- Changes: 20230821 - Update from Mozilla repository to 2023-08-21 - Added certificates: - Atos TrustedRoot Root CA ECC TLS 2021 sha256: b2fae53e14ccd7ab9212064701ae279c1d8988facb775fa8a008914e663988a8 - Atos TrustedRoot Root CA RSA TLS 2021 sha256: 81a9088ea59fb364c548a6f85559099b6f0405efbf18e5324ec9f457ba00112f - SSL.com TLS ECC Root CA 2022 sha256: c32ffd9f46f936d16c3673990959434b9ad60aafbb9e7cf33654f144cc1ba143 - SSL.com TLS RSA Root CA 2022 sha256: 8faf7d2e2cb4709bb8e0b33666bf75a5dd45b5de480f8ea8d4bfe6bebc17f2ed - Sectigo Public Server Authentication Root E46 sha256: c90f26f0fb1b4018b7519b5ca2b53e2ca5b3be5cf18efe1bef47380c5383 - Sectigo Public Server Authentication Root R46 sha256: 7bb647a62aeeac88bf257aa522d01ffea395e0ab45c73f93f65654ec38f25a06 - Removed certificates: - E-Tugra Global Root CA ECC v3 sha256: 873f4685fa7f563625252e6d36bcd7f16fc24951f264e47e1b954f4908cdca13 - E-Tugra Global Root CA RSA v3 sha256: ef66b0b10a3cdb9f2e3648c76bd2af18ead2bfe6f117655e28c4060da1a3f4c2 Only for rawhide, bump to last version. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2229718 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202229718%23c8 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[rpms/perl-Mozilla-CA] PR #5: 20230821 bump
mspacek merged a pull-request against the project: `perl-Mozilla-CA` that you are following. Merged pull-request: `` 20230821 bump `` https://src.fedoraproject.org/rpms/perl-Mozilla-CA/pull-request/5 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[rpms/perl-Mozilla-CA] PR #5: 20230821 bump
mspacek opened a new pull-request against the project: `perl-Mozilla-CA` that you are following: `` 20230821 bump `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Mozilla-CA/pull-request/5 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
Hi Leigh, On Fri, Aug 25, 2023 at 10:03 AM Leigh Scott wrote: > Those warnings should disappear once the 39 release rpm's are installed. > I have fixed the missing repodata for the unused updates repo's. > As I'm on my laptop again, I was able to try to run the rebase again and for Philip it was about rpmfusion-nonfree-updates, but I'm hitting: error: Updating rpm-md repo 'rpmfusion-free-updates': cannot update repo 'rpmfusion-free-updates': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-39=x86_64 (IP: 78.47.223.143); Last error: Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-39=x86_64 (IP: 158.69.60.128) Tom ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Self Introduction: Adam Piasecki
Hello Robert, Cześć Dominik! Now I am overwhelmed - it was indeed an absolute pleasure to meet you in person at Flock '23 (Cork). Looking forward to the next one :) ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[rpms/perl-Mozilla-CA] PR #4: 20230807 bump
mspacek merged a pull-request against the project: `perl-Mozilla-CA` that you are following. Merged pull-request: `` 20230807 bump `` https://src.fedoraproject.org/rpms/perl-Mozilla-CA/pull-request/4 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[rpms/perl-Mozilla-CA] PR #4: 20230807 bump
mspacek opened a new pull-request against the project: `perl-Mozilla-CA` that you are following: `` 20230807 bump `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Mozilla-CA/pull-request/4 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Self Introduction: Adam Piasecki
Cześć, Adam! On Thursday, 24 August 2023 at 15:48, Adam Piasecki wrote: [...] > Here's to many fruitful discussions! Welcome to Fedora! It was an excellent opportunity to meet you in person at Flock. Regards, Dominik -- Fedora https://fedoraproject.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2234337] perl-DBD-Pg-3.17.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2234337 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA Fixed In Version||perl-DBD-Pg-3.17.0-1.fc40 Last Closed||2023-08-25 09:07:35 --- Comment #2 from Fedora Update System --- FEDORA-2023-6414f7ef88 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2234337 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202234337%23c2 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2234337] perl-DBD-Pg-3.17.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2234337 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-6414f7ef88 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6414f7ef88 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2234337 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202234337%23c1 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
Those warnings should disappear once the 39 release rpm's are installed. I have fixed the missing repodata for the unused updates repo's. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Warning: DNF is unprotected
Am Fr., 25. Aug. 2023 um 08:21 Uhr schrieb Adam Williamson : > > On Thu, 2023-08-24 at 21:23 +0200, Tomasz Torcz wrote: > > On Thu, Aug 24, 2023 at 07:39:07PM +0200, Robert-André Mauchin wrote: > > > Hello, > > > > > > Just a heads-up: for the upgrade to DNF5 in F39, we unprotected the DNF > > > package, which leaves all of our users vulnerable to a removal of DNF. > > > > > > > > > We have one affected user here: > > > https://bsd.network/@claudiom/110944941506724767 > > > > Not just on, #fedora-qa: > > 101441 I've just notice my rawhide system is without `dnf` > > command, and this ling dnf-automatic timers do not work. There is `dnf5` > > command available, though > > That's likely not the result of lack of protection, but just of running > Rawhide. If you ran Rawhide through the period when dnf5 was made the > provider of /usr/bin/dnf , then you didn't automatically get dnf > installed back when you updated to the post-revert versions. This is by > design, or rather, it's unfortunate but it would be rather icky to try > and 'fix' it, so folks decided not to. You're expected to be able to do > 'dnf5 install dnf' if you run Rawhide and want it back. Not really. On my Fedora 38 with updates, `/etc/dnf/protected.d/dnf.conf` looks like this: ``` # DNF is obsoleted in Fedora 39 by DNF 5 and should no longer be marked as protected. # dnf ``` It's the result of an update on 05/23 (or just before) which unprotected dnf, protected python3-dnf and with the following diff in dnf related packages: ``` -dnf-data,noarch,dnf-data-4.15.0-1.fc38 -dnf,noarch,dnf-4.15.0-1.fc38 -dnf-plugins-core,noarch,dnf-plugins-core-4.4.0-1.fc38 -dnf-utils,noarch,dnf-utils-4.4.0-1.fc38 +dnf-data,noarch,dnf-data-4.15.1-1.fc38 +dnf,noarch,dnf-4.15.1-1.fc38 +dnf-plugins-core,noarch,dnf-plugins-core-4.4.1-1.fc38 +dnf-utils,noarch,dnf-utils-4.4.1-1.fc38 -libdnf,x86_64,libdnf-0.70.0-1.fc38 +libdnf,x86_64,libdnf-0.70.1-1.fc38 -python3-dnf,noarch,python3-dnf-4.15.0-1.fc38 -python3-dnf-plugins-core,noarch,python3-dnf-plugins-core-4.4.0-1.fc38 +python3-dnf,noarch,python3-dnf-4.15.1-1.fc38 +python3-dnf-plugins-core,noarch,python3-dnf-plugins-core-4.4.1-1.fc38 -python3-libdnf,x86_64,python3-libdnf-0.70.0-1.fc38 +python3-libdnf,x86_64,python3-libdnf-0.70.1-1.fc38 -yum,noarch,yum-4.15.0-1.fc38 +yum,noarch,yum-4.15.1-1.fc38 ``` [Yes, I store this info redantly on purpose for easy diffing/splitting.] Currently my dnf is at dnf-4.16.2-1.fc38.noarch, config is unchanged, and it would happily remove itself. (I also installed dnf5 recently, it didn't change that config and is not aliased.) Michael ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Broken Discrete/Dedicated GPU support
> On Mon, Aug 14, 2023 at 7:59 PM Michael Catanzaro > > It looks like these fdo / non-GNOME projects would need new homes / > maintainers: > > - power-profiles-daemon > - switcheroo-control > - iio-sensor-proxy > - low-memory-monitor > > Looks like they are *all* installed by default in Fedora Workstation. > So it would likely be a good idea if *somebody* took them over ... > I'm not saying I'm volunteering though - I can write decent Rust code, > but C scares me, especially the GObject kind ;) > > Fabio This is a bit worrying. I consider power-profiles-daemon to be an important piece of Fedora Workstation on laptops. I haven't programmed in C in years and this would essentially be my first contribution to such low-level software so I'd need someone to guide me. If someone is willing to provide guidance and or supervision I could try working on power-profiles-daemon. ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Warning: DNF is unprotected
On Thu, 2023-08-24 at 21:23 +0200, Tomasz Torcz wrote: > On Thu, Aug 24, 2023 at 07:39:07PM +0200, Robert-André Mauchin wrote: > > Hello, > > > > Just a heads-up: for the upgrade to DNF5 in F39, we unprotected the DNF > > package, which leaves all of our users vulnerable to a removal of DNF. > > > > > > We have one affected user here: > > https://bsd.network/@claudiom/110944941506724767 > > Not just on, #fedora-qa: > 101441 I've just notice my rawhide system is without `dnf` command, > and this ling dnf-automatic timers do not work. There is `dnf5` command > available, though That's likely not the result of lack of protection, but just of running Rawhide. If you ran Rawhide through the period when dnf5 was made the provider of /usr/bin/dnf , then you didn't automatically get dnf installed back when you updated to the post-revert versions. This is by design, or rather, it's unfortunate but it would be rather icky to try and 'fix' it, so folks decided not to. You're expected to be able to do 'dnf5 install dnf' if you run Rawhide and want it back. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
Hi Leigh, On Thu, Aug 24, 2023 at 7:26 PM Leigh Scott wrote: > > just a note rpmfusion free and nofree not ready > > > > > > What do you mean? > I branched rpmfusion two week ago, the repo deps look fine to me. > See the reply from Philip Rhoades - I've hit the same on Silverblue when trying to rebase it to Fedora 39: Errors during downloading metadata for repository 'rpmfusion-nonfree-updates': - Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo=nonfree-fedora-updates-released-39=x86_64 (IP: 158.69.60.128) - Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo=nonfree-fedora-updates-released-39=x86_64 (IP: 78.47.223.143) Error: Failed to download metadata for repo 'rpmfusion-nonfree-updates': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.rpmfusion.org/metalink?repo= nonfree-fedora-updates-released-39=x86_64 (IP: 78.47.223.143) Ignoring repositories: rpmfusion-nonfree-updates Tom ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue