Bug 1288082

Summary:	Systemd package split
Product:	[Fedora] Fedora	Reporter:	Jan Kurik <jkurik>
Component:	Changes Tracking	Assignee:	Zbigniew Jędrzejewski-Szmek <zbyszek>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	sgallagh, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ChangeAcceptedF24, SystemWideChange
Fixed In Version:	systemd-229-6.fc24	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-14 15:54:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jan Kurik 2015-12-03 12:52:40 UTC

This is a tracking bug for Change: Systemd package split
For more details, see: https://fedoraproject.org//wiki/Changes/systemd_package_split

Two new subpackages will be split out from the main systemd package. systemd-container will contain stuff for launching and managing VMs and containers. system-udev will contain udevd and other hardware-related bits.

Comment 1 Jan Kurik 2016-02-24 14:26:01 UTC

On 2016-Feb-23, we have reached Fedora 24 Change Checkpoint: Completion deadline (testable).

At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.

Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.

Incomplete and non testable Changes will be reported to FESCo on 2016-Feb-26 meeting.  Contingency plan for System Wide Changes, if planned for Alpha (or in case of serious doubts regarding Change completion), will be activated.

Comment 2 Zbigniew Jędrzejewski-Szmek 2016-02-26 07:04:12 UTC

Yep, I didn't push this change. I have it fully implemented in local packages, but there have been unrelated problems with systemd (mainly #1308771, but also some upstream issues). If if it is still possible, I'd like to push it this week after the situation with #1308771 is cleared up and the compose process is fully funcitional again.

Comment 3 Stephen Gallagher 2016-03-04 15:42:31 UTC

(In reply to Zbigniew Jędrzejewski-Szmek from comment #2)
> Yep, I didn't push this change. I have it fully implemented in local
> packages, but there have been unrelated problems with systemd (mainly
> #1308771, but also some upstream issues). If if it is still possible, I'd
> like to push it this week after the situation with #1308771 is cleared up
> and the compose process is fully funcitional again.

Any word on this?

Comment 4 Zbigniew Jędrzejewski-Szmek 2016-03-04 17:08:38 UTC

So... #1308771 is still not fixed as you probably know. We've been going down the rabbit hole further and further, and heavily patching systemd-selinux code. But it's not done yet.

I pushed the patches for #1308771 and the split for this bug to rawhide/F24 and it's building in koji now.