Ports transitioned to git.

PSA. VM is good. Just run a virtual machine, and test different scenarios. I'm doing the same; right now.
At the moment, I have 11 VMs and all are still on SVN mood! I have an extra VM to test Git for different
scenarios. Plus there's 2 bare-metal FreeBSD Desktop machines, too. I won't migrate unless I get it right.
 
1. Can't reproduce on my 14-CURRENT, that's built just one week before yours. net/gitup runs fine here. Might try again after a git pull and rebuild, strongly expect exactly the same result.

2. When using -CURRENT, you should really be aware of a few things. Problems with undefined symbols are mostly caused by linking against different library versions than the ones present when trying to run the program. You should be prepared to recompile all your ports every time you upgrade base. Yes, there are binary packages for -CURRENT, they will only work when you keep your -CURRENT up to date all the time – it changes often, as expected in a development branch.

Not a bug with the transition, however if gitup is to be formally popularised when the transition completes, it'll make sense for the port to work as expected in non-RELEASE environments.
I specifically don't think so. Running -CURRENT is for testing and development, so it probably makes a lot of sense to actually use devel/git on these machines.

Nevertheless, nothing "broken" here.
 
So what is the url for the gits quarterly?

I had prepped a scripted with information from here https://github.com/bsdimp/freebsd-git-docs/blob/main/URLs.md

Instead of using those for the transition I see there is no 2021Q2 branch, the head has no updates since end of march and the above url is now 404.

Where has this information been communicated?

It seems odd as there was already a quarterly branch in place and I assumed it would just be a transition to it at end of march.

grahamperrin https://cgit.freebsd.org/ports/ has no updates since end of march and no current quarterly branch it seems its not been used now.
 
I'm not sure. Seems like it would be a good idea. chrcol, looking at my /usr/local/etc/gitup.conf, I have this for quarterly, but don't know if it is correct. Mostly I use packages, the only port I build is dwm because I use a custom config file, and so far, I've been using portsnap and probably will till it's gone. Anyway, from my gitup.conf, and this is quarterly's default, because I haven't edited anything but the release section of the file
Code:
"quarterly" : {
                "host"       : "github.com",
                "repository" : "/freebsd/freebsd-ports.git",
                "branch"     : "quarterly",
                "target"     : "/usr/ports",
                "ignores"    : [
                        "distfiles",
                        "packages",
 
Thanks. I ran gitup ports -v 2 for maximum verbosity, imagined that it was stuck because there was nothing (not a word) for a few minutes.

Eventually:

Code:
root@mowa219-gjp4-8570p:~ # gitup ports -v 2
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
GET /freebsd/freebsd-ports.git/info/refs?service=git-upload-pack HTTP/1.1
Host: github.com:443
User-Agent: gitup/0.90
Git-Protocol: version=2



==> bytes sent: 148
==> bytes read: 537     bytes_expected: 565     total_bytes_read: 570
001e# service=git-upload-pack
0000000eversion 2
0023agent=git/github-gacb49e25c7ae
000cls-refs
0019fetch=shallow filter
0012server-option
0017object-format=sha1
0000

POST /freebsd/freebsd-ports.git/git-upload-pack HTTP/1.1
Host: github.com:443
User-Agent: gitup/0.90
Accept-encoding: deflate, gzip
Content-type: application/x-git-upload-pack-request
Accept: application/x-git-upload-pack-result
Git-Protocol: version=2
Content-length: 178

0014command=ls-refs
0022agent=git/github-gacb49e25c7ae0016object-format=sha100010009peel
000csymrefs
0014ref-prefix HEAD
001bref-prefix refs/heads/
001aref-prefix refs/tags/
0000

==> bytes sent: 461
==> bytes read: 573     bytes_expected: 2365    total_bytes_read: 2370
00504010f7bbc03638d71781ce091bf40a0907fa12fe HEAD symref-target:refs/heads/main
003f5f4d6e1d6b07bb34e5cbf866b4ef81e8ccdcb2da refs/heads/2014Q1
003fa3377806e58e030668a0406a35c434394a9333e1 refs/heads/2014Q2
003fa0ccd6f83108ca7e16e64b6fd690dacefc5d0d58 refs/heads/2014Q3
003fce9f5d32567600a981517b7e35b2542a1114ece0 refs/heads/2014Q4
003f5bd325869bdeccff8037a64e2089b799abe798e0 refs/heads/2015Q1
003f7d7c2271f6c957574221e8746e5a356435cd114f refs/heads/2015Q2
003fa69940fb27f798fd49cfecb02cac3785412b76d0 refs/heads/2015Q3
003f38269ac51865d5d9bbaa23f6afcc2e6a6db5e9b1 refs/heads/2015Q4
003f847fef4d2acd28d745c9fe57194624dafc02e927 refs/heads/2016Q1
003f859c6d655ba8ec51549be3d8f52a302e7023d4ad refs/heads/2016Q2
003fdbe3dbb507e6a2068dee12ee7844edc3797e7dea refs/heads/2016Q3
003fe113cbca02fc10dfb61a77d9c547550718cc7190 refs/heads/2016Q4
003f995d6409b4234b211b27bd14989a9c467f4d4b1a refs/heads/2017Q1
003fee7b50bc8addebc46b27f99488b0f2c3a2ef6b94 refs/heads/2017Q2
003fa16d9e9f97932862f4433c03ee35493ec26fd29d refs/heads/2017Q3
003ff204b02d6dcefb91393ebeac39b3b6741b9ae5b1 refs/heads/2017Q4
003f8e67d346991ca584ffbe6ad23380c597e10d0ddf refs/heads/2018Q1
003f06d6d83e775282797de36344c649a2c33a70861d refs/heads/2018Q2
003f20f7d7640bc5014692574a4e09a7191dc021ecce refs/heads/2018Q3
003f6948b132a446b2a84e021a6dd26b5ac7ea8e575a refs/heads/2018Q4
003fd2f5722e633ae238daba15792d4949b15d22c174 refs/heads/2019Q1
003fab797ee3a93f4bb4a3b22900257b9cbd91349887 refs/heads/2019Q2
003fd5d60820925216fc48c025190e0c30a79f52bf3b refs/heads/2019Q3
003ff24745656dbbc619a6ee0360a5cababea241813c refs/heads/2019Q4
003f28b4da349ddcc9e8493e8c3d013eb2fc4107098a refs/heads/2020Q1
003f22e399d695717c14566f60255c72aae4c8c3d08c refs/heads/2020Q2
003fc0d44897151cceb0c4e63f2f7763b030f3019b66 refs/heads/2020Q3
003fc9104cb760e6d462d2e0a768cbbf0d95968012fa refs/heads/2020Q4
003f1b85cb72f7defaa7d2fba7c39a48841996a4ec5c refs/heads/2021Q1
003d4010f7bbc03638d71781ce091bf40a0907fa12fe refs/heads/main
0000

gitup: get_commit_details: refs/heads/master doesn't exist in /freebsd/freebsd-ports.git: Invalid argument
root@mowa219-gjp4-8570p:~ #

Things are not yet ready for the forward-looking change that I suggested at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254760#c0 but I guess that I should (at least) change the default to reflect the non-existence of master.
 
Check your gitup config. See what the server offers:
00504010f7bbc03638d71781ce091bf40a0907fa12fe HEAD symref-target:refs/heads/main
vs what you're requesting:
gitup: get_commit_details: refs/heads/master doesn't exist […]

Obviously, there's no branch named "master" and the default branch is named "main". This seems to be a new default on Github, for "reasons"…

Or, just use the official repo on git.freebsd.org instead of the Github mirror.
 
… the default branch is named "main". …
Yep, fixed a couple of days ago: https://lists.freebsd.org/pipermail/freebsd-git/2021-April/000849.html

Here, there was a wait of around ten minutes before the first line of output:

Code:
root@mowa219-gjp4-8570p:~ # time gitup ports -v 1
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
# Want: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Branch: main
# Action: clone
 * /usr/ports/CHANGES
…
 * /usr/ports/x11/zenity/Makefile
 - /usr/ports/.portsnap.INDEX
 - /usr/ports/INDEX-14
 - /usr/ports/net/gitup/dialog4ports.core
 - /usr/ports/net/gitup/work
…
 - /usr/ports/net/gitup/work/stage/usr/local/www
10.079u 8.477s 10:50.11 2.8%    49+357k 106059+109255io 0pf+0w
root@mowa219-gjp4-8570p:~ #

I imagine things becoming faster after https://git.freebsd.org/ports.git begins to redirect.
 
Completely unrelated and different issue.

Here, there was a wait of around ten minutes before the first line of output:
Output suggests it did a "clone". This is expected to take considerable time, given a repository that large. It should be a lot faster for consecutive runs, doing "pull" instead.

"Fishy" things in your output: A portsnap Index? a coredump from dialog4ports? a workdir from building gitup? Looks like you tried it on an existing ports tree. Initial "clone" might be faster on a clean directory.

I imagine things becoming faster after https://git.freebsd.org/ports.git begins to redirect.
Redirect what? From your output, I can see gitup is configured to use the mirror on Github, not the official repo on git.freebsd.org.
 
… Redirect what? From your output, I can see gitup is configured to use the mirror on Github, not the official repo on git.freebsd.org.
Configured to use a GitHub URL because https://git.freebsd.org/ports.git is still 404, not found (no surprise, during the transition).

… use the official repo on git.freebsd.org instead of the Github mirror.
https://git.freebsd.org/docs.git redirects to https://cgit.freebsd.org/doc where https://git.FreeBSD.org/doc.git is the primary non-developer address for cloning. I ignore non-working links such as (public-mirror).

https://git.freebsd.org/src.git redirects to https://cgit.freebsd.org/src where https://git.FreeBSD.org/src.git is the primary non-developer address for cloning.

As the transition progresses, I expect https://git.freebsd.org/ports.git to begin redirecting to https://cgit.freebsd.org/ports
 
… on a clean directory. …

Code:
root@mowa219-gjp4-8570p:~ # time rm -r /usr/ports/*
0.574u 7.715s 2:52.24 4.8%      9+161k 14098+0io 0pf+0w
root@mowa219-gjp4-8570p:~ # rm -r /usr/ports/.git*
root@mowa219-gjp4-8570p:~ # ls -adhl /usr/ports/.*
drwxr-xr-x   2 root  wheel     3B Apr  6 02:51 /usr/ports/.
drwxr-xr-x  17 root  wheel    17B Jan  3 07:57 /usr/ports/..
-rw-r--r--   1 root  wheel   115B Nov 23 04:40 /usr/ports/.arcconfig
root@mowa219-gjp4-8570p:~ # cat /usr/ports/.arcconfig
{
        "repository.callsign" : "P",
        "phabricator.uri" : "https://reviews.freebsd.org/",
        "history.immutable" : true
}
root@mowa219-gjp4-8570p:~ # rm /usr/ports/.arcconfig
root@mowa219-gjp4-8570p:~ # time gitup ports
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
# Have: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Want: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Branch: main
! /usr/ports/.arcconfig is missing.
! /usr/ports/.gitattributes is missing.
! /usr/ports/.gitauthors is missing.
! /usr/ports/.gitignore is missing.
! /usr/ports/.gitmessage is missing.
! /usr/ports/CHANGES is missing.
…
! /usr/ports/x11/zenity/pkg-plist is missing.
gitup: build_repair_command: There are too many files to repair -- please re-clone the repository: Argument list too long
0.663u 0.195s 0:05.18 16.4%     51+169k 108+0io 0pf+0w
root@mowa219-gjp4-8570p:~ # time gitup ports -c
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
# Have: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Want: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Branch: main
0.388u 0.166s 0:01.05 51.4%     51+168k 1+1io 0pf+0w
root@mowa219-gjp4-8570p:~ # df -h /usr/ports
Filesystem              Size    Used   Avail Capacity  Mounted on
copperbowl/usr/ports    190G    104K    190G     0%    /usr/ports
root@mowa219-gjp4-8570p:~ # time gitup ports -c
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
# Have: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Want: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Branch: main
0.429u 0.127s 0:00.98 55.1%     50+166k 0+1io 0pf+0w
root@mowa219-gjp4-8570p:~ # df -h /usr/ports
Filesystem              Size    Used   Avail Capacity  Mounted on
copperbowl/usr/ports    190G    104K    190G     0%    /usr/ports
root@mowa219-gjp4-8570p:~ # time rm -r /usr/ports/*
rm: No match.
0.000u 0.000s 0:00.00 0.0%      0+0k 0+0io 0pf+0w
root@mowa219-gjp4-8570p:~ # rm -r /usr/ports/.git*
root@mowa219-gjp4-8570p:~ # ls -adhl /usr/ports/.*
drwxr-xr-x   2 root  wheel     2B Apr  6 02:58 /usr/ports/.
drwxr-xr-x  17 root  wheel    17B Jan  3 07:57 /usr/ports/..
root@mowa219-gjp4-8570p:~ # time gitup ports -c
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
# Have: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Want: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Branch: main
0.415u 0.127s 0:01.22 43.4%     50+166k 0+1io 0pf+0w
root@mowa219-gjp4-8570p:~ #
 
… worked around by removing /usr/ports/.gituprevision and the database for gitup(1), after which an initial run of gitup ports with an empty /usr/ports/ completed relatively quickly.

The second run took much longer. Timed:
6.873u 11.903s 36:15.25 0.8% 50+165k 141126+1io 0pf+0w
– I'm not complaining. YMMV, depending on hardware, time of day and so on.

Code:
root@mowa219-gjp4-8570p:~ # ls -hl /var/db/gitup
total 9725
-rw-r--r--  1 root  wheel    13M Apr  5 20:42 ports
root@mowa219-gjp4-8570p:~ # rm /var/db/gitup/ports
root@mowa219-gjp4-8570p:~ # ls -adhl /usr/ports/.*
drwxr-xr-x   2 root  wheel     3B Apr  6 02:59 /usr/ports/.
drwxr-xr-x  17 root  wheel    17B Jan  3 07:57 /usr/ports/..
-rw-r--r--   1 root  wheel    14B Apr  6 02:59 /usr/ports/.gituprevision
root@mowa219-gjp4-8570p:~ # rm /usr/ports/.gituprevision
root@mowa219-gjp4-8570p:~ # time gitup ports
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
# Want: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Branch: main
# Action: clone
 + /usr/ports/.arcconfig
 + /usr/ports/.gitattributes
 + /usr/ports/.gitauthors
 + /usr/ports/.gitignore
 + /usr/ports/.gitmessage
 + /usr/ports/CHANGES
…
 + /usr/ports/x11/zenity/pkg-plist
6.593u 13.397s 2:02.72 16.2%    49+3329k 761+217601io 0pf+0w
root@mowa219-gjp4-8570p:~ # df -h /usr/ports
Filesystem              Size    Used   Avail Capacity  Mounted on
copperbowl/usr/ports    190G    670M    190G     0%    /usr/ports
root@mowa219-gjp4-8570p:~ # time gitup ports
load: 0.32  cmd: gitup 9088 [zio->io_cv] 995.65r 2.95u 4.57s 0% 280632k
mi_switch+0xc1 sleepq_timedwait+0x2f _cv_timedwait_sbt+0x107 zio_wait+0x2f9 dmu_buf_hold_array_by_dnode+0x29d dmu_read_uio_dnode+0x3a dmu_read_uio_dbuf+0x3b zfs_read+0x1da zfs_freebsd_read+0x44 VOP_READ_APV+0x1f vn_read+0x1ed vn_io_fault_doio+0x43 vn_io_fault1+0x15c vn_io_fault+0x1a4 dofileread+0x81 sys_read+0xbc amd64_syscall+0x10c fast_syscall_common+0xf8
load: 0.43  cmd: gitup 9088 [zio->io_cv] 1213.15r 3.31u 5.26s 0% 280648k
mi_switch+0xc1 sleepq_timedwait+0x2f _cv_timedwait_sbt+0x107 zio_wait+0x2f9 dmu_buf_hold_array_by_dnode+0x29d dmu_read_uio_dnode+0x3a dmu_read_uio_dbuf+0x3b zfs_read+0x1da zfs_freebsd_read+0x44 VOP_READ_APV+0x1f vn_read+0x1ed vn_io_fault_doio+0x43 vn_io_fault1+0x15c vn_io_fault+0x1a4 dofileread+0x81 sys_read+0xbc amd64_syscall+0x10c fast_syscall_common+0xf8
load: 0.30  cmd: gitup 9088 [zio->io_cv] 1979.81r 5.19u 9.06s 0% 325832k
mi_switch+0xc1 sleepq_timedwait+0x2f _cv_timedwait_sbt+0x107 zio_wait+0x2f9 dmu_buf_hold_array_by_dnode+0x29d dmu_read_uio_dnode+0x3a dmu_read_uio_dbuf+0x3b zfs_read+0x1da zfs_freebsd_read+0x44 VOP_READ_APV+0x1f vn_read+0x1ed vn_io_fault_doio+0x43 vn_io_fault1+0x15c vn_io_fault+0x1a4 dofileread+0x81 sys_read+0xbc amd64_syscall+0x10c fast_syscall_common+0xf8
# Host: github.com
# Port: 443
# Repository: /freebsd/freebsd-ports.git
# Target: /usr/ports
# Have: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Want: 4010f7bbc03638d71781ce091bf40a0907fa12fe
# Branch: main
6.873u 11.903s 36:15.25 0.8%    50+165k 141126+1io 0pf+0w
root@mowa219-gjp4-8570p:~ #
 
… second run took much longer. Timed:
6.873u 11.903s 36:15.25 0.8% 50+165k 141126+1io 0pf+0w
– I'm not complaining. YMMV, depending on hardware, time of day and so on. …

Third run of gitup ports: quicker. Around thirteen minutes:
5.910u 8.047s 12:38.38 1.8% 50+166k 143029+1io 0pf+0w

In due course, when things are complete (I shouldn't treat https://wiki.freebsd.org/git#Ports_Schedule as fully comprehensive) I'll test with https://git.freebsd.org/ports.git instead of GitHub. For my use case:
  • I don't expect a significant difference in speed from a change of source
  • I do expect git(1) and portsnap(8) to be faster than gitup(1).
 
The transision is complete, there are already a few commits updating ports. I'm right now cloning the ports tree on my builder machine…
Code:
builder# git clone https://git.freebsd.org/ports.git .
Cloning into '.'...
remote: Enumerating objects: 991, done.
remote: Counting objects: 100% (991/991), done.
remote: Compressing objects: 100% (175/175), done.
Receiving objects:  55% (2710986/4907881), 468.39 MiB | 6.63 MiB/s

What's missing from the schedule is just getting the sync to mirrors (like Gitup) up and running again.

edit: Done, and I love it – finally some structure for my local changes on top of origin/HEAD:
Code:
706ae52ff248 (HEAD -> local) security/stunnel: downgrade to 5.48
aa07aaa1ce22 emulators/virtualbox-ose: fix build with libressl
17bec063cb3e sysutils/gkrellm2: fix build with libressl
8dd6367e86c1 www/chromium: fix build with MIT krb5
cf44ad3f0ed7 sysutils/pam_mount: fix build with libressl
3858ab6b0b10 security/openvpn: fix build with libressl
a465c8a99ee4 graphics/gtkam: fix dependency
f8229dc6cc57 add micropolis-fbsd
868ae2421595 add spindle
b602ce4d15ea add exomizer2
7162fcf86480 add mkd64
05017885ce98 (origin/main, origin/HEAD, main) devel/awscli: Update 1.19.36 -> 1.19.44
 
Again: No. Pushing to mirrors is nothing "gitup" would need. Just configure the official repository, it's there, it's actively used, updates coming in pretty fast right now*. If you have an old config, use this one instead: https://github.com/johnmehr/gitup/blob/main/gitup.conf

---
* that's the log since commits are possible (only two hours so far):
Code:
848355ff18d2 graphics/mesa-devel: update to 21.0.b.4158
1e8c41d07054 emulators/citra: update to s20210403
a67b6931f198 emulators/yuzu: update to s20210404
6ce48c1cfb86 emulators/rpcs3: update to 0.0.15.12048
60a8b261e7f6 x11-servers/xwayland-devel: update to 1.20.0.886
4c47c324b2d7 www/py-flask-restx: update to 0.3.0
ad7765865cfe www/gallery-dl: update to 1.17.2
f2aa5c86adf0 www/youtube_dl: update to 2021.04.01
72f7b59ccdc8 x11/wezterm: update to 20210405.110924.a5.b5.b8
0751da285384 devel/rust-bindgen: update to 0.58.0
5a89dd6e7c23 devel/cargo-c: update to 0.8.0
4cc8ae097fc4 multimedia/mpv: update to 0.33.1
f8732455e4bb multimedia/rav1e: update to 0.4.1
cc87022694a6 graphics/libplacebo: update to 3.120.0
0f984aa02a5b lang/intel-compute-runtime: update to 21.13.19438
6cc47c27a695 multimedia/libva-utils: update to 2.11.1
ea90aab81688 multimedia/intel-media-sdk: update to 21.1.3
09d06e7228aa multimedia/libva-intel-media-driver: update to 21.1.3
8c16874b817f multimedia/gmmlib: update to 21.1.1
d34abcb3e18f devel/git-cinnabar: update to 0.5.7
f59286f56314 x11-wm/sway: unbreak fetch
722e4c5e303e x11-toolkits/wlroots: unbreak fetch
5254fca65db2 Chase GH_ACCOUNT rename for Greg V
1f090b794c9b audio/ardour6: drop bsd.port.pre.mk
021faaac0be6 audio/ardour6: unbreak on aarch64
f990e2b38bff devel/cargo-c: drop libgit2 < 1.1 workaround after e7d94d42f82e
b1a2d52166ab Document gitlab-ce vulnerabilities.
1532b5be3796 devel/rust-analyzer: Update to 2021-04-05
9b79896e8f15 Major upgrade to 13.10 which includes security related upgrade to 13.10.1. Changelog: https://about.gitlab.com/releases/2021/03/22/gitlab-13-10-released/ https://about.gitlab.com/releases/2021/03/31/security-release-gitlab-13-10-1-released/
c0b6ad5b5016 Update to 13.10.1 which is required for gitlab-ce 13.10.
c2acab3b6bbe Update to 1.36.0 which is required for gitlab-ce 13.10.
46c5af56a39e Update to 16.10.7 which is required for gitlab-ce 13.10.
462dbbcdec08 Update to 16.11.7 which is required for gitlab-ce 13.10. Changelog: https://github.com/chef/chef/blob/master/RELEASE_NOTES.md
6bb00d2ad2d0 Fix dependencies to work with chef upgrade.
d0407b2937ab Update to 16.11.7. This update is required for a security related update of gitlab-ce to 13.10.1. PR:              254548
0b4d6a9a3de1 Update to 1.1.0 which is required for gitlab-ce 13.10.
4d8acc04bf20 Update to 1.7.1 which is required for gitlab-ce 13.10.
43dfa5f733d1 Update to 1.0.1 which is required for gitlab-ce 13.10.
8702c15bcb25 Update to 3.9.0. This update is required for a security update of www/gitlab-ce.
5c0415a6535d Update to 0.3.10. This update is required for a security related upgrade of gitlab-ce.
42d771f692bb Update to 0.0.9 which is required for gitlab-ce 13.10.
9f48b4070467 Update to 1.6.0 which is required for gitlab-ce 13.10.
11be3d86f769 Update to 1.11.8 which is required for gitlab-ce 13.10.
68e3cf9815ff Update to 0.5.5 which is required for gitlab-ce 13.10.
6c5e5b3b7c8f Update to 1.3.1 which is required for gitlab-ce 13.10.
8c8badcc0838 Update to 0.16.2 which is required for gitlab-ce 13.10.
3fba248f462e Update to 0.5.1 which is required for gitlab-ce 13.10.
4376e187f101 Update to 13.10.1 which is required for gitlab-ce 13.10.
b6ed29de5bba Added new port which is required for gitlab-ce 13.10.
e7d94d42f82e Update libgit2 to 1.1.0. This update is also required for www/gitlab-ce 13.10 upgrade.
634a88402a52 Update to Version 4.0.0
6bf14cb7b01b devel/awscli: Update 1.19.44 -> 1.19.45
2b488206169f devel/py-botocore: Update 1.20.44 -> 1.20.45
11b77b717cb1 security/openssl-unsafe: Unbreak with FreeBSD 13
05017885ce98 devel/awscli: Update 1.19.36 -> 1.19.44
3ba3a94c3578 devel/py-botocore: Update 1.20.36 -> 1.20.44
dda06a776cea www/node: Update 15.12.0 -> 15.13.0
a26284996496 www/node12: Update 12.21.0 -> 12.22.0
8c7fa30e3e42 www/node10: Mark as deprecated and set expiration date
c8481a0e21c4 net/py-python-socks: Update to 1.2.4
785f39d86108 editors/emacs-devel: Update to 2021-04-05 commit, 0342354
b9ad876d99f0 devel/py-Js2Py: update to 0.71
a663968e406b audio/fasttracker2: Update to 1.46
ed8d3eda309d Mark the repository has been converted to Git
 
Back
Top