ubiquity

~didrocks/ubiquity:ad-sssd-gpo

  1. Git
  2. lp:~didrocks/ubiquity
  3. ad-sssd-gpo
Last commit made on 2021-03-12
Get this branch:
git clone -b ad-sssd-gpo https://git.launchpad.net/~didrocks/ubiquity
Only Didier Roche-Tolomelli can upload to this branch. If you are Didier Roche-Tolomelli please log in for upload directions.

Branch merges

Branch information

Name:
ad-sssd-gpo
Repository:
lp:~didrocks/ubiquity

Recent commits

296af1a... by Didier Roche-Tolomelli

Configure Kerberos for AD installations

Configure krb5 client so access to AD with GPO enabled works out of the
box after installation.

c801ceb... by Didier Roche-Tolomelli

Keep packages required for AD installed.

When AD installation is selected we want to keep all the packages used
to make it work and remove them otherwise.

fda7d70... by Łukasz Zemczak

Forward-port change from 20.04.2 so that we have the same baseline.

edc8d5b... by Steve Langasek

releasing package ubiquity version 21.04.10

d321a6d... by Steve Langasek

Drop build-dependency on obsolete dh-systemd

86e8145... by Dimitri John Ledkov

Add casper-md5check.json integration.

ae6415d... by Dimitri John Ledkov

releasing package ubiquity version 21.04.9

00f5b8a... by Iain Lane

check-kernels: Don't remove the oem kernel if we want it

The OEM kernel is never auto selected. We install it if the system to be
installed on requires it, as ultimately is communicated to us by its
oem-...-meta metapackage.

There's a codepath in check-kernels to try to install the OEM kernel in
this situation, but it doesn't account for the fact that the rest of the
code - where the kernel is automatically detected - will consider the
OEM kernel to be incompatible with the target system.

What we need to do is, if we want the OEM kernel, make sure not to
remove it from the system we're installing to. Technically that means
remove it from the "$incompatible" list.

LP: #1915114

78974b3... by Iain Lane

Finalise changelog

cf98761... by Iain Lane

Update changelog