DNF Sytem Upgrade requirements for an F37 → F38 upgrade
Hello, TL;DR: DNF memory usage during upgrades from F37 to F38 on a couple of Fedora Cloud images (with 2 GB of RAM each) led to oomd kicking in and killing the upgrade process. It might be worth looking into before the final (also beta?) release. The longer story: I have a couple of hosted VMs, which started their lives as Fedora Cloud 27 and which I have been upgrading to the next Fedora release via dnf-plugin-system-upgrade. These VMs run very few things, mainly some PHP applications on Apache and a good chunk of the PHP stack, some scheduled network scripts, a private rpm repository, OpenVPN and Wireguard nodes and when I am far from my main computer and koji or copr happen to be busy, I test things in mock on them. These VMs are near clones of each other, so usually only one of them is up at any moment. I've never had an issue with memory use up to now and when the systems aren't building packages, they seldom require more than 200 MB of RAM. What's more, there's the default swap-on-zram, so they should be more than happy memory-wise with 2 GB of RAM. I tried to upgrade one VM to F38, to see what problems I might face and after the packages had been downloaded, I lost the ssh connection as DNF was running the transaction test, right after a successful transaction check. I repeated the whole thing a couple more times, until I remembered that oomd is there and sure enough, DNF had been consuming 1-1.3 GB until oomd decided to kill it. Well, actually it killed my entire session and not just DNF. I tried running the upgrade inside a screen (the GNU one) session and I came back to an empty session. The transaction involved the upgrade of 1620 packages, with a total size of 1.2 GB. I think the difference between that and the previous upgrade F36 to F37) is around 100 MB and 30 or 40 packages. In each of the failed attempts, the memory pressure was 55 to 78% for more than 20 seconds, according to systemd-oomd. The exact same issues appeared when upgrading the second VM. Eventually I did the upgrade by doubling the available RAM to 4 GB (and then set it back to 2), but perhaps this could be a problem for others, especially those who pay for cloud-based resources. Is DNF supposed to be a legitimate target for systemd-oomd? Conversely, is DNF supposed to use up so much memory? ___ 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
[Test-Announce] [Test Day] GNOME 44 Desktop and Core Apps 2023-03-06 through 2023-03-08
Hey folks! This week we will be testing GNOME 44. To make it easier for testers to test and the Workstation team to make the results submitted useful, we have split the GNOME test week into two parts, the first leg will be covering the desktop and the core apps. The latter will focus on apps that will need a lot more testing. Today, we kick off the first leg [0] and the workstation team will be monitoring their libera chat room for questions. The "how to test" [1] section will help testers understand what to test for (if they are completely new to this) [0] https://fedoraproject.org/wiki/Test_Day:2023-03-06_Fedora_38_GNOME_44_Desktop_and_Core_Apps [1] https://fedoraproject.org/wiki/Test_Day:2023-03-06_Fedora_38_GNOME_44_Desktop_and_Core_Apps#How_to_test? -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2170646] Please branch and build perl-Config-Grammar for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2170646 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2023-d0d4fb8dfb has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-d0d4fb8dfb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2170646 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2175475] perl-Perl-Critic-1.150 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2175475 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #4 from Fedora Update System --- FEDORA-2023-1a11dd77b1 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1a11dd77b1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2175475 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2144909] perl-Log-Any-1.713 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2144909 --- Comment #7 from Fedora Update System --- FEDORA-2023-9364813e45 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2144909 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: ffmpeg 6.x needed for HDR content decoding
On Sun, Mar 5, 2023 at 6:27 PM Reon Beon via devel wrote: > > February 28th, 2023, FFmpeg 6.0 "Von Neumann" > > A new major release, FFmpeg 6.0 "Von Neumann", is now available for download. > This release has many new encoders and decoders, filters, ffmpeg CLI tool > improvements, and also, changes the way releases are done. All major releases > will now bump the version of the ABI. We plan to have a new major release > each year. Another release-specific change is that deprecated APIs will be > removed after 3 releases, upon the next major bump. This means that releases > will be done more often and will be more organized. > > New decoders featured are Bonk, RKA, Radiance, SC-4, APAC, VQC, WavArc and a > few ADPCM formats. QSV and NVenc now support AV1 encoding. The FFmpeg CLI (we > usually reffer to it as ffmpeg.c to avoid confusion) has speed-up > improvements due to threading, as well as statistics options, and the ability > to pass option values for filters from a file. There are quite a few new > audio and video filters, such as adrc, showcwt, backgroundkey and ssim360, > with a few hardware ones too. Finally, the release features many > behind-the-scenes changes, including a new FFT and MDCT implementation used > in codecs (expect a blog post about this soon), numerous bugfixes, better ICC > profile handling and colorspace signalling improvement, introduction of a > number of RISC-V vector and scalar assembly optimized routines, and a few new > improved APIs, which can be viewed in the doc/APIchanges file in our tree. A > few submitted features, such as the Vulkan improvements and more FFT > optimizations will be in the next > minor release, 6.1, which we plan to release soon, in line with our new > release schedule. Some highlights are: > I'm already aware of the new ffmpeg release. It takes time for me to get this done, but it is in progress. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2173738] perl-libwww-perl-6.68 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2173738 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-libwww-perl-6.68-1.fc3 ||7 Resolution|--- |ERRATA Last Closed||2023-03-06 02:14:55 --- Comment #8 from Fedora Update System --- FEDORA-2023-1067dc376c has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2173738 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2175432] perl-Test2-Suite-0.000148 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2175432 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-Test2-Suite-0.000147 |perl-Test2-Suite-0.000148 |is available|is available --- Comment #1 from Upstream Release Monitoring --- Releases retrieved: 0.000148 Upstream release that is considered latest: 0.000148 Current version/release in rawhide: 0.000145-6.fc38 URL: http://search.cpan.org/dist/Test2-Suite/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/9536/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Test2-Suite -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2175432 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2175591] New: perl-DBD-Pg-3.16.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2175591 Bug ID: 2175591 Summary: perl-DBD-Pg-3.16.1 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DBD-Pg Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: dev...@gunduz.org, jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com, perl-devel@lists.fedoraproject.org, prais...@redhat.com, rhug...@redhat.com, rstr...@redhat.com, sandm...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 3.16.1 Upstream release that is considered latest: 3.16.1 Current version/release in rawhide: 3.16.0-3.fc38 URL: http://search.cpan.org/dist/DBD-Pg/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/2809/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-DBD-Pg -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2175591 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2175585] New: perl-Class-Method-Modifiers-2.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2175585 Bug ID: 2175585 Summary: perl-Class-Method-Modifiers-2.15 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Class-Method-Modifiers Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, mspa...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 2.15 Upstream release that is considered latest: 2.15 Current version/release in rawhide: 2.14-2.fc38 URL: http://search.cpan.org/dist/Class-Method-Modifiers Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/6735/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Class-Method-Modifiers -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2175585 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2174756] If I ask for my closed bugs it uses an old email address & gives nothing
https://bugzilla.redhat.com/show_bug.cgi?id=2174756 Jeff Fearn changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed||2023-03-06 00:48:42 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2174756 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
ffmpeg 6.x needed for HDR content decoding
February 28th, 2023, FFmpeg 6.0 "Von Neumann" A new major release, FFmpeg 6.0 "Von Neumann", is now available for download. This release has many new encoders and decoders, filters, ffmpeg CLI tool improvements, and also, changes the way releases are done. All major releases will now bump the version of the ABI. We plan to have a new major release each year. Another release-specific change is that deprecated APIs will be removed after 3 releases, upon the next major bump. This means that releases will be done more often and will be more organized. New decoders featured are Bonk, RKA, Radiance, SC-4, APAC, VQC, WavArc and a few ADPCM formats. QSV and NVenc now support AV1 encoding. The FFmpeg CLI (we usually reffer to it as ffmpeg.c to avoid confusion) has speed-up improvements due to threading, as well as statistics options, and the ability to pass option values for filters from a file. There are quite a few new audio and video filters, such as adrc, showcwt, backgroundkey and ssim360, with a few hardware ones too. Finally, the release features many behind-the-scenes changes, including a new FFT and MDCT implementation used in codecs (expect a blog post about this soon), numerous bugfixes, better ICC profile handling and colorspace signalling improvement, introduction of a number of RISC-V vector and scalar assembly optimized routines, and a few new improved APIs, which can be viewed in the doc/APIchanges file in our tree. A few submitted features, such as the Vulkan improvements and more FFT optimizations will be in the next minor release, 6.1, which we plan to release soon, in line with our new release schedule. Some highlights are: Radiance HDR image support ddagrab (Desktop Duplication) video capture filter ffmpeg -shortest_buf_duration option ffmpeg now requires threading to be built ffmpeg now runs every muxer in a separate thread Add new mode to cropdetect filter to detect crop-area based on motion vectors and edges VAAPI decoding and encoding for 10/12bit 422, 10/12bit 444 HEVC and VP9 WBMP (Wireless Application Protocol Bitmap) image format a3dscope filter bonk decoder and demuxer Micronas SC-4 audio decoder LAF demuxer APAC decoder and demuxer Media 100i decoders DTS to PTS reorder bsf ViewQuest VQC decoder backgroundkey filter nvenc AV1 encoding support MediaCodec decoder via NDKMediaCodec MediaCodec encoder oneVPL support for QSV QSV AV1 encoder QSV decoding and encoding for 10/12bit 422, 10/12bit 444 HEVC and VP9 showcwt multimedia filter corr video filter adrc audio filter afdelaysrc audio filter WADY DPCM decoder and demuxer CBD2 DPCM decoder ssim360 video filter ffmpeg CLI new options: -stats_enc_pre[_fmt], -stats_enc_post[_fmt], -stats_mux_pre[_fmt] hstack_vaapi, vstack_vaapi and xstack_vaapi filters XMD ADPCM decoder and demuxer media100 to mjpegb bsf ffmpeg CLI new option: -fix_sub_duration_heartbeat WavArc decoder and demuxer CrystalHD decoders deprecated SDNS demuxer RKA decoder and demuxer filtergraph syntax in ffmpeg CLI now supports passing file contents as option values hstack_qsv, vstack_qsv and xstack_qsv filters We strongly recommend users, distributors, and system integrators to upgrade unless they use current git master. https://ffmpeg.org/download.html#release_6.0 ___ 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
libgit2 1.6.x in rawhide and F38 with a compat package for 1.5.x
I just bumped libgit2 to 1.6.x in both rawhide and F38 and added a compat package for the old 1.5.x ABI. This should allow seamless switchover to the new ABI without breaking anything that needs 1.5.x. Let me know if you run into issues with this. The compat package system for libgit2 is still new and may have some teething issues. Here is the F38 update: https://bodhi.fedoraproject.org/updates/FEDORA-2023-fdee262d55I left gnome-builder out of it as amigadave has gnome-builder updates pending. Packages still using old libgit2 versions: 1.3: nothing left so I just retired the libgit2_1.3 package in rawhide. Will do the same in F38 once the freeze is over.1.4: julia, rpm-git-tag-sort1.5: R-gert, git-time-metric, python-pygit2, rust Pete___ 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: Firecracker microVM manager
On Sun, Mar 5, 2023 at 1:31 AM David Michael wrote: > > Okay, thanks for all the feedback. I interpret this as essentially > requiring the use of the glibc Rust target for inclusion in Fedora, so > the changes on the Fedora side would be reduced to adding a couple > dozen crates and ideally supporting the kernel as a guest. That > shifts the bulk of the work to getting glibc fully supported upstream, > and running a not-quite-as-secure build until then. I'll investigate > this, and if there are no other blockers, maybe I can start sending > review requests for the glibc build. Sounds great! If you need help with the Rust packaging side of things, feel free to reach out. The Rust SIG is available on the "rust" list, in "#fedora-rust" on irc.libera.chat, or in the "Fedora Rust" room on the Fedora Matrix server. Either me or somebody else should be able to help pretty quickly if you're having trouble with Rust packaging toolchain, or if you need reviewers for packages for new crates. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2175475] perl-Perl-Critic-1.150 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2175475 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #3 from Fedora Update System --- FEDORA-2023-1a11dd77b1 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1a11dd77b1 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2175475 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: JupyterLab finally in Fedora and the future of Jupyter Notebook
On 05. 03. 23 18:17, Lumír Balhar wrote: Should we include JupyterLab in Fedora 39 Python Classroom Lab? Adding it there soon might help us with testing but users of Classroom lab might want better stability. What do you think? Should be add it there now or wait at least for the stable release? I'd say users who want such stability don't generally use Rawhide. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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: JupyterLab finally in Fedora and the future of Jupyter Notebook
On 05. 03. 23 18:17, Lumír Balhar wrote: Should we include JupyterLab in Fedora 39 Python Classroom Lab? Adding it there soon might help us with testing but users of Classroom lab might want better stability. What do you think? Should be add it there now or wait at least for the stable release? I'd say users who want such stability don't generally use Rawhide. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2170646] Please branch and build perl-Config-Grammar for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2170646 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2023-d0d4fb8dfb has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-d0d4fb8dfb -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2170646 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: JupyterLab finally in Fedora and the future of Jupyter Notebook
On 3/5/23 16:19, Miro Hrončok wrote: On 05. 03. 23 12:32, Lumír Balhar wrote: Hi. There were some attempts to package JupyterLab (the first one in 2018) but none of them were successful. But now, after packaging 20 new Python and Rust packages, JupyterLab finally landed into rawhide. The main motivation for this effort is the ongoing plan to base the next version of Jupyter Notebook (version 7) on top of the components of JupyterLab. Take a look at JEP 79 is you want to know more about this - https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html So, how the future of Jupyter Notebook looks like in Fedora? In Fedora 37, there is still the old standalone Jupyter Notebook version 6.4 and nothing will change about it. Fedora 38 contains a slightly newer version of Jupyter Notebook (6.5 - the last release in 6). Everything looks the same as before but behind the curtains, the standard components Notebook is based on moved to a new package named nbclassic. This is gonna be important for Fedora 39. Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to update Jupyter Notebook to 7.0.0 alpha 14. So, there will be three options in rawhide you can choose from when working with ipynb files: * JupyterLab - new development environment with text editor, consoles, files browser and more. * Jupyter Notebook - document-centric UI you already know but looking a little bit different because it'll based on components from Jupyter lab. * Jupyter nbclassic - The good old Jupyter Notebook as you know it for years. This package should be supported upstream for 2 years after the stable version of Notebook v7 is released. Both JupyterLab and Notebook are currently alpha but the plan of upstream developers is to release stable releases before JupyterCon in May so we should have plenty of time to update the packages in rawhide before the beta freeze in August. If you want to use the new notebook v7 before I update it in rawhide, use this COPR: https://copr.fedorainfracloud.org/coprs/lbalhar/notebook/ Any help testing the prereleases is appreciated. Thank you, Lumír, for doing this! Should we include JupyterLab in Fedora 39 Python Classroom Lab? Adding it there soon might help us with testing but users of Classroom lab might want better stability. What do you think? Should be add it there now or wait at least for the stable release? If so, we need to add it here: https://pagure.io/fedora-comps/blob/main/f/comps-f39.xml.in Search for: python3-notebook ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: JupyterLab finally in Fedora and the future of Jupyter Notebook
On 3/5/23 16:19, Miro Hrončok wrote: On 05. 03. 23 12:32, Lumír Balhar wrote: Hi. There were some attempts to package JupyterLab (the first one in 2018) but none of them were successful. But now, after packaging 20 new Python and Rust packages, JupyterLab finally landed into rawhide. The main motivation for this effort is the ongoing plan to base the next version of Jupyter Notebook (version 7) on top of the components of JupyterLab. Take a look at JEP 79 is you want to know more about this - https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html So, how the future of Jupyter Notebook looks like in Fedora? In Fedora 37, there is still the old standalone Jupyter Notebook version 6.4 and nothing will change about it. Fedora 38 contains a slightly newer version of Jupyter Notebook (6.5 - the last release in 6). Everything looks the same as before but behind the curtains, the standard components Notebook is based on moved to a new package named nbclassic. This is gonna be important for Fedora 39. Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to update Jupyter Notebook to 7.0.0 alpha 14. So, there will be three options in rawhide you can choose from when working with ipynb files: * JupyterLab - new development environment with text editor, consoles, files browser and more. * Jupyter Notebook - document-centric UI you already know but looking a little bit different because it'll based on components from Jupyter lab. * Jupyter nbclassic - The good old Jupyter Notebook as you know it for years. This package should be supported upstream for 2 years after the stable version of Notebook v7 is released. Both JupyterLab and Notebook are currently alpha but the plan of upstream developers is to release stable releases before JupyterCon in May so we should have plenty of time to update the packages in rawhide before the beta freeze in August. If you want to use the new notebook v7 before I update it in rawhide, use this COPR: https://copr.fedorainfracloud.org/coprs/lbalhar/notebook/ Any help testing the prereleases is appreciated. Thank you, Lumír, for doing this! Should we include JupyterLab in Fedora 39 Python Classroom Lab? Adding it there soon might help us with testing but users of Classroom lab might want better stability. What do you think? Should be add it there now or wait at least for the stable release? If so, we need to add it here: https://pagure.io/fedora-comps/blob/main/f/comps-f39.xml.in Search for: python3-notebook ___ 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
[Test-Announce] 2023-03-06 @ 17:00 UTC - Fedora 38 Blocker Review Meeting
# F37 Blocker Review meeting # Date: 2023-03-06 # Time: 17:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 4 proposed Beta blockers, 10 proposed Beta freeze exceptions and 7 proposed Final blockers to review, so let's have a review meeting. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F38 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-03-06 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-03-06 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.libera.chat Greetings testers! It's meeting time again! We're in freeze and on the track to F38 Beta now. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 38 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Packaging portmidi versions: devel conflicts OK?
> I think so , see openssl example : > > dnf install openssl1.1-devel openssl-devel > > Package openssl-devel-1:3.0.8-1.fc37.x86_64 is already installed. > Error: > Problem: problem with installed package openssl-devel-1:3.0.8- > 1.fc37.x86_64 > - package openssl1.1-devel-1:1.1.1q-2.fc37.i686 conflicts with openssl- > devel provided by openssl-devel-1:3.0.8-1.fc37.x86_64 > - package openssl1.1-devel-1:1.1.1q-2.fc37.i686 conflicts with openssl- > devel provided by openssl-devel-1:3.0.5-3.fc37.x86_64 > - conflicting requests > - package openssl1.1-devel-1:1.1.1q-2.fc37.x86_64 conflicts with > openssl-devel provided by openssl-devel-1:3.0.8-1.fc37.x86_64 > - package openssl1.1-devel-1:1.1.1q-2.fc37.x86_64 conflicts with > openssl-devel provided by openssl-devel-1:3.0.5-3.fc37.x86_64 Thanks for pointing this out. Their compat had this in spec: ``` # The devel subpackage intentionally conflicts with main openssl-devel # as simultaneous use of both openssl package cannot be encouraged. # Making the packages non-conflicting would also require further # changes in the dependent packages. Conflicts: openssl-devel ``` I'm not sure this beats packaging guidelines, though ... ___ 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: JupyterLab finally in Fedora and the future of Jupyter Notebook
On 05. 03. 23 12:32, Lumír Balhar wrote: Hi. There were some attempts to package JupyterLab (the first one in 2018) but none of them were successful. But now, after packaging 20 new Python and Rust packages, JupyterLab finally landed into rawhide. The main motivation for this effort is the ongoing plan to base the next version of Jupyter Notebook (version 7) on top of the components of JupyterLab. Take a look at JEP 79 is you want to know more about this - https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html So, how the future of Jupyter Notebook looks like in Fedora? In Fedora 37, there is still the old standalone Jupyter Notebook version 6.4 and nothing will change about it. Fedora 38 contains a slightly newer version of Jupyter Notebook (6.5 - the last release in 6). Everything looks the same as before but behind the curtains, the standard components Notebook is based on moved to a new package named nbclassic. This is gonna be important for Fedora 39. Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to update Jupyter Notebook to 7.0.0 alpha 14. So, there will be three options in rawhide you can choose from when working with ipynb files: * JupyterLab - new development environment with text editor, consoles, files browser and more. * Jupyter Notebook - document-centric UI you already know but looking a little bit different because it'll based on components from Jupyter lab. * Jupyter nbclassic - The good old Jupyter Notebook as you know it for years. This package should be supported upstream for 2 years after the stable version of Notebook v7 is released. Both JupyterLab and Notebook are currently alpha but the plan of upstream developers is to release stable releases before JupyterCon in May so we should have plenty of time to update the packages in rawhide before the beta freeze in August. If you want to use the new notebook v7 before I update it in rawhide, use this COPR: https://copr.fedorainfracloud.org/coprs/lbalhar/notebook/ Any help testing the prereleases is appreciated. Thank you, Lumír, for doing this! Should we include JupyterLab in Fedora 39 Python Classroom Lab? If so, we need to add it here: https://pagure.io/fedora-comps/blob/main/f/comps-f39.xml.in Search for: python3-notebook -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: JupyterLab finally in Fedora and the future of Jupyter Notebook
On 05. 03. 23 12:32, Lumír Balhar wrote: Hi. There were some attempts to package JupyterLab (the first one in 2018) but none of them were successful. But now, after packaging 20 new Python and Rust packages, JupyterLab finally landed into rawhide. The main motivation for this effort is the ongoing plan to base the next version of Jupyter Notebook (version 7) on top of the components of JupyterLab. Take a look at JEP 79 is you want to know more about this - https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html So, how the future of Jupyter Notebook looks like in Fedora? In Fedora 37, there is still the old standalone Jupyter Notebook version 6.4 and nothing will change about it. Fedora 38 contains a slightly newer version of Jupyter Notebook (6.5 - the last release in 6). Everything looks the same as before but behind the curtains, the standard components Notebook is based on moved to a new package named nbclassic. This is gonna be important for Fedora 39. Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to update Jupyter Notebook to 7.0.0 alpha 14. So, there will be three options in rawhide you can choose from when working with ipynb files: * JupyterLab - new development environment with text editor, consoles, files browser and more. * Jupyter Notebook - document-centric UI you already know but looking a little bit different because it'll based on components from Jupyter lab. * Jupyter nbclassic - The good old Jupyter Notebook as you know it for years. This package should be supported upstream for 2 years after the stable version of Notebook v7 is released. Both JupyterLab and Notebook are currently alpha but the plan of upstream developers is to release stable releases before JupyterCon in May so we should have plenty of time to update the packages in rawhide before the beta freeze in August. If you want to use the new notebook v7 before I update it in rawhide, use this COPR: https://copr.fedorainfracloud.org/coprs/lbalhar/notebook/ Any help testing the prereleases is appreciated. Thank you, Lumír, for doing this! Should we include JupyterLab in Fedora 39 Python Classroom Lab? If so, we need to add it here: https://pagure.io/fedora-comps/blob/main/f/comps-f39.xml.in Search for: python3-notebook -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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: Packaging portmidi versions: devel conflicts OK?
> On Sat, Mar 4, 2023 at 8:13 AM Michael J Gruber wrote:
>
>
> Compatibility packages do not get a "compat-" prefix any more; they only
> get a version suffix. The old portmidi could be portmidi217 (to match the
> old versioning) or possibly portmidi0 (to match the soversion). It's also
> preferred (but I'm not sure that it's written down or is just a discussion
> within the FPC right now) that the un-suffixed version is the latest one.
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple
Good point. Whether it's required or just preferred - it's a recommendation
which I should follow, and why I've been asking here :)
It forces depending packages to choose between changing their BuildRequires (to
the new name for the old version) or adjusting if needed (to the new version).
It also forces me to introduce epoch so that version 2.0.4 will be an update of
the existing 217, right?
Now the big question is: In which releases can I rename the package? I'm afraid
the answer will be "rawhide only", which means "new" portmidi will be in Fedora
39 only. Or can I have "portmidi0 + portmidi" there and "portmidi + portmidi2"
in releases branches?
> Compatibility packages do not need a review.
> https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuideline...
That much is clear. Your preference provides an answer to another question of
mine: "... and MUST NOT conflict with all other versions of the same package."
So, while openssl seems to violate that for whatever reasons, I cannot do the
same.
So, technically speaking:
- I go through the new-package process for a new package (the compat package)
but note that no review is required.
- Import the package (and history) into the newly created dist-git repo and
rewrite the spec for the new name (portmidi0 or such).
- Update the package in the old dist-git repo to the new repo.
Or do I request a new repo "portmidi2" and build the new "portmidi" from there
("and portmidi0" from the "portmidi" dist-git repo)?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 compose report: 20230305.n.0 changes
OLD: Fedora-38-20230304.n.0 NEW: Fedora-38-20230305.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230304.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
JupyterLab finally in Fedora and the future of Jupyter Notebook
Hi. There were some attempts to package JupyterLab (the first one in 2018) but none of them were successful. But now, after packaging 20 new Python and Rust packages, JupyterLab finally landed into rawhide. The main motivation for this effort is the ongoing plan to base the next version of Jupyter Notebook (version 7) on top of the components of JupyterLab. Take a look at JEP 79 is you want to know more about this - https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html So, how the future of Jupyter Notebook looks like in Fedora? In Fedora 37, there is still the old standalone Jupyter Notebook version 6.4 and nothing will change about it. Fedora 38 contains a slightly newer version of Jupyter Notebook (6.5 - the last release in 6). Everything looks the same as before but behind the curtains, the standard components Notebook is based on moved to a new package named nbclassic. This is gonna be important for Fedora 39. Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to update Jupyter Notebook to 7.0.0 alpha 14. So, there will be three options in rawhide you can choose from when working with ipynb files: * JupyterLab - new development environment with text editor, consoles, files browser and more. * Jupyter Notebook - document-centric UI you already know but looking a little bit different because it'll based on components from Jupyter lab. * Jupyter nbclassic - The good old Jupyter Notebook as you know it for years. This package should be supported upstream for 2 years after the stable version of Notebook v7 is released. Both JupyterLab and Notebook are currently alpha but the plan of upstream developers is to release stable releases before JupyterCon in May so we should have plenty of time to update the packages in rawhide before the beta freeze in August. If you want to use the new notebook v7 before I update it in rawhide, use this COPR: https://copr.fedorainfracloud.org/coprs/lbalhar/notebook/ Any help testing the prereleases is appreciated. Have a nice day. Lumír ___ 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
JupyterLab finally in Fedora and the future of Jupyter Notebook
Hi. There were some attempts to package JupyterLab (the first one in 2018) but none of them were successful. But now, after packaging 20 new Python and Rust packages, JupyterLab finally landed into rawhide. The main motivation for this effort is the ongoing plan to base the next version of Jupyter Notebook (version 7) on top of the components of JupyterLab. Take a look at JEP 79 is you want to know more about this - https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html So, how the future of Jupyter Notebook looks like in Fedora? In Fedora 37, there is still the old standalone Jupyter Notebook version 6.4 and nothing will change about it. Fedora 38 contains a slightly newer version of Jupyter Notebook (6.5 - the last release in 6). Everything looks the same as before but behind the curtains, the standard components Notebook is based on moved to a new package named nbclassic. This is gonna be important for Fedora 39. Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to update Jupyter Notebook to 7.0.0 alpha 14. So, there will be three options in rawhide you can choose from when working with ipynb files: * JupyterLab - new development environment with text editor, consoles, files browser and more. * Jupyter Notebook - document-centric UI you already know but looking a little bit different because it'll based on components from Jupyter lab. * Jupyter nbclassic - The good old Jupyter Notebook as you know it for years. This package should be supported upstream for 2 years after the stable version of Notebook v7 is released. Both JupyterLab and Notebook are currently alpha but the plan of upstream developers is to release stable releases before JupyterCon in May so we should have plenty of time to update the packages in rawhide before the beta freeze in August. If you want to use the new notebook v7 before I update it in rawhide, use this COPR: https://copr.fedorainfracloud.org/coprs/lbalhar/notebook/ Any help testing the prereleases is appreciated. Have a nice day. Lumír ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2175333] perl-HTTP-BrowserDetect-3.38 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2175333 Emmanuel Seyman changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |CLOSED Resolution|--- |RAWHIDE Fixed In Version||perl-HTTP-BrowserDetect-3.3 ||8-1.fc39 Last Closed||2023-03-05 10:00:39 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2165101 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2175333 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
