November 2023 - Epel-packagers-sig - Fedora Mailing-Lists

[Bug 2120537] New: 'bodhi updates new' does not report error/warning when setting karma limit below minimal value for package in critical path

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2120537 Bug ID: 2120537 Summary: 'bodhi updates new' does not report error/warning when setting karma limit below minimal value for package in critical path Product: Fedora Version: rawhide Status: NEW Component: bodhi-client Assignee: thrcka(a)redhat.com Reporter: zdohnal(a)redhat.com CC: aurelien(a)bompard.org, epel-packagers-sig(a)lists.fedoraproject.org, lenka(a)sepu.cz, thrcka(a)redhat.com Target Milestone: --- Classification: Fedora Hi, I was surprised why my bodhi update ( https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 ) doesn't show an option for pushing into stable or why the update is not in stable already, because the positive karma limit (1) is reached. On #fedora-devel IRC channel kalev answered: (09:34:34 AM) zdohnal: Hi all, do you have an idea what blocks this update https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 from being pushed to the stable? (09:38:32 AM) kalev: zdohnal: looks like it's marked as critical path and because of that, it needs minimum of +2 karma to be pushed to stable (09:40:19 AM) GrannyGoose left the room (quit: Quit: Going offline, see ya! (www.adiirc.com)). (09:41:00 AM) zdohnal: kalev: aha - good to know. However bodhi-client should give me error when I set karma below this limit... According to the conversation, there is karma limit for components in critical path and it is higher - 2 - than the limit set by me - 1, which causes confusion. I use 'bodhi updates new' CLI command for creating updates, and I didn't see any error/warning regarding setting the karma limit too low. IMHO CLI command has to fail if user tries to set the limit too low, and bodhi web UI should handle this in some way as well. Would you mind looking into it? Version-Release number of selected component (if applicable): bodhi-client-6.0.1-4.fc37 How reproducible: always Steps to Reproduce: 1. $ bodhi updates new --type bugfix --close-bugs --request testing --autokarma --autotime --stable-karma 1 --unstable-karma -1 --notes "Update for component in critical path" <critical-component-1.2.3-1.fc37> Actual results: No error or warning, bodhi web ui shows user defined limit and the update has karma to fulfill the limit, but the update is not pushed into stable. Expected results: Give error (in both interfaces - CLI and Web UI) if user wants to set lower karma limit than it is required on the package. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2120537

4 days, 21 hours

1
1
0 / 0

[Bug 2093731] New: zbarimg does not read a Code 128 barcode

by bugzilla＠redhat.com

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

4 days, 21 hours

1
5
0 / 0

[Bug 2225757] New: diskimage-builder: FTBFS in Fedora rawhide/f39

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2225757 Bug ID: 2225757 Summary: diskimage-builder: FTBFS in Fedora rawhide/f39 Product: Fedora Version: rawhide Status: NEW Component: diskimage-builder Assignee: amoralej(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: amoralej(a)redhat.com, apevec(a)redhat.com, bnemec(a)redhat.com, davide(a)cavalca.name, epel-packagers-sig(a)lists.fedoraproject.org, jslagle(a)redhat.com, mburns(a)redhat.com, openstack-sig(a)lists.fedoraproject.org Blocks: 2168842 (F39FTBFS,RAWHIDEFTBFS) Target Milestone: --- Classification: Fedora diskimage-builder failed to build from source in Fedora rawhide/f39 https://koji.fedoraproject.org/koji/taskinfo?taskID=103568042 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild Please fix diskimage-builder at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, diskimage-builder will be orphaned. Before branching of Fedora 40, diskimage-builder will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2168842 [Bug 2168842] Fedora 39 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2225757 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week

1
8
0 / 0

[Bug 2225758] New: dlrn: FTBFS in Fedora rawhide/f39

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2225758 Bug ID: 2225758 Summary: dlrn: FTBFS in Fedora rawhide/f39 Product: Fedora Version: rawhide Status: NEW Component: dlrn Assignee: extras-orphan(a)fedoraproject.org Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, extras-orphan(a)fedoraproject.org, jpena(a)redhat.com, openstack-sig(a)lists.fedoraproject.org Blocks: 2168842 (F39FTBFS,RAWHIDEFTBFS) Target Milestone: --- Classification: Fedora dlrn failed to build from source in Fedora rawhide/f39 https://koji.fedoraproject.org/koji/taskinfo?taskID=103568275 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild Please fix dlrn at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, dlrn will be orphaned. Before branching of Fedora 40, dlrn will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2168842 [Bug 2168842] Fedora 39 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2225758 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week

1
8
0 / 0

[Bug 2251779] New: python-zope-testrunner fails to build with Python 3.13: ImportError: cannot import name '_start_new_thread' from 'threading'

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2251779 Bug ID: 2251779 Summary: python-zope-testrunner fails to build with Python 3.13: ImportError: cannot import name '_start_new_thread' from 'threading' Product: Fedora Version: rawhide Status: NEW Component: python-zope-testrunner Assignee: loganjerry(a)gmail.com Reporter: ksurma(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: aurelien(a)bompard.org, epel-packagers-sig(a)lists.fedoraproject.org, infra-sig(a)lists.fedoraproject.org, ksurma(a)redhat.com, loganjerry(a)gmail.com, mhroncok(a)redhat.com, michel(a)michel-slm.name Blocks: 2244836 (PYTHON3.13) Target Milestone: --- Classification: Fedora python-zope-testrunner fails to build with Python 3.13.0a1. This report is automated and not very verbose, but we'll try to get back here with details. + python3 -m unittest discover -s zope/testrunner -t . .........................................E ====================================================================== ERROR: zope.testrunner.tests.test_threadsupport (unittest.loader._FailedTest.zope.testrunner.tests.test_threadsupport) ---------------------------------------------------------------------- ImportError: Failed to import test module: zope.testrunner.tests.test_threadsupport Traceback (most recent call last): File "/usr/lib64/python3.13/unittest/loader.py", line 394, in _find_test_path module = self._get_module_from_name(name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.13/unittest/loader.py", line 337, in _get_module_from_name __import__(name) File "/builddir/build/BUILDROOT/python-zope-testrunner-6.2-1.fc40.x86_64/usr/lib/python3.13/site-packages/zope/testrunner/tests/test_threadsupport.py", line 16, in <module> from threading import _start_new_thread ImportError: cannot import name '_start_new_thread' from 'threading' (/usr/lib64/python3.13/threading.py). Did you mean: '_start_joinable_thread'? ---------------------------------------------------------------------- Ran 42 tests in 0.014s https://docs.python.org/3.13/whatsnew/3.13.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora... For all our attempts to build python-zope-testrunner with Python 3.13, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/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.13: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/ Let us know here if you have any questions. Python 3.13 is planned to be included in Fedora 41. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13. 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=2244836 [Bug 2244836] Python 3.13 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2251779 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week, 2 days

1
3
0 / 0

[Bug 2240040] New: [abrt] blender: module(): gltf2_blender_conversion.py:5:<module>:ModuleNotFoundError: No module named 'numpy'

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2240040 Bug ID: 2240040 Summary: [abrt] blender: module(): gltf2_blender_conversion.py:5:<module>:ModuleNotFoundE rror: No module named 'numpy' Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:69a60ba0c5ea2d290eef274755b30460e5715da6;VAR IANT_ID=workstation; Component: blender Assignee: luya_tfz(a)thefinalzone.net Reporter: redhat.vb4r3(a)passinbox.com QA Contact: extras-qa(a)fedoraproject.org CC: code(a)musicinmybrain.net, design-devel(a)lists.fedoraproject.org, epel-packagers-sig(a)lists.fedoraproject.org, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: blender-1:3.5.1-3.fc38 Additional info: reporter: libreport-2.17.11 kernel: 6.4.14-200.fc38.x86_64 cmdline: /usr/bin/blender /home/seth/obama/obama_freedom_device.blend cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Nautilus@5.service uid: 1000 reason: gltf2_blender_conversion.py:5:<module>:ModuleNotFoundError: No module named 'numpy' executable: /usr/bin/blender type: Python3 package: blender-1:3.5.1-3.fc38 runlevel: N 5 exception_type: ModuleNotFoundError crash_function: module interpreter: blender-3.5.1-3.fc38.x86_64 Truncated backtrace: #1 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/com/gltf2_blender_conversion.py:5] <module> #2 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_get.py:8] <module> #3 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_gather_cache.py:6] <module> #4 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_gather_nodes.py:10] <module> #5 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_gather.py:8] <module> #6 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_export.py:11] <module> #7 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/__init__.py:583] execute -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2240040 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week, 4 days

1
3
0 / 0

[Bug 2249063] New: CVE-2023-5363 openssl3: openssl: Incorrect cipher key and IV length processing [epel-8]

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2249063 Bug ID: 2249063 Summary: CVE-2023-5363 openssl3: openssl: Incorrect cipher key and IV length processing [epel-8] Product: Fedora EPEL Version: epel8 Status: NEW Component: openssl3 Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: michel(a)michel-slm.name Reporter: saroy(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2243839 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=2249063 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week, 4 days

1
6
0 / 0

[Bug 2248621] New: CVE-2023-5678 openssl3: openssl: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow [epel-8]

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2248621 Bug ID: 2248621 Summary: CVE-2023-5678 openssl3: openssl: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow [epel-8] Product: Fedora EPEL Version: epel8 Status: NEW Component: openssl3 Keywords: Security, SecurityTracking Severity: low Priority: low Assignee: michel(a)michel-slm.name Reporter: askrabec(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2248616 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=2248621 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week, 4 days

1
6
0 / 0

[Bug 2228050] New: CVE-2023-3817 openssl3: OpenSSL: Excessive time spent checking DH q parameter value [epel-all]

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2228050 Bug ID: 2228050 Summary: CVE-2023-3817 openssl3: OpenSSL: Excessive time spent checking DH q parameter value [epel-all] Product: Fedora EPEL Version: epel8 Status: NEW Component: openssl3 Keywords: Security, SecurityTracking Severity: low Priority: low Assignee: michel(a)michel-slm.name Reporter: saroy(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2227852 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=2228050 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week, 4 days

1
6
0 / 0

[Bug 2223821] New: TRIAGE-CVE-2023-2975 openssl3: openSSL: AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries [epel-8]

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2223821 Bug ID: 2223821 Summary: TRIAGE-CVE-2023-2975 openssl3: openSSL: AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries [epel-8] Product: Fedora EPEL Version: epel8 Status: NEW Component: openssl3 Keywords: Security, SecurityTracking Severity: low Priority: low Assignee: michel(a)michel-slm.name Reporter: saroy(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2223016 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=2223821 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

1 week, 4 days

1
6
0 / 0

2024

2023

2022

2021

Epel-packagers-sig November 2023