Package: glibc
Version: N/A
Severity: normal
[root@foo /etc]# grep search resolv.conf
search ytti.fi sn.net
[root@foo /etc]# host irc
irc.ytti.fi does not exist (Authoritative answer)
[root@foo /etc]# grep search resolv.conf
search sn.net ytti.fi
[root@foo /etc]# host irc
irc.sn.net
Also, please put a space after an ellipsis.
| inetd: stopping...starting...done.
| cron: stopping...starting...done.
| apache: stopping...starting...done.
| ssh: stopping...starting...done.
--
Martin Michlmayr
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
On Thu, Nov 14, 2002 at 06:32:58PM +0100, Martin Michlmayr wrote:
> Also, please put a space after an ellipsis.
>
>
> | inetd: stopping...starting...done.
> | cron: stopping...starting...done.
> | apache: stopping...starting...done.
> | ssh: stopping...starting...done.
Please include det
* Jeff Bailey <[EMAIL PROTECTED]> [2002-11-14 10:49]:
> > Also, please put a space after an ellipsis.
> > | ssh: stopping...starting...done.
>
> Please include details in bug reports, like why you think it's a bug.
Because it's ugly... but apparently Policy 10.4 disagrees with me, so
ignore my
I would like to do a glibc upload this weekend.
The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
there's no way we can reasonable pull from it.
If you have patches that you need and are in CVS, please email me the
ChangeLog entry - I can extract them and get them in. If you hav
On Wed, Aug 07, 2002 at 07:44:43PM +0200, Michael Fedrowitz wrote:
> > glibc22-m68k-fpic.dpatch
> > 2.2 CVS:not in
> > 2.3 CVS:not in
> > Comment:Should be merged within upstream if it's ok.
> > Status: merge
> Yes, this one would make sense, if ups
Processing commands for [EMAIL PROTECTED]:
> severity 155794 important
Bug#155794: pthread man pages missing from glibc-doc
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian B
On Thu, Nov 14, 2002 at 03:05:11PM -0800, Jeff Bailey wrote:
> I would like to do a glibc upload this weekend.
>
> The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
> there's no way we can reasonable pull from it.
>
> If you have patches that you need and are in CVS, please email
On Thu, Nov 14, 2002 at 03:05:11PM -0800, Jeff Bailey wrote:
> I would like to do a glibc upload this weekend.
>
> The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
> there's no way we can reasonable pull from it.
Why not? It is quite frequent to do exactly that. I guarantee you
severity 155794 important
thanks
The pthread manpages are still missing from the glibc documentation.
They are an important part of this package, thus making the package
unuseable for some users (while not for all).
The bug is now 100 days old...
Gruss,
Erich Schubert
--
erich@(mucl.de|d
On Thu, Nov 14, 2002 at 07:03:02PM -0500, Ben Collins wrote:
> > I would like to do a glibc upload this weekend.
> > The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
> > there's no way we can reasonable pull from it.
> Why not? It is quite frequent to do exactly that. I guarant
d-glibc,
I've seen this problem before and can't remember the root cause...
---
firin:~/glibc-debian-cvs# dpkg -i libc6_2.3.1-4_hppa.deb
(Reading database ... 17374 files and directories currently installed.)
Preparing to replace libc6 2.2.5-15 (using libc6_2.3.1-4_hppa.deb) ...
Unpacking repla
>
> The arm bug isn't fixed in CVS - It's a toolchain problem that I'll work
> around with a local hack to disable combreloc. HPPA hasn't submitted
> yet. Last I heard ia64's patch wasn't in CVS yet, and I have no idea
> what's up with Sparc. So it doesn't seem like post of the arch bugs are
>
Jeff,
Are you sure the regex leaks are specific to the current glibc cvs
and not in 2.3.1 as well. The way I read things was that these regex
leaks were just being discovered. I haven't seen anyone claim they
were just introduced in the cvs. Speaking of regex...while we are
waiting for the next
Hi, I've tested this bug myself, and here's what I found. Doing an strace
after a ulimit -v, I get:
[snipped lots of brk()'s]
brk(0x889d000) = 0x889d000
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192)
= 8192
brk(0x889f000)
Package: glibc
Version: N/A
Severity: normal
[EMAIL PROTECTED] /etc]# grep search resolv.conf
search ytti.fi sn.net
[EMAIL PROTECTED] /etc]# host irc
irc.ytti.fi does not exist (Authoritative answer)
[EMAIL PROTECTED] /etc]# grep search resolv.conf
search sn.net ytti.fi
[EMAIL PROTECTED] /etc]# ho
Also, please put a space after an ellipsis.
| inetd: stopping...starting...done.
| cron: stopping...starting...done.
| apache: stopping...starting...done.
| ssh: stopping...starting...done.
--
Martin Michlmayr
[EMAIL PROTECTED]
On Thu, Nov 14, 2002 at 06:32:58PM +0100, Martin Michlmayr wrote:
> Also, please put a space after an ellipsis.
>
>
> | inetd: stopping...starting...done.
> | cron: stopping...starting...done.
> | apache: stopping...starting...done.
> | ssh: stopping...starting...done.
Please include det
* Jeff Bailey <[EMAIL PROTECTED]> [2002-11-14 10:49]:
> > Also, please put a space after an ellipsis.
> > | ssh: stopping...starting...done.
>
> Please include details in bug reports, like why you think it's a bug.
Because it's ugly... but apparently Policy 10.4 disagrees with me, so
ignore my
I would like to do a glibc upload this weekend.
The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
there's no way we can reasonable pull from it.
If you have patches that you need and are in CVS, please email me the
ChangeLog entry - I can extract them and get them in. If you hav
On Wed, Aug 07, 2002 at 07:44:43PM +0200, Michael Fedrowitz wrote:
> > glibc22-m68k-fpic.dpatch
> > 2.2 CVS:not in
> > 2.3 CVS:not in
> > Comment:Should be merged within upstream if it's ok.
> > Status: merge
> Yes, this one would make sense, if ups
Processing commands for [EMAIL PROTECTED]:
> severity 155794 important
Bug#155794: pthread man pages missing from glibc-doc
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian B
On Thu, Nov 14, 2002 at 03:05:11PM -0800, Jeff Bailey wrote:
> I would like to do a glibc upload this weekend.
>
> The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
> there's no way we can reasonable pull from it.
>
> If you have patches that you need and are in CVS, please email
On Thu, Nov 14, 2002 at 03:05:11PM -0800, Jeff Bailey wrote:
> I would like to do a glibc upload this weekend.
>
> The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
> there's no way we can reasonable pull from it.
Why not? It is quite frequent to do exactly that. I guarantee you
severity 155794 important
thanks
The pthread manpages are still missing from the glibc documentation.
They are an important part of this package, thus making the package
unuseable for some users (while not for all).
The bug is now 100 days old...
Gruss,
Erich Schubert
--
erich@(mucl.de|d
On Thu, Nov 14, 2002 at 07:03:02PM -0500, Ben Collins wrote:
> > I would like to do a glibc upload this weekend.
> > The diff from glibc-2.3.1 to current CVS is over 6 Megs. As such,
> > there's no way we can reasonable pull from it.
> Why not? It is quite frequent to do exactly that. I guarant
d-glibc,
I've seen this problem before and can't remember the root cause...
---
firin:~/glibc-debian-cvs# dpkg -i libc6_2.3.1-4_hppa.deb
(Reading database ... 17374 files and directories currently installed.)
Preparing to replace libc6 2.2.5-15 (using libc6_2.3.1-4_hppa.deb) ...
Unpacking repla
>
> The arm bug isn't fixed in CVS - It's a toolchain problem that I'll work
> around with a local hack to disable combreloc. HPPA hasn't submitted
> yet. Last I heard ia64's patch wasn't in CVS yet, and I have no idea
> what's up with Sparc. So it doesn't seem like post of the arch bugs are
>
Jeff,
Are you sure the regex leaks are specific to the current glibc cvs
and not in 2.3.1 as well. The way I read things was that these regex
leaks were just being discovered. I haven't seen anyone claim they
were just introduced in the cvs. Speaking of regex...while we are
waiting for the next
Hi, I've tested this bug myself, and here's what I found. Doing an strace
after a ulimit -v, I get:
[snipped lots of brk()'s]
brk(0x889d000) = 0x889d000
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192)
= 8192
brk(0x889f000)
30 matches
Mail list logo
