Re: The Javapocalypse is Monday
On 6/3/21 3:55 PM, Sérgio Basto wrote: On Thu, 2021-06-03 at 15:30 -0600, Jerry James wrote: I've just been looking through my packager-dashboard page. A depressingly large chunk of my packages are going to become unbuildable on Monday when a bunch of orphaned Java packages are retired. I think a lot of us are going to be affected. In my case, there are quite a few non-Java packages involved (due to the parser generators antlr3 and antlr4-project), primarily OCaml and python packages. Mikolaj has a huge pile of work on his shoulders, so don't take this as criticism of him. Here are some of the pain points: - log4j will be retired, which will break ant. - hamcrest2 will be retired, which will break apache-commons-lang3, which will break bcel, which will also break ant. - google-gson and javassist will be retired, which will break reflections, which will break jna, which is used by about a dozen packages, including bcel. I may take these 4 Just to be clear - "hamcrest" is now at version "2.2" and so should replace "hamcrest2". -- Orion Poplawski he/him/his - surely the least important thing about me 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
x86_64 and -mcx16
I'm curious if there are other ideas out there for how to deal with this: From https://bugzilla.redhat.com/show_bug.cgi?id=1965692: I recently acquired a cheap wintel toy tablet/laptop (a Kano PC), which has a Celeron N4000 processor. I tried running HPL benchmarks on it to figure out how fast the thing is. However, xhpl_openmpi crashed with an illegal instruction. I then installed the MPICH version of HPL, and xhpl_mpich runs fine. The issue is thus in OpenMPI. Looking at the build logs of openmpi-4.1.0-5.fc34.x86_64, I see that it has been compiled with the -mcx16 flag detected by configure. According to the GCC man page This option enables GCC to generate "CMPXCHG16B" instructions in 64-bit code to implement compare-and-exchange operations on 16-byte aligned 128-bit objects. This is useful for atomic updates of data structures exceeding one machine word in size. The compiler uses this instruction to implement __sync Builtins. However, for __atomic Builtins operating on 128-bit integers, a library call is always used. However, because the instruction is not available on all x86_64 processors, the use of the flag should be disabled in OpenMPI. I filed https://github.com/open-mpi/ompi/issues/9022 and we seem to have the ability to disable this now. Does this seem like the right solution? It does seem a shame to have to cripple the compile though. There was mention of setting -march - is that appropriate? Thanks, Orion -- Orion Poplawski he/him/his - surely the least important thing about me 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a20d7c1ddd rxvt-unicode-9.26-1.el8 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-bdd3e1ab81 opendmarc-1.4.1-1.el8 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-6c72c1c9a5 gromacs-2019.6-2.el8 kokkos-3.0.00-2.el8 slurm-20.11.7-2.el8 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-0e0c1a76c6 slurm-20.11.7-3.el8 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-c734316809 chromium-90.0.4430.212-1.el8 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-bb6ec0e942 singularity-3.7.4-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1dd57fe441 radsecproxy-1.9.0-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing libdispatch-5.4.1-1.el8 libtpms-0.8.3-0.20210601git9e736d5281.el8.1 mongo-c-driver-1.17.6-2.el8 pdsh-2.34-4.el8 scitokens-cpp-0.6.2-1.el8 Details about builds: libdispatch-5.4.1-1.el8 (FEDORA-EPEL-2021-4b67864af9) Apple's Grand Central Dispatch library Update Information: Updated to 5.4.1-RELEASE ChangeLog: libtpms-0.8.3-0.20210601git9e736d5281.el8.1 (FEDORA-EPEL-2021-f06229dba2) Library providing Trusted Platform Module (TPM) functionality Update Information: Update to 0.8.3 ChangeLog: * Tue Jun 1 2021 Stefan Berger - 0.8.3-0.20210601git9e736d5281 - tpm2: Work-around for Windows 2016 & 2019 bug related to ContextLoad mongo-c-driver-1.17.6-2.el8 (FEDORA-EPEL-2021-40da4f666a) Client library written in C for MongoDB Update Information: * Fix possible crash when speculative authentication fails with network error. ChangeLog: * Thu Jun 3 2021 Remi Collet - 1.17.6-2 - update to 1.17.6 - fix invalid rpath pdsh-2.34-4.el8 (FEDORA-EPEL-2021-6635a8ea5e) Parallel remote shell program Update Information: Add pdsh to EPEL8 ChangeLog: References: [ 1 ] Bug #1960006 - Add EPEL8 build of pdsh https://bugzilla.redhat.com/show_bug.cgi?id=1960006 [ 2 ] Bug #1967184 - Non-responsive maintainer check for dmlb2000 https://bugzilla.redhat.com/show_bug.cgi?id=1967184 scitokens-cpp-0.6.2-1.el8 (FEDORA-EPEL-2021-33b1e570c3) C++ Implementation of the SciTokens Library Update Information: Correct WLCG compat for condor read permissions Fix vector resize for el8+ builds - Fix compilation errors on c++11 - Update to jwt-cpp-0.4.0 vendor - Change scitoken profile name to match spec, scitoken:2.0 ChangeLog: * Thu Jun 3 2021 Derek Weitzel - 0.6.2-1 - Correct WLCG compat for condor read permissions * Thu May 20 2021 Derek Weitzel - 0.6.1-1 - Fix vector resize for el8+ builds * Tue May 18 2021 Derek Weitzel - 0.6.0-2 - Add back paren patch * Tue Mar 9 2021 Derek Weitzel - 0.6.0-1 - Fix compilation errors on c++11 - Update to jwt-cpp-0.4.0 vendor - Change scitoken profile name to match spec, scitoken:2.0 * Wed Jan 27 2021 Fedora Release Engineering - 0.5.1-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-6cc996cdc4 opendmarc-1.4.1-1.el7 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-969456590e rxvt-unicode-9.21-4.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-0fec8057df python3-lxml-4.2.5-4.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-17f170d38c caribou0-0.4.21-26.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7e9a7ecfb4 slurm-20.11.7-3.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-0402b44d82 chromium-90.0.4430.212-1.el7 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-15abda18e1 singularity-3.7.4-1.el7 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1f259a45ef openjpeg2-2.3.1-11.el7 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9eaea6f65c audacious-plugins-4.0.5-4.el7 fluidsynth-2.1.8-4.el7 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f706ca6458 radsecproxy-1.9.0-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-8c50b78c57 nginx-1.20.1-2.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing pdsh-2.34-4.el7 scitokens-cpp-0.6.2-1.el7 Details about builds: pdsh-2.34-4.el7 (FEDORA-EPEL-2021-83835fa4a7) Parallel remote shell program Update Information: Bugfix release for pdsh on EPEL7 ChangeLog: * Tue Jan 26 2021 Fedora Release Engineering - 2.34-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Sat Aug 1 2020 Fedora Release Engineering - 2.34-3 - Second attempt - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Tue Jul 28 2020 Fedora Release Engineering - 2.34-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Thu Jun 18 2020 Tom Callaway - 2.34-1 - update to 2.34 * Wed Jan 29 2020 Fedora Release Engineering - 2.33-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild * Mon Nov 18 2019 Tom Callaway - 2.33-1 - update to 2.33 * Fri Jul 26 2019 Fedora Release Engineering - 2.31-15 - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild * Sun Feb 17 2019 Igor Gnatenko - 2.31-14 - Rebuild for readline 8.0 * Fri Feb 1 2019 Fedora Release Engineering - 2.31-13 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Fri Jul 13 2018 Fedora Release Engineering - 2.31-12 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Thu Feb 8 2018 Fedora Release Engineering - 2.31-11 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild * Thu Aug 3 2017 Fedora Release Engineering - 2.31-10 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild * Thu Jul 27 2017 Fedora Release Engineering - 2.31-9 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild * Sat Feb 11 2017 Fedora Release Engineering - 2.31-8 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild * Thu Jan 12 2017 Igor Gnatenko - 2.31-7 - Rebuild for readline 7.x * Thu Feb 4 2016 Fedora Release Engineering - 2.31-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild * Tue Jan 19 2016 Tom Callaway - 2.31-5 - spec file cleanups scitokens-cpp-0.6.2-1.el7 (FEDORA-EPEL-2021-d2929dc053) C++ Implementation of the SciTokens Library Update Information: Correct WLCG compat for condor read permissions Fix vector resize for el8+ builds - Fix compilation errors on c++11 - Update to jwt-cpp-0.4.0 vendor - Change scitoken profile name to match spec, scitoken:2.0 ChangeLog: * Thu Jun 3 2021 Derek Weitzel - 0.6.2-1 - Correct WLCG compat for condor read permissions * Thu May 20 2021 Derek Weitzel - 0.6.1-1 - Fix vector resize for el8+ builds * Tue May 18 2021 Derek Weitzel - 0.6.0-2 - Add back paren patch * Tue Mar 9 2021 Derek Weitzel - 0.6.0-1 - Fix compilation errors on c++11 - Update to jwt-cpp-0.4.0 vendor - Change scitoken profile name to match spec, scitoken:2.0 * Wed Jan 27 2021 Fedora Release Engineering - 0.5.1-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an
[Bug 1967347] perl-Socket-2.032 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967347 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System --- FEDORA-2021-d42c1e5851 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d42c1e5851` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d42c1e5851 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1963113] perl-CPAN-Perl-Releases-5.20210521 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1963113 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210521-1.fc35 |0210521-1.fc35 |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210521-1.fc33 |0210521-1.fc33 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc34 --- Comment #6 from Fedora Update System --- FEDORA-2021-c69a79afcc has been pushed to the Fedora 34 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1962958] perl-CPAN-Perl-Releases-5.20210520 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1962958 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210520-1.fc35 |0210520-1.fc35 |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210521-1.fc33 |0210521-1.fc33 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc34 --- Comment #10 from Fedora Update System --- FEDORA-2021-c69a79afcc has been pushed to the Fedora 34 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1957176] perl-CPAN-Perl-Releases-5.20210505 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1957176 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210505-1.fc35 |0210505-1.fc35 |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210521-1.fc33 |0210521-1.fc33 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc34 --- Comment #16 from Fedora Update System --- FEDORA-2021-c69a79afcc has been pushed to the Fedora 34 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1960857] perl-CPAN-Perl-Releases-5.20210515 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1960857 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210515-1.fc35 |0210515-1.fc35 |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210521-1.fc33 |0210521-1.fc33 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc34 --- Comment #11 from Fedora Update System --- FEDORA-2021-c69a79afcc has been pushed to the Fedora 34 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1963116] perl-Module-CoreList-5.20210521 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1963116 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Module-CoreList-5.2021 |perl-Module-CoreList-5.2021 |0521-1.fc35 |0521-1.fc35 |perl-Module-CoreList-5.2021 |perl-Module-CoreList-5.2021 |0521-1.fc33 |0521-1.fc33 ||perl-Module-CoreList-5.2021 ||0521-1.fc34 --- Comment #6 from Fedora Update System --- FEDORA-2021-8915f36bea has been pushed to the Fedora 34 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1962952] perl-Module-CoreList-5.20210520 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1962952 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Module-CoreList-5.2021 |perl-Module-CoreList-5.2021 |0520-1.fc35 |0520-1.fc35 |perl-Module-CoreList-5.2021 |perl-Module-CoreList-5.2021 |0521-1.fc33 |0521-1.fc33 ||perl-Module-CoreList-5.2021 ||0521-1.fc34 --- Comment #9 from Fedora Update System --- FEDORA-2021-8915f36bea has been pushed to the Fedora 34 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1963113] perl-CPAN-Perl-Releases-5.20210521 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1963113 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210521-1.fc35 |0210521-1.fc35 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc33 Resolution|--- |ERRATA Last Closed||2021-06-04 01:02:47 --- Comment #5 from Fedora Update System --- FEDORA-2021-66a33e03bb has been pushed to the Fedora 33 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1960857] perl-CPAN-Perl-Releases-5.20210515 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1960857 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210515-1.fc35 |0210515-1.fc35 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc33 Resolution|--- |ERRATA Last Closed||2021-06-04 01:02:43 --- Comment #10 from Fedora Update System --- FEDORA-2021-66a33e03bb has been pushed to the Fedora 33 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1962958] perl-CPAN-Perl-Releases-5.20210520 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1962958 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210520-1.fc35 |0210520-1.fc35 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc33 Resolution|--- |ERRATA Last Closed||2021-06-04 01:02:45 --- Comment #9 from Fedora Update System --- FEDORA-2021-66a33e03bb has been pushed to the Fedora 33 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1957176] perl-CPAN-Perl-Releases-5.20210505 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1957176 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0210505-1.fc35 |0210505-1.fc35 ||perl-CPAN-Perl-Releases-5.2 ||0210521-1.fc33 Resolution|--- |ERRATA Last Closed||2021-06-04 01:02:41 --- Comment #15 from Fedora Update System --- FEDORA-2021-66a33e03bb has been pushed to the Fedora 33 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1963116] perl-Module-CoreList-5.20210521 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1963116 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-Module-CoreList-5.2021 |perl-Module-CoreList-5.2021 |0521-1.fc35 |0521-1.fc35 ||perl-Module-CoreList-5.2021 ||0521-1.fc33 Resolution|--- |ERRATA Last Closed||2021-06-04 01:02:39 --- Comment #5 from Fedora Update System --- FEDORA-2021-beedf43562 has been pushed to the Fedora 33 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1962952] perl-Module-CoreList-5.20210520 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1962952 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-Module-CoreList-5.2021 |perl-Module-CoreList-5.2021 |0520-1.fc35 |0520-1.fc35 ||perl-Module-CoreList-5.2021 ||0521-1.fc33 Resolution|--- |ERRATA Last Closed||2021-06-04 01:02:37 --- Comment #8 from Fedora Update System --- FEDORA-2021-beedf43562 has been pushed to the Fedora 33 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. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: Make btrfs the default file system for Fedora Cloud (System-Wide Change proposal)
> Am 03.06.2021 um 15:35 schrieb Dusty Mabe :
>
>
>
> On 6/2/21 5:28 AM, Peter Boy wrote:
>>
>>
>>
>> very nicely put. According to Matthew and others cloud wg did virtually not
>> exist for more than a year, no meetings, silence on mailing list beyond
>> bi-weekly announcement of a „standing“ meeting nobody attended to, there was
>> discussion to „kill“ it, great reluctance on the side of Dusty in our
>> meeting March 3 to make any changes on the artefacts at all, new start of
>> 2-weekly meetings March 30, „months of conversation“ which spell down to 4
>> meetings in 2 months, and then such a very fundamental change. Well, the
>> wording may be a bit offhand, but by no means farfetched.
>
> We typically run meetings every two weeks, but that did stop happening when I
> was away earlier this year. There is some truth in here though.
To clear up any misunderstanding: I am in no way criticizing or disliking the
way the Cloud WG works. It is about rebutting the attempt of a subsequent
legitimization ("months of discussion") by the facts as they are.
> https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_meeting/fedora_cloud_meeting.2021-05-11-15.58.log.txt
> 16:18:15 There is also the discussion of merging with the server
> WG - if we change to BTRFS does that inhibit that potential path for us (i.e.
> should we get server to buy in on the FS change too, or maybe they have
> already)?
I do not want any misunderstanding here either. This passage has nothing to do
with you. It is about the fact that all Cloud WG members have known from the
very beginning that there are considerations about a cooperation. No one can
pretend not to have known (some Cloud members asked me for proof of the
existence of this discussion). Everybody knew pretty well what he was doing.
> Maybe we can get everyone together to discuss all
> the various options and the best path forward?
I would still very much welcome and advocate that. However, some Server WG
members are already a bit annoyed and feel little inclination to let the server
WG eventually get infected, too. In our discussion yesterday, I would have
preferred to keep all options open and carefully weigh all arguments and
options before making any commitment to one option.
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: The Javapocalypse is Monday
On 03. 06. 21 23:30, Jerry James wrote: - hamcrest2 will be retired, which will break apache-commons-lang3, Package "hamcrest" was updated to 2.x, so this should be OK. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/EIU7CNABRKL5EFZNCFIWQIK2AHIEKWBB/ -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The Javapocalypse is Monday
On Thu, 2021-06-03 at 15:30 -0600, Jerry James wrote: > I've just been looking through my packager-dashboard page. A > depressingly large chunk of my packages are going to become > unbuildable on Monday when a bunch of orphaned Java packages are > retired. I think a lot of us are going to be affected. In my case, > there are quite a few non-Java packages involved (due to the parser > generators antlr3 and antlr4-project), primarily OCaml and python > packages. Mikolaj has a huge pile of work on his shoulders, so don't > take this as criticism of him. > > Here are some of the pain points: > - log4j will be retired, which will break ant. > - hamcrest2 will be retired, which will break apache-commons-lang3, > which will break bcel, which will also break ant. > - google-gson and javassist will be retired, which will break > reflections, which will break jna, which is used by about a dozen > packages, including bcel. I may take these 4 > - maven-install-plugin will be retired, which will break tycho, which > will break eclipse. Eclipse for me may fall, I already use eclipse installer from https://www.eclipse.org/downloads/ > - args4j will be retired, which will break jacoco and jgit. > - maven-invoker-plugin and several of its dependencies > (maven-doxia-sitetools, plexus-velocity, maven-reporting-api, > maven-script-interpreter, and maven-reporting-impl) will be retired, > which will break xml-maven-plugin, which is used by eclipse. > - jakarta-el and jakarta-server-pages will be retired, which will > break eclipse. > - aopalliance will be retired, which will break maven-native. > - jdependency will be retired, which will break maven-shade-plugin, > which is used by openjfx8, a dependency of java-1.8.0-openjdk. > - apache-ivy will be retired, which will break javapackages-tools. > I can also take these two jdependency and apache-ivy . maybe I should also take maven-invoker-plugin . what do you think ? > I have packages that depend directly on the following, so I am > willing > to adopt them if nobody more competent shows up (although there is no > point in taking ant-contrib if ant is going to be broken anyway): > - ant-contrib > - jakarta-common-httpclient > - jakarta-ws-rs > - maven-invoker-plugin > - spec-version-maven-plugin > > I introduced the jansi1 and jline2 packages so that jansi could be > moved to 2.x and jline to 3.x, but I don't actually maintain any > packages that need the old versions. I would like to give them away > to someone who needs them, but note that you will need to grab > jansi-native as well, before Monday! > > Has anybody already done something about any of these packages (and > my > packager-dashboard page just hasn't caught up yet)? Is anybody > planning to do something about any of these packages before they are > retired on Monday? > -- > Jerry James > http://www.jamezone.org/ > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Take the new Annual Fedora Contributor Survey
> Am 03.06.2021 um 20:00 schrieb Bruno Wolff III : > > Given that badges are being handed out, it is clear the survey is not > anonymous. > > People that do surveys love to claim they are anonymous when they aren't, to > increase the response. When you are collecting detailed information from > someone it is hard to prevent the person from being identified by that data > even if you don't collect their identity directly. From a point of social survey: if it is hard to identify a person by the survey data depends of the data and the sample. Given the questions of the Fedora survey it will be hard. You would need additional data, e.g. the IP address or other user specific data stored together (or linked) to the answers (as all those „social“ media try). That would be a gross breach of trust and malpractice. And the standard software for online surveys does not include it as an option. > If you have people authenticate or send out links to the survey that are > customised per person (perhaps to prevent someone from filling out the survey > repeatedly) then the survey is clearly not anonymous. Even if you don't do > that, web server logs can often reveal who the responders are. From a point of social survey: Anonymous refers to the attribution of the response graph to an individual (rsp. the lack of), not whether someone participated. > In my opinion it is best to state what you are actually doing with regards to > privacy rather than simplify it and make a statement that is clearly false. It’s not clearly false, but nevertheless a somewhat more detailed note might be useful. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)
On Thu, Jun 3, 2021 at 4:53 PM Marcin Juszkiewicz wrote: > > W dniu 03.06.2021 o 22:35, Ben Cotton pisze: > > https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot > > > > == Summary == > > > > With recent changes in public cloud widely accepting the > > use of UEFI boot, it would be consistent to add hybrid boot in support of > > both unifying the legacy (BIOS) and UEFI boot to the Fedora Linux > > cloud base images. > > > > > == Detailed Description == > > The Fedora Cloud Edition image will be updated to be configured with > > multiple partitions and a GPT label instead of one single partition > > and implicit MBR. > > > > The partition order will be: > > > > # A BIOS boot partition > > # An EFI System partition > > # A general data partition > > Please make first partition at least 4MB in size. Those Arm/AArch64 > systems which store bootloaders on boot media will have a space for it > (as some already read from around that area). Sure we can, but for AArch64 images, wouldn't we just be UEFI only anyway? I think we already produce these images as UEFI only for AArch64... -- 真実はいつも一つ！/ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The Javapocalypse is Monday
I knew that a bunch of java stuff was going away, but I am not sure what the impact of that is going to be. Is there a feature page or similar that summarizes what the effect we be? I have one package that produces a java program using ant that I like to be able to keep building somehow. There is also an OCaml package I help maintain, that is used in an old game that I doubt gets much use these days and I wouldn't be too sad if that went away. Is there a recommendation to move to maven? Is there anything like the old gcc based java compiler that could be used? Is there still going to be a java runtime? I spend a lot of time using the former as a passtime game and would miss it if it wasn't in Fedora any more. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
The Javapocalypse is Monday
I've just been looking through my packager-dashboard page. A depressingly large chunk of my packages are going to become unbuildable on Monday when a bunch of orphaned Java packages are retired. I think a lot of us are going to be affected. In my case, there are quite a few non-Java packages involved (due to the parser generators antlr3 and antlr4-project), primarily OCaml and python packages. Mikolaj has a huge pile of work on his shoulders, so don't take this as criticism of him. Here are some of the pain points: - log4j will be retired, which will break ant. - hamcrest2 will be retired, which will break apache-commons-lang3, which will break bcel, which will also break ant. - google-gson and javassist will be retired, which will break reflections, which will break jna, which is used by about a dozen packages, including bcel. - maven-install-plugin will be retired, which will break tycho, which will break eclipse. - args4j will be retired, which will break jacoco and jgit. - maven-invoker-plugin and several of its dependencies (maven-doxia-sitetools, plexus-velocity, maven-reporting-api, maven-script-interpreter, and maven-reporting-impl) will be retired, which will break xml-maven-plugin, which is used by eclipse. - jakarta-el and jakarta-server-pages will be retired, which will break eclipse. - aopalliance will be retired, which will break maven-native. - jdependency will be retired, which will break maven-shade-plugin, which is used by openjfx8, a dependency of java-1.8.0-openjdk. - apache-ivy will be retired, which will break javapackages-tools. I have packages that depend directly on the following, so I am willing to adopt them if nobody more competent shows up (although there is no point in taking ant-contrib if ant is going to be broken anyway): - ant-contrib - jakarta-common-httpclient - jakarta-ws-rs - maven-invoker-plugin - spec-version-maven-plugin I introduced the jansi1 and jline2 packages so that jansi could be moved to 2.x and jline to 3.x, but I don't actually maintain any packages that need the old versions. I would like to give them away to someone who needs them, but note that you will need to grab jansi-native as well, before Monday! Has anybody already done something about any of these packages (and my packager-dashboard page just hasn't caught up yet)? Is anybody planning to do something about any of these packages before they are retired on Monday? -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)
W dniu 03.06.2021 o 22:35, Ben Cotton pisze: https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot == Summary == With recent changes in public cloud widely accepting the use of UEFI boot, it would be consistent to add hybrid boot in support of both unifying the legacy (BIOS) and UEFI boot to the Fedora Linux cloud base images. == Detailed Description == The Fedora Cloud Edition image will be updated to be configured with multiple partitions and a GPT label instead of one single partition and implicit MBR. The partition order will be: # A BIOS boot partition # An EFI System partition # A general data partition Please make first partition at least 4MB in size. Those Arm/AArch64 systems which store bootloaders on boot media will have a space for it (as some already read from around that area). ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)
https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot == Summary == With recent changes in public cloud widely accepting the use of UEFI boot, it would be consistent to add hybrid boot in support of both unifying the legacy (BIOS) and UEFI boot to the Fedora Linux cloud base images. == Owner == * Name: [[User:Davdunc|David Duncan]], [[User:Chrismurphy|Chris Murphy]], [[User:Salimma|Michel Alexandre Salim]], [[User:Dcavalca|Davide Cavalca]], [[User:Ngompa|Neal Gompa]], [[User:Dustymabe|Dusty Mabe]] * Email: davd...@amazon.com, chrismur...@fedoraproject.org, mic...@michel-slm.name, dcava...@fb.com, ngomp...@gmail.com, du...@dustymabe.com * Products: Fedora Cloud Edition * Responsible WGs: Fedora Cloud WG == Detailed Description == The Fedora Cloud Edition image will be updated to be configured with multiple partitions and a GPT label instead of one single partition and implicit MBR. The partition order will be: # A BIOS boot partition # An EFI System partition # A general data partition == Benefit to Fedora == This is a continuation from the changes outlined in the [[Releases/34|Fedora Linux 34]] changes to [[Changes/UnifyGrubConfig|unify the Grub configuration files]]. There has been an overwhelming support in the public cloud architectures leading to widespread support for UEFI boot in support of migration work. This also adds support for other anticipated changes that would require this modification to include the boot partitions; both legacy boot as a fallback through the BIOS boot partition and UEFI boot through the EFI system partition. This is going to require a group of modifications to the cloud base, including modifying the partition to support UEFI and a disk label change to GPT. With this change in place, the images will have greater flexibility to support file systems, such as btrfs, for boot across a number of supported providers and environments. * To have a consistent configuration across all the architectures * Allows the same image to be booted using either UEFI or legacy BIOS. * Allow easier migration from one environment to another where there is potentially a change in boot loader. * Use the same documentation and commands for the available cloud architectures instead of having special cases for different environments. * Align with images generated by COSA, KIWI, and OSBuild on how the GRUB configuration files are used. * Align with other installation methods on how the partitions under /boot are defined * Align with other distributions, like CentOS and openSUSE, on support for GRUB configuration == Scope == * Proposal owners: ** Submit PRs for Cloud Edition kickstarts to produce hybrid boot. * Release engineering: [https://pagure.io/releng/issue/10143 #10143] * Policies and guidelines: N/A * Trademark approval: N/A == Upgrade/compatibility impact == Change will not affect upgrades. == How To Test == Once the change lands in Rawhide, spin up the images in AWS, GCP, and KVM/OpenStack to test to see systems boot and run. Where possible, test images on cloud virtual machines types where both boot methods are supported. Verify that the general data partition is properly grown in the case that the root volume is larger than the image default. == User Experience == * Mostly transparent. * Consistent recovery experience with other distributions and builds of Fedora Linux. == Dependencies == * fedora-kickstarts == Documentation == No extra documentation is required reading for users. Supporting recovery documentation is already available. == Release Notes == Fedora Linux cloud images are updated to boot both UEFI and legacy boot (BIOS) through a hybrid configuration. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)
https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot == Summary == With recent changes in public cloud widely accepting the use of UEFI boot, it would be consistent to add hybrid boot in support of both unifying the legacy (BIOS) and UEFI boot to the Fedora Linux cloud base images. == Owner == * Name: [[User:Davdunc|David Duncan]], [[User:Chrismurphy|Chris Murphy]], [[User:Salimma|Michel Alexandre Salim]], [[User:Dcavalca|Davide Cavalca]], [[User:Ngompa|Neal Gompa]], [[User:Dustymabe|Dusty Mabe]] * Email: davd...@amazon.com, chrismur...@fedoraproject.org, mic...@michel-slm.name, dcava...@fb.com, ngomp...@gmail.com, du...@dustymabe.com * Products: Fedora Cloud Edition * Responsible WGs: Fedora Cloud WG == Detailed Description == The Fedora Cloud Edition image will be updated to be configured with multiple partitions and a GPT label instead of one single partition and implicit MBR. The partition order will be: # A BIOS boot partition # An EFI System partition # A general data partition == Benefit to Fedora == This is a continuation from the changes outlined in the [[Releases/34|Fedora Linux 34]] changes to [[Changes/UnifyGrubConfig|unify the Grub configuration files]]. There has been an overwhelming support in the public cloud architectures leading to widespread support for UEFI boot in support of migration work. This also adds support for other anticipated changes that would require this modification to include the boot partitions; both legacy boot as a fallback through the BIOS boot partition and UEFI boot through the EFI system partition. This is going to require a group of modifications to the cloud base, including modifying the partition to support UEFI and a disk label change to GPT. With this change in place, the images will have greater flexibility to support file systems, such as btrfs, for boot across a number of supported providers and environments. * To have a consistent configuration across all the architectures * Allows the same image to be booted using either UEFI or legacy BIOS. * Allow easier migration from one environment to another where there is potentially a change in boot loader. * Use the same documentation and commands for the available cloud architectures instead of having special cases for different environments. * Align with images generated by COSA, KIWI, and OSBuild on how the GRUB configuration files are used. * Align with other installation methods on how the partitions under /boot are defined * Align with other distributions, like CentOS and openSUSE, on support for GRUB configuration == Scope == * Proposal owners: ** Submit PRs for Cloud Edition kickstarts to produce hybrid boot. * Release engineering: [https://pagure.io/releng/issue/10143 #10143] * Policies and guidelines: N/A * Trademark approval: N/A == Upgrade/compatibility impact == Change will not affect upgrades. == How To Test == Once the change lands in Rawhide, spin up the images in AWS, GCP, and KVM/OpenStack to test to see systems boot and run. Where possible, test images on cloud virtual machines types where both boot methods are supported. Verify that the general data partition is properly grown in the case that the root volume is larger than the image default. == User Experience == * Mostly transparent. * Consistent recovery experience with other distributions and builds of Fedora Linux. == Dependencies == * fedora-kickstarts == Documentation == No extra documentation is required reading for users. Supporting recovery documentation is already available. == Release Notes == Fedora Linux cloud images are updated to boot both UEFI and legacy boot (BIOS) through a hybrid configuration. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Take the new Annual Fedora Contributor Survey
On Thu, Jun 03, 2021 at 21:34:22 +0200, Miro Hrončok wrote: On 03. 06. 21 20:29, Matthew Miller wrote: On Thu, Jun 03, 2021 at 01:00:23PM -0500, Bruno Wolff III wrote: Given that badges are being handed out, it is clear the survey is not anonymous. When the survey is complete, you get a non-personalized link which will let you get the badge. It might be theoretically possible to correlate this by IP address from logs, but I don't think any one actually has access to both the LimeSurvey web logs and ours. Also by time. If you are concerned about privacy, save the link and use it to claim the badge later (after some randomized/secret amount of time). My issue was more with the claim about being anonymous, rather than how to try to advise people on how to try to respond while making it hard to be identified. I doubt that many people here care whether their replies are anonymous or not for this survey. I think people doing surveys throw that text in by rote because they think it helps response rate. When I see survey requests using that text my first thought is that the person requesting the participation is either incompetent or intentionally lying and I probably shouldn't respond to the request. I think people requesting surveys should either make no privacy related comment or one that indicates what their practice will be. Instead of saying the responses are anonymous, they might say they are confidential or that they will be published without identity being explicitly included or whatever the practice is. While many people on this list will understand that surveys are not really anonymous unless the responses are simple and special care is taken in how you interact with the survey, that isn't true in general. And I think survey requesters should be held to a higher bar in properly informing people about the privacy aspects of their surveys. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : ELN SIG
On Thu, Jun 3, 2021 at 8:44 AM Stephen Gallagher wrote: > > Please submit topics for the agenda in replies to this email. > > My topics: > > 1. Broken Compose and detection > 2. Tracking side-tags in Rawhide > A topic I want to add: clarifying guidance on conditionals[1]. There seem to be some mistaken impressions on conditional guidance that I think we should straighten out. [1]: https://docs.fedoraproject.org/en-US/eln/ftbfs/ -- 真実はいつも一つ！/ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RPMLint 2.0 released!
On Thu, Jun 3, 2021 at 3:52 PM Tom Callaway wrote: > > I have landed rpmlint 2.0.0 in rawhide, along with Mirek Suchý's toml configs > (with updates for the licenses.toml). PRs, bug reports, and suggestions > welcome. > Thank you so much, Tom! -- 真実はいつも一つ！/ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RPMLint 2.0 released!
I have landed rpmlint 2.0.0 in rawhide, along with Mirek Suchý's toml configs (with updates for the licenses.toml). PRs, bug reports, and suggestions welcome. Thanks, ~spot On Wed, May 19, 2021 at 6:55 AM Miroslav Suchý wrote: > Dne 19. 05. 21 v 6:46 Michal Schorm napsal(a): > > * RPMLint includes _many more checks_! Nearly all of the generally > > However I always have a hard time understanding what the issue caught > by RPMLint actually is. > I would like to see some library of the checks with the explanation of > what it is, why it is important and usual examples of bad / correct > code and how to fix it. Something like CWEs (e.g. [1]) > Is there something like it already by any chance ? > > There is a long way between an error / warning being reported by > RPMLint with maintainer just ignoring it, and the maintainer to > understand the value and importance of having it fixed (as well as > knowledge how to fix it) > > [1] https://cwe.mitre.org/data/definitions/416.html > > $ python3 lint.py /tmp/tito/rpmconf-1.1.4-1.fc34.src.rpm > > ... > > rpmconf.src: E: description-line-too-long This tool search ... > > $ python3 lint.py -e description-line-too-long > description-line-too-long: > Your description lines must not exceed 79 characters. If a line is > exceeding > this number, cut it to fit in two lines > > Or you can run rpmlint in verbose mode "-v" where this explanation is > printed for every findings. > > > Is this good enough? ;) > > Miroslav > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Take the new Annual Fedora Contributor Survey
On 03. 06. 21 20:29, Matthew Miller wrote: On Thu, Jun 03, 2021 at 01:00:23PM -0500, Bruno Wolff III wrote: Given that badges are being handed out, it is clear the survey is not anonymous. When the survey is complete, you get a non-personalized link which will let you get the badge. It might be theoretically possible to correlate this by IP address from logs, but I don't think any one actually has access to both the LimeSurvey web logs and ours. Also by time. If you are concerned about privacy, save the link and use it to claim the badge later (after some randomized/secret amount of time). -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Take the new Annual Fedora Contributor Survey
On Thu, Jun 03, 2021 at 01:00:23PM -0500, Bruno Wolff III wrote: > Given that badges are being handed out, it is clear the survey is > not anonymous. When the survey is complete, you get a non-personalized link which will let you get the badge. It might be theoretically possible to correlate this by IP address from logs, but I don't think any one actually has access to both the LimeSurvey web logs and ours. -- Matthew Miller Fedora Project Leader ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Take the new Annual Fedora Contributor Survey
On Wed, Jun 02, 2021 at 18:14:50 +0200, Aleksandra Fedorova wrote: Hello, everyone, Please participate in the Annual Fedora Contributor Survey 2021! * https://fedoraproject.limequery.com/2021 The survey is anonymous, it has 44 questions and It is targeting Fedora contributors of all kinds and asks about your default choices of applications and services. Given that badges are being handed out, it is clear the survey is not anonymous. People that do surveys love to claim they are anonymous when they aren't, to increase the response. When you are collecting detailed information from someone it is hard to prevent the person from being identified by that data even if you don't collect their identity directly. If you have people authenticate or send out links to the survey that are customised per person (perhaps to prevent someone from filling out the survey repeatedly) then the survey is clearly not anonymous. Even if you don't do that, web server logs can often reveal who the responders are. In my opinion it is best to state what you are actually doing with regards to privacy rather than simplify it and make a statement that is clearly false. In this cases you might have said that you were not going to store the identity along side the responses. Even claiming you wouldn't try to find out who the responders were probably wouldn't have been true without caveats. (For example if someone used the survey to make a serious sounding death threat, you very likely would make some attempt to find out who made it.) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[ELN] Broken ELN Compose detection
I wrote the following script a while ago to check on the ELN composes.[1][2] It's not fancy, and the webpage it outputs isn't fancy,[3] but it works. It's a good starting point for checking ELN Composes. I thought I'd share it before the ELN meeting tomorrow so people would have a chance to look at it. Troy [1] - https://tdawson.fedorapeople.org/eln/eln-compose-status.py [2] - https://tdawson.fedorapeople.org/eln/compose-status.html.jira [3] - https://tdawson.fedorapeople.org/eln/output/compose-status.html ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Becoming maintainer for pdsh for EPEL - unresponsive maintainer
On Wed, Jun 02, 2021 at 01:42:23PM -0700, Troy Dawson wrote: > EPEL Packages have a modified version of the non-responsive package > maintainer. > https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Stalled_EPEL_Requests > > This is for stalled requests, which is a bit different than non-responsive > package maintainers. Fedora package maintainers don't have to do anything > with EPEL if they don't want to, thus we needed it to be a bit different. Thanks for the correction, Troy. I'll remember this for the next time! -- Matthew Miller Fedora Project Leader ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: Make btrfs the default file system for Fedora Cloud (System-Wide Change proposal)
On Thu, Jun 03, 2021 at 09:35:24AM -0400, Dusty Mabe wrote: > Bear with me and try to assume good faith. When this was first brought up > in the cloud WG meeting recently I did ask of the implications on our > pending talks to merge with Server. I thought it had been discussed in the > Server WG first. We had a long talk about it several years ago, but that was effectively the previous Server WG not the current one. > But.. at the end of the day I'm mostly just trying to do the best I can > with limited time. Maybe we can get everyone together to discuss all the > various options and the best path forward? +1 -- Matthew Miller Fedora Project Leader ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967644] New: perl-Dancer2-0.301003 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967644 Bug ID: 1967644 Summary: perl-Dancer2-0.301003 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Dancer2 Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.301003 Current version/release in rawhide: 0.301002-2.fc35 URL: http://search.cpan.org/dist/Dancer2 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://fedoraproject.org/wiki/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/5847/ -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 Change: Make btrfs the default file system for Fedora Cloud (System-Wide Change proposal)
On 6/2/21 5:28 AM, Peter Boy wrote: > > > > very nicely put. According to Matthew and others cloud wg did virtually not > exist for more than a year, no meetings, silence on mailing list beyond > bi-weekly announcement of a „standing“ meeting nobody attended to, there was > discussion to „kill“ it, great reluctance on the side of Dusty in our meeting > March 3 to make any changes on the artefacts at all, new start of 2-weekly > meetings March 30, „months of conversation“ which spell down to 4 meetings in > 2 months, and then such a very fundamental change. Well, the wording may be a > bit offhand, but by no means farfetched. We typically run meetings every two weeks, but that did stop happening when I was away earlier this year. There is some truth in here though. It's very true that the cloud WG needs a leader. I'm mostly just trying to keep the lights on. I don't have significant amounts of time to put into it. When people show up with ideas and are willing to execute on them I try not to get in the way assuming the change isn't vastly fundamental. > > And lest there be any misconception, Cloud WG may decide what or about what > they deem useful. That is not my business. But regarding the planned > discussion about cooperation and alignment of server and Cloud WG and > artifacts, I am "not amused" and can't really take it seriously anymore. > There are more serious and urgent tasks waiting for us. Bear with me and try to assume good faith. When this was first brought up in the cloud WG meeting recently I did ask of the implications on our pending talks to merge with Server. I thought it had been discussed in the Server WG first. https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_meeting/fedora_cloud_meeting.2021-05-11-15.58.log.txt 16:18:15 There is also the discussion of merging with the server WG - if we change to BTRFS does that inhibit that potential path for us (i.e. should we get server to buy in on the FS change too, or maybe they have already)? But.. at the end of the day I'm mostly just trying to do the best I can with limited time. Maybe we can get everyone together to discuss all the various options and the best path forward? Dusty ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : ELN SIG
Please submit topics for the agenda in replies to this email. My topics: 1. Broken Compose and detection 2. Tracking side-tags in Rawhide On Thu, Jun 3, 2021 at 8:01 AM wrote: > > Dear all, > > You are kindly invited to the meeting: >ELN SIG on 2021-06-04 from 12:00:00 to 13:00:00 US/Eastern >At fedora-meet...@irc.libera.net > > The meeting will be about: > > > > Source: https://apps.fedoraproject.org/calendar/meeting/9920/ > > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RPM build error on Rawhide
On 6/3/21 1:28 PM, Vitaly Zaitsev via devel wrote:
On 6/3/21 12:20 PM, Miroslav Suchý wrote:
You can try with:
rpm --eval '%{_javadir}/pycharm-community'
F34:
$ rpm --eval '%{_javadir}/pycharm-community'
/usr/share/java/pycharm-community
On Rawhide it doesn't exists. Maybe it was extracted to a separate
*-macros package?
Yep:
[pmatilai︎lumikko ~]$ grep _javadir /usr/lib/rpm/macros.d/*
/usr/lib/rpm/macros.d/macros.javapackages-filesystem:%_javadir
%{_datadir}/java
[pmatilai︎lumikko ~]$ rpm -qf
/usr/lib/rpm/macros.d/macros.javapackages-filesystem
javapackages-filesystem-5.3.0-13.fc33.noarch
- Panu -
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: RPM build error on Rawhide
On 6/3/21 12:20 PM, Miroslav Suchý wrote: Common culprit is that this macro is not defined. Adding BuildRequires: javapackages-filesystem fixed issue for me. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2021-06-04 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.net The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/9920/ ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2021-06-04 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.net The meeting will be about: Source: https://apps.fedoraproject.org/calendar/meeting/9920/ ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967347] perl-Socket-2.032 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967347 --- Comment #1 from Fedora Update System --- FEDORA-2021-d42c1e5851 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d42c1e5851 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: [cdparanoia] License field fix awaiting to be merged
If the README has the last word here and it does not matter that some sequences of bits of /usr/bin/cdparanoia are licensed under GPLv2+ and the rest of it under GPLv2, so be it. On the other hand, https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/#_mixed_source_licensing_scenario states that if /usr/bin/foo is generated from foo1.c licensed under A and foo2.c licensed under B, where A and B are compatible, but different, licenses, then this scenario should be handled by "(A and B)" in License field. The best way to deal with this situation would be to ask upstream to re-license those two files to GPLv2, but cdparanoia upstream is effectively dead. Regards, Jiri On Wed, Jun 2, 2021 at 2:23 PM Andrea Musuruane wrote: > I believe this patch is not correct. > > "The License: field refers to the licenses of the contents of the *binary* > rpm." > > https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/ > > In the README file there is writted: "cdparanoia (the command line tool) > is released under the GPLv2. The interface and paranoia libraries are > covered by the LGPLv2.1." > > So, it doesn't really matter if two source files are distributed under the > GPLv2+ > license. The resulting binary (i.e. /usr/bin/cdparanoia) will always be > GPLv2. > > BR, > > Andrea > > > On Wed, Jun 2, 2021 at 2:03 PM Jiri Kucera wrote: > >> Thanks Neal! >> >> On Wed, Jun 2, 2021 at 1:06 PM Neal Gompa wrote: >> >>> On Wed, Jun 2, 2021 at 6:54 AM Neal Gompa wrote: >>> > >>> > On Wed, Jun 2, 2021 at 6:53 AM Jiri Kucera wrote: >>> > > >>> > > Adding broader audience: >>> https://src.fedoraproject.org/rpms/cdparanoia/pull-request/4 >>> > > >>> > > Neither @pjones nor @ajax are responding. >>> > > >>> > >>> > I'll deal with it. >>> > >>> >>> This is done, and updates have been proposed for stable releases: >>> >>> * Fedora 34: >>> https://bodhi.fedoraproject.org/updates/FEDORA-2021-31358601f8 >>> >>> * Fedora 33: >>> https://bodhi.fedoraproject.org/updates/FEDORA-2021-4c93fe43a0 >>> >>> Please karma them up for release to stable. >>> >>> >>> >>> >>> -- >>> 真実はいつも一つ！/ 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 on the list, report it: >> https://pagure.io/fedora-infrastructure >> > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967544] New: perl-SDL-2.548-11.fc35 FTBFS with sdl12-compat-devel-0.0.1~git.20210602.cc5826a-1.fc35
https://bugzilla.redhat.com/show_bug.cgi?id=1967544 Bug ID: 1967544 Summary: perl-SDL-2.548-11.fc35 FTBFS with sdl12-compat-devel-0.0.1~git.20210602.cc5826a-1.fc35 Product: Fedora Version: rawhide Status: NEW Component: perl-SDL Assignee: hdego...@redhat.com Reporter: ppi...@redhat.com QA Contact: extras...@fedoraproject.org CC: hdego...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora sdl12-compat replaced SDL in Fedora 35 and perl-SDL-2.548-11.fc35 fails to build now because of failing tests: Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.puyE59 + umask 022 + cd /builddir/build/BUILD + cd SDL-2.548 + ./Build test [Alien::SDL] Build option used: Already installed SDL ver=1.2.15 path=/usr SDL(v1.2.15) SDL_image(v1.2.12) SDL_mixer(v1.2.12) SDL_ttf(v2.0.11) SDL_gfx(v2.0.26) SDL_Pango(v1.3) Building SDL # Failed test 'use SDL;' # at t/00-load.t line 88. # Tried to use 'SDL'. # Error: Can't locate loadable object for module SDL_perl in @INC (@INC contains: /builddir/build/BUILD/SDL-2.548/blib/lib /builddir/build/BUILD/SDL-2.548/blib/arch inc /usr/local/lib64/perl5/5.34 /usr/local/share/perl5/5.34 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /builddir/build/BUILD/SDL-2.548/blib/lib/SDL.pm line 42. # Compilation failed in require at /builddir/build/BUILD/SDL-2.548/blib/lib/SDL.pm line 42. # BEGIN failed--compilation aborted at /builddir/build/BUILD/SDL-2.548/blib/lib/SDL.pm line 42. # Compilation failed in require at t/00-load.t line 88. # BEGIN failed--compilation aborted at t/00-load.t line 88. Bailout called. Further testing stopped: Test failed. BAIL OUT!. FAILED--Further testing stopped: Test failed. BAIL OUT!. error: Bad exit status from /var/tmp/rpm-tmp.puyE59 (%check) -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RPM build error on Rawhide
On 6/3/21 12:20 PM, Miroslav Suchý wrote:
You can try with:
rpm --eval '%{_javadir}/pycharm-community'
F34:
$ rpm --eval '%{_javadir}/pycharm-community'
/usr/share/java/pycharm-community
On Rawhide it doesn't exists. Maybe it was extracted to a separate
*-macros package?
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: RPM build error on Rawhide
Dne 03. 06. 21 v 12:03 Vitaly Zaitsev via devel napsal(a):
Hello all.
RPM build errors:
File must begin with "/": %{_javadir}/pycharm-community
F33 and F34 were built fine.
Common culprit is that this macro is not defined.
It then expand to '%{_javadir}/pycharm-community'. LIteraly.
You can try with:
rpm --eval '%{_javadir}/pycharm-community'
Miroslav
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
RPM build error on Rawhide
Hello all.
RPM build errors:
File must begin with "/": %{_javadir}/pycharm-community
F33 and F34 were built fine.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
[Bug 1967373] perl-Convert-ASN1-0.31 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967373 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED CC|caillon+fedoraproject@gmail | |.com, caol...@redhat.com, | |jples...@redhat.com,| |ka...@ucw.cz, | |mspa...@redhat.com, | |rhug...@redhat.com, | |rstr...@redhat.com, | |sandm...@redhat.com | Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967347] perl-Socket-2.032 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967347 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-Socket-2.032-1.fc35 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-Socket] PR #1: Tests
jplesnik merged a pull-request against the project: `perl-Socket` that you are following. Merged pull-request: `` Tests `` https://src.fedoraproject.org/rpms/perl-Socket/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[rpms/perl-Socket] PR #1: Tests
jplesnik opened a new pull-request against the project: `perl-Socket` that you are following: `` Tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Socket/pull-request/1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967347] perl-Socket-2.032 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967347 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED CC|jples...@redhat.com,| |mspa...@redhat.com, | |ppi...@redhat.com | Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967434] New: perl-CGI-4.53 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967434 Bug ID: 1967434 Summary: perl-CGI-4.53 is available Product: Fedora Version: rawhide Status: NEW Component: perl-CGI Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mmasl...@redhat.com, mspa...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 4.53 Current version/release in rawhide: 4.52-4.fc35 URL: http://search.cpan.org/dist/CGI/ 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://fedoraproject.org/wiki/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/2687/ -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967068] perl-Graphics-TIFF-15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967068 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-Graphics-TIFF-15-1.fc3 ||5 --- Comment #1 from Petr Pisar --- A bug-fix release suitable for all Fedoras. Updating stable Fedoras postponed until stabilizing perl-Graphics-TIFF-13. -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[389-devel] 389 DS nightly 2021-06-03 - 94% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2021/06/03/report-389-ds-base-2.0.5-20210603gitff830604e.fc34.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1967068] perl-Graphics-TIFF-15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1967068 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED CC|ppi...@redhat.com | Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
