On Tue, Apr 13, 2010 at 3:34 AM, Filipus Klutiero <[email protected]> wrote:
> On April 12, 2010 10:26:57 pm James Vega wrote:
>> On Mon, Apr 12, 2010 at 02:44:04PM -0400, Filipus Klutiero wrote:
>> > bts is failing the same way on 2 machines on 2 tested:
>> >
>> > $ LANG=C bts tags 407598 - fixed-upstream
>> > User-Agent: devscripts bts/2.10.62: No such file or directory
>> > bts: mail:
>> > chea...@vinci:~$
>> >
>> > This happens with version 2.10.61 (testing) too. It seems unusable. I'm
>> > not using bts regularly, but it would be surprising that bts was
>> > completely broken.
>>
>> The part of the script in which this occurs is where we fork/exec the
>> mail process.  It basically boils down to:
>>
>> printf "tags 407598 - fixed-upstream\nthanks\n" | mail -s "tagging 407598"
>>  -a "User-Agent: devscripts bts/2.10.62" [email protected]
>>
>> Although the above isn't exactly what's happening, does that work?  The
>> error message you're getting seems like it may be due to not finding
>> mail, but I'd expect to see more than just "No such file or directory".
>
> It doesn't work. The output for your test was
> User-Agent: devscripts bts/2.10.62: No such file or directory
>
> This happens because mail is provided by heirloom-mailx, for which -a means:
>
> -a file
>  Attach the given file to the message.

Interesting.  That throws a wrench in the works.  Do you know how one
would specify extra mail headers using heirloom-mailx?

> The management of the
> mailx alternative seems to be broken. If you install/uninstall mailx providers
> to fix this issue, please pay attention to what happens to mail(1). It broke 
> at
> some point on the 2 PCs. mailutils may well be the culprit. It provides
> mail(1) directly in /usr/bin/mail, which is usually an alternative link. This
> would deserve another bug report. I think /usr/bin/mail disappears sometimes,
> even when a mailx provider is present.

Indeed.  That's a bug.  Thanks for the information.  I'll file a bug
against mailutils soon.

-- 
James
GPG Key: 1024D/61326D40 James Vega <[email protected]>




--
To unsubscribe, send mail to [email protected].

Reply via email to