[Reportbug-maint] Bug#590242: now without the email variable in ~/.bashrc

Sandro Tosi morph at debian.org
Mon Aug 2 20:21:07 UTC 2010

retitle 590242 should always write realname/email on --configure

Hi Neil,

On Sun, Aug 1, 2010 at 23:23, Neil Williams <codehelp at debian.org> wrote:
> Package: reportbug
> Version: 4.12.4em1
> Severity: normal
> Reconfigured from a terminal started afresh after commenting out the setting of
> the EMAIL environment variable and then reconfiguring reportbug to simulate
> where the user hadn't set such a variable at all.
> This time, configuring reportbug didn't find the email address to use, so it
> invented a local one which I replaced and which then appeared in the
> reportbugrc.
> So this bug is actually that reportbugrc fails to get the environment variable
> using the desktop file (because that was set in ~/.bashrc) which it would use
> when loaded from the command line. Not really a fault in reportbug (as long as
> this one sends OK).
> I don't know whether reportbug would be able to source the ~/.bashrc even when
> using the GTK2 frontend which would avoid this potential problem, particularly
> as other command line programs will re-use the same variable.

Thanks to your patience we have come to a conclusion here: thanks a lot!

The problem is that --configure propose values for realname and email,
but don't write to ~/.reportbugrc (well, it writes them, but
commented) if it finds them in the env (so like DEBFULLNAME and
DEBEMAIL env variables).

Then again, when executed the GTK+ UI from the menu, those variables
are not set (there's no env) and so reportbug doesn't know how to fill
those info when sending the email, hence the error receive in the
original post.

I think that only executing reportbug from the menu (right from the
beginning) would lead to a working setup, since the first time
reportbug will run configuration, find no env vars, write the config
file correctly, and next times will find the info needed. But in case
there are mixed situations, it might lead to not working setup.

The solution I see is to "force" reportbug to write realname and email
even if found in the environment. Given it might lead to unexpected
behavior, I won't fix this for squeeze (aren't we supposed to freeze
in a month? ;) ), but I'll target experimental with other potential
disruptive changes sometime soon.

Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

More information about the Reportbug-maint mailing list