Downgrade from testing to stable

hardware: bare-metal amd64 at home
yunohost: YunoHost 11.1.2 (testing)
ssh access: yes
webadmin: yes
special context: no

since update to yunohost 11 i messed up with testing version and since update yesterday i have issues with showing domains in admin ui.

"400" Bad Request
Aktion: "GET" /yunohost/api/domains/main?locale=de

can i safely downgrade
yunohost Version: 11.1.2 (testing)
yunohost-admin Version: 11.1.2 (testing)
moulinette Version: 11.1.2 (testing)
ssowat Version: 11.1.2 (testing)
to stable and how?

Sorry for the inconvenience. :confused:

Unfortunately no, sorry. You will have to wait for a fix in a subsequent testing release.
Meanwhile you can still administer your domains with the CLI: yunohost domain --help

1 Like

I am currently trying to downgrade to stable, too but it looks like there isn’t a way at the moment.

$ sudo yunohost tools versions
yunohost: 
  repo: testing
  version: 11.1.0.2
yunohost-admin: 
  repo: testing
  version: 11.1.0.2
moulinette: 
  repo: stable
  version: 11.0.9
ssowat: 
  repo: stable
  version: 11.0.9

I looked in and nothing looks out of sorts in /etc/apt/sources.list.d

/etc/apt/sources.list looks like it is on stable.

$ cat sources.list
# 

# deb cdrom:[Debian GNU/Linux 10 _Buster_ - Unofficial amd64 CD Binary-1 20210504-19:05]/ bullseye main non-free

#deb cdrom:[Debian GNU/Linux 10 _Buster_ - Unofficial amd64 CD Binary-1 20210504-19:05]/ bullseye main non-free

deb http://ftp.debian.org/debian bullseye main contrib
deb-src http://ftp.debian.org/debian bullseye main contrib

## YunoHost repository
deb http://forge.yunohost.org/debian/ bullseye stable

deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free

# bullseye-updates, previously known as 'volatile'
deb http://ftp.debian.org/debian bullseye-updates main contrib non-free
deb-src http://ftp.debian.org/debian bullseye-updates main contrib non-free

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

Maybe it is on stable but both stable and testing are the same for now? Seems to be some transition happening since Debian 11 changeover. I think we just need to sit tight for now.

thank u, sit and wait are basically my main skills :smile: but will there a point in future i can revert to stable?

1 Like

Hi @arkadi,

When running yunohost --version, I get an output quite similar to yours:

yunohost: 
  repo: testing
  version: 11.1.0.2
yunohost-admin: 
  repo: testing
  version: 11.1.0.2
moulinette: 
  repo: stable
  version: 11.0.9
ssowat: 
  repo: stable
  version: 11.0.11

Btw. the content of /etc/apt/sources.list also suggests that I am on stable:

deb http://deb.debian.org/debian bullseye main
deb-src http://deb.debian.org/debian bullseye main
deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main
deb http://deb.debian.org/debian bullseye-updates main
deb-src http://deb.debian.org/debian bullseye-updates main
#deb http://deb.debian.org/debian bullseye-backports main
#deb-src http://deb.debian.org/debian bullseye-backports main

as well as the content of /etc/apt/sources.list.d/yunohost.list:

deb http://forge.yunohost.org/debian/ bullseye stable

I have to admit that I am a bit lost with what is set where :grin: I am also wondering if there is a way to put everything back to stable. Following the discussion in Yunohost 11.1 spooky testing, I wonder if a full switch to testing and then a manual change of keyword is the answer. Do you know more than I do or have a resource you could point me towards?

1 Like

Classic confusion, but sources.list strictly speaking doesn’t like wether or not “you are on stable / testing / whatever”

It lists which channels apt will fetch update/upgrades from.

So you can very well have a testing package installed, but only allow upgrades from the stable channel at this very moment

Adding / removing the testing keyword to this file doesnt do anything by itself, it just impacts what the next apt update and apt upgrade will do. And even removing the testing keyword doesnt “downgrade” your system, it just mean you will stop receiving upgrades from the testing channel

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.