Hello Andrey: > It would be nice if you looked at that page and decided to do something > with at least the big red items. It wouls also be nices if you ran lintian > locally and read the output. > > > libapache2-mod-authnz-external (3.3.3-1) unstable; urgency=medium > > . > > * New upstream release (Josef Liska & Micah Andersen - July 22, 2019).
I am fairly new to this so bear with me. I am updating from the previous version (3.3.2-3) and kept the configuration consistent. Now, I realize that this is not an excuse to leave lintian warnings alone, but I also don't necessarily expect to resolve everything on the immediate version. That being said, the warnings and errors that I see locally (debuild -us -uc) are E: libapache2-mod-authnz-external changes: bad-distribution-in-changes-file unstable W: libapache2-mod-authnz-external source: newer-standards-version 4.7.3 (current is 4.6.2) W: libapache2-mod-authnz-external source: obsolete-url-in-packaging http://code.google.com/p/mod-auth-external/downloads/list?can=1 [debian/watch] The first, "unstable", is expected since I understand I am to upload it as such before it gets officially published. The second, standards version, I will not fully resolve since my Ubuntu 24 does not have 4.7.3. The last, with the obsolete url, I anticipate removing in the future and wanted to phase it out with the updated upstream location. Concerning the mentors.debain.net issues, these are more difficult for me to understand why they are different than my local system. I am especially confused as to why debuild and the consistent configuration would give a malformed archive. What would be the best way to resolve this? For the NMU warning, I thought that since I am adopting this, that all I needed was to include my name as the maintainer; am I also supposed to have something special in the changelog? > It should be just "New upstream release" Then the additional information is inappropriate. Thank you, I will remove this along with other changes incurred from our discussion. > This doesn't belong here, please read and follow > https://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog > and > https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.en.html#writing-useful-changelog-entries I had thought that I read somewhere in the documentation to preserve the upstream changelog entries. I had read a lot in preparing this so it seems as though I am mistaken. Thank you, I will remove this along with other changes incurred from our discussion. ~Matthew J.Turner
