-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adeodato Simó skrev:
>   Thanks to you for adopting a package (though I don't see any orphaning
>   bug, nor a note in the changelog telling if this was agreed with the
>   maintainer or not; perhaps this information was elsewere, was it?)

Thank you for your consideration. The package was not orphaned at
the time of adoption.

As for documenting a formal adoption agreement in the changelog; I
have not seen any policy that mandate this. I can understand your
question from a transparency point of view; But I have not found any
Debian documentation that make this a requirement.

>>   * Closes: #314856: Missing pre-dependency on debconf.
> 
> 
>   Anyway, back topic: if you have removed the upgrade path, then please
>   note it in the changelog. The wording you have used leads to thinking
>   that you've just added the pre-dependency on debconf, which is not the
>   case. It's very useful to have changelog entries with detailed
>   information of what changes were done to fix a certain bug.

There never was an upgrade path. The debconf stuff in preinst should
never have been there. I don't know the history behind this exactly,
but I'm pretty sure it was a leftover from sqlite 2.x, which exist
in parallel and lives it's own life. The upgrade path is all about
sqlite 2.x, not sqlite 3.x.

As for putting more detailed information in changelog; If I had made
an actual addition or removal I would surely have mentioned it in
the changelog. In this case, I considered it to be a minor cleanup
and choosed not to comment it any further beside the reference to
the bug report.

Thank you for caring.

- --
Tomas Fasth <[EMAIL PROTECTED]>
GnuPG Fingerprint: DC7B 9453 7F26 1BF9 6B21 9F90 C187 7355 9FE8 D504

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC8ipmwYdzVZ/o1QQRAnjIAJwOJYtxlXK9VGdSxP2RuHmkLKPTkACfZ9N+
y5lwwQfaZKYMFhAIViiSBUQ=
=nsfl
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to