Hi Steven.
On 27.01.2014 21:22, Steven Chamberlain wrote:
I could reproduce it 8 times out of 100 here on kfreebsd-amd64.
The race happens after getting Connection Refused trying to contact the
fcgi-responder which has just exit (intentionally).
The parent does a wait4() syscall, and if
Package: acct
Version: 6.5.5-2
Severity: serious
Tags: patch
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
Hi,
There is a fairly obvious preprocessor syntax error here:
--- a/acct-6.5.5/files.h.in 2014-01-28 18:02:54.0 +
+++ b/acct-6.5.5/files.h.in 2014-01-28
unarchive 664470
reopen 664470 =
found 664470 1.9.0+svn250-1
tags 664470 + patch
thanks
Hi,
This bug was been reintroduced in 1.9.0+svn250-1. My patch from
http://bugs.debian.org/664470#5 was dropped without explanation. Please
find a refreshed copy of it attached, which fixes the FTBFS on
Package: drumkv1
Version: 0.3.6-1
Severity: serious
Tags: patch
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
Hi,
debian/rules runs configure with --enable-alsa-midi only on Linux.
Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi,
Package: samplv1
Version: 0.3.6-2
Severity: serious
Tags: patch
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
Hi,
debian/rules runs configure with --enable-alsa-midi only on Linux.
Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi,
Package: synthv1
Version: 0.3.6-1
Severity: serious
Tags: patch
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
Hi,
debian/rules runs configure with --enable-alsa-midi only on Linux.
Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi,
Date: Tue, 28 Jan 2014 20:47:52 +
From: Adam D. Barratt a...@adam-barratt.org.uk
Control: tags -1 + confirmed
On Tue, 2014-01-28 at 03:58 +, Steven Chamberlain wrote:
On 27/01/14 16:25, Adam D. Barratt wrote:
The BTS metadata implies that this bug is unfixed in unstable and
On Tue, Jan 28, 2014 at 06:52:14PM +, Steven Chamberlain wrote:
unarchive 664470
reopen 664470 =
found 664470 1.9.0+svn250-1
tags 664470 + patch
thanks
Hi,
This bug was been reintroduced in 1.9.0+svn250-1. My patch from
http://bugs.debian.org/664470#5 was dropped without
Package: busybox
Version: 1:1.22.0-3
Severity: serious
Tags: patch
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
Hi,
busybox FTBFS trying to set up a signal handler for SIGPWR, which is
not used or defined on kfreebsd-* or hurd-i386. The attached patch
would skip setting up this
On 28/01/14 21:02, Steven Chamberlain wrote:
Note that with this patch, it still fails the testsuite as I think
debian/testsuite-kfreebsd.diff needs to be refreshed.
Attached is a refreshed debian/testsuite-kfreebsd.diff
The patch hunks for 'du' had been merged in upstream.
Thanks,
Regards,
tags 728139 + patch
user debian-bsd@lists.debian.org
usertags 728139 kfreebsd
thanks
Hi,
This happens because, only on Linux i386, `-msse` is enabled and so
function convolver_sse_convolve_add is compiled.
Is that allowed by Debian policy? A real 386 or 486 may not be able to
run it.
If
Hi,
Please could we give back stimfit for build on kfreebsd-amd64 and
kfreebsd-i386; I suspect the original problem is fixed, but expect it
to fail now with a Boost-related error instead.
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to
Hi everyone,
What init system would we like to use by default on the non-Linux ports
for jessie?
I hope this question is really as straightforward as it looks, and that
we might come to some general agreement much more quickly than the
tech-ctte bug!
Here are the options I can think of - but
Hi,
I'm planning on uploading xorg-server 1.15 to sid in a week or two.
I've done a test build of all reverse deps on amd64. The intel and
vmware drivers failed, I'll fix them before uploading the server (unless
somebody beats me to it). The geode driver fails. I haven't been able
to test nv,
Steven Chamberlain ste...@pyro.eu.org writes:
Please could we give back stimfit for build on kfreebsd-amd64 and
kfreebsd-i386; I suspect the original problem is fixed, but expect it
to fail now with a Boost-related error instead.
OK, done
Thanks
Christoph
--
9FED 5C6C E206 B70A 5857
Em 2014-01-28 20:31, Steven Chamberlain escreveu:
Hi everyone,
What init system would we like to use by default on the non-Linux
ports
for jessie?
I hope this question is really as straightforward as it looks, and that
we might come to some general agreement much more quickly than the
kfreebsd-9_9.0-10+deb70.6_kfreebsd-amd64.changes uploaded successfully to
localhost
along with the files:
kfreebsd-9_9.0-10+deb70.6.dsc
kfreebsd-9_9.0-10+deb70.6.debian.tar.gz
kfreebsd-source-9.0_9.0-10+deb70.6_all.deb
kfreebsd-headers-9.0-2_9.0-10+deb70.6_kfreebsd-amd64.deb
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 28 Jan 2014 22:09:39 +0100
Source: kfreebsd-9
Binary: kfreebsd-source-9.0 kfreebsd-headers-9.0-2 kfreebsd-image-9.0-2-686-smp
kfreebsd-image-9-686-smp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/01/2014 23:31, Steven Chamberlain wrote:
Here are the options I can think of - but let me know if you want
something not represented here:
1. stay with sysvinit
2. switch to OpenRC unconditionally
3. switch to Upstart unconditionally
4.
On 28/01/14 22:31, Steven Chamberlain wrote:
1. stay with sysvinit
I know that would be the least work, but I think we should take the
opportunity to switch now to one of the modern init systems. Some
package maintainers specifically expressed that they don't want to
maintain SysV init scripts
On 2014-01-28 23:39, Julien Cristau wrote:
On the closed drivers front, I assume nvidia's non-legacy driver will be
fine,
This time nvidia was quick: all (legacy) drivers currently in jessie
already support 1.15.
and fglrx will lag by a few weeks/months as usual?
Probably ...
What is the X
Control: tags -1 + patch
Hi,
This could be fixed by building hid-libusb.c on kfreebsd-any. I
don't know a specific qmake platform specifier for this, but the
patch below (unix but not linux) seems to work nicely, and with
some luck it might work for GNU/Hurd too.
Don't have a Funcube Dongle to
Processing commands for cont...@bugs.debian.org:
tags 643236 - wheezy
Bug #643236 {Done: godi...@debian.org (Martin A. Godisch)} [src:pachi] pachi:
FTBFS: dpkg-buildpackage: error: dpkg-source -b pachi-1.0 gave error exit
status 2
Removed tag(s) wheezy.
notfixed 647956 1.7.1-1
Bug #647956
23 matches
Mail list logo