[Bug 2268548] New: perl-Verilog-Perl-3.482-1.fc41 FTBFS: cc1plus: fatal error: VParseBison.c: No such file or directory compilation terminated.
https://bugzilla.redhat.com/show_bug.cgi?id=2268548 Bug ID: 2268548 Summary: perl-Verilog-Perl-3.482-1.fc41 FTBFS: cc1plus: fatal error: VParseBison.c: No such file or directory compilation terminated. Product: Fedora Version: rawhide Status: NEW Component: perl-Verilog-Perl Assignee: jples...@redhat.com Reporter: ppi...@redhat.com QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora A local build of perl-Verilog-Perl-3.482-1.fc41 in mock failed for me: make[1]: Entering directory '/builddir/build/BUILD/Verilog-Perl-3.482/Parser' rm -rf VParseBison.c VParseBison.cpp bison --version | head -1 bison (GNU Bison) 3.8.2 Note: toolhash ignores VParseBison.output; remove gen/ if you want to debug the grammar Note: If the next command fails, you probably need to install Bison 1.875 or newer "/usr/bin/perl" ../Preproc/toolhash --verbose --name bisonpre --vercmd bison --skip-cmd 1 \ --in VParseBison.y bisonpre \ --out VParseBison.c VParseBison.h \ --cmd "/usr/bin/perl" bisonpre --yacc bison --debug --verbose --d -p VParseBison -k VParseBison.y -o VParseBison.c edit VParseBison.y VParseBison_pretmp.y bison -t -d -k -v --report=itemset --report=lookahead -p VParseBison -b VParseBison_pretmp -o VParseBison_pretmp.c VParseBison_pretmp.y edit VParseBison_pretmp.output VParseBison.output edit VParseBison_pretmp.c VParseBison.c edit VParseBison_pretmp.h VParseBison.h toolhash: Cache hit running bisonpre mv VParseBison.c VParseBison.cpp make[1]: Leaving directory '/builddir/build/BUILD/Verilog-Perl-3.482/Parser' [...] make[1]: Entering directory '/builddir/build/BUILD/Verilog-Perl-3.482/Parser' g++ -c -D_REENTRANT -D_GNU_SOURCE -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switc hes -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURC E=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong - specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fwrapv -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../Preproc -g -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer-DVERSION=\"3.482\" -DXS_VERSION=\"3.482\" -fPIC "-I/usr/lib64/perl5/CORE" VParseBison.c cc1plus: fatal error: VParseBison.c: No such file or directory compilation terminated. make[1]: *** [Makefile:335: VParseBison.o] Error 1 This looks like a race among parallel Makefile jobs. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2268548 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202268548%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
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-dc7c97ee12 chromium-122.0.6261.94-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-9b53b79398 golang-1.20.12-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing copr-cli-1.111-1.el7 python-copr-1.131-1.el7 Details about builds: copr-cli-1.111-1.el7 (FEDORA-EPEL-2024-1360839ea4) Command line interface for COPR Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 1.111-1 - correctly check CoprDir name before uploading large SRPM - assign fallback value from self.username - fix `copr build` +args --help output - typo in --namespace help output python-copr-1.131-1.el7 (FEDORA-EPEL-2024-1360839ea4) Python interface for Copr Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 1.131-1 - don't fail project create action if the new exist_ok=False opt is used -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ae22e0853d chromium-122.0.6261.94-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing copr-cli-1.111-1.el8 dkms-3.0.13-1.el8 lagrange-1.17.6-1.el8 python-copr-1.131-1.el8 python-copr-common-0.22-1.el8 Details about builds: copr-cli-1.111-1.el8 (FEDORA-EPEL-2024-e9b3113fcf) Command line interface for COPR Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 1.111-1 - correctly check CoprDir name before uploading large SRPM - assign fallback value from self.username - fix `copr build` +args --help output - typo in --namespace help output dkms-3.0.13-1.el8 (FEDORA-EPEL-2024-e4c830972b) Dynamic Kernel Module Support Framework Update Information: Update to bugfix release 3.0.13 ChangeLog: * Wed Mar 6 2024 Simone Caronni - 3.0.13-1 - Update to 3.0.13. lagrange-1.17.6-1.el8 (FEDORA-EPEL-2024-0abb112426) A Beautiful Gemini Client Update Information: Bug fixes: memory leaks. Gopher: Autodetect text media type from file name. ChangeLog: * Wed Mar 6 2024 Packit - 1.17.6-1 - Update to 1.17.6 - Resolves rhbz#2258919 * Thu Jan 25 2024 Fedora Release Engineering - 1.17.5-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild * Sun Jan 21 2024 Fedora Release Engineering - 1.17.5-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild References: [ 1 ] Bug #2258919 - lagrange-1.17.6 is available https://bugzilla.redhat.com/show_bug.cgi?id=2258919 python-copr-1.131-1.el8 (FEDORA-EPEL-2024-e9b3113fcf) Python interface for Copr Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 1.131-1 - don't fail project create action if the new exist_ok=False opt is used python-copr-common-0.22-1.el8 (FEDORA-EPEL-2024-850bb97d32) Python code used by Copr Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 0.22-1 - fix misleading warning for non-copr library consumers - add `contextlib.nullcontext` function as EL8 compat - limit stdout/stderr of ssh.run_expensive() commands - use 'copr-common/' as http user agent identifier - changes needed to allow user SSH to builders -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 9 updates-testing report
The following Fedora EPEL 9 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-99e002f742 chromium-122.0.6261.94-1.el9 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d996eeff0f rust-routinator-0.13.2-1.el9 The following builds have been pushed to Fedora EPEL 9 updates-testing copr-cli-1.111-1.el9 dkms-3.0.13-1.el9 lagrange-1.17.6-1.el9 python-copr-1.131-1.el9 python-copr-common-0.22-1.el9 python-shortuuid-1.0.12-2.el9 turbo-attack-0.1.0-1.el9 Details about builds: copr-cli-1.111-1.el9 (FEDORA-EPEL-2024-83215d2cb5) Command line interface for COPR Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 1.111-1 - correctly check CoprDir name before uploading large SRPM - assign fallback value from self.username - fix `copr build` +args --help output - typo in --namespace help output dkms-3.0.13-1.el9 (FEDORA-EPEL-2024-5dae42bc65) Dynamic Kernel Module Support Framework Update Information: Update to bugfix release 3.0.13 ChangeLog: * Wed Mar 6 2024 Simone Caronni - 3.0.13-1 - Update to 3.0.13. lagrange-1.17.6-1.el9 (FEDORA-EPEL-2024-ea3a500451) A Beautiful Gemini Client Update Information: Bug fixes: memory leaks. Gopher: Autodetect text media type from file name. ChangeLog: * Wed Mar 6 2024 Packit - 1.17.6-1 - Update to 1.17.6 - Resolves rhbz#2258919 * Thu Jan 25 2024 Fedora Release Engineering - 1.17.5-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild * Sun Jan 21 2024 Fedora Release Engineering - 1.17.5-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild References: [ 1 ] Bug #2258919 - lagrange-1.17.6 is available https://bugzilla.redhat.com/show_bug.cgi?id=2258919 python-copr-1.131-1.el9 (FEDORA-EPEL-2024-83215d2cb5) Python interface for Copr Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 1.131-1 - don't fail project create action if the new exist_ok=False opt is used python-copr-common-0.22-1.el9 (FEDORA-EPEL-2024-1cfdf63ac4) Python code used by Copr Update Information: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html ChangeLog: * Fri Mar 1 2024 Pavel Raiskup 0.22-1 - fix misleading warning for non-copr library consumers - add `contextlib.nullcontext` function as EL8 compat - limit stdout/stderr of ssh.run_expensive() commands - use 'copr-common/' as http user agent identifier - changes needed to allow user SSH to builders python-shortuuid-1.0.12-2.el9 (FEDORA-EPEL-2024-a141c85f1a) A generator library for concise, unambiguous and URL-safe UUIDs Update Information: Annotate *args as Any (#95) [Kamil Essekkat] Various upstream code modernization (SPDX, pyproject.toml, etc.) ChangeLog: * Wed Mar 6 2024 Michel Lind - 1.0.12-2 - Fix test run, upstream no longer ships setup.py * Wed Mar 6 2024 Packit - 1.0.12-1 - Update to 1.0.12 -
Re: reprodubible builds (re)introduction
On Thu, 7 Mar 2024 at 18:38, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Mar 07, 2024 at 10:01:08PM +, Richard W.M. Jones wrote: > > On Thu, Mar 07, 2024 at 12:39:37PM +, Zbigniew Jędrzejewski-Szmek > wrote: > > > Nevertheless, for me, reproducibility is interesting because it aids > debugability, and "threats" are not an immediate concern. Essentially, > when the > builds are stable, any unexpected change in the build outputs is much > easier to > diagnose. We have already found and submitted a bunch of obvious fixes that > would not have been found otherwise. Also, when builds are stable, when > working > on the tools, it is easy to do a rebuild with the patched tools and > observe the > diff. If the build is "unstable", i.e. there are various other unrelated > changes, interesting differences often drown in noise. > > Now this is the part which is the real important part which gets overlooked a lot. As much as some people somehow make it out that reproducibility will make things secure.. it will only do so against a threat which isn't as existent as people injecting bad source code. [Supply chain attacks are already just including bad source code which will build reproducible but still be bad. It is much cheaper to make mostly useful but compromised code into pypi, cpan, some cargo place etc and getting other people to need to include it in a distro or just straight to a developer than it is to break into Fedora/Debian/etc and compromise a gcc ] The real fix is in Quality and catching things which silently make builds bad. A CPU problem, a memory problem, a builder kernel issue, etc are bigger problems and more likely to cause hard to fix bugs because they aren't bugs in the code. Of course this means that builds need to be built twice inside a build system to make sure that both builds match.. otherwise you can end up where someone rebuilding starts reporting problems with our build system but its because they used overclocked ram or cpu :) > E.g. today I ended up creating a pull request for intltool package [1], > backporting a patch to fix a race in cache creation which was corrupting > translations in files. The patch is from 2015, but seemingly nobody > noticed the > issue in Fedora so far. > > More examples are [2,3], one of the many examples of noarch packages using > arch-dependent macros, e.g. %_libdir, leading to packages that are > "noarch", > but actually depend on the build architecture, and misbehave when installed > on a system with a different architecture than the build machine. > > [1] https://src.fedoraproject.org/rpms/intltool/pull-request/2 > [2] https://src.fedoraproject.org/rpms/xbyak/pull-request/5 > [3] https://src.fedoraproject.org/rpms/python-virt-firmware/pull-request/3 > > Zbyszek > -- > ___ > 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 > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren -- ___ 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: reprodubible builds (re)introduction
On Thu, Mar 07, 2024 at 10:01:08PM +, Richard W.M. Jones wrote: > On Thu, Mar 07, 2024 at 12:39:37PM +, Zbigniew Jędrzejewski-Szmek wrote: > > Hi, > > > > The effort to make package builds in Fedora reproducible has picked > > up steam again. We now have a new website: > > https://docs.fedoraproject.org/en-US/reproducible-builds > > I read this page but it doesn't cover an important point (for me). > What's the actual threat model you have in mind? The threat model is the build machine being "compromised" and modifying the build artifacts somehow. In case of a software attack, this could mean for example a rogue version of the compiler injecting additional code into the binaries. In general, any kind of "supply chain attack". But a non-malicious scenario is also possible, with the hardware being flaky or overheated or having firmware problems that result in some modification to the output binaries. I imagine that large organizations may invest in setting up a "shadow rebuild" instance that has the full pipeline from dist-git to binary rpms and does fully independent builds of packages. Reproducibility allows independent verification that the dist-git sources actually correspond to the binaries that are delivered. With such checks, any kind of supply chain attack would be very hard to do undetected. The build infrastracture in Fedora is obviously well protected, so such an attack would be very hard to pull off, but it also is exteremely attractive because of how effective and stealthy it would be. So by making builds reproducible and allowing 3rd parties to do rebuilds, we allow more trust to be established for our packages. Nevertheless, for me, reproducibility is interesting because it aids debugability, and "threats" are not an immediate concern. Essentially, when the builds are stable, any unexpected change in the build outputs is much easier to diagnose. We have already found and submitted a bunch of obvious fixes that would not have been found otherwise. Also, when builds are stable, when working on the tools, it is easy to do a rebuild with the patched tools and observe the diff. If the build is "unstable", i.e. there are various other unrelated changes, interesting differences often drown in noise. E.g. today I ended up creating a pull request for intltool package [1], backporting a patch to fix a race in cache creation which was corrupting translations in files. The patch is from 2015, but seemingly nobody noticed the issue in Fedora so far. More examples are [2,3], one of the many examples of noarch packages using arch-dependent macros, e.g. %_libdir, leading to packages that are "noarch", but actually depend on the build architecture, and misbehave when installed on a system with a different architecture than the build machine. [1] https://src.fedoraproject.org/rpms/intltool/pull-request/2 [2] https://src.fedoraproject.org/rpms/xbyak/pull-request/5 [3] https://src.fedoraproject.org/rpms/python-virt-firmware/pull-request/3 Zbyszek -- ___ 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 Linux 40 blocker status summary
Hi folks, As we are gearing up to the Fedora Linux 40 Beta release, there are a number of blockers that need attention. Below is a summary of current accepted and proposed blockers for F40 Beta[1]. As a reminder, the Beta release target date is Tuesday 19th March[2], and the Go/No-Go meeting is scheduled for next Thursday, 14th March[3]. == Proposed Blocker == 1. anaconda - UEFI installs using bootupd do not write an EFI boot manager entry, can make it hard to boot the installed system - NEW ACTION: Maintainer to diagnose issue == Accepted Blockers == 1. bcm283x-firmware - Raspberry Pi 400 shows nothing on screen when booting Fedora 40 images (even before grub) ACTION: IoT team to provide a fix 2. desktop-backgrounds - We need F40 backgrounds - MODIFIED ACTION: QA to verify https://bodhi.fedoraproject.org/updates/FEDORA-2024-f0fdde3a5d 3. shim - Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards - NEW ACTION: Maintainer to provide updated package if possible 4. shim-unsigned-aarch64 - Fedora fails to boot via BOOT/bootaa64->fbaa64 on UEFI machines with EFI_MEMORY_ATTRIBUTES_PROTOCOL - POST ACTION: Maintainer to provide updated build if possible 5. uboot-tools - u-boot doesnt find and load the Fedora provided DTBs from /boot/dtb - ASSIGNED ACTION: Maintainer to diagnose Accepted Previous Release Blocker 1. distribution - dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key - NEW ACTION: Maintainer to diagnose = Bug by Bug Detail = == Proposed Blockers == 1. anaconda - UEFI installs using bootupd do not write an EFI boot manager entry, can make it hard to boot the installed system - https://bugzilla.redhat.com/show_bug.cgi?id=2268505 - NEW UEFI installs using bootupd do not write an EFI boot manager entry. This can make the installed system difficult to boot - it will depend on the system's firmware implementation and configuration. It is affecting Fedora IoT images built with os-build and all Fedora Atomic Desktop images. We need the anaconda team to work on a fix for this. == Accepted Blockers == 1. bcm283x-firmware - Raspberry Pi 400 shows nothing on screen when booting Fedora 40 images (even before grub) - https://bugzilla.redhat.com/show_bug.cgi?id=2267968 - ASSIGNED Raspberry Pi 400 doesn't boot at all with 40-20240223.n.0 and 40-20240304.n.0 when tested both as is and with the firmware update, the display is black from the start even with the display on. 40-20240219.n.0 shows the same behaviour and on 40-20240304.n.0 when downgraded u-boot to 2024.01-2.fc40, the RPi400 behaves the same. The last working firmware is bcm283x-firmware-20231123-1.93d3f79.fc40, see https://koji.fedoraproject.org/koji/buildinfo?buildID=2324215. The IoT team will need to work on a fix to resolve this issue. 2. desktop-backgrounds - We need F40 backgrounds - https://bugzilla.redhat.com/show_bug.cgi?id=2264153 - MODIFIED There are no F40 backgrounds available yet for desktop. Work is being done at https://gitlab.com/groups/fedora/design/-/epics/32 and backgrounds have been submitted for testing https://bodhi.fedoraproject.org/updates/FEDORA-2024-f0fdde3a5d 3. shim - Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards - https://bugzilla.redhat.com/show_bug.cgi?id=2113005 - NEW UEFI LoadOptions that start with NUL cause boot failure. This is fixed upstream in https://github.com/rhboot/shim/pull/505 but the SecureBoot signing process requires NX support in the kernel. This is now in kernel 6.7 and unsigned shim builds showed up recently, so this is moving closer to being resolved once signed shim builds can be procured. The sign request can be seen here https://github.com/rhboot/shim-review/issues/386 and is yet to be merged 4. shim-unsigned-aarch64 - Fedora fails to boot via BOOT/bootaa64->fbaa64 on UEFI machines with EFI_MEMORY_ATTRIBUTES_PROTOCOL - https://bugzilla.redhat.com/show_bug.cgi?id=2259264 - POST Fedora boots that are going via the bootaa64->fbaa64 path (installers) fail to boot on machines that have the EFI_MEMORY_ATTRIBUTES_PROTOCOL. shim 15.8 is available upstream and has been built for x86 (shim-unsigned-x64-15.8-1) but not aarch64 as of yet and is waiting on this action to be resolved. 5. uboot-tools - u-boot doesnt find and load the Fedora provided DTBs from /boot/dtb - https://bugzilla.redhat.com/show_bug.cgi?id=2247873 - ASSIGNED Fedora Server images do not boot on the Jetson Nano. Non-Server images are not affected as they can use the kernel DTBs, and they boot OK. There is a similar root cause in https://bugzilla.redhat.com/show_bug.cgi?id=2246428 for this bug also. We need the ARM team to provide a fix for this. == Accepted Previous Release Blocker == 1. distribution - dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key - https://bugzilla.redhat.com/show_bug.cgi?id=2242759 - NEW beta dnf system-upgrade reboot fails on Raspberry Pi
Re: reprodubible builds (re)introduction
On Thu, Mar 07, 2024 at 12:39:37PM +, Zbigniew Jędrzejewski-Szmek wrote: > Hi, > > The effort to make package builds in Fedora reproducible has picked > up steam again. We now have a new website: > https://docs.fedoraproject.org/en-US/reproducible-builds I read this page but it doesn't cover an important point (for me). What's the actual threat model you have in mind? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- ___ 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 2268208] perl-CGI-4.63 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2268208 --- Comment #4 from Fedora Update System --- FEDORA-2024-ac1618b093 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ac1618b093` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ac1618b093 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2268208 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202268208%23c4 -- ___ 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
[Bug 2267294] perl-CGI-4.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2267294 --- Comment #5 from Fedora Update System --- FEDORA-2024-ac1618b093 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ac1618b093` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ac1618b093 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2267294 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202267294%23c5 -- ___ 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: Possible intermittent lost mail from Pagure
On Thu, Mar 07, 2024 at 09:30:02AM -0800, Kevin Fenzi wrote: > On Wed, Mar 06, 2024 at 11:44:51AM +, Richard W.M. Jones wrote: > > I can't quite point to proper evidence, but I have a feeling that > > email notifications are being lost from Pagure. > > I'm guessing from below you mean the src.fedoraproject.org instance? > (pagure.io is the other one, so it's best to be clear which one) Yes, src.fedoraproject.org > > One case where I'm about 90% sure this happened was with: > > > > https://src.fedoraproject.org/rpms/ogre/pull-request/3 > > > > where I did not receive the "cc @rjones" email. I don't think it was > > dropped by spam filters etc. > > > > I've seen other people complaining about this too, today for instance: > > > > https://src.fedoraproject.org/rpms/pcp/pull-request/25#comment-187753 > > So, src.fedoraproject.org should output fedora-messaging messages and > then notifications acts on those to notify people. > > What settings do you have in https://notifications.fedoraproject.org ? > Also, does this only happen some of the time? or always? This is definitely intermittent, and probably rare. I don't think I have change the notification settings. > It might be a fmn bug, or something deeper. ;( > > Can you start by filing on fmn: > https://github.com/fedora-infra/fmn/ > and we can try and track it down from there? > > > On a related subject, pagure does not send out email when someone > > rebases / force pushes to a pull request, which seems like a pretty > > big problem. > > I think that might be an upstream pagure issue? > https://pagure.io/pagure Thanks, Rich. > -- > ___ > 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 libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- ___ 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: Possible intermittent lost mail from Pagure
On Wed, Mar 06, 2024 at 11:44:51AM +, Richard W.M. Jones wrote: > I can't quite point to proper evidence, but I have a feeling that > email notifications are being lost from Pagure. I'm guessing from below you mean the src.fedoraproject.org instance? (pagure.io is the other one, so it's best to be clear which one) > One case where I'm about 90% sure this happened was with: > > https://src.fedoraproject.org/rpms/ogre/pull-request/3 > > where I did not receive the "cc @rjones" email. I don't think it was > dropped by spam filters etc. > > I've seen other people complaining about this too, today for instance: > > https://src.fedoraproject.org/rpms/pcp/pull-request/25#comment-187753 So, src.fedoraproject.org should output fedora-messaging messages and then notifications acts on those to notify people. What settings do you have in https://notifications.fedoraproject.org ? Also, does this only happen some of the time? or always? It might be a fmn bug, or something deeper. ;( Can you start by filing on fmn: https://github.com/fedora-infra/fmn/ and we can try and track it down from there? > On a related subject, pagure does not send out email when someone > rebases / force pushes to a pull request, which seems like a pretty > big problem. I think that might be an upstream pagure issue? https://pagure.io/pagure kevin 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
[Bug 2257106] F40FailsToInstall: perl-WWW-Google-Contacts
https://bugzilla.redhat.com/show_bug.cgi?id=2257106 --- Comment #4 from Fedora Fails To Install --- This package has been orphaned. You can pick it up at https://src.fedoraproject.org/rpms/perl-WWW-Google-Contacts by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257106 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257106%23c4 -- ___ 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
[Bug 2268454] New: Upgrade perl-Carp-Assert-More to 2.4.0
https://bugzilla.redhat.com/show_bug.cgi?id=2268454 Bug ID: 2268454 Summary: Upgrade perl-Carp-Assert-More to 2.4.0 Product: Fedora Version: rawhide URL: https://metacpan.org/release/Carp-Assert-More Status: NEW Component: perl-Carp-Assert-More Assignee: spo...@gmail.com Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, spo...@gmail.com, xav...@bachelot.org Target Milestone: --- Classification: Fedora Latest Fedora delivers 2.3.0 version. Upstream released 2.4.0. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2268454 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202268454%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 40 compose report: 20240307.n.0 changes
OLD: Fedora-40-20240306.n.0 NEW: Fedora-40-20240307.n.0 = SUMMARY = Added images:1 Dropped images: 6 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 = Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-40-20240307.n.0.iso = DROPPED IMAGES = Image: Workstation live-osbuild x86_64 Path: Workstation/x86_64/iso/Fedora-Workstation-Live-osb-40-20240306.n.0.x86_64.iso Image: Kinoite ociarchive ppc64le Path: Kinoite/ppc64le/images/Fedora-Kinoite-40.20240306.n.0.ociarchive Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-40-20240306.n.0.iso Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-40-20240306.n.0.iso Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-40-20240306.n.0.iso Image: Workstation live-osbuild aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-osb-40-20240306.n.0.aarch64.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = -- ___ 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 rawhide compose report: 20240307.n.0 changes
OLD: Fedora-Rawhide-20240305.n.0 NEW: Fedora-Rawhide-20240307.n.0 = SUMMARY = Added images:3 Dropped images: 5 Added packages: 13 Dropped packages:0 Upgraded packages: 236 Downgraded packages: 0 Size of added packages: 7.40 MiB Size of dropped packages:0 B Size of upgraded packages: 6.58 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 32.34 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20240307.n.0.iso Image: Kinoite dvd-ostree aarch64 Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20240307.n.0.iso Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20240307.n.0.iso = DROPPED IMAGES = Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20240305.n.0.iso Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20240305.n.0.iso Image: Workstation live-osbuild aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-osb-Rawhide-20240305.n.0.aarch64.iso Image: Astronomy_KDE live x86_64 Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-Rawhide-20240305.n.0.iso Image: Workstation live-osbuild x86_64 Path: Workstation/x86_64/iso/Fedora-Workstation-Live-osb-Rawhide-20240305.n.0.x86_64.iso = ADDED PACKAGES = Package: ghc-toml-parser-1.3.2.0-29.fc41 Summary: TOML 1.0.0 parser RPMs:ghc-toml-parser ghc-toml-parser-devel ghc-toml-parser-doc ghc-toml-parser-prof Size:4.90 MiB Package: golang-github-edoardottt-golazy-0.1.4-1.fc41 Summary: Golang module exporting general purpose functions I get tired of rewriting every time RPMs:golang-github-edoardottt-golazy-devel Size:23.91 KiB Package: golang-github-jackc-puddle2-2.2.1-1.fc41 Summary: Generic resource pool for Go RPMs:golang-github-jackc-puddle2-devel Size:30.78 KiB Package: golang-github-yuin-goldmark-meta-1.1.0-1.fc41 Summary: A YAML metadata extension for the goldmark markdown parser RPMs:golang-github-yuin-goldmark-meta-devel Size:13.39 KiB Package: h3-4.1.0-1.fc41 Summary: Hexagonal hierarchical geospatial indexing system RPMs:h3 h3-devel h3-tools Size:599.69 KiB Package: msgraph-0.2.1-1.fc41 Summary: Library to access MS Graph API for Microsoft 365 RPMs:msgraph msgraph-devel msgraph-doc Size:512.97 KiB Package: php-nikic-php-parser5-5.0.2-1.fc41 Summary: A PHP parser written in PHP - version 5 RPMs:php-nikic-php-parser5 Size:210.05 KiB Package: pybind11-json-0.2.13-1.fc41 Summary: Using nlohmann::json with pybind11 RPMs:pybind11-json-devel Size:14.08 KiB Package: python-docopt-ng-0.9.0-1.fc41 Summary: Humane command line arguments parser RPMs:python3-docopt-ng Size:41.33 KiB Package: python-pytest-home-0.5.1-1.fc41 Summary: A temporary home directory fixture RPMs:python3-pytest-home Size:12.68 KiB Package: rust-backoff-0.4.0-1.fc41 Summary: Retry operations with exponential backoff policy RPMs:rust-backoff+async-std-devel rust-backoff+async_std_1-devel rust-backoff+default-devel rust-backoff+futures-core-devel rust-backoff+futures-devel rust-backoff+pin-project-lite-devel rust-backoff+tokio-devel rust-backoff+tokio_1-devel rust-backoff-devel Size:83.37 KiB Package: syncplay-1.7.1-1.fc41 Summary: Synchronize playback of various video players via internet RPMs:syncplay Size:838.35 KiB Package: tomcat-jakartaee-migration-1.0.8-1.fc41 Summary: Tomcat Migration Tool for Jakarta EE RPMs:tomcat-jakartaee-migration tomcat-jakartaee-migration-javadoc Size:182.19 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: Cython-3.0.8-4.fc41 Old package: Cython-3.0.8-1.fc40 Summary: Language for writing Python extension modules RPMs: python3-cython Size: 15.58 MiB Size change: 2.88 KiB Changelog: * Wed Feb 21 2024 Karolina Surma - 3.0.8-3 - Use Python 3.13.0a4 PyCFunctionFastWithKeywords * Sat Mar 02 2024 Miro Hron??ok - 3.0.8-4 - Disable GCC warnings/errors about wrong self casts in final function calls Package: SDL2_image-2.8.2-4.fc41 Old package: SDL2_image-2.8.2-3.fc40 Summary: Image loading library for SDL RPMs: SDL2_image SDL2_image-devel Size: 668.05 KiB Size change: 1.22 KiB Changelog: * Wed Mar 06 2024 S??rgio Basto - 2.8.2-4 - add jpegxl and avif as shared libs Package: accel-config-4.1.6-6.fc41 Old package: accel-config-4.1.2-5.fc41 Summary: Configure accelerator subsystem devices RPMs: accel-config accel-config-devel accel-config-libs Size: 302.06 KiB Size change: 395 B Changelog: * Tue Mar 05 2024 Jun Miao - 4.1.2-6 - Update to v4.1.6 release Package: agenda-1.1.2-23.fc41 Old package: agenda-1.1.2-21.fc40 Summary: A simple, slick, speedy and no-nonsense task
CANCELLED - Fedora Linux 40 Beta Go/No-Go Meeting on 2024-03-07
Due to outstanding blocker bugs[1], we do not have an F40 Beta RC. As a result, F40 Beta is NO-GO by default and today's Go/No-Go meeting is cancelled. The next Fedora Linux 40 Beta Go/No-Go meeting[2] will be held at 1700 UTC on Thursday 14th March in #meeting:fedoraproject.org on Matrix. We will aim for the current Beta Target date (target date #1) of 19th March. The release schedule[3] has been updated accordingly. [1] https://qa.fedoraproject.org/blockerbugs/milestone/40/beta/buglist [2] https://calendar.fedoraproject.org/meeting/10758/ [3] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] CANCELLED - Fedora Linux 40 Beta Go/No-Go Meeting on 2024-03-07
Due to outstanding blocker bugs[1], we do not have an F40 Beta RC. As a result, F40 Beta is NO-GO by default and today's Go/No-Go meeting is cancelled. The next Fedora Linux 40 Beta Go/No-Go meeting[2] will be held at 1700 UTC on Thursday 14th March in #meeting:fedoraproject.org on Matrix. We will aim for the current Beta Target date (target date #1) of 19th March. The release schedule[3] has been updated accordingly. [1] https://qa.fedoraproject.org/blockerbugs/milestone/40/beta/buglist [2] https://calendar.fedoraproject.org/meeting/10758/ [3] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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: reprodubible builds (re)introduction
On Thu, Mar 07, 2024 at 12:39:37PM +, Zbigniew Jędrzejewski-Szmek wrote: > Second, for the usual enticement: join and be merry. I forgot to add: if you want me to rebuild your package and report the result, please send a name-version-release string. Zbyszek -- ___ 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
reprodubible builds (re)introduction
Hi,
The effort to make package builds in Fedora reproducible has picked up steam
again.
We now have a new website:
https://docs.fedoraproject.org/en-US/reproducible-builds
and an issue tracker: https://pagure.io/fedora-reproducible-builds/project
and a matrix room: https://matrix.to/#/#reproducible-builds:fedora.im
We've done a mini rebuild using [1] for the package list [2] and results are at
[3].
(The result is a json dump of rpmdiff output by package. Generally, "" means
the rebuild was identical except for variable metadata, and non-empty
output else means that the rebuild was different.)
[1] https://github.com/keszybz/fedora-repro-build
[2] https://fedorapeople.org/~zbyszek/builds-2024-02-fc41-filtered.txt
[3] https://fedorapeople.org/~zbyszek/builds-2024-02-fc41-filtered.results.txt
I'm writing this mail for two purposes. First, as a heads-up:
various patches and RFEs have been filed to fix issues as they are detected.
Second, for the usual enticement: join and be merry.
The plan for the immediate future is to fix various issues, both those
that affect a single package and also the ones that affect a swath of packages.
Some of the remaining second type:
https://pagure.io/fedora-reproducible-builds/project/issue/7
— static archives do not respect $SOURCE_DATE_EPOCH, embed UID and GID
https://pagure.io/fedora-reproducible-builds/project/issue/10
— Java jar files embed build timestamps
https://pagure.io/fedora-reproducible-builds/project/issue/12
— Python pyc file serialization is architecture-specific
https://pagure.io/fedora-reproducible-builds/project/issue/14
— noarch packages installing into %{_libdir}
https://pagure.io/fedora-reproducible-builds/project/issue/15
— golang debuginfo pakages have files with .gdb_index section of varying size
If you have ideas how to tackle some of those issues, help would be very
welcome.
Please use the matrix room for coordination.
Currently the percentage of reproducibility is not very high.
Once we fix the issues that affect swaths of packages and we're down
to issues that only affect one or a very small number of packages, I hope
we can make reproducibility an official effort in Fedora. But that's still
some way ahead.
Zbyszek
--
___
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 2261451] perl-WWW-Google-Contacts: FTBFS in Fedora rawhide/f40
https://bugzilla.redhat.com/show_bug.cgi?id=2261451 Fedora Admin user for bugzilla script actions changed: What|Removed |Added Assignee|avibra...@gmail.com |extras-orphan@fedoraproject ||.org --- Comment #4 from Fedora Admin user for bugzilla script actions --- This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261451 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261451%23c4 -- ___ 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
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2024-03-08 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10568/ -- ___ 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: Donate 1 minute of your time to test upgrades from F39 to F40
On Thu, 2024-03-07 at 11:15 +, Sérgio Basto wrote: > On Thu, 2024-03-07 at 10:27 +, Barry Scott wrote: > > > > > > > > > > On 21/02/2024 07:11, Miroslav Suchý wrote: > > > > > > > > dnf --releasever=40 --setopt=module_platform_id=platform:f40 \ > > > --enablerepo=updates-testing \ > > > $(rpm -q fedora-repos-modular >/dev/null && echo -- > > > enablerepo=updates-testing-modular) \ > > > --assumeno distro-sync > > > > > > > Fedora KDE spin - Intel CPU AMD GPU - > > > > Error: > > Problem: problem with installed package blender-1:4.0.2- > > 1.fc39.x86_64 > > - blender-1:4.0.2-1.fc39.x86_64 from @System does not belong to > > a distupgrade repository > > - nothing provides libopenvdb.so.10.1()(64bit) needed by blender- > > 1:4.0.2-1.fc40.x86_64 from fedora > > (try to add '--skip-broken' to skip uninstallable packages) > > is the combination of > Bug 2259558 - F40FailsToInstall: blender > Bug 2261013 - blender: FTBFS in Fedora rawhide/f40 > Blender is FTBFS because : DEBUG util.py:461: Failed to resolve the transaction: DEBUG util.py:461: Problem 1: package usd-devel-23.11-2.fc40.aarch64 requires libusd_ms.so.0.23.11()(64bit), but none of the providers can be installed DEBUG util.py:461: - package usd-devel-23.11-2.fc40.aarch64 requires usd-libs(aarch-64) = 23.11-2.fc40, but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:461: - nothing provides libboost_python312.so.1.81.0()(64bit) needed by usd-libs-23.11- 2.fc40.aarch64 DEBUG util.py:461: - nothing provides libopenvdb.so.10.1()(64bit) needed by usd-libs-23.11-2.fc40.aarch64 DEBUG util.py:461: - nothing provides libdraco.so.8()(64bit) needed by usd-libs-23.11-2.fc40.aarch64 DEBUG util.py:461: Problem 2: package openshadinglanguage-devel- 1.12.14.0-9.fc40.aarch64 requires liboslquery.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-devel-1.12.14.0- 9.fc40.aarch64 requires liboslexec.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-devel-1.12.14.0- 9.fc40.aarch64 requires liboslcomp.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-devel-1.12.14.0- 9.fc40.aarch64 requires liboslnoise.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-devel-1.12.14.0- 9.fc40.aarch64 requires libtestshade.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-devel-1.12.14.0- 9.fc40.aarch64 requires openshadinglanguage-libs(aarch-64) = 1.12.14.0- 9.fc40, but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:461: - nothing provides libboost_thread.so.1.81.0()(64bit) needed by openshadinglanguage-libs- 1.12.14.0-9.fc40.aarch64 DEBUG util.py:461: Problem 3: package OpenImageIO-devel-2.4.17.0- 1.fc40.aarch64 requires libOpenImageIO_Util.so.2.4()(64bit), but none of the providers can be installed DEBUG util.py:461: - package OpenImageIO-devel-2.4.17.0-1.fc40.aarch64 requires libOpenImageIO.so.2.4()(64bit), but none of the providers can be installed DEBUG util.py:461: - package OpenImageIO-devel-2.4.17.0-1.fc40.aarch64 requires OpenImageIO(aarch-64) = 2.4.17.0-1.fc40, but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:461: - nothing provides libboost_thread.so.1.81.0()(64bit) needed by OpenImageIO-2.4.17.0- 1.fc40.aarch64 DEBUG util.py:461: - nothing provides libopenvdb.so.10.1()(64bit) needed by OpenImageIO-2.4.17.0-1.fc40.aarch64 DEBUG util.py:461: Problem 4: package openshadinglanguage-common- headers-1.12.14.0-9.fc40.noarch requires openshadinglanguage = 1.12.14.0-9.fc40, but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-1.12.14.0- 9.fc40.aarch64 requires liboslquery.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-1.12.14.0- 9.fc40.aarch64 requires liboslexec.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - package openshadinglanguage-1.12.14.0- 9.fc40.aarch64 requires liboslcomp.so.1.12()(64bit), but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:461: - nothing provides libboost_thread.so.1.81.0()(64bit) needed by openshadinglanguage-libs- 1.12.14.0-9.fc40.aarch64 DEBUG util.py:610: Child return code was: 1 DEBUG util.py:185: kill orphans in chroot /var/lib/mock/f40-build- 48392202-5759785/root > > Fedora Server as router - Intel CPU > > - No problems. > > > > Fedora Server as router - RaspberryPi > > - No problems. > > > > Fedora Server as file server/imapl server/prometheus - Intel CPU > > - No problems > > > > Fedora KODI media player - Intel CPU > > - No problems > > > > Barry > > > > > > > > > > > > > > >
Re: Donate 1 minute of your time to test upgrades from F39 to F40
On Thu, 2024-03-07 at 10:27 +, Barry Scott wrote: > > > > > On 21/02/2024 07:11, Miroslav Suchý wrote: > > > > > dnf --releasever=40 --setopt=module_platform_id=platform:f40 \ > > --enablerepo=updates-testing \ > > $(rpm -q fedora-repos-modular >/dev/null && echo -- > > enablerepo=updates-testing-modular) \ > > --assumeno distro-sync > > > > Fedora KDE spin - Intel CPU AMD GPU - > > Error: > Problem: problem with installed package blender-1:4.0.2- > 1.fc39.x86_64 > - blender-1:4.0.2-1.fc39.x86_64 from @System does not belong to a > distupgrade repository > - nothing provides libopenvdb.so.10.1()(64bit) needed by blender- > 1:4.0.2-1.fc40.x86_64 from fedora > (try to add '--skip-broken' to skip uninstallable packages) is the combination of Bug 2259558 - F40FailsToInstall: blender Bug 2261013 - blender: FTBFS in Fedora rawhide/f40 > Fedora Server as router - Intel CPU > - No problems. > > Fedora Server as router - RaspberryPi > - No problems. > > Fedora Server as file server/imapl server/prometheus - Intel CPU > - No problems > > Fedora KODI media player - Intel CPU > - No problems > > 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 -- 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: Donate 1 minute of your time to test upgrades from F39 to F40
On 21/02/2024 07:11, Miroslav Suchý wrote: dnf --releasever=40 --setopt=module_platform_id=platform:f40 \ --enablerepo=updates-testing \ $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \ --assumeno distro-sync Fedora KDE spin - Intel CPU AMD GPU - Error: Problem: problem with installed package blender-1:4.0.2-1.fc39.x86_64 - blender-1:4.0.2-1.fc39.x86_64 from @System does not belong to a distupgrade repository - nothing provides libopenvdb.so.10.1()(64bit) needed by blender-1:4.0.2-1.fc40.x86_64 from fedora (try to add '--skip-broken' to skip uninstallable packages) Fedora Server as router - Intel CPU - No problems. Fedora Server as router - RaspberryPi - No problems. Fedora Server as file server/imapl server/prometheus - Intel CPU - No problems Fedora KODI media player - Intel CPU - No problems 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
Looking for new maintainers for Epson inkjet printer drivers
Hi, due to increased activity in a number of open source scientific projects, I no longer have as much time for Fedora packages, and need to prune out packages I no longer can effectively maintain. The Epson inkjet drivers are very high on this list, given that I haven't even had an Epson inkjet printer in several years. I am hoping to find new maintainers for the epson-inkjet-printer-escpr and epson-inkjet-printer-escpr2 packages. Susi -- Susi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- ___ 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 2268208] perl-CGI-4.63 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2268208 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Fixed In Version||perl-CGI-4.63-1.fc41 Resolution|--- |ERRATA Last Closed||2024-03-07 08:38:18 --- Comment #3 from Fedora Update System --- FEDORA-2024-34b096b358 (perl-CGI-4.63-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2268208 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202268208%23c3 -- ___ 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
[Bug 2268208] perl-CGI-4.63 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2268208 --- Comment #2 from Fedora Update System --- FEDORA-2024-ac1618b093 (perl-CGI-4.63-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ac1618b093 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2268208 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202268208%23c2 -- ___ 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
[Bug 2268208] perl-CGI-4.63 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2268208 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2024-34b096b358 (perl-CGI-4.63-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-34b096b358 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2268208 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202268208%23c1 -- ___ 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
