Re: clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu'
On Mon, Apr 15, 2024 at 06:49:54AM -0700, Tom Stellard wrote: > On 4/15/24 02:55, Richard W.M. Jones wrote: > > > >Anyone got any idea about this build failure? > > > >https://koji.fedoraproject.org/koji/taskinfo?taskID=116395331 > > > >[+] All set and ready to build. > >clang: warning: -Wl,-z,relro: 'linker' input unused > >[-Wunused-command-line-argument] > >clang: warning: -Wl,--as-needed: 'linker' input unused > >[-Wunused-command-line-argument] > >clang: warning: -Wl,-z,pack-relative-relocs: 'linker' input unused > >[-Wunused-command-line-argument] > >clang: warning: -Wl,-z,now: 'linker' input unused > >[-Wunused-command-line-argument] > >clang: warning: -Wl,--build-id=sha1: 'linker' input unused > >[-Wunused-command-line-argument] > >clang: warning: -ldl: 'linker' input unused [-Wunused-command-line-argument] > >clang: warning: -lrt: 'linker' input unused [-Wunused-command-line-argument] > >clang: warning: -lm: 'linker' input unused [-Wunused-command-line-argument] > >clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for > >target 'x86_64-redhat-linux-gnu' > > > >AFAICT -mtls-dialect=gnu2 is not added by anything in the spec file or > >in AFL++ sources, so it must be coming from RPM macros? > > > > Are you building with both gcc and clang? If you are only building with > clang, you > should use the toolchain macro which will ensure you get the correct flags; > > %global toolchain clang Unfortunately the AFL "build system" (which would be more accurately described as "big pile of semi-documented Makefiles") is rather obtuse. However it does need to build for both GCC and Clang so I don't think this will work. Also builds differently on x86_64 and !x86_64, although I disabled !x86_64 for now as it was too much trouble. And it doesn't work upstream with LLVM18, so I am having to use LLVM17 in Rawhide. If you want to take a look and suggest improvements please be my guest: https://src.fedoraproject.org/rpms/american-fuzzy-lop/tree/rawhide Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- ___ 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: network service removed in Fedora 40 without a Change proposal(?)
On Fri, Apr 12, 2024 at 9:41 PM Adam Williamson wrote: > > Michel Lind just prompted me to notice that the 'network' service > appears to have been removed from initscripts in Fedora 40+. > Should this have been a Change? How worried are we about it going out > in Fedora 40 without having been through the Change process? I think it should have been better documented (i.e. called out in a change proposal for feedback), but I am going to suggest systemd-networkd as the longer term better solution (but that would be for another day). -- ___ 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
Schedule for Monday's FESCo Meeting (2024-04-15)
* NOTE: Meeting time moved 30 minutes earlier. Following is the list of topics that will be discussed in the FESCo meeting Monday at 19:00 UTC in #meeting:fedoraproject.org on Matrix. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2024-04-15 19:00 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = Discussed and Voted in the Ticket = #3190 Change: Enable Consistent Device Naming in Cloud Images https://pagure.io/fesco/issue/3190 APPROVED (4, 0, 0) #3189 Change: Change Compose Settings https://pagure.io/fesco/issue/3189 APPROVED (8, 0, 0) #3188 Change: RPM 4.20 https://pagure.io/fesco/issue/3188 APPROVED (7, 0, 0) = New business = #3196 [FastTrack] Proposal: require legacy network service to be reinstated in Fedora 40 (removal should require a Change) https://pagure.io/fesco/issue/3196 = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- ___ 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: network service removed in Fedora 40 without a Change proposal(?)
On Mon, 2024-04-15 at 10:44 +, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Apr 15, 2024 at 10:46:39AM +0200, Lukáš Nykrýn wrote: > > Just for record, the removal of network-scripts was done because > > https://fedoraproject.org/wiki/Changes/dhclient_deprecation > > That page has Category:ChangePageIncomplete. > dhcp-client is present in F40, even though it has Provides:deprecated(). > > > Network-scripts heavily depend on dhclient and there is no plan to rework > > them to use a different dhcp implementation. > > Ack. So it sounds like we could keep using both in F40 > and prepare for removal in F41. There are various uses of the service that do not need a DHCP client, like the one I referred to in the bug report and FESCo ticket. Heck, you can kinda *assume* anyone still using the service at this point is doing something weird with it, not just a 'normal' "bring up this interface for me with DHCP" kinda thing. The removal of the network service should still be treated as its own significant operation, not a natural consequence of the removal of dhclient. -- 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: network service removed in Fedora 40 without a Change proposal(?)
> > > Just for record, the removal of network-scripts was done because > > > https://fedoraproject.org/wiki/Changes/dhclient_deprecation > > > > That page has Category:ChangePageIncomplete. > > dhcp-client is present in F40, even though it has Provides:deprecated(). > > > > > Network-scripts heavily depend on dhclient and there is no plan to rework > > > them to use a different dhcp implementation. > > > > Ack. So it sounds like we could keep using both in F40 > > and prepare for removal in F41. > > There are various uses of the service that do not need a DHCP client, > like the one I referred to in the bug report and FESCo ticket. Heck, > you can kinda *assume* anyone still using the service at this point is > doing something weird with it, not just a 'normal' "bring up this > interface for me with DHCP" kinda thing. > > The removal of the network service should still be treated as its own > significant operation, not a natural consequence of the removal of > dhclient. The System-V scripts are also deprecated since systemd v254 so eventually they'll be going away too: https://lists.freedesktop.org/archives/systemd-devel/2023-August/049349.html -- ___ 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: F41 Change Proposal: Versioned Kubernetes Packages (Self-Cont
One of the characteristics of Kubernetes is that skipping minor versions during an upgrade is not supported. This reduces the potential complexity in correctly setting Obsoletes/Provides in the package for the replacing version. The unsupported version can also be marked deprecated. These steps can help inform a user during dnf updates. In addition, there is a Kubernetes page in Quick Docs which contains, in part, life cycle information for each Kubernetes release. While I am a maintainer this page will be kept reasonably current, although I cannot speak for subsequent maintainers. This page can be supplemented by email to this list and posts on the Fedora community blog and Discussions. I will be glad to update the proposal to make this more explicit. best regards Brad Smith On Sun, Apr 14, 2024 at 8:56 AM Zbigniew Jędrzejewski-Szmek wrote: > > Something that is not discussed explicitly in the proposal: > what happens during an upgrade, when the user has a version installed > that is not supported anymore. Do they get some notification that > they should switch to the next one? > > 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
Re: Non-responsive maintainer check for aarapov
(Adding Eugene for increased visibility) On Mon, Apr 15, 2024 at 02:38:01PM +0200, Anton Arapov wrote: > Hello Lichen, > > I commented on the issue. Apologies, I didn’t spot it earlier; > https://pagure.io/find-inactive-packagers/issue/1695 > > https://pagure.io/user/esyr Eugene Syromiatnikov, should be looking after > dmidecode; He should be with Red Hat still. About dmidecode, it's currently shown with just Anton as packager: https://src.fedoraproject.org/rpms/dmidecode If Eugene wishes to co-maintain we should add him. Lichen Liu and Coiby Xu are Red Hat associates & kernel devs who are maintaining this package in RHEL, and they have expressed a wish to co-maintain it also: https://pagure.io/packager-sponsors/issue/644 Note this is not either-or, you can all co-maintain it together if you want, but the package currently seems unmaintained. Rich. > Anton. > > > On 15. 4. 2024, at 4:28, Lichen Liu wrote: > > > > Hello devel-list! > > > > Does anyone know how to contact @aarapov, the maintainer of dmidecode? > > > > Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2275034 > > > > I haven't seen any activity recently, and there is a > > find-inactive-packagers ticket: > > > > https://pagure.io/find-inactive-packagers/issue/1695 > > > > Dmidecode is a very important package, I want to keep it updated. > > > > Thanks > > > > Lichen > > -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- ___ 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: clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu'
On 4/15/24 02:55, Richard W.M. Jones wrote: Anyone got any idea about this build failure? https://koji.fedoraproject.org/koji/taskinfo?taskID=116395331 [+] All set and ready to build. clang: warning: -Wl,-z,relro: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,--as-needed: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,-z,pack-relative-relocs: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,-z,now: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,--build-id=sha1: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -ldl: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -lrt: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -lm: 'linker' input unused [-Wunused-command-line-argument] clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu' AFAICT -mtls-dialect=gnu2 is not added by anything in the spec file or in AFL++ sources, so it must be coming from RPM macros? Are you building with both gcc and clang? If you are only building with clang, you should use the toolchain macro which will ensure you get the correct flags; %global toolchain clang -Tom 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
Summary/Minutes from today's Fedora Flatpak Packaging SIG Meeting (2024-04-15)
Text Log: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-04-15/flatpak-sig.2024-04-15-15.03.log.txt HTML Log: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-04-15/flatpak-sig.2024-04-15-15.03.log.html Text Minutes: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-04-15/flatpak-sig.2024-04-15-15.03.txt HTML Minutes: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-04-15/flatpak-sig.2024-04-15-15.03.html = # #meeting-1:fedoraproject.org: flatpak-sig = Meeting started by @kalev:fedora.im at 2024-04-15 15:03:21 Meeting summary --- * TOPIC: Init process (@kalev:fedora.im, 15:03:31) * TOPIC: f40 mass rebuild (@yselkowitz:fedora.im, 15:06:26) * INFO: ~82% of flatpaks are rebuilt for f40 and in testing (@yselkowitz:fedora.im, 15:07:12) * LINK: https://pad.riseup.net/p/Tyg0nsudHLy2v__a0HzE (@yselkowitz:fedora.im, 15:07:19) * TOPIC: openh264 (@yselkowitz:fedora.im, 15:32:14) * TOPIC: issue trackers (@yselkowitz:fedora.im, 15:40:52) * INFO: speech-dispatcher-libs are included in f40 runtimes (@yselkowitz:fedora.im, 15:41:17) * LINK: https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/28 (@yselkowitz:fedora.im, 15:41:20) * INFO: no "Fedora Flatpaks" product in RHBZ (@yselkowitz:fedora.im, 15:47:02) * LINK: https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/29 (@yselkowitz:fedora.im, 15:47:07) * INFO: flatpakBuild[Arch] are not searchable in kojiweb (@yselkowitz:fedora.im, 15:50:44) * LINK: https://pagure.io/koji-flatpak/issue/1 (@yselkowitz:fedora.im, 15:50:48) * TOPIC: open floor (@yselkowitz:fedora.im, 15:52:27) Meeting ended at 2024-04-15 16:00:32 Action items People Present (lines said) --- * @yselkowitz:fedora.im (63) * @kalev:fedora.im (44) * @meetbot:fedora.im (2) * @zodbot:fedora.im (1) -- ___ 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 40 compose report: 20240415.n.0 changes
OLD: Fedora-40-20240414.n.0 NEW: Fedora-40-20240415.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 3 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 1.34 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 1.67 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Cloud_Base docker aarch64 Path: Cloud/aarch64/images/Fedora-Cloud-Base-GCE.aarch64-40-20240414.n.0.tar.gz = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: gcc-14.0.1-0.15.fc40 Old package: gcc-14.0.1-0.13.fc40 Summary: Various compilers (C, C++, Objective-C, ...) RPMs: cpp gcc gcc-c++ gcc-gdb-plugin gcc-gdc gcc-gfortran gcc-gm2 gcc-gnat gcc-go gcc-objc gcc-objc++ gcc-offload-amdgcn gcc-offload-nvptx gcc-plugin-annobin gcc-plugin-devel libasan libasan-static libatomic libatomic-static libgcc libgccjit libgccjit-devel libgfortran libgfortran-static libgm2 libgm2-static libgnat libgnat-devel libgnat-static libgo libgo-devel libgo-static libgomp libgomp-offload-amdgcn libgomp-offload-nvptx libgphobos libgphobos-static libhwasan libhwasan-static libitm libitm-devel libitm-static liblsan liblsan-static libobjc libquadmath libquadmath-devel libquadmath-static libstdc++ libstdc++-devel libstdc++-docs libstdc++-static libtsan libtsan-static libubsan libubsan-static Size: 998.84 MiB Size change: 1.72 MiB Changelog: * Wed Apr 10 2024 Jakub Jelinek 14.0.1-0.14 - update from trunk - PRs analyzer/114588, bootstrap/106472, c++/91079, c++/99377, c++/100667, c++/103825, c++/104040, c++/32, c++/114377, c++/114462, c++/114479, c++/114537, c++/114561, c++/114562, c++/114572, c++/114580, c/114361, debug/114608, fortran/36337, fortran/50410, fortran/106999, fortran/110987, fortran/112407, fortran/113885, fortran/113956, fortran/114474, fortran/114535, gcov-profile/113765, gcov-profile/114115, gcov-profile/114601, ipa/111571, ipa/113359, ipa/113907, ipa/113964, libquadmath/114533, libquadmath/114623, libstdc++/104606, libstdc++/114519, libstdc++/114633, lto/114655, middle-end/114552, middle-end/114599, middle-end/114604, middle-end/114627, middle-end/114628, modula2/114517, modula2/114520, modula2/114548, modula2/114565, modula2/114617, modula2/114648, rtl-optimization/112560, rtl-optimization/114415, target/88309, target/101865, target/112919, target/113233, target/113986, target/114577, target/114587, target/114590, target/114603, target/114607, testsuite/114034, testsuite/114036, testsuite/114307, testsuite/114614, testsuite/114642, testsuite/114662, tree-optimization/112303, tree-optimization/114115, tree-optimization/114480, tree-optimization/114485, tree-optimization/114551, tree-optimization/114555, tree-optimization/114557, tree-optimization/114566, tree-optimization/114624 - don't emit VEX encoded AES-NI instructions when just -maes and not -mavx is enabled (#2272758, PR target/114576) - fix s390* peephole2 to check mode of constant pool entries and for 64-bit extraction from 128-bit constant pool entry extract the correct half of the value (#2273618, PR target/114605) * Thu Apr 11 2024 Jakub Jelinek 14.0.1-0.15 - update from trunk - PRs analyzer/114472, c++/114303, c++/114409, debug/112878, fortran/106500, middle-end/110027, middle-end/114681, target/114639, tree-optimization/109596, tree-optimization/114672 - fix symbol version of std::__basic_file::native_handle() const (PR libstdc++/114692) - emit -Whardened warning even for -fhardened -fcf-protection=none (#2273610, PR target/114606) Package: mesa-24.0.5-1.fc40 Old package: mesa-24.0.4-1.fc40 Summary: Mesa graphics libraries RPMs: mesa-dri-drivers mesa-filesystem mesa-libEGL mesa-libEGL-devel mesa-libGL mesa-libGL-devel mesa-libOSMesa mesa-libOSMesa-devel mesa-libOpenCL mesa-libOpenCL-devel mesa-libd3d mesa-libd3d-devel mesa-libgbm mesa-libgbm-devel mesa-libglapi mesa-libxatracker mesa-libxatracker-devel mesa-omx-drivers mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers Size: 272.34 MiB Size change: -88.13 KiB Changelog: * Thu Apr 11 2024 Jos?? Exp??sito - 24.0.5-1 - Update to 24.0.5 Package: qt6-qtbase-6.6.2-7.fc40 Old package: qt6-qtbase-6.6.2-6.fc40 Summary: Qt6 - QtBase components RPMs: qt6-qtbase qt6-qtbase-common qt6-qtbase-devel qt6-qtbase-examples qt6-qtbase-gui qt6-qtbase-ibase qt6-qtbase-mysql qt6-qtbase-odbc qt6-qtbase-postgresql qt6-qtbase-private-devel qt6-qtbase-static Size: 102.12 MiB Size change: 35.83 KiB Changelog: * Thu Apr 11 2024 Adam
Re: network service removed in Fedora 40 without a Change proposal(?)
> The System-V scripts are also deprecated since systemd v254 so > eventually they'll be going away too: > > https://lists.freedesktop.org/archives/systemd-devel/2023-August/049349.html This change should be reverted in Fedora. The "systemd cabal"'s hatred of SysV is insufficient justification for this dropping a 'network' service, and there exist myriad third-party tools that prefer imperative control over their start process anyway. -- ___ 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: Updating Taskwarrior to v3
Hi Ankur, On 4/15/24 07:59, Ankur Sinha wrote: On Mon, Apr 15, 2024 14:18:59 +0200, Jos Vos wrote: On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote: Hrm, but the problem here is that a user that currently has the task package installed (currently v2) will end up with v3 if I update the task package to v3---which is something we'd like to avoid here. Just a side question: is this task v3 update planned to be distributed *during* an OS lifecycle or only at the start of a new one (e.g. F41, I assume it is too late for F40 now)? Are there any Fedora policies for this kind of incompatible updates? The general policy is to not introduce backwards incompatible changes to stable releases: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases I am thinking that the best way for this would be to announce it as a self-contained change so it'll land in rawhide (F41). In the meantime, I can perhaps keep a COPR repository for stable Fedora releases (F39/F40) for users that do want to use taskv3 already. https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_self_contained_changes How does that sound? What you can probably do now is to introduce the compat package *first* into all stable releases - and make it obsolete the task package at the current NEVRA. Then for Rawhide, you can update the task package to version 3 - that way current users will get moved to task2 seamlessly (probably make the update suggest they log out, just in case), and when task v3 is packaged, they can then export their current database using the existing task2 and import it after reinstalling task? Best, -- _o) Michel Lind (né Salim) _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 OpenPGP_0x8B229D2F7CCC04F2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital 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: network service removed in Fedora 40 without a Change proposal(?)
On Mon, Apr 15, 2024 at 09:20:32PM -, Japheth J.C. Cleaver wrote: > > The System-V scripts are also deprecated since systemd v254 so > > eventually they'll be going away too: > > > > https://lists.freedesktop.org/archives/systemd-devel/2023-August/049349.html > > This change should be reverted in Fedora. The "systemd cabal"'s hatred of > SysV is insufficient justification for this dropping a 'network' service, and > there exist myriad third-party tools that prefer imperative control over > their start process anyway. Regardless of whether you agree with deprecating SysV or not, network-scripts' removal from Fedora has nothing to do with the "systemd cabal" - indeed, the systemd maintainer in Fedora, zbyszek, voted in favor of restoring network-scripts earlier today. Best regards, and let's treat each other respectfully, -- _o) Michel Lind (né Salim) _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 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: Updating Taskwarrior to v3
As a tangent on this thread, it would be cool if there were a mechanism in dnf to tell users when an upgrade needs special attention/instructions. Another example like this is postgresql updates, which also require manual intervention. -- ___ 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: Obsolete pygobject3-devel usage
On Fri, 2024-04-12 at 17:35 -0400, Yaakov Selkowitz wrote: > The pygobject3-devel compat provides was recently removed from > python3-gobject-devel: > > https://src.fedoraproject.org/rpms/pygobject3/c/0eda657eab55405bdbebc6eb3112fcf7dcb517ba?branch=rawhide > > However, a number of packages still use it, and now FTBFS as a result: > > accerciser.spec:BuildRequires: pygobject3-devel > bolt.spec:BuildRequires: pygobject3-devel > gnome-abrt.spec:BuildRequires: pygobject3-devel > gnumeric.spec:BuildRequires: pygobject3-devel > gom.spec:BuildRequires: pygobject3-devel > gst-editing-services.spec:BuildRequires: pygobject3-devel > mozo.spec:BuildRequires: pygobject3-devel > nautilus-python.spec:BuildRequires: pygobject3-devel > nfoview.spec:BuildRequires: pygobject3-devel > piper.spec:BuildRequires: pygobject3-devel > pluma.spec:BuildRequires: pygobject3-devel > python-caja.spec:BuildRequires: pygobject3-devel > python-gstreamer1.spec:BuildRequires: pygobject3-devel > sugar-toolkit-gtk3.spec:BuildRequires: pygobject3-devel > xpra.spec:BuildRequires: pygobject3-devel > zbar.spec:BuildRequires: pygobject3-devel > > This is blocking the F40 rebuild of a number of flatpaks, so I'll > provenpackager them soon if not fixed by then. These are now all fixed in rawhide, and in f40 as needed. Thank you to all those who helped. -- Yaakov Selkowitz Principal Software Engineer - Emerging RHEL Red Hat, Inc. -- ___ 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
Summary/Minutes from today's FESCo Meeting (2024-04-15)
Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-15/fesco.2024-04-15-19.01.log.txt HTML Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-15/fesco.2024-04-15-19.01.log.html Text Minutes: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-15/fesco.2024-04-15-19.01.txt HTML Minutes: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-15/fesco.2024-04-15-19.01.html Meeting summary --- * TOPIC: Init Process (@tstellar:fedora.im, 19:01:42) * TOPIC: #3196 [FastTrack] Proposal: require legacy network service to be reinstated in Fedora 40 (removal should require a Change) (@tstellar:fedora.im, 19:32:16) * LINK: https://src.fedoraproject.org/rpms/initscripts/pull-request/10 (@zbyszek:fedora.im, 20:18:43) * AGREED: proposal: FESCo asks that the legacy network subpackage be reinstated for F40. The bug requesting the reinstatement is marked as F40-0day and F40-freeze-exception. APPROVED(+7,0,0) (@tstellar:fedora.im, 20:27:27) * TOPIC: Next week's chair (@tstellar:fedora.im, 20:27:47) * TOPIC: #3196 [FastTrack] Proposal: require legacy network service to be reinstated in Fedora 40 (removal should require a Change) (@tstellar:fedora.im, 20:30:52) * AGREED: Proposal: the network-scripts should block F40 GA. REJECTED(+1,0,-6) (@tstellar:fedora.im, 20:33:25) * TOPIC: Next week's chair (@tstellar:fedora.im, 20:33:35) * ACTION: zbyszek will chair next meeting (@tstellar:fedora.im, 20:34:03) * ACTION: Stephen Gallagher will chair the meeting in two weeks. (@tstellar:fedora.im, 20:34:38) * TOPIC: Open Floor (@tstellar:fedora.im, 20:34:47) Meeting ended at 2024-04-15 20:48:15 Action items * zbyszek will chair next meeting * Stephen Gallagher will chair the meeting in two weeks. People Present (lines said) --- * @conan_kudo:matrix.org (60) * @nirik:matrix.scrye.com (51) * @zbyszek:fedora.im (49) * @tstellar:fedora.im (46) * @sgallagh:fedora.im (29) * @salimma:fedora.im (18) * @zodbot:fedora.im (12) * @decathorpe:fedora.im (11) * @mhayden:fedora.im (7) * @jistone:fedora.im (7) * @smooge:fedora.im (4) * @meetbot:fedora.im (2) * @jsteffan:fedora.im (1) -- ___ 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: [SPDX] Mass license change OSL 2.0, ERPL, EU Datagrid, SPL
Dne 08. 04. 24 v 8:23 dop. Miroslav Suchý napsal(a): Hi. I am going to do the mass change of the license from OSL 2.0 to OSL-2.0 The proposed diff is in attachment. Affected package: dirvish Change from ERPL to ErlPL-1.1 Affected packages: erlang-gen_leader erlang-p1_pgsql Change from EU Datagrid to EUDatagrid Affected package: edg-gridftp-client Change from SPL to SPL-1.0 Affected package: brazil All done. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys -- ___ 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
clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu'
Anyone got any idea about this build failure? https://koji.fedoraproject.org/koji/taskinfo?taskID=116395331 [+] All set and ready to build. clang: warning: -Wl,-z,relro: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,--as-needed: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,-z,pack-relative-relocs: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,-z,now: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -Wl,--build-id=sha1: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -ldl: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -lrt: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -lm: 'linker' input unused [-Wunused-command-line-argument] clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu' AFAICT -mtls-dialect=gnu2 is not added by anything in the spec file or in AFL++ sources, so it must be coming from RPM macros? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html -- ___ 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: clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu'
On Mon, Apr 15, 2024 at 10:55:34AM +0100, Richard W.M. Jones wrote:
>
> Anyone got any idea about this build failure?
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=116395331
>
> [+] All set and ready to build.
> clang: warning: -Wl,-z,relro: 'linker' input unused
> [-Wunused-command-line-argument]
> clang: warning: -Wl,--as-needed: 'linker' input unused
> [-Wunused-command-line-argument]
> clang: warning: -Wl,-z,pack-relative-relocs: 'linker' input unused
> [-Wunused-command-line-argument]
> clang: warning: -Wl,-z,now: 'linker' input unused
> [-Wunused-command-line-argument]
> clang: warning: -Wl,--build-id=sha1: 'linker' input unused
> [-Wunused-command-line-argument]
> clang: warning: -ldl: 'linker' input unused [-Wunused-command-line-argument]
> clang: warning: -lrt: 'linker' input unused [-Wunused-command-line-argument]
> clang: warning: -lm: 'linker' input unused [-Wunused-command-line-argument]
> clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for
> target 'x86_64-redhat-linux-gnu'
>
> AFAICT -mtls-dialect=gnu2 is not added by anything in the spec file or
> in AFL++ sources, so it must be coming from RPM macros?
Never mind, I see what it is, it's from redhat-rpm-config-288-1.fc41.noarch:
$ rpm --eval '%{optflags}'
... -mtls-dialect=gnu2 ...
which clang 18 doesn't understand.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
--
___
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: clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu'
On Mon, Apr 15, 2024 at 4:56 AM Richard W.M. Jones wrote: > > > Anyone got any idea about this build failure? > > https://koji.fedoraproject.org/koji/taskinfo?taskID=116395331 > > [+] All set and ready to build. > clang: warning: -Wl,-z,relro: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,--as-needed: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,-z,pack-relative-relocs: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,-z,now: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,--build-id=sha1: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -ldl: 'linker' input unused [-Wunused-command-line-argument] > clang: warning: -lrt: 'linker' input unused [-Wunused-command-line-argument] > clang: warning: -lm: 'linker' input unused [-Wunused-command-line-argument] > clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for > target 'x86_64-redhat-linux-gnu' > > AFAICT -mtls-dialect=gnu2 is not added by anything in the spec file or > in AFL++ sources, so it must be coming from RPM macros? > It was added a month ago to redhat-rpm-config: https://src.fedoraproject.org/rpms/redhat-rpm-config/c/b7d1bfae1fb673c4d8a21a8866ba4e37b2cd6eaf -- 真実はいつも一つ！/ Always, there's only one truth! -- ___ 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: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 09:41:05 -, Onuralp SEZER wrote: > > +1 to create task3 but the CLI command is "task". It either needs to > rename both like "task2,task3" or conflict old and new ones and > prevent installing both of them. They are not designed to be installed in parallel, so task3 will obsolete task. However, task3 will not provide the task package, so that task will not be updated to task3 during normal upgrades. Users will have to explicitly install task3. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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: F41 Change Proposal - Reproducible Package Builds (System-Wide)
On Mon, Apr 15, 2024 at 11:10:28AM +0200, Miroslav Suchý wrote: > Dne 13. 04. 24 v 1:16 odp. Zbigniew Jędrzejewski-Szmek napsal(a): > > The proposal explicitly states that we don't want Perl in all buildroots. > > How many seconds we save by NOT pulling Perl? Per each build? In total for > whole release cycle? > > How many seconds we loose (lost) by refactoring the code? I wasn't measuring the time exactly, but about two weeks of my time. > And syncing with Debian? > Or even worse finding issues that Debian will find and we not? Some divergence from Debian would happen anyway. Their build system is different enough that we have some non-overlapping issues. And in my implementation, I was a bit more conservative in what is changed, doing the minimal replacements. We'd either have to maintain some patches or wait until upstream accepts our changes and makes a release. Having a tool that is under our control allows us to update much more quickly. For Perl, the issue is not so much the seconds and megabytes, but that a) Perl is now effectively a niche language, we made the choice to use Python for tooling instead a long time ago, and b) it'd pull in the interpreter and a set of modules. Considering that we need python marshalparser for the pyc files, that'd mean two interpreter stacks in some cases. Perl certainly has and will have its uses, but I don't think we should use it when adding completely new tooling to our build system. 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
Re: Updating Taskwarrior to v3
Hi, On Mon, Apr 15, 2024 at 11:04:22AM +0100, Ankur Sinha wrote: They are not designed to be installed in parallel, so task3 will obsolete task. However, task3 will not provide the task package, so that task will not be updated to task3 during normal upgrades. Users will have to explicitly install task3. Being a happy taskwarrior user since years: Note that users do not always update (full) OS releases, but do new installs while keeping (a.o.) /home. So, after installing that new OS release, users will face the same issue. Furthermore, if they are used to install "task", they will install the wrong version, even if they may want to use the new version. The fact that v3 does *require* a v2 for exporting is of course a bad thing, they should have added a export-v2 option or so. Will the task v3 warn users if they detect old data? What is the idea? To temporarily provide both packages, v2 and v3, that can not be installed together? About the naming / versioning part: this probably has happened before with other packages, I am not aware of all the policies. But I would think that having task2 for backwards compatibility would be a better option. Can't task2 be built in such a way that it can be installed alongside task (task v3). Cheers, -- --Jos Vos --X/OS Experts in Open Systems BV | Office: +31 20 6938364 --Amsterdam, The Netherlands| Mobile: +31 6 26216181 -- ___ 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: F41 Change Proposal - Reproducible Package Builds (System-Wide)
Dne 13. 04. 24 v 21:04 Zbigniew Jędrzejewski-Szmek napsal(a): On Sat, Apr 13, 2024 at 01:38:49PM +, Zbigniew Jędrzejewski-Szmek wrote: On Sat, Apr 13, 2024 at 01:41:59PM +0200, Fabio Valentini wrote: On Sat, Apr 13, 2024 at 1:18 PM Zbigniew Jędrzejewski-Szmek wrote: Yes. But actually I think Rust is the optimal choice here. Writing this in Python would be possibly slightly nicer, but we don't want to pull the interpreter and packages into the buildroot. Python also has the problem (challenge?) that it needs to be bootstrapped once per year. The less packages are involved in the bootstrap, the easier it is. And if the brp was written in Python, we'd need to deal with that, and it would probably increase the number of builds which are done without the cleanup. Having this as an indepedent binary avoids some of the issues with bootstrap. I think Rust *would* be a good choice here ... BUT add-determinism uses pyo3 to link to CPython, so it pulls in python3-libs anyway. So you get the downsides of pulling in Python without the upsides of using Rust ... Yes, it currently pulls in python3-libs as a dependency, but not the rest of the Python stack. Ideally, the dependency on python3-libs will become optional, and we'll use it if found at runtime if found and ignore otherwise. (Anything that creates pyc files will have python installed, so it's fine if the pyc handler only works if there.) How to best do this is something that needs to be figured out… https://github.com/keszybz/add-determinism/pull/1 makes the dependency on libpython optional. One option would be to compile the binary twice, and use rich dependencies to install the heavyweight one if python3 is installed. If somebody has a better approach, I'm all ears. Could you please share some comparison of what is impact on buildroot? How many packages added, download size, install size. Thx a lot Vít OpenPGP_signature.asc Description: OpenPGP digital 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: Updating Taskwarrior to v3
+1 to create task3 but the CLI command is "task". It either needs to rename both like "task2,task3" or conflict old and new ones and prevent installing both of them. -- ___ 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: network service removed in Fedora 40 without a Change proposal(?)
On Sun, Apr 14, 2024 at 08:13:30AM -0700, Adam Williamson wrote: > On Sat, 2024-04-13 at 18:17 -0400, Matthew Miller wrote: > > On Fri, Apr 12, 2024 at 06:00:41PM -0700, Adam Williamson wrote: > > > > This should have been an announced Change. This is a significant > > > > change with wide impact. > > > > > > I've filed a bug, proposed it as a blocker, and filed a FESCo ticket > > > asking FESCo to designate the bug as a blocker. > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2274830 > > > https://pagure.io/fesco/issue/3196 > > > > I admit I was also initially surprised. But, this actually has been going > > through the Change process for a while: > > > > F33: > > https://fedoraproject.org/wiki/Changes/NetworkManager_keyfile_instead_of_ifcfg_rh > > F36: https://fedoraproject.org/wiki/Changes/NoIfcfgFiles > > F39: https://fedoraproject.org/wiki/Changes/MigrateIfcfgToKeyfile > > I would argue that it has not. Those Changes are all about the > NetworkManager plugin that reads ifcfg files. The network service - > /etc/init.d/network - is a different thing. Right, the changes above are about NetworkManager dropping support for reading and writing ifcfg files. There is no direct relation with the network service and its removal. Beniamino > They may be tied together > in the maintainers' minds, I don't know, but they are not tied together > technically and none of those Changes, IMHO, at all clearly conveys > "the network service is going away in Fedora 40". > -- > 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 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: clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu'
On Mon, 15 Apr 2024 10:55:34 +0100 "Richard W.M. Jones" wrote: > > Anyone got any idea about this build failure? > > https://koji.fedoraproject.org/koji/taskinfo?taskID=116395331 > > [+] All set and ready to build. > clang: warning: -Wl,-z,relro: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,--as-needed: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,-z,pack-relative-relocs: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,-z,now: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -Wl,--build-id=sha1: 'linker' input unused > [-Wunused-command-line-argument] > clang: warning: -ldl: 'linker' input unused [-Wunused-command-line-argument] > clang: warning: -lrt: 'linker' input unused [-Wunused-command-line-argument] > clang: warning: -lm: 'linker' input unused [-Wunused-command-line-argument] > clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for > target 'x86_64-redhat-linux-gnu' > > AFAICT -mtls-dialect=gnu2 is not added by anything in the spec file or > in AFL++ sources, so it must be coming from RPM macros? it comes from "x86-64 -mtls-dialect=gnu2 change landed in rawhide", see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/M2SCED77ZDJQ7BHWU5LCRGMUSHV6L3CY/ Dan -- ___ 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: network service removed in Fedora 40 without a Change proposal(?)
On Fri, Apr 12, 2024 at 05:44:36PM -0500, Ian Pilcher wrote: > On 4/12/24 16:46, Adam Williamson wrote: > > it seems since I last looked at this, NM has grown some level of > > openvswitch support, but it seems to be limited, and I don't know off- > > hand if it's sufficient for what openQA needs. I will need to look into > > that. > > https://github.com/NetworkManager/NetworkManager/blob/main/man/nm-openvswitch.xml > > I've attempted to use it on a couple occasions, and I've never been > able to get it to work. It requires creating 3 different objects, Right, that's because the OVS support in NM is modeled after the ovsdb schema, with separate entities for bridges, ports and interfaces. When you create a bridge with 'ovs-vsctl add-br br1', that actually generates 3 objects: # ovs-vsctl show Bridge br1 Port br1 Interface br1 type: internal If there was only a single NM connection profile for the whole bridge, it wouldn't be possible e.g. to attach another interface to port "br1", or to describe more complex setups in a declarative way. > in the correct order, with exactly the right settings. The order shouldn't matter; if it does, that seems a bug. If it helps, "man nm-openvswitch" provides an overview of OVS support in NM. > And AFAIK, it still doesn't support setting the internal port to the > same name as the bridge itself, which is the default behavior of > ovs-vsctl and the network scripts, so it's a disruptive change to the > network configuration even if it can be made to work. This configuration is certainly supported. If you found any problems, please report a bug. Beniamino 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: network service removed in Fedora 40 without a Change proposal(?)
On Mon, Apr 15, 2024 at 10:46:39AM +0200, Lukáš Nykrýn wrote: > Just for record, the removal of network-scripts was done because > https://fedoraproject.org/wiki/Changes/dhclient_deprecation That page has Category:ChangePageIncomplete. dhcp-client is present in F40, even though it has Provides:deprecated(). > Network-scripts heavily depend on dhclient and there is no plan to rework > them to use a different dhcp implementation. Ack. So it sounds like we could keep using both in F40 and prepare for removal in F41. 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
Re: Updating Taskwarrior to v3
Our guidelines suggest that the "main" package should be unversioned, while if needed, the "compat" packages should include version: https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple So if you want to introduce new package, then please introduce `task2` and update the current `task` package to the most recent version. Vít Dne 15. 04. 24 v 12:04 Ankur Sinha napsal(a): On Mon, Apr 15, 2024 09:41:05 -, Onuralp SEZER wrote: +1 to create task3 but the CLI command is "task". It either needs to rename both like "task2,task3" or conflict old and new ones and prevent installing both of them. They are not designed to be installed in parallel, so task3 will obsolete task. However, task3 will not provide the task package, so that task will not be updated to task3 during normal upgrades. Users will have to explicitly install task3. -- ___ 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 OpenPGP_signature.asc Description: OpenPGP digital 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: network service removed in Fedora 40 without a Change proposal(?)
Just for record, the removal of network-scripts was done because https://fedoraproject.org/wiki/Changes/dhclient_deprecation Network-scripts heavily depend on dhclient and there is no plan to rework them to use a different dhcp implementation. ne 14. 4. 2024 v 17:14 odesílatel Adam Williamson < adamw...@fedoraproject.org> napsal: > On Sat, 2024-04-13 at 18:17 -0400, Matthew Miller wrote: > > On Fri, Apr 12, 2024 at 06:00:41PM -0700, Adam Williamson wrote: > > > > This should have been an announced Change. This is a significant > > > > change with wide impact. > > > > > > I've filed a bug, proposed it as a blocker, and filed a FESCo ticket > > > asking FESCo to designate the bug as a blocker. > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2274830 > > > https://pagure.io/fesco/issue/3196 > > > > I admit I was also initially surprised. But, this actually has been going > > through the Change process for a while: > > > > F33: > https://fedoraproject.org/wiki/Changes/NetworkManager_keyfile_instead_of_ifcfg_rh > > F36: https://fedoraproject.org/wiki/Changes/NoIfcfgFiles > > F39: https://fedoraproject.org/wiki/Changes/MigrateIfcfgToKeyfile > > I would argue that it has not. Those Changes are all about the > NetworkManager plugin that reads ifcfg files. The network service - > /etc/init.d/network - is a different thing. They may be tied together > in the maintainers' minds, I don't know, but they are not tied together > technically and none of those Changes, IMHO, at all clearly conveys > "the network service is going away in Fedora 40". > -- > 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
Re: F41 Change Proposal - Reproducible Package Builds (System-Wide)
Dne 13. 04. 24 v 1:16 odp. Zbigniew Jędrzejewski-Szmek napsal(a): The proposal explicitly states that we don't want Perl in all buildroots. How many seconds we save by NOT pulling Perl? Per each build? In total for whole release cycle? How many seconds we loose (lost) by refactoring the code? And syncing with Debian? Or even worse finding issues that Debian will find and we not? -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys -- ___ 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
Updating Taskwarrior to v3
Hi folks, Taskwarrior has recently released version 3.x. While the command line remains the same, this version includes backwards incompatible changes: https://github.com/GothenburgBitFactory/taskwarrior/releases/tag/v3.0.0 https://taskwarrior.org/docs/upgrade-3/ - the user task database format has changed and requires users to manually migrate - it no longer supports taskserver for syncing The upgrade steps say that one must migrate their data base *before* installing task v3. So, this is clearly a backwards incompatible change that requires users intervention. What would be the best way of handling this? I didn't want to just update the package in Fedora. Instead I was thinking of packaging taskwarrior v3 as a new package, task3, that will obsolete the current package but not update it. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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: F41 Change Proposal - Reproducible Package Builds (System-Wide)
Dne 15. 04. 24 v 11:10 Miroslav Suchý napsal(a): Dne 13. 04. 24 v 1:16 odp. Zbigniew Jędrzejewski-Szmek napsal(a): The proposal explicitly states that we don't want Perl in all buildroots. How many seconds we save by NOT pulling Perl? Per each build? In total for whole release cycle? I know that I have saved quite significant time every build. Also having buildroot minimal also makes sure that we have correctly specified explicit dependencies, therefore making the builds more reproducible. IOW adding Perl back into the build root would be against the goal of this change proposal. Vít How many seconds we loose (lost) by refactoring the code? And syncing with Debian? Or even worse finding issues that Debian will find and we not? -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys -- ___ devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-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 OpenPGP_signature.asc Description: OpenPGP digital 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: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 12:53:06 +0200, Vít Ondruch wrote: > Our guidelines suggest that the "main" package should be unversioned, while > if needed, the "compat" packages should include version: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple > > So if you want to introduce new package, then please introduce `task2` and > update the current `task` package to the most recent version. > Hrm, but the problem here is that a user that currently has the task package installed (currently v2) will end up with v3 if I update the task package to v3---which is something we'd like to avoid here. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 12:50:48 +0200, Jos Vos wrote: > Hi, > > On Mon, Apr 15, 2024 at 11:04:22AM +0100, Ankur Sinha wrote: > >They are not designed to be installed in parallel, so task3 will >obsolete task. However, task3 will not provide the task package, so that >task will not be updated to task3 during normal upgrades. Users will >have to explicitly install task3. > > Being a happy taskwarrior user since years: > > Note that users do not always update (full) OS releases, but do > new installs while keeping (a.o.) /home. So, after installing > that new OS release, users will face the same issue. Furthermore, > if they are used to install "task", they will install the wrong > version, even if they may want to use the new version. > > The fact that v3 does *require* a v2 for exporting is of course a > bad thing, they should have added a export-v2 option or so. Will > the task v3 warn users if they detect old data? It won't use the old data format at all. After conversion, if one still has the old data files, it will show warnings: https://taskwarrior.org/docs/upgrade-3/ > > What is the idea? To temporarily provide both packages, v2 and v3, > that can not be installed together? > > About the naming / versioning part: this probably has happened > before with other packages, I am not aware of all the policies. > But I would think that having task2 for backwards compatibility > would be a better option. Can't task2 be built in such a way > that it can be installed alongside task (task v3). They both provide the same binary, but we could perhaps rename the task binary from taskv2 to task2. I've not looked at the rest of the package files yet to be able to say if they'll all require similar mangling to allow taskv2 and taskv3 to be installed in parallel. Theoretically, it should be doable. The issue with updating task to v3 and keeping task2 is that people that aren't aware of the change will end up with a non-functional task installation when the task package is upgraded. They'll have to downgrade to an older version of the package (or install task2), export their data, and then re-upgrade task to make it all work (and sync with taskserver won't work even then, of course). The documentation says "Before installing Taskwarrior 3, export all of your tasks". I haven't tested out what happens if one runs task3 without exporting the data---it shouldn't touch the old data files, but I don't know if it affects the import later. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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: F41 Change Proposal - Reproducible Package Builds (System-Wide)
On Mon, Apr 15, 2024 at 12:59:04PM +0200, Vít Ondruch wrote: > Could you please share some comparison of what is impact on buildroot? How > many packages added, download size, install size. $ rpm -qiR add-determinism-0.2.0-1.fc40.x86_64 ... Size: 2801276 (installed size, 2.7 MB) ... libc.so.6()(64bit) libgcc_s.so.1()(64bit) libbz2.so.1()(64bit) libzstd.so.1()(64bit) libpython3.12.so.1.0()(64bit) ... So I think the size and deps are neglible, with the exception of libpython3, which is large (45 MB). As discussed, we'll make it optional. I amended the Proposal page now to say that explicitly. 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
Re: clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' for target 'x86_64-redhat-linux-gnu'
On Mon, 2024-04-15 at 10:55 +0100, Richard W.M. Jones wrote: > > Anyone got any idea about this build failure? > I think is this bug https://bugzilla.redhat.com/show_bug.cgi?id=2263180 > https://koji.fedoraproject.org/koji/taskinfo?taskID=116395331 > > [+] All set and ready to build. > clang: warning: -Wl,-z,relro: 'linker' input unused [-Wunused- > command-line-argument] > clang: warning: -Wl,--as-needed: 'linker' input unused [-Wunused- > command-line-argument] > clang: warning: -Wl,-z,pack-relative-relocs: 'linker' input unused [- > Wunused-command-line-argument] > clang: warning: -Wl,-z,now: 'linker' input unused [-Wunused-command- > line-argument] > clang: warning: -Wl,--build-id=sha1: 'linker' input unused [-Wunused- > command-line-argument] > clang: warning: -ldl: 'linker' input unused [-Wunused-command-line- > argument] > clang: warning: -lrt: 'linker' input unused [-Wunused-command-line- > argument] > clang: warning: -lm: 'linker' input unused [-Wunused-command-line- > argument] > clang: error: unsupported argument 'gnu2' to option '-mtls-dialect=' > for target 'x86_64-redhat-linux-gnu' > > AFAICT -mtls-dialect=gnu2 is not added by anything in the spec file > or > in AFL++ sources, so it must be coming from RPM macros? > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: > http://rwmj.wordpress.com > virt-builder quickly builds VMs from scratch > http://libguestfs.org/virt-builder.1.html > -- > ___ > 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: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote: Hrm, but the problem here is that a user that currently has the task package installed (currently v2) will end up with v3 if I update the task package to v3---which is something we'd like to avoid here. Just a side question: is this task v3 update planned to be distributed *during* an OS lifecycle or only at the start of a new one (e.g. F41, I assume it is too late for F40 now)? Are there any Fedora policies for this kind of incompatible updates? -- --Jos Vos --X/OS Experts in Open Systems BV | Office: +31 20 6938364 --Amsterdam, The Netherlands| Mobile: +31 6 26216181 -- ___ 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: 20240415.n.0 changes
OLD: Fedora-Rawhide-20240414.n.0 NEW: Fedora-Rawhide-20240415.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 3 Dropped packages:1 Upgraded packages: 57 Downgraded packages: 0 Size of added packages: 125.22 KiB Size of dropped packages:53.10 KiB Size of upgraded packages: 870.91 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -1.20 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: LXQt live aarch64 Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20240415.n.0.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: golang-github-kovidgoyal-imaging-1.6.3-1.fc41 Summary: Imaging is a simple image processing package for Go RPMs:golang-github-kovidgoyal-imaging-devel Size:45.13 KiB Package: rust-jod-thread-0.1.2-1.fc41 Summary: Std::thread which joins on drop by default RPMs:rust-jod-thread+default-devel rust-jod-thread-devel Size:20.92 KiB Package: rust-tracing-tree-0.3.0-1.fc41 Summary: Tracing Layer which prints a tree of spans and events RPMs:rust-tracing-tree+default-devel rust-tracing-tree+time-devel rust-tracing-tree+tracing-log-devel rust-tracing-tree-devel Size:59.17 KiB = DROPPED PACKAGES = Package: rust-pep440_rs0.3-0.3.12-2.fc40 Summary: Library for python version numbers and specifiers, implementing PEP 440 RPMs:rust-pep440_rs0.3+default-devel rust-pep440_rs0.3+serde-devel rust-pep440_rs0.3+tracing-devel rust-pep440_rs0.3-devel Size:53.10 KiB = UPGRADED PACKAGES = Package: NetworkManager-l2tp-1.20.14-1.fc41 Old package: NetworkManager-l2tp-1.20.10-5.fc40 Summary: NetworkManager VPN plugin for L2TP and L2TP/IPsec RPMs: NetworkManager-l2tp NetworkManager-l2tp-gnome Size: 1019.93 KiB Size change: 28.49 KiB Changelog: * Sun Apr 14 2024 Douglas Kosovic - 1.20.14-1 - Updated to 1.20.14 release Package: ansible-packaging-1-15.fc41 Old package: ansible-packaging-1-14.fc40 Summary: RPM packaging macros and generators for Ansible collections RPMs: ansible-packaging ansible-packaging-tests ansible-srpm-macros Size: 42.99 KiB Size change: 991 B Changelog: * Sat Feb 10 2024 Maxwell G - 1-15 - %ansible_test_unit: handle test dependencies on other collections Package: castxml-0.6.5-1.fc41 Old package: castxml-0.6.4-2.fc41 Summary: C-family abstract syntax tree XML output tool RPMs: castxml Size: 3.24 MiB Size change: -637 B Changelog: * Mon Apr 15 2024 Mattias Ellert - 0.6.5-1 - Update to version 0.6.5 Package: fedora-release-41-0.9 Old package: fedora-release-41-0.6 Summary: Fedora release files RPMs: fedora-release fedora-release-budgie fedora-release-budgie-atomic fedora-release-cinnamon fedora-release-cloud fedora-release-common fedora-release-compneuro fedora-release-container fedora-release-coreos fedora-release-designsuite fedora-release-i3 fedora-release-identity-basic fedora-release-identity-budgie fedora-release-identity-budgie-atomic fedora-release-identity-cinnamon fedora-release-identity-cloud fedora-release-identity-compneuro fedora-release-identity-container fedora-release-identity-coreos fedora-release-identity-designsuite fedora-release-identity-i3 fedora-release-identity-iot fedora-release-identity-kde fedora-release-identity-kinoite fedora-release-identity-lxqt fedora-release-identity-matecompiz fedora-release-identity-mobility fedora-release-identity-server fedora-release-identity-silverblue fedora-release-identity-snappy fedora-release-identity-soas fedora-release-identity-sway fedora-release-identity-sway-atomic fedora-release-identity-toolbx fedora-release-identity-workstation fedora-release-identity-xfce fedora-release-iot fedora-release-kde fedora-release-kinoite fedora-release-lxqt fedora-release-matecompiz fedora-release-mobility fedora-release-ostree-desktop fedora-release-server fedora-release-silverblue fedora-release-snappy fedora-release-soas fedora-release-sway fedora-release-sway-atomic fedora-release-toolbx fedora-release-workstation fedora-release-xfce Size: 627.25 KiB Size change: 16.26 KiB Changelog: * Wed Feb 28 2024 Yaakov Selkowitz - 41-0.7 - ELN: drop wget and zlib hints * Wed Feb 28 2024 Yaakov Selkowitz - 41-0.8 - ELN: switch default Java to 21 * Fri Apr 12 2024 Paul Whalen - 41-0.9 - IoT: enable fdo-client-linuxapp.service Package: ga-5.8.2-7.fc41 Old package: ga-5.8.2-5.fc40 Summary: Global Arrays Toolkit RPMs: ga-common ga-mpich ga-mpich-devel ga-mpich-static ga-openmpi ga-openmpi-devel ga-openmpi-static Size: 5.72 MiB Size change: -6.24 KiB Changelog: * Thu Apr 11 2024 Jiasheng Zhao - 5.8.2-6 - Add riscv64 support * Sun Apr 14 2024 Marcin Dulak - 5.8.2-7 - Correct shell continuation to be && instead of ; - Use make macros - https://fedoraproject.org/wiki
Re: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 14:18:59 +0200, Jos Vos wrote: > On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote: > >Hrm, but the problem here is that a user that currently has the task >package installed (currently v2) will end up with v3 if I update the >task package to v3---which is something we'd like to avoid here. > > Just a side question: is this task v3 update planned to be distributed > *during* an OS lifecycle or only at the start of a new one (e.g. F41, > I assume it is too late for F40 now)? Are there any Fedora policies > for this kind of incompatible updates? The general policy is to not introduce backwards incompatible changes to stable releases: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases I am thinking that the best way for this would be to announce it as a self-contained change so it'll land in rawhide (F41). In the meantime, I can perhaps keep a COPR repository for stable Fedora releases (F39/F40) for users that do want to use taskv3 already. https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_self_contained_changes How does that sound? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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 2275122] New: perl-Parse-PMFile-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275122 Bug ID: 2275122 Summary: perl-Parse-PMFile-0.46 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Parse-PMFile Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mspa...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 0.46 Upstream release that is considered latest: 0.46 Current version/release in rawhide: 0.45-1.fc40 URL: https://metacpan.org/dist/Parse-PMFile/ 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/3195/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Parse-PMFile -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275122 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275122%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
[Bug 2275122] perl-Parse-PMFile-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275122 --- Comment #2 from Fedora Update System --- FEDORA-2024-3101c3959e (perl-Parse-PMFile-0.46-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3101c3959e -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275122 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275122%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 2275122] perl-Parse-PMFile-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275122 Jitka Plesnikova changed: What|Removed |Added CC|jples...@redhat.com,| |mspa...@redhat.com | Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275122 -- ___ 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 2275122] perl-Parse-PMFile-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275122 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Parse-PMFile-0.46-1.fc ||41 Status|MODIFIED|CLOSED Resolution|--- |ERRATA Last Closed||2024-04-15 14:42:25 --- Comment #3 from Fedora Update System --- FEDORA-2024-6560693658 (perl-Parse-PMFile-0.46-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=2275122 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275122%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 2274529] perl-ExtUtils-HasCompiler-0.024 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2274529 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2024-43744da256 (perl-ExtUtils-HasCompiler-0.024-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-43744da256 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2274529 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202274529%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
[Bug 2274529] perl-ExtUtils-HasCompiler-0.024 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2274529 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Fixed In Version||perl-ExtUtils-HasCompiler-0 ||.024-1.fc41 Resolution|--- |ERRATA Last Closed||2024-04-15 14:03:40 --- Comment #2 from Fedora Update System --- FEDORA-2024-43744da256 (perl-ExtUtils-HasCompiler-0.024-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=2274529 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202274529%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 2275122] perl-Parse-PMFile-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275122 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2024-6560693658 (perl-Parse-PMFile-0.46-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-6560693658 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275122 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275122%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
[Bug 2275134] New: Upgrade perl-Crypt-OpenSSL-Random to 0.16
https://bugzilla.redhat.com/show_bug.cgi?id=2275134 Bug ID: 2275134 Summary: Upgrade perl-Crypt-OpenSSL-Random to 0.16 Product: Fedora Version: rawhide URL: https://metacpan.org/release/Crypt-OpenSSL-Random Status: NEW Component: perl-Crypt-OpenSSL-Random Assignee: wjhns...@hardakers.net Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, wjhns...@hardakers.net Target Milestone: --- Classification: Fedora Latest Fedora delivers 0.15 version. Upstream released 0.16. 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=2275134 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275134%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 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f060b59d26
perl-Clipboard-0.29-1.el8
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-762aef7cb1
chromium-123.0.6312.122-1.el8
The following builds have been pushed to Fedora EPEL 8 updates-testing
castxml-0.6.5-1.el8
snapd-2.62-0.el8
tio-2.8-1.el8
Details about builds:
castxml-0.6.5-1.el8 (FEDORA-EPEL-2024-d2fe54e367)
C-family abstract syntax tree XML output tool
Update Information:
CastXML 0.6.5
ChangeLog:
* Mon Apr 15 2024 Mattias Ellert - 0.6.5-1
- Update to version 0.6.5
* Wed Mar 6 2024 Mattias Ellert - 0.6.4-2
- Backport LLVM 18 support from upstream
References:
[ 1 ] Bug #2274886 - castxml-0.6.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2274886
snapd-2.62-0.el8 (FEDORA-EPEL-2024-27362990ef)
A transactional software package manager
Update Information:
New upstream release 2.62
ChangeLog:
* Thu Mar 21 2024 Ernest Lotter
- New upstream release 2.62
- Aspects based configuration schema support (experimental)
- Refresh app awareness support for UI (experimental)
- Support for user daemons by introducing new control switches
--user/--system/--users for service start/stop/restart
(experimental)
- Add AppArmor prompting experimental flag (feature currently
unsupported)
- Installation of local snap components of type test
- Packaging of components with snap pack
- Expose experimental features supported/enabled in snapd REST API
endpoint /v2/system-info
- Support creating and removing recovery systems for use by factory
reset
- Enable API route for creating and removing recovery systems using
/v2/systems with action create and /v2/systems/{label} with action
remove
- Lift requirements for fde-setup hook for single boot install
- Enable single reboot gadget update for UC20+
- Allow core to be removed on classic systems
- Support for remodeling on hybrid systems
- Install desktop files on Ubuntu Core and update after snapd
upgrade
- Upgrade sandbox features to account for cgroup v2 device filtering
- Support snaps to manage their own cgroups
- Add support for AppArmor 4.0 unconfined profile mode
- Add AppArmor based read access to /etc/default/keyboard
- Upgrade to squashfuse 0.5.0
- Support useradd utility to enable removing Perl dependency for
UC24+
- Support for recovery-chooser to use console-conf snap
- Add support for --uid/--gid using strace-static
- Add support for notices (from pebble) and expose via the snapd
REST API endpoints /v2/notices and /v2/notice
- Add polkit authentication for snapd REST API endpoints
/v2/snaps/{snap}/conf and /v2/apps
- Add refresh-inhibit field to snapd REST API endpoint /v2/snaps
- Add refresh-inhibited select query to REST API endpoint /v2/snaps
- Take into account validation sets during remodeling
- Improve offline remodeling to use installed revisions of snaps to
fulfill the remodel revision requirement
- Add rpi configuration option sdtv_mode
- When snapd snap is not installed, pin policy ABI to 4.0 or 3.0 if
present on host
- Fix gadget zero-sized disk mapping caused by not ignoring zero
sized storage traits
- Fix gadget install case where size of existing partition was not
correctly taken into account
- Fix trying to unmount early kernel mount if it does not exist
- Fix restarting mount units on snapd start
- Fix call to udev in preseed mode
- Fix to ensure always setting up the device cgroup for base bare
and core24+
- Fix not copying data from newly set homedirs on revision change
- Fix leaving behind empty snap home directories after snap is
removed (resulting in broken symlink)
- Fix to avoid using libzstd from host by adding to snapd snap
- Fix autorefresh to correctly handle forever refresh hold
- Fix username regex allowed for system-user assertion to not allow
'+'
- Fix incorrect application icon for notification after autorefresh
completion
- Fix to restart mount units when changed
- Fix to support AppArmor running under incus
- Fix case of snap-update-ns dropping synthetic mounts due to
failure to match desired mount dependencies
- Fix parsing of base snap version to enable pre-seeding of Ubuntu
Core
[Bug 2275216] New: perl-Net-Whois-Raw-2.99039 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275216 Bug ID: 2275216 Summary: perl-Net-Whois-Raw-2.99039 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Net-Whois-Raw Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 2.99039 Upstream release that is considered latest: 2.99039 Current version/release in rawhide: 2.99.038-1.fc41 URL: https://metacpan.org/dist/Net-Whois-Raw 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/6677/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Net-Whois-Raw -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275216 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275216%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
[Bug 2275188] New: perl-Socket-2.038 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275188 Bug ID: 2275188 Summary: perl-Socket-2.038 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Socket Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mspa...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 2.038 Upstream release that is considered latest: 2.038 Current version/release in rawhide: 2.037-5.fc40 URL: https://metacpan.org/dist/Socket/ 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/3321/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Socket -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275188 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275188%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
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-a8b1cd8e52
perl-Clipboard-0.29-1.el7
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-9bc8e80200
chromium-123.0.6312.122-1.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
snapd-2.62-0.el7
tio-2.8-1.el7
Details about builds:
snapd-2.62-0.el7 (FEDORA-EPEL-2024-e153bfdcaf)
A transactional software package manager
Update Information:
New upstream release 2.62
ChangeLog:
* Thu Mar 21 2024 Ernest Lotter
- New upstream release 2.62
- Aspects based configuration schema support (experimental)
- Refresh app awareness support for UI (experimental)
- Support for user daemons by introducing new control switches
--user/--system/--users for service start/stop/restart
(experimental)
- Add AppArmor prompting experimental flag (feature currently
unsupported)
- Installation of local snap components of type test
- Packaging of components with snap pack
- Expose experimental features supported/enabled in snapd REST API
endpoint /v2/system-info
- Support creating and removing recovery systems for use by factory
reset
- Enable API route for creating and removing recovery systems using
/v2/systems with action create and /v2/systems/{label} with action
remove
- Lift requirements for fde-setup hook for single boot install
- Enable single reboot gadget update for UC20+
- Allow core to be removed on classic systems
- Support for remodeling on hybrid systems
- Install desktop files on Ubuntu Core and update after snapd
upgrade
- Upgrade sandbox features to account for cgroup v2 device filtering
- Support snaps to manage their own cgroups
- Add support for AppArmor 4.0 unconfined profile mode
- Add AppArmor based read access to /etc/default/keyboard
- Upgrade to squashfuse 0.5.0
- Support useradd utility to enable removing Perl dependency for
UC24+
- Support for recovery-chooser to use console-conf snap
- Add support for --uid/--gid using strace-static
- Add support for notices (from pebble) and expose via the snapd
REST API endpoints /v2/notices and /v2/notice
- Add polkit authentication for snapd REST API endpoints
/v2/snaps/{snap}/conf and /v2/apps
- Add refresh-inhibit field to snapd REST API endpoint /v2/snaps
- Add refresh-inhibited select query to REST API endpoint /v2/snaps
- Take into account validation sets during remodeling
- Improve offline remodeling to use installed revisions of snaps to
fulfill the remodel revision requirement
- Add rpi configuration option sdtv_mode
- When snapd snap is not installed, pin policy ABI to 4.0 or 3.0 if
present on host
- Fix gadget zero-sized disk mapping caused by not ignoring zero
sized storage traits
- Fix gadget install case where size of existing partition was not
correctly taken into account
- Fix trying to unmount early kernel mount if it does not exist
- Fix restarting mount units on snapd start
- Fix call to udev in preseed mode
- Fix to ensure always setting up the device cgroup for base bare
and core24+
- Fix not copying data from newly set homedirs on revision change
- Fix leaving behind empty snap home directories after snap is
removed (resulting in broken symlink)
- Fix to avoid using libzstd from host by adding to snapd snap
- Fix autorefresh to correctly handle forever refresh hold
- Fix username regex allowed for system-user assertion to not allow
'+'
- Fix incorrect application icon for notification after autorefresh
completion
- Fix to restart mount units when changed
- Fix to support AppArmor running under incus
- Fix case of snap-update-ns dropping synthetic mounts due to
failure to match desired mount dependencies
- Fix parsing of base snap version to enable pre-seeding of Ubuntu
Core Desktop
- Fix packaging and tests for various distributions
- Add remoteproc interface to allow developers to interact with
Remote Processor Framework which enables snaps to load firmware to
ARM Cortex microcontrollers
- Add kernel-control interface to enable controlling the kernel
firmware search path
- Add nfs-mount interface to allow mounting of NFS shares
- Add ros-opt-data interface to allow snaps to access the host
/opt/ros/ paths
- Add snap-refresh-observe interface that provides refresh-app-
awareness clients access to relevant snapd API endpoints
- steam-support interface: generalize Pressure Vessel root paths and
allow access to driver information, features and container
versions
- steam-support interface: make implicit on Ubuntu Core Desktop
- desktop interface: improved support for Ubuntu Core Desktop and
[Bug 2222637] F39FailsToInstall: perl-Syntax-Feature-Loop
https://bugzilla.redhat.com/show_bug.cgi?id=637 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #9 from Fedora Update System --- FEDORA-2024-f3032015a3 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-f3032015a3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f3032015a3 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=637 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20637%23c9 -- ___ 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 2275122] perl-Parse-PMFile-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275122 --- Comment #4 from Fedora Update System --- FEDORA-2024-3101c3959e 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-3101c3959e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3101c3959e 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=2275122 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275122%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 2222637] F39FailsToInstall: perl-Syntax-Feature-Loop
https://bugzilla.redhat.com/show_bug.cgi?id=637 --- Comment #10 from Fedora Update System --- FEDORA-2024-684108482c has been pushed to the Fedora 39 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-684108482c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-684108482c 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=637 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20637%23c10 -- ___ 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 2222637] F39FailsToInstall: perl-Syntax-Feature-Loop
https://bugzilla.redhat.com/show_bug.cgi?id=637 --- Comment #8 from Fedora Update System --- FEDORA-2024-684108482c (fedora-obsolete-packages-39-22) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-684108482c -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=637 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20637%23c8 -- ___ 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 2222637] F39FailsToInstall: perl-Syntax-Feature-Loop
https://bugzilla.redhat.com/show_bug.cgi?id=637 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #7 from Fedora Update System --- FEDORA-2024-f3032015a3 (fedora-obsolete-packages-40-29) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-f3032015a3 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=637 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20637%23c7 -- ___ 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-Task-Catalyst] PR #1: Stop building for 32-bit x86
ppisar commented on the pull-request: `Stop building for 32-bit x86` that you are following: `` I see. Could you please mention flamegraph in the commit message? E.g. "Stop building for 32-bit x86 because of flamegraph". `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Task-Catalyst/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
[Bug 2184301] perl-Syntax-Feature-Loop-1.8.0-18.fc39 FTBFS: t/01_basic.t and 3 more tests fail
https://bugzilla.redhat.com/show_bug.cgi?id=2184301 Petr Pisar changed: What|Removed |Added CC||ppi...@redhat.com --- Comment #9 from Petr Pisar --- This package was removed from Fedora since Fedora release 40. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184301 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202184301%23c9 -- ___ 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 2222637] F39FailsToInstall: perl-Syntax-Feature-Loop
https://bugzilla.redhat.com/show_bug.cgi?id=637 Petr Pisar changed: What|Removed |Added Assignee|extras-orphan@fedoraproject |ppi...@redhat.com |.org| Status|NEW |ASSIGNED --- Comment #6 from Petr Pisar --- This package was removed from Fedora since Fedora release 40. Because it was last built in Fedora 38 against Perl 5.36, and not rebuilt for Perl 5.38 in Fedora 39 (bug #2184301), this package cannot be installed in Fedora 39. Because that can prevent users from upgrading from Fedora 38 to Fedora 39, this package will be obsoleted by fedora-obsolete-packages there. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=637 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20637%23c6 -- ___ 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 2222637] F39FailsToInstall: perl-Syntax-Feature-Loop
https://bugzilla.redhat.com/show_bug.cgi?id=637 Petr Pisar changed: What|Removed |Added Fixed In Version||fedora-obsolete-packages-40 ||-29 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=637 -- ___ 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-AnyEvent-I3] PR #1: Fix URL
jplesnik merged a pull-request against the project: `perl-AnyEvent-I3` that you are following. Merged pull-request: `` Fix URL `` https://src.fedoraproject.org/rpms/perl-AnyEvent-I3/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
[Bug 2274529] perl-ExtUtils-HasCompiler-0.024 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2274529 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2274529 -- ___ 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 2274116] perl-AnyEvent-I3-0.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2274116 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2024-b4a2afd31d (perl-AnyEvent-I3-0.19-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-b4a2afd31d -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2274116 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202274116%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
[Bug 2274116] perl-AnyEvent-I3-0.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2274116 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA Fixed In Version||perl-AnyEvent-I3-0.19-1.fc4 ||1 Last Closed||2024-04-15 13:00:25 --- Comment #2 from Fedora Update System --- FEDORA-2024-b4a2afd31d (perl-AnyEvent-I3-0.19-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=2274116 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202274116%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
