Re: List of long term FTBFS packages to be retired in February
Miro Hrončok wrote on 2024/01/25 1:38: Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 40 approximately one week before branching. 5 weekly reminders are required, hence the retirement will happen approximately in 5 weeks, i.e. around 2024-02-28. Since this is unfortunately after the branching, packages will be retired on rawhide and f40. I apologize for starting this process a bit later than required again. Unfortunately, I had other work obligations. Volunteers to take over this are always welcome. Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The packages in rawhide were not successfully built at least since Fedora 37. This report is based on dist tags. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb If you see a package that was built, please let me know. If you see a package that should be exempted from the process, please let me know and we can work together to get a FESCo approval for that. If you see a package that can be rebuilt, please do so. Package (co)maintainers telepathy-gabble aperezbios Depending on: telepathy-gabble (31) sugar (maintained by: aperezbios, chimosky) sugar-0.120-5.fc39.noarch requires telepathy-gabble sugar-abacus (maintained by: chimosky) sugar-abacus-61-9.fc39.noarch requires sugar Too many dependencies for telepathy-gabble, not all listed here PR submitted to rescue SoaS spin: https://src.fedoraproject.org/rpms/telepathy-gabble/pull-request/2 Regards, Mamoru -- ___ 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 2261854] New: perl-PDL-2.085 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2261854 Bug ID: 2261854 Summary: perl-PDL-2.085 is available Product: Fedora Version: rawhide Status: NEW Component: perl-PDL Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, ka...@ucw.cz, lkund...@v3.sk, perl-devel@lists.fedoraproject.org, rhug...@redhat.com, rstr...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 2.085 Upstream release that is considered latest: 2.085 Current version/release in rawhide: 2.84.0-5.fc40 URL: https://metacpan.org/dist/PDL/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3205/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-PDL -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261854 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261854%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
[Bug 2258287] perl-libwww-perl-6.73 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2258287 --- Comment #5 from Fedora Update System --- FEDORA-2024-7b72801203 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7b72801203` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7b72801203 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=2258287 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258287%23c5 -- ___ 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 2259685] perl-libwww-perl-6.75 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2259685 --- Comment #6 from Fedora Update System --- FEDORA-2024-7b72801203 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7b72801203` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7b72801203 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=2259685 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202259685%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
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-4ff425606f openssl11-1.1.1k-7.el7 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-54270ec4b3 clojure-1.8.0-2.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing barman-3.10.0-1.el7 Details about builds: barman-3.10.0-1.el7 (FEDORA-EPEL-2024-e3e54fa722) Backup and Recovery Manager for PostgreSQL Update Information: Update to 3.10.0 ChangeLog: * Thu Jan 25 2024 Simone Caronni - 3.10.0-1 - Update to 3.10.0. References: [ 1 ] Bug #2260108 - barman-3.10.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=2260108 -- ___ 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
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 26 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3a29f0d349 python-paramiko-2.12.0-2.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-76443fce3f indent-2.2.13-5.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-272d6fcaca atril-1.26.2-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-93d34f40f0 chromium-121.0.6167.85-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing AMF-1.4.33-1.el8 barman-3.10.0-1.el8 dfuzzer-2.3-2.el8 Details about builds: AMF-1.4.33-1.el8 (FEDORA-EPEL-2024-39ccf80406) Advanced Media Framework (AMF) SDK Update Information: AMD release 1.4.33. ChangeLog: * Mon Jan 29 2024 Simone Caronni - 1.4.33-1 - Update to 1.4.33. barman-3.10.0-1.el8 (FEDORA-EPEL-2024-e255d6b671) Backup and Recovery Manager for PostgreSQL Update Information: Update to 3.10.0 ChangeLog: * Thu Jan 25 2024 Simone Caronni - 3.10.0-1 - Update to 3.10.0. References: [ 1 ] Bug #2260108 - barman-3.10.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=2260108 dfuzzer-2.3-2.el8 (FEDORA-EPEL-2024-fdb44ee08b) D-Bus fuzz testing tool Update Information: Work around old meson in EL8 ChangeLog: * Mon Jan 29 2024 Frantisek Sumsal - 2.3-2 - Work around old meson in EL8 * Mon Jan 29 2024 Frantisek Sumsal - 2.3-1 - Bump to v2.3 -- ___ 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 2260383] perl-libwww-perl-6.76 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2260383 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2024-7b72801203 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7b72801203` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7b72801203 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=2260383 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260383%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
openQA test failures for Rawhide: heads up
Hey folks! You may have noticed unpredictable openQA test failures on Rawhide updates ATM. This is mainly because of the mass rebuild. All the packages from the mass rebuild have been tagged into the buildroot repo (which the openQA tests use), so now there are far more on-the-fly updates than is usually the case, and various test steps are hitting timeouts depending on how fast the download / update process runs. I'll re-run tests opportunistically for now, but some may still fall through the cracks. Once the currently-running Rawhide compose completes (fingers crossed), I can regenerate the base disk images so they're up to date with the mass rebuild package set, and things should settle down again. -- 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: A reminder: you cannot just "revert" package version bumps
On 2024-01-29 16:00, Sérgio Basto wrote: https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily you may do a new build with lower EVR That is not what that guideline says. It says the Rawhide build can be lower-versioned than a current build from *a different branch* *temporarily*. It says nothing about allowing a new Rawhide build to be lower versioned than the previous one. -- 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
[Bug 1936241] Compiled @INC in 5.32 No longer Includes Suitable Path For Custom System-Wide Modules
https://bugzilla.redhat.com/show_bug.cgi?id=1936241 Jeffrey Hutzelman changed: What|Removed |Added CC||jh...@cmu.edu --- Comment #3 from Jeffrey Hutzelman --- This is wrong. That reasoning is sound for sitearch, which contains architecture-dependent (binary) module files. It makes plenty of sense to look for such modules in an ABI-version-dependent directory; Perl has done that since 5.005 or so. It is completely inapplicable to sitelib, which contains architecture-independent modules. Such modules are non-binary and so cannot be ABI-version-dependent. They do not need to be in a versioned directory tree. This may come as a surprise, but CPAN is not everything. Lots of us have private, site-specific modules. Most of those are pure-perl. Most of them are relatively simple -- a single file, or a small tree of files. And most of them are installed by dropping files in the right place, via whatever mechanism we are using to manage hundreds or thousands of machines. They are not built on each machine, or even "built" at all -- Perl's module build system is great for modules that actually have something that need to be compiled, but way overkill for something that just needs a few files to be dropped into perl's sitelib directory. It is a huge problem for Perl to suddenly stop looking in that site-specific, version-agnostic location across an upgrade. Even if that is a major-version upgrade like RHEL8->RHEL9 (which is the first time enterprise customers saw this, and not all tha long ago on the timescale of people who manage thousands of machines supporting hundreds of applications). In fact, it's a huge problem to have to guess what is the correct location, on a per-machine basis, depending on what version of perl might be there. This is a regression. /usr/local/share/perl5 worked in RHEL7 and RHEL8; it does not work in RHEL9. Apparently the same was true with Fedora 30->31. Perhaps Red Hat is not interested in fixing this bug. But it is certainly a bug. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1936241 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201936241%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: A reminder: you cannot just "revert" package version bumps
Sérgio Basto wrote: > yes rawhide user should use dnf distro-sync not dnf upgrade +1. Rawhide EVRs should be allowed to go backwards, that is an integral part of being a development branch. Kevin Kofler -- ___ 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: A reminder: you cannot just "revert" package version bumps
On Tue, Jan 30, 2024 at 1:00 AM Sérgio Basto wrote: > (snip) > yes rawhide user should use dnf distro-sync not dnf upgrade It is better, yes, but it is not *required*. > https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily This is a completely different problem. Package updates that don't build in Rawhide but build on stable branches are permissible as long as the package update will be submitted to Rawhide *eventually*. > you may do a new build with lower EVR No, you may not. That is exactly what Adam's email is about. Fabio -- ___ 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: A reminder: you cannot just "revert" package version bumps
On Mon, 2024-01-29 at 15:43 -0800, Adam Williamson wrote: > nirik ran a script that checks for versioning issues in Rawhide > today, > and it found several: > https://pagure.io/releng/issue/11922#comment-893797 > > Some of these followed a pattern, so I figured a reminder was in > order. > In all these cases, a new version was pushed to Rawhide, then > "reverted" > some time later: > > golang-github-nats-io-jwt - bumped to 2.4.1 in July, reverted to > 1.2.2 > in September > golang-google-grpc - bumped to 1.58.0 in September, reverted to > 1.48.0 > in October; no 1.58.0 build ever landed, but the revert left the > %release much lower than before > python-mizani - bumped to 0.10.0 on September 10, reverted to 0.9.3 > on > September 12 > python-pywlroots - bumped to 0.16.6 on November 4, reverted to 0.16.4 > later the same day > > so the reminder is this: you cannot simply "downgrade" RPM package > versions like this. Especially not if the upgraded version ever made > it > into a Rawhide compose. > > If a Rawhide user has your package installed, and got the upgraded > version, they will be marooned on that build forever unless they > manually run `dnf distro-sync`. A `dnf upgrade` will not downgrade > the > package to the build you now consider to be the "current" one. yes rawhide user should use dnf distro-sync not dnf upgrade https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily you may do a new build with lower EVR > If you have to downgrade a package that made it to a Rawhide compose, > you must use an epoch. If the package did not have an epoch before, > make > it `Epoch: 1`. If it had an epoch already, bump it by 1. People tend > not > to like epochs, so *try* not to have to do this. Be really certain > before pushing out version bumps. > > If the "upgraded" build never made it into a compose (as is likely > the > case for python-pywlroots) you're *probably* okay, but it's still > something to be careful about - for instance you might fall into the > trap golang-google-grpc fell into with the %release tag. > > Thanks folks! > -- > 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 -- 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
A reminder: be careful with snapshot versioning, especially with %autorelease
nirik ran a script that checks for versioning issues in Rawhide today, and it found several: https://pagure.io/releng/issue/11922#comment-893797 Aside from rogue version downgrades (see other mail), a few of these followed a different pattern: problems with snapshot versioning. 1. patool: highest tagged build patool-1.12-22.fc39, most recent tagged build patool-1.12-0.27.20231014gitab64562.fc40 2. python-pyunicorn: highest tagged build python-pyunicorn-0.7.0a1-1.20230730gitmaster.fc40 , most recent tagged build python-pyunicorn-0.7.0~a1-5.20230730gitmaster.fc40 3. vim-devicons: highest tagged build vim-devicons-0.11.0-10.20200509gitd12c9b4.fc39 , most recent tagged build vim-devicons-0.11.0-0.20221001git71f239a.13.fc40 In the python-pyunicorn case, the packager simply made a mistake with pre-release versioning, then fixed it. The current version is correct, but unfortunately evaluates as lower than the incorrect one which was missing the tilde. This means that anyone who happened to get python-pyunicorn-0.7.0a1-1.20230730gitmaster.fc40 installed will likely never see an update until 0.7.1 comes out (even a 0.7.0 final release will evaluate lower than "0.7.0a1"). In the other two cases, %autorelease is involved. autorelease is a great tool, but use it carefully when using snapshot builds. Without any additional guidance, %autorelease assumes that if you're building from a snapshot, it is a pre-release snapshot for the specified "Version". So it'll use a release like 0.(date)git(tag).(rel). If your snapshot is a post-release snapshot, you need to provide %autorelease with more cues about how to version it to get the desired effect. This is the problem for vim-devicons and patool. -- 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
A reminder: you cannot just "revert" package version bumps
nirik ran a script that checks for versioning issues in Rawhide today, and it found several: https://pagure.io/releng/issue/11922#comment-893797 Some of these followed a pattern, so I figured a reminder was in order. In all these cases, a new version was pushed to Rawhide, then "reverted" some time later: golang-github-nats-io-jwt - bumped to 2.4.1 in July, reverted to 1.2.2 in September golang-google-grpc - bumped to 1.58.0 in September, reverted to 1.48.0 in October; no 1.58.0 build ever landed, but the revert left the %release much lower than before python-mizani - bumped to 0.10.0 on September 10, reverted to 0.9.3 on September 12 python-pywlroots - bumped to 0.16.6 on November 4, reverted to 0.16.4 later the same day so the reminder is this: you cannot simply "downgrade" RPM package versions like this. Especially not if the upgraded version ever made it into a Rawhide compose. If a Rawhide user has your package installed, and got the upgraded version, they will be marooned on that build forever unless they manually run `dnf distro-sync`. A `dnf upgrade` will not downgrade the package to the build you now consider to be the "current" one. If you have to downgrade a package that made it to a Rawhide compose, you must use an epoch. If the package did not have an epoch before, make it `Epoch: 1`. If it had an epoch already, bump it by 1. People tend not to like epochs, so *try* not to have to do this. Be really certain before pushing out version bumps. If the "upgraded" build never made it into a compose (as is likely the case for python-pywlroots) you're *probably* okay, but it's still something to be careful about - for instance you might fall into the trap golang-google-grpc fell into with the %release tag. Thanks folks! -- 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
[Bug 2261658] New: rt: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261658 Bug ID: 2261658 Summary: rt: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: rt Assignee: rc040...@freenet.de Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: j...@tib.bs, perl-devel@lists.fedoraproject.org, rc040...@freenet.de Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora rt failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112410060 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix rt at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, rt will be orphaned. Before branching of Fedora 41, rt will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261658 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261658%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
[Bug 2261658] rt: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261658 --- Comment #2 from Fedora Release Engineering --- Created attachment 2013429 --> https://bugzilla.redhat.com/attachment.cgi?id=2013429=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261658 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261658%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 2261658] rt: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261658 --- Comment #3 from Fedora Release Engineering --- Created attachment 2013430 --> https://bugzilla.redhat.com/attachment.cgi?id=2013430=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261658 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261658%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 2261658] rt: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261658 --- Comment #1 from Fedora Release Engineering --- Created attachment 2013428 --> https://bugzilla.redhat.com/attachment.cgi?id=2013428=edit build.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261658 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261658%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
[Bug 2261642] New: perl-Module-CoreList-5.20240129 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2261642 Bug ID: 2261642 Summary: perl-Module-CoreList-5.20240129 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Module-CoreList Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mspa...@redhat.com, perl-devel@lists.fedoraproject.org, spo...@gmail.com, st...@silug.org Target Milestone: --- Classification: Fedora Releases retrieved: 5.20240129 Upstream release that is considered latest: 5.20240129 Current version/release in rawhide: 5.20231230-3.fc40 URL: https://metacpan.org/dist/Module-CoreList/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3080/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Module-CoreList -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261642 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261642%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
Orphan libtranslate and gnome-translate
I've orphaned gnome-translate and libtranslate packages. Both are unmaintained upstream more than a decade and do not work nowadays at all. For replacement just use translate-shell package (cmdline only). BTW, executable name "/usr/bin/translate" is now free (once upon a time someone wanted to take this name for themselves) :) Regards, Dmitry Butskoy -- ___ 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 2261451] perl-WWW-Google-Contacts: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261451 --- Comment #2 from Fedora Release Engineering --- Created attachment 2012857 --> https://bugzilla.redhat.com/attachment.cgi?id=2012857=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261451 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261451%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 2261451] perl-WWW-Google-Contacts: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261451 --- Comment #3 from Fedora Release Engineering --- Created attachment 2012858 --> https://bugzilla.redhat.com/attachment.cgi?id=2012858=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261451 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261451%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 2261452] perl-Wx-GLCanvas: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261452 --- Comment #1 from Fedora Release Engineering --- Created attachment 2012859 --> https://bugzilla.redhat.com/attachment.cgi?id=2012859=edit build.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261452 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261452%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
[Bug 2261451] New: perl-WWW-Google-Contacts: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261451 Bug ID: 2261451 Summary: perl-WWW-Google-Contacts: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: perl-WWW-Google-Contacts Assignee: avibra...@gmail.com Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: avibra...@gmail.com, perl-devel@lists.fedoraproject.org Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora perl-WWW-Google-Contacts failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112366561 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix perl-WWW-Google-Contacts at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, perl-WWW-Google-Contacts will be orphaned. Before branching of Fedora 41, perl-WWW-Google-Contacts will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261451 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261451%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
[Bug 2261452] perl-Wx-GLCanvas: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261452 --- Comment #2 from Fedora Release Engineering --- Created attachment 2012860 --> https://bugzilla.redhat.com/attachment.cgi?id=2012860=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261452 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261452%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 2261452] New: perl-Wx-GLCanvas: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261452 Bug ID: 2261452 Summary: perl-Wx-GLCanvas: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: perl-Wx-GLCanvas Assignee: mhron...@redhat.com Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mhron...@redhat.com, perl-devel@lists.fedoraproject.org Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora perl-Wx-GLCanvas failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112366867 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix perl-Wx-GLCanvas at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, perl-Wx-GLCanvas will be orphaned. Before branching of Fedora 41, perl-Wx-GLCanvas will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261452 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261452%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
[Bug 2261452] perl-Wx-GLCanvas: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261452 --- Comment #3 from Fedora Release Engineering --- Created attachment 2012861 --> https://bugzilla.redhat.com/attachment.cgi?id=2012861=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261452 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261452%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 2261449] perl-Prima: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261449 --- Comment #3 from Fedora Release Engineering --- Created attachment 2012852 --> https://bugzilla.redhat.com/attachment.cgi?id=2012852=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261449 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261449%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 2261451] perl-WWW-Google-Contacts: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261451 --- Comment #1 from Fedora Release Engineering --- Created attachment 2012856 --> https://bugzilla.redhat.com/attachment.cgi?id=2012856=edit build.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261451 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261451%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
[Bug 2261449] perl-Prima: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261449 --- Comment #1 from Fedora Release Engineering --- Created attachment 2012850 --> https://bugzilla.redhat.com/attachment.cgi?id=2012850=edit build.log file build.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261449 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261449%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
[Bug 2261449] perl-Prima: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261449 --- Comment #2 from Fedora Release Engineering --- Created attachment 2012851 --> https://bugzilla.redhat.com/attachment.cgi?id=2012851=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261449 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261449%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 2261449] New: perl-Prima: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261449 Bug ID: 2261449 Summary: perl-Prima: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: perl-Prima Assignee: ppi...@redhat.com Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: lkund...@v3.sk, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora perl-Prima failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112359659 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix perl-Prima at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, perl-Prima will be orphaned. Before branching of Fedora 41, perl-Prima will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261449 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261449%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
[Bug 2261448] perl-Curses: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261448 --- Comment #3 from Fedora Release Engineering --- Created attachment 2012849 --> https://bugzilla.redhat.com/attachment.cgi?id=2012849=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261448 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261448%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 2261448] perl-Curses: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261448 --- Comment #1 from Fedora Release Engineering --- Created attachment 2012847 --> https://bugzilla.redhat.com/attachment.cgi?id=2012847=edit build.log file build.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261448 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261448%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
[Bug 2261448] perl-Curses: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261448 --- Comment #2 from Fedora Release Engineering --- Created attachment 2012848 --> https://bugzilla.redhat.com/attachment.cgi?id=2012848=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261448 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261448%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 2261448] New: perl-Curses: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261448 Bug ID: 2261448 Summary: perl-Curses: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: perl-Curses Assignee: steve.tray...@cern.ch Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, steve.tray...@cern.ch Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora perl-Curses failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112344005 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix perl-Curses at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, perl-Curses will be orphaned. Before branching of Fedora 41, perl-Curses will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261448 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261448%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
[Bug 2261445] perl-Authen-Krb5-Admin: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261445 --- Comment #3 from Fedora Release Engineering --- Created attachment 2012840 --> https://bugzilla.redhat.com/attachment.cgi?id=2012840=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261445 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261445%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 2261445] perl-Authen-Krb5-Admin: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261445 --- Comment #2 from Fedora Release Engineering --- Created attachment 2012839 --> https://bugzilla.redhat.com/attachment.cgi?id=2012839=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261445 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261445%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 2261446] perl-Cairo: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261446 --- Comment #3 from Fedora Release Engineering --- Created attachment 2012843 --> https://bugzilla.redhat.com/attachment.cgi?id=2012843=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261446 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261446%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 2261446] perl-Cairo: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261446 --- Comment #2 from Fedora Release Engineering --- Created attachment 2012842 --> https://bugzilla.redhat.com/attachment.cgi?id=2012842=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261446 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261446%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 2261446] perl-Cairo: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261446 --- Comment #1 from Fedora Release Engineering --- Created attachment 2012841 --> https://bugzilla.redhat.com/attachment.cgi?id=2012841=edit build.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261446 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261446%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
[Bug 2261446] New: perl-Cairo: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261446 Bug ID: 2261446 Summary: perl-Cairo: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: perl-Cairo Assignee: spo...@gmail.com Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, spo...@gmail.com Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora perl-Cairo failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112341394 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix perl-Cairo at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, perl-Cairo will be orphaned. Before branching of Fedora 41, perl-Cairo will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261446 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261446%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
[Bug 2261445] New: perl-Authen-Krb5-Admin: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261445 Bug ID: 2261445 Summary: perl-Authen-Krb5-Admin: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: perl-Authen-Krb5-Admin Assignee: c...@plauener.de Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: c...@plauener.de, perl-devel@lists.fedoraproject.org Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora perl-Authen-Krb5-Admin failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112340152 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix perl-Authen-Krb5-Admin at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, perl-Authen-Krb5-Admin will be orphaned. Before branching of Fedora 41, perl-Authen-Krb5-Admin will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261445 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261445%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
[Bug 2261445] perl-Authen-Krb5-Admin: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261445 --- Comment #1 from Fedora Release Engineering --- Created attachment 2012838 --> https://bugzilla.redhat.com/attachment.cgi?id=2012838=edit build.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261445 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261445%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
Summary/Minutes from today's FESCo Meeting (2024-01-29)
Logs and minutes: https://zbyszek.fedorapeople.org/fesco-2024-01-29.2024-01-29-19.30.log.html https://zbyszek.fedorapeople.org/fesco-2024-01-29.2024-01-29-19.30.log.txt https://zbyszek.fedorapeople.org/fesco-2024-01-29.2024-01-29-19.30.minutes.html https://zbyszek.fedorapeople.org/fesco-2024-01-29.2024-01-29-19.30.minutes.txt Meeting summary --- * TOPIC: #3122 Consider changing maximum size for network install images (also affects Workstation) !fesco 3122 (@zbyszek:fedora.im, 19:32:10) * INFO: https://pagure.io/fesco/issue/3122#comment-893698 (@zbyszek:fedora.im, 19:34:38) * LINK: https://pagure.io/fesco/issue/3122#comment-893698 (@zbyszek:fedora.im, 19:34:48) * AGREED: APPROVED (+6, 0, 0) (@zbyszek:fedora.im, 19:37:35) * TOPIC: #3152 Change: Run Anaconda dir/image installations only in non-interactive text mode (@zbyszek:fedora.im, 19:37:54) * AGREED: APPROVED (+5, 0, -1) (@zbyszek:fedora.im, 19:57:48) * TOPIC: #3158 Change: Arm Minimal Image OS Build (@zbyszek:fedora.im, 19:58:58) * TOPIC: (Lack of) voting in FastTrack proposals (@zbyszek:fedora.im, 20:12:13) * ACTION: zbyszek to submit a draft for the Fesco page to mention the changing of the title for FastTrack issues. (@zbyszek:fedora.im, 20:19:01) * AGREED: FastTrack tickets must gain a [FastTrack] title addition and if they have not received enough votes in 48 hours, a FESCo member should send a reminder (+6, 0, 0) (@zbyszek:fedora.im, 20:21:39) * TOPIC: Next week's chair (@zbyszek:fedora.im, 20:21:58) * INFO: Next meeting will be February 12th. (@zbyszek:fedora.im, 20:24:08) * ACTION: Stephen Gallagher will chair the next meeting (in two weeks). (@zbyszek:fedora.im, 20:26:00) * TOPIC: Open Floor (@sgallagh:fedora.im, 20:26:19) * TOPIC: #3165 Requesting FESCo assistance with issue about plasma-x11 (@conan_kudo:matrix.org, 20:27:37) Meeting ended at 2024-01-29 20:34:20 Action items * zbyszek to submit a draft for the Fesco page to mention the changing of the title for FastTrack issues. * Stephen Gallagher will chair the next meeting (in two weeks). Because of a mishap (my error), the logs were not uploaded properly (https://pagure.io/releng/issue/11921). -- ___ 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 2261386] New: mod_perl: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261386 Bug ID: 2261386 Summary: mod_perl: FTBFS in Fedora rawhide/f40 Product: Fedora Version: rawhide Status: NEW Component: mod_perl Assignee: zonexpertconsult...@outlook.com Reporter: rel...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jor...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com, zonexpertconsult...@outlook.com Blocks: 2231791 (F40FTBFS) Target Milestone: --- Classification: Fedora mod_perl failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112327636 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix mod_perl at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, mod_perl will be orphaned. Before branching of Fedora 41, mod_perl will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2231791 [Bug 2231791] Fedora 40 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261386 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261386%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
[Bug 2261386] mod_perl: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261386 --- Comment #2 from Fedora Release Engineering --- Created attachment 2012653 --> https://bugzilla.redhat.com/attachment.cgi?id=2012653=edit root.log file root.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261386 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261386%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 2261386] mod_perl: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261386 --- Comment #1 from Fedora Release Engineering --- Created attachment 2012652 --> https://bugzilla.redhat.com/attachment.cgi?id=2012652=edit build.log file build.log too big, will only attach last 32768 bytes -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261386 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261386%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
[Bug 2261386] mod_perl: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261386 --- Comment #3 from Fedora Release Engineering --- Created attachment 2012654 --> https://bugzilla.redhat.com/attachment.cgi?id=2012654=edit state.log -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261386 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261386%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: Mass change of LicenseRef-KDE-Accepted-* licenses
Dne 29. 01. 24 v 13:58 Ben Beasley napsal(a): Could you please double-check this change? I noticed that in spacebar, LicenseRef-KDE-Accepted-GPL was the actual name of a license file in the %files section; this was replaced with (GPL-2.0-only OR GPL-3.0-only), which causes the package to FTBFS. Looking at the grep output you originally posted, it seems like plasma-phonebook has a similar problem, and kf6-kglobalaccel, kf6-kjobwidgets, and kf6-kservice had filenames in comments replaced, which won’t break their builds but isn’t correct either. Indeed. This possibility did not cross my mind. I fixed all of them and fixed my grep'o'foo script and find only the cases you reported. Nothing else. I checked scratch and it was mass rebuilt before my change, so it was build sucessfully. So I did not rebuilt it. I still appreciate that you are cleaning this up! And I appreciate you understand human mistake. Still - I am sorry for this. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys -- ___ 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/slic3r] PR #13: Convert to %autorelease and %autochangelog
zuul commented on the pull-request: `Convert to %autorelease and %autochangelog` that you are following: `` Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/00a475203c7b4ddf91316585ebd988f5 - [check-for-arches ](https://fedora.softwarefactory-project.io/zuul/build/7496df7f815c48de93c9ed6752c4fb66) : SUCCESS in 6m 11s - [check-for-eln ](https://fedora.softwarefactory-project.io/zuul/build/66743faa02a9449a8c3c70664d70ec87) : SUCCESS in 18s - [rpm-scratch-build ](https://fedora.softwarefactory-project.io/zuul/build/02199161aa3748a6b13a5f6458fd51dd) : SUCCESS in 23m 53s - [rpm-scratch-build-s390x ](https://fedora.softwarefactory-project.io/zuul/build/4b2670fd2e6c4b5897ee71d02294a91c) : FAILURE in 7m 55s (non-voting) - [rpm-scratch-build-ppc64le ](https://fedora.softwarefactory-project.io/zuul/build/abfc8f2f233f4e8493860f47f4628835) : SUCCESS in 40m 57s (non-voting) - [rpm-scratch-build-i686 ](https://fedora.softwarefactory-project.io/zuul/build/18b8bdc5be7d452daf1dfff8ef4e8a8c) : FAILURE in 7m 52s (non-voting) - [rpm-scratch-build-aarch64 ](https://fedora.softwarefactory-project.io/zuul/build/7065c5641aaa406ea425aa4dc3fe0bd6) : SUCCESS in 20m 04s (non-voting) - [rpm-linter ](https://fedora.softwarefactory-project.io/zuul/build/ee2cdb7e29a34615a258583a945f57e2) : SUCCESS in 6m 50s (non-voting) - [rpm-rpminspect ](https://fedora.softwarefactory-project.io/zuul/build/cb0fbde73b7b4ad586561ec054aabd5b) : FAILURE in 10m 17s (non-voting) - [check-for-sti-tests ](https://fedora.softwarefactory-project.io/zuul/build/8bb3e559c9df487aa8cdcc474112ff69) : SUCCESS in 15s - [check-for-fmf-tests ](https://fedora.softwarefactory-project.io/zuul/build/98c88cefff914576ae8b41ddcd62d5e2) : SUCCESS in 15s - [rpm-install-test ](https://fedora.softwarefactory-project.io/zuul/build/eefd7fad3ed14010bb42692815f25175) : SUCCESS in 2m 01s Skipped 3 jobs `` To reply, visit the link below https://src.fedoraproject.org/rpms/slic3r/pull-request/13 -- ___ 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
Package review ticket status change after approval
Hello folks, before all, I want to thank everyone putting their time in reviewing new package requests! That is a key task in distinguish Fedora among the other Linux distribution and ensure we have high quality packages in our repositories. That said, I'd like to make a request and maybe make all reviewers aware of a feature which was implemented some time ago. I've noticed many reviewers change the ticket status from ASSIGNED to POST when they flag the package as approved: I'd like to request to not do that. The Package Review Tracker webpages make a distinction between packages approved (fedora-review flag set to +) and packages approved AND being built in Fedora. That distinction relies on the ticket status change to POST, which is automatically set when the repository is created in src.fp.o. I think that distinction can be useful to see all packages that were approved, but for some reason the submitter never asked for the repository to be created. So, if you also think that is useful and can change what it may have become a routine for you, just set the review flag accordingly without changing the ticket status. BTW, for the future (if I find some spare time) I plan to change the interface of the Package Review Tracker webpages by moving from using colors to icons. That's because the colors are currently mutually exclusive i.e. whenever a ticket is marked NEEDSPONSOR, the green background will take precedence over all other descriptions. By using multiple icons, we can have better "visual categorization" (and, maybe, enhance the js filter). But before doing so, I'll make a preview of the change and post it here (or on Discussion) to get some feedback... Thanks Mattia -- ___ 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: runaway fork() in Lua script
https://bugzilla.redhat.com/show_bug.cgi?id=2254463 reappeared, this time on Fedora 39. The fix is known, it just needs to get built and released. On Mon, Jan 29, 2024 at 1:35 PM Richard Shaw wrote: > > On Mon, Jan 29, 2024 at 12:03 PM Jerry James wrote: >> >> For the second time in two days, running "fedpkg build" gave me a few >> dozen lines that say: >> >> warning: runaway fork() in Lua script >> >> before the usual build messages start appearing. Is this a known issue? > > > Just started seeing this after a `dnf update` and reboot... > > 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 -- ___ 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: runaway fork() in Lua script
On Mon, Jan 29, 2024 at 12:03 PM Jerry James wrote: > For the second time in two days, running "fedpkg build" gave me a few > dozen lines that say: > > warning: runaway fork() in Lua script > > before the usual build messages start appearing. Is this a known issue? > Just started seeing this after a `dnf update` and reboot... 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
runaway fork() in Lua script
For the second time in two days, running "fedpkg build" gave me a few dozen lines that say: warning: runaway fork() in Lua script before the usual build messages start appearing. Is this a known issue? It looks like I am not the only one to encounter this: https://github.com/QubesOS/qubes-issues/issues/8771 -- Jerry James http://www.jamezone.org/ -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 40 Mass Rebuild Finished
Hi all, Per the Fedora Linux f40 schedule and the challenges [1], we started a mass rebuild for Fedora Linux f40 on 2024-01-22. We did a mass rebuild for Fedora Linux f40 for changes like: - https://fedoraproject.org/wiki/Changes/GNUToolchainF40 - https://fedoraproject.org/wiki/Changes/Java21 check the tracker for more details: https://pagure.io/releng/issues?status=Open=mass+rebuild=f40=changes The mass rebuild was done in a side tag (f40-rebuild) and moved over to f40. Failures can be seen at https://kojipkgs.fedoraproject.org/mass-rebuild/f40-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f40-need-rebuild.html 21971 builds have been tagged into f40, there are currently 991 failed builds that need to be addressed by the package maintainers. FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng by dropping an email to our list [2], or joining #releng:fedoraproject.org on Matrix, or filing an issue in pagure [3]. Regards, Samyak Jain Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ -- ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-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
Fedora Linux 40 Mass Rebuild Finished
Hi all, Per the Fedora Linux f40 schedule and the challenges [1], we started a mass rebuild for Fedora Linux f40 on 2024-01-22. We did a mass rebuild for Fedora Linux f40 for changes like: - https://fedoraproject.org/wiki/Changes/GNUToolchainF40 - https://fedoraproject.org/wiki/Changes/Java21 check the tracker for more details: https://pagure.io/releng/issues?status=Open=mass+rebuild=f40=changes The mass rebuild was done in a side tag (f40-rebuild) and moved over to f40. Failures can be seen at https://kojipkgs.fedoraproject.org/mass-rebuild/f40-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f40-need-rebuild.html 21971 builds have been tagged into f40, there are currently 991 failed builds that need to be addressed by the package maintainers. FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng by dropping an email to our list [2], or joining #releng:fedoraproject.org on Matrix, or filing an issue in pagure [3]. Regards, Samyak Jain Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 1731721] perl-Font-AFM depends on files/directories from non-standard locations
https://bugzilla.redhat.com/show_bug.cgi?id=1731721 Ralf Corsepius changed: What|Removed |Added Resolution|--- |RAWHIDE Status|NEW |CLOSED Last Closed|2021-05-25 15:02:01 |2024-01-29 16:54:22 --- Comment #9 from Ralf Corsepius --- Another packaging regression caused by FPC lack of understanding. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1731721 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201731721%23c9 -- ___ 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 1731700] rt depends on files/directories from non-standard locations
https://bugzilla.redhat.com/show_bug.cgi?id=1731700 Ralf Corsepius changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |RAWHIDE Last Closed|2020-11-24 18:26:38 |2024-01-29 16:53:14 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1731700 -- ___ 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-ExtUtils-CppGuess] PR #2: Convert to %autorelease and %autochangelog
zuul commented on the pull-request: `Convert to %autorelease and %autochangelog` that you are following: `` Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/5ae0717deecf41f2a502d27b5140486c - [check-for-arches ](https://fedora.softwarefactory-project.io/zuul/build/0a3499db028849abbc31426858574226) : SUCCESS in 5m 53s - [check-for-eln ](https://fedora.softwarefactory-project.io/zuul/build/d3ec56c1ed5f4f14936ec4c8cdb91f9a) : SUCCESS in 19s - [rpm-scratch-build ](https://fedora.softwarefactory-project.io/zuul/build/c10359efba1f42338c293d93b48a2b08) : SUCCESS in 14m 27s - [rpm-scratch-build-s390x ](https://fedora.softwarefactory-project.io/zuul/build/74784a394539498ab14b381dafbef86a) : SUCCESS in 8m 50s (non-voting) - [rpm-scratch-build-ppc64le ](https://fedora.softwarefactory-project.io/zuul/build/cad84a7e2366415dbd0bd62b85b4fa28) : SUCCESS in 12m 26s (non-voting) - [rpm-scratch-build-i686 ](https://fedora.softwarefactory-project.io/zuul/build/4101fbbcc8a64596a11912ed0134c260) : SUCCESS in 16m 28s (non-voting) - [rpm-scratch-build-aarch64 ](https://fedora.softwarefactory-project.io/zuul/build/d6582b7e77e8489c942e226dec8d7272) : SUCCESS in 8m 26s (non-voting) - [rpm-linter ](https://fedora.softwarefactory-project.io/zuul/build/0870b354127c4cbe93560d2f436d199b) : SUCCESS in 10m 13s (non-voting) - [rpm-rpminspect ](https://fedora.softwarefactory-project.io/zuul/build/190efe98e9eb43f8bf5e3525a6f256b1) : SUCCESS in 16m 03s (non-voting) - [check-for-sti-tests ](https://fedora.softwarefactory-project.io/zuul/build/2d8dcf5a4e5840bb9937dfd4331742d6) : SUCCESS in 18s - [check-for-fmf-tests ](https://fedora.softwarefactory-project.io/zuul/build/99c2a4ed9b5c45efb145bba3b3c57c20) : SUCCESS in 17s - [rpm-install-test ](https://fedora.softwarefactory-project.io/zuul/build/953b947618824b619eb4ee34b3ff55ca) : SUCCESS in 1m 30s Skipped 3 jobs `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-ExtUtils-CppGuess/pull-request/2 -- ___ 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-Module-Build-WithXSpp] PR #1: Convert to %autorelease and %autochangelog
zuul commented on the pull-request: `Convert to %autorelease and %autochangelog` that you are following: `` Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/cf2bf27b41aa4f709db2ce8c459ceaa1 - [check-for-arches ](https://fedora.softwarefactory-project.io/zuul/build/7a08448be5954ad7aef92aad22809b36) : SUCCESS in 6m 56s - [check-for-eln ](https://fedora.softwarefactory-project.io/zuul/build/fba78a62a60d4d59b5102056a364c207) : SUCCESS in 20s - [rpm-scratch-build ](https://fedora.softwarefactory-project.io/zuul/build/3b41badc68384cfab6dd02816c7165b4) : SUCCESS in 11m 47s - [rpm-scratch-build-s390x ](https://fedora.softwarefactory-project.io/zuul/build/5fae911bc06a4d0fa2560f9ff5b9c21a) : SUCCESS in 8m 58s (non-voting) - [rpm-scratch-build-ppc64le ](https://fedora.softwarefactory-project.io/zuul/build/24e2b099ec4946df8a1c1f1aef6445b8) : SUCCESS in 22m 08s (non-voting) - [rpm-scratch-build-i686 ](https://fedora.softwarefactory-project.io/zuul/build/97719dd6f62f470883aac0fb3c282205) : SUCCESS in 8m 50s (non-voting) - [rpm-scratch-build-aarch64 ](https://fedora.softwarefactory-project.io/zuul/build/be02266d4a1b400497345ef9b2e12660) : SUCCESS in 14m 55s (non-voting) - [rpm-linter ](https://fedora.softwarefactory-project.io/zuul/build/1c4d395c8f674029b38025f0a827c7fc) : SUCCESS in 10m 14s (non-voting) - [rpm-rpminspect ](https://fedora.softwarefactory-project.io/zuul/build/c3f8536fbb544259a7ce2fef612cd6c0) : SUCCESS in 14m 37s (non-voting) - [check-for-sti-tests ](https://fedora.softwarefactory-project.io/zuul/build/361f6569b5554e24b860dc7a8ff05ff8) : SUCCESS in 15s - [check-for-fmf-tests ](https://fedora.softwarefactory-project.io/zuul/build/b4d0131c7aba45a1bc6de1d88ac9e07b) : SUCCESS in 15s - [rpm-install-test ](https://fedora.softwarefactory-project.io/zuul/build/3e2e5a6e44f6890530219886e9ec) : SUCCESS in 1m 32s Skipped 3 jobs `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Module-Build-WithXSpp/pull-request/1 -- ___ 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 2260493] Retiring perl-Test-Vars, needed by perl-Test-Apocalypse
https://bugzilla.redhat.com/show_bug.cgi?id=2260493 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED Link ID||CPAN 105792 Doc Type|--- |If docs needed, set a value --- Comment #1 from Petr Pisar --- I will retire perl-Test-Apocalypse. It's only a metamodule without any additional value. The only user in Fedora is perl-Test-Pod-No404s and that's only an optional test and the test should have been disabled for many years. Also perl-Test-Apocalypse upstream was not much active regarding this Test::Vars problem so far. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2260493 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260493%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
[rpms/perl-Growl-GNTP] PR #1: Convert to %autorelease and %autochangelog
zuul commented on the pull-request: `Convert to %autorelease and %autochangelog` that you are following: `` Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/38d17d49c2b743edb22bd4bb1903db8b - [check-for-arches ](https://fedora.softwarefactory-project.io/zuul/build/c40bb98dcf924394a017b7071dd5824e) : SUCCESS in 3m 53s - [check-for-eln ](https://fedora.softwarefactory-project.io/zuul/build/30bab1dd1fea44aa94789c22684d7748) : SUCCESS in 19s - [rpm-scratch-build ](https://fedora.softwarefactory-project.io/zuul/build/4d2847994b864365a368b7b77fe9ae39) : SUCCESS in 12m 27s - [rpm-scratch-build-s390x ](https://fedora.softwarefactory-project.io/zuul/build/9d3538ce5dec4b7c9642dabcc3877766) : SUCCESS in 9m 18s (non-voting) - [rpm-scratch-build-ppc64le ](https://fedora.softwarefactory-project.io/zuul/build/84a7ee2f861c4f098b8a82e9dd3b0275) : SUCCESS in 12m 26s (non-voting) - [rpm-scratch-build-i686 ](https://fedora.softwarefactory-project.io/zuul/build/7a5d45aff8c74f99ac51b206e69207f6) : SUCCESS in 15m 13s (non-voting) - [rpm-scratch-build-aarch64 ](https://fedora.softwarefactory-project.io/zuul/build/f46c246f3c5248a6af2e3b858da8747e) : SUCCESS in 9m 20s (non-voting) - [rpm-linter ](https://fedora.softwarefactory-project.io/zuul/build/25773c0057714b809e77247e6ef50251) : SUCCESS in 10m 04s (non-voting) - [rpm-rpminspect ](https://fedora.softwarefactory-project.io/zuul/build/b9f7ce103c004f71836c2c53494431f9) : SUCCESS in 7m 02s (non-voting) - [check-for-sti-tests ](https://fedora.softwarefactory-project.io/zuul/build/0c18607dff364b4fa17bfc5d8b8a0cc7) : SUCCESS in 18s - [check-for-fmf-tests ](https://fedora.softwarefactory-project.io/zuul/build/88cdc0da8ee64b88acc4d3a9acc62f32) : SUCCESS in 16s - [rpm-install-test ](https://fedora.softwarefactory-project.io/zuul/build/f0744d92b69347b4ac52bcb692cec4d6) : SUCCESS in 1m 29s Skipped 3 jobs `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Growl-GNTP/pull-request/1 -- ___ 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-ExtUtils-Typemaps-Default] PR #1: Convert to %autorelease and %autochangelog
zuul commented on the pull-request: `Convert to %autorelease and %autochangelog` that you are following: `` Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/be94edeec1da42878737fbfdec387606 - [check-for-arches ](https://fedora.softwarefactory-project.io/zuul/build/16c890e166e845628d6fa7d40366ab06) : SUCCESS in 3m 51s - [check-for-eln ](https://fedora.softwarefactory-project.io/zuul/build/6892683e567346da9252b8569ffde110) : SUCCESS in 20s - [rpm-scratch-build ](https://fedora.softwarefactory-project.io/zuul/build/9f754af18b9d479fa4746a19c73787f5) : SUCCESS in 12m 19s - [rpm-scratch-build-s390x ](https://fedora.softwarefactory-project.io/zuul/build/5a4273b358a945668ae1f2ede0574e37) : SUCCESS in 8m 16s (non-voting) - [rpm-scratch-build-ppc64le ](https://fedora.softwarefactory-project.io/zuul/build/795e00cf8f0645aea3bafb4bd6ff3086) : SUCCESS in 15m 52s (non-voting) - [rpm-scratch-build-i686 ](https://fedora.softwarefactory-project.io/zuul/build/89d7de95a5c54f038d02045943d24c25) : SUCCESS in 13m 01s (non-voting) - [rpm-scratch-build-aarch64 ](https://fedora.softwarefactory-project.io/zuul/build/d76e4fb81898410bb58719bf218dba09) : SUCCESS in 7m 51s (non-voting) - [rpm-linter ](https://fedora.softwarefactory-project.io/zuul/build/5efd514a8f434a3db52d3a5ff438b9fa) : SUCCESS in 4m 29s (non-voting) - [rpm-rpminspect ](https://fedora.softwarefactory-project.io/zuul/build/8b0007d14b60490c8d3e6d58f7b743ad) : SUCCESS in 8m 11s (non-voting) - [check-for-sti-tests ](https://fedora.softwarefactory-project.io/zuul/build/912724657f784eb89e78058a74988923) : SUCCESS in 17s - [check-for-fmf-tests ](https://fedora.softwarefactory-project.io/zuul/build/2602341b46d142fbb6f0dc04a17bfc36) : SUCCESS in 18s - [rpm-install-test ](https://fedora.softwarefactory-project.io/zuul/build/f61cd80d027b455281562463bc9d3f50) : SUCCESS in 1m 29s Skipped 3 jobs `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-ExtUtils-Typemaps-Default/pull-request/1 -- ___ 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-Wx-GLCanvas] PR #3: Convert to %autorelease and %autochangelog
zuul commented on the pull-request: `Convert to %autorelease and %autochangelog` that you are following: `` Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci https://fedora.softwarefactory-project.io/zuul/buildset/b0d9fce13169459f9639816dbfc7e188 - [check-for-arches ](https://fedora.softwarefactory-project.io/zuul/build/eb4487f64b404b35b407ffc938fa395f) : SUCCESS in 6m 38s - [check-for-eln ](https://fedora.softwarefactory-project.io/zuul/build/0c402998359f42818a0d28ff4b3222a2) : SUCCESS in 20s - [rpm-scratch-build ](https://fedora.softwarefactory-project.io/zuul/build/fd808a77425141828ce47557ca47cc3c) : FAILURE in 11m 52s - [rpm-scratch-build-s390x ](https://fedora.softwarefactory-project.io/zuul/build/a89a367093064b068f0396e90e1256a5) : FAILURE in 14m 29s (non-voting) - [rpm-scratch-build-ppc64le ](https://fedora.softwarefactory-project.io/zuul/build/16b26507565d4930bdc6f00705487e9d) : FAILURE in 17m 47s (non-voting) - [rpm-scratch-build-i686 ](https://fedora.softwarefactory-project.io/zuul/build/cd30bedb421d47bc8b464486eb831e9c) : FAILURE in 15m 30s (non-voting) - [rpm-scratch-build-aarch64 ](https://fedora.softwarefactory-project.io/zuul/build/7cad33cbf65740da9fcb879880d6c364) : FAILURE in 9m 35s (non-voting) - [rpm-linter ](https://fedora.softwarefactory-project.io/zuul/build/4304a9cde0994f0ca69d70a4314b99c9) : SKIPPED Skipped due to failed job rpm-scratch-build (non-voting) - [rpm-rpminspect ](https://fedora.softwarefactory-project.io/zuul/build/66576c9832db44338c0307a6cbf470eb) : SKIPPED Skipped due to failed job rpm-scratch-build (non-voting) - [check-for-sti-tests ](https://fedora.softwarefactory-project.io/zuul/build/9f960f0cf0db437bace30404c86b79a9) : SKIPPED Skipped due to failed job rpm-scratch-build - [check-for-fmf-tests ](https://fedora.softwarefactory-project.io/zuul/build/ed11910bfba146538a05735f58d584ad) : SKIPPED Skipped due to failed job rpm-scratch-build - [rpm-install-test ](https://fedora.softwarefactory-project.io/zuul/build/24cd8dee27ad4e01bdbee7c9d4f7ac31) : SKIPPED Skipped due to failed job rpm-scratch-build - [rpm-tmt-test ](https://fedora.softwarefactory-project.io/zuul/build/561edcd9cd454861a370ff3189289701) : SKIPPED Skipped due to failed job rpm-scratch-build - [rpm-sti-test ](https://fedora.softwarefactory-project.io/zuul/build/5374431acc8a4ef49f59185b3969fd24) : SKIPPED Skipped due to failed job rpm-scratch-build Skipped 1 job `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Wx-GLCanvas/pull-request/3 -- ___ 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
Schedule for Monday's FESCo Meeting (2024-01-29)
Following is the list of topics that will be discussed in the FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org on Matrix. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2024-01-29 19:30 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = Discussed and Voted in the Ticket = #3150 Change: GNU Toolchain F40 https://pagure.io/fesco/issue/3150 We voted on this in the 2024-01-22 meeting while discussing #3145. https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-01-22/fesco.2024-01-22-19.30.log.txt APPROVED (+8, 0, -0) #3147 Change: java-21-openjdk as the system JDK in F40 https://pagure.io/fesco/issue/3147 APPROVED (+6, 0, 0) #3143 adding @haskell-lang-sig to most Haskell packages https://pagure.io/fesco/issue/3143 APPROVED (+5, 0, -0) #3119 Numerous package git repos fail git-fsck, causing issues for mirroring, and need to be fixed https://pagure.io/fesco/issue/3119 FESCo approves the rewriting the history in those repositories using git filter-repo, with the old branches saved to refs/archive/ namespace. APPROVED (+4, 0, 0) #3116 Treating Change Proposals Post 'Accepted' Decision on Discourse https://pagure.io/fesco/issue/3116 Leave the change proposals open and let them auto-close from inactivity. APPROVED (+6, 0, 0) = Followups = = New business = #3122 Consider changing maximum size for network install images (also affects Workstation) https://pagure.io/fesco/issue/3122 #3152 Change: Run Anaconda dir/image installations only in non-interactive text mode https://pagure.io/fesco/issue/3152 #3158 Change: Arm Minimal Image OS Build https://pagure.io/fesco/issue/3158 (Lack of) voting in FastTrack proposals = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- ___ 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/slic3r] PR #13: Convert to %autorelease and %autochangelog
churchyard opened a new pull-request against the project: `slic3r` that you are following: `` Convert to %autorelease and %autochangelog `` To reply, visit the link below https://src.fedoraproject.org/rpms/slic3r/pull-request/13 -- ___ 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
[EPEL-devel] Re: Incompatible Upgrade Request - singularity-ce
On Mon, Jan 29, 2024 at 6:37 AM Neal Gompa wrote: > On Mon, Jan 29, 2024 at 2:32 PM David Trudgian via epel-devel > wrote: > > > > Dear all, > > > > Following advice from Neal elsewhere on this list [1], I’m requesting > that the singularity-ce EPEL packages may be updated to 4.1.0 following the > incompatible upgrade procedure. The justification for the upgrade is that > 3.x singularity-ce is no longer maintained upstream. Note that because > singularity-ce necessarily bundles many Go dependencies specified in > upstream go.mod/go.sum, lack of maintenance can quickly lead to inherited > security issues. > > > > Upstream singularity-ce (https://github.com/sylabs/singularity) > maintenance is limited to the latest x.y minor version, currently 4.1. The > upstream project has committed more formally to semantic versioning > conventions since 4.0.0, so any 4.y.z minor (y) and patch (z) version > updates are expected to be compatible upgrades for EPEL purposes. > > > > At present, singularity-ce in EPEL 7/8/9 has been held at 3.11.5 due to > incompatible changes. > > > > Incompatibilities from 3.11.5 -> 4.1.0 are as follows: > > > > (a) The CLI has split some functionality previously provided by the > `singularity remote` command into new `singularity registry` and > `singularity keyserver` commands. > > (b) The `singularity remote add` command now sets a newly added remote > as the default (unless suppressed). Previously the user had to set the > default remote manually. > > (c) The `—vm` flag to start `singularity` inside a Virtual Machine has > been removed. This was not intended to be user facing, but was used by a > separate and proprietary Singularity Desktop project that has been retired > for some time. `—vm` was unmaintained, and I don’t believe there is any > practical use outside of this context. > > > > (d) Bind mounts are now performed in the order in which they are > specified. Previously, image based bind mounts were performed before others. > > (e) Current working directory on the host is now created in the > container, restoring a behaviour from Singularity <3.6.0 unless suppressed. > > (f) If the current directory paths on the container and host contains > symlinks to different locations, the current working directory is not > mounted. > > > > The above are expected to have a minor impact on users. Arguably > (d)/(e)/(f) are bug fixes as they address issues reported by users as > unexpected behaviour. Changes (e)/(f) were also previously included in the > apptainer project's upgrade to their v1.2.0 that was not submitted as an > incompatible upgrade. > > > > Highlighting also for Dave Dykstra’s benefit that any thoughts around > the relevance of incompatible upgrade policy to (b) & (c) will also be > relevant to apptainer’s upcoming 1.3.0 upgrade, as apptainer has pulled > both of these changes from singularity-ce upstream. > > > > Other changes in behaviour from 3.11.5 -> 4.1.0 are compatible. > Configuration files do not need to be modified. > > > > This seems reasonable to me. > I agree with Neal, this looks good to me. Thank you for the nice explanation/write-up. Troy -- ___ 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
[EPEL-devel] Re: Incompatible Upgrade Request - singularity-ce
On Mon, Jan 29, 2024 at 2:32 PM David Trudgian via epel-devel wrote: > > Dear all, > > Following advice from Neal elsewhere on this list [1], I’m requesting that > the singularity-ce EPEL packages may be updated to 4.1.0 following the > incompatible upgrade procedure. The justification for the upgrade is that 3.x > singularity-ce is no longer maintained upstream. Note that because > singularity-ce necessarily bundles many Go dependencies specified in upstream > go.mod/go.sum, lack of maintenance can quickly lead to inherited security > issues. > > Upstream singularity-ce (https://github.com/sylabs/singularity) maintenance > is limited to the latest x.y minor version, currently 4.1. The upstream > project has committed more formally to semantic versioning conventions since > 4.0.0, so any 4.y.z minor (y) and patch (z) version updates are expected to > be compatible upgrades for EPEL purposes. > > At present, singularity-ce in EPEL 7/8/9 has been held at 3.11.5 due to > incompatible changes. > > Incompatibilities from 3.11.5 -> 4.1.0 are as follows: > > (a) The CLI has split some functionality previously provided by the > `singularity remote` command into new `singularity registry` and `singularity > keyserver` commands. > (b) The `singularity remote add` command now sets a newly added remote as the > default (unless suppressed). Previously the user had to set the default > remote manually. > (c) The `—vm` flag to start `singularity` inside a Virtual Machine has been > removed. This was not intended to be user facing, but was used by a separate > and proprietary Singularity Desktop project that has been retired for some > time. `—vm` was unmaintained, and I don’t believe there is any practical use > outside of this context. > > (d) Bind mounts are now performed in the order in which they are specified. > Previously, image based bind mounts were performed before others. > (e) Current working directory on the host is now created in the container, > restoring a behaviour from Singularity <3.6.0 unless suppressed. > (f) If the current directory paths on the container and host contains > symlinks to different locations, the current working directory is not mounted. > > The above are expected to have a minor impact on users. Arguably (d)/(e)/(f) > are bug fixes as they address issues reported by users as unexpected > behaviour. Changes (e)/(f) were also previously included in the apptainer > project's upgrade to their v1.2.0 that was not submitted as an incompatible > upgrade. > > Highlighting also for Dave Dykstra’s benefit that any thoughts around the > relevance of incompatible upgrade policy to (b) & (c) will also be relevant > to apptainer’s upcoming 1.3.0 upgrade, as apptainer has pulled both of these > changes from singularity-ce upstream. > > Other changes in behaviour from 3.11.5 -> 4.1.0 are compatible. Configuration > files do not need to be modified. > This seems reasonable to me. -- 真実はいつも一つ！/ Always, there's only one truth! -- ___ 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
[rpms/perl-Wx-GLCanvas] PR #3: Convert to %autorelease and %autochangelog
churchyard opened a new pull-request against the project: `perl-Wx-GLCanvas` that you are following: `` Convert to %autorelease and %autochangelog `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Wx-GLCanvas/pull-request/3 -- ___ 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-Module-Build-WithXSpp] PR #1: Convert to %autorelease and %autochangelog
churchyard opened a new pull-request against the project: `perl-Module-Build-WithXSpp` that you are following: `` Convert to %autorelease and %autochangelog `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Module-Build-WithXSpp/pull-request/1 -- ___ 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-Growl-GNTP] PR #1: Convert to %autorelease and %autochangelog
churchyard opened a new pull-request against the project: `perl-Growl-GNTP` that you are following: `` Convert to %autorelease and %autochangelog `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Growl-GNTP/pull-request/1 -- ___ 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-ExtUtils-Typemaps-Default] PR #1: Convert to %autorelease and %autochangelog
churchyard opened a new pull-request against the project: `perl-ExtUtils-Typemaps-Default` that you are following: `` Convert to %autorelease and %autochangelog `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-ExtUtils-Typemaps-Default/pull-request/1 -- ___ 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-ExtUtils-CppGuess] PR #2: Convert to %autorelease and %autochangelog
churchyard opened a new pull-request against the project: `perl-ExtUtils-CppGuess` that you are following: `` Convert to %autorelease and %autochangelog `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-ExtUtils-CppGuess/pull-request/2 -- ___ 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
[EPEL-devel] Incompatible Upgrade Request - singularity-ce
Dear all, Following advice from Neal elsewhere on this list [1], I’m requesting that the singularity-ce EPEL packages may be updated to 4.1.0 following the incompatible upgrade procedure. The justification for the upgrade is that 3.x singularity-ce is no longer maintained upstream. Note that because singularity-ce necessarily bundles many Go dependencies specified in upstream go.mod/go.sum, lack of maintenance can quickly lead to inherited security issues. Upstream singularity-ce (https://github.com/sylabs/singularity) maintenance is limited to the latest x.y minor version, currently 4.1. The upstream project has committed more formally to semantic versioning conventions since 4.0.0, so any 4.y.z minor (y) and patch (z) version updates are expected to be compatible upgrades for EPEL purposes. At present, singularity-ce in EPEL 7/8/9 has been held at 3.11.5 due to incompatible changes. Incompatibilities from 3.11.5 -> 4.1.0 are as follows: (a) The CLI has split some functionality previously provided by the `singularity remote` command into new `singularity registry` and `singularity keyserver` commands. (b) The `singularity remote add` command now sets a newly added remote as the default (unless suppressed). Previously the user had to set the default remote manually. (c) The `—vm` flag to start `singularity` inside a Virtual Machine has been removed. This was not intended to be user facing, but was used by a separate and proprietary Singularity Desktop project that has been retired for some time. `—vm` was unmaintained, and I don’t believe there is any practical use outside of this context. (d) Bind mounts are now performed in the order in which they are specified. Previously, image based bind mounts were performed before others. (e) Current working directory on the host is now created in the container, restoring a behaviour from Singularity <3.6.0 unless suppressed. (f) If the current directory paths on the container and host contains symlinks to different locations, the current working directory is not mounted. The above are expected to have a minor impact on users. Arguably (d)/(e)/(f) are bug fixes as they address issues reported by users as unexpected behaviour. Changes (e)/(f) were also previously included in the apptainer project's upgrade to their v1.2.0 that was not submitted as an incompatible upgrade. Highlighting also for Dave Dykstra’s benefit that any thoughts around the relevance of incompatible upgrade policy to (b) & (c) will also be relevant to apptainer’s upcoming 1.3.0 upgrade, as apptainer has pulled both of these changes from singularity-ce upstream. Other changes in behaviour from 3.11.5 -> 4.1.0 are compatible. Configuration files do not need to be modified. Many Thanks, Dave Trudgian [1] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/IQENLTYUAIMOTAX4LUWHYINOPSCRWCIS/ -- ___ 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
[EPEL-devel] Canceling this weeks EPEL Steering Committee meeting
Hello, Many of the EPEL Steering Committee members will be at a conference this Wedensday. We have also changed the meeting time to 1800 UTC (Same date and location). We don't have much (or anything) to cover. Unless something dramatic comes up. I would like to cancel this weeks meeting. Troy -- ___ 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 2251788] perl-Net-DNS-1.43 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2251788 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Fixed In Version||perl-Net-DNS-1.43-1.fc40 Resolution|--- |ERRATA Last Closed||2024-01-29 14:22:16 --- Comment #10 from Fedora Update System --- FEDORA-2024-bf9bb8504e 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=2251788 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251788%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
[Bug 2251788] perl-Net-DNS-1.43 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2251788 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #9 from Fedora Update System --- FEDORA-2024-bf9bb8504e has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-bf9bb8504e -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2251788 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251788%23c9 -- ___ 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
[Test-Announce] [Test Day] Fedora 40 KDE Plasma 6 2024-01-29 through 2024-02-05
Hey Folks, KDE SIG x Fedora QA hosts the KDE Plasma 6 Test Week. If you are willing to test new Desktop Environments or use KDE for some time; this is your time. Contribute to testing the new KDE and finding bugs ahead of the F40 release. The instructions are simple, and can be found in the wiki[0] and the results can be submitted on the results page[1] [0] https://fedoraproject.org/wiki/Test_Day:2024-01-29_KDE_Plasma_6_Test_Week [1] https://testdays.fedoraproject.org/events/174 Happy Testing! -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- ___ 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
[rpms/perl-Net-DNS] PR #5: 1.43 bump (rhbz#2251788)
jplesnik merged a pull-request against the project: `perl-Net-DNS` that you are following. Merged pull-request: `` 1.43 bump (rhbz#2251788) `` https://src.fedoraproject.org/rpms/perl-Net-DNS/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: HELP! What's up with OpenVDB?
On Mon, 29 Jan 2024 at 13:03, Richard Shaw wrote: > > On Mon, Jan 29, 2024 at 4:16 AM Jonathan Wakely wrote: >> >> On Sun, 28 Jan 2024 at 15:18, Richard Shaw wrote: >> > >> > Well I upped the memory to 10GB and got it to build but the issue on i686 >> > with the wrong tbb package being pulled in has not been corrected by any >> > of the 4 maintainers of the package. >> >> I fixed tbb to stop installing tbb32.pc so the underlying cause should >> be fixed in tbb-2021.11.0-5.fc40 and rebuilding openvdb should get the >> right tbb now. > > > Not sure why it didn't work then, but it doesn't change the fact that the BR > hadn't been updated in a very long time, using version 3 instead of date type > release format. The last standard version release was 4.4 in 2016. Doh, I thought I'd already waived the gating CI failures for tbb-2021.11.0-5 but I hadn't. I've done it now: https://bodhi.fedoraproject.org/updates/FEDORA-2024-115f00ec5c The annocheck failures will be addressed ASAP. > > More than likely all of the BRs need a refresh to the cmake format if it's > supported by the package. > > 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 -- ___ 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: HELP! What's up with OpenVDB?
I opened a PR on calligra[1] at the leaf of the remaining i686 dependency chain to start the process of dropping i686, because even if we get openvdb working now, there’s no good reason to keep i686 versions of these packages in the future. The EncourageI686LeafRemoval Change was specifically designed to help avoid this kind of extra work to support building packages nobody is using on a multilib-only architecture. Now that I’ve done this, I see that the deed is already done in openvdb, OpenImageIO, and OpenColorIO. So once the calligra PR is merged, this should be cleanly resolved. [1] https://src.fedoraproject.org/rpms/calligra/pull-request/1 On 1/29/24 08:20, Richard Shaw wrote: On Mon, Jan 29, 2024 at 7:13 AM Sérgio Basto wrote: > > Well I just re-tried openvdb with _smp_build_ncpus 1 and it still > failed so I don't think we have a choice at this point. Perhaps it > was hitting the 4GB max per process due to being 32bit? > Have you try set in build the ulimit [1] . On copr, copr already set the max number of files already by default [2] have you check if you can build it on copr ? No, and I don't have the time, it's not even my package, I just need it "fixed" so I can build OpenImageIO and its dependencies in my side-tag that should have been merged already. Also, I'm not sure there's any compelling reason to "save" OpenVDB or its dependencies on i686 but if someone wants to go to the trouble I'll throw away my side tag and start over, again... Thanks, Richard -- ___ devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-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
[rpms/perl-Net-DNS] PR #5: 1.43 bump (rhbz#2251788)
jplesnik opened a new pull-request against the project: `perl-Net-DNS` that you are following: `` 1.43 bump (rhbz#2251788) `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Net-DNS/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: List of long term FTBFS packages to be retired in February
On Thu, Jan 25, 2024 at 02:48:19PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Jan 25, 2024 at 03:25:02PM +0100, Sandro wrote: > > On 24-01-2024 17:38, Miro Hrončok wrote: > > > Dear maintainers. > > > > > > Based on the current fail to build from source policy, the following > > > packages > > > should be retired from Fedora 40 approximately one week before branching. > > > > > > > > > yaksa zbyszek > > > > I updated and build yaksa and checked that mpich is still building against > > the updated version. We have quite a few packages depending on mpich in the > > neuro-sig pool of packages, so we wouldn't want to see mpich going FTBFS. > > > > @zbyszek, feel free to add neuro-sig as co-maintainers to the package. For > > now there's a PR [1] for you. > > > > [1] https://src.fedoraproject.org/rpms/yaksa/pull-request/1 > Thanks! I'll merge this when the CI passes. > > I cannot log in to src.fp.o unfortunately, so I can't change the > settings. I'll try to remember to do that later. FTR, that's been done. The login worked, it was just rely slow. Zbyszek -- ___ 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: List of long term FTBFS packages to be retired in February
On Wed, Jan 24, 2024 at 05:38:59PM +0100, Miro Hrončok wrote: > infinipath-psm honli I think this project should be retired. The upstream repo has been archives with a message that Intel no longer supports this project. I'll rebuild mpich without this dependency. Zbyszek -- ___ 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: HELP! What's up with OpenVDB?
On Mon, Jan 29, 2024 at 7:13 AM Sérgio Basto wrote: > > > > Well I just re-tried openvdb with _smp_build_ncpus 1 and it still > > failed so I don't think we have a choice at this point. Perhaps it > > was hitting the 4GB max per process due to being 32bit? > > > > Have you try set in build the ulimit [1] . > On copr, copr already set the max number of files already by default > [2] have you check if you can build it on copr ? > No, and I don't have the time, it's not even my package, I just need it "fixed" so I can build OpenImageIO and its dependencies in my side-tag that should have been merged already. Also, I'm not sure there's any compelling reason to "save" OpenVDB or its dependencies on i686 but if someone wants to go to the trouble I'll throw away my side tag and start over, again... 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: HELP! What's up with OpenVDB?
On Sun, 2024-01-28 at 15:57 -0600, Richard Shaw wrote: > On Sun, Jan 28, 2024 at 9:55 AM Ben Beasley > wrote: > > Blender already excludes i686: > > > > https://src.fedoraproject.org/rpms/blender/blob/8088da10c20e53ab0e1dd5de6fd3a2344bd288aa/f/blender.spec#_207 > > > > So does prusa-slicer: > > > > https://src.fedoraproject.org/rpms/prusa-slicer/blob/44359e4b53c503cb61a60842abf991a01d1cb9db/f/prusa-slicer.spec#_68 > > > > Packages depending directly on openvdb are: > > > > $ fedrq wrsrc -s openvdb > > OpenImageIO-2.4.17.0-1.fc40.src > > blender-1:4.0.2-1.fc40.src > > luxcorerender-2.7-0.10.beta1.fc40.src > > openvkl-2.0.0-5.fc40.src > > prusa-slicer-2.4.2-13.fc40.src > > usd-23.11-2.fc40.src > > > > Of these, it looks like only OpenImageIO builds on i686. Packages > > depending on it are: > > > > $ fedrq wrsrc -s OpenImageIO > > OpenColorIO-2.2.1-6.fc40.src > > blender-1:4.0.2-1.fc40.src > > embree-4.3.0-2.fc40.src > > luxcorerender-2.7-0.10.beta1.fc40.src > > oidn-2.1.0-1.fc40.src > > openshadinglanguage-1.12.14.0-9.fc40.src > > usd-23.11-2.fc40.src > > > > Of those, only OpenColorIO builds on i686. Packages depending on it > > are: > > > > $ fedrq wrsrc -s OpenColorIO > > OpenImageIO-2.4.17.0-1.fc40.src > > blender-1:4.0.2-1.fc40.src > > calligra-3.2.1-25.fc39.src > > krita-5.2.2-1.fc40.src > > luxcorerender-2.7-0.10.beta1.fc40.src > > usd-23.11-2.fc40.src > > > > Of those, only calligra builds on i686, and it’s a leaf package. > > So, if > > I haven’t missed anything, as long as i686 support is dropped from > > all > > of calligra, OpenColorIO, OpenImageIO, and openvdb, then it should > > be OK. > > > > > Well I just re-tried openvdb with _smp_build_ncpus 1 and it still > failed so I don't think we have a choice at this point. Perhaps it > was hitting the 4GB max per process due to being 32bit? > Have you try set in build the ulimit [1] . On copr, copr already set the max number of files already by default [2] have you check if you can build it on copr ? [1] %build ulimit -n 4096 [2] https://pagure.io/fedora-infra/ansible/blob/main/f/roles/copr/backend/files/provision/files/mock/site-defaults.cfg https://pagure.io/fedora-infra/ansible/blob/main/f/roles/copr/backend/files/provision/provision_builder_tasks.yml#_176-186 > 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 -- 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: HELP! What's up with OpenVDB?
On Mon, Jan 29, 2024 at 4:16 AM Jonathan Wakely wrote: > On Sun, 28 Jan 2024 at 15:18, Richard Shaw wrote: > > > > Well I upped the memory to 10GB and got it to build but the issue on > i686 with the wrong tbb package being pulled in has not been corrected by > any of the 4 maintainers of the package. > > I fixed tbb to stop installing tbb32.pc so the underlying cause should > be fixed in tbb-2021.11.0-5.fc40 and rebuilding openvdb should get the > right tbb now. > Not sure why it didn't work then, but it doesn't change the fact that the BR hadn't been updated in a very long time, using version 3 instead of date type release format. The last standard version release was 4.4 in 2016. More than likely all of the BRs need a refresh to the cmake format if it's supported by the package. 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: Mass change of LicenseRef-KDE-Accepted-* licenses
Miroslav, Could you please double-check this change? I noticed that in spacebar, LicenseRef-KDE-Accepted-GPL was the actual name of a license file in the %files section; this was replaced with (GPL-2.0-only OR GPL-3.0-only), which causes the package to FTBFS. Looking at the grep output you originally posted, it seems like plasma-phonebook has a similar problem, and kf6-kglobalaccel, kf6-kjobwidgets, and kf6-kservice had filenames in comments replaced, which won’t break their builds but isn’t correct either. I still appreciate that you are cleaning this up! Thanks, Ben Beasley (FAS: music) On 1/23/24 04:52, Miroslav Suchý wrote: Lots of packages in Fedora use license LicenseRef-KDE-Accepted-GPL and LicenseRef-KDE-Accepted-LGPL. These licenses were never approved. It took lots of time to discuss it and document it. We finally come with: https://docs.fedoraproject.org/en-US/legal/update-existing-packages/#_licenseref_kde_accepted (copy for your convience) > KDE project uses LicenseRef-KDE-Accepted-* licenses. This was discussed here and here. The consensus is that upstream license LicenseRef-KDE-Accepted-GPL should be replaced in Fedora by GPL-2.0-only OR GPL-3.0-only. And upstream license LicenseRef-KDE-Accepted-LGPL should be replaced by LGPL-2.1-only OR LGPL-3.0-only. It is used 123 times in our spec files (full list at the bottom of this email). I am willing to do the mass change (with my proven package hat on). I welcome your feedback. If no one stops me with a reason by end of this month, I will do the change early next month. $ grepLicenseRef-KDE-Accepted * akonadiconsole.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-KDE-Accepted-GPL akonadi-mime.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND LGPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-only AND LicenseRef-KDE-Accepted-LGPL akonadi-search.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-or-later AND LGPL-2.1-only AND LGPL-2.1-or-later AND LGPL-3.0-only AND LicenseRef-KDE-Accepted-GPL AND LicenseRef-KDE-Accepted-LGPL AND (MIT OR Apache-2.0) AND MIT calendarsupport.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-or-later AND LicenseRef-KDE-Accepted-GPL incidenceeditor.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-or-later AND LicenseRef-KDE-Accepted-GPL kactivitymanagerd.spec:License: CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.1-only AND LGPL-3.0-only AND LicenseRef-KDE-Accepted-GPL AND LicenseRef-KDE-Accepte d-LGPL kalendar.spec:License: BSD-2-Clause AND BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND LGPL-2.0-or-later AND LGPL-2.1-only A ND LGPL-2.1-or-later AND LGPL-3.0-only AND LGPL-3.0-or-later AND LicenseRef-KDE-Accepted-GPL AND LicenseRef-KDE-Accepted-LGPL kdepim-addons.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-only AND LGPL-2.0-or-later AND LGPL-3.0-only AND LicenseRef-KDE-Acce pted-GPL AND LicenseRef-KDE-Accepted-LGPL kdepim-runtime.spec:License: AGPL-3.0-or-later AND BSD-2-Clause AND BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND LGPL-2.0-only AN D LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-only AND LGPL-3.0-or-later AND LicenseRef-KDE-Accepted-GPL AND LicenseRef-KDE-Accepted-LGPL kdeplasma-addons.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND LGPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-only AND LGPL-2.1-or-later AND LGPL-3.0-only AND LGPL-3.0-or-later AND LicenseRef-KDE-Accepted-GPL AND LicenseRef-KDE-Accepted-LGPL AND MIT kf5-akonadi-mime.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND LGPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-only AND LicenseRef-KDE-Accepted-LGPL kf5-akonadi-search.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-or-later AND LGPL-2.1-only AND LGPL-2.1-or-later AND LGPL-3.0-o nly AND LicenseRef-KDE-Accepted-GPL AND LicenseRef-KDE-Accepted-LGPL kf5-akonadi-server.spec:License: BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef -KDE-Accepted-GPL AND MIT kf5-attica.spec:License: CC0-1.0 AND LGPL-2.0-or-later AND LGPL-2.1-only AND LGPL-3.0-only AND LicenseRef-KDE-Accepted-LGPL kf5-bluez-qt.spec:License: CC0-1.0, LGPL-2.1-only AND LGPL-2.1-or-later AND LGPL-3.0-only AND LicenseRef-KDE-Accepted-LGPL kf5-calendarsupport.spec:License:
Re: Announce: Log Detective - AI tool to analyze build logs failures
Hello all, I recorded a very short video showing how you can contribute to the Log Detective project. https://www.youtube.com/watch?v=_-O7ryKCnlQ Any help will be greatly appreciated :-) Jakub On Wed, Jan 17, 2024 at 8:26 PM Jiri Kyjovsky wrote: > Hello Tristan, > > We store the data in json format. You can access and download the data > directly at our main page at the bottom - "Download collected data". Or via > https://log-detective.com/download > > Cheers > Jiri > -- > ___ > 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
Intend to unretire stgit
Hi, I intend to get stgit unretired and want to maintain it in the future. The package has been in Fedora up to f38 but has since been orphaned and, following that, retired. The reason for orphaning it was lack of time of the maintainer, especially as stgit got rewritten in Rust and required significant packaging effort to get all dependencies into Fedora. The dependencies are now all packaged (thanks to all the packagers dealing with these numerous Rust dependencies!). As stgit has been retired for a while, a re-review is needed. I already created the review request for stgit at [1]. Thanks, Felix [1]: https://bugzilla.redhat.com/show_bug.cgi?id=2260849 -- ___ 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
Spin / Lab Keepalive for F40 Request
Good evening folks, FESco previously approved a requirement[1] that Spin/Labs owners send a keepalive request in order to keep building the spin or lab. I have opened Pagure issues[2] for all Spins and Labs for this release[3]. If you are the owner of one of those spins and labs, please reply in the appropriate ticket by Friday February 2nd 2024 to indicate the spin should continue to be produced. If there is a spin or lab that does not have an open ticket, please create one[4]. The reasoning for this is to not ship spins that are not actively maintained. Future improvements to the release process that will allow for teams to self-publish solutions will eventually remove the need for these keepalives. Apologies for the lateness of this request and I appreciate your help confirming. Kindest regards, Aoife [1] https://pagure.io/fesco/issue/1972 [2] https://pagure.io/fedora-pgm/schedule/issues?status=Open=spins+keepalive [3] https://docs.fedoraproject.org/en-US/releases/f40/spins/ [4] https://pagure.io/fedora-pgm/schedule/new_issue -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-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
Orphaned packages looking for new maintainers
Report started at 2024-01-28 16:04:44 UTC The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/ Full report available at: https://a.gtmx.me/orphans/orphans.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager-dashboard.fedoraproject.org/ For all orphaned packages, see https://packager-dashboard.fedoraproject.org/orphan Package (co)maintainersStatus Change 3proxy orphan 3 weeks ago applet-window-buttons @kde-sig, orphan0 weeks ago bismuth@kde-sig, orphan0 weeks ago cdsclient @astro-sig, orphan 4 weeks ago csmith orphan 4 weeks ago drumstick0 orphan, yanqiyu 1 weeks ago elpa @scitech_sig, orphan3 weeks ago kpipewire5 @kde-sig, orphan2 weeks ago lightlyorphan 0 weeks ago php-PHP-CSS-Parser orphan 3 weeks ago plasma-bigscreen @kde-sig, orphan0 weeks ago python-GridDataFormats @scitech_sig, orphan3 weeks ago python-compressed-rtf orphan 4 weeks ago python-extractcode @python-packagers-sig, orphan 0 weeks ago python-flit@epel-packagers-sig, @python- 0 weeks ago packagers-sig, orphan, salimma python-jupyter-collaboration orphan 2 weeks ago python-jupyter-server-fileid orphan 2 weeks ago python-jupyter-ydocorphan 2 weeks ago python-kaitaistructorphan 3 weeks ago python-maya@neuro-sig, orphan 5 weeks ago python-mmtf@scitech_sig, orphan3 weeks ago python-mrcfile orphan 3 weeks ago python-red-black-tree-mod orphan 4 weeks ago python-represent orphan 0 weeks ago python-y-py@python-packagers-sig, orphan 2 weeks ago python-ypy-websocket orphan 2 weeks ago qterm orphan 4 weeks ago rubygem-hrxjcpunk, orphan, tdawson 5 weeks ago rubygem-linked-listjcpunk, orphan, tdawson 5 weeks ago rubygem-rubygems-mirror@ruby-packagers-sig, orphan 1 weeks ago rust-lib0 @rust-sig, orphan 2 weeks ago rust-yrs @rust-sig, orphan 2 weeks ago scamp @astro-sig, orphan 4 weeks ago sphinxbase @epel-packagers-sig, orphan 0 weeks ago tachyon@scitech_sig, orphan3 weeks ago virtme orphan 3 weeks ago xdrawchem @scitech_sig, orphan3 weeks ago The following packages require above mentioned packages: Depending on: applet-window-buttons (1), status change: 2024-01-24 (0 weeks ago) maui-mauikit (maintained by: thunderbirdtr) maui-mauikit-2.1.1-4.fc39.i686 requires applet-window-buttons = 0.11.1-7.fc39 maui-mauikit-2.1.1-4.fc39.x86_64 requires applet-window-buttons = 0.11.1-7.fc39 Depending on: cdsclient (1), status change: 2023-12-29 (4 weeks ago) scamp (maintained by: @astro-sig, orphan) scamp-2.10.0-5.fc38.src requires cdsclient = 3.84-16.fc39 scamp-2.10.0-5.fc38.x86_64 requires cdsclient = 3.84-16.fc39 Depending on: drumstick0 (1), status change: 2024-01-18 (1 weeks
Spin / Lab Keepalive for F40 Request
Good evening folks, FESco previously approved a requirement[1] that Spin/Labs owners send a keepalive request in order to keep building the spin or lab. I have opened Pagure issues[2] for all Spins and Labs for this release[3]. If you are the owner of one of those spins and labs, please reply in the appropriate ticket by Friday February 2nd 2024 to indicate the spin should continue to be produced. If there is a spin or lab that does not have an open ticket, please create one[4]. The reasoning for this is to not ship spins that are not actively maintained. Future improvements to the release process that will allow for teams to self-publish solutions will eventually remove the need for these keepalives. Apologies for the lateness of this request and I appreciate your help confirming. Kindest regards, Aoife [1] https://pagure.io/fesco/issue/1972 [2] https://pagure.io/fedora-pgm/schedule/issues?status=Open=spins+keepalive [3] https://docs.fedoraproject.org/en-US/releases/f40/spins/ [4] https://pagure.io/fedora-pgm/schedule/new_issue -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Orphaned packages looking for new maintainers
Orphaned packages looking for new maintainers -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
List of long term FTBFS packages to be retired in February
Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 40 approximately one week before branching. 5 weekly reminders are required, hence the retirement will happen approximately in 5 weeks, i.e. around 2024-02-28. Since this is unfortunately after the branching, packages will be retired on rawhide and f40. I apologize for starting this process a bit later than required again. Unfortunately, I had other work obligations. Volunteers to take over this are always welcome. Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The packages in rawhide were not successfully built at least since Fedora 37. This report is based on dist tags. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb If you see a package that was built, please let me know. If you see a package that should be exempted from the process, please let me know and we can work together to get a FESCo approval for that. If you see a package that can be rebuilt, please do so. Package (co)maintainers cl-asdf green erlang-jose bowlofeggs, erlang-maint-sig, jcline, peter fwtsbenzea ghdlsailer git-secrets keesdejong golang-github-acme-lego eclipseo, go-sig golang-github-eclesh-welford abulimov, dcavalca, go-sig golang-github-gatherstars-com-jwzeclipseo, go-sig golang-github-genuinetools-pkg eclipseo, go-sig golang-github-gobs-prettyeclipseo, go-sig golang-github-google-gopacketgo-sig, salimma golang-github-jhillyerd-enmime eclipseo, go-sig golang-github-pierrre-compareeclipseo, go-sig golang-github-smartystreets-goconvey alexsaezm, go-sig, jchaloup golang-gopkg-square-jose-2 alexsaezm, go-sig golang-gvisoreclipseo, elmarco, go-sig golang-opentelemetry-otel-0.20 alexsaezm, go-sig golang-sigs-k8s-kustomizedcavalca, go-sig golang-vitesseclipseo, go-sig infinipath-psm honli j4-dmenu-desktop ibotty jackson-dataformats-binary mbooth jackson-dataformats-text mbooth java-1.8.0-openjdk-aarch32 akasko, jvanek jreenrdieter kdevelop-pg-qt jgrulich, kde-sig, rdieter, than libdeltacloudclalance libva-v4l2-request kwizart, rathann lmms thm lxc hguemar, sagarun, thm mingw-clucenegreghellings mingw-cppunitkwizart mingw-dirac kwizart mingw-speexdsp janisozaur nbd-runner xiubli nodejs-generic-pool patches, piotrp ofononjha, thunderbirdtr openni-primesensecottsay, jkastner, rmattes pcmciautils harald pesign-test-app javierm, nfrayer, pjones, rwood pthsem ixs rust-drg jbtrystram, rust-sig telepathy-gabble aperezbios yaksazbyszek The following packages require above mentioned packages: Depending on: cl-asdf (5) common-lisp-controller (maintained by: green) common-lisp-controller-7.4-26.fc39.noarch requires cl-asdf emacs-slime (maintained by: bkreuter, salimma) emacs-slime-2:2.28-2.fc39.noarch requires common-lisp-controller emacs-slime-2:2.28-2.fc39.src requires common-lisp-controller sbcl (maintained by: green, rdieter) sbcl-2.3.11-1.fc40.src requires common-lisp-controller sbcl-2.3.11-1.fc40.x86_64 requires common-lisp-controller maxima (maintained by: jamatos, rdieter) maxima-5.45.1-6.fc40.src requires sbcl wxMaxima (maintained by: jamatos, rdieter) wxMaxima-20.12.1-10.fc39.x86_64 requires maxima Depending on: erlang-jose (1) erlang-p1_acme (maintained by: bowlofeggs, erlang-maint-sig, peter) erlang-p1_acme-1.0.8-6.fc38.noarch requires erlang-jose erlang-p1_acme-1.0.8-6.fc38.src requires erlang-jose Depending on: golang-github-eclesh-welford (1) golang-github-facebook-time (maintained by: abulimov, dcavalca, go-sig, leoleovich, salimma) golang-github-facebook-time-0^20240118git2f194ba-1.fc40.src requires golang(github.com/eclesh/welford) golang-github-facebook-time-devel-0^20240118git2f194ba-1.fc40.noarch requires
Re: Heads-up: abseil-cpp 20240116.0 coming to F40/Rawhide
Sorry for the late action. I've merged PR for mozc. Thanks, On Mon, Jan 29, 2024 at 3:43 AM Ben Beasley wrote: > > In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp > from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side > tags for F40/Rawhide. If I miss getting the update into Rawhide before > F40 branching, I plan to do the update in both F41/Rawhide and F40/Branched. > > Like all new calendar versions of abseil-cpp, this breaks ABI > compatibility and bumps the SONAME version. There are also some small > intentional breaking API changes[2]. > > Testing in COPR[3] indicates all directly-dependent packages are > compatible, except mozc, which can be fixed by a PR[4]. > > Besides abseil-cpp, I plan to rebuild all dependent packages using > maintainer/co-maintainer or provenpackager privileges. I also plan to > merge the mozc PR if it is still open. These packages are: > > - bear > - bloaty > - credentials-fetcher > - CuraEngine_grpc_definitions > - fastnetmon > - fcitx5-mozc > - frr > - grpc > - ilbc > - libarrow > - libphonenumber > - mozc > - onnxruntime > - parlaylib > - plasma-dialer > - qmlkonsole > - qt6-qtgrpc > - spacebar > - syslog-ng > > Of these, I expect plasma-dialer and syslog-ng to FTBFS in the side tag > since they already FTBFS in Rawhide. > > Maintainers of all affected packages should have received this email > directly (by BCC rather than CC, to keep the message from being held for > moderation due to a long CC list). > > If you want to handle the rebuild of the package yourself, or you have > other questions or concerns, please just let me know before 2024-02-04. > > – Ben Beasley (FAS: music) > > > [1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/16 > > [2] https://github.com/abseil/abseil-cpp/releases/tag/20240116.0 > > [3] https://copr.fedorainfracloud.org/coprs/music/abseil-cpp/packages/ > > [4] https://src.fedoraproject.org/rpms/mozc/pull-request/6 > > -- Akira TAGOH -- ___ 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 2260383] perl-libwww-perl-6.76 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2260383 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-2024-7b72801203 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-7b72801203 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2260383 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260383%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
Re: SWIG 4.2 Python transition
On Fri, 26 Jan 2024 at 12:29, Florian Weimer wrote: > In the past, this kind of problem would have just compiled and resulted > in a run-time error when the Python extension module is loaded. In some > cases, issues went completely unnoticed because the Python bindins were > unused. But with GCC 14, it is necessary to fix calls to undeclared > functions. Thanks, this is a great example of why diagnostics like that should be errors by default. -- ___ 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
