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
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
https://bugzilla.redhat.com/show_bug.cgi?id=2148193
Bug ID: 2148193
Summary: cross-gcc on EPEL9 expects libstdc++ 12, but CentOS
Stream 9 uses libstdc++11
Product: Fedora EPEL
Version: epel9
Status: NEW
Component: cross-gcc
Assignee: lkundrak(a)v3.sk
Reporter: harry.mallon(a)codex.online
QA Contact: extras-qa(a)fedoraproject.org
CC: dan(a)danny.cz, dhowells(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
lkundrak(a)v3.sk
Target Milestone: ---
Classification: Fedora
Description of problem:
cross-gcc aarch64 on x86_64 host. It expects to find the C++ headers in gcc
folders with a 12 in them. However the libstdc++-devel that is available for
aarch64 CentOS 9 uses version 11, so it cannot find C++ headers without extra
include paths.
Version-Release number of selected component (if applicable):
gcc-c++-aarch64-linux-gnu 12.1.1-1.el9
libstdc++-devel 11.3.1-2.1.el9
How reproducible:
Every time
Steps to Reproduce:
1. Install gcc-c++-aarch64-linux-gnu on x86_64 host
2. Try to compile a simple C++ file
3. You will get include errors as the default includes are wrong
Actual results:
```
# /usr/bin/aarch64-linux-gnu-c++ -v test.cpp
... snip
ignoring nonexistent directory
"/usr/lib/gcc/aarch64-linux-gnu/12/../../../../aarch64-linux-gnu/include/c++/12"
ignoring nonexistent directory
"/usr/lib/gcc/aarch64-linux-gnu/12/../../../../aarch64-linux-gnu/include/c++/12/aarch64-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc/aarch64-linux-gnu/12/../../../../aarch64-linux-gnu/include/c++/12/backward"
ignoring nonexistent directory
"/usr/lib/gcc/aarch64-linux-gnu/12/../../../../aarch64-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/aarch64-linux-gnu/12/include
/usr/aarch64-linux-gnu/sys-root/usr/local/include
/usr/lib/gcc/aarch64-linux-gnu/12/include-fixed
/usr/aarch64-linux-gnu/sys-root/usr/include
End of search list.
GNU C++17 (GCC) version 12.1.1 20220507 (Red Hat Cross 12.1.1-1)
(aarch64-linux-gnu)
compiled by GNU C version 11.2.1 20220127 (Red Hat 11.2.1-9), GMP
version 6.2.0, MPFR version 4.1.0-p9, MPC version 1.2.1, isl version none
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: ee1d63ceabfbcd15639b63b507165dcf
test.cpp:1:10: fatal error: string: No such file or directory
1 | #include <string>
| ^~~~~~~~
compilation terminated.
```
Expected results:
I expect libstc++-devel from CentOS 9 repo to be fully compatible with
cross-gcc from EPEL 9.
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=2148193
https://bugzilla.redhat.com/show_bug.cgi?id=2130196
Bug ID: 2130196
Summary: CVE-2022-39835 gajim: security issue
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: trathi(a)redhat.com
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: Other
A vulnerability was found in Gajim which allowed attackers to craft a XML
stanza in a way, so Gajim would accept it as message correction for messages
not originating from the attacker.
https://bugzilla.redhat.com/show_bug.cgi?id=2128097https://bugzilla.redhat.com/show_bug.cgi?id=2122047
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2130196
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
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
https://bugzilla.redhat.com/show_bug.cgi?id=2222350
Bug ID: 2222350
Summary: CVE-2022-38900 yarnpkg: decode-uri-component: improper
input validation resulting in DoS [epel-8]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: yarnpkg
Keywords: Security, SecurityTracking
Severity: high
Priority: high
Assignee: zsvetlik(a)redhat.com
Reporter: mrehak(a)redhat.com
CC: epel-packagers-sig(a)lists.fedoraproject.org,
manisandro(a)gmail.com, ngompa13(a)gmail.com,
zsvetlik(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=2170644
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 on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2222350
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
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