public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/bear] epel10: Update to 3.1.2 (close RHBZ#2188808)
Date: Sat, 11 Jul 2026 02:31:37 GMT [thread overview]
Message-ID: <178373709723.1.18318071644613385962.rpms-bear-dc20482e8473@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/bear
Branch : epel10
Commit : dc20482e8473a8795cff2dc5abc6211b144bdd65
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2023-04-22T15:14:08-04:00
Stats : +4/-37 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/bear/c/dc20482e8473a8795cff2dc5abc6211b144bdd65?branch=epel10
Log:
Update to 3.1.2 (close RHBZ#2188808)
---
diff --git a/.gitignore b/.gitignore
index 17cd8c8..ad8a172 100644
--- a/.gitignore
+++ b/.gitignore
@@ -20,3 +20,4 @@
/bear-3.0.20.tar.gz
/bear-3.0.21.tar.gz
/bear-3.1.1.tar.gz
+/bear-3.1.2.tar.gz
diff --git a/bear-c99.patch b/bear-c99.patch
deleted file mode 100644
index a6405f6..0000000
--- a/bear-c99.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-Avoid implicit function declarations in tests, for C99 compatibility
-
-Include <stdio.h> for printf and define _GNU_SOURCE for execvpe.
-
-Future compilers will not support implicit function declartions by
-default, causing these tests to fail to build.
-
-Submitted upstream: <https://github.com/rizsotto/Bear/pull/521>
-
-diff --git a/test/cases/intercept/preload/errno_reset.c b/test/cases/intercept/preload/errno_reset.c
-index c9c82bf6ef727864..82821f3ef0564cdb 100644
---- a/test/cases/intercept/preload/errno_reset.c
-+++ b/test/cases/intercept/preload/errno_reset.c
-@@ -5,6 +5,7 @@
- #include <stdlib.h>
- #include <errno.h>
- #include <string.h>
-+#include <stdio.h>
-
- int main()
- {
-diff --git a/test/cases/intercept/preload/posix/execvpe/success.c b/test/cases/intercept/preload/posix/execvpe/success.c
-index 0b4b66d0ce16587e..9017be6cfbcc8e3f 100644
---- a/test/cases/intercept/preload/posix/execvpe/success.c
-+++ b/test/cases/intercept/preload/posix/execvpe/success.c
-@@ -8,6 +8,7 @@
- #include "config.h"
-
- #if defined HAVE_UNISTD_H
-+#define _GNU_SOURCE
- #include <unistd.h>
- #endif
-
diff --git a/bear.spec b/bear.spec
index a89cdee..370ea6c 100644
--- a/bear.spec
+++ b/bear.spec
@@ -1,12 +1,11 @@
Name: bear
-Version: 3.1.1
+Version: 3.1.2
Release: %autorelease
Summary: Tool that generates a compilation database for clang tooling
License: GPL-3.0-or-later
URL: https://github.com/rizsotto/%{name}
Source: %{url}/archive/%{version}/%{name}-%{version}.tar.gz
-Patch0: bear-c99.patch
BuildRequires: cmake
BuildRequires: cmake(fmt)
@@ -41,7 +40,7 @@ how single compilation unit should be processed and can be used by Clang
tooling.
%prep
-%autosetup -p 1 -n Bear-%{version}
+%autosetup -n Bear-%{version}
%build
diff --git a/sources b/sources
index 16ec893..30b1fad 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (bear-3.1.1.tar.gz) = 1380583e8e96833c9932d91dbae0d7cd8f86018ad5c610e8d3c8f9174f7362be3e095ede51e0dd14c0b10b023eb772038588bfdcb52617012299a99fea66a477
+SHA512 (bear-3.1.2.tar.gz) = 02701e8a53b9d776ca838248f5b5d149d7ded6e024ce65bd1ca3b440ab1bf95691dc3d36bb28f043ce24bc1da6e666fb022ff92fa9df7c3142451742de16ca3e
reply other threads:[~2026-07-11 2:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178373709723.1.18318071644613385962.rpms-bear-dc20482e8473@fedoraproject.org \
--to=code@musicinmybrain.net \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox