Hi,
See below a message from Motohiro KOSAKI, a Ruby developer (Cced).
Full discussion at http://redmine.ruby-lang.org/issues/5239
Short story:
Some breaks in the Ruby test suite on kfreebsd. The code does:
- create a process with fork()
- create a (p)thread
- issue a waitpid() from the pthread o
Package: kfreebsd-image-8.1-1-amd64
Version: 8.1+dfsg-8
Severity: serious
Hi,
Test case:
<-
#include
#include
#include
#include
#include
#include
int retval;
int pid;
void * thread_get_retval(void *arg) {
if (waitpid(pid, &retval, 0) == -1) {
perror("waitpi
Hi,
A change in Ruby caused it to hang again, likely due to a pthread
semantic difference on kfreebsd. It doesn't hang, neither on Linux nor
on FreeBSD.
Affected package is the experimental one. It's a pre-release snapshot
(candidate RC1) for Ruby 1.9.3, to be released in september, and likely
th
On 29/08/11 at 14:05 +0200, Petr Salinger wrote:
> Hi.
>
> >A change in Ruby caused it to hang again, likely due to a pthread
> >semantic difference on kfreebsd. It doesn't hang, neither on Linux nor
> >on FreeBSD.
> >
> >Affected package is the experimental one. It's a pre-release snapshot
> >(ca
On 29/08/11 at 20:57 +0200, Petr Salinger wrote:
> >Would you have time to turn that into a (tested ;) ) patch?
>
> I tried the attached one, but it does not compile/link:
>
> linking ruby1.9.1
> main.o: In function `main':
> .../ruby1.9.1-1.9.3~preview1+svn33077/main.c:36:
> undefined re
Hi,
Ruby 1.9.3 is going to be released in september, and is a candidate for
the default ruby version in wheezy. A snapshot is available in
experimental. Now is an ideal time to work on porting issues and get the
fixes integrated upstream. Ruby has a fairly large test suite, which
makes finding pro
08/11 at 23:48 +0200, Lucas Nussbaum wrote:
> Ruby 1.9.3 is going to be released in september, and is a candidate for
> the default ruby version in wheezy. A snapshot is available in
> experimental. Now is an ideal time to work on porting issues and get the
> fixes integrated upstream.
On 03/11/11 at 21:27 +0100, Julien Cristau wrote:
> On Sun, Oct 23, 2011 at 14:11:26 +0200, Lucas Nussbaum wrote:
>
> > At this point, I'm confident that we can reach a (at least partially)
> > working Ruby on kfreebsd, sparc and armel at some point. I'm l
On 06/03/08 at 17:53 +0100, Lucas Nussbaum wrote:
> Hi,
>
> I actually have the opposite problem with my r8169:
> - if the interface is left up during shutdown, WOL works.
> - if the interface is down during shutdown, WOL doesn't work.
> But that's a driver pr
0 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--
To U
ot;ok")
Uh?
#916 test_thread.rb:254:in `':
STDERR.reopen(STDOUT)
exec "/"
#=> killed by signal 32
Same: uh? What's signal 32 on FreeBSD?
Appropriate steps to investigate those:
- rebuild ruby1.9.1 with DEB_BUILD_OPTIONS=nocheck (so the test suite won'
This may be a ruby bug, but
> it's still really, really annoying.
Which version of ruby are you using? Is it >= 1.8.7.249-4 ?
ruby1.8 (1.8.7.249-4) unstable; urgency=low
[ Lucas Nussbaum ]
[..]
* Update debian/patches/100312_timeout-fix.dpatch after discussion with
Petr
-1;arch=kfreebsd-i386;stamp=1280703210
https://buildd.debian.org/fetch.cgi?pkg=ruby1.9.1;ver=1.9.2~svn28788-1;arch=kfreebsd-amd64;stamp=1280661492
There's an history of kfreebsd problems with Ruby 1.9.* (#543805, #542927,
#590002) but all are supposed to be fixed.
Since it works fine on am
On 10/11/14 at 23:01 +, Steven Chamberlain wrote:
> I guess snapshots.d.o would still have copies of the last packages that
> were _in_ testing?
Yes
> But won't have the indices _for_ testing.
It has them as well. See e.g.
http://snapshot.debian.org/archive/debian/2014T040940Z/dists/jess
On 10/11/14 at 22:09 +, Steven Chamberlain wrote:
> Petr Salinger wrote:
> > >Jonathan Wiltshire wrote:
> > >>[...] though we do hope that the
> > >>porters will be able to make a simultaneous unofficial release.
> >
> > It is unclear, what we have to duplicate. Do we stay in testing ?
>
> I'
Source: freebsd-buildutils
Version: 10.3~svn296373-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefull
Source: kfreebsd-10
Version: 10.3~svn300087-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> d
Source: freebsd-glue
Version: 0.2.22
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules binary
> M
Source: freebsd-libs
Version: 10.3~svn296373-10
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules
19 matches
Mail list logo
