Re: zlib-ng as a compat replacement for zlib
Also to that point, the compatibility issues aren't always compatibility issues, but rather poorly written tests. For example, some tests might hardcode an expected checksum [0] for the compressed output, which could be broken by any number of changes even if the compressed output is entirely valid and decompresses correctly. [0] https://github.com/rpm-software-management/createrepo_c/pull/336 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Proposal to CANCEL: 2023-08-07 Fedora QA Meeting
Hi folks! I'm proposing we cancel the QA meeting tomorrow. It's a holiday in Canada and some folks may still be recovering from Flock. If anyone thinks we should have a meeting and wants to run it instead of me, please go ahead and send out an agenda and plan to run the meeting - see https://fedoraproject.org/wiki/QA:SOP_IRC_meeting_process Thanks folks! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: List of long term FTBFS packages to be retired this week
On 8/5/23 12:47, Miro Hrončok wrote: On 01. 08. 23 23:48, Robert-André Mauchin wrote: On 7/31/23 12:13, Miro Hrončok wrote: Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 39 approximately one week before branching. 5 weekly reminders are required, hence the retirement will happen this week. Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The packages in rawhide were not successfully built at least since Fedora 36. This report is based on dist tags. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb If you see a package that was built, please let me know. If you see a package that should be exempted from the process, please let me know and we can work together to get a FESCo approval for that. If you see a package that can be rebuilt, please do so. Package (co)maintainers Can you exempt the golang packages for a while more? I'm working on them... The current list is: golang-github-burntsushi-xgbutil golang-github-docker-slim golang-github-facebookarchive-inject golang-github-facebookarchive-structtag golang-github-facebookgo-ensure golang-github-facebookgo-stack golang-github-haproxytech-models golang-gopkg-seborama-govcr-2 golang-gvisor golang-rsc-qr golang-sigs-k8s-kustomize golang-vitess Branching is in couple days. Should I exempt them still? The following can be nuked: golang-github-burntsushi-xgbutil to retire and then update deepin zhich does not use it anymore golang-github-docker-slim renamed to https://github.com/slimtoolkit/slim/ Retire then rebuild under the new name golang-github-facebookarchive-inject Was potentially used for unbundling Grafana but not used upstream anymore golang-github-facebookarchive-structtag Was potentially used for unbundling Grafana but not used upstream anymore golang-github-facebookgo-ensure Needed by golang-github-facebookincubator-dhcplb which we can update to get rid of it, then leaf to drop golang-github-facebookgo-stackNeeded by golang-github-facebookgo-ensure, to drop golang-github-haproxytech-models To retire, was merged into github.com/haproxytech/client-native, which is not packaged yet golang-gopkg-seborama-govcr-2 To retire, we update to 4.5.0 through a new package https://pagure.io/releng/fedora-scm-requests/issue/55265 This one is fixed: golang-rsc-qr So TL:DR: these still need exemption if possible: golang-gvisor: I'm currently updating it, but I need to update containerd for it and it's a hell of a job golang-sigs-k8s-kustomize: new deps are needed to fix it golang-vitess: new deps are needed to fix it Thank you! Robert-André ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Problem with ffmpeg and chromaprint circular dependency
On Sun, 2023-08-06 at 10:08 -0500, Richard Shaw wrote: > On Sun, Aug 6, 2023 at 9:44 AM Sérgio Basto > wrote: > > On Sun, 2023-08-06 at 08:04 -0500, Richard Shaw wrote: > > > From what I can tell in the spec file[1] for chromaprint, the > > > only thing that's supposed to depend on ffmpeg is the tools > > > package, but it seems to have found its way into > > > libchromaprint[2] as well. > > > > > > I'm trying to build a new version of codec2 with a soname change > > > but I'm hitting this: > > > DEBUG util.py:442: Problem: package libchromaprint-devel-1.5.1- > > > 11.fc39.i686 from build requires libchromaprint.so.1, but none of > > > the providers can be installed > > > DEBUG util.py:442: - package libchromaprint-devel-1.5.1- > > > 11.fc39.i686 from build requires libchromaprint(x86-32) = 1.5.1- > > > 11.fc39, but none of the providers can be installed > > > DEBUG util.py:442: - package libchromaprint-1.5.1-11.fc39.i686 > > > from build requires libavcodec.so.60, but none of the providers > > > can be installed > > > DEBUG util.py:442: - package libchromaprint-1.5.1-11.fc39.i686 > > > from build requires libavcodec.so.60(LIBAVCODEC_60), but none of > > > the providers can be installed > > > DEBUG util.py:442: - conflicting requests > > > DEBUG util.py:442: - nothing provides libcodec2.so.1.0 needed > > > by libavcodec-free-6.0-10.fc39.i686 from build > > > > > > I'm guessing I don't have a choice but to do a bootstrap build of > > > libchromaprint without ffmpeg first... > > > > > > > > no, see my fork > > https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/commits/rawhide > > and specially commit > > https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/c/0e39e40877b404970ab024c579283e50851db20c?branch=rawhide > > > > > Let me know if I missed something but those commits don't seem to > have made their way into SCM so doesn't really help. The solution that we found after talk with upstream [1] is bootstrap chromaprint before soname bump ffmpeg Also we can leave with chromaprint bootstrapped , ffmpeg is just used for a particular thing that is rarely used IIRC [1] https://github.com/acoustid/chromaprint/issues/129#issuecomment-1468612507 > Also, as far as I know there's no way to pass general options or -- > with / --without options to Koji. > > Thanks, > Richard > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Problem with ffmpeg and chromaprint circular dependency
Specifically I think this needs to be addressed if possible: # dnf repoquery --whatrequires libchromaprint\* | grep x86_64 Last metadata expiration check: 0:02:55 ago on Sun 06 Aug 2023 10:10:31 AM CDT. acoustid-fingerprinter-0:0.6-31.fc38.x86_64 chromaprint-tools-0:1.5.1-8.fc38.x86_64 clementine-0:1.4.0~rc2-3.fc38.x86_64 ffmpeg-libs-0:6.0-11.fc38.x86_64 ffmpeg-libs-0:6.0-6.fc38.x86_64 gstreamer1-plugins-bad-free-extras-0:1.22.1-1.fc38.x86_64 gstreamer1-plugins-bad-free-extras-0:1.22.5-1.fc38.x86_64 kid3-common-0:3.9.2-3.fc38.x86_64 kid3-common-0:3.9.4-1.fc38.x86_64 libavformat-free-0:6.0-2.fc38.x86_64 libavformat-free-0:6.0-4.fc38.x86_64 libchromaprint-devel-0:1.5.1-8.fc38.x86_64 mixxx-0:2.3.4-2.fc38.x86_64 mixxx-0:2.3.5-1.fc38.x86_64 strawberry-0:1.0.15-1.fc38.x86_64 strawberry-0:1.0.18-1.fc38.x86_64 vlc-core-1:3.0.19-0.3.fc38.1.x86_64 # dnf repoquery --requires libchromaprint\* Last metadata expiration check: 0:03:19 ago on Sun 06 Aug 2023 10:10:31 AM CDT. /usr/bin/pkg-config libavcodec.so.60 libavcodec.so.60()(64bit) libavcodec.so.60(LIBAVCODEC_60) libavcodec.so.60(LIBAVCODEC_60)(64bit) libavutil.so.58 libavutil.so.58()(64bit) libavutil.so.58(LIBAVUTIL_58) libavutil.so.58(LIBAVUTIL_58)(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.4) libchromaprint(x86-32) = 1.5.1-8.fc38 libchromaprint(x86-64) = 1.5.1-8.fc38 libchromaprint.so.1 libchromaprint.so.1()(64bit) [SNIP] Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Problem with ffmpeg and chromaprint circular dependency
On Sun, Aug 6, 2023 at 9:44 AM Sérgio Basto wrote: > On Sun, 2023-08-06 at 08:04 -0500, Richard Shaw wrote: > > From what I can tell in the spec file[1] for chromaprint, the only thing > that's supposed to depend on ffmpeg is the tools package, but it seems to > have found its way into libchromaprint[2] as well. > > I'm trying to build a new version of codec2 with a soname change but I'm > hitting this: > DEBUG util.py:442: Problem: package > libchromaprint-devel-1.5.1-11.fc39.i686 from build requires > libchromaprint.so.1, but none of the providers can be installed > DEBUG util.py:442:- package libchromaprint-devel-1.5.1-11.fc39.i686 > from build requires libchromaprint(x86-32) = 1.5.1-11.fc39, but none of the > providers can be installed > DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from > build requires libavcodec.so.60, but none of the providers can be installed > DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from > build requires libavcodec.so.60(LIBAVCODEC_60), but none of the providers > can be installed > DEBUG util.py:442:- conflicting requests > DEBUG util.py:442:- nothing provides libcodec2.so.1.0 needed by > libavcodec-free-6.0-10.fc39.i686 from build > > I'm guessing I don't have a choice but to do a bootstrap build of > libchromaprint without ffmpeg first... > > > > no, see my fork > > https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/commits/rawhide > and specially commit > > https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/c/0e39e40877b404970ab024c579283e50851db20c?branch=rawhide > Let me know if I missed something but those commits don't seem to have made their way into SCM so doesn't really help. Also, as far as I know there's no way to pass general options or --with / --without options to Koji. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Problem with ffmpeg and chromaprint circular dependency
On Sun, 2023-08-06 at 08:04 -0500, Richard Shaw wrote: > From what I can tell in the spec file[1] for chromaprint, the only > thing that's supposed to depend on ffmpeg is the tools package, but > it seems to have found its way into libchromaprint[2] as well. > > I'm trying to build a new version of codec2 with a soname change but > I'm hitting this: > DEBUG util.py:442: Problem: package libchromaprint-devel-1.5.1- > 11.fc39.i686 from build requires libchromaprint.so.1, but none of the > providers can be installed > DEBUG util.py:442: - package libchromaprint-devel-1.5.1- > 11.fc39.i686 from build requires libchromaprint(x86-32) = 1.5.1- > 11.fc39, but none of the providers can be installed > DEBUG util.py:442: - package libchromaprint-1.5.1-11.fc39.i686 > from build requires libavcodec.so.60, but none of the providers can > be installed > DEBUG util.py:442: - package libchromaprint-1.5.1-11.fc39.i686 > from build requires libavcodec.so.60(LIBAVCODEC_60), but none of the > providers can be installed > DEBUG util.py:442: - conflicting requests > DEBUG util.py:442: - nothing provides libcodec2.so.1.0 needed by > libavcodec-free-6.0-10.fc39.i686 from build > > I'm guessing I don't have a choice but to do a bootstrap build of > libchromaprint without ffmpeg first... no, see my fork https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/commits/rawhide and specially commit https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/c/0e39e40877b404970ab024c579283e50851db20c?branch=rawhide btw that made me remember the bootstrap macro in /usr/lib/rpm/macros.d/macros.dist doesn't make src.rpm correctly in my opinion , but that is another subject > Thanks, > Richard > > [1] > https://src.fedoraproject.org/rpms/chromaprint/blob/rawhide/f/chromaprint.spec > [2] https://koji.fedoraproject.org/koji/rpminfo?rpmID=35116382 > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
mass rebuild for opencv 4.8.0 with soname bump on rawhide
Hi, I will start a mass rebuild in a side-tag, very soon , the goal is finish and merge it before the mass branch which is scheduled for 08 Aug 2023 Best regards, -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: zlib-ng as a compat replacement for zlib
On 8/6/23 02:00, Peter Robinson wrote: We tried to pull some of the optimisations in some time ago to the Fedora package and they caused some issues with compatibility. Please provide *any* documentation! Such as: the dates the work was performed, the participants, the nature of the issues, the "other side" of the problem cases (the other packages, the use cases, etc.) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Problem with ffmpeg and chromaprint circular dependency
>From what I can tell in the spec file[1] for chromaprint, the only thing that's supposed to depend on ffmpeg is the tools package, but it seems to have found its way into libchromaprint[2] as well. I'm trying to build a new version of codec2 with a soname change but I'm hitting this: DEBUG util.py:442: Problem: package libchromaprint-devel-1.5.1-11.fc39.i686 from build requires libchromaprint.so.1, but none of the providers can be installed DEBUG util.py:442:- package libchromaprint-devel-1.5.1-11.fc39.i686 from build requires libchromaprint(x86-32) = 1.5.1-11.fc39, but none of the providers can be installed DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from build requires libavcodec.so.60, but none of the providers can be installed DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from build requires libavcodec.so.60(LIBAVCODEC_60), but none of the providers can be installed DEBUG util.py:442:- conflicting requests DEBUG util.py:442:- nothing provides libcodec2.so.1.0 needed by libavcodec-free-6.0-10.fc39.i686 from build I'm guessing I don't have a choice but to do a bootstrap build of libchromaprint without ffmpeg first... Thanks, Richard [1] https://src.fedoraproject.org/rpms/chromaprint/blob/rawhide/f/chromaprint.spec [2] https://koji.fedoraproject.org/koji/rpminfo?rpmID=35116382 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2229486] New: perl-Apache-Reload-0.14 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2229486 Bug ID: 2229486 Summary: perl-Apache-Reload-0.14 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Apache-Reload Keywords: FutureFeature, Triaged Assignee: mspa...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mspa...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 0.14 Upstream release that is considered latest: 0.14 Current version/release in rawhide: 0.13-24.fc39 URL: http://search.cpan.org/dist/Apache-Reload/ 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_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/14026/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Apache-Reload -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2229486 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202229486%23c0 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230806.n.0 changes
OLD: Fedora-Rawhide-20230805.n.0 NEW: Fedora-Rawhide-20230806.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 3 Dropped packages:26 Upgraded packages: 81 Downgraded packages: 0 Size of added packages: 333.20 KiB Size of dropped packages:51.73 MiB Size of upgraded packages: 373.40 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -592.20 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230806.n.0.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: golang-github-sigurn-crc16-0-0.1.20230703git20ab5af.fc39 Summary: Go CRC16 package RPMs:golang-github-sigurn-crc16-devel Size:12.92 KiB Package: rust-axum-0.6.18-1.fc39 Summary: Web framework that focuses on ergonomics and modularity RPMs:rust-axum+default-devel rust-axum+form-devel rust-axum+headers-devel rust-axum+http1-devel rust-axum+http2-devel rust-axum+json-devel rust-axum+macros-devel rust-axum+matched-path-devel rust-axum+multipart-devel rust-axum+original-uri-devel rust-axum+query-devel rust-axum+tokio-devel rust-axum+tower-http-devel rust-axum+tower-log-devel rust-axum+tracing-devel rust-axum+ws-devel rust-axum-devel Size:264.61 KiB Package: rust-prometheus-client-0.19.0-1.fc39 Summary: Open Metrics client library allowing users to natively instrument applications RPMs:rust-prometheus-client+default-devel rust-prometheus-client-devel Size:55.67 KiB = DROPPED PACKAGES = Package: axc-0.3.7-2.20220526git8e14a66.fc39 Summary: Client library for libsignal-protocol-c RPMs:axc axc-devel Size:286.88 KiB Package: bctoolbox-5.2.45-2.fc39 Summary: Utility library for software from Belledonne Communications and others RPMs:bctoolbox bctoolbox-devel bctoolbox-tester Size:1.44 MiB Package: bcunit-5.2.0-3.fc39 Summary: Provide C programmers basic testing functionality RPMs:bcunit bcunit-devel Size:700.33 KiB Package: belcard-5.2.45-2.fc39 Summary: C++ library to manipulate vCard standard format files RPMs:belcard belcard-data belcard-devel belcard-tools Size:1.06 MiB Package: belr-5.2.45-2.fc39 Summary: Language recognition library RPMs:belr belr-devel belr-tools Size:1003.58 KiB Package: gfbgraph-0.2.5-4.fc39 Summary: GLib/GObject wrapper for the Facebook Graph API RPMs:gfbgraph gfbgraph-devel Size:447.29 KiB Package: git-subrepo-0.4.6-2.fc39 Summary: Git Submodule Alternative RPMs:git-subrepo Size:50.45 KiB Package: libeXosip2-5.3.0-3.fc39 Summary: A library that hides the complexity of using the SIP protocol RPMs:libeXosip2 libeXosip2-devel Size:2.08 MiB Package: libosip2-5.3.1-2.fc39 Summary: oSIP is an implementation of SIP RPMs:libosip2 libosip2-devel Size:885.64 KiB Package: linphone-3.6.1-50.fc38 Summary: Phone anywhere in the whole world by using the Internet RPMs:linphone linphone-devel linphone-mediastreamer linphone-mediastreamer-devel Size:34.51 MiB Package: maddy-1.1.2-7.fc39 Summary: C++ Markdown to HTML header-only parser library RPMs:maddy-devel Size:134.63 KiB Package: mingw-freexl-1.0.6-8.fc39 Summary: MinGW Windows freexl library RPMs:mingw32-freexl mingw64-freexl Size:114.57 KiB Package: mod_limitipconn-0.23-32.fc39 Summary: Simultaneous connection limiting module for Apache RPMs:mod_limitipconn Size:80.10 KiB Package: mod_qos-11.70-4.fc39 Summary: Quality of service module for Apache RPMs:mod_qos Size:4.79 MiB Package: mod_ruid2-0.9.8-20.fc39 Summary: A suexec module for Apache RPMs:mod_ruid2 Size:105.31 KiB Package: mod_security3-0.0.9-0.20210819git0488c77.1.fc39.4 Summary: ModSecurity v3 Apache Connector RPMs:mod_security3 Size:101.59 KiB Package: pidgin-groupchat-typing-notifications-3-11.fc39 Summary: Adds typing notifications for group chats in Pidgin RPMs:pidgin-groupchat-typing-notifications Size:115.09 KiB Package: pidgin-toobars-1.14-19.fc38 Summary: Toolbar and status bar for Pidgin RPMs:pidgin-toobars Size:287.70 KiB Package: purple-discord-0-37.20210928gitb7ac723.fc39 Summary: Discord plugin for libpurple RPMs:pidgin-discord purple-discord Size:457.80 KiB Package: purple-googlechat-0-3.20221106gitb6b824a.fc39 Summary: Google Chat plugin for libpurple RPMs:pidgin-googlechat purple-googlechat Size:702.52 KiB Package: purple-libsteam-1.7.1-5.fc39 Summary: Steam plugin for Pidgin/Adium/libpurple RPMs:pidgin-libsteam purple-libsteam Size:220.41 KiB Package: purple-lurch-0.7.0-2.fc39 Summary: OMEMO Encryption plugin for libpurple RPMs:purple-lurch Size:202.01 KiB Package: purple-matrix-0.1.0-5.fc39 Summary: Matrix plugin for libpurple RPMs:pidgin-matrix purple-matrix Size:252.06 KiB Package: purple-plugin_pack-2.8.0-7.fc39 Summary: A set of plugins for libpurple, pidgin
Re: SPDX Statistics - Flock edition
Dne 06. 08. 23 v 10:26 Barry Scott napsal(a):
On 05/08/2023 08:07, Miroslav Suchý wrote:
Tip of the day:
Do you want to validate your License string? Use: license-validate
"$YOUR_LICENSE_STRING"
I dnf installed license-validate on F38
Then run it to check a license and it does this:
$ /usr/bin/license-validate BSD
No terminal defined for 'B' at line 1 col 1
BSD
^
This is the old string. In legacy system.
$ license-validate--old-vBSD
Approved license
$ license-fedora2spdx'BSD'
Warning: more options on how to interpret BSD. Possible options: ['BSD-3-Clause', 'BSD-3-Clause-Modification',
'BSD-2-Clause', 'BSD-2-Clause-Views', 'BSD-2-Clause-FreeBSD', 'BSD-1-Clause']
{{pick BSD choice}}
You have to dig in and actually find which of these licenses it is. Let say you
find that it is BSD-3-Clause.
$ license-validate-vBSD-3-Clause
Approved license
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: SPDX Statistics - Flock edition
On 05/08/2023 08:07, Miroslav Suchý wrote:
Tip of the day:
Do you want to validate your License string? Use: license-validate
"$YOUR_LICENSE_STRING"
I dnf installed license-validate on F38
Then run it to check a license and it does this:
$ /usr/bin/license-validate BSD
No terminal defined for 'B' at line 1 col 1
BSD
^
Expecting: {'__ANON_79', 'SWL', '__ANON_91', '__ANON_128', 'TTWL',
'__ANON_8', '__ANON_253', 'LATEX2E', '__ANON_104', '__ANON_223', '
What am I doing wrong?
Barry
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: zlib-ng as a compat replacement for zlib
On Sun, Aug 06, 2023 at 04:34:46AM -, Daniel Alley wrote: > >In my test zlib-ng is about 40% faster. > > I did some testing with zlib-ng and createrepo-c a few months ago > [0], and I also found that the compression portion of the workload > was about 40% faster. So this matches my experience, too. > > (BTW, if that github comment [0] sounds negative, it isn't meant to, > it's just that zlib ended up not being the primary culprit of the > performance issue I was investigating at the time, so I was not as > immediately interested in replacing it.) > > I support this proposal. A tricky detail is that one of the big > upsides of zlib-ng is that it has a lot of optimized codepaths for > ARM, POWER, Z, RISC-V, AVX-256, AVX-512 and so forth which > madler/zlib does not have. And that's fantastic, but I expect it > could make the testing process a bit more painful. There are indeed quite a lot. For example this is just x86: https://github.com/zlib-ng/zlib-ng/tree/develop/arch/x86 > Since each of the arch-specific acceleration codepaths is behind a > separate build flag [1] though, (I assume) we could easily do a more > conservative rollout with most arch-specific optimizations disabled > at first, and then enabled gradually over time. & the other thing it is important to note is that it does seem to do CPUID detection at runtime, so we are able to ship a "runs anywhere" binary. See: https://github.com/zlib-ng/zlib-ng/blob/develop/arch/x86/x86_features.c Rich. > [0] > https://github.com/rpm-software-management/createrepo_c/pull/335#issuecomment-1381362220 > [1] https://github.com/zlib-ng/zlib-ng#advanced-build-options > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: zlib-ng as a compat replacement for zlib
On Sun, Aug 6, 2023 at 5:35 AM Daniel Alley wrote: > > >In my test zlib-ng is about 40% faster. > > I did some testing with zlib-ng and createrepo-c a few months ago [0], and I > also found that the compression portion of the workload was about 40% faster. > So this matches my experience, too. > > (BTW, if that github comment [0] sounds negative, it isn't meant to, it's > just that zlib ended up not being the primary culprit of the performance > issue I was investigating at the time, so I was not as immediately interested > in replacing it.) > > I support this proposal. A tricky detail is that one of the big upsides of > zlib-ng is that it has a lot of optimized codepaths for ARM, POWER, Z, > RISC-V, AVX-256, AVX-512 and so forth which madler/zlib does not have. And > that's fantastic, but I expect it could make the testing process a bit more > painful. We tried to pull some of the optimisations in some time ago to the Fedora package and they caused some issues with compatibility. > Since each of the arch-specific acceleration codepaths is behind a separate > build flag [1] though, (I assume) we could easily do a more conservative > rollout with most arch-specific optimizations disabled at first, and then > enabled gradually over time. > > [0] > https://github.com/rpm-software-management/createrepo_c/pull/335#issuecomment-1381362220 > [1] https://github.com/zlib-ng/zlib-ng#advanced-build-options > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
