Re: python3-PyPDf2 -> python3-pydf package
Additionally, see here: https://stackoverflow.com/questions/63199763/maintained-alternatives-to-pypdf2 On Sunday, August 27, 2023 at 10:21:29 PM CDT, Globe Trotter via devel wrote: Thanks! On Sun, Aug 27, 2023 at 5:39 AM Sandro wrote: > > On 27-08-2023 06:33, Globe Trotter via devel wrote: > > I am the maintainer of python-PyPDF2 for Fedora (which I do since I > > was interested in pdf-stapler that I also maintain as a consequence). > > For a while now, upstream has been wanting all PyPDF2 users to pypdf. > > I was wondering how I go about this for the F38 repos. Do I need to > > go through packaging again, or is there an easier way to update > > python3-PyPDF2 to python3-pypdf? If so, what do I have to do? > > Could you provide some links to the upstream sources of PyPDF2 and > pypdf? And me be also to the issue where the switch from PyPDF2 to pypdf > is discussed. I understand that the pypdf maintainer is the same as that of PyPDF2 and says here that: https://stackoverflow.com/questions/34837707/how-to-extract-text-from-a-pdf-file that PyPDF2 and PyPDF3 and PyPDF4 packages are not maintained. > I'm assuming PyPDF2 and pypdf are separate packages. In that case you > would need to submit pypdf as a new package. Once pdf-stapler is built > against pypdf you can retire PyPDF2 if no other package depends on it. The above search indicates they are, and that there is a pypdf3. > If pypdf is a rename of PyPDF2 you'd submit a re-review of the package > and you need to take care of proper Provides: and Obsoletes: in the new > package. See the docs for more info: > > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Renaming_Process/ > https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages > Thanks, simply renaming and obsoleting seems to me to be a better option, and I will look into that. Thanks again! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Add a push update mechanism for https://release-monitoring.org/
Faster updates are always as plus. Should this be under infrastructure list? Thoughts? Thanks in advance for all the work done to make this distro great. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: python3-PyPDf2 -> python3-pydf package
Thanks! On Sun, Aug 27, 2023 at 5:39 AM Sandro wrote: > > On 27-08-2023 06:33, Globe Trotter via devel wrote: > > I am the maintainer of python-PyPDF2 for Fedora (which I do since I > > was interested in pdf-stapler that I also maintain as a consequence). > > For a while now, upstream has been wanting all PyPDF2 users to pypdf. > > I was wondering how I go about this for the F38 repos. Do I need to > > go through packaging again, or is there an easier way to update > > python3-PyPDF2 to python3-pypdf? If so, what do I have to do? > > Could you provide some links to the upstream sources of PyPDF2 and > pypdf? And me be also to the issue where the switch from PyPDF2 to pypdf > is discussed. I understand that the pypdf maintainer is the same as that of PyPDF2 and says here that: https://stackoverflow.com/questions/34837707/how-to-extract-text-from-a-pdf-file that PyPDF2 and PyPDF3 and PyPDF4 packages are not maintained. > I'm assuming PyPDF2 and pypdf are separate packages. In that case you > would need to submit pypdf as a new package. Once pdf-stapler is built > against pypdf you can retire PyPDF2 if no other package depends on it. The above search indicates they are, and that there is a pypdf3. > If pypdf is a rename of PyPDF2 you'd submit a re-review of the package > and you need to take care of proper Provides: and Obsoletes: in the new > package. See the docs for more info: > > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Renaming_Process/ > https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages > Thanks, simply renaming and obsoleting seems to me to be a better option, and I will look into that. Thanks again! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: python3-PyPDf2 -> python3-pydf package
On Sun, Aug 27, 2023 at 5:39 AM Sandro wrote: > > On 27-08-2023 06:33, Globe Trotter via devel wrote: > > I am the maintainer of python-PyPDF2 for Fedora (which I do since I > > was interested in pdf-stapler that I also maintain as a consequence). > > For a while now, upstream has been wanting all PyPDF2 users to pypdf. > > I was wondering how I go about this for the F38 repos. Do I need to > > go through packaging again, or is there an easier way to update > > python3-PyPDF2 to python3-pypdf? If so, what do I have to do? > > Could you provide some links to the upstream sources of PyPDF2 and > pypdf? And me be also to the issue where the switch from PyPDF2 to pypdf > is discussed. Perhaps check pypi.org? https://pypi.org/search/?q=pypdf= Python module capitalization, and inconsist names used by RPM published modules, are an old problem for Fedora and RHEL. > I'm assuming PyPDF2 and pypdf are separate packages. In that case you > would need to submit pypdf as a new package. Once pdf-stapler is built > against pypdf you can retire PyPDF2 if no other package depends on it. The above search indicates they are, and that there is a pypdf3. > If pypdf is a rename of PyPDF2 you'd submit a re-review of the package > and you need to take care of proper Provides: and Obsoletes: in the new > package. See the docs for more info: > > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Renaming_Process/ > https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages > > I hope that helps. > > -- Sandro > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: SPDX Statistics - Voyager 2 edition
Top-posting a few comments related to this thread in total (instead of multiple responses to separate posts) and in hopes that people will be more likely to see/read :) As to Rust saying MPL-2.0+ is invalid - this is likely because Rust thinks of the SPDX License List as *only* what is this page https://spdx.org/licenses/ - ignoring the links at the top of that page that provide the greater context, which is really important to understand. This is a somewhat common misconception, especially when adoption of SPDX ids occurs without actual engagement in the SPDX community. Some time ago, I started (in presentations) to repeat "it's not just a 'list'" to help educate people and updated the first FAQ to this end - https://github.com/spdx/license-list-XML/blob/main/DOCS/faq.md Maybe I need to re-write that lead-in language on the top of the page again or put a big yellow flashing sign also? sigh If you want to pass along this concept to people at Rust and tell them to join the spdx-legal mailing list, we'd be happy to help advise. As for deprecated SPDX ids and validity in the context of Fedora - I would strongly urge us to use the current ids and not muddy things with the use of deprecated ids. The change as of the SPDX License List 2.0 added the operators (AND, OR, WITH, and +) and so it would super confusing if people still used the ids from v1.0 Further comments below thanks, Jilayne On 8/22/23 2:55 PM, Richard Fontana wrote: On Tue, Aug 22, 2023 at 4:44 PM Fabio Valentini wrote: On Tue, Aug 22, 2023 at 10:39 PM Richard Fontana wrote: On Tue, Aug 22, 2023 at 3:06 PM Fabio Valentini wrote: On Tue, Aug 22, 2023 at 1:21 PM Miroslav Suchý wrote: rust-bitmaps warning: not valid neither as Callaway nor as SPDX, please check This uses MPL-2.0 or later, denoted as "MPL-2.0+". It looks like an SPDX identifier, but it's not (there is no "-or-later" variant of MPL-2.0 in SPDX). I'll investigate and file an issue with upstream. Jilayne can correct me if I'm wrong, but I am pretty sure `MPL-2.0+` is a valid and semantically meaningful SPDX identifier. It is arguably redundant since MPL-2.0 permits downstream relicensing to later versions. correct It's not on the list though: https://spdx.org/licenses/ The use of `+` is documented at https://spdx.github.io/spdx-spec/v2-draft/SPDX-license-expressions/ (there's probably a more recent version) Here is the current spec link https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/ D.3 Simple license expressions A simple is composed one of the following: An SPDX License List Short Form Identifier. For example: CDDL-1.0 An SPDX License List Short Form Identifier with a unary "+" operator suffix to represent the current version of the license or any later version. For example: CDDL-1.0+ An SPDX user defined license reference: ["DocumentRef-"1*(idstring)":"]"LicenseRef-"1*(idstring) I believe CDDL-1.0 is like MPL-2.0 in having a built-in "later versions" clause. this is more or less correct, although we did some analysis on the various license with "or later" clauses and the variations on the actual wording and meaning was surprising... Also, cargo / crates.io even documents that licenses in crate metadata needs to be valid SPDX expressions and only things from SPDX license list are acceptable, so this isn't considered valid by crates.io That is at least in some sense wrong, since the SPDX spec shows that valid SPDX expressions include use of the `+` operator with SPDX identifiers. I think in reality crates.io is redefining what "valid SPDX expressions" means, though possibly not intentionally. see comment above - but I'd rephrase that crates.io is probably not "redefining" but operating on a limited understanding :( For Fedora, I think there are (quite rare) cases where the use of postpositional `+` should be recognized as valid. I know of one package (though I can't remember what it is now) that says its license is the Apache License 2.0 or any later version -- this is validly represented as `Apache-2.0+` in SPDX. I would argue that Apache-2.0+, while technically valid, would be silly/incorrect, though :) Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2233000] perl-Module-CoreList-5.20230820 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2233000 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023 |0820-1.fc40 |0820-1.fc40 ||perl-Module-CoreList-5.2023 ||0820-1.fc38 --- Comment #9 from Fedora Update System --- FEDORA-2023-2e6690438d has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2233000 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202233000%23c9 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 9 updates-testing report
The following Fedora EPEL 9 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-02f7139d40 ntpsec-1.2.2a-1.el9 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7a43301d55 ImageMagick-6.9.12.93-1.el9 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f4d52e6818 mosquitto-2.0.17-1.el9 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8849a14e7f caddy-2.6.4-1.el9 The following builds have been pushed to Fedora EPEL 9 updates-testing python-apprise-1.5.0-1.el9 rust-aho-corasick-1.0.4-1.el9 rust-anyhow-1.0.75-2.el9 rust-argh-0.1.12-1.el9 rust-argh_derive-0.1.12-1.el9 rust-argh_shared-0.1.12-1.el9 rust-async-lock-2.8.0-1.el9 rust-async-trait-0.1.73-1.el9 rust-bitflags-2.4.0-1.el9 rust-cargo-util-0.2.5-1.el9 rust-const-oid-0.9.5-1.el9 rust-critical-section-1.1.2-1.el9 rust-encoding_rs-0.8.33-1.el9 rust-filetime-0.2.22-1.el9 rust-flate2-1.0.27-1.el9 rust-globset-0.4.13-1.el9 rust-log-0.4.20-1.el9 rust-num-complex-0.4.4-1.el9 rust-pest-2.7.2-1.el9 rust-pest_derive-2.7.2-1.el9 rust-pest_generator-2.7.2-1.el9 rust-pest_meta-2.7.2-1.el9 rust-pin-project-1.1.3-1.el9 rust-pin-project-internal-1.1.3-1.el9 rust-ref-cast-1.0.20-1.el9 rust-ref-cast-impl-1.0.20-1.el9 rust-rust_decimal-1.32.0-1.el9 rust-serde_json-1.0.105-1.el9 rust-slog-async-2.8.0-1.el9 rust-strum_macros-0.25.2-1.el9 rust-tar-0.4.40-1.el9 rust-thiserror-1.0.47-1.el9 rust-thiserror-impl-1.0.47-1.el9 rust-tokio-1.32.0-1.el9 rust-tokio-test-0.4.3-1.el9 rust-typetag-0.2.13-1.el9 rust-typetag-impl-0.2.13-1.el9 Details about builds: python-apprise-1.5.0-1.el9 (FEDORA-EPEL-2023-99a1e7b3ba) A simple wrapper to many popular notification services used today Update Information: Updated to v1.5.0 ChangeLog: * Sun Aug 27 2023 Chris Caron - 1.5.0 - Updated to v1.5.0 - apprise-fedora-rpm-testcase-handling.patch added for test handling * Fri Jul 21 2023 Fedora Release Engineering - 1.4.5-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Thu Jul 6 2023 Chris Caron - 1.4.5 - Updated to v1.4.5 * Wed Jun 14 2023 Python Maint - 1.4.0-2 - Rebuilt for Python 3.12 * Mon May 15 2023 Chris Caron - 1.4.0 - Updated to v1.4.0 rust-aho-corasick-1.0.4-1.el9 (FEDORA-EPEL-2023-01e861bb78) Fast multiple substring searching Update Information: Update to version 1.0.4. ChangeLog: * Sun Aug 27 2023 Fabio Valentini - 1.0.4-1 - Update to version 1.0.4; Fixes RHBZ#2230772 rust-anyhow-1.0.75-2.el9 (FEDORA-EPEL-2023-b543eccb50) Flexible concrete Error type built on std::error::Error Update Information: - Update the anyhow crate to version 1.0.75. - Update the thiserror and thiserror-impl crates to version 1.0.47. ChangeLog: * Sun Aug 27 2023 Fabio Valentini - 1.0.75-2 - Re-enable tests after bootstrap with thiserror * Sun Aug 27 2023 Fabio Valentini - 1.0.75-1 - Update to version 1.0.75; Fixes RHBZ#2232079 * Fri Jul 21 2023 Fedora Release Engineering - 1.0.72-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild rust-argh-0.1.12-1.el9 (FEDORA-EPEL-2023-38ce38629c) Derive-based argument parser optimized for code size Update Information: Update the argh, argh_derive, and argh_shared crates to version 0.1.12. ChangeLog: * Sun Aug 27 2023 Fabio Valentini - 0.1.12-1 - Update to version 0.1.12; Fixes RHBZ#2229848 * Fri Jul 21 2023 Fedora Release Engineering - 0.1.10-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5120258393 ImageMagick-6.9.12.93-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing profanity-0.14.0-2.el8 python-apprise-1.5.0-1.el8 Details about builds: profanity-0.14.0-2.el8 (FEDORA-EPEL-2023-0157410c4d) A console based XMPP client Update Information: Update to 0.14.0 ChangeLog: * Sun Aug 27 2023 Matthieu Saulnier - 0.14.0-2 - Add patch to fix vcard support during the build * Thu Aug 3 2023 Matthieu Saulnier - 0.14.0-1 - Update to 0.14.0 - Improve file ownership in doc subpackage - Minor fix in the doc subpackage (no need to remove rst files) - Concat patch files into a single file python-apprise-1.5.0-1.el8 (FEDORA-EPEL-2023-988297b0d2) A simple wrapper to many popular notification services used today Update Information: Updated to v1.5.0 ChangeLog: * Sun Aug 27 2023 Chris Caron - 1.5.0 - Updated to v1.5.0 - apprise-fedora-rpm-testcase-handling.patch added for test handling * Fri Jul 21 2023 Fedora Release Engineering - 1.4.5-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Thu Jul 6 2023 Chris Caron - 1.4.5 - Updated to v1.4.5 * Wed Jun 14 2023 Python Maint - 1.4.0-2 - Rebuilt for Python 3.12 * Mon May 15 2023 Chris Caron - 1.4.0 - Updated to v1.4.0 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 39 compose report: 20230827.n.0 changes
OLD: Fedora-39-20230826.n.0 NEW: Fedora-39-20230827.n.0 = SUMMARY = Added images:4 Dropped images: 3 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Sericea dvd-ostree x86_64 Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-39-20230827.n.0.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-39-20230827.n.0.iso Image: Cinnamon live x86_64 Path: Spins/x86_64/iso/Fedora-Cinnamon-Live-x86_64-39-20230827.n.0.iso Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-39-20230827.n.0.iso = DROPPED IMAGES = Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-39-20230826.n.0.iso Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-39-20230826.n.0.iso Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-39-20230826.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2235104] perl-App-Cmd-0.336 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2235104 Emmanuel Seyman changed: What|Removed |Added Resolution|--- |RAWHIDE Status|NEW |CLOSED Doc Type|--- |If docs needed, set a value Fixed In Version||perl-App-Cmd-0.336-1.fc40 Last Closed||2023-08-27 10:15:36 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2279599 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2235104 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202235104%23c1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2233769] Upgrade perl-Text-MultiMarkdown to 1.001
https://bugzilla.redhat.com/show_bug.cgi?id=2233769 Emmanuel Seyman changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Text-MultiMarkdown-1.0 ||01000-1.fc40 Resolution|--- |RAWHIDE Last Closed||2023-08-27 10:15:06 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2279630 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2233769 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202233769%23c1 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230827.n.0 changes
OLD: Fedora-Rawhide-20230826.n.0 NEW: Fedora-Rawhide-20230827.n.0 = SUMMARY = Added images:2 Dropped images: 6 Added packages: 4 Dropped packages:0 Upgraded packages: 35 Downgraded packages: 0 Size of added packages: 98.30 MiB Size of dropped packages:0 B Size of upgraded packages: 402.72 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 6.93 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20230827.n.0.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230827.n.0.iso = DROPPED IMAGES = Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230826.n.0.iso Image: LXQt live aarch64 Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20230826.n.0.iso Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20230826.n.0.iso Image: i3 live aarch64 Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-Rawhide-20230826.n.0.iso Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20230826.n.0.iso Image: Sericea dvd-ostree x86_64 Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230826.n.0.iso = ADDED PACKAGES = Package: btrfsd-0.1.0-1.fc40 Summary: Tiny Btrfs maintenance daemon RPMs:btrfsd Size:170.26 KiB Package: golang-modernc-parser-1.0.8-1.fc40 Summary: Collection of Go parsers RPMs:golang-modernc-parser golang-modernc-parser-devel Size:71.17 KiB Package: racket-7.4-12.fc40 Summary: General purpose programming language RPMs:racket racket-collects racket-devel racket-doc racket-minimal racket-pkgs Size:98.05 MiB Package: rust-xterm-query-0.2.0-1.fc40 Summary: Query your terminal RPMs:rust-xterm-query+default-devel rust-xterm-query-devel Size:19.12 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: adobe-source-code-pro-fonts-2.042.1.062.1.026-1.fc40 Old package: adobe-source-code-pro-fonts-2.030.1.050-15.fc39 Summary: A set of mono-spaced OpenType fonts designed for coding environments RPMs: adobe-source-code-pro-fonts adobe-source-code-vf-fonts Added RPMs: adobe-source-code-vf-fonts Size: 981.56 KiB Size change: 151.15 KiB Changelog: * Sat Aug 19 2023 Akira TAGOH - 2.030.1.050-21 - Convert License tag to SPDX. * Sat Aug 19 2023 bbhtt - 2.042.1.062.1.026-1 - Update to 2.042.1.062.1.026 Package: audit-3.1.2-2.fc40 Old package: audit-3.1.2-1.fc39 Summary: User space tools for kernel auditing RPMs: audispd-plugins audispd-plugins-zos audit audit-libs audit-libs-devel python3-audit Size: 2.83 MiB Size change: -9.48 KiB Changelog: * Sat Aug 26 2023 Steve Grubb 3.1.2-2 - SPDX Migration Package: cfn-lint-0.79.7-1.fc40 Old package: cfn-lint-0.79.6-1.fc40 Summary: CloudFormation Linter RPMs: cfn-lint Size: 1.48 MiB Size change: 4.01 KiB Changelog: * Sat Aug 26 2023 Benjamin A. Beasley - 0.79.7-1 - Update to 0.79.7 Package: containerd-1.6.23-1.fc40 Old package: containerd-1.6.19-2.fc39 Summary: Open and reliable container runtime RPMs: containerd containerd-devel Size: 124.38 MiB Size change: 1.86 MiB Changelog: * Fri Aug 25 2023 Davanum Srinivas - 1.6.23-1 - update to containerd v1.6.23 Package: gnome-desktop3-44.0-6.fc40 Old package: gnome-desktop3-44.0-3.fc40 Summary: Library with common API for various GNOME modules RPMs: gnome-desktop3 gnome-desktop3-devel gnome-desktop3-tests gnome-desktop4 gnome-desktop4-devel Size: 4.75 MiB Size change: 61.47 KiB Changelog: * Sat Aug 26 2023 Ray Strode - 44.0-4 - Add APIs for finding default input sources * Sat Aug 26 2023 Ray Strode - 44.0-5 - Fix typo (s/langtool/langtable/) * Sat Aug 26 2023 Ray Strode - 44.0-6 - Improve APIs for finding default input sources Package: gnome-initial-setup-45~beta-6.fc40 Old package: gnome-initial-setup-45~beta-3.fc40 Summary: Bootstrapping your OS RPMs: gnome-initial-setup Size: 2.25 MiB Size change: -102 B Changelog: * Sat Aug 26 2023 Ray Strode - 45~beta-4 - Add keyboard and input method handling fixes * Sat Aug 26 2023 Ray Strode - 45~beta-5 - Clean up gnome-desktop requires * Sat Aug 26 2023 Ray Strode - 45~beta-6 - Update to use slightly tweaked default input sources api from gnome- desktop Package: haruna-0.12.0-1.fc40 Old package: haruna-0.11.3-3.fc39 Summary: Open source video player built with Qt/QML and libmpv RPMs: haruna Size: 1.71 MiB Size change: 222.33 KiB Changelog: * Sat Aug 26 2023 Yaroslav Sidlovsky - 0.12.0-1 - version 0.12.0 Package: javacc-7.0.12-3.fc40 Old package: javacc
Re: python3-PyPDf2 -> python3-pydf package
On 27-08-2023 06:33, Globe Trotter via devel wrote: I am the maintainer of python-PyPDF2 for Fedora (which I do since I was interested in pdf-stapler that I also maintain as a consequence). For a while now, upstream has been wanting all PyPDF2 users to pypdf. I was wondering how I go about this for the F38 repos. Do I need to go through packaging again, or is there an easier way to update python3-PyPDF2 to python3-pypdf? If so, what do I have to do? Could you provide some links to the upstream sources of PyPDF2 and pypdf? And me be also to the issue where the switch from PyPDF2 to pypdf is discussed. I'm assuming PyPDF2 and pypdf are separate packages. In that case you would need to submit pypdf as a new package. Once pdf-stapler is built against pypdf you can retire PyPDF2 if no other package depends on it. If pypdf is a rename of PyPDF2 you'd submit a re-review of the package and you need to take care of proper Provides: and Obsoletes: in the new package. See the docs for more info: https://docs.fedoraproject.org/en-US/package-maintainers/Package_Renaming_Process/ https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages I hope that helps. -- Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
