[Bug 2250861] perl-Data-Clone-0.006 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2250861 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-Data-Clone-0.005 is|perl-Data-Clone-0.006 is |available |available --- Comment #1 from Upstream Release Monitoring --- Releases retrieved: 0.006 Upstream release that is considered latest: 0.006 Current version/release in rawhide: 0.004-30.fc39 URL: http://search.cpan.org/dist/Data-Clone Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/7043/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Data-Clone -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2250861 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202250861%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
[Test-Announce] 2023-11-27 @ ** 16:00 ** UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-11-27 # Time: ** 16:00 ** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: ** #fedora-meeting on irc.libera.chat ** Greetings testers! It's time for another QA meeting. Note clocks have changed everywhere they change, by now. If you follow daylight savings time, the meeting should be at the same local time as usual. If you do not follow daylight savings time, the meeting will be one hour later than it was over the summer, in your local time. You can run `date -u` to see the current UTC time if you are unsure. As usual lately, please note this meeting will really be *on IRC*. Matrix may be ready for meeting purposes pretty soon, but I need to check on that before moving the meeting. So please use an IRC client or the web client - https://web.libera.chat/#fedora-meeting - to join. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. Note I have a partial conflict for the second half hour of the meeting slot, so might have to cut the meeting short or let someone take over. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in and Change review 3. Communications overhaul: Discourse and Matrix? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ 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: How can I delete a rawhide Bodhi update?
On Fri, 2023-11-24 at 09:51 +, Mattia Verga via devel wrote: > I must say this is really a rare case when an automatic update which is > gated by failing tests and stuck in testing It's really not *that* rare any more, since we do quite extensive gating of critical path updates on openQA tests. I'd estimate about one update every two or three days fails tests for legit reasons. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ 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 deprecation/removal of Initial Setup from Fedora
I am a devout anaconda bigot, and I exclusively use the Everything.iso with it. Of course, I use it via terminal mode. A feature I relish in anaconda, is the ability to manage disks and partitions.(using the right most radio button)My system has 2 SSD and 6 disks, and with anaconda, I select all of them and thenuse the mentioned disk management to build the target system along with a completed /etc/fstab. If I was looking to improve anaconda, I would add a one or two line description against each group.the right most application selection column. As well, an option to offer a way to respond to what "Gerd Hoffmann" was posting, Please do not add another tool, just embellish anaconda to include the extra functionality. Leslie Satenstein On Friday, November 24, 2023 at 06:18:47 p.m. EST, Adam Williamson wrote: On Fri, 2023-11-24 at 13:38 +0100, Jiri Konecny wrote: > Hi, > > I wonder, I thought that the server images are usually using Anaconda to > create a user during installation. Am I missing something? No, I think you're right there. initial-setup is not part of the anaconda-deployed Server package set. anaconda - as it does for all other spins/editions except Workstation - requires you to create a root password or admin user, so you can always log in. I think if initial-setup was included in the package set, it would run on boot if you didn't *both* set the root password *and* create a user (as it does on spins where it is installed, e.g. KDE), but it isn't. I tested this with a Server DVD image I had lying around; doing an install with only root password (no user created) didn't run initial- setup on boot, and rpm shows initial-setup not installed. However, as dgilmore noted, the Server ARM disk images certainly do rely on initial-setup. > > Best Regards, > Jirka > > Dne 22. 11. 23 v 13:53 Gerd Hoffmann napsal(a): > > On Tue, Nov 21, 2023 at 08:07:06AM -0800, Davide Cavalca wrote: > > > On 2023-11-21 04:34, Jiri Konecny wrote: > > > > Is Anaconda Initial Setup important for your project or workflow? What > > > > functionality is absolutely necessary for you? Do you use the text > > > > mode or the graphical mode? Are you aware of any alternatives? Is > > > > there anything that would prevent you from migrating to one of the > > > > proposed alternatives? Also please feel free to share this mail to any > > > > relevant groups. > > > The Fedora Asahi Remix uses initial-setup (in text mode) for our Server > > > and > > > Minimal variants. > > I think this is used by *all* server images. It offers to set the root > > password and add users, so without that you simply can't login ... > > > > take care, > > Gerd > > -- > > ___ > > 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 > -- > ___ > 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 -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ 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 -- ___ 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
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7e5dc8aef7 chromium-119.0.6045.159-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing golang-1.20.10-3.el7 php-smarty-gettext-1.7.0-2.el7 Details about builds: golang-1.20.10-3.el7 (FEDORA-EPEL-2023-1c906d04ee) The Go Programming Language Update Information: Security fix for CVE-2023-39320, CVE-2023-39318, CVE-2023-39321, CVE-2023-39322, CVE-2023-39323 ChangeLog: * Thu Nov 23 2023 Dave Dykstra - 1.20.10-3 - Skip ppc64le_cgo_inline_plt test which is failing on el7. * Thu Nov 23 2023 Dave Dykstra - 1.20.10-2 - Rebuild to correct day of week on 1.19.13 changelog. * Thu Nov 23 2023 Dave Dykstra - 1.20.10-1 - Update to 1.20.10 by doing the equivalent changes done in RedHat ubi8. References: [ 1 ] Bug #2237775 - CVE-2023-39320 golang: cmd/go: go.mod toolchain directive allows arbitrary execution https://bugzilla.redhat.com/show_bug.cgi?id=2237775 [ 2 ] Bug #2237776 - CVE-2023-39318 golang: html/template: improper handling of HTML-like comments within script contexts https://bugzilla.redhat.com/show_bug.cgi?id=2237776 [ 3 ] Bug #223 - CVE-2023-39321 golang: crypto/tls: panic when processing post-handshake message on QUIC connections https://bugzilla.redhat.com/show_bug.cgi?id=223 [ 4 ] Bug #2237778 - CVE-2023-39322 golang: crypto/tls: lack of a limit on buffered post-handshake https://bugzilla.redhat.com/show_bug.cgi?id=2237778 [ 5 ] Bug #2242544 - CVE-2023-39323 golang: cmd/go: line directives allows arbitrary execution during build https://bugzilla.redhat.com/show_bug.cgi?id=2242544 php-smarty-gettext-1.7.0-2.el7 (FEDORA-EPEL-2023-976baae7b3) Gettext support for Smarty Update Information: First EPEL 7 build. ChangeLog: * Thu Nov 16 2023 Xavier Bachelot - 1.7.0-2 - Provide autoloader - Run test suite * Mon Jul 17 2023 Xavier Bachelot - 1.7.0-1 - Initial package -- ___ 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
Re: Possible deprecation/removal of Initial Setup from Fedora
On Fri, 2023-11-24 at 13:38 +0100, Jiri Konecny wrote: > Hi, > > I wonder, I thought that the server images are usually using Anaconda to > create a user during installation. Am I missing something? No, I think you're right there. initial-setup is not part of the anaconda-deployed Server package set. anaconda - as it does for all other spins/editions except Workstation - requires you to create a root password or admin user, so you can always log in. I think if initial-setup was included in the package set, it would run on boot if you didn't *both* set the root password *and* create a user (as it does on spins where it is installed, e.g. KDE), but it isn't. I tested this with a Server DVD image I had lying around; doing an install with only root password (no user created) didn't run initial- setup on boot, and rpm shows initial-setup not installed. However, as dgilmore noted, the Server ARM disk images certainly do rely on initial-setup. > > Best Regards, > Jirka > > Dne 22. 11. 23 v 13:53 Gerd Hoffmann napsal(a): > > On Tue, Nov 21, 2023 at 08:07:06AM -0800, Davide Cavalca wrote: > > > On 2023-11-21 04:34, Jiri Konecny wrote: > > > > Is Anaconda Initial Setup important for your project or workflow? What > > > > functionality is absolutely necessary for you? Do you use the text > > > > mode or the graphical mode? Are you aware of any alternatives? Is > > > > there anything that would prevent you from migrating to one of the > > > > proposed alternatives? Also please feel free to share this mail to any > > > > relevant groups. > > > The Fedora Asahi Remix uses initial-setup (in text mode) for our Server > > > and > > > Minimal variants. > > I think this is used by *all* server images. It offers to set the root > > password and add users, so without that you simply can't login ... > > > > take care, > >Gerd > > -- > > ___ > > 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 > -- > ___ > 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 -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ 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 deprecation/removal of Initial Setup from Fedora
On Tue, 2023-11-21 at 13:34 +0100, Jiri Konecny wrote: > Hello everyone, > > Is Anaconda Initial Setup important for your project or workflow? What > functionality is absolutely necessary for you? Do you use the text mode > or the graphical mode? Are you aware of any alternatives? Is there > anything that would prevent you from migrating to one of the proposed > alternatives? Also please feel free to share this mail to any relevant > groups. In addition to the other uses identified: if you do a KDE install and set the root password but do not create a user account, i-s will run on first boot and allow (not sure if it requires) user creation. This is probably the case for other non-GNOME desktops too (GNOME uses its own gnome-initial-setup). openQA tests this: https://openqa.fedoraproject.org/tests/2280185#step/_graphical_wait_login/1 -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ 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: Blender 4.0.0 failure on aarch64 and ppc64le
Luya Tshimbalanga venit, vidit, dixit 2023-11-24 01:45:37: > Hello team, > Blender 4.0.1 failed to build on both aarch64 and ppc64le on the following > lines: > ``` > /builddir/build/BUILD/blender/intern/cycles/blender/attribute_convert.h:69:44: > error: cannot convert ‘ccl::float4’ to ‘float’ >69 | return color_srgb_to_linear(make_float4(byte_to_float(value[0]), > | ~~~^ > || > |ccl::float4 >70 | byte_to_float(value[1]), > | >71 | byte_to_float(value[2]), > | >72 | byte_to_float(value[3]))); > | > In file included from > /builddir/build/BUILD/blender/intern/cycles/blender/attribute_convert.h:9: > /builddir/build/BUILD/blender/intern/cycles/util/color.h:62:45: note: > initializing argument 1 of ‘float ccl::color_srgb_to_linear(float)’ >62 | ccl_device float color_srgb_to_linear(float c) > | ~~^ > ``` > while the previous version 3.6.5 worked as intendedd and x86_64 is > unaffected. Could someone running the above architecture addressing the issue > please? > See > https://copr.fedorainfracloud.org/coprs/g/designsuite/blender/build/6681752/ Hi Luya, looks like this one: https://projects.blender.org/blender/blender/pulls/115098 The backport seems to be this one: https://projects.blender.org/blender/blender/commit/641b7808f24fa6eae593dd8f093878e4cafc4499 So it will be in 4.0.2. Cheers, Michael -- ___ 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
[rpms/perl-MARC-Record] PR #1: Package tests and format license to SPDX
spot merged a pull-request against the project: `perl-MARC-Record` that you are following. Merged pull-request: `` Package tests and format license to SPDX `` https://src.fedoraproject.org/rpms/perl-MARC-Record/pull-request/1 -- ___ 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
[rpms/perl-MARC-Record] PR #1: Package tests and format license to SPDX
mspacek opened a new pull-request against the project: `perl-MARC-Record` that you are following: `` Package tests and format license to SPDX `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-MARC-Record/pull-request/1 -- ___ 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 rawhide compose report: 20231124.n.0 changes
OLD: Fedora-Rawhide-20231123.n.0 NEW: Fedora-Rawhide-20231124.n.0 = SUMMARY = Added images:3 Dropped images: 3 Added packages: 10 Dropped packages:0 Upgraded packages: 71 Downgraded packages: 0 Size of added packages: 1.27 MiB Size of dropped packages:0 B Size of upgraded packages: 14.15 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 2.17 GiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20231124.n.0.iso Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20231124.n.0.iso Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20231124.n.0.iso = DROPPED IMAGES = Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20231123.n.0.iso Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20231123.n.0.iso Image: Kinoite dvd-ostree aarch64 Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20231123.n.0.iso = ADDED PACKAGES = Package: elementary-notifications-7.0.1-1.fc40 Summary: GTK Notifications Server RPMs:elementary-notifications elementary-notifications-demo Size:296.07 KiB Package: msv-2022.7-1.fc40 Summary: Multi-Schema Validator Toolkit RPMs:msv-javadoc msv-xsdlib Size:546.62 KiB Package: python-lqrt-0.3.3-5.fc40 Summary: Hypothesis Testing of Location Parameters using Lq-Likelihood-Ratio-Type Test RPMs:python3-lqrt Size:34.30 KiB Package: rust-clap_complete_command-0.5.1-1.fc40 Summary: Reduces boilerplate for adding a shell completion command to Clap RPMs:rust-clap_complete_command+default-devel rust-clap_complete_command+fig-devel rust-clap_complete_command+nushell-devel rust-clap_complete_command-devel Size:35.60 KiB Package: rust-clearscreen-2.0.1-1.fc40 Summary: Cross-platform terminal screen clearing RPMs:rust-clearscreen+default-devel rust-clearscreen-devel Size:151.97 KiB Package: rust-countme-3.0.1-1.fc40 Summary: Counts the number of live instances of types RPMs:rust-countme+dashmap-devel rust-countme+default-devel rust-countme+enable-devel rust-countme+once_cell-devel rust-countme+print_at_exit-devel rust-countme+rustc-hash-devel rust-countme-devel Size:60.99 KiB Package: rust-drop_bomb-0.1.5-1.fc40 Summary: Runtime guard for implementing linear types RPMs:rust-drop_bomb+default-devel rust-drop_bomb-devel Size:21.55 KiB Package: rust-fs-set-times-0.20.0-1.fc40 Summary: Set filesystem timestamps RPMs:rust-fs-set-times+default-devel rust-fs-set-times-devel Size:30.86 KiB Package: rust-insta-cmd-0.4.0-1.fc40 Summary: Command line extension to the insta testing library for Rust RPMs:rust-insta-cmd+default-devel rust-insta-cmd-devel Size:26.16 KiB Package: rust-trycmd-0.14.19-1.fc40 Summary: Snapshot testing for a herd of CLI tests RPMs:rust-trycmd+color-auto-devel rust-trycmd+color-devel rust-trycmd+debug-devel rust-trycmd+default-devel rust-trycmd+diff-devel rust-trycmd+escargot-devel rust-trycmd+examples-devel rust-trycmd+filesystem-devel rust-trycmd+schema-devel rust-trycmd-devel Size:100.90 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: SkyX-0.4-34.fc40 Old package: SkyX-0.4-31.fc37 Summary: Photo-realistic sky simulator RPMs: SkyX SkyX-devel Size: 14.54 MiB Size change: -11.62 KiB Changelog: * Wed Jul 20 2022 Fedora Release Engineering - 0.4-32 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Wed Jan 18 2023 Fedora Release Engineering - 0.4-33 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Wed Jul 19 2023 Fedora Release Engineering - 0.4-34 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Thu Nov 23 2023 Rich Mattes - 0.4-34 - Fix boost linkage - Resolves: rhbz#2114519 Package: angelfish-24.01.75-1.fc40 Old package: angelfish-23.08.2-1.fc40 Summary: Plasma Mobile minimal web browser RPMs: angelfish Size: 851.51 KiB Size change: 44.36 KiB Changelog: * Thu Nov 23 2023 Yaakov Selkowitz - 24.01.75-1 - 24.01.75 Package: arianna-24.01.75-1.fc40 Old package: arianna-23.08.2-1.fc40 Summary: EPub Reader for mobile devices RPMs: arianna Size: 758.24 KiB Size change: 29.02 KiB Changelog: * Thu Nov 23 2023 Yaakov Selkowitz - 24.01.75-1 - 24.01.75 Package: arm-trusted-firmware-2.10.0-1.fc40 Old package: arm-trusted-firmware-2.10-0.1.rc0.fc40 Summary: ARM Trusted Firmware RPMs: arm-trusted-firmware-armv8 Size: 153.00 KiB Size change: -19 B Changelog: * Thu Nov 23 2023 Peter Robinson - 2.10.0-1 - Update to 2.10,0 Package: copr-backend-1.173-1.fc40 Old package: copr-backend
Re: Possible deprecation/removal of Initial Setup from Fedora
Hi, I wonder, I thought that the server images are usually using Anaconda to create a user during installation. Am I missing something? Best Regards, Jirka Dne 22. 11. 23 v 13:53 Gerd Hoffmann napsal(a): On Tue, Nov 21, 2023 at 08:07:06AM -0800, Davide Cavalca wrote: On 2023-11-21 04:34, Jiri Konecny wrote: Is Anaconda Initial Setup important for your project or workflow? What functionality is absolutely necessary for you? Do you use the text mode or the graphical mode? Are you aware of any alternatives? Is there anything that would prevent you from migrating to one of the proposed alternatives? Also please feel free to share this mail to any relevant groups. The Fedora Asahi Remix uses initial-setup (in text mode) for our Server and Minimal variants. I think this is used by *all* server images. It offers to set the root password and add users, so without that you simply can't login ... take care, Gerd -- ___ 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 -- ___ 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 2251183] Upgrade perl-Encode-JIS2K to 0.05
https://bugzilla.redhat.com/show_bug.cgi?id=2251183 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Encode-JIS2K-0.05-1.fc ||40 Resolution|--- |ERRATA Status|MODIFIED|CLOSED Last Closed||2023-11-24 12:24:40 --- Comment #2 from Fedora Update System --- FEDORA-2023-cfcd843a08 has been pushed to the Fedora 40 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=2251183 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251183%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 2251183] Upgrade perl-Encode-JIS2K to 0.05
https://bugzilla.redhat.com/show_bug.cgi?id=2251183 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-cfcd843a08 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-cfcd843a08 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2251183 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251183%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
libxml2 2.12.0 (and 2.12.1) in rawhide, with some API breaks
The latest released versions of libxml2 have a couple of important changes in header files that have unintentionally caused some packages to fail to build without modification, including: * several functions now accept or return a const xmlError struct * cyclic dependencies in header files were fixed (by dropping some includes) Most failures that have been witnessed so far by davidlt while rebuilding RISCV packages, and have been related to the xmlError const change, but xmlsec1 was hit by the include changes: https://github.com/lsh123/xmlsec/pull/729 https://src.fedoraproject.org/rpms/xmlsec1/pull-request/4 As libxml2 is used rather widely, I expect more changes to come up over time, so please feel free to ask me for help (amigadave on IRC, or Cc on bugs) and I will be happy to submit patches upstream and do builds; I am a provenpackager, so happy to help. Thanks to davidlt for spotting the breakages! -- https://amigadave.com/ 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
Re: How can I delete a rawhide Bodhi update?
Il 23/11/23 21:11, Adam Williamson ha scritto: > On Thu, 2023-11-23 at 20:40 +0100, Florian Weimer wrote: >> * Mattia Verga via devel: >> >>> Il 23/11/23 16:40, Florian Weimer ha scritto: I've got an update that I don't see pushed to stable. How do I make sure that doesn't happen? As it's for rawhide, I didn't create the Bodhi update, and I don't see an option to delete it. >>> There's no option to delete Bodhi updates. It can only be done by >>> hacking the database directly, but it is usually never necessary. >>> >>> I assume you're referring to >>> https://bodhi.fedoraproject.org/updates/FEDORA-2023-13783978e8. That >>> update will never be pushed to stable, since it is gated by failed >>> tests. >> Half a dozen people can waive those tests, and there have been incorrect >> waivers before. 8-/ >> >> I just want to make sure the update doesn't proceed because I'm not >> entirely confident that the fix I have is logically correct. > If we can get two more people to -1 it, Bodhi should obsolete/unpush it > in response to that karma. > > As Mattia said, it's intentional that there's no option to *delete* an > update. We don't want history to disappear. But it does seem like > there's a workflow problem here. It would be useful for maintainers to > have the ability to put an update in a state from which it cannot be > pushed stable by karma or autopush (only by the maintainer or a > provenpackager changing the state again). For regular release updates > the maintainer can at least "unpush" them, though I'm not sure this > fully achieves the goal. For Rawhide updates it looks like you can't > even do that, which is awkward. I'd say it's probably worth filing a > Bodhi issue for this... That's weird: as a provenpackager I had the "edit" button available in the webUI, so I would assume that Florian as the update submitter should have it too. Anyway, despite not having the button for unpushing the update, I was able to do that by CLI. I must say this is really a rare case when an automatic update which is gated by failing tests and stuck in testing, but I'll look to provide an unpush button in the web UI when this happens. It would have been nice to test if Florian had the power to unpush the update by CLI, unfortunately I already did so... maybe next time. Mattia -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
