Bug#650975: marked as done (r8168: does not belong in a stable release)
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 ---
Bug#650975: r8168: does not belong in a stable release
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). Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650975:
hello all, I got my hardware back from repairs for a mainboard replacement. (Asus P8H67-M LE b3 rev) To find out the r8169 driver is loaded on every distro i tried for my r8111/8168b nic apparently this is stopping me from using any kind of live cd / netinstall only because some people think the r8169 duplicates functionality for the r8168. so now I have 2 choices, doing a full downloaded install and fix afterwards or steps like below: http://forums.linuxmint.com/viewtopic.php?f=42t=80757start=0sid=f0e920bc9ac7823b1a9443f2845b5ed0#p469071 is it really that important to reduce 600 kb of sourcecode that causes issues for so many people ? -- Met vriendelijke groeten, Keimpe de Jong (UndiFineD) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650975: r8168: does not belong in a stable release
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
Bug#650975: r8168: does not belong in a stable release
Am 04.12.2011 19:41, schrieb Julien Cristau: Source: r8168 Severity: serious (x-debbugs-cc to pmatthaei and debian-release) Hi, Hey, thanks for submitting! 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, From my point of view, there are this pros and cons for the driver: Pros: - It is free - It is a working driver (mainline r8169 also covers those NICs, but it is not working for years with specific NICs) - Our users with such a crippled NIC could install this *alternative* driver from our archive Cons: - Overlapping PCIIDs with r8169 - People simple switch to r8168 without reporting bugs (decreased bugfixing on r8169) Sure r8169 should be fixed in upstream, so that there is only one driver and everyone is happy, but when it is fixed? Tomorrow or 2015? Who knows. If someone has got a patch I would be happy to test it :) For the time where it isn't fixed we (IMHO) should ship the driver with our release(s) until r8169 is fixed or r8168 is in mainline (who knows..) the ITP was NAKed by the kernel maintainers, and apparently you agreed in 4ebfcf49.5070...@abeckmann.de to not let this enter wheezy. I just want to note: It is my personal motivation that we should release it (but there is much time until the next release, so the situation could change), not the motivation of Andreas Beckmann, I am doing it on my own. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
