nanopub - Debian Package Tracker

general

source: nanopub (main)
version: 0.2.0+ds-1.1
maintainer: Jonas Smedegaard (DMD) (LowNMU)
arch: any
std-ver: 4.7.3
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

testing: 0.2.0+ds-1
unstable: 0.2.0+ds-1.1

versioned links

0.2.0+ds-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.2.0+ds-1.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

nanopub

action needed

Marked for autoremoval on 05 April due to oxigraph, rust-ureq: #1130467, #1130011, #1130511 high

Version 0.2.0+ds-1 of nanopub is marked for autoremoval from testing on Sun 05 Apr 2026. It is affected by #1130467. It depends (transitively) on oxigraph, rust-ureq, affected by #1130011, #1130511. You should try to prevent the removal by fixing these RC bugs.

Created: 2026-03-21 Last update: 2026-03-22 11:02

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2026-03-21 Last update: 2026-03-21 21:32

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2026-03-13 Last update: 2026-03-22 12:00

lintian reports 1 warning normal

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2026-02-26 Last update: 2026-02-26 05:00

testing migrations

excuses:
- Migrates after: rust-getrandom
- Migration status for nanopub (0.2.0+ds-1 to 0.2.0+ds-1.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- ∙ ∙ Missing build on riscv64
- ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
- ∙ ∙ Lintian check waiting for test results on riscv64 - info
- ∙ ∙ Too young, only 0 of 5 days old
- ∙ ∙ Build-Depends(-Arch): nanopub rust-getrandom (not considered)
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanopub.html
- ∙ ∙ Reproducibility check waiting for results on amd64
- ∙ ∙ Reproducibility check waiting for results on arm64
- ∙ ∙ Reproducibility check waiting for results on armhf
- ∙ ∙ Reproducibility check waiting for results on i386
- ∙ ∙ Reproducibility check waiting for results on ppc64el
- Not considered

news

[rss feed]

[2026-03-21] Accepted nanopub 0.2.0+ds-1.1 (source) into unstable (Peter Michael Green)
[2026-03-06] nanopub 0.2.0+ds-1 MIGRATED to testing (Debian testing watch)
[2026-02-25] Accepted nanopub 0.2.0+ds-1 (source) into unstable (Jonas Smedegaard)

bugs [bug history graph]

all: 0

links

homepage
lintian (0, 1)
buildd: logs, reproducibility, cross
popcon
browse source code
edit tags
other distros
debian patches