On Thu, Feb 02, 2012 at 09:41:46PM +, Robert Millan wrote:
El 2 de febrer de 2012 18:54, Aurelien Jarno aurel...@aurel32.net ha escrit:
We need the rebuild for ABI transition anyway, so it's no harm to
queue it right away.
Does it mean that after a rebuild, it won't work anymore
On Fri, Feb 03, 2012 at 12:33:33AM +, peter green wrote:
Kurt Roeckx wrote:
Can I instead suggest someone looks at the kernel and fixes it?
It used to work, it works on the porter machines, it just fails
on the buidds.
Aurelien Jarno wrote:
The kernel part is not trivial to solve.
forwarded 658639 http://www.freebsd.org/cgi/query-pr.cgi?pr=164793
thanks
2012/2/5, Nicolas Bourdaud nicolas.bourd...@gmail.com:
Bug report opened upstream:
http://www.freebsd.org/cgi/query-pr.cgi?pr=164793
Thanks!
--
Robert Millan
--
To UNSUBSCRIBE, email to
Processing commands for cont...@bugs.debian.org:
forwarded 658639 http://www.freebsd.org/cgi/query-pr.cgi?pr=164793
Bug #658639 [src:kfreebsd-9] kfreebsd-9: 'write' system call violates POSIX
standard
Set Bug forwarded-to-address to
'http://www.freebsd.org/cgi/query-pr.cgi?pr=164793'.
thanks
Package: iceweasel
Version: 9.0.1-1
Severity: grave
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
After upgrading from 7.0.1-4, iceweasel now gets stuck in an infinite poll()
loop during startup.
ktrace output:
1116 xulrunner-stub CALL poll(0x7fffbe30,0x1,0x)
1116
On 04/02/2012 21:07, Robert Millan wrote:
Can you reproduce this with upstream kernel? (apt-get install
kfreebsd-downloader)
Yes it is reproducible with upstream kernel
If it affects upstream, for this kind of reports it's much better to
report them to FreeBSD PR database instead:
Processing commands for cont...@bugs.debian.org:
owner 658677 debian-bsd@lists.debian.org
Bug #658677 [kfreebsd-image-9] [kfreebsd-image-9] Please enable pflog device by
default
Warning: Unknown package 'kfreebsd-image-9'
Owner recorded as debian-bsd@lists.debian.org.
Warning: Unknown package
owner 658677 debian-bsd@lists.debian.org
thanks
On 05/02/12 02:23, Dererk wrote:
As a side note, current archive's tcpdump version is unable to recognize
the pseudo interface type[1][2], but using openbsd's provided tcpdump
does read kbsd's captured dumps. If this patch is accepted, I'll try
2012/2/5, Aurelien Jarno aurel...@aurel32.net:
The problem there is that given that all 9.x packages have been already
pushed to the archive with ABI changes and so on, we *must* switch the
default kernel for wheezy to 9.x.
This is not really the case. We can switch the default [1] kernel if
2012/2/2, Sven Joachim svenj...@gmx.de:
Yes, with the caveat that they will face problems connecting to other
systems from within the chroot, since xterm- does not exist in
non-Debian systems. So if the chroot is never used with a Debian
kernel, overriding the xterm terminfo is certainly
Now we have no choice than making a real plan for switching to 9.x
kernel:
- We have to make sure users are using wheezy/sid with a 9.x kernel.
- We have to provide an upgrade path for users, including the best
moment to switch from one kernel to another in the release notes.
You're missing a
On 2012-02-05 14:39 +0100, Robert Millan wrote:
2012/2/2, Sven Joachim svenj...@gmx.de:
Yes, with the caveat that they will face problems connecting to other
systems from within the chroot, since xterm- does not exist in
non-Debian systems. So if the chroot is never used with a Debian
There's a divergence in id_t definition between Glibc and kfreebsd headers:
- Glibc defines id_t as uint32_t (on all architectures)
- kFreeBSD defines id_t as int64_t (on all architectures)
Glibc defines id_t in bits/typesizes.h which allows kernel ports to
define it as they please.
13 matches
Mail list logo
