[unstable channel] 1.2.0~rc.1 deb release asset unavailability

[yermulnik]

Cross-posting #38 for visibility:

> cat /etc/apt/sources.list.d/kunobi.list
deb [signed-by=/usr/share/keyrings/kunobi-archive-keyring.gpg arch=amd64] https://r2.kunobi.ninja/apt unstable main

> apt list --upgradable
Listing... Done
kunobi/unknown 1.2.0~rc.1 amd64 [upgradable from: 1.1.0-beta.1]
N: There is 1 additional version. Please use the '-a' switch to see it

> apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  kunobi
1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Need to get 31,6 MB of archives.
After this operation, 73,6 MB disk space will be freed.
Do you want to continue? [Y/n]
Err:1 https://r2.kunobi.ninja/apt unstable/main amd64 kunobi amd64 1.2.0~rc.1
  404  Not Found [IP: 104.21.5.90 443]
E: Failed to fetch https://r2.kunobi.ninja/apt/pool/main/k/kunobi/kunobi_1.2.0%7erc.1_amd64.deb  404  Not Found [IP: 104.21.5.90 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

👉🏻 stable channel is fine though.

[jleni]

@emmanuelm41 maybe you know?

[emmanuelm41]

@yermulnik thanks for the detailed report — you're right that this traces back to before our fix for pre-release publishing on the unstable channel.

What happened: 1.2.0~rc.1 was the first pre-release to go through some reworked packaging logic, and during that transition the channel's package list ended up advertising a build that wasn't actually available to download — hence the 404. Stable was never affected.

This has since been corrected, and the unstable channel is serving valid builds again. A quick apt update should clear the stale
entry. Sorry for the friction, and thanks for flagging it!

[yermulnik]

Thanks for update 👍🏻