#301 Policy around packagers not getting an exception for a library or refusing to comply with an unbundling ruling
Closed: Fixed None Opened 9 years ago by toshio.

We talked about this at today's fpc meeting in relation to https://bugzilla.redhat.com/show_bug.cgi?id=964940

We want to lay out what steps people need to be taking in the No Bundled Libraries Guidelines and show that if it comes to enforcement, the request then goes to FESCo.


Update the following two sections:

When a Bundled Library is Discovered Post-Review

Bundling of libraries is a serious problem. If a package that is in the distribution is discovered to have bundled libraries we need to fix it. First, open a bug report against the package. Then add the bug to the Duplicate libraries tracker. Once that's done, if help is needed fixing the bug ask on the mailing list. Maintainers must leave the bug open until the situation is resolved (either by unbundling or via an FPC exception). If a patch is supplied the maintainer needs to evaluate it and actively work to apply it to the package. Note that unbundling is one of several areas in which we will locally patch to override upstreams.

Exceptions are granted on a case-by-case basis by FPC. You can look in the following section for help on making a case for why an exception should be granted. You should open up a ticket in the FPC's trac[https://fedorahosted.org/fpc/] with information asked for below.

If you are reporting a bundling situation and the package maintainer either won't request an exception as required by these Guidelines or won't conform to an FPC ruling on whether they are allowed to bundle, the next step is to open a ticket with FESCo [https://fedorahosted.org/fesco] to have the guideline enforced.

Policy draft approved (+1:7, 0:0, -1:0)

Login to comment on this ticket.