Hi!
I'm trying to build a firmware-enriched kfreebsd-9.1 kernel. However
some of the drivers disabled FTBFS (see below). What would be the
convenient way to disable the failing drivers (or get the iwn*fw.ko)?
Christoph
===> nve (all)
uudecode <
/home/christoph/scratch/kfreebsd-9-9.1/flavor-
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 31 Jul 2013 13:52:17 +0200
Source: kfreebsd-9
Binary: kfreebsd-source-9.2 kfreebsd-headers-9.2-1 kfreebsd-image-9.2-1-686-smp
kfreebsd-image-9-686-smp kfreebsd-headers-9.2-1-686-smp
kfreebsd-headers-9-686-smp kfree
Your message dated Wed, 31 Jul 2013 15:20:10 +
with message-id
and subject line Bug#718250: fixed in kfreebsd-9 9.2~svn253698-1
has caused the Debian Bug report #718250,
regarding kfreebsd-image-9.1-1-amd64: attaching USB keyboard makes system reboot
to be marked as done.
This means that you
kfreebsd-9_9.2~svn253698-1_kfreebsd-amd64.changes uploaded successfully to
localhost
along with the files:
kfreebsd-9_9.2~svn253698-1.dsc
kfreebsd-9_9.2~svn253698.orig.tar.xz
kfreebsd-9_9.2~svn253698-1.debian.tar.gz
kfreebsd-source-9.2_9.2~svn253698-1_all.deb
kfreebsd-headers-9.2-1_9.2~s
2013/7/31 Steven Chamberlain :
> On 31/07/13 12:45, Robert Millan wrote:
>>> It probably needs to
>>> end up in a README.Debian at least, plus mentioned in the changelog:
>>
>> Sounds fine too.
>
> I'm not sure how to deploy that file exactly. Could you please try?
> I'll be a little busy today.
2013/7/30 Guillem Jover :
> Hmmm, this has the problem that it introduces a circular
> build-dependency:
>
> freebsd-buildutils → freebsd-libs (via libsbuf-dev) → freebsd-buildutils
>
> which is a problem when bootstrapping on new architectures.
Yes, I'm aware of it. I don't see this as a proble
On 31/07/13 12:45, Robert Millan wrote:
>> It probably needs to
>> end up in a README.Debian at least, plus mentioned in the changelog:
>
> Sounds fine too.
I'm not sure how to deploy that file exactly. Could you please try?
I'll be a little busy today.
Thanks,
Regards,
--
Steven Chamberlain
s
2013/7/30 Steven Chamberlain :
> I've written the following text to explain 'workarounds' for those
> issues. I'm not sure exactly where to put this.
Maybe DSA advisory is the best place?
> It probably needs to
> end up in a README.Debian at least, plus mentioned in the changelog:
Sounds fine t
8 matches
Mail list logo