---
title: APT “Repository changed its Origin value” Error
description: "## Overview During a system update using noid-updater, you may encounter the following error: ``` E: Repository 'file:/media/local_update_repo bookworm InRelease' changed its 'Origin' value from 'Debian' to 'Relianoid' ``` This issue prevents the update process from continuing. ## Cause This…"
url: "https://www.relianoid.com/resources/knowledge-base/troubleshooting/apt-repository-changed-its-origin-value-error/"
updated: "2026-05-05"
category: Troubleshooting
---

# APT “Repository changed its Origin value” Error

## Overview

During a system update using noid-updater, you may encounter the following error:

```
E: Repository 'file:/media/local_update_repo bookworm InRelease' changed its 'Origin' value from 'Debian' to 'Relianoid'
```

This issue prevents the update process from continuing.

## Cause

This behavior is related to a recent metadata change in RELIANOID update repositories.

Specifically, the **repository “Origin” label** has been updated **from Debian to Relianoid**.

This change was introduced to more accurately identify update ISOs generated and maintained by the RELIANOID team, instead of inheriting the default Debian origin label.

However, the APT package manager includes a security mechanism that detects changes in repository metadata (such as Origin, Label, or Suite). When such a change is detected, APT blocks updates until the local cache is refreshed, to prevent potential repository spoofing.

## Solution

To resolve the issue, clear the local APT cache so the system can accept the updated repository metadata.

Run the following command:

```
rm -rf /var/lib/apt/lists/*
```

Then retry the update process:

```
noid-updater
noid-updater -i
```

## Explanation

Removing `/var/lib/apt/lists/*` forces APT to rebuild its local repository metadata so, on the next update attempt, the system will recognize and accept the new **Origin: Relianoid** value. This is a one-time action required after the metadata change.

## Additional Notes

This is an expected behavior and not an error in the update itself. No packages or system integrity are affected. The change improves traceability and clarity of RELIANOID-managed update sources.

### 📄 Download this document in PDF format