#1123719 O: bear -- generate compilation database for Clang tooling

Package:
wnpp
Source:
wnpp
Submitter:
Sebastian Ramacher
Date:
2026-09-02 01:11:03 UTC
Severity:
normal
#1123719#5
Date:
2025-12-20 10:16:48 UTC
From:
To:
Package: wnpp
Severity: normal
X-Debbugs-Cc: bear@packages.debian.org, sramacher@debian.org
Control: affects -1 + src:bear

I intend to orphan the bear package.

The package description is:
 Bear records the flags passed to the compiler for each translation unit and
 stores them in a JSON file. This file can be used by Clang's tooling interface
 and programs like clang-check to process a translation unit.
 .
 cmake supports the generation of JSON compilation databases out of the box.
 For any other build system that does not support this, Bear can be used
 instead to intercept the invocation of the compiler.

Cheers
#1123719#12
Date:
2026-02-20 21:59:30 UTC
From:
To:
Hi,
I am  interested in adopting the bear package and maintain it.
I am new to debian packaging, so I would appreciate guidance if any
issues arise.
and I have plan to upload new upstream, fix lintian warning and then
push changes to bear salsa-repository.
It's so much pleasure for me to get me access for salsa repository.
thanks a lot  Sebastian for maintaining bear debian package until now,
bear is very helpful tool for me.

best regards,
Iliya Abolghasemi (gfaerny)
#1123719#21
Date:
2026-07-06 12:34:21 UTC
From:
To:
Hi Iliya,

I'm Bear's upstream maintainer. Thank you for stepping up to adopt the
package - and thank you Sebastian for maintaining it all these years.

One heads-up for planning: the current upstream line (4.x) is a
ground-up rewrite in Rust, so bringing the package up to the latest
version is more than a routine bump - the build system, dependencies,
and install layout all changed since 3.x.

How would you like to approach it? I'm happy to support the packaging
work from the upstream side; tell me what would help. And if anything
in upstream's build or release process creates friction for Debian,
I'd like to hear about it - that feedback is valuable to me.

I'm easy to reach on the GitHub tracker, or by mail.

Cheers,
Laszlo Nagy
#1123719#26
Date:
2026-08-28 10:40:44 UTC
From:
To:
I have decided to step down from adopting the bear package due to the
endless internet connectivity issues in my area.

bear requires an active maintainer, especially given the frequent
upstream changes and versioning updates:

Notes for the new maintainer:

bear has migrated to Rust Cargo. All required build dependencies are
already available in Debian Unstable, except for the serde-saphyr
crate, which in turn depends on the granit-parser crate.

bear
└─ serde-saphyr
     └─ granit-parser

It also requires relaxing the Cargo.toml dependency constraints.

Regards