[Bug 2232889] New: perl-ORLite-2.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2232889 Bug ID: 2232889 Summary: perl-ORLite-2.00 is available Product: Fedora Version: rawhide Status: NEW Component: perl-ORLite 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, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 2.00 Upstream release that is considered latest: 2.00 Current version/release in rawhide: 1.99-1.fc40 URL: http://search.cpan.org/dist/ORLite/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3181/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-ORLite -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2232889 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202232889%23c0 ___ 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 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-917679773c GitPython-3.1.32-1.el9 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e2fcc4af81 llhttp-8.1.1-1.el9 python-aiohttp-3.8.5-1.el9 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f08c8f0812 chromium-116.0.5845.96-1.el9 The following builds have been pushed to Fedora EPEL 9 updates-testing clamav-1.0.2-1.el9 libXISF-0.2.9-1.el9 python-django-clacks-0.3.1-1.el9 Details about builds: clamav-1.0.2-1.el9 (FEDORA-EPEL-2023-e2f8cb1ee1) End-user tools for the Clam Antivirus scanner Update Information: CVE-2023-20197 ClamAV File Scanning Infinite Loop Denial of Service Vulnerability ChangeLog: * Fri Aug 18 2023 Orion Poplawski - 1.0.2-1 - Update to 1.0.2 CVE-2023-20197 (bz#2232508) * Wed Jul 19 2023 Fedora Release Engineering - 1.0.1-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Mon Feb 27 2023 Orion Poplawski - 1.0.1-4 - Mark cvd files is clamav-data as %config(noreplace) (bz#2170876) - Rename clamav-update to clamav-freshclam - Make clamav-freshclam supplement clamd - Have clamav-freshclam ghost all of the .cld and .cvd files - Update data files with help of Cisco-Talos/cvdupdate - Update to 1.0.1 - Make sure RUSTFLAGS are passed to rustc (bz#2167194) - Fix multilib install References: [ 1 ] Bug #2232508 - CVE-2023-20197 fedora: ClamAV File Scanning Infinite Loop Denial of Service Vulnerability https://bugzilla.redhat.com/show_bug.cgi?id=2232508 libXISF-0.2.9-1.el9 (FEDORA-EPEL-2023-083644b9d3) Library to load and write XISF format Update Information: - Upgrade to 0.2.9 - Enable zstd support ChangeLog: * Fri Aug 18 2023 Mattia Verga - 0.2.9-1 - Update to 0.2.9 (fedora#2231736) - Enable zstd support * Thu Jul 20 2023 Fedora Release Engineering - 0.2.8-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild python-django-clacks-0.3.1-1.el9 (FEDORA-EPEL-2023-1b5b68c3d7) Django Middleware for X-Clacks-Overhead Update Information: Initial import (fedora#2229551). ChangeLog: * Sat Aug 19 2023 Daniel Milnes - 0.3.1-1 - Initial import (fedora#2229551). ___ 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
F40 Proposal: Revitalize Forge Macros (Self-Contained Change proposal)
(I'm announcing this myself as per https://pagure.io/fesco/issue/3051.)
https://fedoraproject.org/wiki/Changes/Revitalize_Forge_Macros
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive community
feedback. This proposal will only be implemented if approved by the
Fedora Engineering Steering Committee.
== Summary ==
Up until now, the
[https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/7331757cf12ee645e895e7e6e91d73ff66106e12/f/macros.forge
forge macros]
have been part of {{package|redhat-rpm-config}}.
We will split them out into a new `forge-srpm-macros` package.
We will add more test coverage and add a new `%forgeversion` macro to allow
adding snapshot info to Version instead of Release.
== Owner ==
* Name: [[User:gotmax23| Maxwell G]]
* Email: maxw...@gtmx.me
== Detailed Description ==
The forge macros will be removed from
{{package|redhat-rpm-config}} in favor of a standalone `forge-srpm-macros`
package.
{{package|redhat-rpm-config}} will gain a dependency on `forge-srpm-macros`.
This will ease maintenance and allow the forge macros to develop independently
of redhat-rpm-config.
This split will also allow us to address longstanding issues such as
lack of test coverage and noncompliance with the new Versioning Guidelines that
mandate putting snapshot info in Version instead of Release.
Development is under way in https://git.sr.ht/~gotmax23/forge-srpm-macros.
Maintaining the macros in a separate upstream repository enables us to have
proper CI and proper versioning and frees us from having to sync macro files
across distgit branches.
The new forge-srpm-macros project
now has support for Codeberg, nested Gitlab groups, and a new
[https://git.sr.ht/~gotmax23/forge-srpm-macros/commit/145b7fc72a31b7e547bfdd114c6c68aa56374043
`%forgeversion` macro].
There are also unit tests covering the core forge macros functionality to
prevent future regressions.
The tests have already uncovered a two year old bug in the Pagure forge
functionality!
For now, we will limit this Change to rawhide, but we may backport the
`forge-srpm-macros` package to stable Fedora releases depending on feedback
from the redhat-rpm-config maintainers and other stakeholders.
This is not a backwards incompatible Change,
so it should be safe to backport after proper testing in Rawhide.
== Feedback ==
The redhat-rpm-config maintainers have expressed that they'd prefer if the forge
macros were split into a separate project.
Other developers have expressed that the lack of regression tests makes them
hesitant to propose or accept changes to the forge macros; this Change fixes
that.
The Go SIG who makes use of {{package|go-rpm-macros}} that relies on the forge
macros is happy to see more maintenance of these macros.
The inability to get changes into the forge macros have blocked us from fixing
bugs that affect the Go macros.
== Benefit to Fedora ==
This split out will ease maintenance and allow us to address longstanding
issues in the current codebase.
== Scope ==
* Proposal owners:
** ✅ Create an upstream repository for the forge-srpm-macros project
** ✅ Prepare a PR for {{package|redhat-rpm-config}} to remove the macros and
associated forge.lua code and add a dependency on the new package:
https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/260
** Submit the `forge-srpm-macros` package for review
** Build `forge-srpm-macros` and the updated {{package|redhat-rpm-config}}
package in a side tag using provenpackager privileges
** Close existing PRs open against the forge macros and direct authors to the
new project
* Other developers:
** Review the {{package|redhat-rpm-config}} PR
** Preform test builds of packages that use the forge macros
* Policies and guidelines:
** ✅ Adjust the
[https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/ SourceURL
Packaging Guidelines] to recommend the new `%forgeversion` macro:
https://pagure.io/packaging-committee/pull-request/1295
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
There shouldn't be any.
The forge macros will remain in the buildroot,
and {{package|redhat-rpm-config}} will Require the new package.
== How To Test ==
There is a test Copr available that contains builds of `forge-srpm-macros`'
`main` branch.
You can use it in mock like this:
copr mock-config gotmax23/forge-srpm-macros-dev fedora-rawhide-x86_64 >
~/.config/mock/forge.cfg
fedpkg sources
# To preform a full package build
mock --spec *.spec --source . -r forge
# To build a source package only
mock --buildsrpm --spec *.spec --source . -r forge
== User Experience ==
This is a developer focussed Change.
This Change does not propose any drastic changes to the macros themselves and
does not mandate specfile changes,
so it shouldn't be too visible.
== Dependencies ==
This change requires coordination with the
Re: %pyproject_save_files license handlers
On Sat Aug 19, 2023 at 22:13 +0200, Miro Hrončok wrote: > On 19. 08. 23 19:44, Maxwell G wrote: > > Hi Pythonistas, > > > > %pyproject_save_files automatically handles marking license files > > with %license when a build backend installs them into a package's > > dist-info directory and the License-File header is specified in the > > METADATA file. Currently, only setuptools and hatchling meet this > > criteria. Notably, poetry and flit do not support this. They will > > install license texts into the dist-info directory, but they do not add > > the License-File metadata. The License-File tag is not standardized, and > > discussion on PEP 639 which defines this standard has stalled. I believe > > relying on this feature is a problem, as if a project changes build > > systems or some other config and a packager doesn't realize, suddenly > > the license file won't be marked with %license or even worse, not > > installed at all. Since the pyproject macros read the build backend from > > pyproject.toml without packagers having to manually specify anything > > (which is generally great!), this situation seems likely to occur. > > > > Until these issues are resolved, I propose banning this in Fedora and > > requiring packagers to manually mark files with %license or at least > > adding a large warning to the Packaging Guidelines. It can be similar to > > the `'*' +auto` flags which are used by pyp2spec for automatic PyPI > > builds in Copr but not allowed in Fedora proper. > > What do y'all think? Am I missing something? > > Hey. Alternatively to banning this: what if we make %pyproject_save_files > fail > without a license? Obviously, that would be a breaking change, so it could be > opt-in first. > >%pyproject_save_files -l ... > > When used like this, no License-File header would result in an error. > > We could introduce a reverse flag -L (don't fail without a license), and have > a > discussion about changing the default later. > > The guidelines could than say something like: If there is a license file you > MUST do one of the following when using %pyproject_save_files: > > 1) use -l and don't list it in %files explicitly > 2) use -L and list it in %files explicitly > > That way, we ensure the license is packaged (and marked as %license) while > not > reducing automation. > I like -l flag idea, but I don't think we can make it fail by default for the foreseeable future, given the status of PEP 639 and build system adoption. We could use a heuristic (such as a hardcoded list of globs) to match license files in dist-info directories if License-File doesn't exist, but I'm not sure that's the best idea. I'm hesitant about adding a noop -L flag until we actually have a plan/criteria on when to start enforcing -l, but I don't feel strongly. -- Maxwell G (@gotmax23) Pronouns: He/They ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F40 Proposal: Revitalize Forge Macros (Self-Contained Change proposal)
(I'm announcing this myself as per https://pagure.io/fesco/issue/3051.)
https://fedoraproject.org/wiki/Changes/Revitalize_Forge_Macros
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive community
feedback. This proposal will only be implemented if approved by the
Fedora Engineering Steering Committee.
== Summary ==
Up until now, the
[https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/7331757cf12ee645e895e7e6e91d73ff66106e12/f/macros.forge
forge macros]
have been part of {{package|redhat-rpm-config}}.
We will split them out into a new `forge-srpm-macros` package.
We will add more test coverage and add a new `%forgeversion` macro to allow
adding snapshot info to Version instead of Release.
== Owner ==
* Name: [[User:gotmax23| Maxwell G]]
* Email: maxw...@gtmx.me
== Detailed Description ==
The forge macros will be removed from
{{package|redhat-rpm-config}} in favor of a standalone `forge-srpm-macros`
package.
{{package|redhat-rpm-config}} will gain a dependency on `forge-srpm-macros`.
This will ease maintenance and allow the forge macros to develop independently
of redhat-rpm-config.
This split will also allow us to address longstanding issues such as
lack of test coverage and noncompliance with the new Versioning Guidelines that
mandate putting snapshot info in Version instead of Release.
Development is under way in https://git.sr.ht/~gotmax23/forge-srpm-macros.
Maintaining the macros in a separate upstream repository enables us to have
proper CI and proper versioning and frees us from having to sync macro files
across distgit branches.
The new forge-srpm-macros project
now has support for Codeberg, nested Gitlab groups, and a new
[https://git.sr.ht/~gotmax23/forge-srpm-macros/commit/145b7fc72a31b7e547bfdd114c6c68aa56374043
`%forgeversion` macro].
There are also unit tests covering the core forge macros functionality to
prevent future regressions.
The tests have already uncovered a two year old bug in the Pagure forge
functionality!
For now, we will limit this Change to rawhide, but we may backport the
`forge-srpm-macros` package to stable Fedora releases depending on feedback
from the redhat-rpm-config maintainers and other stakeholders.
This is not a backwards incompatible Change,
so it should be safe to backport after proper testing in Rawhide.
== Feedback ==
The redhat-rpm-config maintainers have expressed that they'd prefer if the forge
macros were split into a separate project.
Other developers have expressed that the lack of regression tests makes them
hesitant to propose or accept changes to the forge macros; this Change fixes
that.
The Go SIG who makes use of {{package|go-rpm-macros}} that relies on the forge
macros is happy to see more maintenance of these macros.
The inability to get changes into the forge macros have blocked us from fixing
bugs that affect the Go macros.
== Benefit to Fedora ==
This split out will ease maintenance and allow us to address longstanding
issues in the current codebase.
== Scope ==
* Proposal owners:
** ✅ Create an upstream repository for the forge-srpm-macros project
** ✅ Prepare a PR for {{package|redhat-rpm-config}} to remove the macros and
associated forge.lua code and add a dependency on the new package:
https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/260
** Submit the `forge-srpm-macros` package for review
** Build `forge-srpm-macros` and the updated {{package|redhat-rpm-config}}
package in a side tag using provenpackager privileges
** Close existing PRs open against the forge macros and direct authors to the
new project
* Other developers:
** Review the {{package|redhat-rpm-config}} PR
** Preform test builds of packages that use the forge macros
* Policies and guidelines:
** ✅ Adjust the
[https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/ SourceURL
Packaging Guidelines] to recommend the new `%forgeversion` macro:
https://pagure.io/packaging-committee/pull-request/1295
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
There shouldn't be any.
The forge macros will remain in the buildroot,
and {{package|redhat-rpm-config}} will Require the new package.
== How To Test ==
There is a test Copr available that contains builds of `forge-srpm-macros`'
`main` branch.
You can use it in mock like this:
copr mock-config gotmax23/forge-srpm-macros-dev fedora-rawhide-x86_64 >
~/.config/mock/forge.cfg
fedpkg sources
# To preform a full package build
mock --spec *.spec --source . -r forge
# To build a source package only
mock --buildsrpm --spec *.spec --source . -r forge
== User Experience ==
This is a developer focussed Change.
This Change does not propose any drastic changes to the macros themselves and
does not mandate specfile changes,
so it shouldn't be too visible.
== Dependencies ==
This change requires coordination with the
Re: %pyproject_save_files license handlers
On 19. 08. 23 19:44, Maxwell G wrote: Hi Pythonistas, %pyproject_save_files automatically handles marking license files with %license when a build backend installs them into a package's dist-info directory and the License-File header is specified in the METADATA file. Currently, only setuptools and hatchling meet this criteria. Notably, poetry and flit do not support this. They will install license texts into the dist-info directory, but they do not add the License-File metadata. The License-File tag is not standardized, and discussion on PEP 639 which defines this standard has stalled. I believe relying on this feature is a problem, as if a project changes build systems or some other config and a packager doesn't realize, suddenly the license file won't be marked with %license or even worse, not installed at all. Since the pyproject macros read the build backend from pyproject.toml without packagers having to manually specify anything (which is generally great!), this situation seems likely to occur. Until these issues are resolved, I propose banning this in Fedora and requiring packagers to manually mark files with %license or at least adding a large warning to the Packaging Guidelines. It can be similar to the `'*' +auto` flags which are used by pyp2spec for automatic PyPI builds in Copr but not allowed in Fedora proper. What do y'all think? Am I missing something? Hey. Alternatively to banning this: what if we make %pyproject_save_files fail without a license? Obviously, that would be a breaking change, so it could be opt-in first. %pyproject_save_files -l ... When used like this, no License-File header would result in an error. We could introduce a reverse flag -L (don't fail without a license), and have a discussion about changing the default later. The guidelines could than say something like: If there is a license file you MUST do one of the following when using %pyproject_save_files: 1) use -l and don't list it in %files explicitly 2) use -L and list it in %files explicitly That way, we ensure the license is packaged (and marked as %license) while not reducing automation. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230819.n.0 changes
OLD: Fedora-Rawhide-20230818.n.0
NEW: Fedora-Rawhide-20230819.n.0
= SUMMARY =
Added images:2
Dropped images: 8
Added packages: 10
Dropped packages:6
Upgraded packages: 77
Downgraded packages: 0
Size of added packages: 9.48 MiB
Size of dropped packages:26.80 MiB
Size of upgraded packages: 2.05 GiB
Size of downgraded packages: 0 B
Size change of upgraded packages: 33.64 MiB
Size change of downgraded packages: 0 B
= ADDED IMAGES =
Image: LXQt live aarch64
Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20230819.n.0.iso
Image: Workstation live aarch64
Path:
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230819.n.0.iso
= DROPPED IMAGES =
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230818.n.0.iso
Image: Silverblue dvd-ostree aarch64
Path:
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20230818.n.0.iso
Image: Silverblue dvd-ostree x86_64
Path:
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20230818.n.0.iso
Image: Server boot ppc64le
Path: Server/ppc64le/iso/Fedora-Server-netinst-ppc64le-Rawhide-20230818.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path:
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230818.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230818.n.0.iso
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20230818.n.0.iso
Image: Server dvd ppc64le
Path: Server/ppc64le/iso/Fedora-Server-dvd-ppc64le-Rawhide-20230818.n.0.iso
= ADDED PACKAGES =
Package: gmult-12.0-2.fc40
Summary: Multiplication Puzzle
RPMs:gmult
Size:332.78 KiB
Package: golang-github-apapsch-jsonmerge-2-2.0.0-1.fc40
Summary: Merge JSON objects
RPMs:golang-github-apapsch-jsonmerge-2
golang-github-apapsch-jsonmerge-2-devel
Size:2.82 MiB
Package: golang-github-bmatcuk-doublestar-1.3.4-1.fc40
Summary: Implements support for double star matches in Go's path.Match and
filepath.Glob
RPMs:golang-github-bmatcuk-doublestar-devel
Size:18.93 KiB
Package: golang-github-gofiber-fiber-2-2.48.0-1.fc40
Summary: Express inspired web framework written in Go
RPMs:golang-github-gofiber-fiber-2-devel
Size:390.44 KiB
Package: golang-github-juju-gnuflag-1.0.0-1.fc40
Summary: GNU-compatible flag handling with a stdlib-like API for Go
RPMs:golang-github-juju-gnuflag-devel
Size:19.87 KiB
Package: golang-github-lestrrat-backoff-2-2.0.8-2.fc40
Summary: Backoff mechanics for Go
RPMs:golang-github-lestrrat-backoff-2-devel
Size:23.41 KiB
Package: golang-github-ravenox-jsoncommentstrip-1.0.0-1.fc40
Summary: Library for strip JSON comments
RPMs:golang-github-ravenox-jsoncommentstrip
golang-github-ravenox-jsoncommentstrip-devel
Size:2.00 MiB
Package: golang-github-ravenox-jsonmerge-1.0.0-1.20230722git0828c73.fc40
Summary: Merge JSON objects to one (replaces only existent values)
RPMs:golang-github-ravenox-jsonmerge-devel
Size:21.69 KiB
Package: golang-github-spkg-bom-1.0.0-1.fc40
Summary: Strip UTF-8 byte order marks
RPMs:golang-github-spkg-bom-devel
Size:11.72 KiB
Package: libgedit-gtksourceview-299.0.4-1.fc40
Summary: Gedit Technology - Source code editing widget
RPMs:libgedit-gtksourceview libgedit-gtksourceview-devel
Size:3.86 MiB
= DROPPED PACKAGES =
Package: R-rgdal-1.6.7-2.fc39
Summary: Bindings for the 'Geospatial' Data Abstraction Library
RPMs:R-rgdal
Size:17.09 MiB
Package: R-rgeos-0.6.4-1.fc39
Summary: Interface to Geometry Engine - Open Source ('GEOS')
RPMs:R-rgeos
Size:3.15 MiB
Package: libgpuarray-0.7.6-21.fc39
Summary: Library to manipulate tensors on a GPU
RPMs:libgpuarray libgpuarray-devel libgpuarray-doc python3-pygpu
python3-pygpu-devel
Size:3.63 MiB
Package: python-theano-1.1.2-6.fc38
Summary: Mathematical expressions involving multidimensional arrays
RPMs:python-theano-doc python3-theano
Size:2.69 MiB
Package: python-visionegg-quest-1.1-16.fc38
Summary: QUEST algorithm for finding threshold
RPMs:python3-visionegg-quest
Size:22.49 KiB
Package: transmageddon-1.5-30.fc38
Summary: Video transcoder
RPMs:transmageddon
Size:220.62 KiB
= UPGRADED PACKAGES =
Package: R-broom-1.0.5-1.fc40
Old package: R-broom-1.0.4-3.fc39
Summary: Convert Statistical Objects into Tidy Tibbles
RPMs: R-broom
Size: 1.97 MiB
Size change: -2.60 KiB
Changelog:
* Fri Aug 18 2023 I??aki ??car - 1.0.5-1
- Update to 1.0.5
Package: R-ggplot2-3.4.3-1.fc40
Old package: R-ggplot2-3.4.2-3.fc39
Summary: Create Elegant Data Visualisations Using the Grammar of Graphics
RPMs: R-ggplot2
Size: 3.47 MiB
Size change: -862.13 KiB
Changelog:
* Fri Aug 18 2023 I??aki ??car - 3.4.3-1
- Update to 3.4.3
Package: R-sp-2.0.0-1.fc40
Old package: R-sp-1.6.1-2.fc39
Summary
%pyproject_save_files license handlers
Hi Pythonistas, %pyproject_save_files automatically handles marking license files with %license when a build backend installs them into a package's dist-info directory and the License-File header is specified in the METADATA file. Currently, only setuptools and hatchling meet this criteria. Notably, poetry and flit do not support this. They will install license texts into the dist-info directory, but they do not add the License-File metadata. The License-File tag is not standardized, and discussion on PEP 639 which defines this standard has stalled. I believe relying on this feature is a problem, as if a project changes build systems or some other config and a packager doesn't realize, suddenly the license file won't be marked with %license or even worse, not installed at all. Since the pyproject macros read the build backend from pyproject.toml without packagers having to manually specify anything (which is generally great!), this situation seems likely to occur. Until these issues are resolved, I propose banning this in Fedora and requiring packagers to manually mark files with %license or at least adding a large warning to the Packaging Guidelines. It can be similar to the `'*' +auto` flags which are used by pyp2spec for automatic PyPI builds in Copr but not allowed in Fedora proper. What do y'all think? Am I missing something? -- Best, Maxwell G (@gotmax23) Pronouns: He/They ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Packaging software for LulzBot Taz-6 3D printer
I am trying to package the software necessary to operate the LulzBot Taz-6 3D printer. This seems to have been supported in previous versions of Fedora [1], so I am trying to take ownership of retired packages. Some of the dependencies should be broadly useful, like the arduino package. I could use help with two things: (1) package reviewing and (2) help with two of the packages. The following are available for review now: jakarta-commons-httpclient: https://bugzilla.redhat.com/show_bug.cgi?id=2232859 jmdns: https://bugzilla.redhat.com/show_bug.cgi?id=2232860 jsemver: https://bugzilla.redhat.com/show_bug.cgi?id=2232861 python-uranium-lulzbot: https://bugzilla.redhat.com/show_bug.cgi?id=2232862 libarcus-lulzbot: https://bugzilla.redhat.com/show_bug.cgi?id=2232864 CuraEngine-lulzbot: https://bugzilla.redhat.com/show_bug.cgi?id=2232865 cura-lulzbot: https://bugzilla.redhat.com/show_bug.cgi?id=2232866 The dependencies led me to create a COPR repository to aid in the review process: [copr:copr.fedorainfracloud.org:mikep:lulzbot] name=Copr repo for lulzbot owned by mikep baseurl=https://download.copr.fedorainfracloud.org/results/mikep/lulzbot/fedora-$releasever-$basearch/ type=rpm-md skip_if_unavailable=True gpgcheck=1 gpgkey=https://download.copr.fedorainfracloud.org/results/mikep/lulzbot/pubkey.gpg repo_gpgcheck=0 enabled=1 enabled_metadata=1 I could use help with two of the packages: arduino and lulzbot-marlin-firmware. To get the arduino package to build and install, I had to remove some dependencies. First, arduino-builder is deprecated. Does someone know Arduino enough to know if I need to replace this with arduino-cli? (And how?) Second, I removed the dependency on asm2, which I found used deprecated RPM macros such as %add_to_maven_depmap. Could someone take a look at that retired package and suggest how to modernize it towards the newer macros? The lulzbot-marlin-firmware does not build. The build fails with: /usr/lib/gcc/arm-none-eabi/12.2.0/../../../../arm-none-eabi/bin/ld: cannot find ../ArduinoAddons/arduino-1.8.5/packages/ultimachine/hardware/sam/1.6.9-b/variants/archim/libsam_sam3x8e_gcc_rel.a: No such file or directory Does anyone know where libsam_sam3x8e_gcc_rel.a is supposed to come from? [1] https://lulzbot.com/learn/cura-lulzbot-edition-installation-fedora -- Mike :wq ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 39 compose report: 20230819.n.0 changes
OLD: Fedora-39-20230818.n.0
NEW: Fedora-39-20230819.n.0
= SUMMARY =
Added images:1
Dropped images: 3
Added packages: 9
Dropped packages:6
Upgraded packages: 59
Downgraded packages: 0
Size of added packages: 20.14 MiB
Size of dropped packages:26.80 MiB
Size of upgraded packages: 836.26 MiB
Size of downgraded packages: 0 B
Size change of upgraded packages: 16.78 MiB
Size change of downgraded packages: 0 B
= ADDED IMAGES =
Image: Workstation live ppc64le
Path:
Workstation/ppc64le/iso/Fedora-Workstation-Live-ppc64le-39-20230819.n.0.iso
= DROPPED IMAGES =
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-39-20230818.n.0.iso
Image: Container_Toolbox docker ppc64le
Path:
Container/ppc64le/images/Fedora-Container-Toolbox-39-20230818.n.0.ppc64le.tar.xz
Image: Workstation live aarch64
Path:
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-39-20230818.n.0.iso
= ADDED PACKAGES =
Package: gmult-12.0-2.fc39
Summary: Multiplication Puzzle
RPMs:gmult
Size:332.56 KiB
Package: golang-github-bmatcuk-doublestar-1.3.4-1.fc39
Summary: Implements support for double star matches in Go's path.Match and
filepath.Glob
RPMs:golang-github-bmatcuk-doublestar-devel
Size:18.93 KiB
Package: golang-github-gofiber-fiber-2-2.48.0-2.fc39
Summary: Express inspired web framework written in Go
RPMs:golang-github-gofiber-fiber-2-devel
Size:390.42 KiB
Package: golang-github-juju-gnuflag-1.0.0-1.fc39
Summary: GNU-compatible flag handling with a stdlib-like API for Go
RPMs:golang-github-juju-gnuflag-devel
Size:19.87 KiB
Package: golang-github-lestrrat-backoff-2-2.0.8-2.fc39
Summary: Backoff mechanics for Go
RPMs:golang-github-lestrrat-backoff-2-devel
Size:23.42 KiB
Package: golang-github-ravenox-jsoncommentstrip-1.0.0-1.fc39
Summary: Library for strip JSON comments
RPMs:golang-github-ravenox-jsoncommentstrip
golang-github-ravenox-jsoncommentstrip-devel
Size:1.99 MiB
Package: golang-github-ravenox-jsonmerge-1.0.0-1.20230722git0828c73.fc39
Summary: Merge JSON objects to one (replaces only existent values)
RPMs:golang-github-ravenox-jsonmerge-devel
Size:21.69 KiB
Package: golang-github-spkg-bom-1.0.0-1.fc39
Summary: Strip UTF-8 byte order marks
RPMs:golang-github-spkg-bom-devel
Size:11.72 KiB
Package: onnxruntime-1.15.1-2.fc39
Summary: A cross-platform inferencing and training accelerator
RPMs:onnxruntime onnxruntime-devel onnxruntime-doc
Size:17.35 MiB
= DROPPED PACKAGES =
Package: R-rgdal-1.6.7-2.fc39
Summary: Bindings for the 'Geospatial' Data Abstraction Library
RPMs:R-rgdal
Size:17.09 MiB
Package: R-rgeos-0.6.4-1.fc39
Summary: Interface to Geometry Engine - Open Source ('GEOS')
RPMs:R-rgeos
Size:3.15 MiB
Package: libgpuarray-0.7.6-21.fc39
Summary: Library to manipulate tensors on a GPU
RPMs:libgpuarray libgpuarray-devel libgpuarray-doc python3-pygpu
python3-pygpu-devel
Size:3.63 MiB
Package: python-theano-1.1.2-6.fc38
Summary: Mathematical expressions involving multidimensional arrays
RPMs:python-theano-doc python3-theano
Size:2.69 MiB
Package: python-visionegg-quest-1.1-16.fc38
Summary: QUEST algorithm for finding threshold
RPMs:python3-visionegg-quest
Size:22.49 KiB
Package: transmageddon-1.5-30.fc38
Summary: Video transcoder
RPMs:transmageddon
Size:220.64 KiB
= UPGRADED PACKAGES =
Package: R-broom-1.0.5-1.fc39
Old package: R-broom-1.0.4-3.fc39
Summary: Convert Statistical Objects into Tidy Tibbles
RPMs: R-broom
Size: 1.96 MiB
Size change: -2.68 KiB
Changelog:
* Fri Aug 18 2023 I??aki ??car - 1.0.5-1
- Update to 1.0.5
Package: R-ggplot2-3.4.3-1.fc39
Old package: R-ggplot2-3.4.2-3.fc39
Summary: Create Elegant Data Visualisations Using the Grammar of Graphics
RPMs: R-ggplot2
Size: 3.46 MiB
Size change: -862.39 KiB
Changelog:
* Fri Aug 18 2023 I??aki ??car - 3.4.3-1
- Update to 3.4.3
Package: R-sp-2.0.0-1.fc39
Old package: R-sp-1.6.1-2.fc39
Summary: Classes and Methods for Spatial Data
RPMs: R-sp R-sp-devel
Size: 9.38 MiB
Size change: -64.70 KiB
Changelog:
* Fri Aug 18 2023 I??aki ??car - 2.0.0-1
- Update to 2.0.0
Package: SDL2_sound-2.0.2-1.fc39
Old package: SDL2_sound-2.0.1-5.fc39
Summary: An abstract soundfile decoder library
RPMs: SDL2_sound SDL2_sound-devel
Size: 1.84 MiB
Size change: 31.11 KiB
Changelog:
* Thu Aug 17 2023 Dominik Mierzejewski - 2.0.2-1
- update to 2.0.2 (#2218920)
- update bundled dependencies versions
- include cmake and pkgconfig files in -devel
Package: asv-0.5.1-12.fc39
Old package: asv-0.5.1-8.fc38
Summary: Airspeed Velocity: A simple Python history benchmarking tool
RPMs: asv asv-doc
Size: 4.34 MiB
Size change: -517.20 KiB
Changelog:
* Sun Apr 09 2023 Elliott Sales de Andrade -
0.5.1-9
[Bug 2232294] perl-Wx-GLCanvas-0.09-36.fc40 FTBFS: Makefile.PL fails
https://bugzilla.redhat.com/show_bug.cgi?id=2232294
--- Comment #7 from Scott Talbert ---
(In reply to Miro Hrončok from comment #5)
> > How to prevent this kind of issue?
>
> We could add something like this to perl-Wx:
>
> Requires: wxGTK = %(rpm -q wxGTK --qf='%%{VERSION}')
>
> That way, when wxGTK is updated, we would be forced to rebuild it. The
> maintainer of wxGTK would obviously need to be aware of this.
Actually...perl-Alien-wxWidgets has a Provides like
perl(Alien::wxWidgets::Config::gtk_3_2_2_uni_gcc_3_4), so perhaps perl-Wx
should have a Requires on this exact Depends (that it was built with) instead?
On the other hand, perl-Alien-wxWidgets should probably have a Requires on the
exact wxGTK version it was built with. I think?
In any event, I'm aware of these issues now and won't go updating wxGTK
carelessly anymore. ;) Feel free to make me a co-maintainer of all these
packages (perl-Alien-wxWidgets, perl-wx, perl-wx-glcanvas) and I can do
rebuilds in a side tag when there's an update.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2232294
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202232294%23c7
___
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
