[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-devel
Subject:    Re: Bug#340428: octave2.9 - lists mailing list as uploader in changelog
From:       Rafael Laboissiere <rafael () debian ! org>
Date:       2005-11-24 13:21:27
Message-ID: 20051124132127.GA29125 () laboiss2
[Download RAW message or body]

* Bastian Blank <waldi@debian.org> [2005-11-24 10:21]:

> On Wed, Nov 23, 2005 at 06:36:53PM +0100, Rafael Laboissiere wrote:
> > As regards the copy of this information into the Changed-By field of the
> > changes file, we are already requiring that the developers of the DOG 
> > use the -e option of debuild (cf the DOG Guidelines, at
> 
> And the autobuilders get this value from where? They use the common way
> by looking into the changelog.

They get the correct entity, which is in the changelog (in the case of
the Debian Octave Group, it is pkg-octave-devel@lists.alioth.debian.org).
If something goes wrong with the autobuild, then this entity should be
contacted, not the person who did the upload.  Why would the autobuilders
be unhappy with a mailing list as the maintainer entity?

On the other hand, debian-installer needs to know who uploaded the
package and this informaation is in the Changed-By field of the changes
file, which will hopefully be correct for any future upload done by the
DOG members.

> > At any rate, it seems that using mailing lists in changelog entries is
> > common practice, like:
> 
> Less than 2% is not common.

I do not know how you ot this figure, but anything greater than 0% should
be fixed if we decide that this practice is really against the Policy
(which I am claiming is not).

-- 
Rafael


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

[prev in list] [next in list] [prev in thread] [next in thread]