I did push a new branch 'profanity-0.5' to the collab-maint repository, containing solely the new version of profanity. https://anonscm.debian.org/cgit/collab-maint/profanity.git/log/?h=profanity-0.5
From d/changelog: > * Imported Upstream version 0.5.0: > - requires new version of libstrophe (>= 0.9.0) > * Enable GTK status bar icons, Xscreensaver timeout > and C-plugin support > * Patches > - removed (obsolete) fix_spelling_error.patch > - introduced new fix-spelling-errors.patch > * Update Standards-Version to 3.9.8 There are still some issues lintian complains about (especially the new library profanity 0.5 comes with): > I: profanity source: vcs-field-uses-insecure-uri vcs-git > git://anonscm.debian.org/collab-maint/profanity.git > W: profanity source: changelog-should-mention-nmu > P: profanity source: debian-watch-may-check-gpg-signature > W: profanity: package-name-doesnt-match-sonames libprofanity > E: profanity: non-empty-dependency_libs-in-la-file > usr/lib/x86_64-linux-gnu/libprofanity.la > W: profanity: shlib-without-versioned-soname > usr/lib/x86_64-linux-gnu/libprofanity.so libprofanity.so > I: profanity: no-symbols-control-file usr/lib/x86_64-linux-gnu/libprofanity.so > E: profanity: package-must-activate-ldconfig-trigger > usr/lib/x86_64-linux-gnu/libprofanity.so Dariusz told me he has some doubts about splitting libprofanity from the main profanity package, however I don't know how else to fix these shared-object library issues. Maybe someone else can look into that.
signature.asc
Description: OpenPGP digital signature
