Fedora 36 compose report: 20220226.n.0 changes
by Fedora Rawhide Report
OLD: Fedora-36-20220225.n.0
NEW: Fedora-36-20220226.n.0
===== SUMMARY =====
Added images: 0
Dropped images: 2
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 0 B
Size of downgraded packages: 0 B
Size change of upgraded packages: 0 B
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
===== DROPPED IMAGES =====
Image: Silverblue dvd-ostree aarch64
Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-36-20220225.n.0.iso
Image: KDE raw-xz aarch64
Path: Spins/aarch64/images/Fedora-KDE-36-20220225.n.0.aarch64.raw.xz
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
2 years, 2 months
Rust Stack Spring Cleaning (February 2022 Edition)
by Fabio Valentini
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
2 years, 2 months
[Test-Announce] 2022-02-28 @ 17:00 UTC - Fedora 36 Blocker Review Meeting
by Adam Williamson
# F36 Blocker Review meeting
# Date: 2022-02-28
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 3 proposed Beta blockers, 4 proposed Beta freeze
exception issues, and 5 proposed Final blockers to review, so let's
have a review meeting on Monday.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F36 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
_______________________________________________
test-announce mailing list -- test-announce(a)lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave(a)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-announce@lists.fedorap...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
2 years, 2 months
Devtoolset for epel7 for build in Copr
by Dmitry Butskoy
Is it possible to use RHEL7 devtoolsets (aka devtoolset-8,
llvm-toolset-11 and so on) for the correspond builds in Copr, as well as
it is possible for builds for Fedora EPEL7 ?
~buc
2 years, 2 months
Rpm: provide a static library in package
by Denis Fateyev
Hello all,
The "ustl" upstream, for which I maintain the RPM package, has recently
switched from providing a shared library to a static library.
So I'm going to make changes in the package, and provide everything in
"-devel" subpackage.
I have looked through
https://docs.fedoraproject.org/en-US/packaging-guidelines/#packaging-stat...
requirements — but there are some questions left.
1) Should I preserve debug information for the static library during build,
so the library can be stripped and debug packages can be created? Or, can I
just skip debug package creation with "%global debug_package %{nil}" ?
I know it's acceptable for header-only, but not sure for packages with
binary static libraries.
2) Can I use the stripping LDFLAGS option ("-s") right during the static
package build, not to strip anything after build? Or, let the built library
be stripped in terms of RPM package flow?
Thanks!
--
wbr, Denis.
2 years, 2 months
unpaper license change
by Petr Pisar
I was able to rebase unpaper to version 6.1^20220117.gite515408 in Fedora 37
thanks to ffmpeg we now have in a distribution. This new version changed
a license from GPL+ to GPLv2.
-- Petr
2 years, 2 months