On Sat, Nov 13, 2010 at 08:13:36PM +0100, Petr Salinger wrote:
what would the effect on the
kfreebsd-* kernel be of removing all of the files which were originally
mentioned in Ben's mails in this bug report, and is that an option which
has been considered by the porters?
From my (non-DD)
Sorry for the slight delay in responding to this.
On Sun, 2010-11-07 at 14:16 +0100, Petr Salinger wrote:
Now we have to somehow prune current source tree and disable some
modules. Could we get squeeze-ignore tag for some of the affected
files or is it necessary to prune all affected files
what would the effect on the
kfreebsd-* kernel be of removing all of the files which were originally
mentioned in Ben's mails in this bug report, and is that an option which
has been considered by the porters?
From my (non-DD) POV, the most problematic are network drivers
On Sat, 2010-11-06 at 10:48 +0100, Petr Salinger wrote:
For the remainder of the files, whilst we may consider granting a
squeeze-ignore tag, we would like to come to an agreement as to how we
can resolve these issues in the medium term. We appreciate that the BSD
kernel has not received
Now we have to somehow prune current source tree and disable some
modules. Could we get squeeze-ignore tag for some of the affected
files or is it necessary to prune all affected files ?
Ben's original lists included some files which we don't appear to be
able to distribute at all. If his
For the remainder of the files, whilst we may consider granting a
squeeze-ignore tag, we would like to come to an agreement as to how we
can resolve these issues in the medium term. We appreciate that the BSD
kernel has not received the same level of upstream attention that the
Linux kernel has
On Sun, 2010-10-03 at 13:04 +0200, Cyril Brulebois wrote:
Ben Hutchings b...@decadent.org.uk (30/08/2010):
The following C files contain firmware images in binary-equivalent
form but are not obviously accompanied by the corresponding source
code: […]
Hi,
and thanks for your report.
On Tue, Oct 26, 2010 at 11:32:13PM +0100, Adam D. Barratt wrote:
...
For the remainder of the files, whilst we may consider granting a
squeeze-ignore tag, we would like to come to an agreement as to how we
can resolve these issues in the medium term.
...
Can you actually add a squeeze-ignore
Ben Hutchings b...@decadent.org.uk (30/08/2010):
Package: kfreebsd-8
Version: 8.1-5
Severity: serious
The following C files contain firmware images in binary-equivalent
form but are not obviously accompanied by the corresponding source
code: […]
Hi,
and thanks for your report. I'm not
Package: kfreebsd-8
Version: 8.1-5
Severity: serious
The following C files contain firmware images in binary-equivalent form
but are not obviously accompanied by the corresponding source code:
sys/contrib/dev/ral/rt2661_ucode.h
- binaries are packaged in firmware-ralink as
Additionally, the following uuencoded files contain binary-equivalent
firmware images with no accompanying source code:
sys/contrib/dev/mwl/mwlboot.fw.uu
sys/contrib/dev/mwl/mw88W8363.fw.uu
- not packaged; distributable
sys/contrib/dev/ral/rt2561.fw.uu
sys/contrib/dev/ral/rt2561s.fw.uu
11 matches
Mail list logo
