Re: BTRFS, relatime vs. noatime
On 9/5/20 5:29 AM, Neal Becker wrote:
If BTRFS is to become fedora default, we should consider this?
"BTRFS relatime vs. noatime - Huge Performance Difference - linux"
https://www.reddit.com/r/linux/comments/imgler/btrfs_relatime_vs_noatime_huge_performance/?utm_source=amp&utm_medium=&utm_content=post_body
The *performance* difference is probably vastly overstated by people who
haven't actually compared btrfs to other filesystems. At least, I keep
seeing this come up, but haven't yet seen anyone offer a comparison to
any other filesystem, and I suspect that it is a myth.
I copied 150,000 files from btrfs to ext4 with atime updates, and the
same transfer with no atime updates. I did the same process with ext4 to
ext4.
The performance impact of atime updates on ext4 was 9.6% (31.65s ->
28.614s). The performance impact of atime updates on btrfs was 3.86%
(29.626s -> 28.482s).
This isn't a scientific test, and I'm not going to argue henceforth that
btrfs performs better than ext4, but the test does suggest that btrfs
with relatime isn't the "sky is falling" performance disaster that
people are making it out to be.
|#!/bin/sh bf1=/home/input bf2=/home/output dd if=/dev/zero of=$bf1
bs=1M count=1 dd if=/dev/zero of=$bf2 bs=1M count=1 losetup
/dev/loop1 $bf1 losetup /dev/loop2 $bf2 mkfs.btrfs /dev/loop1 mkfs.ext4
/dev/loop2 mkdir /mnt/input mkdir /mnt/output mount /dev/loop1
/mnt/input mount /dev/loop2 /mnt/output rsync -aHS /home/flatpak
/mnt/input find /mnt/input -exec touch -h -a -d 'Jan 1 2020' {} + time
rsync -aHS /mnt/input/ /mnt/output umount /mnt/output mkfs.ext4
/dev/loop2 mount /dev/loop2 /mnt/output # atime is already updated on
/mnt/input, so it's not strictly necessary to remount it with noatime
time rsync -aHS /mnt/input/ /mnt/output umount /mnt/input umount
/mnt/output rmdir /mnt/input rmdir /mnt/output losetup -d /dev/loop1
losetup -d /dev/loop2 rm $bf1 rm $bf2|
___
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
Re: Fedora 33 blocker status , with CALL FOR TESTING on abrt/libreport
On 9/12/20 5:10 PM, Chris Murphy wrote: This is pending for 3 days, so --advisory doesn't work since it's still not in u-t. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd3d0e6879 Instead I did bodi updates download --updateid=FEDORA-2020-fd3d0e6879 dnf update *rpm And it skips a bunch of rpms that get downloaded as part of that update, but aren't already installed. Here's what I discovered following that: https://bugzilla.redhat.com/show_bug.cgi?id=1878317 Thanks for that! I get bug 1873029[0]. [0] - https://bugzilla.redhat.com/show_bug.cgi?id=1873029#c16 ___ 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
Re: Is there a Qt5 rebuild in progress?
On 9/12/20 5:43 PM, Orion Poplawski wrote: On 9/12/20 2:39 AM, Vitaly Zaitsev via devel wrote: On 11.09.2020 22:10, Miro Hrončok wrote: Is there a Qt5 rebuild in progress? Yes. Qt 5.15.1 is going to Rawhide and F33. It's introduced at least two FTBFS in my packages (plplot, vtk) - are we sure we want to push to F33 now? There are some others as well: https://koschei.fedoraproject.org/affected-by/qt5-qtbase-devel?epoch1=0&version1=5.14.2&release1=8.fc33&epoch2=0&version2=5.15.1&release2=1.fc34&collection=f34 -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Is there a Qt5 rebuild in progress?
On 9/12/20 2:39 AM, Vitaly Zaitsev via devel wrote: On 11.09.2020 22:10, Miro Hrončok wrote: Is there a Qt5 rebuild in progress? Yes. Qt 5.15.1 is going to Rawhide and F33. It's introduced at least two FTBFS in my packages (plplot, vtk) - are we sure we want to push to F33 now? -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 33 blocker status , with CALL FOR TESTING on abrt/libreport
On Sat, Sep 12, 2020 at 2:13 PM Brandon Nielsen wrote: > > On 9/11/20 3:44 PM, Adam Williamson wrote: > > On Fri, 2020-09-11 at 15:50 -0400, Ben Cotton wrote: > >> > >> Accepted blockers > >> - > >> 1. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=1860616 — ON_QA > >> abrt-server errors when processing zstd compressed core dumps produced > >> by systemd-246~rc1-1.fc33 > >> > >> FEDORA-2020-59e144acee contains a potential fix, but appears to > >> introduce a new blocker (BZ 1873029). It may be moot until the retrace > >> server is brought back online. The infra team has provisioned a basic > >> instance, which msuchy is working to get ready for use. > > > > So yeah: it would really help if other folks could try installing the > > update and see if they are able to successfully file a crash bug or > > not. Please report your findings to the bug report(s). > > > > > Is there an easy way to install the update? It's been "unpushed", so the > command to install (`sudo dnf upgrade --enablerepo=updates-testing > --advisory=FEDORA-2020-59e144acee`) it doesn't seem to work. This is pending for 3 days, so --advisory doesn't work since it's still not in u-t. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd3d0e6879 Instead I did bodi updates download --updateid=FEDORA-2020-fd3d0e6879 dnf update *rpm And it skips a bunch of rpms that get downloaded as part of that update, but aren't already installed. Here's what I discovered following that: https://bugzilla.redhat.com/show_bug.cgi?id=1878317 -- Chris Murphy ___ 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
Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal
> how much memory that amounts to in the usual scenarios 700M on F32 without any apps started. Largest file: (207.9M) /usr/lib/locale/locale-archive Files list with its sizes: https://pastebin.com/Hpr6D3Sv Locking even 250M-300M takes good effect. For example, demo: https://www.youtube.com/watch?v=vykUrP1UvcI - no freezes with prelockd and freeze without prelockd. ___ 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
Re: Fedora 33 blocker status , with CALL FOR TESTING on abrt/libreport
On 9/11/20 3:44 PM, Adam Williamson wrote: On Fri, 2020-09-11 at 15:50 -0400, Ben Cotton wrote: Accepted blockers - 1. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=1860616 — ON_QA abrt-server errors when processing zstd compressed core dumps produced by systemd-246~rc1-1.fc33 FEDORA-2020-59e144acee contains a potential fix, but appears to introduce a new blocker (BZ 1873029). It may be moot until the retrace server is brought back online. The infra team has provisioned a basic instance, which msuchy is working to get ready for use. So yeah: it would really help if other folks could try installing the update and see if they are able to successfully file a crash bug or not. Please report your findings to the bug report(s). Is there an easy way to install the update? It's been "unpushed", so the command to install (`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-59e144acee`) it doesn't seem to work. ___ 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
Re: F33 update stuck for past 6 days in request for testing->stable
On Saturday, September 12, 2020 5:52:14 PM WEST Sérgio Basto wrote: > I agree , why not even have a count for starting to freeze ? , I though > that freeze just start after we have first beta candidate. It does not work that way. There is a freeze for beta and there is a freeze for the final release. After beta is released packages that transition to stable will go the repository that will be fedora 33. -- José Abílio___ 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
Re: F33 update stuck for past 6 days in request for testing->stable
On Sat, 2020-09-12 at 15:33 +0200, Björn Persson wrote: > Kevin Fenzi wrote: > > We are in Beta freeze. Only packages that fix accepted blocker bugs > > or > > freeze break exceptions can go stable. > > > > https://fedoraproject.org/wiki/Milestone_freezes > > Would it be possible for Bodhi to say so, so people don't need to ask > here on the mailing list? > > Kevin's wording is perfect. It just needs to be visible in the web > interface, with the words "Beta freeze" as a link. I agree , why not even have a count for starting to freeze ? , I though that freeze just start after we have first beta candidate. -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Looking for new Python package maintainers
On Sat, 2020-09-12 at 10:18 +, Dhanesh B. Sabane wrote: > Hey Michel, > > > I'll take python-lupa > > > > Thanks for your work over the years, and hope you at least remain a > > user, > > I've provided you admin access for python-lupa. Thank you so much for > taking it up! :) > Thanks Dhanesh! I already have an update in testing for F33's Lua 5.4. > I'll definitely remain a user and will try to help out with > evangelism. I hope I'll get enough time in the future to get back to > Fedora contributions. > Great to hear! I've been in the same situation before. We are all volunteers (well, mostly) so of course it's fine if other things in life takes a priority. You're probably already in the ambassadors and join groups? Cheers, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name chat via email: https://delta.chat/ GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2 signature.asc Description: This is a digitally signed message part ___ 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
Fedora-IoT-33-20200912.0 compose check report
No missing expected images. Soft failed openQA tests: 1/16 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-IoT-33-20200909.0): ID: 663811 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/663811 Passed openQA tests: 15/16 (x86_64) Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default_upload: System load changed from 0.06 to 0.26 Previous test data: https://openqa.fedoraproject.org/tests/660210#downloads Current test data: https://openqa.fedoraproject.org/tests/663812#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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
Re: F33 update stuck for past 6 days in request for testing->stable
Kevin Fenzi wrote: > We are in Beta freeze. Only packages that fix accepted blocker bugs or > freeze break exceptions can go stable. > > https://fedoraproject.org/wiki/Milestone_freezes Would it be possible for Bodhi to say so, so people don't need to ask here on the mailing list? Kevin's wording is perfect. It just needs to be visible in the web interface, with the words "Beta freeze" as a link. Björn Persson pgpfEuTuG6xiz.pgp Description: OpenPGP digital signatur ___ 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
Fedora-33-20200912.n.0 compose check report
No missing expected images. Failed openQA tests: 1/181 (x86_64) Old failures (same test failed in Fedora-33-20200911.n.0): ID: 663654 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/663654 Soft failed openQA tests: 11/181 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-33-20200911.n.0): ID: 663579 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/663579 ID: 663598 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/663598 ID: 663625 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/663625 ID: 663638 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/663638 ID: 663658 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/663658 ID: 663661 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/663661 ID: 663675 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/663675 ID: 663687 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/663687 ID: 663688 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/663688 ID: 663709 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/663709 ID: 663712 Test: x86_64 universal upgrade_2_minimal_uefi@uefi URL: https://openqa.fedoraproject.org/tests/663712 Passed openQA tests: 169/181 (x86_64) New passes (same test not passed in Fedora-33-20200911.n.0): ID: 663683 Test: x86_64 universal install_mirrorlist_graphical URL: https://openqa.fedoraproject.org/tests/663683 Installed system changes in test x86_64 Workstation-live-iso install_default_upload: 1 packages(s) added since previous compose: pipewire-gstreamer System load changed from 0.79 to 1.51 Average CPU usage changed from 24.4 to 39.43809524 Previous test data: https://openqa.fedoraproject.org/tests/662367#downloads Current test data: https://openqa.fedoraproject.org/tests/663622#downloads Installed system changes in test x86_64 Workstation-live-iso install_default@uefi: 1 packages(s) added since previous compose: pipewire-gstreamer System load changed from 1.12 to 1.62 Average CPU usage changed from 22.7333 to 8.67142857 Previous test data: https://openqa.fedoraproject.org/tests/662369#downloads Current test data: https://openqa.fedoraproject.org/tests/663624#downloads Installed system changes in test x86_64 KDE-live-iso install_default_upload: System load changed from 1.21 to 1.03 Previous test data: https://openqa.fedoraproject.org/tests/662386#downloads Current test data: https://openqa.fedoraproject.org/tests/663641#downloads Installed system changes in test x86_64 KDE-live-iso install_default@uefi: Average CPU usage changed from 1.86190476 to 27.00952381 Previous test data: https://openqa.fedoraproject.org/tests/662387#downloads Current test data: https://openqa.fedoraproject.org/tests/663642#downloads Installed system changes in test x86_64 Silverblue-dvd_ostree-iso install_default_upload: Used mem changed from 833 MiB to 736 MiB Used swap changed from 20 MiB to 28 MiB Previous test data: https://openqa.fedoraproject.org/tests/662403#downloads Current test data: https://openqa.fedoraproject.org/tests/663658#downloads Installed system changes in test x86_64 Silverblue-dvd_ostree-iso install_default@uefi: Used mem changed from 759 MiB to 837 MiB Used swap changed from 29 MiB to 22 MiB Previous test data: https://openqa.fedoraproject.org/tests/662406#downloads Current test data: https://openqa.fedoraproject.org/tests/663661#downloads Installed system changes in test x86_64 universal install_package_set_kde: Used swap changed from 6 MiB to 3 MiB System load changed from 0.92 to 1.16 Previous test data: https://openqa.fedoraproject.org/tests/662447#downloads Current test data: https://openqa.fedoraproject.org/tests/663702#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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
Fedora 33 compose report: 20200912.n.0 changes
OLD: Fedora-33-20200911.n.0 NEW: Fedora-33-20200912.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 6 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 158.92 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -1.75 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: LXQt raw-xz armhfp Path: Spins/armhfp/images/Fedora-LXQt-armhfp-33-20200912.n.0-sda.raw.xz = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: anaconda-33.25.2-3.fc33 Old package: anaconda-33.25.2-1.fc33 Summary: Graphical system installer RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui anaconda-install-env-deps anaconda-live anaconda-tui anaconda-widgets anaconda-widgets-devel Size: 20.84 MiB Size change: -4.06 KiB Changelog: * Mon Sep 07 2020 Martin Kolman - 33.25.2-2 - Always clear treeinfo metadata (#1872056) (jkonecny) * Wed Sep 09 2020 Martin Kolman - 33.25.2-3 - Add the DBus method IsDeviceShrinkable (#1875677) (vponcova) Package: enjarify-1.0.3-14.fc33 Old package: enjarify-1.0.3-11.fc32 Summary: Translate Dalvik bytecode to equivalent Java bytecode RPMs: enjarify python3-enjarify Size: 490.50 KiB Size change: 48.41 KiB Changelog: * Tue May 26 2020 Miro Hron??ok - 1.0.3-12 - Rebuilt for Python 3.9 * Mon Jul 27 2020 Fedora Release Engineering - 1.0.3-13 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Sat Aug 01 2020 Fedora Release Engineering - 1.0.3-14 - Second attempt - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Wed Aug 26 2020 Zbigniew J??drzejewski-Szmek - 1.0.3-14 - Disable tests (#1808128). The tests are right and the package is broken with python3.9 (https://bugs.python.org/issue41531). Hopefully python3.9 will be fixed before the final release. Package: gnome-settings-daemon-3.37.92-1.fc33 Old package: gnome-settings-daemon-3.37.0-1.fc33 Summary: The daemon sharing settings from GNOME to GTK+/KDE applications RPMs: gnome-settings-daemon gnome-settings-daemon-devel Size: 6.26 MiB Size change: 101.65 KiB Changelog: * Sat Aug 29 2020 Kalev Lember - 3.37.1-1 - Update to 3.37.1 * Mon Sep 07 2020 Kalev Lember - 3.37.92-1 - Update to 3.37.92 Package: gnome-shell-3.37.91-4.fc33 Old package: gnome-shell-3.37.91-2.fc33 Summary: Window management and application launching for GNOME RPMs: gnome-shell Size: 7.82 MiB Size change: 15.01 KiB Changelog: * Wed Sep 02 2020 Florian M??llner - 3.37.91-3 - Add missing pipewire dependency for screen recorder * Wed Sep 02 2020 Kalev Lember - 3.37.91-4 - Add missing pipewire-gstreamer dependency for screen recorder - Set minimum gnome-settings-daemon version for Screencast proxy changes - Backport upstream fix to save screencasts under resolved file name Package: libuv-1:1.39.0-1.module_f33+10144+90bd8609 Old package: libuv-1:1.38.1-1.module_f33+9662+0b377b41 Summary: Platform layer for node.js RPMs: libuv libuv-devel libuv-static Size: 1.43 MiB Size change: 15.41 KiB Changelog: * Tue Sep 08 2020 Stephen Gallagher - 1.39.0-1 - Update to 1.39.0 Package: nodejs-1:14.10.0-1.module_f33+10144+90bd8609 Old package: nodejs-1:14.7.0-1.module_f33+9662+0b377b41 Summary: JavaScript runtime RPMs: nodejs nodejs-devel nodejs-docs nodejs-full-i18n nodejs-libs npm v8-devel Size: 122.08 MiB Size change: -1.92 MiB Changelog: * Fri Aug 21 2020 Jeff Law - 1:14.7.0-2 - Narrow LTO opt-out to just armv7hl * Tue Sep 08 2020 Stephen Gallagher - 1:14.10.0-1 - Update to 14.10.0 = DOWNGRADED PACKAGES =___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] Fedora 33 Branched 20200912.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 33 Branched 20200912.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20200906.n.0: anaconda-33.25.2-1.fc33.src, 20200912.n.0: anaconda-33.25.2-3.fc33.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/33 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ 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
Re: Looking for new Python package maintainers
Hey Michel, > I'll take python-lupa > > Thanks for your work over the years, and hope you at least remain a > user, I've provided you admin access for python-lupa. Thank you so much for taking it up! :) I'll definitely remain a user and will try to help out with evangelism. I hope I'll get enough time in the future to get back to Fedora contributions. Cheers! -- Dhanesh Sabane ___ 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
Re: Looking for new Python package maintainers
Hey Andy! > On Mon, 7 Sep 2020 at 07:44, Dhanesh B. Sabane wrote: > > If there are no takers, I'd like to maintain the python-blindspinner > package. I see there is some room to bring in its "click" dependencies. I've provided you admin access on python-blindspinner. Thank you so much for taking it up! :) Cheers! -- Dhanesh Sabane ___ 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
Re: The Future of the Java Stack (also regarding ELN and RHEL)
On Sat, Sep 12, 2020 at 11:05 AM Zbigniew Jędrzejewski-Szmek wrote: > > On Sat, Sep 12, 2020 at 10:32:51AM +0200, Vitaly Zaitsev via devel wrote: > > On 11.09.2020 18:42, Zbigniew Jędrzejewski-Szmek wrote: > > > I'm not enthusiastic about build-time-only packages, but if the choice > > > is between that and retiring the packages (or hiding them in modules > > > which has the same effect), I'll take it. > > > > This will be Modularity 2.0. All packages must be installable if the end > > user wants to do so. > > The packages *would* be trivially installable. I didn't say that explicitly, > but you would always be able to install a package that has > "Provides:fedora-build-time-only" > and then install any such packages on any system. (That is how they would > installed in mock or koji too.) > > > Check header-only C++ libraries packaging. They provide only the -devel > > and virtual -static subpackages and can be easily installed in Koji/mock > > or directly. > > > > Also check Rust packaging. They build crates to a separate packages and > > use them only for the static linkage. Hm, that comparison doesn't fit that well. Let me try to clarify some things that have come up in this discussion a couple of times, probably because the confusing "build-only dependencies" vs. "source-only dependencies / static linking": TL;DR: Java packaging in fedora is more like python packaging than Rust packaging. - Java code is compiled into architecture-independent bytecode (.class files) that's usually bundled into Zip files with some metadata (.jar files). - That bytecode is - and can be - used at both build-time and at runtime by dependent packages, so it's basically like Python packages. On the other hand, Rust packages only contain source code, which is *freshly compiled every time it's used* in dependent packages and then statically linked. - The "build-only dependencies" with respect to Java packages (as mentioned in this thread) refer to *build tools* (like maven and ant) and their dependencies, which are only used at build-time, but are obviously not needed at runtime (just like packages built with autotools, CMake or meson also don't require them at runtime). However! Of course the dependency trees of build tools and the built software itself *do overlap* (this is the fact the Java Modularity approach is ignoring). A lot of Java packages are used both as runtime dependencies for build tools *and* as runtime dependencies for applications (which is apparently outside the scope of Red Hat ???) , so those have to be maintained as non-modular packages anyway, apparently as a community-only effort. Fabio ___ 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
Fedora-Cloud-32-20200912.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-32-20200911.0): ID: 663576 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/663576 Passed openQA tests: 6/7 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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
Re: The Future of the Java Stack (also regarding ELN and RHEL)
On Sat, Sep 12, 2020 at 10:32:51AM +0200, Vitaly Zaitsev via devel wrote: > On 11.09.2020 18:42, Zbigniew Jędrzejewski-Szmek wrote: > > I'm not enthusiastic about build-time-only packages, but if the choice > > is between that and retiring the packages (or hiding them in modules > > which has the same effect), I'll take it. > > This will be Modularity 2.0. All packages must be installable if the end > user wants to do so. The packages *would* be trivially installable. I didn't say that explicitly, but you would always be able to install a package that has "Provides:fedora-build-time-only" and then install any such packages on any system. (That is how they would installed in mock or koji too.) > Check header-only C++ libraries packaging. They provide only the -devel > and virtual -static subpackages and can be easily installed in Koji/mock > or directly. > > Also check Rust packaging. They build crates to a separate packages and > use them only for the static linkage. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Is there a Qt5 rebuild in progress?
On 11.09.2020 22:10, Miro Hrončok wrote: > Is there a Qt5 rebuild in progress? Yes. Qt 5.15.1 is going to Rawhide and F33. -- 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
Re: The Future of the Java Stack (also regarding ELN and RHEL)
On 11.09.2020 18:42, Zbigniew Jędrzejewski-Szmek wrote: > I'm not enthusiastic about build-time-only packages, but if the choice > is between that and retiring the packages (or hiding them in modules > which has the same effect), I'll take it. This will be Modularity 2.0. All packages must be installable if the end user wants to do so. Check header-only C++ libraries packaging. They provide only the -devel and virtual -static subpackages and can be easily installed in Koji/mock or directly. Also check Rust packaging. They build crates to a separate packages and use them only for the static linkage. -- 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
Re: The Future of the Java Stack (also regarding ELN and RHEL)
On 11.09.2020 10:16, Mikolaj Izdebski wrote: > You get a side tag in Koji where you can have private build-only > dependencies that are discarded (filtered) once they are no longer > needed, after module build is done. IMO, this is a very bad practice. I maintain a lot of C++ header-only libraries, needed to build other packages and this is fine. Everyone can use them without bundling into their own 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
