Bug 725931 - Fix GPL v3 dependency in autofs
Summary: Fix GPL v3 dependency in autofs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: autofs
Version: 6.1
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Ian Kent
QA Contact: yanfu,wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 02:25 UTC by Ian Kent
Modified: 2011-12-06 17:59 UTC (History)
2 users (show)

Fixed In Version: autofs-5.0.5-35
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 17:59:20 UTC
Target Upstream Version:


Attachments (Terms of Use)
Patch - replace GPLv3 code (19.93 KB, patch)
2011-07-27 02:28 UTC, Ian Kent
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1723 0 normal SHIPPED_LIVE autofs bug fix and enhancement update 2011-12-06 01:02:10 UTC

Description Ian Kent 2011-07-27 02:25:15 UTC
Description of problem:

Sorry, I had forgotten about this for RHEL-6.2 but I think
it needs to be considered.

autofs has (inadvertently) used some code from samba which
is licensed under GPLv3 which makes autofs implicitly GPLv3.
This isn't too bad since the autofs license statement reads
as "GPLv2 or later".

We have verified autofs as a GPLv2 product which is now
incorrect.

The copyright holder refused to allow autofs to use this
code and retain GPLv2 status, probably because the GPLv3
license doesn't allow it but certainly because he believes
in the GPLv3 license, which is fair enough. I didn't want
to re-license autofs without due consideration so the code
was re-written.

This bug has been raised to replace that code with the GPLv2
licensed re-write.

Comment 1 Ian Kent 2011-07-27 02:28:06 UTC
Created attachment 515400 [details]
Patch - replace GPLv3 code

Upstream patch which replaces the GPLv3 code in question.

Comment 4 errata-xmlrpc 2011-12-06 17:59:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1723.html


Note You need to log in before you can comment on or make changes to this bug.