Hi Robert,
Robert Millan wrote:
> This isn't a kernel bug. The kernel recognizes O_CLOEXEC properly
> when userland uses it.
>
> The problem is that userland isn't actually using O_CLOEXEC, because
> its declaration is missing in glibc headers. Actually it's already
> been reported: see #679198
Accepted:
kfreebsd-kernel-headers_0.82.dsc
to main/k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_0.82.dsc
kfreebsd-kernel-headers_0.82.tar.gz
to main/k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_0.82.tar.gz
kfreebsd-kernel-headers_0.82_kfreebsd-amd64.deb
to
main/k/kfreebsd-kernel
Your message dated Fri, 29 Jun 2012 21:18:21 +
with message-id
and subject line Bug#677417: fixed in kfreebsd-kernel-headers 0.82
has caused the Debian Bug report #677417,
regarding kfreebsd-source-9.0: _types.h breaks tcc as it uses gcc specific type
__va_list
to be marked as done.
This mea
kfreebsd-kernel-headers_0.82_kfreebsd-amd64.changes uploaded successfully to
localhost
along with the files:
kfreebsd-kernel-headers_0.82.dsc
kfreebsd-kernel-headers_0.82.tar.gz
kfreebsd-kernel-headers_0.82_kfreebsd-amd64.deb
Greetings,
Your Debian queue daemon (running on host fra
Accepted:
freebsd-glue_0.0.4.dsc
to main/f/freebsd-glue/freebsd-glue_0.0.4.dsc
freebsd-glue_0.0.4.tar.gz
to main/f/freebsd-glue/freebsd-glue_0.0.4.tar.gz
freebsd-glue_0.0.4_all.deb
to main/f/freebsd-glue/freebsd-glue_0.0.4_all.deb
Changes:
freebsd-glue (0.0.4) unstable; urgency=high
.
2012/6/22 Anton Gladky :
> It would be good to know your opinion on that, comments and patches
> are very welcome.
I don't think the hierarchy is supposed to be there at all,
that was just compatibility glue for an API transition. It's long
gone on both FreeBSD and GNU/kFreeBSD now.
--
Robert
On Fri, 29 Jun 2012, Robert Millan wrote:
> > reassign 679128 freebsd-utils
> > thankyou
> > On Tue, Jun 26, 2012 at 10:43:17AM -0400, Yaroslav Halchenko wrote:
> >> is there any specific reason or could it be shipped under /sbin/ ?
> > Ask the freebsd-utils people, after all it is their program
2012/6/29 Steven Chamberlain :
> #679198 is this bug. Did you mean #635192?
Yes, sorry.
> In /usr/include/i386-kfreebsd-gnu/bits/fcntl.h :
>
>> #if _POSIX_C_SOURCE >= 200809L
>> #define O_TTY_INIT 0x0008 /* Restore default termios
>> attributes */
>> /* Defining O_CLOEXEC would br
Hi Steven,
2012/6/25 Steven Chamberlain :
> Do we define SIGCANCEL as __SIGRTMIN?
No, you're looking at the wrong code. Our SIGCANCEL definition is in
sysdeps//kfreebsd/linuxthreads/kernel-posix-timers.h
> If so, having redefined __SIGRTMIN from 32 to the awkward number 65,
> does that not
On 29/06/12 20:28, Robert Millan wrote:
> The problem is that userland isn't actually using O_CLOEXEC, because
> its declaration is missing in glibc headers. Actually it's already
> been reported: see #679198.
#679198 is this bug. Did you mean #635192?
In /usr/include/i386-kfreebsd-gnu/bits/fcn
freebsd-glue_0.0.4_kfreebsd-amd64.changes uploaded successfully to localhost
along with the files:
freebsd-glue_0.0.4.dsc
freebsd-glue_0.0.4.tar.gz
freebsd-glue_0.0.4_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
--
To UNSUBSCRIBE, email to debia
2012/6/24 Christoph Egger :
> The most "interesting" change IMHO is SHELL now being /bin/sh while it
> was bash. Happy to take suggestions on what to try to modify here as
> well. Unfortunately building the thing up to the error takes something
> like half a day so I can't build new tests that fast
Processing commands for cont...@bugs.debian.org:
> reassign 679198 bash
Bug #679198 [src:kfreebsd-9] bash: [on native FreeBSD] unable to set FD_CLOEXEC
flag
Bug reassigned from package 'src:kfreebsd-9' to 'bash'.
Ignoring request to alter found versions of bug #679198 to the same values
previous
2012/6/26 Craig Small :
> reassign 679128 freebsd-utils
> thankyou
>
> On Tue, Jun 26, 2012 at 10:43:17AM -0400, Yaroslav Halchenko wrote:
>> is there any specific reason or could it be shipped under /sbin/ ?
> Ask the freebsd-utils people, after all it is their program and not
> mine.
What's the
reassign 679198 bash
thanks
2012/6/29 Debian Bug Tracking System :
> Processing commands for cont...@bugs.debian.org:
>
>> reassign 679198 src:kfreebsd-9
This isn't a kernel bug. The kernel recognizes O_CLOEXEC properly
when userland uses it.
The problem is that userland isn't actually using O_
2012/6/28 Steven Chamberlain :
> So is there going to be a freebsd-glue 0.0.4, or was that a mistake in
> the build deps?
My bad. Looks like I prepared the upload but forgot to dput it :-(
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "uns
On 26/06/12 18:02, Raúl Sánchez Siles wrote:
> I would greatly appreciate if you could test the build again. I don't have
> access to a kfreebsd machine and hence I'm unable to test this on time before
> the freeze.
Hi,
It seems to build OK now on kfreebsd-i386 after this commit fixed the
bui
Please could somebody look at the python3.3 build for kfreebsd, and provide the
missing patches?
thanks, Matthias
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fedbd
cking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tarantool
Source-Version: 1.4.6+20120629-1
We believe that the bug you reported is fixed in the latest version of
tarantool, which is due to be installed in the Debian FTP archive:
libtarantool-dev_1.4.6+20120629-1_
On 29/06/12 14:12, Stefan Ott wrote:
> Interesting. If you have a ideas / patches that I could try out I
> would be happy to.
You could rebuild bash with Jonathan Nieder's patch, and use it locally
http://lists.debian.org/20120627015952.GH7701@burratino
It would be nice to fix this, as bash is a
On Fri, Jun 29, 2012 at 1:41 PM, Steven Chamberlain wrote:
> reassign 679198 src:kfreebsd-9
> affects 679198 src:bash
> retitle 679198 bash: [on native FreeBSD] unable to set FD_CLOEXEC flag
> thanks
>
> On 29/06/12 03:19, Stefan Ott wrote:
>> I suppose that narrows it down a little. I'm more and
Processing commands for cont...@bugs.debian.org:
> reassign 679198 src:kfreebsd-9
Bug #679198 [bash] bash: Fails to upgrade in kFreeBSD jails
Bug reassigned from package 'bash' to 'src:kfreebsd-9'.
No longer marked as found in versions bash/4.2-2.
Ignoring request to alter fixed versions of bug #6
reassign 679198 src:kfreebsd-9
affects 679198 src:bash
retitle 679198 bash: [on native FreeBSD] unable to set FD_CLOEXEC flag
thanks
On 29/06/12 03:19, Stefan Ott wrote:
> I suppose that narrows it down a little. I'm more and more inclined to
> blame ZFS.
But /dev/null itself is on a devfs so I d
Hi again,
Are you running multiple postgres instances? The sysvipc namespace is
unfortunately shared across all jails and with the host (which is why
it's normally disabled).
Apparently each postgres instance would need a different uid in
/etc/passwd to work around that:
http://wiki.freebsd.org
This is an automatic notification regarding your Bug report
which was filed against the src:goobox package:
#679313: goobox: FTBFS: syntax error near unexpected token `maximum'
It has been closed by Helge Kreutzmann .
Their explanation is attached below along with your original report.
If this e
Hi,
I don't see any differences in our setup except for my host system being
GNU/kFreeBSD and not upstream FreeBSD. I also don't have a jexec so I'm
entering the jail by either:
1. jail -m jid=4 command=/bin/bash
2. starting sshd in the jail and then logging into it that way
Maybe the rlimits a
26 matches
Mail list logo
