Thomas Dickey dixit:
Without some charset in the document, or override via command-line or lynx
configuration, the file will be treated as ISO-8859-1. He seems to be
expecting lynx to treat it as UTF-8.
I think this is what recent (X)HTML/HTTP standards assume as well.
This is the reason I
Atsuhito Kohda dixit:
aqwa『~』$ lynx.cur --dump test.html
* é
*
This is very interesting:
[EMAIL PROTECTED]:~ $ lynx -dump test.htm
* é
* �
[EMAIL PROTECTED]:~ $ lynx -version
Lynx Version 2.8.7dev.9 (27 Apr 2008)
libwww-FM 2.14, SSL-MM 1.4.1, ncurses 5.6.20080830(wide)
tags 492377 + help
reassign 492377 qa.debian.org
thanks
dann frazier dixit:
Function `strcasestr' implicitly converted to pointer at ] scn.c:4
I suggest you read your eMail INBOX, as I already wrote to you in
Message-ID: [EMAIL PROTECTED]
that this is a FALSE POSITIVE and that I request help
dann frazier dixit:
but mksh cannot release until it is fixed somehow
Hm okay.
I don't have any good solutions in mind
Good, then I might try some workaround against the regex matcher. Can a
non-DD get access to an IA64 test machine, or can I send a beta package
for testing and NOT uploading
Hi!
implicit_pattern = re.compile(([^:]*):(\d+): warning: implicit declaration …
I think that a simple addition to the already-existing sed command, like
s/^[^:]*:[0-9]*:/config test;/ (which I did in mksh-35.2-2, pending to be
uploaded by my sponsor¹) should avoid your script to be triggered.
Luk Claes dixit:
Why did you restrict the build dependency on dietlibc to a whole list of
architectures?
This is the list of architectures dietlibc exists on (taken from its
debian/control file, copied verbatim).
On architectures without dietlibc, mksh-static is statically linked
against glibc
tags 499139 +help
thanks
Hi,
I verified #499139 with mksh, pdksh and – interestingly enough – ATT ksh93
on Debian GNU/Linux testing/unstable.
I wonder if the file descriptor magic of debconf is at fault here instead,
as, usually, the ksh93 behaviour is “right”.
As I barely know debconf at all,
retitle 499139 Possible problem with debconf and Korn shell interaction?
thanks
.oO(Agustin, your first two retitles didn’t work ☺)
For what it’s worth: You wrote…
I have done further research on this and the result follows:
GOOD: bash, dash, posh, pdksh
BAD: ksh, mksh
BAD2: zsh
[…]
For this
Agustin Martin dixit:
I may have messed up the names with all the sh changes.
I just changed the shebang lines instead ;)
Note /bin/ksh is a symbolic link, thus shouldn't be needed to be tested.
The simple way to keep everybody joined is to abuse he BTS, reassigning bug
report to e.g.
Agustin Martin dixit:
/bin# ln -sf pdksh sh
and keep the shebang lines pointing to /bin/sh the test script runs (no hang
and no error signalled, even with '-e' flag enabled in both scripts, and the
right return value shown). However, if I explicitly change the shebang lines
scripts seem to
tags 499139 -help +upstream +confirmed
thanks
This seems to be related to #154540 – found after I got the information
that it only happens to pdksh with FSH not set.
Would a fix for this bug be worth a freeze exception? Otherwise, I’ll
just fix it upstream, and the Debian package would be
restricted
The shell is a restricted shell.
This option can only be used when the shell is invoked.
@@ -5525,7 +5532,7 @@ and many other persons, and is currently
.An Thorsten Glaser Aq [EMAIL PROTECTED] .
.Sh BUGS
This document attempts to describe
-.Nm mksh\ R35
+.Nm mksh\ R35c
and up
Robert Luberda dixit:
However I have never checked if it's true that POSIX doesn't specify what
happens in this case. But if it is, debconf should be fixed not to use
such constructions, I think.
Right. Many people assume POSIX shells are similar to Bourne shells, but
the Korn shells often
Package: wnpp
Severity: wishlist
Owner: Thorsten Glaser [EMAIL PROTECTED]
* Package name: libbsd-arc4random-perl
Version : 1.30
Upstream Author : Thorsten Glaser [EMAIL PROTECTED]
* URL : http://www.mirbsd.org/man3/arc4random
* License : MirOS Licence (same
Package: lintian
Version: 1.24.2.1
Severity: wishlist
#!/bin/mksh is not recognised by lintian yet. Please refer to the mksh package
for a candidate.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux
Package: lintian
Version: 1.24.2.1
Severity: normal
W: mircpio: manpage-has-errors-from-man usr/share/man/man1/mircpio.1.gz list
open at EOF! A .Bl directive has no matching .El
I’ve got three manpages in mdoc(7) format with this error now. All of
them are valid (at least I think so), but
reassign 498082 man-db
thanks
Russ Allbery dixit:
The error message is coming from man --warnings. It's possible that it
may have some sort of problem. Can you double-check first that you have
the most current man-db package? If so, I'll transfer the bug there.
Oh okay. Sure.
ii man-db
Colin Watson dixit:
Please note that man-db is almost never the real source of this kind of
bug
Okay, I did not know which of the many components may be the source.
if you think the warning is incorrect, please reassign to
groff-base, not to man-db. (I've reassigned this one.)
Thanks.
Could
Colin Watson dixit:
Heh, you managed to find a case where it actually *was* a man-db bug
after all! I did say almost never, I guess ...
Happens ;-)
This is triggered by your use of UTF-8 characters that aren't just
recoded versions of ISO-8859-1 characters in comments at the top of the
manual
Colin Watson dixit:
would mean that line/byte numbers would be wrong, which could be
confusing.
They are wrong anyway, as the macro packages count for byte numbers
too, at least in the iconv example. But still a point: we could just
wc the macro package first.
mdoc; docj.tmac still has it,
Hi,
with the upload of mksh-30.1-1, no further action is needed, since it will
not define the “stop” alias any more if called as /bin/sh. You therefore
might want to close this bug report.
On the other hand, other Korn shells – most prominently, pdksh – probably
will still define this alias, so
Martin,
can I use the account on the Alpha you gave me now to test this?
Last time I tried it still did not work (you said something like
the sid dchroot being broken). I have no other way to check that,
and I didn't get real instructions how to reproduce it on non-
alpha from that SuSE guy
I have an idea…
Dixi:
Martin Zobel-Helas dixit:
/usr/include/sys/stat.h:217: error: conflicting types for 'stat'
/usr/include/sys/stat.h:365: error: previous definition of 'stat' was here
[...]
Sounds like a bug in the header file to me:
215 extern int __REDIRECT_NTH (stat, (__const
This version was uploaded to 'experimental' exactly to find out
possibly portability problems, e.g. with kfreebsd and hurd ;)
So I suppose that was a good move.
Martin Zobel-Helas dixit:
/usr/include/sys/stat.h:217: error: conflicting types for 'stat'
/usr/include/sys/stat.h:365: error:
Package: freebsd-utils
Version: 6.2-3
Severity: important
Tags: patch
A few scripts from freebsd-utils contain calls that are not
pure bourne/posix shell, namely:
[EMAIL PROTECTED]:~ # fgrep -nr 'exec -a' /bin /sbin
Package: lynx-cur
Version: 2.8.7dev4-2
Severity: wishlist
lynx currently has issues with pages with non-ASCII characters on an
unicode capable terminal (which, for me, is uxterm running on my laptop,
ssh'ing into the Debian system), most prominently www.google.co.jp
Linking with libncursesw and
Cyril Brulebois dixit:
IMHO fixing is better than workarounding. Using a bash shebang would add
an (otherwise) unnecessary Depends:
In Debian, it would not, because /bin/bash is, at the moment, required to
be always there.
and having POSIX-compliant scripts sounds *much* better to me.
Same for
Package: module-init-tools
Version: 6.2-3
Severity: grave
Justification: renders package unusable
S20module-init-tools calls '... | sort | uniq' but is run at a time
during bootup where /usr is not yet mounted, and sort and uniq are,
obviously, not available yet:
[EMAIL PROTECTED]:~ # whence -p
Package: sendmail-bin
Version: 8.14.1-2
Severity: important
The postinst script contains a shell function stop () { ... }
but this fails when using a Korn shell as /bin/sh, because it
is normally defined as shell alias:
$ for a in ash bash dash mksh pdksh ksh93 zsh; do env me=$a $a -c 'stop () {
Package: module-init-tools
Version: 6.2-3
Severity: normal
S20module-init-tools uses shopt which is only supported by bash.
Either rewrite* the code in question to use only portable shell
idioms (preferred), or change the shebang line to #!/bin/bash instead,
as per Debian policy that /bin/sh
Package: net-tools
Version: 6.2-3
Severity: minor
cosmetic: when doing an ifdown -a, the following message occurs:
ifconfig: invalid option -- i
usage: ifconfig [-L] [-C] interface address_family [address [dest_address]]
[parameters]
ifconfig interface create
Marco d'Itri dixit:
On May 15, Thorsten Glaser [EMAIL PROTECTED] wrote:
Package: module-init-tools
Version: 6.2-3
Why do I keep receiving bugs for a kfreebsd-i386 package which I do not
maintain?
No idea, in this case I suspect there are two different packages with
the same name. (I thought
Package: slapd
Version: 2.3.30-5
Severity: important
Tags: patch
Hi,
I've reported a similar bug to the sendmail-bin postinst script
some time ago, you'll find it at
| http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424213
for reference and deeper information.
The script defines a shell
Package: nscd
Version: 2.3.6.ds1-8
Severity: important
Tags: patch
Hi,
I've reported a similar bug to the sendmail-bin postinst script
some time ago, you'll find it at
| http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424213
for reference and deeper information.
The script defines a shell
unblock 408850 by 412070
thanks
I'd recommend forwarding this to upstream, it doesn't seem to be Debian
or Alpha specific. Unblocking from the Alpha issue and /delurk.
I hope someone knowledgeable about gcc and on good terms with the SC
can get this fixed.
bye,
//mirabile
--
I believe no one
Pierre Habouzit dixit:
exists, so it's definitely a ksh only issue, and is not worth a stable
update.
The fix will appear in the soon to be uploaded 2.6 packages though.
That is okay, as mksh only offers to be used as /bin/sh via debconf
in the package currently in unstable, and the other
Hi,
wouldn't it be possible to at least make the en_US.UTF-8 locale forcibly
generated, so that it can't be deselected by dpkg-reconfigure locales?
If this one isn't installed, many apps break when I ssh from an OS that
uses exclusively UTF-8 to a Debian box.
Thanks!
//mirabile
--
I believe no
martin f krafft dixit:
Why en_US? Why not en_GB?
Because how many applications come with en_US data files and how
many speak proper English? I know it's sad, but it happens to be
like this.
If this one isn't installed, many apps break when I ssh from an OS that
uses exclusively UTF-8 to a
martin f krafft dixit:
also sprach Thorsten Glaser [EMAIL PROTECTED] [2007.06.16.1323 +0100]:
Funnily I cannot if I'm not root. And I've seen etch boxen where
en_US.UTF-8 was not installed.
Then please bug the admin.
That's what I did, but the idea is not to have to do that. (Besides,
C
martin f krafft dixit:
Please stop CCing debian-project.
I don't.
Does a C.UTF-8 exist? If yes, then this is a sound proposal,
I think.
If not, one could probably easily create one. It would have to
have all properties of C except for LC_CTYPE, which it would
have to take from en_US.UTF-8.
Roger Leigh dixit:
Does a C.UTF-8 exist? If yes, then this is a sound proposal,
I think.
I believe that the C locale is supposed to be US_ASCII only.
That applies to “C” but not to a hypothetical “C.UTF-8” locale,
which would have to be set via setlocale(3) anyway, and differ
from “C” only in
Sven Joachim dixit:
Package: mksh
Version: 29.2-1
Severity: grave
Your package depends on libssp0 which is no longer present in the
latest gcc-4.1 upload (4.1.2-4).
Why is that library gone and/or how is ProPolice SSP in gcc 4.1+ then
supposed to work without it?
If the __guard_setup() and
block 421518 by 408850
thanks
Falk Hueffner dixit:
/usr/include/sys/stat.h:208: error: conflicting types for 'stat'
/usr/include/sys/stat.h:435: error: previous definition of 'stat' was here
[...]
Full log at
unblock 421518 by 408850
reassign 408850 gcc
retitle 408850 using flags -fwhole-program --combine broken
thanks
Hi all,
thanks to Steve Langasek I now know that the “conflicting prototypes” issues
for the mksh package appear due to use of the gcc flags “-fwhole-program
--combine” which,
Mike Hommey dixit:
it's not. We could create a neutral.utf-8 locale for sure
Sounds like a plan. Maybe something short and uppercase, akin to
C and POSIX, how about STD.UTF-8?
but a
C.utf-8 is really bad, because some programs check the locale for 'C'
and when they foind that use hand
Package: openssh-server
Version: 1:4.6p1-1
Severity: grave
Justification: renders package unusable
After upgrading to latest unstable today, I couldn't start
sshd any longer. Find below a typescript showing the issues:
[EMAIL PROTECTED]:~/tmp # /usr/sbin/sshd
/usr/sbin/sshd[1]: syntax error: '('
Package: debianutils
Version: 2.21
Followup-For: Bug #340219
While I'm in favour of #428189 too (you by the way forgot to mention
that, if printf is moved to /bin, we need a /usr/bin/printf symlink
to not break POSIX or existing scripts), there's a way to solve this
issue for Korn shells, which
Okay, I've found out more about the cause:
sshd is compiled as PIE (position independent executable), but only
Linux, NetBSD and MirBSD can execute them; FreeBSD, OpenBSD and
DragonflyBSD cannot. (The DragonFly gcc ignores -pie because it
knows that its kernel can't execute them anyway.)
So the
Aurelien Jarno dixit:
Thorsten Glaser a C)crit :
Could you give us more details?
Sure, these are however also in the PR.
What problem do you get with this binary?
It's not executable.
Which architecture are you
kfreebsd-i386
And which kernel are you using?
Both 5.4 and 7.0 show the bug
close 430455
thanks
Aurelien Jarno dixit:
An upgrade to a 6.1 kernel may fix the bug.
It did. So the bug is closed for openssh.
How about, we either nuke the 5.4 and 7.0 kernels, or fix them too,
so that no other user will experience this problem?
bye,
//mirabile
--
I believe no one can
Hi Colin,
sorry I didn't know that the close command is deprecated.
As for the PIEs, kFreeBSD 6.x kernel has gained a patch to support
executing PIEs some time ago (since I only tested 5.4 and 7.0 I had
not known that, plus I'm not exactly a heavy Debian user...), and
they backported the fix to
Tomas Pospisek dixit:
in the description s/si- milar/similar/
Are we not allowed to wrap the text then?
I will fix it with the next release which is due soon.
Thanks,
//mirabile
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God
Package: gforge-common
Version: 4.5.14-22etch2
X-Debbugs-CC: [EMAIL PROTECTED]
GForge (I did not exactly know which subpackage, so I filed
against gforge-common) produces a huge lot of warnings, so
that our log files get pretty large:
-rw-r- 1 root adm 2136984104 2008-07-09 21:15
tags 477587 + patch
tags 477588 + patch
thanks
FWIW, both “bashisms” work with mksh ☺
Untested diff below:
Index: kfreebsd-6/debian/rules
===
--- kfreebsd-6/debian/rules (revision 2166)
+++ kfreebsd-6/debian/rules (working
Hi,
the behaviour you describe is normal for any Korn shell, since the idioms
you are trying to use are GNU bash extensions.
Instead of
export PS1='\033[0;[EMAIL PROTECTED] \033[0;33m\w\033[0;39m
$ '
you should use this (the lines 2 and 3 have a tab and a space inside the []):
:
Package: mksh
Version: 33.1-2
Severity: minor
Tags: goal-dash, moreinfo
Owner: [EMAIL PROTECTED]
Hello!
I just saw the following:
# Switch /bin/sh to dash
Advocate: Petter Reinholdtsen?
Release-Team-Contact: ??
Description: Make sure dash is installed and preseed debconf question.
Fix
Apparently, it has not been fixed with later runs:
$ lynx -dump http://packages.qa.debian.org/m/mksh.html
[…]
Overview of [4]mksh source package
General information
Latest version 37.3-2
Maintainer [5]Thorsten Glaser [6][email]
Maintenance[7]DMUA
Dixi quod:
(as stdin replacement)
More on this:
t...@frozenfish:~ $ mksh
t...@frozenfish:~ $ true x; echo $?
mksh: cannot open x: No such file or directory
1
t...@frozenfish:~ $ ^D
t...@frozenfish:~ $ bash
t...@frozenfish:~$ true x; echo $?
bash: x: No such file or directory
1
Clint Adams dixit:
% mksh /tmp/horsies ; echo $?
/tmp/horsies: /tmp/horsies: No such file or directory
1
t...@herc:~ $ mksh /tmp/horsies; print $?
/tmp/horsies: /tmp/horsies: No such file or directory
1
t...@herc:~ $ mksh -c /tmp/horsies; print $?
mksh:
Geoff Clare dixit:
Clint is right. Look at the synopsis for sh:
Okay, the HTML versions I had were not easy to search.
Then I’ll fix that in mksh, and Clint should file it
with dash too.
The Austin Group mailing list is open to anyone to join. See
www.opengroup.org/austin/lists.html
Thanks!
Geoff Clare dixit:
So the 127 exit is required for sh /tmp/horsies if /tmp/horsies could
not be found.
Heh. The source code even *tried* to DTRT, setting exstat to 127,
but the errorf() function doing the actual abortion set it to 1…
fixed.
//mirabilos
--
Yay for having to rewrite other
found 541535 binutils/2.19.91.20090927-1
thanks
Still there…
//mirabilos
--
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
-- Tonnerre Lombard in #nosec
--
To UNSUBSCRIBE, email to
tags 549179 wontfix
severity 549179 wishlist
thanks
Jari Aalto dixit:
mkdir tmp
mksh tmp
= No error messages, no status code $? to signify an error.
t...@herc:~ $ cat tmp; echo $?
0
t...@herc:~ $ mksh tmp; echo $?
0
This is consistent with the rest of the operating system,
ans as
Hi,
I had a good laugh reading the recent posh changelog entries.
Thanks for the appreciation of my patches, I wasn’t even aware
of it ;) In fact, you might want to take a lot more bugfixes
out of it; run our testsuite over it to see them (although it
does test for a lot more things, feature
22:37⎜mika:#grml this is so win² for FAI
:)
22:38⎜mika:#grml because if thomas finally learns git we finally get a chance
for its usage for FAI in the
⎜long run :)
22:38⎜lynx:#grml oh no…
22:39⎜* lynx:#grml should write git2cvs
Source: python2.6
Version: 2.6.6-7
Severity: normal
Hi,
please disable the profiled bootstrap of Python (any version, really)
on m68k. The process running the testsuite for the profile feedback
generation hangs at 0% CPU (and 0.00 load), and I had to kill it to
make the compilation continue.
Gosh, just hold Shift while pasting,
run mc with -d or inside GNU screen with disabled mouse support.
I suggest this be closed.
bye,
//mirabilos
--
ch you introduced a merge commit│mika % g rebase -i HEAD^^
mika sorry, no idea and rebasing just fscked │mika Segmentation
ch should have
Jonathan Nieder dixit:
This construct is also handy when one wants to update the current
environment downstream from some other process.
process |
while IFS= read -pr line; do
…
done
↑ is the proper ksh idiom for that.
( ... )- runs ... in a
Francesca Ciceri dixit:
w.r.t. the recent effort to revive the port and the progress about it).
I’ll write on that later. Just FYI that I saw it and will RSVP.
bye,
//mirabilos
--
ch you introduced a merge commit│mika % g rebase -i HEAD^^
mika sorry, no idea and rebasing just fscked
Raphael Hertzog dixit:
with concrete optimizations, a bug report saying it's slow is useless.
I never meant this as bug report, just a sort of heads-up. If it is
unfixable, unless things are rewritten in non-Perl, that’s the way
it is. But still, I see a lot of slowness when building packages on
Francesca Ciceri dixit:
Debian currently runs on the 68020, 68030, 68040 and 68060 processors.
Current Debian releases support Atari, Amiga, VMEbus, and some
Macintosh systems.
I’d keep the “Debian currently runs” but state that this is not in a
released version and hasn’t
Raphael Hertzog dixit:
But he provides patches from time to time so I have some hopes that it
means he's interested to look into the issue. :-)
Indeed ☺
It seems really that perl is just slow on your setup.
Yes, I thought so.
Maybe the calls to the various dpkg-* and dh* tools could use
cache
Guillem Jover dixit:
Your initial time showed 7s, but the profile shows only 2s, maybe
No, as I said, those are different machines (as I had already shut
down the slower VM).
bye,
//mirabilos
--
ch you introduced a merge commit│mika % g rebase -i HEAD^^
mika sorry, no idea and rebasing
Jonathan Nieder dixit:
save time on autobuilders.
Ah, I see it was already reported. Thanks, this should speed up
m68k builds a lot ☺
I wonder though, why is the BUILD_DOCS, install-indep-real, etc.
necessary, shouldn’t dpkg-buildpackage just call binary-arch and
that be it?
bye,
block 608476 by 603910
thanks
Daniel Schaal dixit:
kwalletcli should use the debian alternative system for kwalletaskpass and
provide ssh-askpass.
Do you think so? Okay, will do in time. Thanks for the patch!
bye,
//mirabilos
--
Support mksh as /bin/sh and RoQA dash NOW!
‣ src:bash (241 (259)
Jonathan Nieder dixit:
Background:
[…]
Thanks. Right, I remember not reading anything about
binary-{indep,arch} being mandated, only binary… damn.
And about make not being able to show whether a target
exists… well, I think this is also making dh7 slow.
Good to know / get a refresher.
bye,
/a, but
Working on it, new eglibc is compiling, thanks _again_
to Andreas Schwab. Maybe it helps, maybe it isn’t.
I think we shouldn’t hardcode such things on the main
website but refer to something like the as-of-yet not
created https://wiki.debian.org/M68k/Status instead.
+p
+Thorsten Glaser has
+
+ * debian/patches/add-{arc4random,mkstemp}: add a minimalistic
+implementation of the arc4random() API on top of jrand48(3)
+to have a self-seeding PRNG; add simple mkstemp(3) implemen-
+tation using it. (Closes: #516774)
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 28 Jan 2011 12:59:06
+ and TLS now; sanity checks were only disabled for linuxthreads)
+- use NPTL instead of linuxthreads
+ * debhelper.in/libc.preinst: require (Debian) 2.6.32 kernel on m68k
+
+ -- Thorsten Glaser t...@mirbsd.de Sat, 29 Jan 2011 00:37:03 +0100
+
eglibc (2.11.2-10) unstable; urgency=low
* Add
+0100
+++ klibc-1.5.21/debian/changelog 2011-01-29 15:48:04.0 +0100
@@ -1,3 +1,10 @@
+klibc (1.5.21-1+tg.2) unstable; urgency=low
+
+ * debian/patches/fix-m68k-syscalls: rewrite m68k syscall ABI
+to fix it (Closes: #334917) and support 6-argument syscalls.
+
+ -- Thorsten Glaser t
maximilian attems dixit:
well ok thanks for the effort, but please really do use git.
Ah okay. I worked against the Debian package, because that is
what I can test and install.
The klibc git repo is at
http://git.kernel.org/?p=libs/klibc/klibc.git;a=summary
git clone it and work away.
Will
Francesca Ciceri dixit:
I've dropped the 'current issues' part and not mentioned the
not-yet-created wiki.d.o/M68k/Status page: we could add this info when the
page will be created.
I’ve created it now and filled it with content; one of the issues has
already been fixed by Andreas Schwab (thanks
SIGSUSPEND(2) Linux Programmer's Manual SIGSUSPEND(2)
NAME
sigsuspend - wait for a signal
SYNOPSIS
#include signal.h
int sigsuspend(const sigset_t *mask);
… and …
SIGSUSPEND(2) BSD Programmer's Manual SIGSUSPEND(2)
NAME
Dixi quod…
root@ara2:~ # klcc -o tklibc t.c; gcc -o tglibc t.c; ./tklibc; ./tglibc
4
128
Hm. Apparently, it’s not that, because klibc appears to use the
old-style functions and old_sigset_t is a long, so okay. (And
no, it’s not related to that commit, 1.5.20 was broken too.)
strace ./mksh -c ls
Source: ruby1.9.1
Version: 1.9.2.0-2
Severity: important
Justification: fails to build from source
Hi,
log attached. Note ruby1.8 built just fine, and ruby1.9 used
to build on m68k but not ruby1.9.1 (it got TLS and eglibc in
the meantime, though).
2111 static void
2112
Hi,
with the latest developer news I saw mksh was listed. However, mksh
needs to have dependencies on debconf ($foo) | cdebconf ($bar) in
two flavours – one is added so lintian doesn’t complain due to mi-
nimum version requirements for certain features, the other is added
via misc:Depends from
Russ Allbery dixit:
that clearly, but I'm quite confident that's the intention.
Yes, thought so. However I was surprised to see it pop up in
the list, and perhaps other packages are similarly affected,
maybe not even this visible.
So what now? Does ftpteam read here or do I contact them, and
in God, just consider God as Nature if you won't deny
existence. -- Coywolf Qi Hunt
-- Forwarded message --
From: Thorsten Glaser t...@mirbsd.de
Message-ID: pine.bsm.4.64l.1101302028040.30...@herc.mirbsd.org
To: debian-...@lists.debian.org
Date: Sun, 30 Jan 2011 20:31:44
Hi,
for additional consideration of any solution: the current binary pak-
kage “mksh” comes with two shells “mksh” and “mksh-static”, and both
are suitable for use as /bin/sh (mksh-static even more so on ports
like m68k where the reduced startup time is noticeable).
So any solution should not
Andreas Schwab dixit:
It's a linker bug, see
http://sourceware.org/ml/binutils/2011-02/msg8.html.
I can confirm the fix.
root@ara2:~ # ./resinit; print $?;
LD_LIBRARY_PATH=/var/cache/pbuilder/build/cow.11168/tmp/buildd/eglibc-2.11.2/build-tree/m68k-libc
./resinit; print $?
Segmentation
Source: eglibc
Version: 2.11.2-11
Hi,
when building eglibc with --debbuildopts -B --binary-arch, after taking
a day or so for locales-all ☺ it still creates a source archive in
build-tree/eglibc-2.11.2.tar.xz which I think is for the eglibc-source
arch:all deb. This creates unnecessary burden on
libc_extra_config_options (all of them, we have __thread
+ and TLS now; sanity checks were only disabled for linuxthreads)
+- use NPTL instead of linuxthreads
+ * debhelper.in/libc.preinst: require (Debian) 2.6.32 kernel on m68k
+
+ -- Thorsten Glaser t...@mirbsd.de Wed, 02 Feb 2011 19:11:39
.1-6+m68k.1) unreleased; urgency=low
+
+ * d/rules: depend build on $(QUILT_STAMPFN) instead of patch, to fix an
+FTBFS caused by the build target having been run twice
+
+ -- Thorsten Glaser t...@mirbsd.de Tue, 08 Feb 2011 19:23:02 +0100
+
texinfo (4.13a.dfsg.1-6) unstable; urgency=low
Norbert Preining dixit:
So *does* it FTBFS or not???
I think it may depend on the moon phase. The second run of
configure, under fakeroot, had different results than the
first, which led to a failure.
Does building twice actually FTBFS?
The first build resulted in an FTBFS already.
(That
Hilmar Preu�e dixit:
Hm. I tried to build on Debian unstable, one time w/, one time w/o the
patch. The build logs did not show a difference. No, I didn't found
an evidence in the log, that something has been done twice.
Interesting. See below…
I used i386, is the problem limited to m86k and if
Hilmar Preu�e dixit:
I applied the patch to our SVN, the next upload will have the fix.
Thanks a lot! (As I said, it probably doesn’t FTBFS in 99.9% of
all builds, across all architectures – but the double-build is
wrong.)
--
sigmentation fault
How fitting ;-)
bye,
//mirabilos
--
Package: ftp.debian.org
Hi,
I think uploads to experimental should NOT close a bug, but
add a tag fixed-in-experimental (which already exists) instead.
bye,
//mirabilos
--
13:47⎜tobiasu if i were omnipotent, i would divide by zero
all day long ;)
(thinking about
Adam D. Barratt dixit:
The tag exists because before the introduction of version tracking it
was the only way of indicating that a bug was fixed in experimental but
still affected unstable.
Ah okay, thanks for the explanation.
bye,
//mirabilos
--
13:47⎜tobiasu if i were omnipotent, i would
)
+
+ -- Thorsten Glaser t...@mirbsd.de Sun, 27 Feb 2011 15:25:22 +
+
binutils (2.21.0.20110216-2) unstable; urgency=low
* Upload to unstable.
diff -u binutils-2.21.0.20110216/debian/patches/series
binutils-2.21.0.20110216/debian/patches/series
--- binutils-2.21.0.20110216/debian/patches/series
On Sat, 26 Feb 2011, Thijs Kinkhorst wrote:
On Monday 21 February 2011 08:21:58 Adrian von Bidder wrote:
Please consider this trivial patch, which exposees message-ids to the
templates used for the email archive.
Thanks. Because there's currently a very small amount of manpower in the
1 - 100 of 4557 matches
Mail list logo
