November 2024 - Epel-packagers-sig - Fedora mailing-lists

[Bug 2210464] New: python-nbxmpp-4.3.0 is available
by bugzilla＠redhat.com 15 May '25

15 May '25

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 62

[Bug 2210415] New: gajim-1.8.0 is available
by bugzilla＠redhat.com 15 May '25

15 May '25

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 58

[Bug 2321588] binutils 2.43.50-1.fc42 -> 2.43.50-2.fc42 regression. unexpected Segmentation fault in meson-python test
by bugzilla＠redhat.com 14 May '25

14 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2321588 --- Comment #39 from Nick Clifton <nickc(a)redhat.com> --- (In reply to Miro Hrončok from comment #38) > Indeed. I got the impression that you do not intend to solve this because > it's a problem in patchelf. Perhaps I misunderstood. Well the truth is that I am hoping that this will turn out to be a problem with patchelf and that I will not need to do anything to the linker. But I am not going to cross my arms and refuse to do anything. I will still try to work with you and anyone else to get to the bottom of this matter and solve the problem. > > (Incidentally this does suggest another possible workaround that > > you try - linking with "-Wl,--noseparate-code" - this should use > > the old layout which combines read-only and code sections into > > one segment. Which is what has been the default in older > > distributions and which presumably works just fine with patchelf). > > Is this the same as -Wl,--no-rosegment? Not the same, but related. The --separate-code option (enabled by default for x86_64) tells the linker to create separate segments for read-only data and code. (Instead of combining them as it used to do). But this option ends up creating *two* read-only segments, one before the code segment and one after it. Which whilst perfectly legal according to the ELF specification does also mean an increase in file size (because segments in the file image are padded out so that they can just be mmap'ed into memory). And file size increases are a problem for containers. The --rosegment option is an attempt to address this issue by augmenting the behaviour of the --separate-code option so that only one read-only segment is produced. (If --separate-code is not active then --rosegment has no effect). It was doen this way because --separate-code was implemented a few years ago but the container size problem has only recently come to light. So, using -Wl,--noseparate-code should make the linker go back to its old layout behaviour, which should be something that is familiar to patchelf. > I was about to ask if building stuff > with this flag is dangerous in any way. Maybe... It increases the risk of successful ROP and JOP style attacks: https://en.wikipedia.org/wiki/Return-oriented_programming If code is separate from read-only data then the read-only data cannot be mis-interpreted as instructions and executed, thus reducing the attack surface for ROP/JOP attacks. Of course using --noseparate-code does not mean that these attacks will occur, or that guarantee that useful sequences of data-that-looks- like-code will be found. But using --separate-code just makes things that harder for potential bad actors. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2321588 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

2 0

[Bug 2325848] New: matrix-synapse-1.119.0rc2 is available
by bugzilla＠redhat.com 13 May '25

13 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2325848 Bug ID: 2325848 Summary: matrix-synapse-1.119.0rc2 is available Product: Fedora Version: rawhide Status: NEW Component: matrix-synapse Keywords: FutureFeature, Triaged Assignee: V02460(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: djc(a)djc.id.au, epel-packagers-sig(a)lists.fedoraproject.org, fedora(a)alex-m.co.uk, jonathan(a)almalinux.org, V02460(a)gmail.com Target Milestone: --- Classification: Fedora Releases retrieved: 1.119.0rc1, 1.119.0rc2 Upstream release that is considered latest: 1.119.0rc2 Current version/release in rawhide: 1.118.0-1.fc42 URL: https://github.com/element-hq/synapse 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/15283/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/matrix-synapse -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2325848 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 92

[Bug 2300701] New: gmime: FTBFS in Fedora rawhide/f41
by bugzilla＠redhat.com 13 May '25

13 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2300701 Bug ID: 2300701 Summary: gmime: FTBFS in Fedora rawhide/f41 Product: Fedora Version: rawhide Status: NEW Component: gmime Assignee: alexl(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: alexl(a)redhat.com, epel-packagers-sig(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, mclasen(a)redhat.com, rstrode(a)redhat.com, walter.pete(a)yandex.com Blocks: 2260875 (F41FTBFS) Target Milestone: --- Classification: Fedora gmime failed to build from source in Fedora rawhide/f41 https://koji.fedoraproject.org/koji/taskinfo?taskID=120660987 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild Please fix gmime 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, gmime will be orphaned. Before branching of Fedora 42, gmime 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_Fails… Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2260875 [Bug 2260875] Fedora 41 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=2300701 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 7

[Bug 2256783] New: FTBFS with autoconf 2.72
by bugzilla＠redhat.com 13 May '25

13 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2256783 Bug ID: 2256783 Summary: FTBFS with autoconf 2.72 Product: Fedora Version: rawhide OS: Linux Status: NEW Component: gmime Severity: medium Assignee: alexl(a)redhat.com Reporter: fberat(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: alexl(a)redhat.com, epel-packagers-sig(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, mclasen(a)redhat.com, rstrode(a)redhat.com, walter.pete(a)yandex.com Target Milestone: --- Classification: Fedora The component fails to build with autoconf 2.72 due to its use of Autoconf internal variables in its configure.ac file. the following section needs to be adapted (or better removed): dnl ************************************* dnl *** Checks for large file support *** dnl ************************************* AC_ARG_ENABLE([largefile], AC_HELP_STRING([--enable-largefile], [enable support for large files [[default=yes]]]),, [enable_largefile="yes"]) [...] if test "x$ac_cv_sys_file_offset_bits" != "xno"; then LFS_CFLAGS="$LFS_CFLAGS -D_FILE_OFFSET_BITS=$ac_cv_sys_file_offset_bits" enable_largefile="yes" fi else LFS_CFLAGS="" fi AM_CONDITIONAL(ENABLE_LARGEFILE, test "x$enable_largefile" = "xyes") The main problem of this section being the check against `$ac_cv_sys_file_offset_bits` which no longer exists. Leading to further failures. AC_SYS_LARGEFILE will define _FILE_OFFSET_BITS if necessary. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2256783 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 6

[Bug 2322867] New: selinux policy violations when asterisk tries to read /proc/sys/net
by bugzilla＠redhat.com 13 May '25

13 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2322867 Bug ID: 2322867 Summary: selinux policy violations when asterisk tries to read /proc/sys/net Product: Fedora Version: 41 Hardware: x86_64 OS: Linux Status: NEW Component: asterisk Severity: medium Assignee: jsmith.fedora(a)gmail.com Reporter: davek(a)komacke.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 Target Milestone: --- Classification: Fedora This seems to have been around for a while. It was reported in Redhat here: 1810727, which was closed for being reported too late in a release cycle. pjsip wants to read /proc/sys/net to figure out some networking information to configure itself. This seems to be triggering selinux policy violations. As covered in the bug above this local policy will resolve it: module my-asterisk 1.0; require { type asterisk_t; type sysctl_net_t; class dir search; class file { getattr open read }; } #============= asterisk_t ============== allow asterisk_t sysctl_net_t:dir search; allow asterisk_t sysctl_net_t:file { getattr open read }; Reproducible: Always Steps to Reproduce: 1. configure asterisk to use pjsip with a "type = transport" section 2. start asterisk 3. check for selinux policy violations for reading from /proc/sys/net/ipv6 and ipv4 Actual Results: I think asterisk is actually running ok. I found these issues by reviewing my journalctl setroubleshoot output. Expected Results: No selinux policy voilations -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2322867 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 8

[Bug 2320845] New: Please branch and build msmtp in epel10
by bugzilla＠redhat.com 13 May '25

13 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2320845 Bug ID: 2320845 Summary: Please branch and build msmtp in epel10 Product: Fedora EPEL Version: epel10 Status: NEW Component: msmtp Assignee: lemenkov(a)gmail.com Reporter: romain.geissler(a)amadeus.com QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, gbcox(a)bzb.us, lemenkov(a)gmail.com, ndevos(a)redhat.com, wart(a)kobold.org Target Milestone: --- Classification: Fedora Please branch and build msmtp in epel10. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2320845 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 17

[Bug 2262655] New: python-Bottleneck-1.3.8rc3 is available
by bugzilla＠redhat.com 13 May '25

13 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2262655 Bug ID: 2262655 Summary: python-Bottleneck-1.3.8rc3 is available Product: Fedora Version: rawhide Status: NEW Component: python-Bottleneck Keywords: FutureFeature, Triaged Assignee: besser82(a)fedoraproject.org Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: besser82(a)fedoraproject.org, epel-packagers-sig(a)lists.fedoraproject.org, jonathan(a)almalinux.org Target Milestone: --- Classification: Fedora Releases retrieved: 1.3.8rc3 Upstream release that is considered latest: 1.3.8rc3 Current version/release in rawhide: 1.3.7-5.fc40 URL: https://pypi.python.org/pypi/Bottleneck 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/3787/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-Bottleneck -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2262655 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 38

[Bug 2209027] New: psutils-3.0 is available
by bugzilla＠redhat.com 12 May '25

12 May '25

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 20

2025

2024

2023

2022

2021

Epel-packagers-sig November 2024