Bug#342883: [Pbuilder-maint] Bug#342883: Incompatibility between pbuilder and devscripts WRT DEBEMAIL
Hi, > pbuilder and the "bts" command seem to disagree on what "DEBEMAIL" is > supposed to hold. > > /usr/lib/pbuilder/pbuilder-buildpackage is calling dpkg-buildpackage > "-m$DEBEMAIL", and that implies DEBEMAIL should hold "Maintainer Name > ", and if you call the bts command with a > DEBEMAIL formatted like this, you will get: > From: Maintainer Name > So, your suggestion is to fix devscripts bts command? I tend to agree with that, please do reassign to devscripts. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342883: [Pbuilder-maint] Bug#342883: Incompatibility between pbuilder and devscripts WRT DEBEMAIL
Hi, On Sat, Dec 17, 2005, Junichi Uekawa wrote: > So, your suggestion is to fix devscripts bts command? > I tend to agree with that, please do reassign to devscripts. I never made such a suggestion, I think *both* devscripts and pbuilder ought to be fixed. The biggest problem is that there's no spec or man page or anything defining what those variables should hold. bts is older than pbuilder, so it might be tempting to point the finger at pbuilder. bts has a much finer logic to detect and use EMAIL/Debian Maintainer environment variables, but it has some mistakes. I suppose that the pbuilder fix would to implement such a logic, or at least permit overriding the decisions: right now, both tools hard code the same environment variable; would pbuilder use some PBUILDER_DEBMAINT="$DEBEMAIL" instead, that would do it. And would bts read the devscripts config file instead of using the environment to get that parameter, that would help too. Cheers, -- Loïc Minier <[EMAIL PROTECTED]>
Bug#342883: [Pbuilder-maint] Bug#342883: Incompatibility between pbuilder and devscripts WRT DEBEMAIL
Hi, > I never made such a suggestion, I think *both* devscripts and pbuilder > ought to be fixed. > > The biggest problem is that there's no spec or man page or anything > defining what those variables should hold. bts is older than pbuilder, > so it might be tempting to point the finger at pbuilder. > > bts has a much finer logic to detect and use EMAIL/Debian Maintainer > environment variables, but it has some mistakes. Note that DEBEMAIL isn't actually an environmental variable, but a configuration variable used internally in pbuilder, set in pbuilderrc, and overridden with --debemail. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342883: [Pbuilder-maint] Bug#342883: Incompatibility between pbuilder and devscripts WRT DEBEMAIL
On Sat, Dec 17, 2005, Junichi Uekawa wrote: > Note that DEBEMAIL isn't actually an environmental variable, but > a configuration variable used internally in pbuilder, > set in pbuilderrc, and overridden with --debemail. But it's inherited from the environment by default. So if in the default case the presence of the DEBEMAIL environment variable changes the behavior of pbuilder, but it behaves wrongly (as was my case when I was using pbuilder in the past: my .changes files were set to Changed-By: [EMAIL PROTECTED] because DEBEMAIL held only an email), then pbuilder ought to be fixed to use DEBFULLNAME/DEBEMAIL/EMAIL correctly. I opened the bug against devscripts and pbuilder at the same time in the hope that the maintainers would take a decision for a common format for these environment variables. Right now, someone configuring his environment in the hope that it will be reused across programs will be deceived by DEBEMAIL which has different behaviors / expected formats across programs. All I did is point at two programs with different behaviors. -- Loïc Minier <[EMAIL PROTECTED]>
Bug#342883: [Pbuilder-maint] Bug#342883: Incompatibility between pbuilder and devscripts WRT DEBEMAIL
Hi, > On Sat, Dec 17, 2005, Junichi Uekawa wrote: > > Note that DEBEMAIL isn't actually an environmental variable, but > > a configuration variable used internally in pbuilder, > > set in pbuilderrc, and overridden with --debemail. > > But it's inherited from the environment by default. The default value should be defined as "" in /usr/share/pbuilder/pbuilderrc. It was done in reaction to a similar report. If it's inherited from the environment, it's probably a bug. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342883: [Pbuilder-maint] Bug#342883: Incompatibility between pbuilder and devscripts WRT DEBEMAIL
On Sat, Dec 17, 2005, Junichi Uekawa wrote: > If it's inherited from the environment, it's probably a bug. I'm afraid it is. I tried two builds, one with DEBEMAIL="$DEBFULLNAME <$EMAIL>" in my pbuilderrc, and the other with unset DEBEMAIL in my pbuilderrc, the later resulted in a .changes file with the Maintainer: taken from control, and the Changed-By: set to me, and the former resulted in the Maintainer: and Changed-By: set to me (and hence incorrect). Cheers, -- Loïc Minier <[EMAIL PROTECTED]>
Bug#342883: [Pbuilder-maint] Bug#342883: Incompatibility between pbuilder and devscripts WRT DEBEMAIL
Hi, > > If it's inherited from the environment, it's probably a bug. > > I'm afraid it is. I tried two builds, one with DEBEMAIL="$DEBFULLNAME > <$EMAIL>" in my pbuilderrc, > former > resulted in the Maintainer: and Changed-By: set to me (and hence > incorrect). If you've set it that way, DEBEMAIL isn't exactly inherited from the environment. That's how you've configured it. This sounds like an expected behavior. Which part of the sequence is the problem? regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
