Debian Bug report logs - #745675
email uploader when there's an error in processincoming

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: email uploader when there's an error in processincoming

Date: Wed, 23 Apr 2014 19:02:14 -0400

Package: reprepro
Severity: wishlist

it is pretty confusing for users when their upload fails to register
in reprepro - they have no way to tell what went wrong, short of
looking into the log, something which only admins have access to.

could reprepro email the uploader when errors happen?

a.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Message #10 received at 745675@bugs.debian.org (full text, mbox, reply):

From: "Bernhard R. Link" <brlink@debian.org>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 745675@bugs.debian.org

Subject: Re: Bug#745675: email uploader when there's an error in processincoming

Date: Sun, 11 May 2014 12:40:10 +0200

* Antoine Beaupré <anarcat@debian.org> [140424 01:03]:
> it is pretty confusing for users when their upload fails to register
> in reprepro - they have no way to tell what went wrong, short of
> looking into the log, something which only admins have access to.
>
> could reprepro email the uploader when errors happen?

This is a long planed feature, TODO already lists "implement sending
mails to uploader", but also a quite complicated one. For one the error
reporting needs some revamping, as most error reporting currently goes
directly to stderro.

Then there is a question of where to send mails to. I guess one wants
something like a whitelist there, to make sure DDs are not pestered with
mails if someone tries to add their package to some local repository
somehwere in the world.

As an intermediate step, you might want to consider if it makes sense
for you to write this log to some place where users can look at them.
(as the repository generated is usually available via plain html,
making the log visible on the same way is usually easy, unless you
consider any information in there especially protectworthy).

	Bernhard R. Link
-- 
F8AC 04D5 0B9B 064B 3383  C3DA AFFC 96D1 151D FFDC

Send a report that this bug log contains spam.