Hi!
Just to be clear: The manpage of [file delete] states that
> Trying to delete a non-existent file is not considered an error.
see https://www.tcl.tk/man/tcl8.6/TclCmd/file.htm#M12
or, the Wiki states that
> If pathname is a non-existent file, nothing is done and it is not an
error.
see ht
Hi Héctor,
Thx for reporting. I prepared 2.1.0-4 plus an autopkgtest to prevent
such troubles in the future. Upload is requested.
All the best,
Stefan
> After reinstalling again, the duplicity is gone, most probably a local
> issue.
>
> The issue with "package req xotcl::serializer" persists, t
Hi Chris!
>> Would you consider applying this patch and uploading?
>
> Friendly ping on this :)
I prepared an package revision incl. a variant of the patch, and already
asked for upload.
Sry for the long'ish delay.
Stefan
My apologies:
> ...
> foreach {f fb} [lsort $fileList] {
> ...
The correct patch is:
...
foreach {f fb} [lsort -stride 2 $fileList] {
...
(assuming it is correct to assume Tcl 8.6 to be the default build-dep).
Stefan
> is it in svn
it is at the tip of the svn trunk.
thank you!
//stefan
Hi Chris,
> ie. src:nfs is currently reproducible on all our platform/dist combinations.
> Hope that helps. :)
Thank you, this is re-assuring!
Stefan
Hi all,
>> But then I discovered that due to the
>> > still unfixed #821962 xotcl is already on the list of to be removed
>> > packages.
>> > Since I use neither xotcl nor aolserver I would currently refrain
>> > from trying to support unmaintained packages further. But I'm putting
>> > Stefan on
Hi Chris,
Hi Sven,
Thanks for re-entering me into the loop. I am afraid, I don't know why,
but I have never received any mailing list emails. Just checked my
archive. I would have acted earlier (I am not checking the PTS sites
regularly, should have probably.)
>> There hasn't seem to be any updat
Thx for this help! Did you test on the very same buildd/porterbox
which reports the issue: hasse.debian.org; or any other armhf/mipsel
box?
I don't have access to the autobuilders, on which logins are restricted
to their actual maintainers. Rather, my test builds were on
harris.debian.org (armh
Thx for this help! Did you test on the very same buildd/porterbox
which reports the issue: hasse.debian.org; or any other armhf/mipsel
box?
I don't have access to the autobuilders, on which logins are restricted
to their actual maintainers. Rather, my test builds were on
harris.debian.org (armh
Hi Aaron!
How can I best simulate the environment at the buildd box? Is there a
chance to obtain a core dump from the buildd box, alternatively?
I'm not aware of a way to get core dumps off of autobuilders, though
perhaps if you asked their maintainers nicely, they might be able to
help you ou
> Builds of nsf on Linux architectures failed with test suite errors, of
> two types. (There was also a kFreeBSD failure, which I'll report
> separately.)
>
> On armhf and mipsel, the linearization test segfaults when done:
We will certainly look at these a.s.a.p.
I tried to reproduce the
> On the remaining Linux architectures, the http test times out, perhaps
> due to idiosyncracies of buildd network configuration:
> !!!::req1 (2): Connection refused by host 'localhost' port '8086'
> error flushing "sock949f8a8": socket is not connected!!!
> xocomm/test.001: incorrect result
Hi Aaron!
Thx for reporting, I had already noticed the failing builds.
> Builds of nsf on Linux architectures failed with test suite errors, of
> two types. (There was also a kFreeBSD failure, which I'll report
> separately.)
>
> On armhf and mipsel, the linearization test segfaults when done:
Package: wnpp
Severity: wishlist
Owner: Stefan Sobernig
* Package name: nsf
Version : 2.0b6
Upstream Author : Stefan Sobernig
* URL : http://next-scripting.org/
* License : MIT
Programming Lang: C, Tcl
Description : The Next Scripting Framework (for
Sven,
I refrain from uploading that right now, in case you can come up with
something more appropriate.
Sven,
I refrain from uploading that right now, in case you can come up with
something more appropriate.
I was desperately looking for the quirk in the source package, only to
find out in th
Sven,
Thx for taking of uploading!
Uploaded but it FTBFS.
Yes, there are several .o and .so files left over by the build system.
Until that's fixed I could offer a very quick and ugly workaround (attached).
I refrain from uploading that right now, in case you can come up with
something more
Alex, Moritz,
Moritz is actually right, your --with-expat=sys is a mere placebo
treatment. this flag has just been added to the xotcl build system in
response to the debian security bulletins. the upcoming 1.6.6 release
provides support for shared expat. i hope that the upstream release will
Package: wnpp
Severity: wishlist
Owner: Stefan Sobernig <[EMAIL PROTECTED]>
* Package name: xotcl
Version : 1.6.0+
Upstream Author : Gustaf Neumann <[EMAIL PROTECTED]>, Uwe Zdun <[EMAIL
PROTECTED]>
* URL : http://www.xotcl.org/
* License :
19 matches
Mail list logo
