Bug 240185 - editors/jucipp: Update pkg-descr WWW URL (Moved to GitLab)
Summary: editors/jucipp: Update pkg-descr WWW URL (Moved to GitLab)
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Tobias Kortkamp
URL: https://gitlab.com/cppit/jucipp
Keywords: easy, needs-patch
Depends on:
Blocks:
 
Reported: 2019-08-29 06:42 UTC by Graham Perrin
Modified: 2019-08-30 10:52 UTC (History)
2 users (show)

See Also:
info: maintainer-feedback+
koobs: merge-quarterly?


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin freebsd_committer freebsd_triage 2019-08-29 06:42:38 UTC
From <https://github.com/cppit/jucipp#readme:> 

> This project has moved to https://gitlab.com/cppit/jucipp
Comment 1 Walter Schwarzenfeld freebsd_triage 2019-08-29 11:49:26 UTC
(In reply to Graham Perrin from comment #0)
Makefile shows:

USE_GITLAB=     yes
GL_ACCOUNT=     cppit
GL_COMMIT=      ec182761603fa01fe008f09989b99acdf3466096
GL_TUPLE=       cppit:libclangmm:2b2f2ead1f685a9efb28ee2c0ff3cbe452a724dd:libclangmm/lib/libclangmm \
                eidheim:tiny-process-library:54b95a21cf35f8467e21038f523fd3342a77de4c:tinyprocesslibrary/lib/tiny-process-library

or did I misunderstood something?
Comment 2 Mohammad S. Babaei 2019-08-30 10:47:13 UTC
Yes, Graham is right. I did update the Makefile but forgot to update pkg-descr file.

Should I upload a patch here or create another bug report with Maintainer Update in the subject?
Comment 3 commit-hook freebsd_committer freebsd_triage 2019-08-30 10:52:17 UTC
A commit references this bug:

Author: tobik
Date: Fri Aug 30 10:51:37 UTC 2019
New revision: 510259
URL: https://svnweb.freebsd.org/changeset/ports/510259

Log:
  editors/jucipp: Fix WWW

  PR:		240185

Changes:
  head/editors/jucipp/pkg-descr
Comment 4 Tobias Kortkamp freebsd_committer freebsd_triage 2019-08-30 10:52:50 UTC
(In reply to Mohammad S. Babaei from comment #2)
> Should I upload a patch here

Yes, here would have been correct. I just fixed it though.