Il 17/05/2013 16:57, Ralf Treinen ha scritto:
This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS
Fixed in 3.2.4-1, please close.
Paolo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
upstream release 3.2.1 added a 1-minute timeout to all tests. This will
at the very least change the infinite loop into a failure and will
possibly show other failures.
The relevant commit is 06d7a0f2b5faea40ea8701b8772d8ef0841766bd.
On 04/15/2010 10:06 AM, Lucas Nussbaum wrote:
Source: gnu-smalltalk
Version: 3.1-3
Severity: serious
Tags: squeeze sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20100415 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build
121: Sport FAILED (testsuite.at:159)
122: Swazoo FAILED (testsuite.at:160)
Fixed by upstream patches
482e75acb44fcf652f29f21bb541e4b00ad5ba52
3d09834cf13e5b21b99e53c18bdac6806de9f4ab
ssed was a kind of experimentation ground for what became sed 4.0. If
you want to drop it altogether fine, but if not the NMU should really be
done to close this release criteria bug.
Paolo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
I don't recall if I already posted this; fixed upstream by commit 232557c9.
Paolo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.
fixed by the upstream patch 232557c9e5a24f5dbd18ad9a2106cafb74e4e0cf
Paolo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On 10/15/2009 02:41 PM, WANG Yunfeng wrote:
Package: sed
Version: 4.2.1-3
Severity: critical
Justification: breaks unrelated software
I applied the patch upstream, thanks.
Paolo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
I cannot reproduce the cobjects.st failure using the included libffi.
Paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Oops, sorry, I was using a -O0 binary. I can reproduce it now. The fix
will go upstream.
Paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Reduced testcase (reproducing on testdrive):
Object extend [
breakIt: anInteger [
category: 'instance creation'
1 to: anInteger do: [ :each | String new: each ].
]
]
#(4450 2) do: [:each | self breakIt: each].
Can you confirm? (Just do ./gst foo.st where foo.st is the
It's a dangling pointer that for no reason should show up rarely, and
for no reason should show up only on ia64, but it does.
Anyway the attached patch, which I'll commit upstream after some more
testing, fixes it. The idea is that a nomemory hook is now able to
divert the allocation to another
-result = 7.70
+result = 2305843009213693952.00
Will try to make a standalone testcase.
./testsuite.at:159: exit code was 139, expected 0
Can you get a backtrace (e.g. from a coredump)?
Paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Philipp Kern wrote:
On Fri, Sep 19, 2008 at 04:01:04PM +0200, Paolo Bonzini wrote:
-result = 7.70
+result = 2305843009213693952.00
Will try to make a standalone testcase.
./testsuite.at:159: exit code was 139, expected 0
Can you get a backtrace (e.g. from a coredump)?
If you tell
Philipp Kern wrote:
On Fri, Sep 19, 2008 at 05:58:39PM +0200, Paolo Bonzini wrote:
./libtool *copy_arguments_from_above* gdb --args gst -f scripts/Test.st
-vp Swazoo
gdb refuses to provide a backtrace, sadly:
what about a core dump (ulimit -c unlimited, then tests/gst -f
scripts/Test.st -vp
Thomas Girard wrote:
Hello,
Le mardi 22 avril 2008 à 13:15 +0200, Paolo Bonzini a écrit :
It might be that rebuilding fixes the failure. I saw random failures of
Swazoo here too, it might be a race condition or something like that.
Paolo, could this error be fixed by the patch[1]?
Regards
It might be that rebuilding fixes the failure. I saw random failures of
Swazoo here too, it might be a race condition or something like that.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
| config.status: linking ./src/ia64/ffitarget.h to include/ffitarget.h
| config.status: error: ./src/ia64/ffitarget.h: file not found
| configure: error: ./configure failed for libffi
| make: *** [configure-stamp] Error 1
The libffi/src/ia64/ffitarget.h is indeed missing in the smalltalk
19 matches
Mail list logo
