17 commits
Author | SHA1 | Message | Date | |
---|---|---|---|---|
wiz
|
6ef8f2b26a |
libgit2: update to 0.28.2.
v0.28.2 ------- This is a bugfix release with the following changes: * Fix include directory ordering when using bundled dependencies. * Fix infinite loop when searching for a non-existing repository with Windows-style paths including drive prefixes. * Fix paths with a trailing "/" not always being treated as directories when computing ignores. * Fix false negatives when computing ignores where ignore rules that are a prefix to a negative ignore rule exist. * Fix patches with CRLF line endings not being parsed correctly. * Fix segfault when parsing patches with file addition (deletion) where the added (deleted) file name contains a space. * Fix assertion failure when trying to write to a non-existent locked configuration file. |
||
wiz
|
9bc820a092 |
libgit2: update to 0.28.1.
v0.28.1 ------- This is a bugfix release with the following change: * The deprecated functions (`git_buf_free` and the `giterr_` family of functions) are now exported properly. In the v0.28 release, they were not given the correct external attributes and they did not have the correct linkage visibility in the v0.28 library. v0.28 ----- ### Changes or improvements * The library is now always built with cdecl calling conventions on Windows; the ability to build a stdcall library has been removed. * Reference log creation now honors `core.logallrefupdates=always`. * Fix some issues with the error-reporting in the OpenSSL backend. * HTTP proxy support is now builtin; libcurl is no longer used to support proxies and is removed as a dependency. * Certificate and credential callbacks can now return `GIT_PASSTHROUGH` to decline to act; libgit2 will behave as if there was no callback set in the first place. * The line-ending filtering logic - when checking out files - has been updated to match newer git (>= git 2.9) for proper interoperability. * Symbolic links are now supported on Windows when `core.symlinks` is set to `true`. * Submodules with names which attempt to perform path traversal now have their configuration ignored. Such names were blindly appended to the `$GIT_DIR/modules` and a malicious name could lead to an attacker writing to an arbitrary location. This matches git's handling of CVE-2018-11235. * Object validation is now performed during tree creation in the `git_index_write_tree_to` API. * Configuration variable may now be specified on the same line as a section header; previously this was erroneously a parser error. * When an HTTP server supports both NTLM and Negotiate authentication mechanisms, we would previously fail to authenticate with any mechanism. * The `GIT_OPT_SET_PACK_MAX_OBJECTS` option can now set the maximum number of objects allowed in a packfile being downloaded; this can help limit the maximum memory used when fetching from an untrusted remote. * Line numbers in diffs loaded from patch files were not being populated; they are now included in the results. * The repository's index is reloaded from disk at the beginning of `git_merge` operations to ensure that it is up-to-date. * Mailmap handling APIs have been introduced, and the new commit APIs `git_commit_committer_with_mailmap` and `git_commit_author_with_mailmap` will use the mailmap to resolve the committer and author information. In addition, blame will use the mailmap given when the `GIT_BLAME_USE_MAILMAP` option. * Ignore handling for files in ignored folders would be ignored. * Worktrees can now be backed by bare repositories. * Trailing spaces are supported in `.gitignore` files, these spaces were previously (and erroneously) treated as part of the pattern. * The library can now be built with mbedTLS support for HTTPS. * The diff status character 'T' will now be presented by the `git_diff_status_char` API for diff entries that change type. * Revision walks previously would sometimes include commits that should have been ignored; this is corrected. * Revision walks are now more efficient when the output is unsorted; we now avoid walking all the way to the beginning of history unnecessarily. * Error-handling around index extension loading has been fixed. We were previously always misreporting a truncated index (#4858). ### API additions * The index may now be iterated atomically using `git_index_iterator`. * Remote objects can now be created with extended options using the `git_remote_create_with_opts` API. * Diff objects can now be applied as changes to the working directory, index or both, emulating the `git apply` command. Additionally, `git_apply_to_tree` can apply those changes to a tree object as a fully in-memory operation. * You can now swap out memory allocators via the `GIT_OPT_SET_ALLOCATOR` option with `git_libgit2_opts()`. * You can now ensure that functions do not discard unwritten changes to the index via the `GIT_OPT_ENABLE_UNSAVED_INDEX_SAFETY` option to `git_libgit2_opts()`. This will cause functions that implicitly re-read the index (eg, `git_checkout`) to fail if you have staged changes to the index but you have not written the index to disk. (Unless the checkout has the FORCE flag specified.) At present, this defaults to off, but we intend to enable this more broadly in the future, as a warning or error. We encourage you to examine your code to ensure that you are not relying on the current behavior that implicitly removes staged changes. * Reference specifications can be parsed from an arbitrary string with the `git_refspec_parse` API. * You can now get the name and path of worktrees using the `git_worktree_name` and `git_worktree_path` APIs, respectively. * The `ref` field has been added to `git_worktree_add_options` to enable the creation of a worktree from a pre-existing branch. * It's now possible to analyze merge relationships between any two references, not just against `HEAD`, using `git_merge_analysis_for_ref`. ### API removals * The `git_buf_free` API is deprecated; it has been renamed to `git_buf_dispose` for consistency. The `git_buf_free` API will be retained for backward compatibility for the foreseeable future. * The `git_otype` enumeration and its members are deprecated and have been renamed for consistency. The `GIT_OBJ_` enumeration values are now prefixed with `GIT_OBJECT_`. The old enumerations and macros will be retained for backward compatibility for the foreseeable future. * Several index-related APIs have been renamed for consistency. The `GIT_IDXENTRY_` enumeration values and macros have been renamed to be prefixed with `GIT_INDEX_ENTRY_`. The `GIT_INDEXCAP` enumeration values are now prefixed with `GIT_INDEX_CAPABILITY_`. The old enumerations and macros will be retained for backward compatibility for the foreseeable future. * The error functions and enumeration values have been renamed for consistency. The `giterr_` functions and values prefix have been renamed to be prefixed with `git_error_`; similarly, the `GITERR_` constants have been renamed to be prefixed with `GIT_ERROR_`. The old enumerations and macros will be retained for backward compatibility for the foreseeable future. ### Breaking API changes * The default checkout strategy changed from `DRY_RUN` to `SAFE` (#4531). * Adding a symlink as .gitmodules into the index from the workdir or checking out such files is not allowed as this can make a Git implementation write outside of the repository and bypass the fsck checks for CVE-2018-11235. |
||
wiz
|
1ba0c9539f |
libgit2: update to 0.27.7.
v0.27.7 ------- This is a bugfix release with the following changes or improvements: - Our continuous integration environment has switched from Travis and AppVeyor to Azure Pipelines CI. - Fix adding worktrees for bare repositories. - Fix parsed patches not computing the old respectively new line numbers correctly. - Fix parsing configuration variables which do not have a section. - Fix a zero-byte allocation when trying to detect file renames and copies of a diff without any hunks. - Fix a zero-byte allocation when trying to resize or duplicate vectors. - Fix return value when trying to unlock worktrees which aren't locked. - Fix returning an unitialized error code when preparing a revision walk without any pushed commits. - Fix return value of `git_remote_lookup` when lookup of "remote.$remote.tagopt" fails. - Fix the revision walk always labelling commits as interesting due to a mishandling of the commit date. - Fix the packbuilder inserting uninteresting blobs when adding a tree containing references to such blobs. - Ignore unsupported authentication schemes in HTTP transport. - Improve performane of `git_remote_prune`. - Fix detection of whether `qsort_r` has a BSD or GNU function signature. - Fix detection of iconv if it is provided by libc. v0.27.6 ------- This as a security release fixing the following list of issues: - The function family `git__strtol` is used to parse integers from a buffer. As the functions do not take a buffer length as argument, they will scan either until the end of the current number or until a NUL byte is encountered. Many callers have been misusing the function and called it on potentially non-NUL-terminated buffers, resulting in possible out-of-bounds reads. Callers have been fixed to use `git__strntol` functions instead and `git__strtol` functions were removed. - The function `git__strntol64` relied on the undefined behavior of signed integer overflows. While the code tried to detect such overflows after they have happened, this is unspecified behavior and may lead to weird behavior on uncommon platforms. - In the case where `git__strntol32` was unable to parse an integer because it doesn't fit into an `int32_t`, it printed an error message containing the string that is currently being parsed. The code didn't truncate the string though, which caused it to print the complete string until a NUL byte is encountered and not only the currently parsed number. In case where the string was not NUL terminated, this could have lead to an out-of-bounds read. - When parsing tags, all unknown fields that appear before the tag message are skipped. This skipping is done by using a plain `strstr(buffer, "\n\n")` to search for the two newlines that separate tag fields from tag message. As it is not possible to supply a buffer length to `strstr`, this call may skip over the buffer's end and thus result in an out of bounds read. As `strstr` may return a pointer that is out of bounds, the following computation of `buffer_end - buffer` will overflow and result in an allocation of an invalid length. Note that when reading objects from the object database, we make sure to always NUL terminate them, making the use of `strstr` safe. - When parsing the "encoding" field of a commit, we may perform an out of bounds read due to using `git__prefixcmp` instead of `git__prefixncmp`. This can result in the parsed commit object containing uninitialized data in both its message encoding and message fields. Note that when reading objects from the object database, we make sure to always NUL terminate them, making the use of `strstr` safe. |
||
taca
|
1885ba2f02 |
devel/libgit2: update to 0.27.5
libgit2 0.27.5 (2018/10/5) This is a security release fixing the following list of issues: * Submodule URLs and paths with a leading "-" are now ignored. This is due to the recently discovered CVE-2018-17456, which can lead to arbitrary code execution in upstream git. While libgit2 itself is not vulnerable, it can be used to inject options in an implementation which performs a recursive clone by executing an external command. * When running repack while doing repo writes, packfile_load__cb() could see some temporary files in the directory that were bigger than the usual, and makes memcmp overflow on the p->pack_name string. This issue was reported and fixed by bisho. * The configuration file parser used unbounded recursion to parse multiline variables, which could lead to a stack overflow. The issue was reported by the oss-fuzz project, issue 10048 and fixed by Nelson Elhage. * The fix to the unbounded recursion introduced a memory leak in the config parser. While this leak was never in a public release, the oss-fuzz project reported this as issue 10127. The fix was implemented by Nelson Elhage and Patrick Steinhardt. * When parsing "ok" packets received via the smart protocol, our parsing code did not correctly verify the bounds of the packets, which could result in a heap-buffer overflow. The issue was reported by the oss-fuzz project, issue 9749 and fixed by Patrick Steinhardt. * The parsing code for the smart protocol has been tightened in general, fixing heap-buffer overflows when parsing the packet type as well as for "ACK" and "unpack" packets. The issue was discovered and fixed by Patrick Steinhardt. * Fixed potential integer overflows on platforms with 16 bit integers when parsing packets for the smart protocol. The issue was discovered and fixed by Patrick Steinhardt. * Fixed potential NULL pointer dereference when parsing configuration files which have "include.path" or "includeIf..path" statements without a value. |
||
taca
|
c1ec19f6d0 |
devel/libgit2: update to 0.27.4
v0.27.4 ------- This is a security release fixing out-of-bounds reads when processing smart-protocol "ng" packets. When parsing an "ng" packet, we keep track of both the current position as well as the remaining length of the packet itself. But instead of taking care not to exceed the length, we pass the current pointer's position to `strchr`, which will search for a certain character until hitting NUL. It is thus possible to create a crafted packet which doesn't contain a NUL byte to trigger an out-of-bounds read. The issue was discovered by the oss-fuzz project, issue 9406. v0.27.3 ------- This is a security release fixing out-of-bounds reads when reading objects from a packfile. This corresponds to CVE-2018-10887 and CVE-2018-10888, which were both reported by Riccardo Schirone. When packing objects into a single so-called packfile, objects may not get stored as complete copies but instead as deltas against another object "base". A specially crafted delta object could trigger an integer overflow and thus bypass our input validation, which may result in copying memory before or after the base object into the final deflated object. This may lead to objects containing copies of system memory being written into the object database. As the hash of those objects cannot be easily controlled by the attacker, it is unlikely that any of those objects will be valid and referenced by the commit graph. Note that the error could also be triggered by the function `git_apply__patch`. But as this function is not in use outside of our test suite, it is not a possible attack vector. |
||
wiz
|
1421b09816 |
libgit2: update to 0.27.1.
v0.27.1 --------- This is a security release fixing insufficient validation of submodule names (CVE-2018-11235, reported by Etienne Stalmans) and disallows `.gitmodules` files as symlinks. While submodule names come from the untrusted ".gitmodules" file, we blindly append the name to "$GIT_DIR/modules" to construct the final path of the submodule repository. In case the name contains e.g. "../", an adversary would be able to escape your repository and write data at arbitrary paths. In accordance with git, we now enforce some rules for submodule names which will cause libgit2 to ignore these malicious names. Adding a symlink as `.gitmodules` into the index from the workdir or checking out such files is not allowed as this can make a Git implementation write outside of the repository and bypass the `fsck` checks for CVE-2018-11235. libgit2 is not susceptible to CVE-2018-11233. |
||
wiz
|
f4a0350636 |
libgit2: update to 0.27.0.
v0.27 --------- ### Changes or improvements * Improved `p_unlink` in `posix_w32.c` to try and make a file writable before sleeping in the retry loop to prevent unnecessary calls to sleep. * The CMake build infrastructure has been improved to speed up building time. * A new CMake option "-DUSE_HTTPS=<backend>" makes it possible to explicitly choose an HTTP backend. * A new CMake option "-DSHA1_BACKEND=<backend>" makes it possible to explicitly choose an SHA1 backend. The collision-detecting backend is now the default. * A new CMake option "-DUSE_BUNDLED_ZLIB" makes it possible to explicitly use the bundled zlib library. * A new CMake option "-DENABLE_REPRODUCIBLE_BUILDS" makes it possible to generate a reproducible static archive. This requires support from your toolchain. * The minimum required CMake version has been bumped to 2.8.11. * Writing to a configuration file now preserves the case of the key given by the caller for the case-insensitive portions of the key (existing sections are used even if they don't match). * We now support conditional includes in configuration files. * Fix for handling re-reading of configuration files with includes. * Fix for reading patches which contain exact renames only. * Fix for reading patches with whitespace in the compared files' paths. * We will now fill `FETCH_HEAD` from all passed refspecs instead of overwriting with the last one. * There is a new diff option, `GIT_DIFF_INDENT_HEURISTIC` which activates a heuristic which takes into account whitespace and indentation in order to produce better diffs when dealing with ambiguous diff hunks. * Fix for pattern-based ignore rules where files ignored by a rule cannot be un-ignored by another rule. * Sockets opened by libgit2 are now being closed on exec(3) if the platform supports it. * Fix for peeling annotated tags from packed-refs files. * Fix reading huge loose objects from the object database. * Fix files not being treated as modified when only the file mode has changed. * We now explicitly reject adding submodules to the index via `git_index_add_frombuffer`. * Fix handling of `GIT_DIFF_FIND_RENAMES_FROM_REWRITES` raising `SIGABRT` when one file has been deleted and another file has been rewritten. * Fix for WinHTTP not properly handling NTLM and Negotiate challenges. * When using SSH-based transports, we now repeatedly ask for the passphrase to decrypt the private key in case a wrong passphrase is being provided. * When generating conflict markers, they will now use the same line endings as the rest of the file. ### API additions * The `git_merge_file_options` structure now contains a new setting, `marker_size`. This allows users to set the size of markers that delineate the sides of merged files in the output conflict file. By default this is 7 (`GIT_MERGE_CONFLICT_MARKER_SIZE`), which produces output markers like `<<<<<<<` and `>>>>>>>`. * `git_remote_create_detached()` creates a remote that is not associated to any repository (and does not apply configuration like 'insteadof' rules). This is mostly useful for e.g. emulating `git ls-remote` behavior. * `git_diff_patchid()` lets you generate patch IDs for diffs. * `git_status_options` now has an additional field `baseline` to allow creating status lists against different trees. * New family of functions to allow creating notes for a specific notes commit instead of for a notes reference. * New family of functions to allow parsing message trailers. This API is still experimental and may change in future releases. ### API removals ### Breaking API changes * Signatures now distinguish between +0000 and -0000 UTC offsets. * The certificate check callback in the WinHTTP transport will now receive the `message_cb_payload` instead of the `cred_acquire_payload`. * We are now reading symlinked directories under .git/refs. * We now refuse creating branches named "HEAD". * We now refuse reading and writing all-zero object IDs into the object database. * We now read the effective user's configuration file instead of the real user's configuration in case libgit2 runs as part of a setuid binary. * The `git_odb_open_rstream` function and its `readstream` callback in the `git_odb_backend` interface have changed their signatures to allow providing the object's size and type to the caller. |
||
ryoon
|
2666aac03a |
Update to 0.26.3
* Fix some security bugs Changelog: 0.26.3 This is a bugfix release. It includes the following non-exclusive list of improvements, which have been backported from the master branch: Fix cloning of the libgit2 project with git clone --recursive by removing an invalid submodule from our testing data. Fix endianness of the port in p_getaddrinfo(). Fix handling of negative gitignore rules with wildcards. Fix handling of case-insensitive negative gitignore rules. Fix resolving references to a tag if the reference is stored with its fully resolved OID in the packed-refs file. Fix checkout not treating worktree files as modified when only their mode has changed. Fix rename detection with GIT_DIFF_FIND_RENAMES_FROM_REWRITES. Enable Windows 7 and earlier to use TLS 1.2. 0.26.2 This is a security release fixing memory handling issues when reading crafted repository index files. The issues allow for possible denial of service due to allocation of large memory and out-of-bound reads. As the index is never transferred via the network, exploitation requires an attacker to have access to the local repository. 0.26.1 This is a security release that includes an update to the bundled zlib to update it to 1.2.11. Users who build the bundled zlib are vulnerable to security issues in the prior version. This does not affect you if you rely on a system-installed version of zlib. All users of v0.26.0 who use the bundled zlib should upgrade to this release. |
||
taca
|
4fca0d1d95 |
Update libgit2 to 0.26.0.
libgit2 2017/6/19 This is the first release of the v0.26 series, "Aufschub". The changelog follows. Changes or improvements Support for opening, creating and modifying worktrees. We can now detect SHA1 collisions resulting from the SHAttered attack. These checks can be enabled at build time via -DUSE_SHA1DC. Fix for missing implementation of git_merge_driver_source getters. Fix for installed pkg-config file being broken when the prefix contains spaces. We now detect when the hashsum of on-disk objects does not match their expected hashsum. We now support open-ended ranges (e.g. "master..", "...master") in our revision range parsing code. We now correctly compute ignores with leading "/" in subdirectories. We now optionally call fsync on loose objects, packfiles and their indexes, loose references and packed reference files. We can now build against OpenSSL v1.1 and against LibreSSL. GIT_MERGE_OPTIONS_INIT now includes a setting to perform rename detection. This aligns this structure with the default by git_merge and git_merge_trees when NULL was provided for the options. Improvements for reading index v4 files. Perform additional retries for filesystem operations on Windows when files are temporarily locked by other processes. API additions New family of functions to handle worktrees: git_worktree_list() lets you look up worktrees for a repository. git_worktree_lookup() lets you get a specific worktree. git_worktree_open_from_repository() lets you get the associated worktree of a repository. git_worktree_add lets you create new worktrees. git_worktree_prune lets you remove worktrees from disk. git_worktree_lock() and git_worktree_unlock() let you lock and unlock a worktree, respectively. git_repository_open_from_worktree() lets you open a repository via git_repository_head_for_worktree() lets you get the current HEAD for a linked worktree. git_repository_head_detached_for_worktree() lets you check whether a linked worktree is in detached HEAD mode. git_repository_item_path() lets you retrieve paths for various repository files. git_repository_commondir() lets you retrieve the common directory of a repository. git_branch_is_checked_out() allows you to check whether a branch is checked out in a repository or any of its worktrees. git_repository_submodule_cache_all() and git_repository_submodule_cache_clear() functions allow you to prime or clear the submodule cache of a repository. You can disable strict hash verifications via the GIT_OPT_ENABLE_STRICT_HASH_VERIFICATION option with git_libgit2_opts(). You can enable us calling fsync for various files inside the ".git" directory by setting the GIT_OPT_ENABLE_FSYNC_GITDIR option with git_libgit2_opts(). You can now enable "offset deltas" when creating packfiles and negotiating packfiles with a remote server by setting GIT_OPT_ENABLE_OFS_DELTA option with GIT_libgit2_opts(). You can now set the default share mode on Windows for opening files using GIT_OPT_SET_WINDOWS_SHAREMODE option with git_libgit2_opts(). You can query the current share mode with GIT_OPT_GET_WINDOWS_SHAREMODE. git_transport_smart_proxy_options() enables you to get the proxy options for smart transports. The GIT_FILTER_INIT macro and the git_filter_init function are provided to initialize a git_filter structure. Breaking API changes clone_checkout_strategy has been removed from git_submodule_update_option. The checkout strategy used to clone will be the same strategy specified in checkout_opts. |
||
taca
|
f2f698b5f2 |
Update libgit2 to 0.25.1, it includes security problem.
For full changes, please refer CHANGESLOG.md file. * libgit2 v0.24.6 and libgit2 v0.25.1, January 9th, 2017 Includes two fixes, one performs extra sanitization for some edge cases in the Git Smart Protocol which can lead to attempting to parse outside of the buffer. The second fix affects the certificate check callback. It provides a valid parameter to indicate whether the native cryptographic library considered the certificate to be correct. This parameter is always 1/true before these releases leading to a possible MITM. This does not affect you if you do not use the custom certificate callback or if you do not take this value into account. This does affect you if you use pygit2 or git2go regardless of whether you specify a certificate check callback. |
||
jperkin
|
5fbe506561 |
Update libgit2 to 0.24.1.
pkgsrc changes: - re-enable libssh2 support - ensure pkgsrc curl and http-parser are picked up and enabled Upstream changes: 2f2575c Updating http parser to accept a `+` in the schema ff8e3f0 Handle git+ssh:// and ssh+git:// protocols support fa8b1a8 Adding spec coverage for ssh+git and git+ssh protocols 429155d Updating change to http_parser to reflect PR for nodejs/http-parser e44f658 Removing #define for SSH_PREFIX_COUNT and using ARRAY_SIZE instead b8dc15f Adding test cases that actually test the functionality of the new transport 4a93a7f Tabs 8ec3d88 Avoid subtraction overflow in git_indexer_commit e3862c9 Buffer sideband packet data cdded63 Remove duplicated calls to git_mwindow_close eb09ead odb: improved not found error messages 9ee498e Only buffer if necessary. 4ebf745 mwindow: free unused windows if we fail to mmap ffb1f41 describe: handle error code returned by git_pqueue_insert e39ad74 config_file: handle missing quotation marks in section header 0370dae Check for __CLANG_INTTYPES_H faf823d tests: transport: fix memory leaks with registering transports fa4b93a backport git_oid__cpy_prefix d0780b8 object: avoid call of memset with ouf of bounds pointer e114bba index: assert required OID are non-NULL |
||
taca
|
dc376aaaa1 |
Update libgit2 to 0.24.0.
v0.24 ------- ### Changes or improvements * Custom filters can now be registered with wildcard attributes, for example `filter=*`. Consumers should examine the attributes parameter of the `check` function for details. * Symlinks are now followed when locking a file, which can be necessary when multiple worktrees share a base repository. * You can now set your own user-agent to be sent for HTTP requests by using the `GIT_OPT_SET_USER_AGENT` with `git_libgit2_opts()`. * You can set custom HTTP header fields to be sent along with requests by passing them in the fetch and push options. * Tree objects are now assumed to be sorted. If a tree is not correctly formed, it will give bad results. This is the git approach and cuts a significant amount of time when reading the trees. * Filter registration is now protected against concurrent registration. * Filenames which are not valid on Windows in an index no longer cause to fail to parse it on that OS. * Rebases can now be performed purely in-memory, without touching the repository's workdir. * When adding objects to the index, or when creating new tree or commit objects, the inputs are validated to ensure that the dependent objects exist and are of the correct type. This object validation can be disabled with the GIT_OPT_ENABLE_STRICT_OBJECT_CREATION option. * The WinHTTP transport's handling of bad credentials now behaves like the others, asking for credentials again. ### API additions * `git_config_lock()` has been added, which allow for transactional/atomic complex updates to the configuration, removing the opportunity for concurrent operations and not committing any changes until the unlock. * `git_diff_options` added a new callback `progress_cb` to report on the progress of the diff as files are being compared. The documentation of the existing callback `notify_cb` was updated to reflect that it only gets called when new deltas are added to the diff. * `git_fetch_options` and `git_push_options` have gained a `custom_headers` field to set the extra HTTP header fields to send. * `git_stream_register_tls()` lets you register a callback to be used as the constructor for a TLS stream instead of the libgit2 built-in one. * `git_commit_header_field()` allows you to look up a specific header field in a commit. * `git_commit_extract_signature()` extracts the signature from a commit and gives you both the signature and the signed data so you can verify it. ### API removals * No APIs were removed in this version. ### Breaking API changes * The `git_merge_tree_flag_t` is now `git_merge_flag_t`. Subsequently, its members are no longer prefixed with `GIT_MERGE_TREE_FLAG` but are now prefixed with `GIT_MERGE_FLAG`, and the `tree_flags` field of the `git_merge_options` structure is now named `flags`. * The `git_merge_file_flags_t` enum is now `git_merge_file_flag_t` for consistency with other enum type names. * `git_cert` descendent types now have a proper `parent` member * It is the responsibility of the refdb backend to decide what to do with the reflog on ref deletion. The file-based backend must delete it, a database-backed one may wish to archive it. * `git_config_backend` has gained two entries. `lock` and `unlock` with which to implement the transactional/atomic semantics for the configuration backend. * `git_index_add` and `git_index_conflict_add()` will now use the case as provided by the caller on case insensitive systems. Previous versions would keep the case as it existed in the index. This does not affect the higher-level `git_index_add_bypath` or `git_index_add_frombuffer` functions. * The `notify_payload` field of `git_diff_options` was renamed to `payload` to reflect that it's also the payload for the new progress callback. * The `git_config_level_t` enum has gained a higher-priority value `GIT_CONFIG_LEVEL_PROGRAMDATA` which represent a rough Windows equivalent to the system level configuration. * `git_rebase_init()` not also takes a merge options. * The index no longer performs locking itself. This is not something users of the library should have been relying on as it's not part of the concurrency guarantees. |
||
agc
|
d9e4cfe05d |
Add SHA512 digests for distfiles for devel category
Issues found with existing distfiles: distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip distfiles/fortran-utils-1.1.tar.gz distfiles/ivykis-0.39.tar.gz distfiles/enum-1.11.tar.gz distfiles/pvs-3.2-libraries.tgz distfiles/pvs-3.2-linux.tgz distfiles/pvs-3.2-solaris.tgz distfiles/pvs-3.2-system.tgz No changes made to these distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail. |
||
fhajny
|
dec55c1aaa |
Update devel/libgit2 to 0.23.3.
Simplify Github distfile handling. Backport a futimes fix from upstream master, fixes build on SunOS. Changes since 0.23.2: - blame: guard xdiff calls for large files - diff: don't feed large files to xdiff - merge_file: treat large files as binary - xdiff: convert size variables to size_t - GITERR_CHECK_ALLOC_ADDn: multi-arg adders |
||
taca
|
3ec6587052 |
Update libgit2 to 0.23.2.
Changes are too many to write here, please refer: <https://github.com/libgit2/libgit2/releases>. |
||
taca
|
194ed7a72f |
Update libgit2 to 0.22.2 required by ruby-rugged.
libgit2 v0.22.2 Maintenance Release @carlosmn carlosmn released this on 25 Mar 12 commits to maint/v0.22 since this release The following fixes have been backported to this maintenance release. All users of the library are encouraged to update. 1f25fe9 checkout: report correct invalid path 8633dd9 win32: further cleanups for 8.3 disabling 93be89c win32: cleanup 8.3 disabled tests 728a013 Fix test failures when 8.3 is disabled 1f726d0 git: make sure to close the network stream 3e163b6 checkout: free last created directory 3440c20 Initialize refs vector in git_remote_update_tips(). dcf6c0c Lower case the include directive of windows header 1dd5e28 http: do not try to use the cert callback on unencrypted streams dd243fe indexer: set an error message on duplicate objects in pack 3a1dc42 Put back the number of expected references to 6 from the test repo cf688ff Fixed active refspecs not reset by git_remote_upload() |
||
fhajny
|
27663956d8 |
Import devel/libgit2 based on wip/libgit2.
libgit2 is a portable, pure C implementation of the Git core methods provided as a re-entrant linkable library with a solid API, allowing you to write native speed custom Git applications in any language which supports C bindings. |