[Quantal][SRU][pull-request] Misc linux-backports-modules cleanup
Leann Ogasawara
leann.ogasawara at canonical.com
Fri Oct 19 16:12:27 UTC 2012
On 10/19/2012 08:54 AM, Tim Gardner wrote:
> On 10/19/2012 09:50 AM, Leann Ogasawara wrote:
>> On 10/19/2012 07:44 AM, Tim Gardner wrote:
>>> On 10/19/2012 07:49 AM, Leann Ogasawara wrote:
>>>> On 10/19/2012 05:40 AM, Tim Gardner wrote:
>>>>> On 10/18/2012 03:00 PM, Leann Ogasawara wrote:
>>>>>> BugLink: http://bugs.launchpad.net/bugs/1068125
>>>>>> BugLink: http://bugs.launchpad.net/bugs/1068283
>>>>>>
>>>>>> == Quantal SRU Justification ==
>>>>>> The following pull request performs some misc cleanup for the
>>>>>> linux-backports-modules package for Quantal.
>>>>>>
>>>>>> The first patch makes the compat-wireless firmware udev helper file
>>>>>> names version and ABI specific. We allow multiple upstream versions of
>>>>>> the compat-wireless stack to be packaged and installed. There currently
>>>>>> exists a potential for conflicts with some of the compat-wireless
>>>>>> firmware udev helper file names due to the files only being ABI
>>>>>> specific, but not version specific, with respect to their naming
>>>>>> convention. Fix this by making these both version and ABI specific.
>>>>>>
>>>>> I am not convinced this is necessary. All subsequent CW packages
>>>>> _must_ conflict, therefore you can never get into a state of clashing
>>>>> udev firmware helpers. Refer to the complex conflict relationships in
>>>>> Lucid LBM.
>>>> Hrm, seems we need our Conflicts: set up for Precise LBM too. But
>>>> that's beyond the scope of this patch set. I'll send a follow on patch
>>>> for that.
>>>>
>>> There is no use having a 'Conflicts:' until there is a package with
>>> which to conflict, i.e., compat-wireless-3.7.
>> Indeed for Quantal LBM that's the case. For Precise LBM though we
>> already have cw-3.3, cw-3.4, cw-3.5, and cw-3.6 but no Conflicts set for
>> any of them.
>>
> Whoops. There is a disaster waiting for a place to happen. You gonna
> write that patch ?
Yep. I'll get it sent to the list shortly.
Thanks,
Leann
More information about the kernel-team
mailing list