Rust February 2022

rust@lists.fedoraproject.org

5 participants
4 discussions

How to auto-generate license information for a spec file
by the Mulhern 26 Feb '22

26 Feb '22

Hi! cargo has the "cargo-license" command that will find all licenses for a project's dependencies. Is there something similar to use when packaging for Fedora? Such a tool would find fewer dependencies and possibly fewer licenses, since "cargo license" picks up, e.g., winapi dependencies, which are irrelevant to Fedora. Thanks for any help you can give me, - mulhern -- The question with me is not whether you have a right to render your people miserable, but whether it is not your interest to make them happy. It is not what a lawyer tells me what I may do, but what humanity, reason and justice tell me I ought to to do. Is a politic act the worse for being a generous one? Is no concession proper but that which is made from your want of right to keep what you grant? - Edmund Burke, "Conciliation with America", 1775

3 2

Rust Stack Spring Cleaning (February 2022 Edition)
by Fabio Valentini 26 Feb '22

26 Feb '22

Hello Rust packagers, Following up on my previous emails, there are still a lot of Rust packages that were imported to Fedora, but the recommended "initial setup" for them was never finished. I have started by adding them all "rust-*" packages to koschei, which makes it way easier for me to see at a glance whether there are any broken packages in our Rust stack at any point in time. There is also the question about whether anitya release-monitoring.org is actually set up for those packages, but I don't have an easy way to make scripted checks for this yet. If you add new Rust packages to Fedora, please make sure to set up release-monitoring with these settings: project: $crate homepage: https://crates.io/crates/$crate backend: crates.io version scheme: semantic version filter: alpha;beta;rc;pre distro: Fedora Package: rust-$crate In addition, I would ask of all of you to make sure all your packages have been added to the @rust-sig group on src.fedoraproject.org (at least with "commit" access), unless there is a very good reason not to do so (and if that is the case for a particular package on this list, I'd be interested in knowing the reason). Without that, it makes it very hard for us to keep the Rust stack up-to-date and in working order, because the "rust-sig" list / bugzilla account does not get CC'd on new bugs that way, and your bugs do not show up in our BugZilla queries. If you want a scripted way of adding "@rust-sig" group to many packages, you can generate an API token on src.fedoraproject.org (with "Modify an existing project") access level, and use the simple Python script from this GitHub gist: https://gist.github.com/decathorpe/9d128982cb00e2d345d9e397372538ec Below is the list of "incompletely set-up" packages, in alphabetic order, and at the bottom, is a list per package maintainer. Thanks, Fabio / decathorpe ================================================================================ Maintainers per package: - rust-arrayvec0.5: eclipseo - rust-assert-impl: dcavalca - rust-atomic-traits: salimma - rust-aws-nitro-enclaves-cose: pbrobinson - rust-benfred-read-process-memory: dcavalca - rust-blsctl: javierm - rust-btrd: dcavalca - rust-clap_generate: eclipseo - rust-clap_generate_fig: eclipseo - rust-clircle: eclipseo - rust-conhash: dcavalca - rust-coolor: dcavalca - rust-cryptoki: pbrobinson - rust-cryptoki-sys: pbrobinson - rust-cty: nickblack - rust-custom_error: dcavalca - rust-dbus-codegen: pbrobinson - rust-dbus-crossroads: pbrobinson - rust-derivative: pbrobinson - rust-directories-next: jbtrystram - rust-drg: jbtrystram - rust-elf: dcavalca - rust-env_proxy: dcavalca - rust-event-listener: dcavalca - rust-fatfs: dcavalca - rust-fontdue: remilauzier - rust-fscommon: dcavalca - rust-helvum: salimma - rust-inferno: dcavalca - rust-is_debug: atim - rust-josekit: pbrobinson - rust-js-sys: pbrobinson - rust-keccak: pbrobinson - rust-libseccomp-sys: slp - rust-libspa: salimma - rust-libspa-sys: salimma - rust-madvr_parse: dcavalca - rust-navi: jbtrystram - rust-netlink-packet-core: cathay4t, ffmancera - rust-num-format: dcavalca - rust-oauth2: ctron, jbtrystram - rust-oid: pbrobinson - rust-os-release: dcavalca - rust-parsec-client: pbrobinson - rust-parsec-interface: pbrobinson - rust-phf0.8: ignatenkobrain - rust-phf_generator0.8: ignatenkobrain - rust-phf_macros0.8: ignatenkobrain - rust-phf_shared0.8: ignatenkobrain - rust-picky-asn1: pbrobinson - rust-picky-asn1-der: pbrobinson - rust-picky-asn1-x509: pbrobinson - rust-pipewire: salimma - rust-pipewire-sys: salimma - rust-pkcs11: pbrobinson - rust-proc-maps: dcavalca - rust-process_control: atim, petersen - rust-prost: pbrobinson - rust-prost-build: pbrobinson - rust-prost-derive: pbrobinson - rust-prost-types: pbrobinson - rust-psa-crypto: pbrobinson - rust-psa-crypto-sys: pbrobinson - rust-qstring: ctron, jbtrystram - rust-rbspy: dcavalca - rust-rbspy-ruby-structs: dcavalca - rust-rbspy-testdata: dcavalca - rust-read-process-memory: dcavalca - rust-remoteprocess: dcavalca - rust-rsa: pbrobinson - rust-sd-notify: pbrobinson - rust-secrecy: pbrobinson - rust-serde_with: pbrobinson - rust-sha3: pbrobinson - rust-shadow-rs: atim - rust-shellwords: jbtrystram - rust-signal: salimma - rust-signal-hook-mio: dcavalca - rust-simple_asn1: pbrobinson - rust-starship-battery: atim - rust-str_stack: dcavalca - rust-strict: dcavalca - rust-subprocess: dcavalca - rust-tabular: jbtrystram - rust-thread-tree: dcavalca - rust-tss-esapi-sys: pbrobinson - rust-umask: dcavalca - rust-universal-hash: pbrobinson - rust-version: pbrobinson - rust-versions: atim - rust-webbrowser: ctron, jbtrystram Packages per maintainer: atim (5): rust-is_debug, rust-process_control, rust-shadow-rs, rust-starship-battery, rust-versions cathay4t (1): rust-netlink-packet-core ctron (3): rust-oauth2, rust-qstring, rust-webbrowser dcavalca (27): rust-assert-impl, rust-benfred-read-process-memory, rust-btrd, rust-conhash, rust-coolor, rust-custom_error, rust-elf, rust-env_proxy, rust-event-listener, rust-fatfs, rust-fscommon, rust-inferno, rust-madvr_parse, rust-num-format, rust-os-release, rust-proc-maps, rust-rbspy, rust-rbspy-ruby-structs, rust-rbspy-testdata, rust-read-process-memory, rust-remoteprocess, rust-signal-hook-mio, rust-str_stack, rust-strict, rust-subprocess, rust-thread-tree, rust-umask eclipseo (4): rust-arrayvec0.5, rust-clap_generate, rust-clap_generate_fig, rust-clircle ffmancera (1): rust-netlink-packet-core ignatenkobrain (4): rust-phf0.8, rust-phf_generator0.8, rust-phf_macros0.8, rust-phf_shared0.8 javierm (1): rust-blsctl jbtrystram (8): rust-directories-next, rust-drg, rust-navi, rust-oauth2, rust-qstring, rust-shellwords, rust-tabular, rust-webbrowser nickblack (1): rust-cty pbrobinson (31): rust-aws-nitro-enclaves-cose, rust-cryptoki, rust-cryptoki-sys, rust-dbus-codegen, rust-dbus-crossroads, rust-derivative, rust-josekit, rust-js-sys, rust-keccak, rust-oid, rust-parsec-client, rust-parsec-interface, rust-picky-asn1, rust-picky-asn1-der, rust-picky-asn1-x509, rust-pkcs11, rust-prost, rust-prost-build, rust-prost-derive, rust-prost-types, rust-psa-crypto, rust-psa-crypto-sys, rust-rsa, rust-sd-notify, rust-secrecy, rust-serde_with, rust-sha3, rust-simple_asn1, rust-tss-esapi-sys, rust-universal-hash, rust-version petersen (1): rust-process_control remilauzier (1): rust-fontdue salimma (7): rust-atomic-traits, rust-helvum, rust-libspa, rust-libspa-sys, rust-pipewire, rust-pipewire-sys, rust-signal slp (1): rust-libseccomp-sys

1 0

PSA: GTK-RS 0.15 update coming to F36+
by Fabio Valentini 20 Feb '22

20 Feb '22

Hello Rust packagers, I have prepared an update of the entire GTK-RS stack to the latest version: https://copr.fedorainfracloud.org/coprs/decathorpe/gtk-rs-0.15/monitor/ I am planning to update these packages in Fedora Rawhide and 36, just like GTK-RS 0.14 was only pushed to Fedora 35 and Rawhide half a year ago. The gstreamer-rs 0.18 updates are blocked by one missing package, I would appreciate it if somebody could review it: https://bugzilla.redhat.com/show_bug.cgi?id=2053892 The applications using gtk-rs in Fedora are: - helvum (latest version is using gtk-rs 0.15) - image-roll (unclear if upstream is working on a port to 0.15) - newsflash (latest git is using gtk-rs 0.15) - squeekboard (unclear, uses non-standard build system) - system76-keyboard-configurator (latest git is using gtk-rs 0.15) If you maintain one of these applications, please test building against the updates I have prepared in COPR. There are also some gtk-rs modules that are going to be retired: - rust-soup-sys (dead upstream, was only kept alive downstream by me for F35) - rust-webkit2gtk, rust-webkit2gtk-sys (dead upstream, dependencies not ported to gtk-rs 0.15 yet) - rust-msgbox (unused in Fedora, still uses very old gtk-rs versions) - rust-ostree, rust-ostree-sys (unused in Fedora, not ported to gtk-rs 0.15 yet) The removal of these 6 packages will only affect newsflash, but it has already stopped using these crates in its development branch. I plan to retire them once the other ~60 package updates have been built and pushed successfully. I plan to start submitting builds into side tags next week, probably starting Feb. 18 or 19, so that all builds can be finished and the side-tag-update pushed to stable in time before the beta freeze for F36 goes into effect on Feb. 22. It would be great if maintainers of dependent applications could have updates for their packages ready by that point, so I can include them in the updates. Fabio

2 3

Packaging help
by Jim Campbell 01 Feb '22

01 Feb '22

Hello Fedora Rust people, I am interested in packaging Rust applications in Fedora. I think it would be good for me to start by updating packages that are already present in the repos rather than bringing in new applications. Where would be a good place for me to start, and are there restrictions around updating packages in already-released Fedora versions? Thanks, and I'll look forward to working with you, Jim

2 2

2024

2023

2022

2021

2020

2019

2018

2017

Rust February 2022