Re: 41 Change Proposal: Make Tuned the Default Power Profile Management Daemon (System-Wide)
Just a note. Users of DEs other than KDE and GNOME can use the Tuned Switcher app. Available both in the main Fedora repository and as a Flatpak: - sudo dnf install tuned-switcher - flatpak install org.easycoding.TunedSwitcher -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding additional flag in cmake-rpm-macros to disallow the use of the FetchContent module
On 27/05/2024 02:22, Byoungchan Lee via devel wrote: In well-maintained Fedora packages, the use of the FetchContent module is generally discouraged because dependencies are already available in the Fedora repositories. FetchContent never worked on Fedora because the builders have no network access. The maintainers have to patch it out. Check this for example: https://github.com/eliaskosunen/scnlib/pull/112 While it's uncertain if build workers in Fedora have internet access, to improve security, I believe it is recommended to entirely disallow the use of the FetchContent module. To achieve this, I propose adding a flag in the cmake-rpm-macros to disable the FetchContent module. Tried it several times, but it doesn't work reliably and in very rare cases. The library name in FetchContent() must match the name in find_package(), which almost never happens in real projects. It will instantly fail but with another error. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Adding additional flag in cmake-rpm-macros to disallow the use of the FetchContent module
On 27/05/2024 02:46, Kan-Ru Chen wrote: It is documented that FIND_PACKAGE_ARGS argument in FetchContent_Declare should instruct it to find system packages first. This only works as expected in very rare cases. The library name in FetchContent() must match the name in find_package(). This is probably going to break packages. I think a change proposal would be good. No, this won't break anything since Fedora builders have no network access and all FetchContent() calls will fail instantly. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Kernel 6.9 Test Week 2024-05-26 to 2024-06-02
On 26/05/2024 12:36, Alicja Brook wrote: As usual, the Fedora QA team will hangout at #fedora-test-day(a)libera.chat The LiberaChat Matrix gate has been closed and all chats are now only available in Matrix. You should replace all links with #fedora-test-day:fedoraproject.org. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: oneapi-level-zero requires cloned spdlog-populate
On 23/05/2024 02:02, Luya Tshimbalanga wrote: Upstream made a change that requires cloning a sub-directory spdlog-populate leading to a failure to build. What will be an alternative to address that issue? You need to patch it and submit a pull request to upstream. Check this example: https://github.com/eliaskosunen/scnlib/pull/112 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Schedule for Monday's FESCo Meeting (2024-05-20)
On 21/05/2024 22:59, Miro Hrončok wrote: I am a tad sad that this was approved by FESCo without being first discussed with the wider community. We have another similar issue: https://pagure.io/fesco/issue/3205 This was also not discussed. Intel wants to include pre-built blobs to the repository: From an end user POV it would have no functional benefit either, since distros would not be permitted to make any source changes. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing spdlog soversion bump
On 21/05/2024 15:30, Vitaly Zaitsev wrote: spdlog 1.14.1 will include a soversion bump from .1.12 to .1.14. Completed and pushed to Rawhide. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal - Reproducible Package Builds (System-Wide)
On 17/04/2024 09:20, Zbigniew Jędrzejewski-Szmek wrote:
In some ways, that'd be nice, because we wouldn't have to install
additional tools in the buildroot. But OTOH, those tools are rather
small and bash/find/etc probably need to be installed anyway.
It doesn't seem to work properly without the marshalparser Python
package installed:
+ /usr/bin/add-determinism --brp -j48
/builddir/build/BUILDROOT/nheko-0.11.3-11.fc41.x86_64
Cannot initialize handler pyc: ModuleNotFoundError: No module named
'marshalparser'
[src/multiprocess.rs:66:9] = Command {
program: "/usr/bin/add-determinism",
args: [
"/usr/bin/add-determinism",
"--socket",
"3",
"--brp",
"--handler",
"ar,jar,javadoc",
],
env: CommandEnv {
clear: false,
vars: {
"SOURCE_DATE_EPOCH": Some(
"1716249600",
),
},
},
create_pidfd: false,
}
Bye!
Bye!
Bye!
Bye!
Also, is it possible to suppress these "Bye!" messages?
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: LLVM Packaging Ideas for Fedora 41
On 22/05/2024 01:45, Tom Stellard wrote:
I looked in the iwyu source, and it's not using ${LLVM_LIBRARY_DIR}
correctly.
That variable points to where the libraries are installed, but iwyu is
using it to look
up the resource directory. iwyu should be using `clang
-print-resource-dir`
instead.
Can you submit a pull request with a fix to upstream?
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: LLVM Packaging Ideas for Fedora 41
On 27/04/2024 06:34, Tom Stellard wrote:
If anyone has any feedback on these ideas we'd like to hear it and are
happy to discuss
these more.
Can you fix the ${LLVM_LIBRARY_DIR} variable in LLVM's CMake config?
It broke after switching LLVM to use /usr/lib. It still points to
/usr/lib64 and we need to patch it manually[1].
[1]: https://src.fedoraproject.org/rpms/iwyu/blob/rawhide/f/iwyu.spec#_51
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Announcing spdlog soversion bump
Hello all. spdlog 1.14.1 will include a soversion bump from .1.12 to .1.14. Affected packages (including spdlog-devel and virtual cmake(spdlog) and pkgconfig(spdlog)): - bear - coeurl - corectrl - cryfs - CuraEngine - freeopcua - gerbera - gnuradio - gqrx - gr-air-modes - gr-funcube - gr-hpsdr - gr-iqbal - gr-osmosdr - gr-rds - libixion - libmamba - luxcorerender - mangohud - mtxclient - nheko - opae - sdrpp - wasmedge - waybar -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Firefox 126.0 with DBus service
On 17/05/2024 11:04, Martin Stransky wrote: I see. I don't think it's useful for gnome search as it uses live data (also from recently visited URL) and also sorts results for popularity. It should give you the same results as writing directly to Firefox URL bar. This is not a problem because *.sqlite databases can be opened in read-only mode. This won't conflict with the running instance of Firefox. I expect Firefox fails to quit for some reason but as it's connected to DBus service (as it's launched from it) so you see it as a part of it. But I bet you'll get the same results (ff hang) without the service. First I'll try to reproduce it on different machines (including virtual machines). -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Firefox 126.0 with DBus service
On 17/05/2024 10:38, Martin Stransky wrote: Hm, does really KDE Plasma access Firefox profile and searches it for anything? That's interesting. Can you point me to any info about it? It looks like it copies Firefox's *.sqlite databases to ~/.cache/bookmarksrunner on every user login and then uses them: $ ls ~/.cache/bookmarksrunner/ | grep firefox bookmarkrunnerfirefoxdbfile.sqlite bookmarkrunnerfirefoxfavdbfile.sqlite KRunner-Favicons-firefox-default I see it takes 24064 bytes only as it's just a simple and small DBus service. Does it really take 1GB on your box? Other people in the Bodhi update ticket have the same problem. Firefox appears to be unable to shut down properly and continues to run in full mode. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Firefox 126.0 with DBus service
On 17/05/2024 08:05, Martin Stransky wrote: Gnome search service is provided by running Firefox application itself. It's because it searches and publishes results from recent live user profile. Why can't GNOME Search engine just parse Firefox's *.sqlite databases like everyone else does (like KDE Plasma)? It's more simple and easy. So if we have Firefox without Gnome search service / DBus service we'd need different .desktop file with 'DBusActivatable=false' for it (as AFAIK rpm doesn't allow to overwrite file owned by different package). W should start providing it as a separate desktop file, since Firefox is now always running in the background and consuming more than 1GB of RAM. User can't even easily terminate this process without disabling the service. If you SIGKILL, systemd will spawn it again. And the service can't be disabled/masked too because Firefox doesn't start. So it's a bit complicated situation here. I think it's clumsy to have firefox-gnome and firefox-non-gnome rpm with different desktop files but I don't see any other option (beside to remove gnome search or implement it as different app and broker the search results). 1. Provide a standard shortcut without DBusActivatable and with NotShowIn=gnome for all other DEs in the firefox package. 2. Create a separate package with gnome-search related files (including a .service file and a special shortcut with OnlyShowIn=gnome). 3. Install this package only if the gnome-shell is installed. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Firefox 126.0 with DBus service
On 15/05/2024 10:52, Ian McInerney via devel wrote: What if I don't use GNOME search? I don't use the GNOME desktop, so I don't want to have a random Firefox process running on my machine that is doing absolutely nothing and just hogging resources. Is this process only created when something tries to talk to it on the DBus socket, or is it always there listening? Yes, it should be moved to a separate package and installed only if the gnome-shell is installed. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: GIMP 3.0 in F41?
On 13/05/2024 13:24, Nils Philippsen wrote: If I’m not off track, renaming the existing version to “gimp2” would at least make people install it as an update to “gimp-2.10.x” without any real benefit to them. And it would make ”gimp” jump to version 3 which is wildly different Fedora is a bleeding edge distribution. All packages should be updated to the latest releases. and would probably go against package compatibility guidelines if done in Fedora <= 40 Major updates in stable Fedora releases are prohibited by the Updates Policy[1]. [1]: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: GIMP 3.0 in F41?
On 13/05/2024 00:58, Sérgio Basto wrote: https://src.fedoraproject.org/rpms/gimp3 The gimp package should be updated to 3.0, and the existing 2.x version should move to the gimp2 compatibility package. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: LLVM Packaging Ideas for Fedora 41
On 13/05/2024 15:41, Vít Ondruch wrote: we can spent time adjusting upstream projects to be compatible with the latest llvm Feel free to start with pocl. It still doesn't support LLVM 18. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: LLVM Packaging Ideas for Fedora 41
On 29/04/2024 16:41, Gary Buhrmaster wrote: Do we have any idea how many code bases are actually sensitive to the specific llvm version? Both of my LLVM dependent packages: iwyu and pocl. On every LLVM major release they break and I have to wait for the upstream to release a new version. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)
On 26/07/2023 11:24, Alexander Ploumistos wrote: What Dominik wrote would apply e.g. for an NVMe replacement drive from Kingston or Samsung (proprietary hardware too, it's a shocker). None of my 5 Samsung SSDs are supported (3 NVMe and 2 SATA). But they can be updated from MS Windows. I guess only built-in Samsung OEM drives can be updated with fwupd. And thanks to fwupd and Logitech's embracing it, we had the fix in a very short time. It has only been partially fixed. A complete fix would require replacing all existing hardware: Mengs says this vulnerability exists due to an incomplete fix for CVE-2016-10761, one of the infamous MouseJack vulnerabilities, and that Logitech has no plans on patching this new attack variation. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)
On 26/07/2023 11:04, Dominik 'Rathann' Mierzejewski wrote: You could, for example, buy a supported Logitech Receiver I don't recommend anyone to buy this proprietary hardware: The vulnerabilities allow attackers to sniff on keyboard traffic, but also inject keystrokes (even into dongles not connected to a wireless keyboard) and take over the computer to which a dongle has been connected. https://www.zdnet.com/article/logitech-wireless-usb-dongles-vulnerable-to-new-hijacking-flaws/ -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)
On 26/07/2023 10:32, Daniel P. Berrangé wrote: Those devices which do support fwupd have a large enough market share that it is justifiable to enable it, even if there are many machines which can't support it. Maybe Anaconda should only enable it if the device is supported? This information can be easily extracted from "fwupdmgr get-devices --json" output. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)
On 26/07/2023 08:48, Dominik 'Rathann' Mierzejewski wrote: Define small. Only Dell, HP and Lenovo laptops are fully supported: https://fwupd.org/lvfs/devices/ fwupd is a great tool on laptops but completely useless on desktops since no motherboard vendors support it. Maybe fwupd should start packaging UEFI BIOS images for desktop motherboards without vendor assistance? Images in BIN format can be easily downloaded from official websites or extracted from MS Windows packages. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaned packages looking for new maintainers
On 25/07/2023 12:35, Hans de Goede wrote: How do I proceed with this ? Should I run "fedpkg retire" for these 4, or is orphaning them preferred ? Orphaned packages will be retired automatically if no one adopts them after 4 weeks. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: speed-dreams-2.3.0: how to handle bundled jar files in spec file ?
On 25/07/2023 10:18, Martin Gansser wrote: that is, remove the jar files from the speed-dreams package and link to the Fedora jar files in the spec file. JAR files must be compiled from sources. Bundled precompiled files must be removed in %prep. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Restricting automounting of uncommon filesystems?
On 22/07/2023 08:01, Matthew Garrett wrote: 1) Automounting of removable media exposes the kernel to a lot of untrusted input Disable automatic mount by default. Problem solved. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]
On 14/07/2023 08:16, Carlos Rodriguez-Fernandez wrote: After much discussion, the AlmaLinux OS Foundation board today has decided to drop the aim to be 1:1 with RHEL. AlmaLinux OS will instead aim to be Application Binary Interface (ABI) compatible* Imagine Red Hat shutting down CentOS Stream in a year or two just because they [Alma, etc.] started doing rebuilds. :-D -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 10/07/2023 20:16, Demi Marie Obenour wrote: In that case it should be removed from the distribution. Can KDE mail clients be built without QtWebEngine? This would disable HTML email support, but plain text mail might still work. I doubt. But last year I disabled QtWebEngine in Psi and Psi+ Jabber clients. More generally, WebKit is the only major browser engine with upstream support for being embedded, so it is the only embedded browser engine that is supportable security-wise. Telegram Desktop uses WebKitGTK instead of QtWebEngine. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 10/07/2023 02:49, Demi Marie Obenour wrote: QtWebEngine (used by Falkon) was a month or more behind upstream Chromium last I checked. Qt5QtWebEngine is an extremely vulnerable thing. It still uses Chromium 87.0[1]. Current Chromium version: 105.0. [1]: https://wiki.qt.io/QtWebEngine/ChromiumVersions -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 09/07/2023 08:59, Mattia Verga via devel wrote: BTW in the spirit of openness, I've set up a poll (UNOFFICIAL) to clearly state community sentiment about enabling OPT-OUT metrics to FESCO: https://discussion.fedoraproject.org/t/unofficial-poll-about-opt-out-metrics-proposal/85494 Just a simple question and a YES/NO reply. Sorry, but we can't trust **ANONYMOUS** vote on a third-party platform. Admins or other people with access to host can easily edit SQL database and set 100500 votes for variant YES there. You have already received a lot of feedback in several threads. FESCO can count these replies. Most of them overwhelmingly oppose this change. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 09/07/2023 08:59, Mattia Verga via devel wrote: Can we please stop implying malevolence every time we don't agree with something? What malevolence? All 4 of my replies are gone from the main thread. I can treat this as a censoring attempt by the RH staff. This is absolutely unacceptable for free projects like Fedora. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing spdlog soversion bump
On 08/07/2023 19:50, Vitaly Zaitsev wrote: I will use my PP rights to rebuild them in a side tag for Rawhide. The side tag has been merged: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ff83d4f4aa FTBFS: cryfs (Python 3.12 issue: AttributeError: module 'configparser' has no attribute 'SafeConfigParser') gqrx (Python 3.12 issue: nothing provides python(abi) = 3.11 needed by gr-osmosdr-0.2.4-5.fc39.x86_64) gr-air-modes (Python 3.12 issue: nothing provides python3.11dist(numpy) >= 1.20 needed by python3-pyqtgraph-0.13.3-2.fc39.noarch) gr-funcube (Python 3.12 issue: nothing provides python3.11dist(numpy) >= 1.20 needed by python3-pyqtgraph-0.13.3-2.fc39.noarch) gr-hpsdr (Python 3.12 issue: nothing provides python3.11dist(numpy) >= 1.20 needed by python3-pyqtgraph-0.13.3-2.fc39.noarch) gr-iqbal (Python 3.12 issue: nothing provides python3.11dist(numpy) >= 1.20 needed by python3-pyqtgraph-0.13.3-2.fc39.noarch) gr-osmosdr (Python 3.12 issue: nothing provides python3.11dist(numpy) >= 1.20 needed by python3-pyqtgraph-0.13.3-2.fc39.noarch) gr-rds (Python 3.12 issue: nothing provides python3.11dist(numpy) >= 1.20 needed by python3-pyqtgraph-0.13.3-2.fc39.noarch) luxcorerender (Python 3.12 issue: nothing provides python(abi) = 3.11 needed by python3-shiboken2-devel-1:5.15.7-2.fc38.x86_64) mangohud (not related to spdlog or fmt; issue with latest Vulkan libs) -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Announcing spdlog soversion bump
Hello all. spdlog 1.12.0 will include a soversion bump from .1.11 to .1.12. Affected packages (including spdlog-devel and virtual cmake(spdlog) and pkgconfig(spdlog)): - bear - coeurl - cryfs - CuraEngine - freeopcua - gerbera - gnuradio - gqrx - gr-air-modes - gr-funcube - gr-hpsdr - gr-iqbal - gr-osmosdr - gr-rds - libixion - luxcorerender - mangohud - mtxclient - nheko - opae - sdrpp - wasmedge - waybar I will use my PP rights to rebuild them in a side tag for Rawhide. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 06/07/2023 18:10, Aoife Moloney wrote: but the conversation about each change will take place on Fedora Discussion at https://discussion.fedoraproject.org/t/f40-change-request-privacy-preserving-telemetry-for-fedora-workstation-system-wide/85320 It looks like they've started moving replies they don't like to other threads to cover up the flow of resentment that comes naturally to them. That's why switching to Fedora Discussion from the mailing lists is a very bad idea: admins or RH staff can easily delete your comments or bury them in another threads. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 06/07/2023 21:32, Michael Catanzaro wrote: As explained in the proposal document, we know that opt-in metrics are not very useful because few users would opt in, and these users would not be representative of Fedora users as a whole. Because Linux users care about their privacy. We are not interested in opt-in metrics. Then the statement "Privacy-preserving Telemetry" is not true. We want privacy - that is, no telemetry at all. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 06/07/2023 18:10, Aoife Moloney wrote: The Red Hat Display Systems Team (which develops the desktop) proposes to enable limited data collection of anonymous Fedora Workstation usage metrics. All telemetry collection MUST be an opt-in feature (disabled by default). I'm strongly against enabling it by default. Please add the ability to completely get rid of it by removing the telemetry collector package. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: How to use llvm15 for building a package
On 04/07/2023 05:24, Tom Stellard wrote:
/usr/include/OpenImageIO/detail/fmt/core.h:1691:7: error: static
assertion failed: Cannot format an argument. To make type T formattable
provide a formatter specialization: https://fmt.dev/latest/api.html#udt
This seems like a failure unrelated to clang. Have you run into this?
fmt 10 issue:
Removed deprecated implicit conversions for enums and conversions to primitive
types for compatibility with std::format and to prevent potential ODR
violations.
You need to patch (or pick an upstream patch) your package and use an
explicit conversion.
Old variant (no longer works with fmt 10):
log("..str..", foo)
New:
log("..str..", static_castfoo)
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: LibreOffice packages
On 03/07/2023 01:28, Michael Catanzaro wrote: OK, host shared libraries and flatpaked libraries will be loaded at the same time, but I really doubt that's going to be at all significant. Include dozens of bundled libraries here too. Only runtimes can use shared memory. They do consume significant disk space if your disk is really small. ostree deduplication is pretty good, though (and OCI images are deduplicated too) Many Flatpaks from Flathub still use the old runtimes. Each runtime consumes approximately 1 GB of disk space. They need to start doing mass rebuilds with every new major release of the runtime. As a matter of strategy, packaging applications is fine, but nowadays it is *optional*. I don't think so. Our most popular applications are nowadays available from Flathub or other third-party sources, and users are going to install them regardless of whether we package them. Sorry, but I can't trust them since they allow uploading pre-built blobs and DEB repacks for popular and even for security-focused applications: - Firefox (uploaded as ostree blob without sources, has disabled ASLR and hardening); - OBS Studio (uploaded as ostree blob); - Element (DEB repack: https://github.com/flathub/im.riot.Riot/blob/master/im.riot.Riot.yaml#L69-L70); - Signal (DEB repack: https://github.com/flathub/org.signal.Signal/blob/master/org.signal.Signal.yaml#L65-L66); - Blender (static binary repack: https://github.com/flathub/org.blender.Blender/blob/master/org.blender.Blender.json#L150-L151); - VS Codium (DEB repack: https://github.com/flathub/com.vscodium.codium/blob/master/com.vscodium.codium.yaml#L98-L99); - many others: https://github.com/search?q=org%3Aflathub+.deb=code They need to forbid uploading pre-built blobs and repacks. All packages (except proprietary ones) should be built on their infrastructure. Flatpaks without sandbox holes are also dramatically more secure than Fedora RPMs, which is why I'm *really* interested in Flatpaks. Also, many Flathub's apps don't use Flatpak isolation at all: - https://github.com/search?q=org%3Aflathub+--filesystem%3Dhost=code - https://github.com/search?q=org%3Aflathub+--filesystem%3Dhome=code They need to restrict such holes. Snap already did this a few years ago (classic snaps are only allowed in exceptional cases). -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaning packages (was LibreOffice packages)
On 02/07/2023 10:51, Simon de Vlieger wrote: The suppliers for these enterprise distributions and the support they offer also abide by political lines. Indeed. That's why having RHEL repacks (Alma, Rocky, Oracle Linux) is good. While your data won't be gone in an instant you still end up in the same situation with using an unsupported office suite. You can simply switch to one of these RHEL binary compatible distributions. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaning packages (was LibreOffice packages)
On 01/07/2023 14:28, Peter Robinson wrote: This sort of comment is off topic, various companies are free to do with their data as they wish, just as you are free to do with it as you please. This is not offtopic. What I mean is that a distribution targeted at enterprise use should have a standalone office suite in their repositories, because most enterprise users will won't use Flathub or any other third party repositories due to their internal security policy. They will simply migrate from RHEL to Ubuntu LTS or another enterprise distribution with LO. Frankly it's often more secure with cloud providers than on corporate networks. And they can easily dump you and all your data. Russian Federation is a good example. Both Microsoft and Google have disabled all paid accounts for users and organizations from this country. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaning packages (was LibreOffice packages)
On 01/07/2023 13:36, Chris Adams wrote: A lot of the corporate world has gone to the "cloud" don't have to worry about local backups of important documents and spreadsheets, they get sharing with minimal effort, they can access things from their mobile devices, etc. And voluntarily hand over all the corporate secrets to Google and Microsoft. Brilliant idea. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On 30/06/2023 10:01, Dominik 'Rathann' Mierzejewski wrote: As it is, you're forcing the above maintainers to scramble to fix their packages at the beginning of summer holiday season. Announced: 23.05.2023. Rebuild started: 27.06.2023. FTBFS packages announced: 28.06.2023. Side tag merged: 30.06.2023. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaning packages
On 30/06/2023 00:09, crissdell wrote: Hi, i'm really interested in maintaining this rpms, jdns and git-subrepo, but i'm not an packager yet, I really appreciate if someone is willing to mentor me, I dont want to mess it up. https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/ -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
The side tag has been merged: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4e8e736635 FTBFS (final): arbor (not related to fmt, some tests failed on s390x) CuraEngine bout++ cachelib dolphin-emu folly mangohud (not related to fmt) wasmedge watchman FTI issues will be generated automatically after the next Rawhide compose. Maintainers of these packages can build fixed versions to Rawhide directly without using any side tags. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On 28/06/2023 23:39, Kalev Lember wrote: Why? Now that you've already done all the work of adding the compatibility package, why drop it and break all of the unbuilt packages in rawhide? I don't think any of the packages from the list are release blocking, but it just seems antisocial for rawhide users to break packages they might be using, especially if it's no extra work for you at this point. At least one maintainer emailed me that they want to use fmt9-devel instead of fixing FTBFS. Sorry, but I can't allow that. Another possible solution - rebuild fmt9 without -devel subpackage to prevent its usage for building new packages. Another thing that comes in my mind is that there is the ongoing python rebuild in f39-python and your rebuilt package set probably intersects with it. Yes. All packages with Python bindings (dnf5 for example). Would be good to let Miro know what packages they need to rebuild again once your fmt tag is merged. Another reason to untag it is to make sure all packages are built against fmt 10. Also FTI RHBZ tickets will be generated automatically. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
FTBFS: 0ad arbor CuraEngine bout++ cachelib dolphin-emu folly freeopcua gerbera luxcorerender mangohud wasmedge watchman I think I will merge this side tag without fmt9 compatibility package tomorrow. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On 28/06/2023 15:00, Aleksei Bavshin wrote: Known regression in fmt. Please, apply https://github.com/fmtlib/fmt/pull/3430. Thanks for the information. The fix has been ported to fmt-10.0.0-2.fc39. waybar is now fixed. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On 28/06/2023 14:10, Kalev Lember wrote: Since you already have the compat package, I would suggest merging the side tag as is. I'm waiting for dnf5: https://github.com/rpm-software-management/dnf5/issues/675 https://bugzilla.redhat.com/show_bug.cgi?id=2218180 I fixed some packages with trivial issues. Now only 16 packages could not be built from sources. Also I want to untag fmt9 compat package before merging side tag. It was introduced only to fix issues with dnf5 in Koji. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
Results: 37 builds succeeded, 19 failed. FTBFS: 0ad arbor CuraEngine bout++ cachelib contour-terminal dnf5 dolphin-emu easyrpg-player folly freeopcua gerbera gnuradio luxcorerender mangohud nheko wasmedge watchman waybar Please fix your packages and use f39-build-side-69394 side tag: fedpkg build --target f39-build-side-69394 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On 28/06/2023 08:32, Vitaly Zaitsev wrote: How I can fix that? Steps how to fix such issues for historical purposes: 1. Create a new side tag. 2. Introduce compatibility fmt9 package. 3. Build fmt9 compatibility package. 4. Build fmt 10. 5. Rebuild dnf5 against fmt 10. 6. Untag fmt9 from this side tag. 7. Retire fmt9 compatibility package. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On 23/05/2023 12:22, Vitaly Zaitsev wrote: I will use my proven-packager rights to rebuild all dependent packages in a separate side tag next week. Koji is now broken in this side tag (f39-build-side-69392): Error: Problem 1: package python3-dnf-4.16.1-2.fc39.noarch from build requires dnf-data = 4.16.1-2.fc39, but none of the providers can be installed - package dnf-data-4.16.1-2.fc39.noarch from build requires /etc/dnf/dnf.conf, but none of the providers can be installed - conflicting requests - nothing provides libfmt.so.9()(64bit) needed by libdnf5-5.0.14-1.fc39.ppc64le from build Problem 2: package python3-dnf-plugins-core-4.4.1-3.fc39.noarch from build requires python3-dnf >= 4.11.0, but none of the providers can be installed - package python3-dnf-4.16.1-2.fc39.noarch from build requires dnf-data = 4.16.1-2.fc39, but none of the providers can be installed - package dnf-plugins-core-4.4.1-3.fc39.noarch from build requires python3-dnf-plugins-core = 4.4.1-3.fc39, but none of the providers can be installed - package dnf-data-4.16.1-2.fc39.noarch from build requires /etc/dnf/dnf.conf, but none of the providers can be installed - conflicting requests - nothing provides libfmt.so.9()(64bit) needed by libdnf5-5.0.14-1.fc39.ppc64le from build (try to add '--skip-broken' to skip uninstallable packages) How I can fix that? -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On 23/05/2023 12:22, Vitaly Zaitsev wrote: I will use my proven-packager rights to rebuild all dependent packages in a separate side tag next week. Many packages are not yet ready for fmt 10. Spdlog for example: - https://github.com/gabime/spdlog/issues/2614 - https://github.com/gabime/spdlog/issues/2767 - https://github.com/gabime/spdlog/issues/2782 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: LLVM 17 (System-Wide)
On 27/06/2023 03:21, Tom Stellard wrote: For this update, we're going to let package maintainers be responsible for rebuilding their own packages if they are unable to use the compat libraries for some reason. We can try to send an announcement when the side-tag is ready. Some package maintainers are too lazy. They won't do anything even if you inform them in the ML. Check my last year's fmt 9.0 update: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FOESCVXNAHV2OATO36UIACIE3BQGMMR5/ I think it will be better to rebuild all dependent packages in a side tag. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: LLVM 17 (System-Wide)
On 27/06/2023 03:19, Tom Stellard wrote:
We're trying to be more consistent with gcc and also upstream clang.
gcc installs some of these same libraries and some equivalent ones
into /usr/lib as well (/usr/lib/gcc/$TRIPLE/$MAJOR_VERSON).
What about FindLLVM.cmake and its ${LLVM_LIBDIR_SUFFIX}? Many projects
use it now.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Is there a chance to phase out `/lib64` directory?
On 27/06/2023 12:30, Kalev Lember wrote: I would like to have a layout similar to what Debian is doing, so that shared libraries would go in /usr/lib/x86_64-redhat-linux/ and /usr/lib64 would be a legacy symlink pointing to it. Debian isn't a good example here. I've fixed over a hundred projects by switching from hard-coded lib/ to GNUInstallDirs. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: LLVM 17 (System-Wide)
On 27/06/2023 08:41, Tom Stellard wrote: I mentioned this in a previous reply, but this is how other compilers like gcc install their internal libraries and it's also where clang expects its libraries to be installed. Got it. Thanks. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: LLVM 17 (System-Wide)
On 26/06/2023 18:12, Aoife Moloney wrote: * The Clang Resource Directory will be moved from /usr/lib64/clang/17/ to /usr/lib/clang/17/ this is the location of clang's internal headers and runtime libraries like libomp and compiler-rt. Why? /usr/lib is a directory for 32-bit and architecture agnostic libraries. 64-bit must use /usr/lib64. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: LLVM 17 (System-Wide)
On 26/06/2023 18:12, Aoife Moloney wrote: Update all llvm sub-projects in Fedora Linux to version 17. Please include iwyu and pocl packages to the side-tag rebuild too. I will update pocl to version 4.0 soon in Rawhide. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Orphaning packages
Hello. I orphaned the following packages: rpms/axc rpms/git-subrepo rpms/jdns rpms/maddy rpms/mdns rpms/pidgin-groupchat-typing-notifications rpms/pidgin-privacy-please rpms/pidgin-toobars rpms/psi rpms/psi-plus rpms/purple-discord rpms/purple-googlechat rpms/purple-libsteam rpms/purple-lurch rpms/purple-matrix rpms/purple-plugin_pack rpms/purple-skypeweb rpms/python-wloc rpms/python-networkmanager rpms/python-pytelegrambotapi rpms/python-emoji -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Fedora?
On 22/06/2023 10:11, Daniel P. Berrangé wrote: Nothing described in that blog post above changes this process, so what's written there doesn't have any direct impact on Fedora. Yet. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On 19/06/2023 08:36, Mattia Verga via devel wrote:
I only need to find how to pass branch names to the alias, instead of
hardcoding them. From a quick search I need to create a function in
.bashrc rather than an alias.
Add to ~/.bashrc:
function fpr {
for i in f$(rpm -E %fedora) f$(($(rpm -E %fedora) - 1)) rawhide; do
fedpkg switch-branch $i
if [[ "$i" != "rawhide" ]]; then
git merge rawhide
fi
fedpkg push
fedpkg build --nowait
done
}
Usage:
cd ~/foo-bar
fpr
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On 18/06/2023 17:42, Ankur Sinha wrote: I threw all the commands into a script with some optional arguments: Maybe this script can be added to fedora-packager? -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On 18/06/2023 14:51, Sandro wrote: Aren't you missing the 'git push' (or 'fedpkg push')? IIRC, your 'fpb' alias would fail since no changes have been pushed to dist-git for koji to base a build on. Good catch. Thanks: alias fpm="fedpkg switch-branch f38 && git merge rawhide && fedpkg switch-branch f37 && git merge rawhide && fedpkg switch-branch rawhide && git push" -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On 18/06/2023 11:16, Mattia Verga via devel wrote: This is quite boring and time wasting... is there a more efficient way to use my packaging time? Do you think fedpkg can be enhanced to have a single command which makes 4-5-6 to all specified branches? Add to your ~/.bashrc the following: alias fpm="fedpkg switch-branch f38 && git merge rawhide && fedpkg switch-branch f37 && git merge rawhide && fedpkg switch-branch rawhide" alias fpb="fedpkg switch-branch rawhide && fedpkg build --nowait && fedpkg switch-branch f38 && fedpkg build --nowait && fedpkg switch-branch f37 && fedpkg build --nowait && fedpkg switch-branch rawhide" Usage: cd ~/foo-bar fpm fpb -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Modules without modularity
On 13/06/2023 18:32, Petr Pisar wrote: Comments are welcome. Trying to reinvent Fedora Modularity without modules with the same problems as before. Instead of using modules, we should use parallel-installable packages. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: LibreOffice packages
On 05/06/2023 13:54, Josh Boyer wrote: I'm not sure what led you to the conclusion that IBM has anything to do with this or that "they fired a lot of good engineers". I don't see evidence of either being the case. Please don't state your own assumptions as facts. https://news.ycombinator.com/item?id=35687687 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: LibreOffice packages
On 03/06/2023 09:51, Samuel Sieb wrote: Did you read the whole thread? It's not going anywhere. People have stepped up to maintain it. LibreOffice is a complex project. It will be very difficult to maintain it. It's not just a trivial Version+Release bump, no. They will need to backport patches, fix issues with non-x86 architectures, etc. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: LibreOffice packages
On 03/06/2023 02:46, Leslie Satenstein via devel wrote: No LibreOffice, no continuation with Fedora. LO better be there with F39. Without it, all you have is Firefox. It is not enough to keep Fedora Diehards from jumping to another popular distribution. Yes, Fedora is dying. Slow, but imminent. IBM doesn't want to keep it in a good condition, so they fired a lot of good engineers. It's very sad. I have been using it for years. I'm thinking about orphaning all my packages (more than 70) too. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Build JDKs once, repack everywhere (System-Wide Change)
On 31/05/2023 19:24, Daniel P. Berrangé wrote: Can you point to the specific guideline that this violates ? I know we've always expected that apps are built from pristine upstream source, but I'm not finding the specific guideline that describes this right now. This: All program binaries and program libraries included in Fedora packages must be built from the source code that is included in the source package. Source: https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-packaged/#prebuilt-binaries-or-libraries -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Build JDKs once, repack everywhere (System-Wide Change)
On 31/05/2023 17:02, David Schwörer wrote: Could you explain what certification means? It sounds like you run some very expensive tests, and building is actually fast. You can't distribute any package named Java or OpenJDK unless it passes the Oracle test suite. I think Fedora should drop openjdk package and introduce a new one - coffee-named-language. Then we can get rid of any Oracle tests. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Build JDKs once, repack everywhere (System-Wide Change)
On 31/05/2023 15:44, Gerd Hoffmann wrote: We do similar things in other cases, see for example shim-unsigned.rpm + shim.rpm Shim is a special case: 1. Shim need to be signed by Microsoft on their own infrastructure and this signature will be built directly into PE file. 2. Shim runs on UEFI, so it can use exception for firmware. The prebuilt RPMs are compiled on Fedora infrastructure too, so I don't see how that violates the 'build from source' requirement. If the package uses prebuilt blobs (their origin is irrelevant), it violates current Fedora packaging guidelines. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Build JDKs once, repack everywhere (System-Wide Change)
On 31/05/2023 14:53, Jiri Vanek wrote: It is built from sources of course! What make you think it is not? For double ensurenes, see the fesco ticket in proposal. IMO, repackaging prebuilt RPM packages is not building from sources. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Build JDKs once, repack everywhere (System-Wide Change)
On 30/05/2023 20:37, Aoife Moloney wrote: Jdks in fedora are already static, and we repack portable tarball into rpms. Currently, the portbale tarball is built for each Fedora and Epel version. Goal here is to build each jdk (8,11,17,21,latest (20)) only once, in oldest live Fedora xor Epel and repack in all live fedoras. All Fedora packages must be built from sources (except linux-firmware package of course). -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating fast_float from 4.0.0 to 5.0.0 in Rawhide, with a license change
On 28/05/2023 17:41, Fabio Valentini wrote: At least for Rust packages, we do have some amount of automation now to help with this chore. I think %autolicense should be added to the rpmautospec project. It will automatically extract license tags from all BRs "-static" or "crate()" and concatenate them with AND. Example: # main project - MIT License: MIT AND %autolicense In future it will be able to use some license validators and replace the entire License tag: License: %autolicense -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating fast_float from 4.0.0 to 5.0.0 in Rawhide, with a license change
On 27/05/2023 14:33, Fabio Valentini wrote: It would probably be better if the legal docs made this explicit, and made Rust no longer a special case. The fact that only Rust is called out is an artifact of this rule having been moved from the Rust Packaging Guidelines to the legal docs, but other languages that are in similar situations didn't even have guidelines for this case. I have the opposite opinion. Even Rust packages should only include to the License tag libraries bundled into the source tarball. All other licenses can be traced, if necessary, from the corresponding -devel packages. If one had to manually track each header-only library in the dependency tree, check their licenses, and document them in the License tag, that would add useless extra work to the maintainers. It must be automated. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating fast_float from 4.0.0 to 5.0.0 in Rawhide, with a license change
On 27/05/2023 13:08, Fabio Valentini wrote: No, this information is outdated. Statically linked components must be taken into consideration, whether bundled or not. I only found this: Some upstream projects bundle code copied from other upstream projects (a practice some communities sometimes call "vendoring"). In certain cases Fedora permits packaging of such projects including the bundled dependencies. In some other cases, a Fedora package may itself bundle dependencies that are not separately packaged in Fedora. In these cases, assuming the bundled dependencies are built or otherwise included in the packaged binary, the License: field must reflect the licenses covering the bundled code. https://docs.fedoraproject.org/en-US/legal/license-field/#_bundled_or_vendored_dependencies I can't find any information about packaged header-only libraries. Could you post a link please? -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: OpenColorIO builds failing due to doxygen patch level update?
On 26/05/2023 14:07, Richard Shaw wrote: Doxygen was updated from 1.9.6 to 1.9.7 which I would assume should be a pretty harmless update Some Doxygen minor updates breaks something. That's why I disabled docs generation in all my packages. Users can easily view docs online. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: CVE: Python-twisted a.o. needs update for F37 due to matrix-synapse security issue
On 26/05/2023 16:22, Marius Schwarz wrote: This brings me to the question: whats the main issue for twisted here? 1. Contact python-twisted maintainers. 2. Check if all dependent packages are compatible with the updated python-binding package. 3. If this is a major update, you or the package maintainer should receive a FESCo approval in accordance with Fedora Updates policy. Another solution: backport the security fix into F37. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: employment related packager groups
On 26/05/2023 19:39, Kevin Fenzi wrote: Should such groups require FESCo approval? Yes. If so, what would be requirements to approve/deny? All group members must prove that they're familiar with Fedora packaging guidelines, i.e. they must receive sponsorship through the standard procedure and not from their employer (may be biased). -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating fast_float from 4.0.0 to 5.0.0 in Rawhide, with a license change
On 26/05/2023 18:35, Ben Beasley wrote: Since fast_float is a header-only library, and our guidelines treat these as a kind of static library, directly-dependent packages should—strictly speaking—include fast_float’s SPDX license expression in their own Only if they use the version built into the source archive. If they're using packaged, they don't have to. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Status of the forge macros?
On 23/05/2023 19:27, Richard W.M. Jones wrote: ... so today I was taking part in a package review which uses these macros and was surprised to be told that they are deprecated. Their author left Fedora a few years ago. They're now unmaintained and may be removed soon (see FPC ticket[1]). [1]: https://pagure.io/packaging-committee/pull-request/1270 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: more distinct default bash prompt?
On 22/05/2023 05:49, Jens-Ulrik Petersen wrote: What do people think overall? Are there other pros and cons of a color prompt? Any better ideas or direction? PS1 from all my systems: export PS1="\[\e[33m\][\[\e[36m\]\u\[\e[0m\]@\[\e[31m\]\h\[\e[0m\] \[\e[32m\]\W\[\e[33m\]]\[\e[35m\]\$\[\e[0m\] " -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Announcing fmt library soversion bump
Hello. fmt 10.0.x update will include a soversion bump from .9 to .10. It has both API and ABI changes. Changelog: https://github.com/fmtlib/fmt/releases/tag/10.0.0 The list of affected packages in Rawhide: 0ad OpenImageIO bear cachelib cantera ceph dnf5 dolphin-emu domoticz easyeffects easyrpg-player fb303 fbthrift fizz fmidi folly freeopcua gerbera giada gnuradio gr-funcube libsemigroups libsonata luxcorerender mcrouter mkvtoolnix nheko proxygen rstudio sdrpp spdlog vcpkg wangle watchman waybar zswap-cli I will use my proven-packager rights to rebuild all dependent packages in a separate side tag next week. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: It’s time to transform the Fedora devel list into something new
On 20/04/2023 23:20, Matthew Miller wrote: It’s time to transform the Fedora devel list into something new I think such serious questions should be put to a vote. Not a FESCo vote, but a vote for all Fedora contributors (can be combined with the next FESCo elections). -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 proposal: Increase vm.max_map_count value (System-Wide Change proposal)
On 24/04/2023 18:12, Ben Cotton wrote: This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. AFAIK, a small number is a security measure. Memory mappings are kernel level objects, so poorly written applications can easily exhaust the limit of the entire system and make it unusable. If needed by Steam or Wine, they should provide a .conf file instead rather than changing this setting system wide. Steam from the RPM Fusion repository is already changing the DefaultLimitNOFILE variable: https://github.com/rpmfusion/steam/blob/master/01-steam.conf -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Error with libheif package
On 22/04/2023 14:41, Christopher Klooz wrote: So once users have rpmfusion enabled, `dnf install/update libheif` ends up in a conflict because of `libheif-hevc` and `libheif-freeworld`. Already fixed in libheif-freeworld-1.15.1-5. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Auto-assign packager sponsors to tickets?
On 17/04/2023 17:53, Jakub Kadlcik wrote: - Instead, I am going to automatically open an issue in the package-sponsors tracker for new contributors after they receive fedora-review+ on their first ticket. LGTM now. Thank you for working on this. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaning pocl
On 10/04/2023 19:44, Tom Stellard wrote: I'm orphaning the pocl package. I'm not interested in maintaining it any more, and it's been FTBFS for the last 2 releases. I will take it and update to version 3.1 with LLVM 15+ support. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Auto-assign packager sponsors to tickets?
On 04/04/2023 23:42, Kevin Fenzi wrote: But then after a outcry... "We are reverting this change for now. More details to follow." Yes, after a lot of negative feedback they (temporary?) reverted this change. Even their own vcpkg (package manager by Microsoft) uses these hashes to verify downloaded files. They said that after each download of the git tag archive, its contents are permanently stored on the content server, and all subsequent downloads will be performed by it. It consumes a lot of disk space. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)
On 04/04/2023 15:15, Neal Gompa wrote: But overall? I don't think so. Web browsers, game engines, audio/video editing software. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)
On 04/04/2023 11:17, Neal Gompa wrote: It seems that moving to -O3 would provide more gains than x86_64-v3. AVX2 can significantly boost the performance of modern processors in SIMD operations. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Auto-assign packager sponsors to tickets?
On 04/04/2023 09:36, Kalev Lember wrote: That's not exactly true. Yes, non-packagers can't upload files to the lookaside cache, but they can update the 'sources' and '.gitignore' files in git. GitHub has stated[1] that they no longer guarantee hash stability between archive downloads. We discussed this issue at #devel:fedoraproject.org[2] and everyone agreed that tarball format is not reproducible. Thus, when the maintainer downloads the tarball using spectool, the hashes will not match. [1]: https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/ [2]: https://matrix.to/#/!lbPXqyjXDnvnfogGYA:matrix.org/$Flv-5iRWTWeG9XYbH3p0jfuyTSpLcHfVeosK4QqKAiA -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Auto-assign packager sponsors to tickets?
On 04/04/2023 07:52, Otto Liljalaakso wrote: Perhaps new package requests could more often be handled in a way where an existing packager assumes the maintainer position with the agreement that the submitter keeps the packager updated and in good condition, through pull requests. We have a serious problem here: non-packages can't upload sources to Fedora SCM. These pull requests require maintainers to do it manually in a separate commit that breaks %autorelease+%autochangelog. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Auto-assign packager sponsors to tickets?
On 04/04/2023 02:59, Jakub Kadlcik wrote: I get the same impression and I would agree with Otto's proposal to get rid of the FE-NEEDSPONSOR entirely. Looks good for me too. Opening a new Pagure ticket would be better, IMO. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)
On 02/04/2023 17:36, Mattia Verga via devel wrote: Is there anyone who could provide some benchmarks to see if there are significant performance improvements about using v2/v3/v3 versus plain x86_64? AVX2 can bring a huge performance boost. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Auto-assign packager sponsors to tickets?
On 01/04/2023 23:14, Jakub Kadlčík wrote: Currently, we have 31 people waiting to be sponsored https://fedoraproject.org/PackageReviewStatus/needsponsor.html many of them waiting for months. If they wait for months, I think they don't want to be sponsored. I sponsored everyone who emailed me or asked in #fedora-devel. I believe there is a technical solution to this problem I doubt. What do you think? Would you be okay with a system like this? Please exclude me from such spam. I'm always willing to review and sponsor new maintainers, but they need to show explicit consent by posting on IRC/Matrix/ML or direct email. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Node.js repackaging status and questions
On 01/04/2023 13:10, Jiri Vanek wrote: I would heavily recomend to use alternatives for this,a nd thus remain aligned with other major runtimes. Alternatives can't be used on immutable Fedora versions (Silverblue, Kinoite, etc). -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Different binaries size in Rawhide and F38
Hello all. It looks like strip is broken in Rawhide. Affected package - telegram-desktop. Fedora 38 binary size: 83,563,448 bytes. Rawhide binary size: 98,968,520 bytes. Builds: https://koji.rpmfusion.org/koji/buildinfo?buildID=25349 (F38) https://koji.rpmfusion.org/koji/buildinfo?buildID=25350 (Rawhide) Build from 2023-03-24 is not affected: https://koji.rpmfusion.org/koji/buildinfo?buildID=25265 They are built from the same sources. Just a release bump due to Qt 6.4.3 update. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Specfile - Upgrade - Check if the old and the new package versions are the same
On 30/03/2023 02:54, Simon Pichugin wrote:
I understand that it's not the correct way... Could you please suggest
how something like this can be achieved? (during the upgrade - check if
the old and the new package versions are the same)
You should use %triggerun instead:
%triggerun -- %{name} < OLD_VERSION
# do something
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Strange hook in cloned package repositories
On 27/03/2023 14:41, Fabio Valentini wrote: It's doing new pre-push checks that were introduced in rpkg 1.66: Thanks for the information. As far as I know, there's no way to disable the checks for now, other than to do "rm .git/hooks/pre-push". Will do, because my $HOME is mounted with 'noexec,nodev,nosuid' flags and on every push it throws a warning: $ git push hint: The '.git/hooks/pre-push' hook was ignored because it's not set as executable. hint: You can disable this warning with `git config advice.ignoredHook false`. I think a new configuration option skip_hooks should be added to the ~/.config/rpkg/fedpkg.conf file. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
