Bug 280523
| Summary: | devel/py-identify: Update to 2.6.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Nicholas Kirby <nick> | ||||
| Component: | Individual Port(s) | Assignee: | Muhammad Moinur Rahman <bofh> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | Flags: | bugzilla:
maintainer-feedback?
(bofh) |
||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=8d861ee315599836d77922fced3f1743bc2027db commit 8d861ee315599836d77922fced3f1743bc2027db Author: Nicholas Kirby <nick@kirby.cx> AuthorDate: 2024-08-18 07:43:49 +0000 Commit: Muhammad Moinur Rahman <bofh@FreeBSD.org> CommitDate: 2024-08-18 07:45:27 +0000 devel/py-identify: Update version 1.4.30=>2.6.0 Changelog: https://github.com/pre-commit/identify/releases/tag/v2.6.0 PR: 280523 devel/py-identify/Makefile | 2 +- devel/py-identify/distinfo | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) It's better if we get git-formatted patches. Do not add an attachment or patch while creating the bug report. Just create the report with the necessary synopsis. Then, create the git-formatted patch, especially with the PR. There are a number of git meta fields that can be set. If you do `git config—-add core.hooksPath .hooks`, then it will pop up a pre-formatted commit message that is self-explanatory. |
Created attachment 252384 [details] Update to 2.6.0 Significant update to py-identify Can't find any detailed changelogs Builds fine in pooudriere