Bug 248689

Summary: devel/libconfuse: Use the correct github account name
Product: Ports & Packages Reporter: Juraj Lutter <otis>
Component: Individual Port(s)Assignee: Fernando Apesteguía <fernape>
Status: Closed FIXED    
Severity: Affects Only Me CC: fernape, meta
Priority: --- Keywords: buildisok
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
devel/libconfuse: Update GH_ACCOUNT
otis: maintainer-approval+
devel/libconfuse: Update GH_ACCOUNT otis: maintainer-approval+

Description Juraj Lutter freebsd_committer freebsd_triage 2020-08-16 13:55:38 UTC
Created attachment 217258 [details]
devel/libconfuse: Update GH_ACCOUNT

Hi,

please find the patch attached.

No functional change, only a GH_ACCOUNT update.
Comment 1 Automation User 2020-08-16 14:06:39 UTC
Build info is available at https://gitlab.com/swills/freebsd-ports/pipelines/178413847
Comment 2 Koichiro Iwao freebsd_committer freebsd_triage 2020-08-17 02:08:48 UTC
Did you intentionally remove "TEST_TARGET=	check" ?
Comment 3 Juraj Lutter freebsd_committer freebsd_triage 2020-08-17 06:10:09 UTC
Created attachment 217271 [details]
devel/libconfuse: Update GH_ACCOUNT
Comment 4 Juraj Lutter freebsd_committer freebsd_triage 2020-08-17 06:10:54 UTC
(In reply to Koichiro Iwao from comment #2)
You are right, it was an erroneous diff.
Comment 5 commit-hook freebsd_committer freebsd_triage 2020-08-21 16:43:47 UTC
A commit references this bug:

Author: fernape
Date: Fri Aug 21 16:43:10 UTC 2020
New revision: 545615
URL: https://svnweb.freebsd.org/changeset/ports/545615

Log:
  devel/libconfuse: Use the correct github account name

  Bump PORTREVISION.

  PR:	248689
  Submitted by:	juraj@lutter.sk (maintainer)

Changes:
  head/devel/libconfuse/Makefile
  head/devel/libconfuse/distinfo
Comment 6 Fernando Apesteguía freebsd_committer freebsd_triage 2020-08-21 16:44:22 UTC
Committed,

Bumping PORTREVISION

Thanks!
Comment 7 Juraj Lutter freebsd_committer freebsd_triage 2020-08-21 16:46:57 UTC
Was there a need for bumping PORTREVISION? There were no functional changes. I'm asking because I probably am missing something.
Comment 8 Fernando Apesteguía freebsd_committer freebsd_triage 2020-08-21 16:52:41 UTC
(In reply to Juraj Lutter from comment #7)
Ummm, I think you're right. We could have lived without it.