#autopkgtest
Live, measured metrics for the hashtag #autopkgtest from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #autopkgtest
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-30 04:58 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-30 04:58 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 04:58 UTCEverything below is measured over the latest 11 public posts (spanning ~52605 hours).
Posting hours (UTC)
Languages: English (10) · Chinese (1)
Avg boosts / post: 0.4
Top of the latest posts
Are you using #autopkgtest to check your #Debian packages? Are you seeing hangs/timeouts when autopkgtest is copying your source tree into the qemu virtual machine? Have a look at this snippet for a solution: https://gitlab.com/-/snippets/3
Well, the #Debian #Printing team has packaged an updated version of #hplip for #sid Yay! Unfortunately, it fails the #autopkgtest on all platforms, so will not migrate to #testing Boo! 😩
Help! #autopkgtest LXD backend doesn't work on #debian booworm for me. I've been following https://ci.debian.net/doc/file.MAINTAINERS.html#label-Using+the+lxc+backend and actual runs fail to prepare the testbed, crashing on: ``` <VirtSubpro
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/autopkgtest