* [all] Error 2
> make[1]: Leaving directory `/build/buildd/glibc-2.3.6/build-tree/s390-s390x'
> make: *** [/build/buildd/glibc-2.3.6/stamp-dir/build_s390x] Error 2
> **
> Build finished at 20060531-0057
> FAILED [dp
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.16
> tags 364098 + experimental
Bug#364098: glibc_2.3.999-1(m68k/experimental):
There were no tags set.
Tags added: experimental
>
End of message, stopping processing here.
Please contac
Hello,
I've set up my DNS servers to sort IP addresses according to our network
topology. for example, lookup for irc.sk should always return this order:
[EMAIL PROTECTED] host irc.sk
irc.sk has address 195.168.2.141
irc.sk has address 147.232.40.23
this is OK, even when I repeat the lookup a fe
Bastian Blank a écrit :
Package: glibc
Version: 2.3.6-12
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of glibc_2.3.6-12 on debian01 by sbuild/s390 85
[...]
This problem has been fixed in 2.3.6-13. However, it still not build, I
am therefore
Your message dated Wed, 31 May 2006 09:58:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369656: [Patch] Fixed error of configuring libidn for m32r
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 31 May 2006 00:47:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369641: fixed in glibc 2.3.6-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now you
Your message dated Wed, 31 May 2006 00:47:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369636: fixed in glibc 2.3.6-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now you
Hi all,
I have just a uploaded glibc 2.3.6-13, which should fix a bug introduced
when I merged m32r patches (linking libgcc_s). 2.6.3-12 has fixed all my
broken udeb stuff.
I just hope this version could go to etch as compared to the version in
etch, it fixes the following bugs among the oth
Accepted:
glibc-doc_2.3.6-13_all.deb
to pool/main/g/glibc/glibc-doc_2.3.6-13_all.deb
glibc_2.3.6-13.diff.gz
to pool/main/g/glibc/glibc_2.3.6-13.diff.gz
glibc_2.3.6-13.dsc
to pool/main/g/glibc/glibc_2.3.6-13.dsc
libc6-amd64_2.3.6-13_i386.deb
to pool/main/g/glibc/libc6-amd64_2.3.6-13_i386.de
On Tue, May 30, 2006 at 05:52:43PM +0200, Ingo Juergensmann wrote:
>
> > >I tried it on akire, but was interrupted by real world issues.
> > >When you could give a more detailed HowTo (sbuild, dpkg-buildpackage,
> > >whatever) I would retry...
> > Very easy:
> > dget http://people.debian.org/~au
glibc_2.3.6-13_multi.changes uploaded successfully to localhost
along with the files:
libc6-dbg_2.3.6-13_i386.deb
locales_2.3.6-13_all.deb
libc6-dev_2.3.6-13_i386.deb
libc6_2.3.6-13_i386.deb
libc6-pic_2.3.6-13_amd64.deb
libc6_2.3.6-13_amd64.deb
nscd_2.3.6-13_amd64.deb
glibc-doc_2.3.
; make[2]: *** [/build/buildd/glibc-2.3.6/build-tree/s390-s390x/libc.so] Error 1
> make[2]: Leaving directory `/build/buildd/glibc-2.3.6/build-tree/glibc-2.3.6'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/glibc-2.3.6/build-tree/s390-s390x'
> make: **
12 matches
Mail list logo
