Processed: Re: Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-11-11 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> retitle 276417 xterm: removes variable TMPDIR from environment of child 
> process
Bug#276417: xterm removes variable TMPDIR from the child's process environment
Changed Bug title.
(By the way, that Bug is currently marked as done.)

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-11-11 Thread Branden Robinson
retitle 276417 xterm: removes variable TMPDIR from environment of child process
thanks

On Wed, Oct 27, 2004 at 01:50:24PM +0200, Michelle Konzack wrote:
> Am 2004-10-25 12:22:18, schrieb Branden Robinson:
> 
> > One very good way to file bugs with the Debian Bug Tracking System is to
> > use the "reportbug" package and command of the same name.  A very nice
> 
> I use ssmtp on my machines and I can not set reportbug toi use asmtp like
> 
> |/usr/sbin/ssmtp -t -au  -p 

Hmm; in that case you should consider filing a wishlist bug against the
"reportbug" package, requesting this functionality.

> To: [EMAIL PROTECTED]
> Body:   index xfree86
> 
> I do this regulary per cron job all two weeks on 
> Packages where I am interested and subscribed...

Ah, I see.  Not a bad idea.  :)

> > (If you've ever gotten a "bounce" message from the Debian Bug Tracking
> > System that tells you your message couldn't be processed, you might
> > appreciate this latter feature.)
> 
> Never gotten... :-)
> The documentation about PTS/BTS is clear enough.

Glad to hear it!

-- 
G. Branden Robinson| When I die I want to go peacefully
Debian GNU/Linux   | in my sleep like my ol' Grand
[EMAIL PROTECTED] | Dad...not screaming in terror like
http://people.debian.org/~branden/ | his passengers.


signature.asc
Description: Digital signature


Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-27 Thread Michelle Konzack
Am 2004-10-25 12:22:18, schrieb Branden Robinson:

> One very good way to file bugs with the Debian Bug Tracking System is to
> use the "reportbug" package and command of the same name.  A very nice

I use ssmtp on my machines and I can not set reportbug toi use asmtp like

|/usr/sbin/ssmtp -t -au  -p 

> feature of reportbug is that, if the machine where you run it has network
> access to the World Wide Web, it can query the Debian Bug Tracking System
> and show you existing reports.  This reduces the chance that you'll file a

To: [EMAIL PROTECTED]
Body:   index xfree86

I do this regulary per cron job all two weeks on 
Packages where I am interested and subscribed...

> correctly by the automated tools that manage the reports.  (If you've ever
> gotten a "bounce" message from the Debian Bug Tracking System that tells
> you your message couldn't be processed, you might appreciate this latter
> feature.)

Never gotten... :-)
The documentation about PTS/BTS is clear enough.

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-25 Thread Branden Robinson
close 276417
severity 276417 normal
merge 276417 276234
thanks

On Thu, Oct 14, 2004 at 02:16:32AM +0200, Michelle Konzack wrote:
> Hello Maintainer and Upstream,
> 
> This is related to BUG #276234
> 
> Greetings
> Michelle

...and is being closed for the same reason.

See http://bugs.debian.org/276234 > for more information.

[The following is a form letter.]

Hello,

You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.

While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports.  This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report.  This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers.  The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports.  (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System.  (If you already do use
"reportbug", please see below.)

One way to install reportbug is with "apt-get"; for
example:

  # apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise.  If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.

  $ reportbug --mode=novice
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.

  $ reportbug
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

The reportbug command is extensively documented in its usage message and
manual page.  Commands to view these pieces of documentation are:

  $ reportbug --help | more
  $ man reportbug

(The output of the above commands has been omitted from this message.)

If you do use reportbug, but are so daunted by the large number of bugs
already filed against a package that you feel you cannot search for a
duplicate, please note that reportbug has a (f)ilter feature that enables
you to use a keyword search to limit the number of bugs reported.  (If
you're feeling ambitious, the filter feature also accepts a regular
expression.)  For example, if you'd like to report a SEGV (segfault), you
might filter based on the term "SEGV".  If you're having trouble upgrading
a package, you might filter based on "upgrad" (to catch both "upgrade" and
"upgrading").  Some package maintainers retitle bugs to contain keywords so
as to facilitate better filtering and convey more useful information, since
a bug report with a title of "broken" or the like is not very useful to
anyone.

We appreciate you taking the time to help package maintainers serve you
better by reducing the amount of time they need to spend coping with
duplicate bug reports.

Thanks for using the Debian system!

-- 
G. Branden Robinson|People with power understand
Debian GNU/Linux   |exactly one thing: violence.
[EMAIL PROTECTED] |-- Noam Chomsky
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-25 Thread Branden Robinson
And by the way, both of you:

xterm contains no logic for scrubbing the environment.

-- 
G. Branden Robinson| Organized religion is a sham and a
Debian GNU/Linux   | crutch for weak-minded people who
[EMAIL PROTECTED] | need strength in numbers.
http://people.debian.org/~branden/ | -- Jesse Ventura


signature.asc
Description: Digital signature


Processed: Re: Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> close 276417
Bug#276417: xterm removes variable TMPDIR from the child's process environment
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Helmut Waitzmann (Debian Bug 
Tracking System) <[EMAIL PROTECTED]>

> severity 276417 normal
Bug#276417: xterm removes variable TMPDIR from the child's process environment
Severity set to `normal'.

> merge 276417 276234
Bug#276234: xterm: doesn't respect stuff I set in my .bash_profile when it's 
not a login shell
Bug#276417: xterm removes variable TMPDIR from the child's process environment
Merged 276234 276417.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-13 Thread Michelle Konzack
Hello Maintainer and Upstream,

This is related to BUG #276234

Greetings
Michelle


Am 2004-10-13 18:54:29, schrieb Helmut Waitzmann:
> 
> Package: xterm
> Version: 4.1.0-16woody1
> Severity: important
> Tags: security
> 
> 
> xterm removes the environment variable TMPDIR from the process environment:
> 
> To reproduce the error, run the following command, which starts a xterm
> showing the value of the TMPDIR environment variable:
> 
> $ env TMPDIR=/tmp xterm -hold -e printenv TMPDIR
> 
> As can be seen in that xterm:  TMPDIR has no value.
> 
> Compare it with the following variant, which shows the value of the tmpdir
> environment variable:
> 
> $ env tmpdir=/tmp xterm -hold -e printenv tmpdir
> 
> This time, xterm displays the value, which is /tmp.
> 
> 
> -- System Information
> Debian Release: 3.0
> Architecture: i386
> Kernel: Linux kugelfisch 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
> Locale: LANG=C, LC_CTYPE=de_DE
> 
> Versions of packages xterm depends on:
> ii  debconf  1.0.32  Debian configuration management 
> sy
> ii  libc62.2.5-11.5  GNU C Library: Shared libraries 
> an
> ii  libfreetype6 2.0.9-1 FreeType 2 font engine, shared 
> lib
> ii  libncurses5  5.2.20020112a-7 Shared libraries for terminal 
> hand
> ii  libxaw7  4.1.0-16woody1  X Athena widget set library
> ii  xlibs4.1.0-16woody1  X Window System client libraries


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Processed: Re: Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> tags  276417 - security
Bug#276417: xterm removes variable TMPDIR from the child's process environment
Tags were: security
Tags removed: security

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#276417: xterm removes variable TMPDIR from the child's process environment

2004-10-13 Thread Debian Bug Tracking System

Package: xterm
Version: 4.1.0-16woody1
Severity: important
Tags: security


xterm removes the environment variable TMPDIR from the process environment:

To reproduce the error, run the following command, which starts a xterm
showing the value of the TMPDIR environment variable:

$ env TMPDIR=/tmp xterm -hold -e printenv TMPDIR

As can be seen in that xterm:  TMPDIR has no value.

Compare it with the following variant, which shows the value of the tmpdir
environment variable:

$ env tmpdir=/tmp xterm -hold -e printenv tmpdir

This time, xterm displays the value, which is /tmp.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux kugelfisch 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages xterm depends on:
ii  debconf  1.0.32  Debian configuration management sy
ii  libc62.2.5-11.5  GNU C Library: Shared libraries an
ii  libfreetype6 2.0.9-1 FreeType 2 font engine, shared lib
ii  libncurses5  5.2.20020112a-7 Shared libraries for terminal hand
ii  libxaw7  4.1.0-16woody1  X Athena widget set library
ii  xlibs4.1.0-16woody1  X Window System client libraries

-- 
Wenn Sie mir E-Mail schreiben, stellen |  When writing me e-mail, please
Sie bitte vor meine E-Mail-Adresse |  precede my e-mail address with
meinen Vor- und Nachnamen, etwa so:|  my full name, like
Helmut Waitzmann <[EMAIL PROTECTED]>, (Helmut Waitzmann) [EMAIL PROTECTED]