Your message dated Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220138: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220953: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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
Hi Jeff,
In your assessment of the three conditions that POSIX tcsetattr needs
to handle, outlined in the Debian BTS at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=218131
you mention that you have a patch for the Debian package,
http://hackers.progeny.com/~licquia/lsb/patches/sarge/glibc_2
On Mon, Dec 15, 2003 at 01:47:53AM +0100, Mathrick wrote:
> Any ideas what I should be looking for? Also, it tends to happen mostly
> on occasions when it's hard to hook strace, like swapping a lot on
> session start, or randomly during usage. Some practical tips would help
> a lot, I'm not too fon
W liście z pon, 15-12-2003, godz. 00:49, Daniel Jacobowitz pisze:
> On Mon, Dec 15, 2003 at 12:07:39AM +0100, Mathrick wrote:
> > W li?cie z nie, 14-12-2003, godz. 20:21, Daniel Jacobowitz pisze:
> >
> > > > So to sum up, it looks like libc bug because:
> > >
> > > So take a simple testcase tha
Your message dated Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220138: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220953: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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
Hi Jeff,
In your assessment of the three conditions that POSIX tcsetattr needs
to handle, outlined in the Debian BTS at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=218131
you mention that you have a patch for the Debian package,
http://hackers.progeny.com/~licquia/lsb/patches/sarge/glibc_2
On Mon, Dec 15, 2003 at 01:47:53AM +0100, Mathrick wrote:
> Any ideas what I should be looking for? Also, it tends to happen mostly
> on occasions when it's hard to hook strace, like swapping a lot on
> session start, or randomly during usage. Some practical tips would help
> a lot, I'm not too fon
W liście z pon, 15-12-2003, godz. 00:49, Daniel Jacobowitz pisze:
> On Mon, Dec 15, 2003 at 12:07:39AM +0100, Mathrick wrote:
> > W li?cie z nie, 14-12-2003, godz. 20:21, Daniel Jacobowitz pisze:
> >
> > > > So to sum up, it looks like libc bug because:
> > >
> > > So take a simple testcase tha
Sorry, didn't cc correctly, sending again.
W liście z nie, 14-12-2003, godz. 20:21, Daniel Jacobowitz pisze:
> > So to sum up, it looks like libc bug because:
>
> So take a simple testcase that shows the problem, attack it with
strace
> and gdb, and figure out what's going on.
It's hard because
Your message dated Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218438: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219664: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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
Sorry, didn't cc correctly, sending again.
W liście z nie, 14-12-2003, godz. 20:21, Daniel Jacobowitz pisze:
> > So to sum up, it looks like libc bug because:
>
> So take a simple testcase that shows the problem, attack it with
strace
> and gdb, and figure out what's going on.
It's hard because
Your message dated Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218438: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219664: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:29 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#203303: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219940: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:29 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#215337: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220991: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221438: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221543: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220991: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:29 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#203303: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219940: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:29 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#215337: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220331: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220232: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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
Accepted:
linux-kernel-headers_2.5.999-test7-bk-10.diff.gz
to
pool/main/l/linux-kernel-headers/linux-kernel-headers_2.5.999-test7-bk-10.diff.gz
linux-kernel-headers_2.5.999-test7-bk-10.dsc
to
pool/main/l/linux-kernel-headers/linux-kernel-headers_2.5.999-test7-bk-10.dsc
linux-kernel-headers_2
Your message dated Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220991: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221438: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221543: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220991: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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
linux-kernel-headers_2.5.999-test7-bk-10_i386.changes uploaded successfully to
localhost
along with the files:
linux-kernel-headers_2.5.999-test7-bk-10.dsc
linux-kernel-headers_2.5.999-test7-bk-10.diff.gz
linux-kernel-headers_2.5.999-test7-bk-10_i386.deb
Greetings,
Your Debian queu
Your message dated Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220331: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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 Sun, 14 Dec 2003 14:02:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220232: fixed in linux-kernel-headers 2.5.999-test7-bk-10
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
On Sun, Dec 14, 2003 at 05:47:47PM +0100, Mathrick wrote:
> Hi, I've asked around on #debian, and was advised to mail you and make
> sure it's glibc problem. I will describe problems I'm experiencing, and
> then explain why I suspect glibc.
>
> About 6 months ago I upgraded Woody -> Sid. I'm using
Accepted:
linux-kernel-headers_2.5.999-test7-bk-10.diff.gz
to pool/main/l/linux-kernel-headers/linux-kernel-headers_2.5.999-test7-bk-10.diff.gz
linux-kernel-headers_2.5.999-test7-bk-10.dsc
to pool/main/l/linux-kernel-headers/linux-kernel-headers_2.5.999-test7-bk-10.dsc
linux-kernel-headers_2.5
linux-kernel-headers_2.5.999-test7-bk-10_i386.changes uploaded successfully to
localhost
along with the files:
linux-kernel-headers_2.5.999-test7-bk-10.dsc
linux-kernel-headers_2.5.999-test7-bk-10.diff.gz
linux-kernel-headers_2.5.999-test7-bk-10_i386.deb
Greetings,
Your Debian queu
On Sun, Dec 14, 2003 at 05:47:47PM +0100, Mathrick wrote:
> Hi, I've asked around on #debian, and was advised to mail you and make
> sure it's glibc problem. I will describe problems I'm experiencing, and
> then explain why I suspect glibc.
>
> About 6 months ago I upgraded Woody -> Sid. I'm using
Hi, I've asked around on #debian, and was advised to mail you and make
sure it's glibc problem. I will describe problems I'm experiencing, and
then explain why I suspect glibc.
About 6 months ago I upgraded Woody -> Sid. I'm using GNOME as my
primary desktop, so did 1.4 -> 2.2 upgrade. Since then
On Sat, Dec 13, 2003 at 08:52:07PM -0800, Karl M. Hegbloom wrote:
> On Sat, 2003-12-13 at 20:24, Jeff Bailey wrote:
> > On Sat, Dec 13, 2003 at 03:30:05PM -0800, Karl M. Hegbloom wrote:
> >
> > > I notice that in debian/sysdeps/linux.mk you set NJOBS according to
> > > the number of CPU's on the c
Hi, I've asked around on #debian, and was advised to mail you and make
sure it's glibc problem. I will describe problems I'm experiencing, and
then explain why I suspect glibc.
About 6 months ago I upgraded Woody -> Sid. I'm using GNOME as my
primary desktop, so did 1.4 -> 2.2 upgrade. Since then
On Sat, Dec 13, 2003 at 08:52:07PM -0800, Karl M. Hegbloom wrote:
> On Sat, 2003-12-13 at 20:24, Jeff Bailey wrote:
> > On Sat, Dec 13, 2003 at 03:30:05PM -0800, Karl M. Hegbloom wrote:
> >
> > > I notice that in debian/sysdeps/linux.mk you set NJOBS according to
> > > the number of CPU's on the c
2.3.2-4 had this:
- debian/patches/revert-old-libio.dpatch: back out changes causing
problems with fseek in binaries linked with glibc 2.0.
(Closes: #206839)
Which might be the cause of your problem. We've since sorted this out
with a correct fix. Can you please try again agains
2.3.2-4 had this:
- debian/patches/revert-old-libio.dpatch: back out changes causing
problems with fseek in binaries linked with glibc 2.0.
(Closes: #206839)
Which might be the cause of your problem. We've since sorted this out
with a correct fix. Can you please try again agains
Package: glibc-doc
Version: 2.3.2.ds1-10
Severity: wishlist
I used the source "make pdf" target to create a PDF of the libc
manual. I've got tetex 2.x installed. It created a beutiful
clickable PDF that is a joy to look upon, and I would like it if
others could have a copy as well. Will you pl
Package: glibc-doc
Version: 2.3.2.ds1-10
Severity: wishlist
I used the source "make pdf" target to create a PDF of the libc
manual. I've got tetex 2.x installed. It created a beutiful
clickable PDF that is a joy to look upon, and I would like it if
others could have a copy as well. Will you pl
48 matches
Mail list logo
