Hello Andrey, thanks for the feedback.
The back-story on this is an age old issue with budgie-desktop. Using the standard rules we would prefer such as in the PR https://github.com/UbuntuBudgie/budgie-desktop/pull/2 the whole desktop does not actually start. This has been discussed at length with upstream (https://github.com/budgie-desktop/budgie-desktop/issues/297) until later discovering a more old fashioned build method works successfully on the debian derivative Ubuntu. It is unknown why debhelper and the manual build mechanism differ so subtly. With upstream dumping Vala and moving to C in the upcoming budgie-desktop v11 I am more confident a straightforward debian/rules will be possible. The I/P/W lintian stuff is the same as previous versions of budgie-desktop. David On 17 December 2016 at 11:40, Andrey Rahmatullin <w...@debian.org> wrote: > Control: tags -1 + moreinfo > > On Sat, Dec 17, 2016 at 11:27:48AM +0000, foss.freedom wrote: >> Have run lintian -i -I on the built .deb, changes and sources files > Running it on the binary .changes would be enough. > Anyway, here is the full output: > > P: budgie-desktop source: debian-watch-may-check-gpg-signature > I: libbudgietheme0: hardening-no-bindnow usr/lib/libbudgietheme.so.0.0.0 > P: libbudgietheme0: no-upstream-changelog > I: libbudgietheme0: no-symbols-control-file usr/lib/libbudgietheme.so.0.0.0 > I: libraven0: hardening-no-fortify-functions usr/lib/libraven.so.0.0.0 > I: libraven0: spelling-error-in-binary usr/lib/libraven.so.0.0.0 Udpating > Updating > I: libraven0: hardening-no-bindnow usr/lib/libraven.so.0.0.0 > 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-desktop: no-upstream-changelog > P: budgie-core-dev: no-upstream-changelog > I: budgie-core: hardening-no-fortify-functions usr/bin/budgie-daemon > I: budgie-core: hardening-no-fortify-functions usr/bin/budgie-panel > I: budgie-core: hardening-no-fortify-functions usr/bin/budgie-polkit-dialog > I: budgie-core: hardening-no-fortify-functions ... use --no-tag-display-limit > to see all (or pipe to a file/program) > I: budgie-core: hardening-no-bindnow usr/bin/budgie-daemon > I: budgie-core: spelling-error-in-binary usr/bin/budgie-panel Reseting > Resetting > I: budgie-core: hardening-no-bindnow usr/bin/budgie-panel > I: budgie-core: hardening-no-bindnow usr/bin/budgie-polkit-dialog > I: budgie-core: hardening-no-bindnow ... use --no-tag-display-limit to see > all (or pipe to a file/program) > I: budgie-core: spelling-error-in-binary > usr/lib/budgie-desktop/plugins/libstatusapplet.so Udpating Updating > I: budgie-core: spelling-error-in-binary > usr/lib/budgie-desktop/plugins/libuserindicator.so Udpating Updating > P: budgie-core: no-upstream-changelog > W: budgie-core: binary-without-manpage usr/bin/budgie-daemon > W: budgie-core: binary-without-manpage usr/bin/budgie-desktop > W: budgie-core: binary-without-manpage usr/bin/budgie-panel > W: budgie-core: binary-without-manpage ... use --no-tag-display-limit to see > all (or pipe to a file/program) > I: budgie-core: desktop-entry-lacks-keywords-entry > usr/share/xsessions/budgie-desktop.desktop > I: libbudgie-plugin0: hardening-no-bindnow usr/lib/libbudgie-plugin.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 > P: gir1.2-budgie-desktop-1.0: no-upstream-changelog > >> Have also checked that it is still not possible to simplify the >> packaging rules set with debhelper 10 - the age old issue of the built >> packages not working with a simplified debhelper rules set is still >> there in Ubuntu Zesty. > What issue are you talking about? > > Also, why are you running autoreconf manually? > > -- > WBR, wRAR
