mail/rubygem-gitlab-mail_room: update to 1.1.0 Required for gitlab 19.2.0 Changes: https://github.com/tpitale/mail_room/commits/master/b359f7737f
Port details
mail/rubygem-gitlab-mail_room 1.1.0
Proxy email (gmail) from IMAP to a delivery method
Port info
- Maintainer
- mfechner@FreeBSD.org
- Packages
- latest: 1.1.0
- Upstream
- up to date
- Last update
- to 1.1.0 · b359f7737f
- Quarterly
- 2026Q4: 1.1.0
- WWW
- https://gitlab.com/gitlab-org/ruby/gems/gitlab-mail_room
- Links
- cgit · VuXML
Install
- Package
# pkg install rubygem-gitlab-mail_roominstalls 1.1.0 fromlatest; fromquarterly(2026Q4) 1.1.0- Port
# cd /usr/ports/mail/rubygem-gitlab-mail_room && make install clean- Size
- 40 KiB download · 144 KiB installed
- Depends on
- databases/rubygem-redis-gitlab 5.4.1, databases/rubygem-redis-namespace-gitlab 1.10.0, devel/ruby-gems 4.0.21, lang/ruby34 3.4.9_2,1, mail/rubygem-net-imap-gitlab 0.6.4.1, net/rubygem-oauth2-gitlab 2.0.25, www/rubygem-jwt 3.3.0
- License
- MIT
Packages by version and architecture
latest
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 16 | 1.1.0 | 1.1.0 | – |
| FreeBSD 15 | 1.1.0 | 1.1.0 | – |
| FreeBSD 14 | 1.1.0 | 1.1.0 | 1.1.0 |
quarterly (2026Q4)
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 15 | 1.1.0 | 1.1.0 | – |
| FreeBSD 14 | 1.1.0 | 1.1.0 | 1.1.0 |
version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by
pkg audit for the packaged version 1.1.0.Fixed (0)
No VuXML entries for this package.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (28)
www/gitlab: security and patch update to 19.0.2 Changes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-2-released/ Security: ac9bab80-6618-11f1-8e04-2cf05da270f31eb6e89618
mail/rubygem-gitlab-mail_room: update to 1.0.0 Required for gitlab 18.10 Changes: https://github.com/tpitale/mail_room/commits/master/8fd8065d4f
mail/rubygem-gitlab-mail_room: update to 0.1.0 Required for gitlab 18.9 Changes: https://github.com/tpitale/mail_room/commits/master/9b48d9c7d7
www/gitlab: security and bugfix update to 18.3.5 Changes: https://about.gitlab.com/releases/2025/10/22/patch-release-gitlab-18-5-1-released/ Security: f741ea93-af61-11f0-98b5-2cf05da270f39b4801f0c2
mail/rubygem-gitlab-mail_room: update to 0.27.0 Changes: https://github.com/tpitale/mail_room/commits/master/7c75619979
mail/rubygem-gitlab-mail_room: update to 0.0.25 Changes: https://gitlab.com/gitlab-org/ruby/gems/gitlab-mail_room/-/tagsa1ba20871d
www/gitlab: fix regression from 335fc7c38d61142727cb9f01fd9e401c476e4ad8 Gitlab requires net-http 0.4.1: Because faraday >= 2, < 2.5 could not be found in locally installed gems and faraday >= 2.5, < 2.12.1 could not be found in locally installed gems, faraday >= 2, < 2.12.1 cannot be used. And because faraday >= 2.12.1 depends on faraday-net_http >= 2.0, < 3.5, faraday >= 2 requires faraday-net_http >= 2.0, < 3.5. Because faraday-net_http >= 3.4.0 depends on net-http >= 0.5.0 and faraday-net_http >= 2.0, < 3.4.0 could not be found in locally installed gems, faraday-net_http >= 2.0 requires net-http >= 0.5.0. Thus, faraday >= 2 requires net-http >= 0.5.0. So, because Gemfile depends on faraday ~> 2 and Gemfile depends on net-http = 0.4.1, version solving has failed. While fixing the problem, moved gitlab used packages to own package names with a PKGNAMESUFFIX of `-gitlab`. This should make the gitlab package much more stable if updates in the ports are done.edc8d0390e
mail/rubygem-gitlab-mail_room: update to 0.0.24 Required for gitlab-ce 16.7 Changelog: https://github.com/tpitale/mail_room/commits/master/66e0ca0db9
mail/rubygem-gitlab-mail_room: update to 0.0.23 Required for gitlab-ce 15.11.6d7898fbfc
devel/ruby-gems: Update to 3.4.2 ChangeLog: https://github.com/rubygems/rubygems/releases/tag/v3.4.2 PR: 268578 Approved by: meta (ruby@, maintainer) Exp-run by: antoinef03ab0f785
Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby
Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk
Notable changes are.
- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.
This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863
I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D3792518c6e18276Remove WWW entries moved into port Makefiles Commit b7f05445c00f has added WWW entries to port Makefiles based on WWW: lines in pkg-descr files. This commit removes the WWW: lines of moved-over URLs from these pkg-descr files. Approved by: portmgr (tcberner)fb16dfecae
Add WWW entries to port Makefiles It has been common practice to have one or more URLs at the end of the ports' pkg-descr files, one per line and prefixed with "WWW:". These URLs should point at a project website or other relevant resources. Access to these URLs required processing of the pkg-descr files, and they have often become stale over time. If more than one such URL was present in a pkg-descr file, only the first one was tarnsfered into the port INDEX, but for many ports only the last line did contain the port specific URL to further information. There have been several proposals to make a project URL available as a macro in the ports' Makefiles, over time. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)b7f05445c0
mail/rubygem-gitlab-mail_room: update to 0.0.20 Required for gitlab-ce 15.20a870680bc
mail/rubygem-gitlab-mail_room: Change RUN_DEPENDS from rubygem-oauth2 to rubygem-oauth21 - Bump PORTREVISION for dependency changeceda95b9f3
mail/rubygem-gitlab-mail_room: update to 0.0.1961fde59ea1
mail/rubygem-gitlab-mail_room: Update to 0.0.12.9a6035a726
One more small cleanup, forgotten yesterday. Reported by: lwhsucf118ccf87
Remove # $FreeBSD$ from Makefiles.305f148f48
Removed svn keywords again. They went in by accident while merging older commits. Reported by: jbeich1b802f473e
Update to 0.0.9 which is required for gitlab-ce 13.10.42d771f692
Update to 0.0.8 which is required for gitlab 13.7.e2b10e9cd2
Update to 0.0.7 which is required for gitlab-ce 13.5.d595bc6dd7
Update to 0.0.6 which is required for gitlab-ce 13.1.1.3f67902b51
Update mail/rubygem-gitlab-mail_room to 0.0.4.3108515225
Sanitize COMMENT per Section 5.6 of the FreeBSD Porter's Handbook (part 5).a7d9790791
New ports required for gitlab-ce 12.9 upgrade.0bb7fbeada