Re: Help with creating first PR for a package
Il 18/02/24 02:52, Loren M. Lang ha scritto: > After looking through the orphaned packages, I found one that looks like > a good candidate for me to help with, python-cachelib, as this package > is not that large and I am well-versed in Python. > > I've cloned it down and worked on bringing it more up-to-date. Now that > I have something passing the test suite, I thought I'd file a PR and > start a discussion. I forked the project on Pagure.io, but found that > even with my own personal fork, I don't seem to have commit access to it > without being in the Packagers group. Is that standard? I thought the > point of the fork was to allow non-packagers to use the PR mechanism as > an easy mechanism for sponsors to view proposals. > If I remember correctly previous replies about this issue, you need to use the https URL to push to your fork, ssh access only works for packagers. Mattia -- ___ 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 2181971] perl-Glib-Object-Introspection-0.050 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181971 --- Comment #27 from Sergio Basto --- FYI, perl-Glib-Object-Introspection-0.051 is going to rawhide and f40 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181971 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202181971%23c27 -- ___ 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
Re: Question about error: inlining failed in call to ‘always_inline’
On Sat, Feb 17, 2024 at 6:32 PM Orion Poplawski wrote:
> simdjson is failing to build with GCC 14 on x86_64:
>
> /usr/bin/cmake -S/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4
> -B/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
> --check-build-system CMakeFiles/Makefile.cmake 0
> /usr/bin/cmake -E cmake_progress_start
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu/CMakeFiles
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu//CMakeFiles/progress.marks
> make -f CMakeFiles/Makefile2 all
> make[1]: Entering directory
> '/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
> make -f CMakeFiles/simdjson.dir/build.make CMakeFiles/simdjson.dir/depend
> make[2]: Entering directory
> '/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
> cd /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
> && /usr/bin/cmake -E cmake_depends "Unix Makefiles"
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu/CMakeFiles/simdjson.dir/DependInfo.cmake
> "--color="
> make[2]: Leaving directory
> '/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
> make -f CMakeFiles/simdjson.dir/build.make CMakeFiles/simdjson.dir/build
> make[2]: Entering directory
> '/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
> [ 50%] Building CXX object CMakeFiles/simdjson.dir/src/simdjson.cpp.o
> /usr/bin/g++ -DSIMDJSON_AVX512_ALLOWED=1 -DSIMDJSON_THREADS_ENABLED=1
> -DSIMDJSON_UTF8VALIDATION=1 -Dsimdjson_EXPORTS
> -I/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/include
> -I/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
> -O2 -g -grecord-gcc-switches -pipe
> -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fno-omit-frame-pointer
> -mno-omit-leaf-frame-pointer -fdata-sections -ffunction-sections
> -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
> -flto=auto -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3
> -Wp,-D_GLIBCXX_ASSERTIONS -Wall -Werror=format-security -DNDEBUG
> -std=c++17 -fPIC -mno-avx256-split-unaligned-load
> -mno-avx256-split-unaligned-store -MD -MT
> CMakeFiles/simdjson.dir/src/simdjson.cpp.o -MF
> CMakeFiles/simdjson.dir/src/simdjson.cpp.o.d -o
> CMakeFiles/simdjson.dir/src/simdjson.cpp.o -c
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/simdjson.cpp
> In file included from
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/fallback.cpp:15,
> from
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/simdjson.cpp:27:
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/json_iterator.h:
> In function ‘simdjson::fallback::(anonymous
> namespace)::stage2::tape_builder::parse_document(simdjson::fallback::dom_parser_implementation&,
> simdjson::dom::document&)simdjson::error_code’:
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/json_iterator.h:119:49:
> error: inlining failed in call to ‘always_inline’
> ‘simdjson::fallback::(anonymous
> namespace)::stage2::json_iterator::walk_document simdjson::fallback::(anonymous
> namespace)::stage2::tape_builder>(simdjson::fallback::(anonymous
> namespace)::stage2::tape_builder&)simdjson::error_code’: target specific
> option mismatch
>119 | simdjson_warn_unused simdjson_inline error_code
> json_iterator::walk_document(V ) noexcept {
>| ^
> In file included from
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/fallback.cpp:17:
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/tape_builder.h:105:39:
> note: called from here
>105 | return iter.walk_document(builder);
>| ~^
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/json_iterator.h:119:49:
> error: inlining failed in call to ‘always_inline’
> ‘simdjson::fallback::(anonymous
> namespace)::stage2::json_iterator::walk_document simdjson::fallback::(anonymous
> namespace)::stage2::tape_builder>(simdjson::fallback::(anonymous
> namespace)::stage2::tape_builder&)simdjson::error_code’: target specific
> option mismatch
>119 | simdjson_warn_unused simdjson_inline error_code
> json_iterator::walk_document(V ) noexcept {
>| ^
> /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/tape_builder.h:105:39:
> note: called from here
>105 | return iter.walk_document(builder);
>| ~^
> make[2]: *** [CMakeFiles/simdjson.dir/build.make:79:
> CMakeFiles/simdjson.dir/src/simdjson.cpp.o] Error 1
> make[2]:
Fedora rawhide compose report: 20240217.n.2 changes
OLD: Fedora-Rawhide-20240216.n.0 NEW: Fedora-Rawhide-20240217.n.2 = SUMMARY = Added images:0 Dropped images: 4 Added packages: 18 Dropped packages:4 Upgraded packages: 237 Downgraded packages: 0 Size of added packages: 130.83 MiB Size of dropped packages:20.41 MiB Size of upgraded packages: 6.79 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -5.94 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Budgie live x86_64 Path: Spins/x86_64/iso/Fedora-Budgie-Live-x86_64-Rawhide-20240216.n.0.iso Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20240216.n.0.iso Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20240216.n.0.iso Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20240216.n.0.iso = ADDED PACKAGES = Package: config-kernel-0.3-1.fc41 Summary: An easy way to edit kernel configuration files and templates RPMs:config-kernel Size:275.75 KiB Package: golang-github-apparentlymart-textseg-15-15.0.0-1.fc41 Summary: Go implementation of Unicode Text Segmentation RPMs:golang-github-apparentlymart-textseg-15-devel Size:63.62 KiB Package: golang-github-tidwall-sjson-1.2.5-1.fc41 Summary: Set JSON values very quickly in Go RPMs:golang-github-tidwall-sjson-devel Size:18.23 KiB Package: helvum-0.5.1-1.fc41 Summary: GTK patchbay for pipewire RPMs:helvum Size:1.81 MiB Package: mingw-qt6-qtscxml-6.6.1-1.fc41 Summary: Qt6 for Windows - QtScxml component RPMs:mingw32-qt6-qtscxml mingw64-qt6-qtscxml Size:1.02 MiB Package: miopen-6.0.2-1.fc41 Summary: AMD's Machine Intelligence Library RPMs:miopen miopen-devel Size:92.03 MiB Package: pkcs11test-0~20230418git2cbe462-2.fc41 Summary: PKCS#11 Test Suite RPMs:pkcs11test Size:1.05 MiB Package: python-google-cloud-monitoring-2.19.1-1.fc41 Summary: Google Cloud Monitoring API client library RPMs:python3-google-cloud-monitoring Size:297.98 KiB Package: python-pyasn-1.6.1-1.fc41 Summary: Offline IP address to Autonomous System Number lookup module RPMs:python3-pyasn Size:256.20 KiB Package: rocm-core-6.0.0-1.fc41 Summary: A utility to get the ROCm release version RPMs:rocm-core rocm-core-devel Size:20.02 KiB Package: rust-app_dirs2-2.5.5-1.fc41 Summary: Put your app's data in the right place on every platform RPMs:rust-app_dirs2+default-devel rust-app_dirs2-devel Size:26.58 KiB Package: rust-lsp-server-0.7.5-1.fc41 Summary: Generic LSP server scaffold RPMs:rust-lsp-server+default-devel rust-lsp-server-devel Size:28.95 KiB Package: rust-nu-0.88.1-2.fc41 Summary: New type of shell RPMs:nu Size:31.22 MiB Package: rust-nu-cli-0.88.1-2.fc41 Summary: CLI-related functionality for Nushell RPMs:rust-nu-cli+default-devel rust-nu-cli+plugin-devel rust-nu-cli-devel Size:87.68 KiB Package: rust-nu-lsp-0.88.1-1.fc41 Summary: Nushell's integrated LSP server RPMs:rust-nu-lsp+default-devel rust-nu-lsp-devel Size:24.73 KiB Package: rust-num-conv-0.1.0-1.fc41 Summary: Num_conv is a crate to convert between integer types without using as casts RPMs:rust-num-conv+default-devel rust-num-conv-devel Size:22.30 KiB Package: rust-oxipng-9.0.0-1.fc41 Summary: Lossless PNG compression optimizer RPMs:oxipng rust-oxipng+binary-devel rust-oxipng+clap-devel rust-oxipng+crossbeam-channel-devel rust-oxipng+default-devel rust-oxipng+env_logger-devel rust-oxipng+filetime-devel rust-oxipng+freestanding-devel rust-oxipng+image-devel rust-oxipng+parallel-devel rust-oxipng+rayon-devel rust-oxipng+sanity-checks-devel rust-oxipng+zopfli-devel rust-oxipng-devel Size:2.58 MiB Package: rust-sequoia-keystore-backend-0.1.0-1.fc41 Summary: Private key store for Sequoia RPMs:rust-sequoia-keystore-backend+default-devel rust-sequoia-keystore-backend-devel Size:29.29 KiB = DROPPED PACKAGES = Package: bacula-docs-9.6.7-6.fc38 Summary: Bacula documentation RPMs:bacula-docs Size:18.76 MiB Package: php-PHP-CSS-Parser-7.0.3-15.fc39 Summary: A Parser for CSS Files RPMs:php-PHP-CSS-Parser Size:42.45 KiB Package: rust-helvum-0.4.0-3.fc40 Summary: GTK patchbay for pipewire RPMs:helvum Size:1.54 MiB Package: virtme-0.1.1-25.fc40 Summary: Virtualize the running distro or a simple rootfs RPMs:virtme Size:75.67 KiB = UPGRADED PACKAGES = Package: AusweisApp2-2.0.3-3.fc41 Old package: AusweisApp2-2.0.3-2.fc40 Summary: Online identification with German ID card (Personalausweis) RPMs: AusweisApp2 AusweisApp2-data AusweisApp2-doc Size: 24.37 MiB Size change: -2.73 KiB Changelog: * Fri Feb 16 2024 Jan Grulich - 2.0.3-3 - Rebuild (qt6) Package: QXlsx-1.4.7-4.fc41 Old package: QXlsx-1.4.7-3.fc40 Summary
Help with creating first PR for a package
After looking through the orphaned packages, I found one that looks like a good candidate for me to help with, python-cachelib, as this package is not that large and I am well-versed in Python. I've cloned it down and worked on bringing it more up-to-date. Now that I have something passing the test suite, I thought I'd file a PR and start a discussion. I forked the project on Pagure.io, but found that even with my own personal fork, I don't seem to have commit access to it without being in the Packagers group. Is that standard? I thought the point of the fork was to allow non-packagers to use the PR mechanism as an easy mechanism for sponsors to view proposals. In any case, I decided to through it up on GitHub temporarily so I could at least create a Remote PR. https://src.fedoraproject.org/rpms/python-cachelib/pull-request/6 I am considering becoming a [co-]maintainer if needed to help keep this package in good, solid shape, however it does look like it has been adopted by topazus in the last couple of days since I started working on it. I am also working on setting up a Python 3.13 environment to debug the issue reported in bug #2251780. Thanks, -- Loren M. Lang lor...@north-winds.org http://www.north-winds.org/ Public Key: http://www.north-winds.org/lorenl_pubkey.asc Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A 98FA signature.asc Description: PGP signature -- ___ 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
Question about error: inlining failed in call to ‘always_inline’
simdjson is failing to build with GCC 14 on x86_64:
/usr/bin/cmake -S/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4
-B/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu/CMakeFiles
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu//CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory
'/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
make -f CMakeFiles/simdjson.dir/build.make CMakeFiles/simdjson.dir/depend
make[2]: Entering directory
'/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
cd /home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
&& /usr/bin/cmake -E cmake_depends "Unix Makefiles"
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu/CMakeFiles/simdjson.dir/DependInfo.cmake
"--color="
make[2]: Leaving directory
'/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
make -f CMakeFiles/simdjson.dir/build.make CMakeFiles/simdjson.dir/build
make[2]: Entering directory
'/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/x86_64-redhat-linux-gnu'
[ 50%] Building CXX object CMakeFiles/simdjson.dir/src/simdjson.cpp.o
/usr/bin/g++ -DSIMDJSON_AVX512_ALLOWED=1 -DSIMDJSON_THREADS_ENABLED=1
-DSIMDJSON_UTF8VALIDATION=1 -Dsimdjson_EXPORTS
-I/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/include
-I/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-O2 -g -grecord-gcc-switches -pipe
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -fdata-sections -ffunction-sections
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-flto=auto -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3
-Wp,-D_GLIBCXX_ASSERTIONS -Wall -Werror=format-security -DNDEBUG
-std=c++17 -fPIC -mno-avx256-split-unaligned-load
-mno-avx256-split-unaligned-store -MD -MT
CMakeFiles/simdjson.dir/src/simdjson.cpp.o -MF
CMakeFiles/simdjson.dir/src/simdjson.cpp.o.d -o
CMakeFiles/simdjson.dir/src/simdjson.cpp.o -c
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/simdjson.cpp
In file included from
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/fallback.cpp:15,
from
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/simdjson.cpp:27:
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/json_iterator.h:
In function ‘simdjson::fallback::(anonymous
namespace)::stage2::tape_builder::parse_document(simdjson::fallback::dom_parser_implementation&,
simdjson::dom::document&)simdjson::error_code’:
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/json_iterator.h:119:49:
error: inlining failed in call to ‘always_inline’
‘simdjson::fallback::(anonymous
namespace)::stage2::json_iterator::walk_documentsimdjson::fallback::(anonymous
namespace)::stage2::tape_builder>(simdjson::fallback::(anonymous
namespace)::stage2::tape_builder&)simdjson::error_code’: target specific
option mismatch
119 | simdjson_warn_unused simdjson_inline error_code
json_iterator::walk_document(V ) noexcept {
| ^
In file included from
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/fallback.cpp:17:
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/tape_builder.h:105:39:
note: called from here
105 | return iter.walk_document(builder);
| ~^
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/json_iterator.h:119:49:
error: inlining failed in call to ‘always_inline’
‘simdjson::fallback::(anonymous
namespace)::stage2::json_iterator::walk_documentsimdjson::fallback::(anonymous
namespace)::stage2::tape_builder>(simdjson::fallback::(anonymous
namespace)::stage2::tape_builder&)simdjson::error_code’: target specific
option mismatch
119 | simdjson_warn_unused simdjson_inline error_code
json_iterator::walk_document(V ) noexcept {
| ^
/home/tkloczko/rpmbuild/BUILD/simdjson-3.6.4/src/generic/stage2/tape_builder.h:105:39:
note: called from here
105 | return iter.walk_document(builder);
| ~^
make[2]: *** [CMakeFiles/simdjson.dir/build.make:79:
CMakeFiles/simdjson.dir/src/simdjson.cpp.o] Error 1
make[2]: Target 'CMakeFiles/simdjson.dir/build' not remade because of
errors.
I really have no idea how to resolve this.
--
Orion Poplawski
he/him/his - surely the least important
Re: Help needed to fix FTBFS in scikit learn
On Sat, Feb 17, 2024 at 10:03:39PM +0100, Sergio Pascual wrote: > Hello, currently python-scikit-learn fails to build in f40 and rawhide > https://bugzilla.redhat.com/show_bug.cgi?id=2261602 > > The problem is a series of incompatible pointer conversions that > appear in cython generated C code. > The code has classes defined in cython and in the offending code > "self" is passed as a pointer to the base class with a conversion to > the derived class > > sklearn/metrics/_dist_metrics.c: In function > ‘__pyx_f_7sklearn_7metrics_13_dist_metrics_19EuclideanDistance32_dist_csr’: > sklearn/metrics/_dist_metrics.c:51033:90: error: passing argument 1 of > ‘__pyx_f_7sklearn_7metrics_13_dist_metrics_19EuclideanDistance32_rdist_csr’ > from incompatible pointer type [-Wincompatible-pointer-types] > > note: expected ‘struct > __pyx_obj_7sklearn_7metrics_13_dist_metrics_EuclideanDistance32 *’ > but argument is of type ‘struct > __pyx_obj_7sklearn_7metrics_13_dist_metrics_DistanceMetric32 *’ If the conversion is correct and desirable, it needs to be explicit, not implicit. Jakub -- ___ 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
Help needed to fix FTBFS in scikit learn
Hello, currently python-scikit-learn fails to build in f40 and rawhide https://bugzilla.redhat.com/show_bug.cgi?id=2261602 The problem is a series of incompatible pointer conversions that appear in cython generated C code. The code has classes defined in cython and in the offending code "self" is passed as a pointer to the base class with a conversion to the derived class sklearn/metrics/_dist_metrics.c: In function ‘__pyx_f_7sklearn_7metrics_13_dist_metrics_19EuclideanDistance32_dist_csr’: sklearn/metrics/_dist_metrics.c:51033:90: error: passing argument 1 of ‘__pyx_f_7sklearn_7metrics_13_dist_metrics_19EuclideanDistance32_rdist_csr’ from incompatible pointer type [-Wincompatible-pointer-types] note: expected ‘struct __pyx_obj_7sklearn_7metrics_13_dist_metrics_EuclideanDistance32 *’ but argument is of type ‘struct __pyx_obj_7sklearn_7metrics_13_dist_metrics_DistanceMetric32 *’ Regards, Sergio -- ___ 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: Proposing a Fedora SIG for the upcoming COSMIC desktop environment
This is my first time participating in a mailing list as well, but I wanted to show my support for this. Thanks for getting the ball rolling! -- ___ 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: Proposing a Fedora SIG for the upcoming COSMIC desktop environment
Thank you both! I have joined the Rust SIG and have also started the Fedora COSMIC matrix server. https://matrix.to/#/#fedora-cosmic:fedora.im I imagine the Rust SIG and COSMIC SIG will work very closely given how rusty COSMIC is :) - Ryan -- ___ 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: Introduction
Welcome :-) On 17/02/2024 13:38, Loren M. Lang wrote: Hello all, I am looking to get more involved in the Fedora Project and contributing back into it. I have been using Linux since Red Hat Linux 5.1 was released in 1998. Since then, I have been able to provide a variety of contributions back to various projects including Debian, Ubuntu, and even FreeBSD. I tend to work mostly in either C, Python, or Rust but can work in a variety of languages. Over the last few years, Fedora has become one of my main drivers for development and I'd like to give back and help maintain some packages in need of loving. I am looking forward to joining the community and offering my assistance. Sincerely, Loren M. Lang https://github.com/penguin359/ -- ___ 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: Proposing a Fedora SIG for the upcoming COSMIC desktop environment
On Sat, Feb 17, 2024 at 4:15 AM Michel Lind wrote: > > Hello and welcome! > > On Fri, Feb 16, 2024 at 08:59:49PM -, Ryan Brue wrote: > > Hello all! This is my first time using a mailing list, but I want to do > > this more often in the future :) > > > > > > If you happen to like rust, or are simply excited to see another desktop > > environment join the space, share your interest! > > If there is enough interest, I would suggest we then create a matrix group, > > similar to what the Fedora KDE SIG has. I believe the KDE SIG uses an IRC > > bridge as well, for those interested in using IRC. > > Happy to join the Matrix room when it's created! Can't commit to being > that involved, but it seems like there's going to be a lot of overlap on > the packaging side with the Rust SIG I'm already in (Rust crates in > Fedora are all co-maintained by the SIG) so feel free to drop in and ask > questions at #rust:fedoraproject.org I'm looking forward to COSMIC as well. I wanted to wait until there's an actual alpha release with trying to package things, so I hadn't looked to closely at it yet :) Also, I agree with Michel, there is probably going to be a lot of overlap with the Rust SIG, so it would be great to have you in the Rust matrix room to coordinate first steps :) Fabio -- ___ 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: Introduction
On 2/17/24 6:38 AM, Loren M. Lang wrote: Hello all, I am looking to get more involved in the Fedora Project and contributing back into it. I have been using Linux since Red Hat Linux 5.1 was released in 1998. Since then, I have been able to provide a variety of contributions back to various projects including Debian, Ubuntu, and even FreeBSD. I tend to work mostly in either C, Python, or Rust but can work in a variety of languages. Over the last few years, Fedora has become one of my main drivers for development and I'd like to give back and help maintain some packages in need of loving. I am looking forward to joining the community and offering my assistance. Welcome Loren! We are all glad that you are here. :) Joe -- Joe Doss j...@solidadmin.com -- ___ 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: Need help with incompatible pointer types on i686
Michael J Gruber wrote: > numpy definitely needs to fix this. You cannot just go by bitsize and > signedness. You never could and now you can't ;) You actually had to before C99, where stdint.h was introduced. On some platforms or compilers, such as MSVC, you still cannot use C99, only C89/C90. (They support new C++ standards, but not new C standards.) So auto- detecting one's own uint32_t is still the only way there. Of course, what the software SHOULD do is to check for stdint.h and use that if it exists, only defining its own type if it does not. But it is still not a good idea for GCC to make this typically harmless warning an error by default (and I have already complained about that, pointing out exactly this use case, when the Change was discussed; sadly, my objection was dismissed). Kevin Kofler -- ___ 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
Fedora 40 compose report: 20240217.n.0 changes
OLD: Fedora-40-20240216.n.0 NEW: Fedora-40-20240217.n.0 = SUMMARY = Added images:2 Dropped images: 2 Added packages: 8 Dropped packages:4 Upgraded packages: 187 Downgraded packages: 0 Size of added packages: 34.49 MiB Size of dropped packages:20.41 MiB Size of upgraded packages: 3.96 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -16.91 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Sericea dvd-ostree x86_64 Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-40-20240217.n.0.iso Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-40-20240217.n.0.iso = DROPPED IMAGES = Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-40-20240216.n.0.iso Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-40-20240216.n.0.iso = ADDED PACKAGES = Package: golang-github-apparentlymart-textseg-15-15.0.0-1.fc40 Summary: Go implementation of Unicode Text Segmentation RPMs:golang-github-apparentlymart-textseg-15-devel Size:63.62 KiB Package: helvum-0.5.1-1.fc40 Summary: GTK patchbay for pipewire RPMs:helvum Size:1.81 MiB Package: mingw-qt6-qtscxml-6.6.1-1.fc40 Summary: Qt6 for Windows - QtScxml component RPMs:mingw32-qt6-qtscxml mingw64-qt6-qtscxml Size:1.02 MiB Package: python-pyasn-1.6.1-1.fc40 Summary: Offline IP address to Autonomous System Number lookup module RPMs:python3-pyasn Size:256.18 KiB Package: rust-lsp-server-0.7.5-1.fc40 Summary: Generic LSP server scaffold RPMs:rust-lsp-server+default-devel rust-lsp-server-devel Size:28.95 KiB Package: rust-nu-0.88.1-2.fc40 Summary: New type of shell RPMs:nu Size:31.21 MiB Package: rust-nu-cli-0.88.1-1.fc40 Summary: CLI-related functionality for Nushell RPMs:rust-nu-cli+default-devel rust-nu-cli+plugin-devel rust-nu-cli-devel Size:87.45 KiB Package: rust-nu-lsp-0.88.1-1.fc40 Summary: Nushell's integrated LSP server RPMs:rust-nu-lsp+default-devel rust-nu-lsp-devel Size:24.73 KiB = DROPPED PACKAGES = Package: bacula-docs-9.6.7-6.fc38 Summary: Bacula documentation RPMs:bacula-docs Size:18.76 MiB Package: php-PHP-CSS-Parser-7.0.3-15.fc39 Summary: A Parser for CSS Files RPMs:php-PHP-CSS-Parser Size:42.45 KiB Package: rust-helvum-0.4.0-3.fc40 Summary: GTK patchbay for pipewire RPMs:helvum Size:1.54 MiB Package: virtme-0.1.1-25.fc40 Summary: Virtualize the running distro or a simple rootfs RPMs:virtme Size:75.67 KiB = UPGRADED PACKAGES = Package: AusweisApp2-2.0.3-3.fc40 Old package: AusweisApp2-2.0.3-2.fc40 Summary: Online identification with German ID card (Personalausweis) RPMs: AusweisApp2 AusweisApp2-data AusweisApp2-doc Size: 24.37 MiB Size change: -3.01 KiB Changelog: * Fri Feb 16 2024 Jan Grulich - 2.0.3-3 - Rebuild (qt6) Package: QXlsx-1.4.7-4.fc40 Old package: QXlsx-1.4.7-3.fc40 Summary: Excel/XLSX file reader/writer library for Qt RPMs: QXlsx QXlsx-devel Size: 1.74 MiB Size change: -1.93 KiB Changelog: * Fri Feb 16 2024 Jan Grulich - 1.4.7-4 - Rebuild (qt6) Package: akonadi-server-24.01.95-2.fc40 Old package: akonadi-server-24.01.95-1.fc40 Summary: PIM Storage Service RPMs: akonadi-server akonadi-server-devel akonadi-server-doc akonadi-server-mysql Size: 26.83 MiB Size change: -13.20 KiB Changelog: * Fri Feb 16 2024 Jan Grulich - 24.01.95-2 - Rebuild (qt6) Package: anaconda-40.22.1-1.fc40 Old package: anaconda-40.21-2.fc40 Summary: Graphical system installer RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui anaconda-widgets anaconda-widgets-devel Size: 17.94 MiB Size change: -43.15 KiB Changelog: * Thu Feb 15 2024 Packit - 40.22.1-1 - Set up the fedora-40 branch (mkolman) Package: anaconda-webui-6-1.fc40 Old package: anaconda-webui-5.2-1.fc40 Summary: Anaconda installer Web interface RPMs: anaconda-webui Size: 1.31 MiB Size change: 206 B Changelog: * Fri Feb 16 2024 Packit - 6-1 - Tests stabilization Package: angelfish-24.01.95-3.fc40 Old package: angelfish-24.01.95-2.fc40 Summary: Plasma Mobile minimal web browser RPMs: angelfish Size: 2.87 MiB Size change: -15.06 KiB Changelog: * Fri Feb 16 2024 Jan Grulich - 24.01.95-3 - Rebuild (qt6) Package: ascii-3.20-1.fc40 Old package: ascii-3.19-1.fc40 Summary: Interactive ascii name and synonym chart RPMs: ascii Size: 110.04 KiB Size change: 904 B Changelog: * Fri Feb 16 2024 Didier Fabert - 3.20-1 - Update to 3.20 version Package: bind9-next-32:9.19.21-2.fc40 Old package: bind9-next-32:9.19.19-3.fc40 Summary: The Berkeley Internet Name Domain
Introduction
Hello all, I am looking to get more involved in the Fedora Project and contributing back into it. I have been using Linux since Red Hat Linux 5.1 was released in 1998. Since then, I have been able to provide a variety of contributions back to various projects including Debian, Ubuntu, and even FreeBSD. I tend to work mostly in either C, Python, or Rust but can work in a variety of languages. Over the last few years, Fedora has become one of my main drivers for development and I'd like to give back and help maintain some packages in need of loving. I am looking forward to joining the community and offering my assistance. Sincerely, Loren M. Lang https://github.com/penguin359/ -- Sent from my Nexus 4 with K-9 Mail. Please excuse my brevity. -- ___ 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: Restore dmz-cursor-themes
Yes, I'm already a packager for Fedora for my programs and theme. I'm going to submit a review request. Le 16/02/2024 21:49, Jerry James a écrit : Hi Fabrice, On Fri, Feb 16, 2024 at 4:43 AM Fabrice wrote: Hi! I would like to become the maintainer of dmz-cursor-themes. https://src.fedoraproject.org/rpms/dmz-cursor-themes I would like to push an update from Debian, v0.4.5.1. Thank you for your interest in this package. Since it has been retired for more than 8 weeks, it will need to be reviewed as described here: https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming Are you currently a Fedora packager? If not, you will need to follow the procedure described here: https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ Feel free to ask questions or ask for help on this mailing list or on https://discussion.fedoraproject.org/. Regards, -- ___ 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
