[Bug 2068421] New: python-executing fails to build with Python 3.11: InvocationError: self.get_executing(inspect.currentframe().f_back)
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2068421
Bug ID: 2068421
Summary: python-executing fails to build with Python 3.11:
InvocationError:
self.get_executing(inspect.currentframe().f_back)
Product: Fedora
Version: rawhide
Status: NEW
Component: python-executing
Assignee: rominf(a)aiven.io
Reporter: thrnciar(a)redhat.com
CC: epel-packagers-sig(a)lists.fedoraproject.org,
lbalhar(a)redhat.com, mhroncok(a)redhat.com,
paul.wouters(a)aiven.io, rominf(a)aiven.io,
thrnciar(a)redhat.com
Blocks: 2016048 (PYTHON3.11)
Target Milestone: ---
Link ID: Github alexmojaki/executing/pull/31
Classification: Fedora
python-executing fails to build with Python 3.11.0a6.
+ /usr/bin/python3 -m tox --current-env -q --recreate -e py311
Traceback (most recent call last):
File
"/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py",
line 317, in executing
args = executing_cache[key]
~~~~~~~~~~~~~~~^^^^^
KeyError: (<code object <module> at 0x7fb5361790d0, file
"/builddir/build/BUILD/executing-0.8.2/tests/test_main.py", line 1>,
140416273322192, 552)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/builddir/build/BUILD/executing-0.8.2/tests/test_main.py", line 682, in
<module>
assert tester([1, 2, 3]) == [1, 2, 3]
^^^^^^^^^^^^^^^^^
File "/builddir/build/BUILD/executing-0.8.2/tests/utils.py", line 40, in
__call__
ex = self.get_executing(inspect.currentframe().f_back)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/builddir/build/BUILD/executing-0.8.2/tests/utils.py", line 28, in
get_executing
return Source.executing(frame)
^^^^^^^^^^^^^^^^^^^^^^^
File
"/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py",
line 372, in executing
args = find(source=cls.for_frame(frame), retry_cache=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py",
line 349, in find
node_finder = NodeFinder(frame, stmts, tree, lasti)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py",
line 626, in __init__
raise RuntimeError(op_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: CALL
ERROR: InvocationError for command
/builddir/build/BUILD/executing-0.8.2/.tox/py311/bin/python tests/test_main.py
(exited with code 1)
___________________________________ summary
____________________________________
ERROR: py311: commands failed
error: Bad exit status from /var/tmp/rpm-tmp.m2JoFZ (%check)
Bad exit status from /var/tmp/rpm-tmp.m2JoFZ (%check)
Upstream has WIP PR for Python 3.11 suport.
The PyFrameObject structure member has been moved to the internal C API
headers.
While the documentation notes that the PyFrameObject fields are subject to
change at any time, they have been stable for a long time and were used in
several popular extensions.
In Python 3.11, the frame struct was reorganized to allow performance
optimizations. Some fields were removed entirely, as they were details of the
old implementation.
PyFrameObject fields:
f_back: use PyFrame_GetBack().
f_blockstack: removed.
f_builtins: use PyObject_GetAttrString((PyObject*)frame, "f_builtins").
f_code: use PyFrame_GetCode().
f_gen: removed.
f_globals: use PyObject_GetAttrString((PyObject*)frame, "f_globals").
f_iblock: removed.
f_lasti: use PyObject_GetAttrString((PyObject*)frame, "f_lasti"). Code
using f_lasti with PyCode_Addr2Line() must use PyFrame_GetLineNumber() instead.
f_lineno: use PyFrame_GetLineNumber()
f_locals: use PyObject_GetAttrString((PyObject*)frame, "f_locals").
f_stackdepth: removed.
f_state: no public API (renamed to f_frame.f_state).
f_trace: no public API.
f_trace_lines: use PyObject_GetAttrString((PyObject*)frame,
"f_trace_lines") (it also be modified).
f_trace_opcodes: use PyObject_GetAttrString((PyObject*)frame,
"f_trace_opcodes") (it also be modified).
f_localsplus: no public API (renamed to f_frame.localsplus).
f_valuestack: removed.
The Python frame object is now created lazily. A side effect is that the f_back
member must not be accessed directly, since its value is now also computed
lazily. The PyFrame_GetBack() function must be called instead.
https://docs.python.org/3.11/whatsnew/3.11.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora...
For all our attempts to build python-executing with Python 3.11, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/pytho...
Testing and mass rebuild of packages is happening in copr. You can follow these
instructions to test locally in mock if your package builds with Python 3.11:
https://copr.fedorainfracloud.org/coprs/g/python/python3.11/
Let us know here if you have any questions.
Python 3.11 is planned to be included in Fedora 37. To make that update
smoother, we're building Fedora packages with all pre-releases of Python 3.11.
A build failure prevents us from testing all dependent packages (transitive
[Build]Requires), so if this package is required a lot, it's important for us
to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you
don't want to work on this now, let us know so we can try to work around it on
our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2016048
[Bug 2016048] Python 3.11
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2068421
1 year, 10 months
[Bug 2067098] New: ImageMagick: heap-buffer-overflow in PushShortPixel of quantum-private.h [fedora-all]
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2067098
Bug ID: 2067098
Summary: ImageMagick: heap-buffer-overflow in PushShortPixel of
quantum-private.h [fedora-all]
Product: Fedora
Version: 35
Status: NEW
Component: ImageMagick
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: trathi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: blaise(a)gmail.com, dcavalca(a)fb.com,
epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, luya_tfz(a)thefinalzone.net,
michel(a)michel-slm.name, ngompa13(a)gmail.com,
pampelmuse(a)gmx.at, sergio(a)serjux.com,
troy(a)troycurtisjr.com
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 fedora-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. 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=2067098
1 year, 11 months
[Bug 2064538] New: ImageMagick: heap-use-after-free in RelinquishDCMInfo of dcm.c
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2064538
Bug ID: 2064538
Summary: ImageMagick: heap-use-after-free in RelinquishDCMInfo
of dcm.c
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: blaise(a)gmail.com, dcavalca(a)fb.com,
epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, jhorak(a)redhat.com,
luya_tfz(a)thefinalzone.net, michel(a)michel-slm.name,
ngompa13(a)gmail.com, pampelmuse(a)gmx.at,
sergio(a)serjux.com, troy(a)troycurtisjr.com
Target Milestone: ---
Classification: Other
A heap-use-after-free vulnerability was found in ImageMagick's
RelinquishDCMInfo function of dcm.c.
References:
https://github.com/ImageMagick/ImageMagick/issues/4947
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2064538
1 year, 11 months
[Bug 2066640] New: ImageMagick: heap-use-after-free in RelinquishDCMInfo of dcm.c [fedora-all]
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2066640
Bug ID: 2066640
Summary: ImageMagick: heap-use-after-free in RelinquishDCMInfo
of dcm.c [fedora-all]
Product: Fedora
Version: 35
Status: NEW
Component: ImageMagick
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: trathi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: blaise(a)gmail.com, dcavalca(a)fb.com,
epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, luya_tfz(a)thefinalzone.net,
michel(a)michel-slm.name, ngompa13(a)gmail.com,
pampelmuse(a)gmx.at, sergio(a)serjux.com,
troy(a)troycurtisjr.com
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 fedora-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. 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=2066640
1 year, 11 months
[Bug 2075405] New: python-flit fails to build with Python 3.11: AssertionError: assert None == 'readme.md'
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2075405
Bug ID: 2075405
Summary: python-flit fails to build with Python 3.11:
AssertionError: assert None == 'readme.md'
Product: Fedora
Version: rawhide
Status: NEW
Component: python-flit
Assignee: mhroncok(a)redhat.com
Reporter: thrnciar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
mhroncok(a)redhat.com, michel(a)michel-slm.name,
python-sig(a)lists.fedoraproject.org,
thrnciar(a)redhat.com
Blocks: 2016048 (PYTHON3.11)
Target Milestone: ---
Classification: Fedora
python-flit fails to build with Python 3.11.0a7.
=================================== FAILURES
===================================
_________________________ test_find_readme[readme.md]
__________________________
readme_file = 'readme.md'
@pytest.mark.parametrize(
"readme_file",
["readme.md", "README.MD", "README.md",
"Readme.md", "readme.MD", "readme.rst",
"readme.txt"])
def test_find_readme(readme_file):
with make_dir([readme_file]) as td:
ib = init.IniterBase(td)
> assert ib.find_readme() == readme_file
E AssertionError: assert None == 'readme.md'
E + where None = <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef22533d0>>()
E + where <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef22533d0>> = <flit.init.IniterBase object
at 0x7fdef22533d0>.find_readme
tests/test_init.py:196: AssertionError
_________________________ test_find_readme[README.MD]
__________________________
readme_file = 'README.MD'
@pytest.mark.parametrize(
"readme_file",
["readme.md", "README.MD", "README.md",
"Readme.md", "readme.MD", "readme.rst",
"readme.txt"])
def test_find_readme(readme_file):
with make_dir([readme_file]) as td:
ib = init.IniterBase(td)
> assert ib.find_readme() == readme_file
E AssertionError: assert None == 'README.MD'
E + where None = <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef200acd0>>()
E + where <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef200acd0>> = <flit.init.IniterBase object
at 0x7fdef200acd0>.find_readme
tests/test_init.py:196: AssertionError
_________________________ test_find_readme[README.md]
__________________________
readme_file = 'README.md'
@pytest.mark.parametrize(
"readme_file",
["readme.md", "README.MD", "README.md",
"Readme.md", "readme.MD", "readme.rst",
"readme.txt"])
def test_find_readme(readme_file):
with make_dir([readme_file]) as td:
ib = init.IniterBase(td)
> assert ib.find_readme() == readme_file
E AssertionError: assert None == 'README.md'
E + where None = <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef2026b50>>()
E + where <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef2026b50>> = <flit.init.IniterBase object
at 0x7fdef2026b50>.find_readme
tests/test_init.py:196: AssertionError
_________________________ test_find_readme[Readme.md]
__________________________
readme_file = 'Readme.md'
@pytest.mark.parametrize(
"readme_file",
["readme.md", "README.MD", "README.md",
"Readme.md", "readme.MD", "readme.rst",
"readme.txt"])
def test_find_readme(readme_file):
with make_dir([readme_file]) as td:
ib = init.IniterBase(td)
> assert ib.find_readme() == readme_file
E AssertionError: assert None == 'Readme.md'
E + where None = <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef1fe3010>>()
E + where <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef1fe3010>> = <flit.init.IniterBase object
at 0x7fdef1fe3010>.find_readme
tests/test_init.py:196: AssertionError
_________________________ test_find_readme[readme.MD]
__________________________
readme_file = 'readme.MD'
@pytest.mark.parametrize(
"readme_file",
["readme.md", "README.MD", "README.md",
"Readme.md", "readme.MD", "readme.rst",
"readme.txt"])
def test_find_readme(readme_file):
with make_dir([readme_file]) as td:
ib = init.IniterBase(td)
> assert ib.find_readme() == readme_file
E AssertionError: assert None == 'readme.MD'
E + where None = <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef32c6b50>>()
E + where <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef32c6b50>> = <flit.init.IniterBase object
at 0x7fdef32c6b50>.find_readme
tests/test_init.py:196: AssertionError
_________________________ test_find_readme[readme.rst]
_________________________
readme_file = 'readme.rst'
@pytest.mark.parametrize(
"readme_file",
["readme.md", "README.MD", "README.md",
"Readme.md", "readme.MD", "readme.rst",
"readme.txt"])
def test_find_readme(readme_file):
with make_dir([readme_file]) as td:
ib = init.IniterBase(td)
> assert ib.find_readme() == readme_file
E AssertionError: assert None == 'readme.rst'
E + where None = <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef32e4d10>>()
E + where <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef32e4d10>> = <flit.init.IniterBase object
at 0x7fdef32e4d10>.find_readme
tests/test_init.py:196: AssertionError
_________________________ test_find_readme[readme.txt]
_________________________
readme_file = 'readme.txt'
@pytest.mark.parametrize(
"readme_file",
["readme.md", "README.MD", "README.md",
"Readme.md", "readme.MD", "readme.rst",
"readme.txt"])
def test_find_readme(readme_file):
with make_dir([readme_file]) as td:
ib = init.IniterBase(td)
> assert ib.find_readme() == readme_file
E AssertionError: assert None == 'readme.txt'
E + where None = <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef3263a50>>()
E + where <bound method IniterBase.find_readme of
<flit.init.IniterBase object at 0x7fdef3263a50>> = <flit.init.IniterBase object
at 0x7fdef3263a50>.find_readme
tests/test_init.py:196: AssertionError
______________________ test_init_readme_found_yes_choosen
______________________
def test_init_readme_found_yes_choosen():
responses = ['test_module_name',
'Test Author',
'test_email(a)example.com',
'', # Home page omitted
'4', # Skip - choose a license later
]
with make_dir(["readme.md"]) as td, \
patch_data_dir(), \
faking_input(responses):
ti = init.TerminalIniter(td)
ti.initialise()
with Path(td, 'pyproject.toml').open('rb') as f:
data = tomli.load(f)
> assert data['project'] == {
'authors': [{'name': 'Test Author', 'email':
'test_email(a)example.com'}],
'name': 'test_module_name',
'readme': 'readme.md',
'dynamic': ['version', 'description'],
}
E AssertionError: assert {'authors': [..._module_name'} == {'authors':
[...: 'readme.md'}
E Omitting 3 identical items, use -vv to show
E Right contains 1 more item:
E {'readme': 'readme.md'}
E Use -v to get the full diff
tests/test_init.py:220: AssertionError
----------------------------- Captured stdout call
-----------------------------
Choose a license (see http://choosealicense.com/ for more info)
1. MIT - simple and permissive
2. Apache - explicitly grants patent rights
3. GPL - ensures that code based on this is shared with the same terms
4. Skip - choose a license later
Written pyproject.toml; edit that file to add optional extra info.
=========================== short test summary info
============================
FAILED tests/test_init.py::test_find_readme[readme.md] - AssertionError:
asse...
FAILED tests/test_init.py::test_find_readme[README.MD] - AssertionError:
asse...
FAILED tests/test_init.py::test_find_readme[README.md] - AssertionError:
asse...
FAILED tests/test_init.py::test_find_readme[Readme.md] - AssertionError:
asse...
FAILED tests/test_init.py::test_find_readme[readme.MD] - AssertionError:
asse...
FAILED tests/test_init.py::test_find_readme[readme.rst] - AssertionError:
ass...
FAILED tests/test_init.py::test_find_readme[readme.txt] - AssertionError:
ass...
FAILED tests/test_init.py::test_init_readme_found_yes_choosen -
AssertionErro...
=================== 8 failed, 192 passed, 2 skipped in 4.96s
===================
https://docs.python.org/3.11/whatsnew/3.11.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora...
For all our attempts to build python-flit with Python 3.11, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/pytho...
Testing and mass rebuild of packages is happening in copr. You can follow these
instructions to test locally in mock if your package builds with Python 3.11:
https://copr.fedorainfracloud.org/coprs/g/python/python3.11/
Let us know here if you have any questions.
Python 3.11 is planned to be included in Fedora 37. To make that update
smoother, we're building Fedora packages with all pre-releases of Python 3.11.
A build failure prevents us from testing all dependent packages (transitive
[Build]Requires), so if this package is required a lot, it's important for us
to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you
don't want to work on this now, let us know so we can try to work around it on
our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2016048
[Bug 2016048] Python 3.11
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2075405
1 year, 11 months
[Bug 2080476] New: ipython-8.3.0 is available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2080476
Bug ID: 2080476
Summary: ipython-8.3.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: ipython
Keywords: FutureFeature, Triaged
Assignee: lbalhar(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dcantrell(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
lbalhar(a)redhat.com, mhroncok(a)redhat.com,
michel(a)michel-slm.name, mrunge(a)redhat.com,
orion(a)nwra.com, python-sig(a)lists.fedoraproject.org,
tomspur(a)fedoraproject.org
Target Milestone: ---
Classification: Fedora
Latest upstream release: 8.3.0
Current version/release in rawhide: 8.2.0-1.fc37
URL: https://ipython.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://fedoraproject.org/wiki/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/1399/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2080476
1 year, 11 months
[Bug 2058882] New: ipython-8.1.0 is available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2058882
Bug ID: 2058882
Summary: ipython-8.1.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: ipython
Keywords: FutureFeature, Triaged
Assignee: lbalhar(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dcantrell(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
lbalhar(a)redhat.com, mhroncok(a)redhat.com,
michel(a)michel-slm.name, mrunge(a)redhat.com,
orion(a)nwra.com, python-sig(a)lists.fedoraproject.org,
tomspur(a)fedoraproject.org
Target Milestone: ---
Classification: Fedora
Latest upstream release: 8.1.0
Current version/release in rawhide: 8.0.1-1.fc36
URL: https://ipython.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://fedoraproject.org/wiki/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/1399/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2058882
1 year, 11 months
[Bug 2058448] New: rocksdb: rebuild for gflags update in c8s
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Bug ID: 2058448
Summary: rocksdb: rebuild for gflags update in c8s
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: rocksdb
Assignee: epel-packagers-sig(a)lists.fedoraproject.org
Reporter: carl(a)redhat.com
CC: dcavalca(a)fb.com,
epel-packagers-sig(a)lists.fedoraproject.org,
hegjon(a)gmail.com, mmuzila(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
In CentOS Stream 8, the gflags package was updated from 2.1.2-6.el8 to
2.2.2-1.el8 (see bug 2035143). That introduces an soname bump from
libgflags.so.2.1 to libgflags.so.2.2. rocksdb links against that soname and
must be rebuilt in epel8-next to work correctly on c8s.
Version-Release number of selected component (if applicable):
rocksdb-6.26.1-2.el8
Steps to Reproduce:
1. dnf install rocksdb (this resolves to the older gflags in the repo)
2. dnf update gflags
Actual results:
Error:
Problem: problem with installed package rocksdb-6.26.1-2.el8.x86_64
- package rocksdb-6.26.1-2.el8.x86_64 requires libgflags.so.2.1()(64bit), but
none of the providers can be installed
- cannot install both gflags-2.2.2-1.el8.x86_64 and gflags-2.1.2-6.el8.x86_64
- cannot install the best update candidate for package
gflags-2.1.2-6.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or
'--skip-broken' to skip uninstallable packages or '--nobest' to use not only
best candidate packages)
Expected results:
installation of the latest gflags and rocksdb
Additional info:
This is happening in c8s now, but will also happen when RHEL 8.6 is released.
At that point it can be remediated in regular epel8.
--
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=2058448
1 year, 11 months
[Bug 2076048] New: ImageMagick-6.9.12-45 is available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2076048
Bug ID: 2076048
Summary: ImageMagick-6.9.12-45 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: ImageMagick
Keywords: FutureFeature, Triaged
Assignee: luya_tfz(a)thefinalzone.net
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: blaise(a)gmail.com, dcavalca(a)fb.com,
epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, luya_tfz(a)thefinalzone.net,
michel(a)michel-slm.name, ngompa13(a)gmail.com,
pampelmuse(a)gmx.at, sergio(a)serjux.com,
troy(a)troycurtisjr.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 6.9.12-45
Current version/release in rawhide: 6.9.12.44-1.fc37
URL: https://legacy.imagemagick.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://fedoraproject.org/wiki/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/16253/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2076048
1 year, 11 months