Your message dated Mon, 02 Nov 2015 14:56:40 +0100
with message-id <56376b98.50...@debian.org>
and subject line Re: Bug#650975: r8168: does not belong in a stable release
has caused the Debian Bug report #650975,
regarding r8168: does not belong in a stable release
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
650975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r8168
Severity: serious
(x-debbugs-cc to pmatthaei and debian-release)
Hi,
I've been blocking this package from entering testing, but as Patrick
Matthäi questions that choice I'm filing this bug for the record.
It is my opinion, as a member of the release team, that we shouldn't
ship this package in stable.
This driver duplicates functionality available in the r8169 module in
the standard linux kernel, which is going to create a support burden,
the ITP was NAKed by the kernel maintainers, and apparently you agreed
in <4ebfcf49.5070...@abeckmann.de> to not let this enter wheezy.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On 2015-06-24 10:32, Andreas Beckmann wrote:
> On 2011-12-04 19:41, Julien Cristau wrote:
>> I've been blocking this package from entering testing, but as Patrick
>> Matthäi questions that choice I'm filing this bug for the record.
>>
>> It is my opinion, as a member of the release team, that we shouldn't
>> ship this package in stable.
>>
>> This driver duplicates functionality available in the r8169 module in
>> the standard linux kernel, which is going to create a support burden,
>> the ITP was NAKed by the kernel maintainers, and apparently you agreed
>> in <4ebfcf49.5070...@abeckmann.de> to not let this enter wheezy.
>
> Since r8168 seems to apply binary patches to the firmware, the package
> has been moved to non-free.
> Can we close this bug now and let r8168 enter stretch/non-free?
> It's also much less intrusive w.r.t. in-tree r8169 than a few years ago
> (no more full blacklisting of r8169, just claims the subset of devices
> it supports).
Closing this bug now to let r8168 into stretch/non-free.
Andreas
--- End Message ---
