Bug 260440 - devel/py-Jinja2: Update to 3.0.3
Summary: devel/py-Jinja2: Update to 3.0.3
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Yuri Victorovich
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2021-12-15 16:51 UTC by Brad Davis
Modified: 2022-11-13 23:54 UTC (History)
2 users (show)

See Also:

Attachments
patch (848 bytes, patch)
2021-12-15 16:51 UTC, Brad Davis 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brad Davis freebsd_committer freebsd_triage 2021-12-15 16:51:20 UTC 
Created attachment 230143 [details]
patch
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2021-12-16 00:56:06 UTC 
Sphinx consumers need bulk testing
Comment 2 Yuri Victorovich freebsd_committer freebsd_triage 2022-11-09 00:14:46 UTC 
Port updated.
Thanks!
Comment 3 commit-hook freebsd_committer freebsd_triage 2022-11-09 00:21:53 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=23cc43859179b1bb1b6932ccee2559ed5f66a968

commit 23cc43859179b1bb1b6932ccee2559ed5f66a968
Author:     Yuri Victorovich <yuri@FreeBSD.org>
AuthorDate: 2022-11-08 15:03:00 +0000
Commit:     Yuri Victorovich <yuri@FreeBSD.org>
CommitDate: 2022-11-09 00:21:12 +0000

    devel/py-Jinja2: Update 3.0.1 -> 3.1.2; Fix test target

    PR:             260440 264990
    Approved by:    nivit@ (maintainer's timoeut on 260440; 10.5 months)
    Submitted by:   brd@, p5B2EA84B3@t-online.de

 devel/py-Jinja2/Makefile | 11 +++++------
 devel/py-Jinja2/distinfo |  6 +++---
 2 files changed, 8 insertions(+), 9 deletions(-)
Comment 4 Kubilay Kocak freebsd_committer freebsd_triage 2022-11-13 23:54:57 UTC 
@Yuri This sphinx update caused a regression.

This port is maintained by python@, nivit@ just happened to be assigned to nivit@. 

The correct/better course of action would have been a reset of assignee to python@ (as it wasn't on our radar). It was an assignee timeout, not a maintainer timeout.

Not withstanding, comment 1 detailed what was necessary to progress, which wasn't ack'd.

The missing bulk / consumer  build test would have picked up the regression.

Further, this update was for 3.0.3 (which wouldn't have broken the build)

The commit updating to 3.1 should have gone through a cycle on this issue, including updating the summary to match.