AUR

archlinux.org · Storage · 2 records · JSON

AUR (Arch User Repository) Storagefails: quotaemail?card?Rper-object-cap
aur Storagefails: quotaemail?card?R

AUR (Arch User Repository) Storage

fails: quotaemail?card?Rper-object-cap

aur.archlinux.org · registry · storage/aur · JSON · compare

Free tier	Not a storage candidate at all: the AUR enforces a hard maximum blob size of 250 KiB per git object. The git hook rejects the push: 'remote: error: maximum blob size (250.00KiB) exceeded / remote: error: hook declined to update refs/heads/master'. Config files around 250.8 KiB already trip it. unit mixed; metered on stored-bytes
Price	none stated
Per-object cap	per-object-cap: 250 KiB (256000 bytes)
Retention	per-object-cap: 250 KiB (hard, server-side git hook). retention: indefinite for packages
Egress	Free (plain git over SSH/HTTPS), but irrelevant given the cap.
Identity	email (placeholder) not published
Limits	per-object-cap per-object-cap: 250 KiB source per-object-cap: 250 KiB (hard, server-side git hook). retention: indefinite for packages. request-rate: git push over ssh, per-key.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	ssh, git, rclone git
Tooling	git over ssh://aur.archlinux.org/<pkg>.git; AUR RPC v5 at /rpc/. No rclone backend (git is the interface).
Composes with	unlimited AUR packages x 250 KiB = useless for bulk. Content must be PKGBUILD + patches; large sources are fetched at build time by URL, never stored.
Reliability	Cleanest possible dead end: a hard 250 KiB blob limit enforced by a git hook. Any 'AUR as storage' idea dies here. Not covered in round 1.
Notes	Not a storage candidate at all: the AUR enforces a hard maximum blob size of 250 KiB per git object. The git hook rejects the push: 'remote: error: maximum blob size (250.00KiB) exceeded / remote: error: hook declined to update refs/heads/master'. Config files around 250.8 KiB already trip it.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 250.0 KiB

Evidence (3)

date	source	what it proved
2026-10-21	bugs.archlinux.org/task/68997	'remote: error: maximum blob size (250.00KiB) exceeded' on a 250.8 KiB config file; maintainer confirms the limit is intentional
2026-10-21	lists.archlinux.org/pipermail/aur-general/2015-August/031470	'[aur-general] max blob size exceeded'
2026-10-21	aur.archlinux.org/rpc/?v=5&type=info&arg=google-chrome	probe: GET -> 200, 679 bytes (RPC v5 live; metadata only, no blob path)

More fields (2)

{
 "unit_note": "free_tier.unit is 'mixed' because the headline is denominated in MiB or KiB, which the schema enum does not carry; the verbatim free_tier.stated keeps the true unit. See the storage-dossier handover.",
 "dead_end": {
  "failure_class": "quota",
  "why": "Not a storage candidate at all: the AUR enforces a hard maximum blob size of 250 KiB per git object. The git hook rejects the push: 'remote: error: maximum blob size (250.00KiB) exceeded / remote: error: hook declined to update refs/heads/master'. Config files around 250.8 KiB already trip it.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (6)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted

aur Storage

fails: quotaemail?card?R

bugs.archlinux.org/task/68997 · rejected-provider · storage/aur-2 · JSON · compare

Free tier	250 KiB hard blob cap enforced by a server-side git hook. Off by three orders of magnitude. unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	250 KiB hard blob cap enforced by a server-side git hook. Off by three orders of magnitude.
Notes	250 KiB hard blob cap enforced by a server-side git hook. Off by three orders of magnitude.
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (1)

date	source	what it proved
2026-10-21	bugs.archlinux.org/task/68997	250 KiB hard blob cap enforced by a server-side git hook. Off by three orders of magnitude.

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "250 KiB hard blob cap enforced by a server-side git hook. Off by three orders of magnitude.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (15)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded