Hello! First time posting, feel free to redirect me if necessary.
I am trying to setup Landscape with “quickstart mode” on my Ubuntu Server 26.04 system. The ppa:landscape/latest-stable returns errors 404 as no resolute release can be found.
Are there alternative methods available? Is there a developpement or unstable branch I can use to setup in 26.04?
Thanks!
Hello and welcome
I see things that do not seem right to me. I see this
https;//ppa.launchpadcontent.net/landscape/self-hosted-24.04/ubuntu resolute Inrelease
I also see the same
/landscape/self-hosted-24.04/ ubuntu
In the other error message
The address is wrong. It seems to me. Surely the address should be “self-hosted-26.04”
Perhaps it is too soon to be doing this. Ubuntu developers hold themselves to a rigid time schedule when developing each new version. Often, perhaps always, the release is not finished by release day. This is why we will not be officially invited to do an online upgrade from 24.04 LTS to 26.04 LTS for another six months.
Regards
You could change the resolute to noble, use the 24.04 setup on your 26.04 machine.
The landscape-server doesn’t have to be the same version as the server its hosted on.
24.04 is an LTS release, I would recommend that:
sudo add-apt-repository ppa:landscape/self-hosted-24.04
On my 22.04 VM we have 24.04 installed
cat /etc/apt/sources.list.d/landscape-ubuntu-self-hosted-24_04-jammy.list deb https://ppa.launchpadcontent.net/landscape/self-hosted-24.04/ubuntu/ jammy main
Additionally, the latest-stable is redundant in this case of you already have the self-hosted. You could use it on the clients thou.
To wrap it up, you could get the repos and the package working in the end, but its not in the docs as ready yet so you will eventually run into issues, probably.
(Some of these docs you should take with a grain of salt unfortunately, since for example it states that 24.04 can run on jammy, but we reached 24.04.10-0landscape0 version and can not upgrade beyond it on it 
)
If that is not the complete resolution, you could see it the problem is with the IPv6 stack I see being attempted here.