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

[Bug 2188913] New: wimlib-1.14.0 is available

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2188913 Bug ID: 2188913 Summary: wimlib-1.14.0 is available Product: Fedora Version: rawhide Status: NEW Component: wimlib Keywords: FutureFeature, Triaged Assignee: pikachu.2014(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, pikachu.2014(a)gmail.com Target Milestone: --- Classification: Fedora Releases retrieved: 1.14.0 Upstream release that is considered latest: 1.14.0 Current version/release in rawhide: 1.13.6-2.fc38 URL: https://wimlib.net/ 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... 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/16320/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/wimlib -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2188913

8 months, 3 weeks

1
20
0 / 0

[Bug 2240297] New: dnscrypt-proxy package doesn't create /var/cache/dnscrypt-proxy directory

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2240297 Bug ID: 2240297 Summary: dnscrypt-proxy package doesn't create /var/cache/dnscrypt-proxy directory Product: Fedora Version: 39 Status: NEW Component: dnscrypt-proxy Assignee: davide(a)cavalca.name Reporter: morb(a)misentropic.com QA Contact: extras-qa(a)fedoraproject.org CC: davide(a)cavalca.name, epel-packagers-sig(a)lists.fedoraproject.org, go-sig(a)lists.fedoraproject.org, zebob.m(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: The package fails to create /var/cache/dnscrypt-proxy, thusly preventing downloading lists of resolvers and further bootstrapping Version-Release number of selected component (if applicable): dnscrypt-proxy-2.1.4-2.fc39 How reproducible: quite Steps to Reproduce: 1. Install the dnscrypt-proxy package from a mirror 2. Start the service 3. Check journalctl for error messages from the service, claiming its inability to update cache file Actual results: ep 22 19:32:27 peppermill dnscrypt-proxy[19778]: dnscrypt-proxy 2.1.4 Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Network connectivity detected Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Now listening to 127.0.0.1:53 [UDP] Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Now listening to 127.0.0.1:53 [TCP] Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Service is not usable yet Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Resolving server host [download.dnscrypt.info] using bootstrap resolvers over udp Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [public-resolvers] failed to update cache file [/var/cache/dnscrypt-proxy/public-resolvers.md]: open /var/cache/dnscrypt-proxy/sf-jm64uh4swjstkxyl.tmp: no such file or directory Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [public-resolvers] loaded Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Service is not usable yet Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Resolving server host [raw.githubusercontent.com] using bootstrap resolvers over udp Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [relays] failed to update cache file [/var/cache/dnscrypt-proxy/relays.md]: open /var/cache/dnscrypt-proxy/sf-uvkpifsx2fujtmrn.tmp: no such file or directory Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [relays] loaded Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Unable to use source [public-resolvers]: [Invalid format for source at [[https://download.dnscrypt.info/resolvers-list/v3/public-resolvers.md https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/p... https://ipv6.download.dnscrypt.info/resolvers-list/v3/public-resolvers.md]]] Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Invalid format for source at [[https://download.dnscrypt.info/resolvers-list/v3/public-resolvers.md https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/p... .md https://ipv6.download.dnscrypt.info/resolvers-list/v3/public-resolvers.md]] Sep 22 19:32:28 peppermill systemd[1]: dnscrypt-proxy.service: Main process exited, code=exited, status=255/EXCEPTION Sep 22 19:32:28 peppermill systemd[1]: dnscrypt-proxy.service: Failed with result 'exit-code'. Expected results: After directory creation: Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: dnscrypt-proxy 2.1.4 Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Network connectivity detected Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Now listening to 127.0.0.1:53 [UDP] Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Now listening to 127.0.0.1:53 [TCP] Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Service is not usable yet Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Resolving server host [raw.githubusercontent.com] using bootstrap resolvers over udp Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Source [public-resolvers] loaded Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Service is not usable yet Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Resolving server host [download.dnscrypt.info] using bootstrap resolvers over udp Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Source [relays] loaded Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Firefox workaround initialized ... Additional info: None -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2240297 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
9
0 / 0

[Bug 2217335] New: dnscrypt-proxy auto-enables itself after installation

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2217335 Bug ID: 2217335 Summary: dnscrypt-proxy auto-enables itself after installation Product: Fedora Version: rawhide OS: Linux Status: NEW Component: dnscrypt-proxy Severity: medium Assignee: davide(a)cavalca.name Reporter: pemensik(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: davide(a)cavalca.name, epel-packagers-sig(a)lists.fedoraproject.org, go-sig(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora I have installed dnscrypt-proxy to look into its documentation. I were using unbound+dnssec-trigger and wanted it to continue. But after a reboot my configuration were broken and VPN redirection did not work. I have found that happened because dnscrypt-proxy has a custom way to auto-enable itself on installation. I do not think this is allowed by packaging guidelines. Reproducible: Always Steps to Reproduce: 1. dnf install unbound dnssec-trigger 2. dnf enable --now dnssec-triggerd 3. dnf install dnscrypt-proxy 4. reboot Actual Results: my explicitly configured unbound has failed to startup, because there is different service listening on the same port already. I have never chosen to replace that by dnscrypt-proxy. Expected Results: The service is enabled only manually, by usual configuration via systemctl: systemctl enable --now dnscrypt-proxy Fedora allows auto-enabled services only when they do not modify other services. That does not happen directly, but by listening on common domain port on 127.0.0.1 it effectively does. If it used alternative localhost address it might be okay. But it must not as it is now. This service has not a FESCo ticket required to be enabled by default: https://src.fedoraproject.org/rpms/fedora-release/blob/rawhide/f/90-defau... I do not think it passes guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices... It also does not use systemd macros, which I think it should use: https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_sy... -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2217335 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
10
0 / 0

[Bug 2210222] New: Systemd unit file is not shipped in %_unitdir

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2210222 Bug ID: 2210222 Summary: Systemd unit file is not shipped in %_unitdir Product: Fedora Version: 38 OS: Linux Status: NEW Component: dnscrypt-proxy Severity: low Assignee: zebob.m(a)gmail.com Reporter: pemensik(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: davide(a)cavalca.name, epel-packagers-sig(a)lists.fedoraproject.org, go-sig(a)lists.fedoraproject.org, zebob.m(a)gmail.com Target Milestone: --- Classification: Fedora I have noticed after installing dnscrypt-proxy package, that its systemd unit file is not in vendor path where unit files from packages are supposed to be. That should be fixed. Reproducible: Always Steps to Reproduce: 1. systemctl cat dnscrypt-proxy | head -1 2. 3. Actual Results: # /etc/systemd/system/dnscrypt-proxy.service Expected Results: # /usr/lib/systemd/system/dnscrypt-proxy.service -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2210222

8 months, 3 weeks

1
6
0 / 0

[Bug 2241775] New: TRIAGE-CVE-2023-5341 ImageMagick: Heap use-after-free in coders/bmp.c [epel-all]

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2241775 Bug ID: 2241775 Summary: TRIAGE-CVE-2023-5341 ImageMagick: Heap use-after-free in coders/bmp.c [epel-all] Product: Fedora EPEL Version: epel8 Status: NEW Component: ImageMagick Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: luya_tfz(a)thefinalzone.net Reporter: pdelbell(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: blaise(a)gmail.com, davide(a)cavalca.name, 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 Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2241774 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=2241775 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
2
0 / 0

[Bug 2241493] New: python-executing-2.0.0 is available

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2241493 Bug ID: 2241493 Summary: python-executing-2.0.0 is available Product: Fedora Version: rawhide Status: NEW Component: python-executing Keywords: FutureFeature, Triaged Assignee: rominf(a)aiven.io Reporter: upstream-release-monitoring(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, lbalhar(a)redhat.com, paul.wouters(a)aiven.io, rominf(a)aiven.io, thrnciar(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 2.0.0 Upstream release that is considered latest: 2.0.0 Current version/release in rawhide: 1.2.0-4.fc39 URL: https://pypi.org/project/executing/0.3.1 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... 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/24668/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-executing -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2241493 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
4
0 / 0

[Bug 2241507] New: python-stack-data-0.6.3 is available

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2241507 Bug ID: 2241507 Summary: python-stack-data-0.6.3 is available Product: Fedora Version: rawhide Status: NEW Component: python-stack-data Keywords: FutureFeature, Triaged Assignee: lbalhar(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, lbalhar(a)redhat.com, michel(a)michel-slm.name Target Milestone: --- Classification: Fedora Releases retrieved: 0.6.3 Upstream release that is considered latest: 0.6.3 Current version/release in rawhide: 0.6.2-5.fc39 URL: https://pypi.org/project/stack-data/0.0.7 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... 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/90020/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-stack-data -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2241507 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
2
0 / 0

[Bug 2240047] New: nemo can not search on smb mountpoint

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2240047 Bug ID: 2240047 Summary: nemo can not search on smb mountpoint Product: Fedora Version: 38 OS: Linux Status: NEW Component: nemo Keywords: Desktop, Regression Severity: medium Assignee: leigh123linux(a)googlemail.com Reporter: bugzilla(a)edvsg.de QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, leigh123linux(a)googlemail.com, riehecky(a)fnal.gov Target Milestone: --- Classification: Fedora nemo version 5.8.4 I have mounted a SMB share from a NAS via NEMO using "CONNECT SERVER". On this share Nemo does not start searching. We have checked this with STRACE. Nemo does not start searching. The settings in NEMO are all on default. But Nemo can search locally, that is not a problem. Note: has worked in previouse version of nemo on the same device Reproducible: Always Steps to Reproduce: see above -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2240047 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
9
0 / 0

[Bug 2222118] New: nemo: /usr/share/nemo.desktop: OnlyShowIn=X-Cinnamon;Budgie;

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2222118 Bug ID: 2222118 Summary: nemo: /usr/share/nemo.desktop: OnlyShowIn=X-Cinnamon;Budgie; Product: Fedora Version: 38 Hardware: x86_64 OS: Linux Status: NEW Component: nemo Severity: low Assignee: leigh123linux(a)googlemail.com Reporter: originalme8(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, leigh123linux(a)googlemail.com, riehecky(a)fnal.gov Target Milestone: --- Classification: Fedora Created attachment 1975219 --> https://bugzilla.redhat.com/attachment.cgi?id=1975219&action=edit Image showing grep of the nemo.desktop file showing problematic line. Description of problem: When installing the Nemo file manager on a Fedora system running the default GNOME desktop, there is no icon created Version-Release number of selected component (if applicable): Fedora 36+ nemo 5.8.3, but reproduced in previous versions How reproducible: Every time Nemo is installed or updated via the Fedora updates repository. Steps to Reproduce: 1. Install Fedora using the default GNOME desktop 2. Install Nemo file manager package from Fedora updates repository 3. Optional: Remove Nautilus file manager from locally installed packages (this makes it easier to identify) 3. Look for Files in the GNOME application "Apps" list Actual results: No icon is displayed called "Files" for the Nemo file manager. If Nautilus has been removed, then there are no "Files" icons shown at all. Expected results: As a user, I would expect a new icon to be displayed after installing a new file manager. Either two "Files" icons will be displayed if Nautilus is installed, or an icon will be shown labeled "Files" which will launch the Nemo file manager. Additional info: This is caused because by default the "desktop" file (/usr/share/applications/nemo.desktop) has a line which limits which environments the icon will be displayed for. Currently, this is limited to Cinnamon and Budgie. You can comment out this line to have it display, but it must be done each time the package is updated. Line OnlyShowIn=X-Cinnamon;Budgie; -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2222118 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
7
0 / 0

[Bug 2155532] Activities search for "nemo" doesn't list nemo file manager even if installed

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2155532 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|nemo-5.8.5-2.fc39 |nemo-5.8.5-2.fc39 | |nemo-5.8.5-2.fc38 --- Comment #10 from Fedora Update System <updates(a)fedoraproject.org> --- FEDORA-2023-e6067e79ca has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2155532 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...

8 months, 3 weeks

1
0
0 / 0

2024

2023

2022

2021

Epel-packagers-sig October 2023