Commit message will be:
New ports required for gitlab update to 10.5.x.
Reviewed by: tz/swills (mentor)
Approved by: tz/swills (mentor)
Differential Revision: URL to this revision
Differential D14840
New ports required for gitlab upgrade to 10.5.x mfechner on Mar 25 2018, 7:04 AM. Authored by Tags None Referenced Files
Subscribers
Details
Commit message will be: Reviewed by: tz/swills (mentor) All patches are build, you can find all build logs: The fresh packages are tested against a new installation using: An old version is updated following the manual:
Diff Detail
Event TimelineComment Actions Since its not possible to see it in the git diffs: It looks like you didn't since security/rubygem-doorkeeper-openid_connect for example exists as 1.2.0 in the tree. You should perform: 455061 is the revision where the port had the required version: The svn syntax means, that it should copy the dir security/rubygem-doorkeeper-openid_connect with the content of revision 455061 into security/rubygem-doorkeeper-openid_connect12. This way the ports share one history and its very easy to track them. Comment Actions What I did was (e.g. for port security/rubygem-doorkeeper-openid_connect12): and then updated the files in the new directory. I also removed and changed some lines that porlint -ACN is fine. Is this ok? Comment Actions No, it misses the '@rev' part, which makes your life much easier. Also it makes history clear. Comment Actions Executed now the following steps: svn copy databases/rubygem-pg@414136 databases/rubygem-pg018 Added the new ports to the ../Makefile. Next step would be then to do a "svn commit". Comment Actions
Next step is to update the review ;) Than i can have a look and approve
Comment Actions Should I undo the TIMESTAMP modification? I prepared the diffs long time ago I had access to SVN. |