[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#861617: Fwd: Re: Bug#861617: RFS: ddcutil/0.8.0-6 [ITP] - control monitor settings



Should have been sent to the entire list.


-------- Forwarded Message --------
Subject: Re: Bug#861617: RFS: ddcutil/0.8.0-6 [ITP] - control monitor settings
Date: Thu, 31 Aug 2017 14:41:21 -0400
From: Sanford Rockowitz <rockowitz@minsoft.com>
Organization: Minaret Software
To: Andrey Rahmatullin <wrar@wrar.name>


I have uploaded a new copy of ddcutil, with a modified 
debian/changelog.  It closes bug 858510, the original ITP bug,  not the 
blocker 861617.  I hope this was the correct choice.

Sanford


On 08/31/2017 01:57 PM, Andrey Rahmatullin wrote:
> On Thu, Aug 31, 2017 at 01:35:33PM -0400, Sanford Rockowitz wrote:
>>>> I assume you mean replace the dummy "Packaged for debian-mentors
>>>> submission." entry and update the timestamp.
>>> Yes, and as I've said, and lintian have told you, you should have done it
>>> at the very beginning.
>> There are 2 changelog related messages from lintian:
>>
>> P: ddcutil: no-upstream-changelog
>>
>>   As I wrote, that file (/usr/share/doc/ddcutil/ChangeLog) will be added in
>> the next upstream point release.
> We were talking about the Debian changelog, why did you suddenly switch to
> the upstream one?
>
>> W: ddcutil: new-package-should-close-itp-bug
>>
>>   Your comment on this message was to ignore the warning for now:
>>
>>      You don't write a separate changelog entry for a mentors "upload".
> I didn't mean that, I meant you should write the correct changelog entry
> from the very beginning and don't write a stub for a mentors "upload"
> (because there is no such thing as a mentors upload wrt debian/changelog).
>
>>>> Can you give some guidance as to what should be in the initial changelog
>>>> entry?   Thanks.
>>> * Initial release. (Closes: #NNNNNN)
>> I'm going to interpret the "it" that I should have done as being the
>> upstream changelog.
> :-/
>


Reply to: