Thanks Andrey.

I've revised the packaging as follows:

New changelog:

  * New upstream release
  * Packaging Changes
    - remove all unneeded triggers
    - debian/control: standards version 4.0.1
    - debian/control: Add build dependency sassc
    - debian/control: add minimum meson version to build
    - debian/control: Add Build-Depends alternate libmutter-1-dev
      for GNOME 3.26 builds
    - debian/control: correct typo in Vcs-Git
    - drop all patches since now dealt with in new release
    - update library symbols files with 10.4 changes
    - Rename binary package gir1.2-budgie-desktop-1.0 to
      match the typelib gir1.2-budgie-1.0; To ensure a smooth upgrade,
      debian/control updated with Replaces/Breaks for the new package
      and budgie-desktop with a restriction for 10.4 and later for the
      new package
    - Add man-page for new binary budgie-desktop-settings
    - Updated debian/copyright for all source files
    - 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
    - debian/rules: add override_dh_installchangelogs with
      debian/changelog-announcement.txt to describe
      where to find the upstream announcement and description of changes
    - add budgie-core.lintian-override with comment to describe
      the rpath lintian error; the error has not been overridden
      in this file since it is valid but without any workaround


>> I have double checked lintian -i -I for the built .dsc
> This checks only the source package which is wrong. You need to check the
binary .changes. Also, you've missed -E --pedantic.

Correct - my bad.  I really should not be packaging well past midnight!

> E: budgie-desktop changes: orig-tarball-missing-upstream-signature 
> budgie-desktop_10.4.orig.tar.xz
Strange - I've redownloaded the .asc and it now appears to be uploaded correctly

> I: budgie-desktop source: testsuite-autopkgtest-missing
I'll discuss this with upstream as some point

>P: budgie-desktop: no-upstream-changelog
>P: libbudgietheme0: no-upstream-changelog
fixed
>I: libbudgietheme0: no-symbols-control-file usr/lib/libbudgietheme.so.0.0.0
fixed
>P: libbudgie-plugin0: no-upstream-changelog
fixed
>I: libbudgie-plugin0: no-symbols-control-file usr/lib/libbudgie-plugin.so.0.0.0
fixed
>P: budgie-desktop-doc: no-upstream-changelog
fixed
>I: libraven0: spelling-error-in-binary usr/lib/libraven.so.0.0.0 Udpating 
>Updating
This is an debug message - no change required
>P: libraven0: no-upstream-changelog
fixed
>X: libraven0: shlib-calls-exit usr/lib/libraven.so.0.0.0
seems to be an experimental lintian issue - no change made
>I: libraven0: no-symbols-control-file usr/lib/libraven.so.0.0.0
fixed
>P: budgie-core-dev: no-upstream-changelog
fixed
>P: gir1.2-budgie-1.0: no-upstream-changelog
fixed
>I: gir1.2-budgie-1.0: typelib-not-in-multiarch-directory 
>usr/lib/girepository-1.0/Budgie-1.0.typelib 
>usr/lib/x86_64-linux-gnu/girepository-1.0

The last time I tested budgie-desktop with multiarch compilation the
desktop refused to initialise.  Multiarch is something upstream does
not do - so I prefer here to keep to the way upstream builds and tests
the desktop

>I: budgie-core: spelling-error-in-binary usr/bin/budgie-panel overriden 
>overridden
This is a debug message - no change required
>E: budgie-core: binary-or-shlib-defines-rpath usr/bin/budgie-wm 
>/usr/lib/x86_64-linux-gnu/mutter
I've added a linitian-override file with an explanation for this - I
haven't actually overridden the message since its valid.  No change
possible here.

>I: budgie-core: spelling-error-in-binary 
>usr/lib/budgie-desktop/plugins/org.budgie-desktop.applet.status/libstatusapplet.so
> Udpating Updating
This is a debug message - no change required

>P: budgie-core: no-upstream-changelog
fixed
>I: budgie-core: desktop-entry-lacks-keywords-entry 
>usr/share/applications/budgie-desktop-settings.desktop
>I: budgie-core: desktop-entry-lacks-keywords-entry 
>usr/share/xsessions/budgie-desktop.desktop
I'll discuss this with upstream at some point.  No change made

>>   Changes since the last upload:
>>
>>   * New upstream release
>>     - Software Highlights:
>>     - Fix Highlights:
>Please don't describe upstream changes in debian/changelog.
Deleted
>>     - 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 - sid appears to be at 4.0.0.  So a bit confused here.
I've updated the standards-version as requested though

>>     - debian/control: Add alternate libmutter-1 version for GNOME 3.26
>Add where?
Updated the changelog to explain
>>     - drop all unnecessary library symbols files
>Why are they unnecessary?
I've reverted this - symbols have been updated with 10.4 changes
>>>     - Merge changelog for 10.2.9-3 bug-fix release
>What does this mean?

I've explained this further in the changelog.  Hopefully this
clarifies this - its something Gianfranco asked me to include that I
didnt merge with the last update to unstable (v10.3.1-4)

On 15 August 2017 at 07:19, Andrey Rahmatullin <w...@debian.org> wrote:
> On Tue, Aug 15, 2017 at 12:21:41AM +0100, foss.freedom wrote:
>> I have double checked lintian -i -I for the built .dsc
> This checks only the source package which is wrong. You need to check the
> binary .changes. Also, you've missed -E --pedantic.
>
> E: budgie-desktop changes: orig-tarball-missing-upstream-signature 
> budgie-desktop_10.4.orig.tar.xz
> I: budgie-desktop source: testsuite-autopkgtest-missing
> P: budgie-desktop: no-upstream-changelog
> P: libbudgietheme0: no-upstream-changelog
> I: libbudgietheme0: no-symbols-control-file usr/lib/libbudgietheme.so.0.0.0
> P: libbudgie-plugin0: no-upstream-changelog
> I: libbudgie-plugin0: no-symbols-control-file 
> usr/lib/libbudgie-plugin.so.0.0.0
> P: budgie-desktop-doc: no-upstream-changelog
> I: libraven0: spelling-error-in-binary usr/lib/libraven.so.0.0.0 Udpating 
> Updating
> P: libraven0: no-upstream-changelog
> X: libraven0: shlib-calls-exit usr/lib/libraven.so.0.0.0
> I: libraven0: no-symbols-control-file usr/lib/libraven.so.0.0.0
> P: budgie-core-dev: no-upstream-changelog
> P: gir1.2-budgie-1.0: no-upstream-changelog
> I: gir1.2-budgie-1.0: typelib-not-in-multiarch-directory 
> usr/lib/girepository-1.0/Budgie-1.0.typelib 
> usr/lib/x86_64-linux-gnu/girepository-1.0
> I: budgie-core: spelling-error-in-binary usr/bin/budgie-panel overriden 
> overridden
> E: budgie-core: binary-or-shlib-defines-rpath usr/bin/budgie-wm 
> /usr/lib/x86_64-linux-gnu/mutter
> I: budgie-core: spelling-error-in-binary 
> usr/lib/budgie-desktop/plugins/org.budgie-desktop.applet.status/libstatusapplet.so
>  Udpating Updating
> P: budgie-core: no-upstream-changelog
> I: budgie-core: desktop-entry-lacks-keywords-entry 
> usr/share/applications/budgie-desktop-settings.desktop
> I: budgie-core: desktop-entry-lacks-keywords-entry 
> usr/share/xsessions/budgie-desktop.desktop
>
>
>>   Changes since the last upload:
>>
>>   * New upstream release
>>     - Software Highlights:
>>     - Fix Highlights:
> Please don't describe upstream changes in debian/changelog.
>>     - debian/control: standards version 4.0.0
> Current one is 4.0.1.
>>     - debian/control: Add alternate libmutter-1 version for GNOME 3.26
> Add where?
>>     - drop all unnecessary library symbols files
> Why are they unnecessary?
>>     - Merge changelog for 10.2.9-3 bug-fix release
> What does this mean?
>
> --
> WBR, wRAR

Reply via email to