Bug#645546: clang: FTBFS(kfreebsd): error: Operating system is unknown, configure can't continue

2011-10-16 Thread Christoph Egger
Package: src:clang Version: 2.9-16 Severity: serious Tags: sid wheezy X-Debbugs-Cc: debian-bsd@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds since -14: cd build-clang && \ ../ll

Bug#645543: libio-aio-perl: FTBFS(kfreebsd): error: 'O_CLOEXEC' undeclared (first use in this function)

2011-10-16 Thread Christoph Egger
Package: src:libio-aio-perl Version: 4.11-1 X-Debbugs-Cc: debian-bsd@lists.debian.org Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: In file included from AIO.xs:126:0:

Processed: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 645469 serious Bug #645469 [kfreebsd-9] bind() fails for AF_UNIX sockets with EINVAL Severity set to 'serious' from 'important' > clone 645469 -1 Bug#645469: bind() fails for AF_UNIX sockets with EINVAL Bug 645469 cloned as bug 645527.

Bug#645469: bind fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Petr Salinger
More importantly, there is the question you raised of whether this should be done in userspace by libc instead.  That would avoid upstream having to wonder, "why should we care what happens when someone using a BSD4.3-style bind() calls our BSD4.4-style kernel"? So it's tempting. Yes, I think th

Bug#645469: bind fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Petr Salinger
More importantly, there is the question you raised of whether this should be done in userspace by libc instead. That would avoid upstream having to wonder, "why should we care what happens when someone using a BSD4.3-style bind() calls our BSD4.4-style kernel"? So it's tempting. For now I prop

Bug#645469: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Guillem Jover
On Sun, 2011-10-16 at 13:44:29 +0200, Robert Millan wrote: > 2011/10/16 Jonathan Nieder : > > More importantly, there is the question you raised of whether this > > should be done in userspace by libc instead.  That would avoid > > upstream having to wonder, "why should we care what happens when >

Bug#645502: Resync dhclient-script with FreeBSD version

2011-10-16 Thread Robert Millan
Package: isc-dhcp-client Version: 4.2.2-1 Severity: important Tags: patch This patch resyncs instances of ifconfig and route commands in dhclient-script with the FreeBSD version provided by upstream. It fixes severe problems derived from CLI incompatibility, which make dhclient behave erratically

Bug#645469: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Robert Millan
2011/10/16 Jonathan Nieder : > More importantly, there is the question you raised of whether this > should be done in userspace by libc instead.  That would avoid > upstream having to wonder, "why should we care what happens when > someone using a BSD4.3-style bind() calls our BSD4.4-style kernel"?

Bug#645469: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Jonathan Nieder
Jonathan Nieder wrote: > --- i/sys/kern/uipc_syscalls.c > +++ w/sys/kern/uipc_syscalls.c > @@ -1703,11 +1703,18 @@ getsockaddr(namp, uaddr, len) [...] > sa->sa_len = len; > + datalen = len - offsetof(struct sockaddr, sa_data[0]); > + p = memchr(sa->sa_data, '\

Bug#645469: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Jonathan Nieder
Robert Millan wrote: > 2011/10/16 Jonathan Nieder : >>        unsigned char sun_len; >>        unsigned char sun_family; >>        char sun_path[108];     /* Path name. */ > > Is this 108 the actual length? ISTR it was just a placeholder. It's the actual size of the sun_path field of struct sock

Bug#645469: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Robert Millan
2011/10/16 Jonathan Nieder : > Here's "struct sockaddr_un" in eglibc (socket/sys/un.h, after a little > typedef-chasing): > >        unsigned char sun_len; >        unsigned char sun_family; >        char sun_path[108];     /* Path name. */ Is this 108 the actual length? ISTR it was just a placeh

Getting rid of type-handling from the archive

2011-10-16 Thread Guillem Jover
Hi! I've been filing bug reports on packages Build-Depending on type-handling to switch to native arch wildcards, the bugs still open are: #639117 [w|+| ] e2tools: Remove unused type-handling from Build-Depends #639332 [w|+| ] buildcross: Remove deprecated Depends on type-handling #639164

kfreebsd-8_8.2-9_kfreebsd-amd64.changes ACCEPTED into unstable

2011-10-16 Thread Debian FTP Masters
Accepted: kfreebsd-8_8.2-9.debian.tar.gz to main/k/kfreebsd-8/kfreebsd-8_8.2-9.debian.tar.gz kfreebsd-8_8.2-9.dsc to main/k/kfreebsd-8/kfreebsd-8_8.2-9.dsc kfreebsd-headers-8-amd64_8.2-9_kfreebsd-amd64.deb to main/k/kfreebsd-8/kfreebsd-headers-8-amd64_8.2-9_kfreebsd-amd64.deb kfreebsd-head

Bug#645469: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Jonathan Nieder
Robert Millan wrote: > http://security.freebsd.org/patches/SA-11:05/unix.patch Thanks for the pointer. Here's "struct sockaddr_un" in eglibc (socket/sys/un.h, after a little typedef-chasing): unsigned char sun_len; unsigned char sun_family; char sun_path[108]; /* Pat

Processing of kfreebsd-8_8.2-9_kfreebsd-amd64.changes

2011-10-16 Thread Debian FTP Masters
kfreebsd-8_8.2-9_kfreebsd-amd64.changes uploaded successfully to localhost along with the files: kfreebsd-8_8.2-9.dsc kfreebsd-8_8.2-9.debian.tar.gz kfreebsd-source-8.2_8.2-9_all.deb kfreebsd-headers-8.2-1_8.2-9_kfreebsd-amd64.deb kfreebsd-image-8.2-1-amd64_8.2-9_kfreebsd-amd64.deb kfre

Bug#645377: marked as done (kfreebsd-8: Buffer overflow in handling of UNIX socket addresses)

2011-10-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Oct 2011 10:03:55 + with message-id and subject line Bug#645377: fixed in kfreebsd-8 8.2-9 has caused the Debian Bug report #645377, regarding kfreebsd-8: Buffer overflow in handling of UNIX socket addresses to be marked as done. This means that you claim that the p

Bug#645469: bind() fails for AF_UNIX sockets with EINVAL

2011-10-16 Thread Robert Millan
2011/10/16 Jonathan Nieder : >        E: unable to bind server socket to file '/tmp/cuptyL8GPC': Invalid > argument >        E: error performing command 'update' > > By contrast, kfreebsd-image-8.2-1-amd64 8.2-8+gcc45 works fine. > > Trying to track this down, I tried the example from the bind(2)