devel/pybugz : update 0.11.1->0.12.3 , change maintainer crees@FreeBSD.org->pgollucci@FreeBSD.org - update 0.11.1->0.12.3 - request maintainer pgollucci@FreeBSD.org Changes: -------- Switch to my fork for use in ports-mgmt/freebsd-bugzilla-cli, upstream williamh is unresponsive Add creator/reporter column Fix quoting, and allow % [1] Add freebsd.conf file [1] Submitted by: jbeich@ -- Generated by ports-mgmt/freebsd-bugzilla-cli - v0.14.0.
Created attachment 160181 [details] patch patch
Created attachment 160182 [details] poudriere log poudriere log
Comment on attachment 160182 [details] poudriere log Did you attach the log via |bugz attach|? It regressed in upstream version on which your fork is based. The fix is trivial but better to understand why it doesn't happen in 0.11.1. https://github.com/williamh/pybugz/issues/88
well I used ports-mgmt/freebsd-bugzilla-cli but it dispatched out to bugz attach. I've never seen it fail with or without -p.
bugmeister@ why wasn't this auto assigned ?
Be my guest :)
While here please fix the man pages installation that goes in the wrong place!
Note I haven't the update, but I did check the current pybugz
Created attachment 171851 [details] fork, v0 jmg reported ports r411240 broke freebsd-bugzilla-cli but not exactly what. Maybe because 0.12 moved on from ~/.bugz_token* to API keys in ~/.bugzrc which requires user interaction to upgrade but not for new install (see big warning on startup). As pgollucci's fork uses incompatible versions anyway let's take a step further by making a port until maintainer comes back or someone else volunteers to fix. Note, v0 conflict with master port can be avoided via USES=uniquefiles.
With pgollucci@ (new upstream) being inactive ports-mgmt/freebsd-bugzilla-cli is effectively abandonware. The only remaining user ran away instead of helping to test the fix. comment 9 alluded to the following (sent privately): From: John-Mark Gurney <jmg|funkthat|com> Subject: please fix freebsd-bugzilla-cli.. To: jbeich|FreeBSD|org Date: Sun, 26 Jun 2016 18:28:51 -0700 I believe your upgrade of pybugz to 0.12.1 broke freebsd-bugzilla-cli, so please either revert the change, or fix freebsd-bugzilla-cli. I need it to report bugs, and I cannot right now. Thanks. Philip can still re-submit newer/rebased version but changing upstream shouldn't be taken lightly, so a separate port is preferred. For now, we don't need unmaintained ports.
Update summary to clarify all changes, assign to committer that resolved.