[EPEL-devel] retiring caddy in EPEL 7
Per policy [0], this is an announcement that I intend to retire the caddy package in EPEL 7. This package is in a bit of a weird state. The version in the EPEL 7 repo is currently 1.0.3, which was released upstream on 2019-08-14. Upstream development on v1 stopped with the release of 1.0.5 on 2020-02-28. Recently I updated the package from 1.0.3 to 1.0.5 to bring it as current as possible without breaking changes. At the same time I updated a bundled library to resolve CVE-2022-3064 [1], and also expected that rebuilding it with a newer golang would resolve CVE-2022-41717 [2]. I published this update [3] to the testing repo with the intention of testing it myself, but life got in the way and it was promoted to stable before I had a chance to. I also forgot that while I had enabled the test suite in Fedora, I did not have it enabled in the epel7 branch. Unfortunately, I discovered that the binary in this package would core dump immediately and was completely non-functional. As a quick partial mitigation, I asked RelEng to untag the broken build to revert the repository back to the previous build [4]. After investigating the problem, and consulting with upstream, I believe that it is simply not possible to build a working caddy v1 binary with golang 1.19 (the version currently available EPEL 7). Caddy is rather sensitive to the version of golang that it is built with, both for the minimum version, and as I discovered during this ordeal, the maximum version as well. I considered doing an incompatible update to bring the EPEL 7 package to a version of caddy that works with golang 1.19, but ultimately decided against it. It would be a very disruptive incompatible update because the config file format changed drastically between v1 and v2. With a mere ten months left before EPEL 7's retirement, I do not believe it is worth the effort or disruption to do such an incompatible update. Due to the outstanding CVEs, and the inability to even rebuild the package, I think the best course of action is to just retire it. Per policy, I will take this action in one week. As an alternative, the upstream project maintains a Copr repository [5][6] that provides the latest version, even for RHEL 7. This will still be a disruptive update from caddy v1 to v2, but users can opt-in to it at their own pace if they are unable/unwilling to migrate away from RHEL 7 yet. Caddy is also available in EPEL 9, and will be available in EPEL 8 soon [7], so upgrading to RHEL 8 or 9 is another possible route if users are ready to migrate their OS. [0] https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/#process_security_reasons [1] https://nvd.nist.gov/vuln/detail/CVE-2022-3064 [2] https://nvd.nist.gov/vuln/detail/CVE-2022-41717 [3] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-284c34a6cc [4] https://pagure.io/releng/issue/11606 [5] https://caddyserver.com/docs/install#fedora-redhat-centos [6] https://copr.fedorainfracloud.org/coprs/g/caddy/caddy/ [7] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-0b57e19163 -- Carl George ___ 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
Re: Planning to update to podofo-0.10.1 + review request for podofo-compat for legacy 0.9.x library
Sent from my Samsung Galaxy Watch Original message From: Jason Tibbitts j...@tib.bs Date: 16/08/2023 06:58 (GMT+02:00) To: Sandro Mani manisan...@gmail.com Cc: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: Re: Planning to update to podofo-0.10.1 + review request for podofo-compat for legacy 0.9.x library null null___ 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: Planning to update to podofo-0.10.1 + review request for podofo-compat for legacy 0.9.x library
> Sandro Mani writes: > To keep these functional, I've prepared a podofo-compat package with > the previous 0.9.x library. The review request is here [2]. Happy to > review in exchange. Note that it's not necessary to go through the review process for multiple versions of packages like this, providing they are named correctly according to https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple We don't use "compat" in the name but instead just something like podofo0.9. To import a package like that, you just do fedpkg request-repo with the "--exception" flag. One of the SCM admins will need to approve it but I try to do that relatively often. - J< ___ 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 2229408] perl-Perl-Metrics-Simple-1.0.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2229408 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Perl-Metrics-Simple-1. |perl-Perl-Metrics-Simple-1. |0.3-1.fc39 |0.3-1.fc39 |perl-Perl-Metrics-Simple-1. |perl-Perl-Metrics-Simple-1. |0.3-1.fc37 |0.3-1.fc37 ||perl-Perl-Metrics-Simple-1. ||0.3-1.fc38 --- Comment #7 from Fedora Update System --- FEDORA-2023-466006d8ef 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=2229408 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202229408%23c7 ___ 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 2227333] perl-Perl-Metrics-Simple-1.0.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2227333 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Perl-Metrics-Simple-1. |perl-Perl-Metrics-Simple-1. |0.2-1.fc39 |0.2-1.fc39 |perl-Perl-Metrics-Simple-1. |perl-Perl-Metrics-Simple-1. |0.3-1.fc37 |0.3-1.fc37 ||perl-Perl-Metrics-Simple-1. ||0.3-1.fc38 --- Comment #11 from Fedora Update System --- FEDORA-2023-466006d8ef 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=2227333 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202227333%23c11 ___ 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: webkit2gtk4.0 and javascriptcoregtk4.0 subpackages to be dropped
On Tue, 2023-08-15 at 19:52 -0500, Michael Catanzaro wrote: > Hi, > > Since Fedora 39 has been branched, it's now time to remove the > webkit2gtk4.0 (and javascriptcoregtk4.0) subpackages from rawhide to > implement the Fedora 40 change proposal: > > https://fedoraproject.org/wiki/Changes/Remove_webkit2gtk-4.0_API_Version > > A reminder that webkit2gtk4.0 provides WebKitGTK for applications that > use GTK 3 and libsoup 2. The migration path is to switch to > webkit2gtk4.1, which contains no API changes but links to libsoup 3 > instead of libsoup 2. All applications that still depend on both > WebKitGTK and libsoup 2 [1] will break until fixed. For info (this is from F39, but should be pretty much right): [adamw@xps13a fedora_openqa (main %)]$ sudo dnf repoquery --whatrequires webkit2gtk4.0 apostrophe-1:2.6.3-8.fc39.noarch apvlv-0:0.4.0-4.fc39.x86_64 balsa-0:2.6.4-3.fc39.x86_64 bookworm-0:1.1.3-0.10.20200414git.c7c3643.fc39.x86_64 claws-mail-plugins-fancy-0:4.1.1-9.fc39.x86_64 ephemeral-0:7.1.0-6.fc39.x86_64 fapolicy-analyzer-0:1.1.0-2.fc39.x86_64 foliate-0:2.6.4-7.fc39.noarch gamehub-0:0.16.3.2-7.fc39.x86_64 geany-plugins-markdown-0:1.38-10.fc39.x86_64 gthumb-1:3.12.2-9.fc39.x86_64 liferea-1:1.15.0-2.fc39.x86_64 lutris-0:0.5.13-4.fc39.x86_64 meteo-0:0.9.9.2-2.fc39.x86_64 midori-0:9.0-13.fc39.x86_64 minigalaxy-0:1.2.5-1.fc39.noarch notes-up-0:2.0.6-5.fc39.x86_64 oidc-agent-desktop-0:4.5.2-1.fc39.x86_64 osmo-0:0.4.4-2.fc39.x86_64 pdfpc-0:4.6.0-1.fc38.x86_64 sugar-0:0.120-5.fc39.noarch sugar-browse-0:207-7.fc39.noarch sugar-toolkit-gtk3-0:0.120-6.fc39.x86_64 surf-0:2.0-16.fc39.x86_64 ulauncher-0:5.15.3-1.fc39.noarch vimb-0:3.6.0-3.fc39.x86_64 webkit2-sharp-0:0-0.19.20170219gita59fd76.fc39.x86_64 wxGTK-webview-0:3.2.2.1-5.fc39.i686 wxGTK-webview-0:3.2.2.1-5.fc39.x86_64 xiphos-0:4.2.1-20.fc39.x86_64 yad-0:9.3-6.fc39.x86_64 -- 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
Heads-up: webkit2gtk4.0 and javascriptcoregtk4.0 subpackages to be dropped
Hi, Since Fedora 39 has been branched, it's now time to remove the webkit2gtk4.0 (and javascriptcoregtk4.0) subpackages from rawhide to implement the Fedora 40 change proposal: https://fedoraproject.org/wiki/Changes/Remove_webkit2gtk-4.0_API_Version A reminder that webkit2gtk4.0 provides WebKitGTK for applications that use GTK 3 and libsoup 2. The migration path is to switch to webkit2gtk4.1, which contains no API changes but links to libsoup 3 instead of libsoup 2. All applications that still depend on both WebKitGTK and libsoup 2 [1] will break until fixed. Michael [1] https://fedoraproject.org/wiki/Changes/Remove_webkit2gtk-4.0_API_Version#Dependencies ___ 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: Intent to orphan several python packages
On 8/13/23 17:17, Mukundan Ragavan wrote:
On 8/13/23 16:28, Mukundan Ragavan wrote:
I am going to orphan the following packages unless someone wants to
pick them up. I do not have time to maintain them anymore since the
dependencies have become more and more complex with each
release.Several of these packages do not have dependencies packaged in
Fedora.
spyder (docstring-to-markdown)
python-rope (pytoolconfig)
python3-lsp-server (yapf >=0.33)
python-lsp-black
python-lsp-server
python-lsp-jsonrpc
python-pyls-spyder
python-qdarkstyle
In addition, I will also orphan the following packages -
python-spyder-kernels
python-textdistance
python-three_merge
python-libsass
python-qtsass
python-qtconsole
python-nbconvert
python-nbclient
python-QtAwesome
Some/most of these were packaged by me for spyder. I intend to orphan
these unless someone wants to pick up.
thanks.
I have now orphaned the following packages -
python-rope
python-lsp-server
python-lsp-black
python-lsp-jsonrpc
python-pyls-spyder
python-qdarkstyle
python-spyder-kernels
python-versioneer
python-textdistance
python-three_merge
python-libsass
python-qtsass
python-qtconsole
python-QtAwesome
python-QtPy
python-qstylizer
python-Rtree
python-whatthepatch
python-wurlitzer
python-apply-defaults
python-entrypoints
python-jupyterlab_pygments
python-pickleshare
python-helpdev
spyder
I have transferred python-{nbclient,nbconvert} to churchyard.
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Intent to orphan several python packages
On 8/13/23 17:17, Mukundan Ragavan wrote:
On 8/13/23 16:28, Mukundan Ragavan wrote:
I am going to orphan the following packages unless someone wants to
pick them up. I do not have time to maintain them anymore since the
dependencies have become more and more complex with each
release.Several of these packages do not have dependencies packaged in
Fedora.
spyder (docstring-to-markdown)
python-rope (pytoolconfig)
python3-lsp-server (yapf >=0.33)
python-lsp-black
python-lsp-server
python-lsp-jsonrpc
python-pyls-spyder
python-qdarkstyle
In addition, I will also orphan the following packages -
python-spyder-kernels
python-textdistance
python-three_merge
python-libsass
python-qtsass
python-qtconsole
python-nbconvert
python-nbclient
python-QtAwesome
Some/most of these were packaged by me for spyder. I intend to orphan
these unless someone wants to pick up.
thanks.
I have now orphaned the following packages -
python-rope
python-lsp-server
python-lsp-black
python-lsp-jsonrpc
python-pyls-spyder
python-qdarkstyle
python-spyder-kernels
python-versioneer
python-textdistance
python-three_merge
python-libsass
python-qtsass
python-qtconsole
python-QtAwesome
python-QtPy
python-qstylizer
python-Rtree
python-whatthepatch
python-wurlitzer
python-apply-defaults
python-entrypoints
python-jupyterlab_pygments
python-pickleshare
python-helpdev
spyder
I have transferred python-{nbclient,nbconvert} to churchyard.
___
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 2229408] perl-Perl-Metrics-Simple-1.0.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2229408 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Perl-Metrics-Simple-1. |perl-Perl-Metrics-Simple-1. |0.3-1.fc39 |0.3-1.fc39 ||perl-Perl-Metrics-Simple-1. ||0.3-1.fc37 Status|ON_QA |CLOSED Resolution|--- |ERRATA Last Closed||2023-08-16 00:38:05 --- Comment #6 from Fedora Update System --- FEDORA-2023-dab7c2bfc0 has been pushed to the Fedora 37 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=2229408 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202229408%23c6 ___ 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 2227333] perl-Perl-Metrics-Simple-1.0.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2227333 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Perl-Metrics-Simple-1. |perl-Perl-Metrics-Simple-1. |0.2-1.fc39 |0.2-1.fc39 ||perl-Perl-Metrics-Simple-1. ||0.3-1.fc37 Resolution|--- |ERRATA Status|ON_QA |CLOSED Last Closed||2023-08-16 00:38:02 --- Comment #10 from Fedora Update System --- FEDORA-2023-dab7c2bfc0 has been pushed to the Fedora 37 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=2227333 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202227333%23c10 ___ 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
Planning to update to podofo-0.10.1 + review request for podofo-compat for legacy 0.9.x library
Hi I'm planning to update to podofo-0.10.1 in rawhide. I did a series of test builds here [1], according to which scribus, vfrnav and pdfsign currently do not support podofo-0.10.x. To keep these functional, I've prepared a podofo-compat package with the previous 0.9.x library. The review request is here [2]. Happy to review in exchange. Thanks Sandro [1] https://copr.fedorainfracloud.org/coprs/smani/podofo-0.10.1/builds/ [2] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2232243 ___ 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: Potential (security) issue for beginners/non-experts when release is End Of Life: Fedora doesn’t consider the behavior of beginners/non-experts sufficiently
On 8/15/23 09:51, Stephen Smoogen wrote: Each of these groups have 'farms' of several hundred of each type of phone which get continual updates and they have a long certification process to make sure that they reach 'all the phones updated without problems and ran N hours without issues afterwards'. This is part of the reason it can take months for a release from The OS manufacturer (aka Android) to get pushed out to fleets of phones. It is fairly 'expensive' work with lots of little issues having to be tracked down and passed. [Because even when you 'built the phone' you find out that N% of that batch still acts slightly different from the rest on this update.] In the desktop/computer mode this is just outside of anything that I think a volunteer oriented organization could try to make work at scale. I do see your point that there's too much variability in the hardware and software setup to be able to exhaustively test all the upgrade paths, but Adam W. and his group do such excellent job of testing that I think statistically a failed update is a black swan. It would be nice to know the actual failure numbers, but we'd need some telemetry for that :). Maybe the technical challenge that would solve this is rollback of failed updates. OStree arguably has an advantage here over file-based updates. For what it's worth I personally was blessed with simple upgrade problems, fixed by temporarily deleting a bunch of large packages like KiCAD 3D models RPM, etc. I was always able to upgrade, so my anecdata makes me trust Fedora updates. In fact, the main challenge I encountered is the accidental persistence of various 'experimental' UI and OS settings I did over time that result in a behavior different from a fresh install---I sometimes wish there was an interactive, granular 'restore factory defaults' option that would let me keep some settings and revert others. ___ 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
Proposal to improve the background packaging process
Cross-posting here as folks may be interested: https://discussion.fedoraproject.org/t/proposal-to-improve-the-background-packaging-process/87527/2 I proposed an idea to try and improve the background packaging process to avoid there being so much hassle when the backgrounds aren't ready by the Branch date. Thoughts appreciated! Ideally over on discussion, but if you really really hate discourse, I guess reply here. :D -- 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: Dropping of sshd.socket unit
Dear Lennart,
I'm sorry, I don't get.
Quoting the
https://www.freedesktop.org/software/systemd/man/systemd.socket.html#TriggerLimitIntervalSec=
Configures a limit on how often this socket unit may be activated
within a specific time interval. The TriggerLimitIntervalSec= may be
used to configure the length of the time interval in the usual time
units "us", "ms", "s", "min", "h", … and defaults to 2s (See
systemd.time(7) for details on the various time units understood). The
TriggerLimitBurst= setting takes a positive integer value and
specifies the number of permitted activations per time interval, and
defaults to 200 for Accept=yes sockets (thus by default permitting 200
activations per 2s), and 20 otherwise (20 activations per 2s). Set
either to 0 to disable any form of trigger rate limiting. If the limit
is hit, the socket unit is placed into a failure mode, and will not be
connectible anymore until restarted. Note that this limit is enforced
before the service activation is enqueued.
But this behavior (the last sentence) exactly matches the DoS
described here: https://bugs.archlinux.org/task/62248
Too many connections to an sshd server, configured using socket
activation can cause the socket to be disabled permanently
("sshd.socket: Trigger limit hit, refusing further activation.").
On Mon, Aug 7, 2023 at 11:48 AM Lennart Poettering wrote:
>
> On Do, 03.08.23 11:29, Dmitry Belyavskiy (dbely...@redhat.com) wrote:
>
> > Dear colleagues,
> >
> > I've pushed a fresh build of OpenSSH to rawhide.
> > We decided to drop the sshd.socket unit from rawhide. We don't think
> > it's worth going through the changes process, but would like to
> > provide a heads-up.
>
> Hmm, why drop it? For many setups, it makes not sense to continously
> run sshd, so socket activation should be fine.
>
> I don't understand the reasoning behind this change. You claim a
> DoS. Which DoS is that supposed to be? That we enforce a trigger time
> limit on socket units by default? If you don't want this, turn it off,
> that's what TriggerLimitIntervalSec=/TriggerLimitBurst= is for, see
> docs.
>
> The discussion makes this sound as if there was a bug in systemd or
> so, but there really isn't, it's literally a safety feature you ran
> into. It might not make sense to have the trigger rate limit in place
> for all usecases, ssh might be one where it is not advisable, but then
> the right approach is to just turn that part off, as documented, via
> the aforementioned options.
>
> See for details:
>
> https://www.freedesktop.org/software/systemd/man/systemd.socket.html#TriggerLimitIntervalSec=
>
> I don't care too much whether you make ssh socket-activated by default
> or not. But at least the option should exist, already for compat with
> existing setups.
>
> Lennart
>
> --
> Lennart Poettering, Berlin
> ___
> 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
--
Dmitry Belyavskiy
___
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] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2023-08-16 from 16:00:00 to 17:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #topic aloha #topic EPEL Issues https://pagure.io/epel/issues * https://pagure.io/epel/issues?tags=meeting=Open #topic Old Business (if needed) #topic General Issues / Open Floor Source: https://calendar.fedoraproject.org//meeting/9854/ ___ 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 2229718] perl-Mozilla-CA-20230807 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2229718 --- Comment #4 from Michal Josef Spacek --- Changes: 20230807 - Prevent extra headers in tarball and make it reproducible For rawhide. -- 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%23c4 ___ 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 2230255] perl-HTTP-Tiny: a ton of new dependencies all of a sudden?
https://bugzilla.redhat.com/show_bug.cgi?id=2230255 Michal Josef Spacek changed: What|Removed |Added Assignee|jples...@redhat.com |mspa...@redhat.com Resolution|NOTABUG |--- Status|CLOSED |ASSIGNED Keywords||Reopened -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2230255 ___ 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: Potential (security) issue for beginners/non-experts when release is End Of Life: Fedora doesn’t consider the behavior of beginners/non-experts sufficiently
On Mon, 14 Aug 2023 at 17:59, Przemek Klosowski via devel < devel@lists.fedoraproject.org> wrote: > On 8/13/23 16:57, Kevin Kofler via devel wrote: > > look at SUPPORT_END in /etc/os-release and nag more frequently. > > Highly recommend other Fedora editions consider similar notifications. > > I don't think more nagging is going to help. It is just going to be > considered yet another annoying nag to ignore or click away. Like it or not, > non-technical users are NEVER going to upgrade to a new operating system > release. Not now, not 10 years from now. Until their computer physically > breaks down, at least. There is just nothing you can do about it. > > I believe this is overly pessimistic: people tend to upgrade their Android > and iOS devices and applications, because the update process is > low-friction and well tested so that people tend to trust it. > > It is fairly well tested because the entire phone hardware set is a 'known' quantity. There are also several different layers of 'testing' and quality control which happen: 0. The OS manufacturer 1. The phone manufacturer (for android about 2 years, for iphone for 10) 2. The wireless carrier (for android about 3 years, for iphone for 7) 3. Sometimes major software app manufacturers Each of these groups have 'farms' of several hundred of each type of phone which get continual updates and they have a long certification process to make sure that they reach 'all the phones updated without problems and ran N hours without issues afterwards'. This is part of the reason it can take months for a release from The OS manufacturer (aka Android) to get pushed out to fleets of phones. It is fairly 'expensive' work with lots of little issues having to be tracked down and passed. [Because even when you 'built the phone' you find out that N% of that batch still acts slightly different from the rest on this update.] In the desktop/computer mode this is just outside of anything that I think a volunteer oriented organization could try to make work at scale. > I have personally had multiple Fedora upgrade issues due to lack of space > in the root filesystem, so maybe Fedora is not yet at a point where we can > unconditionally launch into upgrading, but it's a technical issue that can > be corrected. > > We already have SUPPORT_END so I think it makes sense to use it. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, 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
Fedora 39 compose report: 20230815.n.0 changes
OLD: Fedora-39-20230814.n.0 NEW: Fedora-39-20230815.n.0 = SUMMARY = Added images:4 Dropped images: 2 Added packages: 4 Dropped packages:0 Upgraded packages: 77 Downgraded packages: 0 Size of added packages: 12.32 MiB Size of dropped packages:0 B Size of upgraded packages: 3.63 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 17.24 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: LXQt raw-xz aarch64 Path: Spins/aarch64/images/Fedora-LXQt-39-20230815.n.0.aarch64.raw.xz Image: LXQt live aarch64 Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-39-20230815.n.0.iso Image: Phosh raw-xz aarch64 Path: Spins/aarch64/images/Fedora-Phosh-39-20230815.n.0.aarch64.raw.xz Image: i3 live aarch64 Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-39-20230815.n.0.iso = DROPPED IMAGES = Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-39-20230814.n.0.iso Image: Server_KVM qcow2 x86_64 Path: Server/x86_64/images/Fedora-Server-KVM-39-20230814.n.0.x86_64.qcow2 = ADDED PACKAGES = Package: rust-clang-tidy-sarif-0.4.1-1.fc39 Summary: Convert clang-tidy output to SARIF RPMs:clang-tidy-sarif Size:3.74 MiB Package: rust-clippy-sarif-0.4.1-1.fc39 Summary: Convert clippy output to SARIF RPMs:clippy-sarif Size:4.07 MiB Package: rust-hadolint-sarif-0.4.1-1.fc39 Summary: Convert hadolint output to SARIF RPMs:hadolint-sarif Size:2.23 MiB Package: rust-shellcheck-sarif-0.4.1-1.fc39 Summary: Convert shellcheck output to SARIF RPMs:shellcheck-sarif Size:2.28 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: boost-1.81.0-7.fc39 Old package: boost-1.81.0-6.fc39 Summary: The free peer-reviewed portable C++ source libraries RPMs: boost boost-atomic boost-b2 boost-build boost-chrono boost-container boost-context boost-contract boost-coroutine boost-date-time boost-devel boost-doc boost-doctools boost-examples boost-fiber boost-filesystem boost-graph boost-graph-mpich boost-graph-openmpi boost-iostreams boost-json boost-locale boost-log boost-math boost-mpich boost-mpich-devel boost-mpich-python3 boost-mpich-python3-devel boost-nowide boost-numpy3 boost-openmpi boost-openmpi-devel boost-openmpi-python3 boost-openmpi-python3-devel boost-program-options boost-python3 boost-random boost-regex boost-serialization boost-stacktrace boost-static boost-system boost-test boost-thread boost-timer boost-type_erasure boost-url boost-wave Size: 338.03 MiB Size change: 5.23 KiB Changelog: * Wed Aug 02 2023 Tom Callaway - 1.81.0-7 - add symlink for b2 files Package: bout++-5.0.0-10.fc39 Old package: bout++-5.0.0-9.fc39 Summary: Library for the BOUndary Turbulence simulation framework RPMs: bout++-common bout++-doc bout++-mpich bout++-mpich-devel bout++-openmpi bout++-openmpi-devel python3-bout++ python3-bout++-mpich python3-bout++-openmpi Size: 18.15 MiB Size change: 191.31 KiB Changelog: * Mon Aug 14 2023 Antonio Trande - 5.0.0-10 - Rebuild for petsc-3.19.4 Package: brltty-6.6-3.fc39 Old package: brltty-6.6-2.fc39 Summary: Braille display driver for Linux/Unix RPMs: brlapi brlapi-devel brlapi-java brltty brltty-at-spi2 brltty-docs brltty-dracut brltty-espeak brltty-espeak-ng brltty-minimal brltty-speech-dispatcher brltty-xw ocaml-brlapi python3-brlapi tcl-brlapi Size: 17.46 MiB Size change: -52.39 KiB Changelog: * Mon Aug 14 2023 Adam Williamson - 6.6-3 - Build with Cython 0.29, it crashes when built with Cython 3 (#2231865) Package: combblas-2.0.0-4.fc39 Old package: combblas-2.0.0-1.fc39 Summary: The Combinatorial BLAS Library RPMs: combblas-mpich combblas-mpich-devel combblas-openmpi combblas-openmpi-devel Size: 5.80 MiB Size change: 596.46 KiB Changelog: * Wed Jul 19 2023 Fedora Release Engineering - 2.0.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Thu Aug 03 2023 Antonio Trande - 2.0.0-3 - Debug builds * Mon Aug 14 2023 Antonio Trande - 2.0.0-4 - Disable LTO flags in debug builds - Disable tests Package: dolfin-2019.1.0.post0-46.fc39 Old package: dolfin-2019.1.0.post0-45.fc39 Summary: FEniCS computational backend and problem solving environment RPMs: dolfin dolfin-devel dolfin-doc python3-dolfin Size: 13.28 MiB Size change: 174.82 KiB Changelog: * Sun Aug 13 2023 Antonio Trande - 2019.1.0.post0-46 - Rebuild for petsc-3.19.4 Package: easyeffects-7.0.7-1.fc39 Old package: easyeffects-7.0.6-1.fc39 Summary: Audio effects for PipeWire applications RPMs: easyeffects Size: 4.52 MiB Size change: 19.83 KiB Changelog: * Mon Aug 14 2023 Vasiliy N. Glazov - 7.0.7-1 - Update to 7.0.7 Package: efs-utils-1.35.0-2.fc39 Old package: efs-utils-1.35.0-1.fc39 Summary: Utilities
[Bug 2230861] perl-Lingua-EN-Fathom-1.27 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2230861 Michal Josef Spacek changed: What|Removed |Added Resolution|--- |RAWHIDE Status|ASSIGNED|CLOSED Fixed In Version||perl-Lingua-EN-Fathom-1.27- ||1.fc40 Last Closed||2023-08-15 13:14:43 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2230861 ___ 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
Pykka was orphaned
Hi all, python3-Pykka (srpm 'pykka') was orphaned yesterday. I intend to adopt it and fix it, probably this weekend. If someone wants to be co-maintainer, please reach out! tobi ___ 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: Replacing DNF with DNF5: changes reverted and helping steps
> > Perhaps a 'dnf-is-dnf5' providing the dnf command as a symlink to dnf5 > (taking inspiration from debian's python-is-python3) would work as a > stop-gap, so people who want a system with just dnf could install that > package as an alternate dnf provider ? > Rather than a `dnf-is-dnf5` package, we are working on a COPR repository to ship dnf5 and dnf with obsolete directives. The packages will be built from dist-git (therefore following fedora versioning) and will be suited for testing dnf replacement. I see this as a good chance for testers and daily users. This COPR repo will be ready by the end of next week and I will announce it on fedora-devel. On Tue, Aug 15, 2023 at 1:31 PM Dominique Martinet wrote: > Vít Ondruch wrote on Tue, Aug 15, 2023 at 12:09:34PM +0200: > > > I think only the mass-prebuild maintainer can help you there. dnf5 > > > cannot be set to provide dnf, because it...doesn't. > > > > > > I know and yet again, I have not find any issues using mass-prebuild with > > DNF5 and until now, it worked just fine. I probably won't ever understand > > this game with names. > > > > But may be we are on the same boat and your "because it...doesn't." falls > > into the same category 路♂️ > > Perhaps a 'dnf-is-dnf5' providing the dnf command as a symlink to dnf5 > (taking inspiration from debian's python-is-python3) would work as a > stop-gap, so people who want a system with just dnf could install that > package as an alternate dnf provider ? > > > Alternatively making dnf install as dnf4 + provide dnf as an > 'alternative' config, and making dnf5 provide dnf as an alternative > config with lower priority would likely also work ; but that probably > requires modifying the dnf package first to avoid conflict. > > -- > Dominique Martinet | Asmadeus > ___ > 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: Replacing DNF with DNF5: changes reverted and helping steps
Vít Ondruch wrote on Tue, Aug 15, 2023 at 12:09:34PM +0200: > > I think only the mass-prebuild maintainer can help you there. dnf5 > > cannot be set to provide dnf, because it...doesn't. > > > I know and yet again, I have not find any issues using mass-prebuild with > DNF5 and until now, it worked just fine. I probably won't ever understand > this game with names. > > But may be we are on the same boat and your "because it...doesn't." falls > into the same category 路♂️ Perhaps a 'dnf-is-dnf5' providing the dnf command as a symlink to dnf5 (taking inspiration from debian's python-is-python3) would work as a stop-gap, so people who want a system with just dnf could install that package as an alternate dnf provider ? Alternatively making dnf install as dnf4 + provide dnf as an 'alternative' config, and making dnf5 provide dnf as an alternative config with lower priority would likely also work ; but that probably requires modifying the dnf package first to avoid conflict. -- Dominique Martinet | Asmadeus ___ 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: 20230815.n.0 changes
OLD: Fedora-Rawhide-20230814.n.0 NEW: Fedora-Rawhide-20230815.n.0 = SUMMARY = Added images:1 Dropped images: 5 Added packages: 9 Dropped packages:0 Upgraded packages: 110 Downgraded packages: 0 Size of added packages: 12.39 MiB Size of dropped packages:0 B Size of upgraded packages: 3.63 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 29.56 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230815.n.0.iso = DROPPED IMAGES = Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230814.n.0.iso Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230814.n.0.iso Image: Kinoite dvd-ostree aarch64 Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20230814.n.0.iso Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20230814.n.0.iso Image: Mate live x86_64 Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-Rawhide-20230814.n.0.iso = ADDED PACKAGES = Package: golang-modernc-httpfs-1.0.6-1.fc40 Summary: Implements http.FileSystem on top of a map[string]string RPMs:golang-modernc-httpfs-devel Size:12.15 KiB Package: golang-modernc-memory-1.6.0-1.fc40 Summary: A memory allocator RPMs:golang-modernc-memory-devel Size:27.11 KiB Package: golang-modernc-opt-0.1.3-1.fc40 Summary: Implements command-line flag parsing RPMs:golang-modernc-opt-devel Size:12.01 KiB Package: golang-modernc-sortutil-1.1.0-11.fc40 Summary: Utilities supplemental to the Go standard "sort" package RPMs:golang-modernc-sortutil-devel Size:13.98 KiB Package: golang-modernc-strutil-1.1.3-1.fc40 Summary: Utils supplemental to the standard strings package RPMs:golang-modernc-strutil-devel Size:17.42 KiB Package: rust-clang-tidy-sarif-0.4.1-1.fc40 Summary: Convert clang-tidy output to SARIF RPMs:clang-tidy-sarif Size:3.72 MiB Package: rust-clippy-sarif-0.4.1-1.fc40 Summary: Convert clippy output to SARIF RPMs:clippy-sarif Size:4.07 MiB Package: rust-hadolint-sarif-0.4.1-1.fc40 Summary: Convert hadolint output to SARIF RPMs:hadolint-sarif Size:2.23 MiB Package: rust-shellcheck-sarif-0.4.1-1.fc40 Summary: Convert shellcheck output to SARIF RPMs:shellcheck-sarif Size:2.28 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: OpenSceneGraph-3.6.5-18.fc40 Old package: OpenSceneGraph-3.6.5-16.fc39 Summary: High performance real-time graphics toolkit RPMs: OpenSceneGraph OpenSceneGraph-Collada OpenSceneGraph-OpenEXR OpenSceneGraph-devel OpenSceneGraph-examples OpenSceneGraph-examples-SDL OpenSceneGraph-examples-fltk OpenSceneGraph-examples-gtk OpenSceneGraph-gdal OpenSceneGraph-gstreamer OpenSceneGraph-libs OpenThreads OpenThreads-devel mingw32-OpenSceneGraph mingw32-OpenSceneGraph-tools mingw64-OpenSceneGraph mingw64-OpenSceneGraph-tools Size: 214.02 MiB Size change: -29.88 KiB Changelog: * Mon Aug 14 2023 Sandro Mani - 3.6.5-17 - Rebuild (mingw-poppler) * Mon Aug 14 2023 Sandro Mani - 3.6.5-18 - Rebuild (mingw-poppler) Package: ProDy-2.4.1-1.fc40 Old package: ProDy-2.4.0-4.fc39 Summary: Application for protein structure, dynamics and sequence analysis RPMs: python3-ProDy Size: 40.70 MiB Size change: 9.59 MiB Changelog: * Mon Aug 14 2023 Antonio Trande - 2.4.1-1 - Release 4.2.1 Package: awscli2-2.13.9-1.fc40 Old package: awscli2-2.13.7-1.fc39 Summary: Universal Command Line Environment for AWS, version 2 RPMs: awscli2 Size: 11.68 MiB Size change: 11.57 KiB Changelog: * Fri Aug 11 2023 Packit - 2.13.9-1 - [packit] 2.13.9 upstream release Package: bout++-5.0.0-10.fc40 Old package: bout++-5.0.0-9.fc39 Summary: Library for the BOUndary Turbulence simulation framework RPMs: bout++-common bout++-doc bout++-mpich bout++-mpich-devel bout++-openmpi bout++-openmpi-devel python3-bout++ python3-bout++-mpich python3-bout++-openmpi Size: 18.15 MiB Size change: 191.21 KiB Changelog: * Mon Aug 14 2023 Antonio Trande - 5.0.0-10 - Rebuild for petsc-3.19.4 Package: brltty-6.6-3.fc40 Old package: brltty-6.6-2.fc39 Summary: Braille display driver for Linux/Unix RPMs: brlapi brlapi-devel brlapi-java brltty brltty-at-spi2 brltty-docs brltty-dracut brltty-espeak brltty-espeak-ng brltty-minimal brltty-speech-dispatcher brltty-xw ocaml-brlapi python3-brlapi tcl-brlapi Size: 17.46 MiB Size change: -51.39 KiB Changelog: * Mon Aug 14 2023 Adam Williamson - 6.6-3 - Build with Cython 0.29, it crashes when built with Cython 3 (#2231865) Package: catfish-4.18.0-1.fc40 Old package: catfish-4.16.4-1.fc39.3 Summary: A
[rpms/perl-Lingua-EN-Fathom] PR #7: 1.27 bump
mspacek merged a pull-request against the project: `perl-Lingua-EN-Fathom` that you are following. Merged pull-request: `` 1.27 bump `` https://src.fedoraproject.org/rpms/perl-Lingua-EN-Fathom/pull-request/7 ___ 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: Replacing DNF with DNF5: changes reverted and helping steps
V Tue, Aug 15, 2023 at 11:52:55AM +0100, Peter Robinson napsal(a): > On Tue, Aug 15, 2023 at 11:41 AM Petr Pisar wrote: > > > > V Tue, Aug 15, 2023 at 12:09:34PM +0200, Vít Ondruch napsal(a): > > > Dne 14. 08. 23 v 19:30 Adam Williamson napsal(a): > > > > On Mon, 2023-08-14 at 16:59 +0200, Vít Ondruch wrote: > > > > > $ sudo dnf update -x dnf > > > > > Updating and loading repositories: > > > > > Repositories loaded. > > > > > Failed to resolve the transaction: > > > > > Problem 1: package mass-prebuild-1.1.0-1.fc39.noarch requires dnf, but > > > > > none of the providers can be installed > > [...] > > > > I think only the mass-prebuild maintainer can help you there. dnf5 > > > > cannot be set to provide dnf, because it...doesn't. > > > > > > I know and yet again, I have not find any issues using mass-prebuild with > > > DNF5 and until now, it worked just fine. I probably won't ever understand > > > this game with names. > > > > > Since DNF5 is planned as a replacement for Fedora 40 and because Fedora 39 > > has > > already branched, I'd like to see making dnf5 replacing dnf package in > > Fedora > > 40 as soon as possible. To have a testing, integration, and stablization > > period > > as long as possible. > > Quoting Samantha [1]: > > "We've gone ahead and decided not to replace DNF with DNF05 in Fedora > 39 and, perhaps notably, Fedora 40 as well. Fedora 41 is the safest > option at the moment." > > So I thought it wasn't coming until Fedora 41? > You are right. I was mistaken and thought that DNF5 only slipped a Fedora release. Then ignore my suggestion. -- 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: Replacing DNF with DNF5: changes reverted and helping steps
On Tue, Aug 15, 2023 at 11:41 AM Petr Pisar wrote: > > V Tue, Aug 15, 2023 at 12:09:34PM +0200, Vít Ondruch napsal(a): > > Dne 14. 08. 23 v 19:30 Adam Williamson napsal(a): > > > On Mon, 2023-08-14 at 16:59 +0200, Vít Ondruch wrote: > > > > $ sudo dnf update -x dnf > > > > Updating and loading repositories: > > > > Repositories loaded. > > > > Failed to resolve the transaction: > > > > Problem 1: package mass-prebuild-1.1.0-1.fc39.noarch requires dnf, but > > > > none of the providers can be installed > [...] > > > I think only the mass-prebuild maintainer can help you there. dnf5 > > > cannot be set to provide dnf, because it...doesn't. > > > > I know and yet again, I have not find any issues using mass-prebuild with > > DNF5 and until now, it worked just fine. I probably won't ever understand > > this game with names. > > > Since DNF5 is planned as a replacement for Fedora 40 and because Fedora 39 has > already branched, I'd like to see making dnf5 replacing dnf package in Fedora > 40 as soon as possible. To have a testing, integration, and stablization > period > as long as possible. Quoting Samantha [1]: "We've gone ahead and decided not to replace DNF with DNF05 in Fedora 39 and, perhaps notably, Fedora 40 as well. Fedora 41 is the safest option at the moment." So I thought it wasn't coming until Fedora 41? [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EYE2JY537OM7GFW46EK7YIBLHJ52USAZ/ ___ 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: Replacing DNF with DNF5: changes reverted and helping steps
V Tue, Aug 15, 2023 at 12:09:34PM +0200, Vít Ondruch napsal(a): > Dne 14. 08. 23 v 19:30 Adam Williamson napsal(a): > > On Mon, 2023-08-14 at 16:59 +0200, Vít Ondruch wrote: > > > $ sudo dnf update -x dnf > > > Updating and loading repositories: > > > Repositories loaded. > > > Failed to resolve the transaction: > > > Problem 1: package mass-prebuild-1.1.0-1.fc39.noarch requires dnf, but > > > none of the providers can be installed [...] > > I think only the mass-prebuild maintainer can help you there. dnf5 > > cannot be set to provide dnf, because it...doesn't. > > I know and yet again, I have not find any issues using mass-prebuild with > DNF5 and until now, it worked just fine. I probably won't ever understand > this game with names. > Since DNF5 is planned as a replacement for Fedora 40 and because Fedora 39 has already branched, I'd like to see making dnf5 replacing dnf package in Fedora 40 as soon as possible. To have a testing, integration, and stablization period as long as possible. That would also resolve Vít's issue with mass-prebuild. -- 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: Replacing DNF with DNF5: changes reverted and helping steps
Dne 14. 08. 23 v 19:30 Adam Williamson napsal(a): On Mon, 2023-08-14 at 16:59 +0200, Vít Ondruch wrote: Can you please make this work? ~~~ $ sudo dnf update -x dnf Updating and loading repositories: Repositories loaded. Failed to resolve the transaction: Problem 1: package mass-prebuild-1.1.0-1.fc39.noarch requires dnf, but none of the providers can be installed - cannot install both dnf5-5.1.0-1.fc39.x86_64 and dnf5-5.1.1-1.fc39.x86_64 - cannot install the best update candidate for package mass-prebuild-1.1.0-1.fc39.noarch - cannot install the best update candidate for package dnf5-5.1.0-1.fc39.x86_64 - package dnf-4.16.2-2.fc39.noarch is filtered out by exclude filtering Problem 2: problem with installed package - package mass-prebuild-1.1.0-1.fc39.noarch requires dnf, but none of the providers can be installed - cannot install both dnf5-5.1.0-1.fc39.x86_64 and dnf5-5.1.1-1.fc39.x86_64 - package dnf5-plugins-5.1.1-1.fc39.x86_64 requires dnf5(x86-64) = 5.1.1-1.fc39, but none of the providers can be installed - cannot install the best update candidate for package dnf5-plugins-5.1.0-1.fc39.x86_64 - package dnf-4.16.2-2.fc39.noarch is filtered out by exclude filtering ~~~ IOW I want to stay with DNF 5 and DNF 5 only. This system was installed with DNF 5 and I don't want to have a mess of all the cache directories DNF leaves behind and what not. BTW I have also asked the mass-prebuild maintainer for help: https://gitlab.com/fedora/packager-tools/mass-prebuild/-/issues/86 I think only the mass-prebuild maintainer can help you there. dnf5 cannot be set to provide dnf, because it...doesn't. I know and yet again, I have not find any issues using mass-prebuild with DNF5 and until now, it worked just fine. I probably won't ever understand this game with names. But may be we are on the same boat and your "because it...doesn't." falls into the same category 路♂️ Vít OpenPGP_signature.asc Description: OpenPGP digital 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
