Your message dated Sun, 26 Jul 2009 04:13:16 -0700
with message-id <[email protected]>
and subject line Re: Bug#537506: syslinux-common: pxelinux doesn't display 
progress on downloading files
has caused the Debian Bug report #537506,
regarding syslinux-common: pxelinux doesn't display progress on downloading 
files
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 your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
537506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537506
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: syslinux-common
Version: 2:3.82+dfsg-1
Severity: normal

when using pxelinux, the version in lenny displays "."s while downloading
files... the pxelinux version in squeeze/sid displays absolutely nothing, which
makes it hard to determine if the download is stalled, or just silently
working, but slow.

live well,
  vagrant



--- End Message ---
--- Begin Message ---
Version: 2:3.82+dfsg-1

On Sun, Jul 19, 2009 at 09:44:43AM +0200, Daniel Baumann wrote:
> Vagrant Cascadian wrote:
> > when using pxelinux, the version in lenny displays "."s while downloading
> > files... the pxelinux version in squeeze/sid displays absolutely nothing, 
> > which
> > makes it hard to determine if the download is stalled, or just silently
> > working, but slow.

apparently, pxelinux interprets the "quiet" option passed to the kernel, and
decides to be quiet itself. this seems like reasonable behavior, so i'm closing
the bug.
 
> please do report upstream bugs directly to upstream at
> [email protected]. I'll forward this one though.

perhaps include a reportbug hook suggesting that the debian syslinux
maintainers prefer upstream bugs to upstream, and how to do so. though
sometimes it is hard for people not intimately familiar with the code to know
what is upstream and what is a bug in debian's build.

live well,
  vagrant


--- End Message ---

Reply via email to