[debian-hurd-Patches][301211] #296115: ifupdown (debian-ports)
debian-hurd-Patches item #301211 was changed at 29/12/2017 17:40 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=301211&group_id=30628 >Status: Closed Priority: 3 Submitted By: Michael Banck (mbanck) Assigned to: Nobody (None) Summary: #296115: ifupdown (debian-ports) Category: debian Group: submitted Resolution: None Initial Comment: Author: Michael Banck Source: ifupdown Status: submitted(#296115) Categories: debian Strip-Level: -p1 -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:40 Message: that was fixed a few years ago. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=301211&group_id=30628
[debian-hurd-Patches][303210] mailutils
debian-hurd-Patches item #303210 was changed at 29/12/2017 17:47 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303210&group_id=30628 >Status: Closed Priority: 3 Submitted By: Christopher Bodenstein (physicman-guest) Assigned to: Nobody (None) Summary: mailutils Category: posix Group: unreviewed Resolution: None Initial Comment: Author: Christopher Bodenstein Source: mailutils Strip-Level: -p1 Status: unreviewed Categories: posix The attached patch removes one instance of MAXHOSTNAMELEN using xgethostname(). Apparently, you need automake1.9 to get the .am files to be processed correctly. Also, I had to disable the checks in the debian/rules file as at least one of them seems to make my machine freeze. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:47 Message: That was fixed some time ago -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303210&group_id=30628
[debian-hurd-Patches][303178] jamvm-1.4.2
debian-hurd-Patches item #303178 was changed at 29/12/2017 17:48 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303178&group_id=30628 >Status: Closed Priority: 3 Submitted By: Barry deFreese (bddebian-guest) Assigned to: Nobody (None) Summary: jamvm-1.4.2 Category: build-env Group: unreviewed Resolution: None Initial Comment: Author: Barry deFreese Source: jamvm Status: unreviewed Categories: build-env Strip-Level: -p1 Missing configure options for gnu*) -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:48 Message: jamvm is not in Debian any more. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303178&group_id=30628
[debian-hurd-Patches][303152] cdargs
debian-hurd-Patches item #303152 was changed at 29/12/2017 17:47 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303152&group_id=30628 >Status: Closed Priority: 3 Submitted By: Christopher Bodenstein (physicman-guest) Assigned to: Nobody (None) Summary: cdargs Category: posix Group: unreviewed Resolution: None Initial Comment: Author: Christopher Bodenstein Source: cdargs Status: unreviewed Categories: posix Strip-Level: -p1 The attached patch uses get_current_dir_name() instead of getcwd if _GNU_SOURCE is defined (get_current_dir_name should be tested in the configure but I can't get it to work properly, when I modify the configure.in the resulting configure is all messed up and the package won't build) and avoids the use of PATH_MAX in that case. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:47 Message: That was fixed some time ago. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303152&group_id=30628
[debian-hurd-Patches][303220] dvdisaster
debian-hurd-Patches item #303220 was changed at 29/12/2017 17:48 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303220&group_id=30628 >Status: Closed Priority: 3 Submitted By: Christopher Bodenstein (physicman-guest) Assigned to: Nobody (None) Summary: dvdisaster Category: posix Group: unreviewed Resolution: None Initial Comment: Author: Christopher Bodenstein Source: dvdisaster Strip-Level: -p1 Status: unreviewed Categories: posix There is one instance of PATH_MAX used in a getcwd(). I use a get_current_dir_name() to replace it, however there is no configure.in so I patched configure directly to check the the function's presence. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:48 Message: That got fixed some time ago. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303220&group_id=30628
[debian-hurd-Patches][303255] libusb-0.1.11
debian-hurd-Patches item #303255 was changed at 29/12/2017 17:48 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303255&group_id=30628 >Status: Closed Priority: 3 Submitted By: Barry deFreese (bddebian-guest) Assigned to: Nobody (None) Summary: libusb-0.1.11 Category: several Group: unreviewed Resolution: None Initial Comment: Here is a patch to build libusb on GNU/Hurd. Obviously you need to run aclocal, autoheader, and autoreconf. It isn't quite complete becuase it didn't finish building but I was getting a segfault with jade making some of the files. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:48 Message: That got fixed some time ago -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303255&group_id=30628
[debian-hurd-Patches][303733] cdargs
debian-hurd-Patches item #303733 was changed at 29/12/2017 17:49 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303733&group_id=30628 >Status: Closed Priority: 3 Submitted By: Michael Banck (mbanck) Assigned to: Nobody (None) Summary: cdargs Category: posix Group: unreviewed Resolution: None Initial Comment: Author: Ben Asselstine -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:49 Message: That got fixed some time ago -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=303733&group_id=30628
[debian-hurd-Patches][305130] native backend for hal
debian-hurd-Patches item #305130 was changed at 29/12/2017 17:49 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=305130&group_id=30628 >Status: Closed Priority: 3 Submitted By: Samuel Thibault (sthibaul-guest) Assigned to: Nobody (None) Summary: native backend for hal Category: None Group: None Resolution: Later Initial Comment: Fixes compilation, but still using the dummy backend. We need to port hal on the Hurd, but we should be probably don't do it blindly, build nice hurdish abstractions, etc. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:49 Message: hal is not in Debian any more. -- Comment By: Pino Toscano (pino-guest) Date: 17/11/2009 01:51 Message: hal 0.5.13-4 now compiles and runs again on the Hurd. Thus changing this tracker for further work on a native backend for the Hurd. -- Comment By: Pino Toscano (pino-guest) Date: 25/10/2009 22:44 Message: Thanks! Done as bug #552386 -- Comment By: Samuel Thibault (sthibault) Date: 25/10/2009 19:35 Message: It seems right, please submit! -- Comment By: Pino Toscano (pino-guest) Date: 25/10/2009 10:50 Message: Here it is a patch for making hal compilable and installable: - tools/hal-disable-polling.c: usual realpath()+PATH_MAX porting - debian/control: linux-only stuff excluded - debian/hal.init: there's no /proc/$PID/root file, so the chroot check is bogus (and makes startup fail); disabling it makes the hal daemon runnable via init script hal still uses the dummy backend on hurd, but that can be worked on later, I guess. -- Comment By: Samuel Thibault (sthibaul-guest) Date: 22/12/2007 23:46 Message: Oops, sorry, we're still using the dummy backend. Porting is still needed. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=305130&group_id=30628
[debian-hurd-Patches][310749] #479657 dancer-ircd patch
debian-hurd-Patches item #310749 was changed at 29/12/2017 17:50 by Samuel
Thibault
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=310749&group_id=30628
>Status: Closed
Priority: 3
Submitted By: Flávio Cruz (flaviocruz-guest)
Assigned to: Nobody (None)
Summary: #479657 dancer-ircd patch
Category: None
Group: None
Resolution: None
Initial Comment:
dancer-ircd-1.0.36 patch for GNU/Hurd
--
>Comment By: Samuel Thibault (sthibault)
Date: 29/12/2017 17:50
Message:
dancer-ircd got removed from debian
--
Comment By: Samuel Thibault (sthibaul-guest)
Date: 01/05/2008 01:52
Message:
Mmm, sizeof(char) is 1 by C99 definition :)
Just a matter of taste: I would rather
#define LOCK_SUFFIX ".lock"
and then use LOCK_SUFFIX and strlen(LOCK_SUFFIX), it is not so obvious
that lock_suffix_len is the length of lock_suffix.
I guess you have checked that only
ConfigFileEntry.{helpfile,motd,opermotd} need to be cleaned up.
Else the patch seems fine.
--
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=310749&group_id=30628
[debian-hurd-Patches][311309] 509252: ghc6 FTBFS (debian-ports)
debian-hurd-Patches item #311309 was changed at 29/12/2017 17:50 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=311309&group_id=30628 >Status: Closed Priority: 3 Submitted By: Samuel Thibault (sthibaul-guest) Assigned to: Nobody (None) Summary: 509252: ghc6 FTBFS (debian-ports) Category: None Group: None Resolution: None Initial Comment: This is due to ghc using setitimer(TIMER_VIRTUAL), for which Mach doesn't provide any support. The attached patch just makes it use ITIMER_REAL instead. I've filed a ticket upstream http://hackage.haskell.org/trac/ghc/ticket/2883 Maybe this could be a debian-ports candidate, as ghc6 is blocking all haskell packages. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:50 Message: that got fixed some time ago -- Comment By: Samuel Thibault (sthibaul-guest) Date: 20/12/2008 12:22 Message: Better patch, submitted upstream, that autodetects such case. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=311309&group_id=30628
[debian-hurd-Patches][311761] Partial patch for kbuild 1:0.1.98svn2318-1
debian-hurd-Patches item #311761 was changed at 29/12/2017 17:50 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=311761&group_id=30628 >Status: Closed Priority: 3 Submitted By: Barry deFreese (bdefreese) Assigned to: Nobody (None) Summary: Partial patch for kbuild 1:0.1.98svn2318-1 Category: linuxism Group: submitted Resolution: None Initial Comment: Hi, Attached is the start of a patch for kbuild. Unfortunately it has several PATH_MAX issues that I just #ifdef'd for now. But even larger is that it include sys/mount.h in several places. Thanks, Barry -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:50 Message: that got fixed some time ago -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=311761&group_id=30628
[debian-hurd-Patches][312117] #558586: hyperestraier 1.4.9
debian-hurd-Patches item #312117 was changed at 29/12/2017 17:51 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=312117&group_id=30628 >Status: Closed Priority: 3 Submitted By: Pino Toscano (pino-guest) Assigned to: Nobody (None) Summary: #558586: hyperestraier 1.4.9 Category: None Group: None Resolution: None Initial Comment: Simple malloc+free usage instead of hardcoded PATH_MAX-sized strings. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:51 Message: that got fixed some time ago -- Comment By: Pino Toscano (pino-guest) Date: 29/11/2009 14:32 Message: Thanks! Filed as bug #558586. -- Comment By: Samuel Thibault (sthibault) Date: 29/11/2009 12:55 Message: Seems correct, please submit! -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=312117&group_id=30628
[debian-hurd-Bugs][312564] chroot ... /bin/zsh hangs on opening a pty
debian-hurd-Bugs item #312564 was changed at 29/12/2017 17:53 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=312564&group_id=30628 >Status: Closed Priority: 3 Submitted By: Samuel Thibault (sthibault) Assigned to: Nobody (None) Summary: chroot ... /bin/zsh hangs on opening a pty Category: None Group: None Resolution: None Initial Comment: /bin/zsh works, but dchroot sid /bin/zsh or chroot somewhere /bin/zsh hangs on opening a pty (even on buildd chroots, where ptys were fixed to work). -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:53 Message: This seems to have been fixed -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=312564&group_id=30628
[debian-hurd-Bugs][303367] [test suite] binutils: test failures
debian-hurd-Bugs item #303367 was changed at 29/12/2017 17:58 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=303367&group_id=30628 >Status: Closed Priority: 3 Submitted By: Michael Banck (mbanck) Assigned to: Nobody (None) Summary: [test suite] binutils: test failures Category: test suite Group: None Resolution: None Initial Comment: === binutils tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/config/default.exp as tool-and-target-specific interface file. Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/ar.exp ... FAIL: ar long file names ERROR: /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/bintest.s: assembly failed ERROR: /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/bintest.s: assembly failed Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/dlltool.exp ... Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/hppa/objdump.exp ... Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/m68k/objdump.exp ... Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/nm.exp ... Version /build/buildd/binutils-2.16.1cvs20060413/builddir-single/binutils/nm-new failed ERROR: /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/bintest.s: assembly failed Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/objcopy.exp ... Version /build/buildd/binutils-2.16.1cvs20060413/builddir-single/binutils/objcopy failed ERROR: /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/bintest.s: assembly failed ERROR: unresolved simple copy FAIL: objcopy -O srec ERROR: objdump can not recognize bintest.o ERROR: objdump can not recognize bintest.o Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/objdump.exp ... Version /build/buildd/binutils-2.16.1cvs20060413/builddir-single/binutils/objdump failed FAIL: objdump -i ERROR: /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/bintest.s: assembly failed Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/readelf.exp ... Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/size.exp ... Version /build/buildd/binutils-2.16.1cvs20060413/builddir-single/binutils/size failed ERROR: /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/bintest.s: assembly failed Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/vax/objdump.exp ... Running /build/buildd/binutils-2.16.1cvs20060413/binutils/testsuite/binutils-all/windres/windres.exp ... === binutils Summary === # of unexpected failures3 # of unresolved testcases 4 # of untested testcases 5 -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 17:58 Message: This seems to have been fixed -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=303367&group_id=30628
[debian-hurd-Bugs][303548] [test-suite] perl: test failures
debian-hurd-Bugs item #303548 was changed at 29/12/2017 17:59 by Samuel Thibault
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=303548&group_id=30628
>Status: Closed
Priority: 3
Submitted By: Michael Banck (mbanck)
Assigned to: Nobody (None)
Summary: [test-suite] perl: test failures
Category: test suite
Group: None
Resolution: None
Initial Comment:
run/fresh_perl..sh: line 1: 26798 Segmentation
fault ./perl "-I../lib" "misctmp002" 2>&1
# PROG:
# package Foo;
# eval { require AnyDBM_File }; # not all places have dbm* functions
# if ($@) {
# print "ok\n";
# exit 0;
# }
# package Foo;
# sub new {
# my $proto = shift;
# my $class = ref($proto) || $proto;
# my $self = {};
# bless($self,$class);
# my %LT;
# dbmopen(%LT, "dbmtest", 0666) ||
# die "Can't open dbmtest because of $!\n";
# $self->{'LT'} = \%LT;
# return $self;
# }
# sub DESTROY {
# my $self = shift;
# dbmclose(%{$self->{'LT'}});
# 1 while unlink 'dbmtest';
# 1 while unlink ;
# print "ok\n";
# }
# package main;
# $test = Foo->new(); # must be package var
# EXPECTED:
# GOT:
# STATUS: 35584
# Failed at run/fresh_perl.t line 55
FAILED test 82
Failed 1/94 tests, 98.94% okay
io/pipe.Confused test output: test 8
answered after test 8
Confused test output: test 9 answered after test 9
Confused test output: test 10 answered after test 10
Confused test output: test 11 answered after test 11
Confused test output: test 12 answered after test 12
Confused test output: test 13 answered after test 13
Confused test output: test 14 answered after test 14
Confused test output: test 15 answered after test 15
Confused test output: test 16 answered after test 16
Confused test output: test 17 answered after test 17
Confused test output: test 18 answered after test 18
Confused test output: test 19 answered after test 19
Confused test output: test 20 answered after test 20
Confused test output: test 21 answered after test 21
FAILED test 7
Failed 1/22 tests, 95.45% okay
op/64bitint.skipped
all skipped: no 64-bit types
op/lfs..skipped
all skipped: no 64-bit file offsets
op/stat.# Failed at op/stat.t line 262
# got '143'
# expected '142'
FAILED test 37
Failed 1/86 tests, 98.84% okay
lib/cygwin..skipped
all skipped: cygwin specific test
4/33 skipped: various reasons
../ext/Cwd/t/win32..skipped
all skipped: this is not win32
../ext/Fcntl/t/syslfs...skipped
all skipped: no 64-bit file offsets
../ext/IO/t/io_unix.Cannot assign requested address at
../ext/IO/t/io_unix.t line 56.
dubious
Test returned status 49 (wstat 12544, 0x3100)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
2/17 skipped: Poor man's MULTICALL can't cope
2/23 skipped: Poor man's MULTICALL can't cope
../ext/NDBM_File/t/ndbm.dubious
Test returned status 0 (wstat 11, 0xb)
../ext/ODBM_File/t/odbm.dubious
Test returned status 0 (wstat 11, 0xb)
../ext/Socket/t/socketpair..Something unexpectedly hung during
testing at ../ext/Socket/t/socketpair.t line 39.
dubious
Test returned status 0 (wstat 4, 0x4)
../ext/Storable/t/interwork56...skipped
all skipped: Your IVs are no larger than your longs
1/78 skipped: irrelevant test in this case
../ext/Sys/Syslog/t/syslog..
# Failed test 'syslog() should return true: '0''
# in ../ext/Sys/Syslog/t/syslog.t at line 109.
# Failed test 'syslog() called with level 'info''
# in ../ext/Sys/Syslog/t/syslog.t at line 113.
# got: 'no connection to syslog available
# - udp connect: nobody listening at ../ext/Sys/Syslog/t/syslog.t line 112
# '
# expected: ''
# Failed test 'syslog() should return true: '0''
# in ../ext/Sys/Syslog/t/syslog.t at line 114.
# Looks like you failed 3 tests of 119.
dubious
Test returned status 3 (wstat 768, 0x300)
DIED. FAILED tests 84-86
Failed 3/119 tests, 97.48% okay (less 66 skipped tests: 50 okay, 42.02%)
../ext/threads/t/libc...dubious
Test returned status 0 (wstat 11, 0xb)
DIED. FAILED tests 10-11
Failed 2/11 tests, 81.82% okay
../ext/threads/t/stress_string..dubious
Test returned status 0 (wstat 11, 0xb)
DIED. FAILED tests 34-64
Failed 31/64 tests, 51.56% okay
../ext/Time/HiRes/t/HiRes...
../ext/Time/HiRes/t/HiRes.t: overall time allowed for tests (300s) exceeded!
Use of uninitialized value in subtraction (-) at ../ext/Time/HiRes/t/HiRes.t
line 592.
dubious
T
[debian-hurd-Bugs][303720] [test-suite] expect
debian-hurd-Bugs item #303720 was changed at 29/12/2017 18:01 by Samuel Thibault
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=303720&group_id=30628
>Status: Closed
Priority: 3
Submitted By: Michael Banck (mbanck)
Assigned to: Nobody (None)
Summary: [test-suite] expect
Category: test suite
Group: None
Resolution: None
Initial Comment:
buildd@beethoven:~/build/chroot-unstable/build/buildd/expect-5.43.0$ make test
rm -f .tmp
echo "set objdir" `pwd` > .tmp
if [ "." = "." ] ; then \
echo "set srcdir" `pwd` >> .tmp ; \
else echo "set srcdir" . >> .tmp ; fi
echo "cd \${srcdir}/tests" >> .tmp
echo "source all.tcl" >> .tmp
rootme=`pwd`; export rootme; \
srcdir=. ; export srcdir ; \
if [ -f ./expect ] ; then \
TCL_LIBRARY=/usr/include/tcl8.4/tcl-private/library ; \
export TCL_LIBRARY ; fi ; \
LD_LIBRARY_PATH=.:/usr/lib:/usr/lib:$LD_LIBRARY_PATH ./expect -f .tmp
cat.test
expect.test
expect-1.3 exact pattern failure FAILED
Contents of test case:
expect "*"
exp_send "hiahi\r"
set timeout 10
set x 0
expect -ex hi {set x 1}
expect -ex hi {set x 2}
expect -ex hi {set x 3}
set x
Result was:
3
Result should have been (exact matching):
2
expect-1.3 FAILED
logfile.test
via sendvia send_uservia send_stdoutvia send_ttypid.test
send.test
spawn.test
stty.test
all.tcl:Total 25 Passed 24 Skipped 0 Failed 1
Sourced 0 Test Files.
Files with failing tests: expect.test
rm -f .tmp
--
>Comment By: Samuel Thibault (sthibault)
Date: 29/12/2017 18:01
Message:
The build now succeeds, with some test failures, but which are not fatal.
--
Comment By: Michael Banck (mbanck)
Date: 30/05/2007 16:43
Message:
This test no longer fails; however, running the test suite in a chroot does not
work (it hangs); running the test suite from the main install yields no
failures.
--
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=303720&group_id=30628
[debian-hurd-Bugs][310484] [test-suite] libatomic-ops 1.2-3
debian-hurd-Bugs item #310484 was changed at 29/12/2017 18:02 by Samuel Thibault
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=310484&group_id=30628
>Status: Closed
Priority: 3
Submitted By: Barry deFreese (bddebian-guest)
Assigned to: Nobody (None)
Summary: [test-suite] libatomic-ops 1.2-3
Category: None
Group: None
Resolution: None
Initial Comment:
#
/usr/bin/make check-TESTS
#
make[4]: Entering directory
`/devel3/bdefreese/pulseaudio/libatomic-ops/libatomic-ops-1.2/tests'
#
Missing: AO_compare_double_and_swap_double
#
Missing: AO_compare_and_swap_double
#
Missing: AO_nop_acquire
#
Missing: AO_store_acquire
#
Missing: AO_short_store_acquire
#
Missing: AO_char_store_acquire
#
Missing: AO_int_store_acquire
#
Missing: AO_compare_double_and_swap_double_acquire
#
Missing: AO_compare_and_swap_double_acquire
#
Missing: AO_nop_release
#
Missing: AO_load_release
#
Missing: AO_short_load_release
#
Missing: AO_char_load_release
#
Missing: AO_int_load_release
#
Missing: AO_compare_double_and_swap_double_release
#
Missing: AO_compare_and_swap_double_release
#
Missing: AO_store_read
#
Missing: AO_short_store_read
#
Missing: AO_char_store_read
#
Missing: AO_int_store_read
#
Missing: AO_compare_double_and_swap_double_read
#
Missing: AO_compare_and_swap_double_read
#
Missing: AO_load_write
#
Missing: AO_short_load_write
#
Missing: AO_char_load_write
#
Missing: AO_int_load_write
#
Missing: AO_compare_double_and_swap_double_write
#
Missing: AO_compare_and_swap_double_write
#
Missing: AO_compare_double_and_swap_double_full
#
Missing: AO_compare_and_swap_double_full
#
Missing: AO_nop_release_write
#
Missing: AO_load_release_write
#
Missing: AO_short_load_release_write
#
Missing: AO_char_load_release_write
#
Missing: AO_int_load_release_write
#
Missing: AO_compare_double_and_swap_double_release_write
#
Missing: AO_compare_and_swap_double_release_write
#
Missing: AO_nop_acquire_read
#
Missing: AO_store_acquire_read
#
Missing: AO_short_store_acquire_read
#
Missing: AO_char_store_acquire_read
#
Missing: AO_int_store_acquire_read
#
Missing: AO_compare_double_and_swap_double_acquire_read
#
Missing: AO_compare_and_swap_double_acquire_read
#
Testing add1/sub1
#
/bin/sh: line 4: 14267 Segmentation fault ${dir}$tst
#
FAIL: test_atomic
#
Missing: AO_nop_acquire
#
Missing: AO_store_acquire
#
Missing: AO_short_store_acquire
#
Missing: AO_char_store_acquire
#
Missing: AO_int_store_acquire
#
Missing: AO_nop_release
#
Missing: AO_load_release
#
Missing: AO_short_load_release
#
Missing: AO_char_load_release
#
Missing: AO_int_load_release
#
Missing: AO_store_read
#
Missing: AO_short_store_read
#
Missing: AO_char_store_read
#
Missing: AO_int_store_read
#
Missing: AO_load_write
#
Missing: AO_short_load_write
#
Missing: AO_char_load_write
#
Missing: AO_int_load_write
#
Missing: AO_nop_release_write
#
Missing: AO_load_release_write
#
Missing: AO_short_load_release_write
#
Missing: AO_char_load_release_write
#
Missing: AO_int_load_release_write
#
Missing: AO_nop_acquire_read
#
Missing: AO_store_acquire_read
#
Missing: AO_short_store_acquire_read
#
Missing: AO_char_store_acquire_read
#
Missing: AO_int_store_acquire_read
#
Testing add1/sub1
#
Succeeded
#
Testing store_release_write/load_acquire_read
#
/bin/sh: line 4: 14272 Segmentation fault ${dir}$tst
#
FAIL: test_atomic_pthreads
#
About 100 pushes + 100 pops in 1 threads: 210 msecs
#
About 100 pushes + 100 pops in 2 threads: 190 msecs
#
About 100 pushes + 100 pops in 3 threads: 280 msecs
#
About 100 pushes + 100 pops in 4 threads: 190 msecs
#
PASS: test_stack
#
Performing 1000 reversals of 1000 element lists in 10 threads
#
Testing AO_malloc/AO_free
#
/bin/sh: line 4: 14280 Segmentation fault ${dir}$tst
#
FAIL: test_malloc
#
===
#
3 of 4 tests failed
#
===
#
make[4]: *** [check-TESTS] Error 1
Disable the make check in debian/rules does allow the package to build.
--
>Comment By: Samuel Thibault (sthibault)
Date: 29/12/2017 18:02
Message:
There is no failure any more
--
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=310484&group_id=30628
[debian-hurd-Bugs][310627] [test-suite] liboil: illegal instruction in mmxCombineAddU
debian-hurd-Bugs item #310627 was changed at 29/12/2017 18:03 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=310627&group_id=30628 >Status: Closed Priority: 3 Submitted By: Michael Banck (mbanck) Assigned to: Nobody (None) Summary: [test-suite] liboil: illegal instruction in mmxCombineAddU Category: test suite Group: None Resolution: None Initial Comment: /usr/bin/make check-TESTS make[5]: Entering directory `/build/buildd/liboil-0.3.13/testsuite' OIL: ERROR liboiltest.c 361: oil_test_check_impl(): illegal instruction in mmxCombineAddU -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:03 Message: This was removed from Debian -- Comment By: Samuel Thibault (sthibaul-guest) Date: 01/03/2008 00:18 Message: It looks like this is just because liboil uses SSE instructions even on non-SSE-capable processors... -- Comment By: Samuel Thibault (sthibaul-guest) Date: 29/02/2008 02:41 Message: Oh, maybe that's an alignment problem. Could you check that the first parameter of the function is aligned on 0x10? I'm currently fixing libpthread into making sure this is the case. -- Comment By: Samuel Thibault (sthibaul-guest) Date: 29/02/2008 01:40 Message: I've no problem here, could you check that the kernel messages contain "Enabling FXSR"? Does Beethoven support XMM? -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=310627&group_id=30628
[debian-hurd-Bugs][310629] dbus doesn't want to start
debian-hurd-Bugs item #310629 was changed at 29/12/2017 18:03 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=310629&group_id=30628 >Status: Closed Priority: 3 Submitted By: Samuel Thibault (sthibaul-guest) Assigned to: Nobody (None) Summary: dbus doesn't want to start Category: None Group: None Resolution: None Initial Comment: Setting up dbus (1.1.20-1) ... The system user `messagebus' already exists. Exiting. Reinstalling init script for new runlevels and priorities ... * Can't start system message bus - /proc is not mounted Should see why on earth dbus needs /proc, and fix it. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:03 Message: This seems to have been fixed -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=310629&group_id=30628
[debian-hurd-Bugs][311674] mkfs does not create filesystems with proper creator-os
debian-hurd-Bugs item #311674 was changed at 29/12/2017 18:04 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311674&group_id=30628 >Status: Closed Priority: 3 Submitted By: Marc Dequènes (duck) Assigned to: Nobody (None) Summary: mkfs does not create filesystems with proper creator-os Category: None Group: None Resolution: None Initial Comment: After a successful mkfs.ext2 /dev/hd1s: Earendil:~# mount /data ext2fs: /dev/hd1s1: panic: get_hypermetadata: inode size 256 isn't supported mount: cannot start translator /hurd/ext2fs: Translator died I had to recreate it using -o hurd to get it working. It is obvious this option is needed on GNU/Linux, but not on Hurd. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:04 Message: This has been fixed some time ago -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311674&group_id=30628
[debian-hurd-Bugs][311679] [test suite] apr
debian-hurd-Bugs item #311679 was changed at 29/12/2017 18:05 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311679&group_id=30628 >Status: Closed Priority: 3 Submitted By: Marc Dequènes (duck) Assigned to: Nobody (None) Summary: [test suite] apr Category: test suite Group: None Resolution: None Initial Comment: shm and other failures. tests have been disabled in the package on debian-ports. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:05 Message: These have been fixed. Some socket errors remain, but they are not fatal -- Comment By: Marc Dequènes (duck) Date: 21/05/2009 10:29 Message: More details : testprocmutex : Line 128: Locks don't appear to work Line 128: Locks don't appear to work Line 128: Locks don't appear to work FAILED 3 of 3 testshm : Line 152: expected <100>, but saw <0> FAILED 1 of 6 -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311679&group_id=30628
[debian-hurd-Bugs][311680] [test suite] apr-util
debian-hurd-Bugs item #311680 was changed at 29/12/2017 18:06 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311680&group_id=30628 >Status: Closed Priority: 3 Submitted By: Marc Dequènes (duck) Assigned to: Nobody (None) Summary: [test suite] apr-util Category: test suite Group: None Resolution: None Initial Comment: testdbd : /bin/bash: line 2: 9825 Segmentation fault (core dumped) LD_LIBRARY_PATH="`echo "../dbd/.libs:../ldap/.libs:$LD_LIBRARY_PATH" | sed -e 's/::*$//'`" ./$prog Failed to load driver file apr_dbd_sqlite2.so -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:06 Message: This got fixed some time ago -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311680&group_id=30628
[debian-hurd-Bugs][311687] apr/apr-util error when starting apache2
debian-hurd-Bugs item #311687 was changed at 29/12/2017 18:08 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311687&group_id=30628 >Status: Closed Priority: 1 Submitted By: Marc Dequènes (duck) Assigned to: Nobody (None) Summary: apr/apr-util error when starting apache2 Category: None Group: None Resolution: None Initial Comment: When starting the apache2 daemon, you can see the following message: [Sun May 17 15:32:25 2009] [warn] (os 0x3ff503aa)Unrecognized resolver error: Failed to enable APR_TCP_DEFER_ACCEPT Nevertheless, apache2 is working like a charm. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:08 Message: This doesn't seem to happen any more -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=311687&group_id=30628
[debian-hurd-Bugs][302425] xkb console driver has syntax error on keycodes/xfree86
debian-hurd-Bugs item #302425 was changed at 29/12/2017 18:07 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=302425&group_id=30628 >Status: Closed Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: xkb console driver has syntax error on keycodes/xfree86 Category: None Group: None Resolution: None Initial Comment: package: console-driver-xkb 0.008-6 The xkb console driver fails to parse keycodes/xfree86 (which it reads by default). The offending lines are 335 and 336. alias = ; alias = ; This is because of the + and - characters inside the keycode. Marco says that the regular expression needs to be changed to include those characters. The original regex looks like: KEYCODE "<"[A-Z][A-Z0-9]*">" This can be changed to something like: KEYCODE "<"[A-Z][-+A-Z0-9]*">" Can someone provide an experimental console-driver-xkb package, so I can test it? Thanks, bing -- Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:07 Message: This got fixed upstream -- Comment By: Thomas Schwinge (tschwinge-guest) Date: 28/10/2006 18:25 Message: Applying such a change and rebuilding the package and starting the console again yields the next follow-up problem: #v+ types/level5:17: syntax error [...] #v- Line seventeen of `/usr/share/X11/xkb/types/level5' looks like this: ``map[LevelFive] = Level5;''. It seems that this `LevelFive' is not supported with the current code. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=302425&group_id=30628
[debian-hurd-Bugs][302425] xkb console driver has syntax error on keycodes/xfree86
debian-hurd-Bugs item #302425 was changed at 29/12/2017 18:07 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=302425&group_id=30628 Status: Open Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: xkb console driver has syntax error on keycodes/xfree86 Category: None Group: None Resolution: None Initial Comment: package: console-driver-xkb 0.008-6 The xkb console driver fails to parse keycodes/xfree86 (which it reads by default). The offending lines are 335 and 336. alias = ; alias = ; This is because of the + and - characters inside the keycode. Marco says that the regular expression needs to be changed to include those characters. The original regex looks like: KEYCODE "<"[A-Z][A-Z0-9]*">" This can be changed to something like: KEYCODE "<"[A-Z][-+A-Z0-9]*">" Can someone provide an experimental console-driver-xkb package, so I can test it? Thanks, bing -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:07 Message: This got fixed upstream -- Comment By: Thomas Schwinge (tschwinge-guest) Date: 28/10/2006 18:25 Message: Applying such a change and rebuilding the package and starting the console again yields the next follow-up problem: #v+ types/level5:17: syntax error [...] #v- Line seventeen of `/usr/share/X11/xkb/types/level5' looks like this: ``map[LevelFive] = Level5;''. It seems that this `LevelFive' is not supported with the current code. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=302425&group_id=30628
[debian-hurd-Bugs][312550] *** glibc detected *** /usr/bin/perl: free(): invalid pointer: 0x01026000 ***
debian-hurd-Bugs item #312550 was changed at 29/12/2017 18:17 by Samuel Thibault You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=312550&group_id=30628 Status: Open Priority: 3 Submitted By: Samuel Thibault (sthibault) Assigned to: Nobody (None) Summary: *** glibc detected *** /usr/bin/perl: free(): invalid pointer: 0x01026000 *** Category: None Group: None Resolution: None Initial Comment: a few perl applications, perldoc notably, crash with *** glibc detected *** /usr/bin/perl: free(): invalid pointer: 0x01026000 *** This is in perl_destruct: for (i = 0; environ[i]; i++) safesysfree(environ[i]); /* Must use safesysfree() when working with environ. */ safesysfree(environ); It's trying to free the environ that glibc has settled. This part of the perl code really looks like black magic to me, I guess the hurd part of glibc is even darker. This seems to happen only within a fakeroot-tcp session. -- >Comment By: Samuel Thibault (sthibault) Date: 29/12/2017 18:17 Message: FTR, here is the upstream bug url: http://rt.perl.org/rt3/Ticket/Display.html?id=91452 -- Comment By: Samuel Thibault (sthibault) Date: 09/04/2011 15:55 Message: Upstream bug reported upstream. Actually a bad interaction of perl's assumption that nobody calls putenv and can thus tinker with it, and libfakeroot which actually calls putenv. -- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=312550&group_id=30628
