Bug#872182: RFS: budgie-desktop/10.4-1

["foss.freedom" <foss.freedom@gmail.com>]

with regards to the latest upload to the mentors queue - I have now
merged in the proposed fix for Bug #869953





On 15 August 2017 at 23:17, foss.freedom <foss.freedom@gmail.com> wrote:
> thanks.
>
> I have doubled checked the bug number in the 10.2.9-3 release - this
> was released to unstable whilst 10.3 was in experimental.  I've
> updated the changelog to reflect this.
>
> I've pulled the budgie 10.4 release notes from the upstream
> announcement and added it to the changelog-announcement.txt
>
> Ack 4.0.1 and Standards-Version.
>
> I've double checked 4.0.1 and 4.0.0 to double check.  bookmarked this
> checklist as well for the future.
>
> I've done a further rebuild to confirm that the changelog changes are
> ok.  Also uploaded to mentors.
>
> On 15 August 2017 at 21:48, Andrey Rahmatullin <wrar@debian.org> wrote:
>> On Tue, Aug 15, 2017 at 09:33:48PM +0100, foss.freedom wrote:
>>>     - Merge changelog for 10.2.9-3 Stretch bug-fix release;
>>>       v10.2.9-3 is a hotfix for Stretch released after the v10.3.x
>>>       series was uploaded to testing
>> 10.2.9-3 is not in stretch.
>> We don't upload to testing.
>> We don't prepend "v" to package versions.
>>
>>>     - debian/rules: add override_dh_installchangelogs with
>>>       debian/changelog-announcement.txt to describe
>>>       where to find the upstream announcement and description of changes
>> This is is wrong, it should contain the upstream changelog directly if
>> present.
>>
>>> >>     - debian/control: standards version 4.0.0
>>> >Current one is 4.0.1.
>>>
>>> My unstable build is up-to-date as of today.  Building does not
>>> recognise 4.0.1
>> Please read what does this field mean:
>> https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-Version
>>
>>> I've updated the standards-version as requested though
>> You shouldn't blindly update it, you should go through
>> https://www.debian.org/doc/debian-policy/upgrading-checklist.html and make
>> sure the package actually conforms to the new policy version.
>>
>> --
>> WBR, wRAR