June 2023 - Epel-packagers-sig - Fedora mailing-lists

[Bug 2210415] New: gajim-1.8.0 is available
by bugzilla＠redhat.com 27 Aug '26

27 Aug '26

https://bugzilla.redhat.com/show_bug.cgi?id=2210415 Bug ID: 2210415 Summary: gajim-1.8.0 is available Product: Fedora Version: rawhide Status: NEW Component: gajim Keywords: FutureFeature, Triaged Assignee: mschmidt(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, lemenkov(a)gmail.com, mschmidt(a)redhat.com, redhat-bugzilla(a)linuxnetz.de, suraia(a)ikkoku.de Target Milestone: --- Classification: Fedora Releases retrieved: 1.8.0 Upstream release that is considered latest: 1.8.0 Current version/release in rawhide: 1.7.3-2.fc39 URL: https://gajim.org/ 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_M… 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/870/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gajim -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2210415

1 116

[Bug 2210464] New: python-nbxmpp-4.3.0 is available
by bugzilla＠redhat.com 26 Aug '26

26 Aug '26

https://bugzilla.redhat.com/show_bug.cgi?id=2210464 Bug ID: 2210464 Summary: python-nbxmpp-4.3.0 is available Product: Fedora Version: rawhide Status: NEW Component: python-nbxmpp Keywords: FutureFeature, Triaged Assignee: mschmidt(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, mschmidt(a)redhat.com, suraia(a)ikkoku.de Target Milestone: --- Classification: Fedora Releases retrieved: 4.3.0 Upstream release that is considered latest: 4.3.0 Current version/release in rawhide: 4.2.2-1.fc39 URL: https://dev.gajim.org/gajim/python-nbxmpp/ 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_M… 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/12980/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-nbxmpp -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2210464

1 86

[Bug 2130200] New: CVE-2022-39835 python-nbxmpp: gajim: security issue [epel-all]
by bugzilla＠redhat.com 24 Aug '26

24 Aug '26

https://bugzilla.redhat.com/show_bug.cgi?id=2130200 Bug ID: 2130200 Summary: CVE-2022-39835 python-nbxmpp: gajim: security issue [epel-all] Product: Fedora EPEL Version: epel8 Status: NEW Component: python-nbxmpp Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: epel-packagers-sig(a)lists.fedoraproject.org Reporter: trathi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, mschmidt(a)redhat.com, suraia(a)ikkoku.de Target Milestone: --- Classification: Fedora This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of epel-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora EPEL. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2130200

1 3

[Bug 2130197] New: CVE-2022-39835 gajim: security issue [epel-all]
by bugzilla＠redhat.com 24 Aug '26

24 Aug '26

https://bugzilla.redhat.com/show_bug.cgi?id=2130197 Bug ID: 2130197 Summary: CVE-2022-39835 gajim: security issue [epel-all] Product: Fedora EPEL Version: epel8 Status: NEW Component: gajim Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: redhat-bugzilla(a)linuxnetz.de Reporter: trathi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, lemenkov(a)gmail.com, mschmidt(a)redhat.com, redhat-bugzilla(a)linuxnetz.de, suraia(a)ikkoku.de Target Milestone: --- Classification: Fedora This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of epel-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora EPEL. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2130197

1 3

[Bug 2128273] New: Please port your pcre dependency to pcre2. Pcre has been deprecated
by bugzilla＠redhat.com 22 Jul '26

22 Jul '26

https://bugzilla.redhat.com/show_bug.cgi?id=2128273 Bug ID: 2128273 Summary: Please port your pcre dependency to pcre2. Pcre has been deprecated Product: Fedora Version: rawhide Status: NEW Component: ccze Assignee: dcavalca(a)fb.com Reporter: ljavorsk(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dcavalca(a)fb.com, epel-packagers-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name, pahan(a)hubbitus.info Target Milestone: --- Classification: Fedora Pcre has been deprecated since Fedora 38. Please consider porting to the new pcre2 version. Fedora change that describes the pcre deprecation is located here: https://fedoraproject.org/wiki/PcreDeprecation FESCo approval is located here: https://pagure.io/fesco/issue/2862 If your component has already ported to pcre2 or you don't Require/BuildRequire any pcre subpackage, feel free to close this Bugzilla. This Bugzilla was created automatically and some issues might have occurred along the way. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2128273

1 3

[Bug 2217559] New: lua-lpeg-1.1.0 is available
by bugzilla＠redhat.com 20 Jul '26

20 Jul '26

https://bugzilla.redhat.com/show_bug.cgi?id=2217559 Bug ID: 2217559 Summary: lua-lpeg-1.1.0 is available Product: Fedora Version: rawhide Status: NEW Component: lua-lpeg Keywords: FutureFeature, Triaged Assignee: asn(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: asn(a)redhat.com, epel-packagers-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name, tkrizek(a)isc.org Target Milestone: --- Classification: Fedora Releases retrieved: 1.1.0 Upstream release that is considered latest: 1.1.0 Current version/release in rawhide: 1.0.2-10.fc38 URL: http://www.inf.puc-rio.br/~roberto/lpeg/ 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_M… 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/1852/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/lua-lpeg -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2217559 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2209027] New: psutils-3.0 is available
by bugzilla＠redhat.com 20 Jul '26

20 Jul '26

https://bugzilla.redhat.com/show_bug.cgi?id=2209027 Bug ID: 2209027 Summary: psutils-3.0 is available Product: Fedora Version: rawhide Status: NEW Component: psutils Keywords: FutureFeature, Triaged Assignee: opohorel(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, opohorel(a)redhat.com, ppisar(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 3.0 Upstream release that is considered latest: 3.0 Current version/release in rawhide: 2.10-1.fc39 URL: https://github.com/rrthomas/psutils 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_M… 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/12921/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/psutils -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2209027

1 28

[Bug 2093731] New: zbarimg does not read a Code 128 barcode
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2093731 Bug ID: 2093731 Summary: zbarimg does not read a Code 128 barcode Product: Fedora Version: 36 Status: NEW Component: zbar Severity: high Assignee: gwync(a)protonmail.com Reporter: cristian.ciupitu(a)yahoo.com QA Contact: extras-qa(a)fedoraproject.org CC: dougsland(a)redhat.com, epel-packagers-sig(a)lists.fedoraproject.org, gwync(a)protonmail.com, mchehab(a)infradead.org, mr.marcelo.barbosa(a)gmail.com, negativo17(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1886898 --> https://bugzilla.redhat.com/attachment.cgi?id=1886898&action=edit Code 128 barcode Description of problem: zbarimg does not read a Code 128 barcode Version-Release number of selected component (if applicable): zbar-0.23.90-1.fc36.x86_64 How reproducible: Every time Steps to Reproduce: 1. zbarimg barcode.png Actual results: scanned 0 barcode symbols from 1 images in 0 seconds WARNING: barcode data was not detected in some image(s) Things to check: - is the barcode type supported? Currently supported symbologies are: . EAN/UPC (EAN-13, EAN-8, EAN-2, EAN-5, UPC-A, UPC-E, ISBN-10, ISBN-13) . DataBar, DataBar Expanded . Code 128 . Code 93 . Code 39 . Codabar . Interleaved 2 of 5 . QR code . SQ code . PDF 417 - is the barcode large enough in the image? - is the barcode mostly in focus? - is there sufficient contrast/illumination? - If the symbol is split in several barcodes, are they combined in one image? - Did you enable the barcode type? some EAN/UPC codes are disabled by default. To enable all, use: $ zbarimg -S*.enable <files> Please also notice that some variants take precedence over others. Due to that, if you want, for example, ISBN-10, you should do: $ zbarimg -Sisbn10.enable <files> Expected results: (Code 128) 755897201062022179.73 Additional info: -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2093731

1 12

[Bug 2173707] New: CVE-2021-438450 CVE-2021-438451 CVE-2022-217221 CVE-2022-247541 CVE-2022-247542 CVE-2022-247631 CVE-2022-247633 CVE-2022-247641 CVE-2022-247644 CVE-2022-247931 CVE-2022-247935 asterisk: pjsip: Multiple Vulnerabilities [epel-all]
by bugzilla＠redhat.com 30 Apr '26

30 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2173707 Bug ID: 2173707 Summary: CVE-2021-438450 CVE-2021-438451 CVE-2022-217221 CVE-2022-247541 CVE-2022-247542 CVE-2022-247631 CVE-2022-247633 CVE-2022-247641 CVE-2022-247644 CVE-2022-247931 CVE-2022-247935 asterisk: pjsip: Multiple Vulnerabilities [epel-all] Product: Fedora EPEL Version: epel8 Status: NEW Component: asterisk Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: epel-packagers-sig(a)lists.fedoraproject.org Reporter: psampaio(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: bennie.joubert(a)jsdaav.com, epel-packagers-sig(a)lists.fedoraproject.org, jsmith.fedora(a)gmail.com, rbryant(a)redhat.com Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2173705 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2173707

1 11

[Bug 2173702] New: CVE-2021-41141 CVE-2021-43845 CVE-2022-24754 CVE-2022-24763 CVE-2022-24786 CVE-2022-24792 CVE-2022-24793 asterisk: pjsip: Multiple vulnerabilities [epel-all]
by bugzilla＠redhat.com 30 Apr '26

30 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2173702 Bug ID: 2173702 Summary: CVE-2021-41141 CVE-2021-43845 CVE-2022-24754 CVE-2022-24763 CVE-2022-24786 CVE-2022-24792 CVE-2022-24793 asterisk: pjsip: Multiple vulnerabilities [epel-all] Product: Fedora EPEL Version: epel8 Status: NEW Component: asterisk Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: epel-packagers-sig(a)lists.fedoraproject.org Reporter: psampaio(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: bennie.joubert(a)jsdaav.com, epel-packagers-sig(a)lists.fedoraproject.org, jsmith.fedora(a)gmail.com, rbryant(a)redhat.com Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2173699 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2173702

1 11

2026

2025

2024

2023

2022

2021

Epel-packagers-sig June 2023