2010/5/3 Modestas Vainius <modes...@vainius.eu>:
> No, you don't need to start -2 revision for these changes because -1 has never
> been officially uploaded to Debian. This also means that you don't need to
> document changes in the changelog until initial release is uploaded to Debian
> archive. So basically, you can just drop this -2 entry completely. Please
> remove 0.3.2-1 tag as well since it is invalid and does not point to official
> upload.

OK. Made these changes.

> We set changelog entry distribution field to UNRELEASED until the package is
> actually uploaded to Debian archive. I suggest you follow this path too. Read
> more at http://wiki.debian.org/PkgKde/DchUse UNRELEASED still is called
> changelog heuristic.
> In your case, debian/changelog should look the following until packaging is
> still in development:
> libdbusmenu-qt (0.3.2-1) UNRELEASED; urgency=low
>  * Initial release. (Closes: #579677)
>  -- Praveen Arimbrathodiyil (A proud GNU user) <prav...@gmail.com>  Mon, 26
> Apr 2010 19:15:31 +0530
>> +
>> +override_dh_makeshlibs:
>> +     dh_makeshlibs -V 'libdbusmenu-qt2 (>=0.3.2)'
>> +     dpkg-shlibdeps debian/tmp/usr/lib/*
> What is that dpkg-shlibdeps command for?

lintian was complaining about so files (I don't remember the exact
warning, but it is not coming now - may be one of the intermediate
versions with incomplete changes) and when looking at the docs I saw

"If you have multiple binary packages, you will need to call
dpkg-shlibdeps on each one which contains compiled libraries or

But it seems redundant, now removed.

പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)


Reply via email to