Releng 2 4 4 #618
Closed
Releng 2 4 4 #618
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit 9138375)
(cherry picked from commit 210cabf)
(cherry picked from commit 3f97362)
(cherry picked from commit de9a211)
(cherry picked from commit f44e7d3)
(cherry picked from commit c1e3f92)
* Add safety belt check for PHP/PHP_pfb versions in pfb_flter.sh service script * Remove all hard links regardless of "Keep settings" on de-installation (cherry picked from commit f7af7bb)
(cherry picked from commit d67c38f)
(cherry picked from commit 3283ee7)
(cherry picked from commit aeb70f1)
(cherry picked from commit eafa69a)
(cherry picked from commit 925b8d1)
(cherry picked from commit 8d72863)
(cherry picked from commit be939e1)
(cherry picked from commit 82e9012)
(cherry picked from commit 683f242)
(cherry picked from commit 7909924)
While here, fix JS that disabled the target field. (cherry picked from commit 358b3bc)
to work around error on systems with larger numbers of network addresses PR: 231800 Submitted by: Franco Fichtner <franco@opnsense.org> (maintainer) (cherry picked from commit 50f9e3a)
(cherry picked from commit 9673644)
This reverts commit fbc28a6.
and add new way to deal with same problem following upstream changes r22478, r2249: - reverse r2246 as it used wrong way to deal with the problem; - make it possible to override results of LCP negotiation and set interface MTU to specified value with a command: set iface mtu NNN override New option "override" is not documented yet. This is dangerous option as it can violate RFC 1661 and should be used with caution and at your own risk. It is useful when you deal with broken PPP peer negotiating too low value while higher MTU is known to work. (cherry picked from commit 67bbe63)
mpd5 successfully compiles with openssl-devel or openssl111 but cannot be linked because it links with base system libfetch(3) that currently links with /usr/lib/libssl.so.8 (openssl 1.0.2p-freebsd). So, one should not attempt to build mpd5 with newer openssl version until it's imported to base system so mpd5 won't link with two distinct openssl versions. PR: 231599 (cherry picked from commit e307b17)
(cherry picked from commit 7d765cc)
(cherry picked from commit f9ff626)
(cherry picked from commit 3a2efbb)
(cherry picked from commit 136024e)
Approved by: portmgr (blanket) (cherry picked from commit 1f6ddd7)
Release notes: * https://blog.rust-lang.org/2018/07/20/Rust-1.27.2.html * https://blog.rust-lang.org/2018/08/02/Rust-1.28.html * https://blog.rust-lang.org/2018/09/13/Rust-1.29.html Up to and including Rust 1.27.x, the Rust build system shelled out to a configure script to detect the presence and usability of libunwind. Since Rust 1.28.0, it's using a static result in a `build.rs` file and expects libunwind to be used. It was not the case on FreeBSD so far, so we need a patch to this `build.rs` to disable that. We still need to study if the FreeBSD port should use libunwind and what to do with this patch. But this problem prevented the update to Rust 1.28.0 already, so enough delay. The update also comes with a patch to a few `USE_GECKO`-based ports such as Firefox [1]. Their configure script has some asumptions on the output of `rustc --print target-list` which are not true anymore. The patch was already committed upstream. The aarch64 version is still marked as BROKEN because I didn't find the time to work on it. As a consequence, there is also no aarch64 bootstrap for Rust 1.29.0. PR: 229826 Approved by: jbeich [1] Obtained from: https://bugzilla.mozilla.org/show_bug.cgi?id=1479540 [1] Differential Revision: https://reviews.freebsd.org/D17178 (cherry picked from commit 1ca2d83)
[ 13%] Building C object src/CMakeFiles/libssh2.dir/channel.c.o /usr/bin/cc -DLIBSSH2_CLEAR_MEMORY -DLIBSSH2_DH_GEX_NEW=1 -DLIBSSH2_HAVE_ZLIB=1 -DLIBSSH2_OPENSSL -I/usr/local/include -Isrc/vendor/libssh2-sys/libssh2/include -Ibuild/x86_64-unknown-freebsd/stage2-tools/x86_64-unknown-freebsd/release/build/libssh2-sys-149db94635ec1367/out/build/src -ffunction-sections -fdata-sections -fPIC -ffunction-sections -fdata-sections -fPIC -m64 -m64 -O3 -DNDEBUG -std=gnu90 -o CMakeFiles/libssh2.dir/channel.c.o -c src/vendor/libssh2-sys/libssh2/src/channel.c src/vendor/libssh2-sys/libssh2/src/channel.c:2262:44: error: use of undeclared identifier 'LIBSSH2_ERROR_CHANNEL_WINDOW_FULL' return _libssh2_error(session, LIBSSH2_ERROR_CHANNEL_WINDOW_FULL, ^ PR: 231411 Reported by: many Obtained from: upstream (libssh2) Approved by: portmgr blanket (cherry picked from commit fdc6841)
- libgit2 in ports is nowadays newer than bundled version - libssh2 was already unbundled until 1.29.0 update - Unbundle libssh2 for USES=cargo (unused atm) PR: 231411 Approved by: rust (dumbbell, tobik) (cherry picked from commit d3cfd07)
- Force rebuild all consumers as standard library is statically linked Changes: https://blog.rust-lang.org/2018/09/25/Rust-1.29.1.html PR: 229826 (follow up) Approved by: dumbbell Differential Revision: https://reviews.freebsd.org/D17337 (cherry picked from commit 8e3d3a7)
PR: 230470 Reported by: Charlie Li <ml+freebsd@vishwin.info> (cherry picked from commit 1f1ae86)
- Force rebuild all consumers in case some are affected by miscompilation Changes: https://blog.rust-lang.org/2018/10/12/Rust-1.29.2.html PR: 229826 (follow up) Approved by: rust (tobik) MFH: 2018Q4 Differential Revision: https://reviews.freebsd.org/D17477 (cherry picked from commit 4070ae2)
- Force rebuild all consumers to catch regressions early Changes: https://blog.rust-lang.org/2018/10/25/Rust-1.30.0.html Approved by: rust (tobik) MFH: 2018Q4 (less rust versions to support) Differential Revision: https://reviews.freebsd.org/D17695 (cherry picked from commit bc056b2)
Release notes: * https://blog.rust-lang.org/2018/11/08/Rust-1.30.1.html (cherry picked from commit 8229cb1)
Approved by: portmgr blanket (cherry picked from commit 1f1ceed)
- devel/racer no longer needs to dowgrade rustc-ap-syntax - Force rebuild all consumers to catch regressions early Changes: https://blog.rust-lang.org/2018/12/06/Rust-1.31.0.html Approved by: rust (tobik) Differential Revision: https://reviews.freebsd.org/D18427 (cherry picked from commit e1b1e02)
(cherry picked from commit 1c17056)
(cherry picked from commit 4791073)
- Simplify .cargo-checksum.json handling [1]. Similar to USES=cargo we disable vendor checksum checking by clearing the list of files in all .cargo-checksum.json, so that cargo does not complain when we patch something. The overall distfile is already checked by us which should be enough. - Add an overridable CARGO_VENDOR_DIR variable to set the crate vendor directory which has moved location in nightly - Add upstream openssl-sys patch to fix build with LibreSSL 2.9.0 [2] Changes: https://blog.rust-lang.org/2018/12/20/Rust-1.31.1.html Submitted by: mikael.urankar@gmail.com [1], ml@vishwin.info [2] Differential Revision: https://reviews.freebsd.org/D18610 (cherry picked from commit 7a49012)
(cherry picked from commit cfa50b2)
(cherry picked from commit 9ac28a2)
(cherry picked from commit 2690f88)
(cherry picked from commit bfa7d95)
(cherry picked from commit 8f6e58b)
(cherry picked from commit 623810f)
* TLS-ALPN support, replaces old TLS-SNI support, binds to a local port (e.g. 443), similar to standalone for HTTP on port 80. If you must use this, bind to an alternate port and forward WAN:443 to the alternate port to avoid a conflict with the GUI web server. * New alternate certificate authority: BuyPass (experimental), to be used instead of Let's Encrypt. This CA has different policies than LE, for example the certificates are valid for 180 days instead of 90, and has a different chain of trust. It still uses the ACME protocol. * New providers * Exoscale * Linode v4 API (split from existing Linode option code) * Various bug fixes from acme.sh upstream. BuyPass support added by https://github.com/mysteq in ports PR pfsense#607 but manually added to this commit instead. (cherry picked from commit d4183e8)
(cherry picked from commit 50a0b43)
(cherry picked from commit 8ad31df)
(cherry picked from commit 447b4f1)
(cherry picked from commit 3ddf24e)
Fix no auto-refresh
netgate-git-updates
pushed a commit
that referenced
this pull request
Jul 1, 2023
Changes since 1.3.0: v1.4.0 This release adds support for Jira v9, a serverinfo command to quickly check your Jira server build info, lets you set resolution, assignee and comment on issue move, and many more. - feat(tui): Allow issue transition from the ui by @ankitpokhrel in #544 - feat(tui): Add help page by @ankitpokhrel in #563 - feat: Filter by multiple statuses by @ankitpokhrel in #573 - feat: Support for adding watcher to Issue by @ankitpokhrel in #584 - feat: Allow different jira server for API and for UI by @markhatch in #613 - fix: Shell completion for Fish and PowerShell by @ankitpokhrel in #553 - fix: Worklog comment don't work together with prompt by @ankitpokhrel in #562 - fix: Use http client wrapper instead of round trip by @ankitpokhrel in #530 - fix: Try to detect if JIRA v8 server is not using the createmeta REST endpoint by @tristianc in #574 - fix: Issue with -c flag on config generation by @ankitpokhrel in #582 - fix: Issue with value assignment in init by @ankitpokhrel in #606 - fix: Issue with epic field on create by @ankitpokhrel in #607 - fix: Comment author name is not always displayed by @ankitpokhrel in (#618) - ehc: Improve PAGER selection by @ankitpokhrel in #570 - dep: Upgrade cobra to v1.7.0 by @dbirks in #608 - ci: Upgrade actions by @ankitpokhrel in #590 - @tristianc made their first contribution in #574 - @dbirks made their first contribution in #608 - @markhatch made their first contribution in #613 Full Changelog: ankitpokhrel/jira-cli@v1.3.0...v1.4.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.