Reject Mail to ITP Bug
 

Hi,

I have seen that many packages are rejected from NEW [1] due to either
licensing or poor packaging and we know the reasons [2] too.

It will be very helpful if Rejection is also mailed to ITP (where it
apply) so, that anyone can look at actual reason and fix problem
(packaging, contacting upstream for license issues etc).

For example, I was looking for why 'command-not-found' package got
rejected, found no way until I speak and discuss to package uploader
(#418613)

Thanks in advance.

[1] http://ftp-master.debian.org/new.html
[2] http://ftp-master.debian.org/REJECT-FAQ.html

--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Homepage: people.debian.org/~kartik
Blogs: {ftbfs,kartikm}.wordpress.com


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reject Mail to ITP Bug
 

On Tue, Aug 26, 2008 at 1:01 PM, Kartik Mistry <kartik.mistry@gmail.com> wrote:

> I have seen that many packages are rejected from NEW [1] due to either
> licensing or poor packaging and we know the reasons [2] too.
>
> It will be very helpful if Rejection is also mailed to ITP (where it
> apply) so, that anyone can look at actual reason and fix problem
> (packaging, contacting upstream for license issues etc).

Sounds good, you might want to ask the ftpmasters if they are willing
to do that, or implement some other solution.

--
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reject Mail to ITP Bug
 

> It will be very helpful if Rejection is also mailed to ITP (where it
> apply) so, that anyone can look at actual reason and fix problem
> (packaging, contacting upstream for license issues etc).

Fine.

If you

- get a uniform (and not too hard) way to know which ITP(s) belong to
the package we just process, if any,
- hand me a git tree to merge from that has a sane solution[1],

I am willing to apply such a patch. But I'm (for the next weeks) not
going to invest time there myself. :)
(Feel free to open a bug about it to keep track of the status of this)


You want to (currently) work with http://ftp-master.debian.org/git/dak.git/


[1] sane does not mean
- assume that every uploader does it right and closes ITPs in
changelog (or even mention them),
- parsing wnpp bug data everytime

--
bye, Joerg
[ New Maintainer Prozess ]
<panthera> ein jahr ist ein bisschen zu optimistisch,
<_rene_> panthera: kommt auf den NM/AM an.
/* _rene_ ist pantheras AM und lässt sich mit pantheras
package check schon ein wenig Zeit ;) */

Reject Mail to ITP Bug
 

On Tue, Aug 26, 2008 at 04:10:38PM +0200, Joerg Jaspert wrote:
>
> > It will be very helpful if Rejection is also mailed to ITP (where it
> > apply) so, that anyone can look at actual reason and fix problem
> > (packaging, contacting upstream for license issues etc).
>
> Fine.
>
> If you
>
> - get a uniform (and not too hard) way to know which ITP(s) belong to
> the package we just process, if any,

That can be easily determined by looking in the .changes for the
"closes" field. If more than one, you can check to see which has "ITP"
in the title. If there is no closes, then assume that there is no ITP
and that's it.

Regards,

-Roberto

--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Reject Mail to ITP Bug
 

Hi,

Kartik Mistry wrote:
> I have seen that many packages are rejected from NEW [1] due to either
> licensing or poor packaging and we know the reasons [2] too.

> It will be very helpful if Rejection is also mailed to ITP (where it
> apply) so, that anyone can look at actual reason and fix problem
> (packaging, contacting upstream for license issues etc).
Any developer can read them on the ftp-master mirror on merkel.

Personally, I'm not sure that I'd be too excited to have reject mails
archived on the BTS when I'm on the receiving end, but I guess that's
just me. In most of the cases they would seem to add little value to the
ITP bug.

Kind regards

T.
--
Thomas Viehmann, http://thomas.viehmann.net/


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reject Mail to ITP Bug
 

Joerg Jaspert <joerg@debian.org> writes:

> [1] sane does not mean
> - assume that every uploader does it right and closes ITPs in
> changelog (or even mention them),
> - parsing wnpp bug data everytime


How about BCC'ing the reject mail to a mailing list with a public,
web-browsable archive?

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reject Mail to ITP Bug
 

Roberto C. Sánchez wrote:

That can be easily determined by looking in the .changes for the
"closes" field. If more than one, you can check to see which has "ITP"
in the title. If there is no closes, then assume that there is no ITP
and that's it.


I would suggest you always check for which one has ITP in the title.

Otherwise it might not be an ITP bug at all. Even if it is a "new"
source package.


Or it might be an ITP for the wrong package. Maybe need to check the
package name too. Maybe the uploader mistyped the bug number.


This in turn might be the reason it was rejected.

Brian May


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reject Mail to ITP Bug
 

On Tue, Aug 26, 2008 at 8:37 PM, Reinhard Tartler <siretart@debian.org> wrote:
> How about BCC'ing the reject mail to a mailing list with a public,
> web-browsable archive?

Yes, even publicly available report is also fine.

--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Homepage: people.debian.org/~kartik
Blogs: {ftbfs,kartikm}.wordpress.com


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reject Mail to ITP Bug
 

Thomas Viehmann <tv@beamnet.de> writes:

> Personally, I'm not sure that I'd be too excited to have reject mails
> archived on the BTS when I'm on the receiving end, but I guess that's
> just me. In most of the cases they would seem to add little value to the
> ITP bug.

Well, they would be pretty useful for the case that the package is team
maintained and the uploader fails or forgets to forward the reject mail
somewhere useful.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org