rpm-ostree

Author SHA1 Message Date

Author	SHA1	Message	Date
Jonathan Lebon	592d6052b9	ci: Bump to F28 Closes: #1358 Approved by: cgwalters	2018-05-23 14:18:41 +00:00
Colin Walters	8726be65e3	core: Finish implementing `override replace ./kernel.x86_64.rpm Previously we merged: #1228 AKA `12dc565b00` My recollection is that was working on it the background, while doing something else, and I clearly didn't get to the point of testing it "for real". There are many interlocking issues here to make this work. For example, the "remove RPM" logic needs special handling for the kernel, because we also inject content into `/usr/lib/ostree-boot` and also generate the initramfs, etc. The architecture I chose is to have the core detect* when a kernel is changed, and also call into the kernel processing code when removing a kernel package. But the logic for doing kernel reinstallation client-side is best alongside the initramfs generation logic which already existed in the sysroot upgrader. I extended the test suite to cover what was failing before, and I tested this interactively. But I'm uncertain about adding a test for actually booting into the GA kernel as it's quite possible some bits in userspace rely on a newer kernel. Fixing this properly really wants some infrastructure to better "re-version" an existing package without changing its content. Closes: https://github.com/projectatomic/rpm-ostree/issues/1334 Closes: #1346 Approved by: jlebon	2018-04-26 16:49:53 +00:00
Colin Walters	12dc565b00	core: Set installonly to ensure we only have one kernel The goal here is to support `override replace kernel.x86_64.rpm`. There's a whole lot of logic in libdnf to support having multiple kernel packages installed. AIUI, that was implemented because: 1) The kernel is the biggest source of regressions 2) It'd be quite noticeable if all of your kernel modules were deleted Of course point 2) applies to a lot of userspace too...that's something rpm-ostree fixes of course. Anyways, in some testing all we need to do really is just turn that logic off unconditionally. Closes: https://github.com/projectatomic/rpm-ostree/issues/946 Closes: #1228 Approved by: jlebon	2018-02-14 16:43:08 +00:00

Jonathan Lebon

592d6052b9

ci: Bump to F28

Closes: #1358
Approved by: cgwalters

2018-05-23 14:18:41 +00:00

Colin Walters

8726be65e3

core: Finish implementing `override replace ./kernel*.x86_64.rpm

Previously we merged: #1228 AKA 12dc565b00
My recollection is that was working on it the background, while doing
something else, and I clearly didn't get to the point of testing it "for real".

There are many interlocking issues here to make this work.  For example,
the "remove RPM" logic needs special handling for the kernel, because
we also inject content into `/usr/lib/ostree-boot` and also generate
the initramfs, etc.

The architecture I chose is to have the core *detect* when a kernel
is changed, and also call into the kernel processing code when removing
a kernel package.  But the logic for doing kernel reinstallation client-side
is best alongside the initramfs generation logic which already existed
in the sysroot upgrader.

I extended the test suite to cover what was failing before, and I
tested this interactively.  But I'm uncertain about adding a test
for actually *booting* into the GA kernel as it's quite possible
some bits in userspace rely on a newer kernel.  Fixing this properly
really wants some infrastructure to better "re-version" an existing
package without changing its content.

Closes: https://github.com/projectatomic/rpm-ostree/issues/1334

Closes: #1346
Approved by: jlebon

2018-04-26 16:49:53 +00:00

Colin Walters

12dc565b00

core: Set installonly to ensure we only have one kernel

The goal here is to support `override replace kernel.x86_64.rpm`.

There's a whole lot of logic in libdnf to support having multiple
kernel packages installed.  AIUI, that was implemented because:

1) The kernel is the biggest source of regressions
2) It'd be quite noticeable if all of your kernel modules were deleted

Of course point 2) applies to a lot of userspace too...that's something
rpm-ostree fixes of course.

Anyways, in some testing all we need to do really is just turn that
logic off unconditionally.

Closes: https://github.com/projectatomic/rpm-ostree/issues/946

Closes: #1228
Approved by: jlebon

2018-02-14 16:43:08 +00:00

3 Commits