Your message dated Fri, 25 Sep 2026 15:38:42 +0000
with message-id <[email protected]>
and subject line Re: ITP: golang-github-dgraph-io-badger-v4 -- embeddable,
persistent and fast key-value database in Go
has caused the Debian Bug report #1148678,
regarding ITP: golang-github-dgraph-io-badger-v4 -- embeddable, persistent and
fast key-value database in Go
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1148678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148678
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Juan Manuel Méndez Rey <[email protected]>
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
* Package name : golang-github-dgraph-io-badger-v4
Version : 4.9.6
Upstream Author : Hypermode Inc. <[email protected]>
* URL : https://github.com/hypermodeinc/badger
* License : Apache-2.0, BSD-3-clause
Programming Lang: Go
Description : embeddable, persistent and fast key-value database in Go
BadgerDB is an embeddable, persistent and fast key-value (KV) database written
in pure Go. It is the underlying database for Dgraph, a distributed graph
database. It uses an LSM tree with the values kept in a separate value log,
and supports ACID transactions with serializable snapshot isolation.
This is a rename of the existing badger source package, needed for the Go
team's Module-Aware Build Transition:
https://wiki.debian.org/Teams/DebianGoTeam/ModuleAwareBuilds
Upstream's go.mod has declared "module github.com/dgraph-io/badger/v4" since
4.0, but golang-github-dgraph-io-badger-dev 4.8.0-2, the version in unstable,
installs the library under
/usr/share/gocode/src/github.com/dgraph-io/badger/ with no /v4 suffix. Module
path and install path disagree, so under module-aware builds badger's own
internal github.com/dgraph-io/badger/v4/... imports do not resolve, and no
import-path mapping in a consumer can bridge that.
golang-github-transparency-dev-tessera-dev, which imports
github.com/dgraph-io/badger/v4, hits this as soon as it is ported. The other
reverse dependency, golang-github-smallstep-nosql-dev, imports the unsuffixed
path and github.com/dgraph-io/badger/v2, so it stays with the legacy package.
The migration FAQ says an import path change needs a new source package and a
new ITP, and that legacy -dev packages are to be left untouched, hence this
bug rather than a rename in place. The existing badger source is not modified
and keeps /usr/bin/badger; this source ships the library only, at the path its
go.mod declares, with the -v4-dev suffix lintian asks for
(go-library-package-does-not-include-version). It builds with dh-go.
I ran into this while packaging go-nix (ITP #1148637), a dependency of syft
(ITP #1124819). go-nix's derivation store imports badger/v3, so I patched it
to badger/v4, the version Debian carries; that import then could not resolve,
because the packaged library does not live at its /v4 path. The choice was to
drop two directories from go-nix or to fix the path. go-nix now
build-depends on this package.
I intend to maintain this package inside the Debian Go Packaging Team. Simon
Josefsson, who made the last two uploads of the legacy badger source, is
copied on this bug. Andreas Henriksson is its listed Uploader; both are of
course welcome in Uploaders here.
--- End Message ---
--- Begin Message ---
Closing this: a new source package was the wrong shape, and no ITP is needed.
The team's guidance for a module whose import path gained a major version is
to keep the source name and version only the binary:
https://wiki.debian.org/Teams/DebianGoTeam/ModuleAwareBuilds#Renaming_Legacy_Package
So the work belongs in the existing badger source, which is what I have done in
4.8.0-3: XS-Go-Import-Path set to github.com/dgraph-io/badger/v4 so the library
installs at that path, the library package renamed to
golang-github-dgraph-io-badger-v4-dev with Breaks and Replaces against the old
name, and golang-github-dgraph-io-badger-dev left as a transitional package in
oldlibs. It builds in a clean unstable chroot.
Renaming the source would also have lost the BTS history, and doing it without
Breaks and Replaces is what caused #1148748 in golang-github-cespare-xxhash,
where the two binary packages overwrote each other's files.
Sorry for the noise. I filed this before reading that page.
Cheers,
Juan
--- End Message ---
