This bug was fixed in the package landscape-client -
23.02-0ubuntu1~22.04.2
---
landscape-client (23.02-0ubuntu1~22.04.2) jammy; urgency=medium
* d/p/0001-start-service-during-config.patch: fix landscape-config does not
start landscape-client service (LP: #2040189)
*
This bug was fixed in the package landscape-client -
23.02-0ubuntu1~20.04.2
---
landscape-client (23.02-0ubuntu1~20.04.2) focal; urgency=medium
* d/p/0001-start-service-during-config.patch: fix landscape-config does not
start landscape-client service (LP: #2040189)
*
I've performed validation on jammy using version 23.02-0ubuntu1~22.04.2,
following the tests and test procedures laid out in
https://wiki.canonical.com/Landscape/ClientSRUTests/23.02 and
https://wiki.ubuntu.com/LandscapeUpdates.
** Tags removed: verification-needed verification-needed-jammy
**
I've performed validation on focal using version 23.02-0ubuntu1~20.04.2,
following the tests and test procedures laid out in
https://wiki.canonical.com/Landscape/ClientSRUTests/23.02 and
https://wiki.ubuntu.com/LandscapeUpdates.
Still working on the same for jammy.
** Tags removed:
Hello Mitch, or anyone else affected,
Accepted landscape-client into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/23.02-0ubuntu1~22.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this
The server repos are currently the correct ones. I've talked to the
Landscape team in the past about having a separate client repo, but so
far that hasn't made progress.
ppa:landscape/self-hosted-23.03 or ppa:landscape/self-hosted-23.10
should work
--
You received this bug notification because
What is the correct PPA to have the newest landscape clients until this
is fixed?
I found ppa:landscape/production which is very outdated, and
ppa:landscape/trunk which does have version 23.10 but it seems odd that
a customer needs to use "trunk" and not "production". Also I was
avoiding pointing
