Summary/Minutes from yesterdays's FESCo Meeting (2023-02-07)
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2023-02-07/fesco.2023-02-07-17.04.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2023-02-07/fesco.2023-02-07-17.04.txt Log: https://meetbot.fedoraproject.org/fedora-meeting/2023-02-07/fesco.2023-02-07-17.04.log.html Meeting summary --- * init process (zbyszek, 17:04:18) * #2934 Restore Provides: singularity to apptainer packaging (zbyszek, 17:06:06) * LINK: https://pagure.io/fesco/issue/2934#comment-839521 claims that both have diverged or plan to diverge (music[m], 17:14:07) * LINK: https://pagure.io/fesco/issue/2934#comment-836095 (mhroncok, 17:24:33) * AGREED: both packages add Provides: alternative-for(singularity) (+6,0,-0) (mhroncok, 17:51:55) [tl;dr: when foo is not available and two or more packages have Provides:alternative-for(foo), 'dnf install foo' asks the user: $ mock -r centos-stream+epel-8-x86_64 install python ... No match for argument: python There are following alternatives for "python": python2, python36, python38, python39 Error: Unable to find a match: python ] * #2950 FTBFS exception request for golang-helm-3 (mhroncok, 17:53:46) * LINK: https://pagure.io/fesco/issue/2950 (zbyszek[m], 17:54:07) * kevin and churchyard both voted +1 in the meeting (mhroncok, 18:02:06) [The ticket will be approved today at 14:05:50 UTC after a week.] * Next week's chair (mhroncok, 18:02:16) * ACTION: Stephen Gallagher will chair the meeting next week * ACTION: Fabio Valentini will chair the meeting the week after next * Open Floor Meeting ended at 18:16:01 UTC. Action Items * Stephen Gallagher will chair the meeting next week * Fabio Valentini will chair the meeting the week after next ___ 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 next week
On Mon, Feb 6, 2023 at 6:50 PM Vít Ondruch wrote:
> Dne 06. 02. 23 v 1:13 Georg Sauthoff napsal(a):
> > Judging from the FTBFS mail/Bugzilla/
> https://src.fedoraproject.org/rpms/datamash it
> > looks like jhladky (Jiri Hladky) currently is the sole maintainer?
>
> You are looking at the right place. Or you can use the API:
>
[snip]
You can also install and use the pagure-cli tool: it defaults to this
server and outputs the json with yaml like this:
$ pagure project datamash
fullname: rpms/datamash
parent: null
close_status: []
namespace: rpms
url_path: rpms/datamash
access_users:
owner:
- jhladky
ticket: []
admin: []
collaborator: []
commit: []
priorities: {}
access_groups:
ticket: []
admin: []
collaborator: []
commit: []
name: datamash
full_url: https://src.fedoraproject.org/rpms/datamash
id: 24246
date_modified: '1569590838'
milestones: {}
user:
fullname: Jirka Hladky
url_path: user/jhladky
name: jhladky
full_url: https://src.fedoraproject.org/user/jhladky
custom_keys: []
date_created: '1503079151'
description: The datamash package
tags: []
___
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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
Lokesh Mandvekar wrote: > We (podman upstream and fedora maintainers) are hoping to disable i686 > and 32-bit arm builds for Podman and some related tools under > https://github.com/containers org. We would like to do this also for > released Fedora versions, and not just the upcoming ones. In general, dropping architectures from packages in released Fedora versions is a no go. That said, i686 is special because it is a multilib-only architecture, so executables such as podman should not have been shipped for i686 to begin with. Does dropping the 32-bit i686 build also imply you cannot use 32-bit containers on a 64-bit architecture? If so, will anybody notice? Since you did not use any special naming tricks (both package naming and file naming) to allow installing both versions (as in, e.g., wine), one has to go out of one's way to install the 32-bit version instead of the 64-bit one, and they cannot both be installed at once. 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
[Bug 2168015] New: perl-Sereal-Decoder-5.003 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2168015 Bug ID: 2168015 Summary: perl-Sereal-Decoder-5.003 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Sereal-Decoder Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: de...@fateyev.com, jples...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 5.003 Upstream release that is considered latest: 5.003 Current version/release in rawhide: 5.002-1.fc38 URL: http://search.cpan.org/dist/Sereal-Decoder/ 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/8066/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Sereal-Decoder -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2168015 ___ 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 2168016] New: perl-Sereal-Encoder-5.003 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2168016 Bug ID: 2168016 Summary: perl-Sereal-Encoder-5.003 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Sereal-Encoder Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: de...@fateyev.com, jples...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 5.003 Upstream release that is considered latest: 5.003 Current version/release in rawhide: 5.002-1.fc38 URL: http://search.cpan.org/dist/Sereal-Encoder/ 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/8065/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Sereal-Encoder -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2168016 ___ 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 2168014] New: perl-Sereal-5.003 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2168014 Bug ID: 2168014 Summary: perl-Sereal-5.003 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Sereal Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: de...@fateyev.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 5.003 Upstream release that is considered latest: 5.003 Current version/release in rawhide: 5.002-1.fc38 URL: http://search.cpan.org/dist/Sereal/ 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/7605/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Sereal -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2168014 ___ 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: Package naming suggestion?
On 2/7/23 8:28 PM, Chris Adams wrote: I've got a few useful Nagios monitoring plugins I'd like to add to Fedora/EPEL. I'm rather unimaginative at naming, so the Github repo for them is "nagios-plugins-cmadams"... while I wouldn't mind having a package with my username in it in Fedora, it seems a little vain. :) Before I go making a package and submitting a new package ticket, any suggestions about that? https://github.com/cmadamsgit/nagios-plugins-cmadams My two cents. I am a big fan of packages that are very explicit on what they are in the name. Doing a `dnf search nagios` turns up that most plugins start with nagios-plugin- so your current repo name follows that established convention. I'd say leave it as is and get that package submitted. :) Joe -- Joe Doss j...@solidadmin.com ___ 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
Package naming suggestion?
I've got a few useful Nagios monitoring plugins I'd like to add to Fedora/EPEL. I'm rather unimaginative at naming, so the Github repo for them is "nagios-plugins-cmadams"... while I wouldn't mind having a package with my username in it in Fedora, it seems a little vain. :) Before I go making a package and submitting a new package ticket, any suggestions about that? https://github.com/cmadamsgit/nagios-plugins-cmadams -- Chris Adams ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following builds have been pushed to Fedora EPEL 7 updates-testing davix-0.8.4-1.el7 Details about builds: davix-0.8.4-1.el7 (FEDORA-EPEL-2023-f82d0d14cd) Toolkit for http based file management Update Information: Davix 0.8.4 ChangeLog: * Tue Feb 7 2023 Mattias Ellert - 0.8.4-1 - New upstream release 0.8.4 - Drop patches accepted upstream * Tue Jan 24 2023 Mattias Ellert - 0.8.3-4 - Rebuild for gtest 1.13.0 - Don't downgrade the C++ version * Thu Jan 19 2023 Fedora Release Engineering - 0.8.3-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Wed Dec 21 2022 Mattias Ellert - 0.8.3-2 - Rebuild against gsoap-2.8.124 (bug #2155567) ___ 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
Heads-up: pre-commit 3.0.4 coming to F38 and Rawhide
In one week, 2023-02-14, or slightly later, I plan to update pre-commit[1] from 2.21.0 to 3.0.4 in F38/Branched and F39/Rawhide. Dependent packages are python-ipykernel, python-jupyter-kernel-test, python-nbconvert, python-opytimark, and python-pyscaffold. COPR testing[2] did not reveal any incompatibilities. - Ben Beasley (FAS music) [1] https://src.fedoraproject.org/rpms/pre-commit/pull-request/12 [2] https://copr.fedorainfracloud.org/coprs/music/pre-commit/packages/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-52e0512741 java-latest-openjdk-19.0.2.0.7-1.rolling.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing davix-0.8.4-1.el8 retsnoop-0.9.4-2.el8 syncthing-1.23.1-1.el8 syslog-ng-3.23.1-3.el8 Details about builds: davix-0.8.4-1.el8 (FEDORA-EPEL-2023-a85967f326) Toolkit for http based file management Update Information: Davix 0.8.4 ChangeLog: * Tue Feb 7 2023 Mattias Ellert - 0.8.4-1 - New upstream release 0.8.4 - Drop patches accepted upstream * Tue Jan 24 2023 Mattias Ellert - 0.8.3-4 - Rebuild for gtest 1.13.0 - Don't downgrade the C++ version * Thu Jan 19 2023 Fedora Release Engineering - 0.8.3-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Wed Dec 21 2022 Mattias Ellert - 0.8.3-2 - Rebuild against gsoap-2.8.124 (bug #2155567) retsnoop-0.9.4-2.el8 (FEDORA-EPEL-2023-f8b2e6e08b) A tool for investigating kernel error call stacks Update Information: `retsnoop` 0.9.4: - fix IP (instruction pointer) fetching on non-x86_64 architectures on older kernels; - handle io_uring source code files better, after Linux code reorganization; - automatically pick debugfs (/sys/kernel/debug/tracing) or tracefs (/sys/kernel/tracing), whichever is available; - handle very old kernels that don't support BPF global data more gracefully. ChangeLog: * Tue Feb 7 2023 Michel Alexandre Salim - 0.9.4-2 - Update vendored dependencies - also generate bundled provides (courtesy of zincati's bundled- provides.jq) * Tue Feb 7 2023 Michel Alexandre Salim - 0.9.4-1 - Update to 0.9.4 * Tue Feb 7 2023 Michel Alexandre Salim - 0.9.3-2 - Explicitly require llvm References: [ 1 ] Bug #2167831 - retsnoop-0.9.4 is available https://bugzilla.redhat.com/show_bug.cgi?id=2167831 syncthing-1.23.1-1.el8 (FEDORA-EPEL-2023-eb9b142b95) Continuous File Synchronization Update Information: Update to version 1.23.1. Release notes: https://github.com/syncthing/syncthing/releases/tag/v1.23.1 ChangeLog: * Tue Feb 7 2023 Fabio Valentini - 1.23.1-1 - Update to version 1.23.1 syslog-ng-3.23.1-3.el8 (FEDORA-EPEL-2023-31e354d8e4) Next-generation syslog server Update Information: Security fix for CVE-2022-38725 ChangeLog: * Mon Feb 6 2023 Peter Czanik - 3.23.1-3 - add 4110.diff to fix CVE-2022-38725 References: [ 1 ] Bug #2164618 - CVE-2022-38725 syslog-ng: integer overflow in the RFC3164 parser can lead to DoS https://bugzilla.redhat.com/show_bug.cgi?id=2164618 ___ 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 9 updates-testing report
The following Fedora EPEL 9 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-fc74dc491a java-latest-openjdk-19.0.2.0.7-1.rolling.el9 The following builds have been pushed to Fedora EPEL 9 updates-testing davix-0.8.4-1.el9 retsnoop-0.9.4-1.el9 rust-darling-0.14.3-1.el9 rust-darling_core-0.14.3-1.el9 rust-darling_macro-0.14.3-1.el9 rust-io-lifetimes-1.0.5-1.el9 rust-parking_lot_core-0.9.7-1.el9 rust-petgraph-0.6.3-1.el9 rust-quick-xml-0.27.1-1.el9 rust-quick-xml0.25-0.25.0-1.el9 rust-rgb-0.8.35-1.el9 syncthing-1.23.1-1.el9 syslog-ng-3.35.1-6.el9 vkd3d-1.6-2.el9 Details about builds: davix-0.8.4-1.el9 (FEDORA-EPEL-2023-64b445f54d) Toolkit for http based file management Update Information: Davix 0.8.4 ChangeLog: * Tue Feb 7 2023 Mattias Ellert - 0.8.4-1 - New upstream release 0.8.4 - Drop patches accepted upstream * Tue Jan 24 2023 Mattias Ellert - 0.8.3-4 - Rebuild for gtest 1.13.0 - Don't downgrade the C++ version * Thu Jan 19 2023 Fedora Release Engineering - 0.8.3-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Wed Dec 21 2022 Mattias Ellert - 0.8.3-2 - Rebuild against gsoap-2.8.124 (bug #2155567) retsnoop-0.9.4-1.el9 (FEDORA-EPEL-2023-6d5a912173) A tool for investigating kernel error call stacks Update Information: `retsnoop` 0.9.4: - fix IP (instruction pointer) fetching on non-x86_64 architectures on older kernels; - handle io_uring source code files better, after Linux code reorganization; - automatically pick debugfs (/sys/kernel/debug/tracing) or tracefs (/sys/kernel/tracing), whichever is available; - handle very old kernels that don't support BPF global data more gracefully. ChangeLog: * Tue Feb 7 2023 Michel Alexandre Salim - 0.9.4-1 - Update to 0.9.4 * Sun Feb 5 2023 Fabio Valentini - 0.9.3-5 - Rebuild for fixed frame pointer compiler flags in Rust RPM macros * Fri Jan 20 2023 Fedora Release Engineering - 0.9.3-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild References: [ 1 ] Bug #2167831 - retsnoop-0.9.4 is available https://bugzilla.redhat.com/show_bug.cgi?id=2167831 rust-darling-0.14.3-1.el9 (FEDORA-EPEL-2023-e674f41b59) Proc-macro library for reading attributes into structs Update Information: Update the darling, darling_macro, and darling_core crates to version 0.14.3. ChangeLog: * Tue Feb 7 2023 Fabio Valentini - 0.14.3-1 - Update to version 0.14.3; Fixes RHBZ#2167533 rust-darling_core-0.14.3-1.el9 (FEDORA-EPEL-2023-e674f41b59) Helper crate for proc-macro library for reading attributes into structs Update Information: Update the darling, darling_macro, and darling_core crates to version 0.14.3. ChangeLog: * Tue Feb 7 2023 Fabio Valentini - 0.14.3-1 - Update to version 0.14.3; Fixes RHBZ#2167520 rust-darling_macro-0.14.3-1.el9 (FEDORA-EPEL-2023-e674f41b59) Internal support for a proc-macro library for reading attributes into structs Update Information: Update the darling, darling_macro, and darling_core crates to version 0.14.3. ChangeLog: * Tue Feb 7 2023 Fabio Valentini - 0.14.3-1 - Update to version 0.14.3; Fixes RHBZ#2167521
Re: Tenacity
On Tue, Feb 7, 2023 at 7:26 PM Philip Rhoades via devel wrote: > > People, > > Has there been any discussion about getting a Tenacity RPM going for > Fedora? - I would prefer that to having to use the AppImage version . . > As I recall, in the beginning, Tenacity (to perform most meaningful operations) required FFmpeg, which was not in Fedora, so that was a clear show stopper. Now that FFmpeg is (or at least with the codecs without IP encumbrances) Tenacity might be able to be packaged as long as it does not include any other libraries that are IP encumbered. Someone will need to perform that IP review, as codecs are a minefield. ___ 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: Tenacity
On 2/7/23 1:25 PM, Philip Rhoades via devel wrote: People, Has there been any discussion about getting a Tenacity RPM going for Fedora? - I would prefer that to having to use the AppImage version . . Thanks, Phil. I have a copr[0]. It has some issues and the current version is old. I have been working on updating to the latest beta from the new upstream location[1], but $DAY_JOB has been consuming a lot of my time. [0] - https://copr.fedorainfracloud.org/coprs/nielsenb/tenacity/ [1] - https://codeberg.org/tenacityteam/tenacity ___ 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: Tenacity
On Tue, 2023-02-07 at 21:03 +, Reon Beon via devel wrote: > https://src.fedoraproject.org/rpms/python-tenacity ? > ___ > 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 Hi, I believe the original reporter here is speaking of the more privacy centric audacity? Regards Phil -- *** Playing the game for the games own sake. *** Associations: * Debian Maintainer (DM) * Fedora/EPEL Maintainer. * Contributor member of the AlmaLinux foundation. WWW: https://kathenas.org Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg Twitter: @kathenasorg Instagram: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part ___ 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: Tenacity
https://src.fedoraproject.org/rpms/python-tenacity ? ___ 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
Tenacity
People, Has there been any discussion about getting a Tenacity RPM going for Fedora? - I would prefer that to having to use the AppImage version . . Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: p...@pricom.com.au ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: EPEL2RHEL - New Wording? - New Workflow?
On 01. 11. 22 15:07, Troy Dawson wrote: Does this sound good to people? Yes please. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
2023-02-07T11:43:53Z Lokesh Mandvekar :
> We (podman upstream and fedora maintainers) are hoping to disable i686
> and 32-bit arm builds for Podman and some related tools under
> https://github.com/containers org. We would like to do this also for
> released Fedora versions, and not just the upcoming ones.
>
> What Fedora paperwork do we need in place to get this going?
arm32 has been removed entirely from F37+. I don't think excluding
packages from arm32 at this point in the F36 release cycle is
acceptable. Wait until the release goes EOL.
As for i686, you don't need extra paperwork thanks to exclude packages
thanks to
https://fedoraproject.org/wiki/Changes/EncourageI686LeafRemoval.
You just need to properly handle dependent packages. You cannot
ExcludeArch a package unless all of its dependents are also excluded.
It's recommended to exclude Go packages with
`ExclusiveArch: %{golang_arches_future}`.
For other packages, a regular `ExcludeArch: %{ix86}` is sufficient.
Here's some of the dependents you need to account for:
---
$ cat
Re: F37 Change Proposal: MAC Address Policy none (System-Wide Change)
Hi, After this change missed F37, it's now testable in F38: https://src.fedoraproject.org/rpms/systemd/pull-request/100 systemd-253~rc2-3.fc38 Thanks Dusty, zbyszek! Thomas ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2023-02-08 from 16:00:00 to 17:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #topic aloha #topic EPEL Issues https://pagure.io/epel/issues * https://pagure.io/epel/issues?tags=meeting=Open #topic Old Business (if needed) #topic General Issues / Open Floor Source: https://calendar.fedoraproject.org//meeting/9854/ ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2167096] Please branch and build perl-RPM2 in epel9
https://bugzilla.redhat.com/show_bug.cgi?id=2167096 --- Comment #3 from rmhe...@yahoo.com --- Thank you! I was able to install this from epel-testing and everything seems to be working great. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2167096 ___ 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
Take 1 minute to help with Infra & Releng Team with a decision
Hi everyone, it came to Infra & Releng Team (sub-team in CPE that is taking care of Fedora Infra, Fedora Release Engineering and CentOS Infra) attention that there is a confusion about the labels we are using for issues in our trackers. Namely fedora-infrastructure, releng and centos-infra. There was even a request to change them to something less confusing. So we want to decide if this is really need to change, so we ask you to take this quick survey [0] (this is an anonymous survey, nothing is collected by us) to see if the change is really needed or people are happy with current labels. The survey will be closed on 7th March 2023. On behalf of I Team, Michal [0] - https://forms.gle/J2HWDkw1UNuj8HYD8 ___ 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: Fedora 38 mass rebuild is finished
On 23. 01. 23 17:44, Tomas Hrcka wrote: FTBFS bugs will be filed shortly. Is there an estimated date when this will happen? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
On Tue, Feb 7, 2023 at 6:12 PM Stephen Smoogen wrote: > > > > On Tue, 7 Feb 2023 at 07:38, Dan Čermák > wrote: >> >> Hi Lokesh, >> >> Lokesh Mandvekar writes: >> >> > Hi, >> > >> > We (podman upstream and fedora maintainers) are hoping to disable i686 >> > and 32-bit arm builds for Podman and some related tools under >> > https://github.com/containers org. We would like to do this also for >> > released Fedora versions, and not just the upcoming ones. >> > >> > What Fedora paperwork do we need in place to get this going? >> >> I would suggest to file a self-contained change proposal to get some >> visibility for this change in the official release notes. But afaik all >> you have to do is to define `ExclusiveArch:` or `ExcludeArch:` in your >> spec file. >> > > Depending on where it might have been 'defined', it may need some fiddling in > releng scripts or releng pungi. As part of the self-contained change proposal > make sure you file the requisite releng ticket to make sure they are aware > that the change will be happening, why it is happening (various software in > the chain of dependencies compiles/works on 32 bit), and what parts will be > affected. > Thanks all. I'll file a self-contained change for i686 and leave armhfp as-is for now, and update this thread once I have it ready. -- Lokesh Libera, GitLab, GitHub, Fedora: lsm5 Matrix: @lsm5:lsm5.ems.host GPG: 0xC7C3A0DD https://keybase.io/lsm5 ___ 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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
On Tue, Feb 7, 2023 at 12:36 PM Lokesh Mandvekar wrote: > > On Tue, Feb 7, 2023 at 5:56 PM Peter Robinson wrote: > > > There are still active users of Fedora IoT 36 on armhfp using > > containers so I suspect they may be unhappy of they go away before the > > F-36 EOL in the late May/early June timeframe. > > I see. I guess we could leave armhfp be until then. Btw, just curious > what happens to IoT on armhfp once f36 goes EOL. > Would users have to pick something else? Basically yes. ___ 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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
On Tue, 7 Feb 2023 at 07:38, Dan Čermák wrote: > Hi Lokesh, > > Lokesh Mandvekar writes: > > > Hi, > > > > We (podman upstream and fedora maintainers) are hoping to disable i686 > > and 32-bit arm builds for Podman and some related tools under > > https://github.com/containers org. We would like to do this also for > > released Fedora versions, and not just the upcoming ones. > > > > What Fedora paperwork do we need in place to get this going? > > I would suggest to file a self-contained change proposal to get some > visibility for this change in the official release notes. But afaik all > you have to do is to define `ExclusiveArch:` or `ExcludeArch:` in your > spec file. > > Depending on where it might have been 'defined', it may need some fiddling in releng scripts or releng pungi. As part of the self-contained change proposal make sure you file the requisite releng ticket to make sure they are aware that the change will be happening, why it is happening (various software in the chain of dependencies compiles/works on 32 bit), and what parts will be affected. > > Hope this helps, > > Dan > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
Hi Lokesh, Lokesh Mandvekar writes: > Hi, > > We (podman upstream and fedora maintainers) are hoping to disable i686 > and 32-bit arm builds for Podman and some related tools under > https://github.com/containers org. We would like to do this also for > released Fedora versions, and not just the upcoming ones. > > What Fedora paperwork do we need in place to get this going? I would suggest to file a self-contained change proposal to get some visibility for this change in the official release notes. But afaik all you have to do is to define `ExclusiveArch:` or `ExcludeArch:` in your spec file. Hope this helps, Dan ___ 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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
On Tue, Feb 7, 2023 at 5:56 PM Peter Robinson wrote: > There are still active users of Fedora IoT 36 on armhfp using > containers so I suspect they may be unhappy of they go away before the > F-36 EOL in the late May/early June timeframe. I see. I guess we could leave armhfp be until then. Btw, just curious what happens to IoT on armhfp once f36 goes EOL. Would users have to pick something else? Thanks, > > Peter > -- Lokesh Libera, GitLab, GitHub, Fedora: lsm5 Matrix: @lsm5:lsm5.ems.host GPG: 0xC7C3A0DD https://keybase.io/lsm5 ___ 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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
On Tue, Feb 7, 2023 at 11:43 AM Lokesh Mandvekar wrote: > > Hi, > > We (podman upstream and fedora maintainers) are hoping to disable i686 > and 32-bit arm builds for Podman and some related tools under > https://github.com/containers org. We would like to do this also for > released Fedora versions, and not just the upcoming ones. There are still active users of Fedora IoT 36 on armhfp using containers so I suspect they may be unhappy of they go away before the F-36 EOL in the late May/early June timeframe. Peter > What Fedora paperwork do we need in place to get this going? > > Thanks > -- > Lokesh > Libera, GitLab, GitHub, Fedora: lsm5 > Matrix: @lsm5:lsm5.ems.host > GPG: 0xC7C3A0DD > https://keybase.io/lsm5 > ___ > 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: Cython build failing on longintrepr.h not found
On 07-02-2023 01:10, Miro Hrončok wrote: 4) contextlib.redirect_stdout does not support stdout of subprocesses https://docs.python.org/3/library/contextlib.html#contextlib.redirect_stdout We might need a more robust way of redirecting all of stdout... And this now finally has a fix ready: https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/353 Thanks Miro. Upstream actually fixed that and you contributed to it. [1] Unfortunately, there has not been a release since. That's why the patch was still needed. [1] https://github.com/has2k1/scikit-misc/pull/18 Cheers, Sandro ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases
Hi, We (podman upstream and fedora maintainers) are hoping to disable i686 and 32-bit arm builds for Podman and some related tools under https://github.com/containers org. We would like to do this also for released Fedora versions, and not just the upcoming ones. What Fedora paperwork do we need in place to get this going? Thanks -- Lokesh Libera, GitLab, GitHub, Fedora: lsm5 Matrix: @lsm5:lsm5.ems.host GPG: 0xC7C3A0DD https://keybase.io/lsm5 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230207.n.0 changes
OLD: Fedora-Rawhide-20230206.n.0 NEW: Fedora-Rawhide-20230207.n.0 = SUMMARY = Added images:3 Dropped images: 0 Added packages: 1 Dropped packages:1 Upgraded packages: 168 Downgraded packages: 0 Size of added packages: 404.92 KiB Size of dropped packages:156.29 KiB Size of upgraded packages: 3.47 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 16.44 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230207.n.0.iso Image: Container_Base docker aarch64 Path: Container/aarch64/images/Fedora-Container-Base-Rawhide-20230207.n.0.aarch64.tar.xz Image: Server_KVM qcow2 ppc64le Path: Server/ppc64le/images/Fedora-Server-KVM-Rawhide-20230207.n.0.ppc64le.qcow2 = DROPPED IMAGES = = ADDED PACKAGES = Package: rubygem-redis-client-0.12.1-1.fc38 Summary: Simple low-level client for Redis 6+ RPMs:rubygem-redis-client rubygem-redis-client-doc Size:404.92 KiB = DROPPED PACKAGES = Package: perl-SystemC-Vregs-1.470-31.fc38 Summary: Utility routines used by vregs RPMs:emacs-vregs-mode perl-SystemC-Vregs Size:156.29 KiB = UPGRADED PACKAGES = Package: PDAL-2.5.0-3.fc38 Old package: PDAL-2.5.0-2.fc38 Summary: Point Data Abstraction Library RPMs: PDAL PDAL-devel PDAL-doc PDAL-libs Size: 50.40 MiB Size change: -1.06 KiB Changelog: * Mon Feb 06 2023 Markus Neteler 2.5.0-3 - patch to guard against bad return numbers (from upstream #3966), to be removed with PDAL 2.5.1 Package: Rex-1.14.0-0.fc38 Old package: Rex-1.13.4-6.fc38 Summary: The friendly automation framework on basis of Perl RPMs: Rex Size: 516.60 KiB Size change: 18 B Changelog: * Mon Feb 06 2023 Dominic Hopf - 1.14.0-1 - Update to 1.14.0 (#2167207) Package: ags-3.6.0.42-1.fc38 Old package: ags-3.6.0.41-1.fc38 Summary: Engine for creating and running videogames of adventure (quest) genre RPMs: ags Size: 5.65 MiB Size change: -971 B Changelog: * Mon Feb 06 2023 Dominik Mierzejewski - 3.6.0.42-1 - update to 3.6.0.42 (#2167149) - drop obsolete patch Package: ansible-bender-0.10.1-1.fc38 Old package: ansible-bender-0.9.0-9.fc38 Summary: Build container images using Ansible playbooks RPMs: ansible-bender Size: 4.88 MiB Size change: 7.31 KiB Changelog: * Mon Feb 06 2023 Tomas Tomecek - 0.10.1-1 - 0.10.1 upstream release Package: apbs-3.0.0-18.fc38 Old package: apbs-3.0.0-16.fc37 Summary: Adaptive Poisson Boltzmann Solver RPMs: apbs apbs-devel apbs-doc apbs-libs apbs-tools python3-apbs Size: 29.02 MiB Size change: 250.22 KiB Changelog: * Wed Jan 18 2023 Fedora Release Engineering - 3.0.0-17 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Mon Feb 06 2023 Florian Weimer - 3.0.0-18 - Fix C99 compatibility issue Package: awscli-1.27.65-1.fc38 Old package: awscli-1.27.64-1.fc38 Summary: Universal Command Line Environment for AWS RPMs: awscli Size: 3.28 MiB Size change: 140 B Changelog: * Mon Feb 06 2023 Gwyn Ciesla - 1.27.65-1 - 1.27.65 Package: bash-5.2.15-3.fc38 Old package: bash-5.2.15-2.fc38 Summary: The GNU Bourne Again shell RPMs: bash bash-devel bash-doc Size: 13.53 MiB Size change: -2.52 KiB Changelog: * Mon Feb 06 2023 Florian Weimer - 5.2.15-3 - Fix C99 compatibility issue on configure script Package: breeze-icon-theme-5.103.0-1.fc38 Old package: breeze-icon-theme-5.102.0-2.fc38 Summary: Breeze icon theme RPMs: breeze-icon-theme breeze-icon-theme-rcc Size: 11.44 MiB Size change: -718 B Changelog: * Sun Feb 05 2023 Marc Deop - 5.103.0-1 - 5.103.0 Package: calligra-3.2.1-22.fc38 Old package: calligra-3.2.1-20.fc38 Summary: An integrated office suite RPMs: calligra calligra-core calligra-karbon calligra-karbon-libs calligra-l10n calligra-libs calligra-sheets calligra-sheets-libs calligra-stage calligra-stage-libs calligra-words calligra-words-libs Dropped RPMs: calligra-okular-odpgenerator calligra-okular-odtgenerator Size: 143.90 MiB Size change: 1.07 MiB Changelog: * Wed Jan 18 2023 Fedora Release Engineering - 3.2.1-21 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Mon Feb 06 2023 Marek Kasik - 3.2.1-22 - Rebuild for poppler-23.02.0 - Disable Okular support for now as it prevents to build Calligra currently Package: cgdb-0.8.0-4.fc38 Old package: cgdb-0.6.8-18.fc36 Summary: CGDB is a curses-based interface to the GNU Debugger (GDB) RPMs: cgdb Size: 872.38 KiB Size change: 293.55 KiB Changelog: * Wed Jan 19 2022 Eric Curtin - 0.8.0-1 - Update to 0.8.0 * Wed Jan 19 2022 Fedora Release Engineering - 0.8.0-2 - Rebuilt
Schedule for Tuesday's FESCo Meeting (2023-02-07)
Following is the list of topics that will be discussed in the FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on irc.libera.chat. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2023-02-07 17:00 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 = #2949 Change: Update python-packaging to version >= 22 https://pagure.io/fesco/issue/2949 APPROVED via fast track (+7,0,-0) #2946 Change: IoT Simplified Installer https://pagure.io/fesco/issue/2946 APPROVED (+3,0,-0) #2945 Change: Remove pam_console https://pagure.io/fesco/issue/2945 APPROVED (+3,0,-0) #2944 Change: cups-filters 2.0b https://pagure.io/fesco/issue/2944 APPROVED (+3,0,-0) = Followups = #2934 Restore Provides: singularity to apptainer packaging https://pagure.io/fesco/issue/2934 = New business = #2950 FTBFS exception request for golang-helm-3 https://pagure.io/fesco/issue/2950 = 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
Re: How/Where to put git_archieve.tar.gz for packaging?
On Tue, Feb 07, 2023 at 04:13:24PM +0800, Ming Lei wrote: > Hello Richard, > > Can we update rawhide(ubdsrv) with upstream commit > 58401cf5614ec3ab2a69166e7f9b596f862de105? > > https://github.com/ming1/ubdsrv/commit/58401cf5614ec3ab2a69166e7f9b596f862de105 https://koji.fedoraproject.org/koji/taskinfo?taskID=97223455 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ___ 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: How/Where to put git_archieve.tar.gz for packaging?
Hello Richard, Can we update rawhide(ubdsrv) with upstream commit 58401cf5614ec3ab2a69166e7f9b596f862de105? https://github.com/ming1/ubdsrv/commit/58401cf5614ec3ab2a69166e7f9b596f862de105 Thanks, Ming ___ 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
