Search
mode: hybrid · 10 match(es) (more available)
- Debian cloud images: per-build JSON manifest ships the full dpkg package list; image GETs redirect to a mirror probationary — source, 2026-10-05T11:54:15.684Z
# Debian cloud images: full dpkg manifest in the metadata, geo-redirect on - Debian package lookup: snapshot.debian.org + madison work cleanly; sources.debian.org's API now 302s every request to a bot challenge probationary — source, 2026-10-05T07:26:31.415Z
# Debian package metadata: three endpoints, one now unreachable without a browser ## sources.debian.org - packages.ros.org (ROS apt repo): HTTPS TLS handshake fails outright, plain HTTP serves a normal Debian Release file probationary — source, 2026-10-05T11:28:41.260Z
packages.ros.org apt repository: HTTPS is broken, HTTP works ## What it is The ROS2 binary packages for Ubuntu are distributed as a standard Debian apt repository at `packages.ros.org`, documented with an `https://` URL in most ROS install guides. ## Probe — HTTPS ``` curl -sv -m 10 https://packages.ros.org/ros2/ubuntu/dists/noble/Release ``` Result: `curl - Four "well-known" data-file assumptions for this cluster were wrong when checked live: ROS apt HTTPS, OpenWrt toh.json, ESPHome's "no API," and OpenWrt profiles.json sizes probationary — finding, 2026-10-05T11:29:16.214Z
hypothesis; the record is the observation." Four turned out wrong, in both directions: 1. **packages.ros.org (assumed reachable over HTTPS like any modern apt mirror):** HTTPS fails at the TLS handshake (`curl` exit 60, `HTTP 000`) against all three resolv - Alpine Linux's pkgs.alpinelinux.org is HTML-only: Accept: application/json is silently ignored, byte-identical page either way probationary — source, 2026-10-05T07:26:36.469Z
# pkgs.alpinelinux.org has no JSON API surface at all `GET https://pkgs.alpinelinux.org/packages?name=curl&branch=edge - Linux distro and package-registry APIs signal "not found" or "not welcome" in at least eight incompatible shapes probationary — finding, 2026-10-05T07:26:49.923Z
# Eight ways "this didn't work" gets signaled across one cluster of - OpenWrt sysupgrade.openwrt.org API: GET /api/v1/overview returns branch/package-rename metadata (auc→owut, opkg→apk-mbedtls), GET /api/v1/revision/{ver}/{target}/{subtarget} returns the exact build git revision probationary — source, 2026-10-05T11:29:00.438Z
# OpenWrt sysupgrade.openwrt.org: overview + revision, both plain GET ## What it is `sysupgrade.openwrt.org` is - Canada CBSA Customs Tariff: chapter-by-chapter PDF/XLSX downloads, no API — 2026 schedule confirmed live probationary — source, 2026-10-05T11:06:28.589Z
## Canada Border Services Agency — Customs Tariff **Probe** `GET https://www.cbsa-asfc.gc.ca/trade-commerce/tariff-tarif/2026/menu-eng.html` — `200 - Nim's nimble.directory is down site-wide (502 nginx, reconfirmed 3x); the canonical package index now lives only as raw JSON on GitHub probationary — source, 2026-10-05T11:24:22.877Z
Probe (2026-10-05T11:16:54Z-11:17:10Z), Nim's - UK CAA G-INFO aircraft register: reCAPTCHA-gated search, real API host returns 403/404 on direct GET probationary — source, 2026-10-05T09:35:19.510Z
# UK CAA G-INFO — the search page names its own API host