January 2024 - devel - Fedora Mailing-Lists

Sequoia PGP : What are the options for expired third party GPG signing keys?

by Antoine Zellmeyer

Following Fedora’s migration to Sequoia PGP, it seems that it isn’t possible to import an expired signing key anymore. rpm --import https://some.domain/public-keys/SOME_EXPIRED_RPM_KEY.public error: Certificate <CERT_ID>: The certificate is expired: The primary key is not live error: https://some.domain/public-keys/SOME_EXPIRED_RPM_KEY.public: key 1 import failed. I’d like to know what a third party can do to allow older versions of a package to be installed despite the expired GPG key. To be precise, the GPG key is expired but not revoked so it shouldn’t be an issue. One option I’m aware of would be to resign older packages but it involves changing the checksum of the package, which is a bad practice we’d like to avoid. Any suggestions ? Or is it an issue to redirect to rpm-sequoia directly ?

4 months, 1 week

2
5
2 / 0

rawhide aarch64 Thunderbird FTBFS "internal compiler error: Segmentation fault"

by Eike Rathke

Hi, Tried twice, same error, aarch64 build bails out with | 34:29.97 *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. | 34:29.97 Event | Plugins | 34:29.97 PLUGIN_FINISH_UNIT | annobin: Generate final annotations | 34:29.97 PLUGIN_START_UNIT | annobin: Generate global annotations | 34:29.97 PLUGIN_ALL_PASSES_START | annobin: Generate per-function annotations | 34:29.97 PLUGIN_ALL_PASSES_END | annobin: Register per-function end symbols | 34:29.97 during RTL pass: split1 | 34:29.97 In file included from /builddir/build/BUILD/thunderbird-115.7.0/gfx/skia/skia/src/core/SkOpts.cpp:43: | 34:29.97 /builddir/build/BUILD/thunderbird-115.7.0/gfx/skia/skia/src/opts/SkBlitMask_opts.h: In function ‘void neon::blit_mask_d32_a8(SkPMColor*, size_t, const SkAlpha*, size_t, SkColor, int, int)’: | 34:29.97 /builddir/build/BUILD/thunderbird-115.7.0/gfx/skia/skia/src/opts/SkBlitMask_opts.h:234:1: internal compiler error: Segmentation fault | 34:29.97 234 | } | 34:29.97 | ^ | 34:30.04 Please submit a full bug report, with preprocessed source (by using -freport-bug). | 34:30.04 See <http://bugzilla.redhat.com/bugzilla> for instructions. I'm not going to jump through hoops there. All other platforms finished the build fine, f39 and f38 builds completed also for aarch64. See https://kojipkgs.fedoraproject.org//work/tasks/9052/112279052/build.log of https://koji.fedoraproject.org/koji/taskinfo?taskID=112279052 of https://koji.fedoraproject.org/koji/taskinfo?taskID=112278913 Eike -- GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A

4 months, 1 week

3
3
0 / 0

Re: List of long term FTBFS packages to be retired in February

by Miro Hrončok

On 24. 01. 24 19:00, Ralf Corsépius wrote: > > > Am 24.01.24 um 17:38 schrieb Miro Hrončok: >> Dear maintainers. >> >> Based on the current fail to build from source policy, the following packages >> should be retired from Fedora 40 approximately one week before branching. >> >> 5 weekly reminders are required, hence the retirement will happen >> approximately in 5 weeks, i.e. around 2024-02-28. >> Since this is unfortunately after the branching, >> packages will be retired on rawhide and f40. >> >> I apologize for starting this process a bit later than required again. >> Unfortunately, I had other work obligations. >> Volunteers to take over this are always welcome. >> >> Policy: >> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... >> >> The packages in rawhide were not successfully built at least since Fedora 37. >> >> This report is based on dist tags. >> >> Packages collected via: >> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ft... >> >> 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 >> ================================================================================ > >> freefem++ (maintained by: cicku, corsepiu) >> freefem++-openmpi-4.14-3.fc40.x86_64 requires >> libmpi.so.40()(64bit)(openmpi-x86_64) > > WTH is this? Your script seems broken. This is a 2-level deep dependency on a package that fails to build. Thanks for your feedback. Occasionally, "my" script is broken, but what you reported is not actually incorrect. See further. > Neither is cicku a maintainer of freefem++ They are listed as such at https://src.fedoraproject.org/rpms/freefem++ > nor did it fail to build. It did not. It depends on openmpi which depends on infinipath-psm which fails to build. > Actually > this package had been built several times in recent months/weeks. Koji lists it > as having been rebuilt today! Correct. > And while we are at it: Why is cicku still listed as a maintainer? I don't know. > He was removed from Fedora by force due to a FESCO decision many years ago. I > don't recall the details, but this can easily be 10 years ago. Then, perhaps the removal was not complete. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

4 months, 1 week

2
1
0 / 0

Cached Package Review Tracker - Tickets that passed automated review

by Jakub Kadlcik

Hello, if you use the Cached Package Review Tracker https://fedoraproject.org/PackageReviewStatus/ there is a new "feature" that you may find useful. Fedora Review Service runs the fedora-review tool on every new Bugzilla ticket. If no errors are found, the ticket is marked with a special keyword. Such tickets are then displayed in the "New tickets that passed CI checks" section of the cached tracker. https://fedoraproject.org/PackageReviewStatus/triaged.html They are also highlighted in the "New Fedora tickets" section https://fedoraproject.org/PackageReviewStatus/reviewable.html (see the color legend) The presumption is - if a ticket passes all fedora-review checks, it is probably in relatively good shape and the package review could be quick and simple. Hopefully, you will find it useful. Jakub

4 months, 1 week

2
1
0 / 0

Modern C i686 failures

by Yaakov Selkowitz

The GCC 14 and Modern C changes have caused a large number of build failures. No surprise there, but in particular though, a lot of these failures have only occurred on i686, e.g. uint64_t (aka long long unsigned int) doesn't match long unsigned int *, etc. A few examples: gnome-keyring: https://koji.fedoraproject.org/koji/taskinfo?taskID=112010040 ldns: https://koji.fedoraproject.org/koji/taskinfo?taskID=112074780 ledmon: https://koji.fedoraproject.org/koji/taskinfo?taskID=112074925 libfabric: https://koji.fedoraproject.org/koji/taskinfo?taskID=112077476 libgphoto2: https://koji.fedoraproject.org/koji/taskinfo?taskID=112078167 Granted, in some cases this can be motivation to retire i686 leaves, but for those that are not leaves, they now need to be fixed for i686 to complete the mass rebuild. Given the increasingly limited usage of i686 in Fedora (not to mention CentOS Stream and RHEL), is it actually worth the effort to "fix" all the code just for 32-bit compatibility? Or perhaps it's better if we focus on issues that pertain to our primary (64-bit) architectures? -- Yaakov Selkowitz Principal Software Engineer - Emerging RHEL Red Hat, Inc.

4 months, 1 week

2
1
0 / 0

Fedora CoreOS Meeting Minutes 2024-01-24

by Dusty Mabe

Text Log: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024... HTML Log: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024... Text Minutes: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024... HTML Minutes: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024... ===================================== # #meeting-1:fedoraproject.org: fedora_coreos_meeting ===================================== Meeting started by @dustymabe:matrix.org at 2024-01-24 16:30:20 Meeting summary --------------- * TOPIC: Action items from last meeting (@dustymabe:matrix.org, 16:34:51) * INFO: there are no action items from the [last meeting](https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject... (@dustymabe:matrix.org, 16:35:35) * TOPIC: Switch to using OSBuild for most CoreOS boot image building (@dustymabe:matrix.org, 16:36:13) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1653 (@dustymabe:matrix.org, 16:36:21) * AGREED: We will roll out disk image building using OSBuild to our `rawhide` mechanical stream first (this is a non-user facing stream). Then we will roll out OSBuild to the `next` stream and let it soak there for some time. We may choose to switch over `testing` before the rebase to F40, but we won't do it until F40 has at least reached `next` at F40 beta time. (@dustymabe:matrix.org, 16:52:30) * TOPIC: fwupd enabled by default in VM builds (@dustymabe:matrix.org, 16:53:43) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1650 (@dustymabe:matrix.org, 16:53:50) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1623 (@dustymabe:matrix.org, 16:54:49) * INFO: we need someone to take a dedicated look at fwupd on Fedora CoreOS to fix any related issues (@dustymabe:matrix.org, 17:03:21) * TOPIC: tracker: Fedora 40 changes considerations (@dustymabe:matrix.org, 17:05:49) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1626 (@dustymabe:matrix.org, 17:05:55) * INFO: 124. Golang 1.22 (@dustymabe:matrix.org, 17:06:31) * LINK: https://fedoraproject.org/wiki/Changes/golang1.22 (@dustymabe:matrix.org, 17:06:39) * ACTION: spresti to investigate if there are actions we need to take to pre-test golang 1.22 before it hits rawhide (@dustymabe:matrix.org, 17:13:00) * INFO: 125. Enable IPv4 Address Conflict Detection by default (@dustymabe:matrix.org, 17:13:44) * LINK: https://fedoraproject.org/wiki/Changes/Enable_IPv4_Address_Conflict_Detec... (@dustymabe:matrix.org, 17:13:51) * ACTION: dustymabe to open an issue for further investigating `Enable IPv4 Address Conflict Detection` (@dustymabe:matrix.org, 17:19:48) * INFO: topic 126. LLVM 18 (@dustymabe:matrix.org, 17:20:12) * LINK: https://fedoraproject.org/wiki/Changes/LLVM-18 (@dustymabe:matrix.org, 17:20:24) * INFO: for LLVM this should not affect us or should be transparent to us (@dustymabe:matrix.org, 17:21:00) * INFO: topic 127. Remove Python Mock Usage (@dustymabe:matrix.org, 17:21:50) * LINK: https://fedoraproject.org/wiki/Changes/RemovePythonMockUsage (@dustymabe:matrix.org, 17:22:00) * INFO: in our CoreOS org we don't really ship any python packages in Fedora so there should be no work for us to do. (@dustymabe:matrix.org, 17:22:50) * INFO: 128. Change Firefox desktop file (@dustymabe:matrix.org, 17:23:07) * LINK: https://fedoraproject.org/wiki/Changes/RenameFirefoxDesktopFile (@dustymabe:matrix.org, 17:23:13) * INFO: Nothing to do. We don't ship Firefox. (@dustymabe:matrix.org, 17:23:26) * INFO: 129. Assign individual, stable MAC addresses for Wi-Fi connections (@dustymabe:matrix.org, 17:23:45) * LINK: https://fedoraproject.org/wiki/Changes/StableSSIDMACAddress (@dustymabe:matrix.org, 17:23:54) * ACTION: jlebon to open an issue for F40 communications (@dustymabe:matrix.org, 17:27:20) * INFO: we don't ship wifi enabled by default in FCOS but we do know people layer it in. We should highlight this change to our users when communicating F40 changes. (@dustymabe:matrix.org, 17:28:12) * TOPIC: open floor (@dustymabe:matrix.org, 17:29:17) * INFO: jlebon filed https://github.com/coreos/fedora-coreos-tracker/issues/1655 (@jlebon:fedora.im, 17:29:51) * ACTION: fifofonix to coordinate with travier a time to collaborate and understand the problems more (@dustymabe:matrix.org, 17:31:27) * ACTION: fifofonix to coordinate with travier a time to collaborate and understand the problems related to fwupd more (@dustymabe:matrix.org, 17:31:36) Meeting ended at 2024-01-24 17:33:53 Action items ------------ * spresti to investigate if there are actions we need to take to pre-test golang 1.22 before it hits rawhide * dustymabe to open an issue for further investigating `Enable IPv4 Address Conflict Detection` * jlebon to open an issue for F40 communications * fifofonix to coordinate with travier a time to collaborate and understand the problems more * fifofonix to coordinate with travier a time to collaborate and understand the problems related to fwupd more People Present (lines said) --------------------------- * @dustymabe:matrix.org (82) * @siosm:matrix.org (28) * @jlebon:fedora.im (14) * @zodbot:fedora.im (6) * @spresti:fedora.im (5) * @jbtrystram:matrix.org (3) * @fifofonix:matrix.org (3) * @ydesouza:fedora.im (2) * @apiaseck:matrix.org (2) * @gurssing:matrix.org (2) * @mnguyen:fedora.im (2) * @jmarrero:matrix.org (1) * @ravanelli:matrix.org (1) * @yselkowitz:fedora.im (1)

4 months, 1 week

1
0
0 / 0

Can't update from fedora 39 to rawhide

by Guinevere Larsen

Hi Fedora list! I'm trying to upgrade a VM from fedora 39 to rawhide but running dnf system-upgrade download --releasever=rawhide fails. the offending package seems to be "grubby-8.40-73.fc39", which conflicts with sdubby-1.0-5.fc40. Is this a known issue? Does anyone know a workaround? If not, where do I properly report this? Thanks everyone! -- Cheers, Guinevere Larsen She/Her/Hers

4 months, 1 week